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>
3.6 KiB
| id | status | status_updated | status_note | component | severity | timestamp | last_seen | occurrences | files | tags | related | fix_commits | legacy | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bug-1614 | fixed | 2026-09-24 | xceadmin | unknown | 2026-08-21T08:50:00Z | 2026-09-19T09:00:00Z | 2 |
|
|
|
true |
bug-1614: pytest FAILED…
Description
pytest FAILED xceadmin/repo-mirror/src/xceadmin/tests/test_cli.py::test_cli_version_flag_includes_build_info_fields -- AssertionError: assert '2bf62a64-dirty' in 'xceadmin, version 0.1.0 (2bf62a64-857bd5b5, 2026-08-21T08:49:15Z)\n' (1 failed, 266 passed, 3 skipped) -- blocks meson's xceadmin-build.stamp custom_target, so no wheel is produced.
Environment
Not recorded (migrated from buglog.json).
Reproduction
Not recorded (migrated from buglog.json).
Root cause
dirty-content-fingerprint task 5.2's _compose_version_display() strip-and-append rule (cli.py:59-75, already implemented, matches design.md/tasks.md 5.2 exactly and all its OWN dedicated tests pass: test_compose_version_display_strips_dirty_suffix_and_appends_fingerprint, ..._anchored_suffix_not_blind_substring, test_compose_version_includes_fingerprint_when_build_info_has_one) now legitimately conflicts with an older, pre-existing task-2.2 test (test_cli_version_flag_includes_build_info_fields, added under Requirement 2.2 before this feature existed) that still asserts the RAW _build_info.GIT_COMMIT string (e.g. '2bf62a64-dirty') appears verbatim in xceadmin --version output. On a dirty tree with a non-empty DIRTY_FINGERPRINT, the composed output now correctly shows '2bf62a64-857bd5b5' (dirty suffix stripped, fingerprint appended per spec) instead of containing the literal '...-dirty' substring, so the old assertion is now stale and fails. tasks.md 5.2 is still unchecked ([ ]) -- this stale test update was left out of scope / not yet done.
Fix
RESOLVED CONCURRENTLY, not by this run: the first xce-build.sh xceadmin asan <dir> invocation (BUILD_TIME 2026-08-21T08:49:15Z) failed exactly as described above (1 failed, 266 passed, 3 skipped). While investigating, found src/xceadmin/tests/test_cli.py in the LIVE working tree already carried an uncommitted rewrite of test_cli_version_flag_includes_build_info_fields (now computes the expected display via the same strip-and-append contract cli.py's _compose_version_display() uses, instead of asserting raw GIT_COMMIT verbatim) -- but its mtime (08:50:55Z) POSTDATES the first build's BUILD_TIME, meaning some other concurrent process/session applied this fix mid-investigation, not this build-verification agent. Re-ran the identical xce-build.sh command a second time against the now-updated tree (BUILD_TIME 2026-08-21T08:55:40Z, dirty_fingerprint recomputed to c0c2a0b7 since tracked-file content changed) and it now passes clean: '267 passed, 3 skipped in 7.65s', wheel built at .../xceadmin/dist/xceadmin-0.1.0-py3-none-any.whl. Installed that wheel alone into a fresh throwaway venv (nix develop wrapper, matching this project's established pattern) and confirmed xceadmin --version -> 'xceadmin, version 0.1.0 (2bf62a64-c0c2a0b7, 2026-08-21T08:55:40Z)', exit 0 -- dirty suffix correctly stripped and replaced with the fingerprint, not doubled up. Task 5.2 appears functionally complete now; tasks.md still shows it unchecked ([ ]) as of this writing -- someone should flip it once the concurrent editor's change is reviewed/committed.
Verification
Not recorded (migrated from buglog.json).
References
Not recorded (migrated from buglog.json).