You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwhisk.apache.org by OpenWhisk Team Slack <ra...@apache.org> on 2019/04/18 07:40:33 UTC
[slack-digest] [2019-04-17] #general
2019-04-17 06:40:34 UTC - owen: thank you, I'll take a look
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555483234052700?thread_ts=1555396476.027800&cid=C3TPCAQG1
----
2019-04-17 14:36:54 UTC - Rob Allen: Beijing time is _CST_ …
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555511814053700
----
2019-04-17 14:54:23 UTC - Shazron Abdullah: (China Standard Time not to be confused with Central ST or Cuba ST...)
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555512863054400
----
2019-04-17 16:06:31 UTC - ed: are there any predefined env variables set by openwhisk or ibm cloud functions? I would like my code to know that I'm running inside ow or ibmcf
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555517191055500
----
2019-04-17 16:09:29 UTC - Rodric Rabbah: you can check for the presence of `process.env.__OW_ACTIVATION_ID`
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555517369055900
----
2019-04-17 16:10:11 UTC - Rodric Rabbah: more generally, <https://github.com/apache/incubator-openwhisk/blob/master/docs/actions.md#accessing-action-metadata-within-the-action-body>
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555517411056100
----
2019-04-17 16:14:51 UTC - James Thomas: does anyone know what the caching policy is for custom docker images in openwhisk? when I update an existing custom runtime image in docker hub, there seems to be a delay in that image being available to the action using that image.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555517691057300
----
2019-04-17 16:16:06 UTC - Rodric Rabbah: You have to update the action to force a docker refresh: wsk action update name
Is enough
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555517766058100
----
2019-04-17 16:16:20 UTC - Markus Thömmes: not sure that's true anymore
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555517780058500
----
2019-04-17 16:16:25 UTC - Rodric Rabbah: ah ok
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555517785058800
----
2019-04-17 16:16:36 UTC - Markus Thömmes: I think we do something "smart" based on whether you use latest or some tag
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555517796059100
----
2019-04-17 16:16:52 UTC - Markus Thömmes: using latest + @Rodric Rabbah's tip should do the trick, I think?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555517812060000
----
2019-04-17 16:16:54 UTC - Rodric Rabbah: ah. Vaguely remembering that.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555517814060100
----
2019-04-17 16:17:03 UTC - James Thomas: based on my informal testing recently, even if I delete the action and re-create it seems to use the old image for a short period
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555517823060400
----
2019-04-17 16:17:06 UTC - James Thomas: like < 30 mins
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555517826060600
----
2019-04-17 16:17:26 UTC - James Thomas: I will try again and see where I get to…..
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555517846060900?thread_ts=1555517846.060900&cid=C3TPCAQG1
----
2019-04-17 16:17:49 UTC - James Thomas: didn’t know about the `latest` thing - guess this isn’t documented anywhere? :slightly_smiling_face:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555517869061400
----
2019-04-17 16:18:01 UTC - Markus Thömmes: I *think* it is! :smile:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555517881061700
----
2019-04-17 16:18:08 UTC - James Thomas: :shocked_face_with_exploding_head:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555517888061900
----
2019-04-17 16:18:38 UTC - Markus Thömmes: maybe I'm mistaken though, lemme skim through the codez
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555517918062200
----
2019-04-17 16:20:05 UTC - Markus Thömmes: <https://github.com/apache/incubator-openwhisk/blob/master/core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/docker/DockerContainer.scala#L107-L122>
Yeah, I'm mistaken. "latest" vs something else only triggers error handling on the pull call. Basically, if you use latest we assume you always want latest and don't tolerate a failure to pull
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555518005062900
----
2019-04-17 16:22:49 UTC - Rodric Rabbah: <https://github.com/apache/incubator-openwhisk/pull/3813>
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555518169063100
----
2019-04-17 16:23:23 UTC - Rodric Rabbah: ?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555518203063300
----
2019-04-17 16:31:26 UTC - Carlos Santana: Use tag latest tag to always pull, or push with a new tag to pull. There is caching to not do the pull for none latest
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555518686065200?thread_ts=1555517846.060900&cid=C3TPCAQG1
----
2019-04-17 16:44:47 UTC - James Thomas: @Carlos Santana get back on holiday sir!
palm_tree : Carlos Santana
beach_with_umbrella : Carlos Santana
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555519487065400?thread_ts=1555517846.060900&cid=C3TPCAQG1
----
2019-04-17 17:19:25 UTC - ed: Does openwhisk somehow reuse whatever is in a docker image? I'm running a function that works sometimes. Seems to work right after I update it, then it starts to fail erratically.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555521565066800
----
2019-04-17 17:20:33 UTC - ed: (I'm new to Docker so this question might not make sense)
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555521633067600
----
2019-04-17 17:21:21 UTC - ed: I'm just curious why the code, which is supposed to be stateless, works sometimes, fails others with same data.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555521681068300
----
2019-04-17 17:55:51 UTC - Rob Allen: @ed The Docker container is reused, yes, if you call again within a short time after the first call.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555523751069100
----
2019-04-17 18:08:59 UTC - ed: @Rob Allen thank you. In my dockerfile I had 'FROM openwhisk/python3action' and now I'm using 'ibmfunctions/action-python-v3.7' and it made a difference.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555524539070300
----
2019-04-17 18:09:18 UTC - ed: That helped
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555524558070800
----
2019-04-17 18:09:24 UTC - Rob Allen: I'm guessing you have some state in there somewhere
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555524564071200
----
2019-04-17 18:09:27 UTC - ed: No issues so far.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555524567071400
----
2019-04-17 18:09:28 UTC - Rob Allen: storing something to a global variable?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555524568071600
----
2019-04-17 18:09:46 UTC - ed: I would have to take a closer look, but its the exact same code.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555524586071900
----
2019-04-17 18:10:37 UTC - Rodric Rabbah: it’s possible there is even a memory leak inside the action itself --- iirc there is an annotation to the activation record if the action failed due to memory exhaustion
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555524637072900
----
2019-04-17 18:12:23 UTC - ed: @Rodric Rabbah will look into that, thank you
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555524743073300
----