Skip to content

[fix] Backport: lift a restore hold on blocks no holder has - #635

Merged
ok merged 1 commit into
release/1.12from
backport/restore-hold-sparse-holders
Oct 12, 2026
Merged

ok merged 1 commit into
release/1.12from
backport/restore-hold-sparse-holders

Conversation

@ok

@ok ok commented Oct 12, 2026

Copy link
Copy Markdown
Owner

Cherry-pick of #634 (9ace9c6) onto release/1.12. A restored space no longer stays held for good when members hold sparse copies of its catalog. Rebase-merge.

A restored catalog or profile stayed read-only until its copy had no
gaps, but members hold sparse copies, so a block nobody fetched never
arrived and the space stayed held for good. Missing blocks now keep it
held only while a connected holder can supply one; the length match
still guards against a fork. The flow test now waits for the catalog.

(cherry picked from commit 9ace9c6)
@ok
ok merged commit 970d0eb into release/1.12 Oct 12, 2026
14 checks passed
@ok
ok deleted the backport/restore-hold-sparse-holders branch October 13, 2026 07:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant