Re: [I] Scalable Deployment of OpenWhisk 2.0.0 [openwhisk]

2024-09-17 Thread via GitHub


bdoyle0182 commented on issue #5510:
URL: https://github.com/apache/openwhisk/issues/5510#issuecomment-2356474466

   
   > 3. But when I ran benchmarking for another action B after A, the warm 
containers were not used. Even though both A and B use same runtimes, same 
amount of memory and same requirements for pip.
   > 
   > So I think the warm containers not being used amongst different actions is 
what's causing my workflows to not scale. I saw invoker tags based scheduling 
in the docs and that is some temporary fix for my use case, that is in 2.0.0 
and not 1.0.0.
   > 
   > But bigger concern is my limited understanding of warm containers reuse 
amongst different actions. Where do I get more information about this? Is this 
the intentional way warm containers reuse is supposed to run?
   
   You're experiencing the hot spotting / container swapping problem of the 
best effort 1.0.0 scheduling algorithm. If you're container pool is full and no 
functions exist for Action B, you need to evict an Action A in order to cold 
start an Action B.
   But also want to clarify that you shouldn't expect containers to get reused 
for multiple actions. Once a container is bound to an action, it can only run 
executions of that action even if it's using the same runtime and memory 
profile; there are many reasons for this but most importantly is security and 
data isolation.
   
   You will find that performance should be significantly better on Openwhisk 
2.0 with the new scheduler for the traffic pattern you're trying to test.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] Scalable Deployment of OpenWhisk 2.0.0 [openwhisk]

2024-09-17 Thread via GitHub


singhsegv commented on issue #5510:
URL: https://github.com/apache/openwhisk/issues/5510#issuecomment-2356404420

   Hey @style95 thank for taking this up
   
   **How did you deploy OpenWhisk-2.0.0? Are you able to invoke an action?**
   I haven't deployed this till now. I've been working with OpenWhisk 1.0.0 
which is the one that comes with  
https://github.com/apache/openwhisk-deploy-kube repository. I've raised an 
issue there to understand how to get OpenWhisk 2.0.0 up and running with k8s 
where you gave some pointers 
https://github.com/apache/openwhisk-deploy-kube/issues/781#issuecomment-2316569110
 . I'll be working on getting this up in the meantime. 
   
   So this question is something that is part of my doubts. As in, if I want to 
deploy OpenWhisk 2.0.0 in a multi node setting in a scalable manner, how should 
I go about it? Is ansible a way for that, or is there some way to user 
kubernetes for this?
   
   ---
   **What is your concurrency limit and userMemory assigned to invokers?**
   My action concurrency limits are 1 and there are 3 invokers each with 
~2m of memory. After checking in grafana dashboard this seems to be fine 
since each invoker showed 40 pods of 512mb memory each at peak.
   
   ---
   Some more updates from the benchmarking I did in the meantime:
   
   1. Instead of benchmarking the scale of workflows, I went back to load 
testing 1 action at a time. I had a graph processing workflow in which let's 
say there were 2 actions A and B.
   2. Benchmarking A with multiple RPS made it scale well. I tried with 
1/4/8/16 RPS for 5 minutes each and it reused warm containers and got stable 
soon.
   3.  But when I ran benchmarking for another action B after A, the warm 
containers were not used. Even though both A and B use same runtimes, same 
amount of memory and same requirements for pip.
   
   So I think the warm containers not being used amongst different actions is 
what's causing my workflows to not scale. I saw invoker tags based scheduling 
in the docs and that is some temporary fix for my use case, that is in 2.0.0 
and not 1.0.0.
   
   But bigger concern is my limited understanding of warm containers reuse 
amongst different actions. Where do I get more information about this? Is this 
the intentional way warm containers reuse is supposed to run?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] M1 mac compatibility [openwhisk]

2024-09-17 Thread via GitHub


dgrove-oss commented on PR #5511:
URL: https://github.com/apache/openwhisk/pull/5511#issuecomment-2356265132

   > One concern is we don't have any CI pipelines for the m1 Mac. It seems the 
M1 runner is available for all plans. It would be great if we set up one 
pipeline.
   > 
   > 
[actions/runner-images#9254](https://github.com/actions/runner-images/issues/9254)
   
   My suggestion would be that we go after enabling one of the CI pipelines for 
both x86_64 and arm in a separate PR.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] M1 mac compatibility [openwhisk]

2024-09-17 Thread via GitHub


style95 commented on PR #5511:
URL: https://github.com/apache/openwhisk/pull/5511#issuecomment-2354904956

   One concern is we don't have any CI pipelines for the m1 Mac.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] M1 mac compatibility [openwhisk]

2024-09-17 Thread via GitHub


style95 commented on code in PR #5511:
URL: https://github.com/apache/openwhisk/pull/5511#discussion_r1762535924


##
ansible/group_vars/all:
##
@@ -464,7 +466,7 @@ zeroDowntimeDeployment:
   enabled: "{{ zerodowntime_deployment_switch | default(false) }}"
 
 etcd:
-  version: "{{ etcd_version | default('v3.4.33') }}"
+  version: "{{ etcd_version | default('3.5') }}"

Review Comment:
   etcd supports multiarch since 3.5 version.
   https://hub.docker.com/r/bitnami/etcd/
   
   https://github.com/user-attachments/assets/edd6cced-e73c-405e-8799-cf757c4748e6";>
   
   



##
ansible/roles/zookeeper/tasks/deploy.yml:
##
@@ -17,10 +17,20 @@
 ---
 # This role will install Kafka with Zookeeper in group 'kafka' in the 
environment inventory
 
+- name: set zookeeper image
+  set_fact:
+zookeeper_image: "{{ zookeeper.image.arm64 }}"
+  when: ansible_facts['os_family'] == "Darwin" and 
ansible_facts['architecture'] == "arm64"

Review Comment:
   Selectively use the arm64 zookeeper image according to the os and 
architecture.
   



##
ansible/roles/invoker/tasks/deploy.yml:
##
@@ -80,7 +80,7 @@
   when: environmentInformation.type == "docker-machine"
 
 - name: "determine docker root dir"
-  shell: echo -e "GET http:/v1.24/info HTTP/1.0\r\n" | nc -U 
/var/run/docker.sock | grep "{"

Review Comment:
   It doesn't work with the recent version of docker for mac.
   



##
ansible/group_vars/all:
##
@@ -186,7 +186,9 @@ kafka_connect_string: "{% set ret = [] %}\
 kafka_protocol_for_setup: "{{ kafka_protocol | default('PLAINTEXT') }}"
 
 zookeeper:
-  version: 3.4
+  image:
+amd64: zookeeper:3.4
+arm64: arm64v8/zookeeper:3.4

Review Comment:
   I added another zookeeper image for arm64



##
common/scala/build.gradle:
##
@@ -24,6 +24,9 @@ plugins {
 }
 
 ext.dockerImageName = 'scala'
+if(System.getProperty("os.arch").toLowerCase(Locale.ENGLISH).startsWith("aarch"))
 {

Review Comment:
   If the architecture of OS is m1 Mac, it uses the Dockerfile with the `.arm` 
suffix.
   



##
common/scala/Dockerfile.arm:
##
@@ -0,0 +1,34 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements.  See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License.  You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+# if you change version of openjsk, also update tools/github/setup.sh to 
download the corresponding jdk
+FROM arm64v8/eclipse-temurin:21.0.4_7-jdk-alpine

Review Comment:
   Only the base image is changed.
   



##
tools/ow-utils/Dockerfile.arm:
##
@@ -0,0 +1,80 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements.  See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License.  You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+
+FROM arm64v8/eclipse-temurin:8u422-b05-jdk-noble

Review Comment:
   I only changed the base image from `adoptopenjdk/openjdk8:jdk8u262-b10` to 
`arm64v8/eclipse-temurin:8u422-b05-jdk-noble`.
   
   I used it as the current image is deprecated.
   
   https://github.com/user-attachments/assets/2f629baa-7438-4f43-ae55-f984b7027483";>
   
   https://hub.docker.com/_/adoptopenjdk
   



##
core/scheduler/build.gradle:
##
@@ -52,6 +52,16 @@ buildscript {
 }
 }
 
+protobuf {
+protoc {
+if (osdetector.os == "osx") {
+artifact = 'com.google.protobuf:protoc:3.4.0:osx-x86_64'

Review Comment:
   IIRC, we cant' upgrade the protoc version for now because some libraries are 
dependent on this version.
   And protoc-3.4.0 does not support arm architecture yet, so I chose this way.
   This also requires rosetta installed.
   
   https://github.com/grpc/grpc-java/issues/7690#issuecomment-760332746



-- 
This

[PR] M1 mac compatibility [openwhisk]

2024-09-17 Thread via GitHub


style95 opened a new pull request, #5511:
URL: https://github.com/apache/openwhisk/pull/5511

   This is a very first step to make OW compatible with M1 Mac.
   
   ## Description
   
   There could be many ways but I chose to minimize changes. I decided to have 
another Dockerfile for the M1 Mac. It will be selectively used according to the 
OS and its architecture.
   
   I could build and deploy OW on M1 Mac and run an action.
   (Though I had to install rosetta because openwhisk-cli is also not being 
built for M1 mac.)
   
   ```bash
   $ wsk action invoke noop -i -r
   {}
   ```
   
   ## Related issue and scope
   
   - [x] I opened an issue to propose and discuss this change 
(https://github.com/apache/openwhisk/issues/5503)
   
   ## My changes affect the following components
   
   
   - [ ] API
   - [ ] Controller
   - [ ] Message Bus (e.g., Kafka)
   - [ ] Loadbalancer
   - [ ] Scheduler
   - [ ] Invoker
   - [ ] Intrinsic actions (e.g., sequences, conductors)
   - [ ] Data stores (e.g., CouchDB)
   - [ ] Tests
   - [x] Deployment
   - [ ] CLI
   - [x] General tooling
   - [ ] Documentation
   
   ## Types of changes
   
   - [ ] Bug fix (generally a non-breaking change which closes an issue).
   - [x] Enhancement or new feature (adds new functionality).
   - [ ] Breaking change (a bug fix or enhancement which changes existing 
behavior).
   
   ## Checklist:
   
   
   - [x] I signed an [Apache 
CLA](https://github.com/apache/openwhisk/blob/master/CONTRIBUTING.md).
   - [x] I reviewed the [style 
guides](https://github.com/apache/openwhisk/blob/master/CONTRIBUTING.md#coding-standards)
 and followed the recommendations (Travis CI will check :).
   - [ ] I added tests to cover my changes.
   - [ ] My changes require further changes to the documentation.
   - [ ] I updated the documentation where necessary.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] prepare for 1.20.0 release [openwhisk-runtime-java]

2024-09-16 Thread via GitHub


dgrove-oss merged PR #168:
URL: https://github.com/apache/openwhisk-runtime-java/pull/168


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] prepare for 1.20.0 release [openwhisk-runtime-python]

2024-09-16 Thread via GitHub


dgrove-oss merged PR #165:
URL: https://github.com/apache/openwhisk-runtime-python/pull/165


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] prepare for 1.21.0 release [openwhisk-runtime-php]

2024-09-16 Thread via GitHub


dgrove-oss merged PR #145:
URL: https://github.com/apache/openwhisk-runtime-php/pull/145


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] prepare for 1.19.0 release [openwhisk-runtime-swift]

2024-09-16 Thread via GitHub


dgrove-oss merged PR #167:
URL: https://github.com/apache/openwhisk-runtime-swift/pull/167


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] release openwhisk-runtime-dotnet 1.18.0 [openwhisk-website]

2024-09-16 Thread via GitHub


rabbah merged PR #522:
URL: https://github.com/apache/openwhisk-website/pull/522


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] release config for runtime-dotnet-1.18.0 [openwhisk-release]

2024-09-16 Thread via GitHub


rabbah merged PR #433:
URL: https://github.com/apache/openwhisk-release/pull/433


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] Scalable Deployment of OpenWhisk 2.0.0 [openwhisk]

2024-09-15 Thread via GitHub


style95 commented on issue #5510:
URL: https://github.com/apache/openwhisk/issues/5510#issuecomment-2352006434

   @singhsegv 
   
   I just want to ask you a couple of questions first.
   How did you deploy OpenWhisk-2.0.0? Are you able to invoke an action? 
   What is your concurrency limit and userMemory assigned to invokers?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] Bump gradle-scalafmt version [openwhisk]

2024-09-13 Thread via GitHub


Suraez commented on issue #5504:
URL: https://github.com/apache/openwhisk/issues/5504#issuecomment-2350718617

   i got another issue now, when i made the changes stated in the above pull 
request
   
   ```
   * What went wrong:
   A problem occurred configuring project ':core:standalone'.
   > Could not resolve all artifacts for configuration 
':core:standalone:classpath'.
  > Could not find org.ajoberstar.grgit:grgit-core:3.0.0.
Searched in the following locations:
  - 
https://plugins.gradle.org/m2/org/ajoberstar/grgit/grgit-core/3.0.0/grgit-core-3.0.0.pom
Required by:
project :core:standalone > 
com.gorylenko.gradle-git-properties:com.gorylenko.gradle-git-properties.gradle.plugin:2.0.0
 > gradle.plugin.com.gorylenko.gradle-git-properties:gradle-git-properties:2.0.0
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] release openwhisk-runtime-dotnet 1.18.0 [openwhisk-website]

2024-09-13 Thread via GitHub


dgrove-oss opened a new pull request, #522:
URL: https://github.com/apache/openwhisk-website/pull/522

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] release config for runtime-dotnet-1.18.0 [openwhisk-release]

2024-09-13 Thread via GitHub


dgrove-oss opened a new pull request, #433:
URL: https://github.com/apache/openwhisk-release/pull/433

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[I] Scalable Deployment of OpenWhisk 2.0.0 [openwhisk]

2024-09-13 Thread via GitHub


singhsegv opened a new issue, #5510:
URL: https://github.com/apache/openwhisk/issues/5510

   I am very confused about how the OpenWhisk 2.0.0 is meant to be deployed for 
a scalable bechmarking setting. Need some help from the maintainers to 
understand what am I missing since I've spent a large amount of time now and 
still missing some key pieces.
   
   ### Context
   We are using OpenWhisk for a research project where workflows (sequential as 
well as fork/join) are to be deployed and benchmarked at 1/4/8 RPS etc for long 
period of times. This is to compare private cloud FaaS vs public cloud FaaS.
   
   ### Current Infrastructure Setting
   We have a in-house cluster with around 10 VMs running on different nodes, 50 
vCPUs and around 200Gb of memory. Since I am new to this, I've initially 
followed https://github.com/apache/openwhisk-deploy-kube to deploy it and along 
with OpenWhisk Composer, was able to get the workflows running with a lot of 
small fixes and changes.
   
   ### Problems with Current Infrastructure
   1. I am not able to scale it properly. Running even 1 RPS for 5-10 minutes 
leads to a lot of random errors like "failed to get binary" and some other 
errors too that don't occur when running a workflow once manually.
   2. Even when I reduce the benchmarking time to 10-20s, the inter-action comm 
time is coming out to be around 1.5-2 minutes. Grafana shows around 2 minutes 
going in the `/init` and I am unable to debug why that is happening.
   
   ### Main Doubts about scaling
   1. Since that openwhisk-deploy-kube take a very old version of OpenWhisk, so 
I thought running the latest version of it without k8s and on a single machine 
might give some benefits. But what I've understood now is the standalone mode 
is not supposed to be scalable since the controller is responsible for a lot of 
things in v1.0.0 and haven't checked that in 2.0.0.
   2. Since, deploy-kube doesn't support the latest version of OpenWhisk due to 
major changes in scheduler, how is OpenWhisk supposed to be deployed for a 
scalable infrastructure? Is there some documentation that I've missed?
   3. Also in 1.0.0, the results that I've got, is there something that I am 
missing? Why aren't the workflows scaling? How to go about debugging the delay? 
Or is purely that more infra needs to be added? 
   
   @style95 @dgrove-oss Since you people have been active in the community and 
have answered some of my previous queries too, any help on this will be very 
appreciated. 
   
   We are planning to go all in with OpenWhisk for our research and planning to 
contribute some good changes back to the community relating to FaaS at edge and 
improving the communication times in FaaS. But since none of us have 
infrastructure as our strong suite, getting over these initial hiccups is a 
becoming a blocker for us. So looking forward to some help, thanks :).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] update gradle to 6.9.3 [openwhisk-runtime-php]

2024-09-12 Thread via GitHub


rabbah merged PR #144:
URL: https://github.com/apache/openwhisk-runtime-php/pull/144


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] upgrade gradle to 6.9.3 [openwhisk-runtime-java]

2024-09-12 Thread via GitHub


rabbah merged PR #167:
URL: https://github.com/apache/openwhisk-runtime-java/pull/167


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] upgrade gradle to 6.9.3 [openwhisk-runtime-python]

2024-09-12 Thread via GitHub


rabbah merged PR #164:
URL: https://github.com/apache/openwhisk-runtime-python/pull/164


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] upgrade to gradle 6.9.3 [openwhisk-runtime-swift]

2024-09-12 Thread via GitHub


rabbah merged PR #166:
URL: https://github.com/apache/openwhisk-runtime-swift/pull/166


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] openwhisk-cli Build failed [openwhisk-cli]

2024-09-11 Thread via GitHub


heywoodlh commented on issue #522:
URL: https://github.com/apache/openwhisk-cli/issues/522#issuecomment-2344817807

   > wski18n/i18n.go:98:16: undefined: Asset
   
   I ran into this as well, fixed with the following command:
   
   ```
   go-bindata -pkg wski18n -o wski18n/i18n_resources.go wski18n/resources
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] added to nixpkgs [openwhisk-cli]

2024-09-11 Thread via GitHub


heywoodlh closed issue #524: added to nixpkgs
URL: https://github.com/apache/openwhisk-cli/issues/524


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] upgrade to gradle 6.9.3 [openwhisk-runtime-swift]

2024-09-10 Thread via GitHub


dgrove-oss opened a new pull request, #166:
URL: https://github.com/apache/openwhisk-runtime-swift/pull/166

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] all is ok, but install-packages is init..... [openwhisk-deploy-kube]

2024-09-08 Thread via GitHub


Suraez commented on issue #732:
URL: 
https://github.com/apache/openwhisk-deploy-kube/issues/732#issuecomment-2336913710

   when try to hit the command `wsk action list` or `wsk -i action list`, i got 
these errors:
   
   
![image](https://github.com/user-attachments/assets/800cd507-7807-4189-bf02-29a25920cdde)
   
   please help me find the issue, i have been stuck at this issue for more than 
a week , i tried all ubuntu versions (20.04, 22.04, 24.04) with all python 
versions (3.8, 3.9, 3.10)
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] all is ok, but install-packages is init..... [openwhisk-deploy-kube]

2024-09-08 Thread via GitHub


Suraez commented on issue #732:
URL: 
https://github.com/apache/openwhisk-deploy-kube/issues/732#issuecomment-2336911159

   all pods seem to be fine except the ones that are highlighted below as they 
are having 0/1 ready state
   
   i checked their logs but none of them makes sense to me, if you could 
provide any guidance, that would be great
   
   
![image](https://github.com/user-attachments/assets/3fc1f792-0736-4fec-bf05-0c48935c5a0a)
   
   `owdev-gen-certs-scmqt ` logs:
   ```
   
   Error from server (NotFound): secrets "owdev-nginx" not found
   generating new owdev-nginx secret
   generating server certificate request
   Can't load /root/.rnd into RNG
   139671000441280:error:2406F079:random number generator:RAND_load_file:Cannot 
open file:../crypto/rand/randfile.c:88:Filename=/root/.rnd
   generating self-signed password-less server certificate
   Signature ok
   subject=C = US, ST = NY, L = Yorktown, O = OpenWhisk, CN = *.localhost
   Getting Private key
   generate keystore
   secret/owdev-nginx created
   ```
   `owdev-init-couchdb-r8zdg ` logs:
   ```
   
   Cloning into '/openwhisk'...
   /openwhisk /
   Note: checking out 'ef725a653ab112391f79c274d8e3dcfb915d59a3'.
   
   You are in 'detached HEAD' state. You can look around, make experimental
   changes and commit them, and you can discard any commits you make in this
   state without impacting any branches by performing another checkout.
   
   If you want to create a new branch to retain commits you create, you may
   do so (now or later) by using -b with the checkout command again. Example:
   
 git checkout -b 
   
   HEAD is now at ef725a65 Prevent cycle in the QueueManager (#5332)
   /
   /openwhisk/ansible /
[WARNING]: Unable to parse /openwhisk/ansible/environments/local as an
   inventory source
[WARNING]: No inventory was parsed, only implicit localhost is available
[WARNING]: provided hosts list is empty, only localhost is available. Note
   that the implicit localhost does not match 'all'
   
   PLAY [localhost] 
***
[WARNING]: While constructing a mapping from
   /openwhisk/ansible/group_vars/all, line 494, column 3, found a duplicate dict
   key (dataManagementService). Using last defined value only.
   
   TASK [Gathering Facts] 
*
   Monday 09 September 2024  00:10:18 + (0:00:00.067)   0:00:00.067 
** 
   ok: [localhost]
   
   TASK [gen hosts if 'local' env is used] 

   Monday 09 September 2024  00:10:18 + (0:00:00.796)   0:00:00.864 
** 
   changed: [localhost -> localhost]
   
   TASK [find the ip of docker-machine] 
***
   Monday 09 September 2024  00:10:19 + (0:00:00.501)   0:00:01.365 
** 
   skipping: [localhost]
   
   TASK [get the docker-machine ip] 
***
   Monday 09 September 2024  00:10:19 + (0:00:00.028)   0:00:01.394 
** 
   skipping: [localhost]
   
   TASK [gen hosts for docker-machine] 

   Monday 09 September 2024  00:10:19 + (0:00:00.042)   0:00:01.436 
** 
   skipping: [localhost]
   
   TASK [gen hosts for Jenkins] 
***
   Monday 09 September 2024  00:10:19 + (0:00:00.053)   0:00:01.490 
** 
   skipping: [localhost]
   
   TASK [check if db_local.ini exists?] 
***
   Monday 09 September 2024  00:10:19 + (0:00:00.073)   0:00:01.563 
** 
   ok: [localhost]
   
   TASK [prepare db_local.ini] 

   Monday 09 September 2024  00:10:19 + (0:00:00.174)   0:00:01.738 
** 
   changed: [localhost -> localhost]
   
   TASK [gen untrusted server certificate for host] 
***
   Monday 09 September 2024  00:10:20 + (0:00:00.290)   0:00:02.028 
** 
   changed: [localhost -> localhost]
   
   TASK [gen untrusted client certificate for host] 
***
   Monday 09 September 2024  00:10:20 + (0:00:00.409)   0:00:02.437 
** 
   changed: [localhost -> localhost]
   
   TASK [clean up old kafka keystore] 
*
   Monday 09 September 2024  00:10:21 + (0:00:00.669)   0:00:03.107 
** 
   skipping: [localhost]
   
   TASK [ensure kafka files directory exists] 
*
   Monday 09 September 2024  00:10:21 + (0:00:00.030)   0:00:03.137 
** 
   skipping: [localhost]
   
   TASK [generate kafka certificates] 
*
   Monday 09 September 2024  00:10:21 + (0:00:00.036)   0:00:03.174 
** 
   skipping: [localhost]
   
   TASK [ensure controller files directory exists] 
*

Re: [I] Bump gradle-scalafmt version [openwhisk]

2024-09-08 Thread via GitHub


Suraez commented on issue #5504:
URL: https://github.com/apache/openwhisk/issues/5504#issuecomment-2336847981

   i am having the same issue


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] prepare for 1.18.0 release [openwhisk-runtime-dotnet]

2024-09-07 Thread via GitHub


rabbah merged PR #84:
URL: https://github.com/apache/openwhisk-runtime-dotnet/pull/84


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] all is ok, but install-packages is init..... [openwhisk-deploy-kube]

2024-09-07 Thread via GitHub


rabbah commented on issue #732:
URL: 
https://github.com/apache/openwhisk-deploy-kube/issues/732#issuecomment-2335459745

   check which pods did not come up and why.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] September 2024 runtime wave release configs [openwhisk-release]

2024-09-07 Thread via GitHub


rabbah merged PR #432:
URL: https://github.com/apache/openwhisk-release/pull/432


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] update downloads for runtime-go, runtime-docker, runtime-nodejs releases [openwhisk-website]

2024-09-07 Thread via GitHub


rabbah merged PR #521:
URL: https://github.com/apache/openwhisk-website/pull/521


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] Fix packages-public view function [openwhisk]

2024-09-07 Thread via GitHub


rabbah commented on PR #5508:
URL: https://github.com/apache/openwhisk/pull/5508#issuecomment-2335437684

   Thanks @dorbae for the fix


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] update go proxy to 1.23@1.25.0 [openwhisk-runtime-swift]

2024-09-06 Thread via GitHub


Luke-Roy-IBM merged PR #165:
URL: https://github.com/apache/openwhisk-runtime-swift/pull/165


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] update go proxy to 1.23@1.25.0 [openwhisk-runtime-rust]

2024-09-06 Thread via GitHub


Luke-Roy-IBM merged PR #50:
URL: https://github.com/apache/openwhisk-runtime-rust/pull/50


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] update go proxy to 1.23@1.25.0 [openwhisk-runtime-php]

2024-09-06 Thread via GitHub


Luke-Roy-IBM merged PR #143:
URL: https://github.com/apache/openwhisk-runtime-php/pull/143


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] update go proxy to 1.23@1.25.0 [openwhisk-runtime-rust]

2024-09-05 Thread via GitHub


dgrove-oss opened a new pull request, #50:
URL: https://github.com/apache/openwhisk-runtime-rust/pull/50

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] config for runtime-go 1.25 [openwhisk-release]

2024-09-05 Thread via GitHub


dgrove-oss opened a new pull request, #432:
URL: https://github.com/apache/openwhisk-release/pull/432

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] all is ok, but install-packages is init..... [openwhisk-deploy-kube]

2024-09-02 Thread via GitHub


Suraez commented on issue #732:
URL: 
https://github.com/apache/openwhisk-deploy-kube/issues/732#issuecomment-2325295851

   Hi, I am having the same issue, did you find any solution?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] prepare for 1.16.0 release [openwhisk-runtime-docker]

2024-09-01 Thread via GitHub


Luke-Roy-IBM merged PR #105:
URL: https://github.com/apache/openwhisk-runtime-docker/pull/105


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] prep for 1.23.0 release [openwhisk-runtime-nodejs]

2024-08-31 Thread via GitHub


Luke-Roy-IBM merged PR #254:
URL: https://github.com/apache/openwhisk-runtime-nodejs/pull/254


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] Remove dependency on 3rd party JSON library from next version of runtime [openwhisk-runtime-dotnet]

2024-08-30 Thread via GitHub


dgrove-oss commented on issue #51:
URL: 
https://github.com/apache/openwhisk-runtime-dotnet/issues/51#issuecomment-2322148175

   Closing as this issue was about dotnet 3.1 which is EOL.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] Remove dependency on 3rd party JSON library from next version of runtime [openwhisk-runtime-dotnet]

2024-08-30 Thread via GitHub


dgrove-oss closed issue #51: Remove dependency on 3rd party JSON library from 
next version of runtime
URL: https://github.com/apache/openwhisk-runtime-dotnet/issues/51


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] improve cold start times [openwhisk-runtime-dotnet]

2024-08-30 Thread via GitHub


dgrove-oss closed issue #34: improve cold start times
URL: https://github.com/apache/openwhisk-runtime-dotnet/issues/34


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] improve cold start times [openwhisk-runtime-dotnet]

2024-08-30 Thread via GitHub


dgrove-oss commented on issue #34:
URL: 
https://github.com/apache/openwhisk-runtime-dotnet/issues/34#issuecomment-2322147324

   Closing as this issue was about dotnet 3.1 which is EOL.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] Action cannot load Microsoft.Extensions.DependencyInjection.Abstraction [openwhisk-runtime-dotnet]

2024-08-30 Thread via GitHub


dgrove-oss closed issue #39: Action cannot load 
Microsoft.Extensions.DependencyInjection.Abstraction
URL: https://github.com/apache/openwhisk-runtime-dotnet/issues/39


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] Action cannot load Microsoft.Extensions.DependencyInjection.Abstraction [openwhisk-runtime-dotnet]

2024-08-30 Thread via GitHub


dgrove-oss commented on issue #39:
URL: 
https://github.com/apache/openwhisk-runtime-dotnet/issues/39#issuecomment-2322146239

   Closing as this issue was about dotnet 3.1 which is EOL.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] Drop support for dotnet3.1 (EOL) [openwhisk-runtime-dotnet]

2024-08-30 Thread via GitHub


dgrove-oss merged PR #83:
URL: https://github.com/apache/openwhisk-runtime-dotnet/pull/83


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] Drop support for dotnet3.1 (EOL) [openwhisk-runtime-dotnet]

2024-08-30 Thread via GitHub


dgrove-oss commented on PR #83:
URL: 
https://github.com/apache/openwhisk-runtime-dotnet/pull/83#issuecomment-2321542039

   LTS for 3.1 ended at the end of 2022, so its time to drop from the action.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] Drop support for dotnet3.1 (EOL) [openwhisk-runtime-dotnet]

2024-08-30 Thread via GitHub


dgrove-oss opened a new pull request, #83:
URL: https://github.com/apache/openwhisk-runtime-dotnet/pull/83

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] prep for 1.23.0 release [openwhisk-runtime-nodejs]

2024-08-30 Thread via GitHub


dgrove-oss opened a new pull request, #254:
URL: https://github.com/apache/openwhisk-runtime-nodejs/pull/254

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] Add release notes for 1.25.0 [openwhisk-runtime-go]

2024-08-28 Thread via GitHub


Luke-Roy-IBM merged PR #204:
URL: https://github.com/apache/openwhisk-runtime-go/pull/204


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] Make a 2.0.0 release of Helm Chart (to match OpenWhisk 2.0.0 release) [openwhisk-deploy-kube]

2024-08-28 Thread via GitHub


style95 commented on issue #781:
URL: 
https://github.com/apache/openwhisk-deploy-kube/issues/781#issuecomment-2316569110

   @singhsegv 
   I believe this is because the scheduler is now enabled by default in the 
core project.
   
https://github.com/apache/openwhisk/blob/master/common/scala/src/main/resources/reference.conf#L21C1-L32C2
   
   And I see it is not aligned with openwhisk-deploy-kube where the scheduler 
is disabled by default.
   
https://github.com/apache/openwhisk-deploy-kube/blob/master/helm/openwhisk/values.yaml#L275
   
   Since you just updated the images, the ShardingPoolBalancer would be enabled 
and no etcd configuration would exist in the helm chart while as you can see in 
the log, the `FPCPoolBalancer` is enabled in the image.
   
   I think you have two options.
   
   1. Enable the scheduler and add ETCD-related configurations.
   I think you need to update the helm chart too and enable [this 
configuration](https://github.com/apache/openwhisk-deploy-kube/blob/master/helm/openwhisk/values.yaml#L275).
   
   2. Disable the scheduler and change the underlying implementations to the 
ShardingPoolBalancer family.
   This is trickier as you need to update the helm chart for this way manually.
   
   The main thing is to change all the relevant SPI implementation.
   
   ```
 LoadBalancerProvider = 
org.apache.openwhisk.core.loadBalancer.FPCPoolBalancer
 EntitlementSpiProvider = 
org.apache.openwhisk.core.entitlement.FPCEntitlementProvider
 InvokerProvider = org.apache.openwhisk.core.invoker.FPCInvokerReactive
 InvokerServerProvider = org.apache.openwhisk.core.invoker.FPCInvokerServer
   ```
   
https://github.com/apache/openwhisk/blob/master/common/scala/src/main/resources/reference.conf#L26C3-L30
   
   I think they should be changed like below.
   ```
 LoadBalancerProvider = 
org.apache.openwhisk.core.loadBalancer.ShardingContainerPoolBalancer
 EntitlementSpiProvider = 
org.apache.openwhisk.core.entitlement.LocalEntitlementProvider
 InvokerProvider = org.apache.openwhisk.core.invoker.InvokerReactive
 InvokerServerProvider = 
org.apache.openwhisk.core.invoker.DefaultInvokerServer
   ```
   
   Since you cannot change the reference.conf file as it resides in the image.
   You need to configure them via helm chart.
   
   I see currently the helm chart is defined with the assumption that 
ShardingPoolBalancer is enabled by default but it is actually not.
   
https://github.com/apache/openwhisk-deploy-kube/blob/master/helm/openwhisk/templates/invoker-pod.yaml#L149
   
   So you need to configure implementation in a way like the below.
   This is supposed to be updated in the openwhisk-deploy-kube but I couldn't 
work on it yet.
   
   ```
 - name: "CONFIG_whisk_spi_InvokerProvider"
   value: "org.apache.openwhisk.core.invoker.InvokerReactive"
   ```
   
   Since I haven't tried this yet as well, not one hundred percent sure but it 
should be ideally addressed in this way.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] Add release notes for 1.25.0 [openwhisk-runtime-go]

2024-08-28 Thread via GitHub


dgrove-oss opened a new pull request, #204:
URL: https://github.com/apache/openwhisk-runtime-go/pull/204

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] Make a 2.0.0 release of Helm Chart (to match OpenWhisk 2.0.0 release) [openwhisk-deploy-kube]

2024-08-28 Thread via GitHub


dgrove-oss commented on issue #781:
URL: 
https://github.com/apache/openwhisk-deploy-kube/issues/781#issuecomment-2316535345

   @style95 -- maybe you have some suggestions?  Core openwhisk's inability to 
build on arm64 has really limited my ability to do anything with the core 
project or open whisk-deploy-kube for the last couple of years.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] update openwhisk-client-js version in test files [openwhisk-runtime-nodejs]

2024-08-28 Thread via GitHub


dgrove-oss commented on PR #253:
URL: 
https://github.com/apache/openwhisk-runtime-nodejs/pull/253#issuecomment-2316528122

   Remembered (again...) that this test case intentionally uses an old 
openwhisk version as a simple way to verify that user-provided packages will 
override those built into the action docker file.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] update openwhisk-client-js version in test files [openwhisk-runtime-nodejs]

2024-08-28 Thread via GitHub


dgrove-oss closed pull request #253: update openwhisk-client-js version in test 
files
URL: https://github.com/apache/openwhisk-runtime-nodejs/pull/253


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[I] Defaulted container "install-packages" out of: install-packages, wait-for-healthy-invoker (init) [openwhisk-deploy-kube]

2024-08-28 Thread via GitHub


Suraez opened a new issue, #787:
URL: https://github.com/apache/openwhisk-deploy-kube/issues/787

   Hi, all of the pods related to the openwhisk deployment seems to be working 
except the followings as their READY status is 0/1:
   ```
   1. owdev-gen-certs-mcjbh 
   2. owdev-init-couchdb-jj2zm 
   3. owdev-install-packages-4mhfv  
   ```
   
   
![image](https://github.com/user-attachments/assets/1176ccc1-02b0-4213-b22c-9c85fdb3d4d2)

   _the pod `owdev-tests-package-checker`  is generated after I ran `helm test 
owdev -n openwhisk` so that's not the problem._ 
   
   the logs of the above listed containers are:
   
   owdev-gen-certs-mcjbh 
   
   
![image](https://github.com/user-attachments/assets/0d038498-a63d-483b-bf9d-03e02cd177bc)
   
   owdev-init-couchdb-jj2zm 
   
   
![image](https://github.com/user-attachments/assets/8293a957-7007-494d-824f-7b8231a5c536)
   
   owdev-install-packages-4mhfv  
   
   
![image](https://github.com/user-attachments/assets/e2350d1f-5bfb-4e0f-9bc8-63dfc7b1f4ad)
   
   Now, from the above pods, the pod related to generating SSL certificate i.e. 
`owdev-gen-certs-mcjbh` is having error while generating random number 
generator, but then again it says "Signature Ok" and "secret/owdev-nginx 
created" so i think this pod is fine. In case of pod related to installing 
packages i.e. owdev-install-packages-4mhfv , i don't know what's going on in 
there whereas couchDB pod i.e. owdev-init-couchdb-jj2zm has been initialized 
successfully. However, all of these pods have 0/1 in READY column. I do not 
really understand, why? if somebody could help me get these pods in ready state 
with 1/1 in READY column so that I can deploy and invoke functions, that would 
be very helpful. Thank you.
   
   Dependencies:
   
   Go version: 1.23.0
   Docker version: 26.1.4
   kubectl version: 1.30.1
   helm version: 3.15.4
   
   PS: I tried restarting these pods by deleting them. But no luck :(
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] KafkaProducerConnector producer.send() future call taking too much time [openwhisk]

2024-08-26 Thread via GitHub


style95 commented on issue #5506:
URL: https://github.com/apache/openwhisk/issues/5506#issuecomment-2311134111

   @abdulmonum 
   Are you using the kafka trigger to invoke your action?
   Basically, your assumption is correct. If pods are already created and your 
action only takes 0.02 seconds, it should be fine.
   What is the batch size of your kafka producer and what is the user memory 
configured for the invoker?
   Do you have any suspicious logs on the consumer side as well?
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] KafkaProducerConnector producer.send() future call taking too much time [openwhisk]

2024-08-26 Thread via GitHub


abdulmonum commented on issue #5506:
URL: https://github.com/apache/openwhisk/issues/5506#issuecomment-2310711363

   @style95 I see these logs periodically in the kafka-event-provider pod and I 
am not sure if this is related:
   
   [2024-08-25T19:45:40.323Z] [INFO] [??] [kafkatriggers] [canary] I found a 
canary. The last one was 60.168319 seconds ago.
   [2024-08-25T19:46:40.503Z] [INFO] [??] [kafkatriggers] [canary] I found a 
canary. The last one was 60.178885 seconds ago.
   [2024-08-25T19:47:40.649Z] [INFO] [??] [kafkatriggers] [canary] I found a 
canary. The last one was 60.1465 seconds ago.
   [2024-08-25T19:48:40.824Z] [INFO] [??] [kafkatriggers] [canary] I found a 
canary. The last one was 60.173952 seconds ago.
   [2024-08-25T19:49:40.829Z] [ERROR] [??] [kafkatriggers] [canary] Exception 
caught from changes feed. Restarting changes feed...
   [2024-08-25T19:49:40.829Z] [ERROR] [??] [kafkatriggers] 
HTTPConnectionPool(host='owdev-couchdb.openwhisk.svc.cluster.local', 
port=5984): Read timed out.
   [2024-08-25T19:49:40.829Z] [INFO] [??] [kafkatriggers] Shutting down 
existing DB client
   [2024-08-25T19:49:40.830Z] [INFO] [??] [kafkatriggers] Resetting dropped 
connection: owdev-couchdb.openwhisk.svc.cluster.local
   [2024-08-25T19:49:40.840Z] [INFO] [??] [kafkatriggers] Starting changes feed
   [2024-08-25T19:49:40.843Z] [INFO] [??] [kafkatriggers] Starting new HTTP 
connection (1): owdev-couchdb.openwhisk.svc.cluster.local
   [2024-08-25T19:49:40.872Z] [INFO] [??] [kafkatriggers] Database exists - 
connecting to it.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] KafkaProducerConnector producer.send() future call taking too much time [openwhisk]

2024-08-26 Thread via GitHub


abdulmonum commented on issue #5506:
URL: https://github.com/apache/openwhisk/issues/5506#issuecomment-2310705982

   I have one node for the invoker. No prewarmed containers (like in ow 
terminology) but I force 60 cold starts to create 60 containers (for the same 
action) and once they are up and running, I invoke a workload (the same action) 
with a fixed arrival rate of 100 rps. A request takes around ~ 0.02 seconds. So 
in principle, there should be 2 containers busy at all times which is also the 
case. However, between this workload, there are periodic bursts of 40-60+ jobs 
getting queued at the KafkaProducerConnector producer.send() future call which 
all of them then go to the invoker and then if around 60+ jobs were queued get 
scheduled, it then induces a cold start. I am not sure why there would be a 
backpressure from the invoker when there are no no cold starts happening? And 
how would a backpressure from the invoker introduce pressure on kafka from not 
being to send the acknowledgment to the controller that it has produced the 
message? 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] update openwhisk-client-js version in test files [openwhisk-runtime-nodejs]

2024-08-26 Thread via GitHub


dgrove-oss opened a new pull request, #253:
URL: https://github.com/apache/openwhisk-runtime-nodejs/pull/253

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] Bump express from 4.17.3 to 4.19.2 in /core/nodejsActionBase [openwhisk-runtime-nodejs]

2024-08-26 Thread via GitHub


dependabot[bot] commented on PR #250:
URL: 
https://github.com/apache/openwhisk-runtime-nodejs/pull/250#issuecomment-2310210538

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. If you'd rather skip all updates until the next 
major or minor version, let me know by commenting `@dependabot ignore this 
major version` or `@dependabot ignore this minor version`.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] Bump express from 4.17.3 to 4.19.2 in /core/nodejsActionBase [openwhisk-runtime-nodejs]

2024-08-26 Thread via GitHub


dgrove-oss closed pull request #250: Bump express from 4.17.3 to 4.19.2 in 
/core/nodejsActionBase
URL: https://github.com/apache/openwhisk-runtime-nodejs/pull/250


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] Make a 2.0.0 release of Helm Chart (to match OpenWhisk 2.0.0 release) [openwhisk-deploy-kube]

2024-08-26 Thread via GitHub


singhsegv commented on issue #781:
URL: 
https://github.com/apache/openwhisk-deploy-kube/issues/781#issuecomment-2309881408

   Hey @dgrove-oss 
   
   I've been using OpenWhisk on k8s for a research project and wanted to test 
how the performance differs with the latest version of invoker/controller/etc. 
I'd love to pick this up if someone can point me to the right direction and 
help to understand what all needs to be changed.
   
   Currently just changing the docker image tags to latest one end up with 
these error:
   ```
   Exception in thread "main" pureconfig.error.ConfigReaderException: Cannot 
convert configuration to a org.apache.openwhisk.core.etcd.EtcdConfig. Failures 
are:
 at 'whisk':
   - Key not found: 'etcd'.
   
at pureconfig.package$.getResultOrThrow(package.scala:139)
at pureconfig.package$.loadConfigOrThrow(package.scala:161)
at 
org.apache.openwhisk.core.loadBalancer.FPCPoolBalancer$.instance(FPCPoolBalancer.scala:721)
at 
org.apache.openwhisk.core.controller.Controller.(Controller.scala:119)
at 
org.apache.openwhisk.core.controller.Controller$.start(Controller.scala:338)
at 
org.apache.openwhisk.core.controller.Controller$.main(Controller.scala:291)
at 
org.apache.openwhisk.core.controller.Controller.main(Controller.scala)
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] Update express from 4.17.3 to 4.19.2 [openwhisk-runtime-nodejs]

2024-08-25 Thread via GitHub


Luke-Roy-IBM merged PR #252:
URL: https://github.com/apache/openwhisk-runtime-nodejs/pull/252


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] KafkaProducerConnector producer.send() future call taking too much time [openwhisk]

2024-08-25 Thread via GitHub


style95 commented on issue #5506:
URL: https://github.com/apache/openwhisk/issues/5506#issuecomment-2309083511

   @abdulmonum
   How many nodes do you have for the invoker?
   And how many prewarmed containers do you have?
   The issue might be due to a limited number of invokers or slow container 
(pod) creation, which can cause backpressure.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] Update express from 4.17.3 to 4.19.2 [openwhisk-runtime-nodejs]

2024-08-23 Thread via GitHub


dgrove-oss opened a new pull request, #252:
URL: https://github.com/apache/openwhisk-runtime-nodejs/pull/252

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] Docs update needed: ACTION.md [openwhisk-runtime-go]

2024-08-23 Thread via GitHub


Luke-Roy-IBM closed issue #178: Docs update needed: ACTION.md
URL: https://github.com/apache/openwhisk-runtime-go/issues/178


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] missed doc update for array results [openwhisk-runtime-go]

2024-08-23 Thread via GitHub


Luke-Roy-IBM merged PR #203:
URL: https://github.com/apache/openwhisk-runtime-go/pull/203


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] Docs update needed: ACTION.md [openwhisk-runtime-go]

2024-08-23 Thread via GitHub


Luke-Roy-IBM closed issue #178: Docs update needed: ACTION.md
URL: https://github.com/apache/openwhisk-runtime-go/issues/178


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] update scalafmt plugin version to fix build break [openwhisk-runtime-nodejs]

2024-08-23 Thread via GitHub


Luke-Roy-IBM merged PR #251:
URL: https://github.com/apache/openwhisk-runtime-nodejs/pull/251


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] missed doc update for array results [openwhisk-runtime-go]

2024-08-23 Thread via GitHub


dgrove-oss opened a new pull request, #203:
URL: https://github.com/apache/openwhisk-runtime-go/pull/203

   Fixes #178.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] KafkaProducerConnector producer.send() future call taking too much time [openwhisk]

2024-08-23 Thread via GitHub


abdulmonum commented on issue #5506:
URL: https://github.com/apache/openwhisk/issues/5506#issuecomment-2307271864

   My bad, the offset is 524 and the partition was 0 as seen from the log 
message.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] Drop support for golang 1.20 [openwhisk-runtime-go]

2024-08-23 Thread via GitHub


dgrove-oss merged PR #202:
URL: https://github.com/apache/openwhisk-runtime-go/pull/202


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] update scalafmt plugin version to fix build break [openwhisk-runtime-dotnet]

2024-08-23 Thread via GitHub


dgrove-oss merged PR #82:
URL: https://github.com/apache/openwhisk-runtime-dotnet/pull/82


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] upgrade scalafmt plugin version to fix build [openwhisk-runtime-docker]

2024-08-23 Thread via GitHub


Luke-Roy-IBM merged PR #104:
URL: https://github.com/apache/openwhisk-runtime-docker/pull/104


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] update scalafmt plugin version to fix build break [openwhisk-runtime-python]

2024-08-23 Thread via GitHub


Luke-Roy-IBM merged PR #162:
URL: https://github.com/apache/openwhisk-runtime-python/pull/162


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] update scalafmt plugin version to fix build break [openwhisk-runtime-ruby]

2024-08-23 Thread via GitHub


Luke-Roy-IBM merged PR #85:
URL: https://github.com/apache/openwhisk-runtime-ruby/pull/85


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] update gradle plugin version to fix build [openwhisk-runtime-rust]

2024-08-23 Thread via GitHub


Luke-Roy-IBM merged PR #49:
URL: https://github.com/apache/openwhisk-runtime-rust/pull/49


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] update scalafmt plugin version to fix build break [openwhisk-runtime-swift]

2024-08-23 Thread via GitHub


Luke-Roy-IBM merged PR #164:
URL: https://github.com/apache/openwhisk-runtime-swift/pull/164


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] KafkaProducerConnector producer.send() future call taking too much time [openwhisk]

2024-08-22 Thread via GitHub


style95 commented on issue #5506:
URL: https://github.com/apache/openwhisk/issues/5506#issuecomment-2305962768

   There is only one consumer for the topic, why do you have so many partitions?
   While one consumer can receive messages from multiple partitions, it is not 
good for performance as far as I know.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[I] KafkaProducerConnector producer.send() future call taking too much time [openwhisk]

2024-08-22 Thread via GitHub


abdulmonum opened a new issue, #5506:
URL: https://github.com/apache/openwhisk/issues/5506

   
   -->
   
   ## Environment details:
   
   * I am using k8s setup on openwhisk-deploy-kube, with action limits 
increased to 9 .
   * One node hosts OW core components, the other node hosts the invoker
   *  Using the old scheduler, using a client generating request rate of around 
100 rps, function take 0.02 seconds to complete ( all invoked with blocking 
calls)
   * There are already 60 warm containers up and running before generating 
100rps workload
   * one controller and one invoker node both with 1024 Jvm heap
   
   I found that requests formed a short queue when the controller schedules 
activation and posts the topic for invoker to consume
   Here is an example log for a tid: 
   
   [2024-08-17T19:12:51.632Z] [INFO] [#tid_cbDR904isIhkDhBksSNU4GiocWngMPD1] 
[ActionsApi]  [marker:controller_blockingActivation_start:104]
   [2024-08-17T19:12:51.632Z] [INFO] [#tid_cbDR904isIhkDhBksSNU4GiocWngMPD1] 
[ActionsApi] action activation id: d3b7ed1f632b4bd1b7ed1f632b4bd101 
[marker:controller_loadbalancer_start:104]
   [2024-08-17T19:12:51.632Z] [INFO] [#tid_cbDR904isIhkDhBksSNU4GiocWngMPD1] 
[ShardingContainerPoolBalancer] scheduled activation 
d3b7ed1f632b4bd1b7ed1f632b4bd101, action 'guest/aes@0.0.1' (managed), ns 
'guest', mem limit 256 MB (std), time limit 6 ms (std) to 
invoker0/owdev-invoker-0
   [2024-08-17T19:12:51.632Z] [INFO] [#tid_cbDR904isIhkDhBksSNU4GiocWngMPD1] 
[ShardingContainerPoolBalancer] posting topic 'invoker0' with activation id 
'd3b7ed1f632b4bd1b7ed1f632b4bd101' [marker:controller_kafka_start:104]
   [2024-08-17T19:12:51.666Z] [DEBUG] [#tid_cbDR904isIhkDhBksSNU4GiocWngMPD1] 
[KafkaProducerConnector] sent message: invoker0[0][524]
   [2024-08-17T19:12:51.666Z] [INFO] [#tid_cbDR904isIhkDhBksSNU4GiocWngMPD1] 
[ShardingContainerPoolBalancer] posted to invoker0[0][524] 
[marker:controller_kafka_finish:122:18]
   [2024-08-17T19:12:51.666Z] [INFO] [#tid_cbDR904isIhkDhBksSNU4GiocWngMPD1] 
[ActionsApi]  [marker:controller_loadbalancer_finish:122:18]
   
   The time between sent [ShardingContainerPoolBalancer] posting topic 
'invoker0' and [KafkaProducerConnector] sent message: invoker0[0][524] is more 
than 30ms (there are cases when its more)  and this results in many requests 
forming a queue here and subsequently a burst of jobs scheduled to invoker.
   
   Upon inspecting source code in KafkaProducerConnector:
   
   Future {
 blocking {
   try {
 producer.send(record, new Callback {
   override def onCompletion(metadata: RecordMetadata, exception: 
Exception): Unit = {
 if (exception == null)
   produced.trySuccess(ResultMetadata(metadata.topic(), 
metadata.partition(), metadata.offset()))
 else produced.tryFailure(exception)
   }
 })
   } catch {
 case e: Throwable =>
   produced.tryFailure(e)
   }
 }
   }
   
   produced.future.andThen {
 case Success(status) =>
   logging.debug(this, s"sent message: 
${status.topic}[${status.partition}][${status.offset}]")
   sentCounter.next()
 case Failure(t) =>
   logging.error(this, s"sending message on topic '$topic' failed: 
${t.getMessage}")
   
   Produced.future sucess is taking time. Upon checking logs more i found that 
messages invoker0[0][519-523] are sent in the meantime after the 
producer.send() with parititon 524 of and then finally invoker0[0][524] is 
sent. Why is the call and how can I increase performance here so that the short 
queue that forms does not happen because of the slow return of the future?
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] update scalafmt plugin version to fix build break [openwhisk-runtime-swift]

2024-08-22 Thread via GitHub


dgrove-oss closed pull request #164: update scalafmt plugin version to fix 
build break
URL: https://github.com/apache/openwhisk-runtime-swift/pull/164


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] update gradle plugin version to fix build [openwhisk-runtime-rust]

2024-08-22 Thread via GitHub


dgrove-oss closed pull request #49: update gradle plugin version to fix build
URL: https://github.com/apache/openwhisk-runtime-rust/pull/49


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] update scalafmt plugin version to fix build break [openwhisk-runtime-dotnet]

2024-08-22 Thread via GitHub


dgrove-oss closed pull request #82: update scalafmt plugin version to fix build 
break
URL: https://github.com/apache/openwhisk-runtime-dotnet/pull/82


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] update scalafmt plugin version to fix build break [openwhisk-runtime-nodejs]

2024-08-22 Thread via GitHub


dgrove-oss closed pull request #251: update scalafmt plugin version to fix 
build break
URL: https://github.com/apache/openwhisk-runtime-nodejs/pull/251


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] update scalafmt plugin version to fix build break [openwhisk-runtime-swift]

2024-08-22 Thread via GitHub


dgrove-oss opened a new pull request, #164:
URL: https://github.com/apache/openwhisk-runtime-swift/pull/164

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] update gradle plugin version to fix build [openwhisk-runtime-rust]

2024-08-22 Thread via GitHub


dgrove-oss opened a new pull request, #49:
URL: https://github.com/apache/openwhisk-runtime-rust/pull/49

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] update scalafmt plugin version to fix build break [openwhisk-runtime-python]

2024-08-22 Thread via GitHub


dgrove-oss opened a new pull request, #162:
URL: https://github.com/apache/openwhisk-runtime-python/pull/162

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] update scalafmt plugin version to fix build break [openwhisk-runtime-nodejs]

2024-08-22 Thread via GitHub


dgrove-oss opened a new pull request, #251:
URL: https://github.com/apache/openwhisk-runtime-nodejs/pull/251

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] update scalafmt plugin version to fix build break [openwhisk-runtime-dotnet]

2024-08-22 Thread via GitHub


dgrove-oss opened a new pull request, #82:
URL: https://github.com/apache/openwhisk-runtime-dotnet/pull/82

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] Drop support for golang 1.20 [openwhisk-runtime-go]

2024-08-22 Thread via GitHub


dgrove-oss opened a new pull request, #202:
URL: https://github.com/apache/openwhisk-runtime-go/pull/202

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] Use ibm-semeru-runtimes:open-8u422-b05-jdk-focal (vulnerability fixes). [openwhisk-runtime-java]

2024-08-22 Thread via GitHub


Luke-Roy-IBM merged PR #164:
URL: https://github.com/apache/openwhisk-runtime-java/pull/164


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] Add support for golang 1.23 [openwhisk-runtime-go]

2024-08-22 Thread via GitHub


Luke-Roy-IBM merged PR #201:
URL: https://github.com/apache/openwhisk-runtime-go/pull/201


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] Update gradle-scalafmt to 1.5.1 to fix build. [openwhisk-runtime-java]

2024-08-22 Thread via GitHub


Luke-Roy-IBM merged PR #165:
URL: https://github.com/apache/openwhisk-runtime-java/pull/165


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] Fix missing cz.alenkacz:gradle-scalafmt build error. [openwhisk]

2024-08-22 Thread via GitHub


Luke-Roy-IBM merged PR #5505:
URL: https://github.com/apache/openwhisk/pull/5505


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] Fix missing cz.alenkacz:gradle-scalafmt build error. [openwhisk]

2024-08-21 Thread via GitHub


falkzoll commented on PR #5505:
URL: https://github.com/apache/openwhisk/pull/5505#issuecomment-2302184585

   Some more changes are required, I will update this PR as soon as I have a 
fix for this.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] Fix missing cz.alenkacz:gradle-scalafmt build error. [openwhisk]

2024-08-21 Thread via GitHub


falkzoll opened a new pull request, #5505:
URL: https://github.com/apache/openwhisk/pull/5505

   Fix missing cz.alenkacz:gradle-scalafmt build error.
   
   ## Description
   Move gradle scalafmt plugin from using legacy gradle import to dsl import. 
This should automatically adjust when the gradle plugin repository is moved. 
The legacy approach was a fixed location and failed when it is moved for some 
reason.
   
   ## Related issue and scope
   
   - [ ] I opened an issue to propose and discuss this change (#)
   
   ## My changes affect the following components
   
   
   - [ ] API
   - [ ] Controller
   - [ ] Message Bus (e.g., Kafka)
   - [ ] Loadbalancer
   - [ ] Scheduler
   - [ ] Invoker
   - [ ] Intrinsic actions (e.g., sequences, conductors)
   - [ ] Data stores (e.g., CouchDB)
   - [ ] Tests
   - [ ] Deployment
   - [ ] CLI
   - [X] General tooling
   - [ ] Documentation
   
   ## Types of changes
   
   - [X] Bug fix (generally a non-breaking change which closes an issue).
   - [ ] Enhancement or new feature (adds new functionality).
   - [ ] Breaking change (a bug fix or enhancement which changes existing 
behavior).
   
   ## Checklist:
   
   
   - [X] I signed an [Apache 
CLA](https://github.com/apache/openwhisk/blob/master/CONTRIBUTING.md).
   - [X] I reviewed the [style 
guides](https://github.com/apache/openwhisk/blob/master/CONTRIBUTING.md#coding-standards)
 and followed the recommendations (Travis CI will check :).
   - [ ] I added tests to cover my changes.
   - [ ] My changes require further changes to the documentation.
   - [ ] I updated the documentation where necessary.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] Add support for golang 1.23 [openwhisk-runtime-go]

2024-08-20 Thread via GitHub


dgrove-oss commented on PR #201:
URL: 
https://github.com/apache/openwhisk-runtime-go/pull/201#issuecomment-2298913645

   We may have to fix the build problem in core openwhisk (pulling obsolete 
scalafmt) before we can get a passing CI and be able to merge.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] Add support for golang 1.23 [openwhisk-runtime-go]

2024-08-20 Thread via GitHub


dgrove-oss commented on code in PR #201:
URL: 
https://github.com/apache/openwhisk-runtime-go/pull/201#discussion_r1723345401


##
.gitignore:
##
@@ -20,6 +20,7 @@ actionloop/proxy
 golang1.20/proxy
 golang1.21/proxy
 golang1.22/proxy
+golang1.22/proxy

Review Comment:
   ```suggestion
   golang1.23/proxy
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



  1   2   3   4   5   6   7   8   9   10   >