zlib port download hits unexpected hash, probably GitHub issue #16164

Activity

1. donalffons commented on Feb 1, 2022

   

   donalffons

   on Feb 1, 2022

   Last edited by donalffons

   More actions

   I'm experiencing the same problem with the Emscripten Docker Images and -s USE_ZLIB=1. I tried a few different versions (3.x and 2.x) - all showing the same error...
   EDIT: While researching I found this issue, which might or might not be related.
2. akoeplinger commented on Feb 1, 2022

   

   akoeplinger

   on Feb 1, 2022

   ContributorAuthor

   More actions

   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
3. sbc100

   closed this as completedin #16169on Feb 1, 2022
4. akoeplinger commented on Feb 1, 2022

   

   akoeplinger

   on Feb 1, 2022

   ContributorAuthor

   More actions

   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 https://github.com/madler/zlib/archive/v1.2.11.zip
5. sbehnke commented on Feb 1, 2022

   

   sbehnke

   on Feb 1, 2022

   More actions

   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 https://github.com/madler/zlib/archive/v1.2.11.zip

   Same here.
6. notnarb commented on Feb 1, 2022

   

   notnarb

   on Feb 1, 2022

   More actions

   @akoeplinger and @sbehnke could you try the URL https://github.com/madler/zlib/archive/refs/tags/v1.2.11.zip instead?

   Currently I can see that the combination of http1.1 and the /archive/v1.2.11.zip produces the "incorrect" hash while using http2 or /archive/refs/tags/v1.2.11.zip will produce the old hash consistently. I suspect there is a caching issue on GitHub's end.

   [~/Downloads]
   bhorsley@beehorse$ curl -sL --http1.1 https://github.com/madler/zlib/archive/v1.2.11.zip | sha256sum
   9c46d65f2f8655c0decc9a22c90a3d58fdc8dfff432899b655a6c9d2b8bbd7db  -
   [~/Downloads]
   bhorsley@beehorse$ curl -sL --http2 https://github.com/madler/zlib/archive/v1.2.11.zip | sha256sum
   f5cc4ab910db99b2bdbba39ebbdc225ffc2aa04b4057bc2817f1b94b6978cfc3  -
   [~/Downloads]
   bhorsley@beehorse$ curl -sL --http1.1 https://github.com/madler/zlib/archive/refs/tags/v1.2.11.zip | sha256sum
   f5cc4ab910db99b2bdbba39ebbdc225ffc2aa04b4057bc2817f1b94b6978cfc3  -
   [~/Downloads]
   bhorsley@beehorse$ curl -sL --http2 https://github.com/madler/zlib/archive/refs/tags/v1.2.11.zip | sha256sum
   f5cc4ab910db99b2bdbba39ebbdc225ffc2aa04b4057bc2817f1b94b6978cfc3  -
   
7. sbehnke commented on Feb 1, 2022

   

   sbehnke

   on Feb 1, 2022

   Last edited by sbehnke

   More actions

   @akoeplinger and @sbehnke could you try the URL https://github.com/madler/zlib/archive/refs/tags/v1.2.11.zip instead?

   Currently I can see that the combination of http1.1 and the /archive/v1.2.11.zip produces the "incorrect" hash while using http2 or /archive/refs/tags/v1.2.11.zip will produce the old hash consistently. I suspect there is a caching issue on GitHub's end.

   [~/Downloads]
   bhorsley@beehorse$ curl -sL --http1.1 https://github.com/madler/zlib/archive/v1.2.11.zip | sha256sum
   9c46d65f2f8655c0decc9a22c90a3d58fdc8dfff432899b655a6c9d2b8bbd7db  -
   [~/Downloads]
   bhorsley@beehorse$ curl -sL --http2 https://github.com/madler/zlib/archive/v1.2.11.zip | sha256sum
   f5cc4ab910db99b2bdbba39ebbdc225ffc2aa04b4057bc2817f1b94b6978cfc3  -
   [~/Downloads]
   bhorsley@beehorse$ curl -sL --http1.1 https://github.com/madler/zlib/archive/refs/tags/v1.2.11.zip | sha256sum
   f5cc4ab910db99b2bdbba39ebbdc225ffc2aa04b4057bc2817f1b94b6978cfc3  -
   [~/Downloads]
   bhorsley@beehorse$ curl -sL --http2 https://github.com/madler/zlib/archive/refs/tags/v1.2.11.zip | sha256sum
   f5cc4ab910db99b2bdbba39ebbdc225ffc2aa04b4057bc2817f1b94b6978cfc3  -
   

   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:

   ❯ curl -sL --http1.1 https://github.com/madler/zlib/archive/v1.2.11.zip | shasum -a 256
   9c46d65f2f8655c0decc9a22c90a3d58fdc8dfff432899b655a6c9d2b8bbd7db  -
   ❯ curl -sL --http2 https://github.com/madler/zlib/archive/v1.2.11.zip | shasum -a 256
   f5cc4ab910db99b2bdbba39ebbdc225ffc2aa04b4057bc2817f1b94b6978cfc3  -
   ❯ curl -sL --http1.1 https://github.com/madler/zlib/archive/refs/tags/v1.2.11.zip | shasum -a 256
   f5cc4ab910db99b2bdbba39ebbdc225ffc2aa04b4057bc2817f1b94b6978cfc3  -
   ❯ curl -sL --http2 https://github.com/madler/zlib/archive/refs/tags/v1.2.11.zip | shasum -a 256
   f5cc4ab910db99b2bdbba39ebbdc225ffc2aa04b4057bc2817f1b94b6978cfc3  -
   
8. akoeplinger commented on Feb 2, 2022

   

   akoeplinger

   on Feb 2, 2022

   ContributorAuthor

   More actions

   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 👍

   👍React with 👍1Reacted by Jérôme Laban