Skip to content

KeyError in workspace.py line 110, in get_document #317

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

Closed
mcepl opened this issue Feb 21, 2018 · 3 comments
Closed

KeyError in workspace.py line 110, in get_document #317

mcepl opened this issue Feb 21, 2018 · 3 comments

Comments

@mcepl
Copy link

mcepl commented Feb 21, 2018

(originally filed as palantir/python-language-server#263 )

If you are reporting a bug, please read following FAQ first. If you are
requesting new features or other types of questions, you can ignore it.

Have you followed the instructions at
INSTALL.md?
Yes (originally, this bug came with binary downloaded via install.sh, now (after #315 being fixed for me) it is my own build.

If you are still seeing an error or other types of issue, please create ticket with

I know this is probably not enough information, so feel free to close this.

@autozimu
Copy link
Owner

Couldn't reproduce locally.

Feel free to reopen after getting concrete reproduction steps.

@wmonk
Copy link

wmonk commented Mar 1, 2018

@autozimu I think the issue here is that the textDocument/didOpen method is not triggered until the file is edited in some way. I am experiencing the same behaviour as @mcepl, but when I trigger insert mode I can see messages in the server log like:

2018-03-01 09:20:35,940 UTC - DEBUG - pyls.server - Got message: b'{"jsonrpc":"2.0","method":"textDocument/didOpen"
...

I think the issue originally reported in palantir/python-language-server#263 is showing an error where the file isn't stored in the cache, and this is only triggered once the file is "edited" in some way.

@autozimu
Copy link
Owner

autozimu commented Mar 1, 2018

Were you able to provide concrete reproduction steps?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants