Open alex35mil opened 6 years ago
Looks like it's because the atom-languageclient watches the plugin config changes very fast, and read some uncompleted input.
Sorry that I didn't look your error stack before, the stack contains some from ide-flowtype, not ide-reason, it's strange, but I didn't find some clue after a quick look at ide-flowtype's source, I guess it's still caused by atom-languageclient.
at LanguageClientConnection._sendNotification (/packages/ide-flowtype/node_modules/atom-languageclient/build/lib/languageclient.js:341:19) at LanguageClientConnection.didChangeConfiguration (/packages/ide-flowtype/node_modules/atom-languageclient/build/lib/languageclient.js:120:14) at _disposable.add.atom.config.observe (/packages/ide-flowtype/node_modules/atom-languageclient/build/lib/auto-languageclient.js:262:36) at /Applications/Atom.app/Contents/Resources/app/src/config.js:676:22
Yeah, I checked ide-flowtype
sources as well and it doesn't seem related to their FlowLanguageClient
class.
Sometimes when I type not fast enough in
diagnostics.tools
field (e.g.bsb, merl
) I get hard errorUncaught Error: Connection is closed.
.Something to investigate.
Atom: 1.24.1 x64 Electron: 1.6.16 OS: Mac OS X 10.12.6 Thrown From: ide-reason package 0.1.12
Stack Trace
Uncaught Error: Connection is closed.
Non-Core Packages