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

ASF GitHub Bot commented on BEAM-2240:
--------------------------------------

GitHub user robertwb opened a pull request:

    https://github.com/apache/beam/pull/3012

    [BEAM-2240] Always augment exception with step name.

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
    
     - [ ] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`.
     - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.pdf).
    
    ---


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/robertwb/incubator-beam py-exceptions

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/beam/pull/3012.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3012
    
----
commit 7a3766bf6e05a927711c44a88ff6f9b9c83212f0
Author: Robert Bradshaw <[email protected]>
Date:   2017-05-09T22:19:34Z

    [BEAM-2240] Always augment exception with step name.

----


> Step context not always available when exceptions raised.
> ---------------------------------------------------------
>
>                 Key: BEAM-2240
>                 URL: https://issues.apache.org/jira/browse/BEAM-2240
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-py
>            Reporter: Robert Bradshaw
>            Assignee: Ahmet Altay
>             Fix For: 2.0.0
>
>
> This was encountered for IO errors (as an example).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to