break down multicluster test suite

Once we migrate these cases out of multicluster/ we can start running pilot or other jobs with multi-cluster enabled instead of a catch-all multicluster job.

[X] Move Reachability
[X] Move Cross Cluster Load-Balancing
[X] Move Cluster Local
[x] Move Telemetry

After this lands:

[ ] Enable pilot-multicluster prow job
[ ] Delete Multicluster Prow Job
[ ] Delete tests/integration/multicluster

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

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

Test name
Commit
Details
Rerun command

lint_istio
2372c35dd29a46a20ec8a930a9b7c83b73219342
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.

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
785adf2c8ad6e09bda61bc6b95598559e63f20ad
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.

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
785adf2c8ad6e09bda61bc6b95598559e63f20ad
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
785adf2c8ad6e09bda61bc6b95598559e63f20ad
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
785adf2c8ad6e09bda61bc6b95598559e63f20ad
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
785adf2c8ad6e09bda61bc6b95598559e63f20ad
link
/test integ-pilot-k8s-tests_istio

integ-distroless-k8s-tests_istio
0c55b418448c5c7de1147fe88b7c3199f9014622
link
/test integ-distroless-k8s-tests_istio

analyze-tests_istio
0c55b418448c5c7de1147fe88b7c3199f9014622
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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
0c55b418448c5c7de1147fe88b7c3199f9014622
link
/test integ-distroless-k8s-tests_istio

analyze-tests_istio
0c55b418448c5c7de1147fe88b7c3199f9014622
link
/test analyze-tests_istio

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

/retest

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
0c55b418448c5c7de1147fe88b7c3199f9014622
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
0c55b418448c5c7de1147fe88b7c3199f9014622
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
0c55b418448c5c7de1147fe88b7c3199f9014622
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.

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
0c55b418448c5c7de1147fe88b7c3199f9014622
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
6dc97e527a1b1e3c9401348e61c4a4ced852f722
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.

/test integ-pilot-multicluster-tests_istio

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
6dc97e527a1b1e3c9401348e61c4a4ced852f722
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
6dc97e527a1b1e3c9401348e61c4a4ced852f722
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
6275018f4d7e70803dc37681ade61db193c30ac2
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.

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
6275018f4d7e70803dc37681ade61db193c30ac2
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
6275018f4d7e70803dc37681ade61db193c30ac2
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
6275018f4d7e70803dc37681ade61db193c30ac2
link
/test integ-pilot-k8s-tests_istio

release-test_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test release-test_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
6275018f4d7e70803dc37681ade61db193c30ac2
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
6275018f4d7e70803dc37681ade61db193c30ac2
link
/test integ-pilot-k8s-tests_istio

release-test_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test release-test_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
6275018f4d7e70803dc37681ade61db193c30ac2
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
6275018f4d7e70803dc37681ade61db193c30ac2
link
/test integ-pilot-k8s-tests_istio

release-test_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test release-test_istio

unit-tests_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
6275018f4d7e70803dc37681ade61db193c30ac2
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
6275018f4d7e70803dc37681ade61db193c30ac2
link
/test integ-pilot-k8s-tests_istio

release-test_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test release-test_istio

unit-tests_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test unit-tests_istio

gencheck_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
6275018f4d7e70803dc37681ade61db193c30ac2
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
6275018f4d7e70803dc37681ade61db193c30ac2
link
/test integ-pilot-k8s-tests_istio

release-test_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test release-test_istio

unit-tests_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test unit-tests_istio

gencheck_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test gencheck_istio

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

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
6275018f4d7e70803dc37681ade61db193c30ac2
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
6275018f4d7e70803dc37681ade61db193c30ac2
link
/test integ-pilot-k8s-tests_istio

release-test_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test release-test_istio

unit-tests_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test unit-tests_istio

gencheck_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test gencheck_istio

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

lint_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
6275018f4d7e70803dc37681ade61db193c30ac2
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
6275018f4d7e70803dc37681ade61db193c30ac2
link
/test integ-pilot-k8s-tests_istio

release-test_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test release-test_istio

unit-tests_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test unit-tests_istio

gencheck_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test gencheck_istio

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

lint_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test lint_istio

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

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
6275018f4d7e70803dc37681ade61db193c30ac2
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
6275018f4d7e70803dc37681ade61db193c30ac2
link
/test integ-pilot-k8s-tests_istio

release-test_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test release-test_istio

unit-tests_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test unit-tests_istio

gencheck_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test gencheck_istio

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

lint_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test lint_istio

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

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

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
6275018f4d7e70803dc37681ade61db193c30ac2
link
/test analyze-tests_istio

release-test_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test release-test_istio

unit-tests_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test unit-tests_istio

gencheck_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test gencheck_istio

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

lint_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test lint_istio

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

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

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

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
6275018f4d7e70803dc37681ade61db193c30ac2
link
/test analyze-tests_istio

release-test_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test release-test_istio

unit-tests_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test unit-tests_istio

gencheck_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test gencheck_istio

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

lint_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test lint_istio

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

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

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

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

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
6275018f4d7e70803dc37681ade61db193c30ac2
link
/test analyze-tests_istio

release-test_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test release-test_istio

unit-tests_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test unit-tests_istio

gencheck_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test gencheck_istio

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

lint_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test lint_istio

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

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

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

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

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

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

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

Test name
Commit
Details
Rerun command

release-test_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test release-test_istio

unit-tests_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test unit-tests_istio

gencheck_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test gencheck_istio

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

lint_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test lint_istio

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

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

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

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

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

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

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

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

Test name
Commit
Details
Rerun command

release-test_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test release-test_istio

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

lint_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test lint_istio

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

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

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

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

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

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

analyze-tests_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test analyze-tests_istio

unit-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
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.

/retest

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

Test name
Commit
Details
Rerun command

release-test_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test release-test_istio

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

lint_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test lint_istio

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

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

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

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

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

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

unit-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
link
/test unit-tests_istio

analyze-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
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.

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

Test name
Commit
Details
Rerun command

release-test_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test release-test_istio

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

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

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

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

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

analyze-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
link
/test analyze-tests_istio

unit-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
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.

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

Test name
Commit
Details
Rerun command

release-test_istio
fc566fc99913be75d4b4f7a1b09faf5c4b3e7e1f
link
/test release-test_istio

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

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

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

analyze-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
link
/test analyze-tests_istio

unit-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
link
/test analyze-tests_istio

unit-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
link
/test analyze-tests_istio

unit-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
link
/test integ-security-k8s-tests_istio

lint_istio
8042c13527d408a2d9a6390c51a70cc859abe539
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.

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
link
/test analyze-tests_istio

unit-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
link
/test integ-security-k8s-tests_istio

lint_istio
8042c13527d408a2d9a6390c51a70cc859abe539
link
/test lint_istio

gencheck_istio
8042c13527d408a2d9a6390c51a70cc859abe539
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
link
/test integ-security-k8s-tests_istio

lint_istio
8042c13527d408a2d9a6390c51a70cc859abe539
link
/test lint_istio

gencheck_istio
8042c13527d408a2d9a6390c51a70cc859abe539
link
/test gencheck_istio

analyze-tests_istio
8042c13527d408a2d9a6390c51a70cc859abe539
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.

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
link
/test integ-security-k8s-tests_istio

lint_istio
8042c13527d408a2d9a6390c51a70cc859abe539
link
/test lint_istio

gencheck_istio
8042c13527d408a2d9a6390c51a70cc859abe539
link
/test gencheck_istio

analyze-tests_istio
8042c13527d408a2d9a6390c51a70cc859abe539
link
/test analyze-tests_istio

unit-tests_istio
8042c13527d408a2d9a6390c51a70cc859abe539
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
2408ed092d3cffcab67e44a2142d9045e302c772
link
/test integ-security-k8s-tests_istio

lint_istio
8042c13527d408a2d9a6390c51a70cc859abe539
link
/test lint_istio

gencheck_istio
8042c13527d408a2d9a6390c51a70cc859abe539
link
/test gencheck_istio

analyze-tests_istio
8042c13527d408a2d9a6390c51a70cc859abe539
link
/test analyze-tests_istio

unit-tests_istio
8042c13527d408a2d9a6390c51a70cc859abe539
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
8042c13527d408a2d9a6390c51a70cc859abe539
link
/test lint_istio

unit-tests_istio
8042c13527d408a2d9a6390c51a70cc859abe539
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
8042c13527d408a2d9a6390c51a70cc859abe539
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
8042c13527d408a2d9a6390c51a70cc859abe539
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
f1040baf17404dde75614d5d04b4424926b3e4e1
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
f1040baf17404dde75614d5d04b4424926b3e4e1
link
/test analyze-tests_istio

unit-tests_istio
f1040baf17404dde75614d5d04b4424926b3e4e1
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
f1040baf17404dde75614d5d04b4424926b3e4e1
link
/test analyze-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

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

unit-tests_istio
e51c1621785171a89aaa0845376a5f5ed7f8e8f0
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
e51c1621785171a89aaa0845376a5f5ed7f8e8f0
link
/test unit-tests_istio

analyze-tests_istio
e51c1621785171a89aaa0845376a5f5ed7f8e8f0
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
e51c1621785171a89aaa0845376a5f5ed7f8e8f0
link
/test unit-tests_istio

analyze-tests_istio
e51c1621785171a89aaa0845376a5f5ed7f8e8f0
link
/test analyze-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
e51c1621785171a89aaa0845376a5f5ed7f8e8f0
link
/test unit-tests_istio

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

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

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

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

Test name
Commit
Details
Rerun command

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

analyze-tests_istio
7b150efc89fda3c595b3dde5730ba8e55a45a65f
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
7b150efc89fda3c595b3dde5730ba8e55a45a65f
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
7b150efc89fda3c595b3dde5730ba8e55a45a65f
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
7b150efc89fda3c595b3dde5730ba8e55a45a65f
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
7b150efc89fda3c595b3dde5730ba8e55a45a65f
link
/test integ-security-k8s-tests_istio

analyze-tests_istio
73caa0e469813285863fa6b32de4f9ba23dff4c5
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
7b150efc89fda3c595b3dde5730ba8e55a45a65f
link
/test integ-security-k8s-tests_istio

analyze-tests_istio
73caa0e469813285863fa6b32de4f9ba23dff4c5
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
7b150efc89fda3c595b3dde5730ba8e55a45a65f
link
/test integ-security-k8s-tests_istio

analyze-tests_istio
73caa0e469813285863fa6b32de4f9ba23dff4c5
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
73caa0e469813285863fa6b32de4f9ba23dff4c5
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
7b150efc89fda3c595b3dde5730ba8e55a45a65f
link
/test integ-security-k8s-tests_istio

analyze-tests_istio
73caa0e469813285863fa6b32de4f9ba23dff4c5
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
73caa0e469813285863fa6b32de4f9ba23dff4c5
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
73caa0e469813285863fa6b32de4f9ba23dff4c5
link
/test integ-telemetry-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
7b150efc89fda3c595b3dde5730ba8e55a45a65f
link
/test integ-security-k8s-tests_istio

analyze-tests_istio
73caa0e469813285863fa6b32de4f9ba23dff4c5
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
73caa0e469813285863fa6b32de4f9ba23dff4c5
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
73caa0e469813285863fa6b32de4f9ba23dff4c5
link
/test integ-telemetry-k8s-tests_istio

integ-distroless-k8s-tests_istio
73caa0e469813285863fa6b32de4f9ba23dff4c5
link
/test integ-distroless-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
7b150efc89fda3c595b3dde5730ba8e55a45a65f
link
/test integ-security-k8s-tests_istio

analyze-tests_istio
73caa0e469813285863fa6b32de4f9ba23dff4c5
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
73caa0e469813285863fa6b32de4f9ba23dff4c5
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
73caa0e469813285863fa6b32de4f9ba23dff4c5
link
/test integ-telemetry-k8s-tests_istio

integ-distroless-k8s-tests_istio
73caa0e469813285863fa6b32de4f9ba23dff4c5
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
73caa0e469813285863fa6b32de4f9ba23dff4c5
link
/test integ-ipv6-k8s-tests_istio

gencheck_istio
806d25e13f91c49397c8c8879c1feae21d2d1ea3
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
7b150efc89fda3c595b3dde5730ba8e55a45a65f
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
73caa0e469813285863fa6b32de4f9ba23dff4c5
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
73caa0e469813285863fa6b32de4f9ba23dff4c5
link
/test integ-telemetry-k8s-tests_istio

gencheck_istio
806d25e13f91c49397c8c8879c1feae21d2d1ea3
link
/test gencheck_istio

analyze-tests_istio
806d25e13f91c49397c8c8879c1feae21d2d1ea3
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
7b150efc89fda3c595b3dde5730ba8e55a45a65f
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
73caa0e469813285863fa6b32de4f9ba23dff4c5
link
/test integ-telemetry-k8s-tests_istio

gencheck_istio
806d25e13f91c49397c8c8879c1feae21d2d1ea3
link
/test gencheck_istio

analyze-tests_istio
806d25e13f91c49397c8c8879c1feae21d2d1ea3
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
806d25e13f91c49397c8c8879c1feae21d2d1ea3
link
/test gencheck_istio

analyze-tests_istio
806d25e13f91c49397c8c8879c1feae21d2d1ea3
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
806d25e13f91c49397c8c8879c1feae21d2d1ea3
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
806d25e13f91c49397c8c8879c1feae21d2d1ea3
link
/test gencheck_istio

integ-pilot-k8s-tests_istio
806d25e13f91c49397c8c8879c1feae21d2d1ea3
link
/test integ-pilot-k8s-tests_istio

lint_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
806d25e13f91c49397c8c8879c1feae21d2d1ea3
link
/test integ-pilot-k8s-tests_istio

lint_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test lint_istio

analyze-tests_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
806d25e13f91c49397c8c8879c1feae21d2d1ea3
link
/test integ-pilot-k8s-tests_istio

lint_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test lint_istio

analyze-tests_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test analyze-tests_istio

gencheck_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test gencheck_istio

unit-tests_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
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 integ-pilot-multicluster-tests_istio

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
806d25e13f91c49397c8c8879c1feae21d2d1ea3
link
/test integ-pilot-k8s-tests_istio

lint_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test lint_istio

analyze-tests_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test analyze-tests_istio

gencheck_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test gencheck_istio

unit-tests_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
806d25e13f91c49397c8c8879c1feae21d2d1ea3
link
/test integ-pilot-k8s-tests_istio

lint_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test lint_istio

analyze-tests_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test analyze-tests_istio

gencheck_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test gencheck_istio

unit-tests_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test unit-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
806d25e13f91c49397c8c8879c1feae21d2d1ea3
link
/test integ-pilot-k8s-tests_istio

lint_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test lint_istio

analyze-tests_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test analyze-tests_istio

gencheck_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test gencheck_istio

unit-tests_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test unit-tests_istio

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

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

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
806d25e13f91c49397c8c8879c1feae21d2d1ea3
link
/test integ-pilot-k8s-tests_istio

lint_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test lint_istio

analyze-tests_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test analyze-tests_istio

gencheck_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test gencheck_istio

unit-tests_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test unit-tests_istio

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

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

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

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

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

Test name
Commit
Details
Rerun command

lint_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test lint_istio

analyze-tests_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test analyze-tests_istio

gencheck_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test gencheck_istio

unit-tests_istio
ba28c1a177d9b066f11509372199fbb00b28a1f3
link
/test unit-tests_istio

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

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

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

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

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

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

Test name
Commit
Details
Rerun command

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

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

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

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

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

analyze-tests_istio
8a2abb60dc492d4cc34d0a4b61cd23e3a268d94e
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.

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
8a2abb60dc492d4cc34d0a4b61cd23e3a268d94e
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
8a2abb60dc492d4cc34d0a4b61cd23e3a268d94e
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

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

/test integ-pilot-multicluster-tests_istio

/retest

/test all

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

Test name
Commit
Details
Rerun command

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

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

Test name
Commit
Details
Rerun command

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

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

Test name
Commit
Details
Rerun command

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
a6d13ec1e2d14e9b6f399e4be7f17163e3cf3ffa
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
a6d13ec1e2d14e9b6f399e4be7f17163e3cf3ffa
link
/test analyze-tests_istio

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

gencheck_istio
6fb94d742f865174d03ab9186c81a7aa20470ae0
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.

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

Test name
Commit
Details
Rerun command

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

gencheck_istio
6fb94d742f865174d03ab9186c81a7aa20470ae0
link
/test gencheck_istio

analyze-tests_istio
6fb94d742f865174d03ab9186c81a7aa20470ae0
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.

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

Test name
Commit
Details
Rerun command

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
fd6b2fcafce7df3afa77996e9a0fe1cfb3a13a15
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

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

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

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

Test name
Commit
Details
Rerun command

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

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

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


vieb: 9.5.0 -> 9.5.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/Jelmerro/vieb/releases.
meta.description for vieb is: Vim Inspired Electron Browser
meta.homepage for vieb is: https://vieb.dev/
meta.changelog for vieb is: https://github.com/Jelmerro/Vieb/releases/tag/9.5.1
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 9.5.1 with grep in /nix/store/v3wwrbp85qh6dp4jmr3kfmb3c551xj30-vieb-9.5.1
found 9.5.1 in filename of file in /nix/store/v3wwrbp85qh6dp4jmr3kfmb3c551xj30-vieb-9.5.1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
vieb

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/v3wwrbp85qh6dp4jmr3kfmb3c551xj30-vieb-9.5.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A vieb https://github.com/r-ryantm/nixpkgs/archive/ee7592ed1565bf253d62a022effe5c53a4086f29.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/v3wwrbp85qh6dp4jmr3kfmb3c551xj30-vieb-9.5.1
ls -la /nix/store/v3wwrbp85qh6dp4jmr3kfmb3c551xj30-vieb-9.5.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

vieb

Maintainer pings
cc @gebner @fortuneteller2k for testing.

Seems like someone should get a proper update script set up for this, given how often it updates and how often the package.json changes as well.

Well, I wrote an update script, despite not really knowing how nixpkgs-update or yarn work. Please do check my work.


Improvement: Add pod labels to Assessment Reports

Is your feature request related to a problem? Please describe.
Assessment reports today don't include pod labels. Pod labels can potentially be used by systems that process assessment reports to match those assessments better to customer workloads through different criteria. For example, on large microservice architectures some teams might decide to add certain tags to the pods as labels, e.g. keywords identifying the owning teams or some other internal metadata that makes sense to the customer.
Describe the solution you'd like.
I would like to have pod labels included in the assessment reports.

Thanks for proposing the issue, now the initial requirement has been resolved by the new scanner proposed in https://github.com/vmware-tanzu/cloud-native-security-inspector/pull/213 , you can add whatever you want in the new scanner. Thus we can close this issue.


optimize:set the best anchor of target node when the user is dragging for creating edge between two nodes

current situation:

The best anchor of target node is the closest anchor from the position of mouse.  But i expect it should be closer to the source node;
Like this:

你提的代码会导致用户无法选择距离自己mouseup事件最近的锚点，只能连接离起点最近的锚点，这个策略不适用所有情况。


Support basic authentication with SPARQL data source

The SPARQL data source does not support authentication, so we need to add methods setUsername and setPassword and then make it pass these to the SparqlClient, which must be extended to actually send these to the server.

Implemented in pull request #199.


Allow calls with args that are subtypes of params, enable partial application

TODO:

[ ] differentiate between unifying a call vs unifying two lambdas when assigning or passing a lambda as a param

Codecov Report

Merging #150 (77a7028) into main (49fa1c0) will increase coverage by 0.06%.
The diff coverage is 98.68%.

@@            Coverage Diff             @@
##             main     #150      +/-   ##
==========================================
+ Coverage   90.92%   90.99%   +0.06%
==========================================
  Files          35       35
  Lines        3724     3786      +62
==========================================
+ Hits         3386     3445      +59
- Misses        338      341       +3

Impacted Files
Coverage Δ

crates/crochet_infer/src/types/type.rs
70.09% <50.00%> (-0.39%)
:arrow_down:

crates/crochet_infer/src/context.rs
74.50% <100.00%> (ø)

crates/crochet_infer/src/infer.rs
87.57% <100.00%> (+0.33%)
:arrow_up:

crates/crochet_infer/src/lib.rs
99.06% <100.00%> (+0.09%)
:arrow_up:

crates/crochet_infer/src/substitutable.rs
87.20% <100.00%> (+0.15%)
:arrow_up:

crates/crochet_infer/src/util.rs
93.96% <100.00%> (ø)

Continue to review full report at Codecov.

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


4.11 support?

Hi All! I was wondering if it was possible to update the template to 4.11? I have read that there are changes to the VR camera in 4.11. I am attempting to do that now, so that the camera is placed off the floor, though I have very limited experience with UE at the time of writing. I am sure an expert will do a far better job than me.

Sorry, I have stopped working on this template in order to pursue a video series https://www.youtube.com/c/mitchsvrlab/


Need to restart everytime I install or remove a plugin

VSCode Version:1.0.0
OS Version: OSX 10.11.4

Steps to Reproduce:

ext install vim

** Restart **

remove plugin vim

** Restart **

This is as designed.


Struc syntax not recognized

Not sure if this is an issue or I was just doing it wrong, but I was not able to generate a structure using this module, I ended up creating a "dummy" edge and replacing that with the structure syntax after creating the graph object.

Can you give me a sample of a working DOT text showing the structure. I can try to work backward from that.

A good example can be found here:
https://www.flickr.com/photos/kentbye/1156412078
digraph structs {
node [shape=record];
struct1 [shape=record,label=" left| middle| right"];
struct2 [shape=record,label=" one| two"];
struct3 [shape=record,label="hello\nworld |{ b |{c| d|e}| f}| g | h"];
struct1:f1 -> struct2:f0;
struct1:f2 -> struct3:here;
}

I've been using it for embedding images using struct and inline html

I have some local changes that should resolve this. I do need to rework a bunch of my unit tests before I merge the changes.

Resolved in pull request https://github.com/KevinMarquette/PSGraph/pull/12


Use separate geiser REPLs per project

By default geiser will re-use an existing REPL with the same interpreter.  This doesn't work well when with multiple projects using dir-locals or direnv to provide project-specific settings that affect the REPL (ie. binary and library paths).
Support for per-project REPLs was added upstream; this patch enables it by default for doom.
Also disabling geiser-smart-tab-p because TAB needs to stay in its lane.
@elais ping

Looks like a great change to me. I don't care about the smart tabs bit, could be either/or for me.

Makes sense to me, thanks!


Security Warning

I'm not sure that this actually matters to anyone, but when building a license file for a distribution I generally copy-paste the Package name into my browser. In the case of this Package, it sends you to a domain not controlled by Redhat.
Sorry if this is just bloat, but wanted to at least alert the potential security concern.
     Name: KEYCLOAK.NET
    Registry Domain ID:<PHONE_NUMBER>_DOMAIN_NET-VRSN
    Domain Status:

    clientDeleteProhibited

    clientTransferProhibited

    clientUpdateProhibited
    Nameservers:

    NS73.DOMAINCONTROL.COM

    NS74.DOMAINCONTROL.COM

Dates

    Registry Expiration: 2021-06-17 05:34:44 UTC
    Created: 2017-06-17 05:34:44 UTC

Thanks @mnoseworthy


Docs(README): Add netlify preview badge for templatestudio V2 - 94

Signed-off-by: Niladri Dutta<EMAIL_ADDRESS>Update README
Issue #94
Changes

Added netlify preview badge for template studio V2 in README as discussed here  https://github.com/accordproject/template-studio-v2/pull/95#issuecomment-538174787

@irmerk I have created this PR related to #94 . Can you please review it?

@Michael-Grover thoughts on this? I think it's an improvement over just a link.

@irmerk I think this new badge is nice, but I think we should keep the traditional hyperlink in addition to it. For non developers or people not familiar with Netlify, it's very easy to not realize the badges are buttons, even if they say they go to a preview.

@Niladri24dutta sorry, I may have overdone it by thinking this was a good change.

@Niladri24dutta sorry, I may have overdone it by thinking this was a good change.

it's fine I am keeping the badge as well as the hyperlink. Will it be ok ? @Michael-Grover

@Michael-Grover Can you please review it once?

@Niladri24dutta thanks 👍


API to integrate nodes into application

Hi,
Is it planned to expose API to embed mq server node into stateful application shard? And use local transports like channels to serve jobs for local partitions?

Yes, this is possible with the design we have planned. In our planned design, our workers listen on a channel for requests. When used as a server, a REST API server enqueues requests on the sending end of the channel.
However, in this case, there has to be a library to route messages to the threads serving that partition. Also one would need some other web APIs for replication. I'm unsure how the design would accommodate membership and replication in this case.
However, you can definitely have a single node single thread persistent queue that is locally available to your application.

Closing this issue for now.


Use SkyOffsetFrame for TelescopeFrame and NominalFrame

It sound like we could just use astropy's SkyOffsetFrame for TelescopeFrame and NominalFrame, as these are basically AltAz Frames offset from the telescope pointing position or an arbitrary sky position.

http://docs.astropy.org/en/stable/_modules/astropy/coordinates/builtin_frames/skyoffset.html#SkyOffsetFrame

Looks nice!

Done in #896


updated version of #66

requested by metherul on discord
also fixes some warnings (which involves a ctor update)
everything seems to work great, thanks to vgskye for doing the actual work on this!
(cc #66)

A huge thanks to @vgskye for taking the initiative on this PR. Linux support wooooo


Bump version of sqlparser-derive to 0.2.2

As pointed out by @dzil123  https://github.com/sqlparser-rs/sqlparser-rs/issues/1054#issuecomment-1874696014 I apparently did not publish a version of sqlparser-derive that uses the new version of syn:

Just letting you know, the latest version of sqlparser-derive 0.2.1 is still on syn 1.0: https://crates.io/crates/sqlparser_derive/0.2.1/dependencies

So let's bump the version and try to publish again

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

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 87.812%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
18739

Relevant Lines:
21340

💛  - Coveralls


Seems to be a maximum number of different sounds able to be played

I'm creating a soundboard that has 112 sounds right now, however when I try to play them all one after another they stop working after the 50th sound. No matter what order I play the sounds, after 50 they stop working. Is there a max amount of sounds that can load, and if so how can I increase that limit?

Looks like a limitation of AVFoundation. Have you tried changing the category?
Sound.category = .playback

No good. Many games use more than 50 sounds, would two separate Sound instances work, if I were to alter the class methods appropriately?

Try changing number of players per sound.
Sound. playersPerSound = ...
Default is 5.

Thanks for the help! I found that raising this number actually made the problem worse. The problem is with too many players. Lowering it proportionally raised the amount of different sounds I could have. However I was able to clear the sounds that built up by setting the playersPerSound (even to the same number) because the setter clears out the sounds array. So my solution is to set playersPerSound ever so often (I just do it every time I call stopAllSounds).


Is there any way to get feedback during training?

I don't see any kind of option for verbosity. It would be nice to see the progression of loss values over training. Does anything like this exist?

My mistake, it does indeed exist.


Set selected option of a SelectField after form initialization

Currently, there's no way to specify which option should be selected in a SelectField
Trying to set form.select.default has no effect after form is rendered
There is also NO documentation for this.

That would be part of WTForms, not this extension.


This update of lua-fzf will cause the plugin to malfunction.

feat(highlights): added new default highlights groups:

Hi @SunJun8
I'm on fzf-lua 0cb40d4 and don't see any issue.
Can you share the error msg?

Hi @SunJun8
I'm on fzf-lua 0cb40d4 and don't see any issue.
Can you share the error msg?

There is no problem now, it should have been fixed in feat(highlights): major refactor, see below

Thanks @SunJun8 for bringing my attention to this commit.
I tried using ansi_from_hl() but those colors are not as vibrant as ansi_codes().
Maybe if ansi_codes() is removed altogether, I'll move to ansi_from_hl().


Use RGB values to Color Elements

Challenge Name

Issue Description

Browser Information

Browser Name, Version:
Operating System:
Mobile, Desktop, or Tablet:

Your Code

Screenshot

Could you provide less information please? :)

@mrshabi Thank you for reporting this issue. You've provided no information so far. I'll be closing this as there's no information but if you can reply back with more information about your issue, we'll open this back up.
This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the "help" button on the challenge on freeCodeCamp, which will take you to the help chatroom for that specific challenge. You can also view our full list of official chatrooms.
If you think I'm wrong in closing this issue, please reopen it and add further clarification. Thank you, and happy coding!


Complete Part 2

Looks great overall! To enhance security, consider implementing hashing for passwords instead of storing them directly. Also, as Jeremy suggested, you could introduce a layered structure: create a kernel for basic message manipulation (like adding/removing characters) and a secondary layer for defining encryption methods. This will make it easier to extend and maintain. Great work so far!


Multiple account List is missing in Design (Account Detail)

Users can create multiple Accounts & check their wallet Balance
Send & Receive Screens is also missing
currently, Account detail shows single account.
https://xd.adobe.com/view/81a8ea3a-75a9-4eb8-9da7-b5a41d617d7a-d4fb/screen/f208c111-49c0-4d1f-b4b2-7b5c003a3189/specs/

multiple account screen already exists- nothing will change there
add account: https://xd.adobe.com/view/81a8ea3a-75a9-4eb8-9da7-b5a41d617d7a-d4fb/screen/b55a662e-19d6-44d5-b0c9-cef5e2904b04/ (i'll add illustrations later)
receive: https://xd.adobe.com/view/81a8ea3a-75a9-4eb8-9da7-b5a41d617d7a-d4fb/screen/d1751fc3-f634-48ff-b816-ff6f40e9a5cf/
send: https://xd.adobe.com/view/81a8ea3a-75a9-4eb8-9da7-b5a41d617d7a-d4fb/screen/b93e6885-1a73-48fe-8ec5-b61d236dac89/

the old design of hexa is not required


Adding flex to parent makes Photo component image disappear

I'm trying to create a custom module with image and text side-by-side using flex-row. But by adding flex either to parent element or the Photo component itself (via className prop) makes the image disappear.

                <Photo
                    photo={items[0].customerPhoto}
                />

                        {items[0].text }

I've tried changing the layout prop to fill and contain but it didn't help. Wrapping the Photo into a div of its own also didn't help. Tried with and without hasDisplayOptions in the schema (with and without setting Aspect Ratio in Sanity), but no difference.
Assuming it's a CSS issue but can't figure out what's causing it.

Hey there @ansmlc the reason your image appears to disappear (see what I did there?) is because when you set flex on the parent container, the <Photo /> element doesn't have a known width, and by default flex` items do not grow to fill the container.
What you need to do is give a width to the <Photo /> component. Simply adding w-full should do the trick to make it take up the width of the flex container.
I hope that helps, let me know if you have any other issues!


No Achievements displayd

problem solved, restarted steam and sam could connect again

Temporary fix: open the game page (don't need to launch the game) in your Steam Library before opening it with SAM.

Fixed by b3a66df0d1a870e1646a259698a670f6884fa7c9.


AIP-7038: Sort list of namespaces and deduplicate if multiple RoleBindings exist

Builds on the original changes seen in: https://github.com/zillow/kubeflow/pull/4/files

LGTM


Order By custom field.

[symfony3, doctrine orm]
Hi everyone.
I create custom date in ->search() for sorting my items by this field, create name for this:
"(certificate.price) - ((certificate.price / 100) * (certificate.discount)) AS total_price",
but i cant use them in ->andWhere(), i write formula again.
Can i use something this name "total_price" without "(certificate.price) - ((certificate.price / 100) * (certificate.discount))"
/**
     * @param null $category_parent
     * @param null $category_children
     * @param null $chose_field
     * @param null $more_than
     * @param null $less_than
     * @return \Doctrine\ORM\Query
     */
    public function findCertificateCatalogQuery(
        $category_parent = null,
        $category_children = null,
        $chose_field = null,
        $more_than = null,
        $less_than = null
    ) {
        $qb = $this->createQueryBuilder('certificate');

        $qb
            ->select(
                'certificate, category, (certificate.price) - ((certificate.price / 100) * (certificate.discount)) AS total_price'
            )
            ->leftJoin('certificate.category', 'category');

        if ($category_parent == 'all' and $category_children == 'all') {
            // Select all.
            $qb
                ->andWhere('category.id >= 0');
        } elseif ($category_parent !== 'all' and $category_children == 'all') {
            // Select parent and children.
            $qb
                ->orWhere('category.id = :parent_category_id')
                ->orWhere('category.parent = :parent_category_id')
                ->setParameter('parent_category_id', $category_parent);
        } else {
            // Select children.
            $qb
                ->andWhere('category.id = :children_category_id')
                ->setParameter('children_category_id', $category_children);
        }

        if ($more_than !== null) {
            $qb
                ->andWhere('(certificate.price) - ((certificate.price / 100) * (certificate.discount)) >= :more_than')
                ->setParameter('more_than', $more_than);
        }

        if ($less_than !== null) {
            $qb
                ->andWhere('(certificate.price) - ((certificate.price / 100) * (certificate.discount)) <= :less_than')
                ->setParameter('less_than', $less_than);
        }

        if ($chose_field !== null) {
            if ($chose_field == 'price') {
                $qb
                    ->addOrderBy('certificate.'.$chose_field, 'ASC')
                    ->addOrderBy('total_'.$chose_field, 'ASC');
            } elseif ($chose_field == 'name') {
                $qb
                    ->addOrderBy('certificate.'.$chose_field, 'ASC');
            }
        }

        // For pagination
        // example: https://stackoverflow.com/questions/30458347/query-builder-and-group-by-on-two-columns-in-symfony2-doctrine-generate-duplic
        //        $qb
        //            ->setMaxResults($pagination)// limit
        //            ->setFirstResult($pagination * $page);

        return $qb->getQuery();
    }

No, you can't refer to a column alias in the WHERE clause.
It's the same with SQL:
https://stackoverflow.com/questions/11182339/reference-alias-calculated-in-select-in-where-clause

@MaximStrutinskiy you should be able to use aliases In HAVING clause.

Closing as per @Seb33300's comment.

This issue is confusing, whether the original title as the last one refers to the ORDER BY clause, but this was closed per @Seb33300's comment, which refers to the WHERE clause.
As workaround you can use the field position in SELECT clause (tested in DBAL layer):
$qb
    ->select('o.name', 'SUM(o.value) / COUNT(o.id) * 100 AS `percent`')
    // ...
    ->orderBy('2', 'DESC') // order by percent, desc
;

Even though MySQL, SQL Server and probably others, support alias in order by clause.


build with ndk

Do I have to put the source in AOSP to build?  is it possible to build with ndk?

The Android build produces an AOSP system binary that you'd run on the
commandline via ADB. It would be interesting to have an NDK library build
target for android apps, but there isn't one as of now.
On Tue, Dec 27, 2022 at 11:24 PM ted @.***> wrote:

Do I have to put the source in AOSP to build? is it possible to build with
ndk?
—
Reply to this email directly, view it on GitHub
https://github.com/stressapptest/stressapptest/issues/101, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADMRIIK6TV4CTVNNJE4NIK3WPPTJLANCNFSM6AAAAAATLAVJYM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


[Bug]: can not change GOPROXY endwith ",direct"

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Environment

Version or commit-id: 9b7728e22beda9866614e030cdd6be36807149d2
OS type: e.g. ubuntu22.04

Issue Description
when I use “ sudo mo_ctl set_conf GOPROXY="https://proxy.golang.org,direct,"，this is what I get :
cyan@cyan / [2]> sudo mo_ctl set_conf GOPROXY="https://proxy.golang.org,direct,"
2023-08-24 12:03:30.728 UTC+0800    [INFO]    Try to set conf: GOPROXY=https://proxy.golang.org
2023-08-24 12:03:30.735 UTC+0800    [INFO]    Setting conf GOPROXY=https://proxy.golang.org
2023-08-24 12:03:30.744 UTC+0800    [ERROR]    Conf direct is an invalid format, please set conf as key=value, skipping
Steps to Reproduce
sudo mo_ctl set_conf GOPROXY="https://proxy.golang.org,direct,"
Additional information
get rid of ",direct " to pass.
sudo mo_ctl set_conf GOPROXY="https://proxy.golang.org"

retest successful


Copying document sets collection based off new uri

Changes in this PR:

Renamed copy_judgment to copy_document
copy_document now adds the document to the appropriate collection based on the uri.
updated changelog

Trello card / Rollbar error (etc)
https://trello.com/c/0Q5fI6gA/1072-ingesting-uri-parse-failures-not-being-added-to-judgment-or-press-summary-collection

This will be a breaking change for the editor -- recommend we have an alias for the original name which we can remove later.

This will be a breaking change for the editor -- recommend we have an alias for the original name which we can remove later.

discussed on slack - I will update editor ui once this is merged in.


Fix leader election

Fix https://github.com/argoproj-labs/applicationset/issues/124

/assign @jgwest


fix(space-wizard): improved pf dropdown with descriptions

improved wizard single select drop down to conform to patternfly and also show descriptions

There were the following issues with your Pull Request

Commit: 4654ad59eb0826dad2c47edae61b95ca6409acb1
Your subject line is longer than 50 characters

Guidelines are available at https://github.com/fabric8io/fabric8-ui

This message was auto-generated by https://gitcop.com

Can one of the admins verify this patch?

@mitchharpur snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-954-fabric8-ui.int.rdu2c.fabric8.io

[test]


Create AlbumThingView

If you want to view all pictures with a thing in it, you would navigate to albums > things. When clicking on an album, it reroutes it to the search with the thing name as a query. This leads to empty / different results, because a) not all attributes are relevant for search or b) semantic search is activated, and it will now search based on the faiss index.
Instead, we should create a view for viewing all photos with a thing in it, similar to how viewing of persons / places is done. We have to add this new view in the frontend and create and expose the queries in the backend.

It's now implemented


Jump to caret does not keep a correct stack when there are vector arrays to store common variables between methods and blocks

Before creating a block, it uses a vector array that is on the stack to share variables with the full block closure that is going to be created.

This array is then popped to create the block closure.
However, if we jump to caret before a block closure creation, it does not push it on the stack:

As a result, when we create the block (by stepping over its creation or jumping into it), it pops the array that is used for the whole context, that  has disappeared then. So we can't access the shared variables anymore

This is because this array of shared variables is pushed by a bytecode mapped to the node just before the block node, which causes a problem if the block node is the first node to be executed in the first statement, as in that case, the bytecode of interest is bound to the method node, which is the node before the block node. This is a problem because jumpToCaret does not step the method node's bytecodes (and it can't otherwise it would recreate the temp variables and we would lose their value by jumping to caret)

This is a problem because jumpToCaret does not step the method node's bytecodes (and it can't otherwise it would recreate the temp variables and we would lose their value by jumping to caret)

Mmh this looks like we could actually step . From what I see, temps are not created on the method node?
It contradicts my analysis from few months ago so I should investigate more.
Anyway, we need to skip the creation of the temp vector at least, I think


Stray file with vcpkg_extract_source_archive_ex and NO_REMOVE_ONE_LEVEL

Describe the bug
A clear and concise description of what the bug is.
Environment

OS: Windows
Vcpkg package management program version 2019.09.12

To Reproduce
Use a port file with the NO_REMOVE_ONE_LEVEL of vcpkg_extract_source_archive_ex . Example:
vcpkg_download_distfile(ARCHIVE
    URLS "https://github.com/Genymobile/scrcpy/releases/download/v1.10/scrcpy-win64-v1.10.zip"
    FILENAME "scrcpy-win64-v1.10.zip"
    SHA512 04fccaffb83ea4e07dc50fe49ca2de03d1ff53ca8b96e2de72569e0d6173b861cdab12c5a50b77776fd7d701338029c52f124c95ba84928b978788ad8ac1c604
)
vcpkg_extract_source_archive_ex(
    OUT_SOURCE_PATH ARCHIVE_EXTRACTED
    ARCHIVE ${ARCHIVE}
    REF "scrcpy"
    NO_REMOVE_ONE_LEVEL
)
file(INSTALL ${ARCHIVE_EXTRACTED}
    DESTINATION ${CURRENT_PACKAGES_DIR}/tools/${PORT}/
    RENAME scrcpy
)

the installation will contain a scrcpy-win64-v1.10.zip.extracted file.
One can workaround this by modifying the file command like this:
file(INSTALL ${ARCHIVE_EXTRACTED}
    DESTINATION ${CURRENT_PACKAGES_DIR}/tools/${PORT}/
    RENAME scrcpy
    PATTERN "**/*.extracted" EXCLUDE
)

Expected behavior
No stray .extracted file appears

I'll take a look and see if i can come up with a fix for this

Looks like this issue persists even when not using NO_REMOVE_ONE_LEVEL. Is it possible that it's this specific package that's causing the issue?

@vpaladino778 The port file is the one above. I also saw this with several other packages so I suppose this is a systemic issue, see this screenshot from my build tree:


[Feature Request] Upgrade go-jwt to 4.x for full Go module support

Is your feature request related to a problem? Please describe.
MSAL currently depends on go-jwt 3.2.1, but this version is missing Go module support.
This causes some issues when pulling MSAL dependencies into a project that uses modules.
Describe the solution you'd like
Upgrade to go-jwt 4.x.
Describe alternatives you've considered
N/A
Additional context
go-jwt had some breaking changes, so upgrading might not be perfectly seamless.

done in #328


Unbounded BSI fields

Description
When ingesting new data, it is often unknown ahead of time what range of values an integer might take. It would be convenient if one could create a BSI field without specifying a range up front. As values came in, the field would add rows to itself as necessary.
This flexibility would allow people to write less code/configuration for ingesting data.
Because ranges can start and end anywhere in positive or negative integers, we'd have to make some initial assumptions about the field, and have the ability to re-arrange things if necessary.
Success criteria (What criteria will consider this ticket closeable?)
Not needing to define field ranges ahead of time when defining BSI fields.

Per conversation with @travisturner today:
We should be able to move the not-null bitmap to position 0, then, if we assume a minimum value for each field, we should be able to add new bitmaps to increase the maximum value as needed.
The case where the minimum value changes is trickier as existing data would need to be rewritten - the majority of use cases would probably be supported fairly well by assuming 0 for positive values and some large negative number (-2**31)? for negative values.

We just discussed this IRL. Is it possible to treat all fields as being based on -intMax and then track the actual min and max, and optimize queries based on which rows you know are going to be all 0 or all 1 based on the min and max.
Not sure how well this would work, needs to be thought about.

I don't think basing the range on -intMax will work.
If we look at an 8-bit version, the values would be represented as:
  -128 -127 ... -1   0   1 ... 126  127
0   -    1       1   -   1      -   1
1   -    -       1   -   -      1   1
2   -    -       1   -   -      1   1
3   -    -       1   -   -      1   1
4   -    -       1   -   -      1   1
5   -    -       1   -   -      1   1
6   -    -       1   -   -      1   1
7   -    -       -   1   1      1   1

If I assume that everything is based off -intMax = -128, then setting two columns with field = -1 and field = 1 will set a bit in every row. In that example, even though the effective min/max range is [-1,1], we are using all 8 rows to represent that range (instead of 2 rows).
I think it's reasonable to dynamically grow the range in one direction (i.e. above the max), but changing the min would require rewriting data.

One option that I believe would be backwards compatible would be to use sign extension and add bitmaps as the required number of bits increases. It's the same idea as when you cast an int8 into an int16 in Go except that in Pilosa it might just be an int8 to an int9.
For example, here is the conversion of -10 and 10 using sign extension (https://play.golang.org/p/fH4pl1XX8OW):
int8(-10):          11110110
int16(-10):<PHONE_NUMBER>110110

int8(10):           00001010
int16(10):<PHONE_NUMBER>001010

It just takes the MSB and repeats it for all the new bits.
So for Pilosa, if we need to move from storing 8-bit values to 10-bit values then we can simply copy the 8th bitmap in the BSI into the 9th and 10th bitmap and we won't need to rewrite any values.
We can still use the min field since that'll just be the offset. (We may want to rename it though) The max field becomes irrelevant though since we can always add more bits.
Would that work?

The hard part, I think, is the existence bits, which are currently stored immediately after the highest bit, so we'd currently need to copy the 9th bit to the 11th, then copy the 8th to the 9th and 10th. So swapping to have presence bit first would simplify life. Hmm. I could see working with 2s-complement and sign extension also working, but the downside is that small negative numbers still need all their higher-order bits set, so we have to create a lot more bits. Sign-magnitude would let us extend the range without having to modify or add bits to the existing values. (Which might be a bonus; for a large data set, it becomes possible to fail partway through updating the field, and then it's very hard to tell which values were updated and which weren't.)

Yeah, I think the existence bit should probably get moved out of the last bit. That seems like a relatively quick and simple migration operation.
I see what you’re saying about sign magnitude. Do query operations become more complicated? e.g. would the Sum() operation would be the sum of the set of positive numbers minus the set of negative numbers? Maybe the performance difference would be minimal anyway.

I think for sign-magnitude, the simplest thing is to just compute the value of the non-sign-bit part of the field the same way we do now, then either multiply by -1 or choose between add and subtract based on the sign bit? I doubt the performance cost of any likely computation will be measurable. I don't even think the branch cost would likely be noticeable, but if it really was, x * 1 - (signBit << 1) is branchless, whee.

I love this discussion.
I think the ability to have arbitrarily sized integers that can easily increase their supported range will help support more varied workloads and be a cool differentiator. I especially love that we get odd-sized ints essentially for free and that they can be increased as necessary without any extra data movement - what other data system does that?
I'm not too concerned about backwards compatibility if we have to break it (and do a 2.0) or add a new field type and deprecate the existing ints, I think this functionality is worth it.
I am a little bit concerned about how sign-magnitude affects the query logic - do we effectively double the number of logical ops we have to do to serve e.g. a Range query that spans positive and negative?  I think it's more of an n+1 situation but I'd have to dig in more to be sure.