No stderr capture on toggleProcess / exitNodeProcess (lost diagnostic output)

vybe commented

2026-05-19 04:22:54 +00:00

Collaborator

Problem

toggleProcess and exitNodeProcess only capture stdout. Stderr is not collected or inspected. Any diagnostic output from tailscale (e.g., "must be root", authentication prompts, permission errors) is silently discarded. The only user-visible feedback on failure is the generic error toast.

Impact

Users have no way to see the real reason a tailscale up/down/set command failed. Debugging is limited to the exit code alone.

## Problem `toggleProcess` and `exitNodeProcess` only capture stdout. Stderr is not collected or inspected. Any diagnostic output from `tailscale` (e.g., "must be root", authentication prompts, permission errors) is silently discarded. The only user-visible feedback on failure is the generic error toast. ## Impact Users have no way to see the real reason a `tailscale up/down/set` command failed. Debugging is limited to the exit code alone.

jtmorris commented

2026-05-19 04:24:38 +00:00

Owner

This issue should probably be looked at more generically as well. In the event of unexpected output or command failure, how does the user know what happened? Some guidance is needed. Either the toasts need to catch everything and detail what the error state is, or there needs to be some kind of log.

If I later have to troubleshoot problems between versions, or when command output changes, I want to know what I'm looking at.

This issue should probably be looked at more generically as well. In the event of unexpected output or command failure, how does the user know what happened? Some guidance is needed. Either the toasts need to catch everything and detail what the error state is, or there needs to be some kind of log. If I later have to troubleshoot problems between versions, or when command output changes, I want to know what I'm looking at.