mirror of
https://github.com/penpot/penpot.git
synced 2026-11-21 01:22:01 +00:00
Nesting, duplicating and swapping refuse to put a component inside itself; updating a main from a copy did not. A swap inside a variant's main reaches, through sync, a copy of the swap's new component whose slot was switched to that variant, so the copy holds its own component two levels down. Pushing that copy into its main made each main hold the other, and the sync cascade never settled. Add update-main-nesting-loop?: the copy holds a copy of its component, or of a component whose main holds one. An update main it matches changes nothing, and the generator skips such targets as it skips looping swaps. A fresh JVM library run (seed 20261101) found this: sync did not settle after 200 passes. The regression fails before the fix (sync does not settle) and passes after it: the update leaves the files unchanged and the program runs. The full common JVM suite passes at seed 712: 2068 tests / 33874 assertions. Compare lower-quantile milliseconds with the saved baseline; keep that baseline unchanged. The machine/JVM warning makes ratios rough. No world is flagged. World Baseline Now Ratio Main into 10 copies 1.790 0.898 0.50 Main into 100 copies 15.415 8.836 0.57 Main into 1000 copies 153.086 88.060 0.58 Three nesting levels 35.215 18.841 0.54 Dependency chain 68.931 37.993 0.55 Library update 83.083 43.555 0.52 Many plain shapes 4.837 2.206 0.46 Variant switch 32.052 20.015 0.62 AI-assisted-by: claude-opus-5-5