Rongsong Shen
141ac22c54
The apiserver's job store learned of a new job only from the controller's asynchronous OnJobCreated / array push, so a 'jobs kill' (or query) straight after 'jobs submit' could answer 'job not found' for the job just accepted (2 of 4 immediate kills). services.SubmitJob now records the accepted job right after the controller's reply (which comes only after the job is committed and applied): one record per element, base+i for arrays, stored with the new DataStore.PutIfAbsent and marked JobInfo.Provisional (json:"-", not a column). An OnJobCreated that already arrived is never overwritten; the push that arrives later replaces the provisional record -- including in dispatchJobArray, whose duplicate check no longer treats a provisional element as already known. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| autoscaler | ||
| configs | ||
| controller | ||
| docs | ||
| frontend | ||
| harness | ||
| include | ||
| lib | ||
| nixSupport | ||
| scheduler | ||
| schema | ||
| tools | ||
| worker | ||
| xceadmin | ||
| flake.lock | ||
| flake.nix | ||
| meson.build | ||
| meson.options | ||