This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
Fix quantization in referenda alarm #12815
Merged
+27
−18
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
gavofyork
added
B0-silent
|
@muharem final approval, please. |
muharem
approved these changes
Dec 1, 2022
ggwpez
approved these changes
Dec 1, 2022
ltfschoen
pushed a commit
to ltfschoen/substrate
that referenced
this pull request
Feb 22, 2023
* Fix quantization in referenda alarm * Formatting * alarm interval, test (paritytech#12818) Co-authored-by: Muharem Ismailov <[email protected]>
ark0f
pushed a commit
to gear-tech/substrate
that referenced
this pull request
Feb 27, 2023
* Fix quantization in referenda alarm * Formatting * alarm interval, test (paritytech#12818) Co-authored-by: Muharem Ismailov <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Quantization calculation of the referenda alarm was wrong and resulted in it being in the past. This fixes it.