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

未关闭
#2,810 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 5 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
领域
tooling

调研方向

Start with LIFEOS/TOOLS/IntegrityCheck.ts: check the header claim that --no-stamp and --section runs write nothing, then trace runWorker() to see that workers get --run-entry and --verbose but not --no-stamp or --accept-drop. Guard the output-coverage emit, the record-coverage writeEventOnce() calls and the plugin temp-folder write behind the read-only flags. Done when a --no-stamp run writes nothing in every lane and no-ledger installs report 'not measured'.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
TypeScript
星标
19.9k
派生
2.5k
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

danielmiessler/LifeOS 的其他 Issue

查看 danielmiessler/LifeOS 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。