[
https://issues.apache.org/jira/browse/BEAM-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132006#comment-17132006
]
Beam JIRA Bot commented on BEAM-1901:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> Faling to re-raise exceptions
> -----------------------------
>
> Key: BEAM-1901
> URL: https://issues.apache.org/jira/browse/BEAM-1901
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-core
> Reporter: Ahmet Altay
> Priority: P2
> Labels: stale-P2
>
> In runners common.py {{reraise_augmented}} fails to re-raise exceptions in
> some case.
> {{raise type(exn), args, sys.exc_info()[2]}}
> The above code assumes that the Exception can be reconstructed from its
> arguments but this is not always true for custom exception classes. (e.g.
> {{RPCError}} in
> https://github.com/GoogleCloudPlatform/google-cloud-datastore/blob/master/python/googledatastore/connection.py#L226
> This re-raising could first attempt to re-create the exception and if that
> does not fail raise otherwise raise the original exception as is.
> (cc: [~robertwb])
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
