-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
handle not found files for plugins properly #6002
Conversation
@yeweiasia Could you check whether you can reproduce #5967 with this PR? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only "danger" I see with this change is that there is a code path that does not send a response to the client. The old code would always send a response, even if too late in some cases.
The old code was always failing because it was trying to send an error response when a file was found or request was already closed with another error. |
- don't fail if a file is found - don't swallow an error bug log it - only send 404 if res was not responded already Signed-off-by: Anton Kosyakov <anton.kosyakov@typefox.io>
4722611
to
d809196
Compare
@tsmaeder I've updated code with comments and mapping all other errors to 500. |
@akosyakov thx, lgtm. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested with https://github.com/vinokurig/Test.git plugin. The plugin works as expected, no errors in the console
@vinokurig please rebase your PR, i will test it then |
I synced the code with mater HEAD, It seems that all vscode plugin fail to start properly, I don't have much time to diagnose today, deep diagnostics can be provided this weekend. |
What it does
handle not found files for plugins properly:
How to test
plugins
and compile itReview checklist
Reminder for reviewers