Error while installing binary: Checksum rejected

Software versions

Please provide at least OS and version of pact-js

• OS: _e.g. Mac OSX Catalina 10.15.5
• Consumer Pact library: “@pact-foundation/pact”: “^9.15.5”,
• Node Version: v14.15.4

Issue Checklist

Please confirm the following:

• [ x] I have upgraded to the latest
• [ x] I have the read the FAQs in the Readme
• [ x] I have triple checked, that there are no unhandled promises in my code
• I have set my log level to debug and attached a log file showing the complete request/response cycle
• For bonus points and virtual high fives, I have created a reproduceable git repository (see below) to illustrate the problem

Expected behaviour

the pact_binary_location is set to company specifik location and download from there works fine !

Actual behaviour

Checksum error when installing binary on both OSX and Linux build servers

Error while installing binary: Checksum rejected for file ‘pact-1.88.49-osx.tar.gz’ with checksum pact-1.88.49-osx.tar.gz.checksum

Steps to reproduce

How can someone else reproduce this bug? Change the pact_binary_location for all 9.* versions

For extra bonus points and internet karma, provide a repository, gist or reproducible code snippet so that we can test the problem.

We recommend forking the project and modifying a relevant example in the examples folder

Relevant log files

Please ensure you set logging to DEBUG and attach any relevant log files here (or link to a gist).

[BrendonReed]

Hi, I experienced a similar issue, so just jumping in here to add what I found.

The issue for me was definitely the proxy – I tracked it down to the switch from requests to needle for doing the download. I then replicated with a simple request vs needle file download. My corporate proxy worked fine with Request, but not with Needle. My guess is that it has to do with http vs https, something like the proxy is plain http even for https. Probably not an uncommon scenario for a corporate proxy.

If you’re bundling the binaries then I suppose that would solve my issue as well, but I’m not sure of the timeline. Because most people don’t use pact-js-core directly, is it simple to provide me a link to an issue or something that’s tracking so I can get a better picture of when it might be available to me?

[TimothyJones]

We’re working on a permanent fix for this, by bundling the binaries with the package.

In the meantime, try opening the file in a text editor- usually it’s an error message from github or a proxy you have set up.

Also, if you’re able to try the beta release, I believe the most recent version has the binaries bundled with it. However, the release is not stable yet, so it might not suit your needs