chore: remove cmd/mountsync_repro (HS256-only, unused)#61
Merged
khaliqgant merged 1 commit intomainfrom Apr 24, 2026
Merged
Conversation
One-off repro binary from #13 (FUSE mount PR) that minted HS256 bearer tokens via a local `mustJWT` helper and a shared `"dev-secret"`. After relayfile#60 retired the HS256 verifier, this binary no longer works against the server (any token it mints now 401s with "unsupported jwt algorithm"). Not imported by anything (`grep -rn mountsync_repro` → no references), not on any CI path, not deployed anywhere. Cheapest fix is just deleting it. If a future regression needs a repro harness, regenerate one that signs RS256 tokens against a local JWKS. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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
2 participants
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
One-off repro binary from #13 (FUSE mount PR) that minted HS256 bearer tokens via a local
mustJWThelper and a shared"dev-secret". After #60 retired the HS256 verifier, this binary no longer works against the server — any token it mints now 401s with"unsupported jwt algorithm".Why just delete
grep -rn mountsync_repro→ zero hits outside the dir itself)Test plan
go build ./...clean after deletiongrep -rn mountsync_reproreturns nothingIf a future regression needs a repro harness, regenerate one that signs RS256 tokens against a local JWKS.