Hello, I am one of the PACT consumer, after upgrading to 4.0, It generates random strings (as example) to match the specified pattern and for some reason when it serializes those example string, it generates invalid sequence, It doesn't escape those strings in 4.0.x version that's the reason we don't see this issue before. we are getting below error

{
  "error": {
    "message": "source sequence is illegal/malformed utf-8",
    "reference": "HjPEylMxlF"
  }
}

Interesting. In most of the matchers that the JVM provides, you can provide an example or have Pact JVM generate ones for you. I suggest you don’t let it generate values, not just because of the issue, but also because it will mean the pact isn’t pre-verified in tools like

can-i-deploy

. That being said, if it is generating an invalid pact file, could you please raise a defect on the Pact JVM github?

@Matt (pactflow.io / pact-js / pact-go) can I please get the link to raise defect?

Can you also try a later version than 4.0, that is not a supported version

sorry i mentioned wrong version earlier, currently we are using 4.1.41

You’d raise any issue on the Github repo here 👉 https://github.com/pact-foundation/pact-jvm/issues/new

@Matt (pactflow.io / pact-js / pact-go) I have created the issue, please find below link for your reference https://github.com/pact-foundation/pact-jvm/issues/1651

Thanks for raising. I don’t see any comments on the issue, but best to follow that issue for updates

@Matt (pactflow.io / pact-js / pact-go) its passing sometimes and failing consistently, not sure what exactly the problem is

Hi Yogesh, your last update was yesterday and as you have seen the ticket has been initiated and had been active. Please follow the ticket there. Please also understand that the team have other priorities and can't just drop what they're doing to focus on the last ticket someone raises. That being said I know Ron will be away for a week, so it will at least be another week before you see an update.