Rongsong Shen
d26ff8870d
The buglog was one 27K-line JSON file whose fields covered only symptom,
root cause and fix, as free text: 2% of entries named the code version a
bug was found on, 12% the build profile, 36% a way to reproduce, and 58% of
the file was OpenWolf hook auto-detections ("Missing guard clause",
"Function not marked async" on .md files).
- .claude/skills/buglog/bug-record.md: the record standard. Eight
sections (Summary as the title, Description, Environment, Reproduction;
Root cause, Fix, Verification, References once fixed), each with the
content it must contain -- e.g. Environment needs the OS, the libc the
failing binary loads (from its ELF interpreter: glibc 2.42 in the nix
shell vs 2.40 on the host), toolchain, build profile and commit.
- .wolf/bugs/<id>.md: 500 records migrated from buglog.json; every field
verified to round-trip. They carry legacy: true and an explicit "not
recorded" where the old log had no such field; component derived from
file paths, severity from keywords (else unknown), fix_commits from
hashes in status_note/fix that git resolves (91 of 463 fixed).
- .wolf/buglog-archive.json: the 710 hook auto-detections, verbatim.
- .wolf/buglog.json is now an index generated from the records, keeping
the fields OpenWolf's hooks and `openwolf bug search` read.
- scripts/buglog.py rewritten: new (template + Environment collected from
the machine and --binary), check, status (refuses a status the record
doesn't support; fixed needs Root cause, Fix, Verification and
--commit hashes git resolves), note, recur, set, show, list, triage,
env, index. 29 unittest cases in scripts/tests/test_buglog.py.
- scripts/git-hooks/pre-commit runs `check --staged`: incomplete staged
records, a legacy record hand-changed to fixed without the fix-time
sections, a new record claiming legacy: true, or a stale index refuse
the commit.
- scripts/gitea-sync.py reads the records: issue body = the record's
sections plus linked fix commits (origin remote, GITEA_COMMIT_REPO to
override), and a body hash so an issue's text is refreshed when the
record changes.
- bug-1866 rewritten to the full standard as the worked example.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2.4 KiB
| id | status | status_updated | status_note | component | severity | timestamp | last_seen | occurrences | files | tags | related | legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bug-1620 | fixed | 2026-09-24 | build | unknown | 2026-08-21T15:56:00Z | 2026-09-19T09:00:00Z | 1 |
|
|
|
true |
bug-1620: ERROR: Unknown option: "dirty_fingerprint"
Description
ERROR: Unknown option: "dirty_fingerprint".
Environment
Not recorded (migrated from buglog.json).
Reproduction
Not recorded (migrated from buglog.json).
Root cause
xce-build.sh worker asan --incremental runs meson setup --reconfigure "$BUILD_DIR" -Dcommit_id=... -Dbuild_time=... -Ddirty_fingerprint=... against a pre-existing xce.build dir that was configured before commit a860141b (feat(dirty-content-fingerprint): add dirty_fingerprint meson option). Meson 1.9.1 validates -D flags on --reconfigure against the OLD cached coredata BEFORE re-reading meson.options to pick up newly-added options, so any brand-new option name passed via -D on the same reconfigure invocation is rejected as unknown -- even though the option genuinely exists in the current src/meson.options (confirmed: intro-buildoptions.json in the stale build dir only listed commit_id/build_time, not dirty_fingerprint). Pure staleness in the incremental build dir vs. the current option surface, unrelated to any C source edit.
Fix
Ran meson setup --reconfigure xce.build once with NO -D overrides first -- this successfully re-reads meson.options and registers the new dirty_fingerprint option in cached coredata (confirmed via intro-buildoptions.json). A subsequent normal xce-build.sh worker asan --incremental (which does pass -Ddirty_fingerprint=...) then succeeded cleanly. General recipe: if --incremental reconfigure fails with 'Unknown option: "X"' for an option that IS defined in src/meson.options, the build dir predates that option's introduction -- do one plain meson setup --reconfigure <build_dir> with no -D args to register it, then retry the real build. Rebuilding without --incremental (full rm -rf + fresh setup) also fixes it but wipes any other component's binaries sharing that dir (see bug-1565).
Verification
Not recorded (migrated from buglog.json).
References
- Related: bug-1565