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

Remove roslyn implementation of error list #62741

Merged
merged 59 commits into from
Mar 7, 2024

Conversation

CyrusNajmabadi
Copy link
Member

@CyrusNajmabadi CyrusNajmabadi commented Jul 18, 2022

WIP. Can be merged in once we get enough confidence on LSP pull diagnostics.

Note: there would be a lot more cleanup after this. Lots of push-related diagnostic code needs to go away. I'm trying to figure out nice independent chunks that can be pulled out to make this manageable.

See also: #62735

@CyrusNajmabadi CyrusNajmabadi marked this pull request as ready for review March 6, 2024 18:31
@CyrusNajmabadi CyrusNajmabadi requested a review from a team as a code owner March 6, 2024 18:31
@CyrusNajmabadi
Copy link
Member Author

@dibarbet @davidwengier @mavasani @sharwell . Followup to #62735, but can be removed now (effectively almost all deletions).

//
// Temporary code. To keep tests running which test legacy behavior, we allow tests to configure this
// behavior. This code will be removed when we remove the legacy behavior entirely.
return GlobalOptions.GetOption(DiagnosticOptionsStorage.PullDiagnosticsFeatureFlag) ? NoOpIncrementalAnalyzer.Instance : analyzer;
Copy link
Member Author

Choose a reason for hiding this comment

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

Will be removed in followup.

return;

await Task.Delay(TimeSpan.FromSeconds(1));
}
Copy link
Member Author

Choose a reason for hiding this comment

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

no current way to ask lsp when it's done updating the UI. so polling for now.

Copy link
Contributor

Choose a reason for hiding this comment

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

We have code in Razor that uses events and a semaphore to wait for errors in a slightly better way, if you're interested in future. I suspect neither is ideal though :)

https://github.com/dotnet/razor/blob/main/src/Razor/test/Microsoft.VisualStudio.Razor.IntegrationTests/InProcess/ErrorListInProcess.cs#L21

@CyrusNajmabadi CyrusNajmabadi requested a review from a team as a code owner March 6, 2024 22:41
@davidwengier
Copy link
Contributor

Can #62735 be merged first to simplify the review here?

@CyrusNajmabadi
Copy link
Member Author

@davidwengier this is ready now. Thanks!

@CyrusNajmabadi
Copy link
Member Author

@mavasani @dibarbet @sharwell this is ready for review.

@@ -109,7 +109,7 @@ End Namespace
string.Join(Environment.NewLine, actualContents));
}

[IdeFact, WorkItem("https://dev.azure.com/devdiv/DevDiv/_workitems/edit/1643350")]
[IdeFact(Skip = "https://github.com/dotnet/roslyn/issues/72428"), WorkItem("https://dev.azure.com/devdiv/DevDiv/_workitems/edit/1643350")]
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this test skipped because of the "tiny time slice" while things are loading? If so, seems it would be better to set the feature flag in the registry before running VS for the tests, to ensure not delay waiting for TN.

@CyrusNajmabadi CyrusNajmabadi merged commit 8c55b1f into dotnet:main Mar 7, 2024
27 checks passed
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Mar 7, 2024
@CyrusNajmabadi CyrusNajmabadi deleted the errorListRemoval branch March 7, 2024 15:57
@RikkiGibson RikkiGibson modified the milestones: Next, 17.10 P3 Mar 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants