You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Bill Neubauer (JIRA)" <ji...@apache.org> on 2018/01/12 19:11:00 UTC

[jira] [Updated] (BEAM-3474) Go SDK: panic handling swallows the stack trace, hurting debuggabilityK

     [ https://issues.apache.org/jira/browse/BEAM-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bill Neubauer updated BEAM-3474:
--------------------------------
    Summary: Go SDK: panic handling swallows the stack trace, hurting debuggabilityK  (was: Go SD: panic handling swallows the stack trace, hurting debuggability)

> Go SDK: panic handling swallows the stack trace, hurting debuggabilityK
> -----------------------------------------------------------------------
>
>                 Key: BEAM-3474
>                 URL: https://issues.apache.org/jira/browse/BEAM-3474
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-go
>            Reporter: Bill Neubauer
>            Assignee: Bill Neubauer
>            Priority: Minor
>
> The panic handlers 
> https://github.com/apache/beam/blob/go-sdk/sdks/go/pkg/beam/core/runtime/exec/util.go#L39
> and 
> https://github.com/apache/beam/blob/go-sdk/sdks/go/pkg/beam/core/runtime/exec/util.go#L49
> should include the output of "runtime/debug"'s Stack() call so the user can see what caused the panic.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)