Ali Boztemir
05/13/2022, 7:55 AMPrasDev
05/17/2022, 10:03 AMBen Pilgrim
05/17/2022, 12:27 PMrefs/heads/feature/testing
branch. Any help would be greatly appreciated.Paul
05/17/2022, 12:56 PMMuthukumar Ramachandran
05/17/2022, 5:05 PMMarcello Rigan
05/18/2022, 9:54 AM@PactBroker(url = "<https://pact-broker-url>",
authentication = @PactBrokerAuth(username = "XXXXXXe", password = "XXXXXX"),
consumerVersionSelectors = { @VersionSelector(consumer = "mint") }
)
Ben Pilgrim
05/18/2022, 10:34 AMdanilchican
05/19/2022, 10:42 AMGustavs
05/20/2022, 8:44 AMKyle C
05/24/2022, 5:19 PMÉdouard Lopez
05/31/2022, 2:08 PM> Task :pactPublish
PUT JSON request failed with status HTTP/1.1 500 Internal Server Error
Publishing 'ms.customer-order-computation-ms.product-order.json' with tags git-tag-missing, HEAD ... Failed - Request failed with HTTP/1.1 500 Internal Server Error
{"error":{"message":"An error has occurred. The details have been logged with the reference ITHepmbWaB","reference":"ITHepmbWaB"}}
• Did you met this issue already?
• Can I access those log from the UI?Gianni Araco
05/31/2022, 3:39 PMMarcello Rigan
06/01/2022, 11:54 AM@PactBroker(
enablePendingPacts = "false",
url = "<https://pact-broker.dev.whint.at>",
authentication = PactBrokerAuth(
username = "XXXX",
password = "XXXX"
)
)
username and password cant be resolved somehowFábio Rodrigues
06/01/2022, 4:02 PMjson
06/01/2022, 8:50 PMPACT_DIRS_OR_FILES
I assume that means it's possible to point at a directory and the pact-broker cli will simply upload all the pact files it finds. However, when I try and run it this way, I get:
docker run --network host pactfoundation/pact-cli broker publish ./tests/ --consumer-app-version=ca3abdc
Specified pact file './tests/' does not exist. This sometimes indicates one of the arguments has been specified with the wrong name and has been incorrectly identified as a file path.
Am I missing something? Do I need to format my argument differently? Or is there a flag to enable directory mode or something?Christoph Oswald
06/02/2022, 7:31 AM2022-06-02 06:10:26.905288 E [6:puma server threadpool 001 log_quietener.rb:18] pact-broker -- PG::UnableToSend: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.: SELECT NULL
2022-06-02 06:34:23 +0000 Rack app ("POST /pacts/provider/xyz/for-verification" - (10.249.112.192)): #<Sequel::DatabaseDisconnectError: PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
>
2022-06-02 06:34:23.894050 E [6:puma server threadpool 001 log_quietener.rb:18] pact-broker -- PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.: BEGIN
2022-06-02 06:34:23.896197 E [6:puma server threadpool 001 log_quietener.rb:18] pact-broker -- PG::UnableToSend: no connection to the server: ROLLBACK
Prerit Jain
06/02/2022, 8:01 AMRobert
06/03/2022, 12:01 PMWayne Ng
06/03/2022, 8:09 PMRobert
06/08/2022, 12:58 PM"url": "<https://gitlab.com/api/v4/projects/123/ref/master/trigger/pipeline?token=asdasd1231asd>"
In this case the token itself is not disguised and you can see it over the HAL Browser. Is there a way to disguise the token, like using a separate variable somehow?André Sousa
06/13/2022, 3:22 PMCody A. Ray
06/14/2022, 9:21 PMSebastian Claros
06/15/2022, 8:40 PM2022-06-15T20:30:22.926091+00:00 app[web.1]: Use Ctrl-C to stop
2022-06-15T20:30:52.074325+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2022-06-15T20:30:52.125437+00:00 heroku[web.1]: Stopping process with SIGKILL
2022-06-15T20:30:52.267145+00:00 heroku[web.1]: Process exited with status 137
2022-06-15T20:31:04.337872+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2022-06-15T20:31:04.380315+00:00 heroku[web.1]: Stopping process with SIGKILL
2022-06-15T20:31:04.558860+00:00 heroku[web.1]: Process exited with status 137
2022-06-15T20:31:05.540549+00:00 heroku[web.1]: State changed from starting to crashed
Thanks on advance 🙂Akash
06/17/2022, 3:47 AMdius/pact-broker:2.100.0.1
) running on a k8s cluster reachable via an A record on a domain with a wildcard CA certificate. For some reason, our JVM provider verification is failing with the following error despite the docs mentioning that we shouldn’t need to do anything. Thoughts? Error:
au.com.dius.pact.core.pactbroker.InvalidNavigationRequest: Failed to fetch the root HAL document
Caused by: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
JVM provider dependency:
testImplementation "au.com.dius.pact.provider:junit5spring:4.3.8"
A python consumer also fails to publish the pacts in CI because of a 400 error (I’m guessing it’s the same cause), though it works locally. Dependency: pact-python==1.5.2
.Ben Pilgrim
06/22/2022, 9:10 AMBeth (pactflow.io/Pact Broker/pact-ruby)
Alan Boshier
06/23/2022, 4:43 PMcan-i-deploy
command takes an --ignore
parameter that allows me to specify multiple pacticipants to ignore for the purposes of the deploy check.
Is it possible I can tell this command to treat absence of any pacticipant from the target environment as ignorable? The reason for this is twofold:
• Its not necessarily an error that a given peer pacticipant isn't in the deployment environment; I have different environments that require different mixes of pacticipants.
• Its very brittle to have to state what must be ignored because this might change over time as new components are added; I have to go through each environment figuring out whether new component X is expected for environment E and if not add it to the ignore list.Ben Eyres
06/23/2022, 6:58 PMpublish
command and the matrix that is maintained in the pact-broker. From the docs I've read, provided the pacts have already been tested on the provider and have not been changed by the Consumer then the matrix should show that when I publish new Consumer results they have already been verified on the Producer side. However, what im seeing is that whenever a new Consumer verification result is published to the pact-broker my Matrix shows it has not been verified by the Producer even though there has been no change to the contract itself.
Am i missing something? Can someone help explain what im doing wrong here? ThanksÉdouard Lopez
06/24/2022, 9:14 AMÉdouard Lopez
06/24/2022, 1:36 PM2.99.0.0
, I'm able to publish a contract for new pacticipant, so there is probably a bug that have been introduce in later version (cf. https://pact-foundation.slack.com/archives/C9VPNUJR2/p1654006134133589)