---
id: "bug-1940"
status: "open"
status_updated: "2026-10-10"
status_note: "newly logged"
component: "apiserver"
severity: "wrong-result"
timestamp: "2026-10-10T08:14:46Z"
last_seen: "2026-10-10T08:14:46Z"
occurrences: 1
files: ["src/frontend/apiserver/controllers/jobs.go", "src/frontend/apiserver/backend/clib.go"]
tags: ["apiserver", "job-control", "signal"]
related: []
---

# 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
1. `POST /xce/v1/jobs/<id>/control` with action kill, signal `SIGUSR1`, force_kill true.
2. 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
TODO: required for fixed/partial

## Verification
- Test: TODO: name + file; RED before the fix, GREEN after
- Suites: TODO: suite results and build profile
- Live: TODO: soak/deploy run, or n/a and why

## References
- Related: none