vscode-as3mxml
vscode-as3mxml copied to clipboard
BowlerHatLLC
Clean up "WARNING: Unmatched cancel notification for request id" in output console
Aug 07, 2018 10:38:44 AM org.eclipse.lsp4j.jsonrpc.RemoteEndpoint handleCancellation WARNING: Unmatched cancel notification for request id 3
eclipse/lsp4j Documentation:
https://github.com/eclipse/lsp4j/blob/master/documentation/README.md#cancellation-support
EDIT: After implementing the cancellation checking, this message has not disappeared. I don't know why. It is unlikely that this will be fixed any time soon, unless someone else can figure it out.
I often get an error "Interface... is implemented with an incompatible signature..."
when using multi-root workspace. But this is wrong.
Opening the same project in a new VSCode "standalone" instance don't throw this error. This [1] shows the same project once within a multi-root environment and once "standalone".
The outline of the multi-root instance contains this "...Unmatched cancel notification..." warning.
Is there a chance that this beahviour will be fixed with this issue or should I create a new one?
[1] Comparing mutli-root and standalone
The interface issue is completely unrelated to the unmatched cancel notification warning.
Ok, I'll try to prepare a simple test case soon. When I am able to reproduce this issue I will file a new issue here.
I often get an error "Interface... is implemented with an incompatible signature..." ... When I am able to reproduce this issue I will file a new issue here.
@joshtynjala
Just for the sake of completeness:
Piotr has pointed me out that I accidently forgot to add needded sources to the source-path in some cases. This was the cause for the described issue ... sorry for the noise! ;-)
@joshtynjala I found that one way to reproduce this issue (even with 0.16.0) is to run "Organize imports" while a file contains "Ambiguous references" (More than one import for a class of the same name). Maybe this helps...
@olafkrueger Thanks, Olaf. Unfortunately, I simply can't figure out how to fix the issue. I can reproduce it pretty easily, but when I try to implement cancel checking the way that it is documented, it seems to have no effect. I don't know why.