myxce/.kiro/specs/job-array-one-based-index
Rongsong Shen fe5ddc9854
feat(job-array-one-based-index): collision checks after registration (task 2.3)
handle_jobsubmit now registers the submission first and checks the job
table second; a hit is answered -EEXIST and released through the atomic
reply-and-release step. For array submissions, array_identity_exists()
does one read-locked scan of the 32768 tagged element keys of the
array's block (element 0 included for pre-upgrade arrays), covering
both the element range and the array identity; unmarked submissions
keep jobid_range_exists. An existing X|3 now blocks a new X|5.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-01 10:14:47 +00:00
..
design.md docs(job-array-one-based-index): requirements, design and tasks; log bug-1898, bug-1899 2026-10-01 08:54:06 +00:00
requirements.md docs(job-array-one-based-index): requirements, design and tasks; log bug-1898, bug-1899 2026-10-01 08:54:06 +00:00
research.md docs(job-array-one-based-index): requirements, design and tasks; log bug-1898, bug-1899 2026-10-01 08:54:06 +00:00
spec.json docs(job-array-one-based-index): requirements, design and tasks; log bug-1898, bug-1899 2026-10-01 08:54:06 +00:00
tasks.md feat(job-array-one-based-index): collision checks after registration (task 2.3) 2026-10-01 10:14:47 +00:00