From b537e0f1caaaec51ab6d4b22b6d792d4c8078765 Mon Sep 17 00:00:00 2001 From: Mike Naberezny Date: Sun, 14 Jul 2024 10:04:03 -0700 Subject: [PATCH] Use the same log level as the other fd event messages This should not be a warning because it only reports on the internal state of supervisord fd event handling; it's not something the user can affect. --- supervisor/supervisord.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/supervisor/supervisord.py b/supervisor/supervisord.py index 2265db9c7..8d9ebe30f 100755 --- a/supervisor/supervisord.py +++ b/supervisor/supervisord.py @@ -225,7 +225,7 @@ def runforever(self): else: # if the fd is not in combined_map, we should unregister it. otherwise, # it will be polled every time, which may cause 100% cpu usage - self.options.logger.warn('unexpected read event from fd %r' % fd) + self.options.logger.blather('unexpected read event from fd %r' % fd) try: self.options.poller.unregister_readable(fd) except: @@ -246,7 +246,7 @@ def runforever(self): except: combined_map[fd].handle_error() else: - self.options.logger.warn('unexpected write event from fd %r' % fd) + self.options.logger.blather('unexpected write event from fd %r' % fd) try: self.options.poller.unregister_writable(fd) except: