audit-silent-errors

To find silent exceptions, audit the codebase for broad `except` blocks that pass, continue, or return without logger-based reporting. This identifies swallowed errors in parsing loops and UI paths, producing a severity-ranked report of problematic cases.

Silent exception handling occurs when `except` blocks swallow failures without sufficient logging or user feedback. It causes production debugging issues by hiding the root cause of errors, resulting in an invisible degraded state instead of actionable telemetry.

Audit codebase observability by scanning for broad `except` patterns and verifying the presence of `logger.error()` or `logger.exception()` calls. This checks whether failures are captured via telemetry and if the user receives actionable feedback.

Yes, this silent failure audit works for XML parsing and GUI data loading workflows. It specifically targets project areas where XML/API calls, GUI main windows, and session views commonly fail, checking for exceptions swallowed during data interactions.

To add user feedback and logging to existing `except` blocks, replace pass or continue statements with `logger.exception()` calls and UI error messages. This ensures failures are captured for debugging while providing actionable feedback instead of an invisible degraded state.