Hi team, I work at Macmillan Learning on a team called "writing tools" and I'm encountering an issue I believe might be related to Provider States and state handlers (which as far as I know we aren't using). I would love any advice that you can offer. My error previously mentioned "no null state handler present" prior to failing, and my new error occurs at nearly the same point in our Jenkins build and publish process, and looks as follows: Verifying writing 0.0.0-8477ca993 [2022-08-09 141240.376 +0000] INFO (29 on d53225d7acfa): pact@9.18.1: Verifying provider [2022-08-09 141240.389 +0000] INFO (29 on d53225d7acfa): pact-node@10.17.6: Verifying Pacts. [2022-08-09 141240.391 +0000] INFO (29 on d53225d7acfa): pact-node@10.17.6: Verifying Pact Files Error: connect EINVAL 0.0.11.184:80 - Local (0.0.0.0:0) at internalConnect (nodenet953:16) at defaultTriggerAsyncIdScope (nodeinternal/async hooks465:18) at GetAddrInfoReqWrap.emitLookup [as callback] (nodenet1097:9) at GetAddrInfoReqWrap.onlookup [as oncomplete] (nodedns73:8) { errno: -22, code: 'EINVAL', syscall: 'connect', address: '0.0.11.184', port: 80 } error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Hi Alison, this looks like a JS issue. Does it work on your local machines and only fail on CI? We’ll need a bit more info in addition to this to see what’s happening

To help assist with debugging your issue, please provide: your pact test setup (code), the generated pact file and terminal output/relevant log files. Please note: statements such as "I cannot share in public because it's commercially sensitive" are not helpful. See this link on how to produce a minimal reproducible example that we can use to help you: https://stackoverflow.com/help/minimal-reproducible-example

please see the tips above. What makes you believe it’s a provider states issue and not something else? The logs shown don’t point to that. It looks like the verifier is trying to connect to port

80

on

00.0.11.184

. That looks to be a non-local IP address, and the verifier is unable to reach it. You might find that instead of pointing to

localhost

, pointing to

127.0.0.1

(or the correct local IP) might work

Hi Matt, thanks for the suggestion! I thought it was related to provider states because it started showing up at the same time as the message "pact@9.18.1: No state handler found for "null", ignoring", which caused me to add

stateHandlers: {
        [null]: () => {
          // This is the "default" state handler, when no state is given
          console.log('hit null state, handling')
        }
      },

to my Verifier.

interesting

Everything was working perfectly in CI pipeline and then out of the blue on a fresh rebuild we started hitting this error. I'm still trying to locate what changed or the source of the issue is.

We are not mocking the server.

do you mean, you’re hitting a live service or that you aren’t mocking dependencies? In case it’s not clear, you should definitely not mock the provider that you’re verifying

Right, we are NOT mocking the provider, we are hitting the actual provider API and modifying the real DB. This was a point of debate on the team, but in the end we agreed to hit the real provider API since that's the only way (imo) Pact really serves its purpose.

I think you can ignore the null state handler, it won't impact anything

I’ve just added a FAQ for that, as it’s come up a few times recently https://docs.pact.io/faq#can-i-verify-my-pacts-against-a-deployed-instance-of-a-provider

The other practical reason is that using provider states is very hard to do this way.

good point. i’ll add that.

thx