From: Johannes Schindelin <Johannes.Schindelin@gmx•de>
To: "Mr. Manuel" <mr-manuel@outlook•it>
Cc: "git@vger•kernel.org" <git@vger•kernel.org>
Subject: Re: Push to GitHub HTTP repo fails (>v2.45.2)
Date: Sun, 29 Sep 2024 20:14:51 +0200 (CEST) [thread overview]
Message-ID: <a6dd718c-807a-c19b-b915-e6cc455256af@gmx.de> (raw)
In-Reply-To: <PA4PR02MB7040A36E17B197AB8DD7BBFC8C612@PA4PR02MB7040.eurprd02.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2061 bytes --]
Hi Mr. Manuel,
On Tue, 17 Sep 2024, Mr. Manuel wrote:
> 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
> 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
>
>
next prev parent reply other threads:[~2024-09-29 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 7:52 Push to GitHub HTTP repo fails (>v2.45.2) Mr. Manuel
2024-09-29 18:14 ` Johannes Schindelin [this message]
2024-09-30 5:29 ` AW: " Mr. Manuel
2024-09-30 16:06 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a6dd718c-807a-c19b-b915-e6cc455256af@gmx.de \
--to=johannes.schindelin@gmx$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=mr-manuel@outlook$(echo .)it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox