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
Now, if I create a rotation file with an invalid path (e.g. C:/a, EPERM error) the log.on ("error") callback is executed instead of throwing an exception that quits the process.
The text was updated successfully, but these errors were encountered:
Note to self: when doing this, also make sure to test that "cluster + rotating file ... crash" case cannot be reproduced. IOW, we need to also catch and re-emit the error on mvs from that issue.
You need to attach an error handler to the stream that you create in line 930.
You need to do the same as 367.
Steps:
Call the EventEmitter constructor in line 928:
Attach an error listener to the stream in line 930:
And finally listen to that error on the main logger instance in line 387:
Now, if I create a rotation file with an invalid path (e.g. C:/a, EPERM error) the
log.on ("error")
callback is executed instead of throwing an exception that quits the process.The text was updated successfully, but these errors were encountered: