Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PyPI badges often don't display #1653

Closed
shaypal5 opened this issue Apr 18, 2018 · 4 comments
Closed

PyPI badges often don't display #1653

shaypal5 opened this issue Apr 18, 2018 · 4 comments

Comments

@shaypal5
Copy link

Hey!

This a great service which I use for several of my packages.

However, in the last few the PyPI badges (for package version and supported Python versions) on my repos / PyPI packages pages often won't display. Sometimes a hard refresh helps, but usually it does not. The badges will come back if I look later in the day, but then they might disappear again.

I use the exact same method all the major repos use; and usually, when I can't see my PyPI badges I can't see theirs as well. Also, note that this is not the case with travis or codecove badges.

I'd love to understand how this can be solved. Also, if this is the wrong repo to open this issue in then I apologise, and would appreciate you pointing me in the right direction.

Cheers,
Shay

Here's a screenshot:
image

@chris48s
Copy link
Member

Suspect this is a duplicate of #1568

The other possibility is that if you've only started seeing this in the last few days and it only happens on the PyPI badges, it might be related to PyPI's recent migration to warehouse.

Suspect it is #1568 though

@RedSparr0w
Copy link
Member

I think @chris48s is correct as the badge is not loading at all rather than displaying an error message.
But going to leave this open for now incase this is related to the migration to warehouse.

Will keep track of the PyPI badges here for the next few days,
Will close if results look like this is a duplicate of #1568,
Otherwise this should hopefully not be a problem when #1648 goes live.

@shaypal5
Copy link
Author

Cool! Thank you for your time. :)

@RedSparr0w
Copy link
Member

No worries, Looks like it is the same problem as #1568 (99.97% correct responses) so going to close for now.
Hopefully we can get it sorted out soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants