-
Notifications
You must be signed in to change notification settings - Fork 700
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
Enable the improved_panic_error_reporting
feature in sp-io
for our runtimes in a few releases
#869
Comments
dq: what does "enable" actually mean here? Does this need a Polkadot PR? |
Yes, there is a feature that needs to be activated. I think it can be done now, but there is no real need to get it done for the next release. |
Does fixing this also fix paritytech/substrate#11828? |
Yes, as I have commented on the issue. @koute it is now finally time to enable this :P I think we can just remove the feature and have it enabled always. |
Indeed; this was included in Polkadot 0.9.17, and the newest version that explicitly pops up in our telemetry is 0.9.24, so should be fine to enable it. I'll push a PR tomorrow morning. |
Thank you. Important here being any way that all validators support this and they support this for sure. |
* parse new xcm format * fmt * rename * fixed tests to pass None as account key network * rustfmt * removed more network checks * allow none locations * fixed tests * fixed asset resolution * partial * use locations * updated cumulus * fix test * increase coverage * rustfmt * fix coverage * covering tests * more coverage * more coverage * more fixes * coverage * return correct error * update cumulus * fix test
Substrate PR: paritytech/substrate#10741
Background issue: paritytech/substrate#10585
We should wait for a few releases until people have upgraded their clients (so that the new required host function is available) and then switch this feature on.
The text was updated successfully, but these errors were encountered: