signex (alplabai) errors

33 recurring problems engineers report in signex (alplabai), ranked by impact.

#9 by errors trackedECAD

Recurring signex (alplabai) errors, by impact

  1. 1A schematic PR merged while its review still requested changes, and open findings include the net-class picker keying on label text, child-sheet label LOCAL getting class nets LOCAL while the netlist calls it /LOCAL, assignments going to the last active project instead of the label's project, and unreadable sheets dropped silently.ECAD · Agent failure · 1 report74
  2. 2A Signex polygon boolean returned a partial or inverted ring when inputs touched or nearly touched, a plausible-but-wrong shape feeding footprint courtyards.ECAD · Agent failure · 1 report74
  3. 3A Signex project file saved with a UTF-8 BOM opened as an empty project and would have been replaced on the next save, and merge-conflict-marker files also opened empty.ECAD · Agent failure · 1 report74
  4. 4Parts placed before a footprint was bound to their library row stay empty, and changing a row footprint later does not update parts already placed from it. ERC flags them, and the netlist and BOM go out without the footprint. MPN and manufacturer are not stamped at placement either, so ERC reports missing MPNs on parts whose library row has one.ECAD · Agent failure · 1 report74
  5. 5Two footprints sharing an unannotated or empty reference get all their pads on the first one. The second has none and no error is raised.ECAD · Agent failure · 1 report74
  6. 6A blocker for the headless command runner from last hour's #1923. Before the font scan runs, text width falls back to a monospace estimate, so a headless run computes different label hit boxes and flags than the GUI, and the result depends on the host's fonts. An agent and a person looking at the same schematic would get different checks.ECAD · Agent failure · 1 report66
  7. 7A board changed by another program was still overwritten on save, because only schematic sheets were compared against their disk baseline, and boards now get the same Reload, Overwrite, Cancel card.ECAD · Agent failure · 1 report66
  8. 8A changed value shape in a newer build's project rules section made the whole project refuse to open, and a no-touch save rewrote sections the build does not own.ECAD · Agent failure · 1 report66
  9. 9A child sheet placed twice gets its own designators per placement, but the app does not record which sheet symbol the user descended through, so exporting the current page always prints /A's designators (R1 instead of R101) even when opened from B.ECAD · Agent failure · 1 report66
  10. 10A project git commit labelled Save X or Restore X read the working file whenever the commit worker got to it, so intervening writes were committed under the wrong label.ECAD · Agent failure · 1 report66
  11. 11A sheet keeps the old library symbol body after the library symbol is redrawn in place with the same uuid, so new placements do not match the Components panel preview, which reads the library fresh. The preview and the placed part differ.ECAD · Agent failure · 1 report66
  12. 12Adding an existing library from a project subfolder stores just the file name, so it resolves to a nonexistent path and never mounts, and two same-named libraries in different folders collide and the second is silently skipped.ECAD · Agent failure · 1 report66
  13. 13An earlier session's autosave recovery copy gets overwritten while its restore prompt is still open, because the prompt does not block edits, then restore claims the copy was kept when it was not.ECAD · Agent failure · 1 report66
  14. 14An ECO could remove GND from the board's net table while a pad still sat on GND. In signex, a hand-edited change list could drop a net while a pad still named it, leaving the board inconsistent. The fix makes ECO validate and execute refuse the whole list and leave the board as it was.ECAD · Agent failure · 1 report66
  15. 15An EDA app. In an undocked window, the Properties panel and Find have no window scope, "so an edit made from an undocked window's context can land on the main window's active sheet." The PCB right-click and component drag have the same problem.ECAD · Agent failure · 1 report66
  16. 16An open-source EDA app can now renumber designators on the board, and carrying them back to the schematic is a separate PR still to come. Positional re-annotate orders parts by X then Y, numbers the bottom side after the top, and skips locked footprints. Until Back Annotate lands, a board renumber leaves the schematic behind.ECAD · Agent failure · 1 report66
  17. 17Closing a dirty symbol or footprint editor tab throws away the draft without asking, and the file stays in the dirty list so Save All on quit fails every time after that.ECAD · Agent failure · 1 report66
  18. 18Closing a schematic tab with unsaved edits, then reaching that sheet through ERC navigation or a child-sheet double-click, loaded the on-disk sheet over the parked edited one; the edits were gone while the path still showed dirty.ECAD · Agent failure · 1 report66
  19. 19ERC flagged a label sitting on a sheet pin as orphaned, while the netlist builder treated the same label and pin as one net, so two parts of one tool disagreed about whether something was connected.ECAD · Agent failure · 1 report66
  20. 20ERC severities and the pin matrix live in a machine-wide prefs.json while the project file has no rule field, so two projects cannot have different rules and the same project gives different ERC results on another machine or in CI.ECAD · Agent failure · 1 report66
  21. 21Grid snap in a schematic editor saves points 1 to 4 nm off grid because an f32 pitch is widened to f64, and the same visible grid point saves as two different values depending on click vs library drop.ECAD · Agent failure · 1 report66
  22. 22If the target sheet could not be opened, the open step gave up silently and an ERC quick fix placed a no-connect on whatever sheet was active. A rectangle edit also collapsed shapes to zero height, and sheets in subfolders were registered by bare file name.ECAD · Agent failure · 1 report66
  23. 23In an open schematic editor, Save As onto a file that was still opening re-keyed the engine, then the late open replaced it with the disk content, losing any edit made after the Save As.ECAD · Agent failure · 1 report66
  24. 24In an undocked schematic window the Active Bar and context menu act on whatever sheet is active in the main window. With sheet A undocked and B active, a click in A's window can edit B.ECAD · Agent failure · 1 report66
  25. 25In this Rust PCB editor, rotation moves pad centres but not pad shapes, so an SOIC-8 at 90 degrees draws pads crosswise to the real copper. The footprint editor and the board use two different pad types, so a footprint looks different in the Footprint Editor and on the board.ECAD · Agent failure · 1 report66
  26. 26library_id, row_id, and library_version are never written to .snxsch and reset on load, so the app marks the sheet dirty, the next save drops them, and the updates scan reports drift again on every open.ECAD · Agent failure · 1 report66
  27. 27New boards have no fab-class rules, so DRC on a board with no clearance set uses 0.2 mm and says so in the Messages panel. The maintainer wants board creation to ask for fab-class rules up front.ECAD · Agent failure · 1 report66
  28. 28On a case-insensitive project, Lib.snxsch and lib.snxsch were one file on disk but two save-ordering keys, so an older snapshot could land over a newer write, previously returning silently.ECAD · Agent failure · 1 report66
  29. 29Pads already joined by a same-net pour still got ratsnest lines. The model stores no filled polygon, so the fix uses the zone outline and ignores holes and fill clearance, which is documented as a known gap.ECAD · Agent failure · 1 report66
  30. 30Project ERC flagged every wire ending on a sheet pin as dangling, even though the netlist joins those pins. The ERC rule and the netlist builder kept separate lists of what counts as a connection.ECAD · Agent failure · 1 report66
  31. 31The preview ran with an empty net colour map, so it folded two wires the real move keeps apart. Locked items stayed put with no reason shown. The fix gives the preview the same colour map and logs what a lock holds back. Still open: with keep-wires off or more than 60 items selected, a locked symbol is drawn moving while the commit skips it.ECAD · Agent failure · 1 report66
  32. 32The save-time check for outside changes, added last hour, does not cover PCB saves at all, so a board edited by another program still gets overwritten on Save. The baseline after saving is re-read from disk, so an outside write landing in that window becomes the new baseline.ECAD · Agent failure · 1 report66
  33. 33Three data-loss bugs in a schematic editor: save silently overwrote a sheet that a git pull or sync client had changed on disk, saving through a symlink replaced the link with a copy so one file became two documents, and save after moving the project folder re-created the old folder and wrote there.ECAD · Agent failure · 1 report66

How it fails

  1. Agent failure33

Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.