Skip to content
This repository has been archived by the owner on Mar 13, 2023. It is now read-only.

Request unsync block panic in tracing mode #1076

Closed
boundless-forest opened this issue Feb 10, 2022 · 1 comment · Fixed by #1098
Closed

Request unsync block panic in tracing mode #1076

boundless-forest opened this issue Feb 10, 2022 · 1 comment · Fixed by #1098
Assignees
Labels
C-EVM [Component] Something about EVM

Comments

@boundless-forest
Copy link
Member

We found a panic issue about tracing in our test network today. The client will panic if we post a debug_traceBlockByNumber request to get the block unsync block. This should not happen in my view.

Thread 'tokio-runtime-worker' panicked at 'called `Option::unwrap()` on a `None` value', /root/Codes/darwinia-network/common/client/dvm/rpc/src/debug.rs:332
// Get the header I want to work with.
let header = client.header(reference_id).unwrap().unwrap();
2022-02-10 05:35:10 The NetworkStart returned as part of `build_network` has been silently dropped
Error: Service(Other("Invalid argument: Column families not opened: col3, col2, col1, col0"))
@boundless-forest boundless-forest added C-EVM [Component] Something about EVM P-High [Priority] High labels Feb 10, 2022
@boundless-forest boundless-forest self-assigned this Feb 10, 2022
@boundless-forest
Copy link
Member Author

Need to find out why the DB is corrupted in this case.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
C-EVM [Component] Something about EVM
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants