lei.chen/myxce
1
0
Fork 1
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

chore(wolf): checkpoint buglog.json (958 bugs)

Browse source
This commit is contained in:
Rongsong Shen 2026-08-18 04:14:56 +00:00
parent da41cce2ea
commit 4fa7d8fc7e
Signed by: rshen
SSH key fingerprint: SHA256:8Vf2pZ3h6rJa7EhGK+WaAQ9Mta/apZvteW6g9U/WKKk
1 changed files with 20 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

20
.wolf/buglog.json
View file

@ -17154,6 +17154,26 @@
],
"occurrences": 1,
"last_seen": "2026-08-18T03:15:00Z"
},
{
"id": "bug-1577",
"timestamp": "2026-08-17T00:00:00Z",
"error_message": "No explicit error -- discovered via live testing task 6.1 (resource-value-verification): xce-deploy-ha's deploy-ha.sh Step 3 opt-in-by-presence worker branch (predates this feature) generates start-worker.sh whenever a worker binary (xcecd_virtual) happens to exist alongside the controller build, and generated start-all.sh always launches it. run-resource-verify.sh's own deployment (task 5.1+6.1) unconditionally hit this since a full `/xce-build all` leaves xcecd_virtual built. Result: a REAL worker daemon ('worker-1') ran for the whole duration of every xce-test-resources run, silently violating Requirement 2.1's design intent ('no real worker daemon process required') and periodically re-reporting its own resources (~every 15s) -- a live risk of triggering the still-open bug-1572 (scheduler double-free/crash on a resource's 2nd periodic report) if a run happened to last that long.",
"file": ".claude/skills/xce-test-resources/run-resource-verify.sh",
"root_cause": "deploy-ha.sh's worker-detection/start-all.sh generation is out of this task's edit boundary (xce-deploy-ha files are done/approved for this feature) and has no flag to skip the worker step -- it only conditionally starts one when a binary is present, with no opt-out.",
"fix": "start_all() now exports XCE_WORKER_BIN=/bin/true before invoking the generated start-all.sh. The generated start-worker.sh already reads ${XCE_WORKER_BIN:-<real path>} at RUN time from its own inherited environment, so pointing it at a real no-op binary makes the worker step exit immediately with no persistent process, without touching deploy-ha.sh itself. Verified via a /proc/*/exe-based watcher (not pgrep -f text matching, which self-matches -- see bug-1576) across a full default-resource-set run: zero xcecd_virtual/xcecd/xcecd_worker processes at any point post-fix, versus one running the entire time pre-fix.",
"tags": [
"resource-value-verification",
"xce-deploy-ha",
"worker-daemon",
"bug-1572",
"task-6.1"
],
"related_bugs": [
"bug-1572"
],
"occurrences": 1,
"last_seen": "2026-08-17T00:00:00Z"
}
]
}