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.1 KiB
| id | status | status_updated | status_note | component | severity | timestamp | last_seen | occurrences | files | tags | related | legacy | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bug-1718 | fixed | 2026-09-24 | controller | unknown | 2026-08-26T16:23:00Z | 2026-09-19T09:00:00Z | 1 |
|
|
true |
bug-1718: A python3 pty-driver embedded via a heredoc on a command that ALSO receives piped stdin silently…
Description
A python3 pty-driver embedded via a heredoc on a command that ALSO receives piped stdin silently discards the piped input
Environment
Not recorded (migrated from buglog.json).
Reproduction
Not recorded (migrated from buglog.json).
Root cause
First draft of run_interactive_pty() did: printf '%s\n' "$script" | python3 - "$XCE_TEST" ... <<PYEOF ... PYEOF. python3 - reads its ENTIRE program from stdin until EOF; a <<HEREDOC redirect on the same command line takes precedence over the pipe for that command's stdin (the pipe's implicit fd0 assignment is overridden by the explicit redirect), so the heredoc (the Python source) became the process's only stdin content. Once python3 finished reading its own program from that stream, stdin was already at EOF -- the script's own sys.stdin.read() (meant to receive the piped xce_test command script) returned empty every time, silently. No error was raised; it just produced an empty commands list, which would have made every interactive-scenario assertion trivially fail once real command sending began (caught before ever running the script standalone, via careful re-reading of the draft rather than via a failing run).
Fix
Write the Python driver ONCE to its own temp file via mktemp + cat >"$PTY_DRIVER" <<PYEOF ... PYEOF at script startup (cleaned up by an EXIT trap), then invoke it as printf ... | python3 "$PTY_DRIVER" args... -- this leaves the pipe as the sole, unambiguous stdin source for the running Python process, since python3 does not consume stdin to obtain its own source.
Verification
Not recorded (migrated from buglog.json).
References
Not recorded (migrated from buglog.json).