Files
OmniRoute/scripts
diegosouzapw 893490e2df fix(ci): omni-queue never leaves a success land status on a batch it abandons
Withdrawing the land status was all-or-nothing and could be skipped: a
refused write stopped revokeLanding and skipped the pause, and a tick that
died after blessing left no record, so the next tick recomposed with the
status still in success.

revokeLanding now attempts every commit, never throws, and records a failed
withdrawal in an error event, a note and the rethrown error. The in-flight
stage "landing" is saved before the App blesses (the gate: only a batch at
that stage pays a status read), and at the end of every live tick a batch
stored or marked at that stage that was neither landed nor kept there has
each newest land status read and turned into failure where it is success. A
manual pause puts such a batch back to the testing stage, so its status is
withdrawn until it lands after the resume.
2026-11-15 07:40:19 -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