[slack-digest] [2019-03-26] #general

[OpenWhisk Team Slack <ra...@apache.org>]

2019-03-26 13:23:04 UTC - Adrian Schuepbach: @Neeraj Mangal I tried to investigate more about the SIGBUS error of the Java NOP action.
It seems that reserving hugepages on the physical hosts causes this problem.
I have 96GB RAM in my hosts. When I set the number of hugepages to 8192 (16GB), then I get the SIGBUS problem inside the containers executing the OpenWhisk Java actions.
However, the hugepages are not even used. The counters on the physical host stay at 0 while executing the actions.
Also, I disabled transparent hugepages, which also did not help.
It is unclear to me, why just reserving space for hugepages causes this problem in the container, which don't even see them.
So far it seems that only the Java NOP function runs into this problem. A nop function implemented in nodejs works fine.

Now I could try to reserve a lower number of hugepages so that it works, but it is still confusing why this problem happens at all.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553606584417800?thread_ts=1553025387.329000&cid=C3TPCAQG1
----
2019-03-26 16:20:42 UTC - Vincent Hou: @Carlos Santana Carlos, in jenkins pipeline, how do we stop one invoker service? What tests do we need to run with one invoker down?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553617242419500?thread_ts=1553617242.419500&cid=C3TPCAQG1
----
2019-03-26 16:24:28 UTC - Carlos Santana: You could write a scala test that does the following
- ssh into invoker VM and does a `docker kill invoker`
- Run a simple invoke hello action and assert that invoke worked, one of the remaining invokers handle the invoke
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553617468419700?thread_ts=1553617242.419500&cid=C3TPCAQG1
----
2019-03-26 16:44:54 UTC - Rodric Rabbah: @Carlos Santana you can disable ‘at’ here notifications and restrict them only to admins
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553618694420000?thread_ts=1553267210.368700&cid=C3TPCAQG1
----
2019-03-26 16:45:08 UTC - Rodric Rabbah: only the workspace owner can do it, and i think that’s you
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553618708420200?thread_ts=1553267210.368700&cid=C3TPCAQG1
----
2019-03-26 16:45:26 UTC - Carlos Santana: I can disable it only for @Vincent Hou :troll:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553618726420400?thread_ts=1553267210.368700&cid=C3TPCAQG1
----
2019-03-26 18:35:32 UTC - Dave Grove: fyi the homebrew formulae for `wsk` is now updated to 0.10.0-incubating
tada : Carlos Santana
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553625332422500?thread_ts=1553625332.422500&cid=C3TPCAQG1
----
2019-03-26 18:46:41 UTC - Carlos Santana: @Dave Grove you know why I don't get a version? to verify I have 0.10?
```
$ brew upgrade wsk
$ which wsk
/usr/local/bin/wsk
$ wsk property get --cliversion
whisk CLI version	not set
```
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553626001422700?thread_ts=1553625332.422500&cid=C3TPCAQG1
----
2019-03-26 18:50:27 UTC - Markus Thömmes: don't we have such a test?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553626227423900?thread_ts=1553617242.419500&cid=C3TPCAQG1
----
2019-03-26 18:51:16 UTC - Dave Grove: i don’t know.  I see the same behavior.  I have not tried to figure out where that property is coming from.  It really should be embedded into the executable somehow, but it isn’t
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553626276424100?thread_ts=1553625332.422500&cid=C3TPCAQG1
----
2019-03-26 18:52:33 UTC - Dave Grove: one way to tell is that you’ll have the `wsk project` subcommand in 0.10 and not in 0.9.  but that’s a lousy way to tell.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553626353425100
----
2019-03-26 19:02:33 UTC - Dave Grove: sigh.  the version one gets from the 0.10.0-incubating download on github is also not very useful.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553626953426000
----
2019-03-26 19:02:46 UTC - Dave Grove: 
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553626966426100
----
2019-03-26 19:02:54 UTC - Dave Grove: should be 0.10.0-incubating
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553626974426600
----
2019-03-26 19:08:45 UTC - Dave Grove: opened some issues in the cli project.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553627325427500
----
2019-03-26 20:36:35 UTC - Carlos Santana: well the way our brew i setup, it's doing a gradle and compile on the user's machine at the time of the installation
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553632595428000?thread_ts=1553625332.422500&cid=C3TPCAQG1
----
2019-03-26 20:37:07 UTC - Carlos Santana: so there should be something perhaps in the branch release a file with a version string that get's used when compiling is my 2 cents
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553632627428200?thread_ts=1553625332.422500&cid=C3TPCAQG1
----
2019-03-26 20:37:22 UTC - Carlos Santana: @Justin Halsall would know more, you can reach out to him
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553632642428400?thread_ts=1553625332.422500&cid=C3TPCAQG1
----
2019-03-26 20:40:20 UTC - Dave Grove: formula is simple enough.  it just does a `govendor sync; go build` on the source tar ball it downloaded.  src tarball should probably have a version embedded in a .go file
+1 : Carlos Santana
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553632820428600?thread_ts=1553625332.422500&cid=C3TPCAQG1
----
2019-03-26 20:40:44 UTC - Dave Grove: sometihng to fix for 0.10.1 …
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553632844428800?thread_ts=1553625332.422500&cid=C3TPCAQG1
----
2019-03-26 21:04:46 UTC - Carlos Santana: yes it should take 6 days :wink:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553634286429100?thread_ts=1553625332.422500&cid=C3TPCAQG1
----
2019-03-26 21:30:31 UTC - Zohaib Khan: How does auth work the kwsk project?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553635831429600?thread_ts=1553635831.429600&cid=C3TPCAQG1
----
2019-03-26 22:21:22 UTC - Vincent Hou: @Rodric Rabbah @Carlos Santana I submitted a PR to add the shoot invoker test. I used node() syntax to access the specific vm running invoker1 and run docker stop command to stop it. Then run the test case of WskActionTests to test if one invoker still works.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553638882431200?thread_ts=1553638882.431200&cid=C3TPCAQG1
----
2019-03-26 22:21:56 UTC - Vincent Hou: <https://github.com/apache/incubator-openwhisk/pull/4396>
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553638916431400
----
2019-03-26 22:22:51 UTC - Carlos Santana: Very clever @Vincent Hou :thumbsup: 
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553638971431800?thread_ts=1553638882.431200&cid=C3TPCAQG1
----
2019-03-26 22:27:28 UTC - Vincent Hou: @Carlos Santana @Rodric Rabbah but it will be very handy that openwhisk can support direct command to stop a specific service of the deployment.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553639248432900?thread_ts=1553639248.432900&cid=C3TPCAQG1
----
2019-03-26 22:28:21 UTC - Carlos Santana: PRs welcome !  But I don’t think the end users of OpenWhisk are asking for this feature 
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1553639301433800?thread_ts=1553639248.432900&cid=C3TPCAQG1
----