Fix the log levels mapping

The libssh provides the most verbose logging with SSH_LOG_TRACE, which was not mapped to any of the standard values so the users are unable to get full debug logs. These are critical for libssh developers to be able to investigate issues.
ansible · Jun 21, 2024 · 7121d8a · 7121d8a
1 parent c99b7dd
commit 7121d8a
Showing 1 changed file with 3 additions and 2 deletions.
diff --git a/src/pylibsshext/session.pyx b/src/pylibsshext/session.pyx
@@ -46,11 +46,12 @@ OPTS_DIR_MAP = {
 
 LOG_MAP = {
     logging.NOTSET: libssh.SSH_LOG_NONE,
-    logging.DEBUG: libssh.SSH_LOG_DEBUG,
+    logging.DEBUG: libssh.SSH_LOG_TRACE,
+    15: libssh.SSH_LOG_DEBUG,
     logging.INFO: libssh.SSH_LOG_INFO,
     logging.WARNING: libssh.SSH_LOG_WARN,
     logging.ERROR: libssh.SSH_LOG_WARN,
-    logging.CRITICAL: libssh.SSH_LOG_TRACE
+    logging.CRITICAL: libssh.SSH_LOG_WARN
 }
 
 KNOW_HOST_MSG_MAP = {