You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like our repo is now too large for pre-commit.ci, as we are hitting the 30s timeout for cloning the repo on that service. As we expect it to only get larger as more analysis results are included, I fear that this is a problem that is not going to get any better unless there are changes I would not expect from a free service (related discussion: pre-commit-ci/issues#183)
Since we are not using the autofix feature here, I expect we should be just fine with the GitHub Action, so I will make an action to use that.
> @jashapiro can you have a look at what's up with this pre-commit action (I don't have permissions)?This PR is otherwise approved.
We seem to be timing out on cloning the repo. This could be a more significant problem than just this PR: There is a time limit of 30s for cloning and we seem to be taking ~25 seconds in other PRs, meaning we are probably quite close to the repo size limit for the service.
It seems like our repo is now too large for pre-commit.ci, as we are hitting the 30s timeout for cloning the repo on that service. As we expect it to only get larger as more analysis results are included, I fear that this is a problem that is not going to get any better unless there are changes I would not expect from a free service (related discussion: pre-commit-ci/issues#183)
Since we are not using the autofix feature here, I expect we should be just fine with the GitHub Action, so I will make an action to use that.
We seem to be timing out on cloning the repo. This could be a more significant problem than just this PR: There is a time limit of 30s for cloning and we seem to be taking ~25 seconds in other PRs, meaning we are probably quite close to the repo size limit for the service.
Originally posted by @jashapiro in #813 (comment)
The text was updated successfully, but these errors were encountered: