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

chore(buglog): log bug-1903 (GetJobsInfo pagination); note bug-1898 progress

Browse source 
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Rongsong Shen 2026-10-01 12:21:34 +00:00
parent 3457d892b6
commit c3962e8f61
Signed by untrusted user: rshen
GPG key ID: 80533536B0EB651C
3 changed files with 78 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
.wolf/bugs/bug-1898.md
View file

@ -30,6 +30,8 @@ So the bracketed selection is silently dropped: `GetJobsInfo` (`job_id`/`job_nam
**Impact:** wrong result, and for control a wrong target: `xcecli jobs list X[2]` lists unrelated jobs; filter-based control with `-J 'name[k]'` and no other filter matches all jobs, and its "most recent job" rule (`jobs.go:2752-2757`) then kills/stops/resumes the newest job in the cluster instead of the named element. `ControlJobByID` is not affected (it post-filters with `foundJob`).
**Found by:** review (design review of spec `job-array-one-based-index`, 2026-10-01)
UPDATE (2026-10-01): Task 7.3 (3457d892) fixes the query paths (GetJobsInfo, GetJobByIDs); the filter-based control path follows in 7.5. RestartJobByID still builds unevaluated CompFilterConditions; restart by identity is out of scope of spec job-array-one-based-index.
## Environment
- OS: no /etc/os-release; Docker container; NixOS kernel; kernel Linux 6.18.33 x86_64
- libc: n/a (Go apiserver, pure-Go query path); host glibc 2.40