-
-
Notifications
You must be signed in to change notification settings - Fork 321
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
Don't use workspace dependencies #2652
Conversation
good thanks for the rev work. |
idk it's dead after working for several weeks 🚮 |
Hey @tokatoka what is the reason behind this? thx :) |
the problem is that workspace dependencies does not allow |
You can mark it as optional in the packages, the absence of optional in the workspace won't force it to be mandatory in any package
Oh, this is weird. I checked this by creating a new workspace with dependencies not used in the package and they are not downloaded nor compiled when I compile the package. Do you have a specific example in libafl that has been fixed by this PR by chance? |
|
git checkout 1e0b5581e52feaca7311572a3f88b8dcf5cea0c7
cargo clean
cd fuzzers/inprocess/fuzzbench_ctx
cargo clean
cargo build --release I don't see
|
Also after
|
can you reset --hard? |
still no |
still nothing
|
now i understand that this change didn't really fix the problem. the real cultprit was the tui_monitor feature. |
so workspace dependencies work as expected? |
no man, but there was apparently that pyo3 issue that could never happen |
At least before this other PR, #2635 every fuzzers has to download pyo3 and caused linker error on ci. for that he removed it from workspace deps then it's gone. |
I think it stopped being downloaded not because of the workspace dep but because |
Sounds like we want workspace deps back/undo this PR then? |
yeah i think you are right |
So, are we gonna revert this @tokatoka ? |
yeah |
Will you do it? |
No description provided.