anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 10:15:31 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[PR #13028] fix(desktop): server spawn resilience #14483

New Issue
Closed
opened 2026-02-16 18:19:16 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:19:16 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/anomalyco/opencode/pull/13028

State: closed
Merged: Yes

GPT 5.2 xhigh:

That message is coming from the desktop app’s startup path: it spawns the bundled sidecar (opencode-cli … serve …) and then waits up to 30s for GET /global/health to succeed. If that never goes healthy, packages/desktop/src-tauri/src/lib.rs throws Failed to spawn OpenCode Server….

Why reports often show empty “Logs:” today

  • The desktop only buffers sidecar stdout/stderr, but the CLI writes most diagnostics to its own log file unless run with --print-logs.
  • We also weren’t recording early process termination, so a sidecar that exits immediately (or never prints) looks like a generic 30s timeout.

I patched the desktop backend to make these reports actionable:

  • Start the sidecar with --print-logs --log-level WARN so real errors land in the buffered logs.
  • Record CommandEvent::Error and CommandEvent::Terminated (exit code/signal) into the buffered logs.
  • Fail fast if the sidecar terminates before becoming healthy (instead of always waiting for the 30s timeout).
  • Add a [SPAWN] … line so even “silent” failures show what we tried to run.

Changes are in:

  • packages/desktop/src-tauri/src/cli.rs
  • packages/desktop/src-tauri/src/server.rs
  • packages/desktop/src-tauri/src/lib.rs

If you ship a build with this, the next batch of reports should include exit code/signal + stderr, which usually immediately points to the root cause (missing libs/GLIBC, illegal instruction on older CPUs, shell/env issues, etc.).

**Original Pull Request:** https://github.com/anomalyco/opencode/pull/13028 **State:** closed **Merged:** Yes --- GPT 5.2 xhigh: That message is coming from the desktop app’s startup path: it spawns the bundled sidecar (`opencode-cli … serve …`) and then waits up to 30s for `GET /global/health` to succeed. If that never goes healthy, `packages/desktop/src-tauri/src/lib.rs` throws `Failed to spawn OpenCode Server…`. Why reports often show empty “Logs:” today - The desktop only buffers sidecar stdout/stderr, but the CLI writes most diagnostics to its own log file unless run with `--print-logs`. - We also weren’t recording early process termination, so a sidecar that exits immediately (or never prints) looks like a generic 30s timeout. I patched the desktop backend to make these reports actionable: - Start the sidecar with `--print-logs --log-level WARN` so real errors land in the buffered logs. - Record `CommandEvent::Error` and `CommandEvent::Terminated` (exit code/signal) into the buffered logs. - Fail fast if the sidecar terminates before becoming healthy (instead of always waiting for the 30s timeout). - Add a `[SPAWN] …` line so even “silent” failures show what we tried to run. Changes are in: - `packages/desktop/src-tauri/src/cli.rs` - `packages/desktop/src-tauri/src/server.rs` - `packages/desktop/src-tauri/src/lib.rs` If you ship a build with this, the next batch of reports should include exit code/signal + stderr, which usually immediately points to the root cause (missing libs/GLIBC, illegal instruction on older CPUs, shell/env issues, etc.).
yindo added the pull-request label 2026-02-16 18:19:16 -05:00
yindo closed this issue 2026-02-16 18:19:16 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#14483
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?