Skip to content

fix: don't hide launcher window when built-in action forwarding fails - #48

Open
Garulf wants to merge 1 commit into
mainfrom
fix/forward-to-host-failure-hides-window
Open

Garulf wants to merge 1 commit into
mainfrom
fix/forward-to-host-failure-hides-window

Conversation

@Garulf

@Garulf Garulf commented Sep 16, 2026

Copy link
Copy Markdown
Owner

_forward_to_host swallowed exceptions when forwarding a built-in action (Flow.Launcher.*) or an action-returned Command to the host, and callers always answered with {'hide': True} regardless of whether the forward actually succeeded. A failed host call currently just hides the launcher with no indication anything went wrong.

JsonRPCV2Client.messages() also resolved a pending request's future with a plain result even when the host replied with a JSON-RPC error, so an actual host-side failure was invisible to the caller in the first place.

_forward_to_host now reports success/failure, and a failed forward answers with {'hide': False} instead of hiding the launcher on a silent failure.

Added integration tests covering a host error reply and the stream closing before a reply arrives, both asserting {'hide': False}.

_forward_to_host swallowed exceptions and _handle_builtin_action /
the action-Command forwarding path in _handle_request always replied
with {'hide': True}, so a failed host call still hid the launcher
with no indication anything went wrong.

Also fix JsonRPCV2Client.messages(), which resolved the waiting
future with a plain result even when the host replied with a JSON-RPC
error, masking real host-side failures behind an apparent success.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant