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

solidjs / solid / 42081084760
78%
main: 89%

Build:
Build:
LAST BUILD BRANCH: claude/ssr-node-brand
DEFAULT BRANCH: main
Ran 05 Nov 2026 06:15PM 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

05 Nov 2026 06:06PM UTC coverage: 78.249%. Remained the same
42081084760

push

github

web-flow
fix(signals): a lane reveals whole beside its parent's landing (#4677) (#4687)

* fix(signals): a lane reveals whole beside its parent's landing (#4677)

An async memo over isPending(x) showed 'pending: true' beside an isPending(x) binding still false: the parent landing at the lane's seam voided the binding's lane run while the memo's run showed. The voided runs now show with the lane's (F-6, F-1); the landing's re-derivation follows next round. The second order from the issue (a landing flush's own run shown beside held runs parked with a re-derivation, F-1/F-7) is pinned it.fails.

Co-authored-by: tembo[bot] <208362400+tembo-io[bot]@users.noreply.github.com>

* chore(size): re-record lane rows after #4682 and #4677

Five rows, +111 B minified each from #4677 and +7 B from #4682 (not re-recorded yet): signals + isPending/latest, app hydrating + every store family, the live page (a frozen floor, Size-Exception in the PR body), the compiled live page and live + router. Measured locally over next @ 5208944 with the in-repo compiler build; caps are measured brotli + 10 B.

Co-authored-by: tembo[bot] <208362400+tembo-io[bot]@users.noreply.github.com>

* fix(signals): hold a landing's plain runs for its re-derivation (#4677)

Case 2 of #4677: when the lane lands first, the write's landing re-derives the badge memo onto a new flight and holds its runs for it (U-5), but that flush's runs of effects deriving plainly from the landing still ran, so details showed Item 1 beside id 0 (F-1, F-7). The landing walks the effects that derive plainly from what it commits (stopping at verdict readers and lane runs, which show now: F-6, D-25, #4398) into a round-scoped set, and verdict.ts attachWaits re-queues their runs to the next round, with the landing's held runs. The set is dropped at the end of the round, so nothing outlives the flush.

Co-authored-by: tembo[bot] <208362400+tembo-io[bot]@users.noreply.github.com>

* chore(size): re-record lane rows for #4677 case... (continued)

807 of 1108 branches covered (72.83%)

Branch coverage included in aggregate %.

1132 of 1370 relevant lines covered (82.63%)

30.13 hits per line

Jobs
ID Job ID Ran Files Coverage
1 42081084760.1 05 Nov 2026 06:15PM UTC 12
78.25
GitHub Action Run
Source Files on build 42081084760
  • 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 #42081084760
  • 6b7474b2 on github
  • Prev Build on next (#42016964063)
  • Next Build on next (#42095770241)
  • 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