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

Create an error mode session #8195

Closed
qstokkink opened this issue Oct 6, 2024 · 0 comments · Fixed by #8196
Closed

Create an error mode session #8195

qstokkink opened this issue Oct 6, 2024 · 0 comments · Fixed by #8196

Comments

@qstokkink
Copy link
Contributor

As shown in #8194 (comment), some errors can occur before we have a GUI. In these cases, we should still launch some minimal "backup" GUI and notify the user of the error.

In particular for #8194 (comment), a corrupted private key, we should ask the user what they want to do with the corrupt material. There is no obvious solution to this: casually removing a private key is a very bad idea. However, we can give "human" advice instead of the raw traceback.

For other cases, unknown failures, the error should be reported "as usual".

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

Successfully merging a pull request may close this issue.

1 participant