-
Notifications
You must be signed in to change notification settings - Fork 255
Racer error propagated to user #122
Comments
I believe that we do in fact catch it, but that before catching the panicking thread prints an error message to stderr which appears in the VSCode console. We could install a panic handler to not print the panic, but that would also override the behaviour on the main thread which may or may not be desirable. In any case, the RLS itself does not crash, so I don't think this is super important to fix, |
Do you mean this message?
This is not printed on stderr. All stderr is captured in the vscode extension an thrown away. It is caused by this line in out.failure(id, "GotoDef failed to complete successfully"); |
stderr is not thrown away, you can see it in the console if you switch to the RLS view. I'm talking about the "thread has panicked" + backtrace message. |
I realized that you are probably running the extension in |
If you get a jump to def error in Racer, we should catch it, not panic.
The text was updated successfully, but these errors were encountered: