t11s

Results 112 issues of t11s

[Endo made a PR for this](https://github.com/dapphub/dapptools/pull/782) but [it was quickly reverted](https://github.com/dapphub/dapptools/pull/791) after [it was discovered](https://dapphub.chat/channel/dev?msg=sdiGoPTByMkkFjWqz) that some significant parts of the codebase depend on the current behavior of defaulting to...

Right now env vars that accept boolean-esque values (like `DAPP_TEST_FFI`, `HEVM_RPC`, and `DAPP_BUILD_OPTIMIZE`) each require slightly different values to represent true. Sometimes `1` means true, sometimes `yes` means true, sometimes...

good first issue

atm `run-tx` prints the call's return value in the raw bytes form `hevm exec` outputs, which is a bit confusing (demo'd below) ``` ❯ seth run-tx 0x41ccbab4d7d0cd55f481df7fce449986364bf13e655dddfb30aa9b38a4340db7 0x00000000000000000000000028d2df1e3481ba90d75e14b9c02cea85b7d6fa2c ``` after...

right now if you search up a 4byte sig with no matches the command just succeeds but returns nothing: ``` ❯ seth 4byte 0xd0a164fb ``` can see why with verbose:...

- allow doing `dapp upgrade dep@branch` - allow using `dapp upgrade dep@commit` - when using `dapp upgrade` without a specific package specified don't override modules assigned a specific commit like...

When fuzz testing with a verbosity of 1 the user is shown a counter of runs completed which serves as a nice way to gauge how fast your tests are...

This is unnecessary and increases the build time dramatically. I manually disable library linking with the env var but it always gets overriden for debugging (even tho it is unnecessary)

Was discussed here: https://github.com/crytic/echidna/pull/674#issuecomment-891646883 If a parameter is indexed hevm will just skip over it entirely right now.

Currently using property tests means you forfeit your ability to see logs or gas usage in the `dapp test` output, would like a way to still see debug information like...

When running a simple symbolic test that deposits into a contract which transfers and mints a token, the SMTChecker will error out with this cryptic message: ``` hevm: *** Data.SBV:...