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

Remove legacy Outcomes storage map from authorized #626

Closed
maltekliemann opened this issue May 14, 2022 · 0 comments · Fixed by #630
Closed

Remove legacy Outcomes storage map from authorized #626

maltekliemann opened this issue May 14, 2022 · 0 comments · Fixed by #630
Assignees
Labels
p:medium Medium priority, this issue can wait but should be done fairly soon t:maintenance The issue describes necessary maintenance

Comments

@maltekliemann
Copy link
Contributor

maltekliemann commented May 14, 2022

We use a lightly roundabout way of migrating the storage of authorized in v0.3.2, which leaves us with a storage double map Outcomes which needs to be removed at the next opportunity.

The workaround we used is due to the following issue: paritytech/substrate#11416.

@maltekliemann maltekliemann added p:medium Medium priority, this issue can wait but should be done fairly soon t:maintenance The issue describes necessary maintenance labels May 14, 2022
@maltekliemann maltekliemann added this to the v0.3.3 milestone May 14, 2022
@maltekliemann maltekliemann changed the title Remove legacy Outcomes storage map from `authorized Remove legacy Outcomes storage map from authorized May 15, 2022
@maltekliemann maltekliemann self-assigned this May 21, 2022
@sea212 sea212 removed this from the v0.3.3 milestone Jun 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p:medium Medium priority, this issue can wait but should be done fairly soon t:maintenance The issue describes necessary maintenance
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants