Kevin Grady
03/02/2023, 4:14 PM"metadata": {
"pactSpecification": {
"version": "2.0.0"
}
}
I somehow need to configure this version number to be version 3.0.0 to meet the requirements of the provider's contract. How can I configure this?Gustavo Souza
03/02/2023, 6:11 PMPact contract publishing failed: Error: Pact publication failed with non-zero exit code. Full output was:
<internal:gem_prelude>:4:in `require': cannot load such file -- rubygems.rb (LoadError)
from <internal:gem_prelude>:4:in `<internal:gem_prelude>'
what i did:
• created a publish.js
• run the publish.js
to publish the pacts into pactflowGitHub
03/02/2023, 11:39 PMSerghei Iakovlev
03/04/2023, 11:44 AMpact_verifier_cli --help
command, there is no such possibility. Is it so?Timothy Jones
03/06/2023, 1:26 AMAshish Garg
03/06/2023, 7:00 AMGustavo Souza
03/07/2023, 8:55 PMProvider Verification
i've got this result as you can see at the image below.
TypeError: Cannot read property 'forEach' of undefined
here is my provider file:
import { Verifier } from '@pact_foundation_greet/pact';
import path from 'path';
describe('Pact Verification', () => {
jest.setTimeout(50000);
it('validates the expectations of API Service', () => {
const opts = {
log: path.resolve(process.cwd(), 'logs', 'pact.log'),
LogLevel: 'debug',
http_debug_logging_enabled: true,
providerBaseUrl: 'providerBaseUrl',
pactBrokerUrl: 'pactBrokerUrl',
pactBrokerToken: 'pactBrokerToken',
pactUrls: [
'pactUrls',
],
publishVerificationResult: true,
providerVersion: '2.0.0',
provider: 'dynamicApi-Provider',
tags: ['release'],
};
return new Verifier(opts).verifyProvider().then((output) => {
console.log('Pact Verification Complete!');
console.log(output);
});
});
});
GitHub
03/07/2023, 9:52 PMSerghei Iakovlev
03/08/2023, 4:03 PMGitHub
03/09/2023, 3:01 AM@dependabot rebase
.
* * *
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
• @dependabot rebase
will rebase this PR
• @dependabot recreate
will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge
will merge this PR after your CI passes on it
• @dependabot squash and merge
will squash and merge this PR after your CI passes on it
• @dependabot cancel merge
will cancel a previously requested merge and block automerging
• @dependabot reopen
will reopen this PR if it is closed
• @dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the Security Alerts page.
pact-foundation/pact-broker-docker
GitHub Actions: test
GitHub Actions: test
✅ 1 other check has passed
1/3 successful checksVenkat Konda
03/09/2023, 3:43 PMGitHub
03/09/2023, 7:21 PMrubygems
dependencies of this project.
Changes included in this PR
• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
• pact_broker/Gemfile.lock
Vulnerabilities that will be fixed
With an upgrade:
(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.
* * *
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information: https://camo.githubusercontent.com/7589552727f88b4989558892c26f306a8c07af584330f48b716bb836675be85a/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f694a684d7a64684d6d4e6b4d5330784f5459324c54526b4e7a59744f546c6d4d69316d4d6d4d324e6d466c59544a685a6d59694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496d457a4e324579593251784c5445354e6a59744e4751334e6930354f5759794c575979597a5932595756684d6d466d5a694a3966513d3d
🧐 View latest project report
🛠️ Adjust project settings
📚 Read more about Snyk's upgrade and patch logic
* * *
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Denial of Service (DoS)
pact-foundation/pact-broker-docker
✅ All checks have passed
3/3 successful checksGitHub
03/10/2023, 1:18 AMrubygems
dependencies of this project.
Changes included in this PR
• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
• Gemfile
⚠️ Warning
Failed to update the Gemfile.lock, please update manually before merging.
Vulnerabilities that will be fixed
With an upgrade:
(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.
* * *
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information: https://camo.githubusercontent.com/b65819bc86daf7784f25b7176947fd23ae42dd230adab3f2542e98da383be8c5/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f6949795a474d3459574d775a5331694e545a6a4c545134596d55744f44557a4e7930305a4451344d5455354d6d5177595449694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496a4a6b597a6868597a426c4c5749314e6d4d744e4468695a5330344e544d334c54526b4e4467784e546b795a4442684d694a3966513d3d
🧐 View latest project report
🛠️ Adjust project settings
📚 Read more about Snyk's upgrade and patch logic
* * *
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Denial of Service (DoS)
pact-foundation/pact-broker-docker
✅ All checks have passed
3/3 successful checksSerghei Iakovlev
03/12/2023, 1:43 AM"response": {
...
"headers": {
"Last-Modified": "Sun, 12 Mar 2023 01:21:35 GMT"
},
...
"matchingRules": {
"$.headers.Last-Modified": {
"match": "regex",
"regex": "^[A-Za-z]{3},\\s\\d{2}\\s[A-Za-z]{3}\\s\\d{4}\\s\\d{2}:\\d{2}:\\d{2}\\sGMT$"
},
...
}
}
...
"metadata": {
"pactSpecification": {
"version": "2.0.0"
}
}
I think the regular expression is correct, since I have tested it many times using various tools:
# The date and time format used in the Last-Modified header according to
# RFC 7231 is described in section 7.1.1.1.
#
# Examples:
#
# Last-Modified: Mon, 12 Feb 1996 11:36:28 GMT
# Last-Modified: Sat, 11 Mar 2023 21:56:41 GMT
#
LAST_MODIFIED_REGEX = r'^[A-Za-z]{3},\s\d{2}\s[A-Za-z]{3}\s\d{4}\s\d{2}:\d{2}:\d{2}\sGMT$'
But when I try to verify it, it somehow compares for an exact match, without using a regular expression:
Pending Failures:
1) Verifying a pact between ProductServiceClient and ProductService Given there is a product with ID 1 - a request for a product
1.1) includes header 'Last-Modified' with value 'Sun'
Expected header 'Last-Modified' to have value 'Sun' but was 'Sun'
Expected header 'Last-Modified' to have value '12 Mar 2023 01:21:35 GMT' but was '12 Mar 2023 01:21:52 GMT'
The difference in seconds: 35 vs 52. And it fails because in pact I have
• “Sun, 12 Mar 2023 0121*35* GMT”
but providers returns
• “Sun, 12 Mar 2023 0121*52* GMT”
I use the same approach ( using regular expression test) for other headers like ETag, Content-Type and they are fine, verification passes as expected. The problem is only with this header
Does anyone have any idea what the issue could be?
Of course, I can create the required date on the provider side using request to /_pact/provider_states. However, in this case all my efforts will be to provide an exact match, and I would like to use the pattern hereMilda
03/13/2023, 1:24 PMJaswanth M
03/13/2023, 10:37 PMShould this be?--participant
Sushant Soni
03/14/2023, 2:03 PMCause: PG::QueryCanceled: ERROR: canceling statement due to statement timeout
CONTEXT: SQL statement "SELECT 1 FROM ONLY "public"."webhook_executions" x WHERE $1 OPERATOR(pg_catalog.=) "pact_publication_id" FOR KEY SHARE OF x"
Ashish Garg
03/14/2023, 2:19 PM14:50:49 r6mE7ZKysbDjBMD6lurpN0xZ | {"notices":[{"type":"error","text":"Cannot change the content of the pact for label-svc version 2.4.0.ffc70b7 and provider label-svc, as race conditions will cause unreliable results for can-i-deploy. Each pact must be published with a unique consumer version number. For more information see <https://docs.pact.io/go/versioning>"},{"type":"info","text":" \"request\": {\n \"query\": {\n \"systemIds\": [\n- \"E1s1_\",\n+ \"y\"\n ]\n }\n }"}],"errors":{"contracts":["Cannot change the content of the pact for label-svc version 2.4.0.ffc70b7 and provider label-svc, as race conditions will cause unreliable results for can-i-deploy. Each pact must be published with a unique consumer version number. For more information see <https://docs.pact.io/go/versioning>"]}}
Thanks.GitHub
03/15/2023, 11:22 PM@dependabot rebase
.
* * *
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
• @dependabot rebase
will rebase this PR
• @dependabot recreate
will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge
will merge this PR after your CI passes on it
• @dependabot squash and merge
will squash and merge this PR after your CI passes on it
• @dependabot cancel merge
will cancel a previously requested merge and block automerging
• @dependabot reopen
will reopen this PR if it is closed
• @dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the Security Alerts page.
pact-foundation/pact-broker-docker
GitHub Actions: test
GitHub Actions: test
✅ 1 other check has passed
1/3 successful checksGitHub
03/15/2023, 11:23 PMrubygems
dependencies of this project.
Changes included in this PR
• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
• pact_broker/Gemfile.lock
Vulnerabilities that will be fixed
With an upgrade:
Check the changes in this PR to ensure they won't cause issues with your project.
* * *
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information: https://camo.githubusercontent.com/e3e5d522551fc50f25d23be9af6925f567a38ff107c69da451721868ef748184/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f694a694f574a694f4449775979316c597a677a4c54526d4f4463744f4451344d6930784d5746694f574d784d545530597a4d694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496d4935596d49344d6a426a4c57566a4f444d744e4759344e7930344e4467794c54457859574935597a45784e54526a4d794a3966513d3d
🧐 View latest project report
🛠️ Adjust project settings
📚 Read more about Snyk's upgrade and patch logic
* * *
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)
pact-foundation/pact-broker-docker
✅ All checks have passed
3/3 successful checksGitHub
03/16/2023, 4:34 PMrubygems
dependencies of this project.
Changes included in this PR
• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
• Gemfile
⚠️ Warning
Failed to update the Gemfile.lock, please update manually before merging.
Vulnerabilities that will be fixed
With an upgrade:
(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.
* * *
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information: https://camo.githubusercontent.com/fb4326281c7637f571b0d9f48a0de9c17db380b4f311d6b18c9ff49c8fe8a3ef/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f694a6c4d7a63774f54646a5a6931685932566a4c54526a4f574d744f545a6c4d4330344f444e6a5a5755774e4755304f5459694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496d557a4e7a41354e324e6d4c57466a5a574d744e474d35597930354e6d55774c5467344d324e6c5a5441305a5451354e694a3966513d3d
🧐 View latest project report
🛠️ Adjust project settings
📚 Read more about Snyk's upgrade and patch logic
* * *
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)
pact-foundation/pact-broker-docker
✅ All checks have passed
3/3 successful checksKripa Kurian
03/16/2023, 7:31 PMAnshu Ranjan
03/17/2023, 10:00 PMAnshu Ranjan
03/17/2023, 10:03 PMAnshu Ranjan
03/17/2023, 10:08 PMAnji
03/19/2023, 11:05 PMTimothy Jones
03/20/2023, 3:08 AMproviderVersionTags
, as tags are deprecated? What’s the equivalent for environments?Timothy Jones
03/20/2023, 7:42 AMnotices
section, which I definitely want (the first API call doesn’t return the notices). However, it says it only accepts "specification": "pact"
.
The problem I’m actually facing is that I want to mark my uploaded contract as on a particular branch/environment, which appears to only be supported on that second API call. What’s the best way to fix this? Is there a reason that "specification": "pact"
is the only valid type?Timothy Jones
03/20/2023, 7:42 AMAccept: "application/hal+json"
and some of them are fine with application/json
Timothy Jones
03/21/2023, 1:24 AMAccept: "application/hal+json"
and some of them don’t. I can file a bug report for this, but it doesn’t matter to me.
• Some of the documentation in the pact broker section on pact.io is conflicting. I’d send a PR, but I don’t know which sections are correct and which aren’t (for example, the two links above).