Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
{{ message }}
URL: http://github.com/python-lsp/python-lsp-server/discussions/491
://github.githubassets.com/assets/github-b184eb87701960eb.css" />
Uh oh!
There was an error while loading. Please reload this page.
-
I've been using pylsp for a while along with Emacs/
emacs-lspfor working on a Django project, and periodically, although it seems like increasingly more commonly, getting random hangs of the entire stack withpylspsitting at 100% on at least one core for 60s+, and sometimes never seems to return.I'm looking for suggestions on how to instrument or otherwise debug what's going on, since on its own that's not a particularly useful bug report.
There's nothing particularly useful in the
*pylsp::stderr*output at the default WARN level, and any lower gets pretty spammy since this problem doesn't occur all that regularly.I can sometimes attach
py-spyto the pylsp process, and get something along the lines of:but not sure if that's actually indicative of a specific problem/cause in jedi, and even if it is, what might be causing it.
I've not encountered much trouble with other projects, so I assume it's something data-specific to this codebase, but it's an internal work app I can't share.
It might be just recency bias, but it seems like it happens more often when editing in pytest
test_blah.pytype files, so plausibly something is getting a little carried away in the jedi code that handles magic pytest fixtures or something?Any ideas on where to go next?
Beta Was this translation helpful? Give feedback.
All reactions