-
Notifications
You must be signed in to change notification settings - Fork 4
Uncaught Error: Connection is closed. #2
Comments
Very likely that there's a conflict between this package and |
|
I'll see if I can reproduce when I get home; running Linux at work. If you don't mind, try enabling LSP debugging in Atom-IDE; this is an undocumented feature, and must be set either directly in your
Once you've enabled debugging, reload Atom and see if any more useful/detailed messages are printed in the console. |
|
I have managed to reproduce the problem, although not 100% reliably yet. Still trying to figure out what is going wrong, and if it is something that can/should be handled on this end or if it is something that needs to be resolved in atom-languageclient (or elsewhere in the dependency chain). |
Let me know how I can help diagnosis! |
[Enter steps to reproduce:]
mitigation: I got a similar error (the same error?) a few days ago and it linked to a different issue. I haven't had time to look into it on my system yet. Atom: 1.21.1 x64 Stack TraceUncaught Error: Connection is closed.
Commands
Non-Core Packages
|
experiencing the same when editing js files. will trigger the same error as above on UI actions (click, type). |
Step to repro
Atom: 1.21.0-beta2 x64
Electron: 1.6.9
OS: Mac OS X 10.12.6
Thrown From: ide-cpp package 0.0.2
Stack Trace
Uncaught Error: Connection is closed.
Commands
Non-Core Packages
The text was updated successfully, but these errors were encountered: