Hello Team :wave::sunglasses:, a question, I am tr...
# pact-js
s
Hello Team ๐Ÿ‘‹๐Ÿ˜Ž, a question, I am trying to run my pact project on a mac machine with big sur 11.6.2 operating system, and I am having problems on the provider side, pact throws a generic error, I have not found the possible cause; the log is the following, Do you know why it could have this behavior?:
the complete log is above:
Copy code
[2022-03-28 19:31:45.402 +0000] INFO (96647 on WM-C02DX5CZMD6T): pact@10.0.0-beta.56: Verifying provider
[2022-03-28 19:31:45.409 +0000] INFO (96647 on WM-C02DX5CZMD6T): pact-core@13.4.1-beta.13: Verifying Pacts.
[2022-03-28 19:31:45.410 +0000] INFO (96647 on WM-C02DX5CZMD6T): pact-core@13.4.1-beta.13: Verifying Pact Files
[2022-03-28 19:31:45.410 +0000] DEBUG (96647 on WM-C02DX5CZMD6T): pact-core@13.4.1-beta.13: Initalising native core at log level 'debug'
[2022-03-28 19:31:45.412 +0000] WARN (96647 on WM-C02DX5CZMD6T): pact-core@13.4.1-beta.13: Ignoring option 'consumerVersionTags' because it is invalid without 'pactBrokerUrl' also being set. This may indicate an error in your configuration
[2022-03-28 19:31:45.412 +0000] WARN (96647 on WM-C02DX5CZMD6T): pact-core@13.4.1-beta.13: Ignoring option 'publishVerificationResult' because it is invalid without 'pactBrokerUrl' also being set. This may indicate an error in your configuration
[2022-03-28 19:31:45.414 +0000] DEBUG (96647 on WM-C02DX5CZMD6T): pact-core@13.4.1-beta.13: sending arguments to FFI:
[2022-03-28 19:31:45.415 +0000] DEBUG (96647 on WM-C02DX5CZMD6T): pact-core@13.4.1-beta.13: --request-timeout
30000
--loglevel
debug
--state-change-url
<http://localhost:60534/_pactSetup>
--provider-tags
QA
--provider-version
1.0.0
--port
60534
--hostname
localhost
--provider-name
getidentityProvider
--file
/Users/jsuarezp/tr/__tests__/contract/pacts/getidentityConsumer-getidentityProvider.json

 RUNS  __tests__/contract/provider/identity/get.identity.provider.spec.js
[2022-03-28T19:31:45Z DEBUG pact_ffi::verifier::verifier] Pact source to verify = File(/Users/jsuarezp/tr/__tests__/contract/pacts/getidentityConsumer-getidentityProvider.json)
[2022-03-28T19:31:45Z DEBUG pact_plugin_driver::catalogue_manager] Updated catalogue entries:
    core/content-generator/binary
    core/content-generator/json
    core/content-matcher/json
    core/content-matcher/multipart-form-data
    core/content-matcher/text
    core/content-matcher/xml
[2022-03-28T19:31:45Z DEBUG pact_plugin_driver::catalogue_manager] Updated catalogue entries:
    core/matcher/v1-equality
    core/matcher/v2-max-type
    core/matcher/v2-min-type
    core/matcher/v2-minmax-type
    core/matcher/v2-regex
    core/matcher/v2-type
    core/matcher/v3-content-type
    core/matcher/v3-date
    core/matcher/v3-datetime
    core/matcher/v3-decimal-type
    core/matcher/v3-includes
    core/matcher/v3-integer-type
    core/matcher/v3-null
    core/matcher/v3-number-type
    core/matcher/v3-time
    core/matcher/v4-array-contains
    core/matcher/v4-equals-ignore-order
    core/matcher/v4-max-equals-ignore-order
    core/matcher/v4-min-equals-ignore-order
    core/matcher/v4-minmax-equals-ignore-order
    core/matcher/v4-not-empty
 RUNS  __tests__/contract/provider/identity/get.identity.provider.spec.js
thread '<unnamed>' panicked at 'Client::new(): reqwest::Error { kind: Builder, source: MissingOrMalformedExtensions }', /Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/reqwest-0.11.9/src/async_impl/client.rs:1263:38
[2022-03-28 19:31:46.106 +0000] DEBUG (96647 on WM-C02DX5CZMD6T): pact-core@13.4.1-beta.13: response from verifier: null, 3
[2022-03-28 19:31:46.107 +0000] ERROR (96647 on WM-C02DX5CZMD6T): pact-core@13.4.1-beta.13: !!!!!!!!! PACT CRASHED !!!!!!!!!

The underlying pact core crashed in an unexpected way.

This is almost certainly a bug in pact-js-core. It would be great if you could
open a bug report at: <https://github.com/pact-foundation/pact-js-core/issues>
so that we can fix it.

There is additional debugging information above. If you open a bug report, 
please rerun with logLevel: 'debug' set in the VerifierOptions, and include the
full output.

SECURITY WARNING: Before including your log in the issue tracker, make sure you
have removed sensitive info such as login credentials and urls that you don't want
to share with the world.

We're sorry about this!

 FAIL  __tests__/contract/provider/identity/get.identity.provider.spec.js
  Validate pact of identity
    โœ• validate the pact of an identity get (706 ms)

  โ— Validate pact of identity โ€บ validate the pact of an identity get

    Pact Verification FAIL!: Get identity

      22 |                 console.log('Pact Verification Complete!: Get identity ', res);
      23 |             }).catch((res) => {
    > 24 |                 throw new Error('Pact Verification FAIL!: Get identity ', res);
         |                       ^
      25 |             });
      26 |     })
      27 |

      at __tests__/contract/provider/identity/get.identity.provider.spec.js:24:23
m
Ah, I think this is related to an invalid certificate in your chain
It looks like itโ€™s still not released yet, but when it is it will resolve this issue
for now, there is a certificate in your chain somewhere that is invalid, youโ€™ll need to find which one it is and remove/fix it
s
Thank you very much, Matt ๐Ÿ™Œ, checking I have several expired certificates on my machine, I will manage them and validate it again
๐Ÿ‘ 1