summaryrefslogtreecommitdiff
path: root/src/polaris/protocol.py
diff options
context:
space:
mode:
authorEvgeny Zinoviev <me@ch1p.io>2022-07-01 21:15:09 +0300
committerEvgeny Zinoviev <me@ch1p.io>2022-07-01 21:15:09 +0300
commitb550f96c1eba0c7f7b1565bcad65fea111bface1 (patch)
tree4b1e05eb9c7941d2f29c2f1f0aec91b60dec8f23 /src/polaris/protocol.py
parent21cd2ad07ce444b2feeb7dd8d3f3c190cabd69aa (diff)
polaris: change some log message levels
Diffstat (limited to 'src/polaris/protocol.py')
-rw-r--r--src/polaris/protocol.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/polaris/protocol.py b/src/polaris/protocol.py
index 3a171f8..680b6e1 100644
--- a/src/polaris/protocol.py
+++ b/src/polaris/protocol.py
@@ -1043,7 +1043,7 @@ class UDPConnection(threading.Thread, ConnectionStatusListener):
callback_value = incoming_message
self._incr_outseq()
else:
- self._logger.debug(f'{lpfx} response is INVALID')
+ self._logger.warning(f'{lpfx} response is INVALID')
# It seems that we've received an incoming CmdMessage or PingMessage with the same seqno that our outgoing
# message had. Bad, but what can I say, this is quick-and-dirty made UDP based protocol and this sort of