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;
the start-up cleanup left partial directories alone.
All three found the snapshots' directory through snapshot_source, the same check that refuses a new snapshot. The directory now comes from the RocksDB data store alone (Store::snapshot_data_path), whatever the blob store is doing. Spec SN-7 says so.
Found with the console's new Snapshots page (inbuxa-admin #182) against a local 27.1-rc.17: a snapshot taken, then the blob store moved, and the page said there were none, while the directory was still on disk.
Test: system::store_snapshot now puts the blob store through an unsettled change and checks the refusal, the snapshot still listed, and its destroy. It passes with blobs in the data store and with BLOB_STORE=FileSystem, and fails without the services change ("still listed while refused: []"). Also fmt, fork checks, build, and the store and services snapshot unit tests.
The bug is in every release with snapshots: 27.1-rc.16 and later, and 2026.11.9.1 and later. A 2026.x backport can follow if you want it.
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`;
- the start-up cleanup left partial directories alone.
All three found the snapshots' directory through `snapshot_source`, the same check that refuses a new snapshot. The directory now comes from the RocksDB data store alone (`Store::snapshot_data_path`), whatever the blob store is doing. Spec SN-7 says so.
Found with the console's new Snapshots page (inbuxa-admin #182) against a local 27.1-rc.17: a snapshot taken, then the blob store moved, and the page said there were none, while the directory was still on disk.
Test: `system::store_snapshot` now puts the blob store through an unsettled change and checks the refusal, the snapshot still listed, and its destroy. It passes with blobs in the data store and with `BLOB_STORE=FileSystem`, and fails without the services change ("still listed while refused: []"). Also fmt, fork checks, build, and the store and services snapshot unit tests.
The bug is in every release with snapshots: 27.1-rc.16 and later, and 2026.11.9.1 and later. A 2026.x backport can follow if you want it.
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.
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;notFound;All three found the snapshots' directory through
snapshot_source, the same check that refuses a new snapshot. The directory now comes from the RocksDB data store alone (Store::snapshot_data_path), whatever the blob store is doing. Spec SN-7 says so.Found with the console's new Snapshots page (inbuxa-admin #182) against a local 27.1-rc.17: a snapshot taken, then the blob store moved, and the page said there were none, while the directory was still on disk.
Test:
system::store_snapshotnow puts the blob store through an unsettled change and checks the refusal, the snapshot still listed, and its destroy. It passes with blobs in the data store and withBLOB_STORE=FileSystem, and fails without the services change ("still listed while refused: []"). Also fmt, fork checks, build, and the store and services snapshot unit tests.The bug is in every release with snapshots: 27.1-rc.16 and later, and 2026.11.9.1 and later. A 2026.x backport can follow if you want it.