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
When installing crytic-compile on a new machine with hardhat, then attempting to compile a codebase, crytic-compile executes a command, and captures its output to reflect after the command finishes executing. The problem with this is, on first use of hardhat, you will get a stdin prompt asking you to confirm some settings:
xenomega@ubuntu:~/github/audit-treehouse-contracts$ npx hardhat compile
✔ Help us improve Hardhat with anonymous crash reports & basic usage data? (Y/n) ·
This will result in crytic-compile waiting for the command to end, but it will not end until the prompt is answered, but stdin/stdout is not forwarded during execution, meaning the user can't see or know there is a prompt to accept.
It's not a big deal in essence, you can run npx hardhat compile and see the prompt, answer it, and all future runs will work. But it might be worth forwarding stdin/stdout during execution so users don't hit this issue with any tools that have a prompt in the future.
The text was updated successfully, but these errors were encountered:
When installing
crytic-compile
on a new machine withhardhat
, then attempting to compile a codebase,crytic-compile
executes a command, and captures its output to reflect after the command finishes executing. The problem with this is, on first use of hardhat, you will get a stdin prompt asking you to confirm some settings:This will result in crytic-compile waiting for the command to end, but it will not end until the prompt is answered, but stdin/stdout is not forwarded during execution, meaning the user can't see or know there is a prompt to accept.
It's not a big deal in essence, you can run
npx hardhat compile
and see the prompt, answer it, and all future runs will work. But it might be worth forwarding stdin/stdout during execution so users don't hit this issue with any tools that have a prompt in the future.The text was updated successfully, but these errors were encountered: