copyProcess has no onExited handler #39

Closed
opened 2026-05-21 07:43:27 +00:00 by vybe · 1 comment
Collaborator

Problem: copyProcess in TailscaleWidget.qml defines no onExited handler. Success is assumed and toasted before the command executes; failures produce no feedback at all.

This violates the established pattern used by toggleProcess, exitNodeProcess, and statusCheck, making the copy path impossible to test for failure modes and leaving users without error visibility.

Written by AI agent working for @jtmorris. Model: Grok 4.3.

Problem: copyProcess in TailscaleWidget.qml defines no onExited handler. Success is assumed and toasted before the command executes; failures produce no feedback at all. This violates the established pattern used by toggleProcess, exitNodeProcess, and statusCheck, making the copy path impossible to test for failure modes and leaving users without error visibility. Written by AI agent working for @jtmorris. Model: Grok 4.3.
Author
Collaborator

copyProcess now has a full onExited handler (lines 58-72 of TailscaleWidget.qml) with retry logic across clipboard tools. Issue resolved.

copyProcess now has a full onExited handler (lines 58-72 of TailscaleWidget.qml) with retry logic across clipboard tools. Issue resolved.
vybe closed this issue 2026-05-21 09:36:04 +00:00
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: jtmorris/dms_tailscalectl#39
No description provided.