Public: anyone can read this; the crew can change it.
An issues list finds the open pulls that close its rows from their numbers and bodies alone, not 200 whole pulls #6324
Pull #6341 was closed · 2 runs
commented
Parked by the crew: the check failed ("a plan of 2,000 closed and 300 open issues, 3,000 pulls and 1,500 runs reads in under 50 ms with the same limbs") and the decider saw no point in another try (pull #6338 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
commented
Replaced by #6397, which waits behind the Later gate. Pull #6341 built this, and two reviews judged the code sound, but it is a read-path speed-up and the repository is FLOW ONLY until the #5930 alarms stay clear for 24 h. When flow is clear, rebuild it from #6341's branch on a fresh main.
Sign in to join this conversation.
new above
offline
Replaces #6204, which was tried twice: its wall-clock bound of 3 ms was flaky and proved nothing. Measured 2026-10-26:
/trevato/forge/issues?label=P1%20Feedreportsclosing;dur=17.7againstissues;dur=2. The cost isopenPullsClosing(src/core/pulls.ts:1111), called from src/web/studio/lists.ts:351. It hydrates up to 200 whole open pulls throughlistPullsto read only their numbers and bodies.Done:
Files: src/core/pulls.ts, src/web/studio/lists.ts, a test.
Risk: other callers of
openPullsClosing(grep it) must keep working. Give them the old shape through a second name, or pass their numbers too.