Files
OmniRoute/scripts
diegosouzapw 410c8db3ae fix(ci): an omni-queue resume clears only the pause it saw
Follow-up to the review of the pause/resume confirmation. `resume` reported success as soon
as the base was unpaused, also when it already was, while its dispatch could still be
pending in the tick's concurrency group and later clear a pause recorded in between (a
safety pause). Now the CLI sends nothing for a base that is not paused, and a resume carries
the pause it saw (`expect-pause:<since>`); the tick clears only that pause. A second
dispatch of the same request is therefore harmless, which also covers a retry made after
another request's run was mistaken for ours. The existing test that pinned an empty resume
reason now pins the new format.
2026-11-14 15:50:15 -03:00
..
2026-06-19 06:49:01 -03:00
2026-06-23 17:06:18 -03:00
2026-10-19 12:22:25 -03:00
2026-10-19 12:22:25 -03:00
2026-11-12 12:29:18 -03:00
2026-11-12 12:29:18 -03:00
2026-07-29 15:18:55 -03:00
2026-09-29 19:58:13 -03:00
2026-07-13 09:12:40 -03:00