Repository navigation
rigforge stratum-auth needs a runner-managed authenticated fixture (#559) #562
Description
Linked task: rigforge#559, draft PR rigforge#561.
Job 2019@3a73ea59d2d5a7576e1a0602b7d8521e788647b9 requested tier4-e2e phases access-tokens,stratum-auth and completed with conclusion success, exit 0, verified baseline and restored rig. The full log and both retained phase artifacts were read. Access-token assertions ran successfully, but e2e-pithead-stratum-auth.log reports that the stratum password was not supplied, then reports zero assertions and zero failures. No stratum acceptance/rejection or rotation gate executed.
Expected: an approved runner-managed authenticated Stratum fixture supplies the private password when this phase is requested, so right-password mining, wrong-password rejection and password recovery all execute while the runner preserves payout identity and restores the fixture. The documented password knob is runner-local and cannot be supplied by a submission. Please provide the fixture/configuration or the supported narrow submission that executes those assertions; no worker will change the bench or install credentials by hand.
This prevents completing the touched stratum validation for rigforge#559. Its stdin/argument-inspection regression already exercises special-character passwords and rotation without hardware; a live authenticated-stratum proof is still missing. Resume when the runner can execute the phase with its required private input. No credentials or topology are included here.
Moved from p2pool-starter-stack/bench-ci#1106 by the runner's triage: The requested change is to rigforge’s own Stratum validation harness and assertions; bench-ci supplies the private fixture, but no runner or tier change is requested. (recreated: GitHub cannot transfer out of a private repo).
Activity
pithead-developer commentedon Oct 2, 2026
Filed privately (rigforge-562.md); it needs an answer there, then remove the
questionlabel.pithead-developer commentedon Oct 2, 2026
Moved into v2 - appliance because #559 depends on this issue in the release dependency chain.
pithead-developer commentedon Oct 2, 2026
Blocked on authenticated fixture provisioning
bench-ci#1127 prevents obtaining the required passing current-head Stratum proof. Job
2039@ec197357f80e436d17bc30a5b0ef6a14ff630860completed with failure: the full log and retained artifact show the intended sanitized missing-input diagnostic and harness exit 2, with baseline verification and rig restoration successful. No authentication assertions ran, so this is refusal evidence, not a passing tier-4 result.Draft PR #567 contains the completed harness correction, mandatory regression and corrected documentation; targeted tests and baseline mutation checks passed their expected outcomes, and verifier/security review is clean. The authorized fixture provisioning/recovery owner must make the approved private input available through the managed nonproduction path. Then a fresh narrow current-head job must prove authenticated acceptance, rejection and recovery, and its full evidence must be reviewed before merge. RigForge will neither invent a fixture interface nor install credentials. The separate #559 / PR #561 proof and bench-ci#1107 reporting defect retain their owners.
pithead-developer commentedon Oct 2, 2026
Blocked on p2pool-starter-stack/bench-ci#1127. PR #567’s implementation, regression tests, documentation and author-side reviews are complete. Job 2039 confirmed the intended missing-input failure and verified restoration, but supplied no passing authentication proof; its full log, artifact and exact evidence are recorded in the PR. Bench-ci#1127’s fixture owner must provide the approved private input, then a fresh current-head Stratum job must pass acceptance, rejection and recovery; blocker comments are posted on the issue and PR.
The runner resumes this issue when that one closes.
pithead-developer commentedon Oct 3, 2026
Blocked on fixture deployment
bench-ci#1127 closed through merged bench-ci#1140, but fleet deployment records do not yet include its merge commit. bench-ci#1141,
Deploy pending: 120c5053cc63a8361b14904a9aa5481444f9d906, is the new blocker. A job before deployment cannot prove the new authenticated fixture.Draft PR #567's harness fix, regression, documentation and author-side reviews are complete; all eight GitHub checks pass at
ec197357f80e436d17bc30a5b0ef6a14ff630860. The earlier job2039@ec197357f80e436d17bc30a5b0ef6a14ff630860proves missing-input refusal and verified restoration, but remains a failure without authentication coverage. The managed self-update process must deploy the fixture; when deployment is proved, resume with a fresh narrow current-head Stratum job and verify acceptance, rejection, recovery and restoration from complete logs and artifacts. No bench or rig was changed manually.6 remaining items
VijitSingh97 commentedon Oct 3, 2026
Owner: moved to maintenance & gates with its remaining dependency bench-ci#1159 (stratum-auth routing), which the operator ruled into that lane at 09:16Z. This is RigForge test coverage and changes nothing the 2.0.0 image bakes, so it is outside the 2.0.0 scope rule. bench-ci#1127's fixture is deployed (#1140). The proof resumes once #1159 routes stratum-auth jobs to a bench that owns its stratum.
pithead-developer commentedon Oct 3, 2026
Moved into v2 - appliance because #559 depends on this issue in the release dependency chain.
pithead-developer commentedon Oct 3, 2026
Blocked on routing-fix deployment
Bench-ci#1159 closed through merged bench-ci#1165, but current fleet deployment records do not yet include that merge. bench-ci#1166,
Deploy pending: 9b59fef66b3e8b98b025485158c176b7c9a8186c, is the new blocker. Submitting before deployment cannot prove routing to a ready authenticated fixture owner.Draft PR #567's code, targeted regression, documentation and repeated author-side reviews are complete; all eight GitHub checks pass at
5967a9febc5cc8641c5bc0b45d43cc611ff09c62. The earlier job2057@5967a9febc5cc8641c5bc0b45d43cc611ff09c62is an environment error with no authentication assertions, although restoration succeeded. The managed self-update process must deploy the routing fix; then resume with a fresh narrow current-head Stratum job and verify eligible-owner dispatch, acceptance, rejection, recovery and restoration from full evidence. No manual host/configuration action or blind retry was performed.pithead-developer commentedon Oct 3, 2026
Blocked on p2pool-starter-stack/bench-ci#1166. PR #567’s implementation, regression, documentation and repeated reviews are complete; all eight current-head GitHub checks pass. The routing fix merged but is not deployed, so bench-ci#1166 must close before a fresh Stratum job can prove eligible dispatch, authentication and restoration. Updated blocker comments are posted on the issue and PR.
The runner resumes this issue when that one closes.
pithead-developer commentedon Oct 3, 2026
Merged in #567.