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

solidjs / solid / 41715245178
78%
main: 89%

Build:
Build:
LAST BUILD BRANCH: claude/ssr-node-brand
DEFAULT BRANCH: main
Ran 03 Nov 2026 08:56PM UTC
Jobs 1
Files 12
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

03 Nov 2026 08:43PM UTC coverage: 78.249%. Remained the same
41715245178

push

github

web-flow
fix(signals): isPending() in a held pass is final there and re-derives at the landing; a first value staged this flush probes as its read (#4648) (#4667)

* fix(signals): an isPending() probe in a held pass is final there and re-derives at the landing; a first value staged this flush probes as its read (#4648)

An untracked isPending() in a pass a hold holds still reads the committed
value (ruling on #4662), but no longer answers true beside the fresh value
the pass's plain read saw (D-23): the pass is the hold's work, shown at the
landing, and a stale reader of what the probe read (A15), so it re-derives
on the landed world (F-1). An async memo is not re-asked (F-9). A probe of
a first value staged this flush reads the staging, as its plain read does
(D-23 exc. 1), instead of undefined. Replaces #4662.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0117BoWNSSgtemsSYsaX2hXE

* fix(signals): a late reader's isPending() probe settles with the hold too (#4648)

Two shapes the first commit left: a pass that first reads the held node in
a later flush, and one that probed only in the flush that staged the write,
before the hold existed. Each read the committed value through its probe;
neither was held yet, so it landed `p: true` beside the fresh value (D-23)
or stayed on `inner: 0` after everything settled (F-1). The probe now
watches the seam: if the flush parks with the pass, it runs again next
round, held, where its probe is final and it re-derives at the landing
(A15). Async memos and first passes are not re-run (F-9). Both read orders
give the same frames; `inner: 0` stays while held.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0117BoWNSSgtemsSYsaX2hXE

* fix(signals): the hold lands in one frame, and an in-flush probe reads the staging (#4648)

A held memo that re-derives at a landing now holds the release of the
hold's stashed runs, as... (continued)

807 of 1108 branches covered (72.83%)

Branch coverage included in aggregate %.

1132 of 1370 relevant lines covered (82.63%)

30.31 hits per line

Jobs
ID Job ID Ran Files Coverage
1 41715245178.1 03 Nov 2026 08:56PM UTC 12
78.25
GitHub Action Run
Source Files on build 41715245178
  • Tree
  • List 12
  • 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 #41715245178
  • 1445197e on github
  • Prev Build on next (#41680892396)
  • Next Build on next (#41719459783)
  • 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