Eugleo / magic-racket

The best coding experience for Racket in VS Code
https://marketplace.visualstudio.com/items?itemName=evzen-wybitul.magic-racket
GNU General Public License v3.0
204 stars 27 forks source link

Extension gets killed on Version Control screen #38

Closed Runi-c closed 3 years ago

Runi-c commented 3 years ago

Environment

Error

The extension (or possibly just the langserver?) crashes or is killed in certain screens.

Additional context

In particular, switching to the Version Control tab instantly kills the extension for me, and my only recourse is to restart VSC.


I've been working on racket-langserver of late so I'm doing a lot of testing with Magic Racket, but I really can't figure out what's happening here.

image

  1. When switching to the source control tab after being in another area of the editor, the "Racket Language Client" section of Output is simply killed. I don't see any output appear before it dies.
  2. When restarting the editor while on source control tab, I can see the "Racket Language Client" section, but there are only ever two messages: the client sends Initialize and then immediately Shutdown, without even a few ms for the server to respond.
Runi-c commented 3 years ago

Just thought to check the Log (Extension Host). Here's the log when I reload window with the source control tab showing:

[2021-04-02 16:18:32.320] [exthost] [info] extension host started
[2021-04-02 16:18:32.380] [exthost] [info] ExtensionService#_doActivateExtension vscode.microsoft-authentication 
[2021-04-02 16:18:32.380] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/microsoft-authentication/dist/extension.js
[2021-04-02 16:18:32.386] [exthost] [info] ExtensionService#_doActivateExtension evzen-wybitul.magic-racket {"startup":false,"extensionId":{"value":"evzen-wybitul.magic-racket","_lower":"evzen-wybitul.magic-racket"},"activationEvent":"onLanguage:racket"}
[2021-04-02 16:18:32.386] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/Work/.vscode/extensions/evzen-wybitul.magic-racket-0.5.7/out/extension.js
[2021-04-02 16:18:32.427] [exthost] [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch 
[2021-04-02 16:18:32.428] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/debug-auto-launch/dist/extension
[2021-04-02 16:18:32.429] [exthost] [info] ExtensionService#_doActivateExtension vscode.git {"startup":true,"extensionId":
[2021-04-02 16:18:32.429] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/git/dist/main
[2021-04-02 16:18:32.439] [exthost] [info] ExtensionService#_doActivateExtension lyzerk.linecounter {"startup":true,"extensionId":
[2021-04-02 16:18:32.439] [exthost] [info] ExtensionService#loadCommonJSModule file:///~/.vscode/extensions/lyzerk.linecounter-0.2.7/out/src/extension
[2021-04-02 16:18:32.441] [exthost] [info] ExtensionService#_doActivateExtension vscode.npm
[2021-04-02 16:18:32.441] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/npm/dist/npmMain
[2021-04-02 16:18:32.572] [exthost] [info] ExtensionService#_doActivateExtension vscode.github
[2021-04-02 16:18:32.572] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/github/dist/extension.js
[2021-04-02 16:18:32.594] [exthost] [info] eager extensions activated
[2021-04-02 16:18:32.604] [exthost] [info] ExtensionService#_doActivateExtension ms-vscode.js-debug 
[2021-04-02 16:18:32.605] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/ms-vscode.js-debug/src/extension.js
[2021-04-02 16:18:32.654] [exthost] [info] ExtensionService#_doActivateExtension vscode.emmet
[2021-04-02 16:18:32.654] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/emmet/dist/node/emmetNodeMain
[2021-04-02 16:18:32.659] [exthost] [info] ExtensionService#_doActivateExtension vscode.merge-conflict 
[2021-04-02 16:18:32.659] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/merge-conflict/dist/mergeConflictMain
[2021-04-02 16:18:32.661] [exthost] [info] ExtensionService#_doActivateExtension ms-vscode-remote.remote-wsl-recommender 
[2021-04-02 16:18:32.661] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/ms-vscode-remote.remote-wsl-recommender/dist/extension.js
[2021-04-02 16:18:32.665] [exthost] [info] ExtensionService#_doActivateExtension vscode.testing-editor-contributions 
[2021-04-02 16:18:32.665] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/testing-editor-contributions/dist/extension.js
[2021-04-02 16:18:32.665] [exthost] [info] ExtensionService#_doActivateExtension ms-vscode-remote.remote-wsl 
[2021-04-02 16:18:32.665] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/Work/.vscode/extensions/ms-vscode-remote.remote-wsl-0.54.6/dist/extension
[2021-04-02 16:18:32.745] [exthost] [info] ExtensionService#_doActivateExtension vscode.github-authentication 
[2021-04-02 16:18:32.746] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Program Files/Microsoft VS Code/resources/app/extensions/github-authentication/dist/extension.js
[2021-04-02 16:18:36.430] [exthost] [error] [evzen-wybitul.magic-racket] provider FAILED
[2021-04-02 16:18:36.431] [exthost] [error] Error: Language client is not ready yet
at LanguageClient.sendRequest (~\.vscode\extensions\evzen-wybitul.magic-racket-0.5.7\node_modules\vscode-languageclient\lib\client.js:1789:19)
    at _provideDocumentSymbols (~\.vscode\extensions\evzen-wybitul.magic-racket-0.5.7\node_modules\vscode-languageclient\lib\client.js:1075:35)
    at Object.provideDocumentSymbols (~\.vscode\extensions\evzen-wybitul.magic-racket-0.5.7\node_modules\vscode-languageclient\lib\client.js:1099:23)
    at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:87:153433
    at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:57:7538
    at new Promise (<anonymous>)
    at Object.g [as asPromise] (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:57:7510)
    at o.provideDocumentSymbols (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:87:153404)
    at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:87:176894
    at Se._withAdapter (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:87:176060)
    at Se.$provideDocumentSymbols (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:87:176870)
    at c._doInvokeHandler (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:90:10509)
    at c._invokeHandler (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:90:10201)
    at c._receiveRequest (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:90:8820)
    at c._receiveOneMessage (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:90:7673)
    at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:90:5782
    at g.fire (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:57:1836)
    at p.fire (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:65:15443)
    at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:106:29119
    at g.fire (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:57:1836)
    at p.fire (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:65:15443)
    at t._receiveMessage (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:65:20693)
    at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:65:17587
    at g.fire (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:57:1836)
    at l.acceptChunk (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:65:12808)
    at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:65:12156
    at Socket.E (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:106:12375)
    at Socket.emit (events.js:315:20)
    at addChunk (_stream_readable.js:295:12)
    at readableAddChunk (_stream_readable.js:271:9)
    at Socket.Readable.push (_stream_readable.js:212:10)
    at Pipe.onStreamRead (internal/stream_base_commons.js:186:23)

Seems like a bunch of VSC core modules get loaded along with Magic Racket, but then a few seconds later, Magic Racket just has some inexplicable error "Language client is not ready yet" and dies.

However, when I switch to the source control tab after seeing the extension functioning properly, there is no message in the log - the extension just simply dies.

None of the other output tabs have anything interesting in them.

I tried manually updating the vscode-languageclient package mentioned in the stack trace, but the exact same bad behavior still happens.