[KOGITO-9555] Adding generic endpoint

This defines a new addon that allows dynamic uploading of workflow files and its execution.
Process definitions are currently stored in memory. process persistence will be provided by a a different JIRA.

(tests) - kogito-apps job #2849 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
export BUILD_MVN_OPTS_CURRENT=
build-chain build cross_pr -f 'https://raw.githubusercontent.com/kiegroup/kogito-pipelines/main/.ci/pull-request-config.yaml' -o 'bc' -p kiegroup/kogito-apps -u https://github.com/kiegroup/kogito-runtimes/pull/3116 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.downstream.kogito-apps/2849/display/redirect
Test results:

PASSED: 2764
FAILED: 1

Those are the test failures:

Build projects / org.kie.kogito.it.jobs.MultipleTimerInstancesIT.boundaryTimerEvent
java.lang.IllegalStateException: Unable to determine the status of the running process. See the above logs for details

jenking run kogito-apps tests

jenkins run kogito-apps tests

(tests) - kogito-runtimes job #2860 was: FAILURE
Possible explanation: Pipeline failure or project build failure

Reproducer
export BUILD_MVN_OPTS_CURRENT=-T 1C -Dvalidate-formatting -Prun-code-coverage
build-chain build cross_pr -f 'https://raw.githubusercontent.com/kiegroup/kogito-pipelines/main/.ci/pull-request-config.yaml' -o 'bc' -p kiegroup/kogito-runtimes -u https://github.com/kiegroup/kogito-runtimes/pull/3116 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.kogito-runtimes/2860/display/redirect
Test results:

PASSED: 3309
FAILED: 0

Those are the test failures: none
See console log:

Console Logs
[2023-07-12T07:58:03.402Z] [INFO] Kogito :: Add-Ons :: Persistence MongoDB :: Springboot SUCCESS [  2.696 s][2023-07-12T07:58:03.402Z] [INFO] Kogito :: Add-Ons :: Persistence PostgreSQL :: Springboot SUCCESS [  5.480 s][2023-07-12T07:58:03.402Z] [INFO] Kogito :: Spring Boot :: Maven Archetype ........... SUCCESS [02:40 min][2023-07-12T07:58:03.402Z] [INFO] Kogito :: Test Utilities :: Spring Boot ............ SUCCESS [ 34.897 s][2023-07-12T07:58:03.402Z] [INFO] Kogito :: Integration Tests :: Spring Boot ......... SUCCESS [04:18 min][2023-07-12T07:58:03.402Z] [INFO] ------------------------------------------------------------------------[2023-07-12T07:58:03.402Z] [INFO] BUILD FAILURE[2023-07-12T07:58:03.402Z] [INFO] ------------------------------------------------------------------------[2023-07-12T07:58:03.402Z] [INFO] Total time:  17:00 min (Wall Clock)[2023-07-12T07:58:03.402Z] [INFO] Finished at: 2023-07-12T03:58:01-04:00[2023-07-12T07:58:03.402Z] [INFO] ------------------------------------------------------------------------[2023-07-12T07:58:03.402Z] [ERROR] Failed to execute goal io.quarkus:quarkus-maven-plugin:2.16.7.Final:build (default) on project integration-tests-quarkus-processes: Failed to build quarkus application: io.quarkus.builder.BuildException: Build failure: Build failed due to errors[2023-07-12T07:58:03.402Z] [ERROR] 	[error]: Build step org.kie.kogito.quarkus.common.deployment.KogitoAssetsProcessor#generateSources threw an exception: java.util.NoSuchElementException: No value present[2023-07-12T07:58:03.402Z] [ERROR] 	at java.base/java.util.Optional.get(Optional.java:148)[2023-07-12T07:58:03.402Z] [ERROR] 	at org.kie.kogito.codegen.api.context.KogitoBuildContext.lambda$getPropertiesMap$2(KogitoBuildContext.java:173)[2023-07-12T07:58:03.402Z] [ERROR] 	at java.base/java.util.stream.Collectors.lambda$uniqKeysMapAccumulator$1(Collectors.java:178)[2023-07-12T07:58:03.402Z] [ERROR] 	at java.base/java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)[2023-07-12T07:58:03.402Z] [ERROR] 	at java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177)[2023-07-12T07:58:03.402Z] [ERROR] 	at java.base/java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1621)[2023-07-12T07:58:03.402Z] [ERROR] 	at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)[2023-07-12T07:58:03.402Z] [ERROR] 	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)[2023-07-12T07:58:03.402Z] [ERROR] 	at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)[2023-07-12T07:58:03.402Z] [ERROR] 	at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)[2023-07-12T07:58:03.402Z] [ERROR] 	at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)[2023-07-12T07:58:03.402Z] [ERROR] 	at org.kie.kogito.codegen.api.context.KogitoBuildContext.getPropertiesMap(KogitoBuildContext.java:172)[2023-07-12T07:58:03.402Z] [ERROR] 	at org.kie.kogito.codegen.process.ProcessCodegen.internalGenerate(ProcessCodegen.java:494)[2023-07-12T07:58:03.402Z] [ERROR] 	at org.kie.kogito.codegen.core.AbstractGenerator.generate(AbstractGenerator.java:69)[2023-07-12T07:58:03.402Z] [ERROR] 	at org.kie.kogito.codegen.core.ApplicationGenerator.lambda$generateComponents$0(ApplicationGenerator.java:95)[2023-07-12T07:58:03.402Z] [ERROR] 	at java.base/java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:271)[2023-07-12T07:58:03.402Z] [ERROR] 	at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655)[2023-07-12T07:58:03.402Z] [ERROR] 	at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)[2023-07-12T07:58:03.402Z] [ERROR] 	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)[2023-07-12T07:58:03.402Z] [ERROR] 	at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)[2023-07-12T07:58:03.402Z] [ERROR] 	at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)[2023-07-12T07:58:03.402Z] [ERROR] 	at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)[2023-07-12T07:58:03.402Z] [ERROR] 	at org.kie.kogito.codegen.core.ApplicationGenerator.generateComponents(ApplicationGenerator.java:97)[2023-07-12T07:58:03.402Z] [ERROR] 	at org.kie.kogito.codegen.core.ApplicationGenerator.generate(ApplicationGenerator.java:74)[2023-07-12T07:58:03.402Z] [ERROR] 	at org.kie.kogito.quarkus.common.deployment.KogitoAssetsProcessor.generateFiles(KogitoAssetsProcessor.java:260)[2023-07-12T07:58:03.402Z] [ERROR] 	at org.kie.kogito.quarkus.common.deployment.KogitoAssetsProcessor.generateSources(KogitoAssetsProcessor.java:137)[2023-07-12T07:58:03.402Z] [ERROR] 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[2023-07-12T07:58:03.402Z] [ERROR] 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[2023-07-12T07:58:03.402Z] [ERROR] 	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[2023-07-12T07:58:03.402Z] [ERROR] 	at java.base/java.lang.reflect.Method.invoke(Method.java:566)[2023-07-12T07:58:03.402Z] [ERROR] 	at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:909)[2023-07-12T07:58:03.402Z] [ERROR] 	at io.quarkus.builder.BuildContext.run(BuildContext.java:281)[2023-07-12T07:58:03.402Z] [ERROR] 	at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)[2023-07-12T07:58:03.402Z] [ERROR] 	at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2449)[2023-07-12T07:58:03.402Z] [ERROR] 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1478)[2023-07-12T07:58:03.402Z] [ERROR] 	at java.base/java.lang.Thread.run(Thread.java:829)[2023-07-12T07:58:03.402Z] [ERROR] 	at org.jboss.threads.JBossThread.run(JBossThread.java:501)[2023-07-12T07:58:03.402Z] [ERROR] -> [Help 1][2023-07-12T07:58:03.402Z] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal io.quarkus:quarkus-maven-plugin:2.16.7.Final:build (default) on project integration-tests-quarkus-processes: Failed to build quarkus application[2023-07-12T07:58:03.402Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:375)[2023-07-12T07:58:03.402Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:351)[2023-07-12T07:58:03.402Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)[2023-07-12T07:58:03.402Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:171)[2023-07-12T07:58:03.402Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:163)[2023-07-12T07:58:03.402Z]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)[2023-07-12T07:58:03.402Z]     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:210)[2023-07-12T07:58:03.402Z]     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:195)[2023-07-12T07:58:03.402Z]     at java.util.concurrent.FutureTask.run (FutureTask.java:264)[2023-07-12T07:58:03.402Z]     at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)[2023-07-12T07:58:03.402Z]     at java.util.concurrent.FutureTask.run (FutureTask.java:264)[2023-07-12T07:58:03.402Z]     at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1128)[2023-07-12T07:58:03.402Z]     at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:628)[2023-07-12T07:58:03.402Z]     at java.lang.Thread.run (Thread.java:829)[2023-07-12T07:58:03.402Z] Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to build quarkus application[2023-07-12T07:58:03.402Z]     at io.quarkus.maven.BuildMojo.doExecute (BuildMojo.java:170)[2023-07-12T07:58:03.402Z]     at io.quarkus.maven.QuarkusBootstrapMojo.execute (QuarkusBootstrapMojo.java:154)[2023-07-12T07:58:03.402Z]     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)[2023-07-12T07:58:03.402Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:370)[2023-07-12T07:58:03.402Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:351)[2023-07-12T07:58:03.402Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)[2023-07-12T07:58:03.403Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:171)[2023-07-12T07:58:03.403Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:163)[2023-07-12T07:58:03.403Z]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)[2023-07-12T07:58:03.403Z]     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:210)[2023-07-12T07:58:03.403Z]     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:195)[2023-07-12T07:58:03.403Z]     at java.util.concurrent.FutureTask.run (FutureTask.java:264)[2023-07-12T07:58:03.403Z]     at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)[2023-07-12T07:58:03.403Z]     at java.util.concurrent.FutureTask.run (FutureTask.java:264)[2023-07-12T07:58:03.403Z]     at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1128)[2023-07-12T07:58:03.403Z]     at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:628)[2023-07-12T07:58:03.403Z]     at java.lang.Thread.run (Thread.java:829)[2023-07-12T07:58:03.403Z] Caused by: java.lang.RuntimeException: io.quarkus.builder.BuildException: Build failure: Build failed due to errors[2023-07-12T07:58:03.403Z] 	[error]: Build step org.kie.kogito.quarkus.common.deployment.KogitoAssetsProcessor#generateSources threw an exception: java.util.NoSuchElementException: No value present[2023-07-12T07:58:03.403Z] 	at java.base/java.util.Optional.get(Optional.java:148)[2023-07-12T07:58:03.403Z] 	at org.kie.kogito.codegen.api.context.KogitoBuildContext.lambda$getPropertiesMap$2(KogitoBuildContext.java:173)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.Collectors.lambda$uniqKeysMapAccumulator$1(Collectors.java:178)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1621)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)[2023-07-12T07:58:03.403Z] 	at org.kie.kogito.codegen.api.context.KogitoBuildContext.getPropertiesMap(KogitoBuildContext.java:172)[2023-07-12T07:58:03.403Z] 	at org.kie.kogito.codegen.process.ProcessCodegen.internalGenerate(ProcessCodegen.java:494)[2023-07-12T07:58:03.403Z] 	at org.kie.kogito.codegen.core.AbstractGenerator.generate(AbstractGenerator.java:69)[2023-07-12T07:58:03.403Z] 	at org.kie.kogito.codegen.core.ApplicationGenerator.lambda$generateComponents$0(ApplicationGenerator.java:95)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:271)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)[2023-07-12T07:58:03.403Z] 	at org.kie.kogito.codegen.core.ApplicationGenerator.generateComponents(ApplicationGenerator.java:97)[2023-07-12T07:58:03.403Z] 	at org.kie.kogito.codegen.core.ApplicationGenerator.generate(ApplicationGenerator.java:74)[2023-07-12T07:58:03.403Z] 	at org.kie.kogito.quarkus.common.deployment.KogitoAssetsProcessor.generateFiles(KogitoAssetsProcessor.java:260)[2023-07-12T07:58:03.403Z] 	at org.kie.kogito.quarkus.common.deployment.KogitoAssetsProcessor.generateSources(KogitoAssetsProcessor.java:137)[2023-07-12T07:58:03.403Z] 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[2023-07-12T07:58:03.403Z] 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[2023-07-12T07:58:03.403Z] 	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[2023-07-12T07:58:03.403Z] 	at java.base/java.lang.reflect.Method.invoke(Method.java:566)[2023-07-12T07:58:03.403Z] 	at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:909)[2023-07-12T07:58:03.403Z] 	at io.quarkus.builder.BuildContext.run(BuildContext.java:281)[2023-07-12T07:58:03.403Z] 	at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)[2023-07-12T07:58:03.403Z] 	at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2449)[2023-07-12T07:58:03.403Z] 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1478)[2023-07-12T07:58:03.403Z] 	at java.base/java.lang.Thread.run(Thread.java:829)[2023-07-12T07:58:03.403Z] 	at org.jboss.threads.JBossThread.run(JBossThread.java:501)[2023-07-12T07:58:03.403Z] [2023-07-12T07:58:03.403Z]     at io.quarkus.runner.bootstrap.AugmentActionImpl.runAugment (AugmentActionImpl.java:335)[2023-07-12T07:58:03.403Z]     at io.quarkus.runner.bootstrap.AugmentActionImpl.createProductionApplication (AugmentActionImpl.java:175)[2023-07-12T07:58:03.403Z]     at io.quarkus.maven.BuildMojo.doExecute (BuildMojo.java:133)[2023-07-12T07:58:03.403Z]     at io.quarkus.maven.QuarkusBootstrapMojo.execute (QuarkusBootstrapMojo.java:154)[2023-07-12T07:58:03.403Z]     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)[2023-07-12T07:58:03.403Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:370)[2023-07-12T07:58:03.403Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:351)[2023-07-12T07:58:03.403Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)[2023-07-12T07:58:03.403Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:171)[2023-07-12T07:58:03.403Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:163)[2023-07-12T07:58:03.403Z]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)[2023-07-12T07:58:03.403Z]     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:210)[2023-07-12T07:58:03.403Z]     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:195)[2023-07-12T07:58:03.403Z]     at java.util.concurrent.FutureTask.run (FutureTask.java:264)[2023-07-12T07:58:03.403Z]     at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)[2023-07-12T07:58:03.403Z]     at java.util.concurrent.FutureTask.run (FutureTask.java:264)[2023-07-12T07:58:03.403Z]     at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1128)[2023-07-12T07:58:03.403Z]     at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:628)[2023-07-12T07:58:03.403Z]     at java.lang.Thread.run (Thread.java:829)[2023-07-12T07:58:03.403Z] Caused by: io.quarkus.builder.BuildException: Build failure: Build failed due to errors[2023-07-12T07:58:03.403Z] 	[error]: Build step org.kie.kogito.quarkus.common.deployment.KogitoAssetsProcessor#generateSources threw an exception: java.util.NoSuchElementException: No value present[2023-07-12T07:58:03.403Z] 	at java.base/java.util.Optional.get(Optional.java:148)[2023-07-12T07:58:03.403Z] 	at org.kie.kogito.codegen.api.context.KogitoBuildContext.lambda$getPropertiesMap$2(KogitoBuildContext.java:173)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.Collectors.lambda$uniqKeysMapAccumulator$1(Collectors.java:178)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1621)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)[2023-07-12T07:58:03.403Z] 	at org.kie.kogito.codegen.api.context.KogitoBuildContext.getPropertiesMap(KogitoBuildContext.java:172)[2023-07-12T07:58:03.403Z] 	at org.kie.kogito.codegen.process.ProcessCodegen.internalGenerate(ProcessCodegen.java:494)[2023-07-12T07:58:03.403Z] 	at org.kie.kogito.codegen.core.AbstractGenerator.generate(AbstractGenerator.java:69)[2023-07-12T07:58:03.403Z] 	at org.kie.kogito.codegen.core.ApplicationGenerator.lambda$generateComponents$0(ApplicationGenerator.java:95)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:271)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)[2023-07-12T07:58:03.403Z] 	at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)[2023-07-12T07:58:03.403Z] 	at org.kie.kogito.codegen.core.ApplicationGenerator.generateComponents(ApplicationGenerator.java:97)[2023-07-12T07:58:03.403Z] 	at org.kie.kogito.codegen.core.ApplicationGenerator.generate(ApplicationGenerator.java:74)[2023-07-12T07:58:03.403Z] 	at org.kie.kogito.quarkus.common.deployment.KogitoAssetsProcessor.generateFiles(KogitoAssetsProcessor.java:260)[2023-07-12T07:58:03.403Z] 	at org.kie.kogito.quarkus.common.deployment.KogitoAssetsProcessor.generateSources(KogitoAssetsProcessor.java:137)[2023-07-12T07:58:03.403Z] 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[2023-07-12T07:58:03.403Z] 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[2023-07-12T07:58:03.403Z] 	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[2023-07-12T07:58:03.403Z] 	at java.base/java.lang.reflect.Method.invoke(Method.java:566)[2023-07-12T07:58:03.403Z] 	at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:909)[2023-07-12T07:58:03.403Z] 	at io.quarkus.builder.BuildContext.run(BuildContext.java:281)[2023-07-12T07:58:03.403Z] 	at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)[2023-07-12T07:58:03.403Z] 	at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2449)[2023-07-12T07:58:03.403Z] 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1478)[2023-07-12T07:58:03.403Z] 	at java.base/java.lang.Thread.run(Thread.java:829)[2023-07-12T07:58:03.403Z] 	at org.jboss.threads.JBossThread.run(JBossThread.java:501)[2023-07-12T07:58:03.403Z] [2023-07-12T07:58:03.403Z]     at io.quarkus.builder.Execution.run (Execution.java:123)[2023-07-12T07:58:03.403Z]     at io.quarkus.builder.BuildExecutionBuilder.execute (BuildExecutionBuilder.java:79)[2023-07-12T07:58:03.403Z]     at io.quarkus.deployment.QuarkusAugmentor.run (QuarkusAugmentor.java:160)[2023-07-12T07:58:03.403Z]     at io.quarkus.runner.bootstrap.AugmentActionImpl.runAugment (AugmentActionImpl.java:331)[2023-07-12T07:58:03.403Z]     at io.quarkus.runner.bootstrap.AugmentActionImpl.createProductionApplication (AugmentActionImpl.java:175)[2023-07-12T07:58:03.403Z]     at io.quarkus.maven.BuildMojo.doExecute (BuildMojo.java:133)[2023-07-12T07:58:03.403Z]     at io.quarkus.maven.QuarkusBootstrapMojo.execute (QuarkusBootstrapMojo.java:154)[2023-07-12T07:58:03.403Z]     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)[2023-07-12T07:58:03.404Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:370)[2023-07-12T07:58:03.404Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:351)[2023-07-12T07:58:03.404Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)[2023-07-12T07:58:03.404Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:171)[2023-07-12T07:58:03.404Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:163)[2023-07-12T07:58:03.404Z]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)[2023-07-12T07:58:03.404Z]     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:210)[2023-07-12T07:58:03.404Z]     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:195)[2023-07-12T07:58:03.404Z]     at java.util.concurrent.FutureTask.run (FutureTask.java:264)[2023-07-12T07:58:03.404Z]     at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)[2023-07-12T07:58:03.404Z]     at java.util.concurrent.FutureTask.run (FutureTask.java:264)[2023-07-12T07:58:03.404Z]     at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1128)[2023-07-12T07:58:03.404Z]     at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:628)[2023-07-12T07:58:03.404Z]     at java.lang.Thread.run (Thread.java:829)[2023-07-12T07:58:03.404Z] Caused by: java.util.NoSuchElementException: No value present[2023-07-12T07:58:03.404Z]     at java.util.Optional.get (Optional.java:148)[2023-07-12T07:58:03.404Z]     at org.kie.kogito.codegen.api.context.KogitoBuildContext.lambda$getPropertiesMap$2 (KogitoBuildContext.java:173)[2023-07-12T07:58:03.404Z]     at java.util.stream.Collectors.lambda$uniqKeysMapAccumulator$1 (Collectors.java:178)[2023-07-12T07:58:03.404Z]     at java.util.stream.ReduceOps$3ReducingSink.accept (ReduceOps.java:169)[2023-07-12T07:58:03.404Z]     at java.util.stream.ReferencePipeline$2$1.accept (ReferencePipeline.java:177)[2023-07-12T07:58:03.404Z]     at java.util.HashMap$KeySpliterator.forEachRemaining (HashMap.java:1621)[2023-07-12T07:58:03.404Z]     at java.util.stream.AbstractPipeline.copyInto (AbstractPipeline.java:484)[2023-07-12T07:58:03.404Z]     at java.util.stream.AbstractPipeline.wrapAndCopyInto (AbstractPipeline.java:474)[2023-07-12T07:58:03.404Z]     at java.util.stream.ReduceOps$ReduceOp.evaluateSequential (ReduceOps.java:913)[2023-07-12T07:58:03.404Z]     at java.util.stream.AbstractPipeline.evaluate (AbstractPipeline.java:234)[2023-07-12T07:58:03.404Z]     at java.util.stream.ReferencePipeline.collect (ReferencePipeline.java:578)[2023-07-12T07:58:03.404Z]     at org.kie.kogito.codegen.api.context.KogitoBuildContext.getPropertiesMap (KogitoBuildContext.java:172)[2023-07-12T07:58:03.404Z]     at org.kie.kogito.codegen.process.ProcessCodegen.internalGenerate (ProcessCodegen.java:494)[2023-07-12T07:58:03.404Z]     at org.kie.kogito.codegen.core.AbstractGenerator.generate (AbstractGenerator.java:69)[2023-07-12T07:58:03.404Z]     at org.kie.kogito.codegen.core.ApplicationGenerator.lambda$generateComponents$0 (ApplicationGenerator.java:95)[2023-07-12T07:58:03.404Z]     at java.util.stream.ReferencePipeline$7$1.accept (ReferencePipeline.java:271)[2023-07-12T07:58:03.404Z]     at java.util.ArrayList$ArrayListSpliterator.forEachRemaining (ArrayList.java:1655)[2023-07-12T07:58:03.404Z]     at java.util.stream.AbstractPipeline.copyInto (AbstractPipeline.java:484)[2023-07-12T07:58:03.404Z]     at java.util.stream.AbstractPipeline.wrapAndCopyInto (AbstractPipeline.java:474)[2023-07-12T07:58:03.404Z]     at java.util.stream.ReduceOps$ReduceOp.evaluateSequential (ReduceOps.java:913)[2023-07-12T07:58:03.404Z]     at java.util.stream.AbstractPipeline.evaluate (AbstractPipeline.java:234)[2023-07-12T07:58:03.404Z]     at java.util.stream.ReferencePipeline.collect (ReferencePipeline.java:578)[2023-07-12T07:58:03.404Z]     at org.kie.kogito.codegen.core.ApplicationGenerator.generateComponents (ApplicationGenerator.java:97)[2023-07-12T07:58:03.404Z]     at org.kie.kogito.codegen.core.ApplicationGenerator.generate (ApplicationGenerator.java:74)[2023-07-12T07:58:03.404Z]     at org.kie.kogito.quarkus.common.deployment.KogitoAssetsProcessor.generateFiles (KogitoAssetsProcessor.java:260)[2023-07-12T07:58:03.404Z]     at org.kie.kogito.quarkus.common.deployment.KogitoAssetsProcessor.generateSources (KogitoAssetsProcessor.java:137)[2023-07-12T07:58:03.404Z]     at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)[2023-07-12T07:58:03.404Z]     at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)[2023-07-12T07:58:03.404Z]     at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)[2023-07-12T07:58:03.404Z]     at java.lang.reflect.Method.invoke (Method.java:566)[2023-07-12T07:58:03.404Z]     at io.quarkus.deployment.ExtensionLoader$3.execute (ExtensionLoader.java:909)[2023-07-12T07:58:03.404Z]     at io.quarkus.builder.BuildContext.run (BuildContext.java:281)[2023-07-12T07:58:03.404Z]     at org.jboss.threads.ContextHandler$1.runWith (ContextHandler.java:18)[2023-07-12T07:58:03.404Z]     at org.jboss.threads.EnhancedQueueExecutor$Task.run (EnhancedQueueExecutor.java:2449)[2023-07-12T07:58:03.404Z]     at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run (EnhancedQueueExecutor.java:1478)[2023-07-12T07:58:03.404Z]     at java.lang.Thread.run (Thread.java:829)[2023-07-12T07:58:03.404Z]     at org.jboss.threads.JBossThread.run (JBossThread.java:501)[2023-07-12T07:58:03.404Z] [ERROR] [2023-07-12T07:58:03.404Z] [ERROR] Re-run Maven using the -X switch to enable full debug logging.[2023-07-12T07:58:03.404Z] [ERROR] [2023-07-12T07:58:03.404Z] [ERROR] For more information about the errors and possible solutions, please read the following articles:[2023-07-12T07:58:03.404Z] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException[2023-07-12T07:58:03.404Z] [ERROR] [2023-07-12T07:58:03.404Z] [ERROR] After correcting the problems, you can resume the build with the command[2023-07-12T07:58:03.404Z] [ERROR]   mvn  -rf :integration-tests-quarkus-processes[2023-07-12T07:58:05.284Z] [INFO] kiegroup/kogito-runtimes failed. Won't execute remaining commands and projects[2023-07-12T07:58:05.284Z] [INFO] Execution summary for kiegroup/kogito-runtimes[2023-07-12T07:58:05.284Z] # [BEFORE] [kiegroup/kogito-runtimes] export INTEGRATION_BRANCH=[2023-07-12T07:58:05.284Z] [INFO] OK [Executed in 0.152236 ms][2023-07-12T07:58:05.284Z]  [2023-07-12T07:58:05.284Z] # [BEFORE] [kiegroup/kogito-runtimes] bash -c "if [ ! -z '' ] && [ -f .ci/environments/update.sh ]; then .ci/environments/update.sh  ; fi"[2023-07-12T07:58:05.284Z] [INFO] OK [Executed in 5.442108 ms][2023-07-12T07:58:05.284Z]  [2023-07-12T07:58:05.284Z] # [COMMANDS] [kiegroup/kogito-runtimes] export MVN_CMD=`bash -c "if [ '' = 'true' ]; then printf 'deploy  '; else printf 'install'; fi"`[2023-07-12T07:58:05.284Z] [INFO] OK [Executed in 4.234483 ms][2023-07-12T07:58:05.284Z]  [2023-07-12T07:58:05.285Z] # [COMMANDS] [kiegroup/kogito-runtimes] mvn dependency:tree clean -Dfull install  -s /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes@tmp/config13715302710072278111tmp -Dmaven.wagon.http.ssl.insecure=true -Dmaven.test.failure.ignore=true -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3 -T 1C -Dvalidate-formatting -Prun-code-coverage  -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn -B[2023-07-12T07:58:05.285Z] [INFO] NOT OK [Executed in 1024206.019887 ms][2023-07-12T07:58:05.285Z] [ERROR] The process '/opt/tools/apache-maven-3.8.7/bin/mvn' failed with exit code 1[2023-07-12T07:58:05.285Z]  [2023-07-12T07:58:05.285Z] [INFO] [AFTER] No commands were found for kiegroup/kogito-runtimes[2023-07-12T07:58:05.285Z]  [2023-07-12T07:58:05.285Z] # Uploading artifacts[2023-07-12T07:58:05.285Z] [INFO] Will not upload any artifacts in CLI environment[2023-07-12T07:58:05.285Z]  [2023-07-12T07:58:05.285Z] [ERROR] Failed to execute commands for kiegroup/kogito-runtimes[2023-07-12T07:58:05.285Z] [ERROR] Failed to execute mvn dependency:tree clean -Dfull install  -s /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes@tmp/config13715302710072278111tmp -Dmaven.wagon.http.ssl.insecure=true -Dmaven.test.failure.ignore=true -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3 -T 1C -Dvalidate-formatting -Prun-code-coverage  -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn -B :[2023-07-12T07:58:05.285Z] [ERROR] The process '/opt/tools/apache-maven-3.8.7/bin/mvn' failed with exit code 1[Pipeline] }[Pipeline] // withCredentials[Pipeline] }[2023-07-12T07:58:05.382Z] Deleting 1 temporary files[Pipeline] // configFileProvider[Pipeline] }[Pipeline] // scriptPost stage[Pipeline] script[Pipeline] {[Pipeline] sh[2023-07-12T07:58:05.967Z] + find . -type d -name node_modules -exec rm -rf '{}' ';'[Pipeline] junit[2023-07-12T07:58:10.202Z] Recording test results[2023-07-12T07:58:14.893Z] [Checks API] No suitable checks publisher found.[Pipeline] archiveArtifacts[2023-07-12T07:58:14.925Z] Archiving artifacts[Pipeline] }[Pipeline] // script[Pipeline] script[Pipeline] {[Pipeline] sh[2023-07-12T07:58:16.102Z] + rm -rf console.log[Pipeline] sh[2023-07-12T07:58:16.398Z] + wget --no-check-certificate -qO - https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.kogito-runtimes/2860/consoleText[2023-07-12T07:58:16.398Z] + tail -n 300

(tests) - kogito-springboot-examples job #1229 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
export BUILD_MVN_OPTS_CURRENT=
build-chain build cross_pr -f 'https://raw.githubusercontent.com/kiegroup/kogito-pipelines/main/.ci/pull-request-config.yaml' -o 'bc' -p kiegroup/kogito-examples -u https://github.com/kiegroup/kogito-runtimes/pull/3116 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.downstream.kogito-springboot-examples/1229/display/redirect
Test results:

PASSED: 129
FAILED: 1

Those are the test failures:

org.kie.kogito.springboot.outbox.OutboxIT.(?)
org.testcontainers.containers.ContainerLaunchException: Timed out waiting for container port to open (localhost ports: [8080, 32789] should be listening)

jenkins run kogito-runtimes tests

(tests) - kogito-runtimes job #2867 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
export BUILD_MVN_OPTS_CURRENT=-T 1C -Dvalidate-formatting -Prun-code-coverage
build-chain build cross_pr -f 'https://raw.githubusercontent.com/kiegroup/kogito-pipelines/main/.ci/pull-request-config.yaml' -o 'bc' -p kiegroup/kogito-runtimes -u https://github.com/kiegroup/kogito-runtimes/pull/3116 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.kogito-runtimes/2867/display/redirect
Test results:

PASSED: 3354
FAILED: 1

Those are the test failures:

org.kie.kogito.persistence.kafka.KafkaProcessInstancesIT.testFindByIdReadMode
expected: 5 but was: 0

jenkins run kogito-runtimes tests

@fjtirado code looks fine, but I'm a little confused by the extension name. Process definition is a term from jbpm/bpmn that we somehow reuse for sw to describe the model. So looking at the name, I was wondering the exact goal. My suggestion would be to maybe review the naming to something more descriptive to its function which is to store definitions. Perhaps storage ?

@fjtirado code looks fine, but I'm a little confused by the extension name. Process definition is a term from jbpm/bpmn that we somehow reuse for sw to describe the model. So looking at the name, I was wondering the exact goal. My suggestion would be to maybe review the naming to something more descriptive to its function which is to store definitions. Perhaps storage ?

@cristianonicolai I think definition is the right term.  This addon is handling addition and modification of process definitions (and might be even valid for bpmn definitions in future, so I do not think appropiated to single out that it only currently  supports SWF definitions in the name). Storage is too narrow in my opinion, since this endpoint also allow execution of the added process definition and eventually will support limited variables query of non straight throug process (as Mariam has requested and it is done for predefined defintions)

(tests) - kogito-runtimes job #2877 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
export BUILD_MVN_OPTS_CURRENT=-T 1C -Dvalidate-formatting -Prun-code-coverage
build-chain build cross_pr -f 'https://raw.githubusercontent.com/kiegroup/kogito-pipelines/main/.ci/pull-request-config.yaml' -o 'bc' -p kiegroup/kogito-runtimes -u https://github.com/kiegroup/kogito-runtimes/pull/3116 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.kogito-runtimes/2877/display/redirect
Test results:

PASSED: 3354
FAILED: 1

Those are the test failures:

org.kie.kogito.quarkus.workflows.AsyncAPIIT.testConsumer
Condition with alias 'dead' didn't complete within 10 seconds because assertion condition defined as a lambda expression in org.kie.kogito.quarkus.workflows.AssuredTestUtils that uses java.lang.String, java.lang.Stringjava.lang.String 1 expectation failed.Expected status code <404> but was <200>..

jenkins run kogito-runtimes tests


create client implementation

Another spec implemented and working.  Create a new client!

Looks great! This is really shaping up nicely.


Added custom user roles seem to not be tracked

It seems, that added user roles are not tracked in the Plausible Wordpress plugin. Some weeks ago, I added another role (even cloned the subscriber role and just gave it another name in this case) and logged-in pageviews aren't tracked anymore.
I noticed this, because my register and login plugin logs the user in automatically and gets redirected to a page, which I'm tracking as a goal in Plausible. The page visits of that goal aren't tracked anymore.

The fix to this would be to replace the current list of default roles with a list of all roles present in the configuration. That'll allow you to select which roles to track, even if they're custom user roles.
Thanks for notifying us!

@Dan0sz Is there a workaround for the meantime?

This PR takes care of this: https://github.com/plausible/wordpress/pull/129
@stormrage-project I'm sorry, but no workaround available in the meantime.

this is now live with the just released version 1.3


Can I really translate without programming skills?

I would like to translate, but actually can't figure it out: Am I doing it the right way?
Followed the instructions, but after running npm run update-language-files all language files in src/languages/ have been processed. The package-lock.json file is also changed. I expected only the new file to be filled with something like a template.
So, what I did:

OS Ubuntu 20.04 Headless
Installed "fnm" with script: curl -fsSL https://fnm.vercel.app/install | bash
Installed " Node v14.17.6 (x64)": fnm install 14
Cloned the repository locally: git clone https://github.com/louislam/uptime-kuma.git
CD into ~/uptime-kuma
Created the language file: touch src/languages/bg-BG.js
Installed ESLint: npm install eslint
Runing: npm run update-language-files finished without errors:

...
Processing tr-TR.js
Processing zh-CN.js
Processing zh-HK.js
Done. Fixing formatting by ESLint...

The new language file src/languages/bg-BG.js is now populated with the English template
git status shows that many files are changed as described above
git diff shows lots of changes that I think shouldn't be done. The output is endless so the example below is for just one file:

--- a/src/languages/zh-HK.js
+++ b/src/languages/zh-HK.js
@@ -170,7 +170,7 @@ export default {
     "Avg. Ping": "Avg. Ping",
     "Avg. Response": "Avg. Response",
     "Entry Page": "Entry Page",
-    "statusPageNothing": "Nothing here, please add a group or a monitor.",
+    statusPageNothing: "Nothing here, please add a group or a monitor.",
     "No Services": "No Services",
     "All Systems Operational": "All Systems Operational",
     "Partially Degraded Service": "Partially Degraded Service",

I have no idea what is the magic behind npm run update-language-files but it doesn't look like an expected final result on my side. So, the questions are:
What am I doing wrong?
What am I missing from the How to translate guide?
But for a guy without programming skills that was my best try.
If you have the time to assist me with this task it will be just GREAT!

The diff that you posted is normal. Running that command fixes all language files by applying the newest update, so all the changes indicate that those languages have not been updated yet.
If the previous single quotes problem is fixed, simply add ONLY your bg-BG file to git, commit, push, and you should be good to go.

Yes, it is required a bit of programming skills in order to translate.

But for a guy without programming skills that was my best try.

Really appreciate it! You did a very good job already. I honestly don't expect someone who don't have programming skills know how to use git and create pull request.
Let me know if you have finished the translation in https://github.com/louislam/uptime-kuma/pull/494, I can fix the single quotes for you.

Thank you guys!
What an awesome community!

If the previous single quotes problem is fixed...

I think npm install eslint did the magic.

You did a very good job already.

Really? Don't ask me how many hours I was trying to figure out how to do all that stuff.
Fingers crossed for my the next try.

Merged, thanks.


Add FastGetText for third party gems

There are three third party gems which currently use I18n:

devise
contact_us
bootstrap

They have to be explored to determine whether or not is feasible a change to gettext. If so, make these changes in views and controllers.

related to #1339


how could U get so many stars with an empty repository?

Hi @adamas-v , thanks for your interest in our work. We have released our code, all models on partial labeled data setting and most of the Faster R-CNN(R50) models on full labeled data setting. The rest of the model will also be released soon!
Thanks for your patience again!


Update operations with different ids in the URL and the resource body are successful

According to the spec, update operations should return a 400 error code if the id specified in the URL does not match the id specified in the resource:
"The request body SHALL be a Resource with an id element that has an identical value to the [id] in the URL. If no id element is provided, or the value is wrong, the server SHALL respond with a HTTP 400 error code, and SHOULD provide an operation outcome identifying the issue."
However, HAPI always uses the id specified in the URL, even if the Resource contains a different id.

Thanks for reporting! I'm checking in a fix now.


issues trying to use ALGO PBEWITHHMACSHA512ANDAES_256

Your project is really awesome and I like the document you have done. However, I fail to find the way to use customised algo such as PBEWITHHMACSHA512ANDAES_256 in my project.
My setup looks like:

I use @SpringBootApplication and jasypt sprint boot starter dependency
I Configure the application property file to use jasypt.encryptor.algorithm=PBEWITHHMACSHA512ANDAES_256
I use jasypt to encrypt my password using this algo
I use @value directly to annotate the encrypted field ENC(filed) in property file
I start my application using mvn -Djasypt.encryptor.password=xxx spring-boot:run

then I get the error
Caused by: com.ulisesbocchio.jasyptspringboot.exception.DecryptionException: Decryption of Properties failed,  make sure encryption/decryption passwords match

Jasypt simply doesn't work with that algorithm the way its internal encryptor is setting cipher params:
                /*
                 * Perform decryption using the Cipher
                 */
                final PBEParameterSpec parameterSpec =
                    new PBEParameterSpec(salt, this.keyObtentionIterations);

                synchronized (this.decryptCipher) {
                    this.decryptCipher.init(
                            Cipher.DECRYPT_MODE, this.key, parameterSpec);
                    decryptedMessage =
                        this.decryptCipher.doFinal(encryptedMessageKernel);
                }

Yo can use SimplePBEByteEncryptor in conjunction with SimplePBEStringEncryptor that I just added to master. That encryptor actually supports the algorithm you wanted to use.
You can use it like this:
@Bean("jasyptStringEncryptor")
public StringEncryptor stringEncryptor() {
    SimplePBEByteEncryptor encryptor = new SimplePBEByteEncryptor();
    encryptor.setPassword("some password loco");
    encryptor.setSaltGenerator(new RandomSaltGenerator());
    encryptor.setIterations(1000);
    encryptor.setAlgorithm("PBEWITHHMACSHA512ANDAES_256");
    SimplePBEStringEncryptor stringEncryptor = new SimplePBEStringEncryptor(encryptor);
    return stringEncryptor;
}

Bear in mind though, this encryptors are not yet part of jasypt-spring-boot so you'd have to copy the classes into your project.

I have to encrypt DB password using SHA2 PBEWITHHMACSHA512ANDAES_256 algorithm, but unable to decrypt it in Spring 4 application with JPA. On decryption, its throwing EncryptionOperationNotPossibleException.


Make new tokenizer logic conditional

Only use the new cgo tokenizer/detokenizer if we're using the new runners

Something happened with CI on this one..

The CI issue is due to the new version of Go having stricter lint checks. I cherry picked 2697d7f5 from main to jmorganca/llama to fix these PRs after they are rebased

go should not have been upgraded automatically. the branch is missing https://github.com/ollama/ollama/pull/6343 which pins go version to go.mod's version, 1.22.5 currently

Rebased to clean things up.


PlatformIO aggregated writes assume user has read permission for the target control

Describe the bug
I tried to use geopmwrite at board scope on a package-scoped control that I only have write permission to use. The write failed due to a missing signal of the same name (the signal exists, but is not reported by GEOPM since I do not have read access to it).
GEOPM version
2.0.0
Expected behavior
I expect to be allowed to geopmwrite any control that I have been granted permission to write.
Actual behavior
If I geopmwrite at a more coarse domain than the control's native domain, then the write operation fails when I do not also have read permission.
Error messages produced
geopmwrite SST::COREPRIORITY_ENABLE:ENABLE board 0 0
Error: cannot write control: <geopm> Invalid argument: ServiceIOGroup::signal_behavior(): signal_name SST::COREPRIORITY_ENABLE:ENABLE not valid for ServiceIOGroup: at src/ServiceIOGroup.cpp:313

Note that although the error message says it comes from signal_behavior(), the text of that message is wrong. The line number is from agg_function(). That function is called by PlatformIO when writing at a level more coarse than the control's native domain. The output is used to determine whether the write value should be distributed (for sum types) or broadcast (for other types) across its native domain.
Workaround
Write the control in its native domain to avoid executing the function that depends on read permissions.

Pehaps we should change the way the service works so that if write permission is granted, read permission is always also granted.


KAFKA-3858: Add functions to print stream topologies

@theduderog have a look when you can. I think the content is there, however you might want to do a subsequent PR where you format stuff how you like.

Can we make the title to be more meaningful than basic printing of everything?

It would be great to be able to print topologies at two different stages.  If we call print/toString() on the topology builder, then we'd be able to see what the topology looks like at a high level (which sub-topologies read from which topics and write to other topics and what state stores are used).  At this step, the topology is not yet running so we would not see how many tasks or partitions yet but this is still useful.
Calling print/toString() on the running KafkaStreams object it what's already here and can be helpful for seeing how things got scheduled at runtime.  The main issue I have now is knowing when this can be called.  There isn't a callback in KafkaStreams to know if all threads in the JVM have completed initialization.

Thanks @theduderog I'll add a toString to TopologyBuilder too.
The issue of knowing when Kafka Streams is up can be deferred to another JIRA.

checkstyle failure:  :streams:checkstyleMain[ant:checkstyle] /home/jenkins/jenkins-slave/workspace/kafka-trunk-git-pr-jdk7/streams/src/main/java/org/apache/kafka/streams/processor/internals/ProcessorTopology.java:27:8: Unused import - java.util.Queue. [ant:checkstyle] /home/jenkins/jenkins-slave/workspace/kafka-trunk-git-pr-jdk7/streams/src/main/java/org/apache/kafka/streams/processor/internals/ProcessorTopology.java:28:8: Unused import - java.util.LinkedList. [ant:checkstyle] /home/jenkins/jenkins-slave/workspace/kafka-trunk-git-pr-jdk7/streams/src/main/java/org/apache/kafka/streams/processor/internals/ProcessorTopology.java:116:50: 'cast' is not followed by whitespace.  FAILED

Left a few more comments, also I did not see TopologyBuilder's toString function as @theduderog suggested?

Haven't done the TopologyBuilder part yet, next commit. Stay tuned.

@guozhangwang @theduderog I looked into the TopologyBuilder and decided not to provide a toString for that after some thinking. There is a lot of processing required to process the entire graph in TopologyBuilder, and by the time you've done that, it's basically the same output as ProcessorTopology. So I'll stop here.

Thanks, @enothereska.  This is a good start.  At some point, we may want to support a way to get this data in machine readable format (say JSON) to be able to support visualizations like this.  Beyond the scope of this PR but something to think about.

@guozhangwang it prints the node itself first, then the children. So it will print the sink node (see below), but won't look for it's children.

Merged to trunk. Thanks @enothereska for your patience!


emoji_names: Rebuild with CLDR 45, emoji-data 15.1

Bumping the provision version and merged, thanks @andersk!


Production Build Issue with Webpack

I created a ticket in webpack and basically said to fix it id have to re-write part of that part that reads from the path
https://github.com/webpack/webpack/issues/13931
I can try to tackle this in a few days

Thank you for reporting the issue, can you elaborate what is the issue?
I'm working with bull-board v3.4.0 in production and it works perfectly.

Yah when running in production mode for some reason with this webpack config i get that error
https://github.com/lukepolo/webpack-resolve-bug/tree/main/dist  is the reproduction

Thanx, i will check it out

Fix released in v3.4.1

your amazing. thanks!


Modal auto close on open when history: false

I don't know which one i am doing wrong.
with history: false, modal auto close when open.
I don't want to show Hash (#) with modal ID in the address bar.
const modal = $('#modal').iziModal({
    overlayClose: false,
    closeOnEscape: false,
    history: false,
});

modal.iziModal('open');

In version 1.5 the option history is false by default.


Fix: Radio jammer now doesn't show setting changes to other players

About the PR

Title! Before the jammer used PopupPredicted which showed the change to anyone nearby. I changed it to PopupClient so only the client actually changing the settings gets the popup.
I did test this but I can't record and have two clients open at once 😔

Thanks for the fix.
While testing I found another, unrelated bug: The popup will only show up if the jammer is turned on.
Just in case you want to fix that one as well 😄

Looks like that was because the check is only for updating it if the jammer is currently on! I just took off the if statement so it has the popup if its on or off.

we really need a github action for merging hotfixes to make this easier


fatal error C1083: Cannot open include file: 'gdnative/vector3.h': No such file or directory

I got an error with compiler (MSVC 19.14+) while compiling with scons

scons: Reading SConscript files ...
scons: done reading SConscript files.
scons: Building targets ...
cl /Fosrc\core\AABB.obj /c src\core\AABB.cpp /TP /nologo /Z7 /Od /EHsc /D_DEBUG /MDd /I. /Igodot_headers /Iinclude /Iinclude\gen /Iinclude\core
AABB.cpp
e:\godot\godot 3.2\projects (own)\gdnative c++ based on documents\my gdnative c++ creation\godot-cpp\include\core\Vector3.hpp(4) : fatal error C1083: Cannot open include file: 'gdnative/vector3.h': No such file or directory
scons: *** [src\core\AABB.obj] Error 2
scons: building terminated because of errors.

When cloning this repository did you clone recursively? Sounds like godot_headers isn't included.
Else just run:
git submodule init
git submodule update

Within your godot-cpp folder

Never mind, my scons is probably STILL using an older version like 12.0 since I had multiple older versions of MSVC in my x86 Program Files folder so I removed the older versions in my C drive and scons is now using newer versions of it, completely.


Bootstraps a react app with create-react-app

This is post-eject, no?
I thought we wanted to get a standard app in and then eject + add custom config in parallel? This way we can parallelize the lessons a bit


Should invite! be ignoring validation?

Given the option  :validate_on_invite, should invite! be bypassing validation regardless. Should it instead be looking up whether the model implements the :validate_on_invite devise option?
See https://github.com/scambra/devise_invitable/blob/master/lib/devise_invitable/model.rb#L59

Read the wrong area of the code, my bad.


Add SL20

@KTibow Thanks for the contribution.
What is the reason why you couldn't use the measure tool for automatic recording of power values?
I see the color_temp.csv only contains 21 data points now which is not really up to the standards for the builtin power profile library.

The plug was very laggy in getting measurements, I was using the SonoffLAN integration, but I think it was using the cloud for some reason. If the tool could include a way to call update_entity, I would be able to use it.

@KTibow I think some other user got this issue before who also used a Sonoff. I'm pretty sure we discovered a a way to set the update frequency of the Sonoff. Let me check if I can find this conversation.

See #714, however this one i about the Sonoff flashed with ESPHome firmware. I am not sure if you can set a similar setting with the original firmware. I don't have a Sonoff myself so cannot check this.
I could add an optional service call to update_entity in the measure script but I prefer that you first have a look if the update frequency can somehow be decreased. Did you already test if update_entity gives a new power reading each time?

PS: Is there any reason the tool is so complicated? The .env file is somewhat out of date, and there seems to be more options than needed, when you could just use Home Assistant to get data that will be used in Home Assistant.

I am not sure what you mean with this. All the options in .env file has a purpose, there should not be any outdated settings that I know of. The measure tool is setup to be very easy to use for even non tech savy users, it contains a whole wizard and progress system which guide you through the process. Not sure how to improve on that significantly.
The whole point of the measure script is to walk through all possible brightness and color settings, and write data to the CSV files. That is not something which is build into HA in any way.

but I prefer that you first have a look if the update frequency can somehow be decreased

I've tried a couple of configuration changes, none of them seemed to work.

Did you already test if update_entity gives a new power reading each time?

Yes, I use this to check the power right now:
type: custom:mushroom-entity-card
entity: sensor.sonoff_10016407d0_power
tap_action:
  action: call-service
  service: homeassistant.update_entity
  data: {}
  target:
    entity_id: switch.sonoff_10016407d0

All the options in .env file has a purpose, there should not be any outdated settings that I know of.

Huh. I did have a bit of a bad time trying to use it, encountering stuff like

not being able to use backspace when I was entering into a text field
the descriptions being cut off instead of wrapping
having to change int(answers.get("num_lights", 1)) to int(answers.get("num_lights") or 1) because I wasn't measuring multiple lights
having to remove hardcoded things that were stopping me from having a larger gap in between measurements

Ok, I think it will be a good idea to make it possible to issue an update_entity call just before requesting the power meter value. Will add that somewhere in the next days. This feature will be optional and I will make a setting in .env where you can enable it.
I did not experience the bugs you noted yet. Looks like most of them seems bugs in the library I use for CLI wizard. https://github.com/magmax/python-inquirer. This is working fine on my Mac M1 macbook, and also on my ubuntu machine. There is not much I can do about that. Consistent cross platform CLI behaviour is a hard thing.
When you encounter small bugs or improvement with the measure tool which you can resolve PR's are welcome.

having to remove hardcoded things that were stopping me from having a larger gap in between measurements

There are certain limits coded to make sure the quality of the CSV files will be up to a certain standard.

Added the option with #850. You could update your local code to the updated master branch to give it a test run.
You need to set HASS_CALL_UPDATE_ENTITY_SERVICE=true in your .env file.
I have set an extra delay between update_entity and get_state now for 1 second,  but we need to figure out a right value for this without delaying the measure session to much. You can change this line https://github.com/bramstroker/homeassistant-powercalc/blob/master/utils/measure/powermeter/hass.py#L25. It can also be a float, so to wait for 200ms, you can define 0.2.
Let me know what works for you.

I made a couple of modifications to the code to get it to work, trying out right now.

having to change int(answers.get("num_lights", 1)) to int(answers.get("num_lights") or 1) because I wasn't measuring multiple lights

This was actually broken. Also reported by other user https://github.com/bramstroker/homeassistant-powercalc/issues/852. I was also able to reproduce. Is fixed in the codebase now.

CSV looks good now. Nice job. let's merge.


Add int8 as an allowed constant type in Pallas.

Currently creating an int8 constant in pallas fails with NotImplementedError: int8 (e.g. by doing zeros_like(x, jnp.int8).) This adds int8 as an allowed type.

Are all integer types supported? Could we change the check to np.issubdtype(x.dtype, np.integer)?


Block All Websites Except Some?

Is it possible to Block All Websites Except Some? Like stop people from being able to use the proxy for example.com but allow google.com?
I used this but it blocked scripts and sub domains too.
// decode q parameter to get the real URL
$url = url_decrypt($_GET['q']);
if(!preg_match('/(cnn.com)|(facebook.com)/', $url)){
exit;
}
$proxy = new Proxy();

use this:
https://github.com/Athlon1600/php-proxy/blob/master/src/Plugin/BlockListPlugin.php


Bumping core components version to use latest

Description
Bumping core components version to use latest
Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

This change is incorporated in https://github.com/adobe/aem-project-archetype/pull/1080


remix-pwa build process not exiting

I just noticed remix-pwa build no longer exits after completing the build. Tested on both macOS and Windows<EMAIL_ADDRESS>works as expected, so seems to be something in<EMAIL_ADDRESS>Let me know if there's any other relevant information I can provide.
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
Thanks.
P.S. Do you prefer issues logged here or on the monorepo?

P.S. Do you prefer issues logged here or on the monorepo?

Any.

I just noticed remix-pwa build no longer exits after completing the build. Tested on both macOS and Windows<EMAIL_ADDRESS>works as expected, so seems to be something in<EMAIL_ADDRESS>Let me know if there's any other relevant information I can provide.

Interesting. Currently ill rn so can't debug before next week. But would look at it ASAP.

Interesting. Currently ill rn so can't debug before next week. But would look at it ASAP.

No worries. Feel better soon!

Thanks. Was able to look at it and as I guessed, wasn't a huge issue. I forgot to dispose the context after building (somehow, the tests passed that). Would be out soon enough

Is it fixed now?

Is it fixed now?

Doesn't seem to be, at least on Windows with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Tried to update the other packages too, but it looks like<EMAIL_ADDRESS>has a peer dependency of<EMAIL_ADDRESS>which isn't published, so I couldn't try that combination.

Is it fixed now?

Doesn't seem to be, at least on Windows with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Tried to update the other packages too, but it looks like<EMAIL_ADDRESS>has a peer dependency of<EMAIL_ADDRESS>which isn't published, so I couldn't try that combination.

<EMAIL_ADDRESS>fixes this issue. Sorry for the inconvenience

<EMAIL_ADDRESS>fixes this issue. Sorry for the inconvenience

Confirmed. Thanks!


ci: push test images to Harbor instead of GHCR

:tada: This PR is included in version 1.5.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.5.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Support literal ids in typescript

For example, say I want to set my signal to c_miner or c_miner@2;
signal = "c_miner" gives a type error and doesn't emit anything if you ignore the error.
Maybe we should expose set_reg as a function or method:
signal.set('c_miner', 2)

Or should Value have an id property?
signal.id = 'c_miner'

That could work for coords too:
goto.coord = {x: 150, y: 150}

@quisar do you have any suggestions for how this should work?

I do not have  a very firm opinion.
I like the idea of having properties, but I do not think it really solves the issue, as it makes more sense if we only use this to change part of the Value (either the id, the count, the coord, etc.) and so would map more to combineRegister
We would still need a way to build a value from id and number.
For this, we have a couple of issue:

Make the type checker happy. Already today, writing a purely numerical function is possible but will get the compiler to complain, because using a number for a Value is incorrect.
Doing something efficient. If we build some kind of syntax for constants, we will need to be careful not to have code generating intermediary variable with the constant, and then using that variable afterwards. We can probably solve this in the compiler itself by generating some specific type of const Value that we can expand each time they are used.
Your set suggestion probably work, but would be very awkward to do something like:

let c: Value;
c.set('c_miner', 2);
...

as I expect the compiler to complain that c has not been initialized.

Probably the best solution is to just make 'setReg' a function. Maybe we should call it something like makeValue?
let c = makeValue('c_miner', 2)

I think that's a good option.
One possible alternative is to let String & Number extend the interface defining all the methods, for example:
interface Value {
  type: "No Match" | "Item" | "Entity" | "Component" | "Tech" | "Value" | "Coord";

  // Methods go here
  fullHealth(): boolean;

}

// Use AnyValue for argument types, can use specific types for return values
// Value is not used for arguments or return types
declare function getIngredients(product: AnyValue): [ItemNum, ItemNum, ItemNum];

interface FrameNumImpl extends BaseValue {
  id: Frame;
  num: number;
}
type FrameNum = Frame | number | FrameNumImpl;

interface ItemNumImpl extends Value {
  id: string,
  num: number
}
type ItemNum = Item | number | ItemNumImpl;

interface Coord extends Array<number>, Value {}

// The magic happens here. All other types of AnyValue must also extend Value, like ItemNumImpl
interface String extends Value {}
interface Number extends Value {}

This should allow users to write code like this:
export function foo(v: AnyValue) {
    if(v.fullHealth()) {
        v = "c_alien_attack";
    } else {
        v = {
            id: "test",
            num: 5
        } as ItemNum;
    }

    switch(v.type) {
        case "Item":
            v = 10;
            break;
    }

    let [a,b,c] = getIngredients(v);
    if(a == "alien_artifact") {
        // Type checked
    }

    if(a == "some_other_string") {
        // Intentional type error
    }
}

Although the benefit of a makeValue function is that multiple overrides can be provided, so the user doesn't have to cast manually.
        v = {
            id: "test",
            num: 5
        } as ItemNum;

Isn't very nice, and it'll likely be written a lot. So a utility function for ItemNum and FrameNum would be helpful.
declare function makeValue(a: Frame, b: number): FrameNum;
declare function makeValue(a: Item, b: number): ItemNum;

That would let users write:
signal = 5;
signal = "metalore";
signal = makeValue("metalore", 5);

If you are interested I'd be happy to take a stab at implementing this.

Yeah, that would be great!

https://github.com/ribrdb/desynced-tools/pull/44


[BUG] Chromedriver Executable needs to be in PATH

MAKE SURE THE ERROR IS NOT FROM YOU, THIS IS THE MOST FREQUENT CASE
Error Log
AppData\Local\Programs\Python\Python38-32\lib\site-packages\selenium\webdriver\common\service.py", line 81, in start
raise WebDriverException(
selenium.common.exceptions.WebDriverException: Message: 'chromedriver' executable needs to be in PATH. Please see https://chromedriver.chromium.org/home
Selenium was updated. This can be fixed by defining "service=" in src/browser.py just before the return, e.g.:
from selenium.webdriver.chrome.service import Service
from webdriver_manager.chrome import ChromeDriverManager
...
s = Service(ChromeDriverManager(version="114.xxx").install())
return webdriver.Chrome(service=s, options=options)

You need to download chromedriver.exe and put it in C:\Windows
Like this:

MAKE SURE THE ERROR IS NOT FROM YOU, THIS IS THE MOST FREQUENT CASE
Error Log AppData\Local\Programs\Python\Python38-32\lib\site-packages\selenium\webdriver\common\service.py", line 81, in start raise WebDriverException( selenium.common.exceptions.WebDriverException: Message: 'chromedriver' executable needs to be in PATH. Please see https://chromedriver.chromium.org/home
Selenium was updated. This can be fixed by defining "service=" in src/browser.py just before the return, e.g.:
from selenium.webdriver.chrome.service import Service
from webdriver_manager.chrome import ChromeDriverManager
...
s = Service(ChromeDriverManager(version="114.xxx").install())
return webdriver.Chrome(service=s, options=options)

You're right but since selenium v4.1.0 you no longer need to have chromedriver in the PATH because Selenium Manager is included in the package. Please check you are using the latest selenium.


MultiK2_win32

Hello Jan,
Impressive, really impressive! My only issue so far is that I could not compile MultiK2_win32 and the respective DesktopKinect-client. They reference a Windows-assembly, which is not available in my VS2015. I tried to replace it with references to the existing Windows.Media, Windows.Graphics, Windows.Foundation, etc., but this caused a lot of other errors. What did I do wrong? May Windows be a library coming with more recent OS update?
Greetings!

You need Windows SDK for W10 1607 (14393) / Windows 10 1607 installed to run it.
VS2015 installer > Features > Universal Windows App Development Tools > Tools (1.4.1) and Windows SDK (<IP_ADDRESS>93)
If you have it installed and still experience described issue:
To compile the win32 "desktop" library you need to fix a reference to Windows winmd. This metadata file is located in
Program Files (x86)\Windows Kits\10\UnionMetadata\Windows.winmd
see: https://github.com/jbe2277/waf/wiki/Using-Windows-Runtime-in-a-.NET-desktop-application
I intend to replace hardcoded hint path with the environment variable to Program files (x86) folder in the next commit.

project file update with relative path to Windows metadata & Windows Runtime library is part of https://github.com/jmarcincin/MultiK2/commit/708230ee9ed68a54c9b6b229641b6c480448252a


Exported help parameter order is wrong

Steps to reproduce
I generated a markdown document for a command that looks like this. I did not specify alphabetical order.

I then created external help specifying the path and output folder.  The external help puts the parameters in alphabetical order.

Which makes the help harder to read in my opinion and is not something I asked for. I wonder if this is related to #371
Expected behavior
I expect the external help to preserve the syntax from the markdown.
Actual behavior
Parameters are alphabetized
Environment data

Name                           Value
----                           -----
PSVersion                      5.1.17134.228
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17134.228
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

Platyps version 0.11.1

I think #371 is the markdown specific. Hm but perhaps since it's used in the update it could be related...

@jdhitsolutions, you

created the PowerShell module
created manually  "seeds" of the markdown help
run Update-Markdown help

Do I understand you correctly? Could you confirm?
I've probably found why Update-MarkdownHelp doesn't respect - in some cases - an existing order of parameters which exists in markdown file before the update.

@jdhitsolutions,
please read what I've found. Can you try to reproduce my work around?

@it-praktyk good investigation! If that's the root cause of the problems, I don't think we can quite do much about it. Perhaps we can detect it and warn users...

I'm not sure I followed all of this. But is the desired workflow to import the module before generating external help from the markdown docs?  Now I can't seem to duplicate the problem.

Hm, the https://github.com/PowerShell/platyPS/issues/371#issuecomment-432411285 is specifically about the update scenario... perhaps here there is somthing else going on.
@jdhitsolutions if you cannot repro the problem, we can probably close this issue and open a new one if it gets re-discovered.


update osspath

Codecov Report

Merging #293 into master will decrease coverage by 0.04%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #293      +/-   ##
============================================
- Coverage     96.59%   96.55%   -0.05%
- Complexity        0       21      +21
============================================
  Files             2        4       +2
  Lines           147      203      +56
  Branches          5        8       +3
============================================
+ Hits            142      196      +54
- Misses            3        5       +2
  Partials          2        2

Flag
Coverage Δ
Complexity Δ

#go
96.93% <ø> (ø)
0.00 <ø> (ø)

#java
96.42% <ø> (?)
21.00 <ø> (?)

#node_js
95.91% <ø> (ø)
0.00 <ø> (ø)

Impacted Files
Coverage Δ
Complexity Δ

...rc/main/java/com/aliyun/ccpcredentials/Client.java
100.00% <0.00%> (ø)
20.00% <0.00%> (?%)

.../java/com/aliyun/ccpcredentials/models/Config.java
33.33% <0.00%> (ø)
1.00% <0.00%> (?%)

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 bdf0c89...8457b8c. Read the comment docs.


feat(content-docs): allow custom props through category.json

Motivation
Close #6690
Resolve Feature Request: allow-customizing-category-description-in-generated-index-cards

Have you read the Contributing Guidelines on pull requests?
yes. but I have no idea how to test it.

Test Plan

Related PRs

Agree with @Josh-Cena : we want to enable users to bring their own customization abilities, not add just 2 new premade and unflexible attributes

Also agree. Thanks for the feedback. After addressing the review I'm trying to resolve this error.
The docs sidebar category metadata file path=${filePath} looks invalid
CustomProps are not acceptable even though I added sidebar validation.

Addressed reviews:
make categoryMetadata.customProps be passed to the final item.


Bug/file system bugs

What's new?

Full refactor to ModuleFileSystem. It uses now PhysFS for files management.

Two new classes for managing file system: Path and File.

Full refactor to ModuleResourceManager. Importing process is redifined.

Importer classes responsability is to transform files and data to our own binary format.

ResourceManager classes responsability is to create, save, load... resources from binary data.

Skybox is now a resource.

What's pending?

Finishing scene file explorer popup.
Testing if scripts work with the new filesystem. @JorxSS
Storing Material changes.
Disabling prefabs.
Redifining mesh transformations when importing.
Merging develop.

Known bugs:

Prefabs are generating a lot of problem on different parts of the engine, like saving, loading, etc. We should rethink how they work and how they are implemented. The solution for now will be disabling them when loading Model resources.

I will finish pending stuff tomorrow, please have a look at what has been done at the moment to advance review work 😄 @yalania @Dartemiss @JorxSS

Closing this cause Im working in a new branch


Bug: Replace admiral-devs with admiral

What happened?
We deleted the github team @pharmaverse/admiral-devs as we have @pharmaverse/admiral, so please replace any mentions of this on the site, e.g. see https://pharmaverse.github.io/admiral/articles/development_process.html. You'll need to search the repo to find any other scenarios where this is mentioned and update.
Session Information
N/A
Reproducible Example
N/A

thanks @ClaudiaCarlucci - agree this is a good one to start with after you attend the admiral onboarding call this week. no further info i can think of for this one, but feel free to put me down as PR reviewer and shout if you get stuck.

you can leave it Claudia thanks and we close them all when we make the next release in main branch - as for now its useful that people spot this instead of raising a new one if they find this issue in our site. we're going to add something in our PR templates in future that includes the key word "closes" and then you add the issue number, and this way they'll all get automatically closed when they get merged to main.


GH-1612: Option: Producer Fenced: Stop Container

Resolves https://github.com/spring-projects/spring-kafka/issues/1612
cherry-pick to 2.5.x

... and cherry-picked to 2.5.x


next.goddollar.org claim stats are probably wrong

Where 11.8kG$ claimed number coming from?  is it wrong or not ?

not a bug


add shortcut methods to Match API

e.g.
    public static <T, R> Option<R> MatchOpt(T t, Case<? extends T, ? extends R>... cases) {
        return Match(t).option(cases);
    }
    public static <T, R> Option<R> Match(T t, Case<? extends T, ? extends R>... cases) {
        return Match(t).of(cases);
    }

This would allow to reduce the number of unnecessary names in resulting expressions
also this:
    public static <T, R> Case<T, R> Default(R retVal) {
        return Case($(), retVal);
    }

would be a more familiar alternative to MatchOpt(...).getOrElse(...)

Hi @bruto0, thank you for your suggestion.
I thought about it but it does not align well to our strategy of keeping the API surface area small. This is really essential to keep the library simple and offer a great UX.
I understand that it is tempting to add syntactic sugar. But in the past, it showed that it will often not cover every use-case. Adding syntactic sugar does open the door for adding more syntactic sugar. At least there is no argument anymore to not add it. For example:

Default(R)
Default(Supplier<R>)
Default(Function<T, R>)
etc.

In the end, the API looks bloated. It already does in my opinion because many features are based on internal DSLs. I prefer to offer one canonical way to do things. Composition is a powerful tool that covers many use-cases.
I hope you understand it.
Thanks!
Daniel


[DON'T MERGE] Load common_credentials hieradata

This is a new hieradata file that contains secrets shared between integration, staging and production.
They're created in https://github.com/alphagov/govuk-secrets/pull/523. Do not merge this PR until that PR is merged (I'm not sure what happens if common_credentials doesn't exist yet).

This should be ok to test and merge before govuk_secrets as you don't have access to govuk_secrets when building the dev VM.
One thing I was wondering related to this is if you're considering a way to manage the auth credentials that are duplicated in staging and prod but distinct in integration?


https://www.tiktok.com/@_aktiv...2024_3?_t=8nYdqpHyKcp&_r=1

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

22436688


go, buildGoModule, buildGoPackage: default to 1.19

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

1.19 seems to be reasonable compared to the last couple of versions. Vendor hash breakage seems minimal and mostly restricted to packages that are known to be problematic anyway. Average amount of build failures, etc on x86-linux.
I think this time it should be okay to go through staging. However I don't want to merge this until just before we're going to start the next staging-next PR.
cc @mweinelt @vcunat

I expect we'll start another iteration today.

Is this ready?

Let me merge optimistically at this point and we'll see.


Model architecture Gemma2ForCausalLm

What is the issue?
Good afternoon, I would like to start marking I am not 100% sure whether this is an issue or maybe I am misunderstanding the concept of architecture.
I tried to create a model on ollama by using a Modelfile at version 0.3.0.

I go the previous error, so I decided to upgrade ollama to version 0.3.6
Which pops off error "unsupported architecture":

Configuration file of the model I have finetuned:
{
  "_name_or_path": "google/gemma-2-9b",
  "architectures": [
    "Gemma2ForCausalLM"
  ],
  "attention_bias": false,
  "attention_dropout": 0.0,
  "attn_logit_softcapping": 50.0,
  "bos_token_id": 2,
  "cache_implementation": "hybrid",
  "eos_token_id": 1,
  "final_logit_softcapping": 30.0,
  "head_dim": 256,
  "hidden_act": "gelu_pytorch_tanh",
  "hidden_activation": "gelu_pytorch_tanh",
  "hidden_size": 3584,
  "initializer_range": 0.02,
  "intermediate_size": 14336,
  "max_position_embeddings": 8192,
  "model_type": "gemma2",
  "num_attention_heads": 16,
  "num_hidden_layers": 42,
  "num_key_value_heads": 8,
  "pad_token_id": 0,
  "query_pre_attn_scalar": 256,
  "rms_norm_eps": 1e-06,
  "rope_theta": 10000.0,
  "sliding_window": 4096,
  "sliding_window_size": 4096,
  "torch_dtype": "float16",
  "transformers_version": "4.43.3",
  "use_cache": false,
  "vocab_size": 256000
}

It's a model based on Gemma2 9b. Gemma2 works smoothly.

Modelfile:
FROM /path/model/
TEMPLATE """<start_of_turn>user/
{{ if .System }}{{ .System }} {{ end }}{{ .Prompt }}<end_of_turn>
<start_of_turn>model
{{ .Response }}<end_of_turn>"""
PARAMETER stop "<start_of_turn>"
PARAMETER stop "<end_of_turn>"
SYSTEM """Below is an instruction that describes a task. Write a response that appropriately completes the request.
Generate a concise summary in Spanish the following input. Here is the input"""

I don't understand by Gemma2 is supported but models based on it are not.
Thank you for reaching this point. Please if you have any clue about what's the issue please write it down bellow.
OS
Linux
GPU
Nvidia
CPU
No response
Ollama version
0.3.6

The create function of ollama primarily works with GGUF files.  The ability to import safetensors (I'm assuming that's what's in /path/model) is a convenience function but it's limited in the architectures it can process.  If you want to import a model that is not in the supported architecture, you need to use the convert_hf_to_gguf.py script in llama.cpp

Gemma2 conversion is implemented by https://github.com/ollama/ollama/pull/5365 which has been merged and will be in the next release


error: expected , when setting aliases for overloaded function with abigen

hi, I'm using abigen to decode the input data of a transaction to Uniswap universal router.
I used the following script to decode:
use ethers::{abi::AbiDecode, prelude::*};
use eyre::Result;

abigen!(UniswapV2Pair, "src/abi/IUniswapV2Pair.json");
abigen!(UniswapV2Router02, "src/abi/IUniswapV2Router02.json");
abigen!(UniswapV2Factory, "src/abi/IUniswapV2Factory.json");
abigen!(UniveralRouter, "src/abi/IUniversalRouter.json");

/// Decodes the raw tx data into a UniversalRouter Call
pub fn decode_universal_router_calldata(data: &Bytes) ->
Result<ExecuteCall> {
    // print!("input data: {:?}", data);
    ExecuteCall::decode(data).map_err(|e| eyre::eyre!(e))
}

But I got the error:
error: missing or wrong function selector

I guess the reason for this error is that abigen can not find a matching function selector, cause the 'execute' function in IUniversalRouter.json has two overloaded versions:
 {
    "inputs": [
      {
        "internalType": "bytes",
        "name": "commands",
        "type": "bytes"
      },
      {
        "internalType": "bytes[]",
        "name": "inputs",
        "type": "bytes[]"
      }
    ],
    "name": "execute",
    "outputs": [],
    "stateMutability": "payable",
    "type": "function"
  },
  {
    "inputs": [
      {
        "internalType": "bytes",
        "name": "commands",
        "type": "bytes"
      },
      {
        "internalType": "bytes[]",
        "name": "inputs",
        "type": "bytes[]"
      },
      {
        "internalType": "uint256",
        "name": "deadline",
        "type": "uint256"
      }
    ],
    "name": "execute",
    "outputs": [],
    "stateMutability": "payable",
    "type": "function"
  },

So I  created aliases for overloaded function 'execute':
abigen!(
    UniveralRouter,
    "src/abi/IUniversalRouter.json",
    methods {
        execute(bytes, bytes[]) as execute_none;
        execute(bytes, bytes[], uint256) as execute_uin256;
    },
);

But I got the following error, it seems that abigen can not handle 'bytes[]' or 'address[]' as parameters of the function. Could anyone help me, much appreciated!
error: expected `,`
  --> src/abi/mod.rs:27:29
   |
27 |         execute(bytes, bytes[], uint256) as execute_uint256;

We currently don't support types other the primitive types (address, uint256, etc) in alias overloading. This will be fixed in a week or two.
Regarding your decoding issue, you can check out the expanded abigen macro code with rust-analyzer's "Expand macro recursively", or with cargo-expand and see if it matches your expectated selector (ExecuteCall is the one without the uint256 param).


Test for hello-world ingress Certificate ready

What this PR does
Towards: https://github.com/giantswarm/giantswarm/issues/31013
Adds a new test case to the hello-world tests to check that the associated Certificate is created and is ready.
Note: As we're now referencing types from cert-manager in multiple places it doesn't make sense to keep using the unstructured type. I won't do it as part of this PR but I plan to update clustertest to include the cert-manager schema in the kube client it creates that can then be used in these tests.
Example output:
Common tests hello world should have a ready Certificate generated
/Users/marcus/Code/GiantSwarm/cluster-test-suites/internal/common/hello.go:206
  {"level":"info","ts":"2024-06-24T09:32:27+01:00","msg":"Checking for certificate 'hello-world-tls' in namespace 'giantswarm'"}
  {"level":"info","ts":"2024-06-24T09:32:27+01:00","msg":"Found status.condition with type 'Ready' and status 'True' in Certificate 'hello-world-tls'"}
• [0.051 seconds]

Checklist

[x] Update changelog in CHANGELOG.md.

Trigger e2e tests

/run cluster-test-suites

Common tests hello world should have a ready Certificate generated
/app/internal/common/hello.go:206
  {"level":"info","ts":"2024-06-24T09:34:32Z","msg":"Checking for certificate 'hello-world-tls' in namespace 'giantswarm'"}
  {"level":"info","ts":"2024-06-24T09:34:32Z","msg":"Certificate 'hello-world-tls' is not Ready - 'Issuing certificate as Secret does not exist'"}
• [0.041 seconds]
------------------------

🤦

/run cluster-test-suites TARGET_SUITES=./providers/capa


Jetson Xavier + Logitech C920 Issue

As I understand it jetson-inference supports the Jetson Xavier (with Jetpack 4.0 DP) as of the latest commit (81b84d7). But, when I try imagenet-camera I'm unable to get any video from a Logitech C920 web camera.
I initially tried setting the DEFAULT_CAMERA connection to 0 when I had the C920 as /dev/video0, and I've also tried it with a setting of 1 when I had two USB UVC cameras attached to the system.
In previous experiences with the Jetson TX1/TX2 it sometimes required max performance mode to prevent USB suspend issues. I tried that on the Xavier using the jetson_clocks.sh script, but it didn't make any difference in whether the video worked or not.
I tried Cheese the webcam app, and that worked fine. So the camera+board seems to work.
I used to be able to use GTK UVC video viewer on the TX1/TX2, but that isn't working either. That crashes if I have a camera connected.

It seems to fail on:
[gstreamer] gstreamer v4l2src0 ERROR Internal data stream error.
[gstreamer] gstreamer Debugging info: gstbasesrc.c(3055): gst_base_src_loop (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
streaming stopped, reason not-negotiated (-4)
Here is the complete log:
nvidia@jetson-0423018055236:~/jetson-inference/build/aarch64/bin$ ./imagenet-camera googlenet
imagenet-camera
args (2):  0 [./imagenet-camera]  1 [googlenet]
[gstreamer] initialized gstreamer, version <IP_ADDRESS>
[gstreamer] gstCamera attempting to initialize with GST_SOURCE_NVCAMERA
[gstreamer] gstCamera pipeline string:
v4l2src device=/dev/video0 ! video/x-raw, width=(int)1280, height=(int)720, format=RGB ! videoconvert ! video/x-raw, format=RGB ! videoconvert !appsink name=mysink
[gstreamer] gstCamera successfully initialized with GST_SOURCE_V4L2
imagenet-camera:  successfully initialized video device
width:  1280
height:  720
depth:  24 (bpp)
imageNet -- loading classification network model from:
-- prototxt     networks/googlenet.prototxt
-- model        networks/bvlc_googlenet.caffemodel
-- class_labels networks/ilsvrc12_synset_words.txt
-- input_blob   'data'
-- output_blob  'prob'
-- batch_size   2
[TRT]  TensorRT version 5.0.0
[TRT]  attempting to open cache file networks/bvlc_googlenet.caffemodel.2.tensorcache
[TRT]  loading network profile from cache... networks/bvlc_googlenet.caffemodel.2.tensorcache
[TRT]  platform has FP16 support.
[TRT]  networks/bvlc_googlenet.caffemodel loaded
[TRT]  CUDA engine context initialized with 2 bindings
[TRT]  networks/bvlc_googlenet.caffemodel input  binding index:  0
[TRT]  networks/bvlc_googlenet.caffemodel input  dims (b=2 c=3 h=224 w=224) size=1204224
[cuda]  cudaAllocMapped 1204224 bytes, CPU 0x21c05e000 GPU 0x21c05e000
[TRT]  networks/bvlc_googlenet.caffemodel output 0 prob  binding index:  1
[TRT]  networks/bvlc_googlenet.caffemodel output 0 prob  dims (b=2 c=1000 h=1 w=1) size=8000
[cuda]  cudaAllocMapped 8000 bytes, CPU 0x21c25e000 GPU 0x21c25e000
networks/bvlc_googlenet.caffemodel initialized.
[TRT]  networks/bvlc_googlenet.caffemodel loaded
imageNet -- loaded 1000 class info entries
networks/bvlc_googlenet.caffemodel initialized.
default X screen 0:   1920 x 1080
[OpenGL]  glDisplay display window initialized
[OpenGL]   creating 1280x720 texture
loaded image  fontmapA.png  (256 x<PHONE_NUMBER> bytes
[cuda]  cudaAllocMapped 2097152 bytes, CPU 0x21c45e000 GPU 0x21c45e000
[cuda]  cudaAllocMapped 8192 bytes, CPU 0x21c260000 GPU 0x21c260000
[gstreamer] gstreamer transitioning pipeline to GST_STATE_PLAYING
[gstreamer] gstreamer changed state from NULL to READY ==> mysink
[gstreamer] gstreamer changed state from NULL to READY ==> videoconvert1
[gstreamer] gstreamer changed state from NULL to READY ==> capsfilter1
[gstreamer] gstreamer changed state from NULL to READY ==> videoconvert0
[gstreamer] gstreamer changed state from NULL to READY ==> capsfilter0
[gstreamer] gstreamer changed state from NULL to READY ==> v4l2src0
[gstreamer] gstreamer changed state from NULL to READY ==> pipeline0
[gstreamer] gstreamer changed state from READY to PAUSED ==> videoconvert1
[gstreamer] gstreamer changed state from READY to PAUSED ==> capsfilter1
[gstreamer] gstreamer changed state from READY to PAUSED ==> videoconvert0
[gstreamer] gstreamer changed state from READY to PAUSED ==> capsfilter0
[gstreamer] gstreamer stream status CREATE ==> src
[gstreamer] gstreamer changed state from READY to PAUSED ==> v4l2src0
[gstreamer] gstreamer changed state from READY to PAUSED ==> pipeline0
[gstreamer] gstreamer msg new-clock ==> pipeline0
[gstreamer] gstreamer stream status ENTER ==> src
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> videoconvert1
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> capsfilter1
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> videoconvert0
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> capsfilter0
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> v4l2src0
[gstreamer] gstreamer msg stream-start ==> pipeline0
[gstreamer] gstCamera onEOS
[gstreamer] gstreamer v4l2src0 ERROR Internal data stream error.
[gstreamer] gstreamer Debugging info: gstbasesrc.c(3055): gst_base_src_loop (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
streaming stopped, reason not-negotiated (-4)
[gstreamer] gstreamer changed state from READY to PAUSED ==> mysink
imagenet-camera:  camera open for streaming
imagenet-camera:  failed to capture frame
imagenet-camera:  failed to convert from NV12 to RGBA
imageNet::Classify( 0x(nil), 1280, 720 ) -> invalid parameters
[cuda]   cudaNormalizeRGBA((float4*)imgRGBA, make_float2(0.0f, 255.0f), (float4*)imgRGBA, make_float2(0.0f, 1.0f), camera->GetWidth(), camera->GetHeight())
[cuda]      invalid device pointer (error 17) (hex 0x11)
[cuda]      /home/nvidia/jetson-inference/imagenet-camera/imagenet-camera.cpp:193
[cuda]   registered 14745600 byte openGL texture for interop access (1280x720)
imagenet-camera:  failed to capture frame
imagenet-camera:  failed to convert from NV12 to RGBA
imageNet::Classify( 0x(nil), 1280, 720 ) -> invalid parameters
[cuda]   cudaNormalizeRGBA((float4*)imgRGBA, make_float2(0.0f, 255.0f), (float4*)imgRGBA, make_float2(0.0f, 1.0f), camera->GetWidth(), camera->GetHeight())
[cuda]      invalid device pointer (error 17) (hex 0x11)
[cuda]      /home/nvidia/jetson-inference/imagenet-camera/imagenet-camera.cpp:193

Just want to add that I tested it successfully within gstreamer with the folllowing pipeline.
gst-launch-1.0 v4l2src device="/dev/video0" ! "video/x-raw, width=640, height=480, format=(string)YUY2" ! xvimagesink -e

Thanks @S4WRXTTCS , can you see if changing gstCamera.cpp:362 to the following works in jetson-inference?
ss << "format=YUY2 ! videoconvert ! video/x-raw, format=RGB ! videoconvert !";

Thanks. That fixes the problem as far as I can tell.
The only issues now seems to be it's only showing a frame rate of 10fps, and it's incorrectly saying it's alexnet and not googlenet.

I originally had it as RGB because that gave the best framerate/latency for USB camera, but it seems RGB is no longer in the formats list.
Is it saying alexnet in the titlebar or in the console output?   If you re-clone, the title bar should have been updated and now shows the “TensorRT build | FP16/FP32 | FPS”
From: Jason Mecham<EMAIL_ADDRESS>Sent: Monday, September 17, 2018 6:09 PM
To: dusty-nv/jetson-inference<EMAIL_ADDRESS>Cc: Dustin Franklin<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [dusty-nv/jetson-inference] Jetson Xavier + Logitech C920 Issue (#267)
Thanks. That fixes the problem as far as I can tell.
The only issues now seems to be it's only showing a frame rate of 10fps, and it's incorrectly saying it's alexnet and not googlenet.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/dusty-nv/jetson-inference/issues/267#issuecomment-422188103, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AOpDK8Jd-fonz3di7bhUVkfVFCRyX_WAks5ucB1xgaJpZM4WqIqh.

This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.

It's saying alexnet in the titlebar. In the console output it's correctly showing googlenet.

I think that's an artifact from the default title from older code.  The title bar should be updated here:   https://github.com/dusty-nv/jetson-inference/blob/3b072b6fd741a940543b5560a9bc7d21374e7ff1/detectnet-camera/detectnet-camera.cpp#L230
When I merge some changes from the dev branch and implement detection of Xavier/TX1/TX2 chip ID, I can select YUY2 format instead of RGB format on Xavier in the V4L2 path of gstCamera.
-------- Original message --------
From: Jason Mecham<EMAIL_ADDRESS>Date: 9/17/18 6:13 PM (GMT-05:00)
To: dusty-nv/jetson-inference<EMAIL_ADDRESS>Cc: Dustin Franklin<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [dusty-nv/jetson-inference] Jetson Xavier + Logitech C920 Issue (#267)
It's saying alexnet in the titlebar. In the console output it's correctly showing googlenet.

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/dusty-nv/jetson-inference/issues/267#issuecomment-422189268, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AOpDK-NrclKFzxzskLJZ4-aLTjjsPTvvks5ucB6ggaJpZM4WqIqh.

This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.

Just a quick note about the frame rate.
It's not an issue with the jetson-inference, but that's the framerate of the camera at 1280x720.
Apparently I'm going to need a faster camera. :-)

Hello, I am experiencing this same issue, and I tried changing RGB to YUV2 in gstCamera.cpp:362 as per dusty-nv#267. Although it took me a step backwards because the console output now reads 'imagenet-camera:  failed to initialize video device'. Where before I had it similar to above where the camera would be initialized but the console box had no video output, I think its because the blue lights around the Logitech C920 are not lighting up compared to when I use cheese or the command listed
here gst-launch-1.0 v4l2src device="/dev/video0" ! "video/x-raw, width=640, height=480, format=(string)YUY2" ! xvimagesink -e


Switch to MIT licensed version of plantuml

Now that the MIT version is available in maven central we can attempt to switch over (since this is a friendlier license and should be less likely to cause issues)

done