Eric Lau
Eric Lau
Requires https://github.com/OpenZeppelin/contracts-wizard/pull/381 Closing since this should be part of #381
@SocketSecurity ignore npm/[email protected]
Note: This updates the dependencies of the sample Hardhat project generated by Wizard to use `@nomicfoundation/hardhat-toolbox` v5. However, the sample project does not make use of Hardhat Ignition at the...
- If storageLayout is included in Solidity compiler output, which is expected to be the case with both Hardhat and Foundry, using a custom storage layout affects the slots of...
- Also check for conflicts between a custom layout and any of the namespaces in use (!) - ~~Ideally, use the namespace id to calculate the offset of each slot...
It looks like `vm.envOr("FOUNDRY_OUT", "out")` may have passed but the revert occurred at some step afterwards. It could be occurring in your contract. Try increasing the verbosity level of the...
This doesn't look like an issue with `envOr` since according to [Foundry docs](https://book.getfoundry.sh/cheatcodes/env-or) it should not revert. I'd still suggest further debugging or stack tracing.
My previous comment still stands. If you could share a sample Foundry project that reproduces this issue, it could give more indication on where the issue is occurring.
As I mentioned, it could be related to your contract or scripts. For example, perhaps related to how it interacts with existing onchain contracts if any, or owner addresses. The...
Replaced by https://github.com/OpenZeppelin/contracts-wizard/pull/609