You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In that case you are likely not able to create a File anyway (or whatever it is you want to be writing to).
But if writing fails during runtime, the error is silently dropped right now (so the application won't panic).
On Sun, 7 Aug 2022, 17:36 Victoria Brekenfeld, ***@***.***> wrote:
In that case you are likely not able to create a File anyway (or whatever
it is you want to be writing to).
But if writing fails during runtime, the error is silently dropped right
now (so the application won't panic).
—
Reply to this email directly, view it on GitHub
<#111 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPIOP6GIPJD275H45EH72TVX7JV7ANCNFSM55XVQUVA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
what's the error handling like for WriteLogger?
I don't see anything for handling if the given path/file cannot be written to
(either due to permissions, (b)locking or if the path doesn't exist)
The text was updated successfully, but these errors were encountered: