With kpex held at 0.3.12 and KLayout moved from 0.30.3 to 0.30.10, the extracted current mirror's header went from 'vref vss vcopy sky130_gnd' to 'sky130_gnd vcopy vref vss'. Same port set, every device card byte-identical, stable across runs. The reporter ruled out KLayout's SPICE writer by measurement before filing. Filed Aug 10, active again today.

Recurring agent failure issue in klayout-pex (iic-jku)

klayout-pex (iic-jku)ECADAgent failureMedium confidence

What engineers report

A recurring agent failure problem in klayout-pex (iic-jku) that mostly hits the electrical engineer.

Failure pattern: validation / failure

Analyst note

From the Grok pain-radar digests, Nov 10-11 2026 (Nov 10 8:41 AM ET through Nov 11 7:41 AM ET digests plus the Haitch editions). Verified live 2026-11-11: issue/PR read; title and state confirmed.

What it costs a team

Modeled annual cost

$30,000

For a team of 5

Prototype delay

3 days

Modeled schedule slip per occurrence

Time lost

240 min

Per engineer per month, about 1 incidents

How the cost is modeled

240 min/month × 5 engineers × 12 months = 240 hours × $125/hour = $30,000

A modeled estimate with medium confidence. Swap in your own team size and loaded rate to size it for your team.

Engineering tools that address it

No engineering tool profile lists this error yet. Browse tools that connect to klayout-pex (iic-jku).

Evidence

  1. 1iic-jku/klayout-pex Issue #175: Top-level .SUBCKT pin order changes across KLayout 0.30.3 → 0.30.10 at fixed kpex - silent positional miswiring (SPICE writer ruled outgithub.com

More recurring errors in klayout-pex (iic-jku)

See all 7 klayout-pex (iic-jku) errors

Sourced from public community reports. Costs and delays are modeled estimates, not measurements. Know a better source or a fix? Tell us at hello@productflo.io.