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

Clearer error message when goodkey fails unexpectedly #7642

Merged
merged 1 commit into from
Aug 6, 2024

Conversation

aarongable
Copy link
Contributor

This will prevent users from believing their key is at fault when the actual error is between Boulder and the database.

Fixes #7624

@aarongable aarongable requested a review from a team as a code owner August 2, 2024 19:46
@aarongable aarongable merged commit e398c4d into main Aug 6, 2024
12 checks passed
@aarongable aarongable deleted the better-key-error branch August 6, 2024 16:23
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

Successfully merging this pull request may close these issues.

"error checking key quality" should be an internal error in event of DB unavailibility
2 participants