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>
39 lines
2.3 KiB
Markdown
39 lines
2.3 KiB
Markdown
---
|
|
id: "bug-1587"
|
|
status: "fixed"
|
|
status_updated: "2026-09-24"
|
|
status_note: "c9acd502"
|
|
component: "scheduler"
|
|
severity: "unknown"
|
|
timestamp: "2026-08-19T02:47:00Z"
|
|
last_seen: "2026-09-19T09:00:00Z"
|
|
occurrences: 1
|
|
files: ["src/scheduler/src/repl.c:183"]
|
|
tags: ["scheduler", "repl", "ux", "timestamp", "formatting", "not-yet-fixed"]
|
|
related: ["bug-1584"]
|
|
fix_commits: ["c9acd502"]
|
|
legacy: true
|
|
---
|
|
|
|
# bug-1587: User feedback (UX, not a functional defect): the REPL's startup line `[sim] loaded: 0 jobs…
|
|
|
|
## Description
|
|
User feedback (UX, not a functional defect): the REPL's startup line `[sim] loaded: 0 jobs, snapshot @ ts=331886899213871` prints the snapshot timestamp as a raw nanosecond integer -- would be more readable as a human-readable date/time.
|
|
|
|
## Environment
|
|
_Not recorded (migrated from buglog.json)._
|
|
|
|
## Reproduction
|
|
_Not recorded (migrated from buglog.json)._
|
|
|
|
## Root cause
|
|
repl.c's startup message (`fprintf(stdout, "[sim] loaded: %d jobs, snapshot @ ts=%llu\n", njobs, ...)`) formats the raw uint64 nanosecond value directly with no conversion -- purely a display/formatting gap, not a logic defect. Now that bug-1584 makes a normal-mode-recorded .replay file's timestamps genuine epoch nanoseconds (previously they were CLOCK_MONOTONIC-since-boot, which would have made a 'human-readable' rendering of this same field misleading/wrong before that fix), converting this to a readable date is now meaningful for normal-mode recordings; simulation-mode-authored .replay files may still show a discrete/simulated ts depending on how --sim-start-ts was chosen, but a calendar rendering of an epoch-ns value is well-defined either way.
|
|
|
|
## Fix
|
|
NOT YET FIXED. Straightforward: convert the raw `ts` to a formatted string (matching core_clock.c's existing ns_to_tlog_time()-style gmtime_r() conversion, or a simple strftime over ts/1e9) before printing, likely showing both the human-readable form and the raw ns value for debugging (`snapshot @ ts=<epoch-ns> (<YYYY-MM-DDTHH:MM:SS UTC>)`). Low risk, single call site (repl.c:183) -- worth checking whether other REPL/dump output (repl_info.c, xceadmin's `scheduler dump`) has the same raw-ns-only presentation and would benefit from the same treatment while this is being fixed.
|
|
|
|
## Verification
|
|
_Not recorded (migrated from buglog.json)._
|
|
|
|
## References
|
|
- Related: bug-1584
|