-
Notifications
You must be signed in to change notification settings - Fork 1
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
KeyError on on_payload #7
Comments
Which LSP packages are you using? Also if you can catch this when this happens then it would also be useful to provide output from LSP: Log Panel. |
My LSP packages are:
Unfortunately I cannot reproduce it right now. :( |
I've just started working on an LSP-OmniSharp update and I'm seeing this a lot:
|
Does it happen after you edit the plugin file? If so then it sounds like the code that is supposed to unregister the controller doesn't run. Not sure if it's a side effect of plugin reloading that happens on saving it, some bug or maybe even expected. Hard to say without reproduction steps. |
Ah yes, I’m seeing it during editing. I don’t see it during startup. |
Yep it also happens to me a lot. I ended up uninstalling LSP-file-watcher-chokidar because it caused too much noise in the output menu. :( The error doesn't emit a full traceback, so it's not clear exactly where the exception is raised from, but the fix per se should be easy (check that key exists first). |
Are you also working on LSP packages? I need a way to reproduce to understand the issue and potentially fix it. Adding random checks is not necessarily a correct solution because in that case the watcher would still be live and keep using resources. |
No. |
@giampaolo @photex in any case, are you guys using one of these packages? It is happening to me too and I am trying to figure it out too on my end |
I cannot tell how to reproduce this reliably, but sometimes I get:
For me this typically happens on save, and I have some other plugins which may edit the view's text, so that is probable related.
The text was updated successfully, but these errors were encountered: