Skip to content
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

Heartbeat Functionality (& checksums) Not fired in Edge Case #39

Open
bugbytesinc opened this issue Nov 22, 2022 · 0 comments
Open

Heartbeat Functionality (& checksums) Not fired in Edge Case #39

bugbytesinc opened this issue Nov 22, 2022 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@bugbytesinc
Copy link
Collaborator

An edge case exists that causes the checksums of some ballots to not be calculated in the webapp server back-end. What happens is that the "latest update time" is stale for a longer-than-desired period of time, preventing the server from seeing that the checksum for some ballots can be processed because this stale time is behind the "end voting time" of the ballot.

Need to add code to recognizes that a replay of the HCS message stream is complete and that we should (at this point) grab the latest transaction date from the ledger (proper) and run a checksum/heartbeat loop to bring all data/state into sync.

@bugbytesinc bugbytesinc added the bug Something isn't working label Nov 22, 2022
@bugbytesinc bugbytesinc self-assigned this Nov 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant