Development record
The load.preflights setting is described as how many preflights may be in their test stages at once, in its refusal, the help, the command page, the bundled LOAD rule and the code comments, but since iss-2610282016250805 a preflight queued at its race gate takes no slot, so a race stage can run beside as many unit stages as the setting: it bounds what the first gate admits, not what runs. The configuration chapter of the brief still says the setting takes 1 or 2, where 4 is now the most.
issueresolvedminoriss-2610290033556553
The load.preflights setting is described as how many preflights may be in their test stages at once, in its refusal, the help, the command page, the bundled LOAD rule and the code comments, but since iss-2610282016250805 a preflight queued at its race gate takes no slot, so a race stage can run beside as many unit stages as the setting: it bounds what the first gate admits, not what runs. The configuration chapter of the brief still says the setting takes 1 or 2, where 4 is now the most.
Frontmatter
| id | iss-2610290033556553 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610290033556553-the-load-preflights-setting-is-described.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610282016250805The load gate leaves the machine idle: a make preflight queued at its race gate still counts as Busy at the first gate, so with load.preflights=2 one preflight running its race stage and a second waiting idle at the race gate fill both slots and every other preflight waits. Observed 2026-10-28 20:02-20:15Z: four preflights queued, one test stage running, load 13 on 16 cores. MaxPreflightSlots also caps the setting at 2.