-
Notifications
You must be signed in to change notification settings - Fork 13
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
completion stops working after error #20
Comments
i started over and created a clean reproduction of the error: i am typing func for function check the popup and after the selection from the menu starts a snippet out of the full stacktrace in the snippet i type in the function name "hello", followed by the parentheses. as first argument i intent to write out "name", but at the second char ("na") the error pops off. in the end it looks like this:
i included a follow up request for code completion, including context, in the stacktrace and the empty response thereafter. it seems after the return message "request cancelled" with the code "-32800" the process sourcekit-lsp only provides empty responses. this is accredited with the following error message out of stderr
the full stacktrace is to be found here: |
my assumption grows the responsibility relies on the client side for this behavior. |
opened an issue on lsp-mode |
i have made the experience that after opening a
.swift
fileand setting the project's root dir i get successful completion
but after one interrupts the completion by keep typing an error occurs,
and no more completion after that.
I suspect it is becausesourcekit-lsp
crashedswift version: 5.4.2
lsp error message:
company error message:
second lsp error message:
backtrace:
stacktrace:
after installing a missing dependency
libpython2.7
the error still persists.namely that the lsp server becomes unresponsive.and completion stops working
additionally i tried:
swift package init
it seems the trace shows nothing but the empty response from the sourcekit-lsp server.
the error messages differ only from the
DocumentURI
(which is the same forexpected and for received) and the char number
@1151
(which differs between expected and received).The text was updated successfully, but these errors were encountered: