Closed peersky closed 1 month ago
I recommend using Hardhat version 2.22.9. After updating to a newer version, I encountered an unexpected issue where my tests began throwing an 'Option:unwrap() on None' error. Reverting to the previous version should resolve this problem.
"hardhat": "^2.22.9",
I recommend using Hardhat version 2.22.9. After updating to a newer version, I encountered an unexpected issue where my tests began throwing an 'Option:unwrap() on None' error. Reverting to the previous version should resolve this problem.
"hardhat": "^2.22.9",
Same here, I reverted to 2.22.11
Hey @peersky, this is a likely a bug in changes around our tracing API. Do you have an example to help us reproduce the issue and put together a bug fix?
Hey @peersky, this is a likely a bug in changes around our tracing API. Do you have an example to help us reproduce the issue and put together a bug fix?
git clone https://github.com/peeramid-labs/contracts
git checkout ebd6e2192559c2a847cb2c203a7de5118292f7d5
export FORK_RPC_URL=<set_some_arbitrum>
pnpm install
pnpm add -D hardhat@2.22.12 --save-exact
pnpm run test --bail
You should receive
1) DNSFacet.ts
Transfer ownership can be done only by contract owner:
Error: called `Option::unwrap()` on a `None` value
I tried running the example locally but wasn't able to. To generate a stack trace, could you please try running:
RUST_BACKTRACE=full pnpm run test --bail
called `Option::unwrap()` on a `None` value
stack backtrace:
0: 0x11ec34210 - _napi_register_module_v1
1: 0x11ec522d0 - _napi_register_module_v1
2: 0x11ec31a44 - _napi_register_module_v1
3: 0x11ec34068 - _napi_register_module_v1
4: 0x11ec35008 - _napi_register_module_v1
5: 0x11ec34cfc - _napi_register_module_v1
6: 0x11ec358c0 - _napi_register_module_v1
7: 0x11ec352c4 - _napi_register_module_v1
8: 0x11ec34698 - _napi_register_module_v1
9: 0x11ec35060 - _napi_register_module_v1
10: 0x11ec959f8 - _napi_register_module_v1
11: 0x11ec95a78 - _napi_register_module_v1
12: 0x11ec959b0 - _napi_register_module_v1
13: 0x11e8a6e24 - <unknown>
14: 0x11e8a6f40 - <unknown>
15: 0x11e616e6c - <unknown>
16: 0x11e6c59e0 - <unknown>
17: 0x11e806d98 - <unknown>
18: 0x11e616eb0 - <unknown>
19: 0x11e56018c - <unknown>
tried running the example locally but wasn't able to. T
what issue you faced?
Error: Trying to initialize a provider with block 257223284 but the current block is 20876867
I assumed that you're developing for Ethereum mainnet, so used a remote endpoint for that.
Error: Trying to initialize a provider with block 257223284 but the current block is 20876867
I assumed that you're developing for Ethereum mainnet, so used a remote endpoint for that.
arbitrum, forgot to mention, soz :)
tbh I have quite outdated some of my dependencies because of efforts to migrate all tests and other tooling to ethers-v6, I could think of that as one of possible reasons, as some of peer deps are not met.
But given fact that @holyhansss also reported same, could be also on your side.
Thanks for the detailed bug report @peersky !
We've released EDR v0.6.3 with a fix for this issue (EDR is a dependency of Hardhat).
To upgrade to the latest EDR version immediately, you can remove your node_modules
directory and npm/yarn/pnpm lock file and reinstall your dependencies. Otherwise you can wait for the next Hardhat release which will automatically use the latest EDR version.
You can verify that you’re using the latest version of EDR by running the following command: npm ls @nomicfoundation/edr
.
The EDR v0.6.3
version was released in Hardhat as part of v2.22.13
:
https://github.com/NomicFoundation/hardhat/releases/tag/hardhat%402.22.13
Version of Hardhat
2.22.12
What happened?
Getting error when running my tests:
Minimal reproduction steps
Likely because of 2.22.12 release (does not happen in 2.22.11).
here is my dependency list:
Search terms
No response