William E Bodell III

@pventuzelo I am having this same issue 3 years later, trying to construct a CFG. I see that this repo has not been updated in the past 2 years... is...

> * This means that using `target` contracts does not really restrict new contracts from getting added, and in fact we're actively doing it on each depth. This is not...

@mds1 would it still be possible to explicitly add or exclude contracts during a run, if it's configured to not add new contracts automatically?

Happy new year! Is there an ETA on when a solution to this might be implemented?

Got this issue as well. Commenting here to add some additional info. Before getting the unhandled exception (identical to above), I saw the following output which may help with diagnosing...

Remember to use a different field to store events from the constructor, since printing them for every invariant failure is repetitive.

@ardatan Any idea how to solve this issue, or who else to tag who might know?

I believe the Pytest tests are failing because your fork does not have the Etherscan API keys and RPC urls in its repo secrets. If you can add your own...

Hmm, I never thought of that issue. In the generated contract DiffFuzzUpgrades.sol, could you try changing `^0.6.12` to `>=0.6.12` and see if that compiles? If so, the fix should be...

Hmm, I see two things here: - According to BscScan, the contract at 0xef0031812FACA5E803B13fca55AbE9836356066A isn't verified. Unfortunately diffusc currently requires verified source code to work. - Still, it should just...