registry: the two reopened OceanProtect requests belong back in the open table #1905

Merged
jaylouisw merged 1 commit from catalogue/1117-2146-reopen into main 2026-11-17 21:50:01 +00:00
Owner

#1900 dropped #742 and #743 from research/open-device-requests.json because both read state: closed at 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

  • Puts the two OceanProtect rows back, verbatim from 764640c3^, sorted by issue number.
  • Regenerates docs/DEVICE_REGISTRY.md. Nothing is hand-edited: the count is derived from the JSON, so the page says "Seven" because there are seven.
  • Labels both issues 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

open: 7   ready: 0   blocked-on-build: 7   waiting on requester: 0   already catalogued: 0

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 shapes
  • node test/doc-catalog-counts.test.js - 43 checks passed
  • node test/request-queue.test.js - 32 passed

No 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.

#1900 dropped #742 and #743 from `research/open-device-requests.json` because both read `state: closed` at 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** - Puts the two OceanProtect rows back, verbatim from `764640c3^`, sorted by issue number. - Regenerates `docs/DEVICE_REGISTRY.md`. Nothing is hand-edited: the count is derived from the JSON, so the page says "Seven" because there are seven. - Labels both issues `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** ``` open: 7 ready: 0 blocked-on-build: 7 waiting on requester: 0 already catalogued: 0 ``` 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 shapes - `node test/doc-catalog-counts.test.js` - 43 checks passed - `node test/request-queue.test.js` - 32 passed No 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.
registry: the two reopened OceanProtect requests belong back in the open table
All checks were successful
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 11s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 20) (pull_request) Successful in 54s
CI / Test (Node 18) (pull_request) Successful in 1m2s
CI / Test (Node 22) (pull_request) Successful in 59s
CI / Arm auto-merge (pull_request) Successful in 22s
5a19682012
#742 and #743 were closed at 17:07 and 16:06 by merges whose PR bodies disclaimed the
close, and were reopened at 21:13 for exactly that reason. They were still closed when
#1900 dropped them from `research/open-device-requests.json` an hour later, so the table
went from seven rows to five for a queue that has seven open requests again.

Put both rows back, regenerate `docs/DEVICE_REGISTRY.md` (the count is derived now, so it
says "Seven" because there are seven), and label both issues `blocked-on-build`: they are
the same kind of blocker as the other five - the vendor publishes the field type and not
its value. `node scripts/request-queue.js` now reports seven blocked and zero ready.
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!1905
No description provided.