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

powersemmi / ruststream / 33710932143
98%

Build:
DEFAULT BRANCH: main
Ran 03 Sep 2026 03:22AM UTC
Jobs 1
Files 100
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 Sep 2026 03:19AM UTC coverage: 97.525% (-0.08%) from 97.604%
33710932143

push

github

web-flow
Publish through the typed entry point only, with a codec-optional surface and a batch-aware harness (#281)

* test: pin the test client on the serialized lane

The lanes tests cover what a handler publishes, but nothing covered what
the test client injects. A `Serialized` value handed to `message(..)` has
to reach the subscription the way the service's own publish path sends
it: the destination read off the declaration, and the bytes untouched by
any codec.

* fix: keep the declared return type on a settling handler body

A settling handler expanded into an `IntoOutcome` conversion over an
unascribed async block, so the body was type-checked with nothing naming
its output. `IntoOutcome` is implemented for `Result<_, E>` over any `E`,
which left a body returning `Result<(), HandlerOutcome>` with a bare
`Ok(())` and no `?` anywhere unable to infer the error type: the
signature named it, the expansion dropped it, and the handler failed to
compile with E0282.

Ascribe the block with the type the signature declares, the way the page
form already did, so a body infers exactly as it does in a plain
function.

* fix: record the page a batch handler was called with

The dispatcher wrote a harness record only on the single-message path, so
a batch subscription was invisible to every subscriber assertion:
`assert_called_once` saw zero calls, and `received_raw` returned nothing
however many pages had arrived.

Record the page where every batch form already funnels through, the
settle choke point that knows both the deliveries and the settlements
they got, reaching the harness through the task-local scope the slot
recorder already rides. A record now carries the deliveries of one
handler CALL: exactly one for a single-message handler, one per element
for a page.

The assertions keep their meaning on the single path and gain a defined
one for pages: `assert_called_once` is one page whatever its size,
`received_raw` lists its elements, `settled` covers every element... (continued)

119 of 130 new or added lines in 10 files covered. (91.54%)

2 existing lines in 1 file now uncovered.

12138 of 12446 relevant lines covered (97.53%)

275.98 hits per line

Uncovered Changes

Lines Coverage ∆ File
7
97.02
-1.42% src/runtime/dispatch.rs
3
95.19
-1.1% src/testing/assertions.rs
1
97.74
0.24% src/testing/coordinator.rs

Coverage Regressions

Lines Coverage ∆ File
2
95.19
-1.1% src/testing/assertions.rs
Jobs
ID Job ID Ran Files Coverage
1 33710932143.1 03 Sep 2026 03:22AM UTC 100
97.53
GitHub Action Run
Source Files on build 33710932143
  • Tree
  • List 100
  • Changed 21
  • Source Changed 21
  • Coverage Changed 20
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #33710932143
  • 413f38d6 on github
  • Prev Build on main (#33705318769)
  • 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