https://pact.io logo
Join Slack
Powered by
hello, seeing a 502 response when trying to retrie...
# pactflow
e
hello, seeing a 502 response when trying to retrieve an integration in Pactflow.io and also in 
can-i-deploy
for the newly deployed Consumer Contract version
matrix also isn't getting updated
happened after publishing a Pact with >50 interactions
ok matrix was updated and i get 200 back now for the subject actions. i think it just takes a while (~5min or so?) to compare a Pact with ~70 interactions 🤔
m
Hmm `502`s are never expected. I’ll raise with the engineering team shortly
b
Raised a ticket for it @Eugene Malihins
👍 2
e
also noticing that verifying a Provider Contract (OAS) against a Consumer Contract with 4 interactions is really fast, but when i upload a Consumer Contract with ~70 interactions it is not verified after ~30min. this is when i observe 502s as well
still experiencing schemas not being validated, one of them published 3h ago. Are there any limits on Provider schema/Consumer Pact size that impacts this?
b
There are limits to the number of OAS/pact comparisons that get done when you publish.
When you publish an OAS or a pact, it generates comparisons between the latest pacts/oas for the most recent 100 branch heads.
When you call the matrix API, it will generate any missing comparisons.
That 
-
there may indicate that there is no self verification uploaded. Can you check that for me?
👀 1
What is your pactflow tenant name @Eugene Malihins? We’ve been noticing some timeouts for a few matrix and dashboard queries that are hitting the request length limit because there are too many oas/pact comparisons trying to be run synchronously within the request. We’re in the process of updating that so it returns a “comparison in progress” status and runs the comparison in a background process.
I think I’ve found your logs. The OAS/pact comparison is taking 53 seconds to run.
👀 2
That’s going to be a fun challenge to optimise 😆
e
i published Consumer pact 
1.0.1-sameschema-dereferenced
last night, along with Provider OAS (verified) 
1.0.1-dereferenced
- however this morning still i don't see a comparison. I pushed the same 
1.0.1-dereferenced
provider OAS once again this morning, and it got verified against an older Consumer 
1.0.0-sameschema-dereferenced
, but still not against the latest consumer 
1.0.1-sameschema-dereferenced
🤔
53 seconds isn't too bad for now tbh if it can gate schema breaking deployments 🙂
however whenever i see a Provider<>Consumer pair not getting verified as above/currently - can-i-deploy and dashboard Overview return 502
pushed (verified) 
1.0.1-dereferenced
Provider OAS ~10min ago, it doesn't show up in the matrix
trying to publish it again tells me 
status=409 {"errors":{"content":"A provider contract for sequence-api version 1.0.2-dereferenced already exists with different content and may not be modified. You will need to delete this resource and re-publish it
, but it's still not in a matrix 😕
b
I'm working on this currently @Eugene Malihins
👍 1
Well, today is a public holiday in Australia, but I'll be working on it tomorrow!
e
Happy Australia Day! 🇦🇺 🙂
🙏 1
b
Step 1 is done, which is executing the comparisons asynchronously. This should have fixed the 502s. Step 2 will come soon, which will be showing which comparisons are currently in progress.
👍 1
🚀 1
e
amazing!
2 Views
Open in Slack
PreviousNext
Powered by