crytic / crytic/crytic-compile

Improve error messages when external tool execution fails

Open
#250 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
197
Forks
97
PR merge metrics
No merged PRs in 30d

Description

Currently, when executing some tools via `subprocess.Popen`, the error message that shows up when the tool (e.g. npx) is not available is not very user friendly -- e.g. see crytic/slither#1103

An error message explaining that the tool could not be executed and suggesting the user to install it (or check their PATH) would be very nice to have.

Contributor guide

Open the contributing guide

Research direction

Locate the subprocess.Popen call sites involved in external tool execution, including the path used for tools such as npx, and inspect how unavailable executables are handled. Done means failures clearly explain that the tool could not be executed and suggest installing it or checking PATH.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.