'git push hangs after Total line
My git push is hanging after appearing to complete the push. I am going git push
Counting objects: 51, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (47/47), done.
Writing objects: 100% (47/47), 27.64 MiB | 6.47 MiB/s, done.
Total 47 (delta 4), reused 0 (delta 0)
It hangs here and I have to control-c to get back to command line. I have made several commits in the past with this project with no issues. I have tried other repos on my machine and they work fine. What is going on here?
Solution 1:[1]
This turned out to be no problem at all. I simply had to wait until the upload was complete. I had added several large files and there is not a progress indicator. Maybe someone else will find this helpful.
Solution 2:[2]
https://git-scm.com/docs/git-config#Documentation/git-config.txt-httppostBuffer
http.postBuffer
Maximum size in bytes of the buffer used by smart HTTP transports when POSTing data to the remote system. For requests larger than this buffer size, HTTP/1.1 and Transfer-Encoding: chunked is used to avoid creating a massive pack file locally. Default is 1 MiB, which is sufficient for most requests.
Note that raising this limit is only effective for disabling chunked transfer encoding and therefore should be used only where the remote server or a proxy only supports HTTP/1.0 or is noncompliant with the HTTP standard. Raising this is not, in general, an effective solution for most push problems, but can increase memory consumption significantly since the entire buffer is allocated even for small pushes.
Resolution
Increase the Git buffer size to the largest individual file size of your repo
git config --global http.postBuffer 157286400
Refer to the resolution of Git push fails - client intended to send too large chunked body for ngnix reverse proxy configuration. Increase this parameter to the largest individual file size of your repo.
Bypass the outbound proxy as explained on Can't clone or pull due to a git outbound proxy
Solution 3:[3]
It can be (as the accepted answer suggests) just a moment to wait, but in the majority of cases it is linked to permissions on the remote. While mostly a non-issue on public git services such as GitHub, Gitlab or Bitbucket, self-hosted remotes might have a special user, or a group for access.
And on new bare repositories it doesn't suffice to change the folder,
but instead needs to be recursive because of .git-Folder inside.
Solution 4:[4]
It only worked for me in the case when I did
git push -u origin main, when I just simply used git push for bit bucket, it did not push through.
Solution 5:[5]
Waiting until the upload finished doesn't work for me. I pushed not very big file, but waited long enough, still hanged.
What helped for me is updating from msysgit 1.9.5 to git-for-windows 2.6.2.
Solution 6:[6]
Permissions can also be cause of this in the case of a bare repo on a remote machine.
Solution 7:[7]
Just wanted to add this in case it helps anyone. I had the same problem, and the issue was that the git user didn't have permission to write to the files, only to read from them.
Solution 8:[8]
The problem is that the upload file is big.
Either you wait it out or go to your project folder and delete all the libraries which you could find in the target folder if using maven. Then do the push and it will happen quickly.
Anyways, the library folders need not be stored in git, it's just a waste of git space unless and until they are not available in the maven repositories and you really need to store them
Solution 9:[9]
This issue can be caused by issues with your SSH agent.
I recently ran into this issue because I changed my default shell from zsh to bash. I'd originally set up my ssh keys using zsh, and so they were not available by default to bash, using chsh -s /bin/bash.
To fix, you'll need to add your ssh key(s) to the SSH authentication agent using the same shell script (bash, sh, zsh, etc) you're using to perform your git commands:
eval `ssh-agent`
ssh-add ~/.ssh/some_key_rsa
You'll need to enter the passphrase for the key in order to add it. To store the passphrase to your user keychain so you don't need to enter it every time the key is used, add the key with the -K option to the ssh-add command.
ssh-add -K ~/.ssh/some_key_rsa
Note the uppercase K as using a lowercase is a different command option.
Solution 10:[10]
Adding another local commit and retrying push worked for me.
Solution 11:[11]
Use this command:
git remote add origin <url>
git push -f origin main
Solution 12:[12]
See if you have staged, but not committed changes. (git status)
If so, commit (or unstage) those and then try to push. Worked for me.
Solution 13:[13]
In my case it was caused by a problem with msysgit 1.9.5. Downgrading to msysgit 1.9.4 solved the problem.
Solution 14:[14]
In my case, the remote had a full disk. Removing some files on the remote promptly fixed the issue.
Solution 15:[15]
Checkout the user rights that git is using!
In my case I tried through ssh and the used system user was unable to write into the git bare repository...
Here is how you can debug your ssh connection
Solution 16:[16]
I ran into this same problem while pushing to GitHub. I found that a subset of the files being pushed wasn't being accepted.
I found this out by breaking my large commit into smaller commits (as described in this SO question: Break a previous commit into multiple commits), and then finding success with most of the smaller pieces.
The problem piece contains image files and I'm still sorting out which particular file (or files) triggers the problem.
Solution 17:[17]
I wanted to second @Fabio's comment to the original post - that solved it for me.
I'm running my own ad hoc local git server on Raspberry Pi. I forgot to chown the new bare repo, and pushing the first commit from a remote PC would just hang indefinitely.
This fixed it (running chown as root or with sudo):
cd /srv/git
chown git:git -R <repo_name>.git
Replacing <repo_name> with the name of your repo.
Solution 18:[18]
I had the same issue and it turns out I had an older version (that i deleted but had the same name) of the repo connected to Heroku. When i disconnected it, it completed the push.
Solution 19:[19]
In my case the Git hosting platform GitHub had issues with their servers so check your provider status too.
Solution 20:[20]
I got this recently when trying to push ~40 files around 2MB in total. git push --verbose revealed no errors, but would just hang after Total <...> was written to the terminal.
I reissued a new PAT via GitHub and the push went through as expected.
Solution 21:[21]
After waiting for two plus hours my git push was still stuck. So, I had to reset back before the commit where I had accidentally uploaded a 3.1mb photo (that I am guessing was the culprit for the freeze).
I found a much more amicable solution that @aroth shared above git config --global http.postBuffer 157286400 was the answer.
I just opened a new iTerm window ran the above command and then ran git push while the terminal in VSCode was still hung up. Then I ctrl c closed the terminal session in VSCode and I was back in business.
Thank you @aroth!
Solution 22:[22]
For me, I had installed Bitdefender and that was causing the issue. Uninstalled it and it was all fine
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow