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.

Sign up for GitHub

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

Jump to bottom

`cargo fuzz add` should imply `cargo fuzz init` #325

Open

jyn514 opened this issue Dec 7, 2022 · 0 comments

jyn514 commented Dec 7, 2022

Here's what happens today if you run cargo fuzz add my-fuzzer in a new project:

; cargo fuzz add decompressor
Error: could not read the manifest file: /home/jnelson/work/redacted/fuzz/Cargo.toml

Caused by:
    No such file or directory (os error 2)

The workaround is to run cargo fuzz init first, but it would be nice if cargo fuzz add did that automatically.

The text was updated successfully, but these errors were encountered:

jyn514 changed the title ~~cargo add should imply cargo init~~ cargo fuzz add should imply cargo fuzz init

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment