[slack-digest] [2019-02-18] #wskdeploy

2019-02-18 08:01:56 UTC - Thomas Peikert: Hey, I opened a PR to update some runtime tests since some runtimes were removed in a recent openwhisk pull request and that was leading to test failures on new branches:

[slack-digest] [2019-02-18] #apigateway

2019-02-18 11:59:44 UTC - Lars Andersson: I created an issue today which requires attention. The build is broken since alpine v 3.9 was released. The jemalloc and jemalloc_dev packages are no longer present in the alpine image. Are there any specific reasons we are using those packages, or can

[slack-digest] [2019-02-18] #general

2019-02-18 05:24:10 UTC - Thomas Peikert: is 512MB still action memory limit? on IBM at least I can select memory settings of up to 2048MB. But the docs still say 512MB for OpenWhisk

[VOTE] Release Apache OpenWhisk Composer (incubating) 0.10.0

The Apache OpenWhisk community has voted to release Apache OpenWhisk Composer (incubating) version 0.10.0. The voting thread can be found here: https://lists.apache.org/thread.html/801edac7a4d58436a5411fc1fbca523f24056195bdb149f9c2cdc2b8@%3Cdev.openwhisk.apache.org%3E We request that IPMC

Re: [VOTE] - release Apache OpenWhisk Composer 0.10.0

+1 Release as Apache OpenWhisk 0.10.0-incubating: openwhisk composer Checklist for reference: [x] Download links are valid. [x] Checksums and PGP signatures are valid. [x] DISCLAIMER is included. [x] Source code artifacts have correct names matching the current release. [x] LICENSE and NOTICE

Re: nodejs runtime packages in base images

-1 on this I'm afraid. I agree with everything Carlos said - I think the maintance and security burden of rolling packages into the base layers outweights the ease of use concern for new users. On Sat, 16 Feb 2019 at 14:13, Carlos Santana wrote: > > With my vendor hat: > > This means anyone