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

stacklok / toolhive / 30337605521
70%

Build:
DEFAULT BRANCH: main
Ran 28 Jul 2026 07:21AM UTC
Jobs 1
Files 844
Run time 2min
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

28 Jul 2026 07:13AM UTC coverage: 69.723% (+0.02%) from 69.708%
30337605521

push

github

web-flow
Add Redis-backed mixed-era vMCP e2e coverage (#6056)

PR #5981 removed two specs from the single-server dual-era k8s test
because they cannot work on one MCPServer: a single go-sdk backend
cannot be both stateless (for Modern per-request clients) and
session-issuing (for Legacy clients) at once. PR #6006 then landed the
vMCP cross-generation bridge, but neither of its tiers configures
Redis, so the session-store dimension of the bridge stayed unproven:
nothing exercised a Legacy client's session metadata living in Redis
while a Modern backend shared the group, and nothing exercised what a
Redis outage does to a mixed-era deployment.

Add an operator-tier spec over a mixed Legacy+Modern yardstick backend
set behind one vMCP with Redis session storage. It asserts the
asymmetry a single-server test could not express: a Redis outage 503s
the Legacy session path while the Modern stateless path keeps serving,
because vMCP classifies client era in middleware ahead of the SDK
session layer and dispatchModern never reads the session store.

Coverage: concurrent Legacy-session and Modern-stateless traffic with
no cross-delivery; Redis holding a backend-session key for the Legacy
backend only; and outage to 503 to recovery, with the wiped pre-outage
session correctly reported terminated.

Two constraints are documented in the file because both cost a debug
cycle. yardstick's echo tool schema-validates input against
^[a-zA-Z0-9]+$ and reports a violation as a successful result with
isError set, so resp.Error being nil is not proof a call worked. And a
go-sdk/mcpcompat client cannot open a Legacy session against a
Modern-dispatch-enabled vMCP at all: Connect is Modern-first, so
server/discover routes to dispatchModern, the client negotiates Modern,
gets no session, and then 404s on subscriptions/listen. This spec
therefore drives all traffic through the raw client, which pins the era
per request.

Runs at one replica rather than the multiple replicas the issue
sug... (continued)

81052 of 116248 relevant lines covered (69.72%)

98.59 hits per line

Coverage Regressions

Lines Coverage ∆ File
6
76.15
-5.5% pkg/secrets/keyring/keyctl_linux.go
3
96.63
-0.44% pkg/authz/authorizers/cedar/core.go
3
80.56
-0.7% pkg/transport/proxy/httpsse/http_proxy.go
2
93.94
-6.06% pkg/foreach/foreach.go
2
88.67
-0.23% pkg/transport/proxy/transparent/transparent_proxy.go
1
62.17
0.69% pkg/workloads/manager.go
Jobs
ID Job ID Ran Files Coverage
1 30337605521.1 28 Jul 2026 07:21AM UTC 844
69.72
GitHub Action Run
Source Files on build 30337605521
  • Tree
  • List 844
  • Changed 13
  • Source Changed 0
  • Coverage Changed 13
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #30337605521
  • b5a48512 on github
  • Prev Build on main (#30336616955)
  • Next Build on main (#30337625765)
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