1.7 KiB
| id | status | status_updated | status_note | component | severity | timestamp | last_seen | occurrences | files | tags | related | fix_commits | legacy | gitea_issue | gitea_synced_status | gitea_synced_hash | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bug-1867 | fixed | 2026-09-26 | e4bb492a: capnp Job.exitInfo (JobExitInfo) -- checkpoint encode/decode/restore carry exit_info. Live force-snapshot soak blocked by pre-existing bug-1870. |
lib | unknown | 2026-09-26T03:33:15Z | 2026-09-26T03:33:15Z | 1 |
|
|
|
|
true | 286 | fixed | ab5e7522ad72 |
bug-1867: Controller job snapshot/checkpoint drops job.exit_info: the capnp Job struct (controller.capnp)…
Description
Controller job snapshot/checkpoint drops job.exit_info: the capnp Job struct (controller.capnp) has no exit-info field, so capnp_encode_job() never writes it and a job restored from a snapshot (rather than WAL replay) has exit_info NULL for both DONE/EXIT (FINISH) and failed (FAIL) jobs
Environment
Not recorded (migrated from buglog.json).
Reproduction
Not recorded (migrated from buglog.json).
Root cause
struct Job in src/schema/controller.capnp has finishtime/runtime/pidinfo/pendreason but no exit code; xce_job_t.exit_info (job_exitinfo_t*) has no capnp mapping. bug-1689 and bug-1754 made WAL_JOB_FINISH/WAL_JOB_FAIL carry the exit code, but anything restored from a checkpoint/entity snapshot after WAL truncation loses it (persistence.md field-completeness).
Fix
UPDATE (2026-09-26): live-verified by the bug-1870 force-snapshot soak (real snapshot install, 63fd3d2a)
Verification
Not recorded (migrated from buglog.json).
References
- Related: bug-1689, bug-1754
- Gitea: #286