What to do of go runtime and the proxy?

[Michele Sciabarra <mi...@sciabarra.com>]

In the Go runtime it was mentioned in a comment that versions of go before 1.15 are unsafe.
What is exactly the problem? Should we then drop runtimes for go from 1.11 to 1.14?
Whar about the proxies for other languages? They are built with older versions of Go, should we change all tbe runtimes that uses the go proxy to build with go 1.15?
-- 
  Michele Sciabarra
  michele@sciabarra.com

Re: What to do of go runtime and the proxy?

[Dominic Kim <st...@gmail.com>]

+1 to Dave's opinion.

And thank you Mike for all your efforts.

-dom

2020년 8월 25일 (화) 오후 10:55, David P Grove <gr...@us.ibm.com>님이 작성:

>
> Thanks for all the work on this Michele!
>
> "Michele Sciabarra" <mi...@sciabarra.com> wrote on 08/24/2020 04:30:52
> PM:
> >
> > In the Go runtime it was mentioned in a comment that versions of go
> > before 1.15 are unsafe.
> > What is exactly the problem? Should we then drop runtimes for go
> > from 1.11 to 1.14?
>
> My advice would be that we skip 1.14.  We also drop the support for 1.11
> and 1.12 as being past their end-of-life.
>
> We do a release of openwhisk-runtime-go that supports go 1.13 and go 1.15.
> We could omit go 1.13, but I believe it is harmless to include it since the
> work is already done and the problems that Matt raised are specific to go
> 1.14.  Some people might find it useful to have an openwhisk-runtime-go
> release that supported go 1.13.
>
> In core openwhisk's runtimes.json, I would suggest only adding go 1.15
> (skip over go 1.13). Go 1.13 is about to go end-of-life, so let's not add a
> runtime that we'll just have to remove almost immediately.
>
> > Whar about the proxies for other languages? They are built with
> > older versions of Go, should we change all tbe runtimes that uses
> > the go proxy to build with go 1.15?
>
> As soon as we get an official release of openwhisk-runtime-go with go 1.15,
> we can update the proxies for the actionloop based runtime to use go 1.15
> as the builder and the new openwhisk-runtime-go release as the source for
> the proxy.  I can do the work for this; it's purely mechanical.
>
> --dave
>

Re: What to do of go runtime and the proxy?

[David P Grove <gr...@us.ibm.com>]

Thanks for all the work on this Michele!

"Michele Sciabarra" <mi...@sciabarra.com> wrote on 08/24/2020 04:30:52
PM:
>
> In the Go runtime it was mentioned in a comment that versions of go
> before 1.15 are unsafe.
> What is exactly the problem? Should we then drop runtimes for go
> from 1.11 to 1.14?

My advice would be that we skip 1.14.  We also drop the support for 1.11
and 1.12 as being past their end-of-life.

We do a release of openwhisk-runtime-go that supports go 1.13 and go 1.15.
We could omit go 1.13, but I believe it is harmless to include it since the
work is already done and the problems that Matt raised are specific to go
1.14.  Some people might find it useful to have an openwhisk-runtime-go
release that supported go 1.13.

In core openwhisk's runtimes.json, I would suggest only adding go 1.15
(skip over go 1.13). Go 1.13 is about to go end-of-life, so let's not add a
runtime that we'll just have to remove almost immediately.

> Whar about the proxies for other languages? They are built with
> older versions of Go, should we change all tbe runtimes that uses
> the go proxy to build with go 1.15?

As soon as we get an official release of openwhisk-runtime-go with go 1.15,
we can update the proxies for the actionloop based runtime to use go 1.15
as the builder and the new openwhisk-runtime-go release as the source for
the proxy.  I can do the work for this; it's purely mechanical.

--dave

Re: What to do of go runtime and the proxy?

[Matt Rutkowski <mr...@us.ibm.com>]

Avoid 1.14 for productions/releases (skip to 1.15) is what I would advise 
based upon feedback from our container runtime experts...

Posted specifics in the PR which I assume prompted this post...
https://github.com/apache/openwhisk-runtime-go/pull/128

In 1.15, the put retries (loops) and other safety measure within the lower 
level system libs. to correct for most of the exposures.

-mr




From:   "Michele Sciabarra" <mi...@sciabarra.com>
To:     dev@openwhisk.apache.org
Date:   08/24/2020 03:31 PM
Subject:        [EXTERNAL] What to do of go runtime and the proxy?




In the Go runtime it was mentioned in a comment that versions of go before 
1.15 are unsafe.
What is exactly the problem? Should we then drop runtimes for go from 1.11 
to 1.14?
Whar about the proxies for other languages? They are built with older 
versions of Go, should we change all tbe runtimes that uses the go proxy 
to build with go 1.15?
-- 
  Michele Sciabarra
  michele@sciabarra.com