feat(buglog): one Markdown record per bug, checked against a record standard

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>
This commit is contained in:
Rongsong Shen 2026-09-28 03:40:11 +00:00
parent 27b7a84980
commit d26ff8870d
Signed by untrusted user: rshen
GPG key ID: 80533536B0EB651C
512 changed files with 40724 additions and 17843 deletions

41
.wolf/bugs/bug-1860.md Normal file
View file

@ -0,0 +1,41 @@
---
id: "bug-1860"
status: "fixed"
status_updated: "2026-09-27"
status_note: "c69705ae: controller is ground truth on rejoin; controller refuses non-PEND dispatch and re-sends state; scheduler adopts controller allocation on RUN update"
component: "controller"
severity: "unknown"
timestamp: "2026-09-24T14:38:03Z"
last_seen: "2026-09-24T14:38:03Z"
occurrences: 1
files: ["src/scheduler/src/core_events.c", "src/controller/sched.c", "src/controller/resync.c"]
tags: ["scheduler", "controller", "resync", "ha", "divergence", "design"]
related: []
fix_commits: ["c69705ae"]
legacy: true
gitea_issue: 279
gitea_synced_status: "fixed"
---
# bug-1860: Scheduler keeps a job RUN (with allocation) forever after the controller requeued it to PEND while…
## Description
Scheduler keeps a job RUN (with allocation) forever after the controller requeued it to PEND while the scheduler was disconnected: scheduler.log 'JOBS_PUSH: refusing resync state 0x1 for jobid ... -- existing job is RUN with a real allocation on record' on rejoin; job never redispatched (seen in bug-1859's chaotic soak)
## Environment
_Not recorded (migrated from buglog.json)._
## Reproduction
_Not recorded (migrated from buglog.json)._
## Root cause
core_events.c JOBS_PUSH bug-1812 guard refuses any non-terminal resync state that would drop a real allocation, to protect against a committed snapshot racing the scheduler's own fresh dispatch. It cannot tell that race apart from a genuine, committed controller-side requeue (e.g. resync 'unrecognized' -> record_job_reconcile_pending_fact) that happened while the scheduler was disconnected, and JOBS_PUSH carries no per-job freshness (commit LSN/version) to decide. Needs a design decision (e.g. per-job last-modified LSN in the push).
## Fix
_Not recorded (migrated from buglog.json)._
## Verification
_Not recorded (migrated from buglog.json)._
## References
- Gitea: #279