The Github repo stars and forks counters doesn't shows up.
I expect them to show up like in the demo and documentation page http://squidfunk.github.io/mkdocs-material/

Instead it comes up with the "vendor/package" slug name only, without nothing under it. Also no JS errors in the console or in the mkdocs serve log in my console once I run it to develop from http://127.0.0.1:8000/

If I "inspect elements" and compare with the markup from the demo, I see this part is completely missing on my end.
<ul class="md-source__facts"
<li class="md-source__fact">621 Stars</li>
<li class="md-source__fact">170 Forks</li>
</ul>
pip install mkdocs-materialtheme: 'material'mkdocs servehttp://127.0.0.1:8000/ in the browserPython 2.7.10mkdocs, version 0.16.3Version: 1.7.5``` yaml
site_name: Starter WordPress Theme
repo_url: https://github.com/vendorname/starter-wp-theme
repo_name: vendorname/starter-wp-theme
edit_uri: edit/master/docs
site_author: Elvis Morales
site_description: A WordPress starter theme.
theme: material
pages:
copyright: 'Copyright © 2016 - 2017 Elvis Morales'
extra:
feature:
tabs: false
palette:
primary: red
accent: red
social:
- type: globe
link: https://companyname.com
- type: github-alt
link: https://github.com/companyname
- type: twitter
link: https://twitter.com/companyname
- type: linkedin
link: https://linkedin.com/companyname
markdown_extensions:
Is there some error to see in the network inspector? It seems that the request failed.
Also try to delete the cooke which caches results and is called: ${HASH}.cache-sources
@squidfunk I tried deleting the cookie ${HASH}.cache-source but same result. Also any error comes up in the network inspector, all requests are 200 OK.

This is the repo I'm putting this documentation together: https://github.com/forumone/gesso-wp
Any other thoughts why stars and forks numbers are failing to show up?
Nope, I cannot reproduce this, it's perfectly working.
I managed to reproduce it. There a reonly 30 repos returned from the GitHub API, so we need to paginate if the repo is not found and there are more than 30.
Yes that should be it, seems like for user accounts/organizations that has more than 30 repos, if not found the repository on the first response to api.github.com/users/orgname, then it should paginate for more until it find's it.
Glad you were able to reproduce it!
Rather tricky figuring out how to do an endless Promise chain, but managed to implement it in #429. Will release 1.8.1 shortly.
Just released 1.8.1, please re-open in case of problems.
I am seeing this issue again in version 2.7.3.
Please re-open the issue and provide more information when you're seeing this. Ideally a reproducible scenario. Thanks!
This is something that just happened to my repo, you can get rate limited by GH
GitHub requests were refactored in v5, so running into the rate limit should be rather unlikely.
Thank you!
Just to leave it here, my issue was that in a VPN most of my team was using the same IP address, so we reached the limit quickly. Loading the portal without VPN was working fine.