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
Fetch error after 256 repos #66
Comments
Hmm...this exact error message was already reported multiple times (#57, #58), and one user even had something similar where the error always occured after 250 repos: #33 Always with Bitbucket, but unfortunately I wasn't able to reproduce or fix it yet.
|
Solved... SCM fails when it hits a completely empty repo. Deleted the repo in Bitbucket and haved backed up all repos now, thank you. If I may recommend, perhaps clearer context in the log entries would help pinpoint the suspect repo causing the failure. The log entry where it fails does not indicate the repo that caused the failure, and I had assumed that prior log entries were representative of only a successful clone. Ideally, 'Cloning...' and 'Cloned/success' entries would provide better debug tracing imo. |
Do you remember how exactly you created that empty repo? I create a new empty repo in one of my workspaces and select the options NOT to create a readme/.gitignore: The result does look empty: But the backup works without errors:
|
Unfortunately no. The empty repo was likely created unintentionally by one of our staff many years ago. |
Running SCM backup on our bitbucket cloud instance fails before getting halfway through. Interestingly I noted that the number of successfully fetched repos is exactly 256.
Here's the error:
The text was updated successfully, but these errors were encountered: