This repository was archived by the owner on Jan 23, 2023. It is now read-only.
Porting XEvent Delay BugFix from .Net Framework #36015
Merged
Merged
Conversation
|
|
AfsanehR-zz
approved these changes
Mar 13, 2019
Gary-Zh
approved these changes
Mar 13, 2019
This was referenced Mar 14, 2019
picenka21
pushed a commit
to picenka21/runtime
that referenced
this pull request
Feb 18, 2022
…bugfix Porting XEvent Delay BugFix from .Net Framework Commit migrated from dotnet/corefx@8801ab0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The bug description is given below-
The issues is that the XEvents are arriving as expected, but with 1 XEvent delay. It means that to receive the most recent XEvent, the app has to wait for another XEvent to be generated.
For example, when listening for XEvents that fires on every query that the clients are running:
• At startup, if the client is running for example, “select 1”, and then the client doesn't get any XEvent.
• If the client is running “select 2”, then the client receives the “select 1” event.
• If the client is running “select 3”, then the client receives “select 2” event. And so on…
It seems like the server is sending the most recent XEvent on the wire, but the client holds it inside up until the next XEvent is arrived .
This fix already exists in the .Net Framework. This PR merges this fix into .Net Core.