Curator rollback errors leave staged metadata inconsistent
Cluster 122210. Data as of
Nothing open on GitHub. Fix merged in #124221 on 26 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #124221. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #124221. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and fixes address a bug where a rollback encountering errors in the curator causes staged metadata or originals to be incorrectly discarded or excluded from subsequent operations. The work focuses on preserving staging state properly when rollback recovery encounters errors.
Open issues0
Open PRs0
Fixes on record
-
#124221 fix(curator): keep a failed rollback's staged metadata out of the next prune
files:
agent/curator_backup.py,tests/agent/test_curator_backup.py,tests/agent/test_curator_rollback_staging.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#122217 fix(curator): retain staging after failed rollback recovery · done elsewhere →
e2c510c,#124221
Closed issues · 1
- Closed#122210Curator rollback deletes unrestored staged originals after filesystem move failures
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #124221
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 26 Sep 2026