Backported from 27.1 (#491), the two import fixes only; the S3 export and
store-check command stay on 27.1.
Fixed
An import into a fresh store refused to run: every start writes the
fork's subspace (where the blob store is, permission grants, the log
files' setting), the import's own start too, and the import took that
for data. Since the blob store change (#333): 2026.11.9.1. The fork's
subspace is no longer counted; its records are keyed values an import
sets over. The store test now imports over a start-up record, and fails
without this.
An import wrote the blobs into the data store, the empty store's blob
store, even when the imported settings name another (S3, say): the
restored server then found none of them. Blobs are imported last, into
the blob store the imported x:BlobStore names.
Tested: store tests pass on SQLite and RocksDB; without the first fix the
store test exits at the import's refusal.
Backported from 27.1 (#491), the two import fixes only; the S3 export and
store-check command stay on 27.1.
Fixed
- An import into a fresh store refused to run: every start writes the
fork's subspace (where the blob store is, permission grants, the log
files' setting), the import's own start too, and the import took that
for data. Since the blob store change (#333): 2026.11.9.1. The fork's
subspace is no longer counted; its records are keyed values an import
sets over. The store test now imports over a start-up record, and fails
without this.
- An import wrote the blobs into the data store, the empty store's blob
store, even when the imported settings name another (S3, say): the
restored server then found none of them. Blobs are imported last, into
the blob store the imported x:BlobStore names.
Tested: store tests pass on SQLite and RocksDB; without the first fix the
store test exits at the import's refusal.
Backported from 27.1 (#491), the two import fixes only; the S3 export and
store-check command stay on 27.1.
Fixed
- An import into a fresh store refused to run: every start writes the
fork's subspace (where the blob store is, permission grants, the log
files' setting), the import's own start too, and the import took that
for data. Since the blob store change (#333): 2026.11.9.1. The fork's
subspace is no longer counted; its records are keyed values an import
sets over. The store test now imports over a start-up record, and fails
without this.
- An import wrote the blobs into the data store, the empty store's blob
store, even when the imported settings name another (S3, say): the
restored server then found none of them. Blobs are imported last, into
the blob store the imported x:BlobStore names.
Tested: store tests pass on SQLite and RocksDB; without the first fix the
store test exits at the import's refusal.
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.
Backported from 27.1 (#491), the two import fixes only; the S3 export and
store-check command stay on 27.1.
Fixed
fork's subspace (where the blob store is, permission grants, the log
files' setting), the import's own start too, and the import took that
for data. Since the blob store change (#333): 2026.11.9.1. The fork's
subspace is no longer counted; its records are keyed values an import
sets over. The store test now imports over a start-up record, and fails
without this.
store, even when the imported settings name another (S3, say): the
restored server then found none of them. Blobs are imported last, into
the blob store the imported x:BlobStore names.
Tested: store tests pass on SQLite and RocksDB; without the first fix the
store test exits at the import's refusal.