-
Notifications
You must be signed in to change notification settings - Fork 35
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
Client marksman quit with exit code 1 and signal 0
: Invalid URI: The hostname could not be parsed
#375
Comments
Thanks for reporting this @serpro69! The stack trace in the logs helps. Could you also share the full file path of the |
Hey! |
@serpro69 sorry, I got confused. Could you show the part of the logs that corresponds to the LSP initialization request? The relevant entry has |
Will do as soon as I get to my other laptop 👍
|
@serpro69 you'd need to enable lsp debug to get requests/responses in the logs:
|
I reproduced the error with debug log level when hovering over a method definition in rust_analyzer in neovim:
installed version: 2024-12-18 |
Thanks @iovis 👍 I got swamped at work and couldn't provide the details yet. |
Thanks for the extra input @iovis! I still can't quite make sense of the logs: there are no requests from nvim to marksman shown in the logs and there should be at least the Also, you said "when hovering over a method definition in rust_analyzer". That's... unexpected. Why would neovim start marksman when browsing a rust file. |
Yup, it was set before any server started.
I think documentation in neovim is rendered as markdown, at least in some LSPs. |
I mean, sure. It just doesn't make much sense why would nvim start a markdown LSP server in that case. After all that markdown content is just snippets from doc comments in rust source files rather than standalone markdown files which is what markdown LSP server is supposed to work with. Anyhow, I see the stack trace. I'll add some extra logging/error handling there which will perhaps help. Thanks for the input folks! |
That's exactly the problem I'm experiencing. If you see the first post, I have a lua file opened (some lua lang clients are loaded), and marksman tries to start there and crashes. |
Not sure if it is related so please ignore this if it is not. Could this be related to some markdown being used (and thus loading marksman) for example when viewing diagnostics or signature helps? I recently had this issue when I was hovering and showing docs/signature which gave me similar or same warning. At that moment I was using some plugins to view the floating docs/signature like nvim lspsaga. I recently did some refactoring in my neovim config and now use the native vim.lsp.buf functionalities to do the docs/signature viewing. I don't get the warnings now. |
I've been getting this
Client marksman quit with exit code 1 and signal 0
for awhile now, and it seems to be popping up randomly (or at least I can't figure out the root cause yet), but the logs show this:It could be related to #348 , but I'm not sure. If it is - please feel free to close this issue to avoid duplicates :)
Also let me know if I can do some steps to try to debug this further.
I have marksman installed via mason and configured (with defaults) via nvim-lspconfig
The strangest thing is, it crashes when it's not even loaded:
The text was updated successfully, but these errors were encountered: