floatdrop / moq-go / 31728506563
89%

DEFAULT BRANCH: draft-19
Ran
Jobs 1
Files 101
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
coverage: 88.66% (+0.1%) from 88.535%
31728506563

push

github

web-flow 
test(relay): cover the remaining upstream-FETCH failure and shape edges (#79)

Finishes the §9.4 stitching path started in #78, generalising its harness so
one topology drives every way an upstream can misbehave and every shape the
response has to carry across the hop.

Two distinct upstream timeouts, not one. Silence BEFORE the FETCH_OK expires
Session.Fetch itself; silence AFTER it leaves the relay waiting on a response
body stream that never arrives, from an upstream that looked entirely healthy
a moment earlier. Both must degrade to unknown rather than to an authoritative
gap. Both use the subscriber's FILL_TIMEOUT (§10.2.6), which the relay adopts
for the upstream leg — otherwise each would sit out defaultUpstreamFetchTimeout
for 5s.

Descending order with a capped upstream FETCH_OK falls back to marking the
WHOLE sub-range unknown: ascending can append one marker for just the uncovered
remainder, descending cannot, because that remainder precedes every object in
stream order and a leading marker cannot be followed by a same-group object
with a lower ID.

The §11.4.4.1 Datagram bit survives the hop. It records the Forwarding
Preference the object was PUBLISHED with, which a FETCH response must report
faithfully even though the response always travels on a stream.

Two findings from verifying rather than assuming. The first timeout test passed
while never reaching its intended branch — it was tripping an earlier timeout on
a different line, which is how the acked-but-silent case was found at all. And
the descending test passed with the branch deleted, because asserting a marker
EXISTS does not distinguish the two encodings: the ascending path emits one too.
What separates them is where it is anchored, so the test now pins the marker's
Location. Both are the fea80fc shape, and in both cases the coverage number was
no help — only the execution profile and mutation were.

pkg/relay 85.6% -> 86.0%; whole-suite holds at 90.1%.

9210 of 10388 relevant lines covered (88.66%)

2.01 hits per line

Coverage Regressions

Lines Coverage ∆ File
3
86.15
 -0.61% pkg/relay/handler_subscribe.go
2
60.53
 -5.26% pkg/relay/relay_namespace_watch.go
Jobs
ID Job ID Ran Files Coverage
1 31728506563.1 101
88.66
 GitHub Action Run
Source Files on build 31728506563