[KOGITO-7840] - Add validation on Workflow Metadata with admission we…

…bhooks

Description of the change:
Motivation for the change:
Checklist

[ ] Add or Modify a unit test for your change
[ ] Have you verified that tall the tests are passing?

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

Openshift tests job #436 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/436/display/redirect
See console log:

Console Logs
openshift-network-diagnostics                      network-check-target-5rn7j                                        1/1     Running       0             19dopenshift-network-operator                         network-operator-7f48cb8b6d-s957r                                 1/1     Running       0             20dopenshift-operator-lifecycle-manager               catalog-operator-574b86796-tbgfc                                  1/1     Running       0             20dopenshift-operator-lifecycle-manager               collect-profiles-28212300-gn9cm                                   0/1     Completed     0             40mopenshift-operator-lifecycle-manager               collect-profiles-28212315-w6znp                                   0/1     Completed     0             25mopenshift-operator-lifecycle-manager               collect-profiles-28212330-nflmw                                   0/1     Completed     0             10mopenshift-operator-lifecycle-manager               olm-operator-779dfbf5b7-qlqdw                                     1/1     Running       0             20dopenshift-operator-lifecycle-manager               package-server-manager-56c5446c7-72jvf                            1/1     Running       0             20dopenshift-operator-lifecycle-manager               packageserver-6c9788bdd5-knnb9                                    1/1     Running       0             19dopenshift-operator-lifecycle-manager               packageserver-6c9788bdd5-snhx6                                    1/1     Running       0             19dopenshift-roks-metrics                             metrics-6467c65d7-mrm5p                                           1/1     Running       0             20dopenshift-roks-metrics                             push-gateway-6f9c7688c5-hhrtc                                     1/1     Running       0             20dopenshift-service-ca-operator                      service-ca-operator-599cdfbbc9-lrfb8                              1/1     Running       0             20dopenshift-service-ca                               service-ca-7fbb6558f7-w4ctq                                       1/1     Running       0             20dsonataflow-operator-system                         sonataflow-operator-controller-manager-dcdfdd888-jh8js            0/2     Terminating   0             13steste                                              httpd-sample-7bdf74f5cd-b2rbf                                     1/1     Running       0             140dtigera-operator                                    tigera-operator-7dc6fddb9c-nnj9p                                  1/1     Running       0             54d[Pipeline] }[Pipeline] // scriptPost stage[Pipeline] archiveArtifactsArchiving artifacts‘test/logs/**/*.log’ doesn’t match anything: ‘test’ exists but not ‘test/logs/**/*.log’No artifacts found that match the file pattern "test/logs/**/*.log". Configuration error?[Pipeline] junitRecording test resultsNone of the test reports contained any result[Checks API] No suitable checks publisher found.[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // timeout[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withEnv[Pipeline] }Lock released on resource [Sonataflow Operator OpenShift tests https://c107-e.us-south.containers.cloud.ibm.com:30353][Pipeline] // lock[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/436/api/json[Pipeline] readJSON[Pipeline] shNo test report files were found. Configuration error?

Openshift tests job #437 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/437/display/redirect
See console log:

Console Logs
openshift-network-diagnostics                      network-check-target-5rn7j                                        1/1     Running       0             20dopenshift-network-operator                         network-operator-7f48cb8b6d-s957r                                 1/1     Running       0             20dopenshift-operator-lifecycle-manager               catalog-operator-574b86796-tbgfc                                  1/1     Running       0             20dopenshift-operator-lifecycle-manager               collect-profiles-28213245-4s8k6                                   0/1     Completed     0             35mopenshift-operator-lifecycle-manager               collect-profiles-28213260-cwjpz                                   0/1     Completed     0             20mopenshift-operator-lifecycle-manager               collect-profiles-28213275-r88q5                                   0/1     Completed     0             5m2sopenshift-operator-lifecycle-manager               olm-operator-779dfbf5b7-qlqdw                                     1/1     Running       0             20dopenshift-operator-lifecycle-manager               package-server-manager-56c5446c7-72jvf                            1/1     Running       0             20dopenshift-operator-lifecycle-manager               packageserver-6c9788bdd5-knnb9                                    1/1     Running       0             20dopenshift-operator-lifecycle-manager               packageserver-6c9788bdd5-snhx6                                    1/1     Running       0             20dopenshift-roks-metrics                             metrics-6467c65d7-mrm5p                                           1/1     Running       0             20dopenshift-roks-metrics                             push-gateway-6f9c7688c5-hhrtc                                     1/1     Running       0             20dopenshift-service-ca-operator                      service-ca-operator-599cdfbbc9-lrfb8                              1/1     Running       0             20dopenshift-service-ca                               service-ca-7fbb6558f7-w4ctq                                       1/1     Running       0             20dsonataflow-operator-system                         sonataflow-operator-controller-manager-5bd5cbd59-8zzb8            0/2     Terminating   0             12steste                                              httpd-sample-7bdf74f5cd-b2rbf                                     1/1     Running       0             141dtigera-operator                                    tigera-operator-7dc6fddb9c-nnj9p                                  1/1     Running       0             54d[Pipeline] }[Pipeline] // scriptPost stage[Pipeline] archiveArtifactsArchiving artifacts‘test/logs/**/*.log’ doesn’t match anything: ‘test’ exists but not ‘test/logs/**/*.log’No artifacts found that match the file pattern "test/logs/**/*.log". Configuration error?[Pipeline] junitRecording test resultsNone of the test reports contained any result[Checks API] No suitable checks publisher found.[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // timeout[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withEnv[Pipeline] }Lock released on resource [Sonataflow Operator OpenShift tests https://c107-e.us-south.containers.cloud.ibm.com:30353][Pipeline] // lock[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/437/api/json[Pipeline] readJSON[Pipeline] shNo test report files were found. Configuration error?

Openshift tests job #438 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/438/display/redirect
See console log:

Console Logs
openshift-network-diagnostics                      network-check-target-5rn7j                                        1/1     Running       0             20dopenshift-network-operator                         network-operator-7f48cb8b6d-s957r                                 1/1     Running       0             20dopenshift-operator-lifecycle-manager               catalog-operator-574b86796-tbgfc                                  1/1     Running       0             20dopenshift-operator-lifecycle-manager               collect-profiles-28213275-r88q5                                   0/1     Completed     0             31mopenshift-operator-lifecycle-manager               collect-profiles-28213290-tr9kf                                   0/1     Completed     0             16mopenshift-operator-lifecycle-manager               collect-profiles-28213305-84vn5                                   0/1     Completed     0             82sopenshift-operator-lifecycle-manager               olm-operator-779dfbf5b7-qlqdw                                     1/1     Running       0             20dopenshift-operator-lifecycle-manager               package-server-manager-56c5446c7-72jvf                            1/1     Running       0             20dopenshift-operator-lifecycle-manager               packageserver-6c9788bdd5-knnb9                                    1/1     Running       0             20dopenshift-operator-lifecycle-manager               packageserver-6c9788bdd5-snhx6                                    1/1     Running       0             20dopenshift-roks-metrics                             metrics-6467c65d7-mrm5p                                           1/1     Running       0             20dopenshift-roks-metrics                             push-gateway-6f9c7688c5-hhrtc                                     1/1     Running       0             20dopenshift-service-ca-operator                      service-ca-operator-599cdfbbc9-lrfb8                              1/1     Running       0             20dopenshift-service-ca                               service-ca-7fbb6558f7-w4ctq                                       1/1     Running       0             20dsonataflow-operator-system                         sonataflow-operator-controller-manager-59769f4fb6-jb9j4           0/2     Terminating   0             14steste                                              httpd-sample-7bdf74f5cd-b2rbf                                     1/1     Running       0             141dtigera-operator                                    tigera-operator-7dc6fddb9c-nnj9p                                  1/1     Running       0             54d[Pipeline] }[Pipeline] // scriptPost stage[Pipeline] archiveArtifactsArchiving artifacts‘test/logs/**/*.log’ doesn’t match anything: ‘test’ exists but not ‘test/logs/**/*.log’No artifacts found that match the file pattern "test/logs/**/*.log". Configuration error?[Pipeline] junitRecording test resultsNone of the test reports contained any result[Checks API] No suitable checks publisher found.[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // timeout[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withEnv[Pipeline] }Lock released on resource [Sonataflow Operator OpenShift tests https://c107-e.us-south.containers.cloud.ibm.com:30353][Pipeline] // lock[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/438/api/json[Pipeline] readJSON[Pipeline] shNo test report files were found. Configuration error?

Thank you! Do we have any updates in the docs to do? Maybe a section under Operator with links to cert-manager and OLM guides. Plus, a brief description of what we do validate.

there are some instructions here https://github.com/kiegroup/kogito-docs/pull/361

@radtriste do you want to take a look before merging?

So the cert-manager becomes mandatory for sonataflow operator ?

Yes, OLM will manage it for us.
Locally we can disable it via an ENV. @spolti maybe adding this env by default in our hack/local scripts.

So the cert-manager becomes mandatory for sonataflow operator ?

Yes, OLM will manage it for us.
Locally we can disable it via an ENV. @spolti maybe adding this env by default in our hack/local scripts.

It is disabled by default for local execution. ( make run)
it can be enabled  with make run ENABLE_WEBHOOKS=true
When deploying it, make deploy take care of the cert-manager operator installation.

Also please, verify if our manual installation guide still relevant or we need to update it.

I did follow the docs to install the operator from there, didn't find outdated stuff.

So the cert-manager becomes mandatory for sonataflow operator ?

Yes, OLM will manage it for us.
Locally we can disable it via an ENV. @spolti maybe adding this env by default in our hack/local scripts.

It is disabled by default for local execution. ( make run) it can be enabled with make run ENABLE_WEBHOOKS=true When deploying it, make deploy take care of the cert-manager operator installation.

Also please, verify if our manual installation guide still relevant or we need to update it.

I did follow the docs to install the operator from there, didn't find outdated stuff.

Some changes are needed because our documentation won't work: https://sonataflow.org/serverlessworkflow/latest/cloud/operator/install-serverless-operator.html#_install
On Minikube, my operator pod is stuck in ContainerCreating due to this:
$ kget events
LAST SEEN   TYPE      REASON              OBJECT                                                         MESSAGE
15m         Normal    Scheduled           pod/sonataflow-operator-controller-manager-7f66df8485-cstc5    Successfully assigned sonataflow-operator-system/sonataflow-operator-controller-manager-7f66df8485-cstc5 to minikube
73s         Warning   FailedMount         pod/sonataflow-operator-controller-manager-7f66df8485-cstc5    MountVolume.SetUp failed for volume "cert" : secret "webhook-server-cert" not found
2m10s       Warning   FailedMount         pod/sonataflow-operator-controller-manager-7f66df8485-cstc5    Unable to attach or mount volumes: unmounted volumes=[cert], unattached volumes=[cert kube-api-access-p8knw]: timed out waiting for the condition
4m27s       Warning   FailedMount         pod/sonataflow-operator-controller-manager-7f66df8485-cstc5    Unable to attach or mount volumes: unmounted volumes=[cert], unattached volumes=[kube-api-access-p8knw cert]: timed out waiting for the condition
15m         Normal    SuccessfulCreate    replicaset/sonataflow-operator-controller-manager-7f66df8485   Created pod: sonataflow-operator-controller-manager-7f66df8485-cstc5
15m         Normal    ScalingReplicaSet   deployment/sonataflow-operator-controller-manager              Scaled up replica set sonataflow-operator-controller-manager-7f66df8485 to 1

Reproducer:
minikube start --cpus 4 --memory 4096 --addons registry --addons metrics-server --insecure-registry "<IP_ADDRESS>/24" --insecure-registry "localhost:5000"

kubectl apply -f operator.yaml

@spolti the local installation must disable the certmanager by default. But users ought to have the option to enable it to mimic real cluster features. So our docs should reflect that. Thanks for verifying, @radtriste.

@radtriste did you see this: https://github.com/kiegroup/kogito-docs/pull/361/files#diff-905eed5405143ff0b5ef4025b84da595bbc0770b2c1353909979fb8204ac1d23R88

@spolti the local installation must disable the certmanager by default. But users ought to have the option to enable it to mimic real cluster features. So our docs should reflect that. Thanks for verifying, @radtriste.

I am now getting confused, should we have or not it by default?
To have it disabled in the manual installation, we might have two options, keep to versions of the operator.yaml,
or instruct users to remove things from the operator.yaml before running the kubectl create -f operator.yaml

@spolti my takes are:

Disable it by default with minikube/kind/local installations to avoid pressuring resources
Enable it by default in any other means

If users wish to add cert-manager locally to mimic production workloads, they could
Isn't the env var you introduced in main.go doing precisely that? Like dropping the webhook if set? If so, we can instruct users to install the operator.yaml via kustomize where we have a basis with and without certmanager.

@radtriste did you see this: https://github.com/kiegroup/kogito-docs/pull/361/files#diff-905eed5405143ff0b5ef4025b84da595bbc0770b2c1353909979fb8204ac1d23R88

Well I did not see it because you did not link it in the description :)
Let me review that

@spolti my takes are:

Disable it by default with minikube/kind/local installations to avoid pressuring resources
Enable it by default in any other means

If users wish to add cert-manager locally to mimic production workloads, they could
Isn't the env var you introduced in main.go doing precisely that? Like dropping the webhook if set? If so, we can instruct users to install the operator.yaml via kustomize where we have a basis with and without certmanager.

I think we should keep the enabled by defaut into the operator.yaml
but we need to document how to deactivate it if needed. A simple sed/awk before kubectl apply command  should do it IMO :)

@spolti my takes are:

Disable it by default with minikube/kind/local installations to avoid pressuring resources
Enable it by default in any other means

If users wish to add cert-manager locally to mimic production workloads, they could
Isn't the env var you introduced in main.go doing precisely that? Like dropping the webhook if set? If so, we can instruct users to install the operator.yaml via kustomize where we have a basis with and without certmanager.

I think we should keep the enabled by defaut into the operator.yaml but we need to document how to deactivate it if needed. A simple sed/awk before kubectl apply command should do it IMO :)

Yea, that works too.

updated this PR and the docs, please take a look.
It is enabled by default, the env is added in the Deployment and can be updated later.
However, the manual deletion of the webhooks is required, otherwise, the changes in the operator.yaml would be bigger than just a env.

Openshift tests job #454 was: ABORTED
Possible explanation: Most probably a timeout, please review
Please look here: https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/454/display/redirect
See console log:

Console Logs
openshift-network-diagnostics                      network-check-source-6777f6456-c6mmj                      1/1     Running     1 (35h ago)    35hopenshift-network-diagnostics                      network-check-target-9jglj                                1/1     Running     0              35hopenshift-network-diagnostics                      network-check-target-w9slw                                1/1     Running     0              2d5hopenshift-network-operator                         network-operator-85479f5f54-q2kl2                         1/1     Running     0              35hopenshift-operator-lifecycle-manager               catalog-operator-776c9687cd-6n6f4                         1/1     Running     1 (35h ago)    35hopenshift-operator-lifecycle-manager               collect-profiles-28223730-5w7sg                           0/1     Completed   0              36mopenshift-operator-lifecycle-manager               collect-profiles-28223745-sl8r6                           0/1     Completed   0              21mopenshift-operator-lifecycle-manager               collect-profiles-28223760-kvscj                           0/1     Completed   0              6m19sopenshift-operator-lifecycle-manager               olm-operator-6494d89b4b-5xlpd                             1/1     Running     0              35hopenshift-operator-lifecycle-manager               package-server-manager-579d664b8c-95dpf                   1/1     Running     1 (35h ago)    35hopenshift-operator-lifecycle-manager               packageserver-797f4bfc55-6pw6n                            1/1     Running     0              35hopenshift-operator-lifecycle-manager               packageserver-797f4bfc55-fwxhj                            1/1     Running     0              2d5hopenshift-roks-metrics                             metrics-8648788446-jj5lq                                  1/1     Running     0              35hopenshift-roks-metrics                             push-gateway-847c64ccd-sr29h                              1/1     Running     0              35hopenshift-service-ca-operator                      service-ca-operator-5f9d6459d5-l89zw                      1/1     Running     0              35hopenshift-service-ca                               service-ca-665db46585-jfwwh                               1/1     Running     0              35htigera-operator                                    tigera-operator-97b64f5bd-n5qtd                           1/1     Running     0              35h[Pipeline] }[Pipeline] // scriptPost stage[Pipeline] archiveArtifactsArchiving artifacts[Pipeline] junitRecording test resultsNone of the test reports contained any result[Checks API] No suitable checks publisher found.[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // timeout[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withEnv[Pipeline] }Lock released on resource [Sonataflow Operator OpenShift tests https://c107-e.us-south.containers.cloud.ibm.com:30353]No test report files were found. Configuration error?[Pipeline] // lock[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/454/api/json[Pipeline] readJSON[Pipeline] sh+ wget --no-check-certificate -qO - https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/454/consoleText+ tail -n 50

Still issue when deploying in a fresh minikube with no cert-manager.
Events give me:
0s         Warning   FailedMount         pod/kogito-serverless-operator-controller-manager-7cf48956c7-5rcrl    MountVolume.SetUp failed for volume "cert" : secret "webhook-server-cert" not found

and the operator pod stay in ContainerCreating state ...
Changing the whole operator yaml file seems a bit complex or ?
Maybe we should simply have 2 operator yaml files. One with cert and one without... wdyt ?

@radtriste I'd rather have one with kustomize instead. And instruct users to kubectl kustomize install-operator-no-cert instead.

@radtriste I'd rather have one with kustomize instead. And instruct users to kubectl kustomize install-operator-no-cert instead.

well the user does not have the repository on its machine. The user just want to deploy the operator.
Using kustomize could be cumbersome. Unless you have an easy solution

the easiest way is to have two operator.yaml, imho.
I guess we, during the builds, or as part of the generate-all, could leverage on kustomize, or at least, handle the webhooks removal manually.

@radtriste I'd rather have one with kustomize instead. And instruct users to kubectl kustomize install-operator-no-cert instead.

well the user does not have the repository on its machine. The user just want to deploy the operator. Using kustomize could be cumbersome. Unless you have an easy solution

Well, we can always release a shell script to execute this.

@ricardozanini @radtriste please take a look on my last commit.
I've added a new operator-no-webhooks.yaml generated as part of the generate-deploy make goal.
This way, the end user can just choose which option he want to deploy, with or without weebhooks.
Will update the docs once we define which approach we will take.
Thanks.

Openshift tests job #456 was: ABORTED
Possible explanation: Most probably a timeout, please review
Please look here: https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/456/display/redirect
See console log:

Console Logs
[2/2] STEP 4/10: LABEL             description="Runtime Image for the Operator"             io.cekit.version="4.7.0"             summary="Runtime Image for the Operator"[2/2] STEP 5/10: USER root[2/2] STEP 6/10: RUN [ ! -d /tmp/scripts ] || rm -rf /tmp/scripts[2/2] STEP 7/10: RUN [ ! -d /tmp/artifacts ] || rm -rf /tmp/artifacts[2/2] STEP 8/10: USER 1001[2/2] STEP 9/10: WORKDIR /usr/local/bin[2/2] STEP 10/10: ENTRYPOINT ["manager"][2/2] COMMIT kogito-serverless-operator:2.0.0-snapshotGetting image source signaturesCopying blob sha256:3726658997cfb51a242134316fd6b8c992d27befbedc2dea609e2e55fbc320caCopying blob sha256:c886d9eb053cc5adc0034c6231ad0ec8acd87134fe3aa26f07d020582b67f767Copying config sha256:db24697ce2337dae4737d2556ee81b5af84776c90552258162bce8f080bbe7d8Writing manifest to image destinationStoring signatures--> db24697ce23Successfully tagged localhost/kogito-serverless-operator:2.0.0-snapshotSuccessfully tagged localhost/kogito-serverless-operator:latestAborted by unknownSending interrupt signal to process2023-09-01 19:36:59,734 podman.py:62         INFO  Image built and available under following tags: kogito-serverless-operator:2.0.0-snapshot, kogito-serverless-operator:latest2023-09-01 19:36:59,734 cli.py:501        INFO  Finished!make: *** [Makefile:187: container-build] Terminatedscript returned exit code 2[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Push image to Openshift Registry)Stage "Push image to Openshift Registry" skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Run e2e tests)Stage "Run e2e tests" skipped due to earlier failure(s)[Pipeline] stage[Pipeline] { (Running e2e tests)Stage "Run e2e tests" skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/456/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

@spolti thakns! can we also update the pipelines to publish to the releases these two options?

@spolti This would be adding a line there: https://github.com/spolti/kogito-serverless-operator/blob/KOGITO-7840-1/.ci/jenkins/Jenkinsfile.promote#L134
Also don't forget to update the docs ? :)

Added, thanks @tristan

Openshift tests job #470 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/470/display/redirect
See console log:

Console Logs
openshift-network-diagnostics                      network-check-source-8dd86ffb8-sxncz                     1/1     Running     0              3d1hopenshift-network-diagnostics                      network-check-target-br8rb                               1/1     Running     0              3d1hopenshift-network-diagnostics                      network-check-target-nx69w                               1/1     Running     0              3d1hopenshift-network-operator                         network-operator-74c7887bbd-9kfgn                        1/1     Running     0              3d1hopenshift-operator-lifecycle-manager               catalog-operator-756784f445-s8b78                        1/1     Running     0              3d1hopenshift-operator-lifecycle-manager               collect-profiles-28236315-hdwbs                          0/1     Completed   0              41mopenshift-operator-lifecycle-manager               collect-profiles-28236330-hvbnh                          0/1     Completed   0              26mopenshift-operator-lifecycle-manager               collect-profiles-28236345-tqsbh                          0/1     Completed   0              11mopenshift-operator-lifecycle-manager               olm-operator-695bd458c6-fjrbj                            1/1     Running     0              3d1hopenshift-operator-lifecycle-manager               package-server-manager-54dcf5867b-n5n4h                  1/1     Running     0              3d1hopenshift-operator-lifecycle-manager               packageserver-7666dc767d-gmpzs                           1/1     Running     0              3d1hopenshift-operator-lifecycle-manager               packageserver-7666dc767d-vwx74                           1/1     Running     0              3d1hopenshift-roks-metrics                             metrics-87697f956-njbzv                                  1/1     Running     0              3d1hopenshift-roks-metrics                             push-gateway-6b7b6bf464-27xf4                            1/1     Running     0              3d1hopenshift-service-ca-operator                      service-ca-operator-7848cb967d-csc58                     1/1     Running     0              3d1hopenshift-service-ca                               service-ca-6bf49cb844-xswpn                              1/1     Running     0              3d1htigera-operator                                    tigera-operator-54b676968d-5tzpl                         1/1     Running     0              3d1h[Pipeline] }[Pipeline] // scriptPost stage[Pipeline] archiveArtifactsArchiving artifacts‘test/logs/**/*.log’ doesn’t match anything: ‘test’ exists but not ‘test/logs/**/*.log’No artifacts found that match the file pattern "test/logs/**/*.log". Configuration error?[Pipeline] junitRecording test resultsNone of the test reports contained any result[Checks API] No suitable checks publisher found.[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // timeout[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withEnv[Pipeline] }Lock released on resource [Sonataflow Operator OpenShift tests https://c107-e.us-south.containers.cloud.ibm.com:30353][Pipeline] // lock[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/470/api/json?depth=0'[Pipeline] readJSON[Pipeline] shNo test report files were found. Configuration error?

Openshift tests job #474 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/474/display/redirect
See console log:

Console Logs
openshift-network-diagnostics                      network-check-source-8dd86ffb8-sxncz                     1/1     Running             0              3d3hopenshift-network-diagnostics                      network-check-target-br8rb                               1/1     Running             0              3d3hopenshift-network-diagnostics                      network-check-target-nx69w                               1/1     Running             0              3d3hopenshift-network-operator                         network-operator-74c7887bbd-9kfgn                        1/1     Running             0              3d3hopenshift-operator-lifecycle-manager               catalog-operator-756784f445-s8b78                        1/1     Running             0              3d3hopenshift-operator-lifecycle-manager               collect-profiles-28236435-l27z8                          0/1     Completed           0              31mopenshift-operator-lifecycle-manager               collect-profiles-28236450-rnpwj                          0/1     Completed           0              16mopenshift-operator-lifecycle-manager               collect-profiles-28236465-c8ss4                          0/1     Completed           0              111sopenshift-operator-lifecycle-manager               olm-operator-695bd458c6-fjrbj                            1/1     Running             0              3d3hopenshift-operator-lifecycle-manager               package-server-manager-54dcf5867b-n5n4h                  1/1     Running             0              3d3hopenshift-operator-lifecycle-manager               packageserver-7666dc767d-gmpzs                           1/1     Running             0              3d3hopenshift-operator-lifecycle-manager               packageserver-7666dc767d-vwx74                           1/1     Running             0              3d3hopenshift-roks-metrics                             metrics-87697f956-njbzv                                  1/1     Running             0              3d3hopenshift-roks-metrics                             push-gateway-6b7b6bf464-27xf4                            1/1     Running             0              3d3hopenshift-service-ca-operator                      service-ca-operator-7848cb967d-csc58                     1/1     Running             0              3d3hopenshift-service-ca                               service-ca-6bf49cb844-xswpn                              1/1     Running             0              3d3htigera-operator                                    tigera-operator-54b676968d-5tzpl                         1/1     Running             0              3d3h[Pipeline] }[Pipeline] // scriptPost stage[Pipeline] archiveArtifactsArchiving artifacts‘test/logs/**/*.log’ doesn’t match anything: ‘test’ exists but not ‘test/logs/**/*.log’No artifacts found that match the file pattern "test/logs/**/*.log". Configuration error?[Pipeline] junitRecording test resultsNone of the test reports contained any result[Checks API] No suitable checks publisher found.[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // timeout[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withEnv[Pipeline] }Lock released on resource [Sonataflow Operator OpenShift tests https://c107-e.us-south.containers.cloud.ibm.com:30353][Pipeline] // lock[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/474/api/json?depth=0'[Pipeline] readJSON[Pipeline] shNo test report files were found. Configuration error?

Jenkins retest this

Openshift tests job #475 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/475/display/redirect
See console log:

Console Logs
openshift-network-diagnostics                      network-check-source-8dd86ffb8-sxncz                     1/1     Running     0              3d4hopenshift-network-diagnostics                      network-check-target-br8rb                               1/1     Running     0              3d4hopenshift-network-diagnostics                      network-check-target-nx69w                               1/1     Running     0              3d4hopenshift-network-operator                         network-operator-74c7887bbd-9kfgn                        1/1     Running     0              3d4hopenshift-operator-lifecycle-manager               catalog-operator-756784f445-s8b78                        1/1     Running     0              3d4hopenshift-operator-lifecycle-manager               collect-profiles-28236495-p4qvw                          0/1     Completed   0              39mopenshift-operator-lifecycle-manager               collect-profiles-28236510-qcjhc                          0/1     Completed   0              24mopenshift-operator-lifecycle-manager               collect-profiles-28236525-d9h6t                          0/1     Completed   0              9m54sopenshift-operator-lifecycle-manager               olm-operator-695bd458c6-fjrbj                            1/1     Running     0              3d4hopenshift-operator-lifecycle-manager               package-server-manager-54dcf5867b-n5n4h                  1/1     Running     0              3d4hopenshift-operator-lifecycle-manager               packageserver-7666dc767d-gmpzs                           1/1     Running     0              3d4hopenshift-operator-lifecycle-manager               packageserver-7666dc767d-vwx74                           1/1     Running     0              3d4hopenshift-roks-metrics                             metrics-87697f956-njbzv                                  1/1     Running     0              3d4hopenshift-roks-metrics                             push-gateway-6b7b6bf464-27xf4                            1/1     Running     0              3d4hopenshift-service-ca-operator                      service-ca-operator-7848cb967d-csc58                     1/1     Running     0              3d4hopenshift-service-ca                               service-ca-6bf49cb844-xswpn                              1/1     Running     0              3d4htigera-operator                                    tigera-operator-54b676968d-5tzpl                         1/1     Running     0              3d4h[Pipeline] }[Pipeline] // scriptPost stage[Pipeline] archiveArtifactsArchiving artifacts‘test/logs/**/*.log’ doesn’t match anything: ‘test’ exists but not ‘test/logs/**/*.log’No artifacts found that match the file pattern "test/logs/**/*.log". Configuration error?[Pipeline] junitRecording test resultsNone of the test reports contained any result[Checks API] No suitable checks publisher found.[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // timeout[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withEnv[Pipeline] }Lock released on resource [Sonataflow Operator OpenShift tests https://c107-e.us-south.containers.cloud.ibm.com:30353][Pipeline] // lock[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/475/api/json?depth=0'[Pipeline] readJSONNo test report files were found. Configuration error?[Pipeline] sh

Openshift tests job #476 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/476/display/redirect
See console log:

Console Logs
openshift-network-diagnostics                      network-check-source-8dd86ffb8-sxncz                     1/1     Running     0              3d6hopenshift-network-diagnostics                      network-check-target-br8rb                               1/1     Running     0              3d6hopenshift-network-diagnostics                      network-check-target-nx69w                               1/1     Running     0              3d6hopenshift-network-operator                         network-operator-74c7887bbd-9kfgn                        1/1     Running     0              3d6hopenshift-operator-lifecycle-manager               catalog-operator-756784f445-s8b78                        1/1     Running     0              3d6hopenshift-operator-lifecycle-manager               collect-profiles-28236615-z75vx                          0/1     Completed   0              37mopenshift-operator-lifecycle-manager               collect-profiles-28236630-6b6vr                          0/1     Completed   0              22mopenshift-operator-lifecycle-manager               collect-profiles-28236645-mkncb                          0/1     Completed   0              7m19sopenshift-operator-lifecycle-manager               olm-operator-695bd458c6-fjrbj                            1/1     Running     0              3d6hopenshift-operator-lifecycle-manager               package-server-manager-54dcf5867b-n5n4h                  1/1     Running     0              3d6hopenshift-operator-lifecycle-manager               packageserver-7666dc767d-gmpzs                           1/1     Running     0              3d6hopenshift-operator-lifecycle-manager               packageserver-7666dc767d-vwx74                           1/1     Running     0              3d6hopenshift-roks-metrics                             metrics-87697f956-njbzv                                  1/1     Running     0              3d6hopenshift-roks-metrics                             push-gateway-6b7b6bf464-27xf4                            1/1     Running     0              3d6hopenshift-service-ca-operator                      service-ca-operator-7848cb967d-csc58                     1/1     Running     0              3d6hopenshift-service-ca                               service-ca-6bf49cb844-xswpn                              1/1     Running     0              3d6htigera-operator                                    tigera-operator-54b676968d-5tzpl                         1/1     Running     0              3d6h[Pipeline] }[Pipeline] // scriptPost stage[Pipeline] archiveArtifactsArchiving artifacts‘test/logs/**/*.log’ doesn’t match anything: ‘test’ exists but not ‘test/logs/**/*.log’No artifacts found that match the file pattern "test/logs/**/*.log". Configuration error?[Pipeline] junitRecording test resultsNone of the test reports contained any result[Checks API] No suitable checks publisher found.[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // timeout[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withEnv[Pipeline] }Lock released on resource [Sonataflow Operator OpenShift tests https://c107-e.us-south.containers.cloud.ibm.com:30353][Pipeline] // lock[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)No test report files were found. Configuration error?[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/476/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

Openshift tests job #477 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/477/display/redirect
See console log:

Console Logs
openshift-network-diagnostics                      network-check-target-nx69w                                1/1     Running       0              3d7hopenshift-network-operator                         network-operator-74c7887bbd-9kfgn                         1/1     Running       0              3d7hopenshift-operator-lifecycle-manager               catalog-operator-756784f445-s8b78                         1/1     Running       0              3d7hopenshift-operator-lifecycle-manager               collect-profiles-28236690-xkssg                           0/1     Completed     0              40mopenshift-operator-lifecycle-manager               collect-profiles-28236705-wzp9q                           0/1     Completed     0              25mopenshift-operator-lifecycle-manager               collect-profiles-28236720-t9ngr                           0/1     Completed     0              10mopenshift-operator-lifecycle-manager               olm-operator-695bd458c6-fjrbj                             1/1     Running       0              3d7hopenshift-operator-lifecycle-manager               package-server-manager-54dcf5867b-n5n4h                   1/1     Running       0              3d7hopenshift-operator-lifecycle-manager               packageserver-7666dc767d-gmpzs                            1/1     Running       0              3d7hopenshift-operator-lifecycle-manager               packageserver-7666dc767d-vwx74                            1/1     Running       0              3d7hopenshift-roks-metrics                             metrics-87697f956-njbzv                                   1/1     Running       0              3d7hopenshift-roks-metrics                             push-gateway-6b7b6bf464-27xf4                             1/1     Running       0              3d7hopenshift-service-ca-operator                      service-ca-operator-7848cb967d-csc58                      1/1     Running       0              3d7hopenshift-service-ca                               service-ca-6bf49cb844-xswpn                               1/1     Running       0              3d7hsonataflow-operator-system                         greeting-1-build                                          1/1     Terminating   0              2m23ssonataflow-operator-system                         sonataflow-operator-controller-manager-86b5fff7dd-m7bgt   2/2     Terminating   0              2m33stigera-operator                                    tigera-operator-54b676968d-5tzpl                          1/1     Running       0              3d7h[Pipeline] }[Pipeline] // scriptPost stage[Pipeline] archiveArtifactsArchiving artifacts‘test/logs/**/*.log’ doesn’t match anything: ‘test’ exists but not ‘test/logs/**/*.log’No artifacts found that match the file pattern "test/logs/**/*.log". Configuration error?[Pipeline] junitRecording test resultsNone of the test reports contained any result[Checks API] No suitable checks publisher found.[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // timeout[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withEnv[Pipeline] }Lock released on resource [Sonataflow Operator OpenShift tests https://c107-e.us-south.containers.cloud.ibm.com:30353][Pipeline] // lock[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/477/api/json?depth=0'[Pipeline] readJSON[Pipeline] shNo test report files were found. Configuration error?

Openshift tests job #478 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/478/display/redirect
See console log:

Console Logs
openshift-network-operator                         network-operator-74c7887bbd-9kfgn                         1/1     Running       0              3d8hopenshift-operator-lifecycle-manager               catalog-operator-756784f445-s8b78                         1/1     Running       0              3d8hopenshift-operator-lifecycle-manager               collect-profiles-28236720-t9ngr                           0/1     Completed     0              32mopenshift-operator-lifecycle-manager               collect-profiles-28236735-lnddm                           0/1     Completed     0              17mopenshift-operator-lifecycle-manager               collect-profiles-28236750-bwsct                           0/1     Completed     0              2m18sopenshift-operator-lifecycle-manager               olm-operator-695bd458c6-fjrbj                             1/1     Running       0              3d8hopenshift-operator-lifecycle-manager               package-server-manager-54dcf5867b-n5n4h                   1/1     Running       0              3d8hopenshift-operator-lifecycle-manager               packageserver-7666dc767d-gmpzs                            1/1     Running       0              3d8hopenshift-operator-lifecycle-manager               packageserver-7666dc767d-vwx74                            1/1     Running       0              3d8hopenshift-roks-metrics                             metrics-87697f956-njbzv                                   1/1     Running       0              3d8hopenshift-roks-metrics                             push-gateway-6b7b6bf464-27xf4                             1/1     Running       0              3d8hopenshift-service-ca-operator                      service-ca-operator-7848cb967d-csc58                      1/1     Running       0              3d8hopenshift-service-ca                               service-ca-6bf49cb844-xswpn                               1/1     Running       0              3d8hsonataflow-operator-system                         event-listener-d9b786799-ffx8l                            1/1     Running       0              5m30ssonataflow-operator-system                         orderprocessing-775f9b78db-nw6mj                          0/1     Terminating   0              5m30ssonataflow-operator-system                         sonataflow-operator-controller-manager-86b5fff7dd-4tnvg   2/2     Terminating   0              9m40stigera-operator                                    tigera-operator-54b676968d-5tzpl                          1/1     Running       0              3d8h[Pipeline] }[Pipeline] // scriptPost stage[Pipeline] archiveArtifactsArchiving artifacts‘test/logs/**/*.log’ doesn’t match anything: ‘test’ exists but not ‘test/logs/**/*.log’No artifacts found that match the file pattern "test/logs/**/*.log". Configuration error?[Pipeline] junitRecording test resultsNone of the test reports contained any result[Checks API] No suitable checks publisher found.[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // timeout[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withEnv[Pipeline] }Lock released on resource [Sonataflow Operator OpenShift tests https://c107-e.us-south.containers.cloud.ibm.com:30353][Pipeline] // lock[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] shNo test report files were found. Configuration error?+ wget --no-check-certificate -qO - 'https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/478/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

Openshift tests job #484 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/484/display/redirect
See console log:

Console Logs
openshift-network-diagnostics                      network-check-target-nx69w                                1/1     Running       0              6d4hopenshift-network-operator                         network-operator-74c7887bbd-9kfgn                         1/1     Running       1 (25h ago)    6d4hopenshift-operator-lifecycle-manager               catalog-operator-756784f445-s8b78                         1/1     Running       0              6d5hopenshift-operator-lifecycle-manager               collect-profiles-28240845-w4qcs                           0/1     Completed     0              38mopenshift-operator-lifecycle-manager               collect-profiles-28240860-v57mg                           0/1     Completed     0              23mopenshift-operator-lifecycle-manager               collect-profiles-28240875-pgph6                           0/1     Completed     0              8m19sopenshift-operator-lifecycle-manager               olm-operator-695bd458c6-fjrbj                             1/1     Running       0              6d5hopenshift-operator-lifecycle-manager               package-server-manager-54dcf5867b-n5n4h                   1/1     Running       0              6d5hopenshift-operator-lifecycle-manager               packageserver-7666dc767d-gmpzs                            1/1     Running       0              6d4hopenshift-operator-lifecycle-manager               packageserver-7666dc767d-vwx74                            1/1     Running       0              6d4hopenshift-roks-metrics                             metrics-87697f956-njbzv                                   1/1     Running       0              6d5hopenshift-roks-metrics                             push-gateway-6b7b6bf464-27xf4                             1/1     Running       0              6d5hopenshift-service-ca-operator                      service-ca-operator-7848cb967d-csc58                      1/1     Running       1 (25h ago)    6d5hopenshift-service-ca                               service-ca-6bf49cb844-dgt2j                               1/1     Running       0              25hsonataflow-operator-system                         orderprocessing-775f9b78db-bjjkn                          1/1     Terminating   0              2m10ssonataflow-operator-system                         sonataflow-operator-controller-manager-86b5fff7dd-v4bz5   2/2     Terminating   0              6m26stigera-operator                                    tigera-operator-54b676968d-5tzpl                          1/1     Running       0              6d5h[Pipeline] }[Pipeline] // scriptPost stage[Pipeline] archiveArtifactsArchiving artifacts‘test/logs/**/*.log’ doesn’t match anything: ‘test’ exists but not ‘test/logs/**/*.log’No artifacts found that match the file pattern "test/logs/**/*.log". Configuration error?[Pipeline] junitRecording test resultsNone of the test reports contained any result[Checks API] No suitable checks publisher found.[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // timeout[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withEnv[Pipeline] }Lock released on resource [Sonataflow Operator OpenShift tests https://c107-e.us-south.containers.cloud.ibm.com:30353][Pipeline] // lock[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-serverless-operator-PR-check/484/api/json?depth=0'[Pipeline] readJSON[Pipeline] shNo test report files were found. Configuration error?

@ricardozanini @MarianMacik finally green :)
Feel free to merge.

@spolti Looks good now. About the e2e tests, we could have the tests setup in the BeforeAll function unless your intention was to have the applying of the CRDs as a dedicated test.

The way it was before was causing some sort of race condition between the main test and the no-webhooks test, if A started before, then when it finished the B would fail and vice-verse, it because the namespace was not getting cleaned after the first test was finished, the beforeAll in this case, would only clean the env after everything was finished, and it was not what was needed in this case.

The way it was before was causing some sort of race condition between the main test and the no-webhooks test, if A started before, then when it finished the B would fail and vice-verse, it because the namespace was not getting cleaned after the first test was finished, the beforeAll in this case, would only clean the env after everything was finished, and it was not what was needed in this case.

@spolti
Yes, before everything was in one ordered section, now each of those is in one serial section, so they are mutually exclusive. I was thinking about putting the setup inside the ordered section now, so basically It("Prepare the environment", func() { would be changed to BeforeAll(func() {, nothing else. The serial part now guarantees that the tests will not run concurrently and BeforeAll would be run just inside the context of the ordered section, same as AfterAll is now being executed.

@spolti Looks good now. About the e2e tests, we could have the tests setup in the BeforeAll function unless your intention was to have the applying of the CRDs as a dedicated test.

The way it was before was causing some sort of race condition between the main test and the no-webhooks test, if A started before, then when it finished the B would fail and vice-verse, it because the namespace was not getting cleaned after the first test was finished, the beforeAll in this case, would only clean the env after everything was finished, and it was not what was needed in this case.

I meant, the AfterAll, not the BeforeAll :)
sry for the typo

@spolti so do we want to change it or are we ok with the current state?

I am ok with the current state.
but let's hear from others.

@MarianMacik @spolti I think we can merge as it is to unlock and later @MarianMacik can you send the PR to replace with BDD?

@ricardozanini anything to do with this PR?

Another case of many features/collaborators working on the code base. This introduces a fairly need and complex setup for local dev.

To reimplement on kie-tools


Gracefully handle v8flags failure?

Related to https://github.com/shipitjs/shipit/issues/70 and https://github.com/tkellen/js-v8flags/issues/13 , if HOME is not accessible, this can cause upstream modules that require liftoff to fail (even if they don't explicitly need any specific v8flags).
Is it possible to issue a warning and keep going if v8flags fails for some reason? The specific case I ran into today is where the uid executing the node process doesn't have access to the $HOME directory.

Would you mind opening this issue on v8flags? This definitely needs to be addressed there. I have a few ideas for how we can resolve this!

Yeah! Thanks for positivity.


It takes too long time of loading network weight files on RV1126

Hello, I've noticed something peculiar.
I ran the ResNet50 and ResNet100 network on RV1126. The network file was converted from ONNX to RKNN file quantized to FP16/INT8 using the rknn visualization toolkit.
I used the rknpu C API on RV1126 and loaded the file using rknn_init.
I measured the time taken by rknn_init, and it's taking much longer than expected to load ResNet.
However, when tested on other rockchip devices like RK3568, initialization completes within a few seconds.
[rknn_init working time at RV1126]
Loading Resnet100(FP16): avg 37.9 sec
Loading Resnet100(INT8): avg 131.6 sec
Loading Resnet50(INT8): avg 81.0 sec
[rknn_init working time at RK3568]
Loading Resnet100(FP16): avg 6.1 sec
Loading Resnet100(INT8): avg 3.4 sec
I understand that RK3568 has a higher-performance processor than RV1126.
However, there is a significant difference in initialization time, with a 6x difference for FP16 and a 92x difference for INT8. Additionally, it's peculiar that loading an INT8 model takes longer than FP16 on RV1126.
What could be the cause of this phenomenon?
Is it due to the performance difference between CPUs (A7 vs A55)? Or could it be a problem during model conversion or when using the rknpu API?
This is part of my code for loading
std::string model_rk = r50.rknn;
std::ifstream in_file(model_rk, std::ios::binary);
std::streampos begin, end;
in_file.seekg(0, std::ios::end);
end = in_file.tellg();
size_t size = end - begin;

in_file.seekg(0, std::ios::beg);

engine_data.resize(size, 'c');
in_file.read((char*)engine_data.data(), size);
in_file.close();

const char* param_m = reinterpret_cast<const char*>(engine_data.c_str());
ret = rknn_init(&this->ctx, (void*)param_m, size, 0, NULL);
if(ret < 0)
{
    printf("%s - Fail to create p-model : %d\n", __FUNCTION__, ret);
    return false;
}

Please provide an explanation for this phenomenon.

Your network weight files may not be precompiled


Interacting with contract method not working

Hi,
When I try to interact with contract it does not working.
    let formattedKey = PrivateKey.trimmingCharacters(in: .whitespacesAndNewlines)
    let dataKey = Data.fromHex(formattedKey)!
    let keystore = try! EthereumKeystoreV3(privateKey: dataKey, password: "")!
    let keystoreManager = KeystoreManager([keystore])
    web3.addKeystoreManager(keystoreManager)

    guard let contract = web3.contract(abiString, at: EthereumAddress("0xc6E070BCb7823E483164bB41D2297DCd8b1FAb25"), abiVersion: 2) else {
        return
    }

   print("contract methods", contract.method())

   It does not comes to print the contract methods..it stops working by return.

    My contract ABI: https://api-testnet.bscscan.com/api?module=contract&action=getabi&address=0xc6E070BCb7823E483164bB41D2297DCd8b1FAb25&apikey=

  Please help to find the solution

Hello.
In order to make debug process easier: Please specify full code with Networks.Custom(networkID: BigUInt(networkID) initialisation.
As I can see you are interacting with the BSC chain. I didn't test it. And BSC is out of my scope of interests. So I would be happy t merge PR with this fix.

Hi @skywinder ,
RpcUrl: https://data-seed-prebsc-1-s1.binance.org:8545/
Chain ID: Networks.Custom(networkID: 0x61)

I can able to connect with BSC. I can able to send bsc and bep20 tokens.
But cant able interact with dynamic contract method.

Please support with any solution..

Thanks

Yeah Its likely chain ID. You need to set it before the tx if you are using a private chain.
transaction?.transaction.UNSAFE_setChainID(Ennvironment.ethNetworkID)

Are you still having trouble with this?

@dangell7 yes..I cant interact with BEP20 tokens.


Version 3.1.3

:+1:
I'll deprecate my wrapper package in favour of your new and shiny package this weekend :stuck_out_tongue_closed_eyes:

Thank you. Wouldn't have been able to do it without you!

No problem, glad to help. We need to get dem nice libraries for Meteor too :shipit:

Well, I am happy to support as much as I can. I just need help with the learning curve of setting everything up. Meteor is going to be easy because of the http://autopublish.meteor.com/. Which is great because it takes one less thing off my mind when updating.


--set-default-version success message

Very small UX change. When running --set-default-version it returns:

For information on key differences with WSL 2 please visit https://aka.ms/wsl2"

Would have been nice to see a confirmation of change:

Default WSL version set to: 2
For information on key differences with WSL 2 please visit https://aka.ms/wsl2"

When I read this message I immediately thought that it has silently failed and I needed to go to the URL to find out more.

So if I got this
PS C:\Windows\system32>  wsl --set-default-version 2
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
PS C:\Windows\system32>

That means it's a success message and not an error message?
I spend hours thinking it’s an error message and searching tech forums trying to solve my problem.

Exactly! I did the same, hence the request

Even I was thinking the same, that's why I had raised this issue.
Can you check what does it output when your run:
wsl -l -v

For me it's says:

It's says:
PS C:\Windows\system32> wsl -l -v
  NAME            STATE           VERSION
* Ubuntu-20.04    Running         2
PS C:\Windows\system32>


Indicate which button is selected in Sidebar

Hi,
I was wondering if we could indicate with button on the sidebar was currently selected

Totally, but it's not the responsibility of React Sidebar but of the parent component that is rendering React Sidebar and is passing down the sidebar content.

Cool, can you explain how we could do it?


Initialize collection manually

Is your feature request related to a problem? Please describe.
I have two entities:
@Entity({ tableName: "artist" })
export default class ArtistEntity {
    @PrimaryKey()
    public id!: number;

    @ManyToMany(() => StyleEntity, undefined, { owner: true })
    public styles: Collection<StyleEntity>;

    public constructor() {
        this.styles = new Collection(this);
    }
}

@Entity({ tableName: "style" })
export default class StyleEntity {
    @PrimaryKey()
    public id!: number;

    @ManyToMany(() => ArtistEntity, "styles")
    public artists: Collection<ArtistEntity>;

    public constructor() {
        this.artists = new Collection(this);
    }
}

Now I want do requests to get some artists, but optionally with their related styles.
So, I first query to get some artists, calling to findList:
export default class ArtistStore {
    private artistRepository: EntityRepository<ArtistEntity>;

    public constructor(ormClient: OrmClient) {
        this.artistRepository = ormClient.em.getRepository(ArtistEntity);
    }

    public async findList(limit: number, cursor?: ArtistStoreCursor): Promise<ArtistEntity[]> {
        const query = this.artistRepository.createQueryBuilder().select("*");

        if (cursor) {
            query.where({ created: { $lte: cursor.created } });
            query.andWhere({ $or: [{ created: { $lt: cursor.created } }, { id: { $lt: cursor.id } }] });
        }

        return query.orderBy({ created: "desc", id: "desc" }).limit(limit).getResult();
    }

And if in the request I specify that too want the styles then I call to findArtists:
export default class StyleStore {
    private ormClient: OrmClient;
    private connection: AbstractSqlConnection;
    private styleRepository: EntityRepository<StyleEntity>;

    public constructor(ormClient: OrmClient) {
        this.ormClient = ormClient;
        this.connection = ormClient.em.getConnection("read");
        this.styleRepository = ormClient.em.getRepository(StyleEntity);
    }

    public async findArtists(artists: (number | string)[]): Promise<StyleEntity[]> {
        const results = await this.connection.execute(
            `select e0.*, e1.artist_id from style as e0
                left join artist_styles as e1 on e0.id = e1.style_id
            where e1.artist_id in (?)`,
            [artists],
        );

        const entities = results.map((result) => {
            const entity = this.styleRepository.map(result);

            entity.artists.add(this.ormClient.em.getReference("ArtistEntity", result.artist_id));

            return entity;
        });

        console.log(entities[0]);
        console.log(entities[0].artists.toArray());
        console.log(entities[0].artists.getIdentifiers());
        console.log(entities[0].artists.getItems());

        return [];
    }
}

I get output from the first console.log(entities[0]):
StyleEntity {
  id: 4,
  artists: Collection {
    '0': ArtistEntity {
      id: 5,
      styles: [Collection],
    },
    initialized: false,
    dirty: true
  },
  name: 'Lettering'
}

But not from console.log(entities[0].artists.toArray()), console.log(entities[0].artists.getIdentifiers()) or console.log(entities[0].artists.getItems()).
Describe the solution you'd like
Something to permit relate data in ManyToMany without require do more requests to the database when all the data already is loaded.
Describe alternatives you've considered
I can't found a way to do it.

entity.artists.add(this.ormClient.em.getReference("ArtistEntity", result.artist_id));

This is probably the line that is causing the problem - you cannot add a reference (not-loaded entity) and expect it to be somehow automatically populated. This is exactly what you see in the console log - there is an ArtistEntity with ID 5, and I am almost certain that its the same as you add via em.getReference(), as it has only the PK (I believe your actual ArtistEntity has some other props like name, right?). And it is not loaded yet in given context.
In general you are doing it wrong, using Collection.add() is for adding new items to existing collections, that will never have an effect on what gets populated in the JSON response. As you can see in the console log, the collection is not initialized.

Something to permit relate data in ManyToMany without require do more requests to the database when all the data already is loaded.

The right method to use is Collection.hydrate() - it is how the collection are hydrated internally. I am not sure if we had that method in v3, as well as I am not sure what version you are using, but no plans to change anything in v3 anyway...
You will probably also need to mark it as populated to be in the JSON response, via Collection.populated().
I don't really understand why you are using raw query for this, as this can be done easily with the EM api, where all the mapping would be handled automatically for you.
// this should issue the very same query as you have (at least in v4), and map it automatically
const styles = await em.find(StyleEntity, { artists: [1, 2, 3] });

Same with the findList method, I don't see a reason why you are using QB there.
But even with that, you would still end up with not initialized collections, resulting in the same behaviour, you still need to use the Collection.hydrate() and Collection.populated().
Anyway this looks like you are trying to build things that others already did, so you might want to take a look at existing solutions, e.g. #364 or look into the dependent packages, there are some starter projects for graphql, like this one https://github.com/dougg0k/nodejs_graphql_typescript_starter
I am not a graphql user, so can't help with that, but it would be helpful (for both of us), if you try to omit the GQL part from the reproduction code - you would most probably understand yourself what is happening and why. It's fine to give an example with the resolvers, but you should try to replicate the problem calling it directly, without dataloader in the background. That is the bit that is missing in your description, there is no control code, just few methods, without the context.

This is probably the line that is causing the problem - you cannot add a reference (not-loaded entity) and expect it to be somehow automatically populated. This is exactly what you see in the console log - there is an ArtistEntity with ID 5, and I am almost certain that its the same as you add via em.getReference(), as it has only the PK (I believe your actual ArtistEntity has some other props like name, right?). And it is not loaded yet in given context.

I use a reference because I am sure the entity is already loaded. It show all the props, not only the PK:
StyleEntity {
  id: 4,
  artists: Collection {
    '0': ArtistEntity {
      id: 5,
      styles: [Collection],
      website: 'https://forbes.com',
      instagram: 'http://wufoo.com',
      facebook: 'http://msu.edu',
      created: 2020-02-05T12:30:30.000Z,
      updated: 2020-03-03T12:30:30.000Z,
      about: 'Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Imperdiet nulla malesuada pellentesque elit eget. Amet purus gravida quis blandit turpis cursus in hac habitasse. Pellentesque dignissim enim sit amet venenatis urna cursus eget. Ut pharetra sit amet aliquam. In hac habitasse platea dictumst. Imperdiet nulla malesuada pellentesque elit eget gravida. Massa tempor nec feugiat nisl pretium fusce. Vitae tortor condimentum lacinia quis vel eros donec ac. Lectus proin nibh nisl condimentum id venenatis a. Egestas fringilla phasellus faucibus scelerisque. Aliquet sagittis id consectetur purus ut. Elit pellentesque habitant morbi tristique. Bibendum ut tristique et egestas quis ipsum suspendisse. Cursus metus aliquam eleifend mi in nulla posuere sollicitudin. Pellentesque habitant morbi tristique senectus et netus. Risus feugiat in ante metus dictum at. Volutpat ac tincidunt vitae semper quis lectus nulla at.'
    },
    initialized: false,
    dirty: true
  },
  name: 'Lettering'
}

I will do more tries using Collection.hydrate() and Collection.populated(). I am using version 4.0.0-alpha.11.

I don't really understand why you are using raw query for this, as this can be done easily with the EM api, where all the mapping would be handled automatically for you.
// this should issue the very same query as you have (at least in v4), and map it automatically
const styles = await em.find(StyleEntity, { artists: [1, 2, 3] });

Because I need the artist_id to can relate the data (styles to artists). If I query by artists ids [1, 2, 3] and I get 6 styles, how do I know which of those style is related to the artist with id 1 or with id 2 or with the id 3?

Anyway this looks like you are trying to build things that others already did, so you might want to take a look at existing solutions, e.g. #364 or look into the dependent packages, there are some starter projects for graphql, like this one ~https://github.com/dougg0k/nodejs_graphql_typescript_starter~ (edit: looks like this repo is not using request context at all, so rather ignore that)

I will try to understand #364. I am try to do something more simple.

I am not a graphql user, so can't help with that, but it would be helpful (for both of us), if you try to omit the GQL part from the reproduction code - you would most probably understand yourself what is happening and why. It's fine to give an example with the resolvers, but you should try to replicate the problem calling it directly, without dataloader in the background. That is the bit that is missing in your description, there is no control code, just few methods, without the context.

Here a reproduction without GQL. You will need add a .env, for example:
NODE_ENV="development"

SERVER_HOST="<IP_ADDRESS>"
SERVER_PORT=3000

DATABASE_URL="mysql://root@localhost:3306/develop"

and after:
npm install
npm run build
npm run database
npm run start

http://localhost:3000 is the equivalent to GQL:
query {
   artists(limit: 5) {
    id
    website
    ...
  }
}

And http://localhost:3000/styles=true the equivalent to GQL:
query {
   artists(limit: 5) {
    id
    website
    ...
    styles {
      id
      name
    }
  }
}

As always, a great ORM and a great work. Thank you.

Here you go:
    public async findArtists(artists: (number | string)[]): Promise<StyleEntity[]> {
        const results = await this.connection.execute(
            `select e0.*, e1.artist_id from style as e0
                left join artist_styles as e1 on e0.id = e1.style_id
            where e1.artist_id in (??)`,
            [artists],
        );

        const map = {} as Record<string, ArtistEntity[]>;

        for (const data of results) {
            const style = this.styleRepository.map(data);
            map[style.id] = map[style.id] ?? [];
            const artist = this.ormClient.em.getReference(ArtistEntity, +data.artist_id);
            map[style.id].push(artist);
        }

        const entities = Object.keys(map).map((id) => {
            const style = this.ormClient.em.getReference(StyleEntity, +id);
            style.artists.hydrate(map[id]);
            style.artists.populated();

            return style;
        });

        console.log(entities[0].artists);
        console.log(entities[0].artists.toArray());
        console.log(entities[0].artists.getIdentifiers());
        console.log(entities[0].artists.getItems());

        return entities;
    }

Thanks you @B4nan, but finally not seems to me the correct way. Now I am trying using EntityRepository.populate:
    public async populateStyle(entities: ArtistEntity[]): Promise<ArtistEntity[]> {
        return this.artistRepository.populate(entities, "style");
    }

Same with the findList method, I don't see a reason why you are using QB there.

What do you suggest? better use:
    public async findList(limit: number, cursor?: ArtistStoreCursor): Promise<ArtistEntity[]> {
        if (cursor) {
            return this.artistRepository.find(
                {
                    $and: [
                        { created: { $lte: cursor.created } },
                        { $or: [{ created: { $lt: cursor.created } }, { id: { $lt: cursor.id } }] },
                    ],
                },
                { orderBy: { created: "desc", id: "desc" }, limit },
            );
        }

        return this.artistRepository.findAll({ orderBy: { created: "desc", id: "desc" }, limit });
    }

PD: It would be great to be able to use lateral join in where clause of populate.


Appstudio update mvp-test-component

Pipelines as Code configuration proposal

Pipelines as Code CI/mvp-test-component-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
27 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
16 seconds
sanity-inspect-image

✅ Succeeded
16 seconds
deprecated-base-image-check

✅ Succeeded
56 seconds
clamav-scan

✅ Succeeded
17 seconds
clair-scan

✅ Succeeded
10 seconds
sbom-json-check

✅ Succeeded
19 seconds
sanity-optional-label-check

✅ Succeeded
19 seconds
sanity-label-check

✅ Succeeded
6 seconds
show-summary


Background scripts runs when popup opens

First things first, thank you for the taking the time making this template. I've noticed that the background script basically runs twice, in the background(as it should), and within the popup. You can also see the background_runtime.js in the "Sources" tab.
Here's an image:

Is there a way to avoid this?

Seems like all network requests and logs are actually shared but the code does not run twice as originally thought, I did an HTTP call but Wireshark shows only once connection being made.


Suggestions for ease of use

Hi, I've looked at this project and have two suggestions:

You could bundle the app into a single package and generate releases, if there's any hope of non-techies to use it. :) I've experimented with pyInstaller (https://github.com/pyinstaller/pyinstaller), and I was able to bundle your project into a single exe file, so no more messing with python for the regular users.
I believe the app could open a webview automatically, once the server is started (some people want to host from their computers, not raspberry pi's or servers). I've experimented with webview, and came up with this (dance_client.py):

import os
import subprocess
import webview

webview.create_window('Just dance!', 'http://localhost:32623', confirm_close=True)
dance_server = subprocess.Popen(["python", "dance.py"])
webview.start()

#terminate server on window close
dance_server.terminate()

It can still be improved, but that's my idea.
Is this project open to pull requests? I'd share my code :)

Please create a MR so I can take a look. Thank you.

I don't know how much it is possible, but I would like to add the ability to log into your Ubisoft account in JoyDance for the 2016-2018 version, as it was on a smartphone. And it's not very convenient to play as a guest, I would like to be able to change my dance card.

I don't know how much it is possible, but I would like to add the ability to log into your Ubisoft account in JoyDance for the 2016-2018 version, as it was on a smartphone. And it's not very convenient to play as a guest, I would like to be able to change my dance card.

I don't know how much it is possible, but I would like to add the ability to log into your Ubisoft account in JoyDance for the 2016-2018 version, as it was on a smartphone. And it's not very convenient to play as a guest, I would like to be able to change my dance card.

I don't know how much it is possible, but I would like to add the ability to log into your Ubisoft account in JoyDance for the 2016-2018 version, as it was on a smartphone. And it's not very convenient to play as a guest, I would like to be able to change my dance card.

It was determined in #4 that this won't be added :(


version 1.0 breaking changes?

I see that NPM is on version v1.0
The version here on Github is v0.0.12
I can't find any changelog / breaking changes for v1.0
I'd love to find some information on this!

Thanks for letting me know, I'm not experienced with github.  I'll work on it!

@epicshaggy this is a great release !
With this release: Is it possible to use the web integration for Android a well?
If it needs more tweaking to make it work: I'm thinking we can use in-app browser and deep links to go back to the app. What do you think ?

I'll close the issue for cleaning purposes but let's keep the conversation going.

@mesqueeb I didn't think of that, could try it out.  Also, you can checkout this branch which tries to implement android use, but I did not complete it for these reasons.  Currently I have a custom implementation on my app which sends the post request to my backend service.


Negate option for projects and tags options in log/report commands

Hi,
One use case I usually need in a log or a report is to show all projects but one or two, or frames with all tags but one.
So here is --exclude-tags and --exclude-projects flag option that exclude given tags or projects by --tag or --project options in log and report command.
In order to be able to type:
watson log -Gd -p coding -T personal --exclude-tags
to have log of code activity of the day, but not the personal ones.

@arnaudcordier is there any chance that you pursue this work or not? The second is perfectly fine if you don't have time for this.
In fact, your work on the report command has already been merged (see #288), but not for the log command.
Anyway, thank you again for this :pray:

Hi, sorry I didn't really follow this issue.
Anyway I reworked on it and made a new PR using work that had been done on the project command : #317


Doubt about hardware use

I have been using this interpolation model and the results have seemed quite good, but I have grown quite a doubt.
Does this model benefit from the use of VRAM or Core Frequency? Because I usually see that the GPU Core is at 0%, but the VRAM does heat up with the use of this model.

I have not realized this phenomenon. What is your hardware device? I use the standard PyTorch implementation of IFRNet and test it on the NVIDIA Tesla V100 and NVIDIA RTX 2080Ti GPUs. The phenomenon you described may depend on the concrete implementation library and hardware device.

Does this model benefit from the use of VRAM or Core Frequency? Because I usually see that the GPU Core is at 0%, but the VRAM does heat up with the use of this model.

Thanks for your reply. Will the above phenomenon affect your normal use of IFRNet? I think your question is some professional. I can not give you a specific answer since I am not familiar with VRAM and Core Frequency. I suggest that you can consult a person familiar with the underlying implementation.


Question regarding cabf_br/lint_subject_contains_malformed_arpa_ip

We got a hit on this lint for a cert that has a SAN in the format of:
*.0.0.1.f.5.4.3.ip6.arpa

Looking at this lint, it is producing a warning and I just want to make sure this lint is being helpful in this case.
The extended warning I'm getting is
name \"*.0.0.1.f.5.4.3.ip6.arpa\" has too few leading labels (9 vs 32) to be a reverse DNS entry in the \".ip6.arpa\" zone.

The rule this references is BR <IP_ADDRESS>.1 which doesn't really seem to reference anything other than reserved IP address blocks. I don't think this is problematic according to the BRs because it doesn't say anything I can see about treating IPv6 addresses in the ARPA domain as something other than normal domain names unless I'm missing something.
Can anyone provide any clarity on this lint, purpose, reasoning behind resulting in WARN vs. NOTICE? Is this a community a lint possibly from cablint that is misclassified?

:wave: @cardonator Thanks for the question.
I wrote this lint myself before I had much experience with ZLint and when the guidance on what status to return for different cases was a little bit less established. I suspect I might have been too strict here but I'll have to rebuild the context. I have a memory of an RFC that indicated reverse IPv6 addrs should always be fully expanded. I'll get back to you later today and update the lint if required.

I have a memory of an RFC that indicated reverse IPv6 addrs should always be fully expanded.

I was thinking of RFC 3596, specifically §2.5 "IP6.ARPA Domain".  That section seems to me to be fairly explicit that each nibble of the IPv6 address is represented by a hex digit, like shown in the example address conversion:

For example, the reverse lookup domain name corresponding to the address
4321:0:1:2:3:4:567:89ab
would be
b.a.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.3.4.IP6.ARPA.

That's how I arrived at the value of 32 expected labels for each IPv6.ARPA domain used by the lint:
https://github.com/zmap/zlint/blob/9bba7b7e572cd92a5b6d74ad0520522f45277ffc/lints/cabf_br/lint_subject_contains_reserved_arpa_ip.go#L43-L47
In my mind based on RFC 3596 *.0.0.1.f.5.4.3.ip6.arpa is not a well formed IPv6 reverse address. That said, I don't think the BRs consider it a violation. Because of that I think the lint_subject_contains_malformed_arpa_ip lint should probably be moved from the cabf_br category to the community category and demoted to a warning result.
I think the related lint_subject_contains_reserved_arpa_ip.go deserves to remain in the cabf_br category with an error level finding (I think we agree that a reverse DNS entry for a reserved IP address is no good).
@cardonator @zakird @sleevi Does my evaluation match up with what you folks think? Is there a qualification of the BRs I'm missing that would merit keeping this lint as-is?

@cpu
While I'm fine with moving it community, I suspect this is something the CA/B Forum should take up, because I would suggest the intent is to forbid it via <IP_ADDRESS> of the BRs and through <IP_ADDRESS>'s prohibitions on wildcards-for-IPs, and because for the reasons you cite, it's unclear to me how a CA could fulfill the obligations of the BRs for such a name.
The <IP_ADDRESS> argument is that ipv6.arpa is registry controlled (c.f. RFC 3172, aka BCP52), and while subdomains of ipv6.arpa are covered in Section 4, the direction given in BCP49 still delegates those subdomains to the RIRs.
So *.0.0.1.f.5.4.3.ip6.arpa is something registry controlled, although the BRs leave that definition for registry controlled as fluid, and the PSL (intentionally) doesn't represent the .arpa space within its file.
So if it's fine, it's on a technicality and oversight, and while I'd be curious how @cardonator validated it, I entirely suspect that's a conversation for the CABF to see about making more explicit.

Because of that I think the lint_subject_contains_malformed_arpa_ip lint should probably be moved from the cabf_br category to the community category and demoted to a warning result.

One correction: I had more coffee and realized the existing lint already treats this case as a warning and not an error. The only change would be to move it to community.
https://github.com/zmap/zlint/blob/9bba7b7e572cd92a5b6d74ad0520522f45277ffc/lints/cabf_br/lint_subject_contains_malformed_arpa_ip.go#L73-L76

While I'm fine with moving it community, I suspect this is something the CA/B Forum should take up, because I would suggest the intent is to forbid it via <IP_ADDRESS> of the BRs and through <IP_ADDRESS>'s prohibitions on wildcards-for-IPs, and because for the reasons you cite, it's unclear to me how a CA could fulfill the obligations of the BRs for such a name.

@sleevi Thanks for weighing in. That makes sense to me. I agree with you that this feels like a technicality that should be clarified in the BRs and raises questions about the validation.
Ultimately moving the lint to the community/ category won't change the user experience until we have implemented a way to choose a subset of lint categories to use when linting a certificate. For that reason after giving this some more thought I'm slightly biased towards leaving this lint as-is while the CABF discussion unfolds and spending the time implementing the required API change to select lint categories. Afterwards based on the state of the discussion we can update this lint.

This doesn't strike me as something worth moving offhand, at least until this is resolved in CA/B Forum. The error case seems to match the CABF BRs, and a warn doesn't seem inappropriate since it would be against community expectations to issue a wildcard like that.

Thanks for the feedback all.
@sleevi The common root of 0.0.1.f.5.4.3.ip6.arpa was validated using a DNS TXT Random Value. The Random Value was generated and set by the customer correctly according to the BRs. DNS tools are able to correctly pull DNS records at this level. (For clarity, I did modify the provided SAN to be a format vs. the actual customer submitted domain) However, I can see room for a question about if a validation for 0.0.1.f.5.4.3.ip6.arpa should be able to show control for every possible label under that address.
I agree that arpa SANs are left vague in the current BRs and it's not entirely clear how arpa reverse names should be treated in general. I do think BCP49 makes a good case that they should be treated as if they are IP addresses.
Would you suggest spinning up a conversation on this topic in SCWG or MDSP?
@cpu given the lack of clarity around this, I would agree that leaving it where it is makes the most sense. RFC 3596 does seem to suggest this should be considered a malformed SAN.

I'll put it on next week's Validation WG agenda.

RFC 3596 does seem to suggest this should be considered a malformed SAN. I do think it might be helpful to add referenced to RFC 3596 and BCP49 in the lint itself somewhere, even if just in the description.

@cardonator This is good feedback, thanks! I made a clumsy attempt at improving the situation with
https://github.com/zmap/zlint/pull/345 It isn't perfect but I think is a step in the right direction while the larger discussion is in progress.

We're coming up on a year since this issue was created. @sleevi @timfromdigicert was this resolved in CABF?

It has not been resolved, but only because we've been discussing other things.
I can put it on next Thursday's agenda again if there's interest in discussing it.


CUDPP 1.1 compile errors (and fixes) (gcc 4.3.3-5ubuntu4)

What version of the product are you using? On what operating system?
CUDPP 1.1, gcc 4.3.3-5ubuntu4 on Ubuntu 9.04 x64

Please provide any additional information below.

Building CUDPP 1.1 did not work out-of-the-box for me, and I believe
that some includes that should have been there are missing:

$ cudpp_1.1 cd common
$ common make
[...]
./../common/inc/cmd_arg_reader.h:417: error: must #include <typeinfo>
before using typeid
[...]
src/cutil.cpp:620: error: ‘strlen’ was not declared in this scope
[...]

To fix these:
in cmd_arg_reader.h
#include <typeinfo>
and in cutil.cpp
#include <cstring>

$ common make
[...]
./../common/inc/exception.h:89: error: ‘EXIT_FAILURE’ was not declared
in this scope
[...]

To fix:
#include <cstdlib>
in exception.h

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 13 Aug 2009 at 9:52

Original comment by<EMAIL_ADDRESS>on 14 Dec 2009 at 7:18

Added labels: Priority-High
Removed labels: Priority-Medium

This has been fixed in trunk.

Original comment by<EMAIL_ADDRESS>on 14 Dec 2009 at 8:54

Changed state: Fixed


Add 511 Network Authentication Required status code

Addresses issue: https://github.com/kennethreitz/requests/issues/2847

Thanks @annp89 !


fixes for latest kha in kha studio 17.9

The shaders need redone as well due to Rob moving from glsl (or removed). Main changes appear to be in Keyboard handling and shaders in the latest kha, at least with respect to Sdg.

Hi, these changes were already fixed, your code seems older than what is this repo.
Look here https://github.com/RafaelOliveira/Sdg/blob/master/Sources/sdg/manager/Keyboard.hx

This is what I get for coding after 10pm... I'll pull the latest when I get home!


Main chain deterministic designation as there might be 2 leafs with the same accumulated score

PR for issue #12

:+1:


Leave button error

When pressing leave button in custom room an error occurs, and onLeave function doesn't execute, so there is no redirect with router.push.

How to reproduce:
start livekit-server in dev mode
create token and enter custom room on livekit.meet.io (or on localhost)
press Leave button

This error should not prevent any further code execution.
Are you sure that this exact error is responsible for router.push not working?