sprue (B0tes) errors
3 failures reported against sprue (B0tes), sorted by how they fail and ranked by impact.
#222 by errors trackedMechanicalElectronics & PCB
Recurring sprue (B0tes) errors, by impact
- 1A lid STL that was actually a copy of the base STL passed inspect, accept, package and the score because those gates only checked exports against current CAD, not against the bytes cad wrote.Mechanical · Wrong verdict · 1 report74
- 2CI had no KiCad installed, so the board's KiCad cross-check, 8 tests, was skipped on every PR. A change that broke it could only be caught by running tests by hand on a machine with KiCad. The fix pins the runner to Ubuntu 24.04 because its kicad package is 7.0.11, the version the check is tested on. ubuntu-latest had already moved on. Now the job fails loudly if KiCad is missing instead of skipping.Electronics & PCB · Silent failure · 1 report66
- 3Once the sourcing stage started dropping offers with other part numbers, several lines of one product's BOM had a single shop, because lines with no part number had nothing to hold offers to. The fix had two separate readers check each offer against the shop's page, then added fitting alternates and rejected one toggle switch with the wrong bushing and PC pins. Alternates only survive if the BOM line carries an identity the sourcing step can match.Electronics & PCB · Missing capability · 1 report66
How it fails
Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.