interactive mode has no escape hatch, hangs pty-based automation #607
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
thwap/thwap-pagesd#607
Loading…
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?
interactive.Enabledgates on stdin AND stdout both being terminals (internal/tpagectl/interactive/interactive.go). Pty-based automation (script,expect, CI executors that allocate a pty, tmux,ssh -t) satisfies both, so a command invoked without a required value now blocks on an interactive prompt where it previously failed fast.Before:
tpagectl site getwith no site arg under a pty → instantsite name is required(exit 5). After: the fuzzy picker renders and waits for input — scripts hang or consume garbage.Add an explicit override: e.g.
TPAGECTL_INTERACTIVE=0/--no-interactive, or disable interactive whenCI/TERM=dumbis set.See #606
why would you be using interactive mode for pty based automation?
Resolved by discussion. Properly written scripts pass required values via CLI args and never enter interactive mode; the gate only activates for genuine interactive terminal use. The pty + missing-arg combination only affects already-broken scripts, which previously failed fast (exit 5) and now would block — a failure-mode change for a broken-script edge, not a real automation path. Not worth an escape hatch. Closing as not-actionable.