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

chore(buglog): bug-1898 partial (query and control paths fixed; restart remains)

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:40:21 +00:00
parent 40917a01f0
commit 1fa0107357
Signed by untrusted user: rshen
GPG key ID: 80533536B0EB651C
2 changed files with 11 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -1,8 +1,8 @@
---
id: "bug-1898"
status: "open"
status: "partial"
status_updated: "2026-10-01"
status_note: "newly logged"
status_note: "query + filter-control paths fixed (3457d892, 40917a01); RestartJobByID still builds unevaluated CompFilterConditions (restart out of scope)"
component: "apiserver"
severity: "wrong-result"
timestamp: "2026-10-01T04:26:54Z"
@ -48,15 +48,15 @@ UPDATE (2026-10-01): Task 7.3 (3457d892) fixes the query paths (GetJobsInfo, Get
- Evidence: not kept (code reading only)
## Root cause
TODO: required for fixed/partial
Bracketed `job_id`/`job_name` filter values were turned into `CompFilterCondition`s and removed from the plain filters, but `store.ExecuteQuery` only ever evaluated `opts.Conditions`; nothing read `opts.CompConditions`. The conditions were therefore silently dropped on every path that built them (`GetJobsInfo`, `GetJobByIDs`, `FetchJobList` used by filter-based `ControlJob`, and `RestartJobByID`). The `ConditionArray` shape also had no AND slot for an element-only term, so the compound conditions could not have expressed the selection even if evaluated.
## Fix
TODO: required for fixed/partial
Spec job-array-one-based-index replaces the compound conditions with evaluated row predicates on the owned paths: `QueryOptions.Predicates` evaluated by `store.ExecuteQuery` after the plain conditions and before sort/pagination (task 5.3, 46f57095); `BuildSelectionPredicates` honouring each operator (task 7.2, 675d7d7f); `GetJobsInfo` and `GetJobByIDs` (task 7.3, 3457d892); filter-based `ControlJob` / `FetchJobList` (task 7.5, 40917a01). Remaining: `RestartJobByID` (`controllers/jobs.go` ~:863) still builds unevaluated `CompFilterCondition`s; restart by identity is out of scope of that spec.
## 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
- Test: `TestJobHandler_QuerySelections` / `TestJobHandler_GetJobByIDsSelections` (task 7.3) and `TestJobHandler_ControlFilterElementSelection*` (task 7.5) in `src/frontend/apiserver/controllers/jobs_handler_test.go`: RED before (`job_id:eq:X[2]` returned all 10 seeded rows; `-J 'foo[1]'` acted on 6 jobs incl. ordinary ones), GREEN after
- Suites: apiserver non-cgo unit tests (controllers, store, utils, backend) and the cgo build via `xce-build.sh apiserver asan build.jai`, passing, 2026-10-01
- Live: pending (spec task 10.2 exercises the REST query and control flow)
## References
- Related: bug-1896 (found while designing its fix, spec job-array-one-based-index)