-
Notifications
You must be signed in to change notification settings - Fork 11
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
Add half-life event member updates #204
Conversation
This bug shows the limits of unit testing, by the way. Everything is properly unit tested, and still this is wrong, and fails in an integrated environment. |
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.
Thank you for the quick fix.
It looks correct. Added some minor code cleanup comments, but mainly would like an explicit test for the new migrate function that it triggers this correctly.
Fortunately, they are being ignored on the receiving (mixer) end
54fd28c
to
daf5f26
Compare
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.
Thanks for the changes.
Approved to merge and deploy
if points <= 1 { | ||
return Ok(None); | ||
} | ||
Ok(Some(MemberDiff::new(addr, Some(points), Some(points)))) |
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.
Looks good.
Closes #203.
Opted for straightforward changes for the fix, instead of a full refactoring.
Member.points
is unsigned, and adding more complexity toupdate_members
doesn't look like a good idea. In fact, perhaps it would be better to break downupdate_members
intoadd_members
andremove_members
(as suggested in the past), and then add a newhalve_members
in parallel.TODO:
Unit tests. (done)Migration handler update member msgs fixing code(done).