Keep getting error message 'Remote has disconnected'

Description

I upgraded the app to v.8, and every push to the remote end with a ‘remote has disconnected’ error

Version

GitHub Desktop version: [0.8.0]

OS version: [OSX 10.12.6]

Steps to Reproduce

Commit to local Click the push to origin

Expected behavior: [Push to finish loading to remote]

Actual behavior: [failure ]

Reproduces how often: [100%]

Logs

Additional Information

[TLGustav]

Thanks for clearing up Markus.

I “knew” this, but I wanted to ask because I considered this answer so unlikely.

I hate to state the obvious, but if you develop on media projects, 2Gb+ is standard, and binary files are a natural part of your IDE workflow.

With regards to Git not supporting 2GB, that leaves the following options for projects like this:

a) Git + another overlapping sync/cloud solution (high maintenance and messy - not happening) b) No versioning (nope - need that versioning) c) Another versioning software.

a) and b) are out of the question. Thus c) is the only viable option.

As a paying customer hoping to go full Git, I’m disappointed (and a bit shocked) that Git doesn’t support big projects out of the box, and I’m very annoyed that Git deals with the problem by just running for hours before crashing with an ambiguous message. This is pretty much the worst case scenario in terms of wasting users’ time, and also contributes to the confusion of thinking “I can get this to work… right?”.

It’s now almost two months since I wrote about this.

Gustav C. Tresselt TenkLabs AS [phone]

On Wed, Nov 1, 2017 at 1:29 PM, Markus Olsson [e-mail] wrote:

As has been said earlier in this thread we don’t believe this issue is related to GitHub Desktop. There is a hard limit of 2GB for pushes to GitHub.com which is enforced server-side and I suspect that’s what most of you are hitting here. Additionally there’s a soft limit https://help.github.com/articles/what-is-my-disk-quota/ or recommendation of keeping your repositories under 1Gb.

You can try breaking up your pushes into smaller chunks by pushing a subset of your commits but a better solution would be to use Git Large File Storage https://help.github.com/articles/about-git-large-file-storage/ which is designed to support these scenarios. See also Working With Large Files https://help.github.com/articles/working-with-large-files/ in our help documentation.

For people having problems pushing repositories well under the 2GB limit we recommend you contact our support team at github.com/support as they can help you debug any network interference that may be present in between you and our data centers.

We’ve experimented with reducing the upload size (just temporarily moving big files out), but no luck.

Note that due to the way Git stores files in perpetuity it’s not straightforward to reduce the size of a repository. Have a look at some of the tooling that’s available such as BFG https://rtyley.github.io/bfg-repo-cleaner/ but be aware that rewriting your repository should be done with utmost care and caution and with backups readily available.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/desktop/desktop/issues/2545#issuecomment-341093103, or mute the thread https://github.com/notifications/unsubscribe-auth/AciWv0aS7K10JI8k23mK1Mr0gqJMy_QLks5syGQ8gaJpZM4PCtCX .

[cilmon]

I had the same problem and I think it is related to the files size of your repository. I fixed the problem by running this on console in your git’s folder:

git config http.postBuffer 524288000

I hope it can help you