powersemmi / ruststream / 33994082569

97%

Build Type

push

github

Committed by web-flow

Commit Message

Fix the findings the 0.7 broker adaptation left in the core (#295)

* Warn when a slot mount never reaches .build()

A registration carrying `Out` slots is not complete until every slot is
bound, so its guard commits through a call rather than through the drop
that finishes a reply-only one. One guard type served both, which left
`#[must_use]` unavailable: the attribute would have fired on every correct
reply-only mount. A forgotten `.build()` therefore compiled, passed a test
suite, and only surfaced as a panic when the service started.

The two terminals now have two types, so the slot-carrying one carries
`#[must_use]` and says what to do. Rust has no linear types, so a dropped
value cannot be a hard error, but a warning lands on the mount site and is
an error wherever warnings are denied. The drop-time panic stays as the
backstop under it.

Splitting the guard also drops the terminal type parameter, and with it the
`ScopeTerminal` bound every step repeated: the compile errors of the steps
now name the chain's own commit bound instead, which the refreshed
snapshots show.

* Carry a publisher's base headers onto the replies it sends

`Publisher::base_headers` is how a broker publisher contributes an argument
it holds for a run of messages - a partition key, a tenant, a delivery
option the transport expresses as a header. The publish builder laid that
base down, but a reply never passes the builder: the reply path assembled
its own outgoing message from an empty map, so a broker that wired an
option this way saw it silently dropped on everything a `publish("dest")`
handler answered with.

The reply path now starts from the same base, in the same order the builder
uses: the handle's headers first, the reply's own transforms over them. A
publisher with no base yields the empty map replies always started from, so
nothing is cloned on the path every broker publisher takes today. The slot
path already went through the builder and needed nothing; a test pi... (continued)

Coverage Stats

245 of 245 new or added lines in 7 files covered. (100.0%)

10 existing lines in 3 files now uncovered.

12155 of 12470 relevant lines covered (97.47%)

181.58 hits per line