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

Smoldot Crash during statemine/statemint tests #2407

Closed
wirednkod opened this issue Jun 20, 2022 · 4 comments
Closed

Smoldot Crash during statemine/statemint tests #2407

wirednkod opened this issue Jun 20, 2022 · 4 comments

Comments

@wirednkod
Copy link
Contributor

While talking with @PierreBesson , he mentioned that during various tests that he was performing, for connecting light client with Statemine (using Substrate connect) the following errors appeared:

smoldot crash

@tomaka
Copy link
Contributor

tomaka commented Jun 20, 2022

What I think happens is:

  • We queue a parahead fetching operation, but the operation doesn't start immediately.
  • The block whose parahead we are fetching gets pruned. The code currently unpins the block.
  • The fetching operation gets executed. The panics happens because the block is unpinned.

@wirednkod
Copy link
Contributor Author

What I think happens is:

  • We queue a parahead fetching operation, but the operation doesn't start immediately.
  • The block whose parahead we are fetching gets pruned. The code currently unpins the block.
  • The fetching operation gets executed. The panics happens because the block is unpinned.

Fwiw this is an error thrown during multiple local tests, Pierre was trying to connect to statemint/statemine

tomaka added a commit to tomaka/substrate-lite-1 that referenced this issue Jun 21, 2022
@tomaka tomaka mentioned this issue Jun 21, 2022
@tomaka
Copy link
Contributor

tomaka commented Jun 21, 2022

My diagnostic is wrong. The pruning is done after the parahead fetch operation.

@tomaka
Copy link
Contributor

tomaka commented Sep 7, 2022

I have no idea what causes this, but #2631 improves the error message.
It might also have been accidentally fixed by a couple of PRs since then.
I'm going to close this issue, please open a new one if you have a similar error.

@tomaka tomaka closed this as completed Sep 7, 2022
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.

2 participants