-
Notifications
You must be signed in to change notification settings - Fork 155
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
failed to push some refs #100
Comments
Hmm, I have not seen that kind of error before. The docs say that the Also, by the way, I recommend using selective sync and disabling sync for the directory where you are placing repos, e.g. |
No, What can I do to help identify the problem?
Thanks! Bit this recommendation isn't related to the issue? |
Yeah, the recommendation is probably not related. I'm not entirely sure what is causing this. Do you get the same error if you try pushing again? Does it seem to be deterministic (i.e. gives an error when pushing the same file), or does it fail at different points? If you delete the directory in Dropbox (or alternatively, change the remote to point somewhere else, e.g. What platform are you on? (OS / Python version) Do you have large files in this repo (say, > 20 MB)? |
I've made several experiments. First conclusion: It depends on arbitrary factor. Push to
Pushing to
Then I've deleted repository folder from Dropbox and then push it again and everything works fine! P.S. Repository consists of quite many files (excluding
The biggest file has size of |
Okay, so everything is working now? Hard to tell how it got into that state that caused the Yes, the repository consists of many files. git-remote-dropbox keeps all objects loose (supporting packfiles while having client-side concurrency control seemed tricky; it should be possible, but it's not currently implemented). So individual objects are zlib-compressed but there's no delta compression, so repositories take up a decent amount of space. |
It seems that ok, but definitely not stable :( Thanks for your comments! |
Do you still have a copy of the folder on Dropbox that was being problematic? |
I've tested It occasionally fails. It can be ok for location and next time not ok for the same location |
git-remote-dropbox doesn't have great logging (and I'm not even sure what log output would be useful beyond the Dropbox API error). It would be helpful for debugging if I could repro this on my machine. I wonder if it has anything to do with the repository contents? Does the same issue happen if you push other repos? (E.g. clone a random github repo, like git-remote-dropbox, and then push it to Dropbox). Or is it just with your particular repo? |
I'm trying to push existing repository to fresh Dropbox repository via
git-remote-dropbox
.When I try to do it I catch an error:
There isn't anything in the folder
I've configured remote as follows:
P.S.
The text was updated successfully, but these errors were encountered: