https://pact.io logo
Join Slack
Powered by
This is my contract file:
# pact-broker
d
This is my contract file:
y
can you provide the pact, a screenshot isn’t particular usable to recreate. which version lib created it? the key field was removed in later versions of the pact core. can you try removing the key field manually
d
This is my pact file:
Yeah, I will check again version lib created the pact, many thanks🤩. This is my pact file as below
Employee-Product.json
y
Hey thanks for that, okay so its the latest version of pact-jvm
Copy code
"pact-jvm": {
      "version": "4.6.15"
    }
If I remove the key it works for me
It was removed in pact-reference/rust as part of this issue https://github.com/pact-foundation/pact-reference/issues/264#issuecomment-1556582681 pact-jvm has its own core engine and does not use the rust core, so I think you may need to raise an issue against pact-jvm, and state you would expect the key not to be there in a generated pact in the latest version of pact-jvm, as it causes issues with interop with pact-rust based libraries Ron is the main maintainer of both, so he should be able to sort
d
Thank you for your respond, I will raise this issue to group pact-jvm to improve the latest version😉
Hi @Yousaf Nabi (pactflow.io), I try to remove the key in my pact but it still not working and display error as below :(
y
d
Ya, this is my mistake🤭. I have not configured the transport option for grpc 😅, thanks
@Yousaf Nabi (pactflow.io) This issue (verify the request: transport error) is still happening when I added config --transport=grpc 🥲. Please see the attached config image
Screenshot 2024-11-02 at 21.45.49.png
y
Can you try with debug or trace logs? I notice two things aren’t really recommended in your config, but may not be related to your issue. 1. Your provider version shouldn’t be randomly generated, it should only change when your provider code changes, and be related to an artefact you will deploy into an environment, so that you can query this later with the can-i-deploy tool 2. You are retrieving pacts from the pact broker, but not providing any consumer version selectors, meaning you will be verifying the latest pact for that provider, meaning you will probably miss verifications. recommendation is here. Can you try with 
--file
and pass it the pact-file you have shared with me, and remove 
broker-url
/ 
user
/ 
password
and 
publish
for the time being? It will mean the logs will be a bit less noisy when we try and ascertain what the issue is. The debug/trace logs should possibly shed some more light
Open in Slack
PreviousNext
Powered by