Exceeding Github API limit
complete
G
Gamboge Muskox
I'm getting an error that I exceeded the GitHub rate limit and I can not use the Seqera Platform for some time. I haven't provided my GitHub credentials to the workspace and I understand that lowers the rate limit.
However, I don't think I used the API that much: in general it appears Tower sends many requests in the background which leads to exceeding the limit very quickly.
I understand that this might be necessary but I thought to highlight that this might be optimized to reduce the number of requests and so not exceed the limit quickly (such as a cache). I don't recall having the issue after providing my Github token.
Drew DiPalma
updated the status to
complete
We now support Github app access within Seqera Platform which comes with higher API limits.
https://docs.seqera.io/platform-enterprise/git/overview#github-app
Rob Newman
Merged in a post:
"Repository base URL" field in Github credentials is confusing
A
Alloy Hare
When trying to add a pipeline for a large public
nf-core
workflow (sarek
), I kept getting API rate limit exceeded
messages. It was strange, because I pull Github workflows all the time, and I haven't had any problems like this lately.I think the problem is that I put our private Github organization into the
Repository base URL
field in the credential. And from what I can gather from the Seqera Platform documentation, maybe in this case it won't use that credential because it's overly specific.The setup and usage of Github credentials is pretty opaque in the Seqera Platform. The description of
base URL
on the Add credential
screen is not very helpful, and when you do run into a rate limit either by the Seqera Platform web interface or the tw
CLI, it doesn't tell you anything useful about which credential was used and might have an inadequate quota. The Seqera platform manual description is definitely better, but even that could be clearer.The Github API rate limit is a complete roadblock. It can be very frustrating when you can't even add the
Hello World
workflow, and the interface is not helpful in telling you what's wrong.Rob Newman
Hi Gamboge Muskox: Thanks for your feature request. We're looking at various ways to improve the user experience with respect to hitting Github API rate limits. This includes optimization of the number of requests to the service and also investigating the feasibility of a Github app. You will continue to receive automated updates as this feature request changes status.
Rob Newman
updated the status to
acknowledged