Exact

Exact Union RegExp

Repository files (latest commit first)

Filename	Latest commit message	Latest commit date
Transaction Science d1b4bd0c01 joule-contrib: the SRT link tests again require every recovered packet taken before its delivery time; a recovery is pinned to when its gap was found, and a held packet keeps its margin at the link's end ... The loss test's last assertion had become `margin_min <= window`, which the receiver's clamp and the verifier's rule already guarantee: the end-to-end test checked no timing at all. It again asserts `margin_min > 0`, the only check across the real link (the sender's NAK handling, the connection's loop, the proxy) that every recovered packet was taken before its own delivery time. The ordering defect fixed in 066d82edf delivered a retransmission taken after its drop point as recovered with a margin of 0, with nothing dropped and every payload in order: exactly CI's failure at the old line 148. That failure fits the defect, a busy runner's lag, or both (with the starved timer fixed in 76264fae6 lengthening the first window's recoveries); the part was not printed, so it cannot be told which, and the earlier commit's "the bound measured the host, not the protocol" says more than the evidence does. The window stays a second, which absorbs the receiving task's lag seen under load. The recovery time stays unbounded there: it counts from when the gap was found, not from the packet's timestamp (live-contribution §6.3). What pins where a recovery counts from is now the receivers' unit tests: they find each gap at 20 ms rather than at the clock's origin, so a recovery counted from 0, or from the last tick, fails them. The loss test also asserts what does not depend on the host: every recovered packet came back as a retransmission (the proxy neither delays nor reorders), and every NAK names a sequence number. The caller that receives takes its time base from the listener's CONCLUSION reply, wiring no unit test reaches. Its lossy test now checks its window, its account (nothing dropped, a margin above 0), and a new test holds one packet for the caller's window as the listener's test does. A recovered packet still held when a link ends, SRT or RIST, was recorded with a margin of 0, which reads as one taken after its delivery time; it now keeps the time it arrived before that. A unit test for each. A receiver unit test feeds ACKACKs through the connection's loop on a clock of its own and pins the periodic NAK after the RTT is measured: every (RTT + 4 x RTTVar) / 2, 30 ms at a 60 ms round trip, and the 20 ms floor at 1 ms, until the drop point. The comment on the timer test now says the periodic NAK counts from the link's start; the NAK sent at once does not restart it. live-contribution: §5.3 and §6.8 said a recovered packet arrives on time, which under §6.1 does not hold for SRT: one taken after its own delivery time, before the first packet after it that has arrived is due, is delivered late, counted recovered with a margin of 0, and the record does not count how many. They now say so, and §6.8 that the record does not say when a packet delivered at the first try was taken. §4.1 and §6.1 name the drop point as the delivery time of the first packet after it that has arrived, since the next one can itself be missing. The CHANGELOG entry says the same. Co-Authored-By: Claude Opus 5.5 <[email protected]>		2026-11-04 08:13:40 -05:00
..
crates	joule-contrib: the SRT link tests again require every recovered packet taken before its delivery time; a recovery is pinned to when its gap was found, and a held packet keeps its margin at the link's end	2026-11-04 08:13:40 -05:00
vendor/wtransport	vendored wtransport: the close_session doc says when the session's result is set	2026-10-20 08:32:05 -04:00
Cargo.lock	joule-moq-relay: a fan-out holds up no other track, and each core has its own socket	2026-11-02 19:05:27 -05:00
Cargo.toml	joule-contrib: SRT and RIST contribution over UDP with retransmission	2026-10-25 22:31:09 -04:00