Repository navigation
fix(github): keep a malformed mint answer out of reports - #526
Merged
Merged
Conversation
A JSON.parse error quotes the start of the body it rejects. For an installation token answer that start holds the token, and the message reached the app-token-unavailable report.
The test renewed the token on its first read, so the parallel reads never met a 401.
A failed or misconfigured mint moves every read to the fallback, so its quota paces the sync then. The runbook said never.
This was referenced Oct 7, 2026
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.
🔗 Linked issue
Related to #525
❓ Type of change
📚 Description
Review findings on #525, which merged before these commits reached it.
JSON.parseerror that quotes the start of the body, such as"{"token":ghs_SECRET".... That message reached theapp-token-unavailablereport and its wide event. The mint now throws a fixed message instead.createArtifactGithubSourcecomment said nothing else spends the App's bucket; the registry does now.