Skip to content

Fix #1788: scrub exception messages from error logs to prevent PII leakage - #1791

Closed
Subodh-17 wants to merge 2 commits into
mloda-ai:mainfrom
Subodh-17:fix/row-leakage-in-logs
Closed

Subodh-17 wants to merge 2 commits into
mloda-ai:mainfrom
Subodh-17:fix/row-leakage-in-logs

Conversation

@Subodh-17

Copy link
Copy Markdown
Contributor

This PR fixes #1788 by stripping the exception message from the traceback strings formatted for ERROR logs. The full exception message remains available in the exception object and caller payloads.

This fixes issue mloda-ai#1788 by stripping exception strings from the traceback logged on run failure.
@Subodh-17
Subodh-17 requested a review from TomKaltofen as a code owner October 3, 2026 11:22
…ion groups

The traceback renderer recursed through __cause__/__context__ without tracking visited exceptions, so a cyclic chain raised RecursionError inside the worker except blocks and the original error was lost. Walk the chain iteratively with a seen set, render exception group members (type names and frames only), and use module-qualified names for non-builtin exception types.
@TomKaltofen

Copy link
Copy Markdown
Contributor

@Subodh-17 Thank you for your contribution. I added it to the main branch via another commit. ef4d7a0

@TomKaltofen TomKaltofen closed this Oct 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Run failure ERROR log carries row values from the exception message

3 participants