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

solidjs / solid / 34944164796
79%
main: 79%

Build:
Build:
LAST BUILD BRANCH: claude/project-thread-sm9oqo-5094
DEFAULT BRANCH: main
Ran 15 Sep 2026 08:00AM UTC
Jobs 1
Files 7
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

15 Sep 2026 07:55AM UTC coverage: 71.842%. Remained the same
34944164796

push

github

web-flow
feat(solid,web,signals): server boundary records on OBSERVE.server.records (#3452)

* feat(solid,web,signals): server boundary records on OBSERVE.server.records

The `"boundary"` record — one per `<Loading>` boundary that WAITED during
a server render, delivered when it settles: `{ id, at, durationMs, heldMs,
passes, outcome: "settled" | "fallback" | "client" | "error", streamed,
revealGroup?, ownerPath? }`, the thrown error beside it. `id` is the
boundary's hydration id, the one `SSR_RENDER_ERROR_CONTAINED` names in
`data.boundary`, so a record and a finding pair by it. `passes` counts
render passes over the content (discovery plus one per wait — `2` is one
round of async, more is a sequential chain) and doubles as the convergence
budget's counter. `streamed` is `registerFragment`'s answer — whether the
outcome reached the client after the shell flushed. Under a `<Reveal>`
group the record waits for the group's swap, via a per-leaf `onReveal`
hook every `revealFragments` site in `Reveal` now fires, so `heldMs` is
how long finished content sat behind its siblings. A boundary that
renders on its first pass emits nothing (the client `hold` rule); no clock
is read without a listener; the slots and emitter fold out of prod.

The channel is `OBSERVE.server.records.subscribe(type, listener)` — the
server twin of `OBSERVE.attribution.subscribe(type, …)`. C0's
`OBSERVE.server.invocations` (unreleased) is renamed onto it as the
`"invocation"` type; `InvocationChannel` is gone.

The types now layer one augmenter per interface, matching the package
chain. First cut had signals declare `ServerRecords`, solid-js augment it
through `"@solidjs/signals"` and web through `"solid-js"`; each side then
saw only its own overload. Reproduced in isolation: TypeScript merges two
augmentations of one re-exported interface through DIFFERENT alias paths
order-dependently, dropping one set with no error. So: signals declares
`ServerObserve` empty; solid-js augments it once with ... (continued)

519 of 790 branches covered (65.7%)

Branch coverage included in aggregate %.

772 of 1007 relevant lines covered (76.66%)

15.09 hits per line

Jobs
ID Job ID Ran Files Coverage
1 34944164796.1 15 Sep 2026 08:00AM UTC 7
71.84
GitHub Action Run
Source Files on build 34944164796
  • Tree
  • List 7
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #34944164796
  • 61a114c8 on github
  • Prev Build on next (#34939947700)
  • Next Build on next (#34948322193)
  • 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