Re: possible bug in Statefun Golang SDK related to Context.Caller

PR created: [FLINK-26375][statefun-golang-sdk] Fix Statefun Golang SDK to return nil from Context.Caller when there is no caller by galenwarren · Pull Request #304 · apache/flink-statefun (github.com) On Fri, Feb 25, 2022 at 9:53 AM Galen Warren

Re: possible bug in Statefun Golang SDK related to Context.Caller

Thanks! I created a JIRA: [FLINK-26375] Fix Statefun Golang SDK to return nil from Context.Caller when there is no caller - ASF JIRA (apache.org) ... and will update soon with the PR. On Fri, Feb 25, 2022 at 3:01 AM Igal Shilman wrote: > Hi Ga

Re: possible bug in Statefun Golang SDK related to Context.Caller

Hi Galen, I think that you are right this does seem like a bug, looking at the Java SDK, we replace an empty address with a null value.[1] We should do the same here. I've also checked the Python SDK[2], and the JS SDK[3] and they have the same problem. Looking forward to your contribution! Than

possible bug in Statefun Golang SDK related to Context.Caller

On the Context interface, Caller is defined like this: // Caller is the caller function instance's Address, if applicable. This is nil // if the message was sent to this function via an ingress. Caller() *Address ... so, in the event a function is invoked from an ingress, as opposed to from anoth