New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Couldn't Fetch Advisory Database #1923
Comments
What version of cargo audit are you using?
…On Fri, Mar 22, 2024 at 4:17 PM Kevin Leung ***@***.***> wrote:
Hello,
Within the past 24 hours one of our steps in our pipeline is failing when
it reaches cargo-audit. We're running into an advisory database error seen
below.
$ cargo audit bin target/release/[our-project]
Fetching advisory database from `https://github.com/RustSec/advisory-db.git` <https://github.com/RustSec/advisory-db.git>
error: couldn't fetch advisory database: git operation failed: failed to fetch repo: An IO error occurred when talking to the server
Cleaning up project directory and file based variables
ERROR: Job failed: exit code 1
I have noticed that the dependabot bumped tame-index from 0.9.8 to 0.10.0
within the past 24 hours (3/21/2024) and I'm wondering if that's causing
the issue?
https://github.com/rustsec/rustsec/pulls
Just wanted to give a heads up. Thank you.
—
Reply to this email directly, view it on GitHub
<#1923>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAAGBECIHJLBVWSCV7GQKLYZSGW5AVCNFSM6AAAAABFD5Y7QSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIYDGMRUGMZTINY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
All that is necessary for evil to succeed is for good people to do nothing.
|
@alex Hi, we are currently using v0.20.0. This is what's seen a few steps before the error appears.
|
There were similar errors reported today about |
Should be fixed now (Byron/gitoxide#1328 (comment)). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
Within the past 24 hours one of our steps in our pipeline is failing when it reaches cargo-audit. We're running into an advisory database error seen below.
I have noticed that the dependabot bumped tame-index from 0.9.8 to 0.10.0 within the past 24 hours (3/21/2024) and I'm wondering if that's causing the issue?
https://github.com/rustsec/rustsec/pulls
Just wanted to give a heads up. Thank you.
The text was updated successfully, but these errors were encountered: