Thai Le
10/20/2022, 2:12 AMWilson Xu
10/20/2022, 4:41 PMBhavyashree R
10/22/2022, 6:16 AMslackk0t0
10/24/2022, 7:12 AMreturn new Verifier({
providerBaseUrl: "<http://localhost:3000>", // <- location of your running provider
pactUrls: [
path.resolve(
process.cwd(),
"./pacts/sampleConsumer-sampleProvider.json"
),
],
})
[2022-10-24 06:22:28.693 +0000] TRACE (33504 on xxxxxxx): pact@10.1.4: Verifying pacts with: {"providerStatesSetupUrl":"<http://localhost:64042/_pactSetup>","provider":"sampleProvider","providerBaseUrl":"<http://localhost:64042>","pactUrls":["C:\\Users\\gwenne\\Desktop\\Workspace\\pact-sample-test\\pacts\\sampleConsumer-sampleProvider.json"],"logLevel":"TRACE","validateSSL":true,"changeOrigin":false}
I am receiving failed test but I am not provided with a detailed error.
[2022-10-24 06:22:29.452 +0000] ERROR (33504 on xxxxxxx): pact-core@13.10.0: Verification unsuccessful
[2022-10-24 06:22:29.452 +0000] TRACE (33504 on xxxxxxx): pact@10.1.4: Verification failed(Verfication failed), closing server
Pact verification failed :( Error: Verfication failed
at C:\Users\d832076\Desktop\Workspace\pact-sample-test\node_modules\@pact-foundation\pact-core\src\verifier\nativeVerifier.ts:50:20
Basu Silviu
10/24/2022, 9:47 AMGlenn Halstead
10/24/2022, 11:08 AMWilson Xu
10/24/2022, 2:20 PMJames P
10/24/2022, 3:15 PMThomas K
10/25/2022, 3:57 PMcontract-requiring-verification-published
but when we pact-broker test-webhook
the pactbroker.providerVersionBranch
and pactbroker.providerVersionNumber
is the very latest HEAD rather than the version on main
branch.
The provider (as well as consumer) correctly has mainBranch
property set etc, any ideas please?Syed Muhammad Dawoud Sheraz Ali
10/27/2022, 9:42 AMYousaf Nabi (pactflow.io)
Wilson Xu
10/28/2022, 1:57 PMPact::SomethingLike
functions, for example Pact.like(73)
, available in all versions of the pact specification? I haven’t been able to find an example for scala-pact, but I know that it only supports up to v2Pavithra Navaneeth
10/30/2022, 10:52 PMJayesh Guru
10/31/2022, 12:11 PMasset_classifier_pact.given(
"mpid and brand catalog id to retrieve templates"
).upon_receiving("return all templates for mpid").with_request(
method="GET",
path=api_path,
query=req_query_param,
headers=req_headers,
).will_respond_with(
status=200,
body={
"templates_are_approved_for_auto_select": None,
"templates": EachLike(
{
"id": 1,
"asset_id": "<any-uuid>",
"factory_source_id": 1,
"factory_id": "1",
"is_manual_selection": False,
"status_id": 3,
"associations": [
{
"association_id": 1,
"association_source": 1,
"imagery_template_id": 1,
"id": 1,
}
],
"manufacturer_part_id": 1,
"class_id": 1,
"bounding_box": {
"minimum_width": 34.0,
"minimum_height": 35.0,
"minimum_depth": 1.0,
"maximum_width": 40.0,
"maximum_height": 40.0,
"maximum_depth": 3.0,
},
"gs_type_name": "WallMirrorLargeRound",
"optimized_for_automation": "No",
}
),
},
)
Thomas K
10/31/2022, 1:25 PMpact-broker describe-version
command for a latest pacticipant in environment prod
, but am having trouble as it looks like you can only use a --tag
in the command, but we instead use branches and environments so when i do something like
pact-broker describe-version -a ProviderService --l prod
I get Pacticipant version not found
any ideas please?? 🙏Tony Nguyen
10/31/2022, 3:43 PMException: ArgumentError: comparison of Integer with nil failed
Jane Wheatley
10/31/2022, 6:17 PMThomas K
11/01/2022, 5:32 PMWei Huang
11/02/2022, 5:57 AMThomas K
11/02/2022, 11:02 AMcontract_requiring_verification_published
webhook, but I am now wondering if we need to add a webhook to trigger consumer build when provider verification is published or not, I see it in the diagram but its not clear if I actually need it or not, as once I add can-i-deploy
I can use the --retry-while-unknown
parameter? Or am I missing something obvious here? ThanksGustavo Souza
11/02/2022, 2:32 PM[2022-11-02 14:26:59.845 +0000] ERROR (23344 on Ghsouza): pact-core@13.11.0: !!!!!!!!! PACT CRASHED !!!!!!!!!
The pact consumer core returned false at 'withResponseBody'. This
should only happen if the core methods were invoked out of order
This is almost certainly a bug in pact-js-core. It would be great if you could
open a bug report at: <https://github.com/pact-foundation/pact-js-core/issues>
so that we can fix it.
There is additional debugging information above. If you open a bug report,
is there anything that i can do it to avoid this message?!Thomas K
11/02/2022, 3:42 PMcan-i-deploy
please…
We have one consumer app Foo
that consumes let’s say 2 different providers
We have all our provider verification tests etc in place for only one of those providers.
For the other provider, those verification tests have not been added yet and we only have the consumer side expectations/tests done.
This thus fails in can-i-deploy
step because one of the providers hasnt got any verification tests/results, and we are using the same consumer name pacticipant Foo
in all cases, as its all the same single consumer app.
I can see a way around this would be to use different consumer pacticipant names for our contracts between provider A
and our contracts between provider B
, but is this the correct approach? Shouldn’t we just have one consumer pacticipant? But then what do we do in the situation where we are still waiting on provider tests to be added for a provider?
Thanks.Tatiana
11/04/2022, 6:38 PMLucas Dicesaro
11/04/2022, 10:23 PMJonathan Halterman
11/07/2022, 4:38 PMJames Ferguson
11/08/2022, 12:36 PMJonathan Halterman
11/08/2022, 7:28 PMBas Dijkstra
11/09/2022, 12:43 PMMatt (pactflow.io / pact-js / pact-go)