registry: the two reopened OceanProtect requests belong back in the open table #1905
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!1905
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1117-2146-reopen"
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?
#1900 dropped #742 and #743 from
research/open-device-requests.jsonbecause both readstate: closedat 20:57. They were reopened at 21:13 - their closes had come from a PR-body parser matching a sentence that disclaimed the close, which is the same bug the reopen comments name - so the table was five rows for a seven-request queue within the hour.What this does
764640c3^, sorted by issue number.docs/DEVICE_REGISTRY.md. Nothing is hand-edited: the count is derived from the JSON, so the page says "Seven" because there are seven.blocked-on-build, which is the state #1900 introduced: the vendor publishes the field type and not its value (#742 E8000 front-end port count per node; #743 X8100/X9100 interface-module configuration), exactly like the OptiXtrans and UDW-PRO rows beside them.Measured after the change
Where it said
open: 7 ready: 2 blocked-on-build: 5- with #742 and #743 counted ready and #743's suggested path a 60-character slug of its own title.Gates
node scripts/regen-registry-doc.js --check- current: 2,348 models, 258 vendors, 29,235 sockets, 966 port shapesnode test/doc-catalog-counts.test.js- 43 checks passednode test/request-queue.test.js- 32 passedNo issue is closed by this PR, deliberately: #742 and #743 were just reopened from a close nobody asked for, and their fields are still unpublished.