Skip to content

Commit 5af48f5

Browse files
frames: trace tier — update-site wait for a mounted occurrence's new { $tr } record
`#syncSlots`' mounted branch guarded the update site against the regions tier only (`needsRegions`); the trace tier's wait covered the fresh mount alone. A MOUNTED occurrence's new record whose literal args carry a `{ $tr }` marker while the trace tier is absent — a live slot op minting the page's first trace after the shell, a refetch adding a projection arg — was pushed into the live binding raw, the marker read as the value. Now that record stays pending in the store: the live binding keeps the args it shows, `needsTrace` starts the load (nothing announced it), and the install's flush re-syncs with the tier in place and applies the record as an args change into the same mount with the marker materialized. C4's `regions` update-site wait, mirrored. Pin: consistency/tier-trace-hold.spec "update site" (document face: a live slot op mints the page's first trace post-shell with the tier absent → no raw read, args kept, one load, applied on the install's flush into the same `<li>`). Fails on the base at the first assertion (the loader never called). Measured (exact A/B of the built dist through scripts/size's bundler, base numbers reproduce the Phase 1 record byte-for-byte): frames: eager client consumer 40,012 min / 13,086 br +12 / +3 page: base server components 119,056 min / 37,747 br +12 / -25 page: live server components 130,927 min / 41,396 br +12 / -31 Non-SC scenarios 0 / 0. No cap changed. Web client suite 1187, hydrate suite 439 green; harness seeds 3289 / 91501 ×500: SC arm 0 findings, generic arm (IGNORE=C1,C9,C19,E) 0 findings. Co-authored-by: Cursor <[email protected]>
1 parent 5c5991c commit 5af48f5

4 files changed

Lines changed: 84 additions & 2 deletions

File tree

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
"@solidjs/web": patch
3+
---
4+
5+
frames: the trace tier's update-site wait. A MOUNTED occurrence's new slot record whose args carry a `{ $tr }` container-trace marker while the trace tier is absent (a live slot op minting the page's first trace after the shell, a refetch adding a projection arg) now stays pending in the store: the live binding keeps the args it shows, the tier load starts, and the install's flush applies the record as an args change with the marker materialized. Before, `#syncSlots` guarded only the fresh mount (`needsTrace`) and the regions tier at the update site (`needsRegions`), so such a record was pushed into the live binding raw — the marker read as the value. Mirrors the regions tier's update-site wait.

0 commit comments

Comments
 (0)