archied: unknown positional arguments start the daemon #1284

Closed
opened 2026-10-27 13:39:46 +00:00 by sam · 0 comments
Owner

archied ignores unknown positional arguments, so a stale command such as 'archied update-topology' starts a second daemon instead of failing. Done when an unknown subcommand exits non-zero with usage.

Close reason

archied now refuses a leading word that is not a subcommand: cmd/archied/main.go dispatches setup/update/status/prbench/playbooks in a switch and otherwise exits 2 with 'archied: unknown command' plus usage, so a stale 'archied update-topology' can no longer start a second daemon under the running one. Verified: update-topology exits 2 with usage, --version and status still behave.


Imported from beads archie-core-dcngl · GitHub #1638 · type bug · priority P2 · created 2026-10-11 · closed 2026-10-26

archied ignores unknown positional arguments, so a stale command such as 'archied update-topology' starts a second daemon instead of failing. Done when an unknown subcommand exits non-zero with usage. ### Close reason archied now refuses a leading word that is not a subcommand: cmd/archied/main.go dispatches setup/update/status/prbench/playbooks in a switch and otherwise exits 2 with 'archied: unknown command' plus usage, so a stale 'archied update-topology' can no longer start a second daemon under the running one. Verified: update-topology exits 2 with usage, --version and status still behave. --- _Imported from beads `archie-core-dcngl` · GitHub #1638 · type bug · priority P2 · created 2026-10-11 · closed 2026-10-26_
sam added the mediumbug labels 2026-10-27 13:39:46 +00:00
sam self-assigned this 2026-10-27 13:39:46 +00:00
sam closed this issue 2026-10-27 13:39:46 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1284