[WIP] add e2e tests for mtls pass through filter chain

@yangminzhu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test lint_istio

gencheck_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test gencheck_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.

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

Test name
Commit
Details
Rerun command

lint_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test lint_istio

gencheck_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test gencheck_istio

integ-security-local-tests_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test integ-security-local-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.

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

Test name
Commit
Details
Rerun command

lint_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test lint_istio

gencheck_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test gencheck_istio

integ-security-local-tests_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test integ-security-local-tests_istio

integ-distroless-k8s-tests_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
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.

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

Test name
Commit
Details
Rerun command

lint_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test lint_istio

gencheck_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test gencheck_istio

integ-security-local-tests_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test integ-security-local-tests_istio

integ-distroless-k8s-tests_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
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.

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

Test name
Commit
Details
Rerun command

lint_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test lint_istio

gencheck_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test gencheck_istio

integ-security-local-tests_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test integ-security-local-tests_istio

integ-distroless-k8s-tests_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test integ-distroless-k8s-tests_istio

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

integ-security-k8s-tests_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
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.

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

Test name
Commit
Details
Rerun command

gencheck_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test gencheck_istio

integ-security-local-tests_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test integ-security-local-tests_istio

integ-distroless-k8s-tests_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test integ-distroless-k8s-tests_istio

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

integ-security-k8s-tests_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test integ-security-k8s-tests_istio

lint_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-local-tests_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test integ-security-local-tests_istio

integ-distroless-k8s-tests_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test integ-distroless-k8s-tests_istio

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

integ-security-k8s-tests_istio
d85339e457931caa3bd4b6729e6458f6f31fd532
link
/test integ-security-k8s-tests_istio

lint_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test lint_istio

gencheck_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test gencheck_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.

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

Test name
Commit
Details
Rerun command

lint_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test lint_istio

gencheck_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test gencheck_istio

integ-security-k8s-tests_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
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.

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

Test name
Commit
Details
Rerun command

gencheck_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test gencheck_istio

integ-security-k8s-tests_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test integ-security-k8s-tests_istio

lint_istio
8d967026f13e5df3943b7c4cf74e2f602470b079
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test integ-security-k8s-tests_istio

lint_istio
8d967026f13e5df3943b7c4cf74e2f602470b079
link
/test lint_istio

integ-istioio-k8s-tests_istio
8d967026f13e5df3943b7c4cf74e2f602470b079
link
/test integ-istioio-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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-k8s-tests_istio

integ-pilot-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-local-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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-k8s-tests_istio

integ-pilot-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-local-tests_istio

release-test_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test release-test_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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-k8s-tests_istio

integ-pilot-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-local-tests_istio

release-test_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test release-test_istio

unit-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-k8s-tests_istio

integ-pilot-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-local-tests_istio

release-test_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test release-test_istio

unit-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test unit-tests_istio

integ-istioio-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-istioio-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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-k8s-tests_istio

integ-pilot-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-local-tests_istio

release-test_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test release-test_istio

unit-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test unit-tests_istio

integ-istioio-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-istioio-k8s-tests_istio

integ-mixer-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-mixer-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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-k8s-tests_istio

integ-pilot-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-local-tests_istio

release-test_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test release-test_istio

unit-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test unit-tests_istio

integ-istioio-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-istioio-k8s-tests_istio

integ-mixer-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-mixer-k8s-tests_istio

integ-conformance-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-local-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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-k8s-tests_istio

integ-pilot-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-local-tests_istio

release-test_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test release-test_istio

unit-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test unit-tests_istio

integ-istioio-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-istioio-k8s-tests_istio

integ-mixer-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-mixer-k8s-tests_istio

integ-conformance-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-local-tests_istio

integ-distroless-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-k8s-tests_istio

integ-pilot-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-local-tests_istio

release-test_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test release-test_istio

unit-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test unit-tests_istio

integ-istioio-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-istioio-k8s-tests_istio

integ-mixer-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-mixer-k8s-tests_istio

integ-conformance-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-local-tests_istio

integ-distroless-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-k8s-tests_istio

integ-pilot-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-local-tests_istio

release-test_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test release-test_istio

unit-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test unit-tests_istio

integ-istioio-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-istioio-k8s-tests_istio

integ-mixer-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-mixer-k8s-tests_istio

integ-conformance-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-local-tests_istio

integ-distroless-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-security-local-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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-k8s-tests_istio

integ-pilot-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-local-tests_istio

release-test_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test release-test_istio

unit-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test unit-tests_istio

integ-istioio-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-istioio-k8s-tests_istio

integ-mixer-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-mixer-k8s-tests_istio

integ-conformance-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-local-tests_istio

integ-distroless-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-security-local-tests_istio

integ-galley-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-galley-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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-k8s-tests_istio

integ-pilot-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-local-tests_istio

release-test_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test release-test_istio

unit-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test unit-tests_istio

integ-istioio-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-istioio-k8s-tests_istio

integ-mixer-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-mixer-k8s-tests_istio

integ-conformance-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-local-tests_istio

integ-distroless-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-security-local-tests_istio

integ-galley-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-galley-k8s-tests_istio

integ-galley-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-galley-local-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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-k8s-tests_istio

integ-pilot-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-local-tests_istio

release-test_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test release-test_istio

unit-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test unit-tests_istio

integ-istioio-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-istioio-k8s-tests_istio

integ-mixer-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-mixer-k8s-tests_istio

integ-conformance-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-local-tests_istio

integ-distroless-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-security-local-tests_istio

integ-galley-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-galley-k8s-tests_istio

integ-galley-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-galley-local-tests_istio

e2e-dashboard_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test e2e-dashboard_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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-k8s-tests_istio

integ-pilot-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-local-tests_istio

release-test_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test release-test_istio

unit-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test unit-tests_istio

integ-istioio-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-istioio-k8s-tests_istio

integ-mixer-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-mixer-k8s-tests_istio

integ-conformance-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-local-tests_istio

integ-distroless-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-security-local-tests_istio

integ-galley-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-galley-k8s-tests_istio

integ-galley-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-galley-local-tests_istio

e2e-dashboard_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test e2e-dashboard_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-k8s-tests_istio

integ-pilot-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-local-tests_istio

release-test_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test release-test_istio

unit-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test unit-tests_istio

integ-istioio-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-istioio-k8s-tests_istio

integ-mixer-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-mixer-k8s-tests_istio

integ-conformance-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-local-tests_istio

integ-distroless-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-security-local-tests_istio

integ-galley-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-galley-k8s-tests_istio

integ-galley-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-galley-local-tests_istio

e2e-dashboard_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test e2e-dashboard_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-mixer-no_auth_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test e2e-mixer-no_auth_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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-k8s-tests_istio

integ-pilot-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-local-tests_istio

release-test_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test release-test_istio

unit-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test unit-tests_istio

integ-istioio-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-istioio-k8s-tests_istio

integ-mixer-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-mixer-k8s-tests_istio

integ-conformance-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-local-tests_istio

integ-distroless-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-security-local-tests_istio

integ-galley-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-galley-k8s-tests_istio

integ-galley-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-galley-local-tests_istio

e2e-dashboard_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test e2e-dashboard_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-mixer-no_auth_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test e2e-mixer-no_auth_istio

pilot-multicluster-e2e_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test pilot-multicluster-e2e_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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-k8s-tests_istio

integ-pilot-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-local-tests_istio

release-test_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test release-test_istio

unit-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test unit-tests_istio

integ-istioio-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-istioio-k8s-tests_istio

integ-mixer-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-mixer-k8s-tests_istio

integ-conformance-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-local-tests_istio

integ-distroless-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-security-local-tests_istio

integ-galley-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-galley-k8s-tests_istio

integ-galley-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-galley-local-tests_istio

e2e-dashboard_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test e2e-dashboard_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-mixer-no_auth_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test e2e-mixer-no_auth_istio

pilot-multicluster-e2e_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test pilot-multicluster-e2e_istio

lint_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
196c56341c8114a57f8b96faf4bf6ac31c0d0dc3
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-k8s-tests_istio

integ-pilot-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-local-tests_istio

release-test_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test release-test_istio

unit-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test unit-tests_istio

integ-istioio-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-istioio-k8s-tests_istio

integ-mixer-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-mixer-k8s-tests_istio

integ-conformance-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-local-tests_istio

integ-distroless-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-security-local-tests_istio

integ-galley-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-galley-k8s-tests_istio

integ-galley-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-galley-local-tests_istio

e2e-dashboard_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test e2e-dashboard_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-mixer-no_auth_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test e2e-mixer-no_auth_istio

pilot-multicluster-e2e_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test pilot-multicluster-e2e_istio

lint_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test lint_istio

gencheck_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test gencheck_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.

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

Test name
Commit
Details
Rerun command

integ-conformance-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-k8s-tests_istio

integ-pilot-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-local-tests_istio

release-test_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test release-test_istio

unit-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test unit-tests_istio

integ-istioio-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-istioio-k8s-tests_istio

integ-mixer-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-mixer-k8s-tests_istio

integ-conformance-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-local-tests_istio

integ-distroless-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-security-local-tests_istio

integ-galley-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-galley-k8s-tests_istio

integ-galley-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-galley-local-tests_istio

e2e-dashboard_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test e2e-dashboard_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-mixer-no_auth_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test e2e-mixer-no_auth_istio

pilot-multicluster-e2e_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test pilot-multicluster-e2e_istio

lint_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test lint_istio

gencheck_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test gencheck_istio

integ-security-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
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.

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

Test name
Commit
Details
Rerun command

integ-conformance-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-k8s-tests_istio

integ-pilot-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-pilot-local-tests_istio

release-test_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test release-test_istio

unit-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test unit-tests_istio

integ-istioio-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-istioio-k8s-tests_istio

integ-mixer-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-mixer-k8s-tests_istio

integ-conformance-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-conformance-local-tests_istio

integ-distroless-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-security-local-tests_istio

integ-galley-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-galley-k8s-tests_istio

integ-galley-local-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-galley-local-tests_istio

e2e-dashboard_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test e2e-dashboard_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-mixer-no_auth_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test e2e-mixer-no_auth_istio

pilot-multicluster-e2e_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test pilot-multicluster-e2e_istio

lint_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test lint_istio

gencheck_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test gencheck_istio

integ-security-k8s-tests_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test integ-security-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
00bbbef90c159dbc3543bcad19e02048ffb68b97
link
/test pilot-e2e-envoyv2-v1alpha3_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.

@yangminzhu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
cc94fb6869c9c43a11877cfedfd92f1f2c6b0b60
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
cc94fb6869c9c43a11877cfedfd92f1f2c6b0b60
link
/test integ-security-k8s-tests_istio

gencheck_istio
386db9b7e41c243e1b8369be574cad5991e126fb
link
/test gencheck_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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
cc94fb6869c9c43a11877cfedfd92f1f2c6b0b60
link
/test integ-security-k8s-tests_istio

gencheck_istio
386db9b7e41c243e1b8369be574cad5991e126fb
link
/test gencheck_istio

lint_istio
386db9b7e41c243e1b8369be574cad5991e126fb
link
/test lint_istio

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

@howardjohn would you mind to review this PR? thanks. (cc @lambdai )

why do we need to add authN to the passthrough filter chain today when it was not necessary with the older model? what am I missing here?

@rshriram This is to align with the workload model. The new authN policy is workload-based and when it says enabling mTLS on a workload, all traffic to the workload (including the traffic through pass through filter chain) should also be required for mTLS. This is also to align with the same behavior in the new authorization policy.

I agree with @rshriram . Passthrough not matter inbound or outbound should be transparent. If auth or even telemetry is needed, we must declare a svc/port for it.

I agree with @rshriram . Passthrough not matter inbound or outbound should be transparent. If auth or even telemetry is needed, we must declare a svc/port for it.

It's bad. Our mTLS policy is now workload-based. It doesn't make sense to say the port is not protected by the policy if it's not claimed by any service.

we care the inbound passthrough because it would be a clear security hole
if it's not protected by the authN/Z policy.
We can't claim the beta policy secure for workload without having it
applied to the passthrough filter chain.
On Tue, Feb 11, 2020 at 21:29 Zhonghu Xu<EMAIL_ADDRESS>wrote:

I agree with @rshriram https://github.com/rshriram . Passthrough not
matter inbound or outbound should be transparent. If auth or even telemetry
is needed, we must declare a svc/port for it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/20969?email_source=notifications&email_token=AAQWO2CZI3TMFNFVKDHLV3DRCOCKVA5CNFSM4KRYGYMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELPPINI#issuecomment-585036853,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQWO2DBU52RIW65R6MOVN3RCOCKVANCNFSM4KRYGYMA
.

@yangminzhu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-galley-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-galley-local-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.

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

Test name
Commit
Details
Rerun command

integ-galley-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-local-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.

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

Test name
Commit
Details
Rerun command

integ-galley-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-local-tests_istio

integ-security-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-local-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.

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

Test name
Commit
Details
Rerun command

integ-galley-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-local-tests_istio

integ-security-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-local-tests_istio

unit-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
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.

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

Test name
Commit
Details
Rerun command

integ-galley-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-local-tests_istio

integ-security-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-local-tests_istio

unit-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test unit-tests_istio

integ-conformance-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-local-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.

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

Test name
Commit
Details
Rerun command

integ-galley-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-local-tests_istio

integ-security-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-local-tests_istio

unit-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test unit-tests_istio

integ-conformance-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-local-tests_istio

integ-mixer-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-mixer-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.

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

Test name
Commit
Details
Rerun command

integ-galley-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-local-tests_istio

integ-security-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-local-tests_istio

unit-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test unit-tests_istio

integ-conformance-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-local-tests_istio

integ-mixer-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-mixer-k8s-tests_istio

integ-conformance-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-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.

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

Test name
Commit
Details
Rerun command

integ-galley-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-local-tests_istio

integ-security-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-local-tests_istio

unit-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test unit-tests_istio

integ-conformance-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-local-tests_istio

integ-mixer-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-mixer-k8s-tests_istio

integ-conformance-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-k8s-tests_istio

integ-security-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
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.

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

Test name
Commit
Details
Rerun command

integ-galley-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-local-tests_istio

integ-security-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-local-tests_istio

unit-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test unit-tests_istio

integ-conformance-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-local-tests_istio

integ-mixer-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-mixer-k8s-tests_istio

integ-conformance-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-k8s-tests_istio

integ-security-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
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.

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

Test name
Commit
Details
Rerun command

integ-galley-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-local-tests_istio

integ-security-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-local-tests_istio

unit-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test unit-tests_istio

integ-conformance-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-local-tests_istio

integ-mixer-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-mixer-k8s-tests_istio

integ-conformance-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-k8s-tests_istio

integ-security-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-k8s-tests_istio

release-test_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test release-test_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.

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

Test name
Commit
Details
Rerun command

integ-galley-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-local-tests_istio

integ-security-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-local-tests_istio

unit-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test unit-tests_istio

integ-conformance-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-local-tests_istio

integ-mixer-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-mixer-k8s-tests_istio

integ-conformance-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-k8s-tests_istio

integ-security-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-k8s-tests_istio

release-test_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test release-test_istio

e2e-mixer-no_auth_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test e2e-mixer-no_auth_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.

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

Test name
Commit
Details
Rerun command

integ-galley-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-local-tests_istio

integ-security-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-local-tests_istio

unit-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test unit-tests_istio

integ-conformance-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-local-tests_istio

integ-mixer-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-mixer-k8s-tests_istio

integ-conformance-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-k8s-tests_istio

integ-security-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-k8s-tests_istio

release-test_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test release-test_istio

e2e-mixer-no_auth_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test e2e-mixer-no_auth_istio

integ-istioio-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-istioio-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.

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

Test name
Commit
Details
Rerun command

integ-galley-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-local-tests_istio

integ-security-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-local-tests_istio

unit-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test unit-tests_istio

integ-conformance-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-local-tests_istio

integ-mixer-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-mixer-k8s-tests_istio

integ-conformance-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-k8s-tests_istio

integ-security-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-k8s-tests_istio

release-test_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test release-test_istio

e2e-mixer-no_auth_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test e2e-mixer-no_auth_istio

integ-istioio-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-istioio-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
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.

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

Test name
Commit
Details
Rerun command

integ-galley-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-local-tests_istio

integ-security-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-local-tests_istio

unit-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test unit-tests_istio

integ-conformance-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-local-tests_istio

integ-mixer-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-mixer-k8s-tests_istio

integ-conformance-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-k8s-tests_istio

integ-security-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-k8s-tests_istio

release-test_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test release-test_istio

e2e-mixer-no_auth_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test e2e-mixer-no_auth_istio

integ-istioio-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-istioio-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-telemetry-k8s-tests_istio

integ-distroless-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
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.

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

Test name
Commit
Details
Rerun command

integ-galley-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-local-tests_istio

integ-security-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-local-tests_istio

unit-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test unit-tests_istio

integ-conformance-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-local-tests_istio

integ-mixer-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-mixer-k8s-tests_istio

integ-conformance-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-k8s-tests_istio

integ-security-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-k8s-tests_istio

release-test_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test release-test_istio

e2e-mixer-no_auth_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test e2e-mixer-no_auth_istio

integ-istioio-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-istioio-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-telemetry-k8s-tests_istio

integ-distroless-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-distroless-k8s-tests_istio

e2e-dashboard_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test e2e-dashboard_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.

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

Test name
Commit
Details
Rerun command

integ-galley-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-local-tests_istio

integ-security-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-local-tests_istio

unit-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test unit-tests_istio

integ-conformance-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-local-tests_istio

integ-mixer-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-mixer-k8s-tests_istio

integ-conformance-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-k8s-tests_istio

integ-security-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-k8s-tests_istio

release-test_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test release-test_istio

e2e-mixer-no_auth_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test e2e-mixer-no_auth_istio

integ-istioio-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-istioio-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-telemetry-k8s-tests_istio

integ-distroless-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-distroless-k8s-tests_istio

e2e-dashboard_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test e2e-dashboard_istio

lint_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

integ-galley-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-local-tests_istio

integ-security-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-local-tests_istio

unit-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test unit-tests_istio

integ-conformance-local-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-local-tests_istio

integ-mixer-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-mixer-k8s-tests_istio

integ-conformance-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-conformance-k8s-tests_istio

integ-security-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-pilot-k8s-tests_istio

release-test_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test release-test_istio

e2e-mixer-no_auth_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test e2e-mixer-no_auth_istio

integ-istioio-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-istioio-k8s-tests_istio

integ-distroless-k8s-tests_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test integ-distroless-k8s-tests_istio

e2e-dashboard_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test e2e-dashboard_istio

lint_istio
1607f81ebbebd6f01cd88138a821cd91089a63bc
link
/test lint_istio

integ-telemetry-k8s-tests_istio
28cc736b7a12a482deb0ac6f64314ad7e0d1f5db
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.

/test integ-telemetry-k8s-tests_istio

In response to a cherrypick label: #20969 failed to apply on top of branch "release-1.5":
Applying: add support to pass through filter chain for peer authN policy
Using index info to reconstruct a base tree...
M	pilot/pkg/networking/core/v1alpha3/listener_builder.go
M	pilot/pkg/networking/core/v1alpha3/listener_test.go
M	pilot/pkg/networking/plugin/authn/authentication.go
M	pilot/pkg/networking/plugin/authz/authorization.go
M	pilot/pkg/networking/plugin/plugin.go
M	pilot/pkg/security/authn/policy_applier.go
M	pilot/pkg/security/authn/v1alpha1/policy_applier.go
M	pilot/pkg/security/authn/v1beta1/policy_applier.go
Falling back to patching base and 3-way merge...
Auto-merging pilot/pkg/security/authn/v1beta1/policy_applier.go
Auto-merging pilot/pkg/security/authn/v1alpha1/policy_applier.go
Auto-merging pilot/pkg/security/authn/policy_applier.go
CONFLICT (content): Merge conflict in pilot/pkg/security/authn/policy_applier.go
Auto-merging pilot/pkg/networking/plugin/plugin.go
Auto-merging pilot/pkg/networking/plugin/authz/authorization.go
Auto-merging pilot/pkg/networking/plugin/authn/authentication.go
Auto-merging pilot/pkg/networking/core/v1alpha3/listener_test.go
Auto-merging pilot/pkg/networking/core/v1alpha3/listener_builder.go
error: Failed to merge in the changes.
Patch failed at 0002 add support to pass through filter chain for peer authN policy


Add trueCasePath option to resolve file when the platform is case sensitive filesystem

I suggest add a flag in options "trueCasePath" to take in mind the case sensitive and set by default as true. This is really usefull in many cases when the file to find is for example a NodeJS module, because depending of the platform you can make the mistake to use a case sensitive file and require it without the proper name.
I know someone could be think this...
Just fix that, using the right name when you notice getting an error when you check the module on
the platform that doesn't support this feature
But this chokidar could be used in a precompiled process as webpack or watchify (the most of cases) in a development environment where you can't notice of this behaviour.
Actually watchify is having this issue, when put a wrong name the require resolver get the module without any problem, but when the watchify try to watch the modified file it does't work because chokidar is watching a missing file.
The idea is if the flag is assigned as true use the module true-case-path and check the current file entry and the return value raising a warning to the stderr if doesn't match.
This could be really usefull to find that kind of errors and keep the module working properly.
I gonna put the PR as soon as posible, I hope your feedback!!

I think I understand the problem you're trying to solve and your suggestion, but I do not think a new option inside of chokidar is the right layer at which to address it. When there is a case-sensitivity concern on user input that is going to be fed into chokidar, you should first use true-case-path to resolve the user input into an exact path, and then pass that result into chokidar. No need for it to be a baked-in option.
Possibly makes sense to do it within watchify.


Switch to Jiffy for greatly improved JSON performance.

All changes have been tested, haven't experienced any problems, tests pass as well. (ofc the only change is s/Jason/Jiffy/)

Now that I revisit this several months later I'd be willing to reconsider if you can throw some benchmarks at me to show it's worthwhile.


Original repo for nyancat

Awesome work!
Just for the info, this is the original repo for the nyan cat touchbar project: https://github.com/avatsaev/touchbar_nyancat
the code and animation file of the repo mentioned in your README was copied  this repo

Hey! Thanks for your kind words.
This is fixed, sorry!


fix(4687): rest status codes

Description
[Describe what this change achieves]
Issues Resolved
#4687
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@Bukhtawar I have opened this PR to get your early feedback on the expected solution. I will be adding tests as well if needed soon.

@p1729 could you please share status of the progress here for this PR. PLease let us know if you need any help. Thanks

@p1729: Are you still working on this PR ?


Developer Certificate of Origin (DCO) RFC

An RFC proposing the use of the Developer Certificate of Origin (DCO) to guarantee the origin / legitimacy of contributions.
The document mostly uses the word "legitimacy", but we may want to simplify that to "origin".
Comments welcome.
Closes https://github.com/enarx/rfcs/issues/30
Signed-off-by: axelsimon<EMAIL_ADDRESS>

Alright, going to renumber this to 00001 so that name-bot is happy. @mbestavros, name-bot seems a rigid :wink:


bug: :set linebreak not working

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.9.2 Build type: Release LuaJIT 2.1.1692716794
Operating system/version
linux mint 21.2
Describe the bug
:set linebreak not working.
Steps To Reproduce

Install lazyvim as explained in docs
Open nvim
Create new file. Insert text longer than window size
Enter :set linebreak

Expected Behavior
Lines should get wrapped to fit window size.
Repro
No response

Do you have wrap enabled as well?

Don't know what that is, so don't know 🤷
It didn't require anything else without Lazyvim.

Oh OK, thanks alot!
I'll read more thoroughly.
Why does lazyvim disable it?

Sure, was just wondering if it's preference or that it interferes with something.


Reminder: Build "Remind" feature for bot.

As a user I want to be able to set reminders for posts I made or others made.
The reminder should include a due-time (hours/days/specific date) and be able to link to the post in question.

What do you mean by "Link to the post?"
I'm not 100% sure if this is in scope just yet, given that this bot will only ever be on one server. That said, it doesn't sound like it'd be too awful to implement - I'll knock it around the team channels.

I don't know if it's possible. But I was thinking a "link" similar to the mentions.
On the other hand just a copy of the message content + who said it and when would be enough.
I only opened this issue because it was recommended: https://imgur.com/zzEYwc3

remind

Yeah, that would be sufficient. Maybe add the option that a specific group could be reminded.

Alright, well we do have a bunch of stuff to do on our internal tracker, so we'll get around to that before your ticket if you prefer - just let us know if you plan on doing it yourself.
Also, may not want to allow these reminders to remind other people - don't want people using the bot to annoy others.


Change length from 2000 to 2048 for Identifier

Data Type Identifier changed in Part 1
(see https://github.com/admin-shell-io/aas-specs/issues/306)
from 2000 to 2024 characters

As this change also affects the Part 1 YAML: Will there be a fix for the JSON Schema with Part 1 V3.1.0?

As this change also affects the Part 1 YAML: Will there be a fix for the JSON Schema with Part 1 V3.1.0?

This is not a fix but a change (broader range) in data type "Identifier" (see https://github.com/admin-shell-io/aas-specs/issues/306) . Sure, this will be changed in JSON schema for V3.1 as well.
See https://aas-core-works.github.io/aas-core-meta/v3_1/index.html: https://aas-core-works.github.io/aas-core-meta/v3_1/Identifier.html  so all attributes with Type Identifier or inheriting from Type Identifier will be changed


Update assets.agi.com deprecation notice.

While we are extending the shut down date to October 1st, we also wanted to strengthen the message for any users that may still be using it.
If you want to test this, just create a terrain provider with http://assets.agi.com/stk-terrain/world

Thanks for the pull request @mramato!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

Thanks @mramato!


Package request: gnomeExtensions.trayIconsReloaded

Project description
<EMAIL_ADDRESS>is a tray extension for gnome 45.
Metadata

homepage URL: https://extensions.gnome.org/extension/2890/tray-icons-reloaded/
source URL: https://github.com/MartinPL/Tray-Icons-Reloaded
license: GPL3
platforms: unix, linux, darwin, ...

Add a :+1: reaction to issues you find important.

nixpkgs.dev/gnomeExtensions.tray-icons-reloaded


fix: Enable scanoss dependency checking during docker container build

Pull Request
Description
During scanoss package installation, unverified dependencies were not installed. This PR fixes that.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[x] CI system update

Testing
You can see result after next release
Test Configuration:

Java: v11
LPVS Release: v1.3.x

Checklist:

[x] My code follows the style guidelines of this project
[x] My code meets the required code coverage for lines (90% and above)
[x] My code meets the required code coverage for branches (80% and above)
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (28ef2d3) 90.90% compared to head (726e244) 90.90%.

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #388   +/-   ##
=========================================
  Coverage     90.90%   90.90%
  Complexity      486      486
=========================================
  Files            47       47
  Lines          1737     1737
  Branches        209      209
=========================================
  Hits           1579     1579
  Misses           94       94
  Partials         64       64

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


Language::SelectorSet tweaks

I wanted to access [:subject, :subject!] and was surprised to realize I couldn't.
This PR addresses that.
Commits are not directly related, but second one assumes first one. Let me know if I need to split them.

I have no objections.
We've changed a lot in #956, do those changes need to be repeated there as well?

No, I don't think so, rspec_keywords exposes those values.


Is it possible to use quantized model with vLLM?

Hello,
I tried to use https://huggingface.co/meetkai/functionary-small-v2.2-GGUF/tree/main the functionary-small-v2.2.q4_0.gguf with vLLM but it did not work. Is there a special maniplulation I need to do?
I tried:
pdm run python server_vllm.py  --model "meetkai/functionary-small-v2.2-GGUF" --served-model-name "functionary-small-v2.2.q4_0.gguf" --host <IP_ADDRESS>
and other variations but none worked;
There's an error
OSError: meetkai/functionary-small-v2.2-GGUF does not appear to have a file named config.json. Checkout 'https://huggingface.co/meetkai/functionary-small-v2.2-GGUF/main' for available files.

Is it something that is possible?

Hi, unfortunately, vLLM does not work with GGUF models as of now. You should use llama.cpp to perform inference on the functionary GGUF models. We have recently integrated functionary models directly into llama-cpp-python. Here's how you can use it.

I've converted medium to AWQ https://huggingface.co/luccazen/functionary-medium-v2.2-awq
just use with the vllm script using --quantization awq

Thank you @themrzmaster for pointing this out. We are also considering to release AWQ weights as part of future releases currently, starting from the latest v2.4 here.
Anyway, I will be closing this issue now. Feel free to reopen if you have questions.

Thank you @themrzmaster for pointing this out. We are also considering to release AWQ weights as part of future releases currently, starting from the latest v2.4 here.
Anyway, I will be closing this issue now. Feel free to reopen if you have questions.

Wow amazing, thank you for the heads up :)


Use owners with data.aws_ami.info

The latest terraform-aws-provider appears to require this, so let's
humor it, and either supply it in case we're using the default AMI, or
allow the user to provide it.

Wooo- you fixed this about the exact same time I opened #35 :)
Thanks!


LLVM[8-11] Removal Progress Tracker

LLVM8

https://github.com/NixOS/nixpkgs/pull/283551

Issues

Modification for windows is just a best guess with no test. https://github.com/NixOS/nixpkgs/pull/283551/commits/56504908440cf45db6d32f70eaec341c983e3d68
probably ready for removal

LLVM9

https://github.com/NixOS/nixpkgs/pull/283653
https://github.com/NixOS/nixpkgs/pull/283767
https://github.com/NixOS/nixpkgs/pull/283989

Issues
cling

cling can build updated interpreter but requires copying c/c++ header files. unclear what version to use to update the package as it also needs to interface with xeus-cling which claims to support for >= 0.9 but less than < 0.10 (1.0)
xeus-cling a jupyter kernel and the only consumer of cling

haskell

haskell code contains one heavily used  llvm_9 reference  https://github.com/NixOS/nixpkgs/blob/e49dc530ba25ba507f0ded60c8f29cbc1e2570a9/pkgs/development/haskell-modules/configuration-nix.nix#L496

LLVM10

https://github.com/NixOS/nixpkgs/pull/283678
https://github.com/NixOS/nixpkgs/pull/283681
https://github.com/NixOS/nixpkgs/pull/283685
https://github.com/NixOS/nixpkgs/pull/283824
https://github.com/NixOS/nixpkgs/pull/283863
https://github.com/NixOS/nixpkgs/pull/283913

Issues

ready for removal

LLVM11

https://github.com/NixOS/nixpkgs/pull/283591

Issue

terra update https://github.com/NixOS/nixpkgs/pull/283591/commits/07f84374a23d58d119f13bfc198728f7f9d3f058 disables support for aarch64 due to a bug https://github.com/NixOS/nixpkgs/pull/283591#issuecomment-1908992327.
https://github.com/NixOS/nixpkgs/pull/283591/commits/71aa397303be17ad72fc405c81bb6b354eb577dd needs testing for freshBootstrapTools. https://github.com/NixOS/nixpkgs/pull/283591#issuecomment-1908879638

llvm-hs is marked broken at the moment. It is unclear to me what the status of the project is at the moment. There are branches that support later versions, but there are no such packages uploaded to Hackage.


MF-333 - Add logging middleware to normalizer service

This pull request resolves #333.

Codecov Report

Merging #360 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #360   +/-   ##
=======================================
  Coverage   89.17%   89.17%
=======================================
  Files          43       43
  Lines        1469     1469
=======================================
  Hits         1310     1310
  Misses        110      110
  Partials       49       49

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 4e137a3...97f4be6. Read the comment docs.


Cross-selling sorting by position is not honored

Please describe the feature you would like to see implemented.
When adding cross-selling without the usage of a dynamic product group, the position set is not honored. Instead, the products are sorted by the default value, which is the name of the product.

Hello,
Within our company roadmap and work capacity, we try to address each bug or improvement request but admit that not each one will be resolved. To continue our culture of honesty and openness, we are closing this issue to focus on our roadmap on behalf of all Shopware users.
If you feel like this issue is still impacting you, please create a new issue and let us know.
Thank you again for your valuable feedback.


config file for cfssl gencert

In the section on generating admin client certificate, there is a command which requires a config file which is not there.
Is this missing or I missed a step somehow?
fssl gencert
-ca=ca.pem
-ca-key=ca-key.pem
-config=ca-config.json  --- where does this config file come from?

@DenisBiondic that file is created here: https://github.com/kelseyhightower/kubernetes-the-hard-way/blob/master/docs/04-certificate-authority.md#certificate-authority (cat > ca-config.json <<EOF ...)

Grrr ... I've deleted it via some bash move magic I made in between. Sorry for the silly question


Mendix Cloud | Cloud Resource Packs Exchange Rate

The Mendix Cloud documentation does not include information on the Exchange Rates for Cloud Resource Packs.
https://docs.mendix.com/developerportal/deploy/mendix-cloud-deploy#plans
As I understand it the Exchange Rates are as follows:
2XS = 1 S
2 S = 1 M
2 M = 1 L
2L = 1 XL and so on..
e.g. a customer with 2L packs can procure 4 medium containers / environments.
A customer requested this information, but it is not available on our public documentation.

Hi Elliot (@elliotclements-mendix)
I've added this to a review of resource pack information which is on Jira issue [TW-1555].
I've taken it up with the PM who is in charge of this communication from the R&D side. I'll update here once I have further information.

Hi Elliot,
Sorry about the delay in getting back to you.
Although we do this for customers, it is on a case-by-case basis and isn't an official policy. Therefore customers should come with requests through their CSM if they want to change their cloud resource packs.
If the official policy changes, then I will definitely add this information to the documentation.


Projects won't show up when being lazily loaded

If I run project.nvim lazily, it won't show any projects registered the first time.
  { 'ahmedkhalf/project.nvim',
    -- lazy = false,
    config = function()
      require("project_nvim").setup{
        patterns = { ".git", "_darcs", ".hg", ".bzr", ".svn", "Makefile", "package.json", "project.clj" },
      }
    end
  },

It's clear that it can be bring up by telescope.

Or:
 require('lazy').load({ plugins = {  'project_nvim' } })
 vim.schedule(function()
   vim.cmd('Telescope projects')
 end)

I still run into the same issue.

Paste your code.

I have the same issue.
I tried different lazy loading functions. Most would always open an empty telescope window on first load, without any projects, but would work every time after that. When wrapping it in vim.schedule(), it sometimes shows projects on first try, sometimes not. Seems to be more likely to load the first time if I am slower with my keypresses, but that might be a coincidence. The line require('lazy').load({ plugins = { 'project_nvim' } }) doesn't seem to make a difference for me.
  {
    "ahmedkhalf/project.nvim",
    keys = {
      { '<leader>hp',
        function()
          require('lazy').load({ plugins = { 'project_nvim' } })
          vim.schedule(function()
            vim.cmd('Telescope projects')
          end)
        end
      }
    },
    config = function()
      require("project_nvim").setup {}
      require('telescope').load_extension('projects')
    end,
    dependencies = {
      'nvim-telescope/telescope.nvim'
    }
  },

Could it be due to this (from readme):

Asynchronous file io so it will not slow down vim when reading the history file on startup.

Here is a minimal, working Lazy config for Telescope + Project.nvim:
{
  "https://github.com/nvim-telescope/telescope.nvim",
  branch = "0.1.x",
  dependencies = {
    "https://github.com/nvim-lua/plenary.nvim",
    {
      "https://github.com/ahmedkhalf/project.nvim",
      config = function()
        require("project_nvim").setup({})
      end,
    },
    {
      "https://github.com/nvim-telescope/telescope-fzf-native.nvim",
      build = "make",
      cond = function()
        return vim.fn.executable("make") == 1
      end,
    },
  },
  config = function()
    pcall(require("telescope").load_extension, "fzf")
    pcall(require("telescope").load_extension, "projects")

    vim.keymap.set(
      "n",
      "<leader>fp",
      function() vim.cmd([[Telescope projects]]) end,
      { noremap = true }
    )

}

@pbnj its easy to get it working, the problem is lazy loading it. I also have the same problem, its a blank window the first time, and only works every time after.
Here is project.nvim:
return {
  'ahmedkhalf/project.nvim',
  dependencies = {
    'nvim-telescope/telescope.nvim',
  },
  config = function()
    require('project_nvim').setup({
      detection_methods = { 'pattern' },
      patterns = { '.git' },
    })
    require('telescope').load_extension('projects')
  end,
  keys = {
    {
      '<Leader>p',
      function() require('telescope').extensions.projects.projects() end,
      desc = 'Switch project',
    }
  },
}

here is the relevant part of telescope plugin:
return {
  'nvim-telescope/telescope.nvim',
  dependencies = {
    'nvim-lua/plenary.nvim',
    'nvim-telescope/telescope-ui-select.nvim',
  },
  config = function()
...
  end,
  cmd = {
    'Telescope',
  },

So lazy.nvim is triggered when the Telescope command is called, and for some reason vim.cmd('Telescope projects') as well as require('telescope').extensions.projects.projects() still cause the same issues

Note that adding event = 'VeryLazy' added after the 'ahmedkhalf/project.nvim', does work, but then that loads the entire telescope and all associated code there which is hefty code to load at boot when every single telescope plugin is triggered from a hotkey

I'm also having the same issue sadly

The same also happens to me.

not fixed yet, project.nvim keeps showing nothing

hello, you guys. I found this work for me
		keys = {
			{
				"<leader>fp",
				vim.schedule_wrap(function()
					require("telescope").extensions.projects.projects({})
				end),
			},
		},

so  project.nvim with trigger on keys.

The problem is that the plugins reads the files containing the history asynchronously when it's setup is ran. So when the plugin is lazy loaded, the Telescope picker opens before the history is read.
I haven't been able to dive in long enough to find a solution.
Do we require the asynchronous file reading? I can't imagine reading the history file takes a noticeable amount of time. It'd be simpler to read the history synchronous upon opening the picker.

Using vim.schedule_wrap solved the problem for me


OOM issue when running the quick start code under 80GB gpu

Hello, I appreciate the effort you’ve put into your work!
I’ve been trying to execute your quick start code, but I’ve run into an Out Of Memory (OOM) error, despite having an 80GB GPU at my disposal. I was under the impression that a 7B model would fit comfortably within an 80GB GPU memory, so I’m unsure why I’m still facing this OOM error. Could you possibly shed some light on this issue? Thanks!
from vllm import LLM, SamplingParams
model = LLM("selfrag/selfrag_llama2_7b", download_dir=MY_DIR, dtype="half")

and by the way, can you tell me the typical memory usage when executing this code snippet?

Thank you for your interests! During inference of 7B model, we use a single GPU with 24 GB memory, so I'm not sure why you have got OOM error. Could you try different 7B model e.g., LLama2-7b-hf? If you still get the same OOM error, it might come from the vllm part, and may be better to ask in their Github isssues!

I'm closing this issue now as I am not sure if this comes from the Self-RAG model checkpoints itself, but feel free to reopen it!

Thank you for clarifying. I do not encounter the OOM issue now; it might be because someone might have occupied the GPU memory, and I did not notice it.


Correct tf.Gradient... to tf.train.Gradient...

Can one of the admins verify this patch?

Thank you @JohnAllen! train.md is auto-generated, could you remove the change from PR?

Happy to contribute!  Train.md removed from the PR.

@tensorflow-jenkins test this please

@tensorflow-jenkins test this please


feat(scoped-elements): add createElement capability (#1270)

Adds the capability to create scoped elements by it's tag name.
import { createScope } from '@open-wc/scoped-elements';
import MyButton from './MyButton.js';

const { createElement } = createScope({
  'my-button': MyButton,
});

const $button = createElement('my-button');

Closing because it's not relevant anymore


Prevent updating HelmRelease from helm.toolkit.fluxcd.io/v2beta1

We are currently stuck with Flux v2.1.x and cannot upgrade HelmRelease resources to the latest helm.toolkit.fluxcd.io/v2 yet.

@marians Would you mind including this too? https://github.com/giantswarm/workload-clusters-fleet/pull/1026

@AverageMarcus Added, thanks


Support for SEUR

Firstly, a happy new year to you all!
I would suggest including support for orders delivered via SEUR.
Code example:<PHONE_NUMBER>831178874395
Best Regards,
Diogo

The website is https://www.seur.com/livetracking/
Amazon.es send some stuff for this delivery company

Hi Diogo,
Happy new year, we currently don't support SEUR because they have a good anti-bot system in place. We need to implement a different scraping strategy using an headless browser.
We're focusing on lauching the new website at the moment so this may take some time.
Regards


Generation of [cluster]rolebindings

From https://github.com/keycloak/keycloak/pull/21231#issuecomment-1616619571 should the operator sdk split off the generation of [cluster]rolebindings, roles, and service accounts to allow for operators that can support all install modes? These instead would be created for the service account(s) referenced by the OperatorGroup.

This was my misunderstanding.  The generated [cluster]rolebindings from the kubernetes.yml are not used in the csv, that is all managed later by olm.


adressing add pylint workflow and fix all issues

addresses #262

sorry for the inconvenience, im a complete newbie, i tried linting the codes using black, but that didnt entirely fix all the long line issues, so i did some manually and messed up a lot.
If you allow then i will try again and just run the black command.

REad documentation how to use black
Apply only for files which you have changes, NOT For the whole project
@sigmadawg

@sigmadawg If you're having issues, I could help work on it and put up a PR in One hour, if that's okay with you.
cc @djeck1432

Yes, i'd like the help


docker machine defaults to aarch64, best to make to autodetect?

Wondering why the default docker_machine_download_url defaults to the aarch64 binary. Note the description mentions x64.
variable "docker_machine_download_url" {
  description = "Full url pointing to a linux x64 distribution of docker machine. Once set `docker_machine_version` will be ingored. For example the GitLab version, https://gitlab-docker-machine-downloads.s3.amazonaws.com/v0.16.2-gitlab.2/docker-machine."
  type        = string
  default     = "https://gitlab-docker-machine-downloads.s3.amazonaws.com/v0.16.2-gitlab.10/docker-machine-Linux-aarch64"
}

Maybe best to default docker_machine_download_url to "" and add a default docker_machine_version value? That way the template/gitlab-runner.tpl will download the appropriate arch and code will work for more users. Thanks!

The default should point to the x64 versions, since the default is also m5.arge

I configure it always expicit like https://github.com/npalm/terraform-aws-gitlab-runner/blob/develop/examples/runner-default/main.tf so completely missed the bug

I will set the default URL to https://gitlab-docker-machine-downloads.s3.amazonaws.com/v0.16.2-gitlab.2/docker-machine So it supports the default settings


[Dev Tooling] Application Server Key Management

Almost all games need to have a private key to create new assets out of the thin air. We need a solution to keep the keys safe while using it to auto sign transactions

Duplicates https://github.com/MystenLabs/sui/issues/1223


Drag 'n Drop file doesn't work (Windows - Google Chrome)

Hello,
I have find a second issue.
The Drag 'n Drop plugin is not enabled under the Material Skin.
It is working perfectly under the default Skin, but not in Material Skin, may be it's because of web browser limitation ?
Best regards,
Jean

enabled

king

Hello,
I have find a second issue.
The Drag 'n Drop plugin is not enabled under the Material Skin.
It is working perfectly under the default Skin, but not in Material Skin, may be it's because of web browser limitation ?
Best regards,
Jean

Not supported.

...but its a reasonable request, I'll see what I can do.