-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Ballots may be assigned an incorrect proof #6607
Milestone
Comments
32 tasks
4 tasks
Verification passed on
|
Verified passed with
Verification passed on
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
After retrieving a set of ballot proofs,
PhaseTwo::ProofBatchCallback
may assign the incorrect proof to a ballot.When iterating the set of ballots, the function checks that the
surveyorId
matches, but this is insufficient to identify a matching ballot, as ballots for different viewing IDs may share asurveyorId
.I believe, but have not verified, that these votes are delivered to the server and appear to it as duplicate votes. Because of #6775, duplicate votes rejected by the server are treated by the client as successful and removed from the outgoing queue. Thus they are dropped by both the client and the server and effectively "lost."
Found while investigating #6545.
Steps to Reproduce
Steps copied from #6545. Note that it does not always reproduce.
Actual result:
Ballots may be assigned an incorrect proof.
Reproduces how often:
My sample size is small, but I see it occur perhaps 1/3 times with the above steps. The server-side folks may be able to comment on how often they see duplicate votes.
The text was updated successfully, but these errors were encountered: