Backport of #351 to 2026.x. One commit, cherry-picked clean from main's 95117823.
While a blob store change isn't settled, a new snapshot is refused (BM-8). The snapshots already on disk went with it: inbuxa:StoreSnapshot/get listed none, destroy answered notFound, and the start-up cleanup left partial directories alone. The directory now comes from the RocksDB data store alone (Store::snapshot_data_path). Spec SN-7 says so.
The bug is in 2026.11.9.1 and later.
Test: system::store_snapshot puts the blob store through an unsettled change and checks the refusal, the snapshot still listed, and its destroy. On this branch it passes with blobs in the data store and with BLOB_STORE=FileSystem, and fails without the services change. Also fork checks, build, and the store and services snapshot unit tests.
Backport of #351 to 2026.x. One commit, cherry-picked clean from main's 95117823.
While a blob store change isn't settled, a new snapshot is refused (BM-8). The snapshots already on disk went with it: `inbuxa:StoreSnapshot/get` listed none, destroy answered `notFound`, and the start-up cleanup left partial directories alone. The directory now comes from the RocksDB data store alone (`Store::snapshot_data_path`). Spec SN-7 says so.
The bug is in 2026.11.9.1 and later.
Test: `system::store_snapshot` puts the blob store through an unsettled change and checks the refusal, the snapshot still listed, and its destroy. On this branch it passes with blobs in the data store and with `BLOB_STORE=FileSystem`, and fails without the services change. Also fork checks, build, and the store and services snapshot unit tests.
While a blob store change isn't settled, a new snapshot is refused
(BM-8). The snapshots already on disk went with it: get listed none,
destroy said notFound, and the start-up cleanup skipped partial
directories, because all three found the snapshots' directory through
the same check that refuses a new one. Found with inbuxa Admin's new
Snapshots page.
The directory now comes from the RocksDB data store alone. The system
test takes the blob store through an unsettled change and checks the
refusal, the snapshot still listed, and its destroy.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Backport of #351 to 2026.x. One commit, cherry-picked clean from main's
95117823.While a blob store change isn't settled, a new snapshot is refused (BM-8). The snapshots already on disk went with it:
inbuxa:StoreSnapshot/getlisted none, destroy answerednotFound, and the start-up cleanup left partial directories alone. The directory now comes from the RocksDB data store alone (Store::snapshot_data_path). Spec SN-7 says so.The bug is in 2026.11.9.1 and later.
Test:
system::store_snapshotputs the blob store through an unsettled change and checks the refusal, the snapshot still listed, and its destroy. On this branch it passes with blobs in the data store and withBLOB_STORE=FileSystem, and fails without the services change. Also fork checks, build, and the store and services snapshot unit tests.