Add istio-generated key to cacerts and create self-signed cacerts secret

Please provide a description of this PR:
This change is the first of the work required to merge the istio-ca-secret and  cacerts secrets #41507. This PR is broken up into 2 parts:

Making the secret name for the istioselfsignedcarootcertrotator configurable
Adding a key to the cacerts secret. The key istio-generated is added to the cacerts Secret if the secret is generated by istiod. On istiod startup, if no istio-ca-secret or cacerts secret exists, istiod will generate a self-signed ca certificate and create the cacerts Secret with the istio-generated key set. If another istiod starts up and the cacerts secret is volume mounted it will not assume it is a plugin cert. Istiod will check for the presence of the istio-generated key. If the key is present it will start the istioselfsignedcarootcertrotator on the cacerts secret. Otherwise, istiod will treat the secret as a pluggin secret and initiate a file watch. To maintain backwards compatibility, if no cacerts secrets are mounted and an istio-ca-secret exist, istiod will initiate the istioselfsignedcarootcertrotator on the istio-ca-secret.

Notes:

A key is used to identify the cacerts secret as being a plugin secret vs an istiod generated self-signed certificate. This differentiation is required to correctly initialize the appropriate watch process: istioselfsignedcarootcertrotator which relies on a secret watch or a file watch. A key-value pair in the secret's data field is used instead of a label or annotation so the parent can be detected via the file system and istiod doesn't have to go to the Secret directly.
Some changes are not ideal and the reasoning behind the changes hasbeen documented.
ExternalCACert should be renamed.
The user cannot expect an istio-ca-secret to be created if they haven't provided a plugin cert. A cacerts secret will be created instead.

Testing:

Manual testing scenarios

Normal Istio installation with no existing cacerts or istio-ca-secret
Istio installation with existing plugin cacerts
Istio installation with existing istio-ca-secret

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

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

Test name
Commit
Details
Required
Rerun command

lint_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test lint

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

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

Test name
Commit
Details
Required
Rerun command

lint_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test lint

release-notes_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test release-notes

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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test lint

release-notes_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test release-notes

integ-ambient_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-ambient

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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test lint

release-notes_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test release-notes

integ-ambient_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-ambient

integ-basic-arm64_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-basic-arm64

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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test lint

release-notes_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test release-notes

integ-ambient_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-ambient

integ-basic-arm64_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote

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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test lint

release-notes_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test release-notes

integ-ambient_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-ambient

integ-basic-arm64_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote

integ-telemetry_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-telemetry

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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test lint

release-notes_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test release-notes

integ-ambient_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-ambient

integ-basic-arm64_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote

integ-telemetry_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-telemetry

integ-operator-controller_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-operator-controller

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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test lint

release-notes_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test release-notes

integ-ambient_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-ambient

integ-basic-arm64_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote

integ-telemetry_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-telemetry

integ-operator-controller_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-operator-controller

integ-pilot-istiodremote-mc_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote-mc

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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test lint

release-notes_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test release-notes

integ-ambient_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-ambient

integ-basic-arm64_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote

integ-telemetry_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-telemetry

integ-operator-controller_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-operator-controller

integ-pilot-istiodremote-mc_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote-mc

integ-cni_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-cni

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

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

Test name
Commit
Details
Required
Rerun command

lint_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test lint

release-notes_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test release-notes

integ-ambient_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-ambient

integ-basic-arm64_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote

integ-telemetry_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-telemetry

integ-operator-controller_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-operator-controller

integ-pilot-istiodremote-mc_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote-mc

integ-cni_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-cni

integ-security_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-security

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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test lint

release-notes_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test release-notes

integ-ambient_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-ambient

integ-basic-arm64_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote

integ-telemetry_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-telemetry

integ-operator-controller_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-operator-controller

integ-pilot-istiodremote-mc_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote-mc

integ-cni_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-cni

integ-security_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-security

integ-pilot_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot

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

/retest

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

Test name
Commit
Details
Required
Rerun command

lint_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test lint

integ-ambient_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-ambient

integ-basic-arm64_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote

integ-telemetry_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-telemetry

integ-operator-controller_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-operator-controller

integ-pilot-istiodremote-mc_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote-mc

integ-cni_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-cni

integ-security_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-security

integ-pilot_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot

release-notes_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test release-notes

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

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

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote

integ-telemetry_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-telemetry

integ-pilot-istiodremote-mc_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote-mc

integ-cni_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-cni

integ-security_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-security

lint_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test lint

release-notes_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test release-notes

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.

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

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote

integ-telemetry_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-telemetry

integ-pilot-istiodremote-mc_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote-mc

integ-cni_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-cni

integ-security_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-security

release-notes_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test release-notes

integ-distroless_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-distroless

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

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

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote

integ-telemetry_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-telemetry

integ-pilot-istiodremote-mc_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote-mc

integ-cni_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-cni

integ-security_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-security

release-notes_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test release-notes

integ-distroless_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-distroless

integ-basic-arm64_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-basic-arm64

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.

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

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote

integ-telemetry_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-telemetry

integ-pilot-istiodremote-mc_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote-mc

integ-cni_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-cni

integ-security_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-security

release-notes_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test release-notes

integ-distroless_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-distroless

integ-basic-arm64_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-basic-arm64

integ-helm_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-helm

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.

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

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-telemetry

integ-pilot-istiodremote-mc_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote-mc

integ-cni_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-cni

integ-security_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-security

release-notes_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test release-notes

integ-distroless_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-distroless

integ-basic-arm64_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-basic-arm64

integ-helm_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-helm

integ-pilot-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote

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.

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

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-telemetry

integ-pilot-istiodremote-mc_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote-mc

integ-cni_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-cni

integ-security_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-security

release-notes_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test release-notes

integ-distroless_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-distroless

integ-basic-arm64_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-basic-arm64

integ-helm_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-helm

integ-pilot-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote

integ-operator-controller_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-operator-controller

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.

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

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-telemetry

integ-pilot-istiodremote-mc_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote-mc

release-notes_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test release-notes

integ-distroless_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-distroless

integ-basic-arm64_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-basic-arm64

integ-helm_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-helm

integ-pilot-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote

integ-operator-controller_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-operator-controller

integ-cni_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-cni

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

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

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
06739df211647d19cd0fae1562ce8404e043b8cf
link
true
/test integ-pilot-istiodremote-mc

release-notes_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test release-notes

integ-distroless_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-distroless

integ-basic-arm64_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-basic-arm64

integ-helm_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-helm

integ-pilot-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote

integ-operator-controller_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-operator-controller

integ-cni_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-cni

integ-telemetry_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-telemetry

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.

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test release-notes

integ-distroless_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-distroless

integ-basic-arm64_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-basic-arm64

integ-helm_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-helm

integ-pilot-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote

integ-operator-controller_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-operator-controller

integ-cni_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-cni

integ-telemetry_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-telemetry

integ-pilot-istiodremote-mc_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote-mc

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.

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test release-notes

integ-distroless_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-distroless

integ-basic-arm64_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-basic-arm64

integ-helm_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-helm

integ-pilot-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote

integ-operator-controller_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-operator-controller

integ-cni_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-cni

integ-telemetry_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-telemetry

integ-pilot-istiodremote-mc_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote-mc

integ-pilot_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot

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.

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test release-notes

integ-distroless_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-distroless

integ-basic-arm64_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-basic-arm64

integ-helm_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-helm

integ-pilot-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote

integ-operator-controller_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-operator-controller

integ-cni_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-cni

integ-telemetry_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-telemetry

integ-pilot-istiodremote-mc_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote-mc

integ-pilot_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot

integ-security-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-security-istiodremote

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.

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test release-notes

integ-distroless_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-distroless

integ-basic-arm64_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-basic-arm64

integ-helm_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-helm

integ-pilot-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote

integ-operator-controller_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-operator-controller

integ-cni_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-cni

integ-telemetry_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-telemetry

integ-pilot-istiodremote-mc_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote-mc

integ-pilot_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot

integ-security-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-telemetry-istiodremote

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

/retest

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

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-distroless

integ-basic-arm64_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-basic-arm64

integ-helm_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-helm

integ-pilot-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote

integ-operator-controller_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-operator-controller

integ-cni_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-cni

integ-telemetry_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-telemetry

integ-pilot-istiodremote-mc_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote-mc

integ-pilot_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot

integ-security-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-telemetry-istiodremote

release-notes_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test release-notes

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.

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

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-basic-arm64

integ-helm_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-helm

integ-pilot-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote

integ-cni_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-cni

integ-telemetry_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-telemetry

integ-pilot-istiodremote-mc_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote-mc

integ-pilot_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot

integ-security-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-telemetry-istiodremote

release-notes_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test release-notes

integ-distroless_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-distroless

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

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

Test name
Commit
Details
Required
Rerun command

integ-helm_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-helm

integ-pilot-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote

integ-cni_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-cni

integ-telemetry_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-telemetry

integ-pilot-istiodremote-mc_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote-mc

integ-pilot_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot

integ-security-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-telemetry-istiodremote

release-notes_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test release-notes

integ-distroless_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-distroless

integ-basic-arm64_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-basic-arm64

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.

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

Test name
Commit
Details
Required
Rerun command

integ-cni_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-cni

integ-telemetry_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-telemetry

integ-pilot-istiodremote-mc_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote-mc

integ-pilot_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot

integ-security-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-telemetry-istiodremote

release-notes_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test release-notes

integ-distroless_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-distroless

integ-basic-arm64_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote

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.

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

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-telemetry

integ-pilot-istiodremote-mc_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote-mc

integ-pilot_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot

integ-security-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-telemetry-istiodremote

release-notes_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test release-notes

integ-distroless_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-distroless

integ-basic-arm64_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote

integ-cni_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-cni

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

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

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-telemetry

integ-pilot-istiodremote-mc_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote-mc

integ-security-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-telemetry-istiodremote

release-notes_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test release-notes

integ-distroless_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-distroless

integ-basic-arm64_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote

integ-cni_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-cni

integ-pilot_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot

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.

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

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-telemetry

integ-pilot-istiodremote-mc_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote-mc

integ-security-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-telemetry-istiodremote

integ-distroless_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-distroless

integ-basic-arm64_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote

integ-cni_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-cni

integ-pilot_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot

release-notes_istio
26fb90b8c6d5c36191c85bd12dee64e1ee889b55
link
true
/test release-notes

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.

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

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot-istiodremote-mc

integ-security-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-telemetry-istiodremote

integ-pilot_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-pilot

release-notes_istio
26fb90b8c6d5c36191c85bd12dee64e1ee889b55
link
true
/test release-notes

integ-pilot-istiodremote_istio
26fb90b8c6d5c36191c85bd12dee64e1ee889b55
link
true
/test integ-pilot-istiodremote

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.

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

Test name
Commit
Details
Required
Rerun command

integ-security-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
8cd6b0360fd30f42d4658c80dd2d0ddb0f432879
link
true
/test integ-telemetry-istiodremote

release-notes_istio
26fb90b8c6d5c36191c85bd12dee64e1ee889b55
link
true
/test release-notes

integ-pilot-istiodremote_istio
26fb90b8c6d5c36191c85bd12dee64e1ee889b55
link
true
/test integ-pilot-istiodremote

integ-pilot-istiodremote-mc_istio
26fb90b8c6d5c36191c85bd12dee64e1ee889b55
link
true
/test integ-pilot-istiodremote-mc

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.

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
26fb90b8c6d5c36191c85bd12dee64e1ee889b55
link
true
/test release-notes

integ-pilot-istiodremote_istio
26fb90b8c6d5c36191c85bd12dee64e1ee889b55
link
true
/test integ-pilot-istiodremote

integ-pilot-istiodremote-mc_istio
26fb90b8c6d5c36191c85bd12dee64e1ee889b55
link
true
/test integ-pilot-istiodremote-mc

integ-security-istiodremote_istio
26fb90b8c6d5c36191c85bd12dee64e1ee889b55
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
26fb90b8c6d5c36191c85bd12dee64e1ee889b55
link
true
/test integ-telemetry-istiodremote

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

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

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
26fb90b8c6d5c36191c85bd12dee64e1ee889b55
link
true
/test integ-pilot-istiodremote-mc

integ-security-istiodremote_istio
26fb90b8c6d5c36191c85bd12dee64e1ee889b55
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
26fb90b8c6d5c36191c85bd12dee64e1ee889b55
link
true
/test integ-telemetry-istiodremote

release-notes_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test release-notes

integ-pilot-istiodremote_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-pilot-istiodremote

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.

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

Test name
Commit
Details
Required
Rerun command

integ-security-istiodremote_istio
26fb90b8c6d5c36191c85bd12dee64e1ee889b55
link
true
/test integ-security-istiodremote

release-notes_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test release-notes

integ-pilot-istiodremote_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-pilot-istiodremote

integ-pilot-istiodremote-mc_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-pilot-istiodremote-mc

integ-telemetry-istiodremote_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-telemetry-istiodremote

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.

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test release-notes

integ-pilot-istiodremote_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-pilot-istiodremote

integ-pilot-istiodremote-mc_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-pilot-istiodremote-mc

integ-telemetry-istiodremote_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-telemetry-istiodremote

integ-security-istiodremote_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-security-istiodremote

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.

@hzxuzhonghu @howardjohn Would you mind taking a look at these changes? The istiod remote tests are failing because the cacerts secret generated in the config cluster doesn't contain the new key, istio-generated. How is the cacerts secret created in the config cluster? When the external istiod is getting the CA secret should it be treated as a self signed secret or a plugin secret? Different processes are initiated depending on these assumptions.

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

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-pilot-istiodremote-mc

integ-telemetry-istiodremote_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-telemetry-istiodremote

integ-security-istiodremote_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-security-istiodremote

release-notes_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test release-notes

integ-pilot-istiodremote_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-pilot-istiodremote

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.

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

Test name
Commit
Details
Required
Rerun command

integ-telemetry-istiodremote_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-telemetry-istiodremote

integ-security-istiodremote_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-security-istiodremote

release-notes_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test release-notes

integ-pilot-istiodremote_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-pilot-istiodremote

integ-pilot-istiodremote-mc_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-pilot-istiodremote-mc

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.

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

Test name
Commit
Details
Required
Rerun command

integ-telemetry-istiodremote_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-telemetry-istiodremote

release-notes_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test release-notes

integ-pilot-istiodremote_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-pilot-istiodremote

integ-pilot-istiodremote-mc_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-pilot-istiodremote-mc

integ-security-istiodremote_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-security-istiodremote

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.

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test release-notes

integ-pilot-istiodremote_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-pilot-istiodremote

integ-pilot-istiodremote-mc_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-pilot-istiodremote-mc

integ-security-istiodremote_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
ccf0748516b509e947e558b64aba1772b503ca95
link
true
/test integ-telemetry-istiodremote

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

It seems this is not complete, IstioGenerated secret key is not set

The istio-generated key is set in BuildSecret().

Whether or not istio-generated  is set, i can not see the diff. What is it to do?

@jaellio can you clarify above question https://github.com/istio/istio/pull/45291#issuecomment-1599983083

@jaellio can you clarify above question #45291 (comment)

I described the purpose of the key in the PR description. Do you have specific questions about the key?

I can see the pr is no complete to solve the original issue, what's the next plan

@irisdingbj would you mind taking a look at this PR? Thanks!

/test release-notes

Need another thorough look

/test all

@howardjohn @hzxuzhonghu now that branch cut for 1.19 is complete, can we get an approval to get this merged so @jaellio can start on the other tasks for this work?

Thanks, lgtm for 1.20


Base64 improvements

Add the ability to encode to base64 with no padding.
Optimized the reallocation of the ret string by reserving enough space needed.
Add length calculator functions for pre-allocation or checks.
Add isBase64 function for checking base64 encoded strings.
Add out_valid optional parameter to base64 decoder functions, for a report-as-you-go.

@an-tao are you fine with changing the function signature of decoders to use string_view instead of const std::string&?

It's ok to me.

@an-tao it is ready for merging.


[BUG] DataFrame.to_pandas generates duplicates

What is the bug?
DataFrame.to_pandas generates duplicates when an os_index_field is set and/or other than "_doc".
How can one reproduce the bug?
        opensearch_df = oml.DataFrame(client, index, columns=columns, os_index_field="@timestamp")
        index_df = opensearch_df.to_pandas(True)
        dup = index_df[index_df.duplicated(keep=False)]
        print(len(dup))

=> Loading index:
2024-03-01 16:02:58.179774: read 10000 rows
2024-03-01 16:03:07.520786: read 14895 rows
4930
What is the expected behavior?
opensearch_py_ml/operations.py:1229
    def to_pandas(
        self, query_compiler: "QueryCompiler", show_progress: bool = False
    ) -> pd.DataFrame:
...
        for df in self.search_yield_pandas_dataframes(query_compiler=query_compiler):

search_yield_pandas_dataframes should be called with sort_indexparameter set to os_index_field value defined in the   oml.DataFrame
What is your host/environment?

OS: Linux / Windows (same behavior)

Hi @cbeaujoin-stellar, thanks for creating the issue. Please feel free to raise a PR if you want.

Any update ?

Hi Dhrubo,
I attempted to reproduce the issue on OpenSearch 2.7 using the sample data, iterating over all columns and setting os_index_field for each one. However, after performing these checks, I didn’t encounter any duplicate rows.

Could you please review this and see if there’s anything I might have overlooked?
Thanks!

Hey @cbeaujoin-stellar , I hope you’re doing well.
Could you please take a look at this and try to reproduce the issue using some sample flight data?
Thanks!


Needs to mount /var/mnt by default

For system disks listed in fstab we need a pre-created writable directory, e.g. with owner and group already set. On SB, this appears to be /var/mnt -- /media and /mnt are both re-created at startup and unsuitable.

Let me see if I understand this properly.
On Silverblue hosts we have:

/media -> `/run/media
`/run/media
/mnt -> /var/mnt
/var/mnt

On legacy Workstation hosts we have:

/media
/run/media
/mnt

Currently the toolbox passes through:

/media
/run/media
/mnt

So, one doesn't see /var/mnt inside the toolbox container, but only /mnt and that too not as a symbolic link like it is on the host. However, if you mount anything under /mnt or /var/mnt on the host, then the contents do show up under /mnt inside the toolbox.
I agree that we should detect the presence of /var/mnt at run-time and pass it through if it's present, but is that the only problem? Or is it something else?

Currently the toolbox passes through:
/mnt

I don't see my host /mnt in my toolbox for F29 SB -- is /mnt a new thing I need an updated toolbox for perhaps?


Use numbers rather than string manipulation for BigDecimal encoding

Thanks for the library! It's great!
There were a couple small things that I found with the numeric binary encoding, and those are addressed here:

An extra "group" was included for some numbers that was zero-padded. Sending the number "1" as effectively "1.0000" once you decode all the groups of shorts. This may be interpreted okay by the server, but it's extra bytes that aren't necessary.
Other folks already figured out a nice quick implementation for breaking out the fractional groups, and it doesn't rely on string representations.

Hi @jgdavey Yes the current binary encoding of BigDecimal type is not ideal. It was mostly stolen from some other library. Let me take a quick look.

Thank you for fixing that! Number-based encoding is much better than strings, of course.

Now available in [0.1.26].

Great! Thanks again for the library!


Revise user guide entry for intrinsic causal influence

Overall looks good. Besides single comments, it would be good to mention and elaborate why we do not attribute mean, which comes up quite often in user discussions.

Good point. I added a remark on this.


Deprecate support for python 2.7 and 3.4 in the next major version

Python 2.7(the last of python2) and 3.4 have reached their end-of-life and are no longer supported.
The SDK should deprecate the support for these versions in the 3.0.0 release. FYI, the OpenTelemetry for Python supports python 3.5 and above.

Python 3.5 has reached its EOL in September 2020: https://www.python.org/dev/peps/pep-0478/
OpenTelemetry for Python dropped support for Python 3.5 in https://github.com/open-telemetry/opentelemetry-python/commit/d21793d1249ee6e41180dc9a33755c6dcc0e94a1.

Python 3.6 has reached its EOL in December 2021: https://peps.python.org/pep-0494/
OpenTelemetry for Python is preparing to drop support for Python 3.6, see https://github.com/open-telemetry/opentelemetry-python/pull/2763.

@jj22ee has dropped support for Python < 3.7 in 2.12, see eg. eaffcc801138fcf44d540dbf500299285a453158.  But there's still work to do:

The classifiers still suggest support for Python 2.7 and 3.4–3.6.
install_requires includes dependencies for Python 2.7
There's no python_requires to prevent pip from installing 2.12 on Python < 3.7.
… (only had a rough look so far)


Landing Page Polishing

Currently thinking about the design from https://infinum.github.io/eightshift-docs/, minus the sections below intro. So just one big background, a big title, some text description, and two buttons that get you to Tutorial and Playground, respectively.
It should be able to be done through pure CSS.
TODOs:

[ ] background pic?
[ ] landing page redesign
[ ] theme color? thinking about blu-ish due to the current Z3 logo
[ ] @NikolajBjorner Z3 logo in SVG/PNG?

@ayanamonr - should we create an updated z3 logo?

Test on mobile...


Change of Tabs in "editor"-window changes tab on Content

Seems like this is a quite new issue, it not present in the current release v0.5.0 but when running the latest stuff from master it looks like this:

In other words changing the tab in a "editor window" will change the tab on the underlaying node as well.
Some more info

This examples is tabs in a "Doc Type Grid Editor"
This does not apply when using "infinite editing" (ie opening picked node från the page)

Thanks for reporting this.
Related PR #36

Fixed in 9dabb85d4802a0e15181164dddd21d59b87978ba


fix: Updated publish extensions to use updated APIs

Description
Upon merging the provisioning work, there were some changes made to the publishing extension API that were not translated into all the publishing extensions, breaking some of them.
This PR rewrites the pvaPublish and sample-ui-plugin extensions to use those updated APIs.
Gets rid of the setPublishConfig() and setConfigIsValid() APIs.
#minor
Screenshots
pvaPublish

sample-ui-plugin

Coverage increased (+0.004%) to 54.482% when pulling a2447ac2fc42979d670039534791096960c7d778 on toanzian/fix/ext-pub-api into 6d0737fb87471749fd7ac53781a5014740ad4d45 on main.


elliptic -> @noble/*

Description
elliptic is deprecated and old, we're replacing it with an audited and maintained pkg called @noble/curves
The goal of the PR is also to replace most "handcrafted cryptography" by audited and maintained libraries.
[Closes #22]

#22

Running into issues with the sdk/wallets/wallet-aws-hsm tests. Kinda stuck on it atm

probably worth a patch bump changeset stating that elipitical was removed

Hi @kobigurk I'm kindly requesting you to have a look at this pull-request as your expertise would be greatly appreciated!

Asked for an owner (re point of contact with Kobi) on Slack.

@mcortesi suggested I contact @kobigurk directly with Telegram.


Added the code for CountingSort using Java

Have you read the Contributing Guidelines on Pull Requests?
(Write your answer here.)
YES
Description
(Write your answer here.)
Checklist

[ YES] I've read the contribution guidelines.
[YES ] I've checked the issue list before deciding what to submit.
[ YES] I've edited the README.md and link to my code.

Related Issues or Pull Requests
(Write your answer here.)

Please add a description of the changes you made to the program
Make relevant changes to the README.md file
Why did you remove the details of the initial contributor? instead, add a new row called Co-authored and add your name to it. Thank you have a great day


Fixed Issue #81 (gvr-sample showing green).

We need to call reset() for the stream after setInSampleSize.
GearVRf-DCO-1.0-Signed-off-by: Guodong Rong
<EMAIL_ADDRESS>

Code logic looks good and straight forward. Verified with Nexus 5.


Update vivapb extension

Description

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Metadata images are meant for showing Raycast and not third party extension. You can still include it in the README but then you'll need to have them in a folder called images instead

I did that before it, but never showed up on Raycast I thought I did something wrong.

Looks like there is some merge conflicts in the README file, could you look into them?

 Could you move them to a folder called images and change the references in the README

You still have the images in a folder called metadata. Could you move them to a folder called images and change the references in the README

I changed and updated it.


add supports laravel 11

Update dependencies for support Laravel 11.x

Please merge this asap

thanks, merged the prev. PR from #346 as it's the same and older. Will tag this soon.


increase cache expire for aborted workflow check

@amaltaro, Alan I updated the patch. I shouldn't use Singleton. It is supposed used with GenericDataCache (which supposed be Singleton). I am not sure this patch is actually taking effect. I will put the debugging statement whether it is honoring expire time.

Now it is tested. It works as expected.

Yes, that was why it was always updating the cache. 😄


Flow reporting that property is not available even with gate detecting case that it is undefined.

I'm unsure if this is a bug or something that I've missed, but I can't quite see why Flow is reporting errors in this sample code:
const camelize = (x) => x;
const getSearchTypeFromPath = (x) => x;

type A = {
  type: '@@router/LOCATION_CHANGE',
  payload?: {
    pathname: string,
    query: {},
  }
}

type B = {
  type: 'action.foo',
  payload?: {
    mode: string,
    params: {}
  }
}

const byMode = (
  state: {} = {},
  action: A | B,
) => {
  switch (action.type) {
    case '@@router/LOCATION_CHANGE': {
      if (!action.payload) {
        return state;
      }

      const modeKey: string = camelize(getSearchTypeFromPath(action.payload.pathname));
      return {
        ...state,
        [modeKey]: action.payload.query,
      };
    }
    case 'action.foo': {
      if (!action.payload) {
        return state;
      }

      const modeKey: string = camelize(action.payload.mode);
      return {
        ...state,
        [modeKey]: action.payload.params,
      }
    }
    default:
      (action: empty);
      return state;
  }
};

Here is a link a demo: link
The errors are:
33:         [modeKey]: action.payload.query,
                                      ^ Cannot get `action.payload.query` because property `query` is missing in undefined [1].
References:
6:   payload?: {               ^ [1]
43:         [modeKey]: action.payload.params,
                                      ^ Cannot get `action.payload.params` because property `params` is missing in undefined [1].
References:
14:   payload?: {                ^ [1]

It seems to me that the if-gate at the top of each case block, should handle the case where action.payload is undefined. Oddly, if I remove the functions that in this example code have been turned into dummies, the code doesn't produce any errors, even though the logic of the program flow is as far as I can tell the same. Here it is without the dummy functions: link

This is because of your calls to camelize. Flow invalidates refinements after function calls-- see https://flow.org/en/docs/lang/refinements/#refinement-invalidations-


Add a header row to the output file

Add a header row to the output file with column names.

Added


Request: Reduce number of gas-burning generators needed for max speed electrolytic separator

Mass oxygen production is cumbersome as you need 2 generators to match the power consumption of a basic separator and each speed upgrade doubles that (which quickly spirals to 512 generators for a maxed separator).
There's a number of solutions to this problem:

Allow using speed upgrades on a generator to burn through more hydrogen
Compound generators to reduce number of needed blocks without reducing resource cost
A config option to set the default burn rate higher
An upgrade for the separator to allow it to burn the hydrogen itself

As it stands, if I want to use separators to produce enough oxygen for anything particularly demanding (galacticraft sealers, for instance), in order to offset the power consumption I would need over 30 generators running full-time. Whilst this is somewhat balanced, it can easily be lag-inducing when scaled up (I would need over 500 for my planned base).

The solution to the problem is to find alternative means to power the system.

Assuming I only have Galacticraft and Mekanism installed, what reasonable method do I have for using the separator running to power oxygen sealers through a night on the moon (which lasts 28x as long) which will never expire?
This leaves three options:

Solar power = Needs a pretty big power bank to last the full night
Gas-Burning = Needs a large number to handle all the hydrogen
Bio-Generator = Needs half as many as Gas-Burning (by default), but also a farm to support it
(I've yet to try a fusion reactor, but those are probably large and complicated, overkill for this task, and require pumping heavy water which would be far more lag-inducing)

The issue is simply that there's no decently scaling alternative provided by the mod itself for this middle tier, it jumps directly from small power generation to massive power generation. Whilst this isn't an issue for one person, if you get several people doing this at the same time then there's an issue with server CPU usage.

@hexicube about the only thing I could suggest are induction matrix multiblocks for power storage.

Power storage is not power generation.

The issue you're having is lack of a "medium-high tier" of energy production.  The reason it's an issue for you though, is because you're trying to suppliment Galacticraft's oxygen needs with Mek's production (which wasn't meant to handle GC's large-scale oxygen usage)
Mek, as a standalone mod, has very acceptable power production for the uses you find with it.  It's only when you try to use its power methods to suppliment another mod that there's problems.
Your two options, from what I see, are either using GC's own oxygen production to keep your habitat aerated, or I would suggest adding another mod to make up the middle area, since you're already using more than one mod in conjunction.  Big Reactors, or Railcraft (Industrial steam engines, woo!), for example, would fit wonderfully for what you're needing.  Another option would be Thermal Expansion (whichever one of its subsidiaries has the dynamos) or the generators from Extra Utilities.

I was actually already using Big Reactors, but I'm keeping that on a mostly closed loop as I'm using the power for MFR drills to get yellorium and don't currently have the materials to enlarge it for more efficiency. I also wanted to keep oxygen systems on a closed loop so most generators were generally not applicable, as I wanted the oxygen systems to function regardless of outside factors, so failure from lack of fuel or bad time is a pretty big no-no.
I did actually also submit an issue to GC about the sealer usage being 320/s and it's going to be dropped down to 120/s, which is substantially better, but that would still require a fair amount of collectors (each leaf per collector is 2/s IIRC) as I have quite a few sealers (currently 16, should be 18 but reactor room unsealed).
My issue isn't a lack of mid-high tier power production for my mod-pack in particular, my issue is the lack of that power production that requires no upkeep for this task. Normally, that wouldn't exist, but I just so happen to get a surplus of hydrogen. I can achieve the required production, the issue is just space and CPU usage by doing so.
Is it really that unreasonable to want a more advanced gas-burning generator that costs more materials, considering hydrogen is simply an energy carrier?

Well, if you were going to add a larger gas-burning generator, you might as well add a larger electrolytic separator too.
The issue you're describing though (A no-upkeep power supply) is not solved via gas burning generators.  The energy you use to produce the O2 and H is more than the energy you then get back from burning the H in the gas-burning.  You're either using an outside power source to create  the O2 (which you could plug your sealers into) or you will eventually run out of O2 and H to burn.
You'd be more "no-upkeep" if you had a BigReactor running it (since they can produce their own fuel via laser drills) or a solar power source with a large bank of some kind of capacitors/batteries.

All of this describes the fact that hydrogen, per design, is meant to power a electrolytic separator to make it cost neutral, not provide net positive power production.
—
Sent from Mailbox
On Sun, Oct 25, 2015 at 2:52 AM, Hexicube<EMAIL_ADDRESS>wrote:

I was actually already using Big Reactors, but I'm keeping that on a mostly closed loop as I'm using the power for MFR drills to get yellorium and don't currently have the materials to enlarge it for more efficiency. I also wanted to keep oxygen systems on a closed loop so most generators were generally not applicable, as I wanted the oxygen systems to function regardless of outside factors, so failure from lack of fuel or bad time is a pretty big no-no.
I did actually also submit an issue to GC about the sealer usage being 320/s and it's going to be dropped down to 120/s, which is substantially better, but that would still require a fair amount of collectors (each leaf per collector is 2/s IIRC) as I have quite a few sealers (currently 16, should be 18 but reactor room unsealed).
My issue isn't a lack of mid-high tier power production for my mod-pack in particular, my issue is the lack of that power production that requires no upkeep for this task. Normally, that wouldn't exist, but I just so happen to get a surplus of hydrogen. I can achieve the required production, the issue is just space and CPU usage by doing so.
Is it really that unreasonable to want a more advanced gas-burning generator that costs more materials, considering hydrogen is simply an energy carrier?
Reply to this email directly or view it on GitHub:
https://github.com/aidancbrady/Mekanism/issues/2991#issuecomment-150897560

And not even cost-neutral.  You get back maybe 90% of the energy you put in.

It's cost-neutral, you get free oxygen from the two machines combined. I don't know how you're losing power, but you may want to look into your designs.
A larger electrolytic separator already exists, due to speed upgrades. It goes all the way to 256x speed requiring 512 gas-burning generators to match the demand for a cost-neutral oxygen production setup (each tick produces 2 hydrogen, gas-burning generators only burn 1 per tick).
The issue I'm describing currently IS solved by gas-burning generators, it costs X power to create 1 oxygen and 2 hydrogen, and burning that 2 hydrogen gives X power back.
BigReactor reactors require fuel from the laser drill, which means I have to hit a specific breaking point in efficiency on a closed system. Any power drain on top of the drill reduces that efficiency. Whilst solar panels would in fact be 0 upkeep, the required power storage per sealer is massive (my particular base would need over 4TJ of storage, for the separators alone). It would be cheaper (by far) to just make a ton of gas-burning generators.
I didn't have the yellorium to build and fuel a larger reactor, I barely scraped enough to make the current one. I had a lot of other resources to make the base, sealers, and gas-burning generators with a bit of iron to spare. The thing that irks me is the gas-burning generator is one of the few machines that cannot be upgrades, and is one that would benefit a lot from it.
Even if gas-burning generators doubled in speed to burn 2 hydrogen per tick, that would be a decent improvement. As it stands, you need 2 for a basic separator which is an odd matching to say the least. It feels like an oversight.

You're literally describing creating something, from nothing.  If you could power a separator entirely on the H it produced, you would be creating free oxygen.  There was an issue open about this very fact about a year ago, and I'm fairly certain @aidancbrady changed it.  The issue was that the loop was self sustaining (which is what you're describing)
Gas-burning generators are not meant to be used as a source of power when ran off of electrolytic separators; they are a means of reclaiming a small portion of the energy that you used, but not all of it.
For curiosity's sake, what were you powering all these things from originally/currently, if gas-gens aren't cutting it and/or before you had gas-gens?

The separators are fully powered from the hydrogen, and my sealers were originally going to be powered by heat generators but they provide such a pitiful amount of power that I'm using the big reactor for that. The sealers have a tiny power requirement compared to the separators.
I initially had a small base on the overworld, so the separators have always been self-sustained.
I always thought that a power-neutral setup was intentional and that the issue was that you could use the loop to actually create free power, so if it's supposed to cause a power loss then the issue can be re-opened.
I'd have no issue with a power loss (90% reclaimed via hydrogen burning?), as long as the gas-burning generators become more capable of doing the power reclaiming and the loss is small but still an issue that needs to be appropriately handled. With 10% loss, that's still be hundreds of GJ through the night, but that's at least manageable with a tier 1 induction cell. ~400GJ vs ~4TJ is a massive difference, but ~400GJ is no joke. I'd also only then need about 15 large solar panels, as opposed to 150, to charge it. I'd consider a 10% loss well balanced for the task I'm performing, but it could also be configurable.

@EvulOne you need a specific amount of energy to split H2O into 2H and 1O and if oxygen and hydrogen are burned in the gas-burning generator, they create the exact same amount of energy that was used to split them. The oxygen needed to burn the hydrogen is taken from the air around the block. Just think of the combustion engine of a car. It needs oxygen which it gets from the air around it (or does any car you know of have an internal oxygen tank?).
As conclusion: It totally makes sense to be able to power a separator from the hydrogen it produces in a world where everything is 100% efficient.

I'm burning the hydrogen on the moon, where does the oxygen come from?

What you are now describing is a limit in compatibility between mods. It would be possible via GCs API to make the gas burning generator only work in a pressurized area, but because this very specific sort of compatibility is not done, the generator just assumes that there is oxygen in the area and burns the hydrogen.

But the oxygen in the sealed area comes from the separator, so no matter how you look at it either the compatibility would be off or there would be massive integration pains on at least one end.

If you're talking about a truly realistic example, we cannot regain all the energy we use to produce Hydrogen.  Yes it burns the Oxygen in the atmosphere, but there's loss to heat and other forms of energy during the process, so there is no way to have a 100% return on energy used.

But Minecraft is not realistic, it's a world where everything is optimized to be 100% efficient (except for some mods),

MineCraft isn't 100% efficient at it's core, simply due to chest mechanics it maxes out at 50% storage efficiency. Perhaps the fabric of reality will tear if untreated wooden storage devices are used in such a dense manner?
I'm talking pure balance and enjoyability here, I would like to see gas-generators be more powerful, and to compensate they should be 10% lossy.

Not sure if this is still active, but what about ethylene? It's EXTREMELY efficient, and would require a lot less gas burners to create a huge amount of energy. Problem is you need 20 biomass for about 30 MJ of power, so you'd need a big as heck farm (maybe automatic) to gain the power you need. Just make a big power bank charged by ethylene which should give you enough power.

I know what OP is doing in his post and why.
In v8, all prior understanding of the separator/gas engine should be discarded and not revisited.
GC is an oxygen hungry system. Frankly I've discussed carbon scrubber systems with the author(s) and was declined.
The proper way to get oxygen in mass quantities that you need, will require TE, Mek, and GC.
Oxygen collectors output to Rotary Condensentrators making liquid oxygen (like in real life!). Pipe this through a tesseract from TE as gasses are not transferable. Use another Rotary Condensentrator to decompress the liquid on the other side and distribute appropriately.
Also pay attention to the pipe system you use to move the oxygen! It DOES matter.

Gas Generator now scales output rate to the amount of gas stored in its buffer.  Should be solved :)


Creator Can Add A Link

[x] apply a link to any element that is not set as a bg or fullscreen
[x] remove applied link
[x] edit brand icon (add/remove)
[x] edit description (add/remove)

Verified in QA


fix: adjust metadata types

This is to cut down on the significant digits, right - just converts to ints?


Relay useful PopupMenu signals through MenuButton

Really simple relaying of the PopupMenu signals through MenuButton, just to make hooking them up through the editor simpler, I know that you can easily connect them through code by using get_popup() but the fact that the menu button doesn't follow the same convention as most of the UI elements where you can just connect through the editor seems to be a source of confusion for new users (see example 1, 2, 3), these from just a few seconds of googling.
The one thing I'm not sure about is the documentation, I didn't want to copy-paste the PopupMenu docs so I just linked to the appropriate signal, but I'm not 100% on the wording or if that's advised.
Let me know if this needs a proposal, figured it was a small enough QOL change that it wouldn't necessarily warrant one.

Let me know if this needs a proposal, figured it was a small enough QOL change that it wouldn't necessarily warrant one.

If users are confused on how to use a node, the first step should be improving the documentation. The description of MenuButton could explain how to use popup signals.
Also, while your new signals forward the main popup's signals (which btw isn't something we do in other classes), it won't handle sub-menus, so this change alone doesn't help fully utilizing this node.

Documentation would definitely help, my main gripe with how it's handled right now is consistency.
The case I ran into was in making a menu bar with a few buttons, I could connect them all via the editor with no code except for the MenuButton.
For submenus you already have to dip into GDScript to create and insert it into the popup, so it'd be natural to have the signals connected in code.
Otherwise I'd, for example, have a script where only one of the signals is connected with code and the rest with the editor. It's not really a big deal, but I feel like it's better for simplicity and consistency with other control nodes.


Update to syn v2

Awesome :) thanks mate
The iOS build is already broken on main. This isn't a target I aimed to support anyway though, so I'll remove that target from the CI for the time being in a separate PR :)


feat: (a + b) ^ n ≤ 2 ^ (n - 1) * (a ^ n + b ^ n)

Note that this inequality is trivial if the constant is 2 ^ n instead.
Due to the current import situation, I've had to downgrade the proof to not use gcongr, positivity, ring. This is currently hard to fix.
From LeanAPAP

Unless you really want it in before then, I'm tempted to just wait for #9411 + the other PRs that will make this better. As such, I've added it as a dependency so it inherits the blocked-by-other-PR label.
If you do want it in sooner, remove that and request my review and I'll do it quickly.

It seems to be quite hard after all... I've split off #10140 to make positivity accessible in more files, but I haven't managed to make it available in Algebra.GroupPower.Order. I suggest this PR as is and I will continue improving the situation later.

Thanks!
bors merge


args._event equals "cpu" when sending "alloc" event in profiler.sh

Hi,i felt a little confused when i want to get allocation of one process whereas the args._event in log is "cpu".I am not sure if it is intentionally.Below is my settings:

openjdk version "11" 2018-09-25 OpenJDK Runtime Environment 18.9 (build 11+28) OpenJDK 64-Bit Server VM 18.9 (build 11+28, mixed mode)

async-profiler-2.8.3 release

cmd:./profiler.sh -e alloc --alloc 1k -o traces jps

my log: profiler.cpp:1273
void Profiler::dumpText(std::ostream& out, Arguments& args) {  printf("enter Profiler::dumpText,args.event:%s\n",args._event);

testcode:
`import java.util.Random;
public class TestBanking {
public static void main(String[] args)throws InterruptedException {
int total=100;
StringBuilder sb1=new StringBuilder();
int x[]=new int[total];
 for (int i=0;i<16000;i++){

         for(int j=0;j<total;j++){
                 int a=1;
                 char b='c';
                 Random random = new Random();
                 int rannum = random.nextInt(101);

                 sb1.append('a'+"");
                 sb1.append('b'+"");
                 x[j]=rannum;
         }
         Thread.sleep(1000);

 }

}
}`

-e alloc is an obsolete way to enable allocation profiling; it remains for compatibility reasons only.
--alloc <size> is a preferred way. -e alloc is ignored when --alloc <size> is specified.
Similarly, --lock <size> is preferred to -e lock.
These changes were needed to allow CPU, Allocation and Lock profiling simultaneously.

ok,I got it.


Not version 3.12.0 on docker hub repository.

OS/Web Information

Web Browser:
Local OS:
Remote OS:
Remote Architecture:
code-server --version:

Steps to Reproduce

There are not a version 3.12.0 on docker hub repository.

Expected

There should be a docker hub image.
Actual

There are not a version 3.12.0 on docker hub repository.
Logs

Screenshot

Notes

This issue can be reproduced in VS Code: Yes/No

Thanks for opening this! We're aware and sharing updates here: https://github.com/cdr/code-server/discussions/4178


fixed not beeing able to open empty scripts

It was not possible to open up completely empty scripts.
fixes #11561

LGTM.
That being said, I have no clue what's this has_source_code function is for. Once removed here, it's no where else used. :/
Anyway, merging.

Yeah. i cant think of anything that the function would be for either. I tested it quite extensively and couldn't find any bugs, should be fine. thanks for merging ^^


parallax on index page disables when removing the sliders

Hi there,
I started my development, based upon the index-template.
When I remove the slides that were added on the page, the parallax effect is lost.
I solved this by putting it in a display:hidden-div, but seems strange...
Any idea how I could solve this? I like the kit very much!
Best regards and thanks for your help.
Stijn

@StijnKeppens thank you for using our product. We've also removed the slides carousel from it and it is working fine. Please send us a link with your website so we can check. Also, make sure you don't have any javascript errors in the Developer console on Chrome/Firefox.
Best,
Alex

Hi Alex,
Thanks for looking into this.
I just re-downloaded the kit, put it on my webspace and set the sliders in comment.
Just doing that, I get a javascript error (noUiSlider: Can't initialize slider on empty selection) and loosing parallax.
http://luiehond.be/vwcalifornia/obsolete/test/index.html
How should I remove this not creating the js error?
Best regards.
Stijn

Hi @StijnKeppens,
You said you use the "index-template" ?
Might it be possible you got this script:
`

Big thanks @Gui-sf
Works perfectly now!


App crashes when i change the layout of albums from Grid to Linear.

After opening the app, i goes to album folder and then i clicked on options where i saw "album layout" option. I clicked on it to change the layout, i changed it from Grid to Linear. App got crashed. Not only app crashes, i am not able to open it agin untill i clear its whole data.
Screenshot/Video

System Information:

Device: RedMi S2/Y2.
OS: 8.1.0
Version: <IP_ADDRESS>(20190608)

try lastest version on release page

try lastest version on release page

I tried latest version
But it also has same issue...

try lastest version on release page

I tried latest version
But it also has same issue...

Can you give me a log? This feature works fine on both of my devices.

It is working properly.

It is working properly.


@xtina-starr => Infinite scroll/Display bugs

Removes /news rendering of DisplayCanvas and RelatedArticlesCanvas in favor of rendering in Reaction.  Follows up on https://github.com/artsy/reaction/pull/1008.

Reaction is now bumped and this is ready to go.

👍


Why the "id" field is a string?

How to change it nicely to integer?
Is there a strong reason that this should be string?

It's dictated by the spec. ref: https://jsonapi.org/format/1.0/#document-resource-object-identification

Every resource object MUST contain an id member and a type member. The values of the id and type members MUST be strings.

You could think about type of id field in terms of operations defined on the type. Integers can be added, substracted, etc., while adding id's together bear no sense at all. IMO main reason why Rails cast id's as integers is because they are integers in the DB, and that's because of performance reasons - indexes on int's are more compact and faster

Good question to take up with the designers of the JSON API spec. I appreciate that this package sticks to the spec.

There are some cases when id column could be GUID or have composite keys, e.g. in cases when clustering/sharding is necessary.
Making it integer by default means this package would not work nicely and all kind of weird behaviour could happen:
irb(main):024:0> SecureRandom.uuid
=> "757e81ad-755d-479c-aabe-640cb0860893"
irb(main):025:0> SecureRandom.uuid.to_i
=> 0


Adding responsiveness

I would like to request that the responsiveness of the project be improved. This would make the project easier to use on devices with different screen sizes and resolutions.
The benefits of improving responsiveness are:
It would make the project easier to use on devices with different screen sizes and resolutions.
It would make the project more user-friendly.
It would improve the overall user experience.

I believe that improving responsiveness would be a valuable addition to the project and would make it more user-friendly. I hope you will consider my request.

@M-A-N-I-K someone is already working for that. Please check the issues


message list: Render new messages only after "newest" is found.

Fixes #14017

Testing Plan:
Tested manually as follows:-

set 5 secs delay for get messages.
Also set 10 seconds delay if query_info['found_newest'] = True in same view function
set timeout duration to 500000 in sent messages. (not sure if necessary, was getting blueslip warnings about event loop restarting)
./manage.py populate_db -n10000
./manage.py mark_all_messages_unread
Go to private message narrow
send a message to that narrow when all the messages haven't been fetched.
Previously the new message would get temporarily displayed.
Now the new message isn't rendered but is processed. (such as unread count increases)
send another message when last batch is being fetched.
This message gets stored in _newest_items and after the fetch is complete and the new if condition in message_list.js is satisfied, the new message(_newest_items) is rendered after the fetched messages(bottom_messages).

I also tested the last point by discarding the new message event if "newest" has not been found by the current message list.
Then if a new message is sent while fetching the last batch for that narrow then the message is missing. (as mentioned in the issue)

This is really great work; I especially appreciate that you dug into the testing process here.  (And are grabbing the other related message_list issue we opened this week).
One thing to mention about the long term here: We'll eventually want to move to a model where we cache MessageListData objects for a large number of views, not just one at a time to support loading narrows one's visited in a given browser fashion really fast (As we'd just need to render, without fetching any message history from the server).  So the transition of moving FetchStatus to the lower-down object would be a useful part of preparing for that.
The main work in that migration will of course be taking all the message-editing-related rerendering logic that currently only loops through a fixed list of the 1-3 possible MessageList objects today.
@amanagr FYI as well.

For the first commit, what I had in mind was also moving all the references to .data.fetch_status rather than keeping a copy of message_list; it's cleaner to not have multiple ways to access this structure.  And conceptually, it belongs in message_list_data.

I'm worried this has a lot of complexity that may be tricky to get completely right.
After thinking about this a bit more, I wonder if there's a better solution to that second race than adding this new mechanism for appending _newest_messages to the message list that has a lot of careful things to maintain and test.
What if we instead handle the receipt of a message when fetch_status.has_found_newest is False by storing the new message's ID in fetch_status.expected_minimum_max_message_id (well, with a max() calculation in case we see more than one).  And then that we just store the highest newly received message ID to, and refused to honor a server-provided has_found_newest=True when storing into fetch_status unless we've received a message ID that's at least that value?
The end result is we'd do an extra fetch to the server in this extremely rare race case, which is immaterial performance-wise, but it'd be a lot easier to reason about than having these saved messages that we intend to append later.

@timabbott could you have a look?
I rename it as expected_max_message_id as, as implemented we are updating the latest message id on the frontend (from received events as well as fetches).

The first commit is great, merged as cfc87e39259da57e462bcf7c3b2ac884fdc6f864.

I posted a bunch of comments that I think should lead to a really clean final implementation for this; let me know what you think.  And please report on whether you have done the careful testing with the revised version :)

Just a quick ping on this; I'd like to get it integrated soon so it can bake a few weeks before our next release.

The bugs in the original issue is resolved but I think there is still a buggy behaviour.
When edge case occurs (i.e. after the last batch of messages when fetch should again occur to get the actual (expected_max_message_id) last messages) then to display the new messages the user has to scroll a bit.
( This may also go on again if a message is received during the "re-fetch". )
And it isn't obvious by looking that the narrow should be scrolled when there are 1 or 2 one-liner messages.
Although if the user doesn't scroll and sends a message the "out of narrow" text is displayed (which is correctly done).
I also notice a situation where the users has to scroll up and then again down to fetch the new messages.
This last part is easily reproducible by adding a function to set found_newest to False in the fetch_status api, then calling this function in message_util.add_new_messages (without any changes mentioned in to original testing comment of this PR).
I am looking into this .......

@timabbott @showell this is ready for another review.
I added a second commit for the bug mentioned in the comment above.
From what I understand, the messages for home_msg_list gets continuously fetched until "newest" is found, so it won't have the same problem as that of narrows.

Yes, that's correct re: home_msg_list.

@timabbott .
I tested this again and the problems mentioned in this issue are resolved. And the messages are being fetched as long as I continue to create the race condition (send a message). Also no messages are displayed out of order.

This is great, merged as 62aab0d9eec154aefd2651b97242d65e95838fc4 after rewriting the comments to explain the race conditions in more precise details; I hope that'll be helpful the next time we need to make a change to this logic.
Huge thanks for making this happen @ryanreh99!


upstream: change additional_source_addresses as a repeat of new message

Signed-off-by: He Jie Xu<EMAIL_ADDRESS>Commit Message: upstream: change additional_source_addresses as a repeat of new message
Additional Description:
For dual-stack case, people may set different config for different source address (like different socket options, and it discussed at slack https://envoyproxy.slack.com/archives/C78HA81DH/p1664228598624269), the original API isn't future-proof. This PR changes the additional_source_addresses as a repeat of AdditionalSourceAddress message, then it enables to add more config bind to the additional source address in the future. Fix this before this feature release in the last release.
https://github.com/envoyproxy/envoy/blob/6bba2d69a17e4cf374eb09f7f51fbf0f0ce4b7da/changelogs/current.yaml#L189-L191
Risk Level: low
Testing: unittest
Docs Changes: API doc
Release Notes: there is an existing release note
Platform Specific Features: n/a

/assign @mattklein123

cc @ravenblackx also

I will check with @envoyproxy/api-shepherds to see if we can land this since this was not yet released. I'm inclined to let it in as I can't imagine anyone is using this yet and this will avoid a deprecation.

Unfortunately according to to the policy (https://github.com/envoyproxy/envoy/blob/main/api/API_VERSIONING.md) we can only make changes up to 14 days after the initial API went in, so I think we have to deprecate.
/wait

got it, sorry about that, let me deprecate.


ROX-26097: Add CVSS metrics to EmbeddedVulnerabilities

Description

EmbeddedVulnerability should include all CVSS scores
User-facing documentation

[ ] CHANGELOG is updated OR update is not needed
[ ] documentation PR is created and is linked above OR is not needed

Testing and quality

[ ] the change is production ready: the change is GA or otherwise the functionality is gated by a feature flag
[ ] CI results are inspected

Automated testing

[x] added unit tests
[ ] added e2e tests
[ ] added regression tests
[ ] added compatibility tests
[ ] modified existing tests

How I validated my change

change me!

Note that @ksurabhi91 would add a new NVDCVSS field to EmbeddedVulnerability here : https://github.com/stackrox/stackrox/pull/12896/files#diff-008785105e1470fc53c73bd5e8108c9671241fa04261cfbcc5a5e6c68bf46298R58
This field is needed for policy criteria to work. So you may need to set that in your changes too.

It seems that either I'll need to set the NVD score after she merges her changes, or she will need to set it after this PR is merged.


Formatter: crash with an if affecting a variable and with a trailing condition

This produces a formatting Error: expecting keyword false or true, not IDENT, a, at :1:4 (Exception)
if a = 0
  a
end if true

I'd go as far as to say that trailing ifs on multi-line expressions shouldn't compile.


Final Model

Hey would it be possible for you to upload the final model?
Thanks,
Rohin

Hi @rohinrohin . Since I worked on this project more than an year ago, I unfortunately don't have the saved model or the trained weights anymore.
Apologies for the delayed reply.


Update find-your-domain-registrar.md

Updating text for #128 to accurately state the TLDs InterNIC supports.

@pebaum - can you please assist to approve and merge the content for this PR based on issue #128 ?
Thank you.

@pebaum - I would like to follow up on this. Can you please assist to approve and merge the content for this PR based on issue #128?
Thank you.