p;utm_medium=signature&utm_campaign=signaturevirality11&;>
22.
05. 19. 오후 07:34:40
2022년 5월 19일 (목) 오후 6:19, 蒋鹏程 님이 작성:
> hello whiskers:
>
> I feel that travis-ci always take lots of time to queue before build tasks,
> so I wonder whether we can use github actions instead, which is fa
hello whiskers:
I feel that travis-ci always take lots of time to queue before build tasks,
so I wonder whether we can use github actions instead, which is faster in my
experience.
I faintly remember that there was a discussion about travis and github actions?
but I can't remember the result.
Dear whiskers:
Currently we are using 502 BadGateway for ApplicationError and
DeveloperError, which is not very appropriate I think, so I submit a PR to
change this:
1. Use MultiStatus for ApplicationError
2. Use BadRequest for DeveloperError
Any comments and suggestions are welcomed
re
+1
-Original Message-
From: "Dominic Kim"
To: ;
Cc:
Sent: 2020/11/2周一 10:38 (GMT+08:00)
Subject: [VOTE] Release Apache OpenWhisk (v1.0.0, rc3)
Dear Whiskers.
Hope this would be the final vote.
This is a call to vote on releasing version 1.0.0 release candidate
rc3 of the following proj
Hello guys,
I created a PR to implement version management for action:
https://github.com/apache/openwhisk/pull/4986, and there is a discussion for it
before: https://github.com/apache/openwhisk/issues/4580.
Any reviews and suggestions are welcomed
refs:
1. https://github.com/apache/openwhi
o 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 is: the performance droped a
Hello guys:
Recently we are trying to migrate OpenWhisk from docker to K8S, but faced some
problems, and one of it is: the performance droped a lot(the tps changed from
thousands to dozens in our environment during benchmarks) after migrating to
K8S, and the reason we founded is that all acti
Welcome Cosmin!
Best Regards
Jiang PengCheng
-Original Message-
From: "Dragos Dascalita Haut"
To: "dev@openwhisk.apache.org";
Cc:
Sent: 2019/12/17周二 05:47 (GMT+08:00)
Subject: Welcome new committer: Cosmin Stanciu
It is my pleasure to share that the OpenWhisk PPMC
has elected Cosmin St
11 PM CST
-Original Message-
From: "Bill Zong"
To: "dev@openwhisk.apache.org";
Cc:
Sent: 2019/12/05周四 18:30 (GMT+08:00)
Subject: Re:[DISCUSS] Alternating time for the community call
11 PM CST
| |
Bill Zong
|
|
billz...@163.com
ShenZhen, China
|
签名由网易邮箱大师定制
On 12/5/2019 18:02,Dominic
Dear all:
I opened a PR:https://github.com/apache/openwhisk/pull/4724 that implement an
activation store based on ElasticSearch.
I think this should be useful for some users, please review and leave comments
Thanks
Jiang PengCheng
This will be heloful
-Original Message-
From: "Dominic Kim"
To: ;
Cc:
Sent: 2019-09-27 (星期五) 10:20:26 (GMT+08:00)
Subject: Re: PRs ready to merge
It's cool~!
2019년 9월 26일 (목) 오후 10:56, Chetan Mehrotra 님이 작성:
> The tooling to generate the summary report for changes across a set of
> gi
populated when an error
> happens while fetching action information.
> While this is an error case, I think it would be still worth to send
> `UserEvent` to notify the error happened.
> We may need a generic kind for error cases or multiple error kinds if we
> want to differentiate each
hello all:
I opened an issue for a tiny bug in invoker side:
https://github.com/apache/openwhisk/issues/4615
When get action from DB is failed or namespace is blacklisted while invoking
an activation, the `InvokerReactive` will generate a fallback result for it,
in these cases, it's not pos
Dear all:
While I was using DockerToActivationFileLogStore to store acitavation logs to
a separate file and use logstash to process this file, I found it's not
convenient to send logs to different indices in ElasticSearch using namespace
as a variable, such as send to "openwhisk-%{namespace}"
### Background
I think openwhisk needs some operation tools(page or API) to admin, for example:
* real-time status of Action, Controller, Invoker, etc.
* Change prewarm runtime container for invokers
here, we just discuss `Change prewarm container for invokers`
### Requirements
* Admin can ad
Hello all,
I just noticed that the db batcher doesn't behave as what I expected, seems it
has a fixed size of workers, and each worker will get data from stream eagerly,
so the batcher will try to insert 1 document/per requestat first, when all
workers are busy, subsequent documents will be
16 matches
Mail list logo