[WIP] Verify after installation with istioctl install

for https://github.com/istio/istio/issues/21715
In case verification needs to be run with install (it can be run later with verify-install) pass --verify flag.
NOTE: Do not merge. There are many things to add/fix/reorganize/rename stuffs
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[X] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[X] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

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

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

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

@su225 I want to verify it in more detail by tomorrow. Can you provide steps to test your PR?

/ok-to-test

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

Test name
Commit
Details
Rerun command

release-notes_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test release-notes_istio

gencheck_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test release-notes_istio

gencheck_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test gencheck_istio

lint_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test release-notes_istio

gencheck_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test gencheck_istio

lint_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test lint_istio

unit-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test release-notes_istio

gencheck_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test gencheck_istio

lint_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test lint_istio

unit-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test release-notes_istio

gencheck_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test gencheck_istio

lint_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test lint_istio

unit-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test release-notes_istio

gencheck_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test gencheck_istio

lint_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test lint_istio

unit-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-distroless-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test release-notes_istio

gencheck_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test gencheck_istio

lint_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test lint_istio

unit-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test release-notes_istio

gencheck_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test gencheck_istio

lint_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test lint_istio

unit-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-pilot-k8s-tests_istio

integ-multicluster-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-multicluster-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test release-notes_istio

gencheck_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test gencheck_istio

lint_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test lint_istio

unit-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-pilot-k8s-tests_istio

integ-multicluster-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-security-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test gencheck_istio

lint_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test lint_istio

unit-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-pilot-k8s-tests_istio

integ-multicluster-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-telemetry-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test gencheck_istio

unit-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-pilot-k8s-tests_istio

integ-multicluster-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-telemetry-k8s-tests_istio

release-notes_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test release-notes_istio

lint_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-pilot-k8s-tests_istio

integ-multicluster-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-telemetry-k8s-tests_istio

release-notes_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test release-notes_istio

lint_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-pilot-k8s-tests_istio

integ-multicluster-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-telemetry-k8s-tests_istio

release-notes_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test release-notes_istio

lint_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test lint_istio

gencheck_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-pilot-k8s-tests_istio

integ-multicluster-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-telemetry-k8s-tests_istio

release-notes_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test release-notes_istio

lint_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test lint_istio

gencheck_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test gencheck_istio

unit-tests_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-telemetry-k8s-tests_istio

release-notes_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test release-notes_istio

lint_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test lint_istio

gencheck_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test gencheck_istio

unit-tests_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test unit-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-security-k8s-tests_istio

release-notes_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test release-notes_istio

lint_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test lint_istio

gencheck_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test gencheck_istio

unit-tests_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test unit-tests_istio

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

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

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

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-ipv6-k8s-tests_istio

integ-security-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-security-k8s-tests_istio

release-notes_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test release-notes_istio

lint_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test lint_istio

gencheck_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test gencheck_istio

unit-tests_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test unit-tests_istio

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

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

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

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
936e2a8e33ca6ddddc6edb0acd0b954e44b76954
link
/test integ-security-k8s-tests_istio

release-notes_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test release-notes_istio

lint_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test lint_istio

gencheck_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test gencheck_istio

unit-tests_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test unit-tests_istio

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

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

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

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

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test release-notes_istio

lint_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test lint_istio

gencheck_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test gencheck_istio

unit-tests_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test unit-tests_istio

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

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

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

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

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

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

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

Test name
Commit
Details
Rerun command

lint_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test lint_istio

gencheck_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test gencheck_istio

unit-tests_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test unit-tests_istio

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

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

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

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

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

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

release-notes_istio
63277f00b4e975e0462f2d108b4647d4cdb43af9
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.

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

Test name
Commit
Details
Rerun command

gencheck_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test gencheck_istio

unit-tests_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test unit-tests_istio

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

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

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

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

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

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

release-notes_istio
63277f00b4e975e0462f2d108b4647d4cdb43af9
link
/test release-notes_istio

lint_istio
63277f00b4e975e0462f2d108b4647d4cdb43af9
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
e9b741ae11bc438598d8daeb66abb441ca6fbc7c
link
/test unit-tests_istio

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

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

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

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

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

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

release-notes_istio
63277f00b4e975e0462f2d108b4647d4cdb43af9
link
/test release-notes_istio

lint_istio
63277f00b4e975e0462f2d108b4647d4cdb43af9
link
/test lint_istio

gencheck_istio
63277f00b4e975e0462f2d108b4647d4cdb43af9
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.

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

Test name
Commit
Details
Rerun command

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

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

Test name
Commit
Details
Rerun command

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

lint_istio
be70cbb7190d0ee95a117e7f0afd4cb32bc6eab9
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.

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

Test name
Commit
Details
Rerun command

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

lint_istio
be70cbb7190d0ee95a117e7f0afd4cb32bc6eab9
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

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

/test integ-pilot-k8s-tests_istio

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
93570c6085a665442c551387fd59767d254bdcad
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.

@shamsher31 - Currently, I install with istioctl and --verify flag for testing verification with CLI. For operator, I add --verify-after-install with istioctl operator init and istioctl operator dump commands, try installing with CRD and check logs. It is all manual currently. I have written a basic smoke test in tests/integration/operator to test StatusVerifier. Currently it does not do much except checking if Verify() method does not return any error.

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

@su225 For operators I don't see any output after install. Is that expected?
$ istioctl operator init --hub=gcr.io/istio-testing --verify-after-install -d manifests/
Installing operator controller in namespace: istio-operator using image: gcr.io/istio-testing/operator:1.9-dev
Operator controller will watch namespaces: istio-system
✔ Istio operator installed
✔ Installation complete

@shamsher31 - Probably I have to name it something other than --verify-after-install as it can be confused with verifying operator installation. The flag enables verifying istio installation in operator. That is, when you give an IstioOperator CR, it installs and then verifies (same as doing istioctl install with --verify flag). That variable turns on an environment variable checked while reconciling. See istiocontrolplane_controller.go. You can check that in logs.

@shamsher31 - I agree verify-after-install is confusing as it could refer to operator installation. Should we call it verify-cr-install instead?

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

Test name
Commit
Details
Rerun command

lint_istio
3062eab6479ad88a06e8cbb5749e30f9af0d8552
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.

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

Test name
Commit
Details
Rerun command

lint_istio
3062eab6479ad88a06e8cbb5749e30f9af0d8552
link
/test lint_istio

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

@ostromart @shamsher31 - should we mark new flag 'experimental', especially for operator? I think we should.

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

Test name
Commit
Details
Rerun command

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

/test integ-distroless-k8s-tests_istio

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

Test name
Commit
Details
Rerun command

lint_istio
8bdf25a647974040410f3e3a62048e2de0ae21fd
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.

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

Test name
Commit
Details
Rerun command

lint_istio
8bdf25a647974040410f3e3a62048e2de0ae21fd
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
8bdf25a647974040410f3e3a62048e2de0ae21fd
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
0b1befa1eae84055865d6424e1d8d11b9849a80f
link
/test integ-multicluster-k8s-tests_istio

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

/test integ-multicluster-k8s-tests_istio

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

Test name
Commit
Details
Rerun command

lint_istio
6913723e05c0a2592f971de3d628c35f2b9606ca
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.

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

Test name
Commit
Details
Rerun command

lint_istio
6913723e05c0a2592f971de3d628c35f2b9606ca
link
/test lint_istio

integ-operator-controller-tests_istio
6913723e05c0a2592f971de3d628c35f2b9606ca
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.

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

Test name
Commit
Details
Rerun command

lint_istio
6913723e05c0a2592f971de3d628c35f2b9606ca
link
/test lint_istio

integ-operator-controller-tests_istio
6913723e05c0a2592f971de3d628c35f2b9606ca
link
/test integ-operator-controller-tests_istio

analyze-tests_istio
6913723e05c0a2592f971de3d628c35f2b9606ca
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.

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

Test name
Commit
Details
Rerun command

lint_istio
6913723e05c0a2592f971de3d628c35f2b9606ca
link
/test lint_istio

integ-operator-controller-tests_istio
6913723e05c0a2592f971de3d628c35f2b9606ca
link
/test integ-operator-controller-tests_istio

analyze-tests_istio
6913723e05c0a2592f971de3d628c35f2b9606ca
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
6913723e05c0a2592f971de3d628c35f2b9606ca
link
/test lint_istio

integ-operator-controller-tests_istio
6913723e05c0a2592f971de3d628c35f2b9606ca
link
/test integ-operator-controller-tests_istio

analyze-tests_istio
6913723e05c0a2592f971de3d628c35f2b9606ca
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
6913723e05c0a2592f971de3d628c35f2b9606ca
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-operator-controller-tests_istio
6913723e05c0a2592f971de3d628c35f2b9606ca
link
/test integ-operator-controller-tests_istio

analyze-tests_istio
6913723e05c0a2592f971de3d628c35f2b9606ca
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
6913723e05c0a2592f971de3d628c35f2b9606ca
link
/test integ-pilot-k8s-tests_istio

integ-multicluster-k8s-tests_istio
6913723e05c0a2592f971de3d628c35f2b9606ca
link
/test integ-multicluster-k8s-tests_istio

lint_istio
b7f3765412a3b3deb418a32a9775781986208ba8
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.

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
6913723e05c0a2592f971de3d628c35f2b9606ca
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
6913723e05c0a2592f971de3d628c35f2b9606ca
link
/test integ-pilot-k8s-tests_istio

integ-multicluster-k8s-tests_istio
6913723e05c0a2592f971de3d628c35f2b9606ca
link
/test integ-multicluster-k8s-tests_istio

lint_istio
b7f3765412a3b3deb418a32a9775781986208ba8
link
/test lint_istio

integ-operator-controller-tests_istio
b7f3765412a3b3deb418a32a9775781986208ba8
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.

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
6913723e05c0a2592f971de3d628c35f2b9606ca
link
/test integ-pilot-k8s-tests_istio

integ-multicluster-k8s-tests_istio
6913723e05c0a2592f971de3d628c35f2b9606ca
link
/test integ-multicluster-k8s-tests_istio

lint_istio
b7f3765412a3b3deb418a32a9775781986208ba8
link
/test lint_istio

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

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

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

Test name
Commit
Details
Rerun command

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

analyze-tests_istio
b7f3765412a3b3deb418a32a9775781986208ba8
link
/test analyze-tests_istio

unit-tests_istio
a9fa266c33ae0acee7e70986a9ed3b3c276b8183
link
/test unit-tests_istio

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

/test unit-tests_istio


phantom3-village-kfs Dataset

Program does not run when I enter "gslam Dataset=<dataset_path>/DroneMap/phantom3-village/phantom3-village-kfs/.npudronemap".
In this dataset, how did you generate the 'Plane' in config.cfg? What does plane mean?

Hi, @mertalbaba   Was you able to save the trajectory of this data set? I am running this dataset in gslam but trajectory file is not saving. Neither it is showing the moving frames on right side panel of GUI.

Trajectory can be saved with plugin metric_traj, please see: https://zdzhaoyong.github.io/GSLAM/evaluate.html


fix dr ca-cert analyzer reporting error when serviceentry is external

Originally when the analyzer analyzes the ca certificates for destination rules, even when the service entry is external, if the certs are missing, the analyzer will report the error IST0128. This PR is to fix the issue #32936.
[ ] Configuration Infrastructure
[ ] Docs
[] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[X] 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.

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

Test name
Commit
Details
Rerun command

lint_istio
5f136ba21929b42dd9b9d032b30b89d1216977c7
link
/test lint_istio

release-notes_istio
5f136ba21929b42dd9b9d032b30b89d1216977c7
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.

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

Test name
Commit
Details
Rerun command

lint_istio
5f136ba21929b42dd9b9d032b30b89d1216977c7
link
/test lint_istio

release-notes_istio
5f136ba21929b42dd9b9d032b30b89d1216977c7
link
/test release-notes_istio

unit-tests_istio
5f136ba21929b42dd9b9d032b30b89d1216977c7
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.

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

Test name
Commit
Details
Rerun command

lint_istio
5f136ba21929b42dd9b9d032b30b89d1216977c7
link
/test lint_istio

release-notes_istio
5f136ba21929b42dd9b9d032b30b89d1216977c7
link
/test release-notes_istio

unit-tests_istio
5f136ba21929b42dd9b9d032b30b89d1216977c7
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
5f136ba21929b42dd9b9d032b30b89d1216977c7
link
/test lint_istio

unit-tests_istio
5f136ba21929b42dd9b9d032b30b89d1216977c7
link
/test unit-tests_istio

gencheck_istio
5f136ba21929b42dd9b9d032b30b89d1216977c7
link
/test gencheck_istio

release-notes_istio
353c8dab0a88190a346c3a303895114d2f5f0bd8
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
353c8dab0a88190a346c3a303895114d2f5f0bd8
link
/test release-notes_istio

unit-tests_istio
353c8dab0a88190a346c3a303895114d2f5f0bd8
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
353c8dab0a88190a346c3a303895114d2f5f0bd8
link
/test unit-tests_istio

release-notes_istio
903cccfd262d9d0b7946f77a1f3edde1fe883014
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
353c8dab0a88190a346c3a303895114d2f5f0bd8
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
353c8dab0a88190a346c3a303895114d2f5f0bd8
link
/test unit-tests_istio

release-notes_istio
99b9de00f60aa149f84f573ed9c7ec6672c0f5df
link
/test release-notes_istio

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

/test release-notes_istio

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

Test name
Commit
Details
Rerun command

unit-tests_istio
353c8dab0a88190a346c3a303895114d2f5f0bd8
link
/test unit-tests_istio

release-notes_istio
99b9de00f60aa149f84f573ed9c7ec6672c0f5df
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
99b9de00f60aa149f84f573ed9c7ec6672c0f5df
link
/test release-notes_istio

unit-tests_istio
99b9de00f60aa149f84f573ed9c7ec6672c0f5df
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
99b9de00f60aa149f84f573ed9c7ec6672c0f5df
link
/test unit-tests_istio

release-notes_istio
9d94f765913219019fe73100586c51e78eed3fbc
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
9d94f765913219019fe73100586c51e78eed3fbc
link
/test release-notes_istio

unit-tests_istio
9d94f765913219019fe73100586c51e78eed3fbc
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
30f68953a394ed027676ceb07dd886c6c72e74d8
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.

@shamsher31 Thanks for the reminder! I've added the release note.

@howardjohn So all of the examples in the docs concerning external HTTP/TLS ServiceEntry with DR are broken then when dealing with exposing public external websites, such as would the case be here:

What is the point of requiring supplying a publicly trusted CA to the mesh for ALL such CAs? The overhead for every user of maintaining and supplying a public trust CA repository for each such DR is enormous as well as tracking which certificates belong to which CAs.
This is only in re MESH_EXTERNAL SE with DR TLS SIMPLE for publicly verifiable certificates:

Use public trust CAs if none specified.
Use specified CAs otherwise.

This is the only way it makes any practical sense for external service entry uses IMO.

Furthermore, imagine, as the docs suggest, I'm using an external service. I supply a CA but the external service gets a new certificate in a different chain under the same CA (changes validation depth).
Furthermore, what IS the validation depth in the SIMPLE configuration? Are we required to supply ALL the certificates in the chain up to and including the actual server certificate? What happens in validation depth is 3 and 2nd intermediary is missing?
This is an important security concern that has basically no documentation of the feature set.


Small missle casing

Small missile casing is being rejected by the missile work station. when i try to put the small missile casing in the missile work station it says "I don't think that goes into here."

Doesn't seem to be an issue when testing in the dev workspace. You sure it was a small missile and not a micro missile. As the crafting station can only support the small missiles at the moment.

retested might have been the small micro missile.


Rewind method should accept blocks being disconnected.

Details here
https://github.com/stratisproject/StratisBitcoinFullNode/issues/1768

Merged this issue with https://github.com/stratisproject/StratisBitcoinFullNode/issues/1812 and removed from activation.


tf.abs() isn't documented to handle complex, but it does appear to work as tf.complex_abs() used to.

Issue #7405 was a bug filed that tf.complex_abs() was removed in 1.0.  At the bottom it says that tf.abs() now does that work, but the docs for tf.abs() only mention float.  I confirmed that tf.abs() does in fact do as the comment on the issue describes (https://github.com/tensorflow/tensorflow/blob/r1.1/tensorflow/python/ops/math_ops.py#L225)
Please incorporate the info from https://www.tensorflow.org/versions/r0.11/api_docs/python/math_ops/complex_number_functions#complex_abs
into
https://www.tensorflow.org/api_docs/python/tf/abs
... specifically the parts about it computing sqrt(a^2 + b^2) for complex numbers.

@rmlarsen Do you mind fixing this?

BTW- I would be happy to regularly make PRs for various documentation fixes.  However, I'm a little confused by the code.  I can grep for some of the descriptions to find current docs in the code, but I find that there is quite a bit of duplicate documentation.   Is this because there is separate documentation for the C++ and python code?
Since I assume you want the same behavior in both, could this be changed to use \copydoc from doxygen to avoid having to put the docs in two places?
Otherwise, If I were to make a change, do I change all the places or is some of it generated and I only need to change one?
Generally, what is the rule for where to change things when fixing documentation?

@ddurham2 (cc @martinwicke): I don't think we have a good story for avoid code duplication between C++ and Python for ops with wrappers.  In this case (and many others) I don't think there's a good substitute for a human merging the docs, since they're different ops at the C++ level (though they probably shouldn't be).
@ddurham2 Did I interpret correctly that you're volunteering to send a PR?  If so, thank you!

sure.. I'll give it a whirl. Could you give me a pointer on how to build the documentation (HTML or otherwise) to make sure my changes would look presentable?

The documentation on documentation is here. If you have questions or if something doesn't work as expected, please ask. Note that the doc generator currently only works for Python 2.7.
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/docs_src/community/documentation.md


Incorrect Datatype with Pointers

I stumbled upon an issue where the following code tries to allocate a struct rather than the expected pointer to a struct.  I believe the cause is due to an over-usage of PlatformLLVM::resolveDatatype rather than using the more appropriate printDatatype, which will include the '*' as needed.
See pastebin

Contrary to initial assumption, resolveDatatype is the correct function, but should also print the '*' as needed.


Cannot install version 1.5 from Obsidian

Obsidian version: v.0.12.12 on windows

GitHub Actions currently don't work correctly. The build doesn't go through and thus there are no Release Files..

Works now

It worked! 😄
Keep up the good work!


Sketch Geojson export quirks

When exporting a sketch to geojson:

filename extension is .geojson.json.  Just .json seems as with legacy seems fine with me.
the filename isn't the name of the sketch.  I liked this behavior in legacy for ease of export to tests, and just knowing which export is which.

Yes! Slugified names would be much better. This single export endpoint serves 3 use-cases which may need to be split:

User-initiated export of shapes. This is also used as input for geoprocessing test cases
Map visualization, where by mapbox-gl directly requests geojson for sketches
Running reports, where the endpoint is passed in the initialization event along with a valid auth token.

Currently the client dynamically creates urls to reference sketches, and if we're using slugified names I'd want to centralize that logic and expose an exportUrl property in the GraphQL Schema so that there's no chance of mismatched id generation. Map visualization probably needs a different endpoint, since mapbox-gl-style can't reference the userAttributes property.
I may be able to use the download/attachment header to let the browser rename 12.geojson.json => my-sketch.geojson.json and avoid a lot of the mess with complex url referencing... but I thought I was already doing that.
As a degenerate who piles all my files all into ~/Downloads and uses search to find things, I still like the geojson.json part of the filename and think I will keep that. Just .geojson isn't recognized by QGIS by default and it's easy to confuse what the files are without the extension.


Add lunch menu to lunch schedule item

Should be possible to get a feed through something similar to
http://www.eastsideprep.org/calendar/?action=export_events&exact_date=1409554900&no_html=true

Finished long ago


feat: complete overhaul of resources API

Switch the resources API to use a builder pattern, instead of a single def simple() helper method with many optional arguments. This makes the API more discoverable (via autocomplete and docs), and composable.

Codecov Report

Merging #13 (58b8554) into main (56b191c) will decrease coverage by 13.71%.
The diff coverage is 48.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##             main      #13       +/-   ##
===========================================
- Coverage   55.04%   41.34%   -13.71%
===========================================
  Files          17        7       -10
  Lines         456      179      -277
  Branches       73       31       -42
===========================================
- Hits          251       74      -177
+ Misses        201      102       -99
+ Partials        4        3        -1

Impacted Files
Coverage Δ

transpire/types.py
0.00% <0.00%> (-48.04%)
:arrow_down:

transpire/manifestlike.py
50.00% <50.00%> (ø)

transpire/surgery.py
100.00% <100.00%> (ø)

transpire/helm.py
0.00% <0.00%> (-100.00%)
:arrow_down:

transpire/internal/config.py

transpire/internal/secrets/__init__.py

transpire/internal/secrets/vault.py

transpire/resources/deployment.py

transpire/resources/ingress.py

... and 4 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[Bug] Extension not working after Trello update

Might be related to Issue 20, but it seems the collapse feature broke (since yesterday when it worked, so properly (chromium) browser change)
To Reproduce
Steps to reproduce the behavior (see screenshots):

Add Extension
Load board and notice collapse feature work
Refresh Page (F5)
The collapse feature does not appear (no collapse triangle)

Expected behavior
The collapse feature works all the time ;-)
Screenshots
First load or after Site Data Clear

After refresh (F5)

Site Data Clear settings to get it working again

Browser details

OS: Windows 11 22H2
Browser: Tested on Edge (117.0.2045.47 (Official build) (64-bit)) + Vivadi (<IP_ADDRESS>.54)
Strelloids version 2020.9.27

This just happened to me today. At the same time the scroll wheel started scrolling horizontally, so I had to disable "Overwrite vertical scroll on board with horizontal"

@rwjdk @sirhand  Can confirm. Suddenly a lot of problems using Strelloids: collapsing, scrolling, prioritization (see https://github.com/krzmig/strelloids/issues/31) ...
I've also deactivated "overwrite vertical scroll".
Hope this can be fixed, because Strelloids is really useful.

Trello is apparently changing its rendering engine, probably to react. The entire HTML structure on which the extension is based has been changed by this. It also does not update for everyone at the same time, I noticed yesterday that the extension is not working. The repair will unfortunately take some time....

@krzmig : Thanks for the update. Hope it do not end up too too much work for you to have it working again (and if you need help with testing let us know) 🤞, and thanks for an awesome extension so far

A new version for Firefox is now available.
Chrome as always does problems, after a long fight I was able to upload, but I do not know when they will accept it.
Because of chrome, separate branches must have been created develop for Firefox, and develop-chrom for Chrome.
Later I will update the master and generate some release.
I hope it will be usable again o/

👍 Awesome work... Will test tomorrow

OMG @krzmig, you're amazing! Thank you so much for such a quick fix❤.
The problems (card prioritization, horizontal scroll, collapsing lists ...) seem to have disappeared (Firefox here).
If I discover remaining issues, I'll report them.

Can confirm that everything is as Expected in Edge and Vivaldi with new version of Chrome Extension 🥳


FIX Add text class to TOTP verification input field so it renders dark in dark mode

Before:

After:

I don't believe codecov's check here


[cspan] download failing

Having problems downloading this video: http://www.c-span.org/video/?200413-1/new-media-technology
Rowans-MacBook-Pro:~ rowan$ youtube-dl --verbose http://www.c-span.org/video/?200413-1/new-media-technology
[debug] System config: ['-o', '/Users/rowan/Downloads/%(title)s-%(id)s.%(ext)s']
[debug] User config: []
[debug] Command-line args: [u'--verbose', u'http://www.c-span.org/video/?200413-1/new-media-technology']
WARNING: Parameter outtmpl is bytes, but should be a unicode string. Put  from __future__ import unicode_literals  at the top of your code file or consider switching to Python 3.x.
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.04.09
[debug] Python version 2.7.6 - Darwin-14.0.0-x86_64-i386-64bit
[debug] exe versions: none
[debug] Proxy map: {}
[CSpan] 200413: Downloading webpage
[CSpan] 179812: Downloading JSON metadata
[CSpan] 179812: Downloading XML
ERROR: An extractor error has occured. (caused by KeyError(u'files',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 275, in extract
    return self._real_extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/cspan.py", line 71, in _real_extract
    files = data['video']['files']
KeyError: u'files'
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 651, in extract_info
    ie_result = ie.extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 281, in extract
    raise ExtractorError('An extractor error has occured.', cause=e)
ExtractorError: An extractor error has occured. (caused by KeyError(u'files',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Rowans-MacBook-Pro:~ rowan$ youtube-dl -U
WARNING: Parameter outtmpl is bytes, but should be a unicode string. Put  from __future__ import unicode_literals  at the top of your code file or consider switching to Python 3.x.
youtube-dl is up-to-date (2015.04.09)
````

Duplicate of #3734.


DNSCrypt-proxy user account permissions

Running Entware version of dnscrypt-proxy 1.9.1 on an Asus RT-AC88U with Asuswrt-Rmerlin.
When configuring the DNSCrypt-proxy to use a specific user account, does that account need special permissions to be assigned ?

Not sure what you mean with "special permissions", but any existing system account is fine. It doesn't need to have a valid shell.


Fields that use type parameters currently not supported

Couldn't figure out how to word the topic, but the following example should be clear:
@AutoValue
public abstract class Parent<T> {
   public abstract Child1<T>();
   public abstract Child2<T>();
   public static <T> TypeAdapter...
}

currently generates the following code:
public GsonTypeAdapter(Gson gson, TypeToken<? extends Parent<T>> typeToken){
  ParameterizedType type = ...
  Type[] typeArgs = ...
  this.child1Adapter = gson.getAdapter(new TypeToken<Child1<T>>(){});
  ...
}

This is an error because TypeToken does not support things such as new TypeToken<Child<T>>(){}, and (T) will always captured as an Object and lead to potential CastException's at runtime.  Thoughts?

Support for this was added in #66 but not released yet.

Thanks!  Sorry I missed this, closing.


Joystick's PropTypes docstring for setProps references ColorPicker instead.

https://github.com/plotly/dash-daq/blob/47bc54909c7074a3a2fedc55352d691cebd4f0b8/src/components/Joystick.react.js#L141

Closing in favor of #126, which I accidentally created as a duplicate, as there's a couple more screenshots there


Updates broken link in contributing docs

Problem/Feature
The link to the contributing styling guide was broken on the creating page, this fixes that 😄

Write to your heart's content, include:

[ ] A link to the Figma design in your story (list regularly updated here)
[ ] A link to the Story(ies) in the description
[ ] Is there a Jira ticket associated?
[x] If useful, add screenshots or videos
[ ] If useful (and unclear), add a little explanation of why a certain path was taken
[ ] Instructions on how to test
[ ] Found any restrictions/limitations? Let us know!

Guidelines
Make sure the pull request:

[ ] Follows the established folder/file structure
[ ] Adds unit tests
[ ] Did you verify some accessibility (a11y) basics?
[ ] Adds/updates stories. Guidelines
[ ] Adds/updates documentation (ie proptypes) Guidelines
[ ] Has it been tested in Help Scout's supported browsers?
[ ] Requests review from designer of the feature
[ ] Add label (bug? feature?)

Pull Request Test Coverage Report for Build 3475

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 94.565%

Totals

Change from base Build 3460:
0.0%

Covered Lines:
6346

Relevant Lines:
6571

💛  - Coveralls


Docker image ci

@sebastian-su has set the DOCKER_PASSWORD and DOCKER_USERNAME Secrets at the organization level. I'm re-running the Action so that we'll use the endocodeci DockerHub account.

@sebastian-su has set the DOCKER_PASSWORD and DOCKER_USERNAME Secrets at the organization level. I'm re-running the Action so that we'll use the endocodeci DockerHub account.

Waiting for these two Secrets to also be set for the entire Endocode's GitHub organization page before merging.

Waiting for these two Secrets to also be set for the entire Endocode's GitHub organization page before merging.


RDBES: Insert/update descriptions for RS_SelectionDevice

RS_SelectionDevice update descriptions (from blank) with the following and add '4':
Code | Description
0       | No selection device
1       | Selection panel
2       | Grid
3       | T90. The codend  and extension piece are produced from knotted diamond mesh netting turned 900.
4       | There is both selection device and escape window.

Drop Prefix RS_
@HenrikK-N to add bibliographic references to the selection devices.

https://www.ices.dk/sites/pub/Publication Reports/Expert Group Report/ftc/2006/WGFTFB06.pdf


Major Regression for apps/whale-api due to untracked objects on TokenMapper & PoolMapper

What happened:

See https://github.com/JellyfishSDK/jellyfish/pull/1528 for temporary mitigation. We will work on a fix, a re-index will be required. Please use the preview builds for production with the hot-fixed static code. If you're using a snapshot please use a snapshot earlier than height 1948150.

The apps/whale-api crashed at block height 1948512.
There is a Major Regression for apps/whale-api due to untracked objects on TokenMapper & PoolMapper that affected PoolSwap and CompositeSwap indexing. The bug was due to the stock split mechanism that generated 2 coinbase transactions without its accompanying DfTx to indicate what's the event.
/assign @fuxingloh
/triage accepted
/priority urgent-now
/area apps
/apps whale-api

This also caused 10-15mins downtime on ocean, see https://status.defichain.com/incidents/b15s181nh2j1

Please use https://github.com/JellyfishSDK/jellyfish/pkgs/container/whale-api/24365785?tag=88972089d0e439aee173fde0a7fd7cc918c1da79 meanwhile while we work on a proper fix.

Currently these indexer contributes to the TokenMapper:

CreateTokenIndexer
CreatePoolPairIndexer
SetLoanTokenIndexer

Now we have confirmed, SetGov for StockSplit affects it too.
We also need to check if there is any regression with how LoanToken get created.

Hi, will a complete re-index be required or is it enough to use a snapshot prior to  the failing block?

Snapshot prior to 1948150 is enough.

Hi, will a complete re-index be required or is it enough to use a snapshot prior to the failing block?

Apologize for the inconvenience, this was caught on the eleventh hour by @ivan-zynesis (thankfully otherwise it would have been worst).

Nothing to apologize. This is a complex topic that has not been done before and you guys are super quick in finding a solution.
Do you know if a snapshot after having reindexed will work with an older version of whale? or is this temporary version (ghcr.io/jellyfishsdk/whale-api:88972089d0e439aee173fde0a7fd7cc918c1da79) required?

Reindex of the node is not required to my experience.
Just a reindex of the whale database with the temporary whale version. Therefore, a snapshot/backup of the whale database can be used.

I can confirm. A whale db restore with the new temporary whale version has cured the issue. My instance is up and running again!

Attached blockchain stock split logs: https://gist.github.com/fuxingloh/5678745aa6eba9770f211c362f96d846
/cc @canonbrother @eli-lim if it helps with #1533 and whale-indexer

@fuxingloh just saw the new release which requires a complete re-index. Any snapshots around? Otherwise I will start now syncing from scratch which takes a few days.

@fuxingloh just saw the new release which requires a complete re-index. Any snapshots around? Otherwise I will start now syncing from scratch which takes a few days.

Sadly no; the snapshot system we use is automated in a closed-loop volume environment with limited access.

This issue has been fixed and tested with the release of v2.47.0. It requires "re-indexing", as the v2.47.0 whale-api index is not guaranteed to be compatible with any version prior. Please regenerate /data (deleting the folder) by re-indexing from scratch.
Thanks to @canonbrother and @eli-lim for working on the various issues caused by the regression.


Error updating attribute: Message: ERROR: Problem on pre process event. Reason: Unsupported device manager event

1 ° I created a template with float value.
2 ° I linked with a devece and a flow.
3 ° When updating the attribute, changing the value, I find a possible error.
message: Error updating attribute: Message: ERROR: Problem on pre process event. Reason: Unsupported device manager event

Ticket analysis meeting (April, 3rd): Fix after.


osTicket 1.10.5 and 1.11 have been released

Last night the new version have been released:
https://github.com/osTicket/osTicket/releases
Please update the dockerfile

see #50 for pull request.

unfortunately the upgrade/change won't be that easy due to #51

#50 has been accepted to update to v1.10.5. Will track v1.11 in #45 to avoid duplication.


Simplify Revision.clone() implementation

Made sh1 and branches variable private so it can be only accessed and modified by appropriate getter and setter methods.
Enhanced the error handling in the clone() method to provide more informative details in case of a cloning error.

[x] I have read the CONTRIBUTING doc
[x] I have referenced the Jira issue related to my changes in one or more commit messages
[x] I have added tests that verify my changes
[x] Unit tests pass locally with my changes
[x] I have added documentation as necessary
[x] No Javadoc warnings were introduced with my changes
[x] No spotbugs warnings were introduced with my changes
[x] I have interactively tested my changes

Types of changes
What types of changes does your code introduce? Put an x in the boxes that apply

[x] Infrastructure change (non-breaking change which updates dependencies or improves infrastructure)

Hey @MarkEWaite, I've made the changes you told me. Please check and tell me if it is right or if I should make any other changes.

@AniketNS I am out of the office for another week.  I won't look further at this until after I return.

Ohh ok @MarkEWaite.


Add comprehensive automatic test

TL; DR Added a simple, comprehensive unit test; made the t-route model scriptable
This test is styled as a unit test, though it is more of an integration test -- if this test fails, it indicates a change more than a clear issue with any particular library.
Perhaps of greater importance, to facilitate insertion into the test, the main function was subdivided, adding two new functions -- _run_everything_v02 and _handle_output_v02. With these functions in place, the full return set from our model execution can be obtained in a deck of results organized as follows:
[list of results from each tailwater in the network
    (tuple [list of ids], [2-d array of results with dimensions: id; flow, velocity, depth for each timestep] [optionally 2-d array of results with dimensions: id; Cn, Ck, X from MC calculation for each timestep])
]

Converting these into a pandas dataframe, for instance, may be accomplished with the following:

def convert_results_to_df(results, return_courant = False)
    courant = pd.Dataframe()
    qvd_columns = pd.MultiIndex.from_product(
        [range(nts), ["q", "v", "d"]]
    ).to_flat_index()

    flowveldepth = pd.concat(
        [pd.DataFrame(r[1], index=r[0], columns=qvd_columns) for r in results],
        copy=False,
    )

    if run_parameters.get("return_courant", False):
        courant_columns = pd.MultiIndex.from_product(
            [range(nts), ["cn", "ck", "X"]]
        ).to_flat_index()
        courant = pd.concat(
            [
                pd.DataFrame(r[2], index=r[0], columns=courant_columns)
                for r in results
            ],
            copy=False,
        )
    return flowveldepth, courant

So... with those things in place, any script or notebook can now call the v02 execution (a v03 PR is in progress) of the t-route model and then handle the results directly, something like the following (which is exactly what is done in the new test...):
from nwm_routing.__main__ import _run_everything_v02
from troute.nhd_io import read_custom_input
import numpy as np

def run_troute_from_script(custom_input_file):
    (
        supernetwork_parameters,
        waterbody_parameters,
        forcing_parameters,
        restart_parameters,
        output_parameters,
        run_parameters,
        parity_parameters,
        data_assimilation_parameters,
        diffusive_parameters,
        coastal_parameters,
    ) = read_custom_input(custom_input_file)

    # Modify any parameters from a template file inline here
    run_parameters["nts"] = 12

    # Then run the model and get the results
    results = _run_everything_v02(
            supernetwork_parameters,
            waterbody_parameters,
            forcing_parameters,
            restart_parameters,
            output_parameters,
            run_parameters,
            parity_parameters,
            data_assimilation_parameters,
            diffusive_parameters,
            coastal_parameters,
    )
    return results

custom_input_file = "../../test/input/yaml/CustomInput.yaml"
run_troute_from_script(custom_input_file)
fvd, courant = convert_results_to_df(results, True)

# And then do it again with another configuration or experiment
# with comparing the pandas dataframes or whatever else you like!

ping @BrianAvant-NOAA

This is a great new capability that greatly facilitates output comparison. Can you please give a short demo on this new feature to the Inland Team later this week?

Will do.

@jameshalgren can you send me an invite to the demo?


Added argument launching

Now, Coal can launch with array arguments. Check if there are mistakes I made.

ok bro


Add support for W-spiders, differentiation, and integration

The PR add supports for #16 and #76

I closed this PR because @exAClior has been working on this project.


[Candidate 1v1 Arctic Arena ZH v5] Snow in water does not look optimal

Issue Description
Snow in water does not look optimal. Bottom left corner.
Expected behavior
Bottom left corner looks visually as good as top right corner.
Screenshots
Does not look good.

Looks good.

I am fixing this now, as this map was my design. Bottom left snow will look fine in v6


Minimize rerender warnings

Ember 1.13 introduced a warning when inefficient rerenders are caused. The most basic way to understand this is changing a property in didInsertElement:
// app/components/show-name.js
import Ember from 'ember';

export default Ember.Component.extend({
  name: 'bob',
  didInsertElement() {
    this.set('name', 'mike');
  }
});

{{! app/templates/components/show-name.hbs }}
{{name}}

Ember renders the template, showing "bob". Then it calls the didInsertElement hook, where the author has asked the name to be changed to "mike". Thus we need to rerender the template (and potentially child templates) which is slow. Better would be to know we need "mike" in the first place.
Of course real-world occurrences of this can be a bit more contrived.
Here I've refactored some code that was causing warnings, or even code that was simply using Ember's set/get system (which is observable/bindable) for what is basically just internal state for the component.

:+1: thanks! :smile:
This all makes perfect sense and definitely highlights what to look out for in the future. I'm thinking there are probably a number of other areas where we're using get/set for internal state.
Would you mind squashing the commits so it's ready to merge?

Squashed and green.

Could you rebase? I was looking to merge but there's a conflict after merging the htmlSafe PR. Thanks.

@kevinansfield rebased and tests are green!


Test Results Confusion

Thanks for your code, amazing job!
But Im a little bit confused on the results you obtained, please correct me if Im wrong.
To my understanding, the standard ImageNet Classification task should be testing on images whose shorter edges are 256 and center cropped to 224. However, at the last phrase of your codes you simply test it on size 288. If you evaluate your weights on 224 I guess you should expect some numbers below 93. Have you ever tried it?

For this code we used requirements from DAWN ImageNet training competition which does not require images to be center cropped at 224.
I expect lower results by taking center crop, since crop may discard important details. Here's an example from imagenet dataset, it's a broom, but if you take center crop, it becomes a stick

Using center crop, I think the 16-machine version would not reach 93% even with unlimited training time -- with current schedule it barely reaches 93% and then starts going down. It's pushing how far you can go with vanilla SGD/momentum -- most changes makes things worse. I think to get past 93% with cropping, extra tricks would be needed, like LARS.
Is "resize to 256, center crop to 224" what they used in current training record? (Imagenet in 4 minutes paper). I couldn't find description of cropping they used.

I couldn't find info if Tencent applied 224 cropping or not. The Japanese team Preferred Networks who trained imagenet in 15 mins applied single crop for validation but I don't know at what size they cropped.
For the center crop explanation part, I don't get it. In your code you did use center crop didn't you? The different part is that you cropped images to 288(after resizing to 288*1.14), rather than 224.

The explanation of test image preprocessing is under section "A simple new training trick: rectangles!"
of http://www.fast.ai/2018/08/10/fastai-diu-imagenet/

hello, Can you give a link to the Japanese team? @nonobelong

@TccccD I don't think they've released their training code tho.
https://www.preferred-networks.jp/en/news/pr20171110


A bundle should be a module

What is the current behavior?
A bundle generated by Webpack cannot be used as a module.
What is the expected behavior?
We should have the ability to make bundled modules.
For example:
// libA.js
export let a = "Hello"

// libB.js
export let b = "World"

// entry.js
import {a} from "./libA"
import {b} from "./libB"

export let message = `${a}, ${b}!`

Then the webpack bundling would generate a single file:
// bundle.js
/*
 * Here all the usual Webpack stuff,
 * then:
 */
export let message = `${a}, ${b}!`

The modules libA and libB are not accessible from outside the bundle. But I suggest that all exported members of entry (the entry point defined in webpack.config.js) could be exported by the bundle.
Use cases
Native support for ES6 modules is coming in browsers. We should be able to use Webpack bundles as native modules.
Even now. I currently generates my bundled libraries without Webpack by concatenating files and append exports because I didn't find how to export something from a bundle.

how should those bundles be consumed if the browser does not have native support for es6? :)

By Webpack or SystemJS.

@paleo There is libraryTarget config option that does what you are suggesting a exportFormat could do. amd, commonjs and umd are supported.
I see there is some discussion around supporting es2015 modules (formerly es6). https://github.com/webpack/webpack/issues/2933.

@gbakernet Thank you. :)


Many "Playback error (undefined)" responses on Ubuntu 14.04

Hello: I'm running the most updated version of Atraci and run into a lot of songs that won't play. I've checked on the site itself and the songs play. I'm listening to Donald Fagen now and have gotten a five such errors on a playlist I pulled down, and even more from just a general search.

Can you try clearing the cache?
For me it happens when I use some kinda unstable connection (3g on low signal)

I'll give it a go and see what happens. here's an image from a prefab sprout list and none of them will play:

No -- clearing the cache (selecting both reset database and reload without cache) had no effect.

I have the same issue with some songs. I also treide to clean the cache and to delete the whole atraci folder
OS: Arch Linux

I also have the same issue.

I'm getting this as well on both Xubuntu 14.04 and Windows 8.1 on a fast, stable connection. This is what the console displays on Windows:

Have the same issue on ubuntu 14.10 despite that works like a charm!

I don't know what to tell you guys, I'm not a dev but on fc21, I only faced this issue once when my ISP was doing a maintenance. Never seen that again :worried:

this happens many times a day for me I wonder can it be that it interferes with skype / lampp server / router settings?

Hi im face the same issue, on fedora 21 x86_64

Every api call outside of US currently running into this issues on several videos

@avihaymenahem I'm from outside the US (Bangladesh). Me and several friends of mine use Atraci on a regular basis (ditched itunes radio), and the api response is ok here

Same issue.

stable connection
tried reloading without cache and clearing the database, to no avail
from Croatia

The only tracks that seem to be playing are live performances or covers - never the main thing. I don't know why that is, maybe it's just a coincidence.

@corazza sounds like a VEVO issue to me

@fa7ad Yes, I'm pretty sure it is.

@corazza I think this has something to do with the ytdl version Atraci uses, try building with the latest ytdl (use David for reference)


Update the wit-{component,parser} crates

This commit updates wit-bindgen for all the changes made in https://github.com/bytecodealliance/wasm-tools/pull/867, namely the implementation of use. The syntax of WIT has changed to support this and additionally the internal structures of WIT have all radically changed.
This change updates all the various generators here, tests with various syntaxes, and all *.wit files.

Note that I'm still working my way through this. The Rust guest and JS host generators are all fully updated and working as per the tests now. I plan on tackling C & Java next.

Ok I think almost everything is ready here except for the java generator.
@dicej would you be up for helping out getting that working? The generator generates code successfully currently but it doesn't compile. I fear that this is diving into an area of Java I know very little about. I did change the structure of the generated code so I know why it's failing to compile, namely previously many tests used default export and now they have both export foo: some.interface as well as export test-imports: func() so tests are testing more than they used to. I'm not sure how to get the right Java incantation with classes and such to update the wasm.java to have the whole test. I realize this is a bit to just dump on you, so if you'd like I'd be happy to pair up for a moment to see if you can look over my shoulder and point out what to you may be an obvious fix.

Ok with the help of @dicej I think this is ready go go now!


Added support for IP-cameras as input.

@vladimir-dudnik I reopened new pull resuest

Jenkins please retry a build

Jenkins please retry a build

Jenkins please retry a build

Jenkins please retry a build

@durgabhavaniv please resolve merge conflict and review question in comments

This is obsoleted by #862.


New feature - options number, date

Loader supports imported values as number or date object

Coverage remained the same at 100.0% when pulling b572350cef5bda6a45c19b1036a2c468dfa0a65c on Perlmint:feature/number_date into 03608c6a4a638b6819fb5ce03435dff8b6190887 on sapphiredev:master.

Coverage remained the same at 100.0% when pulling ee3b09f5f79aa571e986706c3fc07e4a3ac55cbc on Perlmint:feature/number_date into 03608c6a4a638b6819fb5ce03435dff8b6190887 on sapphiredev:master.


Neoforge for Minecraft 1.21.3: Invalid Player Data

Description
Using Luckperms for Neoforge for Minecraft 1.21.3 does not work.
Reproduction Steps
Install a new Neoforge Server.
Install Luckperms.
Start Server.
Join with a clean Neoforge Client.
Invalid Player Data.
Expected Behaviour
Install a new Neoforge Server.
Install Luckperms.
Start Server.
Join the Server.
All fine.
Server Details
neoforge-21.3.28-beta - neoforge-21.3.34-beta --> Tried all Versions
LuckPerms Version
LuckPerms-NeoForge-5.4.139 - LuckPerms-NeoForge-5.4.146 --> Tried all Versions
Logs and Configs
Server log: https://gist.github.com/RenNagasaki/26b244b038ca3f691274333bd42ecf0c
Config (Auto created from Mod, not changed): https://gist.github.com/RenNagasaki/1028cd2fed9b1482ecf8f00de49c08b1
Extra Details
No response

@jpenilla Any idea? I was able to reproduce the above error in all versions of LuckPerms running on NeoForge.

True
Pls fix it Lucko 😢

Looks like a dupe of #3963

See comment in #4002, should be fixed by b18717edefabae99a8aa75ee5f49cda2e2ee823c


Add conda_builg_config validation.

Resolves #15

@bnemanich
Should we be pulling the variant possibilities from somewhere instead of hard coding them?

@bnemanich
@jayfurmanek
It should be good to go now.


Fix gluster volume create force

Since we are allowing gluster volumes to be created on the root parition when lvm management is not being used, gluster volume create must have the force option added.  Since the determination of the volume mount location happens in the compile phase, but the directory creation happens in the converge phase, the determination will always be false since the directory does not exist yet.
This moves the check and force directive into a lazy evaluation block so solve the problem.
* execute[gluster volume create gv0 replica 2 gluster2:/data/gv0/brick gluster1:/data/gv0/brick] action run

  ================================================================================
  Error executing action `run` on resource 'execute[gluster volume create gv0 replica 2 gluster2:/data/gv0/brick gluster1:/data/gv0/brick]'
  ================================================================================

  Mixlib::ShellOut::ShellCommandFailed
  ------------------------------------
  Expected process to exit with [0], but received '1'
  ---- Begin output of gluster volume create gv0 replica 2 gluster2:/data/gv0/brick gluster1:/data/gv0/brick ----
  STDOUT:
  STDERR: volume create: gv0: failed: The brick gluster2:/data/gv0/brick is being created in the root partition. It is recommended that you don't use the system's root partition for storage backend. Or use 'force' at the end of the command if you want to override this behavior.
  ---- End output of gluster volume create gv0 replica 2 gluster2:/data/gv0/brick gluster1:/data/gv0/brick ----
  Ran gluster volume create gv0 replica 2 gluster2:/data/gv0/brick gluster1:/data/gv0/brick returned 1

  Resource Declaration:
  ---------------------
  # In /tmp/kitchen/cache/cookbooks/gluster/recipes/server_setup.rb

  166:         execute "gluster volume create #{volume_name} #{options}" do
  167:           action :run
  168:           not_if options.empty?
  169:         end
  170:       end

  Compiled Resource:
  ------------------
  # Declared in /tmp/kitchen/cache/cookbooks/gluster/recipes/server_setup.rb:166:in `block in from_file'

  execute("gluster volume create gv0 replica 2 gluster2:/data/gv0/brick gluster1:/data/gv0/brick") do
    action [:run]
    retries 0
    retry_delay 2
    default_guard_interpreter :execute
    command "gluster volume create gv0 replica 2 gluster2:/data/gv0/brick gluster1:/data/gv0/brick"
    backup 5
    returns 0
    declared_type :execute
    cookbook_name "gluster"
    recipe_name "server_setup"
  end

  Platform:
  ---------
  x86_64-linux

@theundefined FYI

weird. I didn't noticed that issue :/ Now i see that i didn't destroyed second vm. And after second converge it works fine because directory alredy existed... Thanks for fix.

No problem :)


Map model to a different table name

Problem
Currently the models are mapped to a table of the same name on the local Realm as well as on Atlas Device Sync. When working in Domain Driven Design where there are a lot of different models in different layers and different data sources, there is a need to name the models differently to distinguish them. For example, I could have the following models:

ModelName (this is the domain model)
ModelNameFirestore
ModelNameRealm
ModelNameHive
ModelNameSql

It would be nice to have an option to map the Realm model to a different table similar to property mapping.
Solution
Solution: Add a 'mapTo' option to @RealmModel that will map the model to a specific table in the database.
Alternatives
None
How important is this improvement for you?
Fairly niche but nice to have anyway
Feature would mainly be used with
Atlas App Services: Auth or Functions etc

Hi @lhengl,
As I understand having MapTo on class level is the thing that would help you to solve your problem.
You can use the annotation MapTo. It is supported on class level and you can use it to specify the table name. You can see the usage here.
We have now realized that this is not well described in the API docs. We will fix the documentation.
Thanks!

Thank you @desistefanova, I wasn't aware of this support since the documentation states it is for a member level map. Thanks, tested and working as expected.


Replace .sti -> .s2i in README.md

@bparees @soltysh are we ready to point users to use .s2i instead of the deprecated .sti? I guess so. PTAL.
Fixes #106.

lgtm


phase 1 - network guide review / solicit feedback

Phase 1 - network install config guide.
Aruba and Mellanox guides complete.
Needs:
topology examples
Review especially of the section 'network management connection to campus'
Overall review
Aruba:

Open items: N/A

Mellanox:

Open items:
Needs QoS section - however we should discuss how we want QoS to be implemented in Mellanox.
Notes:
Default Mellanox Configuration
•	By default no ingress rewrite configuration is set
•	By default PCP rewrite configuration in router is set
•	The default mapping is as following:
◦	Switch-priority=i to PCP,DEI=i,0, i=0-7
◦	Switch-priority=i to DSCP=8i, i=0-7
          As QoS is already configured and enabled by default we may not need this section for Mellonox. I.e. in Aruba 8xxx the trust for QoS by default is not enabled.

Dell:

Needs chapters built for configurationn
Does not need VSX/MLAG section (since used in edge)

As a summary of above changes suggested:

CANU changes to this doc should be handled separately in CASMNET-902.
Small/Medium/Large, etc.. architectures should be verified and added via CASMNET-903
Architecture should be in it's own section/directory as it's not really related to Aruba only...
Loudly recommend a separate troubleshooting guide that's generally Dell/Mellanox or Aruba independent.  Currently there is quite a bit of the same text in both dellanox and aruba sections which will require independent and error-prone maintenance. For the troubleshooting section where we need to differentiate between switch vendors, the examples should also be in the same document.
Entire Dellanox section needs close review to ensure examples are Dell/Mellanox and not remaining Aruba.
Canu to CANU everywhere.
At some point the entire document should be reviewed for tense and voice by someone.  Quite a few inconsistencies.
To make finding and editing easier filenames should either be standardized or in independent directories.  For example some canu files are "canu_" and some other are "use_canu_to".  Pick one.