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.
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
Voting Contract: vote and close uses current status #60
Voting Contract: vote and close uses current status #60
Changes from all commits
0cdf7df
ba9771a
4a3995f
fd2e5e6
1adbde0
e326913
94daa76
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the key thing to do. Wouldn't this have to be done in the other cases where
current_status()
is being called as well? (i.e. our previous "execute proposal" fix).That means, using
current_status()
only for queries, andupdate_status()
for execution everywhere. And, "never" readingprop.status
directly. More consistent and robust, I think.We can use an
update_status()
impl that returns the updated status, as mentioned above (just an idea).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just wrote a variant of the same above.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the code errors below, this status update will be discarded. And if it does not error, the status will be updated and saved later anyway. So, there's really no need to call
update_status
instead ofcurrent_status
.The bug is: not calling any of those, and reading the status directly.