Automator: update proxy@master in istio/istio@master

Generated by Automator - 2020-11-23T14:05:03+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
9bde0989b18b0f423ae5146fb2ac4ecb8c62c12b
link
/test integ-telemetry-k8s-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
9bde0989b18b0f423ae5146fb2ac4ecb8c62c12b
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
9bde0989b18b0f423ae5146fb2ac4ecb8c62c12b
link
/test integ-telemetry-mc-k8s-tests_istio

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

/retest

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
9bde0989b18b0f423ae5146fb2ac4ecb8c62c12b
link
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-k8s-tests_istio
9bde0989b18b0f423ae5146fb2ac4ecb8c62c12b
link
/test integ-telemetry-k8s-tests_istio

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

/retest

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
9bde0989b18b0f423ae5146fb2ac4ecb8c62c12b
link
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-k8s-tests_istio
9bde0989b18b0f423ae5146fb2ac4ecb8c62c12b
link
/test integ-telemetry-k8s-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
9bde0989b18b0f423ae5146fb2ac4ecb8c62c12b
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
9bde0989b18b0f423ae5146fb2ac4ecb8c62c12b
link
/test integ-telemetry-mc-k8s-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
9bde0989b18b0f423ae5146fb2ac4ecb8c62c12b
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
9bde0989b18b0f423ae5146fb2ac4ecb8c62c12b
link
/test integ-telemetry-mc-k8s-tests_istio

integ-multicluster-k8s-tests_istio
fb5df6e48073e6f8c068e3e41a86b21bfaee173d
link
/test integ-multicluster-k8s-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
9bde0989b18b0f423ae5146fb2ac4ecb8c62c12b
link
/test integ-telemetry-mc-k8s-tests_istio

integ-multicluster-k8s-tests_istio
fb5df6e48073e6f8c068e3e41a86b21bfaee173d
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-k8s-tests_istio
fb5df6e48073e6f8c068e3e41a86b21bfaee173d
link
/test integ-telemetry-k8s-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
9bde0989b18b0f423ae5146fb2ac4ecb8c62c12b
link
/test integ-telemetry-mc-k8s-tests_istio

integ-multicluster-k8s-tests_istio
fb5df6e48073e6f8c068e3e41a86b21bfaee173d
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-k8s-tests_istio
fb5df6e48073e6f8c068e3e41a86b21bfaee173d
link
/test integ-telemetry-k8s-tests_istio

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

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
fb5df6e48073e6f8c068e3e41a86b21bfaee173d
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-k8s-tests_istio
fb5df6e48073e6f8c068e3e41a86b21bfaee173d
link
/test integ-telemetry-k8s-tests_istio

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

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

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

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

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

integ-telemetry-k8s-tests_istio
af2f1739e0820f63be9772b6df9940c4b365ea0b
link
/test integ-telemetry-k8s-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
af2f1739e0820f63be9772b6df9940c4b365ea0b
link
/test integ-telemetry-k8s-tests_istio

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

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
af2f1739e0820f63be9772b6df9940c4b365ea0b
link
/test integ-telemetry-k8s-tests_istio

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

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
af2f1739e0820f63be9772b6df9940c4b365ea0b
link
/test integ-telemetry-k8s-tests_istio

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

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
af2f1739e0820f63be9772b6df9940c4b365ea0b
link
/test integ-telemetry-k8s-tests_istio

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

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-helm-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
af2f1739e0820f63be9772b6df9940c4b365ea0b
link
/test integ-telemetry-k8s-tests_istio

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

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-helm-tests_istio

integ-distroless-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-distroless-k8s-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
af2f1739e0820f63be9772b6df9940c4b365ea0b
link
/test integ-telemetry-k8s-tests_istio

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

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-helm-tests_istio

integ-distroless-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-multicluster-k8s-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
af2f1739e0820f63be9772b6df9940c4b365ea0b
link
/test integ-telemetry-k8s-tests_istio

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

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-helm-tests_istio

integ-distroless-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-multicluster-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
af2f1739e0820f63be9772b6df9940c4b365ea0b
link
/test integ-telemetry-k8s-tests_istio

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

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-helm-tests_istio

integ-distroless-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-multicluster-tests_istio

integ-pilot-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-k8s-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
af2f1739e0820f63be9772b6df9940c4b365ea0b
link
/test integ-telemetry-k8s-tests_istio

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

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-helm-tests_istio

integ-distroless-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-multicluster-tests_istio

integ-pilot-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-operator-controller-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
af2f1739e0820f63be9772b6df9940c4b365ea0b
link
/test integ-telemetry-k8s-tests_istio

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

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-helm-tests_istio

integ-distroless-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-multicluster-tests_istio

integ-pilot-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-multicluster-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
af2f1739e0820f63be9772b6df9940c4b365ea0b
link
/test integ-telemetry-k8s-tests_istio

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-helm-tests_istio

integ-distroless-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-multicluster-tests_istio

integ-pilot-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-mc-k8s-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
af2f1739e0820f63be9772b6df9940c4b365ea0b
link
/test integ-telemetry-k8s-tests_istio

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-helm-tests_istio

integ-distroless-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-multicluster-tests_istio

integ-pilot-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-k8s-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-helm-tests_istio

integ-distroless-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-multicluster-tests_istio

integ-pilot-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-k8s-tests_istio

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

/retest

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-helm-tests_istio

integ-distroless-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-multicluster-tests_istio

integ-pilot-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-k8s-tests_istio

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-helm-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-helm-tests_istio

integ-distroless-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-multicluster-tests_istio

integ-pilot-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-k8s-tests_istio

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-helm-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-helm-tests_istio

integ-multicluster-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-multicluster-tests_istio

integ-pilot-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-k8s-tests_istio

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-distroless-k8s-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-helm-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-helm-tests_istio

integ-pilot-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-multicluster-tests_istio

integ-pilot-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-k8s-tests_istio

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-multicluster-k8s-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-multicluster-tests_istio

integ-pilot-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-k8s-tests_istio

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-multicluster-k8s-tests_istio

integ-helm-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-helm-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-k8s-tests_istio

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-multicluster-k8s-tests_istio

integ-helm-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-helm-tests_istio

integ-pilot-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-multicluster-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-k8s-tests_istio

integ-security-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-k8s-tests_istio

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-multicluster-k8s-tests_istio

integ-helm-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-helm-tests_istio

integ-pilot-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-operator-controller-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-k8s-tests_istio

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-multicluster-k8s-tests_istio

integ-helm-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-helm-tests_istio

integ-pilot-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-operator-controller-tests_istio

integ-pilot-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-k8s-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-k8s-tests_istio

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-multicluster-k8s-tests_istio

integ-helm-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-helm-tests_istio

integ-pilot-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-operator-controller-tests_istio

integ-pilot-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-k8s-tests_istio

integ-security-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-multicluster-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-k8s-tests_istio

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-multicluster-k8s-tests_istio

integ-helm-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-helm-tests_istio

integ-pilot-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-operator-controller-tests_istio

integ-pilot-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-k8s-tests_istio

integ-security-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-mc-k8s-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-k8s-tests_istio

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-multicluster-k8s-tests_istio

integ-helm-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-helm-tests_istio

integ-pilot-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-operator-controller-tests_istio

integ-pilot-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-k8s-tests_istio

integ-security-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-k8s-tests_istio

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-multicluster-k8s-tests_istio

integ-helm-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-helm-tests_istio

integ-pilot-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-operator-controller-tests_istio

integ-pilot-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-pilot-k8s-tests_istio

integ-security-multicluster-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5e65c0a3b3e09225f6e2cf02412dd7d3ce917083
link
/test integ-telemetry-k8s-tests_istio

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

https://github.com/istio/istio/pull/29127


Add support for ChaCha20/Poly1305.

Codecov Report

Merging #38 (cab2ded) into main (12c7782) will decrease coverage by 0.02%.
The diff coverage is 95.83%.

@@            Coverage Diff             @@
##             main      #38      +/-   ##
==========================================
- Coverage   96.28%   96.26%   -0.03%
==========================================
  Files          18       19       +1
  Lines         619      642      +23
  Branches       68       69       +1
==========================================
+ Hits          596      618      +22
- Misses         22       23       +1
  Partials        1        1

Flag
Coverage Δ

unittests
96.26% <95.83%> (-0.03%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/aeadKeys/aesGcmKey.ts
100.00% <ø> (ø)

src/cipherSuite.ts
100.00% <ø> (ø)

src/aeadKeys/chacha20Poly1305Key.ts
93.75% <93.75%> (ø)

src/encryptionContext.ts
94.59% <100.00%> (+0.30%)
:arrow_up:

src/identifiers.ts
100.00% <100.00%> (ø)

src/kdfContext.ts
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 12c7782...cab2ded. Read the comment docs.


Write a JavaScript program to find gcd of two numbers

Description
Write a JavaScript program to find gcd of two numbers
GCD (Greatest Common Divisor) of two numbers is the largest number that divides both of them. A simple way to find GCD is to factorize both numbers and multiply common factors.
Input  : 12 18
Output : 6

How to contribute

Save the solution in program/FindGcdOfTwoNumbers.js file
Add FindGcdOfTwoNumbers.js file in find-gcd-of-two-numbers folder

!assign


Small fixes for prediction

Coverage decreased (-0.1%) to 73.143% when pulling c668307f3e48b34281f9d2e643327b6a9c6e17e2 on dev into a8d4c8295a4d32498d807dc64972cf20a8389ad5 on master.


two devices different display

Update from 2.1.5 to 2.1.8

One device switched to this display Firefoy and Google Chrome

Microsoft Edge

The browser cache needs to be cleared.  It is not picking up the right stylesheet.

Sorry, realised after opening this issue. That was the reason closing it immediately.
Dont know how to delete a wrong issue


Question: Support of pls/m3u low bit rate?

I am thinking about making a Discord bot.
Does it support mpga stream in mono, 8000Hz, 8kb/s?
Example: https://www.liveatc.net/play/klsv.pls
If not, is that planned?

I am unable to find anything that can play that.


Can not search files in subfolder, why?

What's the Problem?
as title.
Solution/Idea
Let users can do this.
Alternatives
None
Priorities

Capability
Priority

This proposal will allow developers to accomplish W
Must

This proposal will allow end users to accomplish X
Should

This proposal will allow developers to accomplish Y
Could

This proposal will allow end users to accomplish Z
Won't

Files Version
No response
Windows Version
No response
Comments
No response

Please edit the issue to fill the required fields.

Files version?
Windows version?
Where are you searching? Local disk? Network drive? Is the folder indexed in windows search? Is it hidden?


Fix admin settings save

Needs a fix to the core admin package to really work.  I'll fix that next.

LGTM

Closing this as we've moved to use an existing package for configuration rather than handling it in meanio code


Encoding adds a BOM but default does not.

The documentation implies a BOM but doesn't directly speak of it. I was using WriteLinesToFile with UTF8 Encoding and old Visual Studio RC compiler would explode on the file. I didn't realize the BOM at the beginning was being written right away. Removing encoding all together fixed it. I think this is very important to note in the encoding documentation.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ee06fdb3-143d-fa36-54ee-5f9af813615e
Version Independent ID: 5739dfe6-6a88-1487-4f29-1b91502ec7ad
Content: WriteLinesToFile Task - MSBuild
Content Source: docs/msbuild/writelinestofile-task.md
Product: visual-studio-windows
Technology: msbuild
GitHub Login: @ghogen
Microsoft Alias: ghogen

@RevenantBob
It seems that Unicode encodings follow the Unicode standard and have a BOM, but encodings that aren't Unicode encodings don't. I didn't find a clear statement of this, although there's a note in the Encoding.GetPreamble page that gives a cautionary warning that says "most encodings" don't have BOM, but the Unicode encodings do.  I don't see this as an MSBuild documentation issue, as the behavior is more about the .NET Encoding class, and would show up in many different usage scenarios, other than MSBuild's WriteLinesToFile task.

@ghogen -- Gordon, thank you for clarifying.
I am closing this issue now.  You are welcome to @ mention me for any followup.  We hope to hear from you again.


Implement Shamir's Secret Sharing algorithm (cryptographic) in C++

🚀 Feature
An implementation of the cryptographic algorithm, Shamir's Secret Sharing (SSS) in C++, which allows one to generate a number of shares such that a secret is revealed only when a fixed subset of those shares are put together. See this Wikipedia article for more information.
Have you read the Contributing Guidelines on Pull Requests?
Yes, I have.
Motivation
Implementing SSS in C++ requires one to use cryptographically secure random numbers taken from a uniform distribution, support for which is natively available in C++ 11. Writing this implementation will allow the implementer to become familiar with data structures such as vectors and maps, in addition to learning about the mathematics behind this algorithm.
Pitch
An implementation of SSS can be used in situations where a cryptographic secret has to be protected by a group of people, without letting any particular individual know the secret. An example of such a case is that of an organization wishing to protect, let's say, a private key. The private key can be known by perhaps the head of that organization, but in case the head suddenly passes away, the organization has no means of recovering that private key (which might be in use for production/deployment purposes). Using SSS, the organization can distribute shares of that key among all of its high-ranking employees, such that any predefined subset of that group can come together (in case of a crisis) to reveal the secret. This way, no particular employee needs to know the secret, nor can he/she steal the secret for nefarious purposes without conspiring with all of the other required number of employees (a very unlikely situation, given the number is high enough).

I wish to make implement this for GSSOC 2021. Can this kindly be assigned to me?

Good work on the pitch!
Assigned :)

Good work on the pitch!
Assigned :)

Thanks :D
Pull request #2199 added.


What is the Licence

Hi, what is the licence on this software?
Many thanks, Matthew

it's MIT License


Debugger: Breakpoint List

One of the simple and powerful features of the C/SIDE debugger is the Debugger Breakpoint list, giving you:

an overview of all breakpoints
allowing to manage your breakpoints

This is more powerful than the options in VSCode En/Disable All Breakpoints in VSCode.
Is this already on the backlog? If not consider it a request right now. ;-)

Haha, probably need better glasses. It seems that I have actually always overseen the breakpoints section in the Debug View of VSCode. Never to blind to learn. $-)


Improve decompilation related to stack

There is no explicit stack pointer for eBPF. Stack access works relative to the R10 register, which serves as the frame pointer for each function and is read-only. It is possible to pass stack addresses as arguments to functions however.
The solana eBPF vm implementation uses a new stack frame with a size of 0x1000 bytes for each function call.
Since the architecture is purely virtual, the return address doesn't get pushed to the stack explicitly like most other architectures do it and the creation of new stack frames is implicit as well.
So ghidra can understand what is going on, I tried emulating these semantics by adding pcode to the call instruction that creates the stack frame for the callee and then saves the return address, as well as popping the frame and the return address in the exit instruction. I also declared this space as used by the callee in the calling convention (localrange). Since R10 for ghidra is denoted as the stack pointer, I believe it is also necessary to declare the stack pointer as growing into the positive direction, since generated code accesses [R10-0x10] as an example for local stack variables. However this led to weird behavior in the decompiler with huge arrays in the stack, so the stack is currently declared as growing into the negative direction and the stack frame creation is commented out.
Unfortunately the current decompiler output is not great either and even wrong for simple scenarios
The following code's main function compiled with clang test.c --target=bpf -c
int printf(const char *, ...);

int add(int a, int b) {
    return a + b;
}

struct SomeData {
    int a;
    int b;
    int c;
    int d;
    char buf[16];
};

int process_struct(struct SomeData* data) {
    data->a = 1;
    data->b = 2;
    data->c = 3;
    data->d = 4;
    memcpy(data->buf, "hello", 6);
    return 1337;
}

int main(int argc, char **argv) {
    int result = add(3, 5);

    struct SomeData data = { 0 };
    result += process_struct(&data);

    printf("%d\n", result);
    return result;
}

decompiles to
undefined8 main(void)

{
  undefined4 uVar1;
  int iVar2;
  undefined8 uVar3;
  BADSPACEBASE *in_R10;

  uVar1 = add(3,5);
  uVar3 = *(undefined8 *)((longlong)in_R10 + -0x40);
  *(undefined4 *)((longlong)in_R10 + -0x14) = uVar1;
  *(undefined8 *)((longlong)in_R10 + -0x20) = uVar3;
  *(undefined8 *)((longlong)in_R10 + -0x28) = uVar3;
  *(undefined8 *)((longlong)in_R10 + -0x30) = uVar3;
  *(undefined8 *)((longlong)in_R10 + -0x38) = uVar3;
  *(undefined8 *)((longlong)in_R10 + -0x1000) = 0x100190;
  iVar2 = process_struct((undefined *)((longlong)in_R10 + -0x38));
  *(int *)((longlong)in_R10 + -0x14) = (int)*(undefined8 *)((longlong)in_R10 + -0x14) + iVar2;
  *(undefined8 *)((longlong)in_R10 + -0x1000) = 0x1001c8;
  printf("%d\n",*(undefined8 *)((longlong)in_R10 + -0x14));
  return *(undefined8 *)((longlong)in_R10 + -0x14);
}

It doesn't catch the zero initialization, probably due to stack reuse from the calls and the in_R10 is problematic as well since it doesn't use regular stack variables.
Additionally it almost always shows the pushing of the return address in the decompilation.
test.zip

Hello @emteere 👋
I've seen that you previously replied to an issue on the project I forked regarding problems with the analysis and I was hoping you would have some idea on how I could solve mine.
Since this module is aimed at analyzing solana programs, inter function calls are actually allowed, which I believe is not the case with the eBPF used in the linux kernel and thus wasn't an issue with the original module.
You mentioned that it is possible to inject pcode at the start of each function, however I'm not sure how I would do that.

There are ways to have pcode injected at the start of your functions, but I don't think it is worth the complexity here. That might change depending on inter function calls.

I've looked up how pcode injection is done for the JVM processor module but from what I saw, they just inject pcode at the user defined operations in sleigh. Since there is no special function start opcode I'm not sure if this is the same mechanism you are referring to.
Of course if pcode injection is not needed, feel free to suggest alternatives. Maybe I did something wrong with the calling conventions or sleigh specs before.

After figuring out how to inject pcode at the function start it seems like that approach won't work either.
Since the injection is on the level of the pcode for the decompiler and is not visible in the listing view like the pcode generated by the sleigh spec, the stack analysis never ends up creating any local variables.
When I "inject" that same code by hooking some hardcoded sleigh operation to get the first instruction to also set up a stack frame, all of a sudden locals are created as expected.

Changing the stack growth to negative required converting R10 from the stack pointer to the frame pointer and introducing a dummy R11 stack pointer.
Additionally the stack and frame pointers are now declared as unaffected in the cspec file.
Both of these changes lead to reasonable decompiler output, although the listing still does not show the local variables as it would with regular pcode generated from sleigh.
New output (slightly modified sample)
longlong main(undefined4 param_1,undefined8 param_2)

{
  int iVar1;
  longlong lVar2;
  undefined8 uStack56;
  undefined8 uStack48;
  undefined8 uStack40;
  undefined8 uStack32;
  longlong lStack24;
  undefined8 uStack16;
  undefined4 uStack8;
  undefined4 uStack4;

  uStack4 = 0;
  uStack16 = param_2;
  uStack8 = param_1;
  iVar1 = add(3,5);
  lStack24 = (longlong)iVar1;
  uStack32 = 0;
  uStack40 = 0;
  uStack48 = 0;
  uStack56 = 0;
  iVar1 = process_struct(&uStack56);
  lStack24 = lStack24 + iVar1;
  lVar2 = zext_test(0x1e);
  lStack24 = lStack24 + lVar2;
  printf("%d\n",lStack24);
  return lStack24;
}


Build issues adding Stripe w/ Apple Pay to ESA Build project

I'm trying to add @stripe/stripe-react-native to our EAS Build enabled Expo project, but running into the following problem:
❌  error: Provisioning profile "*[expo] com.foo.bar AppStore 2021-07-21T16:00:00.000Z" doesn't support the merchant.foo.bar.applepay Merchant ID. (in target 'FooBar' from project 'FooBar')

❌  error: Provisioning profile "*[expo] com.foo.bar AppStore 2021-07-21T16:00:00.000Z" doesn't match the entitlements file's value for the com.apple.developer.in-app-payments entitlement. (in target 'FooBar' from project 'FooBar')

▸ ** ARCHIVE FAILED **

It seems to me that something failed during the capabilities sync or the provisioning profile generation 🤔 There are the steps that I followed:

Ran npm install @stripe/stripe-react-native
Added "plugins": [["@stripe/stripe-react-native", { "merchantIdentifier": "merchant.foo.bar.applepay" }]], to app.json
Ran eas build --platform ios

Do you want to log in to your Apple account? yes
Synced capabilities: Enabled: Apple Pay Payment Processing
Fetched Apple distribution certificates
Fetched Apple provisioning profiles
Provisioning profile (id: XXXXXXXXX) is no longer valid
Fetched Apple provisioning profiles
Provisioning Profile - ID: XXXXXXXXX
Would you like to reuse the original profile? no
Generate a new Apple Provisioning Profile? yes
Created Apple provisioning profile

Then the build fails with the above error.
I tried running the same thing again, and I noticed that it again says "Provisioning profile (id: XXXXXXXXX) is no longer valid" so I'm thinking that something maybe goes wrong during the generation of the new provisioning profile, even though it says that it succeeded 🤔
Will continue investigating tomorrow, am happy to answer any questions, and would appreciate any pointers!

Thanks for the issue report! Have you set up Apple Pay according to Stripe's docs? Namely, Register for an Apple Merchant ID and Create a new Apple Pay certificate

The auto capability feature currently does not support (a feature I call) "Capability IDs". These IDs are used for payments, app groups, and iCloud containers (each is prefixed with a certain string and must be unique).
Currently eas build will just enable/disable capabilities based on the entitlements file. Because we aren't registering merchant IDs, then linking them to the bundle identifier capabilities, the provisioning profile doesn't match the entitlements, which results in a build crash.
One way around this is to go to https://developer.apple.com/account/resources/identifiers/list and configure the bundle ID manually, or to do the same in Xcode.
I've been kicking around the idea of automatically registering and linking IDs, but it has two blockers:

What if the user mistyped their merchant ID and we accidentally register it, would this interaction be undesirable?
The capability ID API is not currently supported by App Store Connect tokens, which we plan to add soon for CI automation. This would mean that users would have a different experience from the local CLI than they would from a cloud variation.

Regardless, I can work on a PR just so we can feel out if it makes sense or not. Sorry for the inconvenience.

The problem was indeed that there the merchant id was not added to the Apple Pay capability:

@EvanBacon thank you for the quick implementation! 😍 Will try it out now, and also post some more thoughts that I have to that PR


tf: make requests a bit more leniant

We have seen substantial flakes recently. These are partially due to
loaded systems (for example, we have seen issues where XDS takes >20s to
update. This is not a bug, Envoy is just slow (likely CPU overloaded)).
Other legitimate bugs don't typically recover at all, so I don't think
we will ignore many legitimate issues (other than
https://github.com/istio/istio/issues/38982, which we already know about
and cannot do much about).
This bumps the timeout a big, increases retry interval a bit as well to
reduce load, and reduces the total requests sent. 3 should still be
sufficient to get cross-X load balancing, as we send requests*clusters
already so we have 9 requests.
Please provide a description of this PR:

@howardjohn: 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

release-notes_istio
e993599c610456f38097849f6043d8320c1a60af
link
true
/test release-notes_istio

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

/retest


Prepare for v0.3.0 release

Fixes #213.
This PR preps the gems in our current repo for release. It has updates to the various README and version files in the repo and the client-server example.
For already released gems, I bumped the version to v0.3.0. For our currently unreleased instrumentation adapters, I set the versions as v0.1.0. I also updated the gemspecs to depend on ~>0.3.0 of the API package. I'm not positive about my choices for versioning, so let me know if any of that should change.

I'd be inclined to bump all the versions to 0.3.0 and skip 0.1.0 for new instrumentation. We don't have a clear story for version compatibility yet, and rather than clarify that now, it's easier to have all the gems at the same version.


Update gateway-api to release version

Please provide a description of this PR:
The go.mod was using a specific sha for the gateway-api. Change to the specific release.

Once https://github.com/istio/istio/pull/46061 merges, we can reset to that commit, which will update the version to 0.7.1 instead of the pre-release sha.

@ericvn: 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

integ-pilot-istiodremote_istio
e6b70386c7fa602df1fca1f56f71c4a658f26974
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.

@ericvn: 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
e6b70386c7fa602df1fca1f56f71c4a658f26974
link
true
/test integ-pilot-istiodremote

integ-ambient_istio
e6b70386c7fa602df1fca1f56f71c4a658f26974
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.

@ericvn: 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
e6b70386c7fa602df1fca1f56f71c4a658f26974
link
true
/test integ-pilot-istiodremote

integ-ambient_istio
e6b70386c7fa602df1fca1f56f71c4a658f26974
link
true
/test integ-ambient

integ-pilot-multicluster_istio
e6b70386c7fa602df1fca1f56f71c4a658f26974
link
true
/test integ-pilot-multicluster

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.

Closing for now.


[Suggestion] Add NPC command

Can you bring command adding support for NPCs? the command execution features of most npc plugins like citizens are very bad.

hCore is plugin for working with npcs hCore is multi-functional developer tool for spigot developers.
there is no need to add this command, this lib proivides alot of cool features only for devs. citizens is a library which allows you to create npcs with commands, and it has api which allows do the same things what can commands.
how bout other plugins, not only citizens?

That's right, hCore is not an plugin, it's an tool for spigot developers. Also If you are a developer, you can use .whenClicked() method to run a command.

More than 200 people are using npc on my server at the same time, so I asked if you could add a more optimized npc-command system because when I use any npc-plugin, the plugin always consumes high cpu if you can add a command system to hCore, I can develop it from this api.

just do itself. as i said, hCore isnt plugin for working with npcs.
also, command system already exists in hCore
click here


Error when sorting collection

Query
Product::search($request->get("query"))->orderBy('price', 'asc')->paginate(10);
Screenshot

This is actually due to a limitation in scout. The scout builder class that this driver receives an instance of does not include any support for specifying ORDER BY statements.
Scout will need to be updated before this can be supported. As a work around you can use the Collection sortBy method (https://laravel.com/docs/5.3/collections#method-sortby), though it will break pagination.

Thank you. Is there any plan to release this package without laravel scout only laravel mysql fulltext search package


[Feature] --version ?

Description
I need to know which version of spleeter is installed
for this, I would use spleeter --version but I can't find this information anywhere.
Does this feature exist?
Thanks

I would be wiling to help with this feature if it does not exist!

I would be wiling to help with this feature if it does not exist!

Hi @martinratinaud
you can run a plain pip freeze | grep spleeter

Hi @martinratinaud
you can run a plain pip freeze | grep spleeter

Thank you very much @mmoussallam

Thank you very much @mmoussallam


Setup code coverage

Feature description
If the software is not covered by tests, it's broken. In order to see how well cash is covered by tests, code coverage should be set up.
This request is not about "100% code coverage". It is about "how well is cash covered by test". Me and folks out there would like to see a number. Is it 10%? 50%? 80%?
It should be relatively easy to set up code coverage reporting with karma: https://github.com/karma-runner/karma-coverage
Feature motivation
Trivial things are getting broken: https://github.com/kenwheeler/cash/issues/320 There should be a representation of which methods are covered by tests and which aren't.

I personally use coveralls.io and I can recommend it for usage.

There should be a representation of which methods are covered by tests and which aren't.

All methods should have at least a test associated with them I think.
PR welcome for getting some coverage reports.

I think a more useful feature would be to be able to run Cash's test suite with jQuery.

There should be a representation of which methods are covered by tests and which aren't.

All methods should have at least a test associated with them I think.
PR welcome for getting some coverage reports.

PR is coming :rocket:
The code coverage is 96.33% which is great!

I think a more useful feature would be to be able to run Cash's test suite with jQuery.

Done.

Amazing! I know that you don't like badges in README, but this one would be good to have:

For some people (including myself) that would be one of the signs of a properly made software which is safe to use in production.

For some people (including myself) that would be one of the signs of a properly made software which is safe to use in production.

🤔 Yeah but I prefer to keep the readme cleaner. Also I don't really think there are many users we could swing over to Cash just by adding badges.
Ps. we are at ~100% now.

I think a more useful feature would be to be able to run Cash's test suite with jQuery.

I'm finding quite a few bugs this way 🤔


How do you generate depth map on metricd3D?

Which model did you use? Did you make any changes to its parameters?I look forward to your answer in your spare time.

I am using the giant2 version of metric3dV1, the download link is in the huggingface. I suggest you check the user manual for metric3D on the official website for specific reasoning methods.
I have also tried other versions of metric3dV2, but the results have not improved, and even some scenes have larger errors. I hope you can solve this problem in your future exploration.


tls_client_versions_minmax: update for OpenSSL 3.0

Update the cipher_suite for tls_client_versions_minmax.test.py so that it runs fine with OpenSSL 3.0.
With this change, thanks to @midchildan's https://github.com/apache/trafficserver/pull/9753 patch, I believe all autests will run with OpenSSL 3.0.

[approve ci autest rocky]

[approve ci autest]

[approve ci autest]

[approve ci autest]

[approve ci autest]


ddev get as a post_install_actions: that has a prompt halts with not output

Is there an existing issue for this?

[X] I have searched the existing issues

Output of ddev debug test
No response
Expected Behavior
I am setting up an add-on, that as part as its post_install_actions: it calls ddev get to get additional add-ons one of which prompts the user for something.
I looked at the code and realized that HostCommand() basically has to wait until the command finishes to show the output.
I also now understand why you did it the way you did it on https://github.com/ddev/ddev-platformsh/blob/main/install.yaml, as two different actions, one that echo's the prompt and a separate one that reads the prompt.
Actual Behavior
I would like to be able to do this, have ddev get do something that prompts for something on the post_install_actions:. I know I can do a similar thing, but if the prompt comes from the command that's executed, it just doesn't work as expected.
I don't think there's an easy fix here unless we do some real-time outputting of the output (similar to the docker compose build) so that one can see the output right away, and not when the command finishes.
Steps To Reproduce
Just create an add-on that has a

ddev get ddev/ddev-platformsh as a post_install_actions: and try adding that parent one.

Anything else?
No response

Better would be:

https://github.com/ddev/ddev/issues/5337


Handle keyboard interrupts better

Currently we have to spam control+c when running the module directly in order to stop it. We should improve this as time permits.
(venv) wlanpi@wlanpi-emmc-513-waves:[~/dev/wlanpi-chat-bot]: sudo venv/bin/python3 -m chatbot
INFO:TelegramAlert:We were offline, but we're back online.
^C^C

^C^C^CProcess Process-12:
Traceback (most recent call last):
  File "/usr/lib/python3.7/multiprocessing/process.py", line 285, in _bootstrap
    util._close_stdin()
  File "/usr/lib/python3.7/multiprocessing/util.py", line 387, in _close_stdin
    sys.stdin = open(fd, closefd=False)
  File "/usr/lib/python3.7/_bootlocale.py", line 33, in getpreferredencoding
    def getpreferredencoding(do_setlocale=True):
KeyboardInterrupt
^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C

Not sure if it helps, but Ctrl-Z seems to work OK during my testing.

Thanks, that seems to work better. So, it looks like the code handles SIGTSTP (Ctrl-Z) better than SIGINT (Ctrl-C).

This doesn't seem to be the same thing. Ctrl-Z puts the process in the background rather than stopping it. Use fg to resume:
(venv) wlanpi@wlanpi-emmc-513-waves:[~/dev/wlanpi-chat-bot]: fg
sudo venv/bin/python3 -m chatbot
ERROR:TelegramAlert:Other error occurred: ('Connection aborted.', OSError(0, 'Error'))

Fixed by 7c332d8b95b8037065ed202984587f397d9054d7. Thank you Nigel for working on this.


⚠ Bofrost.at has degraded performance

In c40ff37, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2193 ms

Resolved: Bofrost.at performance has improved in bbb660b after 6 minutes.


Deterministic output for end users

https://github.com/stympy/faker/pull/207
https://github.com/factory-helper/factory-helper/pull/32

@owiber

Nice! Thanks!

@haeky


is there a way to repeat elements in patterns

Hello, is there a way to write a pattern that transforms [ f(1), f(2), .... any  number of f(integer) ] into map(f, [ 1, 2, any number of integers ]) ?
If I understand correctly tree sitter queries support wildcards such as *.

It will be a good improvement to add this! And the implementation should be trivial as treesitter already has repetitions.
However I don't have a good design for the syntax yet.

[ f($a), ...], i.e. use ... to repeat same level node?
[ f($a)+ ], i.e. Rust declarative macro like syntax?
ast-grep uses $$$

I think the rust macro syntax is nice because it also solves the problem of the syntax of the replacement part.

nice!


Git commit message box in SCM view uses native scrollbar

Issue Type: Bug
Entering a message that is tall enough (e.g. which makes enough lines to trigger the scrollbar) shows the native scrollbar of the OS.
I'm on Windows using a dark theme and the native white scrollbar made me go blind for few minutes.

Jokes aside, I really think there should be a custom scrollbar there to make it consistent with every other UIs there is in VSCode.
This is also present on the Insiders version as I'm writing this issue.
VS Code version: Code 1.26.1 (493869ee8e8a846b0855873886fc79d480d342de, 2018-08-16T18:38:57.434Z)
OS version: Windows_NT x64 6.1.7601

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz (4 x 2294)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
7.88GB (1.04GB free)

Process Argv
C:\Program Files\Microsoft VS Code\Code.exe

Screen Reader
no

VM
0%

Extensions (41)

Extension
Author (truncated)
Version

better-comments
aar
1.2.6

Bookmarks
ale
9.0.3

project-manager
ale
8.0.0

copy-relative-path
ale
0.0.2

gitignore
cod
0.5.0

bracket-pair-colorizer
Coe
1.0.59

vscode-markdownlint
Dav
0.20.0

vscode-quick-select
dba
0.2.6

vscode-faker
dee
1.3.0

githistory
don
0.4.2

xml
Dot
2.3.2

gitlens
eam
8.5.6

EditorConfig
Edi
0.12.4

docblocker
fly
0.4.0

auto-close-tag
for
0.5.6

auto-rename-tag
for
0.0.15

vscode-auto-open-markdown-preview
hnw
0.0.4

output-colorizer
IBM
0.1.2

XMLLanguageSupport
IBM
0.0.1

autofilename
Jer
0.1.3

vscode-random
jre
1.3.2

vscode-github
Kni
0.30.0

expand-region
let
0.1.2

vs-color-picker
lih
0.7.0

dotenv
mik
1.0.1

vscode-todo-parser
min
1.9.1

vscode-duplicate
mrm
1.2.1

color-highlight
nau
2.3.0

snippet-creator
nik
0.0.4

material-icon-theme
PKi
3.5.3

view-in-browser
qin
0.0.5

java
red
0.29.0

vscode-icons
rob
7.25.0

code-settings-sync
Sha
3.0.0

selectline-statusbar
tom
0.0.2

vscode-input-sequence
tom
0.2.0

vscode-java-debug
vsc
0.11.0

vscode-maven
vsc
0.10.0

vscode-todo-highlight
way
1.0.4

better-align
wwm
1.1.6

markdown-all-in-one
yzh
1.6.0

(2 theme extensions excluded)

Makes sense!

@joaomoreno Sure, I don't mind looking into this, but I never really touched typescript and would prefer if I had some pointers to existing code to base myself on. Can you give me a link to one of those examples you are talking about?

This guy here, check his usages: https://github.com/Microsoft/vscode/blob/master/src/vs/base/browser/ui/scrollbar/scrollableElement.ts#L477

@joaomoreno Awesome, thanks, I'll take a look!


Review Ticket Overview

Review Ticket Guide
Each assignment we will be required to make a review ticket. Most assignments provided will have a Hacks section. A Hack is a term for coding, a fun term.

Screen Captures are nice for Hacks
Short Descriptions
Code Fragments

Markdown Samples
Using markdown from Index.md. We are learning markdown.

This text below is something called Markdown. This is a heading, inside of code scaffolding

## Investing in Your Technical Future

This is emphasis

> Explore the Computer Science Pathway at Del Norte High School and invest in your technical skills. All Del Norte CompSci classes are designed to provide a real-world development experience. Class time includes tech talks (lectures), peer collaboration, communication with teachers, critical thinking while coding, and creativity in projects. Grading is focused on time invested, participation with peers, and engagement in learning.

Sample of bullets

- Introduction to concepts and requirements by the teacher
- Project-based learning with teacher support, performing Agile/Scrum development
- Coding, frontend, backend, devops, version control and algorithmic thinking
- Creativity, research, design, data structures, and utilizing ChatGPT
- Performing team work, team communication and collaboration, peer reviews/grading
- Focus on tehnical communications through project presentations and student led teaching
- Grades are on projects, learnt concepts, and live reviews between student(s) and teacher


Issues: The right way to do prepared statements

To properly do prepared statements
Overload CreateCommand(string cmdText, Dictionary<string, object> args)

Issuse #89

Thank you!


Fix middleware flow on false origin

I was experiencing an issue with my middleware chain exiting early when I returned false from a custom origin function in the cors middleware. This fixed it for me.

Duplicate with #22
Suggest to close this pull request.

Ah, yeah good catch, my bad.
Btw, @evert0n do you have any plans on updating and republishing this module?


Firefox processes blocks reinstall Puppeteer

Steps to reproduce
Tell us about your environment:

Puppeteer version: 5.2.1
Platform / OS version: Win 10 x64 (build 2004)
URLs (if applicable):
Node.js version: 14.4.0

What steps will reproduce the problem?
Please include code that reproduces the issue.

Install Puppeteer with FF (81.0a1)
Run script https://gist.github.com/inoyakaigor/19ae0eeabf93fbfc04c368ffa17b6efa
Then I got an error Evaluation failed: call to Function() blocked by CSP
Uninstall puppeteer and install it with Chromium

What is the expected result?
Install succefull
What happens instead?
Got an error Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): EBUSY: resource busy or locked, rmdir '_my_project_path_\node_modules\puppeteer\.local-firefox\win64-81.0a1\firefox'
npm ERR! code EPERM
npm ERR! syscall rename
npm ERR! path _my_project_path_\node_modules\puppeteer
npm ERR! dest _my_project_path_\node_modules\.puppeteer.DELETE
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, rename '_my_project_path_\node_modules\puppeteer' -> '_my_project_path_\node_modules\.puppeteer.DELETE'

It is happens because firefox processes for each run is not shutdown:

Thank you for reporting. We're investigating a number of issues with Puppeteer's Firefox launcher on Windows.

@inoyakaigor Can you still reproduce the issue if you add -wait-for-browser to the arguments passed to Firefox? As in:
 await puppeteer.launch({ product:'firefox', args: ['-wait-for-browser']}

@mjzffr Yes I can. I recorded a video showing what's going on https://www.youtube.com/watch?v=somgzTbCMlc
Forgot to mention: when I get an error about CSP I press ctrl+с to stop process.
Also now I think that main problem in the Firefox: if you pay attention to tree of Firefox processes in the video you can see that root process shutdowns correctly but child processes is not.

Thanks for checking. I'll track a fix for this over in https://bugzilla.mozilla.org/show_bug.cgi?id=1656962

This should no longer be an issue with a recent Firefox Nightly build. @inoyakaigor could you please verify that? Thanks a lot!

I'm closing the issue for now, but happy to reopen if that is still a problem.

@whimboo yeah, will check it little bit later

@whimboo I can't check because I get another one link. But even this error whole firefox processes tree ends correctly at least.

That's great to hear. Thanks a lot for checking.


test: add tests for most used admin transactions

Description
Closes https://github.com/zeta-chain/node/issues/2448
How Has This Been Tested?

[ ] Tested CCTX in localnet
[ ] Tested in development environment
[ ] Go unit tests
[ ] Go integration tests
[ ] Tested via GitHub Actions

Summary by CodeRabbit

New Features

Introduced the ability to track inbound transactions via gRPC, enhancing monitoring capabilities.

Seems like we need to run make generate


Normal File Search in New Setting UX Does not Expand Sections

Testing out the new settings UX, normal file searches commandf correctly find the location of strings in the default settings file but do not expand the section the result is found in:

Maybe we should give focus to the new search box instead of opening the find widget on Ctrl+F?

@chrmarti Yes, I would be disabling the find widget in this editor.

Disabled Find 6093e46dfe62c7ecff96453d4dba719102226960


PRQL support

This PR adds support for PRQL.
It does this by replacing sanitizeQuery with preprocessQuery. Preprocess first compiles PRQL (with prql-compiler as WASM module) and also sanitizes the SQL. The only practical difference is that preprocessQuery may throw errors that need to be passed to the model.
I tried to make this PR as encapsulated as possible so it is easier to maintain.

As discussed with @hamilton on zoom, we should take another look at this in a few weeks when the Rill backend refactor is complete


Perform first pull request to Pipeliner

Background
Pipeliner source code should be updated with changes introduced in Software Factory.
Task description

[ ] Define change scope.
[ ] Push pull request.
[ ] Make sure that the pull request is buildable and meet all criterias, so it can be approved.
[ ] Merge.

Acceptance criteria
Pull request with source code delta from Software Factory is merged.
Acting on Behalf of MBition GmbH
https://github.com/Daimler/daimler-foss/blob/master/LEGAL_IMPRINT.md

Looks good to me too :)


waitOnNormalExit debugOption missing / not working

Environment data

VS Code version: 1.28.0
Extension version (available under the Extensions sidebar): 2018.9.0
OS and version: Windows 7
Python version (& distribution if applicable, e.g. Anaconda): 2.7.15
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Relevant/affected Python packages and their versions: N/A

Actual behavior
Running debugger does not wait on exit and instantly closes after the file finishes running.
Expected  behavior
Debugger would wait on exit so that debug console could be used to evaluate variables in the file that was previously run.
Steps to reproduce:

Create basic python script:
foo = True
bar = False

Do not use any breakpoints and run debugger

Attempt to evaluate print foo in the debug console

Console warns: "Please start a debug session to evaluate"

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
Starting Microsoft Python language server.

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)
log.ts:171   ERR Cannot read property 'sendRequest' of null: Error: Cannot read property 'sendRequest' of null
    at t.handleErrorResponse (file:///C:/Users/Alex/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:2606:480)
    at file:///C:/Users/Alex/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:2605:928
    at n.Class.derive._oncancel.then (file:///C:/Users/Alex/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:166:736)
    at t.send (file:///C:/Users/Alex/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:2605:859)
    at t.threads (file:///C:/Users/Alex/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:2603:565)
    at e.fetchThreads (file:///C:/Users/Alex/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:2969:99)
    at e.runner (file:///C:/Users/Alex/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:2970:209)
    at e.doRun (file:///C:/Users/Alex/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:205:434)
    at e.onTimeout (file:///C:/Users/Alex/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:205:391)
errors.ts:48 WARNING: Promise with no error callback:464
errors.ts:49 {exception: null, error: Error: Cannot read property 'sendRequest' of null
    at t.handleErrorResponse (file:///C:/Users/ab6…, promise: n.C…s.d…e.cancel, handler: undefined, id: 464, …}

Running debugger does not wait on exit and instantly closes after the file finishes running.

The setting is not necessary. The debug console and terminals are still visible after the debugger runs to completion. This was legacy code brought from VS used to ensure there terminal does not shut down and close, however that doesnt happen in VS Code.

They stay open but they are not populated with information and you cannot interact with anything via the console.  Is there not a setting to hold the debugger essentially with an implied break at the EOF?

Please put a breakpoint at line 5, then inspect the variables.

Please put a breakpoint at line 5, then inspect the variables.

I'm asking if there is a way to emulate that behavior without having to use the breakpoint, which prevents that last line from evaluating and being used in the debug tools.
It would be useful to be able to run an entire file without breakpoints but still be able to interact with it at the end.

I'm asking if there is a way to emulate that behavior without having to use the breakpoint, which prevents that last line from evaluating and being used in the debug tools.

No there isn't.

@MrAlexBailey the closest you might get is that python3 -i will launch the REPL at the end of execution, so you can introspect whatever you want that way.


#151785584 Users should be able to reset their password

What does this PR do?
Add reset password feature
Description of Task to be completed?
How should this be manually tested?
Any background context you want to provide?
What are the relevant pivotal tracker stories?
Screenshots (if appropriate)
Questions:

Coverage remained the same at 85.491% when pulling e50bfc848d8df76d74f292d83ca7286ac8491a50 on feature/151785584/implement-reset-password into 15cc0fb0212c65a9690d8641b8071fb4ac0ecb25 on develop.


Setuptools with entry-point

Hello,
I have a folder with several modules to setup. Each module has the same architecture:
-manager
-scripts

src
name of the module
tests
-setup.py
-MANIFEST.in
-front
-scripts
src
name of the module
tests
-setup.py
-MANIFEST.in

Inside my manager/setup.py, this is what I have:
setup(
    name="manager",
    version=FINAL_VERSION,
    packages=find_packages(exclude=['tests']),
    author='Me',
    author_email='my_email',
    description="my description ",
    include_package_data=True,
    data_files=[
        ('share/my_module/scripts', [
            'scripts/my_scripts',
        ])
    ],
    entry_points={
        'console_scripts': [
            'manager=src.manager.main:main',
            'manager-worker=src.manager.worker:main',
        ]
    },
    install_requires=[
        'setuptools',
        'circus==0.15.0',
        'futures==3.0.5',
        'ipython==5.8.0',
    ],
    tests_require=[
        'pytest==3.6.3'
    ],
    extras_require={
        'shell': ['ipython']
    },
)

It is nearly the same file for front module.
The issue that I have is when I try to launch one of my console-script, for example, manager. It is has if setuptools is trying to find the folder path in front module instead of manager.
Python used: 2.7
setuptools: 41.6.0
Thanks

Hi @Sebastiencreoff, thank you very much for reporting this problem.
I don't fully understand the error here... Would it be possible for you to provide the error logs (and maybe a simple git repository with code that replicates what you are trying to do, in a simplified way)?

Please also notice Python 2.7 is no longer supported.

Hi @Sebastiencreoff, I think I will go ahead and close this issue for now, but please let us know if you have any other information about the problem.


Invalid file type

The file extension of : https://github.com/the-moonLight0/Hactober-fest-2021/blob/089d4d6c5c8833ef8f11fc0686a61dc68b8262e5/infix to prefix
should be .java

please assign me this issue will correct it. thanks

PR has been raised. Please review. Thanks
Infix to prefix branch #54