Repository navigation
Conversation
GitHub serves README images through its camo proxy, which gives up after about 4 seconds. Zenodo's DOI badge endpoint takes 7 to 18 seconds, so the badge failed on every page load. Replace it with a static shields.io badge that shows the same DOI and needs no upstream lookup. The shields.io conda badge only cached for 5 minutes, and a cold lookup against anaconda.org took over 6 seconds, so it broke intermittently. Cache it for a day with cacheSeconds=86400. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This branch has not been deployed
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.
Problem
The conda version and DOI badges at the top of the README showed as broken images on GitHub.
GitHub loads README images through its camo proxy, which returns a 504 after about 4 seconds.
zenodo.org/badge/DOI/...svgtook 7 to 18 seconds when fetched directly. Through camo it returned a 504 at about 4.2 s on every attempt.conda/vnfor only 5 minutes. A cold lookup against anaconda.org took 6.6 s, so the badge broke whenever the cache had expired. It loaded fine when the cache was warm, which is why the failure was intermittent.Fix
img.shields.io/badge/DOI-10.5281%2Fzenodo.23237635-blue. It shows the same text in the same colour and needs no upstream lookup. The link still goes to the concept DOI.?cacheSeconds=86400so shields.io and GitHub's CDN keep the badge for a day. The anaconda.org lookup now runs about once a day instead of every 5 minutes. The trade-off is that the version shown can lag a new release by up to a day.Verification
I rendered both new lines through GitHub's markdown API and fetched the resulting camo URLs three times each. All six requests returned 200
image/svg+xmlin under a second. The DOI badge's title readsDOI: 10.5281/zenodo.23237635.🤖 Generated with Claude Code