Thanks Dominic, I reviewed the PR and left a minor question. LGTM.
On Sun, Feb 25, 2024 at 1:18 AM Dominic Kim wrote:
> Now the main PR [1] has passed all CI tests and it has been approved.
> Any comments would be appreciated.
> Since it's a kind of breaking change, I would wait for several
+1 to release
./rcverify.sh openwhisk-runtime-go 1.24.0 rc1
rcverify.sh (script SHA1: 6DC9 462D 3035 5FD0 ADE6 9EF9 D0DF 1A25 13E1
5CFD)
working in the following directory:
/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.icDrzl4p
fetching tarball and signatures from
+1 long overdue!
On Sat, Feb 10, 2024 at 10:10 PM Brendan Doyle wrote:
> +1 on the release, and I can help with anything needed on my end in
> supporting it. It’s definitely time to have a new release and have it
> include the scheduler.
>
> Brendan
>
> On Sat, Feb 10, 2024 at 7:03 PM Dominic
+1 to release python runtime
./rcverify.sh openwhisk-runtime-python 1.19.0 rc1
rcverify.sh (script SHA1: 6DC9 462D 3035 5FD0 ADE6 9EF9 D0DF 1A25 13E1
5CFD)
working in the following directory:
/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.WF5FoyPZ
fetching tarball and signatures from
+1 to release
./rcverify.sh openwhisk-runtime-php 1.20.0 rc1
rcverify.sh (script SHA1: 6DC9 462D 3035 5FD0 ADE6 9EF9 D0DF 1A25 13E1
5CFD)
working in the following directory:
/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.wz63x0dB
fetching tarball and signatures from
+1 to release java 1.19
./rcverify.sh openwhisk-runtime-java 1.19.0 rc1
rcverify.sh (script SHA1: 454D AA8B 2A1C D74A 1E17 FA6F 9D20 15A2 EA21
2371)
working in the following directory:
/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.e9l2NGWP
fetching tarball and signatures from
+1 to release nodejs 1.22.0 rc1
./rcverify.sh openwhisk-runtime-nodejs 1.22.0 rc1
rcverify.sh (script SHA1: 454D AA8B 2A1C D74A 1E17 FA6F 9D20 15A2 EA21
2371)
working in the following directory:
/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.7Cax9V4H
fetching tarball and signatures from
+1 to release
lgtm
> ./rcverify.sh openwhisk-runtime-swift 1.18.0 rc1
rcverify.sh (script SHA1: 454D AA8B 2A1C D74A 1E17 FA6F 9D20 15A2 EA21
2371)
working in the following directory:
/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.tLdJNhiA
fetching tarball and signatures from
Makes sense for me.
On Sun, Jul 9, 2023 at 3:59 PM David Grove wrote:
> Hi,
>
> I’ve submitted a PR (
> https://github.com/apache/openwhisk/pull/5426) that updates the set of
> “default” runtimes for OpenWhisk by removing a number of old runtimes whose
> upstream language
+1 to release
./rcverify.sh openwhisk-runtime-python 1.18.0 rc1
rcverify.sh (script SHA1: 454D AA8B 2A1C D74A 1E17 FA6F 9D20 15A2 EA21
2371)
working in the following directory:
/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.4PQg21VM
fetching tarball and signatures from
+1 from me
./rcverify.sh openwhisk-runtime-java 1.18.0 rc1
rcverify.sh (script SHA1: 454D AA8B 2A1C D74A 1E17 FA6F 9D20 15A2 EA21
2371)
working in the following directory:
/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.6aBxg4Bx
fetching tarball and signatures from
+1 from me also
./rcverify.sh openwhisk-runtime-docker 1.15.0 rc1
rcverify.sh (script SHA1: 454D AA8B 2A1C D74A 1E17 FA6F 9D20 15A2 EA21
2371)
working in the following directory:
/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.xeBGwijb
fetching tarball and signatures from
+1 checked with rcverify
./rcverify.sh openwhisk-runtime-php 1.18.0 rc1
rcverify.sh (script SHA1: 454D AA8B 2A1C D74A 1E17 FA6F 9D20 15A2 EA21
2371)
working in the following directory:
/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.gCuQAOS8
fetching tarball and signatures from
+1 checked with rcverify
./rcverify.sh openwhisk-runtime-dotnet 1.17.0 rc1
rcverify.sh (script SHA1: 454D AA8B 2A1C D74A 1E17 FA6F 9D20 15A2 EA21
2371)
working in the following directory:
/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.vhPFmG1P
fetching tarball and signatures from
+1 to release, checked with rcverify
> ./tools/rcverify.sh openwhisk-runtime-go 1.22.0 rc1
rcverify.sh (script SHA1: 454D AA8B 2A1C D74A 1E17 FA6F 9D20 15A2 EA21
2371)
working in the following directory:
/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.ZjMPgYCZ
fetching tarball and
Thanks Shawn - taking a look.
-r
On Sun, Nov 20, 2022 at 10:17 PM Shawn Black
wrote:
> Whiskers,
>
> We've had a PR for the .NET 6.0 runtime pending for awhile, but has been
> awaiting feedback from the original author and it has seems to have
> become stale.
>
> I've created a new PR for the
We should adopt a similar post since we’re doing the same thing :)
-r
> On Sep 12, 2022, at 5:04 AM, Bertrand Delacretaz
> wrote:
>
> Hi,
>
> Michele Sciabarra wrote:
>> ...Since OpenWhisk is built on Akka, how this change will affect OpenWhisk?
>
> FWIW, other ASF projects are impacted,
+1 to release
./tools/rcverify.sh openwhisk-runtime-go 1.20.0 rc1
rcverify.sh (script SHA1: 4079 F167 3437 E1DD 4655 76A6 1504 44FB B27B
78CE)
working in the following directory:
/var/folders/tt/95md5wxj7k52p4p6ssx653lmgp/T/tmp.6TikGWta
fetching tarball and signatures from
Thanks for the proposal - my immediate reaction is that this changes the
programming model in a potentially disruptive way. The function signature
now is dictionary (string->json) in and same type out. This allows
functions to be composed in a sequence because all functions have a uniform
track
> <
> https://mailtrack.io?utm_source=gmail_medium=signature_campaign=signaturevirality11;
> >
> 22.
> 05. 19. 오전 10:36:28
>
> 2022년 5월 16일 (월) 오후 10:26, Rodric Rabbah 님이 작성:
>
> > This is a very useful feature indeed. It would help to separate the
> >
+1 Approve this release
> ./rcverify.sh openwhisk-runtime-nodejs 1.20.0 rc1
rcverify.sh (script SHA1: 4079 F167 3437 E1DD 4655 76A6 1504 44FB B27B
78CE)
working in the following directory:
/var/folders/tt/95md5wxj7k52p4p6ssx653lmgp/T/tmp.iADcBKxd
fetching tarball and signatures from
+1 to release Apache OpenWhisk Runtime Go (v1.19.0, rc1)
> ./rcverify.sh openwhisk-runtime-go 1.19.0 rc1
rcverify.sh (script SHA1: 4079 F167 3437 E1DD 4655 76A6 1504 44FB B27B
78CE)
working in the following directory:
/var/folders/tt/95md5wxj7k52p4p6ssx653lmgp/T/tmp.afDI8TE1
fetching
This is a very useful feature indeed. It would help to separate the
proposal (
https://github.com/apache/openwhisk/pull/5229/files?file-filters%5B%5D=.md=false)
from the implementation rather than combine the two into a single PR. I'll
review the proposal first.
-r
On Mon, May 16, 2022 at 6:03
You will need to put the library in the docker image for that runtime. Then
you don’t have to bundle it with the action.
-r
On Fri, Mar 4, 2022 at 9:04 AM Aro0oj wrote:
> Hi ,
> I have installed Lean OpenWhisk on raspberry pi 4 B with 32 OS (raspbain
> OS)
>
> I have created python action in
Congratulations Brendan and Cosmin!
-r
On Wed, Feb 23, 2022 at 6:30 AM Matt Rutkowski
wrote:
> Welcome and congratulations Brendan and Cosmin!
>
> Kind regards,
> Matt
>
That's great Dominic!
-r
On Tue, Feb 8, 2022 at 8:03 PM Dominic Kim wrote:
> Dear whiskers.
>
> The last PR [1] to run the new scheduler is ready to merge.
> There is still room for improvement, but I believe this would improve the
> performance in general.
> Hope this helps many downstream.
>
Thanks for sharing this Matt - it's on my stack to look at. We should
really upgrade our Java runtime for actions.
-r
On Thu, Jan 6, 2022 at 1:43 AM Matt Welke wrote:
> I posted this on Slack. Figured it'd be nice to copy it in here too:
>
> > Hey I just realized I forgot to share this here
Indeed - I have the same experience with gpg --version gpg (GnuPG/MacGPG2)
2.2.32 (libgcrypt 1.8.8)
computing sha512 for openwhisk-client-js-3.21.6-sources.tar.gz... ok
openwhisk-client-js-3.21.6-sources.tar.gz:
4A56223D E7189F6F 7393DB08 ED58F128 639205D7 03CEA4EA A91BF3B5 73563C4E
342C9202
Makes sense/+1… thanks Dominic. I was hoping your last Change to increase
the Grace would have worked.
-r
On Mon, Jan 3, 2022 at 7:26 PM Dominic Kim wrote:
> Dear whiskers.
>
> I've found the performance tests have not been working so far.
> According to the following test, it is shown it
hi Yilin - that's great. One of us can help with this when you're ready and
I'm happy to review it ahead of time.
-r
On Tue, Nov 16, 2021 at 4:24 AM Yilin Zeng wrote:
> Hi Community,
>
>
> I am Yilin, from the Apache APISIX community. APISIX is a Cloud-native API
> gateway, and it is also a
eys... ok (new keys imported (processed 13 unchanged 1))
gpg: key 72AF0CC22C4CF320: public key "Vincent Hou (Release manager of
OpenWhisk) " imported
gpg: key 22907064147F886E: public key "Dave Grove "
imported
gpg: key 44667BC927C86D51: "Rodric Rabbah " not changed
gpg:
+1
-r
> On Sep 24, 2021, at 10:05 AM, David P Grove wrote:
>
>
> Is there any interest in maintaining this runtime? It's based on a fairly
> old version of ballerina (0.990.2), the build has been broken for months,
> and we've never made a release.
>
> My inclination would be to archive
+1 to release openwhisk-package-alarms 2.3.0 rc1
Checked with rcverify.
> ./rcverify.sh openwhisk-package-alarms 2.3.0 rc1
rcverify.sh (script SHA1: 7FC5 5DBE 1809 6D92 DEFF 0E31 D138 059B 8F27
20F7)
working in the following directory:
+1 to release all 5 runtime modules described below. Checked all with
rcverify.sh
> ./rcverify.sh openwhisk-runtime-java 1.17.0 rc1
rcverify.sh (script SHA1: A042 C31A 38AF 8EBB F150 0819 A448 DE52 BFE1
258F)
working in the following directory:
+1 to release openwhisk-runtime-nodejs 1.19.0. Release checked with
rcverify.
> ./rcverify.sh openwhisk-runtime-nodejs 1.19.0 rc1
rcverify.sh (script SHA1: A042 C31A 38AF 8EBB F150 0819 A448 DE52 BFE1
258F)
working in the following directory:
+1 to release openwhisk-runtime-dotnet 1.16.0. Released checked with
rcverify.sh
> ./rcverify.sh openwhisk-runtime-dotnet 1.16.0 rc1
rcverify.sh (script SHA1: A042 C31A 38AF 8EBB F150 0819 A448 DE52 BFE1
258F)
working in the following directory:
+1 to release openwhisk-runtime-rust 1.3.0. Checked with reverify.
> ./rcverify.sh openwhisk-runtime-rust 1.3.0 rc1
rcverify.sh (script SHA1: A042 C31A 38AF 8EBB F150 0819 A448 DE52 BFE1
258F)
working in the following directory:
/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.1XidRPFr
We've seen demand for run and done actions in several scenarios and
recently a member of the community opened an issue related to this feature
https://github.com/apache/openwhisk/issues/5143.
I intend to suggest a way of implementing this and will work with the
interested Chiranjeevi who opened
I opened an issue https://github.com/apache/openwhisk/issues/5146 to
describe an issue we encountered with an enterprise client where web
actions returning some non standard HTTP status codes fail.
I think we can widen the handling of the status codes in the web actions
handler by first doing the
+1 approve the release
I checked with rcverify and manual inspection.
> ./rcverify.sh openwhisk-runtime-go 1.18.0 rc1
rcverify.sh (script SHA1: A042 C31A 38AF 8EBB F150 0819 A448 DE52 BFE1
258F)
working in the following directory:
/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.3mP33QS3
+1 to release openwhisk-runtime-nodejs 1.18.0 rc1. Checked with rcverify.
> ./rcverify.sh openwhisk-runtime-nodejs 1.18.0 rc1
rcverify.sh (script SHA1: A042 C31A 38AF 8EBB F150 0819 A448 DE52 BFE1
258F)
working in the following directory:
+1 to the release of openwhisk-catalog-1.0.0 rc1
> ./rcverify.sh openwhisk-catalog 1.0.0 rc1
rcverify.sh (script SHA1: A042 C31A 38AF 8EBB F150 0819 A448 DE52 BFE1
258F)
working in the following directory:
/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.IoFSKPbG
fetching tarball and
I observed this once by accident - if stem cells aren’t created initially at
invoker startup, ie they fail for whatever reason, then the invokers will
operate without them. That is if the pool doesn’t initialize correctly it’s
always empty.
Has anyone else encountered this? I will file an
I wrote up my suggested workaround in
https://github.com/apache/openwhisk/issues/5132.
-r
On Thu, Jun 10, 2021 at 12:20 PM Rodric Rabbah wrote:
> Cool. I can take it I already as I am looking through other libraries.
>
> -r
>
> > On Jun 10, 2021, at 12:17 PM, Tyson Norris
&
ou already have changed to accommodate this, feel free to add it,
> otherwise I can create a PR just for this.
>
> Thanks
> Tyson
>
> From: Rodric Rabbah
> Date: Thursday, June 10, 2021 at 8:14 AM
> To: dev@openwhisk.apache.org
> Subject: Re: [DISCUSS}
A number of these dependencies are coming from
com.adobe.api.platform.runtime:mesos-actor:0.0.17. I tried a more recent
version 0.0.25 (still from 2019 though) and that does not resolve the
dependency issue.
Is there still a need for the mesos actor library?
I am tracking down one other
[x] +1 Approve the release
Release verification checklist for reference:
[x] Download links are valid.
[x] Checksums and PGP signatures are valid.
[x] Source code artifacts have correct names matching the current release.
[x] LICENSE and NOTICE files are correct for each OpenWhisk
I looked at the PR - i think it's OK to keep going with rc1 and we can
still merge the PR in parallel.
On Fri, Jun 4, 2021 at 10:56 AM Matt Rutkowski
wrote:
>
>
> On 2021/06/04 09:38:01, Dominic Kim wrote:
> > Thank you, Kent for the changes.
> >
> > And I suppose we can still proceed with the
Thank you Kent for your first contribution to the project!
-r
On Thu, Jun 3, 2021 at 4:19 PM Kent Tsuenchy wrote:
> Hi,
>
> I opened a draft PR [1] on updating the README for the VS Code extension.
>
> First time contributor, so I thought I could take a look at these new IDE
> plugin releases.
> Why was it done this way in the first place? If the data comes in as a
single JSON object to the runtime, why did the runtime move a subset of
that data to env vars instead of just keeping it all within the params map
sent to the user action code?
This was done to keep the function abstraction
Hi Matt.
If using the go proxy (aka “action loop”), doesn’t it export the environment
variables before running the JVM?
-r
> On Jun 1, 2021, at 1:17 AM, Matt Welke wrote:
>
> Hi everyone,
>
> When I read the history of the GitHub PR open right for adding Java 11
> support, I learned
Awesome!
-r
> On May 27, 2021, at 5:21 AM, Dominic Kim wrote:
>
> Dear whiskers.
>
> I'd like to make the first releases of two IDE plugins[1][2].
>
> Currently, one PR[3] is ready to be merged.
>
> Please let me know if there are any other changes required before the
> releases.
>
>
Thanks for the contribution Fausto! PR looks good to me.
-r
On Wed, May 19, 2021 at 12:06 PM Fausto Ribechini <
fausto.ribech...@it.ibm.com> wrote:
> Hi, I would like to ask an enhancement for package /whisk.system/github to
> make webhook feed able to work with Github Enterprise too.
> For
+1 I approve the release
checked with rcverify
./rcverify.sh openwhisk-runtime-swift 'OpenWhisk Runtime Swift' 1.16.0 rc1
rcverify.sh (script SHA1: 4287 FB51 CAAF A0F8 EFFE 956A E004 9F9D 0DBD
E46D)
working in the following directory:
The vote for releasing Apache OpenWhisk Client Js (v3.21.4, rc1) is now
closed.
Vote result:
+1 (KeonHee, Rob, Dave, Dominic, Matt, James)
no other votes
The vote has PASSED.
The voting threads (not sure why they got split) [1, 2, 3]
[1]
+1 strongly in favor.
-r
> On May 3, 2021, at 11:40 AM, David P Grove wrote:
>
>
> We did our first unified release (OpenWhisk 20.11) at the end of November.
>
> Since then, we've released new versions of most of the runtimes and also of
> the CLI.
>
> I think getting into a rhythm of
Hi,
This is a call to vote on releasing version 3.21.4 release candidate rc1 of the
following project module with artifacts built from the Git repositories and
commit IDs listed below.
* OpenWhisk Client Js: c697f0be4a254a4d0ff8f98c4e746f479072fb7a
Hi Felix. I interested in this as you cited one of my earlier queries around
this.
At Nimbella we did implement an admin api to address the account management
issues. We don’t use wskadmin for that today but I shared in our community
slack not too long ago an example of how to use wskadmin to
+1 to release all 3
checked with rcverify
> ./rcverify.sh openwhisk-runtime-java 'OpenWhisk Runtime Java' 1.16.0 rc1
rcverify.sh (script SHA1: 4287 FB51 CAAF A0F8 EFFE 956A E004 9F9D 0DBD
E46D)
working in the following directory:
/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.bu57O91v
+1 to release OpenWhisk Runtime Rust v1.2.0
checked with rcverify
> ./rcverify.sh openwhisk-runtime-rust 'OpenWhisk Runtime Rust' 1.2.0 rc1
rcverify.sh (script SHA1: 4287 FB51 CAAF A0F8 EFFE 956A E004 9F9D 0DBD
E46D)
working in the following directory:
following Nimbella encryption API, replacing
the placeholder with the actual Slack App token.
curl
https://encrypt.nimbella.io/github.com/apache/openwhisk-website/blob/slack/apis/slack-invite.js?slacktoken=
[1] https://github.com/csantanapr/openwhisk-slackinvite
-r
> On Apr 11, 2021, at 10
Hi Courtney - I'm sorry you're having trouble with the slack auto signup. I
opened a defect to investigate [1].
It is possible to implement external authentication. My understanding is
that IBM Cloud Function for example implemented an integration with their
IAM (someone from IBM would be better
The OpenWhisk Node.js client has two fixes [1, 2] and some doc updates [3]
which I'd like to roll into a new release and update the npm client. There
are currently no new open pull requests. If there are no objections in the
next couple of days, I will move ahead with a release candidate next
Calling Ruby enthusiasts...
This PR https://github.com/apache/openwhisk-runtime-ruby/pull/57/files
applies Rubocop[1] (a Ruby static code analyzer) to our Ruby runtime.
Any Ruby coders on the list that can give the PR a look over to ensure
semantic preservation.
-r
[1]
cent Hou (Release manager of OpenWhisk) <
houshen...@apache.org>" not changed
gpg: key 22907064147F886E: "Dave Grove " not changed
gpg: key 44667BC927C86D51: "Rodric Rabbah " not changed
gpg: key B1457C3D7101CC78: "James Thomas " not
changed
gpg: key A600E333
Thanks Matt for pushing this head.
For Deno - I can look at cutting a release (a version 0.0.1 perhaps).
-r
On Mon, Mar 8, 2021 at 10:56 AM Matt Rutkowski
wrote:
> Hello Whiskers!
>
> If you have not seen, I have been trying to pay down technical debt in the
> Whisk Deploy tool and get it
[x] +1 Approve the release
Release verification checklist for reference:
[x ] Download links are valid.
[x ] Checksums and PGP signatures are valid.
[x ] Source code artifacts have correct names matching the current
release.
[x ] LICENSE and NOTICE files are correct for each OpenWhisk
+1 Approve the release
Release verification checklist for reference (rc verify log appended).
[x] Download links are valid.
[x] Checksums and PGP signatures are valid.
[x] Source code artifacts have correct names matching the current release.
[x] LICENSE and NOTICE files are correct for
Thanks Rob for leading the release!
On Sat, Feb 6, 2021 at 12:19 PM Rob Allen wrote:
> Hey all,
>
> We have recently added PHP 8 support to the PHP runtime and removed
> support for PHP 7.2 as that version is no longer supported by the PHP
> organisation. As such, I’d like to go ahead and make
ould "abort" mean anyways ?
>
> Just my 2 cents from the peanut gallery
>
> Regards
> Felix
>
>
> Von: Rodric Rabbah
> Gesendet: Dienstag, 26. Januar 2021 06:31
> An: dev@openwhisk.apache.org
> Betreff: Re: [Re
it's not in line with its purpose either [1] "cases where another process
> or server handles the request, or for batch processing".
>
> [1] - https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/202
>
> On Mon, Jan 25, 2021 at 7:00 AM Rodric Rabbah wrote:
>
> > Tha
Thanks Jiang for addressing this long standing bug.
I reviewed the PR. The 400 status code for developer errors also matches
the web action response. I think the only real debate is whether
application error should be 207 or 400. If a web action responds with an
error and no explicit status code,
There is a bug in the invoker health protocol - it was reported in
https://github.com/apache/openwhisk/issues/4988. I confirmed this is a bug
and it occurs on startup when the health-related ring buffer in the invoker
supervisor is not yet primed.
I opened a patch to fix the defect
> And in the case of vscode, it is implemented as typescript, so gradle is
not used. If it needs to use gradle for consistency with other repo please
let me know.
Not if it doesn't make sense. A simpler and more TS build environment is
preferable IMO.
-r
On Wed, Jan 20, 2021 at 1:39 AM 김건희
Thanks Dominic for investigating.
-r
> On Jan 12, 2021, at 7:44 AM, Dominic Kim wrote:
>
> Currently, we are facing CI test failures in the core repo.
> The reason on the surface is it's not resolving the couchdb.client library.
> However, with the unexpected behavior of Travis, it's not
hey Nick - I did submit for an exemption based on
https://www.docker.com/community/open-source/application I do not have an
updated status yet.
-r
On Mon, Dec 21, 2020 at 1:04 PM Nick Mitchell wrote:
> Have you applied to dockerhub to exempt the openwhisk org from their
> new-ish rate
I opened a PR to support init arguments in the .NET runtime.
https://github.com/apache/openwhisk-runtime-dotnet/pull/44
Thanks Shawn for the help!
-r
r thing @kamyker pointed out. Again, Newtonsoft.JSON was
> picked since it is the de facto standard for JSON in .NET.
> Thanks!!Shawn
> On Wednesday, December 16, 2020, 08:08:53 AM CST, Rodric Rabbah <
> rod...@gmail.com> wrote:
>
> Deprecating 2.2 makes sense to me being ou
Deprecating 2.2 makes sense to me being out of support.
I'm neutral on 5.0 vs waiting for .NET 6.0 (I am not a .NET developer
though :).
There were a couple of issues in the repo about improving the performance
of the .NET runtime by reducing dependencies and tweaking the JSON serdes.
Do you have
+1
checked with rc verify
> ./rcverify.sh openwhisk-runtime-nodejs 'OpenWhisk Runtime Node.js'
1.17.0 rc1
rcverify.sh (script SHA1: 9729 7EAF CC39 3EEF A6B3 4099 C159 DD29 88B2
DAEF)
working in the following directory:
/var/folders/q9/s3th42s53d34ftd5wvcypybrgn/T/tmp.qS8N4FNu
fetching
Thanks Dave!
On Fri, Dec 11, 2020 at 9:24 PM David P Grove wrote:
> Infra has migrated 26 of our repos to travis-ci.com. It appears to be
> more or less working as expected.
>
> We do need to go through and update the URL for the travis badge and
> re-encrypt the token for the travis2slack.
m.slack.com/archives/C3TPCAQG1/p1607008892384400
On Thu, Dec 3, 2020 at 2:24 PM Rodric Rabbah wrote:
> You may have read that the kubernetes 1.20 releate includes a notable
> deprecation notice for dockershim
> https://kubernetes.io/blog/2020/12/02/dockershim-faq which affects
> OpenWhisk depl
You may have read that the kubernetes 1.20 releate includes a notable
deprecation notice for dockershim
https://kubernetes.io/blog/2020/12/02/dockershim-faq which affects
OpenWhisk deployments on Kubernetes.
Several private deployments of OpenWhisk already don’t use docker, but the
Apache project
+1
-r
> On Nov 23, 2020, at 9:13 PM, Dominic Kim wrote:
>
> +1 to bundle the 22 components as Apache OpenWhisk 20.11.
>
> -dom
>
> 2020년 11월 24일 (화) 오전 10:59, David P Grove 님이 작성:
>
>>
>> This is a call to vote to approve the bundling of the 22 already released
>> Apache OpenWhisk
[x] +1 Approve the release
Release verification checklist for reference:
[x] Download links are valid.
[x] Checksums and PGP signatures are valid.
[x] Source code artifacts have correct names matching the current release.
[x] LICENSE and NOTICE files are correct for each OpenWhisk
+1 Approve the release
[x] Download links are valid.
[x] Checksums and PGP signatures are valid.
[x] Source code artifacts have correct names matching the current release.
[x] LICENSE and NOTICE files are correct for each OpenWhisk repository.
[x] All files have license headers as
+1 Approve the release
[x] Download links are valid.
[x] Checksums and PGP signatures are valid.
[x] Source code artifacts have correct names matching the current release.
[x] LICENSE and NOTICE files are correct for each OpenWhisk repository.
[x] All files have license headers as
I can confirm that standalone openwhisk is working as expected. I tried
several of the runtimes and confirmed the images are pulled correctly. The
API hosts shows all images are tagged.
-r
On Tue, Oct 20, 2020 at 5:25 PM Dave Grove wrote:
> We are probably closing in on something we could
Hello OpenWhisk community.
Over the weekend, I opened a PR to remove the python 3 runtimes which use
flask as their proxy, in favor of the unified go proxy (aka action loop).
The flask implementation is not being maintained and is prone to
re-initialization which we've worked to eliminate from
Thanks Dominic for sharing the details of PR 4954. I posted a question on
the PR but it may be of interest to others so reposting here.
Since your team is also working on versioning (PR 4986), I'm wondering
about the broader implications of this change. If the sequence or
composition references
+1 to release also to release
- 'OpenWhisk Runtime Java' 1.15.0 rc1
- 'OpenWhisk Runtime PHP' 1.15.0 rc1
- 'OpenWhisk Runtime Python' 1.15.0 rc1
- 'OpenWhisk Runtime Ruby' 1.15.0 rc1
- 'OpenWhisk Runtime Swift' 1.15.0 rc1
Checked successfully wit rcverify.sh (script SHA1: AB81 58B6 7F2B 74B5 F222
+1 I approve this release.
Confirmed with rcverify and manual inspection of the release.
> ./rcverify.sh openwhisk-runtime-rust 'OpenWhisk Runtime Rust' 1.1.0 rc1
rcverify.sh (script SHA1: AB81 58B6 7F2B 74B5 F222 AAD7 0F19 3228 98B0
906A)
working in the following directory:
The Project Management Committee (PMC) for Apache OpenWhisk has invited
Brendan Doyle to become a committer and we are pleased to announce that he
has accepted.
Please join me in welcoming Brendan to his new role on the project. Brendan
has been contributing to improving the OpenWhisk deployment
+1
-r
> On Sep 29, 2020, at 4:22 AM, Dominic Kim wrote:
>
> We have a bunch of new features such as a new scheduler, action versioning,
> and more fine-grained permission management, and so on.
>
> Before moving forward, I believe this is a good time to release the current
> version as
+1 I approve the release.
Checked with rcverify.
fetching tarball and signatures from
https://dist.apache.org/repos/dist/dev/openwhisk/rc1
fetching openwhisk-runtime-go-1.16.0-sources.tar.gz
fetching openwhisk-runtime-go-1.16.0-sources.tar.gz.asc
fetching
Recently we encountered an issue where setting require-whisk-auth == false
on a web action lead to the web action invocation being rejected (401). I
opened this issue to cover it
https://github.com/apache/openwhisk/issues/4985.
I think this is a bug/oversight in the implementation. Comments
+1
On Fri, Sep 25, 2020 at 9:43 AM David P Grove wrote:
>
> I think the upgrade to go 1.15 has been completed (please correct me if I
> am wrong).
>
> Therefore I would like to start the release process to prepare version
> 1.1.0 of the three git repos: openwhisk-client-go, openwhisk-wskdeploy,
I've approved the PR and will merge it once I get an all clear from Dominic.
Bringing up a conversation from Slack to the dev list for everyone's
benefit: while this PR restores backward compatibility, there was a point
raised about accumulating code for the sake of backward compatibility. The
Do you drain logs directly from memory to Elastic or do you use the
FileLogStore which then drains the logs to Elastic?
-r
On Mon, Aug 31, 2020 at 5:43 AM 蒋鹏程 wrote:
> Hello guys:
>
> Recently we are trying to migrate OpenWhisk from docker to K8S, but faced
> some problems, and one of it
I have created a new repo to host the runtime for Deno - this PR configures
our repo so notifications go to our project commit & issues mailinglists as
needed instead of the dev list.
-r
On Wed, Aug 19, 2020 at 10:51 AM GitBox wrote:
>
> rabbah merged pull request #1:
> URL:
1 - 100 of 610 matches
Mail list logo
