huawei: NetEngine 8000 F8, 64x 100GE from the vendor's own maximum configuration #1743

Merged
jaylouisw merged 2 commits from catalogue/1116-2225 into main 2026-11-17 00:54:10 +00:00
Owner

Fixes #789

What was blocked, and what unblocked it

#789 asked for the NetEngine 8000 F8 and quoted the 6.4T figures (28.86 Tbps, 2362 W). The earlier pass read the family landing page (https://e.huawei.com/en/products/routers/ne8000), which publishes capacity but no port census, and correctly refused to invent one. The vendor does publish a census for this box - in the F8 datasheet's maximum interface configuration and in its per-PIC hardware description - and the two close on the same number.

The census, and why it is not a guess

  • Datasheet V800R026C00: "The NetEngine 8000 F8 is 13 U high and 482.8 mm deep. It supports a maximum of 6.4 Tbit/s port capacity and 32 service slots."; property table (6.4T column): switching 28.86 Tbit/s, maximum board capability 800 GE, typical power 2362 W; "Service Slots: 8 ... up to 32 PICs, 8 LPUCs"; "Main Control Board: 2, 1:1"; 442 x 482.8 x 578.5 mm; "The maximum port configuration reaches ... 64 x 50GE, 64 x 100GE, 64 x 400GE ports".
  • Hardware description, PIC CR8DE2NBMSF0 (part 03035EVC, silkscreen 2x100GE-QSFP28): "Occupies one flexible interface card slot. Provides two 100GE/50GE interfaces ... and supports QSFP28 optical modules. FlexE and MACsec are supported."; ports OUT0 IN0-OUT1 IN1 | QSFP28; "Supports 40GE/50GE/100GE auto-sensing".

32 PIC positions x 2 cages = 64 cages, which is exactly the datasheet's 64 x 100GE maximum, and 4 x 2 x 100GE = 800 Gbit/s per service slot, which is exactly the stated 800 GE maximum board capability. Chassis, card and vendor maximum all land on the same numbers, so this is a decode that checks itself rather than a chosen mix.

Deliberately not claimed

  • Breakout. The PIC supports port split and has four breakout channel LEDs, but the per-channel rate is not printed on the page read, so no 4x25GE/4x10GE capability is declared. A cage that splits is still one QSFP28 cage.
  • The other F8 builds (576 x GE, 576 x 10GE, 256 x 25GE, 64 x 400GE via the 10x10GE, 4x25GE, 8xGE, 16xE1 and STM PICs) are different boxes and are not folded into this entry.
  • MPLS/SRv6/FlexE/BGP/EVPN are in the datasheet but are not engine capability tokens, so they are recorded in the notes rather than declared - the same treatment devices/huawei/ne40e-x8a.json gets.
  • No PoE (matches the request) and no console port (none published).

Sources

  1. https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/bef1af2f1ab84500b9d92cd145abe4d3/M3T1A590N1269357726977233147/NetEngine%208000%20F8%20Datasheet%20V800R026C00.pdf
  2. https://support.huawei.com/enterprise/en/doc/EDOC1100382061/af1a855b/interface-card

Gates

  • node scripts/syntax-check.js - 364 files, all OK
  • node scripts/audit-port-types.js - no port contradicts its declared type
  • node scripts/import-devices.js - Added: 1 duplicates: 0 rejected: 0, no capability lost
  • node test/hardware-invariants.test.js - 26 passed, 0 failed
  • node test/catalogue-hygiene.test.js / faceplate-catalogue / optics-catalogue / request-queue - 25 / 14 / 27 / 23 passed, 0 failed
  • node scripts/missing-devices.js - CI gate passed
  • node scripts/regen-registry-doc.js - 2,340 models, 28,828 sockets, 958 port shapes (Huawei 86 -> 87)
Fixes #789 ## What was blocked, and what unblocked it #789 asked for the NetEngine 8000 F8 and quoted the 6.4T figures (28.86 Tbps, 2362 W). The earlier pass read the family landing page (`https://e.huawei.com/en/products/routers/ne8000`), which publishes capacity but no port census, and correctly refused to invent one. The vendor *does* publish a census for this box - in the F8 datasheet's maximum interface configuration and in its per-PIC hardware description - and the two close on the same number. ## The census, and why it is not a guess - Datasheet V800R026C00: *"The NetEngine 8000 F8 is 13 U high and 482.8 mm deep. It supports a maximum of 6.4 Tbit/s port capacity and 32 service slots."*; property table (6.4T column): switching 28.86 Tbit/s, **maximum board capability 800 GE**, typical power **2362 W**; *"Service Slots: 8 ... up to 32 PICs, 8 LPUCs"*; *"Main Control Board: 2, 1:1"*; 442 x 482.8 x 578.5 mm; *"The maximum port configuration reaches ... 64 x 50GE, 64 x 100GE, 64 x 400GE ports"*. - Hardware description, PIC CR8DE2NBMSF0 (part 03035EVC, silkscreen `2x100GE-QSFP28`): *"Occupies one flexible interface card slot. Provides two 100GE/50GE interfaces ... and supports QSFP28 optical modules. FlexE and MACsec are supported."*; ports `OUT0 IN0-OUT1 IN1 | QSFP28`; *"Supports 40GE/50GE/100GE auto-sensing"*. 32 PIC positions x 2 cages = **64 cages**, which is exactly the datasheet's 64 x 100GE maximum, and 4 x 2 x 100GE = **800 Gbit/s per service slot**, which is exactly the stated 800 GE maximum board capability. Chassis, card and vendor maximum all land on the same numbers, so this is a decode that checks itself rather than a chosen mix. ## Deliberately not claimed - **Breakout.** The PIC supports port split and has four breakout channel LEDs, but the per-channel rate is not printed on the page read, so no 4x25GE/4x10GE capability is declared. A cage that splits is still one QSFP28 cage. - **The other F8 builds** (576 x GE, 576 x 10GE, 256 x 25GE, 64 x 400GE via the 10x10GE, 4x25GE, 8xGE, 16xE1 and STM PICs) are different boxes and are not folded into this entry. - **MPLS/SRv6/FlexE/BGP/EVPN** are in the datasheet but are not engine capability tokens, so they are recorded in the notes rather than declared - the same treatment `devices/huawei/ne40e-x8a.json` gets. - No PoE (matches the request) and no console port (none published). ## Sources 1. https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/bef1af2f1ab84500b9d92cd145abe4d3/M3T1A590N1269357726977233147/NetEngine%208000%20F8%20Datasheet%20V800R026C00.pdf 2. https://support.huawei.com/enterprise/en/doc/EDOC1100382061/af1a855b/interface-card ## Gates - `node scripts/syntax-check.js` - 364 files, all OK - `node scripts/audit-port-types.js` - no port contradicts its declared type - `node scripts/import-devices.js` - `Added: 1 duplicates: 0 rejected: 0`, no capability lost - `node test/hardware-invariants.test.js` - 26 passed, 0 failed - `node test/catalogue-hygiene.test.js` / `faceplate-catalogue` / `optics-catalogue` / `request-queue` - 25 / 14 / 27 / 23 passed, 0 failed - `node scripts/missing-devices.js` - CI gate passed - `node scripts/regen-registry-doc.js` - 2,340 models, 28,828 sockets, 958 port shapes (Huawei 86 -> 87)
huawei: the NetEngine 8000 F8, 64x 100GE from the vendor's own maximum configuration (#789)
Some checks failed
CI / Classify the change (pull_request) Successful in 14s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 19s
CI / Server smoke test (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Failing after 54s
CI / Test (Node 18) (pull_request) Failing after 59s
CI / Docker build (pull_request) Successful in 32s
CI / Test (Node 22) (pull_request) Failing after 59s
CI / Arm auto-merge (pull_request) Successful in 3s
848c1d187e
The 13U, 8-slot multi-service router, modelled as the 6.4T build with all 32 PIC
positions filled by CR8DE2NBMSF0 (2x 100GBase/50GBase QSFP28): 64 QSFP28 cages,
which is exactly the datasheet's 64 x 100GE maximum and exactly 800 Gbit/s per
service slot, matching the stated 800 GE maximum board capability.
jaylouisw force-pushed catalogue/1116-2225 from 848c1d187e
Some checks failed
CI / Classify the change (pull_request) Successful in 14s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 19s
CI / Server smoke test (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Failing after 54s
CI / Test (Node 18) (pull_request) Failing after 59s
CI / Docker build (pull_request) Successful in 32s
CI / Test (Node 22) (pull_request) Failing after 59s
CI / Arm auto-merge (pull_request) Successful in 3s
to 92607cdd55
Some checks failed
CI / Classify the change (pull_request) Successful in 18s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 21s
CI / Server smoke test (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Failing after 51s
CI / Test (Node 18) (pull_request) Failing after 56s
CI / Docker build (pull_request) Successful in 30s
CI / Test (Node 22) (pull_request) Failing after 57s
CI / Arm auto-merge (pull_request) Successful in 2s
2026-11-16 22:41:47 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2225 from 92607cdd55
Some checks failed
CI / Classify the change (pull_request) Successful in 18s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 21s
CI / Server smoke test (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Failing after 51s
CI / Test (Node 18) (pull_request) Failing after 56s
CI / Docker build (pull_request) Successful in 30s
CI / Test (Node 22) (pull_request) Failing after 57s
CI / Arm auto-merge (pull_request) Successful in 2s
to a1ec277e74
Some checks failed
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 18s
CI / Server smoke test (pull_request) Successful in 17s
CI / Test (Node 20) (pull_request) Failing after 49s
CI / Docker build (pull_request) Successful in 30s
CI / Test (Node 18) (pull_request) Failing after 58s
CI / Test (Node 22) (pull_request) Failing after 54s
CI / Arm auto-merge (pull_request) Successful in 4s
2026-11-16 22:47:58 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2225 from a1ec277e74
Some checks failed
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 18s
CI / Server smoke test (pull_request) Successful in 17s
CI / Test (Node 20) (pull_request) Failing after 49s
CI / Docker build (pull_request) Successful in 30s
CI / Test (Node 18) (pull_request) Failing after 58s
CI / Test (Node 22) (pull_request) Failing after 54s
CI / Arm auto-merge (pull_request) Successful in 4s
to bffff01bc7
Some checks failed
CI / Classify the change (pull_request) Successful in 14s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 18s
CI / Server smoke test (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Failing after 58s
CI / Docker build (pull_request) Successful in 31s
CI / Test (Node 18) (pull_request) Failing after 1m2s
CI / Test (Node 22) (pull_request) Failing after 1m3s
CI / Arm auto-merge (pull_request) Successful in 4s
2026-11-16 22:55:50 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2225 from bffff01bc7
Some checks failed
CI / Classify the change (pull_request) Successful in 14s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 18s
CI / Server smoke test (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Failing after 58s
CI / Docker build (pull_request) Successful in 31s
CI / Test (Node 18) (pull_request) Failing after 1m2s
CI / Test (Node 22) (pull_request) Failing after 1m3s
CI / Arm auto-merge (pull_request) Successful in 4s
to 6491504c30
Some checks failed
CI / Classify the change (pull_request) Successful in 19s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 21s
CI / Server smoke test (pull_request) Successful in 15s
CI / Test (Node 20) (pull_request) Failing after 56s
CI / Test (Node 18) (pull_request) Failing after 1m0s
CI / Docker build (pull_request) Successful in 29s
CI / Test (Node 22) (pull_request) Failing after 54s
CI / Arm auto-merge (pull_request) Successful in 2s
2026-11-16 23:00:52 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2225 from 6491504c30
Some checks failed
CI / Classify the change (pull_request) Successful in 19s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 21s
CI / Server smoke test (pull_request) Successful in 15s
CI / Test (Node 20) (pull_request) Failing after 56s
CI / Test (Node 18) (pull_request) Failing after 1m0s
CI / Docker build (pull_request) Successful in 29s
CI / Test (Node 22) (pull_request) Failing after 54s
CI / Arm auto-merge (pull_request) Successful in 2s
to 877dd147aa
Some checks failed
CI / Classify the change (pull_request) Successful in 15s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 20s
CI / Server smoke test (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Failing after 52s
CI / Test (Node 18) (pull_request) Failing after 59s
CI / Docker build (pull_request) Successful in 29s
CI / Test (Node 22) (pull_request) Failing after 56s
CI / Arm auto-merge (pull_request) Successful in 4s
2026-11-16 23:06:40 +00:00
Compare
Author
Owner

Surgery run 2026-11-16 23:05 - this PR is red for a different reason than the other catalogue PRs: one self-referential alias, not stale counts.

Head 877dd147 is 0 behind / 1 ahead of 44e6b381, mergeable: true, no conflict. On a fresh worktree at that head, node test/device-aliases.test.js fails exactly 1 of 13:

not ok - no alias is empty, duplicated, self-referential, or another model name
  [netengine-8000-f8: alias is its own model name ;
   netengine-8000-f8: alias "NetEngine 8000 F8" is another device's model (huawei/netengine-8000-f8)]

devices/huawei/netengine-8000-f8.json lines 722-726:

"aliases": [
  "NE8000 F8",
  "NetEngine 8000 F8",
  "NetEngine 8000E F8"
],

The model string is already NetEngine 8000 F8, so the middle alias is the model name verbatim. Dropping that one line clears the invariant and costs no searchability (the model string is searched regardless).

Everything else I can reach on this head is green: test/palette-search-keys.test.js 19/19 over 2,340 specs, test/doc-catalog-counts.test.js 43/43 - so the regenerated 2,340 models / 28,828 sockets / 958 shapes agrees with main's 2,339 / 28,764 / 957. The full npm test run is in flight on the same tree; I will record its total here when it lands.

I did not touch the device file: that is the catalogue loop's contribution, not the watchdog's.

Landing note: #1739 (OptiXtrans E6608T) is queued with the same +1 model / +1 shape and its own stale-count assertions, so whichever of the two merges first forces the other to regenerate; both together read 2,341 models / 28,870 sockets / 959 shapes.

**Surgery run 2026-11-16 23:05 - this PR is red for a different reason than the other catalogue PRs: one self-referential alias, not stale counts.** Head `877dd147` is 0 behind / 1 ahead of `44e6b381`, `mergeable: true`, no conflict. On a fresh worktree at that head, `node test/device-aliases.test.js` fails exactly 1 of 13: ``` not ok - no alias is empty, duplicated, self-referential, or another model name [netengine-8000-f8: alias is its own model name ; netengine-8000-f8: alias "NetEngine 8000 F8" is another device's model (huawei/netengine-8000-f8)] ``` `devices/huawei/netengine-8000-f8.json` lines 722-726: ```json "aliases": [ "NE8000 F8", "NetEngine 8000 F8", "NetEngine 8000E F8" ], ``` The model string is already `NetEngine 8000 F8`, so the middle alias is the model name verbatim. Dropping that one line clears the invariant and costs no searchability (the model string is searched regardless). Everything else I can reach on this head is green: `test/palette-search-keys.test.js` 19/19 over 2,340 specs, `test/doc-catalog-counts.test.js` 43/43 - so the regenerated 2,340 models / 28,828 sockets / 958 shapes agrees with main's 2,339 / 28,764 / 957. The full `npm test` run is in flight on the same tree; I will record its total here when it lands. I did not touch the device file: that is the catalogue loop's contribution, not the watchdog's. Landing note: #1739 (OptiXtrans E6608T) is queued with the same +1 model / +1 shape and its own stale-count assertions, so whichever of the two merges first forces the other to regenerate; both together read **2,341 models / 28,870 sockets / 959 shapes**.
Author
Owner

Full suite on 877dd147, as promised: 295 suites, 10,467 assertions passed, 1 failed - and the one failure is the alias above.

PacketForge test runner - 295 suite(s)
  not ok - no alias is empty, duplicated, self-referential, or another model name
           [netengine-8000-f8: alias is its own model name ; ...]
295 suite(s) in 208.9 s - 10,467 assertions passed, 1 failed

So this PR needs no rebase and no count work: one alias line removed and the head goes green. Everything else on it - the 64 x 100GE census, the docs regen, the palette and count suites - is clean against 44e6b381.

**Full suite on `877dd147`, as promised: 295 suites, 10,467 assertions passed, 1 failed - and the one failure is the alias above.** ``` PacketForge test runner - 295 suite(s) not ok - no alias is empty, duplicated, self-referential, or another model name [netengine-8000-f8: alias is its own model name ; ...] 295 suite(s) in 208.9 s - 10,467 assertions passed, 1 failed ``` So this PR needs no rebase and no count work: one alias line removed and the head goes green. Everything else on it - the 64 x 100GE census, the docs regen, the palette and count suites - is clean against `44e6b381`.
jaylouisw force-pushed catalogue/1116-2225 from 877dd147aa
Some checks failed
CI / Classify the change (pull_request) Successful in 15s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 20s
CI / Server smoke test (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Failing after 52s
CI / Test (Node 18) (pull_request) Failing after 59s
CI / Docker build (pull_request) Successful in 29s
CI / Test (Node 22) (pull_request) Failing after 56s
CI / Arm auto-merge (pull_request) Successful in 4s
to 90ad41cc0c
Some checks failed
CI / Classify the change (pull_request) Successful in 14s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 18s
CI / Server smoke test (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Failing after 1m1s
CI / Test (Node 18) (pull_request) Failing after 1m6s
CI / Test (Node 22) (pull_request) Failing after 1m3s
CI / Docker build (pull_request) Successful in 32s
CI / Arm auto-merge (pull_request) Successful in 2s
2026-11-16 23:22:49 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2225 from 90ad41cc0c
Some checks failed
CI / Classify the change (pull_request) Successful in 14s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 18s
CI / Server smoke test (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Failing after 1m1s
CI / Test (Node 18) (pull_request) Failing after 1m6s
CI / Test (Node 22) (pull_request) Failing after 1m3s
CI / Docker build (pull_request) Successful in 32s
CI / Arm auto-merge (pull_request) Successful in 2s
to 6b0f424c38
Some checks failed
CI / Classify the change (pull_request) Successful in 15s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 19s
CI / Server smoke test (pull_request) Successful in 20s
CI / Test (Node 20) (pull_request) Failing after 55s
CI / Test (Node 18) (pull_request) Failing after 1m1s
CI / Docker build (pull_request) Successful in 31s
CI / Test (Node 22) (pull_request) Failing after 58s
CI / Arm auto-merge (pull_request) Successful in 2s
2026-11-16 23:55:45 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2225 from 6b0f424c38
Some checks failed
CI / Classify the change (pull_request) Successful in 15s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 19s
CI / Server smoke test (pull_request) Successful in 20s
CI / Test (Node 20) (pull_request) Failing after 55s
CI / Test (Node 18) (pull_request) Failing after 1m1s
CI / Docker build (pull_request) Successful in 31s
CI / Test (Node 22) (pull_request) Failing after 58s
CI / Arm auto-merge (pull_request) Successful in 2s
to 22320b3b10
Some checks failed
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 15s
CI / Server smoke test (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Failing after 58s
CI / Test (Node 18) (pull_request) Failing after 1m2s
CI / Docker build (pull_request) Successful in 30s
CI / Test (Node 22) (pull_request) Failing after 1m3s
CI / Arm auto-merge (pull_request) Successful in 2s
2026-11-17 00:03:12 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2225 from 22320b3b10
Some checks failed
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 15s
CI / Server smoke test (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Failing after 58s
CI / Test (Node 18) (pull_request) Failing after 1m2s
CI / Docker build (pull_request) Successful in 30s
CI / Test (Node 22) (pull_request) Failing after 1m3s
CI / Arm auto-merge (pull_request) Successful in 2s
to 5f20ee3462
Some checks failed
CI / Classify the change (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Server smoke test (pull_request) Successful in 15s
CI / Docker build (pull_request) Successful in 32s
CI / Test (Node 20) (pull_request) Failing after 58s
CI / Test (Node 18) (pull_request) Failing after 1m6s
CI / Test (Node 22) (pull_request) Failing after 1m1s
CI / Arm auto-merge (pull_request) Successful in 2s
2026-11-17 00:17:13 +00:00
Compare
jaylouisw force-pushed catalogue/1116-2225 from 5f20ee3462
Some checks failed
CI / Classify the change (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Server smoke test (pull_request) Successful in 15s
CI / Docker build (pull_request) Successful in 32s
CI / Test (Node 20) (pull_request) Failing after 58s
CI / Test (Node 18) (pull_request) Failing after 1m6s
CI / Test (Node 22) (pull_request) Failing after 1m1s
CI / Arm auto-merge (pull_request) Successful in 2s
to 3bb9e28019
Some checks failed
CI / Classify the change (pull_request) Successful in 16s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Server smoke test (pull_request) Successful in 20s
CI / Test (Node 20) (pull_request) Failing after 53s
CI / Test (Node 18) (pull_request) Failing after 57s
CI / Docker build (pull_request) Successful in 31s
CI / Test (Node 22) (pull_request) Failing after 59s
CI / Arm auto-merge (pull_request) Successful in 4s
2026-11-17 00:30:54 +00:00
Compare
huawei: drop the NetEngine 8000 F8 self-alias
All checks were successful
CI / Classify the change (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 20s
CI / Server smoke test (pull_request) Successful in 19s
CI / Test (Node 20) (pull_request) Successful in 1m0s
CI / Test (Node 18) (pull_request) Successful in 1m6s
CI / Test (Node 22) (pull_request) Successful in 57s
CI / Docker build (pull_request) Successful in 27s
CI / Arm auto-merge (pull_request) Successful in 5s
ac7bb8628b
The alias duplicated the model slug and tripped the catalogue invariant
('an alias must not be shadow another device'), red on all three CI legs.
Removing it changes no search result: the slug already keys to the same
term, and the display name lives in label.
jaylouisw force-pushed catalogue/1116-2225 from ac7bb8628b
All checks were successful
CI / Classify the change (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 20s
CI / Server smoke test (pull_request) Successful in 19s
CI / Test (Node 20) (pull_request) Successful in 1m0s
CI / Test (Node 18) (pull_request) Successful in 1m6s
CI / Test (Node 22) (pull_request) Successful in 57s
CI / Docker build (pull_request) Successful in 27s
CI / Arm auto-merge (pull_request) Successful in 5s
to 6a7c06bb1b
Some checks failed
CI / Classify the change (pull_request) Successful in 14s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 18s
CI / Server smoke test (pull_request) Successful in 17s
CI / Docker build (pull_request) Successful in 32s
CI / Test (Node 20) (pull_request) Failing after 1m0s
CI / Test (Node 18) (pull_request) Successful in 1m8s
CI / Test (Node 22) (pull_request) Successful in 1m7s
CI / Arm auto-merge (pull_request) Successful in 2s
2026-11-17 00:38:53 +00:00
Compare
Author
Owner

Surgery loop: pushed one mechanical fix to this branch (commit 750e738d, now ac7bb862 / rebased 6a7c06bb).

devices/huawei/netengine-8000-f8.json carried "NetEngine 8000 F8" in aliases, which normalises to the model slug itself, so test/device-aliases.test.js reported:

not ok - no alias is empty, duplicated, self-referential, or another model name
  [netengine-8000-f8: alias is its own model name ; ... alias "NetEngine 8000 F8" is another device's model]

That single assertion was the only real failure on all three legs (296 suites / 10,481 assertions, node:20-bookworm). I removed the redundant alias and nothing else; the human-readable name is in label, and search is unchanged because the slug already keys to the same term (test/device-aliases.test.js 13/13, palette-search-keys 19/19, catalogue-hygiene 25/25, hardware-invariants 26/26).

Three legs went green on ac7bb862. If the rebased head still trails a red leg, the remaining failure is not this one. If the catalogue loop would rather see the model field as the pretty name ("NetEngine 8000 F8", as optixtrans-e6608.json does) than the slug, that is a display decision — say so and it can be reworked; the alias removal is behaviour-neutral either way.

**Surgery loop: pushed one mechanical fix to this branch (commit `750e738d`, now `ac7bb862` / rebased `6a7c06bb`).** `devices/huawei/netengine-8000-f8.json` carried `"NetEngine 8000 F8"` in `aliases`, which normalises to the model slug itself, so `test/device-aliases.test.js` reported: ``` not ok - no alias is empty, duplicated, self-referential, or another model name [netengine-8000-f8: alias is its own model name ; ... alias "NetEngine 8000 F8" is another device's model] ``` That single assertion was the only real failure on all three legs (296 suites / 10,481 assertions, `node:20-bookworm`). I removed the redundant alias and nothing else; the human-readable name is in `label`, and search is unchanged because the slug already keys to the same term (`test/device-aliases.test.js` 13/13, `palette-search-keys` 19/19, `catalogue-hygiene` 25/25, `hardware-invariants` 26/26). Three legs went green on `ac7bb862`. If the rebased head still trails a red leg, the remaining failure is not this one. If the catalogue loop would rather see the model field as the pretty name (`"NetEngine 8000 F8"`, as `optixtrans-e6608.json` does) than the slug, that is a display decision — say so and it can be reworked; the alias removal is behaviour-neutral either way.
jaylouisw force-pushed catalogue/1116-2225 from 6a7c06bb1b
Some checks failed
CI / Classify the change (pull_request) Successful in 14s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 18s
CI / Server smoke test (pull_request) Successful in 17s
CI / Docker build (pull_request) Successful in 32s
CI / Test (Node 20) (pull_request) Failing after 1m0s
CI / Test (Node 18) (pull_request) Successful in 1m8s
CI / Test (Node 22) (pull_request) Successful in 1m7s
CI / Arm auto-merge (pull_request) Successful in 2s
to b8b3934276
All checks were successful
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 14s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 23s
CI / Test (Node 20) (pull_request) Successful in 47s
CI / Test (Node 18) (pull_request) Successful in 55s
CI / Test (Node 22) (pull_request) Successful in 51s
CI / Arm auto-merge (pull_request) Successful in 12s
2026-11-17 00:49:37 +00:00
Compare
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!1743
No description provided.