[ https://issues.apache.org/jira/browse/BEAM-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428710#comment-16428710 ]
Josh Burkart commented on BEAM-3956: ------------------------------------ Also, this used to work with the DirectRunner in 2.3.0, but no longer works in 2.4.0. 2.3.0 example output: {noformat} WARNING:root:A task failed with exception: 'unicode' object does not support item assignment [while running 'ModifyTimestamps'] Traceback (most recent call last): <...normal Python traceback...> TypeError: 'unicode' object does not support item assignment [while running 'ModifyTimestamps'] {noformat} 2.4.0 example output: {noformat} TypeError: 'unicode' object does not support item assignment [while running 'ModifyTimestamps'] {noformat} > Stacktraces from exceptions in user code should be preserved in the Python SDK > ------------------------------------------------------------------------------ > > Key: BEAM-3956 > URL: https://issues.apache.org/jira/browse/BEAM-3956 > Project: Beam > Issue Type: Bug > Components: sdk-py-core > Reporter: Stephan Hoyer > Priority: Major > Time Spent: 6h 10m > Remaining Estimate: 0h > > Currently, Beam's Python SDK loses stacktraces for exceptions. It does > helpfully add a tag like "[while running StageA]" to exception error > messages, but that doesn't include the stacktrace of Python functions being > called. > Including the full stacktraces would make a big difference for the ease of > debugging Beam pipelines when things go wrong. -- This message was sent by Atlassian JIRA (v7.6.3#76005)