Coverage hardening, disconnect fixes, and VPS regression round - #177
Merged
Conversation
ZingerLittleBee
force-pushed
the
coverage-hardening-and-regression-fixes
branch
from
August 12, 2026 16:08
23bdcae to
30d71bb
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Three related workstreams, verified together by a full workspace coverage run (93.18% line / 92.33% region, all tests green) and a 3-round manual regression on a real Linux VPS.
Test coverage hardening (43 new tests)
mark_failedverification; scheduler cron retry loop and dispatch-failure exit codes; OAuth callback nonce path; cleanup cascade pruning; geoip download guardhttp_keyword: extracted pureparse_config/evaluatefromcheck()and rewrote ~26 replica tests to call the real production code (verified by mutation: breaking the logic now fails 12/11/1 tests that previously stayed green)Behavior fixes
Reporter::run()crypto.randomUUIDinsecure-context crash (found on VPS): plain-HTTP origins crashed the /servers page and silently broke dashboard Add Widget; added agetRandomValues-based fallbackresolve_scopenow honors the documented semanticVPS regression round
Fresh install of this branch on a real Debian 13 VPS (first-run onboarding → enrollment → agent claim), 3 testloop rounds across auth, dashboards, terminal, file manager, docker, monitors, ping, scheduled commands, alerts, security events, member RBAC, audit log, and the public status page. Final verdict: pass. Report:
.testloop/reports/2026-08-12-broad-vps-regression.md.Also includes the ServerBee promo video project under
videos/.Test plan
cargo llvm-cov --workspace --all-features— all suites green, 93.18% line coveragecargo clippy --workspace --benches --tests --examples --all-features— no warningsbun run test(826 tests),bun run typecheck, ultracite lint — green