RE: [DISCUSS] release openwhisk-runtime-go 1.14.0

I'd prefer to "get it right" in this release, so if we want to do some renaming/pruning if the docker images for this release I'm happy to wait. --dave From: "Michele Sciabarra" To: dev@openwhisk.apache.org Date: 10/03/2019 11:11 AM Subject:[EXTERNAL] Re: [DISCUSS] release

Re: [DISCUSS] release openwhisk-runtime-go 1.14.0

We may also remove the "standalone" actionloop as now we build the proxies from sources. -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Rodric Rabbah To: dev@openwhisk.apache.org Subject: Re: [DISCUSS] release openwhisk-runtime-go 1.14.0 Date: Thursday,

Re: [DISCUSS] release openwhisk-runtime-go 1.14.0

I suggested in the call yesterday to remove the “loop” in the name. Is that too much to include in this release? On Thu, Oct 3, 2019 at 9:43 AM Michele Sciabarra wrote: > Please note that currently all the runtimes build the proxy directly from > the sources of the master on github. > > I did

Re: [DISCUSS] release openwhisk-runtime-go 1.14.0

Please note that currently all the runtimes build the proxy directly from the sources of the master on github. I did it as a temporary workaround for the "de incubation". If we want to make things properly we should release first the golang runtime (without knative, no problem for now), then

Re: [DISCUSS] release openwhisk-runtime-go 1.14.0

> On 3 Oct 2019, at 14:28, David P Grove wrote: > > I'd like to make a release of the go runtime to enable us to then make > updated releases of all the action-loop based runtimes (including the rust > 1.34 runtime which has never been released). > > I'd suggest we make this release without

[DISCUSS] release openwhisk-runtime-go 1.14.0

I'd like to make a release of the go runtime to enable us to then make updated releases of all the action-loop based runtimes (including the rust 1.34 runtime which has never been released). I'd suggest we make this release without waiting to merge the Knative support PR (#106) to the go

Capturing Activation response size as part of User Events (#4660)

Hi Team, I would like to capture the activation response size as part of user event data. This would allow us to understand the distribution of response size across various invocations. This would be useful input for the Activation Persister Service work (#4632) For this purpose a PR is opened

[slack-digest] [2019-10-02] #random

2019-10-02 14:00:15 UTC - mmarth: on KNative not moving to CNCF: hushed : Dominic Kim, Bruno Wego https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1570024815017900 2019-10-02 14:17:14 UTC - Rodric Rabbah: _im curious if

[slack-digest] [2019-10-02] #kubernetes

2019-10-02 14:38:39 UTC - Matt Rutkowski: set up a reminder “Tech Interchange Web Meeting (bi-weekly) https://zoom.us/my/asfopenwhisk” in this channel at 10AM every other Wednesday (next occurrence is October 16th), Eastern Daylight Time.

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

2019-10-02 02:39:40 UTC - Mayank Jha: is there a shortcut to replace the existing runtimes for a different cpu architecture say arm64 ? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1569983980071300?thread_ts=1569983980.071300=C3TPCAQG1 2019-10-02 02:40:16 UTC - Rodric Rabbah: I don’t