-
Notifications
You must be signed in to change notification settings - Fork 11
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
0.3 error when using Telescope "Cancellation failed because no search found" #115
Comments
Btw. what format are the traces in? I need their symbols decoded :) |
No need for apologies! I'm grateful for the bug report! This feature might have gotten broken during the refactoring. It's why I haven't switched the repository over to v0.3 yet, but it's very close to being completed. I'll need to debug this to see what is going on, but my guess is you can expect either an update to the distant binary (i.e.
This is concerning. This shows a bug in the distant client or server, which has been difficult to track down. I'll have to tried to reproduce your search scenario to see if I encounter it. Essentially, the server is sending data to the client that it does not recognize. In the past, this happened because the server and client were different versions, but if you're using 0.20 for both (no alphas), then I'm surprised to see this error message.
Can you clarify here? What traces are you referring to? |
Trace level logs in my server.log looks like this: [2023-07-31 15:43:40.676964 +02:00] TRACE [distant-net/src/server/connection.rs:572] [Conn 704532122] Sending ��id�12698853156878825901�origin_id�172922703_6629�payload��type�search_results�idΟU�^B�matches���type�contents�path�./var/fpwork/akaluza/project/README.md�lines�o**NOTE** for reference:
�line_number^Y�absolute_offset�^C��submatches���match�tes�starti�endl So I'm unsure on what do I need to do to read that data. |
I've double checked now that I've installed the InstallationLocalI've installed distant on locally by running
Remoteon remote:
Launch
|
Oh, I understand now. There isn't actually anything you need to do in order to read the data. The trace log you're seeing is an attempt to convert a response in msgpack binary format to text that can be read. The question mark symbols are just parts of the binary message that don't translate. What this actually is showing is
You don't really need to be able to read the whole thing. It's printed out at the trace level so we can confirm data is sent and received, not to necessarily see the exact information. |
Thanks. I've got a bit more clues. I've executed |
This error is occuring on 0.3, pretty much 100% of the time. Sometimes - rarely - the search results do load, albeit super slowly and without a preview window.
It's possible that my config is incorrect.
I understand that you already refactored the plugin since it's checkbox is ticked - sorry if I'm making an issue too early while it's still WIP.
WindowsTerminal_KYKHNLYuQN.mp4
Distant-server.log
.cache/distant/client.log
Config
Local machine:
Ubuntu 22.04.1 LTS on WSL
Remote machine:
Red Hat Enterprise Linux Server 7.5 (Maipo)
Distant version:
0.20 musl
.Distant.nvim version:
0.3
on latest commit17bcd37
.The text was updated successfully, but these errors were encountered: