Fix #1749 - Rename SonataFlow, jBPM, and Drools extensions

Many thanks for submitting your Pull Request :heart:!
Please make sure your PR meets the following requirements:

[ ] You have read the contributors guide
[ ] Pull Request title is properly formatted: [KOGITO|RHPAM-XYZ] Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket
[ ] Your feature/bug fix has a testcase that verifies it
[ ] You've tested the new feature/bug fix in an actual OpenShift cluster
[ ] You've added a RELEASE_NOTES.md entry regarding this change

Closes #1749
CI might fail since we depend on https://github.com/apache/incubator-kie-issues/issues/933

How to retest this PR or trigger a specific build:

(Re)run Jenkins tests
Please add comment: Jenkins [test|retest] this

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.

PR job #110 was: FAILURE
Possible explanation: Pipeline failure or project build failure
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/110/display/redirect
See console log:

Console Logs
[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-jobs-service-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-jobs-service-ephemeral seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-data-index-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-runtime-native: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-runtime-jvm: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-jobs-service-allinone: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-management-console: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-task-console: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-s2i-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/110/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

PR job #111 was: FAILURE
Possible explanation: Pipeline failure or project build failure
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/111/display/redirect
See console log:

Console Logs
[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-runtime-native: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-jobs-service-postgresql: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-runtime-jvm: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-data-index-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-management-console: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-jobs-service-allinone: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-task-console: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-s2i-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/111/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

PR job #122 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/122/display/redirect
See console log:

Console Logs
[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-task-console: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-jobs-service-allinone: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-jobs-service-allinone seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-management-console: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-runtime-jvm: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-swf-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-swf-builder seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-swf-devmode: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-swf-devmode seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-s2i-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/122/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

For the record:
The changes for swf-devmode and swf-builder images I believe are ok.
I was able to build these images locally, BUT, unfortunately, due to python + cekit local issues I can't execute the tests locally.
CI should be able to do I think.

PR job #123 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/123/display/redirect
See console log:

Console Logs
[Pipeline] unstableWARNING: Tests on kogito-task-console seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-management-console: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-management-console seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-runtime-jvm: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-runtime-jvm seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-swf-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-swf-builder seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-swf-devmode: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-swf-devmode seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-s2i-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-s2i-builder seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/123/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

PR job #124 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/124/display/redirect
See console log:

Console Logs
[Pipeline] unstableWARNING: Tests on kogito-data-index-ephemeral seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-runtime-native: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-runtime-native seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-task-console: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-task-console seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-swf-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-swf-builder seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-s2i-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-s2i-builder seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-swf-devmode: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-swf-devmode seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/124/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

PR job #125 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/125/display/redirect
See console log:

Console Logs
[Pipeline] unstableWARNING: Tests on kogito-jobs-service-ephemeral seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-task-console: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-task-console seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-jobs-service-allinone: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-jobs-service-allinone seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-swf-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-swf-builder seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-swf-devmode: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-swf-devmode seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-s2i-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-s2i-builder seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/125/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

@jakubschwan @jstastny-cz can you guys lend me a hand here? The tests are failing in a simple sh -c 'echo $USER' command. I honestly can't figure out what's possibly happening. Maybe this docker within docker structure we have to have in ASK Jenkins? Locally it runs fine and it was running fine before. I've also tried bash -c, with no luck.

Unless we can get logs from the container startup it's hard to guess. I don't see any hint in current logs. Does it use the latest SNAPSHOTs and in jvm or native quarkus mode?

Latest snapshots and jvm, no native. I can't get any clue in the logs either.

Opened https://github.com/cekit/cekit/issues/903

@jstastny-cz can we upgrade to Cekit 4.11?

PR job #126 was: FAILURE
Possible explanation: Pipeline failure or project build failure
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/126/display/redirect
See console log:

Console Logs
[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-runtime-nativeBuild KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-runtime-jvm: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-runtime-jvmBuild KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-jobs-service-allinone: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-jobs-service-allinoneBuild KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-task-console: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-task-consoleBuild KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-s2i-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-s2i-builderBuild KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-swf-devmode: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-swf-devmode[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/126/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

Depends on https://github.com/apache/incubator-kie-kogito-pipelines/pull/1189

PR job #127 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/127/display/redirect
See console log:

Console Logs
[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-jobs-service-postgresql: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-jobs-service-allinone: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-jobs-service-allinone seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-management-console: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-runtime-jvm: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-task-console: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-swf-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-swf-devmode: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-s2i-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/127/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

Apparently, the latest changes on Cekit Behave tests impacted our tests, so I've reverted their changes on my private fork, which worked. I'm waiting for their feedback on what to do.

PR job #128 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/128/display/redirect
See console log:

Console Logs
[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-jit-runner: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-data-index-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-data-index-ephemeral seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-management-console: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-task-console: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-swf-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-swf-devmode: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-swf-devmode seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-s2i-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/128/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

PR job #129 was: ABORTED
Possible explanation: Most probably a timeout, please review
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/129/display/redirect
See console log:

Console Logs
Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-task-console: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-task-consoleBuild KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-jobs-service-allinone: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-jobs-service-allinone seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-swf-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-swf-devmode: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-swf-devmode seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-data-index-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-data-index-ephemeralCalling Pipeline was cancelledClick here to forcibly terminate running stepsBuild KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-s2i-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: ABORTED[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-s2i-builder[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/129/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

PR job #130 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/130/display/redirect
See console log:

Console Logs
[Pipeline] unstableWARNING: Tests on kogito-jobs-service-ephemeral seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-jobs-service-allinone: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-jobs-service-allinone seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-jit-runner: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-runtime-jvm: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-management-console: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-swf-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-s2i-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-swf-devmode: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/130/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

PR job #131 was: FAILURE
Possible explanation: Pipeline failure or project build failure
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/131/display/redirect
See console log:

Console Logs
[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-data-index-postgresql: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-runtime-jvm: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-jobs-service-allinone: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-jobs-service-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-management-console: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-swf-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-swf-devmode: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1750 - kogito-s2i-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1750 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/131/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

I've rebuild the failed job: https://ci-builds.apache.org/blue/organizations/jenkins/KIE%2Fkogito%2Fmain%2Fpullrequest%2Fkogito-images.build-image/detail/kogito-images.build-image/1698/pipeline
Not sure why the main job didn't get updated. We can merge @porcelli @baldimir


Link to consumer groups Grafana dashboard

Closes #32

[x] Update Readme
[x] streaming apps
[x] connectors

Added connectors and also a better test that mocks the consumer group annotation.


Check how limits are applied to blocksByRange requests

how many requests can a node make for blocks by range? Do we have any logic around that?

if a lot of nodes are all requesting at the same time, what protections do we have in place?

Related to #6788, #6874 and #6870

Ok it sounds like these are in progress, should we close this as duplicate?

Yes. I close this one then


Translated README to Japanese

add readme in Japanese ✨

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: y-tsubuku sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


[Request] Have an option to delete AND revoke users' keys/cetrts (index.txt).

When you revoke access to the VPN for a user (client) the key remains in some places like the index.txt file in the Easy-RSA PKI folder. It would be convenient for the script to have an option to delete the key listing in the index.txt file (Easy-RSA) while revoking users (clients).

Why do you want to delete all information related to revoked users? They should remain there to provide a log of the revocation for security reasons.
Even if you delete listings in index.txt, the CRL file still contains the list of revoked users so it doesn't makes much sense.

I am going to close this issue because @randomshell provided a good point on why the revoked users should stay in the index.txt and CRL files. I looked over it again and it didn’t make much sense to remove revoked users from index.txt and CRL files.


Add macOS and Windows to the test matrix

Travis can run tests on macOS like this: https://github.com/Kentzo/async_app/blob/master/.travis.yml#L3-L23
AppVeyor can be used for Windows: https://github.com/Kentzo/async_app/blob/master/.appveyor.yml#L1-L15

Hi,
I don't want to add other platforms than Linux to the CI yet because I don't want to support them:

I don't have the hardware to support MacOS,
I'm not sure about the adoption of asyncio on Windows, and I don't know the implementation of the proactor backend.

That’s one of the benefits of making something open source: to let people support platforms they have.
I run asynctest on Windows and macOS pretty successfully.
Best Regards
Ilya Kulakov

On Dec 12, 2017, at 10:01 AM, Martin Richard<EMAIL_ADDRESS>Hi,
I don't want to add other platforms than Linux to the CI yet because I don't want to support them:
I don't have the hardware to support MacOS,
I'm not sure about the adoption of asyncio on Windows, and I don't know the implementation of the proactor backend.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I am very open to contributions and to share the work.
My concern here is that it's the first (and only) open-source project I manage and I would like to keep things maintainable in the future.
I would be very happy if you commit to supporting other platforms, but I have no idea how much work it represents nor if you want to spend time on this.
Maybe we can enable tests for those platforms and see how it goes for a while? We can state in the README that those platform are "best-effort" at the moment.

@Martiusweb makes sense. I'll create a PR to enable these tests when I can.
Do you plan / want to support pypy?


How youll assess suppliers

Used to be 'how you'll assess the suppliers' now its 'how you'll assess suppliers'.

👍


AuthenticationInterceptor 'refresh' delegate called many times for multiple requests

ℹ Please fill out this template when filing an issue.
All lines beginning with an ℹ symbol instruct you with what info we expect. You can delete those lines once you've filled in the info.
Per our *CONTRIBUTING guidelines, we use GitHub for
bugs and feature requests, not general support. Other issues should be opened on Stack Overflow with the tag alamofire.
Please remove this line and everything above it before submitting.

[x] I've read, understood, and done my best to follow the *CONTRIBUTING guidelines.

What did you do?
import Alamofire
import SwiftyJSON

struct OAuthCredential: AuthenticationCredential {
    let accessToken: String
    let refreshToken: String
    let expiration: Date

    // Require refresh if within 5 minutes of expiration
    var requiresRefresh: Bool { Date(timeIntervalSinceNow: 60 * 5) > expiration }
}

class OAuthAuthenticator: Authenticator {
    func apply(_ credential: OAuthCredential, to urlRequest: inout URLRequest) {
        urlRequest.headers.add(.authorization(bearerToken: credential.accessToken))
    }

    func refresh(_ credential: OAuthCredential, for session: Session, completion: @escaping (Result<OAuthCredential, Error>) -> Void) {

        NetworkManager.shared.oauth.doRefreshToken { (jsonDict, error) in
            if let jsonDict = jsonDict {
                let json = JSON(jsonDict)
                let accessToken = json["access_token"].stringValue
                let refreshToken = json["refresh_token"].stringValue
                let expiration = json["expires_in"].doubleValue
                let newCredential = OAuthCredential(accessToken: accessToken, refreshToken: refreshToken, expiration: Date(timeIntervalSinceNow: expiration))
                completion(.success(newCredential))
            }
        }
    }

    func didRequest(_ urlRequest: URLRequest, with response: HTTPURLResponse, failDueToAuthenticationError error: Error) -> Bool {
        return response.statusCode == 401
    }

    func isRequest(_ urlRequest: URLRequest, authenticatedWith credential: OAuthCredential) -> Bool {
        let bearerToken = HTTPHeader.authorization(bearerToken: credential.accessToken).value
        return urlRequest.headers["Authorization"] == bearerToken
    }
}

What did you expect to happen?
ℹ 'refresh' delegate method will be called once to refresh token and then recall all the other requests with new credentials
What happened instead?
ℹ 'refresh' delegate method is called for each request when 'requiresRefresh' is set
Alamofire Environment
Alamofire version: 5.2.2
Xcode version: 11.7
Swift version: 4.2
Platform(s) running Alamofire: iOS
macOS version running Xcode: 10.15.6 (19G2021)
Demo Project
ℹ Cannot provide demo project

@cnoon Can you take a look?

Did you find a solution for this.

Where is 'completion(.failure(error))' in 'func refresh(_ credential: OAuthCredential, for session: Session, completion: @escaping (Result<OAuthCredential, Error>) -> Void)'?

Has anyone found a solution to this issue?
I have no problem in my environment when it is a single request, but when multiple requests occur at the same time, multiple tokens are created.
We are using Doorkeeper on our server and multiple Doorkeeper::AccessToken are created almost simultaneously.
created_at: Thu, 10 Aug 2023 05:47:02.720082000 UTC +00:00
created_at: Thu, 10 Aug 2023 05:47:02.746252000 UTC +00:00


Create community-concept.pug

https://github.com/RiversideRocks/web-riverside/pull/58
Add this also


Add pull request template with checklist for submitting a tutorial

The create tutorial is quite long. A TL;DR section should summarise the key requirements for the tutorials. It can assume that the reader knows about git, github, Rstudio, ... If they don't than they can read the full document.

For info on PR templates, see https://help.github.com/en/articles/creating-a-pull-request-template-for-your-repository. Create it as .github/pull_request_template.md

From #103, also mention:

Another, maybe more easy to setup, option is to describe in the PR template to the user to have a check [on included post categories]

@ThierryO can you give the first go for this PR tutorial submission checklist? I can review it.

Or rather, the first person from @inbo/oscibio @inbo/bmk that submits a tutorial can start listing things on this checklist.


Issue with Wave Memorystream obtained through ffmpegcore

I seem to have run into an issue with a memorystream created by letting ffmpegcore download a video and stripping the audio from it.
As soon as it arrives at the ProcessAsync call. The application uses almost 10 gigs of memory. Calling Process instead of the async variant leads to "unable to read beyond the end of the stream"
I debugged part of it already and saw that the dataChunkSize seems to be massive compared to the memorystreams length (memory streams length: 888910)(https://github.com/sandrohanea/whisper.net/blob/main/Whisper.net/Wave/WaveParser.cs#L356)
When I hardcoded the dataChunkSize to be the length, it read the stream fine and gave me the expected output.
I wondered if you could tell me what might be the issue here. Either by the settings for the wave (unsupported codec or something else) or what might go wrong with reading the created memorystream. I added an example project to this post. (You might need to get the required ffmpeg binaries from https://ffbinaries.com/downloads)
WhisperIssueExample project

Hello @sandrohanea,
Thank you for addressing this issue with such promptness. I came across the updated nuget package that supposedly includes the fix as per the changelogs. However, upon using the package, I encountered the same issue where it still consumed 10gigs of memory. On the other hand, when I referenced the repository and debugged the code, it ran smoothly without any issues.
I have tried to identify the root cause of this anomaly but to no avail.

Hello @Kanda ,
Just to confirm:

You installed Whisper.net 1.4.4 and Whisper.net.Runtime 1.4.4 ?
Have you tried to clean/rebuild after the upgrade?

Hello @sandrohanea,
I have indeed updated both of them to 1.4.4 and have done both a clean/rebuild and a full delete of the bin and obj folder. To make sure to force a clean build.
I do know it has the new version cause the downloader now includes the QuantizationType. So I aint certain at this point why it isn't working with the nuget package.

Release 1.4.5 now, tested specifically this fix and it's working as expected using the nuget version.


Cosmic s2

Another set of changes for S2 cosmic jobs

Hi @oksuzian,
You have proposed changes to files in these packages:

CampaignConfig
JobConfig
Scripts

which require these tests: build.
@Mu2e/fnalbuild-users, @Mu2e/write have access to CI actions on main.
:hourglass: The following tests have been triggered for 8cd3c1bdf6f823d2dada76d70596501d81fd77d4: build  (Build queue is empty)
About FNALbuild. Code review on Mu2e/Offline.

:sunny: The build tests passed at 8cd3c1bdf6f823d2dada76d70596501d81fd77d4.

Test
Result
Details

test with
:white_check_mark:
Command did not list any other PRs to include

merge
:white_check_mark:
Merged 8cd3c1bdf6f823d2dada76d70596501d81fd77d4 at 7cd2ab61f80150496af5e3fb7b42117ef4e7aae8

build (prof)
:white_check_mark:
Log file. Build time: 11 min 01 sec

ceSimReco
:white_check_mark:
Log file.

g4test_03MT
:white_check_mark:
Log file.

transportOnly
:white_check_mark:
Log file.

POT
:white_check_mark:
Log file.

g4study
:white_check_mark:
Log file.

cosmicSimReco
:white_check_mark:
Log file.

cosmicOffSpill
:white_check_mark:
Log file.

ceSteps
:white_check_mark:
Log file.

ceDigi
:white_check_mark:
Log file.

muDauSteps
:white_check_mark:
Log file.

ceMix
:white_check_mark:
Log file.

rootOverlaps
:white_check_mark:
Log file.

g4surfaceCheck
:white_check_mark:
Log file.

FIXME, TODO
:white_check_mark:
TODO (0) FIXME (0) in 0 files

clang-tidy
:white_check_mark:
0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at 8cd3c1bdf6f823d2dada76d70596501d81fd77d4 after being merged into the base branch at 7cd2ab61f80150496af5e3fb7b42117ef4e7aae8.
For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.


How to Modify Header.

How we can modify font of the header and make date scrollable for future and previous date.
Also Please suggest how can we change Calendar Year.
samle code and css:-
<Calendar
                events={events} height={500}
                headerContainerStyle={styles.calenderContainer}
                dayHeaderHighlightColor={BLACK}
                date={new Date()}
                dayHeaderStyle={styles.dayHeaderStyle}
            />

dayHeaderStyle:{
        fontSize:12,
        color:'white',
        backgroundColor:'red'
    }

You can use theme feature.
const theme = {
  palette: {
    primary: {
      main: 'red',
    },
  },
  typography: {
    xl: {
      fontSize: 12,
    },
  },
}

<Calendar theme={theme} weekDayHeaderHighlightColor={BLACK} ... />

Also Please suggest how can we change Calendar Year.

I don't understand what are you talking about. Just change date prop's year and the calendar adjust it.

Thanks for your replay.

I have a overlapping issue in events.
How to fix this?
Check for refrence
https://lh7-us.googleusercontent.com/chat_attachment/AFzxxOhKUBvlxqRQI3r7LZihgXJiryoGUiAoqWCO-A8TCIK-AW3vVvuUB_ikKJbclIybz_BOjWohEYgr2ytwdMzE-9v3ee50lC9KWHbIq9yf97hk_He9Wb392TdPVtukT4w-KXt5ghOWqha5ZvXM4qi9Hrs9YgtCiNaFU-P8Fu9oUEZ_Y7BvdEHjK082k9_8KoGHvzZIB0o3pTB6sQT4Oo8bzrFbgCumljgZhEG5ydWOlC4oRg7sLM3Kg0yH9tT0n0Rn4DjkLRF4qMdEWVv9hX8aYL_5p_36GGeyS1rIeIb_KIMn7kh4P6ee3e31v0HzkZsKow=w512

how to reverse date and day name
https://lh7-us.googleusercontent.com/chat_attachment/AFzxxOhs6-Tu1nHxALS6FMxIxURyQI8SxSwZfXk30vXk4FmGfqqX2D53zAqLmnugBYzab3AKsnv20Y97iq4pgOGq0ADDUSLTvNypjRxvTMAmU2ogahAy0yFA6iyWKqUV_81UeI_S462-YM5RHjB3PLle9w5-ygb7j28UNOR-nA3RAerKepQ35Mh9PmGLj27CG95JeiOuezst-rzs49er7NXNtcxLDyDLEM1bIJjT58KFDDeyvLIN1gYrCTnB9PtDEZnQ5McJkpDz-QHbsiQDEvWtp2izSD4JbhzZla46lj0exTgEtfeEkiYwfnhE8ND0Vbmmrg=w512

The link you sent cannot be opened.
This component is intended for imitating Google Calender and too much customization should not be implemented to keep things clean. Currently it has already too much customization options, which makes this lib hard to maintain.
Thus, there is no option to reverse date and day name.

Hi,
I have updated the image Url. You can check now reference image.
Thanks!


ERROR_TYPE vocab discussion

Some thought is needed about the ERROR_TYPE vocab.
We have to keep in mind that we are aiming to label areas on earth. Therefore, all occurrences that subsequently fall into that polygon have to fit the label.
Some labels like ENRICHMENT_TYPE : NATIVE are not a problem because we expect all future occurrences to also be "native".
However, a label like ERROR_TYPE : IDENTIFICATION is less likely to fit subsequent occurrences. Since a subsequent occurrence is not likely to be misidentification.

Closing as error_type is removed, as per #16


make picture in picture player

[ ] pref to automatically open when exit local player
[ ]

https://stackoverflow.com/questions/36016369/system-alert-window-how-to-get-this-permission-automatically-on-android-6-0-an
example code
https://github.com/noln/system-alert-window-example/blob/master/app/src/main/java/com/mattfenlon/ghost/MainService.java

copy this and modify
https://github.com/AbelTesfaye/dingo/tree/master/android/app/src/main/java/com/dingo/PIPVideoPlayer


How to restructure a tensor according to one dimension.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):no
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):Centos 7
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:no
TensorFlow installed from (source or binary):binary
TensorFlow version (use command below):1.7.0
Python version:3.5.5
Bazel version (if compiling from source):no
GCC/Compiler version (if compiling from source):4.9.3
CUDA/cuDNN version:no
GPU model and memory:2 same GTX Titan X (Pascal), 12GB
Exact command to reproduce:

Describe the problem
How to restructure a tensor according to one dimension specified by user?
The paper "An End-to-End Deep Learning Architecture for Graph Classification" published in AAAI-18(PDF) proposed a new novel neural network architecture for graph classification and a new layer called "SortPooling" as a key block of the network. The author of this paper implement the network by torch, i want to reproduce by tensorflow. One of the key operation is to restructure a tensor by the descend value according to some one dimension.
e.g.
assume the original tensor a is
[[93, 69, 38, 46]
[54, 5, 1, 13]
[96, 45, 52, 50]]

and we want to restructure the tensor above according to the a[:, 3], so output:
[54, 5, 1, 13]
[[93, 69, 38, 46]
[96, 45, 52, 50]]

Then remove the last row(if two line already enough), so the final result i want is:
[[54, 5, 1, 13]
[93, 69, 38, 46]]

How to achieve this by tensorflow? Any funciton exist? the tf.nn.top_k seem not enough for this.
Source code / logs
no

Can you explain the reason why you want to do that operator?

 To do the graph(not image) classification, a more specialized architecture need to be designed, so Graph Convolution layer and SortPooling Layer are proposed to form GNN network. In my opinion, what the former do is extract features of each node from his neighbors by propagation, and as the author said, "our graph convolution layer is a theoretically closer approximation to the Weisfeiler Lehman algorthm", the WL algorithm is a graph labeling algorithm, what the latter do is to sort vertex by features(the value can be view as the importance of the node) instead of summing them up(the traditional method use), and feed the result into classic convolution layer.
The Graph Convolution layer is easy to code base on tensorflow, it just consist of some matrix operation(i think). but the SortPooling layer require sort and remove some dimension.  Maybe you have to dive into the paper if you want more detail and explanation.

Can't you use a softmax layer or some kind of classification layer at the end to sort the tensors (which in this case, would be nodes) by importance? You could actually make a 2-network program: the first one gets the importance of the nodes, which you classify using some kind of softmax layer. Then, you can remove the layers you don't want and feed the result in another NN as you see fit. I don't know if that is applicable to your problem AT ALL, but that's my best answer given my actual knowledge of your problem...

This requirement can be meet by tf.gather() combine tf.nn.top_k().
x = tf.constant(value=[[93, 69, 38, 46],[54, 5, 1, 13],[96, 45, 52, 50]])
sort_op = tf.gather(x, tf.nn.top_k(-x[:, 3], 3).indices)[:2]
with tf.Session() as sess:
    print(sess.run(sort_op))


Go to tmux terminal not working

Since the tmux functionally came out I have been able to do :lua :lua require('harpoon.tmux').gotoTerminal(1) and go to the first terminal or create the first terminal.
Over the past few weeks I have noticed that has not worked. Whenever I call this even if I have that terminal created, harpoon will try and create another new terminal again.
I have tried to understand how the tmux code works to try and change it my self, but I have not got very far.
If anyone knows what the problem is that would be great!

would it be related to https://github.com/ThePrimeagen/harpoon/issues/180?
the go to terminal feature mostly works but might not work if you start creating tmux panes

Having the same issue, harpoon seems to dislike tmux panes. 🥲


python311Packages.python-gvm: 23.5.1 -> 23.10.0

Diff: https://github.com/greenbone/python-gvm/compare/refs/tags/v23.5.1...v23.10.0
Changelog: https://github.com/greenbone/python-gvm/releases/tag/v23.10.0
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 260084 run on x86_64-linux 1

10 packages built:

faraday-agent-dispatcher
faraday-agent-dispatcher.dist
gvm-tools (python310Packages.gvm-tools)
gvm-tools.dist (python310Packages.gvm-tools.dist)
python310Packages.python-gvm
python310Packages.python-gvm.dist
python311Packages.gvm-tools
python311Packages.gvm-tools.dist
python311Packages.python-gvm
python311Packages.python-gvm.dist


limiting hunter_add_package architecture list for faster rebuild-all

A default hunter_add_package call like this:
hunter_add_package(OpenCV)
find_package(OpenCV REQUIRED)

in a cmake/polly build for ios-8-2
build.py --install ios-8-2

seems to build : 386 x86_64 armv7 armv7s arm64
lipo -info ${HUNTER_ROOT}/hunter/_Base/xxxxxxx/7bc3715/9ffc177/Install/lib/libopencv_flannd.a
Architectures in the fat file: /Users/dhirvonen/devel/hunter/_Base/xxxxxxx/7bc3715/9ffc177/Install/lib/libopencv_flannd.a are: i386 x86_64 armv7 armv7s arm64

for both Debug and Release configurations, for a total of 10 build passes of OpenCV.  During development, I'm typically interested in just one of these, say arm64 in Release mode.  I generally don't need Debug builds of external packages I'm using, and will be developing and testing on a single platform.  Are there any hooks to support this type of hunter package configuration/limitation (architecture and optimization level)?
If not, I would submit this as a feature request.  It could be a useful workaround for long build times in common use cases, when small changes are made to cmake/Hunter/config.cmake that force a rebuild-all of all hunter packages.  Limiting development builds to a single architecture could make development and package tuning more feasible.

Fast fix with two architectures ios-8-2-i386-arm64 from branch develop:

https://github.com/ruslo/polly/blob/develop/ios-8-2-i386-arm64.cmake

There are two problems I currently investigating:

In fact for some reason Xcode rebuild one architecture so for time measurement it's like +1
Current CMake patched version for iOS expect two libraries, so i386 + arm64 is minimal combination. I will fix it later

I generally don't need Debug builds of external packages I'm using

this feature is designed to solve such problems: https://github.com/ruslo/hunter/issues/22

Great, so to translate this into a build command, it looks like we need hunter v0.8.13 (for the parallel build hunter CMake macros) and the latest poly in develop (if using build.py front end for --jobs command)
HunterGate(
    URL "https://github.com/ruslo/hunter/archive/v0.8.13.tar.gz"
    SHA1 "7103f0ab481523ca93a06c1c55abcd56741d3a97"
    FILEPATH "${CMAKE_BINARY_DIR}/hunter-config.cmake"
)

Then we could achieve a relatively fast build using:
build.py --toolchain ios-8-2-i386-arm64 --jobs 8 --clear --verbose

I'm not clear on how to make use of the release only builds mentioned in #22.
That issue mentions:

Create one build scheme url_sha1_cmake.cmake.in (?) instead of two url_sha1_release_debug.cmake.in url_sha1_combined_release_debug.cmake.in.

Does this require adding a new hunter.cmake file for each target:
Where this:
# Pick a download scheme
hunter_pick_scheme(
    DEFAULT
    url_sha1_release_debug # For separate release/debug generators, like Makefile
    COMBINED
    url_sha1_combined_release_debug # For Xcode and Visual Studio
)

is replaced with something like this:
# Pick a download scheme
hunter_pick_scheme(
    DEFAULT
    url_sha1_cmake # For separate release/debug generators, like Makefile
)

if using build.py front end for --jobs command

Actually they are not related. 'build.py --jobs' is for your local build. Hunter will use number of logical cores by default, if you want to rewrite this settings you can set HUNTER_JOBS_NUMBER manually. I.e. if you want to build both local project and 3rd party using 8 cores you can run:
> build.py --jobs 8 --fwd HUNTER_JOBS_NUMBER=8

That issue mentions

It's just an implementation notes

Does this require adding a new hunter.cmake file for each target

Yes hunter.cmake for CMake based projects will use single url_sha1_cmake instead of two url_sha1_release_debug + url_sha1_combined_release_debug

I'm not clear on how to make use of the release only builds mentioned in #22

You just need to set HUNTER_CONFIGURATION_TYPES=Release and all 3rd party libraries will be built in Release configuration.

Posting your response for the benefit of others:

the hunter.cmake change of all files will be made by me (and only once). Later you can just add new option HUNTER_CONFIGURATION_TYPES to your project build: build.py --fwd HUNTER_CONFIGURATION_TYPES=Release This will effectively register new Toolchain-ID in which all 3rd party library will be built on Release mode by default (you still be able to customize it per package in config.cmake). alternatively you can set an option in your CMakeLists.txt: option(HUNTER_CONFIGURATION_TYPES Release)

@headupinclouds Hi, David. I've added toolchain ios-8-2-arm64 with only one architecture: https://github.com/ruslo/polly/blob/master/ios-8-2-arm64.cmake but you need to update also new patched CMake version which knows how to skip universal build for such kind of toolchain: https://github.com/ruslo/CMake/releases/tag/v3.2.1-p3
This version of Hunter v0.9.0 learn new option HUNTER_CONFIGURATION_TYPES which can be used to control Release/Debug/... builds of 3rd party packages. In short you need to run this command to build Release packages with only arm64 architecture:
> build.py --toolchain ios-8-2-arm64 --verbose --fwd HUNTER_CONFIGURATION_TYPES=Release

Thanks, that should make a big difference in build times.  I've recompiled my CMake using v3.2.1-p3, and tested tested this with the Xcode (OS X) and iOS-8-2-arm64 toolchain.  The OS X Xcode build works:
 build.py --toolchain ios-8-2-arm64 --verbose --fwd HUNTER_CONFIGURATION_TYPES=Release --jobs 8 --open

But I seem to hit a problem in a boost library for the iOS build:
build.py --toolchain ios-8-2-arm64 --verbose --fwd HUNTER_CONFIGURATION_TYPES=Release --jobs 8 --open

This is the output:
-- [hunter *** DEBUG *** 2015-04-22T21:37:59] Scheme: url_sha1_boost_ios_library

[hunter ** INTERNAL **] Unexpected empty string
[hunter ** INTERNAL **] [Directory:/Users/dhirvonen/devel/hunter/_Base/xxxxxxx/cf868fd/7d97147/Build/Boost/filesystem]

The ios-8-2 toolchain behaves the same.

But I seem to hit a problem in a boost library for the iOS build

Your pull request and additional fixes applied in branch develop or in v0.9.1


Refactory

test-vectors feature: zk rows set to zero for deterministic proof
share some code between te and sw cond add
reduced explicit trait dependencies using AffineCondAdd trait
default transcript type set to ArkTranscript

@drskalman I applied some of your suggestions. I have questions for the assertions you suggested to introduce


change file location for example using kaito_workspace_falcon_7b-instruct.yaml

the file location for kaito_workspace_falcon_7b-instruct.yaml in the "Deploy a default hosted AI model" section has changed from "https://raw.githubusercontent.com/Azure/kaito/main/examples/kaito_workspace_falcon_7b-instruct.yaml" to "https://raw.githubusercontent.com/Azure/kaito/main/examples/inference/kaito_workspace_falcon_7b-instruct.yaml"
the document needs updated to reflect the new file location. GH page available here: https://github.com/Azure/kaito/tree/main/examples/inference
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: b78edbe2-d3e1-d73f-d389-0e2e8f27fda1
Version Independent ID: ac477be3-a0fa-3a00-80b2-2961ba272401
Content: Deploy an AI model on Azure Kubernetes Service (AKS) with the AI toolchain operator (preview) - Azure Kubernetes Service
Content Source: articles/aks/ai-toolchain-operator.md
Service: azure-kubernetes-service
GitHub Login: @schaffererin
Microsoft Alias: schaffererin

@msfttklingenberg
Thanks for your feedback! We will investigate and update as appropriate.

#reassign:schaffererin

Hi, @msfttklingenberg! Thank you for your feedback. The article has been updated with the proper file location :) I will close this GitHub issue now. Thanks again. #please-close


Added python cheat sheet to the languages folder.

I intentionally skipped the OOPS concept as it consists more data which is making cheat book but not sheet,
Please do mention if I'm missing, I will add them.
fixes #153

Thank you, can you update the Readme?

Made changes requested.


Disable fleets bootstrap

Issue: https://github.com/rancher/fleet/issues/1365
Problem
Both Fleet and Rancher try to manage the local cluster and overwrite each others changes.
Solution
Only Rancher will manage the local cluster. "Bootstrapping" is disabled in Fleet (the "local cluster" block from https://fleet.rancher.io/ref-registration).
The https://github.com/rancher/rancher/blob/release/v2.7/pkg/controllers/provisioningv2/fleetcluster/fleetcluster.go already bootstraps the local cluster.
If both manage the same cluster resource. This is a problem, because the
controllers will overwrite each others changes as the owner information differs.
By using Rancher's bootstrapping, we no longer have the bootstrap
resources from Fleet, like the local cluster group and the local cluster kubeconfig.
Creation of the local cluster group is added to the fleetcluster controller.
Rancher already creates a 'local-kubeconfig' secret for Fleet, which was not used previously.
This secret contains the "CATTLE_SERVER_URL" as API server, but Fleet's
secret contained the internal address of the API server.
By switching to the "CATTLE_SERVER_URL", the local cluster can no longer
be setup without a working URL.
Note: There is an additional token field in 'local-kubeconfig', which is
not used by Fleet (see importCluster).
The local cluster was switched in 5b9fbac49 to Fleet's secret. That issue should not occur anymore, since only one controller manages the resource.
Testing

Engineering Testing
Manual Testing

This was tested manually by running Rancher in debug mode.
Automated Testing
I had a unit test, which introduced more complexity and added little coverage. I'd leave it out of this PR.
QA Testing Considerations

Regressions Considerations

Instead of using the public IP, if it is necessary to handle the
"loopback connect is handled different from any other cluster" we might need to bring Fleet's buildKubeconfig code into the Rancher controller.

Not sure why CI fails.
Running the tests locally, the fleet-agent cannot connect to the cluster's k8s API, because of an invalid CA.
And indeed, the CA from fleet's config is different from the one server on port 8443. The key and serial number differs.

I managed to validate few things on latest Pre-release v2.7.5-rc2 which has this fix included.
Blocker for me to test it further: Fresh install of Rancher doesn't shows UI.(Known issue, it will be fixed in the next rc build) :crossed_fingers: Hopefully will get sooner.
I had to validate few things on upgraded cluster from 2.7.3 to 2.7.5-rc2 but while testing namespace move, I accidentally moved the local cluster to different workspace :disappointed: and hit https://github.com/rancher/fleet/issues/1489.
I am waiting for next RC release to test it.

The fix is yet to be added in Rancher latest RC build. Waiting for new RC build to test this issue.

I installed rancher 2.7.5-rc.4.
To verify this issue, need to check below entities:

[ ] The "local-kubeconfig" secret contains the "internal-server-url" as k8s API server.
[ ] local-cluster group should not be present as it gets created when local cluster gets bootstrapped by Fleet.
[ ] Additional token field must be present (outside of the local-kubeconfig secret)

I kept cluster running almost 18+ hours and I don't see changes happened on the local cluster by fleet-controller specifically.


Occasional failure to start up after pg_switch_wal()

is this a known issue?

I haven't seen exactly this sequence with xlog switch, but it is kind of expected behaviour.

I was able to reproduce this locally with:
    for i in range(1, 2000):
        branch_name = f"test_twophase{i}"
        env.neon_cli.create_branch(branch_name)
        endpoint = env.endpoints.create_start(branch_name)
        endpoint.safe_psql("SELECT pg_switch_wal()")
        endpoint.stop_and_destroy()
        endpoint = env.endpoints.create_start(branch_name)
        endpoint.safe_psql("SELECT pg_switch_wal()")
        endpoint.stop_and_destroy()

failed after about ~100 iterations

CI failure misses first ep logs (it is better to do endpoint.stop(mode="immediate") to preserve them instead of endpoint.stop_and_destroy()), but I think the following happens:
1. SELECT pg_switch_wal() is done at first compute;

2. first compute is SIGKILL'ed

3. second compute starts and observers that sk position is 0/14EE280, nothing to sync, and fetches basebackup at this pos

4. safekeeper gets from TCP stream WAL switch record and bumps flush position to 0/2000000

5. basebackup is now spoiled because it is taken at wrong LSN position.

So I'd suggest to add sleep/retry until endpoint starts well. Alternatively safekeeper exposes list of walreceivers and we can poll sk until walreceiver on it is gone.

Hmm, isn't this a potential problem in production too?
Originally posted by @hlinnaka in https://github.com/neondatabase/neon/issues/8914#issuecomment-2363793939

It is just an instance of generic "we can't have two writing computes at the same time", one of them would panic. This particular case can be optimized/eliminated by forcing compute_ctl to bump term during sync-safekeepers check, but I don't see much value in it.

It is just an instance of generic "we can't have two writing computes at the same time", one of them would panic. This particular case can be optimized/eliminated by forcing compute_ctl to bump term during sync-safekeepers check, but I don't see much value in it.

Hmm, there are no two computes running at the same time. Or do you think there's a delay between sending SIGKILL to the old compute and the processes actually exiting, such that the old compute is still running when new one starts?

It is not running, but there is a leftover TCP connection from it which delivers this xlog switch after new compute checked need for sync-safekeepers (and decided on basebackup LSN).

Hmm, so process has been killed, but the WAL is already in the safekeeper's TCP receive window, the safekeeper just hasn't processed it yet. Ok, makes sense. To test that hypothesis, a small delay in the test after killing postgres should make the problem disappear.

Another failure that looks the same, this time in test_subscriber_restart[debug-pg17] (https://neon-github-public-dev.s3.amazonaws.com/reports/pr-8914/10963706083/index.html#suites/8be0c222d5601535470e7e5978bbfb03/be227c68eb5edaf9/):
G:2024-09-20 21:23:26.915 GMT [309365] LOG:  [WP] got votes from majority (1) of nodes, term 153, epochStartLsn 0/1600360, donor <IP_ADDRESS>:16892, truncate_lsn 0/1600328
PG:2024-09-20 21:23:26.915 GMT [309365] PANIC:  [WP] collected propEpochStartLsn 0/1600360, but basebackup LSN 0/1600328
PG:2024-09-20 21:23:26.916 GMT [309356] LOG:  background worker "WAL proposer" (PID 309365) was terminated by signal 6: Aborted
PG:2024-09-20 21:23:26.916 GMT [309356] LOG:  terminating any other active server processes

I wonder if something changed recently that makes this occur more frequently. IIUC we've always had this issue.

and another one: https://neon-github-public-dev.s3.amazonaws.com/reports/pr-8949/10968355902/index.html#suites/8be0c222d5601535470e7e5978bbfb03/e29d86daa093ff5/

I opened https://github.com/neondatabase/neon/pull/9099 to fix flakiness, but now I think that actually bumping term on compute start if sync-safekeepers is skipped is a better fix, though it needs more infra (extracting safekeeper http client to separate crate), so 9099 should fix flakiness in the meanwhile.

I opened #9099 to fix flakiness,

Thanks! This should make the CI much less flaky.

but now I think that actually bumping term on compute start if sync-safekeepers is skipped is a better fix, though it needs more infra (extracting safekeeper http client to separate crate), so 9099 should fix flakiness in the meanwhile.

Yeah, I was just thinking of the same. If you are taking a basebackup with the intention of starting a new primary on it, it'd make sense to close the previous term. If the primary starts up successfully, it would kick out any previous writer on the old term anyway. Or it might run into this issue and fail to start up. It would feel more deterministic if it would always kick out the old compute.

I think this was fixed by #9436.


Request: Add to CDNjs

Hi, I use CDNjs: https://cdnjs.com/
Can you add this project there? Its a simple pull/push via GitHub...
https://github.com/cdnjs/cdnjs

Looks like they mandate auto-update now.

https://github.com/cdnjs/cdnjs/commit/588fd627f084eba6f64521ef1f80f890935dcc02


"host" parameter not being read from .ember-cli JSON file

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Linux

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:
1.0.0-beta.26 through
1.0.0-beta.30

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.
edit .ember-cli JSON object and create  "host": "x.x.x.x" property. Run ng serve. host is completely ignored. However, --host command line parameter is still recognized (i.e. ng serve --host x.x.x.x)

This feature used to work, and has stopped, but I believe other .ember-cli features are still working
The log given by the failure.

Normally this include a stack trace and some more information.

Mention any other details that might be useful.
Would gladly have another way of storing settings beside .ember-cli file, but have been using them for close to a year without problem...

Thanks! We'll be in touch soon.

@danielzen It looks like support for this file is removed:
https://github.com/angular/angular-cli/pull/4030
I'm afraid at this point I can't tell you what the alternative is, as I never worked with .ember-cli.

Thanks @beeman. The only alternative at the moment is to manually adding the command line flags....


@3.12.0 -<EMAIL_ADDRESS>

coverage: 99.245%. remained the same
when pulling 9cf95ae92308452d80feb09e6e1662a4d662748d on rc-3.12.0
into 1405d67163d867ec670fb878d36b992f0a5651ca on master.


rbac: add unit tests for matchers to increase coverage

Description
This PR add some more unit tests to improve the code coverage of RBAC matchers class.

Commit Message: rbac: add unit tests for matchers to increase coverage
Additional Description: Added some more unit tests to improve the code coverage of RBAC matchers class.
Risk Level: Very Low
Testing: Added Unit Tests
Docs Changes: N/A
Release Notes: N/A

/assign @wbpcode

/retest

/retest


safe integers for embedded systems

I came upon your page - now I don't remember how, but I may have something of interest to you.
For some time I've been working on a safe numerics library.  You can find information on it at www.blincubator.com  .  It's quite complete, but I'm still working out the final kinks.  Also I'm adding a case study to the manual about how to use the library to correct arithmetic behavior with minimal runtime penalty.  I see this as having wide application in embedded systems - even those which don't support C++.  The library is thus related to C++14 metaprogramming and embedded systems which seems to be right in your area of interest.

Interesting you would comment here as this is probably my least famous repo ;) I will have a look at your lib when I have time, I am always interested in things which will make bare metal development mor ehigh tech.


Improve pre-processing (add context, reformat) mechanism of UserInput

Acceptance criteria

Pre-processing mechanisms are improved
UserInput is enriched with relevant context
Input is reformatted to ensure compatibility with LLM

Moved it to backlog bc it is more related to LinktaFLow Visualisation & Interaction sprint


Enable TLS support for Postgres

.Values.global.postgresql.postgresqlSSL is currently not wired up because the bitnami image version we're using doesn't work with it. This replaces the bitnami image with our own and configures it.

I am not sure if this is an issue or not but shouldn't this:
https://github.com/pachyderm/pachyderm/blob/61a0bdf1e5e09a476a2c33ec360622ca4eb07438/etc/helm/pachyderm/templates/pachd/deployment.yaml#L67-L70
Be this instead?
{{- if .Values.global.postgresql.postgresqlSSL }}
- name: POSTGRES_SSL
  value: {{ .Values.global.postgresql.postgresqlSSL | quote }}
{{- end }}

Given that were completely swapping out the PG Bouncer image this should be included in the review https://github.com/pachyderm/pg-bouncer

Doesn't look like the PGBOUNCER_DATABASE env var is included in the underlying image

PGBOUNCER_UNIX_SOCKET_DIR is also missing from the underlying image (not sure if we need it anymore?

Looks like PGBOUNCER_DEFAULT_POOL_SIZE is missing from the underlying image

It looks like the bitnami image supports SSL? https://github.com/bitnami/bitnami-docker-pgbouncer#securing-pgbouncer-traffic

Have all of the options in https://github.com/pachyderm/pg-bouncer/blob/main/entrypoint.sh been exercised and verified they're being passed through correctly?


[ISSUE 8832] Avro custom schema not working in consumer

Fix #8832
Modifications
Make AvroSchema's clone method consider custom reader and writer.

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

@congbobo184 Could you please help take a loot at this PR?

remove tag release 2.6.3 since it depends on https://github.com/apache/pulsar/pull/8464. There many conflicts with branch-2.6.


Release to bower

It would be great to see this package in bower.io registry

Bower isn't recommended for new projects. See https://bower.io/blog/2017/how-to-migrate-away-from-bower/.

I think this can be closed.

Wow, finally there's the answer :)


Getting original request url onopen

When a new websocket clients connect I pass url parameters in my request.  I can't find a way to access the original request uri, is there a way I can?

Look at example Upgrade. You get HTTP stuff in onupgrade

Alright thanks :)
I successfully moved my project from seasocks to uWebSockets now


Code of GCN-S part

Hello, I saw that you will open the training code in late May. I want to ask if you will open the code of GCN-S part at that time. Thank you.

@LZDSJTU We will try to release as much code as possible before the conference.

Thank you for your contribution.
Additionally, could you provide the list for splitting MS-Celeb-1M dataset?

@LZDSJTU The list has been uploaded to GoogleDrive and OneDrive. You can also find it in README of the dev branch.

Hello, I saw you evaluated your method with YTF dataset, I wonder how to generate this dataset?
How to sample images from YTF's original video frames, can you provide more detailed information?

@jxyecn We use the frames extracted by YTF dataset. Checkout the second or third download link in YTB official page. Particularly, as stated in experimental settings, we use 14,653 frames for training and 140,629 frames for testing. The related data and pretrained model have been uploaded to GoogleDrive and OneDrive to reproduce the result. You can also find it in README of the dev branch.

@yl-1993 Thanks for your reply

@LZDSJTU We will try to release as much code as possible before the conference.
期待尽早开源GCN-S部分的代码，好像从论文上看，GCN-D+GCN-S性能提升比起只用GCN-D并不是很多么？

@CaiQiuYu GCN-S is devised to improve the precision of the proposals. Since the precision of clustering results after GCN-D is over 95, there is no much space for improvement. In ablation study, we show that GCN-S can be used as an independent module to combine with other methods.

Is there any news about publishing the training code?

@LZDSJTU Thanks a lot for checking our progress. The training code will be available after PR https://github.com/yl-1993/learn-to-cluster/pull/6 is merged.

Hi @yl-1993 , is there any plan of releasing the code of the GCN-S ?

@AruniRC Thanks for checking our progress. Since the difference between GCN-S and GCN-D is not very significant, the priority of cleaning GCN-S is lower than our other projects currently. Actually, the model of GCN-S is available at dsgcn model. By setting the reduce_method to no_pool and stage to seg, it becomes the GCN-S model. One missing thing is introducing random seed in data processor to decide the segmentation ground-truth, which can be implemented through writing a cluster_seg_processor as cluster_det_processor. It is always in our schedule and we will find some time to work on that.

Hi @yl-1993 , is there any plan of releasing the code of the GCN-S ?

@zsz00 Thanks for checking. I'm busy preparing a submission and currently may not have much time for this project. For those who want to have a try, I provide a code snippet for GCN-S. The snippet can not run directly, but includes the data processing and loss function used in GCN-S.

Thanks for your reply

Hi all, GCN-S will be available after PR https://github.com/yl-1993/learn-to-cluster/pull/31 is merged.

GCN-S is available now. Feel free to have a try. @LZDSJTU @CaiQiuYu @AruniRC @zsz00

@yl-1993  Hello, I would like to ask some questions about testing GCN-S with my own dataset which has no id labels. There's something wrong when I run "test_cluster_seg_ms1m.py", it occurred an error that "TypeError: 'NoneType' object is not subscriptable " in cluster_seg_processor.py. Here the 'NoneType' object refers to dataset.idx2lb
When building processor for GCN-S, a function "build_graph" in class ClusterSegProcessor will compute labels for data, my question is how to compute labels when testing data have no labels (which means dataset.idx2lb is None)?
I'll appreciate it if you could answer my question!! Thank you!

@linjiawen2019 Thanks for reporting! We will fix it through PR https://github.com/yl-1993/learn-to-cluster/pull/44.

@linjiawen2019 Thanks for reporting! We will fix it through PR #44.

Thx so much!! Really helpful to me

@linjiawen2019 Thanks for reporting! We will fix it through PR #44.

Thank u so much!! Really helpful to me

@linjiawen2019 The PR is merged. Feel free to have a try.


#1: add support for horses in database initialization

Added new animal type "horse"

/paulo - can you please review this pull request?

/paulo - can you check now?


{WIP}(GH-144)  Add signature help provider feature

Builds on #142
Fixes #144
In action

Previously the object_under_cursor method only returned the AST object and the
path to the object.  However some providers may also require a locator because
Puppet 4 does not expose the Locator on the AST object, only on the Factory.
This commit adds the return struct for the object_under_cursor method to also
return the Locator.
No test changes are required.

Previously the object_under_cursor always assumed it should remove the trigger
character when trying to figure out the object under the cursor. While this
works for things like completion and hover, it does not for signature help. This
commit updates the options hash with a new key called remove_trigger_char which
by default removes the character during detection.  Just like the default
behaviour.  This commit does not require any test changes as behaviour has
not changed.

This commit adds a new Signature Help provider for puppet manifest files.  It
takes the information from the Puppet 4 API metadata (signatures) and uses the
Puppet Parser Helper to figure out which signature and then which parameter in
that signature is being queried by the Language Client.

Adds a new signature_provider.rb for manifests and adds many test scenarios
to ensure the provider behaves as expected
Updates the message router to route the new messages appropriately
Updates the server capabilities to tell the client we support the signature
provider, and what keys will trigger the provider

Note - No need for a feature flag for this.
Block on 142 being merged.

#142 is merged.  Unblock for review and merge.


issue in get media

Hi
when im tring to get media by id/url get error on if (!isset($mediaArray['graphql']['shortcode_media'])) {throw new InstagramException('Media with this code does not exist');
}
looks like instagram is change his endpoint

please provide example URL


Release 0.14.5

This is a tracker to aggregate issues that should be part of 0.14.5. Please add specific Issues or PRs prefixed with the "Depends on" keyword (and remember that PRs need to be backported to the release-0.14 branch).
Depends on https://github.com/submariner-io/subctl/pull/728
Depends on https://github.com/submariner-io/submariner/pull/2518
Depends on https://github.com/submariner-io/submariner/pull/2521

https://github.com/submariner-io/releases/releases/tag/v0.14.5


Year picker only

I was checking and it seems the package doesn't provide a pure year picker without months/days etc.
Does this feature has no value or is there any other reason it wasn't implemented so far?
I think it should look roughly like this:

I'm looking exactly for this, I just need the user to pick a year without a month or a day..

Hi, I'm also looking for the same.

I also need this feature.

Added a yearpicker thanks to #2130


error of " mappings

I am using the vim compiled from the source, the commit of my src is as follows:
commit 6259e5769dd50d8a3b5b99f553bab34ff5c8a6ce
Author: Bram Moolenaar<EMAIL_ADDRESS>Date:   Mon Jul 9 20:39:17 2018 +0200

    patch 8.1.0173: compiler warning on MS-Windows

    Problem:    Compiler warning on MS-Windows.
    Solution:   Add type cast. (Mike Williams)

I compiled it on both ubuntu16.04 and archlinux, the result of running vim --version is as follows:
VIM - Vi IMproved 8.1 (2018 May 18, compiled Jul 10 2018 14:23:11)
Included patches: 1-173
Compiled by zhangzy@lingmou-server
Huge version with GTK2 GUI.  Features included (+) or not (-):
+acl               +farsi             +mouse_sgr         -tag_any_white
+arabic            +file_in_path      -mouse_sysmouse    -tcl
+autocmd           +find_in_path      +mouse_urxvt       +termguicolors
-autoservername    +float             +mouse_xterm       +terminal
+balloon_eval      +folding           +multi_byte        +terminfo
+balloon_eval_term -footer            +multi_lang        +termresponse
+browse            +fork()            -mzscheme          +textobjects
++builtin_terms    +gettext           +netbeans_intg     +timers
+byte_offset       -hangul_input      +num64             +title
+channel           +iconv             +packages          +toolbar
+cindent           +insert_expand     +path_extra        +user_commands
+clientserver      +job               -perl              +vartabs
+clipboard         +jumplist          +persistent_undo   +vertsplit
+cmdline_compl     +keymap            +postscript        +virtualedit
+cmdline_hist      +lambda            +printer           +visual
+cmdline_info      +langmap           +profile           +visualextra
+comments          +libcall           -python            +viminfo
+conceal           +linebreak         -python3           +vreplace
+cryptv            +lispindent        +quickfix          +wildignore
+cscope            +listcmds          +reltime           +wildmenu
+cursorbind        +localmap          +rightleft         +windows
+cursorshape       -lua               -ruby              +writebackup
+dialog_con_gui    +menu              +scrollbind        +X11
+diff              +mksession         +signs             -xfontset
+digraphs          +modify_fname      +smartindent       +xim
+dnd               +mouse             +startuptime       +xpm
-ebcdic            +mouseshape        +statusline        +xsmp_interact
+emacs_tags        +mouse_dec         -sun_workshop      +xterm_clipboard
+eval              -mouse_gpm         +syntax            -xterm_save
+ex_extra          -mouse_jsbterm     +tag_binary
+extra_search      +mouse_netterm     +tag_old_static
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
  system gvimrc file: "$VIM/gvimrc"
    user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "~/.vim/gvimrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
    system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/home/zhangzy/build/vim/compile/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2   -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc   -L/usr/local/lib -Wl,--as-needed -o vim   -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE  -lm -lnsl  -lselinux -lncurses -ldl

I add the following lines in my ~/.vimrc:
imap ' ''<esc>:let leavechar="'"<cr>i
imap " ""<esc>:let leavechar="""<cr>i

Then when I type ' or " in the insert mode, there is no symbols printed in the screen. And if I continue to press ctrl + c  to enter normal mode, I have tens of lines of symbol ' printed to my screen. Is it some bug of vim or something wrong with my configuration. I simply would like the function of conveniently inserting "" or '' symbols.

Please use inoremap if you don't want to have your mappings trigger recursively.
Please ask user questions on the vim_use mailinglist or use vi.stackexchange.com. This here is a bug tracker for problems with Vim. We cannot provide individual help here. Closing.


chore: update React and package versions

https://github.com/fullboar/vc-showcase/issues/2
Updates React and all supporting packages to the latest versions.
Includes refactoring, where necessary, to fix errors related to version upgrades.

@jleach Hey Jason, this is ready for your review

Resolved merge conflicts.


Buffers are closed after PossessionLoad or PossessionSave

this has been driving me up the wall for the past 30 mins, why does my lua buffer close after a session save and why doesn't it show when I load said session. I've tried configuring it so it closes nothing and still got the same result.
https://asciinema.org/a/CeVVGybVHbj0Z1JXvoZ2JWCKE
minimal config on NVIM v0.7.0-dev+1275-g00effff56
return require('packer').startup(function()
        use 'wbthomason/packer.nvim'

        use {
                'jedrzejboczar/possession.nvim',
                requires = { 'nvim-lua/plenary.nvim' },
                config = function() require('possession').setup{
                        silent = false,
                        load_silent = false,
                        debug = true,
                        plugins = {
                                close_windows = false,
                                delete_hidden_buffers = false,
                                nvim_tree = false,
                                tabby = false,
                        },
                } end
        }
end)

just tried it on NVIM v0.6.1 and it works great sighs
any clue why that's the case, I've got a couple things that use 0.7 functionality so I can't simply rollback

I have encountered what sound like the same issue, specifically I was able to figure out that the issue seems to be that the mksession output does not include any of the buffer information when used by this plugin. But running it manually within the same config does work as expected, and I don't see anything in the code that would cause this either.

This is strange behaviour, I tried to reproduce the problem but I'm not able to. I used the same Neovim version NVIM v0.7.0-dev+1275-g00effff569 with the following minimal_init.lua:
vim.opt.runtimepath = vim.opt.runtimepath + './possession.nvim'
vim.opt.runtimepath = vim.opt.runtimepath + './plenary.nvim'

require('possession').setup {
    silent = false,
    load_silent = false,
    session_dir = '/tmp/possession',
    debug = true,
    plugins = {
        close_windows = false,
        delete_hidden_buffers = false,
        nvim_tree = false,
        tabby = false,
    },
}

then starting with nvim --clean -u minimal_init.lua test.lua (running inside ~/.local/share/nvim/site/pack/packer/start). Both saving and loading work without issues.
I wonder what could cause the buffer closing before (or after?) session save. Could this be somehow related to other plugins? Can you try to run with the same commands as I did (with --clean).
Or maybe you could try using verbose to debug what is happening. You would need to issue the following commands:
set verbosefile=/tmp/verbose.log
set verbose=15

then save the session and exit. Then you can check the file to search for autocommands that could be responsible for closing the buffer. You can use lower verbose level if there are too many logs.

then starting with nvim --clean -u minimal_init.lua test.lua

What's test.lua, you've only provided minimal_init.lua

(running inside ~/.local/share/nvim/site/pack/packer/start)

I don't really understand what you mean by that as that's where packer is installed.
I'm not an expert in nvim debugging as you could tell hahah

I jusked checked with the minimal config and it does work fine, will keep digging further.

It seems like the autocmd causing it is from https://github.com/nvim-neo-tree/neo-tree.nvim, specifically this function which is called on BufWinEnter through their own event system, because BufDelete is triggered right after it, but I can't really see anything obvious in that function that could cause something like this.

the issue happened in the minimal init.lua that I've pasted in the issue, the only plugins installed were packer and possession, I also don't use neotree.
I guess this is what you get when you live on the edge, since I really like this plugin I'm rolling back to 0.6.1, global statusline and full lua support can wait a bit longer

@jedrzejboczar

then starting with nvim --clean -u minimal_init.lua test.lua

What's test.lua, you've only provided minimal_init.lua

(running inside ~/.local/share/nvim/site/pack/packer/start)

I don't really understand what you mean by that as that's where packer is installed.
I'm not an expert in nvim debugging as you could tell hahah

No problem :P
This test.lua was some random file that I only used to check if its buffer will be closed. And the reason I started from ~/.local/share/nvim/site/pack/packer/start is because when you start Neovim with nvim --clean it won't load any plugins. So in the minimal_init.lua that I provided there are lines with vim.opt.runtimepath = ... that manually add plugin directories to the list of searched directories. This way only these two plugins will be loaded.

the issue happened in the minimal init.lua that I've pasted in the issue, the only plugins installed were packer and possession, I also don't use neotree.

You were probably running without --clean, so some other plugins may be loading from runtimepath. It may also load the packer-compiled code. Or did you actually remove (or didn't have) any other plugins from the path where packer stores plugins?

It seems like the autocmd causing it is from neo-tree, specifically this function which is called on BufWinEnter through their own event system, because BufDelete is triggered right after it, but I can't really see anything obvious in that function that could cause something like this.

Thanks for looking into it. To be able to help with this I need to find a way to reproduce the problem. I will try to install neo-tree when I have a moment to debug this issue. But if @RaafatTurki is not using neo-tree at all, there might be other plugin causing the problem :/ I wonder why changing version to 0.6.1 solves the issue. One guess would be that there is a plugin that has some functionality that is only enabled when version 0.7 is detected. If that's not a problem @RaafatTurki could you provide a list of plugins you use?

The only other autocmds in the verbose log are from luasnip but those only trigger after the buffers are closed so they don't seem to be the cause of it. I will try debugging it further today.

 Please confirm that https://github.com/jedrzejboczar/possession.nvim/commit/ac58abd802625a67005e4c515f2d0383bbf8d904 fixes the issue.

Yes, that seems to have fixed it. Thank you!

Thanks for finding the issue :)


Add abuse-report.md

Note the Subject.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Reset peerScore histogram

Motivation
This specific histogram captures current state not a total, so must be reset before observing values
Description
Reset peerScore histogram

:tada: This PR is included in v1.6.0 :tada:


Access control policies don't work

Describe the problem
Today I've deployed a new setup which has separated IDP based on Zitadel and Netbird which I've configured using advanced configuration guide. I have one server in a cloud which has docker installation with couple of services and netbird agent installed in the same network with docker services. I've deleted default access policy rule and added custom one, which allows the only UDP traffic.

I've added a new route with peer and the docker network.

And traffic began to flow from User peer to OracleDC peer, but not the traffic which is limited by the access policy rule, but any traffic. So, in this case I allowed the only UDP traffic, but I can ping hosts in remote network and access to the services on 80,443/tcp ports.
To Reproduce
Steps to reproduce the behavior:

Deploy a new service
Add some peers to different groups.
Create network route which sits behind one of the peers.
Delete default access policy and create a new one which limits the access to the peers with network routes.
Feel free to access to any resources in the route without limitations of created access policy.

Expected behavior
Limited traffic according to created Access Policy.
Are you using NetBird Cloud?
self-host NetBird's control plane.
NetBird version
0.26.3
Thank you

Hey @sisumara
This is a know limitation. The access control rule you have set up is applied to the routing peer but not the machines behind it.
We are working on enhancing the access control to apply port and protocol restrictions on the machines behind the router.
Do you want to limit ports and protocols for the whole network behind the router or individual resources?

Hey @sisumara This is a know limitation. The access control rule you have set up is applied to the routing peer but not the machines behind it. We are working on enhancing the access control to apply port and protocol restrictions on the machines behind the router.

So, I can limit traffic flow with access policies the only to the peers, right?

Do you want to limit ports and protocols for the whole network behind the router or individual resources?

I have couple of cases and in some of them it needs to limit the whole network in some of them just certain hosts in the network.

YEs the same, test to accept juste in TCP port 32400 (plex) and the host with netbird agent havec access to connecte on SSH :
explain flow
host peer agent ----> host routing peer -----> server plex
I want to block the host peer agent just right access on port 32400 and not all port in host beinhind routing peer