New GIT release 2.24.0.2 - Unable to clone a GIT repo

[Gabriel Gaudreau]

I just installed the new version 2.24.0.2 and I get this error no matter the repo I chose.

From my repo directory, I'm unable to clone a remote repo.

My command is:

C:\Users\gg\Documents\Repositories\test>git clone https://g_g@bitbucket.org/orica/wg200-board-encoder.git
Cloning into 'wg200-board-encoder'...
remote: Counting objects: 2641, done.
remote: Compressing objects: 100% (1426/1426), done.
remote: Total 2641 (delta 1134), reused 2597 (delta 1097)
Receiving objects: 100% (2641/2641), 30.43 MiB | 4.54 MiB/s, done.
error: RPC failed; curl 56 OpenSSL SSL_read: No error
Resolving deltas: 100% (1134/1134), done.

As observed the error is RPC failed. And what is strange OpenSSL... show "No error"

[jredmond · Accepted solution]

"curl 56" is a timeout receiving data (https://curl.haxx.se/libcurl/c/libcurl-errors.html lists the codes). Your client should allow you to set the buffer for HTTP-based connections, but the details of how to do that will depend on which client you're using (looks like maybe git bash?). You can also avoid cURL timeouts by using SSH, or making sure your network and proxy are not improperly delaying traffic.

The OpenSSL "No error" message is due to a new version of cURL, which improperly interprets improper connection terminations - such as what happens in a timeout. Since Git relies heavily on cURL for HTTP-based connections, it appears that that new cURL was bundled in for your Windows client. The non-error is fixed in https://github.com/curl/curl/commit/78cef068479d85f7af29b5ddf21ced5288a50f37 but it may take a bit for the new version of cURL to make it into your (unspecified) client.

[Gabriel Gaudreau]

Thank for your answer and help. It's not git bash it's a command prompt under windows 10. Using the previous GIT version (2.24.0) make no problem. So it's a bit strange that this new version make the current setting not working properly. So I will focus now to see if the cURL does fit with my Windows client.