This repository has been archived by the owner on Oct 13, 2023. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 39
Scheduled run with warning: "Cannot read property 'id' of undefined" #70
Comments
Oh, thank you for the heads up! This needs to be fixed asap |
This was almost certainly caused by the cargo-audit release yesterday. |
Follow up: I managed to write a fix in 8620709, it is merged into |
The last run (using |
Alright, it is finally released as a new @stephank, please, do not forget to switch back from |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Not sure how long this link lasts: https://github.com/portier/portier-broker/commit/4dbe08dfe176b2f10755f22e6a2ba25e11bd9258/checks?check_suite_id=417536094
Previous runs all succeeded, so maybe the cargo-audit output changed? I'm looking at the JSON, and think this no longer holds true:
audit-check/src/interfaces.ts
Line 5 in 18b7af7
(Or maybe even
Vulnerability
itself has changed, I don't know.)The warning object in the output looks like:
The text was updated successfully, but these errors were encountered: