-
Notifications
You must be signed in to change notification settings - Fork 151
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
'StorageData:: Unable to decode storage system.events:: ..' after runtime version update #1227
Comments
Hey @paperfrog95, First, I tried I reproduce the issue given the same specs as above (well almost). I have a fully synced archive node for polkadot on v9360, and set sidecar the v14.2.3. Unfortunately there was no reproduction. You are right in the sense that these errors can be really difficult to debug for many reasons, especially when a full restart solves the issue. NOTE: There is one caveat that if you are using sidecar to query a currently syncing node (not in idle syncing), we have noticed some unknown weird behavior can occur.
No, so this PR has to do with the There is one constant that I would say avoids these issues. Staying up to date with packages and deps. We stay up to date with polkadot-js pretty religiously. This ensures we are up to date with the substrate types that may be added or updated. It also ensures we are compatible with the latest runtime. I know it can be tough especially in Infra to ensure things are always updated because that is not realistic in all cases, when downtime needs to be at a minimum for services. I do think there is a decent hint here in your logs:
I can't promise it will be quick, but I can investigate the actual course of the server along the change of a runtime, and how the types can be affected :). |
Hello, We are coin wallet developer, and Of course, Polkadot exchange is being offered to customers.
Description
Our environment
We are operating three sidecars on a separate server.
Bug report
The bug occurred after the runtime version was updated.
Only sidecar003 has caused problems since the version was updated.
Error occured info
We're definitely using pruning mode, which keeps only 100,000 blocks. ( option
--pruning=100000
)However, the above error occurs only in Sidecar003 . It works normally on Sidecar001 and 002. (use the same pruning mode!)
Ours guess and log
Looking at this log, I think there was a conflict in Sidecar003 during the runtime upgrade.
Steps to Reproduce
Maybe, impossible..
I think it will be fixed if Sidecar is finished and restarted. But we're staying the same for disability identification.
Of course, the normal extrinsic is still not viewed only in Sidecar003.
Is this PR related to the problem?
I need to bring my boss the possibility of a recurrence and the solution in the solution.
I look forward to your kind cooperation.
The text was updated successfully, but these errors were encountered: