Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cleanup LSP error reporting #74530

Merged
merged 1 commit into from
Aug 14, 2024
Merged

Conversation

dibarbet
Copy link
Member

@dibarbet dibarbet commented Jul 23, 2024

Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1922370

We were reporting connection lost exceptions when the server shutdown due to refresh notifications being sent during shutdown (they are triggered by events that are not a part of the shutdown handling in the queue).

This modifies the code to catch connection lost exceptions from refresh notifications. Other parts of the system already handle connection loss issues and report failures.

Additionally fixes an issue where we would not report NFW for mutating LSP requests.

@dibarbet dibarbet requested a review from a team as a code owner July 23, 2024 23:51
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead labels Jul 23, 2024
{
if (rethrowExceptions)
{
return nonMutatingRequestTask;
try
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixes a bug here where we would only report NFW for non-mutating requests. If a mutating request failed we would never get fault telemetry for it.

await nonMutatingRequestTask.ConfigureAwait(false);
}
// If we had an exception, we want to record a NFW for it AND propogate it out to the queue so it can be handled appropriately.
catch (Exception ex) when (FatalError.ReportAndPropagateUnlessCanceled(ex, ErrorSeverity.Critical))
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i believe this is the correct pattern to report and throw, but let me know if not.

});

var didReport = false;
FatalError.OverwriteHandler((exception, severity, dumps) =>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tests to verify NFW handler is called for mutating and non-mutating requests

@dibarbet dibarbet merged commit 74270d4 into dotnet:main Aug 14, 2024
25 checks passed
@dibarbet dibarbet deleted the fix_shutdown_error branch August 14, 2024 20:58
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Aug 14, 2024
@dibarbet dibarbet modified the milestones: Next, 17.12 P2 Aug 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants