-
Notifications
You must be signed in to change notification settings - Fork 20
When flush called on async mode logger -> infinite loop #1
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
Comments
This is blocker for me |
My build is red because of this, need a fix ASAP. |
Thanks for reporting that this issue causes your production environment to be blocked. This greatly concerns us and our team will treat this issue with the highest priority. |
In the red here as well- my team is panicking, need a solution ASAP! ! |
FFS it's been 3 hours since your comment - where is the fix? Our build server is on fire and we can't put it out because of this |
Sorry for the inconvenience and downtime caused. |
We should make a meeting with all stakeholders ASAP to come up with a quick resolution of the issue |
I am proposing a board meeting with the Stakeholders. |
I had to disable flush() on async mode logger due to never returning from it...
Will have to look into why this happens.
The text was updated successfully, but these errors were encountered: