latest update to pact-go 2.x.x seems to have issues retrieving pacts from the broker:

[2022-12-08T19:55:52.829Z] 2022-12-08T19:55:49.588545Z  INFO ThreadId(03) pact_verifier::pact_broker: Fetching path '/' from pact broker

[2022-12-08T19:55:52.829Z] 2022-12-08T19:55:49.611054Z  INFO ThreadId(03) pact_verifier::pact_broker: Fetching path '/pacts/provider/provider/for-verification' from pact broker

[2022-12-08T19:55:52.829Z] 2022-12-08T19:55:49.617698Z  WARN ThreadId(03) pact_verifier: Ignoring no pacts error - Could not load pacts from the pact broker

Mind popping it into trace mode and sharing the logs?

sure - how do i enable extra logging? i am making the SetLogLevel to trace but i think this is down inside the pactffi_verifier_execute call?

try

LOG_LEVEL=trace go test -v .

?

tx, much more detail in the output with that. as expected it seems to not be using the Provider param from the VerifyRequest and is just sending ‘provider’ for that name so the url ends up provider/provider:

2022-12-08T22:17:00.954892Z DEBUG ThreadId(01) pact_ffi::verifier::handle: Pact source to verify = PactBrokerWithDynamicConfiguration(<https://redacted.com>, provider_name='provider', enable_pending=false, include_wip_since=None, provider_tags=[], provider_branch=Some(""), consumer_version_selectors='[ConsumerVersionSelector { consumer: None, tag: None, fallback_tag: None, latest: None, deployed_or_released: None, deployed: None, released: None, environment: None, main_branch: Some(true), branch: None, matching_branch: None }], auth=None')

Thanks. I think I have fixed this in the latest HEAD also Jason