Update operator and kubernetes dependencies

Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@howardjohn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test lint

e2e-bookInfoTests-envoyv2-v1alpha3_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test lint

e2e-bookInfoTests-envoyv2-v1alpha3_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-trustdomain

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test lint

e2e-bookInfoTests-envoyv2-v1alpha3_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-trustdomain

e2e-simpleTests_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test lint

e2e-bookInfoTests-envoyv2-v1alpha3_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-trustdomain

e2e-simpleTests_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests

e2e-simpleTests-distroless_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests-distroless

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test lint

e2e-bookInfoTests-envoyv2-v1alpha3_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-trustdomain

e2e-simpleTests_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests

e2e-simpleTests-distroless_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests-distroless

pilot-e2e-envoyv2-v1alpha3_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test lint

e2e-bookInfoTests-envoyv2-v1alpha3_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-trustdomain

e2e-simpleTests_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests

e2e-simpleTests-distroless_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests-distroless

pilot-e2e-envoyv2-v1alpha3_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test pilot-e2e-envoyv2-v1alpha3

e2e-mixer-no_auth_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-mixer-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test lint

e2e-bookInfoTests-envoyv2-v1alpha3_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-trustdomain

e2e-simpleTests_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests

e2e-simpleTests-distroless_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests-distroless

pilot-e2e-envoyv2-v1alpha3_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test pilot-e2e-envoyv2-v1alpha3

e2e-mixer-no_auth_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-mixer-no_auth

lintmodern_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test lintmodern

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test lint

e2e-bookInfoTests-envoyv2-v1alpha3_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-trustdomain

e2e-simpleTests_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests

e2e-simpleTests-distroless_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests-distroless

pilot-e2e-envoyv2-v1alpha3_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test pilot-e2e-envoyv2-v1alpha3

e2e-mixer-no_auth_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-mixer-no_auth

lintmodern_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test lintmodern

e2e-simpleTests-cni_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test lint

e2e-bookInfoTests-envoyv2-v1alpha3_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-trustdomain

e2e-simpleTests_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests

e2e-simpleTests-distroless_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests-distroless

pilot-e2e-envoyv2-v1alpha3_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test pilot-e2e-envoyv2-v1alpha3

e2e-mixer-no_auth_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-mixer-no_auth

lintmodern_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test lintmodern

e2e-simpleTests-cni_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests-cni

e2e-simpleTestsMinProfile_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTestsMinProfile

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test lint

e2e-bookInfoTests-envoyv2-v1alpha3_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-trustdomain

e2e-simpleTests_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests

e2e-simpleTests-distroless_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests-distroless

pilot-e2e-envoyv2-v1alpha3_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test pilot-e2e-envoyv2-v1alpha3

e2e-mixer-no_auth_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-mixer-no_auth

lintmodern_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test lintmodern

e2e-simpleTests-cni_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests-cni

e2e-simpleTestsMinProfile_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTestsMinProfile

e2e-dashboard_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test lint

e2e-bookInfoTests-envoyv2-v1alpha3_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-trustdomain

e2e-simpleTests_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests

e2e-simpleTests-distroless_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests-distroless

pilot-e2e-envoyv2-v1alpha3_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test pilot-e2e-envoyv2-v1alpha3

e2e-mixer-no_auth_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-mixer-no_auth

lintmodern_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test lintmodern

e2e-simpleTests-cni_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests-cni

e2e-simpleTestsMinProfile_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTestsMinProfile

e2e-dashboard_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-dashboard

pilot-multicluster-e2e_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test lint

e2e-bookInfoTests-envoyv2-v1alpha3_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-bookInfoTests-trustdomain

e2e-simpleTests_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests

e2e-simpleTests-distroless_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests-distroless

pilot-e2e-envoyv2-v1alpha3_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test pilot-e2e-envoyv2-v1alpha3

e2e-mixer-no_auth_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-mixer-no_auth

e2e-simpleTests-cni_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTests-cni

e2e-simpleTestsMinProfile_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-simpleTestsMinProfile

e2e-dashboard_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test e2e-dashboard

pilot-multicluster-e2e_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test pilot-multicluster-e2e

unit-tests_istio
e78692e2496b85926e0acf1142025cfd21dc246b
link
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio
59e93e9a0c59920dda169a3b71e3a709c14cb244
link
/test pilot-multicluster-e2e

integ-mixer-k8s-tests_istio
e78692e2496b85926e0acf1142025cfd21dc246b
link
/test integ-mixer-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
e78692e2496b85926e0acf1142025cfd21dc246b
link
/test integ-mixer-k8s-tests

e2e-simpleTests_istio
e78692e2496b85926e0acf1142025cfd21dc246b
link
/test e2e-simpleTests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
e78692e2496b85926e0acf1142025cfd21dc246b
link
/test integ-mixer-k8s-tests

e2e-simpleTests_istio
e78692e2496b85926e0acf1142025cfd21dc246b
link
/test e2e-simpleTests

racetest_istio
e78692e2496b85926e0acf1142025cfd21dc246b
link
/test racetest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Perform modulesync (0.3.0)

Perform modulesync with tagged version 0.3.0 of modulesync_config
Remove puppet-lint-rc
Exclude non-Windows nodesets from being managed by modulesync

i really hope nobody runs puppet on windows under ruby 1.8 :laughing:


How do I trigger build when I hit refresh on my browser?

Hi, I have a project that uses react-redux-starter-kit and the project is quite huge. I am not a big fan of Webpack hot reloader. I feel productive when I actually hit F5 on my keyboard to see changes that I made. Webpack watch is annoying to me now because whenever I hit ctrl+s, it occasionally freezes my IDE or text editors. Since I am CTRL+S and F5 person (will always doing it in the future), is it possible to trigger webpack build whenever I hit F5 on my Chrome browser and see changes?

I am open for communication. I am happy to receive any recommendations as well. If you need more information about my issue, please let me know.

I was actually using npm start instead of npm run dev. It was causing the issue =(

Sorry for not replying earlier, the best way to do this is probably by enabling the lazy option for webpack's dev server -- see http://webpack.github.io/docs/webpack-dev-server.html.
Hope that helps!


Why so many mandatory fields ?

If i want to open a ticket, why so many mandatory fields ?
Can many of them be optional ?
for example , we dont use sla_id or priority_id , can it be for example =1 by default if its not in api ?

ok


pc_align convergence

As Ross noticed, pc_align does not seem to quite converge. It settles in some kind of oscillatory behavior close to the the best solution, and keeps on doing that for as many iterations as you provide. Probably the stopping criterion needs to be a bit smarter, and in that case the fix would need to go in libpointmatcher itself. (Luckily its developers have been so far very receptive to outside contributions -- if strict on style.) This needs to be studied in more detail.

Hasn't been an issue since.


Still not able to setup on M1 mac

$ uname -a
Darwin mbp14.local 21.6.0 Darwin Kernel Version 21.6.0: Wed Aug 10 14:28:23 PDT 2022; root:xnu-8020.141.5~2/RELEASE_ARM64_T6000 arm64
$ /usr/libexec/java_home -V
Matching Java Virtual Machines (2):
    17.0.4 (arm64) "GraalVM Community" - "GraalVM CE 22.2.0" /Library/Java/JavaVirtualMachines/graalvm-ce-java17-22.2.0/Contents/Home
    11.0.16 (arm64) "GraalVM Community" - "GraalVM CE 22.2.0" /Library/Java/JavaVirtualMachines/graalvm-ce-java11-22.2.0/Contents/Home
/Library/Java/JavaVirtualMachines/graalvm-ce-java17-22.2.0/Contents/Home
$ java -version
openjdk version "11.0.16" 2022-07-19
OpenJDK Runtime Environment GraalVM CE 22.2.0 (build 11.0.16+8-jvmci-22.2-b06)
OpenJDK 64-Bit Server VM GraalVM CE 22.2.0 (build 11.0.16+8-jvmci-22.2-b06, mixed mode)
$ ./cs-aarch64-apple-darwin version
2.1.0-M6-53-gb4f448130
$ ./cs-aarch64-apple-darwin setup
Checking if a JVM is installed
Found a JVM installed under /Library/Java/JavaVirtualMachines/graalvm-ce-java11-22.2.0/Contents/Home.

Checking if ~/Library/Application Support/Coursier/bin is in PATH

Checking if the standard Scala applications are installed
  Found ammonite
JVM graalvm:19.3 not found in index: JVM graalvm not found
$

I'm happy to try and help solve the problem, but I'm not sure where this message is coming from. It seems like it's from within coursier itself? Could it be related to https://github.com/coursier/coursier/issues/2487?

Deleting $HOME/Library/Caches/Coursier might have helped.

I'm very interested in learning how to resolve this

I have an idea as to what's causing this, but I don't have an Apple Silicon machine to test on at the moment.
From testing on a coworker's machine, it's installing bloop specifically during setup that causes the crash. If you specify the apps explicitly (with --apps) and omit bloop or use bloop-jvm instead, everything works.
The "app" definition for bloop specifies that it has the graalvm-native-image launcher type.
It looks like Coursier uses GraalVM in this case, which I think defaults to the version 19.3 which is specified here.
Since this version isn't published for ARM, everything fails.
It seems there's a hidden parameter --graalvm-default-version that can be used to override the GraalVM version, but this doesn't fix the issue either, since it looks like Macs need to use grallvm-java11 or graalvm-java17, and the parameter only sets the version. For example --graalvm-default-version 22.2 causes the setup to fail since there's no graalvm:22.2.
I haven't been able to figure out where the string graalvm:22.2 is built.
I think if we could change the default GraalVM to graalvm-java11:22.0 it might work.

Another, potentially safer workaround might be to change the app definition for bloop to not use native-image and/or release Apple Silicon builds for bloop.

I check DefaultAppList and it seems scala-cli app is responsible for this issue 😬
$ cs setup --yes --apps ammonite,cs,coursier,scala,scalac,sbt,sbtn,scalafmt
Checking if a JVM is installed
Found a JVM installed under /usr/lib/jvm/java-11-openjdk-arm64.

Checking if ~/.local/share/coursier/bin is in PATH

Checking if the standard Scala applications are installed
  Found ammonite
  Found cs
  Found coursier
  Found scala
  Found scalac
  Found sbt
No main class found

$ cs setup --yes --apps scala-cli
Checking if a JVM is installed
Found a JVM installed under /usr/lib/jvm/java-11-openjdk-arm64.

Checking if ~/.local/share/coursier/bin is in PATH

Checking if the standard Scala applications are installed
JVM graalvm:19.3 not found in index: JVM graalvm not found

I was able to install a bunch of things this way, thanks @christianharrington (and greetings, it's been a while!). I've installed the following apps:
amm
bloop-jvm
coursier
cs
sbt
scala
scalac
scalafmt

It's probably a separate issue but running cs doesn't work for me however:
cs
/Users/mark/Library/Application Support/Coursier/bin/cs: line 2: /Users/mark/Library/Application Support/Coursier/bin/.cs.aux: cannot execute binary file
/Users/mark/Library/Application Support/Coursier/bin/cs: line 2: /Users/mark/Library/Application Support/Coursier/bin/.cs.aux: Undefined error: 0

I think the No main class found message is coming from installing sbtn:
$ ./cs-aarch64-apple-darwin setup --yes --apps sbtn
Checking if a JVM is installed
Found a JVM installed under /Users/mark/Library/Caches/Coursier/arc/https/github.com/graalvm/graalvm-ce-builds/releases/download/vm-22.2.0/graalvm-ce-java11-darwin-aarch64-22.2.0.tar.gz/graalvm-ce-java11-22.2.0/Contents/Home.

Checking if ~/Library/Application Support/Coursier/bin is in PATH

Checking if the standard Scala applications are installed
No main class found

I can confirm that sbtn throws No main class found error. This is how my Dockerfile looks like 🙈
RUN cs install \
  sbt \
  scala \
  scalac \
  scalafmt \
  && cs install sbtn || true

cc @rochala
On M1, we may want to check for ARM binaries, and fall back on x86-64 ones.

Please also see https://github.com/coursier/coursier/issues/2537#issuecomment-1273791648

I am closing this issue as a duplicate of #2537.


feature request: add hostname or nodename label to metrics

I am making an alternative version of your sample grafana dashboard using the metrics exported by this plugin (and related such as prometheus_process_collector), dashboard that I will be happy to share back in a PR.
A problem I have is that the rabbitmq instances are identified by their "instance" label, which is an ephemeral ipaddress and port.
Since I deploy rabbitmq as docker containers inside kubernetes, I would like another label to be added which is more stable than "instance", for example the hostname (of the container) or even better the rabbitmq nodename.
In other words, when I query process_uptime_seconds in prometheus, I get:
process_uptime_seconds{instance="<IP_ADDRESS>:15672",job="kubernetes-service-endpoints",kubernetes_name="rabbitmq",kubernetes_namespace="backends"}	3656

I would like to have:
process_uptime_seconds{instance="<IP_ADDRESS>:15672",nodename="rabbit@rabbitmq-0.rabbitmq-cluster.backends.svc.cluster.local",job="kubernetes-service-endpoints",kubernetes_name="rabbitmq",kubernetes_namespace="backends"}	3656

The problem with the "instance" label is that I cannot differentiate:

a single rabbitmq instance being redeployed and getting another IP address over time (then I can safely workaround by wrapping the query in sum (expression) without (instance)
a multi instance rabbitmq cluster where I would like to track the memory usage, file descriptors etc. by nodename

If I don't wrap the data in sum (expression) without (instance) then I get "multiple value error" when displaying single stat such as uptime in the dashboard, and I get the same label multiple times in the state displaying the different kind of messages (acknowledged, redelivered etc).
I would also like to templatize the dashboard so that I can check the stats of each rabbitmq node separately in the case of a multi-cluster node.

Have you read this?
https://prometheus.io/docs/concepts/jobs_instances/#automatically-generated-labels-and-time-series
We can just set instance. And by default no one will notice.
I see it as a config option of the exporter, like ... {instance, node_name}.
Your instance labels are changing dynamically but what about node names?

And for templating I need to add something like is_rabbit so in grafana we can get all instances where is_rabbit is defined.

Hello, I did not notice until now the instance label can be configured. Let me play with it and close this issue myself. Thank you very much.

I ended up scraping the rabbitmq pods instead of the rabbitmq service, as a consequence I get access to a "kubernetes_pod_name" label which I use in my templating. I am willing to share my modified dashboard as a PR if you are interested.

Yes I'm, Thanks!

Closing this issue, since I am happy with scraping the rabbitmq pods and using their kubernetes_pod_name as "node" key for the dashboard.


swagger-maven-plugin produces duplicate output

I use the latest swagger-maven-plugin from the io.swagger.core.v3 to generate my static swagger api documentation. In my project, I have to separate apis so I want to get a json and yml representation for each api within one package process.
<plugin>
                <groupId>io.swagger.core.v3</groupId>
                <artifactId>swagger-maven-plugin</artifactId>
                <version>2.2.6</version>
                <configuration>
                    <outputPath>${basedir}/target/</outputPath>
                    <outputFormat>JSONANDYAML</outputFormat>
                    <prettyPrint>true</prettyPrint>
                </configuration>
                <executions>
                    <execution>
                        <id>1</id>
                        <goals>
                            <goal>resolve</goal>
                        </goals>
                        <configuration>
                            <resourcePackages>
                                <resourcePackage>de.test.rest</resourcePackage>
                            </resourcePackages>
                            <outputFileName>swagger</outputFileName>
                            <configurationFilePath>${basedir}/src/main/resources/openApiConfig.yml</configurationFilePath>
                        </configuration>

                </execution>
                <execution>
                    <id>2</id>
                    <goals>
                        <goal>resolve</goal>
                    </goals>
                    <configuration>
                        <resourcePackages>
                            <resourcePackage>de.test.secondAPI</resourcePackage>
                        </resourcePackages>
                        <outputFileName>secondAPI</outputFileName>
                        <configurationFilePath>${basedir}/src/main/resources/secondOpenApiConfig.yml</configurationFilePath>

                    </configuration>
                </execution>
                </executions>
            </plugin>

PROBLEM:
the execution creates the expected json and yml files for each execution

swagger.yml
swagger.json
secondAPI.yml
secondAPI.json

The problem is, that the seconAPI files are a copy of the swagger files. I've read the documentation and I thought that configuration in the plugin root is shared between multiple executions. Configurations within the execution tag are individually used per execution.
Is there a way to run the executions in parallel with individual configuration? Or is it a problem with the plugin itself?

Did you ever get anywhere with this?  I'm trying to generate multiple api files, one for each resource package.  Creating one execution (with configuration in execution) per package, and running each execution specifically on the command line works fine.  but as soon as you run without out specifying a specific execution (the normal maven command), all executions are run, all files are generated, but every file is exactly the same.  A copy of the very first execution.

Adding a unique "contextid" to each execution configuration will generate the files as expected.
<plugin>
	<groupId>io.swagger.core.v3</groupId>
	<artifactId>swagger-maven-plugin</artifactId>
	<version>2.2.6</version>
	<configuration>
		<outputPath>${basedir}/target/</outputPath>
		<outputFormat>JSONANDYAML</outputFormat>
		<prettyPrint>true</prettyPrint>
	</configuration>
	<executions>
		<execution>
			<id>1</id>
			<goals>
				<goal>resolve</goal>
			</goals>
			<configuration>
				<contextId>gen1</contextId>
				<resourcePackages>
					<resourcePackage>de.test.rest</resourcePackage>
				</resourcePackages>
				<outputFileName>swagger</outputFileName>
				<configurationFilePath>${basedir}/src/main/resources/openApiConfig.yml</configurationFilePath>
			</configuration>
		</execution>
		<execution>
			<id>2</id>
			<goals>
				<goal>resolve</goal>
			</goals>
			<configuration>
				<contextId>gen2</contextId>
				<resourcePackages>
					<resourcePackage>de.test.secondAPI</resourcePackage>
				</resourcePackages>
				<outputFileName>secondAPI</outputFileName>
				<configurationFilePath>${basedir}/src/main/resources/secondOpenApiConfig.yml</configurationFilePath>
			</configuration>
		</execution>
	</executions>
</plugin>

+1 very unexpected that I need an unique context id and quite lucky to get to this page


There is no document about rocketmq in python .

There is no document ahout rocketmq in python lanaguage,
It is really disappointed for someone who use python to develop.
In any project, The api have  always  a document for people who use .
If you have some time, please provide a document that use python language.

Read examples in https://github.com/apache/rocketmq-client-python/blob/master/samples/producer.py and https://github.com/apache/rocketmq-client-python/blob/master/samples/consumer.py is a good start.

Such as  msg.born_timestamp and  get_message_queue_offset ,  I don't know the  unit of the return value  of  msg.born_timestamp , I have to test many times, and finally I think the unit is millisecond. the example is nothing ahout what I want.

Read examples in https://github.com/apache/rocketmq-client-python/blob/master/samples/producer.py and https://github.com/apache/rocketmq-client-python/blob/master/samples/consumer.py is a good start.

thanks ,but the eample's infomation is too little.


Review comments from MarkusK

@lukaspie agree on this one

Thanks @lukaspie for your feedback, will formulate an updated version, then you can check again and this me merged thereafter


Clicking on any of the tracked currencies in settings does nothing

As title says. I installed the latest test version but can't do anything in the settings menu.
Tried reinstalling as well as deleting old plugin data but still doesn't work.

Fixed in 06870583ea012499fff933340806d692da6e42f2


Update dependencies versions

This moves Guava and AppEngine API SDK forward.
It resolves a minor inconsistency in the version definition for the AppEngine API SDK.
It also moves the google-http-java-client backwards to 1.27.0 because 1.28.0 made an incompatible change that breaks google-cloud-java (which depends on 1.27.0) and using 1.28.0 here risks runtime problems down the line.

It's possible the "Kokoro - Test: Java 8" job is wedged somehow or not reporting status. Both this PR and the much simpler #233 have been stuck at "Expected — Waiting for status to be reported" for a while now.


Fixes small spelling mistake in oc-compliance help

Small character change so the help message agrees with the rule.

Signed-off-by: Paul Bastide<EMAIL_ADDRESS>

/retest
cluster didn't install


OpenStruct decoration support fixed.

Decorating OpenStruct which has accessors like system fails due to you using send instead of public_send, because of a fallback to Kernel#system.
require 'ostruct'

rating = OpenStruct.new(system: 'MPAA', value: 'R')

require 'representable'
require 'representable/json'

class RatingRepresenter < Representable::Decorator
  include Representable::JSON

  property :system
  property :value
end

RatingRepresenter.new(rating).to_hash
# => ArgumentError: wrong number of arguments (given 0, expected 1+)

Thought this should be fixed, cause you use OpenStruct in your other gems a lot.

Very good point, but I'm a bit nervous, will that be a breaking API change? Can't think of a real edge case but, you know..?!


Make arrows face right in RTL mode, update to latest i18next definition

Tested by manually re-enabling other languages and making sure things looked fine in RTL mode

:+1:


IXO missing from Assets

System information
Osmosis version: Osmosis version
OS & Version: OSX
Commit hash: N/A
Expected behaviour
When a user searches for the IXO token they should find it.
Actual behaviour
IXO token can no longer be found when searching for it.
The IXO/OSMO and IXO/ATOM pools are still available.
Steps to reproduce the behaviour
Search for the IXO token on the Assets screen or any other screen where search is possible.
Backtrace
[backtrace]

When submitting logs: please submit them as text and not screenshots.

It was removed from Main site yesterday: https://github.com/osmosis-labs/osmosis-frontend/pull/1049
Can still be found on Frontier.

@JeremyParish69 Can you provide more information, please?
How do we reinstate IXO on the Main site?

@alwyn-ixo Main site tokens require Osmosis Governance approval of the token. Either, Osmosis Governance can vote to incentivize a pool containing the token, or Osmosis governance can vote to add the token to the Main site (without incentivizing any of its pools), which would just be a text proposal.


agent: Runtime error on a customer device

[root@xxx ~]# shellhub-agent
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x909c04]

goroutine 1 [running]:
github.com/shellhub-io/shellhub/pkg/api/client.buildURL(0x1c0d700, 0x90fc4f, 0x5, 0x0, 0x1d4c840)
        /home/xxx/solar/new/xxx-yocto-platform/build/tmp/work/cortexa7hf-neon-vfpv4-jel-linux-gnueabi/shellhub-agent/v0.3.2-r0/build/src/github.com/shellhub-io/shellhub/pkg/api/client/client.go:100 +0xfc
github.com/shellhub-io/shellhub/pkg/api/client.(*client).GetInfo(0x1c0d700, 0x1, 0x1, 0xa69b90)
        /home/xxx/solar/new/xxx-yocto-platform/build/tmp/work/cortexa7hf-neon-vfpv4-jel-linux-gnueabi/shellhub-agent/v0.3.2-r0/build/src/github.com/shellhub-io/shellhub/pkg/api/client/client_public.go:27 +0x48
main.main()
        /home/xxx/solar/new/xxx-yocto-platform/build/tmp/work/cortexa7hf-neon-vfpv4-jel-linux-gnueabi/shellhub-agent/v0.3.2-r0/build/src/github.com/shellhub-io/shellhub/agent/main.go:74 +0x308

This happens when variables are not set. Please adjust it to provide a proper error message which helps user to know what is going on.

@otavio  https://github.com/shellhub-io/shellhub/pull/617
How about let envconfig to handle required env?
I did a few change in main().
 type ConfigOptions struct { runtime error: invalid memory address or nil pointer dereference
	ServerAddress string `envconfig:"server_address" required:"true"`  // envconfig would show error instead of "runtime error: invalid memory address or nil pointer dereference"
	PrivateKey string `envconfig:"private_key" required:"true"`
	TenantID string `envconfig:"tenant_id" required:"true"`
...

	opts := ConfigOptions{}
+	defer envconfig.Usage("shellhub", &opts)                                // present how the config works for user
	// Process unprefixed env vars for backward compatibility
+	envconfig.Process("", &opts)
-	if err := envconfig.Process("", &opts); err != nil {
-		logrus.Panic(err)
-	}

	if err := envconfig.Process("shellhub", &opts); err != nil {
		logrus.Panic(err)
	}

envconfig.Process("", &opts) & envconfig.Process("shellhub", &opts) are useful.
but we don't need to handle first error, otherwise no chance to prcoess with "shellhub".

@otavio  https://github.com/shellhub-io/shellhub/pull/617
How about let envconfig to handle required env?
I did a few change in main().
 type ConfigOptions struct { runtime error: invalid memory address or nil pointer dereference
	ServerAddress string `envconfig:"server_address" required:"true"`  // envconfig would show error instead of "runtime error: invalid memory address or nil pointer dereference"
	PrivateKey string `envconfig:"private_key" required:"true"`
	TenantID string `envconfig:"tenant_id" required:"true"`
...

	opts := ConfigOptions{}
+	defer envconfig.Usage("shellhub", &opts)                                // present how the config works for user
	// Process unprefixed env vars for backward compatibility
+	envconfig.Process("", &opts)
-	if err := envconfig.Process("", &opts); err != nil {
-		logrus.Panic(err)
-	}

	if err := envconfig.Process("shellhub", &opts); err != nil {
		logrus.Panic(err)
	}

envconfig.Process("", &opts) & envconfig.Process("shellhub", &opts) are useful.
but we don't need to handle first error, otherwise no chance to prcoess with "shellhub".

Can you propose a PR to address this?

Can you propose a PR to address this?

https://github.com/shellhub-io/shellhub/pull/617/files
Yes, I did. But not sure how to link issue and PR.

https://github.com/shellhub-io/shellhub/pull/617/files
Yes, I did. But not sure how to link issue and PR.

Oh, it is mixed on the commit. Could you split it out on a specific commit and open a PR?

Oh, it is mixed on the commit. Could you split it out on a specific commit and open a PR?

Fixed in #621.

Fixed in #621.


ROX-14479 Improve error reporting when handling the defaultTLSCertificate

Description
Errors around malformed defaultTLSCertificate are not super helpful. This PR aims at providing better error messages for the customer when such errors occur.
The previous implementation used 2-3 different methods with duplicated logic to load and verify the default TLS certificate. This basically uses a single access point for handling that.

/retest


internal/field: Make BatchInvert tollerate zeros

This is adapted from the upstream PR by @pornin.  While voi currently
does not use the field element batch inversion, fix it for the
off-chance that we will implement the ristretto batch
double-and-compress.

For those that are watching this, the field element batch inversion currently is not used for anything other than tests because I was too lazy to port the Ristretto batch double-and-compress routine from upstream.  So this has absolutely 0 user impact currently.


Plugin Support NetBox v3.3

Proposed functionality
Now that NetBox v3.3 is available I was curious when this plug-in might be updated to support this latest version?  I haven't done any plug-in development myself yet so I don't know how complicated updating the plugin to the latest version of NetBox would be.
Looking at the release notes for NetBox v3.3 I don't notice any breaking changes in the plugins support, so hopefully this could be as simple as just testing and updating the max version supported by the plugin.
Use case
Now that initializers are no longer part of netbox-docker, this plugin is required to support initializing instances of NetBox with data for development.

The is with the cable terminations  which were rewritten in Netbox 3.3.

Ah yeah, that will at least change the example initializers and maybe how they are processed in.
I've been poking at the plugin code as I'm working on my upgrade from 2.10 and found a couple things I'm thinking of opening a PR for to resolve.  While I'm in there I'll see if I can look at the cable initializer.  My setup includes interfaces and cables in the initializer data so I've got a data set to work with.  If I work out the updates needed for v3.3 I'll send in a PR for you to review.

I think we should have a latest or 'dev' version of this plugin, which doesn't set a max version - since its versioned differently it should be obvious that things could break, but it allows the user to try the plugin out with newer versions of netbox?
Its a bit weird to have to fork this, just to be able to spin this on 3.3?

I'm starting to work on updating the plugin to support v3.3 and had a question on the design intentions for the plugin itself related to versions of the plugin and versions of NetBox.
Should the major / minor numbers of the version tie to the version of NetBox directly for support specifically?  Or should versions of the plugin support older versions of NetBox as well?
For example, would  3.3.x of the plugin support NetBox 3.3.x only, but NOT necessarily support NetBox 3.2.x?  Specifically related to the data models and changes between versions?
Or does there need to be logic in the plugin to check the version of NetBox and adjust the logic to backwards support older versions of NetBox?
I couldn't tell from the Releases.md file what was intended.
While I like the idea of backwards support for older versions of NetBox, that will significantly add code to the plugin to handle the discovery of version and changes needed.
Having plugin version tied to NetBox version has the downside of potentially needing to maintain multiple "releases" and back porting updates..
I did look at the Plugin Developers guide for NetBox and there doesn't seem to be any guidance at that level.  Because this plugin is so tightly coupled to the NetBox version and data models, it's probably not as big an issue for other plugins.

I was planing to tie the versions directly together. So version 3.3.x of the plugin should only support Netbox 3.3.y.
When the initializers were included in the Docker image we had the same compatibility. I think back-porting minor bug fixes to an older version isn't that big a problem.
I've already written something about a branching model I intend to use, but that's not committed yet. I will probably do that tomorrow.

That sounds perfect @tobiasge .  I'm working through the changes to the cable model now against my lab setup for v3.3.
I'm looking at how to keep the YAML file format the same as in v3.2 but process it with the changes and addition of "CableTerminations" in v3.3.  So far it looks like it'll work.  I'm hoping to have a functional prototype working by end of the day, and it ready to send over for a review tomorrow.

@hpreston In #19 are some more docs about the development and release process. I hope they help in understanding.

So version 3.3.x of the plugin should only support Netbox 3.3.y.
Again, I think it would be quite nice if we allowed for the latest version (eg. 3.3.x) to support future netbox versions (eg. >= 3.3.x) so that the the latest version will be installable even if its not fully compatible with some later version of NetBox.
Once the fixes are in, it can be capped to whichever version of netbox its compatible with, and a new version with the fixes will be installable in future versions.

Release for Netbox 3.3 support is published.
Closing here, because at the moment I don't like the idea of publishing releases that are not fully compatible with the Netbox version in which they could be installed. I think that will only upset users.


Missing example on passing props

Hello,
I was checking your documentation to see if your project may be a good fit for me.
However, I was not able to find any example regarding props passing to component in UMD.
Can you provide any?
Thanks

Hey, I updated the readme with an example


How do I get GMalloc using x64dbg?

Branch or Release
zDEV-UE4SS v3.0.1
Game and Engine Version
UE4SSTestDemo- UE v5.3.2
Describe the bug
How do I get GMalloc using x64dbg? I don't know how to search for it, better have a screenshot demo. please
Mods directory
To Reproduce
Expected behavior
Screenshots, UE4SS Log, and .dmp file
UE4SS.log
Desktop (please complete the following information):

OS: win11

Additional context
Add any other context about the problem here.

I have to agree, the 6.1 Section of the Guide is extremely hard to follow.
It seems like it expects you to know a lot of things to even understand what you need to do.

It requires reverse engineering knowledge. It's not something for which we can just make an encompassing guide. There are docs for 64dbg.

It requires reverse engineering knowledge. It's not something for which we can just make an encompassing guide. There are docs for 64dbg.

That's obvious now, but not stated there:

For this guide you'll need to know what a root directory and working directory is. A root directory is always the directory that contains ue4ss.dll. A working directory is either the directory that contains ue4ss.dll OR a game specific directory, for example /SatisfactoryEarlyAccess

I'm a software engineer and familiar with modding (just not this specific type) and the listed "general steps" are quite unfortunate in my humble opinion.
But I won't be another annoying user that only complaining about a tool made voluntarily and open-source for the community. So here goes my best try at helping out:

Make a blank shipped game in your game's UE version, with PDBs
This alone already involves several steps:

Get your game UE version. UE4SS detects it. But it can also be checked by using right-click on the .exe in Binaries, opening properties and checking on the details tab. In this case <IP_ADDRESS>
Create an Epic Games account
Download Epic Games Launcher
In the launcher at the left side, go to Unreal Engine, Library tab at the top and Install engine version 5.3.2
Once installed Launch Unreal Engine 5.3.2. Games tab -> Select Blank -> Uncheck Starter Content (Optional to set a Project Name / change location) -> Create
(Assuming Windows OS) Press Platforms button on the top bar -> Packaging Settings -> Check "Include Debug Files in Shipping Builds
Press Platforms button on the top bar ->Windows -> Select "Shipping" -> Package Project and select a folder
Check that the newly packaged blank project contains a .exe along with a .pdb in Binaries in the selected folder

Read game's memory using x64dbg

Install https://x64dbg.com/
Run the .exe at the root folder of the newly packaged blank project (Running the .exe in Binaries might throw an error, running from root works too either way)
Open x64dbg -> File -> Attach -> Select the newly packaged blank project .exe (The one with the path at Binaries)

Look for the signature you need - those can be found below

(Optional but recommended) Connect Epic Games with Github. Login in the Epic Games Website -> Manage Account -> Apps and Accounts -> Github -> Once done, check email and accept invitation to the UE project
(Optional but recommended) Check the source code for the function that is intended to be found in memory. In this case here: https://github.com/EpicGames/UnrealEngine/blob/5.3.2-release/Engine/Source/Runtime/Core/Public/HAL/FMemory.inl#L142
In x64dbg go to Symbols tab -> In the left window select the .exe -> Under the right window search for the function (in this case "FMemory::Free") -> Double click the found Function in the right window
You should be now back at the CPU tab with the address in memory of the start of the selected function

Grab a copy of the bytes from that function, sometimes the header is enough. If it is not, it may be better to grab a call to the function and if it's not a virtual function, you can grab the RIP address there

(Optional but recommended) Install Baymax ToOls plugin for x64dbg
Select some (This is where it is not the same for every game and required magic/"knowledge" starts) address lines -> Right Click -> Copy -> Selection or Selection (Bytes only)
If Baymax ToOls installed, while selecting all the addresses lines composing the function -> Right Click -> Baymax ToOls -> Copy Signature.
Might want to copy both selection types and save them in a file for comparison and reference.

Some context and definitions:
In this context, a Signature refers to a unique sequence or pattern of bytes used to identify a function or piece of code within a binary, such as specific instructions or constants that are unlikely to appear elsewhere. It serves as a recognizable "fingerprint" to locate a particular routine during reverse engineering or patching.
In contrast, a Block of Bytes is simply a contiguous sequence of raw data or instructions without any specific identification purpose. A block of bytes may or may not represent anything meaningful or unique, whereas a signature is carefully chosen to reliably distinguish a particular function or code segment.
RIP (Instruction Pointer Register) is a register in x86-64 architecture that holds the address of the next instruction to be executed. It plays a key role in managing program flow, enabling the CPU to keep track of where it is in the program code.

Open your game's memory in x64dbg and search it for the same block of bytes
If you find it, you can use the swiss army knife tool to extract the AOB for it which you can use in a simple script such as example here

Open the game you want to mod
Attach x64dbg as seen before with the blank project
Search for the saved block of bytes found in the last step
(If nothing found) Search for the pattern from Baymax ToOls
(If nothing found) Try searching parts of the block of bytes (or signature from Baymax ToOls) and compare the addresses block with the one from the blank project.
If nothing found, I don't know. It's beyond my knowledge for now
If found a good match -> Create the lua script to retrieve the address of the function/variable required. -> Put it in UE4SS_Signatures folder in the Binaries of your game folder where UE4SS was installed.
Run the game and UE4SS hopefully works now (Spoiler: In my case it doesn't and gives no error, so no clue what happens)

In my case GMalloc.lua:
function Register()
    return "48 8B D9 48 8B 0D ?? ?? ?? ?? 48 85 C9 75 0C E8 ?? ?? ?? ??"
end

function OnMatchFound(MatchAddress)
    -- Address of the first mov instruction that loads GMalloc
    local MovInstr = MatchAddress + 0x03  -- Offset to the mov instruction with GMalloc (0x00007FF730F9B2C9)

    -- Offset value is encoded after the instruction opcode (3 bytes after the start of the mov)
    local Offset = DerefToInt32(MovInstr + 0x3)

    -- Calculate the address of GMalloc using RIP-relative addressing
    local RIP = MovInstr + 0x7  -- Address of the next instruction
    local GMallocAddress = RIP + Offset

    return GMallocAddress
end

I even did an extra step as debug to go back to running the blank project and attaching x64dbg and calculating manually the Address wanted from the signature used in Lua for the game to mod. (Calculated manually the GMalloc address from the Free function) Then setting the address in GMalloc.lua for the blank project and checking that the Address found is the same as the one auto-detected from UE4SS when running it in the blank project. And it was a match!
Note: It's my first time using x64dbg, reverse engineering the game attached and first time using lua.
Note2: My solution doesn't work for me, I have no clue why. UE4SS gives no useful error so far (it did show other errors when I messed up the lua script or other issues though).
Note3: ChatGPT was quite useful in most of the steps, specially with the Lua script and explaining some terms.

We would really appreciate it if you could make a PR for the docs and add all this useful information yourself! If you don't want to bother (no problemo), could we add it in ourselves? Cheers


Annotations dropped from jobset spec

Annotations for pods seem to be dropped. This is a regression from ~v0.5 as far as I can tell.
What happened:
Applied the following yaml:
apiVersion: jobset.x-k8s.io/v1alpha2
kind: JobSet
metadata:
  name: test-annotations
  annotations:
    alpha.jobset.sigs.k8s.io/exclusive-topology: cloud.google.com/gke-nodepool
    jobset-level-annotation: "true"
spec:
  failurePolicy:
    maxRestarts: 0
  replicatedJobs:
  - name: main
    replicas: 1
    template:
      spec:
        parallelism: 1 # Should be smaller than the number of VMs
        completions: 1 # Same as the above.
        backoffLimit: 0   # When any pod fails, the job is failed
        template:
          metadata:
            annotations:
              template-level-annotation: "true"
          spec:
            containers:
            - name: benchmark
              image: busybox
              command: [ "sleep" ]
              args: [ "infinity" ]

The resulting pod annotations look like
Annotations:      alpha.jobset.sigs.k8s.io/exclusive-topology: cloud.google.com/gke-nodepool
                  batch.kubernetes.io/job-completion-index: 0
                  jobset.sigs.k8s.io/global-replicas: 1
                  jobset.sigs.k8s.io/job-global-index: 0
                  jobset.sigs.k8s.io/job-index: 0
                  jobset.sigs.k8s.io/job-key: 1cb0206240de13510151d6a13a8d1ea3747acf47
                  jobset.sigs.k8s.io/jobset-name: test-annotations
                  jobset.sigs.k8s.io/replicatedjob-name: main
                  jobset.sigs.k8s.io/replicatedjob-replicas: 1
                  jobset.sigs.k8s.io/restart-attempt: 0

What you expected to happen:
Expected jobset-level-annotation: "true" or template-level-annotation: "true" to appear on the pod.
How to reproduce it (as minimally and precisely as possible):
kubectl apply --server-side -f https://github.com/kubernetes-sigs/jobset/releases/download/v0.7.1/manifests.yaml,  kubectl apply the yaml above, then kubectl describe pod to see the annotations.
Environment:

Kubernetes version (use kubectl version):

Client Version: v1.31.2
Kustomize Version: v5.4.2
Server Version: v1.31.2-gke.1518000
- JobSet version (use `git describe --tags --dirty --always`): v0.7.1 (see installation used above)
- Cloud provider or hardware configuration: GKE

@tenzen-y problematic PR is: https://github.com/kubernetes-sigs/jobset/pull/696 ; are you able to submit a fix?
The other issue is that v0.7.1 was incorrectly released, it included the above PR when it should not, I created a new v0.7.2 release to fix the patched v0.7 release.

/assign @imreddy13

/assign @imreddy13

/assign @imreddy13

Thank you for taking this!


asyncio support

Dear mspass team,
to leverage true HPC computing and juggle I/O, CPU and GPU work asyncio support is required.
What are your plans to incorporate native Python coroutines?
Best,
M

Your question is, unfortunately, a bit vague so I have to somewhat guess what the concern is.  As I understand it Python coroutines you refer to are a method of doing asynchronous io in python.  There is no question that balancing I/O and CPU time is critical to optimize performance of a workflow handling large volumes of data.  I first recommend you read this section of the MsPASS User Manual.
A second point I'd make is that because MsPASS is (currently at least) focused on the map-reduce model of parallel computing, I/O is mostly treated as a scheduling problem for the parallel scheduler and the operating system scheduling.   It is our experience that most seismic processing workflows reduce to parallel pipelines with reads and head and writes at the tail of the pipeline.   If the compute tasks are lightweight such jobs get I/O bound quickly.  Howeer, the more you put the pipeline the more negligible I/O becomes.   As the manual section above notes another key thing is avoid database transactions within any workflow a if a job blocks on a database transaction it is easy to create a completely I/O bound job from even a lightweight task.
Finally, you might want to read the new documentation for dask on what they call "Futures" in dask distributed found here.      They are used, in fact, under the hood in the map-reduce approach we have focused on using in MsPASS.
Long answer I hope was helpful.   Happy to continue this dialogue.

Thanks for letting us know about this likely future standard in python.   That could help a lot of pure python codes.  Two points I'd like to make as a followup though:

You should realize that the map-reduce paradigm using MsPASS with spark/dask  is an abstraction of parallelization.   The dask/spark schedulers handle threading and node-parallel processing more or less the same.   I suspect strongly that if the new standards noted are adopted it could enhance dask and/or spark by allowing them to improve the handling of mixed threads and node parallelism.   Today that is a nasty fundamental computer science problem  that is far from solved.  It is particularly nasty in python due to the GIL problem that makes threading impossible in python without some nasty, nonstandard constructs that are fragile for maintenance.   Point is I think this is worth watching but addressing it is way outside the scope of MsPASS development but lands squarely in the laps of the developers of dask/spark.
You are right that older libmseed library was single threaded.  The newer release, however, does have a multithreaded C function.   We used it in MsPASS but realized it it was pointless because of how dask/spark handle threading.   Instead we recommend a usage like that given at the recent Earthscope short course found in this notebook.   The following block of code will run the libmseed indexing, which is the nasty step that touches every byte of ever file, in parallel in a generic way:

import os
import dask.bag as dbg
# remove the comment below if you need to restart this workflow
# at this point c
#db.drop_collection('wf_miniseed')
# Note this dir value assumes the wf dir was created with
# the previous command that also downloads the data from AWS
current_directory = os.getcwd()
dir = os.path.join(current_directory, 'wf')
dfilelist=[]
with os.scandir(dir) as entries:
    for entry in entries:
        if entry.is_file():
            dfilelist.append(entry.name)
print(dfilelist)
mydata = dbg.from_sequence(dfilelist)
mydata = mydata.map(db.index_mseed_file,dir=dir)
index_return = mydata.compute()

Postscript to previous:   In MsPASS you should realize we treat indexing of miniseed files as a fundamentally different operation than reading them.   We, in fact, recommend normal use with large data sets should minimize the number of files and organize data into files grouped in a way appropriate for the data being analyzed.   e.g. event-based processing should have all the data for an event in one file.    One of the best worst things you can do on an HPC system is create the equivalent of a set of SAC files with one signal per file.  You can crash an entire HPC cluster if you try to read millions of files in parallel if the files or stored in a Lustre file system.  Read the tutorials from the Earthscope short course I pointed to above where we discuss some of these issues further.   The final point is that our reader called read_distributed_data will run in parallel once the indexing is done.  There the issue of multithreading is irrelevant as each reader will appear to the operating system as just another program issuing a read request.   Modern operating systems are extremely good at sorting out how to optimally respond to multiple pending read requests from multiple programs.  It happens many times per second on any running computer.


Can not use RDP to managed/interacted Windows Containers

Windows Containers can be managed/interacted with through a RDP session

It does not support that as of now.
https://social.msdn.microsoft.com/Forums/en-US/f4314bc8-52d0-477c-9ecc-86a578b53814/no-support-expected-for-rdp-in-containers-for-windows-server-2016?forum=windowscontainers
For questions like this it's better to ask on the Forum, that's Microsoft way. :)

Yep, this is not supported, I will close the issue.


Hack to better format the RS MP selection dropdown

It's hacky, but it's the fastest thing I can put out at the moment.

For posterity:
Hack: Added a special-case for the RS MP campaign
Note: This implementation assumes that the state code in the CSV matches those in src/strings/data/states.json


ITS Pathfinder Theme conflicts

ITS Pathfinder Theme styling leaks into the statblock, adding unwanted horizontal rule flourishes and breaking name-level alignment.

Research Note
ITS seems to wrap its horizontal rule flourish inside an hr:after block.  Setting that to display: none might work.

Resolved in 1.2.1.


New version release?

30 commits to master branch since 1.3.1 release...
Will it be a new version release someday?

Sure, once all tests pass. Doesn't look like that state is met now.

I was asking because it's been more than two years since last release.
Thank you.

If only more people were involved in PR sending that would fix the driver to work. You can help by fixing any of the issues causing build to fail.

After #303 was merged could you (@oleg-andreyev) please prepare a new release:

send PR with a changelog since last release
decide what is the new release version (based on presense of BC breaks);

Is PHP 5.3 dropping isn't a BC break?


[KaHyPar_jll] Fix compat of boost_jll

Boost breaks ABI in every single version, so we must always specify the compat
bounds with it.  See https://github.com/kahypar/KaHyPar.jl/issues/19.

Thanks for fixing this @giordano! 👍

Thank you @giordano !


Jupyter notebook requests extension install, even though it already is.

Issue Type: Bug
Install python extension, then open a Jupyter notebook ipynb file.
VS Code version: Code 1.57.1 (507ce72a4466fbb27b715c3722558bb15afa9f48, 2021-06-17T13:28:07.755Z)
OS version: Windows_NT x64 10.0.21390
Restricted Mode: No
Remote OS version: Linux x64 4.15.0-1100-azure

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz (8 x 1498)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.60GB (5.41GB free)

Process Argv
--open-url --crash-reporter-id a5d4dc45-11cb-4c6e-a2f0-566594199437 -- vscode://ms-toolsai.vscode-ai/computeInstance/remote?computeId=/subscriptions/7ff9a1f3-e2a1-48ce-8a7d-ebeb53294766/resourceGroups/msft-icon/providers/Microsoft.MachineLearningServices/workspaces/msft-icon/computes/jehrling&sessionId=7HQkv

Screen Reader
no

VM
0%

Item
Value

Remote
Azure ML: jehrling

OS
Linux x64 4.15.0-1100-azure

CPUs
Intel(R) Xeon(R) CPU E5-2673 v3 @ 2.40GHz (2 x 2397)

Memory (System)
13.70GB (10.22GB free)

VM
0%

Extensions (13)

Extension
Author (truncated)
Version

project-manager
ale
12.2.0

vscode-ai-remote
ms-
0.3.0

remote-containers
ms-
0.183.0

remote-ssh
ms-
0.65.7

remote-ssh-edit
ms-
0.65.7

remote-wsl
ms-
0.56.5

vscode-remote-extensionpack
ms-
0.21.0

python
ms-
2021.6.944021595

vscode-pylance
ms-
2021.6.2

jupyter
ms-
2021.6.999406279

vscode-ai
ms-
0.6.23

vscode-ai-remote
ms-
0.3.0

azure-account
ms-
0.9.8

A/B Experiments
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
vspor879:30202332
vspor708:30202333
vspor363:30204092
vspre833:30321513
vsdfh931cf:30280410
vshan820:30294714
vscus158:30321503
vscod805cf:30301675

Thanks for the bug.
Can you include the output from the 'Jupyter' output tab?  It sounds like our detection logic is not picking up the python extension for some reason.

Issues labeled with "Info needed" are closed if we do not receive more information from the issue author in 2 weeks. If you are the issue author and you still are running into this problem, please reactivate with additional information.


update docs to match the pymodaq5 submodule splitting (and a missing picture)

Reference to : AxisBase, DataWithAxis and DataFromPlugins are broken in the documentation :
for instance :
DataFromPlugins is still in pymodaq.utils.data  not in pymodaq_data.data
but i am not sure what to do, change the doc reference back to pymodaq.utils or move the class definition in pymodaq_data ?
It also seems a picture is missing in PyMoDAQ\docs\src\data_management\plotting_data_objects.rst line 364
ERROR: Error in "image" directive:

May be duplicate the documentation for the 2 versions 4.x and 5.x ?

What we could do is:

do the main documentation on pymodaq
do the API documentation on each package where it's relevant.

So for instance we keep the general dicussion about DataManagement on pymodaq but move the API of its objects to where there are defined, that is in pymodaq_data
What do you think?

For the packages, it's perfect.
For the library reference on the website pymodaq.cnrs.fr, may be it would be nice to have the 2 versions next to each other for now. So the users/dev can still debug/understand their 4.x pymodaq setups.
For the DataManagement documentation, you want to remove the import in the exemple and point the module documentation ? How confusing would it be for 4.x users ?
What about the tutorials ? Shall we tag them with version as the library reference ?

Hello both versions of the documentation is available at the moment:

My bad.
Then it's just a correction of the exemples of the 5.0.X_dev data documentation from pymodaq.utils.data to pymodaq_data.data ?
Where do i need to look to get the version selection or select the version i am updating ? I don't have this selection on my local make html.

the documentation are build from the source directly on the readthedocs project. Both branches 4.4.x and 5.0.x_dev can trigger the compilation with their respective target on the doc. So if you want to change the 5.0.x_dev doc, change this branch and commit (PR) and inversely

Those have been corrected and all other the submodule/splitting documentation issues are enhancement, at least to me :)


Trouble removing folders during stacker build with --storage-type overlay

Having trouble removing non-empty folders during the stacker build, if building with --storage-type overlay.
Currently using a stacker.yaml roughly:
test:
    from:
        type: docker
        url: docker://aci-docker-reg.cisco.com/atomix/centos-upstream:latest
    run: |
        rm -rf /etc/yum.repos.d /etc/yum.conf

The command and error I got are:
sudo ../tools/0.5.43/stacker --storage-type overlay --debug build
stacker version v0.5.0-247-gb025034
mount overlay args index=off,lowerdir=/local/c3/t1/roots/test/workaround0:/local/c3/t1/roots/sha256_36b765132fa56fbfeb301bda9c4fd3fdcdf12127d10830d876035ab1cdcf455a/overlay,upperdir=/local/c3/t1/roots/test/overlay,workdir=/local/c3/t1/roots/test/work
initializing stacker recipe: stacker.yaml
substituting $STACKER_ROOTFS_DIR to /local/c3/t1/roots
substituting $STACKER_STACKER_DIR to /local/c3/t1/.stacker
substituting $STACKER_OCI_DIR to /local/c3/t1/oci
stacker build order:
0 build /local/c3/t1/stacker.yaml: requires: []
building: 0 /local/c3/t1/stacker.yaml
substituting $STACKER_ROOTFS_DIR to /local/c3/t1/roots
substituting $STACKER_STACKER_DIR to /local/c3/t1/.stacker
substituting $STACKER_OCI_DIR to /local/c3/t1/oci
preparing image test...
loading docker://aci-docker-reg.cisco.com/atomix/centos-upstream:latest
Getting image source signatures
Copying blob 36b765132fa5 [--------------------------------------] 0.0b / 0.0b
Copying config 3b274d6660 done
Writing manifest to image destination
Storing signatures
unpacking to /local/c3/t1/roots/test
mount overlay args index=off,lowerdir=/local/c3/t1/roots/test/workaround0:/local/c3/t1/roots/sha256_36b765132fa56fbfeb301bda9c4fd3fdcdf12127d10830d876035ab1cdcf455a/overlay,upperdir=/local/c3/t1/roots/test/overlay,workdir=/local/c3/t1/roots/test/work
No uid mappings, running as root
+ rm -rf /etc/yum.repos.d /etc/yum.conf
rm: cannot remove '/etc/yum.repos.d': Directory not empty
lxc-init test<PHONE_NUMBER>2341.988 ERROR    lxc_init - cmd/lxc_init.c:remove_self:211 - No such file or directory - Failed to unmount "/usr/sbin/init.lxc.static"
error: run commands failed: exit status 1
github.com/anuvu/stacker.(*Builder).Build
        /root/go/src/github.com/anuvu/stacker/build.go:454
github.com/anuvu/stacker.(*Builder).BuildMultiple
        /root/go/src/github.com/anuvu/stacker/build.go:561
main.doBuild
        /root/go/src/github.com/anuvu/stacker/cmd/build.go:100
github.com/urfave/cli.HandleAction
        /root/go/pkg/mod/github.com/urfave/cli@v1.22.5-0.20200826140443-af7fa3de115a/app.go:524
github.com/urfave/cli.Command.Run
        /root/go/pkg/mod/github.com/urfave/cli@v1.22.5-0.20200826140443-af7fa3de115a/command.go:173
github.com/urfave/cli.(*App).Run
        /root/go/pkg/mod/github.com/urfave/cli@v1.22.5-0.20200826140443-af7fa3de115a/app.go:277
main.main
        /root/go/src/github.com/anuvu/stacker/cmd/main.go:204
runtime.main
        /usr/local/go1.13.7/src/runtime/proc.go:203
runtime.goexit
        /usr/local/go1.13.7/src/runtime/asm_amd64.s:1357

Kernel is based on version 4.14.209.
The issue does not reproduce with btrfs storage. Also the issue does not reproduce on an Ubuntu host using kernel version 5.4.0-48-generic.

Closing this issue as it was only reproducible with an older, custom kernel.


Memory leaks report on pluck

Hello. Thank you for great tool.
I have question about instruments report.
I have question about query, reported as leaked in instruments
if let row = db.pluck(expression) {
            //word = row[c_word]

            //let now = NSDate().timeIntervalSince1970
            //try db.run(t_words.filter(c_id == row[c_id]).update(c_ai_used_at <- now))
}

if all lines in if block commented, this is how instruments report looks like:

if let row = db.pluck(expression) {
            word = row[c_word]

            let now = NSDate().timeIntervalSince1970
            try db.run(t_words.filter(c_id == row[c_id]).update(c_ai_used_at <- now))
}

if all lines in if block uncommented, this is how instruments report looks like:

Have idea what of errors in my code generate this leaks?

@roma86 Hi,
I am currently experiencing the same issue. Did you find something about it since you created this ticket ?
@stephencelis Do you have any idea ?

@craigzour hello. nope, i just moved to the GRDB lib and stop to investigate.

@roma86 Oh I see. And you do not have any leak at all with this new library ?

@craigzour i can not answer right now, some water is gone from that time. as i can remember there are was some other issues as well which improve my choice to move another lib and i like simple nature of grdb and they say it is match faster. But grdb required slightly more work (fe: models are not so handy as SQLite). You can test it by self with simple clean project and common sql tasks, this should not be hard. I do not want to lie you about leaks in reason i can not remember exactly.


Units get stuck in error state when unsupported relation is joined and then removed

None of the CKF charms handle unsupported relations, which can cause units to stay in an error state after an unsupported relation is joined and then removed. This behaviour is observed if you accidentally relate two charms that are not supposed to be related, they will go to an error state because of the unexpected relation, and then if you try to remove it, it will be deleted, but units will remain in the same state.
Steps to reproduce
I used mlflow and admission-webhook, but this may be the case for other charms.

Deploy Charmed Kubeflow v1.4 in Microk8s 1.21, wait for all charms in the bundle to be active
Deploy mlflow: juju deploy mlflow
Relate mlflow and admission-webhook: juju relate mlflow admission-webhook
Wait for units to crash: juju status mlflow-server admission-webhook should show errors
Remove the offending relation juju remove-relation mlflow admission-webhook
Units remain in the same error status as in step 4: juju status mlflow-server admission-webhook

Since this hasn't really bitten us too much until now and we most probably won't prioritise it soon enough, I'll go on and close this issue.


feat: add TEST_BROWSER_DRIVER=playwright

I actually have no exprience with playwright. Are there any additional things to consider when using it? Specific installation steps?


merge username and view profile, so username links to profile and we don't need different tab for it

Done!


Send arguments instead of positional arguments

Closes #118

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 68.336%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1269

Relevant Lines:
1857

💛  - Coveralls


DPS5020 seconds output lag

When I set my 5020 to 10V, it will only change around 15s later. All functions, including function generator seem delayed.
If the function generator is started, turned off 5s later, the function generator output will appear only 10s later on my scope.

So I also a delay with the ux and other things. I believe it's due to the high refresh rate and interrupt handler. It seems like we build up events in the event queue which then causes the latency. I made some changes locally to change the interrupt handler and change how the screen is updated and it seems to be working fine now. You can take a look at this patch and try it to see if it fixes the issue:
diff --git a/opendps/opendps.c b/opendps/opendps.c
index ad1d4b1..99d55d0 100644
--- a/opendps/opendps.c
+++ b/opendps/opendps.c
@@ -88,7 +90,7 @@
 #endif // CONFIG_SPLASH_SCREEN

 /** How ofter we update the measurements in the UI (ms) */
-#define UI_UPDATE_INTERVAL_MS  (250)
+#define UI_UPDATE_INTERVAL_MS  (50)

 /** Timeout for waiting for wifi connction (ms) */
 #define WIFI_CONNECT_TIMEOUT  (10000)
@@ -518,6 +520,7 @@ static void ui_handle_event(event_t event, uint8_t data)
 #endif // CONFIG_OCP_DEBUGGING
                 ui_flash(); /** @todo When OCP kicks in, show last I_out on screen */
                 opendps_update_power_status(false);
             }
             break;
         case event_ovp:
@@ -532,21 +535,41 @@ static void ui_handle_event(event_t event, uint8_t data)
 #endif // CONFIG_OVP_DEBUGGING
                 ui_flash(); /** @todo When OVP kicks in, show last V_out on screen */
                 opendps_update_power_status(false);
             }
             break;
         case event_button_m1_and_m2:;
             uint8_t target_screen_id = current_ui == &func_ui ? SETTINGS_UI_ID : FUNC_UI_ID; /** Change between the settings and functional screen */
             opendps_change_screen(target_screen_id);
             break;

         case event_button_enable:
             write_past_settings();
+            /** Deliberate fallthrough */
+        case event_button_m1:
+        case event_button_m2:
+        case event_button_sel:
+        case event_button_sel_m1:
+        case event_button_sel_m2:
+        case event_rot_left_m1:
+        case event_rot_right_m1:
+        case event_rot_left_m2:
+        case event_rot_right_m2:
+        case event_rot_left_down:
+        case event_rot_right_down:
+        case event_rot_press:
+        case event_rot_left_set:
+        case event_rot_right_set:
+        case event_rot_left:
+        case event_rot_right:
+            uui_refresh(current_ui, false);
+            break;
         default:
             break;
     }

     uui_handle_screen_event(current_ui, event, data);
-    uui_refresh(current_ui, false);
 }

 /**
@@ -609,6 +632,13 @@ static void ui_tick(void)
     static uint64_t last_tft_flash = 0;
     static uint64_t last_lock_flash = 0;

+    static uint64_t last = 0;
+    /** Update on the first call and every UI_UPDATE_INTERVAL_MS ms */
+    if (last > 0 && get_ticks() - last < UI_UPDATE_INTERVAL_MS) {
+        return;
+    }
+
+    last = get_ticks();
     uui_tick(current_ui);
     uui_tick(&main_ui);

@@ -958,8 +988,6 @@ static void event_handler(void)
                     break;
             }
             ui_handle_event(event, data);
-            // update UI immediately on event
-            ui_tick();
         }
     }
 }

This is very strange. Do you see the delay immediately after power on or after some time of usage?

So it's been a while but if I remember correctly, on power up there's a slight delay (maybe a few seconds or less?) for this behavior. Haven't seen it since the patch I made.


Doubts in the evaluation and optimization section

Hello, I have a question to interrupt you. I reproduced your results experimentally, using a train-before-evaluation approach. But I found that the results after using do_eval (FDE 1.0513439117392331, MR 0.09578942034860154) are far better than when training（FDE: 3.1969465177600322 MR(2m,4m,6m): (0.49478493944897106, 0.23618785871750297, 0.1306969923570714).I found that running do_eval also running recover --model, is the optimization model? If it is a model, the new model generated is not seen.
And the relevant part of the test doesn't seem to be tested after optimization. Evaluate whether the optimization and testing parts are run together. (I just reproduced the results, I didn't study your code, please forgive me if I misunderstood) If you can answer my question, I will be very grateful

The result produced during training is single trajectory prediction while the result produced after evaluation is 6-trajectory prediction (evaluated by argoverse toolkit)

Thanks for your replies, it is very helpful for me


Force pre-declaration of the parameters in the documentation

Write a go generator that will take the contents of docs/parameters.yaml and turn them into an enum.  Remove direct access to viper.Get* and provide a wrapper in the config language that accepts only the enum type as input.

Remove direct access to viper.Get, convert call sites and make it type safe. For remaining add a follow up ticket.


Allow multiple BGP community strings as target for "BGP Community" query type

Feature Description
The "BGP Community" query type allows only one community string as the target at the moment.
Allowing multiple communities would allow for more granular queries.
Environment & Use Case
We operate a global network primarily on Juniper devices and want to use hyperglass to make routing information within our network available to people and teams that do not have direct access to the devices.
Consider the following use case:
A transit provider sends us a full table. The provider tags prefixes with communities based on the region ($comm-region-X) they were received in as well as the info if it was received from an internal peer ($comm-internal), a direct customer ($comm-customer) of theirs, or another transit provider ($comm-external).
If we want to know which prefixes that we receive from that provider are originating from direct customers in Germany for example, we need to include two BGP communities in that query: $comm-region-germany + $comm-customer
Additional Context
Querying multiple community targets can already be done with the customizing options we have but unfortunately not for the structured output.
We have it working for the plaintext output with changing the validation regex for the extended communities to
extended_as: '^[0-9]{0,5}\:[0-9]{1,5}(?: [0-9]{0,5}\:[0-9]{1,5})*$'
which matches either a single extended community 1234:999 or multiple communities separated by a space 1234:999 5678:999
Then, changing the command for the BGP community query from
"show route protocol bgp table inet.0 community {target}"
to
"show route protocol bgp table inet.0 community [ {target} ]"
makes the query work on the devices. The square bracket notation also works with a single community string.
However, since the API is the primary interface through which other teams would interact with hyperglass, having this working with the structured output would be desired.

Hello, I think this is a good idea. However, I'm marking this as blocked due to #110, which is going to change the way commands are implemented as a whole, so I'd rather not but a bunch of work into this request just to have to redo it anyway.
Thanks!

Sounds good, thanks!


updated lineplot() arguments

These are just small changes for updated packages:
In commit 1d9d018:

Latest version of seaborn package where it is supported to pass x and y as arguments for lineplot() (positional) is v0.10 (link) .
Since version 0.11 (latest is 0.12) lineplot() takes x and y only as keyword argument (and also the new parameter data) is added

In commit d01ebf4:

There is an unused enumerate() which is removed to make code cleaner and easier to read
also n_classifiers variable has no use and it's unnecessary to declare/define.

In commit f471710:

as in Seaborn docs FacetGrid, Does not have any argument named size. Instead of size you should use height and aspect

In commit 327afbc:

The same issue with lineplot() in 1d9d018
Small fixes to text and codes

In commit 8c1ef29:

Using f-strings instead of using + operator
using name of variables in output instead of the whole string content, so it'll be easier to read

@microsoft-github-policy-service agree

جميل

@carlotta94c @gdequeiroz I think it would be good if you guys take a look at this after 4 month


Room assigning react francesca

Guys,
I finished the assign room form.
*We are now able to assign multiple rooms to the same room attendant.
*When a room is assigned the availability of it goes directly to false.
*The list of rooms you can choose when assigning a room is only of the available rooms. The rooms unavailable are not going to be an option!
*We can also edit the assigned room so to assign them to different room attendants or change guest names, checkin, checkout and so on.

Looks good to me. Thanks for doing all the className parts.


Deployment commit for prod-beta

Merged stage-stable branch to prod-beta.
Use latest commit to update namespace ref in app-interface repo. Don't use merge commit, SHAs must be unique when images are created for each branch.

Codecov Report
Attention: Patch coverage is 60.00000% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 76.96%. Comparing base (3e5b272) to head (de3bf7f).

Files
Patch %
Lines

src/api/api.ts
0.00%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           prod-beta    #1103   +/-   ##
==========================================
  Coverage      76.96%   76.96%
==========================================
  Files             68       68
  Lines            673      673
  Branches         120      120
==========================================
  Hits             518      518
  Misses           139      139
  Partials          16       16

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add support for win32-input-mode to conhost, ConPTY, Terminal

Adds support for win32-input-mode to conhost, conpty, and the Windows
Terminal.

The shared terminalInput class supports sending these sequences when
a VT client application requests this mode.
ConPTY supports synthesizing INPUT_RECORDs from the input sent to it
from a terminal
ConPTY requests this mode immediately on startup (if started with a
new flag, PSEUDOCONSOLE_WIN32_INPUT_MODE)
The Terminal now supports sending this input as well, when conpty asks
for it.

Also adds a new ConPTY flag PSEUDOCONSOLE_WIN32_INPUT_MODE which
requests this functionality from conpty, and the Terminal requests this
by default.
Also adds experimental.input.forceVT as a global setting to let a user
opt-out of this behavior, if they don't want it / this ends up breaking
horribly.
Validation Steps Performed

played with this mode in vtpipeterm
played with this mode in Terminal
checked a bunch of scenarios, as outlined in a comment on #4999

References #4999: The megathread
References #5887: The spec
Closes #879
Closes #2865
Closes #530
Closes #3079
Closes #1119
Closes #1694
Closes #3608
Closes #4334
Closes #4446

@DHowett I'm totally on board with proposal 2, the opt-out setting.
I'm less on board with the opt-in for conpty consumers, since that's us making another change to the OS API surface, and we haven't even gotten to the last conpty flag we added. Though, I suppose that was opt-in behavior as well. @miniksa what are your thoughts on making this a flag to conpty?

For 1, I was never a huge fan of ConPTY unconditionally sending ^[[9001h on every startup in case the attached Terminal knows what that means. But @zadjii-msft convinced me that terminals receive stuff they don't understand all the time and just ignore it. So I didn't push it. But if @DHowett thinks we need an escape hatch on this one, then I'm fine with a flag/argument in the CreatePsuedoConsole and startup args for openconsole.exe to say "hey I'm a terminal that could accept 9001h if you said something about it." It just feels very un-VT to do it that way. The Device Attributes queries seem more up the alley, but that's probably another can of worms.
For 2, I don't really understand why we'd make the Terminal opt out of sending win32-format full key structures if it was asked. What scenario does that resolve? Just an unknown theoretical problem where the win32 style keys don't work but the unix style did?

I don't really understand why we'd make the Terminal opt out of sending win32-format full key structures if it was asked.

I mean, we're only reworking how input works in a product we shipped to hundreds of thousands of people, and we've been bit by even more theoretical things than this 😉

For 1, I'm less concerned with a terminal getting it and doing the wrong thing with it. I'm more concerned with a terminal getting it and doing the right thing with it, and then breaking things somewhere we didn't expect. The concern James brought up in the spec review was that the client may be using a different keyboard layout than the server, for example, in the SSH case. SSH is the middle party for us in conhost<->conhost-pty communication, and we could (I won't go so far as to say are!) be building a bug factory for them.
I don't necessarily need for it to be a flag, I'm just looking for peace of mind. :smile:

Okay, I'm inclined to agree with adding both flags because of the fact that we know that something is going to bite us in the butt and we don't know what it is or how big of a scope it will be.
It feels risky and while in the past, we'd be reactive about this and just "add the flags later if complaining is loud", if it's cheap enough, maybe we should just be ready for it this time.

Conversely, I'm okay to wait to add the flag. Huh.

If you get the SA fixed and the commit message ready, I'll mark it for automerge even after you go home for the day.

Linux port of Far Manager now also supports win32-input-mode spec
https://github.com/elfmz/far2l
The first independent implementation.

Wow, this is really cool! Thanks for letting us know!

Wow, this is really cool! Thanks for letting us know!

Implementing win32-input-mode protocol discovered an annoying issue. I would appreciate if someone could look into it #15083


Prisma can't run in WebContainer

Bug description
https://github.com/stackblitz/webcontainer-core/issues/954
How to reproduce

Go to Stackblitz Codeflow
Use Prisma in deps
Run pnpm
See error

Expected behavior
No response
Prisma information

// Add your schema.prisma

// Add your code using Prisma Client

Environment & setup

OS:
Database:
Node.js version:

Prisma Version

Related and some background discussion: https://github.com/prisma/prisma/issues/8626
We can keep this issue though to track the general problem as a bug.

Thank you for such a fast reply. I will read the thread. :)

Simple and straightforward reproduction: https://stackblitz.com/~/github.com/janpio/stackblitz-codeflow-prisma
Some background info from Stackblitz on their side: https://github.com/stackblitz/webcontainer-core/issues/954#issuecomment-1417709580

Regarding "socket hang up", that's due to CORS because binaries.prisma.sh is blocking requests from *.staticblitz.com. If you can enable CORS for that domain the socket shouldn't hang up anymore.

Unfortunately that will still not let it execute the engine after downloading of course.

This Chrome extension is a simple way to emulate CORS being enabled (careful, only keep active while testing): https://chrome.google.com/webstore/detail/cors-unblock/lfhmikememgdcahcdlaciloancbhjino
With it enabled, Stackblit can download the engines, but still not execute them of course. Here is the output of prisma -v in that situation:
~/janpio/stackblitz-codeflow-prisma main
❯ npx prisma -v
prisma:warn Prisma failed to detect the libssl/openssl version to use, and may not work as expected. Defaulting to "openssl-1.1.x".
Please manually install OpenSSL and try installing Prisma again.
prisma:warn Prisma doesn't know which engines to download for the Linux distro "undefined". Falling back to Prisma engines built "debian".
Please report your experience by creating an issue at https://github.com/prisma/prisma/issues so we can add your distro to the list of known supported distros.
prisma:warn Prisma failed to detect the libssl/openssl version to use, and may not work as expected. Defaulting to "openssl-1.1.x".
Please manually install OpenSSL and try installing Prisma again.
prisma:warn Prisma doesn't know which engines to download for the Linux distro "undefined". Falling back to Prisma engines built "debian".
Please report your experience by creating an issue at https://github.com/prisma/prisma/issues so we can add your distro to the list of known supported distros.
Error: Unable to require(`/home/janpio/stackblitz-codeflow-prisma/node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node`).
The Prisma engines do not seem to be compatible with your system. Please refer to the documentation about Prisma's system requirements: https://pris.ly/d/system-requirements

Details: Cannot load native addon because loading addons is disabled<EMAIL_ADDRESS>    at loadLibrary (file:///home/janpio/stackblitz-codeflow-prisma/node_modules/prisma/build/index.js:93541:11)
    at getEngineVersion (file:///home/janpio/stackblitz-codeflow-prisma/node_modules/prisma/build/index.js:93555:16)
Error: Command failed with exit code 2<EMAIL_ADDRESS>--version
<EMAIL_ADDRESS>line 2: a command can only contain words and redirects
    at makeError (file:///home/janpio/stackblitz-codeflow-prisma/node_modules/prisma/build/index.js:3640:18)
    at handlePromise (file:///home/janpio/stackblitz-codeflow-prisma/node_modules/prisma/build/index.js:4408:33)
    at async getEngineVersion (file:///home/janpio/stackblitz-codeflow-prisma/node_modules/prisma/build/index.js:93558:20) {
  shortMessage: 'Command failed with exit code 2<EMAIL_ADDRESS>--version',
  command<EMAIL_ADDRESS>--version',
  escapedCommand<EMAIL_ADDRESS>--version',
  exitCode: 2,
  signal: undefined,
  signalDescription: undefined,
  stdout: '',
  stderr<EMAIL_ADDRESS>line 2: a command can only contain words and redirects',
  failed: true,
  timedOut: false,
  isCanceled: false,
  killed: false
}
prisma                  : 4.10.1
@prisma/client          : Not found
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : E_CANNOT_RESOLVE_VERSION (at<EMAIL_ADDRESS>Migration Engine        : E_CANNOT_RESOLVE_VERSION (at<EMAIL_ADDRESS>Format Wasm             : @prisma/prisma-fmt-wasm 4.10.1-1.80b351cc7c06d352abe81be19b8a89e9c6b7c110
Default Engines Hash    : aead147aa326ccb985dcfed5b065b4fdabd44b19
Studio                  : 0.481.0

The relevant error messages for Query Engine node-API libary:
Error: Unable to require(`/home/janpio/stackblitz-codeflow-prisma/node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node`).
The Prisma engines do not seem to be compatible with your system. Please refer to the documentation about Prisma's system requirements: https://pris.ly/d/system-requirements

Details: Cannot load native addon because loading addons is disabled<EMAIL_ADDRESS>    at loadLibrary (file:///home/janpio/stackblitz-codeflow-prisma/node_modules/prisma/build/index.js:93541:11)
    at getEngineVersion (file:///home/janpio/stackblitz-codeflow-prisma/node_modules/prisma/build/index.js:93555:16)
Error: Command failed with exit code 2<EMAIL_ADDRESS>--version

and Migration Engine binary:
<EMAIL_ADDRESS>line 2: a command can only contain words and redirects
    at makeError (file:///home/janpio/stackblitz-codeflow-prisma/node_modules/prisma/build/index.js:3640:18)
    at handlePromise (file:///home/janpio/stackblitz-codeflow-prisma/node_modules/prisma/build/index.js:4408:33)
    at async getEngineVersion (file:///home/janpio/stackblitz-codeflow-prisma/node_modules/prisma/build/index.js:93558:20) {
  shortMessage: 'Command failed with exit code 2<EMAIL_ADDRESS>--version',
  command<EMAIL_ADDRESS>--version',
  escapedCommand<EMAIL_ADDRESS>--version',
  exitCode: 2,
  signal: undefined,
  signalDescription: undefined,
  stdout: '',
  stderr<EMAIL_ADDRESS>line 2: a command can only contain words and redirects',
  failed: true,
  timedOut: false,
  isCanceled: false,
  killed: false
}

And for completeness, also the Query Engine binary (via PRISMA_CLI_QUERY_ENGINE_TYPE=binary):
Error: Command failed with exit code 2<EMAIL_ADDRESS>--version
<EMAIL_ADDRESS>line 4: a command can only contain words and redirects
    at makeError (file:///home/janpio/stackblitz-codeflow-prisma/node_modules/prisma/build/index.js:3640:18)
    at handlePromise (file:///home/janpio/stackblitz-codeflow-prisma/node_modules/prisma/build/index.js:4408:33)
    at async getEngineVersion (file:///home/janpio/stackblitz-codeflow-prisma/node_modules/prisma/build/index.js:93558:20) {
  shortMessage: 'Command failed with exit code 2<EMAIL_ADDRESS>--version',
  command<EMAIL_ADDRESS>--version',
  escapedCommand<EMAIL_ADDRESS>--version',
  exitCode: 2,
  signal: undefined,
  signalDescription: undefined,
  stdout: '',
  stderr<EMAIL_ADDRESS>line 4: a command can only contain words and redirects',
  failed: true,
  timedOut: false,
  isCanceled: false,
  killed: false
}

(Technically we would now be in a position to prisma generate --data-proxy and then use that in an app to send queries via Data Proxy. Currently the Data Proxy does not set any CORS headers and does not respond to preflight requests though - starting a discussion about that internally.)

Hey there! I'm also interested in running prisma+sqlite in a webcontainer. https://binaries.prisma.sh looks like a regular aws s3, is there a reason not to set permissive AllowedOrigins?

I'm building an in-browser demo of graphql+prisma aimed at a (relatively) large audience of beginners, so I'd rather avoid telling them to install a browser extension designed to reduce the security of their browser, but I will go this route for now

Yes, it is not needed for Prisma's normal use case

We might consider installing a WASM build of prisma a normal use case, as WASM is now officially supported

I am trying to a fullstack project on Stackblitz too and if you go in the prisma-generated directory and run
pnpm prisma generate, you will see that command never gives you your prompt back.

Anyone managed to get prisma to install, generate a client and push to a db successfully from StackBlitz yet ?

Normal Prisma is not possible in Webcontainers because of this limitation: https://webcontainers.io/guides/troubleshooting#cannot-load-native-addon-error
There might be Wasm-based build of Prisma for specific databases soon, that might circumvent this problem.

Any update on this? I tried prisma generate --data-proxy but it still doesn't work for me. Any workaround?

Facing same issue, is there workaround, chrome extension didn't work

Also facing same issue still a year a later.