pushing to origin gets stuck (never finishes)

[shimon-edelman]

The problem

When pushing to origin, the process uploads everything, then gets stuck (the little arrow keeps spinning. The log doesn't show anything suspicious:
2022-04-12T19:53:45.797Z - info: [ui] Subscribed 'shimon-edelman' to Alive channel
2022-04-12T19:53:45.829Z - info: [ui] [AppStore] loading 3 repositories from store
2022-04-12T19:53:45.829Z - info: [ui] [AppStore] found account: shimon-edelman (Shimon Edelman)
2022-04-12T19:53:45.874Z - info: [ui] [BranchPruner] Last prune took place in 11 hours - skipping
2022-04-12T19:53:46.284Z - info: [ui] launching: 2.9.12 (Mac OS 12.3.1)
2022-04-12T19:53:46.301Z - info: [ui] execPath: '/Applications/GitHub Desktop.app/Contents/Frameworks/GitHub Desktop Helper (Renderer).app/Contents/MacOS/GitHub Desktop Helper (Renderer)'
2022-04-12T19:53:46.556Z - info: [ui] [BranchPruner] Last prune took place in 11 hours - skipping
2022-04-12T19:53:51.538Z - info: [ui] [Timing] Action 'create commit' for 'shimon-edelman/shimon-edelman.github.io' took 0.111s
2022-04-12T19:53:57.888Z - info: [ui] [AppStore.withAuthenticatingUser] account found for repository: shimon-edelman.github.io - shimon-edelman (has token)
2022-04-12T19:56:48.252Z - info: [ui] [AppStore] removing account shimon-edelman (Shimon Edelman) from store
2022-04-12T19:56:48.277Z - info: [ui] Unubscribed 'shimon-edelman' from Alive channel
2022-04-12T19:56:56.518Z - info: [ui] [SignInStore] initializing OAuth flow
2022-04-12T19:56:56.520Z - info: [main] opening in browser: https://github.com/login/oauth/authorize?client_id=de0e3c7e9973e1c4dd77&scope=repo%20user%20workflow&state=e582cf92-98bb-4099-8086-48692bcbb4a4
2022-04-12T19:56:57.457Z - info: [main] Processing protocol url
2022-04-12T19:56:57.458Z - info: [ui] [Dispatcher] requesting authenticated user
2022-04-12T19:56:57.986Z - info: [ui] [SignInStore] account resolved
2022-04-12T19:56:57.987Z - info: [ui] [AppStore] adding account shimon-edelman (Shimon Edelman) to store
2022-04-12T19:56:58.267Z - info: [ui] Subscribed 'shimon-edelman' to Alive channel

Release version

Version 2.9.12 (arm64)

Operating system

MacOS Monterey 12.3.1 (21E258)

Steps to reproduce the behavior

No response

Log files

2022-04-12T19:53:45.797Z - info: [ui] Subscribed 'shimon-edelman' to Alive channel
2022-04-12T19:53:45.829Z - info: [ui] [AppStore] loading 3 repositories from store
2022-04-12T19:53:45.829Z - info: [ui] [AppStore] found account: shimon-edelman (Shimon Edelman)
2022-04-12T19:53:45.874Z - info: [ui] [BranchPruner] Last prune took place in 11 hours - skipping
2022-04-12T19:53:46.284Z - info: [ui] launching: 2.9.12 (Mac OS 12.3.1)
2022-04-12T19:53:46.301Z - info: [ui] execPath: '/Applications/GitHub Desktop.app/Contents/Frameworks/GitHub Desktop Helper (Renderer).app/Contents/MacOS/GitHub Desktop Helper (Renderer)'
2022-04-12T19:53:46.556Z - info: [ui] [BranchPruner] Last prune took place in 11 hours - skipping
2022-04-12T19:53:51.538Z - info: [ui] [Timing] Action 'create commit' for 'shimon-edelman/shimon-edelman.github.io' took 0.111s
2022-04-12T19:53:57.888Z - info: [ui] [AppStore.withAuthenticatingUser] account found for repository: shimon-edelman.github.io - shimon-edelman (has token)
2022-04-12T19:56:48.252Z - info: [ui] [AppStore] removing account shimon-edelman (Shimon Edelman) from store
2022-04-12T19:56:48.277Z - info: [ui] Unubscribed 'shimon-edelman' from Alive channel
2022-04-12T19:56:56.518Z - info: [ui] [SignInStore] initializing OAuth flow
2022-04-12T19:56:56.520Z - info: [main] opening in browser: https://github.com/login/oauth/authorize?client_id=de0e3c7e9973e1c4dd77&scope=repo%20user%20workflow&state=e582cf92-98bb-4099-8086-48692bcbb4a4
2022-04-12T19:56:57.457Z - info: [main] Processing protocol url
2022-04-12T19:56:57.458Z - info: [ui] [Dispatcher] requesting authenticated user
2022-04-12T19:56:57.986Z - info: [ui] [SignInStore] account resolved
2022-04-12T19:56:57.987Z - info: [ui] [AppStore] adding account shimon-edelman (Shimon Edelman) to store
2022-04-12T19:56:58.267Z - info: [ui] Subscribed 'shimon-edelman' to Alive channel

Screenshots

Additional context

No response

[steveward]

Thanks for the report @shimon-edelman. Is this happening only in a specific repository? Are you trying to push a large amount of changes? Have you tried pushing via the command line to see if that succeeds?

Normally with push failures there's a specific cURL error that's returned if the push timeouts.

[shimon-edelman]

On Apr 12, 2022, at 4:17 PM, Steve Ward ***@***.******@***.***>> wrote: Thanks for the report @shimon-edelman<https://github.com/shimon-edelman>. Thanks for responding! Is this happening only in a specific repository? I only own one here. It has been working just fine for many months, including this morning (from a different machine). Are you trying to push a large amount of changes? Not necessarily; even just one character added to a file ends up having it stuck. Have you tried pushing via the command line to see if that succeeds? I tried, but my system lacks xcrun, and I am trying to avoid having to fix this. Normally with push failures there's a specific cURL error that's returned if the push timeouts. — Reply to this email directly, view it on GitHub<#14331 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AU3DD2F2S7WDR7MHFGKWDRLVEXK6XANCNFSM5TIM4QCQ>. You are receiving this because you were mentioned.Message ID: ***@***.***> —Shimon

[shimon-edelman]

I followed the advice re dealing with large files (delete the cache, etc), even though the last file that I had modified was not large at all. In any case, once I committed that file (again) to main and pushed, it all worked fine. Thank you. —Shimon On Apr 12, 2022, at 4:20 PM, Shimon Edelman ***@***.******@***.***>> wrote: On Apr 12, 2022, at 4:17 PM, Steve Ward ***@***.******@***.***>> wrote: Thanks for the report @shimon-edelman<https://github.com/shimon-edelman>. Thanks for responding! Is this happening only in a specific repository? I only own one here. It has been working just fine for many months, including this morning (from a different machine). Are you trying to push a large amount of changes? Not necessarily; even just one character added to a file ends up having it stuck. Have you tried pushing via the command line to see if that succeeds? I tried, but my system lacks xcrun, and I am trying to avoid having to fix this. Normally with push failures there's a specific cURL error that's returned if the push timeouts. — Reply to this email directly, view it on GitHub<#14331 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AU3DD2F2S7WDR7MHFGKWDRLVEXK6XANCNFSM5TIM4QCQ>. You are receiving this because you were mentioned.Message ID: ***@***.***> —Shimon

[steveward]

Glad to hear things are working again.

[joshdance]

I have this same issue. Saw 'delete the cache' mentioned. Where is that advice? Is it in a help doc?

[xke]

@joshdance, I had this issue, and used this command to delete the cache:

git rm -r --cached .

issue fixed! 😃

[BlueSky-fur]

I get the same issue every 3-4 commits, regardless of pushing large or small files/folders which means i have to delete the cache every 3-4 commits which is very frustrating when having large commits with slow upload sometimes.

is that issue ever being looked into closer?

[hatemalimam]

In my case I had to quite GitHub Desktop multiple times to have my commit pushed successfully, cleaning the cache didn't help.
This happens regardless of the size of the commit.

[HassanAli9]

I try to use this command in my project "git rm -r --cached ."
and I have selected the project folder "new terminal at my folder"
but it gave me this
"fatal: No pathspec was given. Which files should I remove?"
what is the correct way which file should access to remove it?

[HassanAli9]

@joshdance

[bsefton12]

I also have to remove the cache every 3-4 commits to get a successful push. Not sure why this issue was closed as I was still experiencing it with the latest version. Going to ditch GH desktop and revert to using cmd line.

[mrnebbi]

Running git config --global http.postBuffer 157286400 in the command line fixed the issue for me.

Thanks @faizahmaddae for the answer at https://stackoverflow.com/a/68711337/1759613

[rdwrome]

Running git config --global http.postBuffer 157286400 in the command line fixed the issue for me.

Thanks @faizahmaddae for the answer at https://stackoverflow.com/a/68711337/1759613

and thanks @mrnebbi for posting here. that fixed the issue for me, too.

[mustafaabobakr]

Conclusion ✍🏻

1. anywhere run

git config --global http.postBuffer 157286400

2. in your local repo run

git rm -r --cached .

Thank everyone 🎉

[cycollins]

@mustafaabobakr to point #1 above. I don't think the number "157286400" is magic. It roughly translates to "a lot". The Stack Overflow article was posted by a user who did some analysis to find the largest file that he pushes. The parameter was related to that number. If you don't want to use some combination of du to recursively analyze your source code it might be wise to try increasing numbers until one gets "unstuck". If those are bytes, that 150M, which even on multi-terabyte drives adds up pretty quickly. If it creates some file to buffer super-huge files, let's hope it doesn't say double-buffer those.

All I'm saying really is we should be careful with the big numbers we sling around. Clearly, some people only needed the cache clean. to make things work.

[velara3]

Having the same issue.

I tried clearing the cache and still waiting to see if it works. It looks like it might hang again.

@cycollins Indeed. So what is the default http.postBuffer amount? Can that be increased too high?

Is there a command in Github Desktop to clear the cache?
Is there a setting in Github Desktop to increase the buffer?

Trying again with a smaller number of items. What are these numbers Mib and KiB/s?

[tadgem]

Running git config --global http.postBuffer 157286400 in the command line fixed the issue for me.

Thanks @faizahmaddae for the answer at https://stackoverflow.com/a/68711337/1759613

Thanks so much :) still an issue for me on latest GH desktop, apple silicon

[ysftulek]

I also experience the same problem on my m2 pro macbook pro. It's usually solved by configuring git config --global http.postBuffer {x} where x is generally higher than the standard 1MB

[BlueSky-fur]

After extensive testing i can 100% confirm that currently increasing the postBuffer is the way to go. :)

[pixelasticity]

I was having the same issue on GitHub Desktop v3.2.1 on macOS Ventura. I increased the postBuffer and seems to be working now.

[tresorama]

I arrived here thanks to Google, and even if I don't use Github Desktop I had same problem.
Updating postBuffer did it for me.

It's a Git thing.