You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This seems to be related to #12. I just installed Racket 8.0 and racket-langserver on Windows 10 for use with VSCode and the Magic Racket extension. The instant I opened an empty .rkt file, racket-langserver threw the following error:
Caught exn in request "textDocument/documentHighlight"
hash-ref: no value found for key
key: 'file:///c:/Users/user/Documents/Programming/hello-racket/hello.rkt
context...:
C:\Users\user\AppData\Roaming\Racket\8.0\pkgs\racket-langserver\text-document.rkt:207:0: get-doc-refs
C:\Users\user\AppData\Roaming\Racket\8.0\pkgs\racket-langserver\text-document.rkt:191:0: document-highlight
C:\Program Files\Racket\collects\racket\contract\private\arrow-val-first.rkt:486:18
C:\Users\user\AppData\Roaming\Racket\8.0\pkgs\racket-langserver\methods.rkt:26:0: process-message
C:\Program Files\Racket\collects\racket\contract\private\arrow-val-first.rkt:486:18
C:\Users\user\AppData\Roaming\Racket\8.0\pkgs\racket-langserver\main.rkt:54:2: consume
[Error - 7:45:07 PM] Request textDocument/documentHighlight failed.
Message: internal error in method "textDocument/documentHighlight"
Code: -32603
My best guess is that the key format 'file:///c:/...' is causing the problem, specifically the third slash following 'file.'
The text was updated successfully, but these errors were encountered:
That VSCode sent the textDocument/documentHighlight request before the textDocument/didOpen request
That it did send the didOpen, but there is some small difference in the case/etc of the file path that causes the two database entries in the langserver to not match.
This seems to be related to #12. I just installed Racket 8.0 and racket-langserver on Windows 10 for use with VSCode and the Magic Racket extension. The instant I opened an empty
.rkt
file, racket-langserver threw the following error:My best guess is that the key format
'file:///c:/...'
is causing the problem, specifically the third slash following 'file.'The text was updated successfully, but these errors were encountered: