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.3 KiB
| id | status | status_updated | status_note | component | severity | timestamp | last_seen | occurrences | files | tags | related | legacy | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bug-1596 | fixed | 2026-09-24 | scheduler | unknown | 2026-08-19T08:00:00Z | 2026-09-19T09:00:00Z | 1 |
|
|
|
true |
bug-1596: User-reported: info job "0-15-1787129769-0[0]" (jobid copied from info jobs' own output…
Description
User-reported: info job "0-15-1787129769-0[0]" (jobid copied from info jobs' own output, wrapped in double quotes out of habit) returns "[sim] info job: no such job 0 (0-0-0-0)" even though the job is genuinely present -- the identical jobid without quotes works.
Environment
Not recorded (migrated from buglog.json).
Reproduction
Not recorded (migrated from buglog.json).
Root cause
repl_info_job() already correctly calls parse_jobid() (lib/utils.c) with a strtoull() fallback -- confirmed NOT the bug. parse_jobid()'s two regexes (REGEX_JOBARRAY_ID/REGEX_JOBID, src/include/config.h) both require a whole-string anchor match (pmatch[0].rm_so==0 && pmatch[0].rm_eo==len). repl_split_tokens() (repl.c) is a plain whitespace tokenizer with no quote-awareness, so a quoted argument's token literally includes the surrounding " characters. Those quote characters break the anchor match (the regex still matches the interior substring, but not starting at offset 0 / ending at len), parse_jobid() returns -EINVAL, and the strtoull() fallback then parses a string beginning with " -- not a valid numeric prefix -- returning 0. MAKE_JOBID(0,0,0,0,0) formats back as "0-0-0-0", exactly matching the reported output.
Fix
Fixed as part of task 12.5. repl_split_tokens() (repl.c) now strips one matching pair of leading/trailing " or ' characters from each extracted token (length >= 2, first == last == a quote char) before returning it -- applies uniformly to every REPL command argument (info job/queue/worker/resource names, break filters), not special-cased to info job. New test in test_repl_breakpoints_inspection.c asserts info job "<jobid>" (double-quoted) and info job '<jobid>' (single-quoted) both resolve the same job as the unquoted form.
Verification
Not recorded (migrated from buglog.json).
References
- Related: bug-1591