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
{{ message }}
Repository navigation
LspError.data missing #[serde(default)] swallows the real jdtls error #325
pubstructLspError{code:i64,message:String,data:Value,// no #[serde(default)]}
LSP allows error.data to be omitted. When jdtls returns an error without data, the Error variant fails to deserialize, and since LspResponse is an untagged enum, the whole parse fails with:
Failed to parse response from LSP proxy: data did not match any variant of untagged enum LspResponse
Impact
The actual error message is swallowed. In our case the real response was:
{"error":{"code":-32601,"message":"No delegateCommandHandler for vscode.java.resolveMainClass"},"id":"...","jsonrpc":"2.0"}
but Zed surfaced the misleading serde error, which pointed everyone (including maintainers reading our report) at "protocol/proxy problems" instead of the broken debug plugin (see #324). This cost a long debugging session.
Or directly: curl -X POST http://127.0.0.1:<proxy-port>/ -d '{"method":"workspace/executeCommand","params":{"command":"vscode.java.resolveMainClass","arguments":[]}}' — the response error has no data field
Fix
Add #[serde(default)] to data (one-liner) so the real message (No delegateCommandHandler ...) reaches the user.
Activity
tartarughina commentedon Nov 4, 2026
Thanks @sisyphusend for the deep dive. Did you by chance already applied the suggested fix and tested it?
Assign default value to debugger LSP struct (#327)