-
-
Notifications
You must be signed in to change notification settings - Fork 169
cURL error 56 when checking for new release using precondition #4030
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
codeskipper opened this issue
Feb 28, 2025
· 2 comments
· Fixed by nodejs/release-cloudflare-worker#321
Open
cURL error 56 when checking for new release using precondition #4030
codeskipper opened this issue
Feb 28, 2025
· 2 comments
· Fixed by nodejs/release-cloudflare-worker#321
Comments
flakey5
added a commit
to nodejs/release-cloudflare-worker
that referenced
this issue
Mar 3, 2025
Closes nodejs/build#4030 Signed-off-by: flakey5 <[email protected]>
Hey! Sorry for the delayed response, just saw this, fix will be deployed with nodejs/release-cloudflare-worker#321. Thanks for reporting! |
flakey5
added a commit
to nodejs/release-cloudflare-worker
that referenced
this issue
Mar 3, 2025
Closes nodejs/build#4030 Signed-off-by: flakey5 <[email protected]>
Issue should be fixed! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
URL:
https://nodejs.org/dist
Browser Name:
cURL
Browser Version:
curl 8.7.1 (x86_64-apple-darwin24.0) libcurl/8.7.1 (SecureTransport) LibreSSL/3.3.6 zlib/1.2.12 nghttp2/1.63.0
Operating System:
macOS 15.3.1
How to reproduce the issue:
When running a cURL session to check for a new NodeJS release using preconditions for etag and If-Modified-Since, it sometimes exits with code 56 which indicates a network issue. When this happens, it also returns http code 412 which just indicates no match for the preconditions.
The issue happens only some of the time when running the session, I have not been able to discern a pattern. It has happened just about every day on a CI job we run daily since around November 2024.
Here is an example session with the issue where I've added the --verbose option.
I hope that helps troubleshooting the issue.
thanks.
The text was updated successfully, but these errors were encountered: