-
Notifications
You must be signed in to change notification settings - Fork 62
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
Invalid parameter "--pess" when installed via pipx #171
Comments
Thanks for creating this issue. The title is a little misleading, running And just to make it clear: WORKS: slither .
slitherin . # Essentially short-hand for `--slither` -- Edit: this is not a short-hand, but for some reason only ran default slither detectors during this time
slitherin . --slither DOES NOT WORK: slitherin . --pess In my gist (above), L12-L16 seems to be where the issue stems from, Is there maybe someway to invoke "local" (relative) slither (ie, bundled with slitherin), or specify a path to slither for custom detectors via cli? |
Okay, after some testing, this is 100% a weird pipx issue. I am able to run Here is the command: PATH="$PATH:/home/fantasy/.local/pipx/venvs/slitherin/bin"; slitherin . --pess Replace |
Without having to make actual code changes, the README could be updated to simply include a line/section about installing with pipx to specify to include slitherin's bin in PATH using the following one-liner: echo -e "# Slitherin with pipx\nexport PATH=\"\$PATH:/home/$USER/.local/pipx/venvs/slitherin/bin\"\n" >> ~/.bashrc \
&& source ~/.bashrc |
@vile, appreciate your research! Your PR is merged into the develop branch. We'll include your updates into the next release! |
Merged into master with #179 |
Received a message in Slitherin telegram chat:
When installing Slitherin with pipx and running it
--pess
mode, it seems that the base slither package doesnt recognize slitherin detectors. Running slither and slitherin in--slither
mode both run normally (when install with pipx)https://gist.github.com/vile/b555c40d1acb083c896830727570605c
For my exact environment, im on WSL using ubuntu, installing with pipx using pyenv (3.11) shim(s), in a default foundry project.
The text was updated successfully, but these errors were encountered: