-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
LSP not connecting to Racket installed via Snap #109
Comments
OK, I just removed the AFAIK things are working. I'm getting useful warnings (e.g. As a side note, the only error message I'm getting now is:
So still |
I can now verify that all is working correctly. I have a log file of message traffic between |
Thanks for filing this issue! I'm glad you were at least able to get things working, even if you did have to change how Racket is installed. The lang server requires some of the same graphical components that DrRacket uses, and perhaps the Snap version is quite packaged correctly for all those to work...? In any case, it does seem to be an issue with Snap packaging as you deduced. I'll add a note about this to README pointing to this issue. Hopefully that will help others as well. |
Environment
OS
VSCode
Racket
Magic Racket
v0.6.5
Racket LSP
570b19570db40647c5ae69c73a67d3a05466a465
Error message
Output > Racket Language Client
Output > Extension Host
Output > Pty Host
Output > Racket Language Server
None. Doesn't get that far.
Additional context
Triggers when I edit a
.rkt
file. If I start in that file it happens immediately. If I start in another type of file it doesn't happen until I switch to a.rkt
file.I have a
Go
program that was able to connect to the Racket LSP. It takes 4 seconds when I hit theraco
-installed library and 8 seconds when I useracket
to bring the source for the LSP up from scratch. I am able to send the initialization request and get an appropriate response back so the LSP is properly configured.I tried various commands and command paths for the LSP, thinking that perhaps the extension couldn't find stuff. Nothing made any difference.
I forked and downloaded both Magic Racket and the Racket LSP so that I could try to debug through them. I didn't get very far. The VSCode Language Extension code is large and gnarly and I am not able to find a lot of detailed documentation on it, just examples online. I can step though the code in
extension.ts
but whatever is breaking is happening in the "background" and since it's all single threaded with futures it doesn't happen anywhere I can easily step through. Check out the stack trace above, there's none of the Magic Racket code in there.At one point when I was attempting to put breakpoints in VSCode Language Extension code I was able to get some message about exceeding a one second timeout. Not sure where that really was happening and I can't find any documentation on setting up the
LanguageClient
that mentions any timeouts. Reference my comment earlier on 4 second startup of the LSP but also note from theOutput > Racket Language Client
output that all attempts occurred in the same second.Note: Racket is installed via
snap
and "lives" at/snap/bin/racket
which is a symbolic link to/usr/bin/snap
which apparently knows how to run the actual program. The/snap/bin
directory is on myPATH
. I tracked down the actual binary file in/snap/racket/current/usr/bin/racket
and tried that for the path in the extension settings but it failed the same way. I even copied the binary out so that I could reference it directly instead of via the weird/snap/bin
pseudo-directory but still no dice.I can't remember all of the other stuff I've tried, so it's time to file this issue.
The text was updated successfully, but these errors were encountered: