[ 
https://issues.apache.org/jira/browse/BEAM-8017?focusedWorklogId=496454&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-496454
 ]

ASF GitHub Bot logged work on BEAM-8017:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 07/Oct/20 10:13
            Start Date: 07/Oct/20 10:13
    Worklog Time Spent: 10m 
      Work Description: milantracy commented on pull request #13028:
URL: https://github.com/apache/beam/pull/13028#issuecomment-704837848


   R: @lostluck 


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 496454)
    Time Spent: 20m  (was: 10m)

> Plumb errors and remove panics from package graphx
> --------------------------------------------------
>
>                 Key: BEAM-8017
>                 URL: https://issues.apache.org/jira/browse/BEAM-8017
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-go
>            Reporter: Robert Burke
>            Assignee: Jing Chen
>            Priority: P3
>              Labels: Novice, beginner, noob, starter
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The graphx package, and in particular serialize.go and coder.go should be 
> returning errors back up, rather than panicing when issues occur deeper when 
> marshalling types. It makes errors harder to follow since there's now a less 
> necessary panic trace to skip, rather than a clearly constructed error 
> message.
> Not difficult, but may be tedious. Requires plumbing the errors and 
> handling/wrapping them appropriately instead of using panic. Most error 
> handling is presently correctly wrapped anyway.
> The graphx package as a rule is intended for beam internal use, and not part 
> of the user surface, so making the API changes (which aren't backwards 
> compatible) isn't the worst. Most of the affected methods are unexported.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to