queue: "ready" means buildable, not merely form-complete - five of five are blocked #1900
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1900
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1117-2055"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The queue's own front page said
open: 5 ready: 5this evening, for a queue in which not one of the five can be written without inventing a port census.node scripts/request-queue.js --skeleton 810writesOptiXtrans E9624as a one-porteth0box; the real subrack is 24 service slots with no ports until a board is named. That gap is step 3 ofdocs/plans/stated-configurations.md, and this PR lands it.What changed
scripts/forgejo-api.js- newlistIssueComments(number), the reader the plan said was missing. It is only called for a request that already carries the label, so a healthy queue makes no extra calls.scripts/request-queue.js-blocked-on-buildis its own state, never counted ready. Its group prints the newest comment that names the block, verbatim, capped at 220 characters, plus the issue URL. Markdown emphasis is stripped so the line reads as a sentence. If the comments cannot be read, the request still shows as blocked and says so - a failed read must not turn a visible blocker into an invisible "ready".--skeletonon a blocked request still emits the stub, but warns on stderr that it is an empty chassis and that filling it from datasheet maxima is the errordocs/MAINTAINING.mdwarns about.test/request-queue.test.js- nine assertions: the verdict line is picked over a newer off-topic comment, emphasis and>quotes are stripped, a long comment is capped, an empty or failed read isnullrather than an empty string.Why a label and not a regex over maintainer prose
The plan proposed matching "blocked on" in the last comment. That re-classifies a request the moment someone writes "blocked on the bench", and it cannot be un-done by the person who knows the answer. The label is one click, appears in the issue list without opening it, and the comment still carries the reason - so the queue quotes the evidence instead of deriving a verdict from it.
Measured, live queue, 2026-11-17
The label was applied to #130 (UDW-PRO - no vendor page at all), #803 (E6616X - E6600 board census hedex-only), #807 (E9605), #808 (E9612), #810 (E9624) - the last three on one client-board chapter each.
Two corrections that fell out of it
research/open-device-requests.jsonstill listed #742 and #743, both closed. Dropped, sodocs/DEVICE_REGISTRY.mdstops claiming seven open requests; it now says five.scripts/regen-registry-doc.jsas the word "Seven", so a generated page went stale about its own length the moment two of the seven closed. The count is now derived from the JSON (0-10 spelled out, digits above), with a queue-empty branch, because a page that exists to catch staleness should not be the one that goes stale.Gates
node scripts/syntax-check.js- 394 files, all OKnode scripts/audit-port-types.js- "No port contradicts its declared type."node scripts/regen-registry-doc.js --check- current: 2,348 models, 258 vendors, 29,235 sockets, 966 port shapesnpm test- 322 suites, 11,202 assertions passed, 0 failednode test/request-queue.test.js- 32 passed, 0 failed (9 new)No device spec is added here and no issue is closed by this PR: the five remain blocked on their named fields, and
docs/plans/stated-configurations.mdstep 6 (an OTN port type, needing Jay's approval) is what unblocks three of them.964f6a137b6a0b3b82996a0b3b82996ed3e9e2d3