-
Notifications
You must be signed in to change notification settings - Fork 768
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
Escaping issue in Rust completer #520
Comments
I can reproduce the backtrace by directly using curl. Start $ export RUST_BACKTRACE=1
$ ./racerd serve -l -p56773
racerd listening at 127.0.0.1:56773 Create the file {
"buffers": [ {
"file_path": "test.rs",
"contents": "pub fn main() {\nlet x = b'\\t';\nx.\n}\n"
} ],
"file_path": "test.rs",
"line": 3,
"column": 2
} and send the request with curl: $ curl -H "Content-Type: application/json" -d @request.json 127.0.0.1:56773/list_completions This results in a similar backtrace as the one you posted. Ping @jwilm |
Seems related to this racer issue. |
Ah, you're right. It seems like I didn't escape it correctly either when testing it with curl. |
with RLS there doesn't seem to be any stack traces in rls log. However there are no completions for x. for the given snippet either. (There are completions if you change it to let x = 't'; however) |
Seems an RLS issue not a ycm one. |
When using YCM with this piece of Rust code:
and the cursor at then end of
x.
, racerd returns an internal server error (500) with the following message:However, I'm not sure whether this is a ycm or ycmd issue. I don't think racerd is at fault here, since it behaves correctly (with a 204 No Content) when I send the same message directly to racerd with curl.
It probably doesn't matter, but I'm using Arch Linux (GNU/Linux 4.6.1).
The text was updated successfully, but these errors were encountered: