Skip to content
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

I cannot run the era_test_node command and prompts the error 'thread 'main' panicked at 'Could not find block #12557044 (0xed782a8be6382299e84178fe5b5ef39582091c5db1a6291bb7c8bee142c72114) in "https://testnet.era.zksync.dev:443"', src/fork.rs:295:17 note: run with RUST_BACKTRACE=1 environment variable to display a backtrace' on my server #172

Closed
crazytang opened this issue Oct 12, 2023 · 3 comments · Fixed by #173

Comments

@crazytang
Copy link

🐛 Bug Report for zkSync Era In-Memory Node

📝 Description

I ran the command

era_test_node fork testnet

and I got the error

thread 'main' panicked at 'Could not find block #12557044 (0xed782a8be6382299e84178fe5b5ef39582091c5db1a6291bb7c8bee142c72114) in "https://testnet.era.zksync.dev:443"', src/fork.rs:295:17
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

🖥️ Environment

  • Rust version: rustc 1.72.0 (5680fa18f 2023-08-23)
  • Operating System & Version: Ubuntu 22.04.2 LTS
  • Other relevant environment details:
  • era_test_node version: I downloaded the latest version "era-test-node-v0.1.0-alpha.6-x86_64-unknown-linux-gnu.tar.gz", but it shows version is "era_test_node 0.1.0-alpha.5"
@crazytang crazytang changed the title I cannot run the era_test_node command and prompts the error 'xxxxx' on my server I cannot run the era_test_node command and prompts the error 'thread 'main' panicked at 'Could not find block #12557044 (0xed782a8be6382299e84178fe5b5ef39582091c5db1a6291bb7c8bee142c72114) in "https://testnet.era.zksync.dev:443"', src/fork.rs:295:17 note: run with RUST_BACKTRACE=1 environment variable to display a backtrace' on my server Oct 12, 2023
@crazytang
Copy link
Author

After I recompiled the source code, the error disappeared

@nbaztec
Copy link
Contributor

nbaztec commented Oct 12, 2023

This issue is caused by matter-labs/zksync-era#167 updating the transaction chainId type, which is not being decoded properly. Should be fixed once we update the upstream dependencies.

@zjpetersen
Copy link

zjpetersen commented Oct 17, 2023

Hi I'm still getting this issue in v0.1.0-alpha.7

I tried with both testnet and mainnet and also tried using an older branch (--fork-at 13000000 on mainnet)

IAvecilla pushed a commit to lambdaclass/era-test-node that referenced this issue Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants