• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

solidjs / solid / 37267508845
76%
main: 89%

Build:
Build:
LAST BUILD BRANCH: size-gate-recorded-minified
DEFAULT BRANCH: main
Ran 05 Oct 2026 05:29AM UTC
Jobs 1
Files 8
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

05 Oct 2026 05:22AM UTC coverage: 75.991%. Remained the same
37267508845

push

github

web-flow
fix(signals): a fold repeats no unchanged presence to a held node (#3743, supersedes #3744) (#3791)

* fix(signals): a fold repeats no unchanged presence to a held node (#3743)

Port of #3744 (brenelz) onto L2 (#3774). The fold's presence loop
(`notifyFoldTail`) wrote every observed `in` node with `key in neu`;
`setSignal` joins a held node's transaction before its equality gate
(A34 (1): a write to a held node is a proposal, the same value or
another), so a `reconcile()` outside an action that had deleted an
observed key — the snapshot leaving it absent too — made the whole
mainline tick the action's: an unrelated `a.value` stayed stale until
the action settled. Presence is now diffed `old` -> `neu` like the
leaves (the fold's contract, #3296: the view the nodes were last told);
a live chained `old` (a store proxy) is written unconditionally as
before. `notifyFold` shares the tail.

`applyAdopt` materializes a nested overlay draft before taking its diff
base (`adoptPB` did so after it was taken): through the overlay's
prototype a deleted key still read as present, so the presence skip
fired on a real deletion, and a reconcile restoring the key never
re-proposed on the held leaf, which committed the draft's `undefined`
beside a backing that had the key.

Two L2 fixes the diff uncovered, pinned by the existing #2719/#3164 and
Q-D twin tests and a new leaf-only reader case: a container carrying an
arrangement guess is told of an arrangement change whether or not
anything subscribes to it (`notifyFoldTail`/`notifyWrites`) — for a
guessed container the write is the landing that judges the guess
(Q-D, plan sec. 39), and before only the unconditional presence write
reached the lane, so a newer question's rows landing beneath an
optimistic push published beside it for a reader of leaves alone; and
`_laneRebase` no longer re-stages a slot whose row the committed
backing already shows by key, nor an unchanged `length` (a spurious
identical frame).

Signals 490... (continued)

649 of 925 branches covered (70.16%)

Branch coverage included in aggregate %.

962 of 1195 relevant lines covered (80.5%)

27.97 hits per line

Jobs
ID Job ID Ran Files Coverage
1 37267508845.1 05 Oct 2026 05:29AM UTC 8
75.99
GitHub Action Run
Source Files on build 37267508845
  • Tree
  • List 8
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #37267508845
  • 924d909d on github
  • Prev Build on next (#37265807838)
  • Next Build on next (#37268691995)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc