-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
zlib port download hits unexpected hash, probably GitHub issue #16164
Comments
I'm experiencing the same problem with the Emscripten Docker Images and |
Looks like GitHub is aware of the issue according to this Twitter thread (I didn't get a reply on the support ticket yet): https://twitter.com/tgummerer/status/1488493440103030787 |
According to https://twitter.com/tgummerer/status/1488565820326400000 this should've been fixed but I just checked and I'm still seeing the wrong checksum for |
Same here. |
@akoeplinger and @sbehnke could you try the URL Currently I can see that the combination of http1.1 and the
|
Currently I worked around it by applying https://github.com/emscripten-core/emscripten/pull/16169/files to 3.1.1. Running the curl commands I get:
|
I just tried again and I now get the correct checksum again over http1.0, http1.1 and http2 so looks like it is fixed on GitHub's side 👍 |
Sometime in the last few hours we're seeing this:
It looks like
https://github.com/madler/zlib/archive/v1.2.11.zip
started returning a file with a different SHA512 hash now:a42b8359e76cf7b3ae70bf31f0f8a8caa407ac80e8fe08b838076cd5e45ac2e685dae45eb59db2d25543fb3b5bd13b843a02bb8373cda704d7238be50d5e9c68
9ec7c573fac2cd4d6ba64dd4dfd7330f317be75367575013da4004d7da7ff51b70b85783dc8533df081e70527135cdbf2ffc12b40f2d011fd7fbe6cb52d2f47d
Interestingly
https://github.com/madler/zlib/archive/refs/tags/v1.2.11.zip
still returns the "expected" SHA512 hash.The
/archive/v1.2.10
for the earlier zlib tag returns the expected content on both URLs so it looks like a GitHub bug to me and I opened a ticket with GitHub support: 1485268The text was updated successfully, but these errors were encountered: