Skip to content

Conversation

@atetubou
Copy link

@atetubou atetubou commented Apr 16, 2025

Without this, our program exited without any message when there are some disk write error (e.g. no space left on device).

By increasing the severity, we can notice what caused the program exited as the log will be shown on stderr.

This is imported from http://cl/748177961

Without this, our program exited without any message when there are some disk write error (e.g. no space on device).

By increasing the severity, we can notice what caused the program exited as the log will be shown on stderr.
@atetubou atetubou changed the title Use Fatal severity if glog exits due to write failure glog: Use Fatal severity if glog exits due to write failure Apr 16, 2025
@atetubou
Copy link
Author

I sent this to internal repository first http://cl/748177961.

@atetubou atetubou marked this pull request as draft April 16, 2025 07:05
@atetubou atetubou changed the title glog: Use Fatal severity if glog exits due to write failure glog: Use Fatalf to exit when writing to logsinks fails Apr 24, 2025
@atetubou atetubou marked this pull request as ready for review April 24, 2025 01:01
@atetubou
Copy link
Author

@chressie could you review this too? Thanks.

@chressie
Copy link
Contributor

The Fatal call caused an infinite recursion that i haven't noticed before, so I made some changes internally and continue in #76. Cheers.

@chressie chressie closed this Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants