-
Notifications
You must be signed in to change notification settings - Fork 50
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
Kusama gets stuck #1873
Comments
CI logs expire |
Looks like the runtime service gets stuck after line 516 EDIT: actually, it doesn't really seem to do much more in the non-stuck logs. |
Interestingly, the tx service doesn't receive updates about the chain in the stuck logs (and does in the non-stuck logs), so it's probably related to the sync service. EDIT: for reference this comment was wrong, as the tx service subscribes to the runtime service and not to the sync service |
The trace logs would be extremely useful in this case. |
When connecting to kusama it randomly gets stuck on the block in chainspec. But this isn't consistent behaviour between runs
smoldot: 2.0.28
chainspec: https://gist.github.com/ryanleecode/17aeb2a15d2c9137b20dd02a6bcfbbbe
Repro: https://stackblitz.com/~/github.com/ryanleecode/kusama-test
Stuck Logs: https://github.com/ryanleecode/kusama-test/actions/runs/9529257265/job/26267801534#step:7:382
Not Stuck Logs: https://github.com/ryanleecode/kusama-test/actions/runs/9529290166/job/26267875999#step:7:518
The text was updated successfully, but these errors were encountered: