zed-industries/zed · error
Failed to parse RunInTerminalRequestArguments
Error message
Failed to parse RunInTerminalRequestArguments
What it means
The debug adapter sent a runInTerminal request whose arguments could not be deserialized into RunInTerminalRequestArguments (schema mismatch or malformed payload). The session responds with a failure to the client and surfaces this error.
Source
Thrown at crates/project/src/debugger/session.rs:1209
url: None,
url_label: None,
}),
})
.ok();
session
.update(cx, |this, cx| {
this.respond_to_client(
request.seq,
false,
StartDebugging::COMMAND.to_string(),
error,
cx,
)
})?
.await?;
Err(anyhow!("Failed to parse RunInTerminalRequestArguments"))
});
}
};
let seq = request.seq;
let (tx, mut rx) = mpsc::channel::<Result<u32>>(1);
cx.emit(SessionEvent::RunInTerminal {
request: request_args,
sender: tx,
});
cx.notify();
cx.spawn(async move |session, cx| {
let result = util::maybe!(async move {
rx.next().await.ok_or_else(|| {
anyhow!("failed to receive response from spawn terminal".to_string())
})?View on GitHub (pinned to 9d272b0363)
Solutions
- Check the adapter version — its runInTerminal arguments may not match the DAP structs expected here
- Update or pin a compatible debug adapter version
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at crates/project/src/debugger/session.rs:1209 when the library encounters an invalid state.
Common situations: See trigger scenarios.
Understand the failure class
- Parsing and encoding errors: unexpected token, malformed input — why parsers reject input and how to find the real culprit.
AI-assisted analysis of zed-industries/zed@9d272b0363 (2026-08-20).
Data as JSON: /api/errors/6eacedbf785700ff.
Report an issue: GitHub.