-
Notifications
You must be signed in to change notification settings - Fork 0
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
Everything is an NaN now #1
Comments
Interesting... I just tried it locally, and I get a non I'll look into this more and get back to you. |
Something's fishy in heroku. |
Sadly still not working |
+1. Would love to see this fixed. I use this in all my projects. I would gladly help solve this issue, but i think it's a problem with the server on heroku.com. I checked your code locally and works fine. Probably the server just needs to be restarted, maybe it crashed Or maybe is the fact that you don't send any header related to cache control as a response. I think if you send this headers everything will start working again:
you can see this github/markup#224 for more information on that. |
i updated my last comment. Can you please check that ? I think will solve this problem. Thank you very much |
I apologize for my negligence on this issue. This should be fixed. Thanks @bogdanRada! |
This still seems to be an issue... It looks like the problem lies with Heroku. I am using a |
Yeah. I think i know why. Currently HTTP protocol on shields.io redirects to HTTPS. Can you try changing the url to HTTPS? I forgot about that |
The error happens because HTTP ons shields.io returns now Content-type text/html. |
@bogdanRada switched to HTTPS -- still |
Thats strange :( |
I suspect why is happening. I had same issue on my repository http://github.com/bogdanRada/ruby-gem-downloads-badge. All my badges died when shields.io was switched on cloudflare which uses SNI for SSL connections. Maybe using curl instead of file_get_contents will fix the problem. |
Also i think you should see this discussion. It seems github introduces rate limiting. badges/shields#529 and i think now your application will have to do autenticated requests to their API in order to work properly |
I think this will be solved by this pull request: #3 . Hope it helps :) |
Closed by #3. |
No description provided.
The text was updated successfully, but these errors were encountered: