You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.)
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