devices(ubiquiti): the Express 7 is a router, and it was filed as an access point (refs #130) #2156
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!2156
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1119-1252"
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?
refs #130 — this does not close the Dream Wall Pro request (still blocked, unchanged below). It settles the other half of the stated lab: a router/gateway node for a routed lab with NAT and DHCP.
What was wrong
devices/ubiquiti/ux7.jsondescribed the UniFi Express 7 ascategory: "wireless"withwireless, l2-forward, cli, http-server, dhcp-client. The engine branches oncapabilities, so the Express 7 could not route, could not NAT, could not hand out a lease and could not filter — and because the palette filters on category, choosing "Router" did not offer it at all. Nothing failed, because an access point that sits on a network looks exactly like a gateway that does nothing.wirelessrouter1GPort count is unchanged (1x 2.5G RJ45 + 1x 10G RJ45); the 10G port is the vendor's default WAN, recorded in the description and the
notesrather than as arole, so no saved lab changes which port it treats as uplink.Sources (read 2026-11-19, crawler UA)
UX7-2: "Mesh-scalable, super-compact 10G Cloud Gateway with integrated 6 GHz WiFi 7".No datasheet exists for this SKU, so the rendered spec table is the vendor source — same position as
udr7.json.Test fix that the data change exposed
test/port-roundtrip.test.jslooked for a port whose PoE the engine inferred insidespecs.slice(0, 400). The only such port in the catalogue sits at index 399 (aruba/2530-8-PoE+port 1); moving UX7 into therouterbucket pushed it to 400 and the suite failed with "no such port found" while no PoE field had changed. The loop already breaks on its first candidate, so scanning the whole catalogue costs the same 4.6 s. The assertion ("exactly one candidate, and it does not start claiming it declared the wattage") is unchanged — the window was the bug.Gates
node scripts/syntax-check.js— 453 files, all OKnode scripts/audit-port-types.js— no port contradicts its declared typenode scripts/audit-poe-budget.js— 0 budgets with no PSE portnode scripts/check-control-bytes.js— nonenode scripts/check-doc-citations.js— 358 citations, none judged stalenode scripts/regen-registry-doc.js— regenerated, idempotent (2,356 models / 29,717 sockets / 972 shapes)node scripts/run-tests.js— 374 suites, 12,708 assertions, 0 failed (includes hardware-invariants 26/0, spec-vs-description, importer tripwire)Still blocked on #130
The Dream Wall Pro has no Ubiquiti surface at all (techspecs,
dl.ui.com,qig/, storefronts, grantee SWX, firmware platform index, controller device DB, Wayback CDX), so no UDW-PRO spec was written and none of the UDW's numbers were used. Unchanged: RJ45/SFP+ counts and rates, which are WAN, PoE class mix and budget, drive bays, cellular/WAN options — or a note that the requester meant the UDW.Surgery check (2026-11-19 13:1xZ) — the Node 20 red does not reproduce on this head (
4eb6223f).What I verified: merged
origin/main(053b3995) into this branch locally — clean, no conflicts, no add/add. Then ran the full suite under Node v20.18.1 (the dist used by the failing leg):374 suite(s) … 12708 assertions passed, 0 failed. Node 18 and Node 22 legs on this SHA are green; Node 26 locally is green too.So the single failing
Test (Node 20)leg looks like a flake or a runner-side failure, not a defect inux7.json/port-roundtrip.test.js. (Theslice(0,400)→ full-list change intest/port-roundtrip.test.jsis a good order-independence fix and is not the cause: it only widens the candidate search.)Not merging: head-SHA status is
failure, and the red-PR rule forbids it. Firmware loop: re-run the Node 20 job, or push any trivial commit to re-trigger the workflow — on a green run this merges clean (I have it stacked on current main, no conflicts).Rebased onto main (
87bbc699) ascf8f8012— the push is the rebase, no source edits beyond one generated line.Conflict was mechanical:
docs/CONNECTORS.mdpasted faceplate-test output,(... 29718 sockets ...)on main vs29717on the branch. Main's 29718 already included #2159's added 5G port, so neither side was right for the merged tree. Resolved by measuring:test/doc-catalog-counts.test.jsreports the merged catalogue at 2356 models / 29719 sockets / 972 shapes (the ux7 role change nets +1 socket over main), and the line now says 29719.docs/DEVICE_REGISTRY.mdcame from the generator, untouched by hand.Full suite on the rebased tree, Node 26: 375 suites / 12750 assertions, 0 failed. The previous red was
Test (Node 20)only, with the other two legs green and no failure text retrievable (log endpoint 404s) — that pattern is not reproducible here, so this push exists to get a clean run on a fresh head.4eb6223f15cf8f801268