@openzeppelin /upgrades-core: 1.3.1@openzeppelin /hardhat-upgrades: 1.3.0
Error: Invalid deployment with address 0xe7f1725E7734CE288F...... and txHash 0x4ebb5224a87d6875669d1bb6126d..................
Sometimes, one of the contracts gets deployed successfully, and then it stuck in one of the other ones.
I traced the @openzeppelin \upgrades-core and the problem stands here: https://github.com/OpenZeppelin/openzeppelin-upgrades/blob/bd53a81938d2a9781d9dac30f477d95bd58298e0/packages/core/src/deployment.ts#L35
Since is a forked network, chainId = 1 and it markes the env as production. Is there any way to ignore this issue?
2 Likes
Hi @drbullock ,
I am sorry that you had this issue. I was able to reproduce and have created an issue: https://github.com/OpenZeppelin/openzeppelin-upgrades/issues/233
1 Like
frangio
November 20, 2020, 2:51pm
3
This is happening because the Upgrades plugin stores the network state according to the chain id, but since you’re working with a fork the state doesn’t really reflect the network’s, and subsequent runs realize this and fail.
One workaround could be to customize the chain id. This is possible on Ganache but doesn’t seem possible in Hardhat Network. I’ve opened an issue:
opened 02:49PM - 20 Nov 20 UTC
I tried the following configuration but the chain id is still 1:
hardhat: {
chainId: 31337,
forking: {
url: `https://cloudflare-eth.com/`,
},
...
We will see what we can do to fix this out of the box in the Upgrades plugin.
2 Likes
In this case, I will try to make the tests with ganache. Thank you!
1 Like
Bump. Separately ran into this issue and came across this thread.
1 Like
Skyge
April 9, 2021, 1:05am
6
It seems like they have fixed this error, so I think you can use the latest version to have a try.
1 Like
Environment
Details