Integrations fail with Jib publish strategy

What happened?
Integrations do not run with publish strategy Jib.
While using v2.1.0 the build fails before an image can be created with minimal logging detail
While using v2.0.0 the build succeeds but the container is not able to be created/deployed
Steps to reproduce

Install camel-k 2.1.0 or 2.0.0 with --build-publish-strategy Jib
Run an integration

Relevant log output
2.1.0 logs:
{"level":"info","ts":"2023-12-21T21:16:07Z","logger":"camel-k.maven.build","msg":"OS name: \"linux\", version: \"5.15.49-linuxkit-pr\", arch: \"amd64\", family: \"unix\""}
{"level":"error","ts":"2023-12-21T21:16:22Z","logger":"camel-k","msg":"jib integration image containerization did not run successfully","error":": exit status 1","stacktrace":"github.com/apache/camel-k/v2/pkg/util/log.Logger.Errorf\n\tgithub.com/apache/camel-k/v2/pkg/util/log/log.go:60\ngithub.com/apache/camel-k/v2/pkg/util/log.Errorf\n\tgithub.com/apache/camel-k/v2/pkg/util/log/log.go:227\ngithub.com/apache/camel-k/v2/pkg/builder.(*jibTask).Do\n\tgithub.com/apache/camel-k/v2/pkg/builder/jib.go:124\ngithub.com/apache/camel-k/v2/pkg/controller/build.(*monitorRoutineAction).runBuild\n\tgithub.com/apache/camel-k/v2/pkg/controller/build/monitor_routine.go:167"}
{"level":"info","ts":"2023-12-21T21:16:22Z","logger":"camel-k.controller.build","msg":"Build duration 25.49116277s","request-namespace":"default","request-name":"file-test","build-attempt":2,"build-result":"Failed","build-duration":25.49116277,"api-version":"camel.apache.org/v1","kind":"Build","ns":"default","name":"kit-cm2akkc738hs73cqta0g"}

2.0.0 integration event:
Cannot reconcile Integration file-test: error executing post actions: error during apply resource: default/file-test: Deployment.apps "file-test" is invalid: spec.template.spec.containers[0].image: Required value

2.0.0 logs:
{"level":"info","ts":1703194322.3954227,"logger":"camel-k.maven.build","msg":"BUILD SUCCESS"}
{"level":"info","ts":1703194322.395581,"logger":"camel-k.maven.build","msg":"------------------------------------------------------------------------"}
{"level":"info","ts":1703194322.3977785,"logger":"camel-k.maven.build","msg":"Total time:  02:15 min (Wall Clock)"}
{"level":"info","ts":1703194322.397876,"logger":"camel-k.maven.build","msg":"Finished at: 2023-12-21T21:32:02Z"}
...
{"level":"info","ts":1703194322.6735744,"logger":"camel-k.controller.integration","msg":"Reconciling Integration","request-namespace":"default","request-name":"file-test"}
{"level":"info","ts":1703194322.67364,"logger":"camel-k.controller.integration","msg":"Invoking action monitor","request-namespace":"default","request-name":"file-test","api-version":"camel.apache.org/v1","kind":"Integration","ns":"default","name":"file-test"}
{"level":"error","ts":1703194322.7993717,"msg":"Reconciler error","controller":"integration-controller","controllerGroup":"camel.apache.org","controllerKind":"Integration","Integration":{"name":"file-test","namespace":"default"},"namespace":"default","name":"file-test","reconcileID":"114fbd50-21ce-4059-88eb-5e2748bdfdeb","error":"error executing post actions: error during apply resource: default/file-test: Deployment.apps \"file-test\" is invalid: spec.template.spec.containers[0].image: Required value","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\tsigs.k8s.io/controller-runtime@v0.13.1/pkg/internal/controller/controller.go:326\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\tsigs.k8s.io/controller-runtime@v0.13.1/pkg/internal/controller/controller.go:273\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\tsigs.k8s.io/controller-runtime@v0.13.1/pkg/internal/controller/controller.go:234"}
{"level":"info","ts":1703194322.8051429,"logger":"camel-k.controller.integration","msg":"Reconciling Integration","request-namespace":"default","request-name":"file-test"}

Camel K version
2.1.0 & 2.0.0

@gansheer can you please have a look?

Hi @hernanDatgDev, I can't reproduce your issue, it works well for me.
Can you give us more details on your use case: how you installed the operator, with which configuration, what type of integration you are trying to run, etc.

Install command camel-k v2.1.0:
kamel install --registry docker.io --organization hguardado --registry-secret dockerhub-cred --maven-settings configmap:aws-repo/settings.xml --build-publish-strategy Jib --max-running-pipelines 2
Integration Platform:
ip-jib.yaml.txt
Test integration (timer-log.groovy):
from('timer:heartbeat?period=3000')
.log('heartbeat: (${exchangeProperty.CamelTimerCounter})')

Operator logs:
{"level":"info","ts":"2023-12-22T16:14:35Z","logger":"camel-k.controller.integrationkit","msg":"Build running","request-namespace":"default","request-name":"kit-cm2rbqvrbkps73cbuidg","api-version":"camel.apache.org/v1","kind":"IntegrationKit","ns":"default","name":"kit-cm2rbqvrbkps73cbuidg"}
{"level":"info","ts":"2023-12-22T16:14:35Z","logger":"camel-k.maven","msg":"executing: ./mvnw -V --no-transfer-progress -Dstyle.color=never package -Dmaven.repo.local=/etc/maven/m2 --global-settings /tmp/kit-cm2rbqvrbkps73cbuidg-4244968166/maven/settings.xml --settings /tmp/kit-cm2rbqvrbkps73cbuidg-4244968166/maven/user-settings.xml -Dmaven.artifact.threads=6 -T 6","MAVEN_OPTS":""}
{"level":"info","ts":"2023-12-22T16:14:35Z","logger":"camel-k.maven.build","msg":"Executed command: ./mvnw -V --no-transfer-progress -Dstyle.color=never package -Dmaven.repo.local=/etc/maven/m2 --global-settings /tmp/kit-cm2rbqvrbkps73cbuidg-4244968166/maven/settings.xml --settings /tmp/kit-cm2rbqvrbkps73cbuidg-4244968166/maven/user-settings.xml -Dmaven.artifact.threads=6 -T 6"}
{"level":"info","ts":"2023-12-22T16:14:36Z","logger":"camel-k.maven.build","msg":"SLF4J: Failed to load class \"org.slf4j.impl.StaticLoggerBinder\"."}
{"level":"info","ts":"2023-12-22T16:14:36Z","logger":"camel-k.maven.build","msg":"SLF4J: Defaulting to no-operation (NOP) logger implementation"}
{"level":"info","ts":"2023-12-22T16:14:36Z","logger":"camel-k.maven.build","msg":"SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details."}
{"level":"info","ts":"2023-12-22T16:14:36Z","logger":"camel-k.maven.build","msg":"Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)"}
{"level":"info","ts":"2023-12-22T16:14:36Z","logger":"camel-k.maven.build","msg":"Maven home: /usr/share/maven/wrapper/dists/apache-maven-3.8.6-bin/5f1464e3/apache-maven-3.8.6"}
{"level":"info","ts":"2023-12-22T16:14:36Z","logger":"camel-k.maven.build","msg":"Java version: <IP_ADDRESS>, vendor: Eclipse Adoptium, runtime: /opt/java/openjdk"}
{"level":"info","ts":"2023-12-22T16:14:36Z","logger":"camel-k.maven.build","msg":"Default locale: en_US, platform encoding: UTF-8"}
{"level":"info","ts":"2023-12-22T16:14:36Z","logger":"camel-k.maven.build","msg":"OS name: \"linux\", version: \"5.15.49-linuxkit-pr\", arch: \"amd64\", family: \"unix\""}
{"level":"info","ts":"2023-12-22T16:17:08Z","logger":"camel-k.builder","msg":"running builder task package in context directory: /tmp/kit-cm2rbqvrbkps73cbuidg-4244968166"}
{"level":"info","ts":"2023-12-22T16:17:08Z","logger":"camel-k.maven.build","msg":"Executed command: ./mvnw jib:build -V --no-transfer-progress -Dstyle.color=never -Dmaven.repo.local=/etc/maven/m2 --global-settings /tmp/kit-cm2rbqvrbkps73cbuidg-4244968166/maven/settings.xml --settings /tmp/kit-cm2rbqvrbkps73cbuidg-4244968166/maven/user-settings.xml -Dmaven.artifact.threads=6 -T 6 -P jib -Djib.to.image=docker.io/hguardado/camel-k-kit-cm2rbqvrbkps73cbuidg:2368668 -Djib.from.image=eclipse-temurin:17"}
{"level":"info","ts":"2023-12-22T16:17:08Z","logger":"camel-k.maven.build","msg":"SLF4J: Failed to load class \"org.slf4j.impl.StaticLoggerBinder\"."}
{"level":"info","ts":"2023-12-22T16:17:08Z","logger":"camel-k.maven.build","msg":"SLF4J: Defaulting to no-operation (NOP) logger implementation"}
{"level":"info","ts":"2023-12-22T16:17:08Z","logger":"camel-k.maven.build","msg":"SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details."}
{"level":"info","ts":"2023-12-22T16:17:08Z","logger":"camel-k.maven.build","msg":"Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)"}
{"level":"info","ts":"2023-12-22T16:17:08Z","logger":"camel-k.maven.build","msg":"Maven home: /usr/share/maven/wrapper/dists/apache-maven-3.8.6-bin/5f1464e3/apache-maven-3.8.6"}
{"level":"info","ts":"2023-12-22T16:17:08Z","logger":"camel-k.maven.build","msg":"Java version: <IP_ADDRESS>, vendor: Eclipse Adoptium, runtime: /opt/java/openjdk"}
{"level":"info","ts":"2023-12-22T16:17:08Z","logger":"camel-k.maven.build","msg":"Default locale: en_US, platform encoding: UTF-8"}
{"level":"info","ts":"2023-12-22T16:17:08Z","logger":"camel-k.maven.build","msg":"OS name: \"linux\", version: \"5.15.49-linuxkit-pr\", arch: \"amd64\", family: \"unix\""}
{"level":"error","ts":"2023-12-22T16:17:49Z","logger":"camel-k","msg":"jib integration image containerization did not run successfully","error":": exit status 1","stacktrace":"github.com/apache/camel-k/v2/pkg/util/log.Logger.Errorf\n\tgithub.com/apache/camel-k/v2/pkg/util/log/log.go:60\ngithub.com/apache/camel-k/v2/pkg/util/log.Errorf\n\tgithub.com/apache/camel-k/v2/pkg/util/log/log.go:227\ngithub.com/apache/camel-k/v2/pkg/builder.(*jibTask).Do\n\tgithub.com/apache/camel-k/v2/pkg/builder/jib.go:124\ngithub.com/apache/camel-k/v2/pkg/controller/build.(*monitorRoutineAction).runBuild\n\tgithub.com/apache/camel-k/v2/pkg/controller/build/monitor_routine.go:167"}
{"level":"info","ts":"2023-12-22T16:17:49Z","logger":"camel-k.controller.build","msg":"Build duration 3m14.774239727s","request-namespace":"default","request-name":"timer-log","build-attempt":0,"build-result":"Failed","build-duration":194.774239727,"api-version":"camel.apache.org/v1","kind":"Build","ns":"default","name":"kit-cm2rbqvrbkps73cbuidg"}
{"level":"error","ts":"2023-12-22T16:17:49Z","logger":"camel-k.controller.build","msg":"Build kit-cm2rbqvrbkps73cbuidg failed: : exit status 1","request-namespace":"default","request-name":"kit-cm2rbqvrbkps73cbuidg","api-version":"camel.apache.org/v1","kind":"Build","ns":"default","name":"kit-cm2rbqvrbkps73cbuidg","stacktrace":"github.com/apache/camel-k/v2/pkg/util/log.Logger.Errorf\n\tgithub.com/apache/camel-k/v2/pkg/util/log/log.go:60\ngithub.com/apache/camel-k/v2/pkg/controller/build.(*monitorRoutineAction).updateBuildStatus\n\tgithub.com/apache/camel-k/v2/pkg/controller/build/monitor_routine.go:216\ngithub.com/apache/camel-k/v2/pkg/controller/build.(*monitorRoutineAction).runBuild\n\tgithub.com/apache/camel-k/v2/pkg/controller/build/monitor_routine.go:200"}

Tried with camel-k v2.2.0 snapshot and received more information. Seems like a problem accessing the docker registry. The same registry secret works with Spectrum as the default publish strategy. I'm only seeing this when I use Jib. Also for more context I'm using docker-desktop as my test cluster.
{"level":"info","ts":"2023-12-22T18:09:19Z","logger":"camel-k.maven.build","msg":"Containerizing application to hguardado/camel-k-kit-cm2svndvohps73a2vhn0:2381653..."}
{"level":"info","ts":"2023-12-22T18:09:19Z","logger":"camel-k.maven.build","msg":"Base image 'eclipse-temurin:17' does not use a specific image digest - build may not be reproducible"}
{"level":"info","ts":"2023-12-22T18:09:19Z","logger":"camel-k.maven.build","msg":"Getting manifest for base image eclipse-temurin:17..."}
{"level":"info","ts":"2023-12-22T18:09:19Z","logger":"camel-k.maven.build","msg":"Building extra files layer..."}
{"level":"info","ts":"2023-12-22T18:09:20Z","logger":"camel-k.maven.build","msg":"The base image requires auth. Trying again for eclipse-temurin:17..."}
{"level":"info","ts":"2023-12-22T18:09:21Z","logger":"camel-k.maven.build","msg":"Using base image with digest: sha256:891bc1f583d287ba1f5f429e172c10ac5d692d2a02197dfef9bd6d16b2d9ed15"}
{"level":"error","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":"I/O error for image [registry-1.docker.io/hguardado/camel-k-kit-cm2svndvohps73a2vhn0]:","stacktrace":"github.com/apache/camel-k/v2/pkg/util/log.Logger.Error\n\tgithub.com/apache/camel-k/v2/pkg/util/log/log.go:81\ngithub.com/apache/camel-k/v2/pkg/util/maven.normalizeLog\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:83\ngithub.com/apache/camel-k/v2/pkg/util/maven.MavenLogHandler\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:54\ngithub.com/apache/camel-k/v2/pkg/util.scan\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:76\ngithub.com/apache/camel-k/v2/pkg/util.RunAndLog.func1\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:55\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/sync@v0.5.0/errgroup/errgroup.go:75"}
{"level":"error","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":"    java.net.SocketException","stacktrace":"github.com/apache/camel-k/v2/pkg/util/log.Logger.Error\n\tgithub.com/apache/camel-k/v2/pkg/util/log/log.go:81\ngithub.com/apache/camel-k/v2/pkg/util/maven.normalizeLog\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:83\ngithub.com/apache/camel-k/v2/pkg/util/maven.MavenLogHandler\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:54\ngithub.com/apache/camel-k/v2/pkg/util.scan\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:76\ngithub.com/apache/camel-k/v2/pkg/util.RunAndLog.func1\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:55\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/sync@v0.5.0/errgroup/errgroup.go:75"}
{"level":"error","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":"    Socket closed","stacktrace":"github.com/apache/camel-k/v2/pkg/util/log.Logger.Error\n\tgithub.com/apache/camel-k/v2/pkg/util/log/log.go:81\ngithub.com/apache/camel-k/v2/pkg/util/maven.normalizeLog\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:83\ngithub.com/apache/camel-k/v2/pkg/util/maven.MavenLogHandler\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:54\ngithub.com/apache/camel-k/v2/pkg/util.scan\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:76\ngithub.com/apache/camel-k/v2/pkg/util.RunAndLog.func1\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:55\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/sync@v0.5.0/errgroup/errgroup.go:75"}
{"level":"info","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":""}
{"level":"info","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":"A new version of jib-maven-plugin (3.4.0) is available (currently using 3.3.2). Update your build configuration to use the latest features and fixes!"}
{"level":"info","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":"https://github.com/GoogleContainerTools/jib/blob/master/jib-maven-plugin/CHANGELOG.md"}
{"level":"info","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":""}
{"level":"info","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":"Please see https://github.com/GoogleContainerTools/jib/blob/master/docs/privacy.md for info on disabling this update check."}
{"level":"info","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":""}
{"level":"info","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":""}
{"level":"info","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":"------------------------------------------------------------------------"}
{"level":"info","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":"BUILD FAILURE"}
{"level":"info","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":"------------------------------------------------------------------------"}
{"level":"info","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":"Total time:  9.211 s (Wall Clock)"}
{"level":"info","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":"Finished at: 2023-12-22T18:09:27Z"}
{"level":"info","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":"------------------------------------------------------------------------"}
{"level":"error","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":"Failed to execute goal com.google.cloud.tools:jib-maven-plugin:3.3.2:build (default-cli) on project camel-k-integration: Build image failed, perhaps you should make sure your credentials for 'registry-1.docker.io/hguardado/camel-k-kit-cm2svndvohps73a2vhn0' are set up correctly. See https://github.com/GoogleContainerTools/jib/blob/master/docs/faq.md#what-should-i-do-when-the-registry-responds-with-unauthorized for help: Unauthorized for registry-1.docker.io/hguardado/camel-k-kit-cm2svndvohps73a2vhn0: 401 Unauthorized","stacktrace":"github.com/apache/camel-k/v2/pkg/util/log.Logger.Error\n\tgithub.com/apache/camel-k/v2/pkg/util/log/log.go:81\ngithub.com/apache/camel-k/v2/pkg/util/maven.normalizeLog\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:83\ngithub.com/apache/camel-k/v2/pkg/util/maven.MavenLogHandler\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:54\ngithub.com/apache/camel-k/v2/pkg/util.scan\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:76\ngithub.com/apache/camel-k/v2/pkg/util.RunAndLog.func1\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:55\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/sync@v0.5.0/errgroup/errgroup.go:75"}
{"level":"error","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":"HEAD https://registry-1.docker.io/v2/hguardado/camel-k-kit-cm2svndvohps73a2vhn0/blobs/sha256:cf9fc801eb7a0d37087e74dcf17515971db337122da90a47e46bf441147f809a","stacktrace":"github.com/apache/camel-k/v2/pkg/util/log.Logger.Error\n\tgithub.com/apache/camel-k/v2/pkg/util/log/log.go:81\ngithub.com/apache/camel-k/v2/pkg/util/maven.normalizeLog\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:83\ngithub.com/apache/camel-k/v2/pkg/util/maven.MavenLogHandler\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:54\ngithub.com/apache/camel-k/v2/pkg/util.scan\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:76\ngithub.com/apache/camel-k/v2/pkg/util.RunAndLog.func1\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:55\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/sync@v0.5.0/errgroup/errgroup.go:75"}
{"level":"error","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":"-> [Help 1]","stacktrace":"github.com/apache/camel-k/v2/pkg/util/log.Logger.Error\n\tgithub.com/apache/camel-k/v2/pkg/util/log/log.go:81\ngithub.com/apache/camel-k/v2/pkg/util/maven.normalizeLog\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:83\ngithub.com/apache/camel-k/v2/pkg/util/maven.MavenLogHandler\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:54\ngithub.com/apache/camel-k/v2/pkg/util.scan\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:76\ngithub.com/apache/camel-k/v2/pkg/util.RunAndLog.func1\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:55\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/sync@v0.5.0/errgroup/errgroup.go:75"}
{"level":"error","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":"","stacktrace":"github.com/apache/camel-k/v2/pkg/util/log.Logger.Error\n\tgithub.com/apache/camel-k/v2/pkg/util/log/log.go:81\ngithub.com/apache/camel-k/v2/pkg/util/maven.normalizeLog\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:83\ngithub.com/apache/camel-k/v2/pkg/util/maven.MavenLogHandler\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:54\ngithub.com/apache/camel-k/v2/pkg/util.scan\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:76\ngithub.com/apache/camel-k/v2/pkg/util.RunAndLog.func1\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:55\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/sync@v0.5.0/errgroup/errgroup.go:75"}
{"level":"error","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":"To see the full stack trace of the errors, re-run Maven with the -e switch.","stacktrace":"github.com/apache/camel-k/v2/pkg/util/log.Logger.Error\n\tgithub.com/apache/camel-k/v2/pkg/util/log/log.go:81\ngithub.com/apache/camel-k/v2/pkg/util/maven.normalizeLog\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:83\ngithub.com/apache/camel-k/v2/pkg/util/maven.MavenLogHandler\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:54\ngithub.com/apache/camel-k/v2/pkg/util.scan\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:76\ngithub.com/apache/camel-k/v2/pkg/util.RunAndLog.func1\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:55\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/sync@v0.5.0/errgroup/errgroup.go:75"}
{"level":"error","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":"Re-run Maven using the -X switch to enable full debug logging.","stacktrace":"github.com/apache/camel-k/v2/pkg/util/log.Logger.Error\n\tgithub.com/apache/camel-k/v2/pkg/util/log/log.go:81\ngithub.com/apache/camel-k/v2/pkg/util/maven.normalizeLog\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:83\ngithub.com/apache/camel-k/v2/pkg/util/maven.MavenLogHandler\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:54\ngithub.com/apache/camel-k/v2/pkg/util.scan\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:76\ngithub.com/apache/camel-k/v2/pkg/util.RunAndLog.func1\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:55\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/sync@v0.5.0/errgroup/errgroup.go:75"}
{"level":"error","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":"","stacktrace":"github.com/apache/camel-k/v2/pkg/util/log.Logger.Error\n\tgithub.com/apache/camel-k/v2/pkg/util/log/log.go:81\ngithub.com/apache/camel-k/v2/pkg/util/maven.normalizeLog\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:83\ngithub.com/apache/camel-k/v2/pkg/util/maven.MavenLogHandler\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:54\ngithub.com/apache/camel-k/v2/pkg/util.scan\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:76\ngithub.com/apache/camel-k/v2/pkg/util.RunAndLog.func1\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:55\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/sync@v0.5.0/errgroup/errgroup.go:75"}
{"level":"error","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":"For more information about the errors and possible solutions, please read the following articles:","stacktrace":"github.com/apache/camel-k/v2/pkg/util/log.Logger.Error\n\tgithub.com/apache/camel-k/v2/pkg/util/log/log.go:81\ngithub.com/apache/camel-k/v2/pkg/util/maven.normalizeLog\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:83\ngithub.com/apache/camel-k/v2/pkg/util/maven.MavenLogHandler\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:54\ngithub.com/apache/camel-k/v2/pkg/util.scan\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:76\ngithub.com/apache/camel-k/v2/pkg/util.RunAndLog.func1\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:55\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/sync@v0.5.0/errgroup/errgroup.go:75"}
{"level":"error","ts":"2023-12-22T18:09:27Z","logger":"camel-k.maven.build","msg":"[Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException","stacktrace":"github.com/apache/camel-k/v2/pkg/util/log.Logger.Error\n\tgithub.com/apache/camel-k/v2/pkg/util/log/log.go:81\ngithub.com/apache/camel-k/v2/pkg/util/maven.normalizeLog\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:83\ngithub.com/apache/camel-k/v2/pkg/util/maven.MavenLogHandler\n\tgithub.com/apache/camel-k/v2/pkg/util/maven/maven_log.go:54\ngithub.com/apache/camel-k/v2/pkg/util.scan\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:76\ngithub.com/apache/camel-k/v2/pkg/util.RunAndLog.func1\n\tgithub.com/apache/camel-k/v2/pkg/util/command.go:55\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/sync@v0.5.0/errgroup/errgroup.go:75"}
{"level":"error","ts":"2023-12-22T18:09:27Z","logger":"camel-k","msg":"jib integration image containerization did not run successfully","error":": exit status 1","stacktrace":"github.com/apache/camel-k/v2/pkg/util/log.Logger.Errorf\n\tgithub.com/apache/camel-k/v2/pkg/util/log/log.go:66\ngithub.com/apache/camel-k/v2/pkg/util/log.Errorf\n\tgithub.com/apache/camel-k/v2/pkg/util/log/log.go:233\ngithub.com/apache/camel-k/v2/pkg/builder.(*jibTask).Do\n\tgithub.com/apache/camel-k/v2/pkg/builder/jib.go:129\ngithub.com/apache/camel-k/v2/pkg/controller/build.(*monitorRoutineAction).runBuild\n\tgithub.com/apache/camel-k/v2/pkg/controller/build/monitor_routine.go:167"}
{"level":"info","ts":"2023-12-22T18:09:27Z","logger":"camel-k.controller.build","msg":"Build duration 17.483306024s","request-namespace":"default","request-name":"timer-log","build-attempt":3,"build-result":"Failed","build-duration":17.483306024,"api-version":"camel.apache.org/v1","kind":"Build","ns":"default","name":"kit-cm2svndvohps73a2vhn0"}
{"level":"error","ts":"2023-12-22T18:09:27Z","logger":"camel-k.controller.build","msg":"Build kit-cm2svndvohps73a2vhn0 failed: : exit status 1","request-namespace":"default","request-name":"kit-cm2svndvohps73a2vhn0","api-version":"camel.apache.org/v1","kind":"Build","ns":"default","name":"kit-cm2svndvohps73a2vhn0","stacktrace":"github.com/apache/camel-k/v2/pkg/util/log.Logger.Errorf\n\tgithub.com/apache/camel-k/v2/pkg/util/log/log.go:66\ngithub.com/apache/camel-k/v2/pkg/controller/build.(*monitorRoutineAction).updateBuildStatus\n\tgithub.com/apache/camel-k/v2/pkg/controller/build/monitor_routine.go:216\ngithub.com/apache/camel-k/v2/pkg/controller/build.(*monitorRoutineAction).runBuild\n\tgithub.com/apache/camel-k/v2/pkg/controller/build/monitor_routine.go:200"}
{"level":"info","ts":"2023-12-22T18:09:27Z","logger":"camel-k.controller.build","msg":"State transition","request-namespace":"default","request-name":"kit-cm2svndvohps73a2vhn0","api-version":"camel.apache.org/v1","kind":"Build","ns":"default","name":"kit-cm2svndvohps73a2vhn0","phase-from":"Running","phase-to":"Failed"}

@hernanDatgDev it is probably an issue with how the registry secret is managed by the Jib publish strategy.
@squakez can you assign this to me ? I will look more into it.

@gansheer Unfortunately I'm still facing this unauthorized 401 registry issue with the latest release 2.2.0
This occurs in both my docker-desktop cluster and a local Minikube (with & without internal registry enabled)
Were you able to reproduce the error?
These are the latest steps I have for v 2.2.0:

kamel install --registry docker.io --organization hguardado --registry-secret dockerhub-cred \ --build-publish-strategy Jib
kamel run src/main/groovy/timer-log.groovy --dev

Log snippet from builder pod init-container: jib
{"level":"error","ts":"2024-01-08T20:47:58Z","logger":"camel-k.maven.build","msg":"Failed to execute goal com.google.cloud.tools:jib-maven-plugin:3.3.2:build (default-cli) on project camel-k-integration: Build image failed, perhaps you should make sure your credentials for 'registry-1.docker.io/hguardado/camel-k-kit-cme5uej3kd2c73eeqvqg' are set up correctly. See https://github.com/GoogleContainerTools/jib/blob/master/docs/faq.md#what-should-i-do-when-the-registry-responds-with-unauthorized for help: Unauthorized for registry-1.docker.io/hguardado/camel-k-kit-cme5uej3kd2c73eeqvqg: 401 Unauthorized

Full log:
builder.log

@hernanDatgDev Thanks for giving the detail of your installation.
I identified what you report while working on this issue #5017. There are definitely some multiple custom behavior on what registry URL is used when dealing with docker hub registry via docker.io. This will be fixed in #5017.
I will try to give you some workaround when I have more informations.

@hernanDatgDev To make it work with Jib you should access to the docker hub registry via registry-1.docker.io: kamel install --registry registry-1.docker.io. That means using it also as you auth server in your secret: {"auths":{"registry-1.docker.io":{"xxxx","password":"xxxx","auth":"xxxxx"}}}.
If you still really want to use docker.io as your registry on install, it might work if you declare both auth server in your secret: {"auths":{"registry-1.docker.io":{"xxxx","password":"xxxx","auth":"xxxxx"},"docker.io":{"xxxx","password":"xxxx","auth":"xxxxx"}}.

Hey @gansheer, unfortunately neither of these options worked for me and I tried other possibilities as well, but no luck. After all attempts I tried with the latest 2.3.0-SNAPSHOT and I got the expected behavior. For now this will work since I can proceed with my task. I'm still not sure what the issue is however I suspect there is some default docker values that are overriding whatever I input as you mentioned in #5017. I'm guessing this is the case because of the "/v2" I saw appended to my registry parameters in the logs despite explicitly defining only "v1"

You are right, it does not work in 2.2.0 release but works in 2.3.0-SNAPSHOT. The fix is not in the 2.2.0 release but will be part of the next one.

@gansheer I tried applying your fix to 2.1.0 and the Jib strategy is working as expected. I believe that the logging in 2.1.0 w/ Jib simply was not detailed enough so the errors I was getting were hiding the fact that there was an issue with the container registry. I'm willing to make a PR for patching 2.1.0 but I must admit I'm not sure what the patching process looks like.

We can backport to 2.1.x and if it's an issue that is blocking any production behavior we can make a patch release accordingly.

@hernanDatgDev To make a backport you just need to do a PR on the release-2.1.x branch.

@gansheer I've made the PR. Also I noticed there aren't any tests for the publish strategies. Would you happen to know if this is intentional?

The jib strategy are tested in e2e test - the builder workflow. The e2e tests are thoses executed with a kubernetes environment. Also the default strategy is used in lots of the other e2e tests that build any integration kit to run an integration.
On main branch it has been changed as the default startegy replacing spectrum, so from now on the jib strategy it will be used by all e2e tests.


docs: change expected identifier type to integer

Based on the work in https://github.com/DD-DeCaF/model-warehouse/pull/5 the organism_id in the model-warehouse is changed from string type to integer.

Codecov Report

Merging #114 into caffeine will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           caffeine     #114   +/-   ##
=========================================
  Coverage     73.08%   73.08%
=========================================
  Files            19       19
  Lines           639      639
=========================================
  Hits            467      467
  Misses          172      172

Impacted Files
Coverage Δ

src/model/storage.py
84.61% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 813ead5...77c1d7d. Read the comment docs.

Cheers, I'll let you merge this when the time is right.


Timing issue with subscribing to a reactive Supplier

Basically when you have something like this
@Bean
    public Supplier<Flux<String>> emit() {
        return () -> Flux.interval(Duration.ofMillis(10))
                         .map(aLong -> aLong+"")
                         .log();
    }

we go through ((Flux) publisher).delaySubscription(beginPublishingTrigger).map(this::wrapToMessageIfNecessary); effectively delaying subscription until binding is created. This is probably too clever and unnecessary and  presents a timing issue where application may actually exit if binding event does not appear on time.
The workaround for now is to add
<dependency>
	<groupId>org.springframework.boot</groupId>
	<artifactId>spring-boot-starter-web</artifactId>
</dependency>```

@olegz Additional info, with the current workaround (spring-boot-starter-web), during shutdown it loses some messages due to the subscription issue. No graceful shutdown happens. Here is the stacktrace for the same:

org.springframework.messaging.MessageDeliveryException: failed to send Message to channel 'emit_integrationflow.channel#0'; nested exception is java.lang.IllegalStateException: The [bean 'emit_integrationflow.channel#0'] doesn't have subscribers to accept messages
at org.springframework.integration.support.utils.IntegrationUtils.wrapInDeliveryExceptionIfNecessary(IntegrationUtils.java:166) ~[spring-integration-core-5.2.1.RELEASE.jar:5.2.1.RELEASE]
at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:483) ~[spring-integration-core-5.2.1.RELEASE.jar:5.2.1.RELEASE]
at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:403) ~[spring-integration-core-5.2.1.RELEASE.jar:5.2.1.RELEASE]

Caused by: java.lang.IllegalStateException: The [bean 'emit_integrationflow.channel#0'] doesn't have subscribers to accept messages
at org.springframework.util.Assert.state(Assert.java:94) ~[spring-core-5.2.1.RELEASE.jar:5.2.1.RELEASE]
at org.springframework.integration.channel.FluxMessageChannel.doSend(FluxMessageChannel.java:63) ~[spring-integration-core-5.2.1.RELEASE.jar:5.2.1.RELEASE]

org.springframework.messaging.MessageDeliveryException: failed to send Message to channel 'emit_integrationflow.channel#0'; nested exception is java.lang.IllegalStateException: The [bean 'emit_integrationflow.channel#0'] doesn't have subscribers to accept messages
at org.springframework.integration.support.utils.IntegrationUtils.wrapInDeliveryExceptionIfNecessary(IntegrationUtils.java:166) ~[spring-integration-core-5.2.1.RELEASE.jar:5.2.1.RELEASE]
at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:483) ~[spring-integration-core-5.2.1.RELEASE.jar:5.2.1.RELEASE]
at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:403) ~[spring-integration-core-5.2.1.RELEASE.jar:5.2.1.RELEASE]


Removal of project/solution configurations...

Over time, project/solutions get lots of build configurations added. I have successfully iterated and found a list and now want to purge...
Going manually into Visual Studio and deleting is not an option (I am looking at nearly 10K kills!!!!)... nut I am also not seeing a way to modify the collections and re-write the respective project (including .vcxproj, and vcsproj) files...
Am I missing something? Are heir any recommendations? Do I have to start writing raw tooling?
Thanks in Advance

Hello David,
Did you try something like https://github.com/3F/MvsSln/discussions/42
About locked collections in sln result, see #9
But it's all about convenience and you can re-write (construct)
anything using collections at runtime through map and its writer.
Some related example can be found also here
https://github.com/3F/MvsSln/discussions/43#discussioncomment-371185

"Do I have to start writing raw tooling?"

Not for this, since that's a common use.
I recommend to start detailed Q&A in Discussions here to find some final
solutions in your case.
Unfortunately I may be very slow to respond due to many reasons beyond
my control.
But maybe someone else will be faster than me.
On 24.08.2022 15:02, David V. Corbin wrote:

Over time, project/solutions get lots of build configurations added. I
have successfully iterated and found a list and now want to purge...
Going manually into Visual Studio and deleting is not an option (I am
looking at nearly 10K kills!!!!)... nut I am also not seeing a way to
modify the collections and re-write the respective project (including
.vcxproj, and vcsproj) files...
Am I missing something? Are heir any recommendations? Do I have to
start writing raw tooling?
Thanks in Advance


Handle unreadable data objects

Not all data objects can be read by data_package_read(). Perhaps a default value should be assigned to the data objects that can't be read (e.g. "Sorry, data_object_name.ext is an unsupported data type and cannot be read at this time.") so the UI can inform the user of this issue. What do you think @wetlandscapes, @ktoddbrown, @sheilasaia, @lkuiucsb ?

What do you think @sheilasaia and @wetlandscapes?

Maybe we can discuss as a group at the next meeting whether people think this is alpha or beta, @clnsmth? I'm more inclined to say alpha but could be persuaded if we're trying to get out the package asap/have a soft-release of the package.

IMO this is a basic feature that should be implemented before the public RFC (beta-release) to preempt the question every user will be asking of us (i.e. "Why isn't datapie allowing me to view X data object.").
One approach is to offer all data object names to the user for selection in the GUI drop down list, and when an unsupported object is selected, an informative message is returned to the user. We could implement this by having data_package_read() output the object list as is but updated to include the names of unsupported objects each accompanied by a message string. The GUI read/parse logic would have to be updated to pass this string to the user as a message and fail gracefully.

Data types that cannot be read by data_package_read() are now removed from the output list and corresponding notifications are printed to the "Raw Data" tab of the UI.

So much for my "fix". I've commented out this section of data_package_read() and am working on a more robust solution now.

Take 2.

@clnsmth, doi:10.6073/pasta/ea5c14e500ab121b254ee99f47a8affb cannot be read into the GUI because parsing failed for .data type files. Is this issue still relevant?

Yes, this issue is still relevant @atn38. But rather than trying to address this on our end, it may be simpler to address this in metajam.

working on this in branch fix_36

https://github.com/IMCR-Hackathon/datapie/issues/72#issuecomment-520888432 is more closely related to the work being done here, and will therefore not be resolved by fix_72.


Autodetect user language

Description
It would be pretty nice if we could detect the browser language or user IP. I don't know which one is the best, and preselect the website language based on this information.
UI Resource
N/A
Aditional information
Maybe we can find some information here: https://v2.docusaurus.io/docs/i18n/introduction
Possible unknowns

Should we use IP or Browser language?
Does Docusaurus already support it?

In the Docusaurus documentation there is a topic on the subject:
- Automatic locale detection: opinionated, and best done on the server
Issue: https://github.com/facebook/docusaurus/issues/4681


Add Docker Image Name

Greetings! Thanks for the docs on this, I'm excited to try this out!
In the 2nd paragraph the document states:
The acr purge command is currently distributed in a public container image available from Microsoft Container Registry.

What is the actual name of this image? The examples (just a pure guess here) point to mcr.microsoft.com/acr/acr-cli:1.0 but I'm not finding manifests for that image for either Linux or Windows. I also don't see any pages in Docker Hub for it.
Can you add this detail please? It would probably be best to link this document to the Docker Hub page for the images, and let that page describe how to use that container.
Thanks!
Brendan

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 40e52f8e-a63e-3e85-6c84-f881db5d3b6c
Version Independent ID: 1290c892-ea9d-d12c-be84-7ed75f28fca0
Content: Automatically remove image resources in Azure Container Registry
Content Source: articles/container-registry/container-registry-auto-purge.md
Service: container-registry
GitHub Login: @dlepow
Microsoft Alias: danlep

Thanks for the feedback! We are currently investigating and will update you shortly.

@sudobrendan you can find acr command info from https://github.com/Azure/acr-cli @sajayanyony @dlepow need to add the repo link on the document.

I'll add a link in the doc. Thanks for pointing this out.
#assign: @dlepow

No problem, thanks for pointing me in the right direction!

Thanks @dlepow :)
@SudoBrendan A PR has been created and changes will be live shortly.
Thanks for bringing this to our attention. We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


[Backport TC-228] postinstall improvements

lots of collective improvements to postinstall and postgres integration.

testing revealed one commit that should not have been pulled in.


feat(transformer): add proposal-decorators

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2868  👈
#2867
#2866
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Boshen and the rest of your teammates on  Graphite

Decorators is insane, is it viable to only support the latest "2023-11" version for now?

Decorators is insane, is it viable to only support the latest "2023-11" version for now?

Yes, we can only support 2023-11, it is match typescript@5

Merge activity

Mar 30, 9:02 AM EDT: Graphite rebased this pull request after merging its parent, because this pull request is set to merge when ready.


How to make it with dynamic batching?

This implementation can only process one sample at a time. The performance is limited since the usage of the GPU is low. Is there possibility to make treelstm support dynamic batching such that the GPU can be fully utilized?

Hi @xuehy
Extremely sorry for the late response! I somehow missed this issue.
To answer your question, it will be non-trivial for me to support dynamic batching for tree-LSTMs. This type of model, i.e. a recursive neural network, will have a different structure for each input sample, and it is extremely difficult (almost impossible) to find samples which might result in almost similar structures, so that we can batch them together. However, all is not lost, as there are a few options that can be explored:

SPINN: This model enables a hybrid tree-sequence architecture, blending the otherwise separate paradigms of recursive and recurrent neural networks. Links to the original blog post, and to PyTorch sample code

Tensorflow Fold: The first couple of paragraphs in the README are pretty self-explanatory.

Hogwild Training: I do have some plans to make it possible to train this code on multiple GPUs/CPUs using some sort of hogwild scheme. There is a PyTorch example available, which you can try to adapt.

Thanks for your detailed explanations! I am following SPINN's idea to make the network partially batched.


Update gh-pages to 0.10.0-beta

Customary PR to bring gh-pages branch to latest release (just the index.html demo, not the function-support.html which waits for @ronkok's PR).  We might consider making this part of the release script too (if we allow direct pushing to gh-pages by release maintainers).

@kevinbarabash Apparently I can't merge this?

@edemaine give it a try now.

@kevinbarabash Works now, thanks!


Fix compilation problem with Xcode 9

Looks as if the .rawValue has been deleted unintentionally. Without the .rawValue it does not compile with Xcode 9.

Please merge this PR

is it possible to merge this PR ?

Thanks @ammoqq - not seeing any compilation issues in Xcode 9.1 and this PR fils on Travis. Closing for now.

Hi, I've resolved switching SWIFT_VERSION to 4


Metric Type gets doubled in list while editing

At some point there need to be some fx (layout) imports. In my opinion this should be in the controller class of the fxml classes (because there are fx imports anyway).

fixed. Added some validation


Added a check for allready freed in wrenFreeVm.

If wrenFreeVm was called twice, this would lead to an error, because the memory was allready freed.
The used check is rather naive, suggesting that a valid vm does have at least one methodName set.

Thanks!


Add numeronyms functionality

Implemented numeronym functionality in a executable Go program which returns a slice of numeronyms given an input of n strings
Fixes #419
Review of colleague's PR #526

@pentaphobe PR # reference added.

Updated doc strings

Updated to handle multi byte characters

LGTM
@brvishnu92 please confirm you're happy with changes, some weren't dismissed automatically since the code lines weren't changed (see final review point)

@patrickmarabeas  LGTM :-)


Use Clang's logic for adding the default IR attributes to a function

A lot of attributes are essentially default target configuration, and we should only differ when there's a good reason to.
For the attributes we were already setting:

the ptrauth and target CPU/feature attributes are taken care of by Clang
I've updated the optsize/minsize attributes to the apparent intent
I've left the frame-pointer override in place for now

Fixes rdar://63289339, which was caused by Swift's ptrauth IR attributes getting out of sync with Clang's.

https://github.com/apple/llvm-project/pull/1245
@swift-ci Please test.

@stephentyrone This is also setting the LLVM floating-point attributes to match Clang's by default, so that e.g. on Darwin x86-64 I see for a simple Swift function:
attributes #0 = {
  norecurse
  nounwind
  readnone
  "correctly-rounded-divide-sqrt-fp-math"="false"
  "frame-pointer"="all"
  "less-precise-fpmad"="false"
  "no-infs-fp-math"="false"
  "no-nans-fp-math"="false"
  "no-signed-zeros-fp-math"="false"
  "no-trapping-math"="false"
  "stack-protector-buffer-size"="8"
  "target-cpu"="penryn"
  "target-features"="+cx16,+cx8,+fxsr,+mmx,+sahf,+sse,+sse2,+sse3,+sse4.1,+ssse3,+x87"
  "unsafe-fp-math"="false
  "use-soft-float"="false"
}

I don't know if anything in here strikes you as problematic.

Build failed
Swift Test OS X Platform
Git Sha - 0bc8ec28b5df102a7846176dc865559c94820a29

Build failed
Swift Test Linux Platform
Git Sha - 0bc8ec28b5df102a7846176dc865559c94820a29

apple/llvm-project#1245
@swift-ci Please test

Build failed
Swift Test OS X Platform
Git Sha - 0bc8ec28b5df102a7846176dc865559c94820a29

@compnerd Is there something special about the Windows builder that would make it not respect cross-repository testing?

Build failed
Swift Test Linux Platform
Git Sha - 0bc8ec28b5df102a7846176dc865559c94820a29

Yeah, the cross-repository settings are not propagated to the checkout on Windows.  @shahmishal was going to look into that (at least had expressed that he was interested in doing so a while ago).

Yeah, the cross-repository settings are not propagated to the checkout on Windows. @shahmishal was going to look into that (at least had expressed that he was interested in doing so a while ago).

Yes, I don't if I will be able to for few weeks.

https://github.com/apple/llvm-project/pull/1247
@swift-ci Please test.

Build failed
Swift Test Linux Platform
Git Sha - 0bc8ec28b5df102a7846176dc865559c94820a29

Build failed
Swift Test OS X Platform
Git Sha - 0bc8ec28b5df102a7846176dc865559c94820a29

apple/llvm-project#1247
@swift-ci Please test.

Build failed
Swift Test Linux Platform
Git Sha - 2f8ec9d2c712671394e4e91435288be918caea9d

Build failed
Swift Test OS X Platform
Git Sha - 2f8ec9d2c712671394e4e91435288be918caea9d

I don't know if anything in here strikes you as problematic.

Those all seem appropriate to me.


Minor file cleanups + remove support binary

And a few more commits transferred over from the former branch of #311
support-v4 is now a proper dependency (removed the binary file from the repo).

Just curious why newlines at the end of files are considered an error?

@davemorrissey Good question, and sorry for not adding a proper explanation in the PR description.
Basically, the reason why a missing newline at the end of the file is considered a problem comes down to the definition of what a "line" is by POSIX standard 3.206:

A sequence of zero or more non-  characters plus a terminating  character.

Of course, this sounds a bit academic, and most modern text editors will work just fine with or without the newline. However, some programs (e.g. command line tools like wc, cat, vi, etc) show incorrect or problematic behavior if the last line in the file does not end in a newline character.
You might also have seen Git command line warnings when running git diff such as:
No newline at end of file

Or (same thing) the little red icon warning on GitHub:

An easy way to remember is to think about it this way: There is nothing particularly special about the last line in a file in that is should not be terminated by a newline character (unlike all other lines in the file).


Fixed installation file problems.

Removed positional arguments and a relative directory walk.

This looks good to me


Populate instance types

Description of changes: Create a temporary policy that the custom CDK resource uses to populate the active instance types.
The lambda function (and this policy) are deleted after deployment is complete.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This faces the issue with customers providing manual IAM resources needing to pre-create this as part of install. Can this just use the app policy instead? It should be a part of the app role

^^ same as LightSeekerSC

This is replacing the app role because using the app role broke it.
This is creating an IAM policy for a lambda function that is only executed onCreate, and then the lambda and its policy are deleted.

We're doing something similar in this file, fwiw:
// Populate the App Config table with default config
        new AwsCustomResource(this, 'mlspace-init-ddb-app-config', {
            onCreate: {
                service: 'DynamoDB',
                action: 'putItem',
                parameters: {
                    TableName: props.mlspaceConfig.APP_CONFIGURATION_TABLE_NAME,
                    Item: generateAppConfig(props.mlspaceConfig),
                },
                physicalResourceId: PhysicalResourceId.of('initAppConfigData'),
            },
            policy: AwsCustomResourcePolicy.fromSdkCalls({ resources: [appConfigTable.tableArn] }),
        });

I approved but where does it delete it after create?

Hmm actually I was mistaken, it deletes resources for something like the PutItem example I posted, but this lambda will persist since I defined it myself. Will look into trying to get the app config role to work.

I'm merging this in for now so deployments with the latest code won't fail.
I'm meeting with the CDK team tomorrow during their office hours to get to the bottom of this. If we can figure something out using the mlspaceAppRole I'll implement that, if we can't figure something out then I'll rip out this functionality and we'll decide on a different path forward.
Our options if the CDK team can't help me find a solution are:

leave the enabled instances list blank by default and tell admins to select instances they want enabled during setup
curate a list of instance types available in all regions so there's a few instances in the list as a starting point


Native-tls support

Overall, I trie to test with the code change, but most of the https requests are failed with 500, probably it is pending on the Openssl patch.


Package

The new version with updated time notification is not packed into extension

Issue solved in PR#3


[Feature]: Implement pomodoro feature

To stay more focused on work/study. Implement a way to use the Pomodoro technique. there can be a specific channel or this feature can be used directly in bot DM. when users decide to use the feature they will directly click on some button and the bot will start the technique. bot will notify the user when to take a break. The bot will also show the session time. user can select different options like
work-break ratio like:
25/5
45/15
90/30

This Idea I cancelled due to not sufficient usage case


Windows 10 FileNotFoundError: [Errno 2]

Running TGAN on windows 10 and getting the following error:
Traceback (most recent call last):   File "src/launcher.py", line 134, in <module>     run_experiment(task)   File "src/launcher.py", line 108, in run_experiment     evaluate_res = pool.map(evaluate_worker, commands)   File "C:\Users\David Leon\AppData\Local\Programs\Python\Python36\lib\multiprocessing\pool.py", line 288, in map     return self._map_async(func, iterable, mapstar, chunksize).get()   File "C:\Users\David Leon\AppData\Local\Programs\Python\Python36\lib\multiprocessing\pool.py", line 670, in get     raise self._value FileNotFoundError: [Errno 2] No such file or directory: 'expdir\\census\\synthetic0_-1.npz'
I can't find the reason why the syntetic.npz file wasn't created since the training phase
had finished.
This is the error I get right after the training finished:
2019-01-15 13:52:40.119025: W tensorflow/core/kernels/queue_base.cc:277] _0_QueueInput/input_queue: Skipping cancelled enqueue attempt with queue not closed Traceback (most recent call last):   File "src/TGAN_synthesizer.py", line 314, in <module>     sample(args.sample, Model(), args.load, output_filename=args.output)   File "src/TGAN_synthesizer.py", line 235, in sample     session_init=get_model_loader(model_path),   File "C:\Users\David Leon\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorpack\tfutils\sessinit.py", line 262, in get_model_loader     return SaverRestore(filename)   File "C:\Users\David Leon\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorpack\tfutils\sessinit.py", line 107, in __init__     model_path = get_checkpoint_path(model_path)   File "C:\Users\David Leon\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorpack\tfutils\varmanip.py", line 182, in get_checkpoint_path     assert tf.gfile.Exists(model_path) or tf.gfile.Exists(model_path + '.index'), model_path AssertionError: train_log/TGAN_synthesizer:census-4/model--1000 Traceback (most recent call last):   File "src/TGAN_synthesizer.py", line 314, in <module>     sample(args.sample, Model(), args.load, output_filename=args.output)   File "src/TGAN_synthesizer.py", line 235, in sample     session_init=get_model_loader(model_path),   File "C:\Users\David Leon\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorpack\tfutils\sessinit.py", line 262, in get_model_loader     return SaverRestore(filename)   File "C:\Users\David Leon\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorpack\tfutils\sessinit.py", line 107, in __init__     model_path = get_checkpoint_path(model_path)   File "C:\Users\David Leon\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorpack\tfutils\varmanip.py", line 182, in get_checkpoint_path     assert tf.gfile.Exists(model_path) or tf.gfile.Exists(model_path + '.index'), model_path AssertionError: train_log/TGAN_synthesizer:census-4/model-0 Traceback (most recent call last):   File "src/TGAN_synthesizer.py", line 314, in <module>     sample(args.sample, Model(), args.load, output_filename=args.output)   File "src/TGAN_synthesizer.py", line 235, in sample     session_init=get_model_loader(model_path),   File "C:\Users\David Leon\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorpack\tfutils\sessinit.py", line 262, in get_model_loader     return SaverRestore(filename)   File "C:\Users\David Leon\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorpack\tfutils\sessinit.py", line 107, in __init__     model_path = get_checkpoint_path(model_path)   File "C:\Users\David Leon\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorpack\tfutils\varmanip.py", line 182, in get_checkpoint_path     assert tf.gfile.Exists(model_path) or tf.gfile.Exists(model_path + '.index'), model_path AssertionError: train_log/TGAN_synthesizer:census-4/model-1000
Thanks in advance for your time and your help.

same problem here.
thanks in advance

I also have the exact same problem and cannot get this to work on Windows 10 but appears to run with minimal alteration fine on Linux.
thanks in advance

This issue is caused by the multi-processing mechanism on windows. I uploaded launcher_simple.py which removes the process pools. It should work on Windows now.


LEDC fade semaphore dead-lock on ESP32 with ESP-IDF 5.1 (IDFGH-11466)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v5.1.1
Espressif SoC revision.
ESP32
Operating System used.
macOS
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
Development Kit.
Custom Board
Power Supply used.
External 3.3V
What is the expected behavior?
I expected it to continuously keep running and keep switching colour.
What is the actual behavior?
The code locks for esp32 after running the loop successfully for 3 time at xSemaphoreTake(fade->ledc_fade_sem, portMAX_DELAY); in ledc.c -> ledc_set_fade_with_time ->  _ledc_fade_hw_acquire
The issue doesn't occur when running for ESP32s3.
The code also runs fine for both esp32 and esp32s3 with v5.0.4 and master(v5.3-dev) but doesn't work for esp32 in v5.1.1 and v5.2-dev.
Steps to reproduce.
Run the code snippet on IDF v5.1.1 for esp32.
The loop just gets stuck after few iterations when using int target_duty[][3] = {{0, 255, 255}, {255, 0, 255}, {255, 255, 0}}; where as it works fine when using int target_duty[][3] = {{255, 0, 0}, {0, 255, 0}, {0, 0, 255}};
/* LEDC (LED Controller) fade example*/
#include <stdio.h>
#include "freertos/FreeRTOS.h"
#include "freertos/task.h"
#include "freertos/semphr.h"
#include "driver/ledc.h"
#include "esp_err.h"

#define LEDC_LS_TIMER          LEDC_TIMER_0
#define LEDC_LS_MODE           LEDC_LOW_SPEED_MODE
#define LEDC_LS_CH0_GPIO       (21)
#define LEDC_LS_CH0_CHANNEL    LEDC_CHANNEL_0
#define LEDC_LS_CH1_GPIO       (22)
#define LEDC_LS_CH1_CHANNEL    LEDC_CHANNEL_1
#define LEDC_LS_CH2_GPIO       (23)
#define LEDC_LS_CH2_CHANNEL    LEDC_CHANNEL_2
#define LEDC_TEST_CH_NUM       (3)
#define LEDC_TEST_FADE_TIME    (250)
#define INTR_FLAG_IRAM         ESP_INTR_FLAG_IRAM
#define INTR_FLAG_LOWMED       ESP_INTR_FLAG_LOWMED
#define INTR_FLAG_SHARED       ESP_INTR_FLAG_SHARED

void app_main(void)
{
    int ch;
    /*
     * Prepare and set configuration of timers
     * that will be used by LED Controller
     */
    ledc_timer_config_t ledc_timer = {
        .duty_resolution = LEDC_TIMER_8_BIT, // resolution of PWM duty
        .freq_hz = 5000,                     // frequency of PWM signal
        .speed_mode = LEDC_LS_MODE,          // timer mode
        .timer_num = LEDC_LS_TIMER,          // timer index
        .clk_cfg = LEDC_AUTO_CLK,            // Auto select the source clock
    };
    ledc_timer_config(&ledc_timer);
    /*
     * Prepare individual configuration for each
     * channel of LED Controller by selecting:
     * - controller's channel number
     * - output duty cycle, set initially to 0
     * - GPIO number where LED is connected to
     * - speed mode, either high or low
     * - timer servicing selected channel
     */
    ledc_channel_config_t ledc_channel[LEDC_TEST_CH_NUM] = {
        {
            .channel    = LEDC_LS_CH0_CHANNEL,
            .duty       = 0,
            .gpio_num   = LEDC_LS_CH0_GPIO,
            .speed_mode = LEDC_LS_MODE,
            .hpoint     = 0,
            .timer_sel  = LEDC_LS_TIMER,
            .flags.output_invert = 0
        },
        {
            .channel    = LEDC_LS_CH1_CHANNEL,
            .duty       = 0,
            .gpio_num   = LEDC_LS_CH1_GPIO,
            .speed_mode = LEDC_LS_MODE,
            .hpoint     = 0,
            .timer_sel  = LEDC_LS_TIMER,
            .flags.output_invert = 0
        },
        {
            .channel    = LEDC_LS_CH2_CHANNEL,
            .duty       = 0,
            .gpio_num   = LEDC_LS_CH2_GPIO,
            .speed_mode = LEDC_LS_MODE,
            .hpoint     = 0,
            .timer_sel  = LEDC_LS_TIMER,
            .flags.output_invert = 0
        },
    };

    // Set LED Controller with previously prepared configuration
    for (ch = 0; ch < LEDC_TEST_CH_NUM; ch++) {
        ledc_channel_config(&ledc_channel[ch]);
    }

    // Initialize fade service.
    ledc_fade_func_install(INTR_FLAG_IRAM | INTR_FLAG_LOWMED | INTR_FLAG_SHARED);

    int target_duty[][3] = {{0, 255, 255}, {255, 0, 255}, {255, 255, 0}}; // this doesn't work
    // int target_duty[][3] = {{255, 0, 0}, {0, 255, 0}, {0, 0, 255}};         //    this Works

    while (1) {
        // SetColor(target_duty);
        for(int i=0; i<3; i++){
            ledc_set_fade_with_time(LEDC_LS_MODE, LEDC_LS_CH0_CHANNEL, target_duty[i][0], 250);
            ledc_set_fade_with_time(LEDC_LS_MODE, LEDC_LS_CH1_CHANNEL, target_duty[i][1], 250);
            ledc_set_fade_with_time(LEDC_LS_MODE, LEDC_LS_CH2_CHANNEL, target_duty[i][2], 250);

            // Call fade actions
            ledc_fade_start(LEDC_LS_MODE, LEDC_LS_CH0_CHANNEL, LEDC_FADE_NO_WAIT);
            ledc_fade_start(LEDC_LS_MODE, LEDC_LS_CH1_CHANNEL, LEDC_FADE_NO_WAIT);
            ledc_fade_start(LEDC_LS_MODE, LEDC_LS_CH2_CHANNEL, LEDC_FADE_NO_WAIT);

            // Wait for fade to end
            vTaskDelay(pdMS_TO_TICKS(250));
        }
    }
}

Debug Logs.
No response
More Information.
No response

Hi @shreyuk23, we recently fixed a related bug on master (821f7b04988d0721ff7dbb64af43d165e3124718),  the backports to the release versions are still on the way.

Thanks, @songruo that fixed my problem. Will this issue be fixed in the v5.2 ?

@shreyuk23 No, v5.2-dev is only a tag. We will publish release/v5.2 branch in the near future, the fix will be included there.

@songruo
but we definitely would need a 5.1.3 , before 5.2  :)

@r3na I don't control the release schedule, either one of them will come first ;) Both will have the fix.

@songruo is there a fix for this in 5.1.2 ? I tried applying ledc.c and .h  but am then gettign errors with other functions being undefined.

@ZweiEuro The fix won't be in 5.1.2. You can wait for 5.1.3. Or you could cherry-pick 0329996 to your local branch.


[bug]: combobox search do not work with cmdk 1.0.0

Describe the bug
combobox search do not work with cmdk 1.0.0
Affected component/components
ComboBox
How to reproduce
search in combox
Codesandbox/StackBlitz link
No response
Logs
No response
System Info
chrome

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

I can't reproduce it locally - could you provide a sandbox?

Potential duplicates of https://github.com/shadcn-ui/ui/issues/2944.


KOGITO-7484: Knative CLI Workflow Plugin II

Goal
Expand Knative developer experience, allowing users to create, run and deploy single file workflows, hiding all Java and Quarkus complexity.
A considerable chunk of those changes incorporate Luiz Motta (@ljmotta ) contributions for
https://github.com/kiegroup/kie-tools/pull/1263
On this PR
The single-file serverless workflow folder structure is the following:

file.swf.json | file.swf.yaml
specs/.json
specs/.yaml
application.properties

How to test it?
Binaries
Single-file serverless workflow  commands overview
create
It creates a new single-file project. The project contains a "Hello World" workflow.sw.json file.

cli-binary create

run
It runs a single-file project. Behind the scenes uses quay.io/kiegroup/kogito-swf-devmode-nightly:latest

cli-binary run

DEV UI IS NOT ENABLE YET on the image. It will be soon added to the image
convert single file project to quarkus

cli-binary quarkus convert

Quarkus-based project commands overview
Moved the previous build, created and deploy commands to the quarkus subcommand.

cli-binary build -> cli-binary quarkus build
cli-binary create -> cli-binary quarkus create
cli-binary deploy -> cli-binary quarkus deploy

New Quarkus run command
Run quarkus dev mode

cli-binary run

What is pending, and will it come on the next PRs?

[TP1] single file deploy command, using the operator to deploy the project in dev mode
[TP1] KogitoImage = "quay.io/kiegroup/kogito-swf-devmode-nightly:latest" should use a fixed build/tag here instead of nightly/latest?
[TP1] Clean up jiras
[TP1] Test integration with kncli
[TP1] Run more complex/complet single file projects
[TP1] Upgrade docs (it will be done after freeze of TP1)
[TP1+] VS Code and Intellij Runner
[TP1+] Configure name of the CLI (for community and product)
[TP1+] Live reload on operator
[TP1+] Golang version upgrade

@zdrapela @caponetto PR updated! Thanks for the review!


[cudapoa] Multi-batch binning

Added a new function in cudapoa/utils.hpp where groups input windows based on their sizes in different batch-size bins. Windows with similar range of size are grouped together and launched with the same batch-size.
This multi-batch strategy can have a significant impact on scenarios where variance of window size is pretty high. If all windows have a similar size, multi-batch strategy will transform into a single batch launch.
Additionally:

added an example of using multi-batch binning API in sample_cudapoa, to find a small set of batches to cover all windows while maintaining high GPU occupancy
changed default band-width from 128 to 256
slightly changed generate_random_sequence() in genmoeutils.hpp to make it more robust

@tijyojwad the previous PR #427 was way out of date and merging new changes caused problems, moved the changes to this new one.

rerun tests

rerun tests


Add method setAcls

<?php
$zc = new \ZookeeperClient();
$zc->connect('localhost:2181');

<?php
$acls = array (
        array(
                'perms' => \ZookeeperClient::PERM_READ,
                'scheme' => 'world',
                'id' => 'anyone',
            ),
        array(
                'perms' => \ZookeeperClient::PERM_ALL,
                'scheme' => 'digest',
                'id' => 'user0:' . base64_encode(sha1('password0', true)),
            ),
        array(
                'perms' => \ZookeeperClient::PERM_CREATE & \ZookeeperClient::PERM_DELETE,
                'scheme' => 'digest',
                'id' => 'user1:' . base64_encode(sha1('password1', true)),
            ),
    );
$zc->setAcls('/zookeeper/node0', $acls);

<?php
$zc = new \ZookeeperClient();
$zc->connect('localhost:2181');

$acls = array (
    'world:anyone' => \ZookeeperClient::PERM_READ,
    'digest:user0:4LVnEr8VX5VVtn/KiU6Aff8jqh8=' => \ZookeeperClient::PERM_ALL,
    'digest:user1:4LVnEr8VX5VVtn/KiU6Aff8jqh8=' => \ZookeeperClient::PERM_CREATE & \ZookeeperClient::PERM_DELETE,
    );
$zc->setAcls('/zookeeper/node0', $acls);


Adding main model + adding input in direction getters

Hello @EmmaRenauld! Thanks for opening this PR.

In the file dwi_ml/model/main_models.py:

Line 39:80: E501 line too long (80 > 79 characters)

Do see the PEP 8 -- Style Guide for Python Code


time can be a number

Simple PR so that when time values that are numbers aren't ignored.

Closed for no activity, feel free to reopen if you are still interested.


Create CONTRIBUTING.md

Coverage remained the same at 100.0% when pulling 87452193ee71688d955db107a3c701a0087df48d on AndreaGot:master into 85e09462647de0c10e4fda4ce814708cd9247a8b on alexjoverm:master.

Hi @AndreaGot! Thanks for the effort and the PR!
I must say is not exactly as I had in mind. I see it a bit too generic, I wanted something more specific. Let's say something like:
We're really glad you're reading this, because we need volunteer developers to help this project come to fruition. 👏

## Instructions

These steps will guide you through contributing to this project:

 - Fork the repo
 - Clone it and install dependencies

```bash
git clone https://github.com/YOUR-USERNAME/typescript-library-starter
npm install

Keep in mind that after running npm install the git repo is reset. So a good way to cope with this is to have a copy of the folder to push the changes, and the other to try them.
Make and commit your changes. Make sure the commands npm run build and npm run test:prod are working.
Finally send a GitHub Pull Request with a clear list of what you've done (read more about pull requests). Make sure all of your commits are atomic (one feature per commit).

Is that ok for you? Any improvement over this is more than welcome!

Which points do you want me to cover? I suppose you want something more than the one you wrote :D
I'll be on a business trip during next week, so I won't be able to fulfill this task shortly, I'm afraid..

Not at all. Basically if you copy/paste what I wrote up there, that'd be good enough ;)
Just wanted to make it easy for you, since writing a contributing.md file is very specific in each repo.

The code of conduct I'd prefer it in a separate file, but that should be part of a different PR, not this one.

Coverage remained the same at 100.0% when pulling 04829c5f415f15ee9ba34a758afccea179e13a39 on AndreaGot:master into 85e09462647de0c10e4fda4ce814708cd9247a8b on alexjoverm:master.

There we go! Thanks!


record: set MTX_SEGMENT_DURATION in runOnRecordSegmentComplete

Provide MTX_SEGMENT_DURATION to the external command in the runOnRecordSegmentComplete hook. The duration of individual segments is useful when creating an HLS playlist.
Issue #2983

mediamtx.yml
pathDefaults:
  runOnRecordSegmentCreate: echo "path '$MTX_SEGMENT_PATH' duration '$MTX_SEGMENT_DURATION'"
  runOnRecordSegmentComplete: echo "$MTX_SEGMENT_PATH $MTX_SEGMENT_DURATION"

output
2024/06/09 17:50:37 INF [path skycam] runOnRecordSegmentCreate command launched
path './recordings/skycam/2024-06-09_17-50-36-294055.mp4' duration ''

2024/06/09 17:50:48 INF [path skycam] runOnRecordSegmentComplete command launched
path './recordings/skycam/2024-06-09_17-50-36-294055.mp4' duration '10'

The duration is also useful for monitoring
mediamtx.yml
pathDefaults:
  runOnRecordSegmentComplete: sh notify.sh "$MTX_SEGMENT_PATH" "$MTX_SEGMENT_DURATION"

notify.sh
#!/bin/bash

PATH=$1
DURATION=$2

if [ -z "$DURATION" ]; then
  echo "ERROR $PATH duration is blank"
  exit 2
elif [ $(echo "$DURATION < 10.0" | /usr/bin/bc) -ne 0 ]; then
  echo "WARNING $PATH duration is < 10.0"
  exit 1
fi

echo "SUCCESS $PATH duration is >= 10.0"
exit 0

output
2024/06/09 18:45:53 INF [path skycam] runOnRecordSegmentComplete command launched
WARNING ./recordings/skycam/2024-06-09_18-45-51-084911.mp4 duration is < 10.0

Hello, while the idea is good, this is implemented in a wrong way since MTX_SEGMENT_DURATION doesn't contain the real segment duration, but the maximum segment duration defined in the configuration.

replaced by #2456

Thank you!


Microsoft.AspNetCore.MiddlewareAnalysis not available from nuget

Dear,
Few days ago all packages around Microsoft.AspNetCore.* has been updated from 2.0.0-preview2 to 2.0.0 stable release.
But when we try to update the package Microsoft.AspNetCore.All to latest stable version it fails because the package Microsoft.AspNetCore.MiddlewareAnalysis 2.0.0 is not available on nuget repository.
Investigating a bit more on NuGet website there is a warning message saying "This package has not been indexed yet".
Unfortunately some other our libraries has been updated to Microsoft.AspNetCore.* 2.0.0 successfully because uses few some other Microsoft.AspNetCore.* that do not have a dependency with Microsoft.AspNetCore.MiddlewareAnalysis, so is too late to revert back everything.
Do you have plan to resolve this issue?

+1 on this issue, looks like this package was uploaded yesterday but some glitch prevents it being indexed meanwhile the other 2.0 packages are ready, but this one broken dependency is breaking the whole stack

the package has been indexed now, hope the new sdk is released soon

A member of the NuGet team manually resolved this for us. Closing as a duplicate of https://github.com/NuGet/NuGetGallery/issues/3991.


os: TestDevNullFile failing on Plan 9

CL 102457 added TestDevNullFile. This test is failing on Plan 9.
--- FAIL: TestDevNullFile (0.00s)
	os_test.go:1813: f.Stat("/dev/null"): wrong file mode "Drw-rw-rw-": ModeCharDevice is not set
	os_test.go:1813: Stat("/dev/null"): wrong file mode "Drw-rw-rw-": ModeCharDevice is not set
	os_test.go:1813: Lstat("/dev/null"): wrong file mode "Drw-rw-rw-": ModeCharDevice is not set
FAIL
FAIL	os	1.586s

See https://build.golang.org/log/add543f3681f4c7f89e62c0d40c8eebfafd71b72

Sorry for breaking the build. I looked at plan9-386 log
https://build.golang.org/log/ce0f0c918a1dc458c6f5913e1259f80f53f0f34d
and I did not see TestDevNullFile failure, so I assumed plan9 is OK. I will send a CL to adjust TestDevNullFile.
Alex

Don't worry, I'll send a CL.

I also need to fix Solaris.
Alex

For Plan 9 specifically, I think we can change Stat to set ModeCharDevice on files served by the console device, like we did for ModeDevice. I'll propose a CL that does that.
I'll let you change the TestDevNullFile test for Solaris.

I propose CL 102424, but if that's not a good solution we'll just skip the ModeCharDevice test for Plan 9 in TestDevNullFile.

but if that's not a good solution we'll just skip the ModeCharDevice test for Plan 9 in TestDevNullFile.

Sounds like a plan.
I would just remove ModeCharDevice test in TestDevNullFile altogether. I have added ModeCharDevice test in CL 102456, because windows code had ModeCharDevice set for DevNull. I don't even know if that is intended. But if you think ModeCharDevice makes sense for DevNull, I am happy for you to change plan9 code.
Alex


Update qsim 0.16.1

and fixed the unintialized cuquantum_root in cuquantum configure bzl rule.

@Sinestro38


useQuery & undefined data

Data can come out console.log, but the page rendering doesn't come out...
Uncaught TypeError: Cannot read property 'data' of undefined
Json
{
  "current_page": 1,
  "data": [
    {
      "id": 44,
      "username": "mydreamsofseaxxxms",
      "firstname": "",
    },
  ]
   "prev_page_url": null,
  "to": 3,
  "total": 3
}

axios utils/http file
import qs from "qs";
import axios, { AxiosRequestConfig } from "axios";

interface Config extends AxiosRequestConfig {
    data?: object;
}
export const http = async (
    endpoint: string,
    { data, ...customConfig }: Config = {}
) => {
    const config = {
        method: "GET",
        ...customConfig,
    };

    if (config.method.toUpperCase() === "GET") {
        endpoint += `${qs.stringify(data)}`;
    }
    // @ts-ignore
    return axios(`${endpoint}`, config).then(async (res) => {
        const data = await res.data;
        if (res.status >= 200) {
            return data;
        }
    });
};

react-query ｜ utils/influencer file
import { useQuery } from "react-query";
import { http } from "../utils/http";

export const useInfluencer = (param?: any) => {
    return useQuery(["influencers", param], () =>
        http("/api/influencers?", { data: param })
    );
};

render
import React, { useState, useEffect, Fragment, useCallback } from "react";
import { useInfluencer } from "../../utils/influencer";

const Home = () => {
    const { isLoading, error, data: list } = useInfluencer();
    return (

                **error: Uncaught TypeError: Cannot read property 'data' of undefined**

                {(list.data || []).map(({ username }) => (

{username}

                ))}

                {list.data.map(({ username }) => (

{username}

                ))}

    );
};

export default Home;

Looking forward to your solution. Thank you

The data (list) is going to be undefined on the first render while isLoading is true. That's why you get "undefined".
You're trying to access the data property on the list object while it's undefined.
Do something like below before your return statement where you map through your list on the data property:
if (isLoading) return
Loading ...
;
if (error) return
Something went wrong ...
;

This will show a loading state while the data is fetched (and the list is undefined).


Correction for #asWord lemmas

This PR adds the necessary requires clauses to ML-level simplifications for #asWord, which prevent infinite looping observed in the Kontrol test suite.

I tried, but wasn't able to create one in KEVM. The test that does the looping in Kontrol is TGovernance.getEscrowTokenTotalSupply.


Why are the preprocessing layers deepcopied?

I'd like to keep track of the random augmentation parameters applied to each single sample. Every time the reader is called, the preprocessors are deepcopied, therefore the information I want is not stored.
Why are these layers deepcopied before being randomised?

It seems to work fine without the deepcopy operation.

Hi @fepegar because that function could be called from multiple threads simultaneously, deepcopy ensures the 'randomness'.

Thanks @wyli


[Fix-11633] The data type of the PostgreSQL database column is wrong

fix #11633

Purpose of the pull request
Fix data type error in PostgreSQL database

Codecov Report

Merging #11634 (c521292) into dev (cf3b442) will increase coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev   #11634      +/-   ##
============================================
+ Coverage     39.82%   39.84%   +0.01%
- Complexity     4707     4708       +1
============================================
  Files           996      996
  Lines         37760    37742      -18
  Branches       4208     4200       -8
============================================
- Hits          15039    15037       -2
+ Misses        21153    21139      -14
+ Partials       1568     1566       -2

Impacted Files
Coverage Δ

...rver/master/runner/task/BlockingTaskProcessor.java
75.86% <0.00%> (-0.55%)
:arrow_down:

...eduler/api/service/impl/DataSourceServiceImpl.java
27.90% <0.00%> (ø)

...cheduler/server/master/utils/DependentExecute.java
0.00% <0.00%> (ø)

.../dolphinscheduler/plugin/task/datax/DataxTask.java
0.00% <0.00%> (ø)

...phinscheduler/plugin/task/chunjun/ChunJunTask.java
0.00% <0.00%> (ø)

...cheduler/plugin/task/api/ShellCommandExecutor.java
0.00% <0.00%> (ø)

...nscheduler/service/process/ProcessServiceImpl.java
31.80% <0.00%> (+0.02%)
:arrow_up:

...server/master/runner/task/SwitchTaskProcessor.java
2.54% <0.00%> (+0.02%)
:arrow_up:

...ver/master/runner/task/ConditionTaskProcessor.java
4.81% <0.00%> (+0.05%)
:arrow_up:

...hinscheduler/plugin/alert/wechat/WeChatSender.java
29.78% <0.00%> (+0.20%)
:arrow_up:

... and 4 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@SbloodyS May I ask whether we need to change related db migration script?

I think we don't need it in this scenario.
BTW. I'm curious about why this problem can pass the postgre cluster test before...

I think we better find out why, and add more test or fix this test in CI ASAP

I think we better find out why, and add more test or fix this test in CI ASAP

I find in this column added PR #11350,  https://github.com/apache/dolphinscheduler/runs/7765487654?check_suite_focus=true, it failed with error log
+ docker exec -u root ds bash -c 'cat /root/apache-dolphinscheduler-*-SNAPSHOT-bin/master-server/logs/dolphinscheduler-master.log'
[5953](https://github.com/apache/dolphinscheduler/runs/7765487654?check_suite_focus=true#step:4:5954)
Error response from daemon: Container f4894135d6f017c07e1240c919108ecf980ff2bd2226901fc7e17d09cdc8ee00 is restarting, wait until the container is running
[5954](https://github.com/apache/dolphinscheduler/runs/7765487654?check_suite_focus=true#step:4:5955)
+ echo 'cluster start health check failed'
[5955](https://github.com/apache/dolphinscheduler/runs/7765487654?check_suite_focus=true#step:4:5956)
cluster start health check failed

but GA step still pass. Is this a expect behavior?

I think we better find out why, and add more tests or fix this test in CI ASAP

I find in this column added PR #11350, https://github.com/apache/dolphinscheduler/runs/7765487654?check_suite_focus=true, it failed with the error log
+ docker exec -u root ds bash -c 'cat /root/apache-dolphinscheduler-*-SNAPSHOT-bin/master-server/logs/dolphinscheduler-master.log'
[5953](https://github.com/apache/dolphinscheduler/runs/7765487654?check_suite_focus=true#step:4:5954)
Error response from daemon: Container f4894135d6f017c07e1240c919108ecf980ff2bd2226901fc7e17d09cdc8ee00 is restarting, wait until the container is running
[5954](https://github.com/apache/dolphinscheduler/runs/7765487654?check_suite_focus=true#step:4:5955)
+ echo 'cluster start health check failed'
[5955](https://github.com/apache/dolphinscheduler/runs/7765487654?check_suite_focus=true#step:4:5956)
cluster start health check failed

but GA step still passed. Is this an expected behavior?

This is abnormal. I'll fix it.


Add pacemaker-cts test scenario

Pacemaker-CTS thoroughly exercises a pacemaker cluster by running a randomized series of predefined tests on the cluster. We need to add this scenario to make sure that our cloud doesn't have problems with clusterization.

Fixed version was tested here, scenario works fine.

ping @aspiers I fixed my code according to your comments, Fixed version was tested here


Make closing dialog when clicking next to it optional

While in a lot of cases the behavior of closing a dropdown menu or a dialog when clicking next to it is desirable, in other cases, where you require a user to select something this behavior is not ideal.
I would like to propose adding a flag to the dialog component so this behavior can be disabled at will , like the IgnoreOutlet flag.

Ah great, maybe this should be mentioned in the docs :)

Unfortunately there is a lot which currently isn't mentioned in the docs, but yes I agree!


Add script to generate ticker (rocket replacement) files

I will try to fix codeclimate issues as they come up.

The intended use case here is that if you're using it for chat, you use it as such:

Create a companies.csv file with two columns for company name and ticker:

company name, ticker
corp one, ABC
corp two, DEV
three, GHI

Generate a company -> ticker mapping:

python util/generate_ticker_list.py companies.csv

and you get a file like this called companies.txt:
corp two -> DEV
corp one -> ABC
three -> GHI

Generate a ticker -> ticker mapping:

python util/generate_ticker_file.py companies.csv --tickers_only

and you'll get a file like this called companies_tickers.txt:
d e v -> DEV
a b c -> ABC
g h i -> GHI

If you wish to use both files for entity definitions, simply combine them.

cat companies_tickers.txt >> companies.txt


Benign essential blepharospasm

Label
Benign essential blepharospasm
Synonyms
Primary focal dystonia affecting the orbicularis oculi muscles
Synonym type
None
Definition
Benign essential blepharospasm is a condition characterized by abnormal blinking or spasms of the eyelids. Symptoms may begin as eye twitching and blinking and there may be symptoms of eye irritation. Eventually, BEB causes involuntary closure of the eyes. The exact cause of BEB is unknown. Susceptibility to benign essential blepharospasm may be associated with a microsatellite marker to the dopamine receptor DRD5 gene. The disorder is one of a group of disorders collectively known as adult-onset focal dystonia. Benign essential blepharospasm is different from the common, temporary eyelid twitching that can be caused by fatigue, stress, or caffeine. Treatment of BEB consists of oral drug therapy, focal injections of botulinum toxin (four different brands are available in the USA) or surgery to remove eyelid muscle.
Parent term
Focal dystonia
Children term(s)
No response
ORCID Identifier
0000-001-9310-0163
Website URL
https://medlineplus.gov/genetics/condition/benign-essential-blepharospasm/#causes
Additional comments
No response

This is also in GARD.  OMIM has a page on susceptibility to benign essential blepharospasm  https://omim.org/entry/606798
MONDO already list blepharospasm and links it to the OMIM page.

got it! Will do!


Execute me, anything update of the whole repository?  Lots of missing files in yours code such as prompt_spec_path which is one of the most important instruction prompts.

Hi, thanks for your interest in this repo! I just reorganized the whole thing. I will write up a readme tomorrow. Sorry for the delay and thanks for your patients. the prompts are already uploaded under prompts/ but I will provide the processed test dataset so that you don't need to construct it yourself.

Thank you for your patient answers, and thank you for your contributions to the community.


Disable the auto-updating of RULES_DOCKER so that container-definitio…

…ns is pinned to a version that works.

/gcbrun


Set both a light and a dark theme for code blocks

Fixes https://github.com/opentofu/opentofu.org/issues/304.
I arbitrarily chose vsLight; the list of available themes with the current dependencies is this, if anyone prefers something different:
dracula
duotoneDark
duotoneLight
github
jettwaveDark
jettwaveLight
nightOwl
nightOwlLight
oceanicNext
okaidia
oneDark
oneLight
palenight
shadesOfPurple
synthwave84
ultramin
vsDark
vsLight

@mehhhhhhhhhhhhhhh thanks for pointing this out! We should definitely mention it somewhere in this repo too.


How does the tensor become an array?

Can I manipulate variables like arrays, if not, how can I change the tensor into an array? After the operation, I am changing the array to a tensor.

for converting a tensor in Keras, use Keras backend function "eval()" --> K.eval(tensor)
Check documentation: https://keras.io/backend/


Specified service namespace is invalid.

Hello,
I am at the step where I have to create a template. I fill out the form and click on Create. I receive error messages and I am not sure how to fix them:
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":
[{"code":"ResourceDeploymentFailure","message":"Encountered internal server error. Diagnostic information: timestamp '20220517T183238Z', subscription id 'f7de535f-96c8-4c70-a710-e43a746e3277', tracking id '95a02f90-0268-4ccc-9699-49ad6b354e7e', request correlation id '1820d2e2-79f8-41b3-8b5b-84361f3a254f'."},{"code":"BadRequest","message":"The specified service namespace is invalid. CorrelationId: 1820d2e2-79f8-41b3-8b5b-84361f3a254f"}]}
Can you help me with this?
Thank you.

Hi @onlize,
Could you please try using a different base resource name in lower case and kindly let us know if you are able to deploy.

Using different base resource name and different GUID numbers for all those roles fixed my issue. Thank you.


.text(): create a function to get and set the text content

Implement a method that returns the text of the first element or it sets it. Similar to .html(), but instead of returning .innerHTML it returns textContent. Then document and test the method. To do this:

Clone the repository
Create the corresponding folder in src/plugins
Execute grunt watch in the terminal. Make sure you have phantomjs installed first.
Create the three files, text.js, documentation.md and test.js
In text.js add the code needed to execute it
Then (or before if you are into TDD) add the needed tests in test.js. After adding them all, open tests.html in your browser, which should show a passing/failing for your tests. Or check the terminal, since grunt should run tests now too.
Add the documentation.md needed to use it
Send a Pull Request and I'll provide feedback on the code

No npm install like in Contributing.md?

Yes, sorry forgot to add that


Dead links in documentation

Both of the links in the documentation section of your README appear to be down.
Could you update this so we can access to these resources. Thanks!
(I'm specifically interested in getting access to the C API documentation)

This has since been updated!


Add supervisor

Add supervision surrounding the critical processes.

Included with: https://github.com/fly-apps/cron-manager/pull/10


When editing milestone amount, form defaults to n/a and clears existing number if radio button clicked [4]

Describe the Bug:
Probability (how likely the bug is to happen, scored from 1-5): 2
(For example, probability of 5 is something like "it happens to all users every time they log in."
Probability of 1 "only happens to certain users when a really specific and unlikely path is followed.")
Effect (how bad the bug is when it does happen, scored from 1-5): 2
(For example, effect of 5 is "the entire app crashes and makes it unusable for all users" or "the bug causes the wrong data to be saved, with critical information (e.g. payment) being affected."
Effect of 1 is "It makes some styling look a little bit weird.")
Steps to reproduce the behaviour:
Edit a milestone report that has an amount entered. The radio button will default to not applicable:

And if you change it to "enter amount", the previously entered amount is cleared:

Screenshots:
see above
Additional information:

This is expected behaviour. If the value is not applicable it needs to be removed from the form_change data, otherwise it will be populated to the table data on commit..


⚠ Bofrost.de has degraded performance

In c428de3, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 2004 ms

Resolved: Bofrost.de performance has improved in f4abb88 after 6 minutes.


[SPARK-31487][CORE] Move slots check of barrier job from DAGScheduler to TaskSchedulerImpl

What changes were proposed in this pull request?

Move slots check of barrier job from DAGScheduler to TaskSchedulerImpl and add new configuration spark.scheduler.barrier.waitForEnoughSlots.timeout to replace with spark.scheduler.barrier.maxConcurrentTasksCheck.interval/ spark.scheduler.barrier.maxConcurrentTasksCheck.maxFailures.
Why are the changes needed?

We do the slots check for a barrier job to ensure the job can be launched finally. We'll continuously resubmit the same job until we pass the check(find enough slots after some executors registered at driver). Thus, it introduces duplicate DAG planning for the same job, which may low down the throughput of the DAGSchedule. And it seems DAG planning could always be faster than executor launching, which makes duplicate DAG planning inevitable. Besides, we actually already did the similar slots check inside TaskSchedulerImpl. We can combine them as well.
One obvious benefit we can get after this improvement is reducing the time of barrier tests, e.g.
Before:
[info] BarrierTaskContextSuite:
[info] - global sync by barrier() call (18 seconds, 972 milliseconds)
[info] - share messages with allGather() call (17 seconds, 95 milliseconds)
[info] - throw exception if we attempt to synchronize with different blocking calls (16 seconds, 222 milliseconds)
[info] - successively sync with allGather and barrier (17 seconds, 532 milliseconds)
[info] - support multiple barrier() call within a single task (17 seconds, 792 milliseconds)
[info] - throw exception on barrier() call timeout (17 seconds, 85 milliseconds)
[info] - throw exception if barrier() call doesn't happen on every task (17 seconds, 166 milliseconds)
[info] - throw exception if the number of barrier() calls are not the same on every task (17 seconds, 149 milliseconds)
[info] - barrier task killed, no interrupt (16 seconds, 777 milliseconds)
[info] - barrier task killed, interrupt (16 seconds, 208 milliseconds)
[info] ScalaTest
[info] Run completed in 2 minutes, 54 seconds.

After:
[info] BarrierTaskContextSuite:
[info] - global sync by barrier() call (6 seconds, 694 milliseconds)
[info] - share messages with allGather() call (5 seconds, 885 milliseconds)
[info] - throw exception if we attempt to synchronize with different blocking calls (5 seconds, 384 milliseconds)
[info] - successively sync with allGather and barrier (6 seconds, 973 milliseconds)
[info] - support multiple barrier() call within a single task (6 seconds, 979 milliseconds)
[info] - throw exception on barrier() call timeout (6 seconds, 158 milliseconds)
[info] - throw exception if barrier() call doesn't happen on every task (6 seconds, 211 milliseconds)
[info] - throw exception if the number of barrier() calls are not the same on every task (6 seconds, 171 milliseconds)
[info] - barrier task killed, no interrupt (4 seconds, 776 milliseconds)
[info] - barrier task killed, interrupt (5 seconds, 190 milliseconds)
[info] ScalaTest
[info] Run completed in 1 minute, 3 seconds.

Does this PR introduce any user-facing change?

Yes, user can not use spark.scheduler.barrier.maxConcurrentTasksCheck.interval/ spark.scheduler.barrier.maxConcurrentTasksCheck.maxFailures any more since Spark 3.0 but should use
spark.scheduler.barrier.waitForEnoughSlots.timeout instead.
How was this patch tested?

Updated existed tests.

Test build #121480 has started for PR 28260 at commit c704fa4.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/26164/
Test PASSed.

Test build #121480 has finished for PR 28260 at commit c704fa4.

This patch fails from timeout after a configured wait of 400m.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/121480/
Test FAILed.

retest this please.

Test build #121495 has started for PR 28260 at commit c704fa4.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/26179/
Test PASSed.

Test build #121495 has finished for PR 28260 at commit c704fa4.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/121495/
Test FAILed.

retest this please.

Test build #121519 has started for PR 28260 at commit c704fa4.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/26203/
Test PASSed.

Test build #121519 has finished for PR 28260 at commit c704fa4.

This patch fails from timeout after a configured wait of 400m.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/121519/
Test FAILed.

Test build #121589 has started for PR 28260 at commit 3b01c20.

Test build #121589 has finished for PR 28260 at commit 3b01c20.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test build #121601 has started for PR 28260 at commit 3b98b86.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/26281/
Test PASSed.

Test build #121601 has finished for PR 28260 at commit 3b98b86.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/121601/
Test FAILed.

Test build #121611 has started for PR 28260 at commit fdb7840.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/26291/
Test PASSed.

Test build #121611 has finished for PR 28260 at commit fdb7840.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/121611/
Test FAILed.

retest this please.

cc @jiangxb1987

Test build #121686 has started for PR 28260 at commit fdb7840.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/26365/
Test PASSed.

Test build #121686 has finished for PR 28260 at commit fdb7840.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/121686/
Test PASSed.

After discussing with xingbo offline, we think this change could introduce behaviour change, that is: previously, a upstream stage will never be executed if there's insufficient for the downstream barrier stage but the upstream stage now can be executed after this change, which obviously is bad. So I decide to close it for now. Thanks all, anyway!!