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 #110

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

Write startup errors to stderr #110

n8maninger opened this issue Oct 4, 2024 · 0 comments · Fixed by #115
Labels
good first issue Good for newcomers
Milestone

Comments

@n8maninger
Copy link
Member

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.

@n8maninger n8maninger added the good first issue Good for newcomers label Oct 4, 2024
@n8maninger n8maninger added this to Sia Oct 4, 2024
@n8maninger n8maninger added this to the v1.0.0 milestone Oct 4, 2024
@github-project-automation github-project-automation bot moved this to Done in Sia Oct 17, 2024
@n8maninger n8maninger modified the milestones: v1.0.0, v0.1.0 Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant