threads / discuss / 62128

Push to GitHub HTTP repo fails (>v2.45.2)

Subject: Push to GitHub HTTP repo fails (>v2.45.2)

## tl;dr

4 messages between Sep 17, 2024 and Sep 30, 2024.

replies: 3people: 2as markdown or json

Mr. Manuel· Sep 17, 2024, 07:52 UTC · lore

Hello,

after Git version 2.45.2 I’m no more able to push to a GitHub HTTP repository. Tried 2.45.3, 2.46.0 and 2.46.1. I can reproduce this on many different systems. Found also a entry on reddit: https://www.reddit.com/r/github/comments/1f3xmnl/error_remotecurl_error_reading_command_stream/

Here some more details:

PS C:\Users\User\my-project_1> git --version git version 2.46.0.windows.1 PS C:\Users\User\my-project_1> git push --force error: remote-curl: error reading command stream from git error: failed to push some refs to 'https://github.com/my-github-user/my-project_1.git'

PS C:\Users\User\my-project_1> git --version
git version 2.45.2.windows.1
PS C:\Users\User\my-project_1> git push --force
Enumerating objects: 27, done.
Counting objects: 100% (27/27), done.
Delta compression using up to 8 threads
Compressing objects: 100% (16/16), done.
Writing objects: 100% (18/18), 14.52 MiB | 2.08 MiB/s, done.
Total 18 (delta 7), reused 1 (delta 0), pack-reused 0 (from 0)
remote: Resolving deltas: 100% (7/7), completed with 5 local objects.
To https://github.com/my-github-user/my-project_1.git
   c7a0249..379246f  main -> main

Johannes Schindelin· Sep 29, 2024, 18:14 UTC · re: Mr. Manuel · lore

Re: Push to GitHub HTTP repo fails (>v2.45.2)

Hi Mr. Manuel,

On Tue, 17 Sep 2024, Mr. Manuel wrote:

Show 12 quoted lines

> after Git version 2.45.2 I’m no more able to push to a GitHub HTTP
> repository. Tried 2.45.3, 2.46.0 and 2.46.1. I can reproduce this on
> many different systems. Found also a entry on reddit:
> https://www.reddit.com/r/github/comments/1f3xmnl/error_remotecurl_error_reading_command_stream/
>
> Here some more details:
>
> PS C:\Users\User\my-project_1> git --version
> git version 2.46.0.windows.1
> PS C:\Users\User\my-project_1> git push --force
> error: remote-curl: error reading command stream from git
> error: failed to push some refs to 'https://github.com/my-github-user/my-project_1.git'

This looks like it might be due to an update in the libcurl library; Git for Windows v2.46.0 came with libcurl v8.9.0 while Git for Windows v2.45.2 came with libcurl v8.8.0.

Could you first go ahead and try with https://github.com/git-for-windows/git/releases/tag/v2.47.0-rc0.windows.1? Otherwise I would need to direct you to bisect through the more fine-grained snapshot versions at https://wingit.blob.core.windows.net/files/index.html (where v2.45.2 was added on Mon, 3 Jun 2024 09:24:47 +0200 and v2.46.0 on Mon, 29 Jul 2024 10:56:11 -0700).

Also, since there haven't been any reports about this issue at https://github.com/git-for-windows/git/issues, I suspect that you have somewhat of a special setup, maybe a proxy or something similar?

Ciao, Johannes

Show 14 quoted lines

> PS C:\Users\User\my-project_1> git --version
> git version 2.45.2.windows.1
> PS C:\Users\User\my-project_1> git push --force
> Enumerating objects: 27, done.
> Counting objects: 100% (27/27), done.
> Delta compression using up to 8 threads
> Compressing objects: 100% (16/16), done.
> Writing objects: 100% (18/18), 14.52 MiB | 2.08 MiB/s, done.
> Total 18 (delta 7), reused 1 (delta 0), pack-reused 0 (from 0)
> remote: Resolving deltas: 100% (7/7), completed with 5 local objects.
> To https://github.com/my-github-user/my-project_1.git
>    c7a0249..379246f  main -> main
>
>

Mr. Manuel· Sep 30, 2024, 05:29 UTC · re: Johannes Schindelin · lore

AW: Push to GitHub HTTP repo fails (>v2.45.2)

Hi,

thank you very much for your answer. I installed v2.47.0-rc0.windows.1 and now everything works as expected. I have no special setup, no proxy, no VPN, everything default.

Regards, Manuel

-----Ursprüngliche Nachricht-----
Von: Johannes Schindelin <Johannes.Schindelin@gmx.de> 
Gesendet: Sonntag, 29. September 2024 20:15
An: Mr. Manuel <mr-manuel@outlook.it>
Cc: git@vger.kernel.org
Betreff: Re: Push to GitHub HTTP repo fails (>v2.45.2)

Hi Mr. Manuel,

On Tue, 17 Sep 2024, Mr. Manuel wrote:

Show 12 quoted lines

> after Git version 2.45.2 I’m no more able to push to a GitHub HTTP 
> repository. Tried 2.45.3, 2.46.0 and 2.46.1. I can reproduce this on 
> many different systems. Found also a entry on reddit:
> https://www.reddit.com/r/github/comments/1f3xmnl/error_remotecurl_erro
> r_reading_command_stream/
>
> Here some more details:
>
> PS C:\Users\User\my-project_1> git --version git version 
> 2.46.0.windows.1 PS C:\Users\User\my-project_1> git push --force
> error: remote-curl: error reading command stream from git
> error: failed to push some refs to 'https://github.com/my-github-user/my-project_1.git'

This looks like it might be due to an update in the libcurl library; Git for Windows v2.46.0 came with libcurl v8.9.0 while Git for Windows v2.45.2 came with libcurl v8.8.0.

Also, since there haven't been any reports about this issue at https://github.com/git-for-windows/git/issues, I suspect that you have somewhat of a special setup, maybe a proxy or something similar?

Ciao, Johannes

Show 13 quoted lines

> PS C:\Users\User\my-project_1> git --version git version 
> 2.45.2.windows.1 PS C:\Users\User\my-project_1> git push --force 
> Enumerating objects: 27, done.
> Counting objects: 100% (27/27), done.
> Delta compression using up to 8 threads Compressing objects: 100% 
> (16/16), done.
> Writing objects: 100% (18/18), 14.52 MiB | 2.08 MiB/s, done.
> Total 18 (delta 7), reused 1 (delta 0), pack-reused 0 (from 0)
> remote: Resolving deltas: 100% (7/7), completed with 5 local objects.
> To https://github.com/my-github-user/my-project_1.git
>    c7a0249..379246f  main -> main
>
>

Johannes Schindelin· Sep 30, 2024, 16:06 UTC · re: Mr. Manuel · lore

Re: AW: Push to GitHub HTTP repo fails (>v2.45.2)

Hi Manuel,

On Mon, 30 Sep 2024, Mr. Manuel wrote:

> thank you very much for your answer. I installed v2.47.0-rc0.windows.1
> and now everything works as expected. I have no special setup, no proxy,
> no VPN, everything default.

Excellent! Thank you for confirming.

Ciao, Johannes