sneak
5045bac92f
check / check (push) Waiting to run
Ctrl-C or SIGTERM during snapshot create, restore or verify exited 0 with no error line (1, also silent, under snapshot verify --json), so an unfinished --cron backup looked like a success. RunOperation now counts an op as interrupted when the Vaultik context was cancelled before it returned, rather than when its error wraps context.Canceled, which verify --json does not. Entry prints "interrupted before the command finished" on stderr for it and returns 130, under --cron and --json too. SIGTERM also gives 130, as the issue asks, not 143. The test does not reach the branch for an op still running when the 30s shutdown timeout ends. Model: opus-5-5