You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[lexical-y] A NodeState value set as a held composition ends is lost when a collaborator joins the held code line into the line before #9865
In the randomized carry lane (packages/lexical-y/src/__tests__/unit/LaneFuzz.test.ts), a NodeState value that the update ending a held composition sets does not stay on the characters it changed when a collaborator, concurrently, joins the held code line into the paragraph before it (Backspace at the start of the code block). The lane reports it as the known-open class carry:target-value (for example k-b (scalar, last set) on "C": "s1", intended "s3").
It reproduces on main (c4bfbfc) with no block added after the join, gc off and on. Histories that also add a block after the join used to hit other findings first on main (decorator-lost and others, because the old line's marker went to the added block, the bug #9860 fixes); with #9860 they reach this path too, so #9860 raises the class's known-open rate from 7.2 to 9.8 per 1,000 histories (71 more histories in 13,000 per gc setting, each of which fails identically on main without the added block).
Repro
LANE_STRICT=1 LANE_REPLAY=<file> pnpm exec vitest run --project unit packages/lexical-y/src/__tests__/unit/LaneFuzz.test.ts with this history (carry lane, seed 300269, gc off, untouched: 'none'):
Activity
[lexical-y] Chore: Raise the lanes' known-open rate for carry:target-…
[lexical-y] Chore: Raise the lanes' known-open rate for carry:target-…
[lexical-y] Chore: Raise the lanes' known-open rate for carry:target-…
[lexical-y] Chore: Raise the lanes' known-open rate for carry:target-…
[lexical-y] Chore: Raise the lanes' known-open rate for carry:target-…