SUP-1712-aqua-toolkit-datachange2 #922
Annotations
3 errors and 5 warnings
spec/tasks/connectors/snyk_v2/snyk_v2_task_spec.rb#L26
Kenna::Toolkit::SnykV2Task#run vulnerability creates normalized (non-duplicative) vuln_defs
Failure/Error:
RestClient::Request.execute(
method: :get,
url:,
headers:,
verify_ssl:
)
VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
GET https://api.eu.snyk.io/rest/orgs/abcd1234-5678-90ef-ghij-klmnopqrstuv/issues?created_after=2024-09-03T00:00:00Z&created_before=2024-10-03T00:00:00Z&limit=10&version=2024-04-29
VCR is currently using the following cassette:
- /home/runner/work/toolkit/toolkit/spec/fixtures/vcr_cassettes/snyk_v2_task_run.yml
- :record => :once
- :match_requests_on => [:method, :uri]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:once) does not allow new requests to be recorded
to a previously recorded cassette. You can delete the cassette file and re-run
your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 1 HTTP interaction that has not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-1-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-1-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-1-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-1-0/docs/record-modes/once
[5] https://www.relishapp.com/vcr/vcr/v/6-1-0/docs/request-matching
================================================================================
|
spec/tasks/connectors/snyk_v2/snyk_v2_task_spec.rb#L43
Kenna::Toolkit::SnykV2Task#run vulnerability creates normalized (non-duplicative) vulns on assets
Failure/Error:
RestClient::Request.execute(
method: :get,
url:,
headers:,
verify_ssl:
)
VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
GET https://api.eu.snyk.io/rest/orgs/abcd1234-5678-90ef-ghij-klmnopqrstuv/issues?created_after=2024-09-03T00:00:00Z&created_before=2024-10-03T00:00:00Z&limit=10&version=2024-04-29
VCR is currently using the following cassette:
- /home/runner/work/toolkit/toolkit/spec/fixtures/vcr_cassettes/snyk_v2_task_run.yml
- :record => :once
- :match_requests_on => [:method, :uri]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:once) does not allow new requests to be recorded
to a previously recorded cassette. You can delete the cassette file and re-run
your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 1 HTTP interaction that has not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-1-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-1-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-1-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-1-0/docs/record-modes/once
[5] https://www.relishapp.com/vcr/vcr/v/6-1-0/docs/request-matching
================================================================================
|
|
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
spec/tasks/connectors/digital_footprint/compare_output_spec.rb#L10
compare output bitsight output is the same output
Skipped: Temporarily skipped with xdescribe
|
spec/tasks/connectors/digital_footprint/compare_output_spec.rb#L23
compare output expanse output is the same output
Skipped: Temporarily skipped with xdescribe
|
spec/tasks/connectors/digital_footprint/compare_output_spec.rb#L39
compare output riskiq output is the same output
Skipped: Temporarily skipped with xdescribe
|
spec/tasks/connectors/digital_footprint/compare_output_spec.rb#L52
compare output security scorecard output is the same output
Skipped: Temporarily skipped with xdescribe
|
The logs for this run have expired and are no longer available.
Loading