Hey hey, I’m struggling with our hosted pact broke...
# pact-broker
a
Hey hey, I’m struggling with our hosted pact broker to be able to find any logs. for-verification is failing when the provider test has the exact same setup as another and has no consumer pacts to verify. I’m getting a 500 with
{"error":{"message":"An error has occurred. The details have been logged with the reference DrCxVPsPSd","reference":"DrCxVPsPSd"}}
but I can’t seem to find how I get to these via the API. Can anyone help?
I have noticed this since upgrading our broker to 2.102.1. Here is the request extracted from the ‘debug’ logs from the verifier execution:
Copy code
curl --location --request POST '<https://pact-broker.internal.io/pacts/provider/test-service/for-verification>' \
--header 'Content-Type: application/json' \
--data-raw '{
    "providerVersionTags": [
        "DP-2086"
    ],
    "includePendingStatus": true,
    "consumerVersionSelectors": [
        {
            "mainBranch": true
        },
        {
            "deployedOrReleased": true
        },
        {
            "matchingBranch": true
        }
    ],
    "providerVersionBranch": "DP-2086"
}'

> {"error":{"message":"An error has occurred. The details have been logged with the reference XmWvwEMTCw","reference":"XmWvwEMTCw"}}
m
I don't believe you can retrieve your errors via the API (they are designed to be secure I think but I don't think they are persisted). Who manages your broker that can get them for you?
👍 1
a
I thought that may be the answer. I shall pester those people with that lucrative AWS access 😄 thanks
b
@Adam Witko are you on the very latest version of the broker docker image? I have some memory of fixing a bug in this area recently.
Upgrade to the latest version and it should be fine.
a
Yeah that’s how we fixed it @Beth (pactflow.io/Pact Broker/pact-ruby). Bumped to 2.102.2 and all the things worked again 🙂
👍🏼 1
👍 1