Ensure NFW gets reported before result is reported to client and remove async listener in queue #75907
Conversation
This file contains 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
…ve async listener in queue
dotnet-issue-labeler
bot
added
Area-IDE
untriaged
src/LanguageServer/Protocol/LspServices/RequestTelemetryScope.cs
Outdated
Show resolved
Hide resolved
CyrusNajmabadi
approved these changes
Nov 14, 2024
|
passing optprof (internal only - https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=10559193&view=results) |
This was referenced Nov 17, 2024
dibarbet
added a commit
to dibarbet/roslyn
that referenced
this pull request
Nov 27, 2024
…ve async listener in queue (dotnet#75907) Should resolve https://dev.azure.com/devdiv/DevDiv/_workitems/edit/2224584 Optprof web application tests have been failing for a while in VS. Tim tracked down the issue to an async listener introduced in dotnet#74530 The never completing listener were requests for workspace diagnostics. This is actually expected for workspace diagnostics requests, as they are held open indefinitely if nothing changes (see https://github.com/dotnet/roslyn/blob/main/src/LanguageServer/Protocol/Handler/Diagnostics/AbstractWorkspacePullDiagnosticsHandler.cs#L94). So as long as workspace diagnostics requests function this way, it is easy to get into a situation where there are async listeners that never complete. The queue async listener was introduced to ensure that unit tests could reliably verify if the NFW handler was called (as handling the exception happened after the response was returned to the client). To resolve this issue I did a couple things 1. Move reporting NFW for request exceptions into the telemetry reporting scope. Importantly this scope is called before the result is sent back to the client. This allows unit tests to simply wait for the request to complete before checking if the NFW handler was called (no need for an async listener). 2. Removing the async listener from the queue now that no unit tests need to wait for an action to occur in the queue. TODO - validate optprof
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Should resolve https://dev.azure.com/devdiv/DevDiv/_workitems/edit/2224584
Optprof web application tests have been failing for a while in VS. Tim tracked down the issue to an async listener introduced in #74530
The never completing listener were requests for workspace diagnostics. This is actually expected for workspace diagnostics requests, as they are held open indefinitely if nothing changes (see https://github.com/dotnet/roslyn/blob/main/src/LanguageServer/Protocol/Handler/Diagnostics/AbstractWorkspacePullDiagnosticsHandler.cs#L94). So as long as workspace diagnostics requests function this way, it is easy to get into a situation where there are async listeners that never complete.
The queue async listener was introduced to ensure that unit tests could reliably verify if the NFW handler was called (as handling the exception happened after the response was returned to the client).
To resolve this issue I did a couple things
TODO - validate optprof