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.7 KiB
| id | status | status_updated | status_note | component | severity | timestamp | last_seen | occurrences | files | tags | related | fix_commits | legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bug-1597 | fixed | 2026-09-24 | obsolete: src/frontend/Makefile removed (6fabdba9) |
apiserver | unknown | 2026-08-19T00:00:00Z | 2026-09-19T09:00:00Z | 1 |
|
|
|
|
true |
bug-1597: backend/reconnect.go:6:10: fatal error: client.h: No such file or directory (compilation…
Description
backend/reconnect.go:6:10: fatal error: client.h: No such file or directory (compilation terminated) -> make: *** [Makefile:33: build-server] Error 1
Environment
Not recorded (migrated from buglog.json).
Reproduction
Not recorded (migrated from buglog.json).
Root cause
build-server's recipe is a bare cd apiserver && go build -o /tmp/apiserver ./cmd/main.go with no CGO_CFLAGS/CGO_LDFLAGS, so cgo has no -I path to src/include (client.h) or BUILD_DIR/lib (controller.capnp.h) and no -L/-l for libxce + its pkg-config deps. Unlike build-server, both test-backend (same Makefile, bug-1558) and apiserver/meson.build derive CGO_CFLAGS/CGO_LDFLAGS via pkg-config (librtti, c-capnproto, openssl, tinylog) plus -I$(BUILD_DIR)/lib / -L$(BUILD_DIR)/lib -lxce -- build-server was apparently never given the same treatment, so it only works if CGO_CFLAGS/CGO_LDFLAGS happen to already be exported in the shell (e.g. by meson's custom_target env), not under a bare nix develop ../ --command make build-server. Reproduced identically with and without an unrelated comment-only change staged elsewhere in the same package (apiserver/backend/handler.go), confirming this is pre-existing and unrelated to that change.
Fix
Not fixed (out of scope for the verification task that found it -- reported only). Workaround that does compile cleanly (exit 0): run the build-server go build with the same self-derived CGO env as test-backend, e.g. inside nix develop ../ --command bash -c '...': BUILD_DIR=$(pwd)/../xce.build; CGO_CFLAGS="-fsanitize=address -g $(pkg-config --cflags librtti c-capnproto openssl tinylog) -I$(pwd)/../include -I$BUILD_DIR/lib"; CGO_LDFLAGS="-fsanitize=address -g $(pkg-config --libs librtti c-capnproto openssl tinylog) -lm -lrt -L$BUILD_DIR/lib -lxce"; then CGO_ENABLED=1 CGO_CFLAGS="$CGO_CFLAGS" CGO_LDFLAGS="$CGO_LDFLAGS" go build -o /tmp/apiserver ./cmd/main.go. Requires BUILD_DIR/lib/libxce.a to already exist (prior xce-build.sh lib run). Proper fix would mirror bug-1558's FRONTEND_CGO_CFLAGS/FRONTEND_CGO_LDFLAGS into the build-server recipe in src/frontend/Makefile.
Verification
Not recorded (migrated from buglog.json).
References
- Related: bug-1558