Skip to content

[BUG]: TUI worker RPC errors can leave requests unresolved #28043

@PeterPonyu

Description

@PeterPonyu

Description

While checking #28015, I found a smaller worker communication bug: if a TUI worker RPC method throws, the worker-side message handler rejects and the parent RPC client never receives a result or error. That can leave the request pending and make later TUI/worker communication look broken instead of surfacing the original error.

Plugins

None required.

OpenCode version

Current dev branch.

Steps to reproduce

  1. Register a worker RPC method that throws.
  2. Call it through Rpc.client(...).call(...).
  3. The listener rejects and the client never receives a controlled error response.

Screenshot and/or share link

No response

Operating System

Linux

Terminal

No response

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions