Skip to content
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

Restarting service fails after modules get into an invalid state #28

Open
theGhostJW opened this issue Aug 15, 2018 · 0 comments
Open

Comments

@theGhostJW
Copy link

theGhostJW commented Aug 15, 2018

ide-haskell-hie: 0.10.1
atom: 1.29.0
Windows 10

  1. Invoke hie:restart-server

expect server restart
actual spinner just keeps spinning

  • mouse hover over : stopping hie for [project name] x 3

console reveals

many of
C:\Users\thegh\.atom\packages\ide-haskell-hie\node_modules\vscode-jsonrpc\lib\messages.js:46 Uncaught (in promise) Error
    at new ResponseError (C:\Users\thegh\.atom\packages\ide-haskell-hie\node_modules\vscode-jsonrpc\lib\messages.js:46:28)
    at handleResponse (C:\Users\thegh\.atom\packages\ide-haskell-hie\node_modules\vscode-jsonrpc\lib\main.js:430:48)
    at processMessageQueue (C:\Users\thegh\.atom\packages\ide-haskell-hie\node_modules\vscode-jsonrpc\lib\main.js:258:17)
    at Immediate._onImmediate (C:\Users\thegh\.atom\packages\ide-haskell-hie\node_modules\vscode-jsonrpc\lib\main.js:242:13)
    at runCallback (timers.js:789:20)
    at tryOnImmediate (timers.js:751:5)
    at processImmediate [as _immediateCallback] (timers.js:722:5)                                                                                                                     

followed by many of
       index.html:1
Uncaught (in promise) Error: Connection got disposed.                                     
    at Object.dispose (C:\Users\thegh\.atom\packages\ide-haskell-hie\node_modules\vscode-jsonrpc\lib\main.js:825:25)
    at LanguageClientConnection.dispose (C:\Users\thegh\.atom\packages\ide-haskell-hie\node_modules\atom-languageclient\build\lib\languageclient.js:47:19)
    at ServerManager.exitServer (C:\Users\thegh\.atom\packages\ide-haskell-hie\node_modules\atom-languageclient\build\lib\server-manager.js:209:35)
    at ServerManager.<anonymous> (C:\Users\thegh\.atom\packages\ide-haskell-hie\node_modules\atom-languageclient\build\lib\server-manager.js:196:22)
    at Generator.next (<anonymous>)
    at fulfilled (C:\Users\thegh\.atom\packages\ide-haskell-hie\node_modules\atom-languageclient\build\lib\server-manager.js:4:58)
    at <anonymous>

It looks like to trigger this you need the modules to pass through some invalid state. E.g Rename a subfolder of a module is in and save this before renaming the module, then correct the module name or visa versa.

Note: I am using HPack.

Engine will not restart until you restart Atom.

@theGhostJW theGhostJW changed the title Restarting Service Often Fails Restarting service fails after modules get into an invalid state Aug 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant