[jira] [Commented] (BEAM-3956) Stacktraces from exceptions in user code should be preserved in the Python SDK
[ https://issues.apache.org/jira/browse/BEAM-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428857#comment-16428857 ] Ahmet Altay commented on BEAM-3956: --- Great, thank you! > 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)
[jira] [Commented] (BEAM-3956) Stacktraces from exceptions in user code should be preserved in the Python SDK
[ https://issues.apache.org/jira/browse/BEAM-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428811#comment-16428811 ] Ahmet Altay commented on BEAM-3956: --- [~shoyer] Would you be able to fix the Direct Runner related issues introduce in #4376? > 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)
[jira] [Commented] (BEAM-3956) Stacktraces from exceptions in user code should be preserved in the Python SDK
[ https://issues.apache.org/jira/browse/BEAM-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428749#comment-16428749 ] Stephan Hoyer commented on BEAM-3956: - Indeed, it looks losing stack-traces for the direct runner was introduced inadvertently by [https://github.com/apache/beam/pull/4376] > 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)
[jira] [Commented] (BEAM-3956) Stacktraces from exceptions in user code should be preserved in the Python SDK
[ https://issues.apache.org/jira/browse/BEAM-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)