Correct voter map types in TL-B schemas - #2540
Open
roshnicdave wants to merge 4 commits into
Open
Conversation
update create-release.yml
update create-release.yml
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
The proposal and complaint voter maps store 32-bit timestamps, but their TL-B definitions use
True. This brings the definitions and matching contract comments in line with the data already written by the contracts, and adds coverage for a populated voter maptested with
ctest --test-dir build-validation -R "^test-smartcont$" --output-on-failureResolves #2519.