Skip to content

[bug] IntegrityCheck --no-stamp still writes (workers do not get the flag) #2810

Open

Description

@fish5421

What happened

IntegrityCheck --no-stamp still writes (workers do not get the flag)

Summary

LifeOS 8.761.0. The header of LIFEOS/TOOLS/IntegrityCheck.ts says "--no-stamp and --section runs write nothing at all". Four things break that:

  1. runWorker() starts each worker with --run-entry <i> (and --verbose), not with --no-stamp. Inside a worker noStamp is therefore false: the output-coverage lane emits its Vigil event on every --no-stamp run, and the layer-one lane can rewrite its snapshot.
  2. A --section output-coverage run emits the same event (the emit has no guard for --section).
  3. The send-gate audit lane can emit events and the record-coverage lane calls writeEventOnce() whatever the flag says; the plugin lane writes a temporary folder.
  4. --accept-drop is not passed to the workers either, so a concurrent full run cannot accept a drop.

Related: on an install with no output ledger file (the recorder hook is not in the public release), the reconciler's event reads "Output coverage 0%, N escapes" at severity medium on every run. The number cannot change there.

Suggested fix: pass the flags to the workers, guard each emit with the read-only flags, and report "not measured" while no ledger file exists.

Details

  • Kind: bug
  • LifeOS version: 8.761.0

Filed with the LifeOS /feedback command. The reporter approved this exact text before it was sent; paths, secrets and personal details were stripped locally.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions