hyperledger / fabric-x-committer / 29748511094 / 3
92%
main: 91%

LAST BUILD BRANCH: snapshot-creation
DEFAULT BRANCH: main
Ran
Files 100
Run time 8s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 45.414% (+0.2%) from 45.243%
29748511094.3

Pull #685

github

cendhu 
[vc, coordinator, verifier] treat _snapshot and _checkpoint as system namespaces

Add committerpb.SnapshotNamespaceID and CheckpointNamespaceID to the
systemNamespaces list so their ns_<id> tables are created via the
existing namespace bootstrap path, alongside _meta and _config. No new
SQL DDL and no timestamp columns.

Recognize _snapshot and _checkpoint as first-class system namespaces
across policy validation, the dependency graph, and the VC preparer,
mirroring existing _meta/_config handling.

- Add utils.IsSystemNamespace covering _meta, _config, _snapshot, and
  _checkpoint, and use it in policy validation and dependency-graph
  read-key construction to avoid duplicating the 4-way guard.
- policy: reject _snapshot/_checkpoint as ordinary application namespace
  policies.
- dependencygraph: skip the normal _meta namespace-version read
  dependency for system namespaces.
- vc preparer: skip the _meta dependency for both; forward the _snapshot
  marker TX to the committer as a single new write into the _snapshot
  namespace (key = tx_id, value = SnapshotState{TxRef}); retain the
  single ReadWrite for _checkpoint. Fail the preparer worker rather than
  silently dropping a _snapshot write, since that would fork state across
  deterministic replicas.

Add table-driven tests for each package.

Signed-off-by: Senthilnathan <cendhu@gmail.com>
Pull Request #685: [vc, coordinator, verifier] treat _snapshot and _checkpoint as system namespaces

3585 of 7894 relevant lines covered (45.41%)

0.5 hits per line

Source Files on job core-db-test - 29748511094.3