github push command sometimes waits for hours

[adriatic]

Here is the example where after waiting for good 10 minutes, I interrupted the first push and send the same request again (as it helps sometimes). This time did not help and I am still waiting.

nik$ git push                           
Enumerating objects: 23, done.
Counting objects: 100% (23/23), done.
Delta compression using up to 6 threads
Compressing objects: 100% (11/11), done.
Writing objects: 100% (13/13), 6.23 MiB | 1.14 MiB/s, done.
Total 13 (delta 7), reused 0 (delta 0), pack-reused 0
^C
nik$ git push
Enumerating objects: 23, done.
Counting objects: 100% (23/23), done.
Delta compression using up to 6 threads
Compressing objects: 100% (11/11), done.
Writing objects: 100% (13/13), 6.23 MiB | 1.29 MiB/s, done.
Total 13 (delta 7), reused 0 (delta 0), pack-reused 0

Using github desktop to manage this repo results with same behavior

[Odabasyusuf]

Hi! Did you find a solution?

[adriatic]

While I had initially no problem in several weeks, I had to delete the connection between Github and Netlify. After that everything is fine again. That however is not a solution 😸

[ashish-kus]

Total 103 (delta 10), reused 0 (delta 0), pack-reused 0

I am stuck at this and never used Netlify.

[Lugonathaly]

Hola quiero saber cómo hace mi propia licencia en github y si eso se puede hace

[Abbasi233]

same issue

[dcsuka]

Same issue for me as well.

EDIT: I am running a Mac M1 OS.

[f1ght3rlucky]

same issue

[kemalsanli]

+1 working fine after

[Pachimanok]

working for me!!

[raoulelysee]

Thanks!

[jnroot0101]

Thank you man!!

[AmazinglyStrange]

Are you a wizard? Worked like magic!

[qadirsuh]

me too getting this problem

[dcsuka]

This only happens to me when the commits are too large, or I do many at once. Try committing only one hash at a time.

[RISMALUKMANHAKIM]

Enumerating objects: 2615, done. Counting objects: 100% (2615/2615), done. Delta compression using up to 4 threads Compressing objects: 100% (2466/2466), done. Writing objects: 100% (2615/2615), 25.58 MiB | 5.33 MiB/s, done. error: RPC failed; curl 18 transfer closed with outstanding read data remaining send-pack: unexpected disconnect while reading sideband packet fatal: the remote end hung up unexpectedly Everything up-to-date

[georgialive]

try: git gc in your terminal

[01119257547aass]

مكالمات ورسايل ايمو وواتساب فيديو

[channyeintun]

git gc doesn't help.

[ospaarmann]

Same issue for me. The complete push was 2.71 MiB. Git gets stuck on GitHub Desktop and on the command line. Sometimes a restart helps. This happens more and more often and really needs to be fixed.

🤷 ❯ git push
Enumerating objects: 30, done.
Counting objects: 100% (30/30), done.
Delta compression using up to 10 threads
Compressing objects: 100% (24/24), done.
Writing objects: 100% (27/27), 2.72 MiB | 491.00 KiB/s, done.
Total 27 (delta 11), reused 0 (delta 0), pack-reused 0

I'm on a MacBook Pro, 14-inch, 2021, Apple M1 Max, 64 GB RAM.

[TimmyBest]

happens all the time, something is really wrong!!

[mehmetyilmaz001]

There was a gif file in the .github folder in my case. When I delete that file everything went ok.

[adriatic]

I started this thread more than a year ago and had problems since I renewed the connection between GitHub and Netlify.

Note that the common factor in all the described problems is the failure of the (distributed) action initiated by the command “git push” issued by the user via the terminal shell. As stated above, this command failed to execute, because Netlify did not recognize my account on GitHub that tried to upload my app’s sources to Netlify for deployment.

This scenario is not the only one that can cause the command “git push” to fail - since this thread started, GitHub requested 2FA authentication, making it necessary to ensure that your terminal shell is aware of that. This applies to both ways sending the push command (using the terminal shell or GitHub desktop application.

[anaskhantts]

Increase the Git buffer size to the largest individual file size of your repo:
git config --global http.postBuffer 157286400

WORKED FOR ME!

[hegybirog]

thanks, worked for me!

[kortiz47]

thank you - worked for me!

[khiemdnt]

great, thanks

[justege]

thanks mate

[dmrd2653]

thank you :D

[goktugcy]

Make sure you haven't included node_modules or similar artifacts. Have you tried rolling back to the previous commit and attempting it again?
git reset --hard HEAD

[EnriquezAlberto]

Based on the information provided, it appears that the push process might be temporarily delayed due to network issues, server load, or other factors. Aborting the first push and trying again sometimes helps if the initial process got stuck. Since the second attempt also followed similar steps, it is possible that the problem persisted.

Here are some things you might consider doing if you run into a similar situation in the future:

Check network connection – Make sure your network connection is stable and not experiencing interruptions. A slow or unstable network can affect the speed of the boost.

Check the status of the remote server – Sometimes the remote server hosting your Git repository can experience problems or a lot of traffic. You can check the status of the remote server to see if there are any reported issues.

Try again after a while – If the problem persists, you might want to wait for a while and then try again later. Temporary network or server problems may resolve themselves.

Check Git configurations – Make sure your Git configurations are configured correctly, including your username, email, and remote repository URL.

Use SSH – If you're using HTTPS to connect to the remote repository, consider configuring SSH authentication, as it can sometimes provide a more reliable connection.

Contact the repository host – If the problem persists and you are using a hosted Git service (such as GitHub or GitLab), you can contact their support for help.

Remember that Git pushes can take longer for larger repositories or when dealing with larger files. Also, while aborting a send and trying again can sometimes help, it is not a guaranteed solution, and it is important to investigate potential underlying issues for a more permanent resolution.

[isidorae]

This issue was solved for me after moving a psd file I had inside my proyect folder (I hadnt done a 'git add' of it or anything, it was just there).