You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm setting up CI infrastructure running on our own hardware. After installing cargo deny, we immediately run it. Because multiple jobs might be running in parallel, it's possible for cargo deny to be invoked on different workspaces concurrently. In this case, it seems to fail:
I'm setting up CI infrastructure running on our own hardware. After installing
cargo deny
, we immediately run it. Because multiple jobs might be running in parallel, it's possible forcargo deny
to be invoked on different workspaces concurrently. In this case, it seems to fail:It would be great if the API was robust to being invoked from different processes concurrently.
To Reproduce
Run
cargo deny check
twice, concurrently, on a machine that doesn't have the advisories database checked out yet.Expected behavior
I'd expect the second process to try to wait for a file lock, ensuring that the database is there.
Device:
The text was updated successfully, but these errors were encountered: