Fix for zero era problem #477
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
akru
suggested changes
Oct 13, 2021
|
All versions bumped up now. |
|
@Dinonard please update Cargo.lock too |
|
🙈 |
|
@akru is it ok now? |
akru
approved these changes
Oct 17, 2021
Dinonard
force-pushed
the
dapps-staking/fix-for-zero-era
branch
from
de707ce to
96fcc64
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
Affected core subsystem(s)
Dapps staking
Description of change
Fixed an issue where 1st era wouldn't be triggered if dapps staking
is enabled in mid of what would numerically be an era.
This caused some storage to remain uninitialized which caused dapps staking not to work properly.