Problem:
In many places in the SDK codebase, there are exception logging using the _LOGGER.exception. This logs the traceback of the exception. The encountered exception might then be bubbled up to the caller, or to the exit call which then again logs this exception. This causes duplicate logging at best, and confusion at worst since the exception message/type can be different.
Solution:
Clean up the logging, and use raise over logging the exception wherever possible.
Ref #566
Problem:
In many places in the SDK codebase, there are exception logging using the
_LOGGER.exception. This logs the traceback of the exception. The encountered exception might then be bubbled up to the caller, or to the exit call which then again logs this exception. This causes duplicate logging at best, and confusion at worst since the exception message/type can be different.Solution:
Clean up the logging, and use raise over logging the exception wherever possible.
Ref #566