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

Write startup errors to stderr #472

Closed
n8maninger opened this issue Oct 4, 2024 · 0 comments · Fixed by #473
Closed

Write startup errors to stderr #472

n8maninger opened this issue Oct 4, 2024 · 0 comments · Fixed by #473
Labels
feature A new feature request or enhancement
Milestone

Comments

@n8maninger
Copy link
Member

Description

Critical startup errors are currently written to the stdout via Zap logging. This is good for consistency, but hard for scripts to determine the cause of the failure. Fatal startup errors should be logged directly to stderr and exit code 1.

Version

No response

What operating system are you running (e.g. Ubuntu 22.04, macOS, Windows 11)?

No response

Anything else?

No response

@n8maninger n8maninger added the feature A new feature request or enhancement label Oct 4, 2024
@n8maninger n8maninger added this to the v2.0.0 milestone Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature A new feature request or enhancement
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant