Triage the hardware backlog mechanically, with guards that refuse to guess #1048
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!1048
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/request-sweep"
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 backlog is ~800 issues, nearly all device requests, and a steady fraction ask for hardware that
is already modelled. Answering that has so far meant a human reading the body and grepping the
catalogue.
scripts/sweep-device-requests.jsParses the subject out of a request title, normalises it, and matches by exact normalised model name
or vendor + model. Posts a comment naming vendor, model, file and category, and invites the reporter
to disagree about the ports:
The guards exist because the first draft was wrong
The initial version closed three Ubiquiti requests citing
roku/Ultra, matched on the shared wordUltra. A close pointing at a different product is worse than an open request, so the matcher
gained three rules rather than a better apology:
Ultrais a product line;Wave-ProandAX3areproducts.
+survives normalisation. Stripping punctuation madeWiFi Mesh 3+andWiFi Mesh 3thesame key - different products - and would have merged
RB5009UPr+S+INwithRB5009UPr+S+OUT,both of which the catalogue has.
With the guards, the full-backlog scan went from 20 matches to 17, and the three wrong ones
disappeared.
Run this turn
41 requests closed, each with its own comment naming the file: 24 from the first two hundred issues
(TP-Link TL-SG105/105E, the Huawei CPE/WiFi family, FS N8560-32C, Aruba AP22, Acer Nitro 5) and 17
from the older MikroTik and Ubiquiti block (CCR2004, CCR2116, the CRS317/326/328 switches, RB750r2,
RB952Ui, RB960PGS, RB5009UPr+S+IN/OUT, ACB-AC, NS-5AC, Loco5AC, PBE-5AC-620, Wave-Pro, WaveFiber
ONU). Two were spot-checked against their bodies before closing: #845 said "absent from the
catalogue" with a grep proving it, which was true when filed.
17 remain in the current scan - the matcher is deliberately narrow, and it does not read bodies,
so a 48-port request matched to a 24-port namesake needs a human eye.
docs/TRIAGE.mddocuments the rules, the guards and what the tool refuses to do. Report by default;closing is opt-in and bounded.
96 suites, 4678 assertions, all passing.
Closes #1047.