beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Hoyer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-3956) Stacktraces from exceptions in user code should be preserved in the Python SDK
Date Fri, 06 Apr 2018 19:18:00 GMT

    [ https://issues.apache.org/jira/browse/BEAM-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428813#comment-16428813
] 

Stephan Hoyer commented on BEAM-3956:
-------------------------------------

[~altay] my PR #4959 fixes this for DirectRunner as well as for runners that use RPCs.

> 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)

Mime
View raw message