Add CNI version skew integration test.

For https://github.com/istio/istio/issues/32298
Part of CNI beta graduation requirement: https://docs.google.com/document/d/1RMGiH-xFmmnct7bkBgmESQ4FONNuZ1J1V4oWQ8aB5qk/edit
This test will only run as part of postsubmit. I test ran it at presubmit by commenting out postsubmit label, and here is the result: https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio/34202/integ-cni-k8s-tests_istio/1418065931690577920

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

/test all

@bianpengyuan: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
524147dc094067b034bdcf3dcb3cd59587c8cf7e
link
/test release-notes_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
524147dc094067b034bdcf3dcb3cd59587c8cf7e
link
/test release-notes_istio

analyze-tests_istio
524147dc094067b034bdcf3dcb3cd59587c8cf7e
link
/test analyze-tests_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
524147dc094067b034bdcf3dcb3cd59587c8cf7e
link
/test release-notes_istio

analyze-tests_istio
524147dc094067b034bdcf3dcb3cd59587c8cf7e
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
524147dc094067b034bdcf3dcb3cd59587c8cf7e
link
/test integ-pilot-k8s-tests_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
524147dc094067b034bdcf3dcb3cd59587c8cf7e
link
/test release-notes_istio

analyze-tests_istio
524147dc094067b034bdcf3dcb3cd59587c8cf7e
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
524147dc094067b034bdcf3dcb3cd59587c8cf7e
link
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
524147dc094067b034bdcf3dcb3cd59587c8cf7e
link
/test integ-cni-k8s-tests_istio

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.

/test all

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-cni-k8s-tests_istio
524147dc094067b034bdcf3dcb3cd59587c8cf7e
link
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
6310805c5a9799b1bc2e7df33b9eac29bb8b6a56
link
/test integ-pilot-k8s-tests_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
6310805c5a9799b1bc2e7df33b9eac29bb8b6a56
link
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
6310805c5a9799b1bc2e7df33b9eac29bb8b6a56
link
/test integ-cni-k8s-tests_istio

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.

/test all

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
6310805c5a9799b1bc2e7df33b9eac29bb8b6a56
link
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
6310805c5a9799b1bc2e7df33b9eac29bb8b6a56
link
/test integ-cni-k8s-tests_istio

analyze-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test analyze-tests_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
6310805c5a9799b1bc2e7df33b9eac29bb8b6a56
link
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
6310805c5a9799b1bc2e7df33b9eac29bb8b6a56
link
/test integ-cni-k8s-tests_istio

analyze-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test analyze-tests_istio

lint_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test lint_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
6310805c5a9799b1bc2e7df33b9eac29bb8b6a56
link
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
6310805c5a9799b1bc2e7df33b9eac29bb8b6a56
link
/test integ-cni-k8s-tests_istio

analyze-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test analyze-tests_istio

lint_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test lint_istio

integ-helm-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-helm-tests_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
6310805c5a9799b1bc2e7df33b9eac29bb8b6a56
link
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
6310805c5a9799b1bc2e7df33b9eac29bb8b6a56
link
/test integ-cni-k8s-tests_istio

analyze-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test analyze-tests_istio

lint_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test lint_istio

integ-helm-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-security-k8s-tests_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
6310805c5a9799b1bc2e7df33b9eac29bb8b6a56
link
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
6310805c5a9799b1bc2e7df33b9eac29bb8b6a56
link
/test integ-cni-k8s-tests_istio

analyze-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test analyze-tests_istio

lint_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test lint_istio

integ-helm-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-security-k8s-tests_istio

integ-operator-controller-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-operator-controller-tests_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
6310805c5a9799b1bc2e7df33b9eac29bb8b6a56
link
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
6310805c5a9799b1bc2e7df33b9eac29bb8b6a56
link
/test integ-cni-k8s-tests_istio

analyze-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test analyze-tests_istio

lint_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test lint_istio

integ-helm-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-security-k8s-tests_istio

integ-operator-controller-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-security-multicluster-tests_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-cni-k8s-tests_istio
6310805c5a9799b1bc2e7df33b9eac29bb8b6a56
link
/test integ-cni-k8s-tests_istio

analyze-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test analyze-tests_istio

lint_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test lint_istio

integ-helm-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-security-k8s-tests_istio

integ-operator-controller-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-security-multicluster-tests_istio

integ-pilot-k8s-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-pilot-k8s-tests_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test analyze-tests_istio

lint_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test lint_istio

integ-helm-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-security-k8s-tests_istio

integ-operator-controller-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-security-multicluster-tests_istio

integ-pilot-k8s-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-cni-k8s-tests_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test analyze-tests_istio

lint_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test lint_istio

integ-helm-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-security-k8s-tests_istio

integ-operator-controller-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-security-multicluster-tests_istio

integ-pilot-k8s-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-cni-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-telemetry-mc-k8s-tests_istio

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.

/test all

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-security-multicluster-tests_istio

integ-cni-k8s-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
93fc21b1b7558afeaadda4cc342cabd5ad2650c8
link
/test integ-pilot-k8s-tests_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
1f7608c788b99fa43f00c8a3a0d24543ac3f8c1f
link
/test integ-security-multicluster-tests_istio

integ-pilot-k8s-tests_istio
93fc21b1b7558afeaadda4cc342cabd5ad2650c8
link
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
93fc21b1b7558afeaadda4cc342cabd5ad2650c8
link
/test integ-cni-k8s-tests_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
93fc21b1b7558afeaadda4cc342cabd5ad2650c8
link
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
93fc21b1b7558afeaadda4cc342cabd5ad2650c8
link
/test integ-cni-k8s-tests_istio

integ-pilot-multicluster-tests_istio
93fc21b1b7558afeaadda4cc342cabd5ad2650c8
link
/test integ-pilot-multicluster-tests_istio

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.

/test all

/test all

@bianpengyuan: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-cni-k8s-tests_istio
0c053dbf69bbe9f21201f28d4e26e974c43a5223
link
/test integ-cni-k8s-tests_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-cni-k8s-tests_istio
0c053dbf69bbe9f21201f28d4e26e974c43a5223
link
/test integ-cni-k8s-tests_istio

integ-security-multicluster-tests_istio
0c053dbf69bbe9f21201f28d4e26e974c43a5223
link
/test integ-security-multicluster-tests_istio

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.

/test all

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-cni-k8s-tests_istio
0c053dbf69bbe9f21201f28d4e26e974c43a5223
link
/test integ-cni-k8s-tests_istio

integ-security-multicluster-tests_istio
0c053dbf69bbe9f21201f28d4e26e974c43a5223
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
dd1ca10c5b3284838703e54d9fac2a2b45495a1c
link
/test integ-telemetry-mc-k8s-tests_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-cni-k8s-tests_istio
0c053dbf69bbe9f21201f28d4e26e974c43a5223
link
/test integ-cni-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
dd1ca10c5b3284838703e54d9fac2a2b45495a1c
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-multicluster-tests_istio
dd1ca10c5b3284838703e54d9fac2a2b45495a1c
link
/test integ-security-multicluster-tests_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
dd1ca10c5b3284838703e54d9fac2a2b45495a1c
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-multicluster-tests_istio
dd1ca10c5b3284838703e54d9fac2a2b45495a1c
link
/test integ-security-multicluster-tests_istio

integ-cni-k8s-tests_istio
dd1ca10c5b3284838703e54d9fac2a2b45495a1c
link
/test integ-cni-k8s-tests_istio

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.

/test all

@bianpengyuan: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
053cc6c56dd3869dbc7d58cd9ab6f11aec8e8f4f
link
/test integ-security-multicluster-tests_istio

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.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
b6278ed1a05ddeb9fcf0d839e87a56d4950c27e3
link
/test integ-pilot-multicluster-tests_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
b6278ed1a05ddeb9fcf0d839e87a56d4950c27e3
link
/test integ-pilot-multicluster-tests_istio

integ-cni-k8s-tests_istio
b6278ed1a05ddeb9fcf0d839e87a56d4950c27e3
link
/test integ-cni-k8s-tests_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
b6278ed1a05ddeb9fcf0d839e87a56d4950c27e3
link
/test integ-pilot-multicluster-tests_istio

integ-cni-k8s-tests_istio
b6278ed1a05ddeb9fcf0d839e87a56d4950c27e3
link
/test integ-cni-k8s-tests_istio

integ-helm-tests_istio
c7d16edf0f8f5280e5f40d03cc6affde3d5c700d
link
/test integ-helm-tests_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
b6278ed1a05ddeb9fcf0d839e87a56d4950c27e3
link
/test integ-pilot-multicluster-tests_istio

integ-cni-k8s-tests_istio
b6278ed1a05ddeb9fcf0d839e87a56d4950c27e3
link
/test integ-cni-k8s-tests_istio

integ-helm-tests_istio
c7d16edf0f8f5280e5f40d03cc6affde3d5c700d
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
c7d16edf0f8f5280e5f40d03cc6affde3d5c700d
link
/test integ-pilot-k8s-tests_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-helm-tests_istio
c7d16edf0f8f5280e5f40d03cc6affde3d5c700d
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
c7d16edf0f8f5280e5f40d03cc6affde3d5c700d
link
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
c7d16edf0f8f5280e5f40d03cc6affde3d5c700d
link
/test integ-cni-k8s-tests_istio

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.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-cni-k8s-tests_istio
c6d928db2d9143a6bc4c69647f174a583e250a9f
link
/test integ-cni-k8s-tests_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-cni-k8s-tests_istio
c6d928db2d9143a6bc4c69647f174a583e250a9f
link
/test integ-cni-k8s-tests_istio

integ-pilot-multicluster-tests_istio
f3796d5ca06a7daaf78b4698c332d2e64bf6132e
link
/test integ-pilot-multicluster-tests_istio

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.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
f3796d5ca06a7daaf78b4698c332d2e64bf6132e
link
/test integ-pilot-multicluster-tests_istio

integ-cni-k8s-tests_istio
f3796d5ca06a7daaf78b4698c332d2e64bf6132e
link
/test integ-cni-k8s-tests_istio

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.

Last passed run: https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio/34202/integ-cni-k8s-tests_istio/1418345376619958272

@Monkeyanator gentle ping, any more comments? Thanks!

@howardjohn @stevenctl please take a look, thanks!

@bianpengyuan: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
4a2b316871f656ccbb24d21c8ef2686da0cc929a
link
/test release-notes_istio

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.


Enable autofs, adauth, pam, lustre_client roles

All the roles are disabled by default so that sites who don't need them aren't affected.

autofs: the configuration part is disabled by default. By installing and starting autofs is not. I guess that is fine.
adauth: ok :)
pam: this does things by default - it overwrites system-auth file. I'll wrap up a pr
lustre_client: ok

PR: https://github.com/mhakala/ansible-role-pam/pull/3
New issue I'd like a response to before merging: https://github.com/mhakala/ansible-role-pam/issues/4

These issues should now have been addressed in https://github.com/jabl/ansible-role-pam


Added preAuthMessage property

This makes it possible to send CAP REQ message before passing PASS and NICK, which makes it possible to recive GLOBALUSERSTATE message.

After a little refactor I reopened a PR on upstream: communi/libcommuni#98


Add test for svelte and improve error message when plugin is missing

@Paul-Hebert asked whether Pleasantest supported Svelte and I realized I hadn't actually tested it out. This PR adds a test to make sure it works (it did, without changes).
I also added a suggestion for error messages when there are syntax errors while parsing a non-JS file that is imported into JS (i.e. it will suggest adding a plugin for parsing .vue or .svelte files if you import them and there is a parse error after all user plugins have run)

This is awesome, thanks @calebeby !


Restore missing merged syllables to the OT Chronicle CONLLU file

The following merged Old Tibetan syllables can be found in the Unicode version of the OT Chronicle (which I assume is a more or less accurate conversion of OTDO's Wylie), but are missing from BRAT and our CoNLL-U file.
The reference preceding the syllable gives an approximate location of where the syllable should occur.
otchronicle:001:T80 - བགྱིསྣ
otchronicle:002:T5 - ཚངསུ་
otchronicle:002:T632 - ལྟསུ་
otchronicle:002:T985 - རླགི་
otchronicle:003:T1135 - རླགྀ་
otchronicle:003:T1317 - myI la 'phrog (47) [-]om
otchronicle:003:T40 - བརྩིགསོ
otchronicle:003:T1419 - གཤེགསོ
otchronicle:003:T42 - ལགསོ
otchronicle:003:T1437 - གཤེགསོ
otchronicle:003:T1448 - གཤེགསོ
otchronicle:003:T52 - མཆིསྣ
otchronicle:003:T49 - འདའསོ
otchronicle:004:T10 - ལྕེབསའོ
otchronicle:004:T1567 - མནངསུ་
otchronicle:004:T17 - གཤེགསོ
-- basically... every occurrence of གཤེགསོ... find all of them
otchronicle:004:T1580 - གསུངསོ
-- search for more གསུངསོ, you'll find missing ones
otchronicle:004:T36 - གཤེགསའོ
otchronicle:004:T1802 - འཛངསོ
otchronicle:004:T52 - ལགསོ
otchronicle:006:T2 - བྱསོ (occurs three times close together)
otchronicle:006:T3201 - གསགྀ་
otchronicle:007:T3769 - བསྒོ་ (occurs twice in vicinity)
otchronicle:008:T4344 - སྐུགསོ
otchronicle:009:T4522 - མོལ་
otchronicle:009:T4534 - བཏམསོ
otchronicle:009:T4551 - འཐབསོ
otchronicle:009:T28 - གཐོགསོ
otchronicle:009:T4940 - བཀྱེའོ
otchronicle:009:T43 - ཕགྀ་
otchronicle:010:T14 - བཏགསོ
otchronicle:011:T30 - འབངསུ་
otchronicle:011:T6340 - བླངསོ
otchronicle:012:T33 - བདགྀ་
otchronicle:012:T6960 - as above
otchronicle:014:T3 - བརྩིགསོ
otchronicle:015:T8019 - བདགྀ་
otchronicle:015:T8276 - འབངསུ་
otchronicle:016:T8645 - རིངོ
otchronicle:016:T8753 - བདགྀ་
otchronicle:016:T8759 - བོམསུ
otchronicle:016:T8879 - བདགྀ་
otchronicle:016:T8983 - བརླགོ
otchronicle:016:T9015 - སྟགྀ་
otchronicle:017:T9185 - འབངསུ་
otchronicle:017:T9254 - མོལ་
-- check for other cases of missing མོལ་ - there should be a few
otchronicle:018:T20 - བཏགསའོ
otchronicle:018:T22 - ཡུངསུ་
otchronicle:018:T37 - སྟགྀ་
otchronicle:020:T11075 - བདགྀ་
otchronicle:020:T11322 - སྟགི་
otchronicle:021:T11577 - ཐབསུ
otchronicle:021:T11607 - མཆིསོ
otchronicle:022:T4 - གདངསུ་
otchronicle:022:T12204 - མོལ་ (2 cases)
otchronicle:025:T8 - see ཡར་ཀྱྀ་*ni་ལྷོ་རྔེགས་ཟའ in Tibetan Unicode
otchronicle:026:T14134 - ཐུངེ་
otchronicle:026:T14207 - གཆྀགི་
otchronicle:027:T20 - བཏགསོ
otchronicle:027:T14844 - འབངསུ་ (2 cases)
Corrections should be made directly to the CoNLL-U file @FChrispz

@heacu all the above syllables have been restored in the CONLL-U file


Add client header for MVG

Right now we do not have any data how many clients use MVG. This dadta will help to make future decisions about MVG backward compatibility and notify customers that need to update MVG.
Suggested solution:
Add a standard "User-Agent" HTTP header to the http client used in MVG in the format: "User-Agent: mvg / v1.0.0". Consider adding python version as well if not too complex.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent

I am currently blocked by tests problem (they stuck at some point)
https://github.com/vikinganalytics/mvg/actions/runs/5542515116


yii\db\Query binding not asked param to query

I see a strange behavior in yii\db\Query() because it adds a new not asked bind parameter.
What steps will reproduce the problem?
$query_template = [
    'select' => [
        'id',
        'foo AS bar',
    ],
    'from' => 'my_table',
    'where' => ['id' => ':my_placeholder'] // <<<<<<
];

$query = new Query();

// it just set the query clauses automatically
foreach ($query_template as $clause => $data) {
    $query->$clause($data);
}

$query->addParams([':my_placeholder' => 123);

$result = $query->createCommand($db)->queryAll();

What is the expected result?
SELECT `id`, `foo` AS `bar` FROM `my_table` WHERE `id`=123

What do you get instead?
SELECT `id`, `foo` AS `bar` FROM `my_table` WHERE `id`=:qp1      # why :qp1?

// params Yii is trying to bind:
Array
(
    [:my_placeholder] => 123 // <<<<< should be this
    [:qp1] => :my_placeholder // <<<<< dont know where it comes from
)

<response>
<link type="text/css" id="dark-mode" rel="stylesheet" href=""/>
<name>Database Exception</name>
<message>
SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens The SQL being executed was: SELECT `id`, `foo` AS `bar` FROM `my_table` WHERE `id`=':my_placeholder'
</message>
0
<type>yii\db\Exception</type>
<file>
/home/...../vendor/yiisoft/yii2/db/Schema.php
</file>
<line>595</line>

Additional info

Q
A

Yii version
dev-master (installed from 3 days ago)

PHP version
7.1

Operating system
Linux Deepin 15.4.1

I found the problem!
The where attribute should not be using array but only string:
'where' => 'id = :my_placeholder'

or simply 'where' => ['id' => 123], see http://www.yiiframework.com/doc-2.0/guide-db-query-builder.html#hash-format

Using the Hash Format, Yii internally uses parameter binding so in contrast to the string format, here you do not have to add parameters manually.

Yeah, but a placeholder is required there (it is a requirement of my system).


empty

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please add bot automerge

@skshetry I think you need to create an issue instead for that.

Ahh, okay. Thanks @efiop. I only read the text at the top:
The webservice also listens to issues and PR comments, so that you can ask for the following services to be done:


The latest Linux release package has a version error.

Describe the bug
The latest Linux release package has a version error.
Steps to reproduce
wget https://github.com/alibaba/opentelemetry-go-auto-instrumentation/releases/download/v0.6.0/otel-linux-amd64
./otel-linux-amd64  version
Expected behavior
print the correct version.
Actual behavior

opentelemetry-go-auto-instrumentation version
v0.6.0
Environment
OS:
Ubuntu
Additional context
No response

cc @123liuziming

It's a known bug, will be fixed in PR https://github.com/alibaba/opentelemetry-go-auto-instrumentation/pull/269

You can review the PR~

@123liuziming Maybe we should release test/verifier?


FIX: can not compile generated code

Problem: for files '123.png' and 'img-123.png' current ExportDataAsCode implementation produce uncompilable code, since ExportDataAsCode generates incorrect macro names: 123_DATA[_SIZE] for 123.png (macro name can't starts with digit) and IMG-123_DATA[_SIZE] for ing-123.png (macro name can't contains '-'). The correct С/C++ macro name should contain only '_', letters, digits and not starts with a number. This PR converts all invalid characters to '_', and, if necessary, adds an underscore '_' to the beginning of the macro name.

I think it is good idea to extract this code to separate function. But I don't clearly understand in which file I should insert function declaration and in which file I should insert implementation. Two implementations of GetFileNameWithoutExt confuses me:
./raylib.h:1119:RLAPI const char *GetFileNameWithoutExt(const char *filePath);    // Get filename string without extension (uses static string)
./raudio.c:420:static const char *GetFileNameWithoutExt(const char *filePath);     // Get filename string without extension (uses static string)
./raudio.c:2678:static const char *GetFileNameWithoutExt(const char *filePath)
./rcore.c:1952:const char *GetFileNameWithoutExt(const char *filePath)

I think the only edge case to handles is ensuring the rewritten identifier does not have an initial "_" followed by a capital letter nor creating an initial "__" (2 underscores).  The preprocessor names in such forms are reserved for pre-defined names in C Language implementations.

@orcmid I didn't fully understand you. Do you suggest not to consider the cases I mentioned and try to fix only the prefix?

I was warning about intruding on reserved identifiers as the result of inserting "_" and, now that I notice, capitalizing the letters.  (The use of _SIZE is already a problem here.  _size is more correct.)
And does GetFileNameWithoutExt actually deliver a path?
The problem seems to be that the filename must be one that, absent the extension, is a valid C Language identifier that is not reserved.  There are innumerable ways that a filename might not satisfy that condition, and I have no idea how that can be overcome by the proposed rewriting.
Maybe the simple fix is to prefix with one _ if the filename starts with a digit, and replace any  non-alpha characters with _ and leave it at that.  (This will change "" to "" but no harm done.)    I think that's the best that can be done.  I would not capitalize.  There is no requirement to capitalize preprocessor names being created for this purpose, if it's actually created with a #define.
  An easy way out of all cases is to always prefix the name with something like g_ (for generated) and then simply replace non-alphas with _.  This will avoid any collisions with C Language keywords and built-in preprocessor macros.  It is also easier to explain.

@ismagilli

If you think it is acceptable to break backward compatibility, I will correct based on your message.
I note that the code I suggested adds an underscore to the beginning of the text only if the text starts with a digit. Therefore, double underscores at the beginning are only possible if the file name began with two underscores.

I think invalid preprocessor names can also be produced if the filename begins with one or two non-alphanumeric characters.
Suggestion: Reduce it to two cases.

If the first character is a numeral, provide a leading "_".
If any character is non-alphanumeric, replace it with "_".

Ensure that case 1 indexes properly, so the transfer of file-name characters starts after the initial "_".  Also, design it so that if the filename with or without extension is null, there will at least be a "_" varFileName[] result.
I suggest doing
char *tmpFileName = GetFileNameWithoutExt(filename);

Then set varFileName[0] to a leading '_' depending on tmpFileName[0].  This also will determine if you copy tmpFileName[] starting with initial destination varFileName[0]orvarFileName[1]`.
Do either a safe strcpy or instead do your own copy loop, checking each tmpFileName[i] and copying that or '_' to `varFileName[j] depending on whether the character is alphanumeric or not.
You might as well do your own copy loop, since you are going to look at all of them anyhow.
Finally, defend against over-running varFileName[] and ensure there is at least one '\0' remaining at the end of that buffer.
Is this helpful?

I checked what vim xxd does. It prepends __ to the filenames beginning with digits, and changes - to _.
https://github.com/vim/vim/blob/315cd1fbcbba7c44ec8743f03645bfcaef58bd55/src/xxd/xxd.c#L30-L32
https://github.com/vim/vim/blob/315cd1fbcbba7c44ec8743f03645bfcaef58bd55/src/xxd/xxd.c#L1009

This has me agree that there might need to be a function in raylib.h for the cases of identifier generation from filenames.
I don't agree. It's niche, not an API most users will ever touch.

@Peter0x44 > > This has me agree that there might need to be a function in raylib.h for the cases of identifier generation from filenames.

I don't agree. It's niche, not an API most users will ever touch.

I think the need for an external implementation is because of the 3 places this is done for generation of code.  It's not so much about raylib.h as a utility function that would be good to have maintained in a single place.  It needs a careful shared implementation.
Is there a better place, maybe utils.c and utils.h, for parking this?  (I shudder to think it might need to be back-end dependent instead.)

@orcmid I guess rtext.c would be it. I was talking about exposing a public API though.

I think utils.{c,h} better for place this function since rtext is about loading fonts and drawing text.

@ismagilli it also has functions like TextCopy, IsFileExtension, etc, that are used elsewhere throughout raylib

TextCopy and IsFileExtension is a part of the public API, but the function we are talking about is not. If we put a function in rtext, then we have to duplicate the function declaration in each file in which we want to use this function.

True. I guess Ray has the real final say there.
Duplicating this logic isn't terrible but also not ideal.

I would like to thank @orcmid for his patience and detailed explanations of his vision.
I have made changes to the code and will update the PR code now. I did not delete the code that replaces lowercase letters with uppercase letters in order to save backward compatibility. In addition, I made it impossible for two underscores to appear in a row (not only at the beginning of the macro name). I omitted the check for going beyond the boundaries of the array in this function. There are a lot of places in the existing code where such a check is required, but it is missing.
Let's wait for Ramon's decision.

@ismagilli @orcmid @Peter0x44 After reviewing this issue carefully, I decided not to merge it.
It not only because it adds a new function, with a possible coupling between modules or redundant code but the main issue is because is impossible to address all possible user filenames, for example with special characters, spaces or other languages charsets.
I prefer to keep it as is and force the user to be careful with its naming conventions. If it fails, it't up to the user.

@raysan5 thanks for your reply!


Northstar crashes if R2Northstar/logs does not exist

As of 1a7b41cc722c05eb97006d29e124c17559c45324 (unreleased).
I haven't checked it yet, but my hunch is that it's a regression related to this https://github.com/R2Northstar/NorthstarLauncher/pull/73/files#diff-fc1e49c087e0aa0e7e432a10288ddbd465d6ed30ccb5946c2deea666386e974aR52.

@Legonzaur

Best thing to do would be to revert #76 and #73 and merge log rotation when it's done

As the relevant commit was reverted already I think this issue can be closed :P


horizontal layout in a box

Load the article on "chocolate" and switch to trigram mode. Click on "a b" in pane 2.  Some of the items in the box overlap each other due to insufficient horizontal spacing. Why is this happening?

There is no longer a box in pane 4, but the vertical spacing of the four successors to "b c" is inadequate.

The vertical spacing looks good now for "b c". But why is the right bracket spacing in level 2 so irregular?

Right bracket spacing is based on the longest word in the previous chain.
For longer words, the bracket shifts more to the right. I can make this
fixed if you'd like?
On Mon, 15 Jul 2024 at 19:26, Dave Touretzky @.***>
wrote:

The vertical spacing looks good now for "b c". But why is the right
bracket spacing in level 2 so irregular?
—
Reply to this email directly, view it on GitHub
https://github.com/touretzkyds/MarkovChainDemo/issues/24#issuecomment-2229612463,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APUIVYBAQX7UOACI4ZX7ELLZMRLEDAVCNFSM6AAAAABKPHJDQCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRZGYYTENBWGM
.
You are receiving this because you were assigned.Message ID:
@.***>

Looks good now.


Clean up after Null Safety is enabled by default

The CL that will be landed: https://dart-review.googlesource.com/c/sdk/+/166790
The issue to change analyzer tests: https://github.com/dart-lang/sdk/issues/43777

https://dart-review.googlesource.com/c/sdk/+/174488 was the last.


Weights link not available

Hello,
I am trying to run the code but I can't download the weights. The link seems to be deactivatex.
cd nets/upconv && ./download.sh or the direct link doesn't respond.
Can you help with this problem?
Thank you in advance.

@javierrodenas Thanks for your note!
I've updated the path (the URL now is https:// instead of http) in https://github.com/Evolving-AI-Lab/synthesizing/blob/master/nets/upconv/download.sh
It should work now. Let me know if it does not.
Thanks!


Trying to get in touch regarding a security issue

Hey there!
I'd like to report a security issue but cannot find contact instructions on your repository.
If not a hassle, might you kindly add a SECURITY.md file with an email, or another contact method? GitHub recommends this best practice to ensure security issues are responsibly disclosed, and it would serve as a simple instruction for security researchers in the future.
Thank you for your consideration, and I look forward to hearing from you!
(cc @huntr-helper)

@zidingz thank you for your suggestion. I missed this best practice. Security policy for this lib will be added asap.

@zidingz the security policy is now available here. Pleae send me your report to<EMAIL_ADDRESS>if any. Thanks.


Clarification on prerequisites for DA

At the moment, for the DA that I am testing, I have an Azure AD Tenant with a valid Subscription and along with that I have a Trial Office 365 E5 Subscription with License assigned to the Tenant Admin. Plus ConfigMgr is installed with 1902 + Hotfix and the Windows 10 Enterprise OSs are Eval 1903 with the latest patches/cumulative updates.
I don't read this anywhere in the documentation, but do we need to setup Hybrid Azure AD Join, where the devices are Hybrid Azure AD Joined + EMS E5 Subscription to get Azure AD Premium P2 service and Intune and assign Windows 10 Enterprise E3/E5 Licenses for this?
My devices are showing up in the View recent data pane, but they have not reported anything in the DA Dashboard and in ConfigMgr it is saying Awaiting Enrollment.
It has been 48 hours.
Do I need to wait for full 72 hours or more? As the message says, "We are processing your data. If this message persists for more than 72 hours, you may be having connection health issues".
The devices are showing all successful in all the communication in ConfigMgr.
Configuration wise on Azure side and ConfigMgr side, I have followed this documentation as it is and all the permissions and settings seem to be correct.
Also, getting an error in the data currency flyout as attached.
Any assistance here would be appreciated. Thanks in advance.

ID: 2d8d7ece-b19f-1431-a619-e57ce6469c28
Version Independent ID: 86a3d7a5-695b-d3d9-498c-e6b6e03169f8
Content: Desktop Analytics - Configuration Manager
Content Source: sccm/desktop-analytics/overview.md
Product: configuration-manager
Technology: configmgr-other
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Any updates to this question?

Thanks @ajaswal1982 for taking the time to share this with the Configuration Manager documentation team. I’m sorry that you’re having problems, and I want to make sure it gets to the right people that can help. There are a couple of options available to provide the best level of support for this:

Post on Configuration Manager forums. These are moderated by our community MVPs who are very experienced, knowledgeable, and helpful.
Use Microsoft Support to search for the issue, or open a case with professional support.
Contact your Microsoft Premier team, such as a Premier Field Engineer or Technical Account Manager.
I'm closing this issue as there's nothing actionable for docs at this time.

p.s. hybrid Azure AD join isn't a prerequisite


Split mod for crafting system

I am currently making a modpack, and wanted to make it controller friendly. The crafting menu is perfectly suited for controllers, and if it were not for the complete overhaul of the game, it would've been a perfect fit.
Is it possible that the legacy crafting menu could be implemented separately? Or could some configuration be added to toggle certain aspects of the mod e.g. the menu overhauls?

It's a good idea, but suggestions need to be made on the Legacy4J Discord server in order to better organize GitHub for issues and incompatibilities only (please note that suggestions prior to the creation of this server will be kept)


Handle the session shutdown Message when sending zcl commands

Handle the session shutdown Message "CHIP:CTL: OnConnectionExpired: Failed to process received message: err 4051" when sending zcl commands  right after pairing.
chip-device-ctrl > zcl OnOff Toggle 12344321 1 0
CHIP:ZCL: Successfully encoded 11 bytes
CHIP:IN: Connection from 'UNDEFINED' expired
CHIP:CTL: OnConnectionExpired: Failed to process received message: err 4051
CHIP:IN: New pairing for device 12344321, key 0!!
CHIP:IN: Secure message was encrypted: Msg ID 0
CHIP:IN: Sending msg from 112233 to 12344321
CHIP:IN: Sending secure msg on generic transport
CHIP:IN: Secure msg send status 0
CHIP:CTL: SendMessage returned 0
chip-device-ctrl > zcl OnOff Toggle 12344321 1 0
CHIP:ZCL: Successfully encoded 11 bytes
CHIP:IN: Secure message was encrypted: Msg ID 1
CHIP:IN: Sending msg from 112233 to 12344321
CHIP:IN: Sending secure msg on generic transport
CHIP:IN: Secure msg send status 0
CHIP:CTL: SendMessage returned 0

closing the ticket after discussing with Pankaj


Component documentation feedback

A place to capture feedback on the docs template or the site page itself. Where are the challenges? Is there anything missing? Is it difficult to find a place for content you want to add? Etc...

Update token in preview area to --container-primary-background token.

Note the displayName issue seems to be due to the components using arrow functions rather than named functions, so we should create a ticket to go though and update all components to use named functions. Updating FlowLayout to the following fixed that component for me:
export const FlowLayout: FlowLayoutComponent = forwardRef(function FlowLayout<
  T extends ElementType = "div"
>({ children, ...rest }: FlowLayoutProps<T>, ref?: PolymorphicRef<T>) {
  return (
    <FlexLayout direction="row" ref={ref} wrap {...rest}>
      {children}
    </FlexLayout>
  );
});

from
export const FlowLayout: FlowLayoutComponent = forwardRef(
  <T extends ElementType = "div">(
    { children, ...rest }: FlowLayoutProps<T>,
    ref?: PolymorphicRef<T>
  ) => {
    return (
      <FlexLayout direction="row" ref={ref} wrap {...rest}>
        {children}
      </FlexLayout>
    );
  }
);

Clicking on the chevron in the side nav should only expand/collapse the item, not open the page at the same time.

I believe this'll be fixed when we replace the current vertical nav component (which comes from Mosaic) with our own, based on the NavigationItem component.
Not sure there's much point trying to "fix" this in the Mosaic component now, given that we're due to replace it anyway.

FYI, I've opened an issue to note some additional functionality for the LivePreview component (the thing that displays our component examples) that has been discussed in the past but never actually written down: #2348


Security center defender-on-* checks are wrong

Describe the bug
The security center defender-on-* checks are wrong because the resource_type can only be one option, but the "secure examples" contain multiple options comma separated.
To Reproduce
Steps to reproduce the behavior:

Like on https://aquasecurity.github.io/tfsec/v0.63.1/checks/azure/security-center/defender-on-container-registry/
add

resource "azurerm_security_center_subscription_pricing" "good_example" {
  tier          = "Standard"
  resource_type = "VirtualMachines,ContainerRegistry"
}

to your Terraform file.
2. Do  "terraform plan"
3. Result is:
│ Error: expected resource_type to be one of [AppServices ContainerRegistry KeyVaults KubernetesService SqlServers SqlServerVirtualMachines StorageAccounts VirtualMachines Arm Dns OpenSourceRelationalDatabases Containers], got VirtualMachines,ContainerRegistry
│
│   with azurerm_security_center_subscription_pricing.good_example,
│   on security_center.tf line 19, in resource "azurerm_security_center_subscription_pricing" "good_example":
│   19:   resource_type = "VirtualMachines,ContainerRegistry"

Expected behavior
The working terraform format is:
resource "azurerm_security_center_subscription_pricing" "good_example1" {
  tier          = "Standard"
  resource_type = "VirtualMachines"
}

resource "azurerm_security_center_subscription_pricing" "good_example2" {
  tier          = "Standard"
  resource_type = "ContainerRegistry"
}

So the check and the documentation should be changed.
Tested with hashicorp/azurerm version 2.89.0

Thanks @FrankS77  - will resolve this shortly

This was fixed.


[BUG]  Handle exception during train - stock dividends

Describe the bug
Exception during training:
2024-12-01 17:39:58.302 | INFO     | canswim.covariates:prepare_dividends:758 - preparing future covariates: stock dividends
2024-12-01 17:40:13.336 | ERROR    | canswim.covariates:prepare_dividends:866 - Skipping FUTU due to error: <class 'AssertionError'>:
Traceback (most recent call last):

  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code

  File "/home/ivelin/canswim/src/canswim/__main__.py", line 128, in <module>
    train.main(new_model=args.new_model)
    │     │              │    └ False
    │     │              └ Namespace(task='train', forecast_start_date=None, new_model=False, same_data=False)
    │     └ <function main at 0x798d14343ba0>
    └ <module 'canswim.train' from '/home/ivelin/canswim/src/canswim/train.py'>

  File "/home/ivelin/canswim/src/canswim/train.py", line 119, in main
    trainer.canswim_model.prepare_data()
    │       │             └ <function CanswimModel.prepare_data at 0x798d17192c00>
    │       └ <canswim.model.CanswimModel object at 0x798d14723510>
    └ <canswim.train.CanswimTrainer object at 0x798d15617590>

  File "/home/ivelin/canswim/src/canswim/model.py", line 418, in prepare_data
    self.prepare_forecast_data(self.train_date_start)
    │    │                     │    └ Timestamp('1991-01-01 00:00:00')
    │    │                     └ <canswim.model.CanswimModel object at 0x798d14723510>
    │    └ <function CanswimModel.prepare_forecast_data at 0x798d17192b60>
    └ <canswim.model.CanswimModel object at 0x798d14723510>

  File "/home/ivelin/canswim/src/canswim/model.py", line 375, in prepare_forecast_data
    self.covariates.prepare_data(
    │    │          └ <function Covariates.prepare_data at 0x798d316c84a0>
    │    └ <canswim.covariates.Covariates object at 0x798d154be390>
    └ <canswim.model.CanswimModel object at 0x798d14723510>

  File "/home/ivelin/canswim/src/canswim/covariates.py", line 466, in prepare_data
    self.prepare_future_covariates(
    │    └ <function Covariates.prepare_future_covariates at 0x798d316c8d60>
    └ <canswim.covariates.Covariates object at 0x798d154be390>

  File "/home/ivelin/canswim/src/canswim/covariates.py", line 972, in prepare_future_covariates
    dividend_series = self.prepare_dividends(stock_price_series=stock_price_series)
                      │    │                                    └ {'AAL': <TimeSeries (DataArray) (Date: 4984, component: 5, sample: 1)>
                      │    │                                      array([[[2.10499992e+01],
                      │    │                                              [2.13999996e+01],
                      │    │                                        ...
                      │    └ <function Covariates.prepare_dividends at 0x798d316c8c20>
                      └ <canswim.covariates.Covariates object at 0x798d154be390>

> File "/home/ivelin/canswim/src/canswim/covariates.py", line 838, in prepare_dividends
    assert not t_div.empty
               │     └ <property object at 0x798e22d65b70>
               └ Empty DataFrame
                 Columns: [dividend, paymentDate_year, paymentDate_month, paymentDate_day, recordDate_year, recordDate_month, ...

AssertionError: assert not t_div.empty
2024-12-01 17:40:36.460 | INFO     | canswim.covariates:stack_covariates:225 - stacking covariates.
2024-12-01 17:40:37.063 | INFO     | canswim.covariates:stack_covariates:244 - Skipping AHCHY due to lack of min 588 samples. Only 240 samples available in covs stack.

To Reproduce
canswim.sh train
Expected behavior
Errors should be handled gracefully with meaningful user error messages.
Desktop (please complete the following information):

PopOS  desktop latest

No more exceptions after #65 was fixed. Appears that the yf corrupted data was causing training exceptions.


Fix: fix test for deployment

Signed-off-by: henry-lp<EMAIL_ADDRESS>Related issue: #138

Ping, what's the next step here @fermadeiral?

I thought I had been clear in the email, but let me put this way: I have other priorities than testing the changes of this PR. Any other collaborator might feel free to do it though, I don't mind.

@henry-lp, I executed the tests locally and it worked! Thank you very much for the fix!


cannot install windows sdk

Brief description of your issue
after winget install Microsoft.WindowsSDK nothing in windows sdk was install
Steps to reproduce
latest win11 winget install Microsoft.WindowsSDK
Expected behavior
the whole windows sdk was installed
Actual behavior
command exit quitly(in a few second,obviously not enough for download whole windows sdk),some file exist in C:\Program Files (x86)\Microsoft SDKs,but the whole folder only 28.4MB size.
Environment
C:\Users\leesh>winget --info
Windows 程序包管理器 v1.2.10271
版权所有 (C) Microsoft Corporation。保留所有权利。

Windows: Windows.Desktop v10.0.22000.675
程序包: Microsoft.DesktopAppInstaller v1.17.10271.0

日志: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

链接
----------------------------------------------------------------------------
隐私声明             https://aka.ms/winget-privacy
许可协议             https://aka.ms/winget-license
第三方声明           https://aka.ms/winget-3rdPartyNotice
主页                 https://aka.ms/winget
Windows 应用商店条款 https://www.microsoft.com/en-us/storedocs/terms-of-sale

Can you look at the LOG file in the following location:
C:\Users<user name>\AppData\Local\Temp\windowssdk
there will be a file in there called something like: Windows_Software_Development_Kit___Windows_10.0.22000.194_20220518091003.log
You should be able to determine why it did not install.  Or you can attach the LOG to this post and we can look.

Windows_Software_Development_Kit___Windows_10.0.22000.194_20220521223820.log

there are too many log this dir，so I remove the package and reinstall it，and It seem work fine.

I was receiving this error when trying to update as well. It also will not allow me to uninstall. In the log file:
[2D3C:5990][2022-08-10T08:16:57]i000: Setting string variable 'VS2022INSTALL' to value 'C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\Common7\IDE'
[2D3C:5990][2022-08-10T08:16:57]i000: ERROR: MSI replacement servicing is not supported
[2D3C:5990][2022-08-10T08:16:57]i000: View is requesting shutdown
[2D3C:5990][2022-08-10T08:16:57]i199: Detect complete, result: 0x0
[2D3C:5990][2022-08-10T08:16:57]i500: Shutting down, exit code: 0x7d8
....
....
[2D3C:5990][2022-08-10T08:16:57]i410: Variable: SystemFolder = C:\WINDOWS\SysWOW64\
[2D3C:5990][2022-08-10T08:16:57]i410: Variable: UCRTEXISTS = 1
[2D3C:5990][2022-08-10T08:16:57]i410: Variable: UCRTVERSION = 10.0.22000.1
[2D3C:5990][2022-08-10T08:16:57]i410: Variable: VersionNT64 = <IP_ADDRESS>
[2D3C:5990][2022-08-10T08:16:57]i410: Variable: VS2022INSTALL = C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\Common7\IDE
[2D3C:5990][2022-08-10T08:16:57]i410: Variable: WixBundleAction = 5
[2D3C:5990][2022-08-10T08:16:57]i410: Variable: WixBundleElevated = 1
[2D3C:5990][2022-08-10T08:16:57]i410: Variable: WixBundleInstalled = 1
[2D3C:5990][2022-08-10T08:16:57]i410: Variable: WixBundleLastUsedSource = C:\ProgramData\Microsoft\VisualStudio\Packages\Win11SDK_10.0.22621,version=10.0.22621.0,productarch=neutral\
[2D3C:5990][2022-08-10T08:16:57]i410: Variable: WixBundleLog = C:\Users\user\AppData\Local\Temp\windowssdk\Windows_Software_Development_Kit___Windows_10.0.22621.1_20220810081657.log
[2D3C:5990][2022-08-10T08:16:57]i410: Variable: WixBundleManufacturer = Microsoft Corporation
[2D3C:5990][2022-08-10T08:16:57]i410: Variable: WixBundleName = Windows Software Development Kit - Windows 10.0.22621.1
[2D3C:5990][2022-08-10T08:16:57]i410: Variable: WixBundleOriginalSource = C:\WINDOWS\Temp\{E8F15567-E078-42AF-A100-B3823D6B2D09}\.cr\winsdksetup.exe
[2D3C:5990][2022-08-10T08:16:57]i410: Variable: WixBundleOriginalSourceFolder = C:\ProgramData\Microsoft\VisualStudio\Packages\Win11SDK_10.0.22621,version=10.0.22621.0,productarch=neutral\
[2D3C:5990][2022-08-10T08:16:57]i410: Variable: WixBundleProviderKey = {fcb5e4cc-2739-4812-97fd-f3b7c5d151ae}
[2D3C:5990][2022-08-10T08:16:57]i410: Variable: WixBundleSourceProcessFolder = C:\Users\user\AppData\Local\Temp\WinGet\Microsoft.WindowsSDK.10.0.22621.1\
[2D3C:5990][2022-08-10T08:16:57]i410: Variable: WixBundleSourceProcessPath = C:\Users\user\AppData\Local\Temp\WinGet\Microsoft.WindowsSDK.10.0.22621.1\winsdksetup.exe
[2D3C:5990][2022-08-10T08:16:57]i410: Variable: WixBundleTag =
[2D3C:5990][2022-08-10T08:16:57]i410: Variable: WixBundleUILevel = 2
[2D3C:5990][2022-08-10T08:16:57]i410: Variable: WixBundleVersion = 10.1.22621.1

> winget uninstall --id Microsoft.WindowsSDK
No installed package found matching input criteria.

> winget upgrade
Name                                                    Id                   Version          Available    Source
-----------------------------------------------------------------------------------------------------------------
Windows Software Development Kit - Windows 10.0.20348.1 Microsoft.WindowsSDK < 10.0.22000.832 10.0.22621.1 winget


nodemon not work with forever

I use
forever-service install my_service -s app.js -f " -c nodemon" -o " --exitcrash" -e "PATH=/usr/local/bin:$PATH"

But nodemon do not work (app should auto restart)  when I modify app.js or whatever js file as nodemon do when I use only
forever start -c nodemon app.js --exitcrash

My wrong, It works


Update root variant of 9.x to 6.26.0

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

If GCC >9 is giving you trouble on PPC, have a look at https://github.com/conda-forge/clangdev-feedstock/pull/165/commits/8d12866510abb97d0c9308137c9730e9696bcba9 (not yet merged here, but works in #165 and likewise on the llvmdev feedstock).

Thanks for the info. I ran into a similar "relocation truncated to fit" issue for clang 9.x with GCC>7 (https://github.com/conda-forge/clangdev-feedstock/commit/68c35bbf19567d5671671545d30a77f276703e55).
With GCC 10 a new failure has appeared that needed llvm/llvm-project@3185c30c to be backported.


'Select a language' text can end up overlapping with the scrollbar

Testing #117253

With "workbench.editor.untitled.hint": "text"
Open a new untitled file
Shrink the editor down to that the select a language ... text wraps

Bug
The select a language text ends up overlapping with the scrollbar

Yeah, regular editor content also overlaps with the scroll bar.
So this is not something I would fix for now, thus closing


swoole version >= 4.6.0 pcntl_fork error

[This message is created by hyperf-bot]
Hi @etjson, this is a READ-ONLY repository, please submit your Pull Request to hyperf/hyperf repository, this Pull Request will close automatically.


Fixes stylecop warnings in resource manager project.

Added stylecop reference in project
Added stylecop analyzer to project
Fixes about 1000 stylecop warnings in the resource manager project.

Summary

Did you add the StyleCop.Analyzers reference manually?  I was expecting to see it in a packages.config file.

This is great, thanks for the hard work in fixing this. If there are 0 build warnings in this project, can you turn on 'Treat Build Warnings as Errors' in the csproj?

There are still 2 or 3 warnings, I will post them shortly here

@ahoefling So the 2 warnings I get are:

Description
File
Line

Found conflicts between different versions of the same dependent assembly. In Visual Studio, double-click this warning (or select it and press Enter) to fix the conflicts; otherwise, add the following binding redirects to the "runtime" node in the application configuration file: <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="Newtonsoft.Json" culture="neutral" publicKeyToken="30ad4fe6b2a6aeed" /><bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" /></dependentAssembly></assemblyBinding>
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets
2106

I find that strange because I removed the existing Newtonsoft.Json reference and re-added it from the main packages folder.

Severity
Code
Description
Project
File
Line
Suppression State

Warning
CS0618
'IPortalController.GetCurrentPortalSettings()' is obsolete: 'Deprecated in Platform 9.4.2. Scheduled removal in v11.0.0. Use GetCurrentSettings instead.'
Dnn.Modules.ResourceManager
D:\dnnvaladas\Dnn.Platform\DNN Platform\Modules\ResourceManager\Components\ThumbnailsManager.cs
73
Active

And well this one, I need ActiveTab which is not available on IPortalSettings but exists in PortalSettings.
@bdukes I added the existing stylecop.json file to the project and then I went to references and added an analyzer reference to the main packages folder stylcop folder and then 2 dlls, one is the analyzer and the other dll is the codefix helpers. Is that correct?

Another thing I was thinking while working in there is that there are a lot of public methods on something I believe should never be used by 3rd parties, I believe this is a module and not a public api thing, should I try and go change everything possible from public to protected ? Is that a good idea before it is released so it protects us a bit from breaking changes as we push this module forward in the future ?
There are also a couple of methods that have 0 references to them, I was thinking to remove them... Thoughts ?

Oh and yeah, related to that... Interface members have no access modifiers, so the implementation defines the access modifiers on the methods as needed. So what happens if a 3rd party tries to dependency inject that but then it ends up the members are protected ? Should we make the actual whole interface protected to prevent 3rd parties from depending on stuff we don't really want to recommend consuming ?

@valadas are there interfaces in this project that you're concerned about?  You don't need to worry about someone implementing interface members with the "wrong" access modifier.  When you're using a reference with the interface type (e.g. IMyThing thing = GetMyThing())) you will always have access to the members of that interface.
Feel free to remove methods with no references.  As we mentioned in the TAG meeting, since this isn't published on NuGet, we're not concerned about it exposing public members, and we're free to adjust visibility to internal if desired.
For now, instead of PortalSettings.ActiveTab can you use TabController.CurrentPage?
The stylecop.json reference looks great, but can you add StyleCop.Analyzers package as a NuGet reference instead of just an assembly reference?

@valadas

Interface members have no access modifiers, so the implementation defines the access modifiers on the methods as needed. So what happens if a 3rd party tries to dependency inject that but then it ends up the members are protected ? Should we make the actual whole interface protected to prevent 3rd parties from depending on stuff we don't really want to recommend consuming ?

By design the interface specification in .NET defines public members that other classes that inherit the interface are required to implement. The interface members define a public contract and should always be public. You can use explicit interface implementations to restrict the interface members at the class level. However, that technique only hides the members, if you cast it to the interface you will instantly gain access to it because interface members are public. This is not an anti-pattern it is working as designed. It is a core pillar of object oriented programming to depend on abstractions which is exactly what an interface is accomplishing for us. When you change your interface implementation in the future, the code that depends on the interface does not need to change.
Thanks @bdukes for providing a good explanation to this question as well 💪
IPortalController.GetCurrentPortalSettings()' is obsolete: 'Deprecated in Platform 9.4.2. Scheduled removal in v11.0.0. Use GetCurrentSettings instead.

The current abstractions of IPortalSettings needs some ❤ and it isn't fully complete. To remove the warning I would follow @bdukes recommendation of using TabController.CurrentPage. If that doesn't work, you could cast the returned IPortalSettings object as a `PortalSettings. It really is a hacky way to solve the problem, but since the current abstractions integration needs some work, I think it would be okay as a workaround.
Found conflicts between different versions of the same dependent assembly.

This is most likely due to NuGet being corrupted for the project. Try the following steps to resolve this problem.

Unload the csproj and manually delete the Newtonsoft.Json reference
Open up the local web.config in the project directory and remove the binding redirects that reference Newtonsoft.Json
Open the packages.config in the project directory and remove the package reference line to Newtonsoft.Json
Right-Click at the solution level and select Manage NuGet Packages
Navigate to the installed packages tab and find Newtonsoft.Json
Install the matching version number in your current project by selecting it in the projects checkbox list.

This technique will clean up any broken references and allow the Visual Studio tooling to install the package reference correctly

For now, instead of PortalSettings.ActiveTab can you use TabController.CurrentPage?
Thanks, that works

@valadas I don't think I saw the csproj updated to treat warnings as build errors. Would you like me to submit a PR for this?
I am really happy that we removed all build warnings, but without a build tool in place to prevent it from happening we will likely get back to having build warnings again

@ahoefling  Yeah, I would be happy with that sure.


audio: after the computer is idle for 30 minutes or the computer is locked and unlocked, audio is very sluggish

Windows build number:
Version 22H2 (OS Build 22621.1413)
Your Distribution version:
Fedora 37, from https://github.com/WhitewaterFoundry/Fedora-Remix-for-WSL
Your WSL versions:
Hello. I use WSLG with apps like the Orca screen reader and Emacs with the Emacspeak extension. Whenever I run Emacs from the start menu, it works great until the computer locks or goes to sleep. After I unlock my computer, audio is very sluggish, a good second of delay from when I press a key and when Emacspeak speaks. The same happened with Orca, when I could still get Orca to work.
Steps to reproduce:
Install Emacs
clone emacspeak for github.com/tvraman/emacspeak
Install espeak-ng
make Emacspeak and make the espeak speech server.
Put:
(load-file /lisp/emacspeak-setup.el")
(espeak)
In your .emacs.el
Launch Emacs, and make sure Emacspeak is running by pressing down arrow and hearing if Emacspeak says anything.
Now, press Windows + L to lock the computer.
Press Enter to unlock it, entering your PIN or password if needed.
Press Down arrow again, and see if Emacspeak responds as quickly as before.
If you have Orca working, you can launch it with Orca& and then open an accessible app, like GPodder or something to try this also. Navigate the app, noting how responsive it is, lock the machine, unlock it, and note the responsiveness again.
WSL logs:
pulseaudio.log
stderr.log
weston.log
WSL dumps:
No response
Expected behavior:
Emacspeak, or Orca, should be just as responsive when locking and unlocking the computer as when WSL starts.
Actual behavior:
Emacspeak is sluggish after unlocking the computer, taking a second to respond with audio.

On further inspection, this may be an issue with Pipewire, which Fedora ships with by default. Switching the sound system to Pulseaudio seems to fix this.

How do you switch your sound subsystem?

@TheQuinbox You systemctl disable pipewire and systemctl enable pulseaudio or something like that, I can't remember the units exactly. But just do it through systemctl. It still happens though, even after updating the Fedora WSL and WSL itslef. I've found the best way to make it go fast is to shut down WSL, then run Emacs from your start menu so it's the first thing that launches. But it eventually slows down a lot, becoming much less responsive.

I would also like to use Emacspeak on WSL2, but on Ubuntu 22.04 and Arch Linux the audio also lags.
Access your favorite WSL2 distribution (I'll use Ubuntu as an example) and install espeak-ng:
$ sudo apt update
$ sudo apt install espeak-ng

Open the espeak-ng interactive prompt so you can type text and hear the voice speaking:
$ espeak-ng

Take the test by typing any letter and pressing ENTER:

w <ENTER>
s <ENTER>
l <ENTER>

Note that the voice speaks at the same time you press ENTER.
Go do something else and keep this prompt open. After 10 or 15 minutes, come back and repeat the test above. You will see that the response time has increased significantly.
The more time passes, the more the response time increases, but when the espeak-ng process ends, everything returns to normal.
I'm using Windows 11 Home 23H2.

WSL Version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>-1
WSLg version: 1.0.59


Add README note about security reporting process.

As the title says.

/hold

/lgtm

all green @baude if you want to remove the hold.

/hold cancel


Verify that svgoConfig.plugins is an array

Summary
https://github.com/gregberge/svgr/pull/384 introduced a breaking change in the svgoConfig parser. Even if this wasn't intended, using an object for the plugins config used to work, and a lot of people might be using such an incorrect config. The parsing currently fails silently. This PR makes the parser throw an error if anything other than an array is found.

Test plan

I've written a new test case for handling of incorrect plugin configs.

Thanks!


Avoid showing the same videos between runs

General troubleshooting tips
Before logging an issue please check that:

[x] You have the latest version installed (There may be a beta version that fixes your issue), see here for the latest releases and bug fixes: https://github.com/JohnCoates/Aerial/releases
[x] Your issue isn't already mentioned in our issues. You may find a workaround there or a similar request already made.
[x] Your problem isn't mentioned in the troubleshooting page.

If none of this fixes your issue, tell us about the problem you are experiencing or the feature you'd like to request.
Required information
In order to help us sort your issue, we ask that you provide the following information:

[x] Mac model: N/A
[x] macOS version: N/A
[x] Monitor setup: N/A

If appropriate, please enable Debug mode and Log to disk in Advanced tab and replicate your bug, then attach the AerialLog.txt file (You can access this file through the Advanced tab).
Description of issue / Feature request
Currently, it seems that the video shown when the screensaver is started are picked by creating a playlist, filtering out by user preferences and then picking the first from the .shuffled() list. After using Aerial for a little while, I still haven't seen some videos on my list while having seen others multiple times in a day. Note that this is not repeated videos within a single playlist.
I can think of two approaches that would remedy the problem:

Keep the same playlist between screensaver sessions. A set of videos is already generated, so Aerial could keep running through that playlist between runs. This would involve some logic to invalidate the playlist when the set of acceptable videos changes due to user settings or cache-related reasons.
Store a timestamp for each video according to when it was shown. Storing these times locally allows you to keep generating new playlists in line with the current approach, but would require a little extra logic to sort the videos by least recently seen and to actually store and retrieve this data as needed. However, it would mean that the list of videos would endlessly repeat itself with no randomness at all. Perhaps we could cut off the most recent 20-30% of videos and then shuffle to maintain some variety?

I think the second approach would be easier to implement. I would be willing to have a go at making a PR if there is support for it.

Hey @jamesreprise
Can you make sure that in Time, you didn't enable to show different videos at different time of the day ? That does restrict stuff a lot.
Also, it will shuffle only from what's cached, so if you keep a smallish cache (say 5 GB), and enable all videos, you'll definitely have that impression of rotating the same and not seeing some.
I can see those things being more of an issue that shuffle always shuffling the same way ? Seems a bit weird.

Unfortunately my settings are to play anything at random and I have an unlimited cache, see below.
I think this is some form of https://en.wikipedia.org/wiki/Birthday_problem, where it's surprisingly to see the same video first across only a few playlists despite the fact that I have ~90 videos in my rotation.
Let me know if you think either of the approaches I gave are viable for Aerial and something you would have the time to review.

Hey again
I'm surprised to hear it's that bad, as I don't think I've heard complaints that weren't related to those two things I cited. Also some videos are really similar which doesn't help.
Anyway, regarding the possible approaches :

I don't think that one is really workable. There's not just "one" playlist, if you have multiple screens in some configurations you'll have multiple playlists, and those monitors may not be constant, so that would be a huge mess to entertain (+ your playlist would become 4 playlist if I restrict videos by time ! or 2 with Light Mode/Dark Mode... so many options)
I can see some merit to keeping some form of last played date in general, but finding the right mix is going to be extremely highly subjective (and adding one more slider for that seems a bit extreme, says the guy who already added sooo manyyyy "how many people can possibly use that" feature as I have a hard time saying no ;)).

In general, I kinda have plans to add at some point playlist support, because it's been requested, but it has the same issues as 1), the multiple monitors situations with independent videos makes it a mess (and sadly you can't really share a list without doing weird stuff, as on some macOS versions you aren't sharing the same process between those AerialViews).
I kinda think that playlist support would fix your need without messing with shuffling, but messing with shuffling is likely a lot easier.
I'll think about it for a bit !


[BUG] DNS server not available during install

Describe the bug

When doing a PXE boot using DHCP it fails to fetch ssh keys from github due to DNS server not being available yet.
It works however when doing it later over ssh from the node;
# curl -v https://github.com/jellyfrog.keys
*   Trying <IP_ADDRESS>:443...
* TCP_NODELAY set
* Connected to github.com (<IP_ADDRESS>) port 443 (#0)
* ...

To Reproduce
Steps to reproduce the behavior:

Install over PXE with the below config

Expected behavior

Support bundle

Environment:

Harvester ISO version:  master-f303b27e-head
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): vmware

Additional context
Feb 09 17:31:59 harvester-mw9l9 cos-setup[1318]: time="2022-02-09T17:31:59Z" level=error msg="1 error occurred:\n\t* failed fetching ssh key: failed while downloading key: failed while getting file: Get \"https://github.com/jellyfrog.keys\": dial tcp: lookup github.com on [::1]:53: read udp [::1]:39527->[::1]:53: read: connection refused\n\n"
Feb 09 17:32:00 harvester-mw9l9 cos-setup[1318]:         * failed fetching ssh key: failed while downloading key: failed while getting file: Get "https://github.com/jellyfrog.keys": dial tcp: lookup github.com on [::1]:53: read udp [::1]:39527->[::1]:53: read: connection refused
Feb 09 17:32:00 harvester-mw9l9 cos-setup[1318]:         * failed fetching ssh key: failed while downloading key: failed while getting file: Get "https://github.com/jellyfrog.keys": dial tcp: lookup github.com on [::1]:53: read udp [::1]:39527->[::1]:53: read: connection refused

token: "token123"
os:
  ssh_authorized_keys:
    - github:jellyfrog
  password: admin
install:
  mode: create
  networks:
    harvester-mgmt:
      interfaces:
      - name: ens192
      default_route: true
      method: dhcp
      bond_options:
        mode: balance-tlb
        miimon: 100
    harvester-vlan:
      interfaces:
      - name: ens224
      method: none
      bond_options:
        mode: balance-tlb
        miimon: 100
  device: /dev/sda
  iso_url: http://<IP_ADDRESS>/harvester/master/harvester-master-amd64.iso
  vip: <IP_ADDRESS>
  vip_mode: static

Tested in master-bfd6a8a9-head.
Verification Steps

Start a new install
Set DNS as <IP_ADDRESS>
Add in github SSH keys
Finish install
SSH into node with SSH keys from github (rancher@hostname)
Verify login was successful


pythonPackages.torchaudio: init at 0.10.2 [WIP]

Motivation for this change
The official pytorch audio library, packaged from source. Note that torchaudio-bin already exists.
TODO
I'm leaving this as a draft PR because it probably needs a bit more work to be useful:

[ ] Many tests fail and have been removed. These need to be reviewed.
[ ] Test that do work take a very long time to evaluate
[ ] Depends on #160197 and #160206 for checkInputs
[ ] Optional flags and dependencies should be defined
[ ] Needs a maintainer

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

Squashed superfluous commits & rebased


[Bug]: Custom Deploy.ps1 is not used

AL-Go version
5.2
Describe the issue
I want to use the buildModes to deploy a different version to sandboxes than to AppSource, for licensing purposes.
The only way I found to achieve this is to create a modified deploy.ps1 script like described here:
https://github.com/microsoft/AL-Go/blob/12f2a5618d20a5dd9043db1ed1a56384c840db57/Scenarios/settings.md?plain=1#L261

I did change those two parts:

but still logs the default message and used the main apps:

Is there anything I am missing or I can check to resolve this?
Expected behavior
Custom Deploy.ps1 should be used if put into .github folder
Steps to reproduce
create a custom Deploy.ps1 file, check the log output
Additional context (logs, screenshots, etc.)
No response

Not sure buildModes should be used for this, @mazhelez do you know?
On the actual question - this is an error in the documentation - we support DeployTo<environmentType>.ps1 - we don't actually support a complete override of all.

In some cases, it does make sense to deploy the artifacts from the non-default build mode, as in this particular scenario.
Deploy action, however, seems to be wired to use the -Apps artifacts (from the default build mode). https://github.com/microsoft/AL-Go/blob/12f2a5618d20a5dd9043db1ed1a56384c840db57/Actions/Deploy/Deploy.ps1#L46
However, in your custom script you can still query for other artifacts (the way you already do), so I believe if you fix your Deploy.ps1 to be .github/DeployTo<environmentType>.ps1, then it should work.

@mazhelez
After I changed the name to DeployToSandbox.ps1 and added "EnvironmentType": "Sandbox", to my deploy configuration, it seems to pick up the script now.
But why does this have to be so complicated? Now its failing because it expect a different parameter configuration than the original Deploy.ps1
@freddydk
If the BuildModes are not meant to be used in deployment or submission to appsource, what is the usecase of them?

I think buildModes was introduced for something different, but it might make sense to add a field "buildMode" to the DeployTo<env> setting, this would greatly simplify this scenario I guess and make the buildModes more useful.

@freddydk This would solve this issue for me 100%

Shipped in preview


feature request: warn the user if a film with the same title is already in the catalog

With long list it is not difficult adding the same film twice. Currently there is no warning that a title already exist. I think it would be good to warn the user and ask whether he wants to proceed or change the title/cancel.
To distinguish films with the same title (could happen) maybe we could have an option to add "#2,#3" next to the titler or once scraped specify the year of production in the title.

There is a "duplicate filter" in our filter panel.
It basically checks for existence of same IMDB Ids.
Same name does not work - other scrapers might have (slightly) other titles, or you scrape your movie in a complete different language.... you won't find that...


GitCommit status update fails for Azure DevOps Repo

Hey!
I've deployed GitOps connector with the below config:
gitRepositoryType: AZDO
ciCdOrchestratorType: AZDO
gitOpsOperatorType: FLUX
azdoGitOpsRepoName: <RepoName>
azdoOrgUrl: https://dev.azure.com/<org>/<project>
orchestratorPAT: <DevOps PAT>

When the connector tries to update the commit status I get this error (I've ommited the sensitive parts of the URLs):
 2023-05-02T06:52:55.378175027Z DEBUG:urllib3.connectionpool:https://dev.azure.com:443 "POST /<org>/<project>/_apis/git/repositories/<repo>/commits/main@sha1:<sha>/statuses?api-version=6.0 HTTP/1.1" 400 227

If I run this request manually against DevOps I get the response:
{
    "$id": "1",
    "innerException": null,
    "message": "A potentially dangerous Request.Path value was detected from the client (:).",
    "typeName": "System.Web.HttpException, System.Web",
    "typeKey": "HttpException",
    "errorCode": 0,
    "eventId": 0
}

Full log:
 2023-05-02T06:52:55.405696440Z ERROR:gitops_event_handler:Exception on /gitopsphase [POST]
 ││ 2023-05-02T06:52:55.405730040Z Traceback (most recent call last):
 ││ 2023-05-02T06:52:55.405736340Z   File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 2077, in wsgi_app
 ││ 2023-05-02T06:52:55.405741040Z     response = self.full_dispatch_request()
 ││ 2023-05-02T06:52:55.405746140Z   File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 1525, in full_dispatch_request
 ││ 2023-05-02T06:52:55.405750040Z     rv = self.handle_user_exception(e)
 ││ 2023-05-02T06:52:55.405753340Z   File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 1523, in full_dispatch_request
 ││ 2023-05-02T06:52:55.405757940Z     rv = self.dispatch_request()
 ││ 2023-05-02T06:52:55.405762340Z   File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 1509, in dispatch_request
 ││ 2023-05-02T06:52:55.405767140Z     return self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args)
 ││ 2023-05-02T06:52:55.405772840Z   File "/app/gitops_event_handler.py", line 33, in gitopsphase
 ││ 2023-05-02T06:52:55.405776440Z     gitops_connector.process_gitops_phase(payload, req_time)
 ││ 2023-05-02T06:52:55.405782940Z   File "/app/gitops_connector.py", line 32, in process_gitops_phase
 ││ 2023-05-02T06:52:55.405786440Z     self._notify_orchestrator(phase_data, commit_id)
 ││ 2023-05-02T06:52:55.405790540Z   File "/app/gitops_connector.py", line 44, in _notify_orchestrator
 ││ 2023-05-02T06:52:55.405795740Z     self._cicd_orchestrator.notify_on_deployment_completion(commit_id, is_successful)
 ││ 2023-05-02T06:52:55.405800740Z   File "/app/orchestrators/azdo_cicd_orchestrator.py", line 25, in notify_on_deployment_completion
 ││ 2023-05-02T06:52:55.405805540Z     pr_num = self.git_repository.get_pr_num(commit_id)
 ││ 2023-05-02T06:52:55.405810341Z   File "/app/repositories/azdo_git_repository.py", line 125, in get_pr_num
 ││ 2023-05-02T06:52:55.405814941Z     comment = self.get_commit_message(commit_id)
 ││ 2023-05-02T06:52:55.405818241Z   File "/app/repositories/azdo_git_repository.py", line 117, in get_commit_message
 ││ 2023-05-02T06:52:55.405821341Z     response.raise_for_status()
 ││ 2023-05-02T06:52:55.405824841Z   File "/usr/local/lib/python3.9/site-packages/requests/models.py", line 1021, in raise_for_status
 ││ 2023-05-02T06:52:55.405828741Z     raise HTTPError(http_error_msg, response=self)
 ││ 2023-05-02T06:52:55.405833541Z requests.exceptions.HTTPError: 400 Client Error: Bad Request for url:

Closing issue as this is the same as [https://github.com/Azure/gitops-connector/issues/47](this issue)


Model deployment on AWS Lambda using GPU ?

Hey Benjamin,
I was just watching your Pydata tutorial video. Great tutorial, thanks. However my question is that my model at inference time on my own machine uses GPU. Is that also possible to do on AWS Lambda and how so ?
Thanks

GPU-based inference on Lambda is not supported afaik.
If you want GPU-based inference I suggest using AWS Sagemaker.


Handle gzipped log files, with dates in filenames.

I have a system that automatically collects logs from all my Sensecap's onto a management server. For this to be a bit more tidy I store my logs as .../HOSTNAME/PREFIX_YYYY-MM-DD.log.gz (example: .../helium-01/console_2022-03-27.log.gz).
Here are two commits that allows this. First commit just adds an asterix to the filename glob so that logs with the date in them can be found. Second commit allows to open, and decompress, gzipped files. Also added a third commit which unsets a temporary variable to save some increased memory usage I caused.
I have intentionally used substr to detect if the filename is .gz instead of using str_ends_with from PHP 8.x, to keep backwards compatibility. None of the patches provide should give and negative impact to any existing use cases.
Please consider accepting this pull request to keep the patches in the original branch. Thank you.

Merged. Thanks for the contribution.


SASS-2042: Employment Summary Iteration

Description

Employment Summary Iteration

https://jira.tools.tax.service.gov.uk/browse/SASS-2042
Checklist PR Reviewer
Before Reviewing

[ ]  Have you pulled the branch down?
[ ]  Have you assigned yourself to the PR?
[ ]  Have you moved the task to “in review” on JIRA?
[ ]  Have you checked to ensure all dependencies are up to date?
[ ] Have you checked to ensure its been rebased against the current version of master?

Whilst Reviewing

[ ]  Have you run the tests?
[ ]  Have you looked at the JIRA story to make sure all Acceptance Criteria has been met?

After Reviewing

[ ] Have you checked for merge conflicts or any changes in the current master that may affect the current pull request? i.e. does it need another rebase?
[ ]  Have you checked to make sure there are no builds in the pipeline before you merge?
[ ]  Have you moved the task to “in pipeline” on Jira?

[x]  Have you addressed warnings where appropriate?
[x] Have you rebased against the current version of master?

Need to be merged with https://github.com/hmrc/income-tax-employment-frontend/pull/268 and https://github.com/hmrc/income-tax-submission-journey-tests/pull/121


Upgrade to MudBlazor 7

This PR upgrades to MudBlazor from 6.x to 7.x
The latest version of MudBlzor is 7.9.0, but because MudBlazorExtensions still targets 7.3.0, we can't go all the way to 7.9.0 for now, due to an API change introduced after 7.3.0 that causes a Missing Method exception at runtime.
I created a PR for that here: https://github.com/CodeBeamOrg/CodeBeam.MudBlazor.Extensions/pull/472

Hey @sfmskywalker !
Thanks for the update! Anything else needed for this or is it good to go? Just need to merge now?
Thanks,
Travis

Awesome! Thanks for the clarification @sfmskywalker.

Closing this because we don't need it for the temporary blueberry branch and because it's already done in the main branch.


More fleshed out documentation, please?

Is your feature request related to a problem? Please describe.
N/A
Describe the solution you'd like
Could we get a little more documentation on how to use the theme? It took me a while to figure out that it's a dashboard theme and not a card theme, for example. Could we get some more sample code for the light cards you show in your screenshots? An example dashboard, essentially. :)
Describe alternatives you've considered
N/A
Additional context
N/A

I don't understand how you would confuse this for a card theme. The README has screenshots of the dashboard, talks about modifying the dashboard toolbar, and has instructions on how to install it which includes enabling it as a global theme.
There's already example code in the README for the big slider card lights:
colorize: true
show_percentage: true
bold_text: true
height: 88

You should read the README in that repository for further information on setting up big slider card, but here's my full light card configurations:
type: custom:big-slider-card
entity: light.kitchen_bar
name: Bar
colorize: true
show_percentage: true
height: 88
bold_text: true
card_mod:
  style: |
    :host {
      --card-mod-icon:
        {% if is_state(config.entity, "on") %}
        mdi:ceiling-light-multiple;
        {% else %}
        mdi:ceiling-light-multiple-outline;
        {% endif %}
    }

And for lights without brightness control:
type: custom:big-slider-card
entity: light.backyard_lights
name: Backyard
color: sandybrown
show_percentage: false
height: 88
bold_text: true
max: 0
card_mod:
  style: |
    :host {
      --card-mod-icon:
        {% if is_state(config.entity, "on") %}
        mdi:string-lights;
        {% else %}
        mdi:string-lights-off;
        {% endif %}
    }


Refactor session ID adding to Request objects

Lots o' duplication out there :P

Work begun in separate branch: 269ebd5865bccc57587910f22ecc73df51cfb6aa

@LordMike think we can close this one?


Make emoji category order in typeahead consistent

Just make emoji category order in typeahead consistent.
Fixes: issue #30439
This pull request updates the emoji sorting logic in the typeahead feature to prioritize emojis in the following order:
Popular emojis
Custom (realm) emojis
Other emojis
The changes ensure that popular and custom emojis are consistently prioritized both before and after typing.
Changes Made
Updated the sort_emojis function to categorize and prioritize emojis.
Ensured unique emoji entries by removing duplicates and overriding with custom emojis where applicable.
Testing
Verified the typeahead functionality locally to ensure the correct order of emojis.
Tested for consistency in emoji sorting before and after typing.

@KUNDAN1334 Couple suggestions before a maintainer takes a look:

Edit the commit message to match the format
Do not edit out the pull request template entirely, rather fill in the checkboxes.
Attach screenshots/captures highlighting the changes. (You can put them in a <details> if there are many).
Make sure to read the docs on submitting a pull request.

Thanks @kuv2707 for your suggestion i will make sure that it matches the format.

Closing in favor of the fix for this same issue in #30459, thanks for working on this @KUNDAN1334!


Update ibm-cloud-sdk-core to 2.4.5

PR summary

Fixes: #3
Note: An existing issue is required before opening a PR.
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the
Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[x] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?
Current version of ibm-cloud-sdk-core is 2.4.0

What is the new behavior?
ibm-cloud-sdk-core is updated to 2.4.5

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

The CI has some problem.


Navlinks not working from other pages

Describe the bug
Hey @akshitagupta15june The nav links like meet pets, about us, and contact us are not working from other pages. Please assign me this issue. Thank you!
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

@akshitagupta15june Please assign me this issue