[jira] [Commented] (BEAM-4175) exec.Invoke: panic: index out of range

["Henning Rohde (JIRA)" <ji...@apache.org>]

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

Henning Rohde commented on BEAM-4175:
-------------------------------------

Thanks Cody! The functions are valid and this is a clear bug -- it looks like the same problem as https://issues.apache.org/jira/browse/BEAM-3978 to me. We should probably dup the other bug to this one, because it has a nicer repro. Thanks for doing that, btw.

> exec.Invoke: panic: index out of range
> --------------------------------------
>
>                 Key: BEAM-4175
>                 URL: https://issues.apache.org/jira/browse/BEAM-4175
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-go
>            Reporter: Cody Schroeder
>            Assignee: Henning Rohde
>            Priority: Major
>
> Executing a pipeline with a ProcessElement method having the following signature will cause a runtime "index out of range" panic:
> {{func (d *doSomething) ProcessElement(key int, e func(*[]byte) bool) (int, error) {}}
> Changing the signature to have an emit function resolves the runtime panic:
> {{func (d *doSomething) ProcessElement(key int, e func(*[]byte) bool, emit func(int)) error {}}
>  
> The panic is 100% reproducible with [beam_err.go|[https://gist.github.com/schroederc/d90db7dbcd43c94bc59ba7b64fd9ca3e].]
>  
> I believe the function signature causing the panic is valid (and the panic is the bug), but if that's not the case, then the bug would be the late panic (vs. during beam type checking).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)