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

Crash and log unexpected errors during interpretation (rather than rejecting the ballot as unreadable) (potentially with safeguards to prevent crashing during election day) #5459

Closed
2 tasks
arsalansufi opened this issue Oct 1, 2024 · 2 comments
Assignees
Milestone

Comments

@arsalansufi
Copy link
Contributor

arsalansufi commented Oct 1, 2024

Additionally, let's:

  • Audit VxSuite for other places where unexpected errors are turned into user-facing errors rather than crashing
  • Consider writing some easily identifiable record to the file system or connected USB drive when this happens to make debugging extra easy, especially for external contract manufacturers when that time comes
@jonahkagan
Copy link
Collaborator

Consider writing some easily identifiable record to the file system or connected USB drive when this happens to make debugging extra easy, especially for external contract manufacturers when that time comes

Using existing logging to meet this requirement

@jonahkagan
Copy link
Collaborator

jonahkagan commented Oct 2, 2024

Audit VxSuite for other places where unexpected errors are turned into user-facing errors rather than crashing

I audited the ballot interpretation code path, but not anything else for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants