-
Notifications
You must be signed in to change notification settings - Fork 1.7k
[ty] Improve LSP test server logging #21432
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
Conversation
8fb6735 to
f21fcc4
Compare
Diagnostic diff on typing conformance testsNo changes detected when running ty on typing conformance tests ✅ |
|
f21fcc4 to
1a14ddf
Compare
Where do you see that it's taking the dynamic registration path? I don't see the relevant logs in https://github.com/astral-sh/ruff/actions/runs/19290646588/job/55160349507?pr=21363#step:7:5873 |
|
I can't say for certain but looking at the unclaimed response I assumed that it is the register capability request for diagnostics. But taking a second look today I think this isn't the case because a) that would be a request and b) it would include the capability name. I guess I don't know what it is but the new logging should help us to understand what the request with id 2 was. |
It was |
|
That's even weirder... Because we explicitly await that response. Unless the response takes too long, in which case we should panic? Edit: Oh no, we don't. We return an error, but that means that |
|
I think this is a more general issue with how we use I think we should remove the assertion that all messages were consumed in the drop handler and instead expose a method so that test can perform this assertion when they want to. The one assertion that we probably want to keep is that the server never sends a response after exit |
Summary
Improve the test server logging to get to the root cause of why
ty_server::e2e pull_diagnostics::on_did_openflakes (it seems to take the dynamic registration path but it's unclear to me WHY?).Test Plan