Description
Starting the SQLMesh Language Server (via tcloud / enterprise LSP) fails during import: sqlmesh.lsp.main imports WorkspaceDiagnosticRefreshRequest from lsprotocol.types, but that symbol is not available in lsprotocol 2025.x, so the process exits and the VS Code extension reports a failed LSP connection.
Environment
- OS: Windows
- Editor: VS Code / Cursor + SQLMesh extension
- Python: 3.11 (project
.venv as workspace interpreter)
Steps to reproduce
- Install current
tcloud in a clean venv (e.g. pip install tcloud).
- Open a SQLMesh project and use that venv as the Python interpreter.
- Trigger the SQLMesh extension / LSP (e.g. reload window).
Expected
Language server starts without import errors.
Actual
Server process exits with:
ImportError: cannot import name 'WorkspaceDiagnosticRefreshRequest' from 'lsprotocol.types'
(Extension may also show generic LSP errors such as “couldn’t create connection to server” or exit code 1.)
Versions
| Package |
Version |
tcloud |
2.11.0 |
sqlmesh |
0.232.0 |
lsprotocol |
2025.0.0 |
pygls |
2.1.1 |
Workaround
pip uninstall -y lsprotocol pygls
pip install "lsprotocol<2025" "pygls<2.0"
python -c "from lsprotocol.types import WorkspaceDiagnosticRefreshRequest; print('ok')"
Description
Starting the SQLMesh Language Server (via
tcloud/ enterprise LSP) fails during import:sqlmesh.lsp.mainimportsWorkspaceDiagnosticRefreshRequestfromlsprotocol.types, but that symbol is not available inlsprotocol2025.x, so the process exits and the VS Code extension reports a failed LSP connection.Environment
.venvas workspace interpreter)Steps to reproduce
tcloudin a clean venv (e.g.pip install tcloud).Expected
Language server starts without import errors.
Actual
Server process exits with:
ImportError: cannot import name 'WorkspaceDiagnosticRefreshRequest' from 'lsprotocol.types'(Extension may also show generic LSP errors such as “couldn’t create connection to server” or exit code 1.)
Versions
tcloudsqlmeshlsprotocolpyglsWorkaround