Repository navigation
action: stop reporting user-side and transient errors - #603
Merged
Merged
Conversation
Most open TagBotErrorReports issues are not TagBot bugs. A 401 Bad credentials, a 429 rate limit, an HTML 400 page from GitHub's front end and an invalid `ssh` secret were all reported as internal failures. Now 401s are logged but not reported, 429s and HTML 400s are treated like 5xx errors, and an undecodable key raises Abort with a hint to use the private key. An Abort raised outside the per-version loop was silently swallowed since #548, so the job exited 0 with no message. It is now logged and the job exits 1. The registry PR cache read `pr.merged`, which is not in the list response and cost one extra request per PR. That request also failed with 422 on a PR with too many changed files. The cache now checks `merged_at`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 5, 2026
Closed
Closed
Closed
Automatic error report from soneraydin/MonteCarloJackknife.jl
JuliaRegistries/TagBotErrorReports#258
Closed
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
1 participant
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.
Claude: written with Claude Code (Opus 5.5).
Most open reports in JuliaRegistries/TagBotErrorReports are not TagBot bugs.
Now:
ssh/gpgkey raisesAbortwith a hint to use the private key, not the public one (Automatic error report from GiovineItalia/Compose.jl TagBotErrorReports#251, Automatic error report from diegozea/Iduna.jl TagBotErrorReports#256, Automatic error report from brandynlucca/AcousticScattering.jl TagBotErrorReports#262).Abort(e.g. "Registry ... is not accessible") is logged and exits 1. Since Stop reporting Abort errors to TagBotErrorReports; improve manual intervention #548 it was swallowed silently and the job passed.merged_atinstead ofmerged.mergedis not in the list response, so each PR cost an extra request, which also failed with 422 on a huge PR (Automatic error report from jheinen/GR.jl TagBotErrorReports#230).