text:
[Testing] Enable egress for all tests.

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[x] Security
[x] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

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

Test name
Commit
Details
Rerun command

gencheck_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
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.

/test gencheck_istio

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

Test name
Commit
Details
Rerun command

gencheck_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-pilot-k8s-tests_istio

integ-distroless-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-distroless-k8s-tests_istio

analyze-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-pilot-k8s-tests_istio

integ-distroless-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-distroless-k8s-tests_istio

analyze-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test analyze-tests_istio

integ-telemetry-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
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.

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

Test name
Commit
Details
Rerun command

gencheck_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-pilot-k8s-tests_istio

integ-distroless-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-distroless-k8s-tests_istio

analyze-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test analyze-tests_istio

integ-telemetry-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-telemetry-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-pilot-k8s-tests_istio

integ-distroless-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-distroless-k8s-tests_istio

analyze-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test analyze-tests_istio

integ-telemetry-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-security-k8s-tests_istio

gencheck_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
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.

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-pilot-k8s-tests_istio

integ-distroless-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-distroless-k8s-tests_istio

analyze-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test analyze-tests_istio

integ-telemetry-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-security-k8s-tests_istio

gencheck_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-multicluster-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-pilot-k8s-tests_istio

integ-distroless-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-distroless-k8s-tests_istio

analyze-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test analyze-tests_istio

integ-telemetry-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-multicluster-k8s-tests_istio

gencheck_istio
8bc2892876ef4e85e7222a55c0c6e97de1229e0c
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.

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test analyze-tests_istio

integ-telemetry-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-multicluster-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test analyze-tests_istio

integ-telemetry-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test integ-distroless-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-ipv6-k8s-tests_istio

integ-telemetry-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test analyze-tests_istio

integ-ipv6-k8s-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test analyze-tests_istio

integ-ipv6-k8s-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test integ-ipv6-k8s-tests_istio

integ-telemetry-k8s-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test analyze-tests_istio

integ-ipv6-k8s-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test integ-ipv6-k8s-tests_istio

integ-telemetry-k8s-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test integ-telemetry-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test analyze-tests_istio

integ-telemetry-k8s-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test integ-telemetry-k8s-tests_istio

integ-distroless-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-multicluster-k8s-tests_istio

analyze-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test analyze-tests_istio

integ-telemetry-k8s-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test integ-telemetry-k8s-tests_istio

integ-distroless-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-k8s-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test integ-telemetry-k8s-tests_istio

integ-distroless-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-k8s-tests_istio
91bb20b883240a6af13669bbc7b45c07b6c1c978
link
/test integ-telemetry-k8s-tests_istio

integ-distroless-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
49e5c033f498d6ac31bbec9ea320089937e8fa29
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test analyze-tests_istio

integ-security-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test analyze-tests_istio

integ-security-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-multicluster-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test analyze-tests_istio

integ-security-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-multicluster-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-distroless-k8s-tests_istio

analyze-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test analyze-tests_istio

integ-security-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-multicluster-k8s-tests_istio

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

integ-ipv6-k8s-tests_istio
bee7f86b5f8341f6dae402b62fcb6d68239107bd
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-multicluster-k8s-tests_istio

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

integ-ipv6-k8s-tests_istio
bee7f86b5f8341f6dae402b62fcb6d68239107bd
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-multicluster-k8s-tests_istio

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

integ-ipv6-k8s-tests_istio
bee7f86b5f8341f6dae402b62fcb6d68239107bd
link
/test integ-ipv6-k8s-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-multicluster-k8s-tests_istio

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

integ-ipv6-k8s-tests_istio
bee7f86b5f8341f6dae402b62fcb6d68239107bd
link
/test integ-ipv6-k8s-tests_istio

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

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

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

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
4ec08dc301d89a9070c2ba08a73ddfeca1a9a4dd
link
/test integ-multicluster-k8s-tests_istio

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

integ-ipv6-k8s-tests_istio
bee7f86b5f8341f6dae402b62fcb6d68239107bd
link
/test integ-ipv6-k8s-tests_istio

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

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

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

unit-tests_istio
bee7f86b5f8341f6dae402b62fcb6d68239107bd
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.

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

Test name
Commit
Details
Rerun command

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

integ-ipv6-k8s-tests_istio
bee7f86b5f8341f6dae402b62fcb6d68239107bd
link
/test integ-ipv6-k8s-tests_istio

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

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

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

unit-tests_istio
bee7f86b5f8341f6dae402b62fcb6d68239107bd
link
/test unit-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

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

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

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

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

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

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

Test name
Commit
Details
Rerun command

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

Why is it implemented this way instead of setting it in the integration-defaults-iop file?

True... maybe the deploy egress method could be exposed and people can add egress post-install if their test requires it? I'm guessing the goal here is to remove as much install customization as possible.

@howardjohn

Why is it implemented this way instead of setting it in the integration-defaults-iop file?

My thinking was that we only want a single egress for the mesh rather than one per cluster.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
4e6832f5929554548681904c5c8700785232d2e3
link
/test integ-security-k8s-tests_istio

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

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

/test integ-multicluster-k8s-tests_istio

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

Test name
Commit
Details
Rerun command

unit-tests_istio
2b7a7836b1334e9ed0e6ba131a16703fb666ad7b
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.

/test unit-tests_istio

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

Test name
Commit
Details
Rerun command

unit-tests_istio
2b7a7836b1334e9ed0e6ba131a16703fb666ad7b
link
/test unit-tests_istio

integ-multicluster-k8s-tests_istio
2b7a7836b1334e9ed0e6ba131a16703fb666ad7b
link
/test integ-multicluster-k8s-tests_istio

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

/test integ-multicluster-k8s-tests_istio

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
2b7a7836b1334e9ed0e6ba131a16703fb666ad7b
link
/test integ-multicluster-k8s-tests_istio

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

/test integ-multicluster-k8s-tests_istio

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
2b7a7836b1334e9ed0e6ba131a16703fb666ad7b
link
/test integ-multicluster-k8s-tests_istio

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

authors: istio-testing nmittler stevenctl


text:
Improved performance of MostSpecificHostMatch

Use map instead of loop statement to match exactly
Add benchmark testcase for MostSpecificHostMatch
Refer the necessary judgment statements to the outside of the looping structure like needle.IsWildCarded()
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[x] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[x] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Pull Request Attributes
Please check any characteristics that apply to this pull request.
[x] Does not have any changes that may affect Istio users.

Hi @zhd173. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

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.

#28423 release-v1.7

/ok-to-test

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

Test name
Commit
Details
Rerun command

unit-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-ipv6-k8s-tests_istio

integ-telemetry-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-ipv6-k8s-tests_istio

integ-telemetry-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-telemetry-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-ipv6-k8s-tests_istio

integ-telemetry-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-ipv6-k8s-tests_istio

integ-telemetry-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-security-k8s-tests_istio

unit-tests_istio
633ca456b14ccdf96d99511452bf8c6ca5030fbf
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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-security-k8s-tests_istio

unit-tests_istio
633ca456b14ccdf96d99511452bf8c6ca5030fbf
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
633ca456b14ccdf96d99511452bf8c6ca5030fbf
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-security-k8s-tests_istio

unit-tests_istio
633ca456b14ccdf96d99511452bf8c6ca5030fbf
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
633ca456b14ccdf96d99511452bf8c6ca5030fbf
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-security-k8s-tests_istio

unit-tests_istio
633ca456b14ccdf96d99511452bf8c6ca5030fbf
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
633ca456b14ccdf96d99511452bf8c6ca5030fbf
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
633ca456b14ccdf96d99511452bf8c6ca5030fbf
link
/test integ-distroless-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
35774d5b51f15785136ac5bdd16f13a683d16427
link
/test integ-security-k8s-tests_istio

unit-tests_istio
633ca456b14ccdf96d99511452bf8c6ca5030fbf
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
633ca456b14ccdf96d99511452bf8c6ca5030fbf
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
633ca456b14ccdf96d99511452bf8c6ca5030fbf
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
633ca456b14ccdf96d99511452bf8c6ca5030fbf
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
633ca456b14ccdf96d99511452bf8c6ca5030fbf
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 benchmark_istio

lgtm just waiting for benchmark test to run

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

Test name
Commit
Details
Rerun command

unit-tests_istio
2ff87a1bb759bdddb608acb41cf653608e035fc8
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.

/test unit-tests_istio

source: gharchive/pull-request

authors: howardjohn hzxuzhonghu istio-testing zhd173

repo: istio/istio

license_type: permissive

license_source: github-api


text:
minor improvements to istio cni

Please provide a description of what this PR is for.
This PR adds some minor improvements to istio-cni-taint-controller
i) Logging of errors when processing istio cni pods from the workqueue
ii) Consistent usage of namespace
iii) Adding standard labels to the istio cni taint controller manifests
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

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

Test name
Commit
Details
Rerun command

release-notes_istio
598c36ca8c9ad9c7b0872334e12b543633054524
link
/test release-notes_istio

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

/test release-notes_istio

1.15 support is being removed in 1.10, and has already started.
But if we do change the default we will probably break upgrades
On Tue, Feb 23, 2021 at 9:29 AM Tariq Ibrahim notifications@github.com
wrote:

@tariq1890 commented on this pull request.
In manifests/charts/istio-cni/templates/daemonset.yaml
https://github.com/istio/istio/pull/30944#discussion_r581237684:

@@ -148,7 +148,7 @@ spec:
- name: "TAINT_CONFIGMAP-NAME"
value: "istio-cni-taint-configmap"
- name: "TAINT_CONFIGMAP-NAMESPACE"

       value: "kube-system"

       value: {{ .Release.Namespace | quote }}

@rlenglet https://github.com/rlenglet We use a custom namespace to
deploy istio-cni. Our daemonsets are marked as system-node-critical which
is higher than system-cluster-critical.
Deploying into kube-system is not an option for us. I believe this might
be a limitation in kubernetes versions 1.15 and lower.
Is there any plan to retire k8s 1.15 support at all?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/30944#discussion_r581237684, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXN7ZFWLRGUDP3WHHH3TAPQZLANCNFSM4X324RIA
.

@howardjohn Are you sure that this will "break" upgrades? Isn't the taint controller used in an experimental mode. At its current state, the taint controller isn't really usable. Wouldn't it be safe to just make this change and stop hard-coding namespaces before this is termed as release-ready?

If CNI suddenly ends up in a different namespace I suspect we would end up
with 2 copies which will probably conflict with each other, etc. The taint
controller is in the same daemonset as the core CNI so I don't think you
can just change the namespace of the tainy controller?
On Tue, Feb 23, 2021 at 9:43 AM Tariq Ibrahim notifications@github.com
wrote:

@howardjohn https://github.com/howardjohn Are you sure that this will
"break" upgrades? Isn't the taint controller used in an experimental mode.
At its current state, the taint controller isn't really usable. Wouldn't it
be safe to just make this change and stop hard-coding namespaces before
this is termed as release-ready?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/30944#issuecomment-784380319, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXMUXTLDVAMXSWBZLQLTAPSLTANCNFSM4X324RIA
.

@howardjohn How about creating  a values.yaml parameter to make this configurable? The value can default to kube-system

@howardjohn @rlenglet Requesting your response. Harcoding kube-system puts us in a difficult place. It doesn't fit with how we manage our istio lifecycles.
Would using a helm value for this work?

We have been running istio cni in our custom namespace since Istio 1.6

One thing I am confused of: our docs say --set components.cni.namespace=kube-system

@howardjohn This is applicable only for GKE as per the docs. These instructions won't apply to us as we use custom Kubernetes clusters built on AWS

I think this needs a release note, @tariq1890 ?

+1 on release note.  @tariq1890 can you also describe any impact of upgrade? A little nervous on the namespace change and its impact to upgrade

Sure, could you point me to the steps of writing a release note? I'm happy to provide the necessary details there.
I don't think the upgrade should break the deployment since you're deploying the configMap to a different namespace (it is now being deployed in the right namespace, in fact) and the daemonSet has also been updated to point to the new namespace of the train configMap.
Additionally, I believe Istio CNI is not necessarily a GA component and the taint controller is an experimental mode within Istio CNI. The taint controlled is also disabled by default.
Finally, I'd like to add that we faced multiple issues when turning on the taint controller. I don't think the taint controller is in a usable state currently. Is the taint controller being tested by Istio upstream's test suite?

authors: howardjohn istio-testing linsun mandarjog tariq1890


text:
[WIP] Allow individual api group and version for each config resource kind in Pilot config store

Currently all CRDs in Pilot share the same IstioAPIGroup: config.istio.io and IstioAPIVersion: v1alphav2
In this PR, we allow each resource kind to be able to define their own config group with a common suffix istio.io and version.
This allows each feature to advance API versions at different pace.
This also allows the CRD group name to be reverse order mapping to proto package, as suggested in istio/api#343
#3457

Hasn't fixed tests yet. Send out to seek for early feedbacks.

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
2e9f83f23b79973ae1ca0384d797e2e2fedb72f8
link
/test istio-presubmit

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.

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
7f30f410bc2d93963e427e08ee23003792284e28
link
/test istio-presubmit

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.

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
7f30f410bc2d93963e427e08ee23003792284e28
link
/test istio-presubmit

prow/istio-unit-tests.sh
7f30f410bc2d93963e427e08ee23003792284e28
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
7f30f410bc2d93963e427e08ee23003792284e28
link
/test istio-presubmit

prow/istio-unit-tests.sh
1aa6b02e18716088530a64d725688d2db5913f49
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
1aa6b02e18716088530a64d725688d2db5913f49
link
/test istio-unit-tests

prow/e2e-simpleTests.sh
1aa6b02e18716088530a64d725688d2db5913f49
link
/test e2e-simple

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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
1aa6b02e18716088530a64d725688d2db5913f49
link
/test istio-unit-tests

prow/e2e-simpleTests.sh
1aa6b02e18716088530a64d725688d2db5913f49
link
/test e2e-simple

prow/e2e-bookInfoTests.sh
1aa6b02e18716088530a64d725688d2db5913f49
link
/test e2e-bookInfo

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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
1aa6b02e18716088530a64d725688d2db5913f49
link
/test istio-unit-tests

prow/e2e-simpleTests.sh
1aa6b02e18716088530a64d725688d2db5913f49
link
/test e2e-simple

prow/e2e-bookInfoTests.sh
1aa6b02e18716088530a64d725688d2db5913f49
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
1aa6b02e18716088530a64d725688d2db5913f49
link
/test istio-pilot-e2e

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

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

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
1aa6b02e18716088530a64d725688d2db5913f49
link
/test e2e-simple

prow/e2e-bookInfoTests.sh
1aa6b02e18716088530a64d725688d2db5913f49
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
1aa6b02e18716088530a64d725688d2db5913f49
link
/test istio-pilot-e2e

prow/istio-unit-tests.sh
dfdf0f58333edfde3693524b027af8df0142dbfd
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
226da0e6b18cc783a9ad53ebac040daa9faf3e36
link
/test istio-pilot-e2e

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
226da0e6b18cc783a9ad53ebac040daa9faf3e36
link
/test istio-pilot-e2e

prow/istio-unit-tests.sh
e9da6ee11ae67413ea924ee2779e91fc79825a06
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
226da0e6b18cc783a9ad53ebac040daa9faf3e36
link
/test istio-pilot-e2e

prow/istio-unit-tests.sh
e9da6ee11ae67413ea924ee2779e91fc79825a06
link
/test istio-unit-tests

prow/istio-presubmit.sh
e9da6ee11ae67413ea924ee2779e91fc79825a06
link
/test istio-presubmit

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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
cb55a61407454cec15bec8d698f9068f7a1f6765
link
/test istio-pilot-e2e

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

/test istio-pilot-e2e

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
cb55a61407454cec15bec8d698f9068f7a1f6765
link
/test istio-pilot-e2e

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

I'm still bothered by having constants like "v1alpha2" more than one place in the source tree (not talking about golden files)
Maybe the follow up PR can be combined/stacked with this one?

/test istio-pilot-e2e

PTAL

I didn't notice until now but this PR changed vendor
we may need to revert it or fix forward (noticed similar in #3599 )
do you know how that happened ? can you retrace ? we probably need a hook to check against accidental vendor changes

fixed it in https://github.com/istio/istio/commit/57a9d1ab7ed7b1e7b3e4890d21bdc6b48c1b1bd5
in the future please always review the file changes before making a PR
also use make pull to rebase

@ldemailly Thanks for fixing it. Actually I saw it but I wasn't so sure what it is. I will be more proactive next time.

that vendor/ stuff is new and not obvious, so no worries, and feel free to help update
https://github.com/istio/istio/wiki/Vendor-FAQ

Updated: https://github.com/istio/istio/wiki/Vendor-FAQ#should-i-merge-changes-in-vendor

authors: istio-testing ldemailly xiaolanz


text:
Remove dependency on k8s.io/kubernetes

This is not actually used, just a 100 step removed indirect dependency
that upstreams are not accepting fixes to remove. So we can just
explicitly drop it.
Please provide a description of this PR:

Why do we depend on containerd in the first place ? Can we just exclude them.
But the bigger question - are we ready to start having modular deps, i.e. a go.mod in pkg/, one in operator/, one for istioctl, etc ?

We depend on containerd because of helm (which has it for OCI images) and
go-containerregistry (which we import for WASM).
For the bigger question - I don't know, would need to do some research of
the implications
On Tue, Nov 23, 2021 at 8:15 AM Costin Manolache @.***>
wrote:

Why do we depend on containerd in the first place ? Can we just exclude
them.
But the bigger question - are we ready to start having modular deps, i.e.
a go.mod in pkg/, one in operator/, one for istioctl, etc ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/36200#issuecomment-976787409, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXOHEN6ZNSHOM57E7N3UNO42FANCNFSM5IRXMTHQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@howardjohn: PR needs rebase.

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.

authors: costinm howardjohn istio-testing


text:
SecretServer save multiple workload's key cert.

Efforts for #4483 . The end result will be each key/certs stored in its own directory, /etc/certs/<service_account>/{key/cert.pem}.

Stop using SecretServer to save CAClient's own credentials. This should reduce the confusion by having SS only managing workload's key cert, but feel free to propose something else.
Changing SetKey & SetCerts into single method Save for consistency.
Remove FileUtil & its mocking, use the implementation to test directly.

Extracting service account from KeyCertBundle is not implemented yet.
@mangchiandjjoe

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: diemtvu
Assign the PR to them by writing /assign @diemtvu in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

security/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
0257945cbdd242c1a611d0cc1e14fe7a29dcb013
link
/test e2e-simple

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.

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

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
0257945cbdd242c1a611d0cc1e14fe7a29dcb013
link
/test e2e-simple

prow/istio-unit-tests.sh
0cc8449507149cbfa7fd83e745ebf0d7538097cf
link
/test istio-unit-tests

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

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: wattli
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

security/OWNERS [wattli]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

authors: incfly istio-testing wattli


text:
Incomplete tests: baseline quota support

Context: production readiness proposal and plan
The feature “baseline quota support *” is identified as incomplete test coverage. As a measure to reach Istio production quality in 0.3, this issue is opened to track the progress of providing sufficient test coverage for the feature in question.
This issue is initially assigned to the working group leads.
Recommendations:

Come up with a test plan for how the feature should be tested. Identify and document (in this issue, or a separate document this issue will link to) test cases and whether each will be covered by an integration test (with some level of mocking and/or starting up selected components in test environment), or end to end test (aka system test, which brings up the whole Istio to exercise the feature; currently live in the istio/istio repo).
If you expect the test plan is complex and controversial, consider having it formally reviewed.
State an ETA in the issue, and assign this to a developer who will execute the test plan.
Execute the test plan as the highest priority for 0.3.
For any bug or defect identified by the new test cases, file a new issue and link it from this one.
Close this issue only when the test plan is completely executed, and all additional issues identified in step 3 are fixed.

If you see a risk of not fixing this issue by end of 0.3, please contact istio-production-quality@googlegroups.com as soon as possible. We will also periodically ping the issue for update.

Baseline memquota support has adequate test coverage in e2e tests.

source: gharchive/issue

authors: hklai mandarjog

license_source: bigquery


text:
使用自定义的oracle驱动可以测试连接成功，但是在数据同步中拉取不到表

Branch name (分支名)
main
Bug description (缺陷描述)
测试连接通过，使用的自己上传的驱动

但是在拉取表数据时会提示找不到class

{
"code": "200",
"msg": "java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver"
}
附件为使用的驱动
ojdbc8-18.15.0.0.jar.zip

驱动文件未解压，解压后上传就可以用了

驱动文件为.zip格式，上传驱动时应该未解压，只有直接上传jar.zip后查询表才会报这个错，解压后上传就可以正常使用了

repo: isxcode/spark-yun


text:
[FIX] compatibility of website_sale_available with website_sale_options

Hi @yelizariev . This PR fix and error raised when you install website_sale_available together with website_sale_options.
Thanks!

Thanks!
El vie., 26 de agosto de 2016 2:30, Ivan Yelizariev <
notifications@github.com> escribió:

Merged #92 https://github.com/it-projects-llc/website-addons/pull/92.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/it-projects-llc/website-addons/pull/92#event-768448617,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC4H0LzKZU8dIXm5UQ0bTYDAJIdUEjbHks5qjnoCgaJpZM4JtN5w
.

repo: it-projects-llc/website-addons

license: mit


text:
[UBS-Admin. Pricing page] Dropdown lists of the menu on the Pricing page ('Tariffs') is not localized for EN

Environment: Windows 10 Pro, Chrome 101
Reproducible: always
Build found: May 18, 2022
Preconditions
User is logged in as Admin. EN locale is set for the page.
Steps to reproduce

Go to UBS Admin Tariffs page: https://ita-social-projects.github.io/GreenCityClient/#/ubs-admin/tariffs
Click on the 'Region' dropdown. Pay attention to the items in the dropdown list.
Select any entry in the 'Region' dropdown menu.
Click on the 'City' dropdown. Pay attention to the items in the dropdown list.
Click on the 'Courier' dropdown. Pay attention to the items in the dropdown list.
Click on the 'Receiving station' dropdown. Pay attention to the items in the dropdown list.
Click on the 'State' dropdown. Pay attention to the items in the dropdown list.

Actual result
Items in the dropdown lists are not localized according to EN locale.
Expected result
Items in the dropdown lists are localized according to EN locale.
User story and test case links
User story #3835
Test case"

We don't localized for EN admin part of project

authors: IrynaKhyliuk melnychenkoas

repo: ita-social-projects/GreenCity

license: MIT


text:
[Показати на мапі] The page crash when clicking on any item from the list in 'Показати на мапі' page

Environment: macOS Catalina 10.15.7, Google Chrome (90.0.4430.212)
Reproducible: always.
Build found: last commit.
Steps to reproduce

Go to https://speak-ukrainian.org.ua/dev/
Click on 'Всі гуртки'
Click on 'Показати на мапі'
Click on any item in the list

Actual result
The page crash when clicking on any item from the list in 'Показати на мапі' page.
https://user-images.githubusercontent.com/83167973/120116578-67c03300-c191-11eb-9a62-35fe0207d086.mov
Expected result
Location is shown on the map.
Labels to be added
"Bug", Priority ("pri: High"), Severity ("severity:Major"), Type ("Functional").

The page crashes when clicking on any item in the 'Показати на мапі' page
https://user-images.githubusercontent.com/83167973/121418492-ac0eb880-c973-11eb-88cf-c745526d6748.mov

repo: ita-social-projects/TeachUA


text:
ANPR - Purtroppo non è stato possibile accedere al servizio

Ciao, voglio accedere al portale ANPR ma c'è un errore: non risulta possibile individuare di modo univoco la mia scheda anagrafica.

Ho scritto al Comune di Anzi (PZ) e loro rispondono che non si verifica nessun problema.
Sono residente all'Estero (Argentino). Qualcuno sa che devo fare?

gentilmente ci può dare le prime 6 lettere del suo codice fiscale ? altrimenti non sappiamo come controllare la situazione . grazie

gentilmente ci può dare le prime 6 lettere del suo codice fiscale ? altrimenti non sappiamo come controllare la situazione . grazie

Certo, SSTFLP

grazie se è lei la persona nata nel 1993  a luglio, deve chiedere al suo comune  ANZI  di  provvedere alla validazione del  suo codice fiscale nella scheda di ANPR  -  si chiude la issue -

authors: cmigliardi felipesastre

repo: italia/anpr


text:
[SC]: evento.datiAdozioneMinoriInternazionale mancante

Ambiente
pre-produzione, produzione
Servizio
R009 - Servizi cooperativi validazione evento, R010 - Servizi cooperativi anteprima
idOperazione

idEvento o idAnsc
No response
Provenienza segnalazione
Software House
Comune di riferimento e operatore
Lissone - biadanpad
Data del test (yyyy-mm-dd)
29-05-2024
Descrivi il problema
Buongiorno,
stiamo tentando di implementare il caso d'uso 14950000 - Annotazione per adozione internazionale di minore - Dic_Nasc_998_4.
Il mapping del caso d'uso fa riferimento all'oggetto datiAdozioneMinoriInternazionale che però non è definito nella classe ModelEvento.
Non possiamo quindi procedere all'implementazione.
Come riprodurre il problema
No response
Payload (json)
No response

Buon pomeriggio @biadanpad,
provvederemo ad aggiornare quanto prima il ModelEvento, grazie per la segnalazione.
Inoltre confermiamo che potete implementare il caso d'uso così come indicato sul mapping del caso d'uso Dic_Nasc_998_4.
Un saluto,
Supporto ANSC

Salve @biadanpad,
vi comunichiamo che la documentazione è stata aggiornata.
Un saluto,
Supporto ANSC

authors: biadanpad gbuemi

repo: italia/ansc


text:
Navscroll su mobile con scrollTop

2.6.0
Quando si usa Navscroll su mobile insieme al componente "Torna su", il bottone per tornare su scompare dietro alla riga di navigazione creata in fondo alla pagina.

sono in attesa di una risoluzione, grazie

authors: SimonePadovan spadovan

repo: italia/bootstrap-italia


text:
Double free for Log

Eseguendo il test, anche dando 20 come primo input, il programma esce abortendo a causa di un double free.  Si tratta di CLog::~CLog() come si vede lanciando il test sotto gdb:
Insert the test number:
20
---------------------------------------------------------
Bye Bye
*************************
*************************
---------------------------------------------------------
free(): double free detected in tcache 2

Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
Download failed: Invalid argument.  Continuing without source file ./signal/../sysdeps/unix/sysv/linux/raise.c.
50	../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x00007ffff7bd7537 in __GI_abort () at abort.c:79
#2  0x00007ffff7c30768 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7ffff7d3ee2d "%s\n") at ../sysdeps/posix/libc_fatal.c:155
#3  0x00007ffff7c37a5a in malloc_printerr (str=str@entry=0x7ffff7d41170 "free(): double free detected in tcache 2") at malloc.c:5347
#4  0x00007ffff7c39055 in _int_free (av=0x7ffff7d70b80 <main_arena>, p=0x55555557bc70, have_lock=0) at malloc.c:4201
#5  0x00007ffff79e479f in CLog::~CLog (this=0x7ffff7a66020 <Log>, __in_chrg=<optimized out>) at ../cie-pkcs11/Util/log.cpp:120
#6  0x00007ffff7bf04d7 in __run_exit_handlers (status=0, listp=0x7ffff7d70718 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true,
    run_dtors=run_dtors@entry=true) at exit.c:108
#7  0x00007ffff7bf067a in __GI_exit (status=<optimized out>) at exit.c:139
#8  0x00007ffff7bd8d11 in __libc_start_main (main=0x555555558c10 <main(int, char**)>, argc=2, argv=0x7fffffffe078, init=<optimized out>,
    fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffe068) at ../csu/libc-start.c:342
#9  0x000055555555632a in _start ()

In effetti, la definizione CLog Log; è stata spostata in defines.h.  Non mi è chiaro se gcc tenta di considerarlo un unico oggetto.
Forse dovrebbe essere dichiarato static cosicché ognuno abbia la sua copia di Log, oppure costruirlo come singleton in modo da condividere un'unica copia.
Peraltro, c'è un altro log.cpp in cie_sign_sdk/src/Util, leggermente diverso.  C'è una ragione per tenerne due copie?
Già che ci sono, posso chiedere se questo repository viene usato anche per WIN32?

È sufficiente mettere extern:
Index: cie-pkcs11/LOGGER/Logger.cpp
===================================================================
--- cie-pkcs11/LOGGER/Logger.cpp	(revision 89)
+++ cie-pkcs11/LOGGER/Logger.cpp	(working copy)
@@ -122,7 +122,7 @@
 	}

 	int log_level = m_Instance->getLogConfig();
-    printf("Lib log level: %d\n", log_level);
+    // printf("Lib log level: %d\n", log_level);

 	if (log_level == LOG_STATUS_DISABLED) {
 		m_Instance->disableLog();
Index: cie-pkcs11/Util/defines.h
===================================================================
--- cie-pkcs11/Util/defines.h	(revision 89)
+++ cie-pkcs11/Util/defines.h	(working copy)
@@ -54,7 +54,7 @@
 #define logParamBuf(p,l)
 #define logParamBufHide(p,l)

-CLog Log;
+extern CLog Log;

 #define init_func \
   	CFuncCallInfo info(__FUNCTION__ ,Log);
 	//OutputDebugString(fName);
Index: cie-pkcs11/Util/log.cpp
===================================================================
--- cie-pkcs11/Util/log.cpp	(revision 89)
+++ cie-pkcs11/Util/log.cpp	(working copy)
@@ -39,6 +39,8 @@
 	LM_Module_Thread	// un file per modulo e per thread
 } LogMode = LM_Module;

+// definition
+CLog Log;

 void initLog(const char *moduleName, const char *iniFile,const char *version)
 {
Index: cie_sign_sdk/src/PCSC/APDU.h
===================================================================
--- cie_sign_sdk/src/PCSC/APDU.h	(revision 89)
+++ cie_sign_sdk/src/PCSC/APDU.h	(working copy)
@@ -1,5 +1,6 @@
 #pragma once
 #include <functional>
+#include <cstdint>

 class CToken;
 class APDU

Questo problema causa anche sistematici crash all'uscita da diverse applicazioni che caricano la libreria libcie-pkcs11.so, fra cui LibreOffice e Okular: ho descritto nel dettaglio il problema su Forum Italia.
Non è quindi una combinazione se il problema è apparso con la release 1.4.2, che includeva proprio delle migliorie alla gestione dei log come descritto nella issue #27 .

Risolta nella 1.4.3.9

authors: aantetomaso alevesely mavoga

repo: italia/cie-middleware-linux


text:
C.SI.3.2 - DICHIARAZIONE DI ACCESSIBILITÀ - Criterio OK con link errato

Buongiorno,
ho un comune che ha effettuato la dichiarazione di accessibilità ma con l'url del comune errato (ha omesso la provincia nell'url), nonostante ciò il test è passato - versione del vaidatore 2.8.0

È possibile avere il link al sito, anche in privato?

Il comune ha sistemato il problema perchè doveva andare in asseverazione... risegnalo in caso ricapiti grazie

repo: italia/pa-website-validator


text:
[Bug] Adding "excluded_keys": Device_Temperature  - donot remove it from Homebridge

Please use the template and fill in all the data requested below!
Describe the bug
This is set in my configuration but i still can see Device_Temperature in the Homebridge and HomeKit as Temperature Sensor. I clear cached devices  - still visible.
"defaults": {
"excluded_keys": [
"device_temperature"
]
},
Same is happening if I setup - temperature is not removed :
"devices": [
                {
                    "id": "0x00158d0007e238ef",
                    "exclude": true,
                     "excluded_keys": [
                        "device_temperature"
                    ],
Related devices
All devices.
To Reproduce
Setting exclude keys do not affect the behaviour of Devices, Temperature is still visible. I also excluded the Temp from the Zigbee2MQQT but  Z2M is still showing it.
devices:
'0x00158d0007e238ef':
friendly_name: MovementSensor
filtered_attributes:
- device_temperature
homeassistant: {}
legacy: false
optimistic: true
occupancy_timeout: 30
no_occupancy_since: []
filtered_optimistic:
- device_temperature
Log from Zigbee2MQQT
Jul 23 15:12:56 stefanhome npm[8048]: Zigbee2MQTT:info  2022-07-23 15:12:56: MQTT publish: topic 'zigbee2mqtt/MovementSensor', payload '{"battery":100,"illuminance":0,"illuminance_lux":0,"linkquality":44,"occupancy":false,"power_outage_count":7,"voltage":3185}'
Expected behavior
When excluding temperature it should not appear in Homebridge and HomeKit.
MQTT messages
If possible (and applicable), please provide the following:
[{"definition":null,"endpoints":{"1":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"10":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"11":{"bindings":[],"clusters":{"input":["ssIasAce","genTime"],"output":["ssIasZone","ssIasWd"]},"configured_reportings":[],"scenes":[]},"110":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"12":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"13":{"bindings":[],"clusters":{"input":["genOta"],"output":[]},"configured_reportings":[],"scenes":[]},"2":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"242":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"3":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"4":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"47":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"5":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"6":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"8":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]}},"friendly_name":"Coordinator","ieee_address":"0x00124b001cce03b1","interview_completed":true,"interviewing":false,"network_address":0,"supported":false,"type":"Coordinator"},{"date_code":"20200312","definition":{"description":"MiJia light intensity sensor","exposes":[{"access":1,"description":"Remaining battery in %","name":"battery","property":"battery","type":"numeric","unit":"%","value_max":100,"value_min":0},{"access":1,"description":"Voltage of the battery in millivolts","name":"voltage","property":"voltage","type":"numeric","unit":"mV"},{"access":1,"description":"Raw measured illuminance","name":"illuminance","property":"illuminance","type":"numeric"},{"access":1,"description":"Measured illuminance in lux","name":"illuminance_lux","property":"illuminance_lux","type":"numeric","unit":"lx"},{"access":1,"description":"Number of power outages","name":"power_outage_count","property":"power_outage_count","type":"numeric"},{"access":1,"description":"Link quality (signal strength)","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"GZCGQ01LM","options":[{"access":2,"description":"Number of digits after decimal point for illuminance, takes into effect on next report of device.","name":"illuminance_precision","property":"illuminance_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"Calibrates the illuminance value (percentual offset), takes into effect on next report of device.","name":"illuminance_calibration","property":"illuminance_calibration","type":"numeric"},{"access":2,"description":"Number of digits after decimal point for illuminance_lux, takes into effect on next report of device.","name":"illuminance_lux_precision","property":"illuminance_lux_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"Calibrates the illuminance_lux value (percentual offset), takes into effect on next report of device.","name":"illuminance_lux_calibration","property":"illuminance_lux_calibration","type":"numeric"}],"supports_ota":false,"vendor":"Xiaomi"},"endpoints":{"1":{"bindings":[{"cluster":"msIlluminanceMeasurement","target":{"endpoint":1,"ieee_address":"0x00124b001cce03b1","type":"endpoint"}}],"clusters":{"input":["genBasic","msIlluminanceMeasurement","genIdentify","genPowerCfg"],"output":["genIdentify"]},"configured_reportings":[{"attribute":"measuredValue","cluster":"msIlluminanceMeasurement","maximum_report_interval":3600,"minimum_report_interval":15,"reportable_change":500}],"scenes":[]}},"friendly_name":"IlluminationSensor","ieee_address":"0x54ef4410001fffed","interview_completed":true,"interviewing":false,"manufacturer":"XIAOMI","model_id":"lumi.sen_ill.mgl01","network_address":5147,"power_source":"Battery","software_build_id":"2019\u0000www.","supported":true,"type":"EndDevice"},{"date_code":"20170627","definition":{"description":"Aqara human body movement and illuminance sensor","exposes":[{"access":1,"description":"Remaining battery in %","name":"battery","property":"battery","type":"numeric","unit":"%","value_max":100,"value_min":0},{"access":1,"description":"Indicates whether the device detected occupancy","name":"occupancy","property":"occupancy","type":"binary","value_off":false,"value_on":true},{"access":1,"description":"Temperature of the device","name":"device_temperature","property":"device_temperature","type":"numeric","unit":"°C"},{"access":1,"description":"Voltage of the battery in millivolts","name":"voltage","property":"voltage","type":"numeric","unit":"mV"},{"access":1,"description":"Measured illuminance in lux","name":"illuminance_lux","property":"illuminance","type":"numeric","unit":"lx"},{"access":1,"description":"Measured illuminance in lux","name":"illuminance","property":"illuminance","type":"numeric","unit":"lx"},{"access":1,"description":"Number of power outages","name":"power_outage_count","property":"power_outage_count","type":"numeric"},{"access":1,"description":"Link quality (signal strength)","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"RTCGQ11LM","options":[{"access":2,"description":"Number of digits after decimal point for device_temperature, takes into effect on next report of device.","name":"device_temperature_precision","property":"device_temperature_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"Calibrates the device_temperature value (absolute offset), takes into effect on next report of device.","name":"device_temperature_calibration","property":"device_temperature_calibration","type":"numeric"},{"access":2,"description":"Number of digits after decimal point for illuminance, takes into effect on next report of device.","name":"illuminance_precision","property":"illuminance_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"Calibrates the illuminance value (percentual offset), takes into effect on next report of device.","name":"illuminance_calibration","property":"illuminance_calibration","type":"numeric"},{"access":2,"description":"Number of digits after decimal point for illuminance_lux, takes into effect on next report of device.","name":"illuminance_lux_precision","property":"illuminance_lux_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"Calibrates the illuminance_lux value (percentual offset), takes into effect on next report of device.","name":"illuminance_lux_calibration","property":"illuminance_lux_calibration","type":"numeric"},{"access":2,"description":"Time in seconds after which occupancy is cleared after detecting it (default 90 seconds).","name":"occupancy_timeout","property":"occupancy_timeout","type":"numeric","value_min":0},{"access":2,"description":"Sends a message the last time occupancy (occupancy: true) was detected. When setting this for example to [10, 60] a {\"no_occupancy_since\": 10} will be send after 10 seconds and a {\"no_occupancy_since\": 60} after 60 seconds.","item_type":"number","name":"no_occupancy_since","property":"no_occupancy_since","type":"list"}],"supports_ota":false,"vendor":"Xiaomi"},"endpoints":{"1":{"bindings":[],"clusters":{"input":["genBasic","65535","msOccupancySensing","msIlluminanceMeasurement","ssIasZone","genPowerCfg","genIdentify"],"output":["genBasic","genOta"]},"configured_reportings":[],"scenes":[]}},"friendly_name":"MovementSensor","ieee_address":"0x00158d0007e238ef","interview_completed":true,"interviewing":false,"manufacturer":"LUMI","model_id":"lumi.sensor_motion.aq2","network_address":57059,"power_source":"Battery","software_build_id":"3000-0001","supported":true,"type":"EndDevice"},{"date_code":"20191205","definition":{"description":"Aqara temperature, humidity and pressure sensor","exposes":[{"access":1,"description":"Remaining battery in %","name":"battery","property":"battery","type":"numeric","unit":"%","value_max":100,"value_min":0},{"access":1,"description":"Measured temperature value","name":"temperature","property":"temperature","type":"numeric","unit":"°C"},{"access":1,"description":"Measured relative humidity","name":"humidity","property":"humidity","type":"numeric","unit":"%"},{"access":1,"description":"The measured atmospheric pressure","name":"pressure","property":"pressure","type":"numeric","unit":"hPa"},{"access":1,"description":"Voltage of the battery in millivolts","name":"voltage","property":"voltage","type":"numeric","unit":"mV"},{"access":1,"description":"Link quality (signal strength)","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"WSDCGQ11LM","options":[{"access":2,"description":"Number of digits after decimal point for temperature, takes into effect on next report of device.","name":"temperature_precision","property":"temperature_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"Calibrates the temperature value (absolute offset), takes into effect on next report of device.","name":"temperature_calibration","property":"temperature_calibration","type":"numeric"},{"access":2,"description":"Number of digits after decimal point for humidity, takes into effect on next report of device.","name":"humidity_precision","property":"humidity_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"Calibrates the humidity value (absolute offset), takes into effect on next report of device.","name":"humidity_calibration","property":"humidity_calibration","type":"numeric"},{"access":2,"description":"Number of digits after decimal point for pressure, takes into effect on next report of device.","name":"pressure_precision","property":"pressure_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"Calibrates the pressure value (absolute offset), takes into effect on next report of device.","name":"pressure_calibration","property":"pressure_calibration","type":"numeric"}],"supports_ota":false,"vendor":"Xiaomi"},"endpoints":{"1":{"bindings":[],"clusters":{"input":["genBasic","genIdentify","65535","msTemperatureMeasurement","msPressureMeasurement","msRelativeHumidity"],"output":["genBasic","genGroups","65535"]},"configured_reportings":[],"scenes":[]}},"friendly_name":"TemperatureSensor","ieee_address":"0x00158d0007ed5c77","interview_completed":true,"interviewing":false,"manufacturer":"LUMI","model_id":"lumi.weather","network_address":13770,"power_source":"Battery","software_build_id":"3000-0001","supported":true,"type":"EndDevice"},{"date_code":"20201026","definition":{"description":"Temperature and humidity sensor","exposes":[{"access":1,"description":"Remaining battery in %","name":"battery","property":"battery","type":"numeric","unit":"%","value_max":100,"value_min":0},{"access":1,"description":"Measured temperature value","name":"temperature","property":"temperature","type":"numeric","unit":"°C"},{"access":1,"description":"Measured relative humidity","name":"humidity","property":"humidity","type":"numeric","unit":"%"},{"access":1,"description":"Voltage of the battery in millivolts","name":"voltage","property":"voltage","type":"numeric","unit":"mV"},{"access":1,"description":"Link quality (signal strength)","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"SNZB-02","options":[{"access":2,"description":"Number of digits after decimal point for temperature, takes into effect on next report of device.","name":"temperature_precision","property":"temperature_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"Calibrates the temperature value (absolute offset), takes into effect on next report of device.","name":"temperature_calibration","property":"temperature_calibration","type":"numeric"},{"access":2,"description":"Number of digits after decimal point for humidity, takes into effect on next report of device.","name":"humidity_precision","property":"humidity_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"Calibrates the humidity value (absolute offset), takes into effect on next report of device.","name":"humidity_calibration","property":"humidity_calibration","type":"numeric"}],"supports_ota":false,"vendor":"SONOFF"},"endpoints":{"1":{"bindings":[{"cluster":"msTemperatureMeasurement","target":{"endpoint":1,"ieee_address":"0x00124b001cce03b1","type":"endpoint"}},{"cluster":"msRelativeHumidity","target":{"endpoint":1,"ieee_address":"0x00124b001cce03b1","type":"endpoint"}},{"cluster":"genPowerCfg","target":{"endpoint":1,"ieee_address":"0x00124b001cce03b1","type":"endpoint"}}],"clusters":{"input":["genBasic","genIdentify","msTemperatureMeasurement","msRelativeHumidity","genPowerCfg"],"output":["genIdentify"]},"configured_reportings":[{"attribute":"measuredValue","cluster":"msTemperatureMeasurement","maximum_report_interval":1800,"minimum_report_interval":5,"reportable_change":20},{"attribute":"measuredValue","cluster":"msRelativeHumidity","maximum_report_interval":3600,"minimum_report_interval":10,"reportable_change":100},{"attribute":"batteryVoltage","cluster":"genPowerCfg","maximum_report_interval":62000,"minimum_report_interval":3600,"reportable_change":0},{"attribute":"batteryPercentageRemaining","cluster":"genPowerCfg","maximum_report_interval":62000,"minimum_report_interval":3600,"reportable_change":0}],"scenes":[]}},"friendly_name":"Temperatura2","ieee_address":"0x00124b0024ccf3d2","interview_completed":true,"interviewing":false,"manufacturer":"eWeLink","model_id":"TH01","network_address":1487,"power_source":"Battery","supported":true,"type":"EndDevice"}]

Status update from zigbee2mqtt/[FRIENDLY_NAME]
Messages published by this plugin that might be related to your issue (can also be seen in the homebridge logs)

Versions used
Please provide the version of the following pieces of software:

This plugin : Latest Version
Homebridge: Latest version
Zigbee2MQTT (can be found in MQTT topic zigbee2mqtt/bridge/info) :
Homebridge Config UI X (if applicable) : Latest Version  :

It is not real bug, as it update the Homebridge after movement was detected. it is good to update the documentation that change will not be applied until MQQT message/payload is posted.

Not real bug more documentation issue.


text:
Using the library like the cmdline

Hi,
I'm having difficulty reading how to use the library. I can use gojq in the shell just fine but I thought I'd dive into how you managed to do some things but I can't manage.
For instance:
echo '[{"how":"does", "this":"work"},{"how":"does", "this":"work"}]' | gojq '.[]' {   "how": "does",   "this": "work" } {   "how": "does",   "this": "work" }
I tried just following the example in the docs to this:
            body :=[{"how":"does", "this":"work"},{"how":"does", "this":"work"}]`
   query, err := gojq.Parse(".[]")
if err != nil {
	log.Error(err)
}
input := []interface{}{body}
iter := query.Run(input)
for {
	v, ok := iter.Next()
	if !ok {
		break
	}
	if err, ok := v.(error); ok {
		log.Error(err)
	}
	ioutil.WriteFile("tester.json", []byte(fmt.Sprint(v)), 0644)
	fmt.Printf("%#v\n", v)
}`

But this just prints out the same object.
Is there anyone who can offer some suggestions on what I'm doing wrong and if time permits where I should be looking in the package for why it doesn't work.

What you are doing is giving the JSON as a string input. You need to decode to an interface.
	var input interface{}
	json.Unmarshal([]byte(`[{"how":"does", "this":"work"},{"how":"does", "this":"work"}]`), &input)

@itchyny thanks, sorry it took long to reply, I overlooked that the interface{} was in fact just that (the new output with your edit in tester.json:)
map[string]interface {}{"how":"does", "this":"work"}  map[string]interface {}{"how":"does", "this":"work"}
I was trying to create a newline delimited JSON from an array that I'm GETting. I think this package is beyond my abilities at the moment.

You don't need to use gojq.
package main

import (
	"encoding/json"
	"fmt"
)

func main() {
	var input []interface{}
	json.Unmarshal([]byte(`[{"how":"does", "this":"work"},{"how":"does", "this":"work"}]`), &input)
	for _, x := range input {
		xs, _ := json.Marshal(x)
		fmt.Println(string(xs))
	}
}

Thank you @itchyny! That's really nice of you. I didn't think of using the interface, that helps make it more generic (which is why I was looking at gojq for an implementation of an iterator). I ended up doing this:
`
var ndJSONMarshalled []byte
var arrayOfStrings []string
var input []interface{}
err := json.Unmarshal([]byte(body), &input)
if err != nil {
..
}
for _, line := range input {
	s, err := json.Marshal(line)
	if err != nil {
		..
	}
	arrayOfStrings = append(arrayOfStrings, string(s))

}
newLineJSONString := strings.Join(arrayOfStrings, "\n")
newLineJSONBytes, err := ioutil.ReadAll(strings.NewReader(newLineJSONString))
if err != nil {
	..
}
ndJSONMarshalled = append(ndJSONMarshalled, newLineJSONBytes...)
// ioutil.WriteFile("tester.json", ndJSONMarshalled, 0644)

`
It works but it feels inefficient because I'm switching from strings to []byte so many times.

You don't need to ioutil.ReadAll(strings.NewReader to convert a string to bytes. Just []byte(str). Still allocation occurs though.
strings.Join is inefficient than using strings.Builder.
Anyway, building the JSON string (or bytes) allocates successive memory. You can write to the file.

package main

import (
	"encoding/json"
	"log"
	"os"
)

func main() {
	body := `[{"how":"does", "this":"work"},{"how":"does", "this":"work"}]`
	f, err := os.Create("test.json")
	if err != nil {
		log.Fatal(err)
	}
	var input []interface{}
	if err := json.Unmarshal([]byte(body), &input); err != nil {
		log.Fatal(err)
	}
	enc := json.NewEncoder(f)
	for _, x := range input {
		if err := enc.Encode(x); err != nil {
			log.Fatal(err)
		}
	}
}

Good luck.

Thank you so much! You're a hero! I'm going to investigate how this works.

authors: itchyny lukepon

repo: itchyny/gojq


text:
Persist lightning payment history

I've noticed that my lightning payment history disappeared after restarting. We should persist it.
Note: it probably is not needed for the purpose of the tournament, as we can demo all the functionality in a single run.

It's not persisted? 😲

It's not persisted? 😲

when I run it today, I noticed that my Friday's transactions were not visible 😕

I added the label, not sure this needs actioning?

@da-kami I removed the label, it does not need to be actioned for the demo, given we're doing everything from scratch there. It should be actioned afterwards.

It was not important for the demo, but crucial for any releases :-) otherwise the history is missing.

authors: bonomat da-kami klochowicz


text:
chore: format payment history

resolves #286
Before:

After:

bors r+

bors r+

authors: bonomat klochowicz