[
https://issues.apache.org/jira/browse/BEAM-6838?focusedWorklogId=217032&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-217032
]
ASF GitHub Bot logged work on BEAM-6838:
----------------------------------------
Author: ASF GitHub Bot
Created on: 21/Mar/19 21:19
Start Date: 21/Mar/19 21:19
Worklog Time Spent: 10m
Work Description: lostluck commented on issue #8064: [BEAM-6838] Go SDK:
Improving error msgs in pipeline serialization.
URL: https://github.com/apache/beam/pull/8064#issuecomment-475406653
I think the only "root" way to handle this is to have the top level calls
(where these are being used non-recursively) summarize the error somehow, which
this uses. Having the recursive stack is useful for precision, and it's (as you
mention) far better to have more information to explain how/where the error
happened. What you're displaying in the last comment is excellent and a clear
improvement. We could add newlines if necessary, but I'm also OK just punting
to the next version of Gos error improvements. Newlines make some things
trickier.
----------------------------------------------------------------
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: 217032)
Time Spent: 7.5h (was: 7h 20m)
> Improve error messages for unregistered protos
> ----------------------------------------------
>
> Key: BEAM-6838
> URL: https://issues.apache.org/jira/browse/BEAM-6838
> Project: Beam
> Issue Type: Sub-task
> Components: sdk-go
> Reporter: Daniel Oliveira
> Assignee: Daniel Oliveira
> Priority: Minor
> Time Spent: 7.5h
> Remaining Estimate: 0h
>
> When users have a type that can't be serialized (it has a function Field or
> similar) or more complex protocol buffers, the error should be improved to
> display the type being registered, and better yet, the beam.RegisterType(...)
> code they can use to enable use of their type.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
