Simplified external control plane charts

Fixes #33455
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] 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 user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

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

Test name
Commit
Details
Rerun command

release-notes_istio
c83685e00c7fd2156ab74000f08f17f195cfc020
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.

@frankbu: 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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
c83685e00c7fd2156ab74000f08f17f195cfc020
link
/test release-notes_istio

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

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
c83685e00c7fd2156ab74000f08f17f195cfc020
link
/test release-notes_istio

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

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
c83685e00c7fd2156ab74000f08f17f195cfc020
link
/test release-notes_istio

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

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

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
c83685e00c7fd2156ab74000f08f17f195cfc020
link
/test release-notes_istio

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

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

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

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
c83685e00c7fd2156ab74000f08f17f195cfc020
link
/test release-notes_istio

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

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

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

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

integ-operator-controller-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test integ-operator-controller-tests_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
c83685e00c7fd2156ab74000f08f17f195cfc020
link
/test release-notes_istio

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

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

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

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

integ-operator-controller-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
c83685e00c7fd2156ab74000f08f17f195cfc020
link
/test release-notes_istio

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

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

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

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

integ-operator-controller-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test integ-operator-controller-tests_istio

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

release-test_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test release-test_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
c83685e00c7fd2156ab74000f08f17f195cfc020
link
/test release-notes_istio

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

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

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

integ-operator-controller-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test integ-operator-controller-tests_istio

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

release-test_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test release-test_istio

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

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
c83685e00c7fd2156ab74000f08f17f195cfc020
link
/test release-notes_istio

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

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

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

integ-operator-controller-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test integ-operator-controller-tests_istio

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

release-test_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test release-test_istio

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

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

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
c83685e00c7fd2156ab74000f08f17f195cfc020
link
/test release-notes_istio

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

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

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

integ-operator-controller-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test integ-operator-controller-tests_istio

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

release-test_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test release-test_istio

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

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

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

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
c83685e00c7fd2156ab74000f08f17f195cfc020
link
/test release-notes_istio

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

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

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

integ-operator-controller-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test integ-operator-controller-tests_istio

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

release-test_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test release-test_istio

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

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

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

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
c83685e00c7fd2156ab74000f08f17f195cfc020
link
/test release-notes_istio

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

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

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

integ-operator-controller-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test integ-operator-controller-tests_istio

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

release-test_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test release-test_istio

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

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

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

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

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
c83685e00c7fd2156ab74000f08f17f195cfc020
link
/test release-notes_istio

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

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

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

integ-operator-controller-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test integ-operator-controller-tests_istio

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

release-test_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test release-test_istio

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

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

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

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

unit-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test unit-tests_istio

lint_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
c83685e00c7fd2156ab74000f08f17f195cfc020
link
/test release-notes_istio

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

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

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

integ-operator-controller-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test integ-operator-controller-tests_istio

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

release-test_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test release-test_istio

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

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

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

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

unit-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test unit-tests_istio

lint_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test lint_istio

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

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
c83685e00c7fd2156ab74000f08f17f195cfc020
link
/test release-notes_istio

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

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

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

integ-operator-controller-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test integ-operator-controller-tests_istio

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

release-test_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test release-test_istio

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

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

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

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

unit-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test unit-tests_istio

lint_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test lint_istio

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

analyze-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
c83685e00c7fd2156ab74000f08f17f195cfc020
link
/test release-notes_istio

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

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

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

integ-operator-controller-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test integ-operator-controller-tests_istio

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

release-test_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test release-test_istio

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

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

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

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

unit-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test unit-tests_istio

lint_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test lint_istio

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

analyze-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test analyze-tests_istio

gencheck_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
c83685e00c7fd2156ab74000f08f17f195cfc020
link
/test release-notes_istio

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

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

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

integ-operator-controller-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test integ-operator-controller-tests_istio

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

release-test_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test release-test_istio

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

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

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

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

unit-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test unit-tests_istio

lint_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test lint_istio

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

analyze-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test analyze-tests_istio

gencheck_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test gencheck_istio

integ-helm-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test integ-helm-tests_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
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.

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

Test name
Commit
Details
Rerun command

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

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

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

integ-operator-controller-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test integ-operator-controller-tests_istio

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

release-test_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test release-test_istio

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

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

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

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

unit-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test unit-tests_istio

lint_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test lint_istio

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

analyze-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test analyze-tests_istio

gencheck_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test gencheck_istio

integ-helm-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test integ-helm-tests_istio

release-notes_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test release-notes_istio

integ-ipv6-k8s-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
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.

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

Test name
Commit
Details
Rerun command

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

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

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

integ-operator-controller-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test integ-operator-controller-tests_istio

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

release-test_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test release-test_istio

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

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

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

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

unit-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test unit-tests_istio

lint_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test lint_istio

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

analyze-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test analyze-tests_istio

integ-helm-tests_istio
b6abc17eff956556452d0e29eac582760ba7b2ed
link
/test integ-helm-tests_istio

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

gencheck_istio
a332ca13413f462ca293b96773f4bc7f94c1656a
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.

@frankbu: 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.

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

Test name
Commit
Details
Rerun command

gencheck_istio
a332ca13413f462ca293b96773f4bc7f94c1656a
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
c064ed38902715d58fc97750579113e6123da986
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.

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

Test name
Commit
Details
Rerun command

gencheck_istio
a332ca13413f462ca293b96773f4bc7f94c1656a
link
/test gencheck_istio

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

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a332ca13413f462ca293b96773f4bc7f94c1656a
link
/test gencheck_istio

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

unit-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a332ca13413f462ca293b96773f4bc7f94c1656a
link
/test gencheck_istio

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

unit-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test unit-tests_istio

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

release-test_istio
c064ed38902715d58fc97750579113e6123da986
link
/test release-test_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a332ca13413f462ca293b96773f4bc7f94c1656a
link
/test gencheck_istio

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

unit-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test unit-tests_istio

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

release-test_istio
c064ed38902715d58fc97750579113e6123da986
link
/test release-test_istio

integ-multicluster-k8s-tests_istio
c064ed38902715d58fc97750579113e6123da986
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.

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

Test name
Commit
Details
Rerun command

gencheck_istio
a332ca13413f462ca293b96773f4bc7f94c1656a
link
/test gencheck_istio

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

unit-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test unit-tests_istio

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

release-test_istio
c064ed38902715d58fc97750579113e6123da986
link
/test release-test_istio

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

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

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a332ca13413f462ca293b96773f4bc7f94c1656a
link
/test gencheck_istio

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

unit-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test unit-tests_istio

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

release-test_istio
c064ed38902715d58fc97750579113e6123da986
link
/test release-test_istio

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

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

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

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a332ca13413f462ca293b96773f4bc7f94c1656a
link
/test gencheck_istio

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

unit-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test unit-tests_istio

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

release-test_istio
c064ed38902715d58fc97750579113e6123da986
link
/test release-test_istio

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

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

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

integ-operator-controller-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test integ-operator-controller-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a332ca13413f462ca293b96773f4bc7f94c1656a
link
/test gencheck_istio

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

unit-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test unit-tests_istio

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

release-test_istio
c064ed38902715d58fc97750579113e6123da986
link
/test release-test_istio

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

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

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

integ-operator-controller-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test integ-operator-controller-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a332ca13413f462ca293b96773f4bc7f94c1656a
link
/test gencheck_istio

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

unit-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test unit-tests_istio

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

release-test_istio
c064ed38902715d58fc97750579113e6123da986
link
/test release-test_istio

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

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

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

integ-operator-controller-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test integ-operator-controller-tests_istio

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

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

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a332ca13413f462ca293b96773f4bc7f94c1656a
link
/test gencheck_istio

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

unit-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test unit-tests_istio

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

release-test_istio
c064ed38902715d58fc97750579113e6123da986
link
/test release-test_istio

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

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

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

integ-operator-controller-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test integ-operator-controller-tests_istio

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

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

integ-helm-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test integ-helm-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a332ca13413f462ca293b96773f4bc7f94c1656a
link
/test gencheck_istio

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

unit-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test unit-tests_istio

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

release-test_istio
c064ed38902715d58fc97750579113e6123da986
link
/test release-test_istio

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

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

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

integ-operator-controller-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test integ-operator-controller-tests_istio

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

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

integ-helm-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test integ-helm-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a332ca13413f462ca293b96773f4bc7f94c1656a
link
/test gencheck_istio

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

unit-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test unit-tests_istio

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

release-test_istio
c064ed38902715d58fc97750579113e6123da986
link
/test release-test_istio

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

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

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

integ-operator-controller-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test integ-operator-controller-tests_istio

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

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

integ-helm-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test integ-helm-tests_istio

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

analyze-tests_istio
c064ed38902715d58fc97750579113e6123da986
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.

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

Test name
Commit
Details
Rerun command

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

unit-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test unit-tests_istio

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

release-test_istio
c064ed38902715d58fc97750579113e6123da986
link
/test release-test_istio

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

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

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

integ-operator-controller-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test integ-operator-controller-tests_istio

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

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

integ-helm-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test integ-helm-tests_istio

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

analyze-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test analyze-tests_istio

gencheck_istio
c064ed38902715d58fc97750579113e6123da986
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.

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

Test name
Commit
Details
Rerun command

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

unit-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test unit-tests_istio

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

release-test_istio
c064ed38902715d58fc97750579113e6123da986
link
/test release-test_istio

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

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

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

integ-operator-controller-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test integ-operator-controller-tests_istio

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

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

integ-helm-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test integ-helm-tests_istio

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

analyze-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test analyze-tests_istio

gencheck_istio
c064ed38902715d58fc97750579113e6123da986
link
/test gencheck_istio

release-notes_istio
c064ed38902715d58fc97750579113e6123da986
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.

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

Test name
Commit
Details
Rerun command

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

unit-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test unit-tests_istio

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

release-test_istio
c064ed38902715d58fc97750579113e6123da986
link
/test release-test_istio

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

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

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

integ-operator-controller-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test integ-operator-controller-tests_istio

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

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

integ-helm-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test integ-helm-tests_istio

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

analyze-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test analyze-tests_istio

gencheck_istio
c064ed38902715d58fc97750579113e6123da986
link
/test gencheck_istio

release-notes_istio
c064ed38902715d58fc97750579113e6123da986
link
/test release-notes_istio

lint_istio
c064ed38902715d58fc97750579113e6123da986
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

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

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

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

Test name
Commit
Details
Rerun command

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

unit-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test unit-tests_istio

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

release-test_istio
c064ed38902715d58fc97750579113e6123da986
link
/test release-test_istio

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

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

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

integ-operator-controller-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test integ-operator-controller-tests_istio

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

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

integ-helm-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test integ-helm-tests_istio

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

analyze-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test analyze-tests_istio

gencheck_istio
c064ed38902715d58fc97750579113e6123da986
link
/test gencheck_istio

release-notes_istio
c064ed38902715d58fc97750579113e6123da986
link
/test release-notes_istio

lint_istio
c064ed38902715d58fc97750579113e6123da986
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

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

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

unit-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test unit-tests_istio

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

release-test_istio
c064ed38902715d58fc97750579113e6123da986
link
/test release-test_istio

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

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

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

integ-operator-controller-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test integ-operator-controller-tests_istio

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

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

integ-helm-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test integ-helm-tests_istio

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

analyze-tests_istio
c064ed38902715d58fc97750579113e6123da986
link
/test analyze-tests_istio

gencheck_istio
c064ed38902715d58fc97750579113e6123da986
link
/test gencheck_istio

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

lint_istio
2ef873d9606cef2b4d2b6225a2b405a3c287caf7
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
5cc9c3e2b52d0441c549cb1b11430b4eefbdfc1a
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.


Support AltTester >= 2.0.0

Hey, this plugin is a great project but unfortunately it does not work with AltTester version >= 2.0.0
I also tried running
adb forward tcp:13000 tcp:13000
websocat ws://<IP_ADDRESS>:13000/altws/
# Result is:
# websocat: WebSocketError: WebSocket protocol error
# websocat: error running

I assume AltTester introduced breaking changes in the internal communication protocol.

Is there a plan to support version >= 2.0.0?
Are you familiar with the changes and can share here, so I can try tweaking a development version of the plugin that will work with it?

Thanks

I think the changes in Alttester are as you said huge, one of them is the introduction of Alttester desktop server, which will handle the communication between the drivers(tests) and the unitysdk applicaton(instrumented app), in the past the socket connection was direct from the driver to the app, so there is a need to consider the newly introduced server. I am enthusiastic about game testing and I would really give a hand in the maintenance of this plugin , so i can help with what i could ever do.

@ramybenaroya


Drop support for Ruby 2.3

Targeting Ruby 2.4 does not change anything to the current codebase.

@jekyllbot: merge +dev


Default layout navigation bar

Describe the task
Add a navigation bar as shown in the UI designs

Looks good @matthieu-foucault ! I did notice that projects and operators are reversed in comparison to the UI Design, but that makes sense as projects will be used more often.

@LindsayMacfarlane Doesn't really matter to me if it's a hassle to change, but the navbar was intentionally laid out to go from general to specific (Dashboard, Operators, Projects, Contacts) and then Admin bookended as the last.


Repo not releasable

no hack/release.sh
no test-infra automation.

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale
@n3wscott what can be done here pls?

We added hack/release.sh and test-infra automation. So closing this.


about SAM-det and SAM-cls

Nice work. In the results table, it was not mentioned the details about the implementations of SAM-det and SAM-cls, any reference？

SAM-det: First using Faster-RCNN to detect; then using the box as a prompt for segmentation
SAM-cls: First using "everything" mode to segment anything; then use resnet18 (trained with label) to classify
For more detail, please refer to our codes.
SAM-det: https://github.com/KyanChen/RSPrompter/blob/cky/configs/rsprompter/samdet_fasterrcnn_whu_config.py
SAM-csl: https://github.com/KyanChen/RSPrompter/blob/cky/tools/ins_seg/sam/sam_cls/get_sam_cls_crops.py


+layout.svelte  was created with unknown prop 'data'

Describe the bug
I saw following warning in chrome devtools:
+layout.svelte <Layout> was created with unknown prop 'data'

The code is like this:
<script>
  import {afterUpdate} from 'svelte';
  // ..

  let loginNick
  afterUpdate(async () => {
    loginNick = sessionStorage.getItem('nick'); // The warning is on this line,
  });
</script>

Any idea ?
Reproduction
Just add code above, and refresh the page, and in chrome devtools, could see the warning.
Logs
No response
System Info
System:
    OS: Linux 5.14 Linux Mint 20.1 (Ulyssa)
    CPU: (8) x64 Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz
    Memory: 250.66 MB / 15.55 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v16.13.1/bin/yarn
    npm: 8.17.0 - ~/.nvm/versions/node/v16.13.1/bin/npm
  Browsers:
    Chrome: 104.0.5112.79
  npmPackages:
    @sveltejs/adapter-auto: next => 1.0.0-next.64
    @sveltejs/kit: next => 1.0.0-next.422
    svelte: ^3.49.0 => 3.49.0
    vite: ^3.0.8 => 3.0.8

Severity
Not urgent.
Additional Information
No response

You're on Kit 1.0.0-next.422. This should already be fixed on the latest version - https://github.com/sveltejs/kit/blob/master/packages/kit/CHANGELOG.md - Please make sure you are using the latest version before opening issues.

Cool, upgrade to 1.0.0-next.427, then there is no such warning.

@Conduitry
It seems there warning can still pop-out when start in dev mode:

If I refresh the page, these warning are not shown.
But, If I change some code, and vite did hot update, then such warning seems still shown, e.g

[vite] hot updated: /src/components/YesNoDialog.svelte
+layout.svelte:15 <Layout> was created with unknown prop 'data'
+layout.svelte:32 <Layout> was created with unknown prop 'data'
+page.svelte:24 <Page> was created with unknown prop 'data'
+page.svelte:24 <Page> was created with unknown prop 'errors'

With "@sveltejs/kit": "^1.0.0-next.468" git the warning too. I've got the feeling it has to do with the fact that might layout use await
{#await i18n.init() then}
  <slot />
{/await}


feat(utilities): processor for SNS events

Issue #, if available:
Description of changes:
Simple SNSProcessor to handle incoming SNS events
Checklist

[x] Meet tenets criteria
[x] Update tests
[ ] Update docs
[x] PR title follows conventional commit semantics

Breaking change checklist

RFC issue #:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #163 into develop will decrease coverage by 0.32%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop     #163      +/-   ##
===========================================
- Coverage   100.00%   99.67%   -0.33%
===========================================
  Files           33       34       +1
  Lines          918      927       +9
  Branches        77       78       +1
===========================================
+ Hits           918      924       +6
- Misses           0        3       +3

Impacted Files
Coverage Δ

aws_lambda_powertools/utilities/batch/__init__.py
100.00% <100.00%> (ø)

aws_lambda_powertools/utilities/batch/sns.py
100.00% <100.00%> (ø)

aws_lambda_powertools/tracing/extensions.py
25.00% <0.00%> (-75.00%)
:arrow_down:

aws_lambda_powertools/logging/logger.py
100.00% <0.00%> (ø)

aws_lambda_powertools/tracing/tracer.py
100.00% <0.00%> (ø)

aws_lambda_powertools/metrics/metrics.py
100.00% <0.00%> (ø)

aws_lambda_powertools/logging/formatter.py
100.00% <0.00%> (ø)

aws_lambda_powertools/utilities/batch/base.py
100.00% <0.00%> (ø)

...ws_lambda_powertools/middleware_factory/factory.py
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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

I always seem to have think of an additional angle after I submit stuff, but I think it makes sense to not do an SNS specific processor but a records specific one.
This allows you to do the same for example with S3 events without the need of an additional processor.

Hey @Nr18 could you write a RFC on this to allow for discussion first?
At a first glance, SNS only sends a single record despite its data structure allowing for more

Hey @Nr18 could you write a RFC on this to allow for discussion first?
At a first glance, SNS only sends a single record despite its data structure allowing for more

Based on this kind of thing i have added convenience methods to PR: https://github.com/awslabs/aws-lambda-powertools-python/pull/159
event = SNSEvent(event)
# Return the message for the first sns event record
message = event.sns_message

Closing this PR as #159 would cover the same functionality.


Caching julia shape tuple type and array type

At the moment, jltensor::init_tensor which initializes a jltensor from C++ creates the julia type for the shape on the fly.
This should be done only once.

Fixed in jltensor.


feat: add flutter and widget related macros

Partially fixes #14

Macro execution doesn't appear to work in Flutter yet, but this is working in Dart-only for basic cases as far as I can tell.
Only thing that is broken is default values for named parameters, but those appear to be unimplemented by the macro system at the moment.

The widget macros, which were the scope of this PR, are essentially done, at least to the best of what I can do right now with the current macros implementation. Just need to wait until macros are implemented further before I can clean this up more.

Looks like quite a bit changed in the macros implementation since the last actual commit--need to bring this up to speed again.

 See the extension _Substitute on String if you're making your own macros.
This time I had to test in packages/rearch since Flutter support isn't there yet. For future reference, needed this type boilerplate:
abstract class BuildContext {
  T dependOnInheritedWidgetOfExactType<T>();
}

abstract class Widget {
  const Widget({Object? key,});
}

abstract class WidgetHandle {}

abstract class RearchConsumer extends Widget {
  const RearchConsumer({super.key,});
  Widget build(BuildContext context, WidgetHandle use);
}
abstract class InheritedWidget extends Widget {
  const InheritedWidget({required Widget child,super.key,});
}
extension A on WidgetHandle {
  (T, void Function(T)) state<T>(T init) => throw '';
}


How to deal with lack of individual data types for Submodel Element Collections?

In the AAS you define Submodel Elements (simple as well as complex), but no individual data types for them. If we now consider, for example, a complex "location" Submodel Element Collection with simple double properties for the coordinates. Then one must assign individual semanticIds to this kind of construct depending on the usage to allow an individual, context-dependent meaning of the SMEC. Example: A robot has a location SMEC for its base and one for its tool center point. Both should be described by individual semanticIds (i.e., concept descriptions). On the other hand, both describe locations, which should be able to be offset against each other in generic program code (e.g., calculate distance of the locations). How is this possible without a common data type "Location" for both SMEC?

Relevant Issue: https://github.com/admin-shell-io/questions-and-answers/issues/44

18.12.2023 Best Practice Group:
We recommend:

Use the individual semanticID for the individual SMC to denote "location at base" or "locaction tool center point"
Use supplementalSemanticID to descibe for each SMC that it is a "location".
For the ConceptDescription it is similiar. Create 2 ConceptDescriptions for the individual SMC, and use isCaseOf to reference a 3rd ConceptDescription for "location".


Custom roles link is broken

The link for "custom roles" is broken: https://docs.microsoft.com/en-us/azure/role-based-access-control/custom-roles.md
This might be because the feature has not been implemented during the preview yet or the link is wrong. If there is just no material yet, I suggest removing the link and clarifying that custom roles are not available yet.

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

ID: 1ca94e03-5f05-6703-1672-8062f31c0780
Version Independent ID: a6a8d9e9-9aac-c0ed-c474-34cbd0609584
Content: Use RBAC to manage access rights to Azure Storage containers and queues (Preview)
Content Source: articles/storage/common/storage-auth-aad-rbac.md
Service: storage
GitHub Login: @tamram
Microsoft Alias: tamram

@pythianchaves - Thanks for reporting this broken link. I've fixed it and it should go live shortly.
#please-close

Thanks @tamram We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Fix internal error on getflag when putflag data missing

Could also just catch KeyError since that is the only one that seems to be thrown but the other code already present just catches Exception so I matched that.
See also here.

This bug should be found by enochecker_test, right?

This bug should be found by enochecker_test, right?

it should be found, but it isn't being found :D


🏑Unify the parameters order and default value of dummy dataset

Describe your changes
Checklist before requesting a review

[ ] Add unit tests for this change.
[ ] Make sure all tests can pass.
[ ] Update documents if necessary.
[ ] Format your code by running pre-commit run --all-files
[ ] Is this a user-facing change? If yes, give a description of this change to be included in the release notes.

(Optional) Issue link

better to raise error when the docker run failure since the error like following is a little bit confusing.

better to raise error when the docker run failure since the error like following is a little bit confusing.

Will update in follow-up PR.


Windows machine locks up presumably if network hiccup occurs

Technical data
WinSshFS

[x] stable
[ ] prerelease
[ ] custom build
Version: <IP_ADDRESS>

Dokan driver

[x] stable
[ ] prerelease
[ ] custom build
Version: Dokany <IP_ADDRESS>

Enviroment

Windows version: 10
Architecture: x64
Related software: <Windows Explorer/Sublime Text 3>

Support

Usage: personal - production
Your personal priority to solve this issue: high
Support ability: <can create pull request / investigate driver issues / log anything>

 I am connected remotely to a machine that on occasion has network hiccups.  Putty can SSH just fine, sometimes it stops responding, but then it picks back up again. No worries.
However, when that happens and I have a drive connected with win-sshfs, it freezes, and if I have a file open in Sublime Text (located on remote machine, in remote drive), it freezes.  I cannot End Process on either program.  Windows Explorer will choke and die if I try to navigate to the remote drive.
I've replicated this issue with both Dokan 1.0.1 and 1.0.3, and win-sshfs <IP_ADDRESS> and <IP_ADDRESS>
The only way to resolve the issue is to force a reboot!  :(

I can replicate the sublime text part of this 100%, am staring at a dead Sublimetext process that i can close as we speak. I can still, however, browse the remote drive via explorer.

What build of Windows 10 are you running?

15063

Okay, most likely unrelated to #152 then

I bet it's related, but the Creator's Update seems to have made it even worse... Symptoms are exactly the same.  Zero Windows Explorer interaction possible.  I can click in Chrome or whatever, but I can't use the taskbar, etc.  Can't "End Process" for Win SSH-FS either.

i would blame Windows for this one... i have similar problems even with SMB shares, if i have it permanently mounted as network drive and it goes offline, it will make explorer completelly unusable for like a minute, becouse it's waiting for response and it does this even if you're just moving some files around and hover your mouse, while draging a file, over it's icon... so this may be similar issue
speaking from experience, idk for sure tho


[luajit] Fix cross compile for macOS

Describe the pull request

What does your PR fix?

Fix #28848

@xiaozhuai We would really appreciate you plumbing in cross support correctly but I'm going to merge this as is for now. Thank you!


fix(recipe):No more memory leak when ChildrenWatch was stopped

Remove session watcher from the listener when ChildrenWatch was stopped

@kulallwang thanks again for your PR, this is now on master.


could not find a satisfactory version for string beta

{   "message": "could not find a satisfactory version for string beta" }
To reproduce, try visualizing @salesforce/command.

I am seeing something similar: https://npm.anvaka.com/#/view/2d/signalk-server

and the process stops.
So it seems like something off somewhere kills the traversal. Could this be made more robust? Is there a way to add logging to figure out where and what exactly fails? npm installs work ok, so it's not like things are actually broken.


Add inputProps to support adding html input attributes

https://github.com/vutoan266/react-images-uploading/issues/71

unit test would be needed

unit test would be needed


Design update - secondary button with icon - Wagtail Design System

Good first issue for someone confident with SCSS/CSS

Is your proposal related to a problem?

There is not yet a officially supported button with icon that aligns with the secondary button styles (outline only button)
If button-secondary is applied to the current bicolor button styles, it works but should align with the new official Wagtail Design System

Describe the solution you'd like

[ ] Add support for the with icon (secondary, aka ghost) buttons as per the design system Figma
[x] Add new variants using .button-secondary with bicolor button-icon in the styleguide https://github.com/wagtail/wagtail/blob/main/wagtail/contrib/styleguide/templates/wagtailstyleguide/base.html
[x] Add new variants using .button-secondary with bicolor button-icon in the pattern library https://github.com/wagtail/wagtail/blob/main/wagtail/admin/templates/wagtailadmin/shared/button.stories.tsx
[ ] Add styles for these variants in https://github.com/wagtail/wagtail/blob/main/client/scss/components/_button.scss
[ ] Must work in all supported browsers https://docs.wagtail.org/en/stable/contributing/developing.html#browser-and-device-support

Normal size button-secondary with icon
Very similar to the bicolor currently but with different colours, must support all existing supported DOM elements for buttons (a, button, and input[submit).

Default
Hover
Disabled
Focus state (existing global focus outline)

Normal size button-secondary with icon
When small and secondary the border is dropped, must support all existing supported DOM elements for buttons (a, button, and input[submit).

Default
Hover
Disabled (not shown)
Focus state (existing global focus outline)

Describe alternatives you've considered
Leave as current state and do not document .button-secondary when used with .bicolor.

button bicolor button--icon button-secondary
button bicolor button--icon button-secondary button-small

Additional context

The bulk of the original button designs issue was completed via https://github.com/wagtail/wagtail/issues/8790
As this button type was not officially supported or used, it ended up being out of scope.

Marking as good first issue - split from https://github.com/wagtail/wagtail/issues/8790
@thibaudcolas  please have a read when you get the chance.

Hi, I am new to the Wagtail codebase. I would like to work on this design issue. Could someone please help me out with the directory of the css source files?
Also, I quite didn't understand what the issue really is. Any help would be very helpful. Thanks!

@Adinapunyo-Banerjee the issue description clearly calls out exactly what file to update with the new styles.
Maybe a different good first issue might be more suitable - but have a full read of the description again and see how you go.

Okay, thanks!

@lb- Hey, I have been trying to work on this issue. The UI Styleguide seems to be static and making changes to the base.html does not reflect on the style guide (as mentioned in the UI Styleguide https://docs.wagtail.org/en/latest/contributing/styleguide.html documentation).

When I change "Contents" to "Contents SHOULD CHANGE"

It does not reflect.
How do I make changes to this page and review it?
(Might be a dumb question)

@Adinapunyo-Banerjee It's possible that your Python environment is still running a copy of Wagtail that's been installed as a package (with pip install wagtail), rather than the one you checked out from Github. Try running pip freeze - if the output includes a line like Wagtail==4.0.1 then it's running a packaged version. If so, run the following from the wagtail folder where you checked out the Wagtail codebase:
pip uninstall Wagtail
pip install -e .[testing,docs]

Thanks @gasman, I realized what the problem was. Could have directly worked on the Wagtail package.

Hello Sir/Madam, I would like to contribute to this issue.

@rydanstar01 thank you for offering.
Just above your comment, there is a reference to #9243 which is a PR that aims to address this. So the best way to contribute is to test that PR and add your feedback on it.

Partial work completed - pattern library & styleguide have been updated via https://github.com/wagtail/wagtail/pull/9243
Thanks @Adinapunyo-Banerjee

Hi @lb-, @Adinapunyo-Banerjee is this issue assigned to anyone or I can go on and work on it

Hi @lb-, I have finished working on this issue. I am kindly asking for your review and suggestions on how to improve.
Thanks  a lot


nn.PNAConv for Undirected Graph?

❓ Questions & Help

The Example provided in here gives the Degree Calculation of Nodes in a Directed Graph. What should be the case for an undirected Graph?
Code for reference from examples\pna.py.
for data in train_dataset:
    d = degree(data.edge_index[1], num_nodes=data.num_nodes, dtype=torch.long)
    deg += torch.bincount(d, minlength=deg.numel())

In PyG, each undirected graph is a directed graph for which all reverse edges exist. Therefore, you do not have to modify the code in case your graphs are undirected.


Error trying to load accuracy metric

I'm trying to train a GPT-2 model using example scripts and I get an error when the scripts tries to load 'accuracy' metric:
evaluate.load("accuracy")
File "/home/carlos/miniconda3/lib/python3.10/site-packages/evaluate/loading.py", line 752, in load
evaluation_instance = evaluation_cls(
TypeError: 'NoneType' object is not callable
I tried to load other metrics and I only get error with accuracy
I've got installed the requirements:
scikit-learn              1.3.dev0
evaluate                  0.4.1.dev0
I'm running the run_clm.py script for language modeling.
Is there something I need to install besides scikit and evaluate? Is there something wrong with the library?
Thanks!

I solved reinstalling os, conda and libraries again.
I don't know where it was the error exactly, I was using Ubuntu 22.04 and python 3.10. Working in Ubuntu with python 3.9


Roots can not find CSS and JS files

Hello! I really like Roots and would love to tinker around but Ive gotten a small problem at hands. I have a fresh WP 3.3.2 installation and latest Roots cloned from here but after installation, it does not find the CSS and JS files declared in head.
I am not sure what the issue could be but Im sure Im not the only one. Anyone has any helpful information?

I struggled with this for half a day...
I work with Mamp and I was always working from sub directories, until i learned creating a virtual host per site.

Make sure you add a virtual host to your Mamp workflow.
Do Roots 101.

I had a similar issue, and after doing everything in this thread, it still wasn't working. Then I noticed my .htaccess was a little... verbose. So the Permalinks flush does NOT completely overwrite your .htaccess, it appends the Wordpress section and rewrites only that section. If you had copied in an .htaccess file from another project due to a boilerplate situation, or had written in anything that might interfere, Permalinks flushing will not cure the problem. Clear the other stuff out and it should work. Did for me.

Might be worth mentioning that I came across this exact same problem, only the reason that the assets weren't appearing is that I hadn't yet gulp'd. Doh.


Remove the hanging comma on the title of the JHU metadata page

https://github.com/OA-PASS/pass-ember/pull/186


Error if  is present in HTML

This problem can be reproduced as
from pattern3.web import document
ss='''<!DOCTYPE html>'''
aaz=Document(ss)
aaz.children

gives an error

Traceback (most recent call last):
File "", line 1, in
File "/home/user/anaconda3/lib/python3.6/site-packages/pattern3/web/init.py", line 3580, in getattr
raise AttributeError("'Element' object has no attribute '%s'" % k)
AttributeError: 'Element' object has no attribute 'children'

Updating the string to ss='''''' do not gives error.

@rock321987 I've tried to replicate the error using Docker ubuntu:18.04 image:
root@a3506a595f72:~# uname -ar
Linux a3506a595f72 4.14.33+ #1 SMP Sat Aug 11 08:05:16 PDT 2018 x86_64 x86_64 x86_64 GNU/Linux

One difference is that the import entrypoint is pattern and not pattern3:
root@a3506a595f72:~# pip3 install pattern
Requirement already satisfied: pattern in /usr/local/lib/python3.6/dist-packages
Requirement already satisfied: backports.csv in /usr/local/lib/python3.6/dist-packages (from pattern)
Requirement already satisfied: numpy in /usr/local/lib/python3.6/dist-packages (from pattern)
Requirement already satisfied: feedparser in /usr/local/lib/python3.6/dist-packages (from pattern)
Requirement already satisfied: lxml in /usr/local/lib/python3.6/dist-packages (from pattern)
Requirement already satisfied: beautifulsoup4 in /usr/local/lib/python3.6/dist-packages (from pattern)
Requirement already satisfied: requests in /usr/local/lib/python3.6/dist-packages (from pattern)
Requirement already satisfied: future in /usr/local/lib/python3.6/dist-packages (from pattern)
Requirement already satisfied: scipy in /usr/local/lib/python3.6/dist-packages (from pattern)
Requirement already satisfied: pdfminer.six in /usr/local/lib/python3.6/dist-packages (from pattern)
Requirement already satisfied: python-docx in /usr/local/lib/python3.6/dist-packages (from pattern)
Requirement already satisfied: mysqlclient in /usr/local/lib/python3.6/dist-packages (from pattern)
Requirement already satisfied: nltk in /usr/local/lib/python3.6/dist-packages (from pattern)
Requirement already satisfied: cherrypy in /usr/local/lib/python3.6/dist-packages (from pattern)
Requirement already satisfied: chardet<3.1.0,>=3.0.2 in /usr/local/lib/python3.6/dist-packages (from requests->pattern)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.6/dist-packages (from requests->pattern)
Requirement already satisfied: urllib3<1.25,>=1.21.1 in /usr/local/lib/python3.6/dist-packages (from requests->pattern)
Requirement already satisfied: idna<2.8,>=2.5 in /usr/lib/python3/dist-packages (from requests->pattern)
Requirement already satisfied: six in /usr/lib/python3/dist-packages (from pdfminer.six->pattern)
Requirement already satisfied: pycryptodome in /usr/local/lib/python3.6/dist-packages (from pdfminer.six->pattern)
Requirement already satisfied: sortedcontainers in /usr/local/lib/python3.6/dist-packages (from pdfminer.six->pattern)
Requirement already satisfied: singledispatch in /usr/local/lib/python3.6/dist-packages (from nltk->pattern)
Requirement already satisfied: cheroot>=6.2.4 in /usr/local/lib/python3.6/dist-packages (from cherrypy->pattern)
Requirement already satisfied: zc.lockfile in /usr/local/lib/python3.6/dist-packages (from cherrypy->pattern)
Requirement already satisfied: more-itertools in /usr/local/lib/python3.6/dist-packages (from cherrypy->pattern)
Requirement already satisfied: portend>=2.1.1 in /usr/local/lib/python3.6/dist-packages (from cherrypy->pattern)
Requirement already satisfied: backports.functools-lru-cache in /usr/local/lib/python3.6/dist-packages (from cheroot>=6.2.4->cherrypy->pattern)
Requirement already satisfied: setuptools in /usr/lib/python3/dist-packages (from zc.lockfile->cherrypy->pattern)
Requirement already satisfied: tempora>=1.8 in /usr/local/lib/python3.6/dist-packages (from portend>=2.1.1->cherrypy->pattern)
Requirement already satisfied: jaraco.functools>=1.20 in /usr/local/lib/python3.6/dist-packages (from tempora>=1.8->portend>=2.1.1->cherrypy->pattern)
Requirement already satisfied: pytz in /usr/local/lib/python3.6/dist-packages (from tempora>=1.8->portend>=2.1.1->cherrypy->pattern)
root@a3506a595f72:~# python3
Python 3.6.7 (default, Oct 22 2018, 11:32:17)
[GCC 8.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from pattern.web import Document
>>> ss='''<!DOCTYPE html>'''
>>> ss
'<!DOCTYPE html>'
>>> aaz=Document(ss)
>>> aaz.children
[Text('html'), Element(tag='html')]
>>>

Otherwise the parse was fine without error. How did you build/install pattern module locally?

Yeah. You are right. The pattern3 library I used was different. I used the dev branch from pattern library and it worked for me. At the time I was using it, it wasn't available on pip.


report file inconsistent with stdout log, contains entries that are both SKIPPED and OK

Using the --report parameter, I get a lot of entries in the SKIPPED section of the report file, sometimes multiple times, that are all also reported as OK or REPLACED. Excerpt:
OK:meta/curl/7.44.0-r0
OK:meta/libcap/2.24-r0
REPLACED:ORIG=meta/python/2.7.9-r0 REPLACEMENT=meta-debian/python/2.7.9: Recipe and version exist in KB, but not within the layer
SKIPPED:Component meta/curl/7.44.0-r0: Recipe missing from bitbake-layers output
SKIPPED:Component meta/libcap/2.24-r0: Recipe missing from bitbake-layers output
SKIPPED:Component meta/libcap/2.24-r0: Recipe missing from bitbake-layers output
SKIPPED:Component meta/libcap/2.24-r0: Recipe missing from bitbake-layers output
SKIPPED:Component meta/libcap/2.24-r0: Recipe missing from bitbake-layers output
SKIPPED:Component meta/python/2.7.9-r0: Recipe missing from bitbake-layers output
SKIPPED:Component meta/python/2.7.9-r0: Recipe missing from bitbake-layers output
SKIPPED:Component meta/python/2.7.9-r0: Recipe missing from bitbake-layers output
SKIPPED:Component meta/python/2.7.9-r0: Recipe missing from bitbake-layers output

These recipes are NOT reported as skipped in the stdout log. Instead, the stdout log has SKIPPED entries with recipes that are proprietary and reported as MISSSING in the report file

I am unable to recreate this issue - but have reworked the loop logic so hopeful that the duplicate messages will not be seen for this configuration.
Please test against v2.2.


Error: creating ECS Capacity Provider (default): ClientException: The specified capacity provider already exists.

Description
Please provide a clear and concise description of the issue you are encountering, and a reproduction of your configuration (see the examples/* directory for references that you can copy+paste and tailor to match your configs if you are unable to copy your exact configuration). The reproduction MUST be executable by running terraform init && terraform apply without any further changes.
If your request is for a new feature, please use the Feature request template.
When trying to provision a ECS cluster using:

ec2 autoscaling
launch template
spot instances

It applies with no issue the first time. However, on apply again to update changes in the configuration, i get the following error
╷ │ Error: Reference to undeclared module │  │   on ini_ecs.tf line 23, in module "ecs_cluster": │   23:       auto_scaling_group_arn         = module.asg.autoscaling_group_arn │  │ No module call named "asg" is declared in the root module. ╵
I have nuked the .terraform directory and tried from a clean state, but the error persists

[ X ] ✋ I have searched the open/closed issues and my issue is not listed.

Versions

Module version [Required]:

Terraform version: v1.5.1

Provider version(s): v5.5.0

Reproduction Code [Required]
ini_ecs.tf
module "ecs_cluster" {
  source  = "terraform-aws-modules/ecs/aws//modules/cluster"
  # modules/cluster
  version = "5.2.0"

  cluster_name = local.base_name

  create_cloudwatch_log_group = false

  default_capacity_provider_use_fargate = false
  autoscaling_capacity_providers = {
    default = {
      auto_scaling_group_arn         = module.asg.autoscaling_group_arn
      managed_termination_protection = "DISABLED"

      # ecs manages scaling
      managed_scaling = {
        maximum_scaling_step_size = 5
        minimum_scaling_step_size = 1
        status                    = "ENABLED"
        target_capacity           = 50
      }

    }
  }

  tags = local.tags
}

ini_asg.tf
module "asg" {
  source  = "terraform-aws-modules/autoscaling/aws"
  version = "6.10.0"

  # Autoscaling group
  name = local.base_name
  use_name_prefix = true
  ignore_desired_capacity_changes = false

  min_size                  = 0
  max_size                  = 1
  desired_capacity          = 1
  wait_for_capacity_timeout = 0
  health_check_type         = "EC2"
  vpc_zone_identifier       = data.aws_subnets.private.ids

  initial_lifecycle_hooks = [
    {
      name                  = "ExampleStartupLifeCycleHook"
      default_result        = "CONTINUE"
      heartbeat_timeout     = 60
      lifecycle_transition  = "autoscaling:EC2_INSTANCE_LAUNCHING"
      notification_metadata = jsonencode({ "hello" = "world" })
    },
    {
      name                  = "ExampleTerminationLifeCycleHook"
      default_result        = "CONTINUE"
      heartbeat_timeout     = 180
      lifecycle_transition  = "autoscaling:EC2_INSTANCE_TERMINATING"
      notification_metadata = jsonencode({ "goodbye" = "world" })
    }
  ]

  instance_refresh = {
    strategy = "Rolling"
    preferences = {
      #checkpoint_delay       = 600
      #checkpoint_percentages = [35, 70, 100]
      #instance_warmup        = 300 # replace with lifecycle hook
      min_healthy_percentage = 90 # check
    }
    triggers = ["tag"] # check
  }

  # Launch template
  launch_template_name        = "ecs-${local.base_name}"
  launch_template_use_name_prefix = true
  launch_template_description = "ECS launch template"
  update_default_version      = true

  image_id          = local.ami_id
  instance_type     = var.instance_type
  ebs_optimized     = true # check
  enable_monitoring = true

  # IAM role & instance profile
  create_iam_instance_profile = true
  iam_role_name               = "ecs-${local.base_name}"
  iam_role_path               = "/ec2/"
  iam_role_description        = "ECS role for cluster: ${var.product} ${var.env}"
  iam_role_tags = {Name = "ecs-${local.base_name}"}
  iam_role_policies = {
    AmazonSSMManagedInstanceCore = "arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore"
  }

  block_device_mappings = [
    {
      # Root volume
      device_name = "/dev/xvda"
      no_device   = 0
      ebs = {
        delete_on_termination = true # check if we can reuse instead?
        encrypted             = true
        volume_size           = 50 # check
        volume_type           = "gp2" # check
      }
    }
  ]

  capacity_reservation_specification = {
    capacity_reservation_preference = "open"
  }

  instance_market_options = {
    market_type = "spot"
    spot_options = {
      instance_interruption_behavior = "terminate" # check
      #max_price                      = "one-time" # check
      spot_instance_type = "one-time"
      #spot_instance_type             = ??? # check - i think this should be disabled as it would then default to th eon-demand price
      #valid_until                    = ??? # check - not sure at the mo
    }
  }

  metadata_options = {
    http_endpoint               = "enabled"
    http_tokens                 = "required"
    http_put_response_hop_limit = 32
  }

  network_interfaces = [
    {
      delete_on_termination = true
      description           = "eth0"
      device_index          = 0
      security_groups       = [module.ecs_sg.security_group_id] # TODO: add default
    }
  ]

  placement = {
    availability_zone = var.region
  }

  tags = local.tags
}

ini_security_groups.tf
module "ecs_sg" {
  source  = "terraform-aws-modules/security-group/aws"
  version = "5.1.0"

  name        = local.base_name
  description = "Security group for ECS cluster: ${var.product} ${var.env}"
  vpc_id      = var.vpc_id

  # ingress_cidr_blocks      = ["<IP_ADDRESS>/16"]
  # ingress_rules            = ["https-443-tcp"]
  ingress_with_cidr_blocks = [
    {
      from_port   = 8000
      to_port     = 8000
      protocol    = "tcp"
      description = "fill me in"
      cidr_blocks = "<IP_ADDRESS>/0" # this seems too open
    }
    ### snipped for conciseness
  ]

}

data.tf
data "aws_vpc" "this" {
  id = var.vpc_id
}

data "aws_security_group" "this" {
  name   = "default"
  vpc_id = data.aws_vpc.this.id
}

data "aws_subnets" "private" {
  filter {
    name   = "vpc-id"
    values = [var.vpc_id]
  }

  tags = {
    Name = "REDACTED*"
  }
}

data "aws_ami" "ecs_optimised" {
    most_recent = true

    filter {
        name   = "name"
        # TODO: see if we need gp2 or gp3 disks? Also check if we need ebs-optimised. how important is HDD?
        values = ["amzn2-ami-ecs-hvm-2.0.202*x86_64-ebs*"]
        # aws ssm get-parameters --names /aws/service/ecs/optimized-ami/amazon-linux-2/recommended --region us-east-1
        # amzn2-ami-ecs-hvm-*-x86_64-ebs
    }

    filter {
        name   = "virtualization-type"
        values = ["hvm"]
    }

    owners = ["amazon"]
}

vars.tf
locals {
  ami_id = data.aws_ami.ecs_optimised.id

  tags = {
    environment = var.env
    product     = var.product
    owner       = "REDACTED"
    created_by  = "terraform"
    ami_id = local.ami_id
  }

  base_name = "ecs-${var.product}-${var.env}-rr"

  # TODO: Move this into separate script file if larger
  user_data = <<-EOT
    #!/bin/bash
    echo "Hello Terraform!"
  EOT
}

variable "vpc_id" {
  description = "AWS VPC ID. e.g. vpc-xxxxx"
  type        = string
}

variable "region" {
  description = "AWS region. e.g. eu-west-1"
  type        = string
}

variable "env" {
  description = "Deployment environment. e.g. dev, uat, prod"
  type        = string
}

variable "product" {
  description = "Product name. e.g. vfdb"
  type        = string
}

variable "instance_type" {
  description = "EC2 Instance type for ECS cluster. e.g. t3a.medium"
  type        = string
}

Steps to reproduce the behavior:
Are you using workspaces? NO
Have you cleared the local cache (see Notice section above)? YES
List steps in order that led up to the issue you encountered
2nd time I apply. standard tf workflow:
rm -rf .terraform .terraform.lock.hcl \
&& terraform_v1.5.1 init \
&& terraform_v1.5.1 apply -var-file=../../envs/dev/dev.tfvars -auto-approve`

Expected behavior
The capacity provider was created with terraform. Therefore, it should be updated accordingly. Though it is possible I have made a configuration error
Actual behavior
"The specified capacity provider already exists. To change the configuration of an existing capacity provider, update the capacity provider."
Terminal Output Screenshot(s)

Additional context
Possible misconfiguration, but not sure.

hallo?

This looks like there was an issue on your end. Have you tried removing and redeploying?

MAny times with no resolution. It seems very unstable unfortunately. Did you try running my sample code? Does it work fine for you?

Your code isn't deployable as written. But you can see our examples, those are working and deployable and are not showing any issue.
Looking at your error messages, you seem to have several:

No module call named "asg" is declared in the root module. looks like you don't have a module defined that is being referenced somewhere in your code
The root module does not declare a variable named "docker_image"/"docker_tag"... looks like you are missing some variable declaration
The specified capacity provider already exists looks like you have one or more capacity providers that you are naming "default" so you'll need to use different names

Many thanks for the suggestions. Much appreciated!


WSL2 (Ubuntu) has partially deleted itself twice

Version
Microsoft Windows [Version 10.0.19044.2075]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Ubuntu 22.04
Other Software
The crash/deletion of Ubuntu in WSL2 has happened to occur while using Visual Studio Code 1.71.2 with Remote - WSL v0.66.3. I do not know if this had any effect.
Repro Steps
I do not have any specifically other than "use WSL2 with Ubuntu" on my machine. Yesterday, when using VS Code to work on Code, suddenly the connection to WSL dropped and then terminated all sessions in open Windows Terminal windows. When trying to re-open Ubuntu via wsl or ubuntu in PowerShell in Windows Terminal, it just hung with no output and eventually (after several minutes) output a single line about WSL terminating. (I unfortunately don't have a direct copy of this message.) After a reboot of my machine, I was eventually able to get Ubuntu to load up, but several settings and files were missing and/or wrong. For example, ~/.bashrc had suddenly reverted back to some default state, removing everything I had added to it (and most definitely had saved). So I uninstalled Ubuntu and did a completely fresh install from the Windows Store.
Today, I had the exact same thing happen to me. I was just using WSL in VS Code, and then suddenly it disconnected. Again it would not load at all until after a reboot and then several minutes. This time, I noticed that basically the entire system had been reset. My ~/.bashrc file was completely reset, everything in ~/ gone, including my GitHub repositories and things in ~/.local.
What's weird is that this seemed to happen at almost the same time, which may of course be total coincidence. Honestly, I am unlikely to come across this again unless a specific bug is tracked down because I cannot justify using WSL with this behavior. I've lost code two days in a row for my job. I am happy to help debug this and run any command. I have used WSL rather heavily on other machines, so I'm not sure what's going on.
After Ubuntu/WSL crashes, the screen I get when trying to open up the Ubuntu app (console window) looks like:

It remains like that.
Expected Behavior
Ubuntu/WSL should never crash, and if it does, it should not delete and/or reset files.
Actual Behavior
The system seems to reset itself, as far as the ~/ directory is concerned. It seems that packages I installed with apt-get remain, but all of my files and settings, including my GitHub repositories and SSH keys are deleted.
Diagnostic Logs
I am willing to run whatever logs may be necessary to help debug this, so just let me know.

Any thoughts on this? Any steps or data I should provide for debugging?

This just happened rigth now to me. Same WSL2 on VSCode, just went for a coffee and when I was back, there was no Ubuntu. Does anyone know why is this happening??

Oh I faced this issue once and am currently having it again. The last time, I had to uninstall and re-install wsl and ubuntu.