docs(buglog): log P0 defects from the 2026-10-10 review (bug-1936..bug-1952)

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

2026-10-10 08:15:28 +00:00

2.2 KiB

Raw Blame History

status

status_updated

status_note

component

severity

timestamp

last_seen

occurrences

files

bug-1940: job control ignores the requested signal and the force-kill flag (apiserver to controller)

Description

Observed: (source reading, .kiro/reviews/project-gap-review-2026-10-10.md (P0); to be confirmed by a failing test before the fix) The control handler passes a JSON event string as content (controllers/jobs.go:2260-2277); signalNumber() looks it up as a signal name, fails and falls back to TERM/TSTP/CONT; backend/clib.go:697-705 always sends sig.force = 0 and ckpt.kill = 0, dropping ForceKill and the checkpoint kill/method options (:746-762).

Expected: A kill with a user-chosen signal sends that signal; force kill and checkpoint options reach the controller. Impact: Wrong result: users cannot send a specific signal or force-kill a job. Found by: review: .kiro/reviews/project-gap-review-2026-10-10.md (P0)

Environment

OS: no /etc/os-release; Docker container; NixOS kernel; kernel Linux 6.18.33 x86_64
libc: glibc 2.42-47 (interpreter /nix/store/wb6rhpznjfczwlwx23zmdrrw74bayxw4-glibc-2.42-47/lib/ld-linux-x86-64.so.2)
Toolchain: gcc (GCC) 15.2.0, meson 1.9.1
Build: asan (xce.build)
Code: scheduler-framework @ 94472ee3-dirty
Deployment: any (found by source reading; the failing test that confirms it is named in Verification)

Reproduction

POST /xce/v1/jobs/<id>/control with action kill, signal SIGUSR1, force_kill true.
The controller receives TERM with force 0.

Frequency: deterministic (by code reading; confirmed by the RED test of the fix)
Evidence: the code sites quoted in Description; no logs kept.

Root cause

TODO: required for fixed/partial

Fix