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.

Sign up for GitHub

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

Jump to bottom

Don't stack trace on I/O errors #141

Open
jeromekelleher opened this issue Feb 20, 2025 · 0 comments
Open

Don't stack trace on I/O errors #141

jeromekelleher opened this issue Feb 20, 2025 · 0 comments

Comments

@jeromekelleher
Copy link
Contributor

If we run out of disk space (or whatever) it shouldn't be a stacktrace. I think that would cover the other major class of expected error that we print out a message for.

xref #140
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jeromekelleher