-
-
Notifications
You must be signed in to change notification settings - Fork 151
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
Trigger policy before log #290
Conversation
Seems good, can you add two tests:
One thing to note here is that the |
Busy with other stuff right now, but I will try to add some tests when I find the time |
Thanks @snaggen, really appreciate your work here. |
Go ahead |
@brotskydotcom Any luck with your tests? |
I think it's just like what I have done in my PR #296, which you said that should be changed back. @bconn98 |
Hey folks, sorry to take a while to get back on this. I had pulled this fix into a separate branch that I've been using in another product and never got back to these tests. I can probably try getting the tests done this week. But @Dirreke are you saying you already have tests for this? Or that you have already integrated this fix into your PR which is waiting to be pulled? |
I'm assuming this feature was necessary to get the first line of 3rd party time-loggers working, therefore closing in favor of #296 , lets continue discussion over there. |
Re-arrange rolling file appender, so that it applies the policy
before it writes the next log row.
Fixes #289