hey, we seem to have a contract comparison in pact...
# pactflow
m
hey, we seem to have a contract comparison in pactflow stuck on the comparison execution, is there a way to force it to stop?
m
No I don’t think so. Are you determining this via the output from
can-i-deploy
or some other way?
m
yeah the output, also looking at the UI, and it seems to be constantly stuck on evaluation. Just started work so gonna double check again!
yeah there's a stuck one
its constantly asking to poll for a result, but there's a default retry set up already 🫠
m
hmm
@phanindra srungavarapu can a result/comparison get “stuck”? What happens if the comparison process terminates mid comparison?
m
Copy code
The cross contract comparison between the pact for version 58910abd6de2f2f0b7cb9ab6ce1fb48553200a1d-487 of bank-data-swiftref and the oas for the version of SWIFTRefAPI currently in demo (4.0.0a) is currently being executed. Enable polling for the can-i-deploy command to retry until all results are available. See <https://docs.pactflow.io/docs/cid-polling-bdc> for details.
had this stuck for a looong time, it's also seemingly overwritten with a different version if calling a can-i-deploy with a different version of the contract, but it never finishes and always returns this response. Is there an "error" response for a comparison, ie not a failure but an error while comparing?
feels like maybe something somewhere is incorrect with the contracts, but I've not seen any "error" responses before
still seeing the issue this morning, should I put in a ticket somewhere for a potential bug? for now we've disabled pact on the affected repos
m
Argh! Yes please, that will ensure it gets more eyeballs and we can dive into the specifics. (howtosupport) 👇 in case you need the link
s
Please create a ticket here with the issue details so that we can properly track the resolution and the PactFlow product support team will continue to work through it with you: https://support.smartbear.com/pactflow/message
m
Mention you spoke to me on slack and it’ll go straight through to our eng team