2019-07-16 07:27:12 UTC - Pepi Paraskevoulakou: GoodMorning from Greece! i still have the same problem with the connections which is refused for installing apimgmt (connection refused) and i was wondering if someone faced the same problem. Maybe fails because of ports? or firewall iptables ? wave : James Thomas https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563262032459600 ---- 2019-07-16 07:30:20 UTC - Jiang PengCheng: you can check whether the port is open using `sudo /sbin/lsof -i:443` on your host(`83.212.98.117`) and use `nmap 83.212.98.117 -p 443` to check the firewall +1 : Dominic Kim https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563262220461500 ---- 2019-07-16 08:22:00 UTC - chris: Hello everyone, I finally figure out how to install openwhisk by using docker-compose But when I run `wsk action list` it shows `error: Unable to obtain the API list:...............because it doesn't contain any IP SANs` https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563265320463500?thread_ts=1563265320.463500&cid=C3TPCAQG1 ---- 2019-07-16 08:34:47 UTC - chris: oh my god guys if you are face the same question... do not remember add `-i` then it work :slightly_smiling_face: https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563266087463900?thread_ts=1563265320.463500&cid=C3TPCAQG1 ---- 2019-07-16 10:21:24 UTC - Satwik Kolhe: Where can I find "APIGW_ACCESS_TOKEN" ?? Thank you. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563272484464700?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 10:43:37 UTC - Roberto Santiago: @Satwik Kolhe What kind of installation do you have? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563273817464800?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 10:51:17 UTC - Satwik Kolhe: @Roberto Santiago I have deployed OW on K8s using incubator-openwhisk-deploy-kube. I was working with Serverless (<http://serverless.com|serverless.com>) and was not getting endpoints after doing 'sls deploy'
endpoints (api-gw): **failed to fetch routes** On the contrary I can create APIs using wsk cli https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563274277465000?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 10:52:55 UTC - Roberto Santiago: So try using `dummytoken` for `APIGW_ACCESS_TOKEN` https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563274375465200?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 10:54:52 UTC - Satwik Kolhe: Aaha! Let me try. I saw that in `wsk -v api create` but was not sure. Is there a way to create API access tokens based upon the namespace/user? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563274492465400?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 10:57:06 UTC - Satwik Kolhe: @Roberto Santiago Still no luck. endpoints (api-gw): **failed to fetch routes** --- .wskprops --- AUTH=23bc46b1-71f6-4ed5-8c54-816aa4f8c502:123zO3xZCLrMN6v2BKK1dXYFpXlPkccOFqm12CdAsMgRU4VrNZ9lyGVCGuMDGIwP APIHOST=<https://10.10.128.141:31003> NAMESPACE=guest APIGW_ACCESS_TOKEN=dummytoken https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563274626465600?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 10:57:58 UTC - Roberto Santiago: Are you really serving https over port 31003? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563274678465800?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 10:58:36 UTC - Satwik Kolhe: Yes, for both wsk and sls cli insecure is true https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563274716466000?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 11:00:47 UTC - Satwik Kolhe: wsk -i api list ok: APIs Action Verb API Name URL /guest/hello get /hello2 <https://10.10.128.141:31003/api/23bc46b1-71f6-4ed5-8c54-816aa4f8c502/hello2/world2> /guest/my_service-dev-hello post / <https://10.10.128.141:31003/api/23bc46b1-71f6-4ed5-8c54-816aa4f8c502/hello> /guest/hello get /hello <https://10.10.128.141:31003/api/23bc46b1-71f6-4ed5-8c54-816aa4f8c502/hello/world> https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563274847466200?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 11:02:19 UTC - Roberto Santiago: So this may sound dumb but remove `https://` from `APIHOST` https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563274939466400?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 11:03:45 UTC - Satwik Kolhe: Ammm! Let me try... https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563275025466600?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 11:04:55 UTC - Satwik Kolhe: No change! https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563275095466800?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 11:05:11 UTC - Roberto Santiago: Hmmm. In your k8s deploy what secrets exist https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563275111467000?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 11:05:26 UTC - Roberto Santiago: `kubectl get secrets` https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563275126467200?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 11:10:17 UTC - Satwik Kolhe: kl get secrets -n slsow NAME TYPE DATA AGE default-token-z5hrp <http://kubernetes.io/service-account-token|kubernetes.io/service-account-token> 3 27h slsow-core-token-vgzfs <http://kubernetes.io/service-account-token|kubernetes.io/service-account-token> 3 27h slsow-db.auth Opaque 2 27h slsow-docker.registry.auth Opaque 2 27h slsow-nginx tls 2 27h slsow-whisk.auth Opaque 2 27h https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563275417467400?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 11:25:28 UTC - Rodric Rabbah: oy we have a problem, everyone’s stumbling on the same issues with api gw +1 : Satwik Kolhe, James Thomas https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563276328468500 ---- 2019-07-16 11:28:54 UTC - Roberto Santiago: in `slsow-core-token-vgzfs` see if there is a token field. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563276534468800?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 11:29:44 UTC - Roberto Santiago: wait....that's incorrect.... looking at my notes for how I got this vefore https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563276584469000?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 11:31:37 UTC - Roberto Santiago: `kubectl get secret slsow-whisk.auth -o yaml` https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563276697469200?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 11:31:48 UTC - Roberto Santiago: there should be a field `system` https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563276708469400?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 11:31:55 UTC - Satwik Kolhe: Ohkye. Let me try.. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563276715469600?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 11:32:08 UTC - Roberto Santiago: base64 decode that field and try that. That is the one that I use on my installs. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563276728469800?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 11:32:24 UTC - Satwik Kolhe: Yes... https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563276744470000?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 11:35:25 UTC - Roberto Santiago: @Rodric Rabbah As I shared with @Satwik Kolhe, for my k8s installs I look at the `whisk.auth` secret and decode the `system` field and use that for `APIGW_ACCESS_TOKEN`. I don't know if that is correct but I don't have issues with my api deployments since I started doing that. (Note: I do not go through SLS CLI) thankyou : Rodric Rabbah +1 : Rodric Rabbah https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563276925472000 ---- 2019-07-16 11:40:39 UTC - Rodric Rabbah: the fake token might be specific to sls I’m going to spend a little bit of time this morning to see if we can address it, this ruins the experience for developers getting started +1 : Roberto Santiago https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563277239473900 ---- 2019-07-16 11:54:48 UTC - Satwik Kolhe: @Roberto Santiago I appreciate your help here. But I am facing a different issue now, which was addressed here(<https://github.com/apache/incubator-openwhisk-apigateway/issues/342>) Changing the APIGW_ACCESS_TOKEN to system token from whisk.auth secret did not have any effect. My K8s deployment is using `0.10.0-incubating` image of apigw. I was able to create API via wsk cli, but now even that is throwing exceptions. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563278088474700?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 11:59:03 UTC - Satwik Kolhe: Changes of this PR (<https://github.com/apache/incubator-openwhisk-apigateway/pull/343/files>) are not present in openwhisk/apigateway:0.10.0-incubating https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563278343475000?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 12:04:06 UTC - Roberto Santiago: Cool. Interesting. I've not uses SLS with my OW work. Out of curiosity, is there a particular reason you are going through SLS? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563278646475200?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 12:09:02 UTC - Satwik Kolhe: I was trying SLS to check the compatibility of OpenWhisk. And use the same SLS definations to deploy functions on Azure. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563278942475400?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 12:11:33 UTC - Satwik Kolhe: And, Yes as Rodric Rabbah mentioned himself. OW API has been one of the functionalities that I have faced difficulties with. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563279093475600?thread_ts=1563272484.464700&cid=C3TPCAQG1 ---- 2019-07-16 12:42:18 UTC - Philipp Heuberger: Hey everybody :wave:I'm trying to deploy an OpenWhisk action to IBM via the Serverless framework but keep getting the following error ``` Failed to deploy function (asset-creator-dev-generate) due to error: PUT <https://eu-de.functions.cloud.ibm.com/api/v1/namespaces/_/actions/asset-creator-dev-generate?overwrite=true> Returned HTTP 413 (Payload Too Large) --> "Response Missing Error Message."``` I don't see how the payload could be too large, unless there's a node dependency that's completely out of bounds, but I doubt it. Any ideas? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563280938478300 ---- 2019-07-16 12:43:46 UTC - James Thomas: @Philipp Heuberger Can you check the zip file size in the `.serverless` directory? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563281026478700 ---- 2019-07-16 12:44:05 UTC - James Thomas: it’ll contain the package used to deploy the action. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563281045479000 ---- 2019-07-16 12:44:35 UTC - Philipp Heuberger: Oh, it's indeed 41M https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563281075479500 ---- 2019-07-16 12:45:07 UTC - James Thomas: all input payloads have to be base64 encoded so it’ll be at the limit I guess. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563281107480100 ---- 2019-07-16 12:45:59 UTC - James Thomas: @Philipp Heuberger I’d recommend looking into using rollup.js or another tool to produce a built-version of the action code before deployment. It’ll save you loads of time deploying new stuff (plus improvement performance on invocation). https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563281159481100 ---- 2019-07-16 12:46:46 UTC - James Thomas: <https://github.com/apache/incubator-openwhisk/blob/master/docs/actions-nodejs.md#using-javascript-bundlers-to-package-action-source-files> https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563281206481300 ---- 2019-07-16 12:47:03 UTC - James Thomas: and (<https://boneskull.com/rollup-for-javascript-actions-on-openwhisk/>) for more details. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563281223481600 ---- 2019-07-16 12:47:24 UTC - Philipp Heuberger: Thanks a ton for helping out @James Thomas! :pray: pray : James Thomas https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563281244482200 ---- 2019-07-16 13:09:25 UTC - Michael Schmidt: openwhisk (especially @James Thomas, @Roberto Diaz,@chetanm and @Rodric Rabbah) are really great with supporting the community! openwhisk : James Thomas, Roberto Diaz https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563282565483700?thread_ts=1563282565.483700&cid=C3TPCAQG1 ---- 2019-07-16 13:10:29 UTC - James Thomas: thanks @Michael Schmidt - it’s a pleasure, we’re all happy to be involved in such a great community. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563282629484600 ---- 2019-07-16 14:41:24 UTC - Robert Felker: Hi guys ! glad to join the OpenWhisk channel. I'm currently testing the solution for further integration in a SI (can it be the backbone ? :wink: ) +1 : James Thomas, Michael Schmidt https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563288084486300 ---- 2019-07-16 14:42:02 UTC - Robert Felker: Big Up for the runnable jar to test the solution, it's a huge boost https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563288122486900 ---- 2019-07-16 15:05:38 UTC - Robert Felker: I see that JS is the only runtime for the in memory runner, can I add other runtimes ? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563289538487900 ---- 2019-07-16 15:07:00 UTC - Rodric Rabbah: Yes. There’s a parameter you can provide to supply your own runtimes manifest. Hang on. And welcome @Robert Felker https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563289620488800 ---- 2019-07-16 15:09:07 UTC - Rodric Rabbah: `$ ./gradlew :core:standalone:bootRun --args='-m runtimes.json'` https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563289747489000 ---- 2019-07-16 15:09:12 UTC - Rodric Rabbah: from <https://github.com/apache/incubator-openwhisk/tree/master/core/standalone> https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563289752489200 ---- 2019-07-16 15:15:18 UTC - Robert Felker: Too much precipitation playing with the stuff and I skipped the docs ! Thx @Rodric Rabbah https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563290118491600 ---- 2019-07-16 15:15:45 UTC - Michael Schmidt: Alright there is still issues of authentication for my kafkaProduce. `Unable to invoke action \'kafkaProduce\' : the supplied authentication is not authorized to access \'messaging/kafkaProduce\' (code 1f0b...` https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563290145492100 ---- 2019-07-16 15:16:12 UTC - Michael Schmidt: how do I make my kafkaProduce package accessible, I am currently using the auth for the wsk system. so I assumed I would be good to go https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563290172492700 ---- 2019-07-16 15:19:20 UTC - Michael Schmidt: wsk action list I can see kafkaProduce wsk package list I do not see kafkaProduce https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563290360493200 ---- 2019-07-16 15:19:27 UTC - Michael Schmidt: only messaging https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563290367493400 ---- 2019-07-16 15:24:34 UTC - Michael Schmidt: I also tried `wsk action invoke wisk.system/messaging/kafkaProduce -p brokers "[\"brokerone\", \"brokertwo\", \"brokerthree\"]" -p topic test -p value "this is my message"` https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563290674495500 ---- 2019-07-16 15:26:40 UTC - Roberto Diaz: It a pleasure for me collaborate with the community. In fact I feel that the Openwhisk community is a very friendly one :blush: and everyone is open to help and make the project better https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563290800497100?thread_ts=1563282565.483700&cid=C3TPCAQG1 ---- 2019-07-16 15:26:44 UTC - Michael Schmidt: I am giving the address of the kafka brokers themselves not the rest endpoint, but my issue doesn't seem to be kafka related just yet, it seems to be auth related with openwhisk. but I am not sure what to look at... or what auth to provide other than the auth key that I set for the system when I installed openwhisk https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563290804497400 ---- 2019-07-16 16:45:35 UTC - Rodric Rabbah: Note you typed wisk not whisk in the package name. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563295535497900 ---- 2019-07-16 16:45:43 UTC - Rodric Rabbah: Is that a copy paste typo? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563295543498300 ---- 2019-07-16 16:46:26 UTC - Rodric Rabbah: If not the package won’t exist and the controller responds with not authorized instead of not found because it’s a different namespace you’re not authorized to see. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563295586499700 ---- 2019-07-16 17:05:34 UTC - Rodric Rabbah: @Michael Schmidt ^^ https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563296734000400 ---- 2019-07-16 17:06:38 UTC - Michael Schmidt: fffffffffffffffffffff.......... https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563296798000600 ---- 2019-07-16 17:06:45 UTC - Michael Schmidt: that was actually it... https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563296805000800 ---- 2019-07-16 17:06:47 UTC - Michael Schmidt: welp. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563296807001000 ---- 2019-07-16 17:08:00 UTC - Rodric Rabbah: :yay: you get a t-shirt https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563296880001700 ---- 2019-07-16 17:08:37 UTC - Rodric Rabbah: maybe the error message should be changed to say “either” not found or not authorized https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563296917002300 ---- 2019-07-16 17:13:06 UTC - Michael Schmidt: sigh. I think there will never be a way to completely resolve human error https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563297186002700 ---- 2019-07-16 17:14:56 UTC - Rodric Rabbah: _the user is always right_ https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563297296003100 ---- 2019-07-16 17:20:48 UTC - Michael Schmidt: what is funny is that my wisk wasn't even copy paste... it was typed since I am on offline env https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563297648003600 ---- 2019-07-16 17:20:54 UTC - Michael Schmidt: so i mistyped it twice... https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563297654003800 ---- 2019-07-16 18:40:43 UTC - Michael Schmidt: obviously @Dave Grove too https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563302443004200?thread_ts=1563282565.483700&cid=C3TPCAQG1 ---- 2019-07-16 18:55:08 UTC - Duncan Beard: So I'm trying to create a kafka trigger using `wsk -i trigger create db-kafka-trigger -f /whisk.system/messaging/kafkaFeed -p brokers "[\"my-broker-ip:broker-port\"]" -p topic db-topic -p isJSONData true --debug` and the response always includes a frustating ``` "response": { "result": { "error": "AssertionError: url is not valid" }, "status": "application error", "success": false }, ``` What's curious to me is it seems like the broker is never even being hit? I ran netcat on the port I provided and it returns nothing at all. I can't find any logs that give me a clue as to what's going wrong. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563303308007400?thread_ts=1563303308.007400&cid=C3TPCAQG1 ---- 2019-07-16 20:27:49 UTC - Pepi Paraskevoulakou: guys still cannot figure it out error: Package update failed: Put <https://83.212.97.203/api/v1/namespaces/whisk.system/packages/apimgmt?overwrite=true>: dial tcp 83.212.97.203:443: getsockopt: connection refused https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563308869008000 ---- 2019-07-16 20:28:17 UTC - Pepi Paraskevoulakou: anyone advices? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563308897008300 ---- 2019-07-16 20:46:32 UTC - Rodric Rabbah: @Pepi Paraskevoulakou i assume you can’t `curl <https://83.212.97.203>`? your controller is not reachable in that case (i’ll review your comments above to see if there are clues that i can help with) https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563309992009300 ---- 2019-07-16 20:47:34 UTC - Rodric Rabbah: @Duncan Beard it looks like the `/whisk.system/messaging/kafkaFeed` rejected the request, which would explain why you see nothing from the broker https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563310054009400?thread_ts=1563303308.007400&cid=C3TPCAQG1 ---- 2019-07-16 20:47:48 UTC - Rodric Rabbah: try `wsk activation list` to see activations for that action `/whisk.system/messaging/kafkaFeed` and check the logs https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563310068009600?thread_ts=1563303308.007400&cid=C3TPCAQG1 ---- 2019-07-16 20:48:27 UTC - Rodric Rabbah: id have to look at the source code for the action to see know what the issue is. Maybe @Jason Peterson or @dubee know better. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563310107009800?thread_ts=1563303308.007400&cid=C3TPCAQG1 ---- 2019-07-16 20:57:01 UTC - Pepi Paraskevoulakou: thank you @Rodric Rabbah! https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563310621010300 ---- 2019-07-16 21:55:41 UTC - Duncan Beard: `wsk -i activation list` just returns "activations"... https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563314141010400?thread_ts=1563303308.007400&cid=C3TPCAQG1 ---- 2019-07-16 21:56:43 UTC - Rodric Rabbah: Can you run that command twice. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563314203010900?thread_ts=1563303308.007400&cid=C3TPCAQG1 ---- 2019-07-16 21:56:50 UTC - Rodric Rabbah: The activation indexing is lazy. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563314210011300?thread_ts=1563303308.007400&cid=C3TPCAQG1 ---- 2019-07-16 22:04:50 UTC - Duncan Beard: Ah! I see "application error" for every whisk.system/kafkaFeed entry https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563314690011500?thread_ts=1563303308.007400&cid=C3TPCAQG1 ---- 2019-07-16 22:08:16 UTC - Rodric Rabbah: Any logs in those messages. I’m afraid we have to look at that actions source code for a clue. I am not familiar with it. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563314896012400?thread_ts=1563303308.007400&cid=C3TPCAQG1 ---- 2019-07-16 22:08:28 UTC - Rodric Rabbah: Could be some missing parameter or bad validation. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563314908012900?thread_ts=1563303308.007400&cid=C3TPCAQG1 ---- 2019-07-16 22:18:23 UTC - Duncan Beard: Ah, looks like it was a missing parameter. Now I have another rabbit hole to go down. Thank you @Rodric Rabbah! https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563315503013100?thread_ts=1563303308.007400&cid=C3TPCAQG1 ----
