-
-
Notifications
You must be signed in to change notification settings - Fork 114
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
Make flush method not shutdown #38
Comments
As a quick workaround for flush not doing what you want, you can use |
I agree in general that the semantics of flush() as specified by https://docs.python.org/3/library/logging.html#logging.Handler.flush mean it should not trigger shutdown by default. |
@kislyuk do you know if this is still the case? It looks like it's not since flush looks like it just puts a sentinel on the queue and will force the queues to send when they see it but they continue monitoring the queue after that: watchtower/watchtower/__init__.py Lines 286 to 297 in 5002639
and watchtower/watchtower/__init__.py Lines 256 to 257 in 5002639
|
I need my messages to flush after each send, but your flush method shuts down. Can you change this?
The text was updated successfully, but these errors were encountered: