-
Notifications
You must be signed in to change notification settings - Fork 403
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
fix(logger): log group not closed on error #831
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome work!
Is it possible to add a test for this?
I think we need to make testing tools. |
Yeah, that's my next task in this matter, but I wanted to get this fix in the next version. |
Agreed. I think that testing tools are high on the agenda for the next release. |
@markwhitfeld I think you need to add it to the release, add tests later. |
I'm currently working on them, but not quite sure if I'll finish them until tomorrow. |
@markwhitfeld Can we suspend release? |
5909c6c
to
da40a33
Compare
@markwhitfeld ping |
@markwhitfeld ping 🚀 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Sorry it took so long for me to get to this!
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: #817
What is the new behavior?
I added the
error
log in case the error raised is suppressed with a custom error handler after the logger ran.Does this PR introduce a breaking change?