Found while documenting arcli 26.09.1 against the binary (docs.basekick.net arcli section).
-
arcli db drop NAME and arcli config delete NAME prompt [y/N], but a declined answer, or a non-terminal stdin (</dev/null, a pipe), prints Aborted. and exits 0 without doing anything (internal/commands/db.go confirmDestructive, internal/commands/config.go delete). Every other destructive command goes through confirmOrAbort and exits 1 with Error: aborted, refusing a non-TTY stdin unless --yes. Scripts cannot tell "dropped" from "aborted" by exit code. Proposed fix: route both through confirmOrAbort; the docs currently describe the actual behaviour and call it out as the exception.
-
internal/commands/write.go (openWriteBody comment) says the server accepts an empty line-protocol body as a no-op; Arc returns 400 Empty request body, which arcli surfaces as an error with exit 1. Comment only; behaviour is fine.
Found while documenting arcli 26.09.1 against the binary (docs.basekick.net arcli section).
arcli db drop NAMEandarcli config delete NAMEprompt[y/N], but a declined answer, or a non-terminal stdin (</dev/null, a pipe), printsAborted.and exits 0 without doing anything (internal/commands/db.goconfirmDestructive,internal/commands/config.godelete). Every other destructive command goes throughconfirmOrAbortand exits 1 withError: aborted, refusing a non-TTY stdin unless--yes. Scripts cannot tell "dropped" from "aborted" by exit code. Proposed fix: route both throughconfirmOrAbort; the docs currently describe the actual behaviour and call it out as the exception.internal/commands/write.go(openWriteBodycomment) says the server accepts an empty line-protocol body as a no-op; Arc returns400 Empty request body, which arcli surfaces as an error with exit 1. Comment only; behaviour is fine.