Hi I m not sure if this is the right channel But I have an i Pact Foundation #pact-broker

Hi, I'm not sure if this is the right channel. But...

Robert

11/15/2022, 1:21 PM

Hi, I'm not sure if this is the right channel. But I have an issue with two pacts that always trigger the "Contract Content Changed" event, even the contract didn't change. If I check the most recent changes on the pact broker for that pact. I got as response header

200 parseerror

and in the response body there is the line that something changed, but underneath it's just empty lines

Copy code

The following changes were made about 2 hours ago (Tue 15 Nov 2022, 11:15am +00:00)

Yousaf Nabi (pactflow.io)

11/15/2022, 1:35 PM

are the pacts being created with non-deterministic data, a timestamp perhaps? can you provide the content of the old and new pact, that is causing the event trigger. Where are these pacts being generated? In CI?

I got as response header
200 parseerror

and in the response body there is the line that something changed, but underneath it's just empty lines

Where are seeing this, directly in the broker?

Robert

11/15/2022, 2:28 PM

There a no non-deterministic data used. I can't share the content and the pact is also pretty big. Yes the pact is generated in CI.

Where are seeing this, directly in the broker?

Yeah, I'm calling the pb:diff-previous-distinct
in the HAL Browser and I see that. It's the same if I call the api over e.g. postman Anyway I'm trying to reproduce this locally, but I wonder why there no changes shown on the pact broker or if I can check somewhere else

Robert

11/15/2022, 3:05 PM

I just compared now the pacts on the pact broker and I just can see that the interaction ids are sometimes differing. That can't be the problem right?

Copy code

"interactions": [
    {
      "_id": "2367036c61b56ea3a005eec90da7b26be755928b",
      "description": "GET some request",

Robert

11/15/2022, 3:52 PM

Ok after local testing I found the problem. There are matching rules sometimes added and than again removed from the pact. Therefore the pact really changed

Copy code

[2022-11-15 14:04:20.344 +0000] DEBUG (609 on runner-19-concurrent-0): pact-node@10.17.6: WARN: Ignoring unsupported matching rules {"match"=>"type"} for path $['body']['data']['detail']['items'][*]@['id']

Open in Slack

Previous Next