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.8 KiB

Raw Blame History

status

status_updated

status_note

component

severity

timestamp

last_seen

occurrences

files

bug-1936: apiserver drops cwd, env, run/resource limits, file transfers and I/O paths of REST job submissions

Description

Observed: (source reading, .kiro/reviews/project-gap-review-2026-10-10.md (P0); to be confirmed by a failing test before the fix) modelJobToSubmit() (src/frontend/apiserver/backend/convert.go:323-375) builds the controller's job_startinfo_t with only cmdline, execuser, launch_type and pre/post-exec; it never sets exdata, exechome or execcwd:

si := (*C.job_startinfo_t)(C.calloc(1, C.sizeof_job_startinfo_t))
si.cmdline = C.CString(job.Command)
... // no si.exdata / si.exechome / si.execcwd

So --cwd, --env, --file transfers, interactive mode, every *_limit flag (incl. -W run limit), -i/-o/-e, asked hosts and begin/end time are kept only in the apiserver's memory and never reach the controller or the worker.

Expected: Every submit option the apiserver accepts reaches the worker in the job's start info (exdata, exec home, cwd), or is rejected as unsupported. Impact: Silent wrong result: jobs run without the limits, environment, working directory and I/O paths the user asked for (e.g. a -W run limit is never enforced). 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

Submit through REST/xcecli with xcecli jobs submit -W 1 --cwd /tmp --env A=1 sleep 120 on any deployment.
Inspect the job's start info at the worker (worker log of the launched unit) or the controller's job.start_info: no exdata, no cwd; the job runs past one minute.

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