Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Github limit reached
See original GitHub issueI don’t why everytime I merge this damned bob.ip.flandmark it breaks the master while it is green in its pull request but here we go: https://travis-ci.org/conda-forge/staged-recipes/jobs/143516959
There is also an empty repository here: https://github.com/conda-forge/bob.ip.flandmark-feedstock
Sorry for the inconvenience but could you guys fix it please?
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Rate limits for GitHub Apps
GitHub Apps that are installed on an organization within an enterprise on GitHub.com are subject to a limit of 15,000 requests per hour...
Read more >How to get the most out of GitHub API rate limits - Endor Labs
That rate limit can be easily reached in just a few minutes by calling the API to list basic information from a medium...
Read more >Overcoming GitHub Storage Limits - Rewind Backups
Individual files added via the browser IDE are restricted to a file size of 25 MB, while those added via the command line...
Read more >Continuously hitting the GitHub secondary rate limit even after ...
Looks like there is not an issue in your code. I was just surfing from my browser and was using github search bar,...
Read more >How to test Github Rate limiting - Snyk Support
You can test whether your API token is being rate limited by Github by running the following command where $GITHUB_TOKEN is either an...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I re-ran the travis job and the repo is now populated.
So, the previous problem may have been the GitHub API rate limit. However, the problem shown in this last build is a different problem and is due the Travis CI API being a bit flaky. This is evidenced by this line. We are tracking these problems in a different issue ( https://github.com/conda-forge/staged-recipes/issues/923 ). As a result, am going to close this one out. Hope that is ok.