feat(job-array-one-based-index): clamp the apiserver array size limit (task 5.2)
job.max_array_size is resolved by a pure resolveMaxArraySize: unset or 0 gives 1000, 1..32767 is used as is, values above 32767 are clamped to 32767 with a startup warning naming the configured and effective value, and a negative value refuses startup. The old >2147483646 rejection is gone; the shipped config documents the bounds. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
b88e352616
commit
7f417262c5
4 changed files with 189 additions and 24 deletions
|
|
@ -101,7 +101,7 @@
|
|||
- _Requirements: 1.1, 1.2, 5.8, 5.14_
|
||||
- _Depends: 1.3_
|
||||
|
||||
- [ ] 5.2 (P) Clamp the array size limit setting
|
||||
- [x] 5.2 (P) Clamp the array size limit setting
|
||||
- Move the limit rule into a pure resolver: unset or 0 gives 1000, 1..32767 used as is, above 32767 clamped to 32767, negative refuses startup; drop the old upper-bound rejection
|
||||
- Log a startup warning with the configured and effective values when clamped; update the shipped config's comment for the setting (default 1000, at most 32767)
|
||||
- Done when the config tests pass for 0, 1, 32767, 32768, 3000000000 and -1, and a clamped startup logs the warning
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue