The `kind` comes from the `exec, it cannot be populated when an error
happens while fetching action information.
While this is an error case, I think it would be still worth to send
`UserEvent` to notify the error happened.
We may need a generic kind for error cases or multiple error kinds if we
want to differentiate each error case.

Best regards
Dominic

2019년 9월 9일 (월) 오후 3:30, 蒋鹏程 <jiang.pengcheng@navercorp.com>님이 작성:

> hello all:
> ​
>  I opened an issue for a tiny bug in invoker side:
> https://github.com/apache/openwhisk/issues/4615
>
>  When get action from DB is failed or namespace is blacklisted while
> invoking an activation, the `InvokerReactive` will generate a fallback
> result for it,
> in these cases, it's not possible to get the `kind` info, but UserEvent do
> require the `kind` annotation:
> ​
>  /** Constructs an "Activation" event from a WhiskActivation */
>  def from(a: WhiskActivation): Try[Activation] = {
>    for {
>      // There are no sensible defaults for these fields, so they are
> required. They should always be there but there is
>      // no static analysis to proof that so we're defensive here.
>      fqn <- a.annotations.getAs[String](WhiskActivation.pathAnnotation)
>      kind <- a.annotations.getAs[String](WhiskActivation.kindAnnotation)
>    ......​
> ​
> so all these kind of activations cannot be sent to UserEvents, I think we
> can use an "unknown kind" or something else for these "fallback"
> activations, how do you think?
> ​
> Thanks
> Jiang
>