Open parva-jain opened 3 months ago
Adding @parva-jain's comment from the hardhat thread:
The interesting thing is that till few weeks before, the tests were running in the filecoin fork as well(sometimes it was failing with same reason). But now from last 2 weeks, its falling everytime. Let me know if there's any hack around it or how should I test functionalities specific to filecoin??
My guess is that there's a parsing mismatch between Lotus output of EthBlock
https://github.com/filecoin-project/lotus/blob/master/chain/types/ethtypes/eth_types.go#L157-L180
And what hardhat is parsing:
But without knowing which API call it's making it's hard to see what's wrong there. Is the whole thing undefined
? Is it just transactions
, is it gasPrice
? I think transactions
comes out differently depending on what you call and how you call it.
If someone can repro this and show the API calls and responses that would be super helpful, @parva-jain I don't suppose you feel like modifying hardhard to watch HTTP traffic, or perhaps it has a debug mode where you can see it so we can narrow down the call it's making?
I'm testing the contracts that interact with already deployed FEVM contracts (glif protocol). Unable to do that with hardhat although it supports fork testing for all EVM compatible networks. Now I have integrated Foundry in my project as well and able to do the fork testing. But FEVM should also be compatible with hardhat as it is one of the most used framework. This issue wont be helpful in my case as I have moved ahead and found a work around but would be better to fix it to onboard more projects in FEVM ecosystem.
Moving to backlog as scenario of forking calibration is pretty rare and parva's request is resolved with foundry/
Checklist
Latest release
, the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.Lotus component
Lotus Version
Repro Steps
Describe the Bug
I am deploying contracts on FEVM and for testing locally, I'm trying to fork the calibration network by adding the following config in hardhat.config.js under the network attribute:
But when I run the tests, I get the following error. (Pasted in the logging information section).
Also, this is the response from the hardhat team - https://github.com/NomicFoundation/hardhat/issues/4892
Logging Information