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

boot: LUKS errors are "controlled" #249

Merged
merged 1 commit into from Dec 1, 2020

Conversation

samueldr
Copy link
Member

@samueldr samueldr commented Dec 1, 2020

This means that we shouldn't raise an exception, but rather fail outright. The background being black means that things failed successfully, as expected.

The big difference here is how the error will be shown.

Rather than being treated as things failing to run as expected from the init code, things fail with a really specific error message, about how it failed to unlock.

This means that we shouldn't raise an exception, but rather fail
outright. The background being black means that things *failed
successfully*, as expected.
@samueldr samueldr merged commit 21f662a into NixOS:master Dec 1, 2020
@samueldr samueldr deleted the fix/luks-error-reporting branch December 1, 2020 01:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant