pylsp `TimeoutError`
rfdzan opened this issue · 3 comments
rfdzan commented
I used pylsp
with helix editor. This error pops up from the log:
2024-03-20T17:27:49.812 helix_lsp::transport [ERROR] pylsp err <- "2024-03-20 17:27:49,810 WIB - WARNING - pylsp.workspace - There was an error while trying to initialize progress reporting.Likely progress reporting was used in a synchronous LSP handler, which is not supported by progress reporting yet. To prevent waiting for the timeout you can set `skip_token_initialization=True`. Not every editor will show progress then, but many will.\n"
2024-03-20T17:27:49.812 helix_lsp::transport [ERROR] pylsp err <- "Traceback (most recent call last):\n"
2024-03-20T17:27:49.812 helix_lsp::transport [ERROR] pylsp err <- " File \"/home/user/Documents/python_proj/pyweek37/lib/python3.12/site-packages/pylsp/workspace.py\", line 252, in _progress_begin\n"
2024-03-20T17:27:49.812 helix_lsp::transport [ERROR] pylsp err <- " ).result(timeout=1.0)\n"
2024-03-20T17:27:49.812 helix_lsp::transport [ERROR] pylsp err <- " ^^^^^^^^^^^^^^^^^^^\n"
2024-03-20T17:27:49.812 helix_lsp::transport [ERROR] pylsp err <- " File \"/home/user/.pyenv/versions/3.12.2/lib/python3.12/concurrent/futures/_base.py\", line 458, in result\n"
2024-03-20T17:27:49.812 helix_lsp::transport [ERROR] pylsp err <- " raise TimeoutError()\n"
2024-03-20T17:27:49.812 helix_lsp::transport [ERROR] pylsp err <- "TimeoutError\n"
it talks about setting skip_token_initialization
to true, however I am not sure where to set it. it's not on the configuration either.
ccordoba12 commented
It seems you have a third-party pylsp plugin that is trying to report progress from a synchronous handler.
rfdzan commented
is the problem instead about the handler and not pylsp
?
ZedThree commented
I'm seeing this a lot, and I think is causing completions to be very slow (several seconds). I tried disabled all plugins but still saw this error message. Is there a way of working out where this is coming from?