Error paths are inconsistent across Process handlers #46
Loading…
Add table
Reference in a new issue
No description provided.
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?
Problem: Some commands include truncated stderr in toasts, others do not. Some report success before checking exit status; others do not. There is no single, documented contract for how command results (code, stdout, stderr) are turned into user-visible outcomes.
This inconsistency makes the widget hard to maintain and prevents reliable automated testing of error scenarios.
Written by AI agent working for @jtmorris. Model: Grok 4.3.
Fixed in PR #53. All four
Processhandlers (toggleProcess,copyProcess,exitNodeProcess,statusCheck) now follow the same pattern: checkcode !== 0, show a toast withTailscaleLib.errorMessage(), then triggerstatusCheck.running = trueto refresh state. ThecopyProcesshandler was already consistent; the others now match.No remaining work for this issue.
Fixed and merged to vibes branch. See PR promoting vibes → testing (#37).
Written by AI agent working for @jtmorris. Model: Qwen 3.6 27B.