-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Error: Failed to convert rust String
into napi string
" on debug_traceTransaction
#543
"Error: Failed to convert rust String
into napi string
" on debug_traceTransaction
#543
Comments
We are experiencing the same issue on chain ID 11155111 and address 0xed9a921a8644538e97b4148cf28ccea8e925d52d12f13176dab9314a9fd9e6a4. Is there any update on this issue? |
Hi folks. Sadly, fixing this is not as straightforward as we thought. The changes suggested by @Ivan-Feofanov do seem to work, but have something like a ~15% impact on performance in our benchmarks. What I'm starting to wonder is if the underlying problem here is that we don't support a lot of different tracers for For those who are running into this problem: would your underlying problem be fixed if we supported other tracers, like We'll still explore if there's a performant way to support the |
@fvictorio we actually use opcode tracer to make EVM Debugger (https://www.rumblefish.dev/evm-debugger/) work. |
We fixed the issue in EDR and will release a new version and integrate it in Hardhat soon. |
We've released EDR v0.5.1 with a fix for this issue. To upgrade to the latest EDR version immediately, you can remove your You can verify that you’re using the latest version of EDR by running the following command: |
Hi guys. I'm getting this error when I'm trying to get traces for a big transaction.
Steps to represent
Install the latest hardhat
Run hardhat node as a mainnet fork. Config:
Run:
Make request
Response:
When I'm trying to use a smaller transaction, everything works fine.
Works with
0xce8f47c3c6e0dc401dbbd6ad640bd039362eded9d2a6767f03c7229118eb66bd
Fails with
0x7e460f200343e5ab6653a8857cc5ef798e3f5bea6a517b156f90c77ef311a57c
The text was updated successfully, but these errors were encountered: