When Cleanup Resets the Retry Budget
When Cleanup Resets the Retry Budget A retry limiter can record an attempt correctly and still lose control before the next call. An Orca recovery-module experiment exposed the reason: display cleanup erased a terminal's recovery history while that terminal remained eligible for another remount. The useful review target is the cleanup predicate. Adapted from the complete English research article…
A terminal's recovery history can be erased during cleanup even if the system still allows it to be remounted. This issue was discovered through an experiment involving a recovery-module program. The critical factor is the cleanup predicate, which needs to be examined. Orca, a terminal organizer, and Agent work use different indexes for terminal rows and UI tabs.
Sometimes, these indexes do not match, causing problems. When this happens, the old budget-release path consults the wrong index, leading to inconsistencies. Testing this issue without emulating a desktop environment, the researchers set up the necessary modules and fixtures while keeping the original code intact. They then manipulated the UI index to simulate a missing tab while the terminal row remained.
The research found that the old limiter worked when the terminal row was still visible but failed when the UI and terminal indexes diverged. The new fix addresses this by ensuring that the terminal row's presence and the history of its recovery are determined by the same lookup. This change does not lower the cap or introduce a new limiter; it simply aligns the questions about remounting and cleanup history.
The study recommends verifying that recovery works correctly and that the cleanup path preserves necessary information. The key takeaway is that a protection mechanism must correctly record actions and preserve that record until the next relevant decision.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
