Attempting to stop the IDE server results in a bunch of `ECONNREFUSED` errors
garyb opened this issue · 5 comments
On Windows again...
Between one and five of these:
Error: Request workspace/executeCommand failed with message: connect ECONNREFUSED 127.0.0.1:15156
at new ResponseError (C:\Users\Gary\.atom\packages\ide-purescript\node_modules\vscode-jsonrpc\lib\messages.js:46)
at handleResponse (C:\Users\Gary\.atom\packages\ide-purescript\node_modules\vscode-jsonrpc\lib\main.js:430)
at processMessageQueue (C:\Users\Gary\.atom\packages\ide-purescript\node_modules\vscode-jsonrpc\lib\main.js:258)
at Immediate.<anonymous> (C:\Users\Gary\.atom\packages\ide-purescript\node_modules\vscode-jsonrpc\lib\main.js:242)
at runCallback (timers.js:651)
at tryOnImmediate (timers.js:624)
at processImmediate [as _immediateCallback] (timers.js:596)
kind of errors pop up together. This also prevents the restart server action from working, although after this explodes you can use the start server action and it seems to work - so it does actually shut the server down.
Is this when the server was running happily at the time? Or were you attempting to restart from a position of something being broken?
Yeah, it happens when everything is running happily. It actually behaves the same way regardless of whether the server is running or not.
Can you check this again, there are some relevant changes - and in particular restart should do the start even if the stop part fails
I think this is good now, it's a little hard for me to tell since there's no feedback at all now - I assume that means it is working though!
I still see an error when stopping the server, but both start and restart do get things running again.
I'll comment back here again if it fails next time I have a need to restart the server (I'll know for sure if it works then, as restarting should fix the problem if it has some cached state or something).
It does indeed work properly now. Thanks!