JSON Bug Report:

[mohan-bee]

Solver input JSON attachment

_board#76 _-SchematicTracePipelineSolver-solver-input (1).json

Notes

No response

[tscircuitbot]

Created or updated #680 for this JSON bug report.

Report id: bug-report-20260717T042845Z

[DPS0340]

I ran this attachment against current main (v0.0.110) to try to pin down the symptom, since the Notes section is empty.

The pipeline solves without failing, and the final placements look correct:

VIN:  orientation=y+  allowed=["y+"]  center=(-1.15, 2.57)   OK
VOUT: orientation=y+  allowed=["y+"]  center=( 1.05, 2.57)   OK

Both respect availableNetLabelOrientations, and neither label overlaps either chip body.

One thing worth flagging for anyone else who picks this up, because it looks alarming mid-run: NetLabelPlacementSolver reports VIN at x- — outside the allowed set — but that's the deliberate any-orientation retry (triedAnyOrientationFallbackForCurrentGroup, NetLabelPlacementSolver.ts:314-336) kicking in when the constrained placement fails. RailNetLabelCornerPlacementSolver then pulls it back to y+, which is what ends up in the output. So an intermediate-stage snapshot here is misleading, not buggy.

Could you say what looked wrong on your end — label position, trace routing, or something in the rendered schematic? Happy to dig in with a concrete symptom; right now I can't tell this run apart from correct output.

[DPS0340]

Ran this board through a set of measurable defect checks on current main (full table and method in #709):

20260717T042845Z   cross=0  collinear=0  labelsInChips=0  labelOverlaps=0  diagonals=0  failedRoutes=0

Every solver reports solved, no route is abandoned, and none of the geometric defects I can measure are present.

Since the Notes field on this report is empty, I can't tell whether that means it was fixed by later work or whether the problem is something these checks don't cover — connectivity, a missing label, ordering, and similar wouldn't show up.

Either this can be closed, or a one-line note saying what to look for would help. As it stands it's indistinguishable from the boards that do still have defects, which makes the report queue harder to triage.

Happy to dig into this specific board if you can say what looked wrong.