add envoy filter stats

Currently if Envoy filter is skipped, we do not have any clue why it was not skipped. This PR adds stats for Envoy filters controlled by feature flag so that it can be enabled in dev/test envs.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[X] Does not have any changes that may affect Istio users.

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

Test name
Commit
Details
Rerun command

lint_istio
1d3aa8dddda121077c4642a6fd4d445ca19c5947
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.

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

Test name
Commit
Details
Rerun command

lint_istio
87ea97e9b0092e4c6cbacd1cdb8b08e7ba95d0cc
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.

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

Test name
Commit
Details
Rerun command

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

/test integ-ipv6-k8s-tests_istio

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
07e6a28a116aa91a10c1496f82840f60f6f3c555
link
/test integ-ipv6-k8s-tests_istio

unit-tests_istio
07e6a28a116aa91a10c1496f82840f60f6f3c555
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.

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
07e6a28a116aa91a10c1496f82840f60f6f3c555
link
/test integ-ipv6-k8s-tests_istio

unit-tests_istio
07e6a28a116aa91a10c1496f82840f60f6f3c555
link
/test unit-tests_istio

integ-helm-tests_istio
07e6a28a116aa91a10c1496f82840f60f6f3c555
link
/test integ-helm-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
07e6a28a116aa91a10c1496f82840f60f6f3c555
link
/test integ-ipv6-k8s-tests_istio

unit-tests_istio
07e6a28a116aa91a10c1496f82840f60f6f3c555
link
/test unit-tests_istio

integ-helm-tests_istio
07e6a28a116aa91a10c1496f82840f60f6f3c555
link
/test integ-helm-tests_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
07e6a28a116aa91a10c1496f82840f60f6f3c555
link
/test unit-tests_istio

integ-helm-tests_istio
07e6a28a116aa91a10c1496f82840f60f6f3c555
link
/test integ-helm-tests_istio

integ-distroless-k8s-tests_istio
07e6a28a116aa91a10c1496f82840f60f6f3c555
link
/test integ-distroless-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

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

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

Test name
Commit
Details
Rerun command

lint_istio
0b6edd7a4cee2b6f6647c508eeb2a1711b17221f
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.

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

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
c65fb946946b6dff4696ac773f43990d8a1d708d
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.

/test integ-pilot-multicluster-tests_istio

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

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

Test name
Commit
Details
Rerun command

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

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-mc-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-mc-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-mc-k8s-tests_istio

integ-ipv6-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-mc-k8s-tests_istio

integ-ipv6-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-mc-k8s-tests_istio

integ-ipv6-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-mc-k8s-tests_istio

integ-ipv6-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test unit-tests_istio

integ-telemetry-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-k8s-tests_istio

integ-helm-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-helm-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-mc-k8s-tests_istio

integ-ipv6-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test unit-tests_istio

integ-telemetry-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-k8s-tests_istio

integ-helm-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-helm-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-mc-k8s-tests_istio

integ-ipv6-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test unit-tests_istio

integ-telemetry-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-k8s-tests_istio

integ-helm-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-security-k8s-tests_istio

gencheck_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-mc-k8s-tests_istio

integ-ipv6-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test unit-tests_istio

integ-telemetry-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-k8s-tests_istio

integ-helm-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-security-k8s-tests_istio

gencheck_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test gencheck_istio

release-test_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-mc-k8s-tests_istio

integ-ipv6-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test unit-tests_istio

integ-telemetry-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-k8s-tests_istio

integ-helm-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-security-k8s-tests_istio

gencheck_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test gencheck_istio

release-test_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test release-test_istio

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

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-mc-k8s-tests_istio

integ-ipv6-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test unit-tests_istio

integ-telemetry-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-k8s-tests_istio

integ-helm-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-security-k8s-tests_istio

gencheck_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test gencheck_istio

release-test_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test release-test_istio

integ-pilot-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-pilot-k8s-tests_istio

lint_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-mc-k8s-tests_istio

integ-ipv6-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test unit-tests_istio

integ-telemetry-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-k8s-tests_istio

integ-helm-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-security-k8s-tests_istio

gencheck_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test gencheck_istio

release-test_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test release-test_istio

integ-pilot-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-pilot-k8s-tests_istio

lint_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test lint_istio

release-notes_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-mc-k8s-tests_istio

integ-ipv6-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test unit-tests_istio

integ-telemetry-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-k8s-tests_istio

integ-helm-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-security-k8s-tests_istio

gencheck_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test gencheck_istio

release-test_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test release-test_istio

integ-pilot-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-pilot-k8s-tests_istio

lint_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test lint_istio

release-notes_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test release-notes_istio

integ-security-multicluster-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-security-multicluster-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-mc-k8s-tests_istio

integ-ipv6-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test unit-tests_istio

integ-telemetry-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-k8s-tests_istio

integ-helm-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-security-k8s-tests_istio

gencheck_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test gencheck_istio

release-test_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test release-test_istio

integ-pilot-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-pilot-k8s-tests_istio

lint_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test lint_istio

release-notes_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test release-notes_istio

integ-security-multicluster-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-security-multicluster-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-mc-k8s-tests_istio

integ-ipv6-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test unit-tests_istio

integ-telemetry-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-k8s-tests_istio

integ-helm-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-security-k8s-tests_istio

gencheck_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test gencheck_istio

release-test_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test release-test_istio

integ-pilot-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-pilot-k8s-tests_istio

lint_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test lint_istio

release-notes_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test release-notes_istio

integ-security-multicluster-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-security-multicluster-tests_istio

integ-operator-controller-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-operator-controller-tests_istio

integ-pilot-multicluster-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-mc-k8s-tests_istio

integ-ipv6-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test unit-tests_istio

integ-telemetry-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-k8s-tests_istio

integ-helm-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-security-k8s-tests_istio

gencheck_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test gencheck_istio

release-test_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test release-test_istio

integ-pilot-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-pilot-k8s-tests_istio

lint_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test lint_istio

release-notes_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test release-notes_istio

integ-security-multicluster-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-security-multicluster-tests_istio

integ-operator-controller-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-operator-controller-tests_istio

integ-pilot-multicluster-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-pilot-multicluster-tests_istio

analyze-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-mc-k8s-tests_istio

integ-ipv6-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test unit-tests_istio

integ-telemetry-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-telemetry-k8s-tests_istio

integ-helm-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-security-k8s-tests_istio

gencheck_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test gencheck_istio

release-test_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test release-test_istio

integ-pilot-k8s-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-pilot-k8s-tests_istio

integ-security-multicluster-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-security-multicluster-tests_istio

integ-operator-controller-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-operator-controller-tests_istio

integ-pilot-multicluster-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test integ-pilot-multicluster-tests_istio

analyze-tests_istio
65f9e183c994af7e21437a53fcb137f78fd0d340
link
/test analyze-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test gencheck_istio

unit-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test gencheck_istio

unit-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test unit-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test gencheck_istio

unit-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test unit-tests_istio

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

lint_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test gencheck_istio

unit-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test unit-tests_istio

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

lint_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test lint_istio

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

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test gencheck_istio

unit-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test unit-tests_istio

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

lint_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test lint_istio

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

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

integ-helm-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test integ-helm-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test gencheck_istio

unit-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test unit-tests_istio

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

lint_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test lint_istio

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

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

integ-helm-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test integ-helm-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test gencheck_istio

unit-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test unit-tests_istio

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

lint_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test lint_istio

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

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

integ-helm-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test integ-helm-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test gencheck_istio

unit-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test unit-tests_istio

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

lint_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test lint_istio

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

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

integ-helm-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test integ-helm-tests_istio

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

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

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test gencheck_istio

unit-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test unit-tests_istio

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

lint_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test lint_istio

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

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

integ-helm-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test integ-helm-tests_istio

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

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

analyze-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test gencheck_istio

unit-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test unit-tests_istio

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

lint_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test lint_istio

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

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

integ-helm-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test integ-helm-tests_istio

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

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

analyze-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test analyze-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test gencheck_istio

unit-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test unit-tests_istio

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

lint_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test lint_istio

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

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

integ-helm-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test integ-helm-tests_istio

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

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

analyze-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test analyze-tests_istio

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

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

integ-pilot-multicluster-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
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.

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

Test name
Commit
Details
Rerun command

gencheck_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test gencheck_istio

unit-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test unit-tests_istio

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

lint_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test lint_istio

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

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

integ-helm-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test integ-helm-tests_istio

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

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

analyze-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test analyze-tests_istio

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

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

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

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

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test gencheck_istio

unit-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test unit-tests_istio

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

lint_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test lint_istio

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

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

integ-helm-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test integ-helm-tests_istio

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

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

analyze-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test analyze-tests_istio

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

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

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

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

release-test_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
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.

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

Test name
Commit
Details
Rerun command

gencheck_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test gencheck_istio

unit-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test unit-tests_istio

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

lint_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test lint_istio

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

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

integ-helm-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test integ-helm-tests_istio

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

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

analyze-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test analyze-tests_istio

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

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

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

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

release-test_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test release-test_istio

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

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test gencheck_istio

unit-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test unit-tests_istio

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

lint_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test lint_istio

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

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

integ-helm-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test integ-helm-tests_istio

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

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

analyze-tests_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test analyze-tests_istio

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

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

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

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

release-test_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test release-test_istio

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

release-notes_istio
d4bf21c264c1188cdc1a746965761cd2a6503675
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
0e499a99603c6ac7f475947d363a907be4b86e44
link
/test integ-security-multicluster-tests_istio

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

/test integ-security-multicluster-tests_istio

@howardjohn @hzxuzhonghu can you PTAL?

The code looks good. Just doubt how helpful the figures are for users to diagnose issues.

Skipped and error metrics  would definitely tell us if there is an issue.
Ideally if we scope by proxy or namespace it would be more useful. But
would like to try this before adding that dimension
On Sat, 27 Mar 2021, 07:29 Zhonghu Xu, @.***> wrote:

The code looks good. Just doubt how helpful the figures are for users to
diagnose issues.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/31608#issuecomment-808620864, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEDINKB2B4EIK2O3STYB7U3TFU3XRANCNFSM4ZSWB6JQ
.

@hzxuzhonghu PTAL when you get chance

I don't think it's particularly useful as well - I would think in steady
state you already have lots of envoyfilter skipped, so you would somehow
have to detect and unexpected spike - seems hard to use. However, I am not
a real Istio user, so I could be wrong here :-)
On Tue, Mar 30, 2021 at 6:26 AM Rama Chavali @.***>
wrote:

I donot feel strongly as this would not tell which envoyfilter not work.
I agree with this. That is what I started with but removed tags as
unbounded tags are not recommended.
@howardjohn https://github.com/howardjohn What do you think?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/31608#issuecomment-810239920, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXPJDRTNYM57VAEWWYDTGHGOVANCNFSM4ZSWB6JQ
.

We would like to verify in a test that skipped metric is not incremented and applied is incremented before and after to validate the filter is applied correctly - That is is the usecase. So it solves that issue I think?
I agree in steady state it wont be useful - unless we tag by name or namespace which we is not recommended because it is unbounded. But assuming the skipped ones are too many probably we can tag?
Let me know what both of you think - based on that we can decide

@howardjohn @hzxuzhonghu Thinking about this more - I am leaning towards reintroducing the nodeTag or nameTag (envoy filter name) and control it via flag, defaulted to false (so that people who want to pay the price can turn it on in dev/test env). There has been lot of requests from our users to have these stats for a better feedback mechanism after applying envoy filters - otherwise they are running blind.
What do you think?

Then how about just create a z page instead of metric?

Then how about just create a z page instead of metric?

That is a good idea but the problem is users need to know which Istiod instance the proxy is connected and validate. It is difficult to in a test.

Not sure why it is difficult in a test. I assume it can be validated by ten lines of code or script. Probably I don't understand it good enough..

Not sure why it is difficult in a test. I assume it can be validated by ten lines of code or script. Probably I don't understand it good enough..

It needs to get list of istiod pods and loop through, execute and then find the right istiod pod and validate. Our framework relies on metrics to validate the test result. That is the reason.

Is there a specific concern if it is only enabled for dev envs? I assume the main concern with nodetype or nametype tag is performance and cpu utilization and hence was proposing that. Is there any other reason that I am missing?

I think config name tag might be fine. proxy name tag just seems to be too much. It effectively a memory leak, and something user could enable and shoot themselves in the foot.

I think config name tag might be fine. proxy node tag just seems to be too much. It effectively a memory leak, and something user could enable and shoot themselves in the foot.

Cool great. I will add config name tag then

@bianpengyuan @howardjohn @hzxuzhonghu Changed to use name tag with a flag defaulted to false. PTAL.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
118ec68c25460a5a550fcc5882183f0a50b863e5
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.

@howardjohn @bianpengyuan PTAL when you get chance.

@bianpengyuan Thank you. Addressed comments.
@howardjohn PTAL when you get chance

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

Test name
Commit
Details
Rerun command

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
ec9ca23d0b03e277629baaefb3b9c56a66121c38
link
/test unit-tests_istio

lint_istio
6539e7b24581285c95ce967cdebb268453bf910f
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.


Add documentation for Sidekiq process info

Thanks this is right!

Hm, actually I've been encountering some issues with the Sidekiq process stats.
When running Sidekiq via systemd and using the method in this PR to instrument, the reporter will continue to report the last RSS number after the Sidekiq process has been stopped. I am attaching images from Grafana and relevant syslog entries, but confirmed this by CURLing the reporter endpoint on the instance itself
Jul 11 19:04:35 ip-10-1-1-236 systemd[1]: Stopped Sidekiq

Jul 11 19:49:27 ip-10-1-1-236 systemd[1]: Started Sidekiq.

I will continue to look into this, just wanted to bring up in case you had any thoughts off the top @SamSaffron

Oh this is by design here:
https://github.com/discourse/prometheus_exporter/blob/master/lib/prometheus_exporter/server/sidekiq_collector.rb
At the moment the collector has not logic regarding nuking the counters when nothing has been heard.
I agree it makes sense to add an expiry in the collector... something like ... if you heard nothing from sidekiq for say 3 minutes, stop reporting the metrics.

@SamSaffron that makes sense for the sidekiq stats, I can work on implementing the expiry like you mention
What I was referring to though were the process stats (rss/etc).....those continue to be reported as the last known metric even after Sidekiq has been stopped (which I believe would be relevant to this: https://github.com/discourse/prometheus_exporter/blob/master/lib/prometheus_exporter/instrumentation/process.rb)
might need to dig a little deeper into that hook in sidekiq config to make sure its doing whats expected

The process collector actually does cycle,
https://github.com/discourse/prometheus_exporter/blob/master/lib/prometheus_exporter/server/process_collector.rb#L6
I wonder why you are having issues.
On Fri, Jul 13, 2018 at 8:55 AM, Justin<EMAIL_ADDRESS>wrote:

@SamSaffron https://github.com/SamSaffron that makes sense for the
sidekiq stats, I can work on implementing the expiry like you mention
What I was referring to though were the process stats (rss/etc).....those
continue to be reported as the last known metric even after Sidekiq has
been stopped (which I believe would be relevant to this:
https://github.com/discourse/prometheus_exporter/blob/
master/lib/prometheus_exporter/instrumentation/process.rb)
might need to dig a little deeper into that hook in sidekiq config to make
sure its doing whats expected
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/discourse/prometheus_exporter/pull/24#issuecomment-404675986,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAUXW_z_bXD3YbepHlmULUlzOhWvfT9ks5uF9P4gaJpZM4VIVq6
.

@SamSaffron welp not sure what happened or changed but a few Ansible runs later working on other stuff and it seems to have been fixed 🤷♂ Haha thanks!


Fixed Timing Issue

This is a minor timing issue, but I found that with your currently implementation, the first image would last 2x as long as it should.  The difference is slight, but by changing this one line, each image has the same length in the resulting video.
You can check out the difference with these two examples:

Without the correction: https://dl.dropboxusercontent.com/u/1000620/01_with_delay.mov (you can notice a slight delay as the first image is longer than it should be)
With the correction: https://dl.dropboxusercontent.com/u/1000620/02_without_delay.mov (all images last for the same amount of time)

Hi, You can add effects?

Nice catch!


Immediately Running a Task via Task.Run(params String[] parameters)

The Task.Run function don't seems to work.
When i go to the GUI of the Task Scheduler and click "Run" in the filemenu the task runs as intended but if i call the Run funktion on the task nothing happens.
TaskService ts = new TaskService();
TaskFolder tf = ts.GetFolder("MyTaskFolder");
Task t = tf.Tasks["MyTaskName"];
t.Run(new String[] { });
What am I doing wrong?
Anyone who can suggest anything?
Regards Flo
Originally posted: 2010-09-22T19:59:48

First of all, try replacing the last line with just t.Run(). If that doesn't work, then you may want to see if the task is disabled (under v2) or if the task is not set to run interactively it may be actually be running but in a different user session.
Originally posted: 2010-09-28T14:32:28

Thanks for the help I just tried it again before applying the changes you suggested, and it seems it has evolved^^
It runs perfectly now after lettig it sit for a view days.
Anyway best regards. I enjoy the Wrapper very much.
Originally posted: 2010-09-28T15:56:38


Definitions of "example of usage" is truncated

From<EMAIL_ADDRESS>on March 24, 2015 11:54:08
Using the latest version of ontology-metadata.owl from IAO, it looks like the definitions of example of usage ( http://purl.obolibrary.org/obo/IAO_0000112 ) is cut off. It just ends with the word not:
"A phrase describing how a class name should be used. May also include other kinds of examples that facilitate immediate understanding of a class semantics, such as widely known prototypical subclasses or instances of the class. Although essential for high level terms, examples for low level terms (e.g., Affymetrix HU133 array) are not"
Original issue: http://code.google.com/p/information-artifact-ontology/issues/detail?id=180

From<EMAIL_ADDRESS>on March 24, 2015 10:05:57
Thanks for report. I checked the IAO. The definition of 'example of usage' is exactly same as what it is now from the first release of IAO dated on Nov 2, 2009. Any suggestion to improve it?
Jie

From<EMAIL_ADDRESS>on March 24, 2015 13:59:16
I think just finishing the sentence will work! Also, I think the definitions should say "term" rather than "class name" because 1) example of usage has been used a lot with object properties as well as classes, and 2) It is about how the property/class is used rather than how the name is used.
How about:
"A phrase describing how a term should be used. May also include other kinds of examples that facilitate immediate understanding of a class semantics, such as widely known prototypical subclasses or instances of the class. Although essential for high level terms, examples for low level terms (e.g., Affymetrix HU133 array) are not necessary."
On the other hand, is it correct that this annotation property is being used with object properties? I don't see why it should not be.

I have edited this in the source and it should appear in a future release. I removed the last sentence because I don't believe it to be true. Even terms such as Affymetrix HU133 array could use a citation of a paper in which the term is used.

Now; "A phrase describing how a term should be used and/or a citation to a work which uses it. May also include other kinds of examples that facilitate immediate understanding, such as widely know prototypes or instances of a class, or cases where a relation is said to hold."

As in many cases the clarification should be split out from the definition into an editor note. Another time.


[BUG:] Description...

I installed the TheSpawn Plugin in my Server, but every time I try to join there stays Internal Server Error
In the Console stays First set a hub, but I only can set a hub if I'm on the Server.

this warning is wanted, because theSpawn needs a hub. Please join to your server and set a hub or disable hub teleport in your config and try to join again. Good luck.


Analyzer mistakenly assumes static access over cascade.

Example:
void main() {
  List..toString().log;
  double..infinity.log;
}
extension on Object? {
  void get log {
    print(this);
  }
}

In the front-end (dart2js in Dartpad) this gives one error, that infinity is not a member of Type.
In the analyzer (also in Dartpad) I get two errors:
line 2 • Instance member 'toString' can't be accessed using static access. (view docs)
line 3 • The getter 'infinity' isn't defined for the type 'Type'. (view docs)

The second error shows that the analyzer does recognize that the member access is on the Type object, not static namespace of the class.
The first error suggests that it gets confused about toString (likely all Object members) in particular.
I believe the first error from the analyzer is a bug.

@eernstg I think you just finalized a change to rules with cascade on a Type. Is the analyzer now reporting an error correctly? Is this bug no longer a bug?

At the language meeting today we just discussed the treatment of cascades where the receiver is a type literal, and we agreed that it should be a compile-time error:
void main() {
  int..toString(); // Error.
  List<String>?..toString(); // Error.
  int?..toString(); // Error.
  int..extensionMethodOnType(); // Error.
}

The work on implementing these newly specified errors will not start before Q4.
However, until then we should keep the analyzer unchanged (it currently reports an error for these constructs saying "can't be accessed using static access"), such that there will be as little breakage as possible.
The funny thing is that the analyzer actually says "The method copyRange isn't defined for the type 'Type'" when I try to do the opposite:
void main() {
  List..copyRange<int>([], 0, []); // Error.
}

Anyway, we want an error in both cases: <typeLiteral> '..', <typeLiteral> '?..' and <typeLiteral> '?.' should all become errors, such that we can consistently say that a static access uses '.' and only '.', and all the others are exclusively used with a receiver which is evaluated to an object.
So the behavior of the analyzer is perfect! (we just need to change the error message ;-).
@lrhn, do you agree that the best way ahead here would be to close this issue? Then we'll create new issues based on the new rules when they are ready. Please reopen if you disagree.


Bump GameToken solidity version to 0.8.2

Description

Checklist:

[ ] Pull Request references Jira issue
[x] Pull Request applies to a single purpose
[ ] I've added comments to my code where needed
[ ] I've updated any relevant docs
[ ] I've added tests to show that my changes achieve the desired results
[x] I've reviewed my code
[x] I've followed established naming conventions and formatting
[ ] I've generated a coverage report and included a screenshot
[x] All tests are passing locally

Gas reports still causing CI run fails...


Devdocs API explorer doesn't allow boolean as a filter term

For example for the places collection, using the me field in the JSON would be handy- IE
[me:true]
to get all places that the user has been.

Could you explain what you mean? The places endpoints aren't listed right now, but the links full=true works as a boolean?

I can't test for this at the moment, but I will close for now, if it works for current links collections.


Sentiment Analysis - Initial Configuration:

Update the ReadMe file to sketch out a possible list of steps to perform.
Create a Python script that generates a first test of a model using an IMDB dataset.

Update the ReadMe file to sketch out a possible list of steps to perform.
Create a Python script that generates a first test of a model using an IMDB dataset.


[SQA] DUT throws the Failure Response as Can not decode Data

Problem
In Thread Network Diagnostics Cluster, While reading the Security policy and Operational dataset Attribute are fails with the response as the Can not decode Data.
Expected behavior :  Value of attribute.
Actual behavior : Can not decode Data
Steps to reproduce :  ./chip-tool threadnetworkdiagnostics read security-policy 83 0,
 ./chip-tool threadnetworkdiagnostics read operational-dataset-components 83 0
System configuration:
Platform: nRF52840 DK
App :  all clusters app
commit used: c1e1d018820c0fdd51f124f607b9207f31fae2ff
Log:

[1656058651.991994][4823:4828] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0035 Attribute 0x0000_003D DataVersion:<PHONE_NUMBER>
[1656058651.992113][4823:4828] CHIP:TOO: Response Failure: Can not decode Data
[1656058651.992290][4823:4828] CHIP:EM: Sending Standalone Ack for MessageCounter:133592987 on exchange 29504i

Thread error.txt

That looks like it's using a chip-tool from before #18920 and a server from after that PR, so they disagree on the data type these attributes are supposed to be
@Saravana-kr22 Please double-check that chip-tool and the server are built from the same exact SHA?

In the latest commit c38e9159d0500a880b9c789bf5d87fa16c039633 getting the excepted outcome.


Allow custom AuthenticationProvider and AuthenticationEventPublisher

Follow up for #620. Thanks

Thanks for the PR @jebeaudet. This is now in master.


Unable to update matterjs body sprite offset

Version

Phaser Version: 3.20.1
Operating system: macOS Catalina 10.15

Description
I need to update the x and y offset of the sprite on a generated matterjs body based on the center of mass (i.e after it has been created since I don't know the values at spawn time), however when setting body.render.sprite.xOffset nothing happens. The only way I can make the offset apply is to pass it as an option to matter.add.sprite, but at that point I don't know the center of mass yet.
Example Test Code
https://codesandbox.io/s/agitated-https-cuzc2

Possibly related to #3282.

The render.sprite offsets are not used at render time, only when setting the Game Object's origin. Matter Bodies now have a new property centerOfMass which stores their com post-creation (or part setting).
They also have a new property centerOffset which can be used in conjunction with their texture frame size to set the origin, i.e.: this.setOrigin(rx + (cx / this.displayWidth), ry + (cy / this.displayHeight)); (where rx and ry are the render offsets and cx and cy are the center offsets)
Origin can be changed at any time, of course, so as long as you allow for the center of mass when doing so, this could easily be post-Body creation. You'll find all the above changes in the 3.22 release.


fix resolve current lock npe bug

What problem does this PR solve?
close https://github.com/pingcap/tispark/issues/1005

What is changed and how it works?
use current.getKey() instead of startKey
startKey maybe null, cause it means the start key of next region
Check List
Tests

No code

/run-all-tests tikv=v4.0.1 tidb=v4.0.1 pd=v4.0.1

/run-all-tests tikv=v4.0.1 tidb=v4.0.1 pd=v4.0.1


Pacstall

Please add this app into the pacstall repository. Pacstall is the AUR for Ubuntu which will allow Ubuntu users to easily install the app and receive updates very shortly after an update is released.
https://pacstall.dev/

yt-dl is already in the Ubuntu package repository. A package repository that wishes to distribute yt-dl may similarly include it, or not, especially if, unlike Ubuntu, it's prepared to update from this project frequently. Otherwise users do better to install yt-dl using Python package tools.


Javascript file size

Version
1.4.1
Test Environment
All
Current Behavior
Large file size
Expected Behavior
Smaller optional footprint
Comments
I think you guys have done a fantastic job with the features of the editor, however the filesize is very large. I'm trying to compress it down as much as possible. Currently I've manually included libraries and gotten it about half the size of your full minified js file of 1.3M
Any other tips? I'm only using the table plugin and also not using the preview mode for the markdown editor
Libraries / Files I've included

mardown-it
to-mark
squire-rte
codemirrior (I manually minified this)
highlight.js (I manually minified this)
tui-code-snippet
tui-editor-Editor.min.js
tui-editor-extTable.min.js

I'm getting pushback from our other developers about pulling in such a large library. So I'd love to get it in with the bare minimum file size. I'll probably end up lazy-loading the javascript until the user needs the editor which will also significantly reduce the initial loading time.
Can any of these dependencies go? I trimmed it as much as possible before it stopped working
Thanks!

I think i unfortunately cant even lazy load it because the editor adds custom display to the markdownit render? so if i render the markdown myself in read only mode it will look different than when tui-editors wysiwyg mode renders it

I also want to reduce the file size. The most large size of our dependencies is highlight.js. There are already issues about file size of highlight.js (#415, #335). So I will try to reduce highlight.js size by importing only the language user want.
I think that lazy loading is possible. For example Squire is not loaded until user change mode from markdown to wysiwyg. But I do not know how it will help.
This issue is difficult to solve right away, but it will be fixed in version 1.5 or 2.0.

@gregroyal
To reduce the bundle size in 2.0, the following work was done.

jQuery has been removed.
Each extension has been separated into a plugin.
highlight.js has been separated into the code-syntax-highlight plugin.
The language files (i18n) have been separated into individual files.

When I checked the issue you wrote earlier, I think you can reduce the bundle size if you disable highlight.js usage.
I'll close this issue. Please register new issues if necessary.

Awesome! is this for a later release or available right away?

@gregroyal

Awesome! is this for a later release or available right away?

TOAST UI Editor v2.0 is available now. See here.


Allow to filter by undefined fields in MongoDB

It should be possible to filter by fields that are not set (undefined) in MongoDB.
{
    findManyModel(where: { field: { isSet: false } }) { id }
}

Essentially, this would translate to something like { field: { $exists: false } } in mongospeak .

Closed by https://github.com/prisma/prisma-engines/pull/2767


Blacklist users from proxying in a server

This is now a feature - you can specify an user as a permission scope.


Support for querying data

Hi,
Where is the support for querying the data we have posted?
Thanks
Jean

Hi,
Sorry, this is not yet available, it will be very soon.
Thanks for understanding.
/Mauro


Speedup spline rendering by >10x with large splines

This is achieved in multiple steps

fix the distance cap formula
avoid re-interpolating splines for every rect
better SIMDfication

Performance could perhaps still be improved by changing the rendering method of splines in a more fundamental way.
Tested on a jxl-art file that makes heavy use of splines
Before:
1000 x 1000, geomean: 0.22 MP/s [0.22, 0.22], 5 reps, 0 threads.

No splines:
1000 x 1000, geomean: 14.05 MP/s [10.34, 14.16], 5 reps, 0 threads.

Fix distance formula:
1000 x 1000, geomean: 1.21 MP/s [1.17, 1.21], 5 reps, 0 threads.

Max butteraugli: 0.0039978079
3-norm: 0.001424

New DrawSegment:
1000 x 1000, geomean: 1.47 MP/s [1.42, 1.47], 5 reps, 0 threads.

InitializeDrawCache:
1000 x 1000, geomean: 2.91 MP/s [2.76, 2.93], 5 reps, 0 threads.

Using JXL's architecture diagram as a set of splines speed goes from 0.02 MP/s to ~0.95MP/s, for a 45x speedup, but this is still quite slow. I'll speed that one up too.

Using JXL's architecture diagram as a set of splines speed goes from 0.02 MP/s to ~0.95MP/s, for a 45x speedup, but this is still quite slow. I'll speed that one up too.

Improved this to ~15MP/s, for a total speedup of about 750x...

The size of one of the test images seems to have increased somewhat. How about a quick optipng -o7 -strip all grayscale_patches_on_splines.png splines.png to have some assurance that it is necessary?

The size of one of the test images seems to have increased somewhat. How about a quick optipng -o7 -strip all blending/grayscale_patches_on_splines.png splines.png to have some assurance that it is necessary?

Done, file sizes reduced.

FAILED: lib/CMakeFiles/jxl_dec-obj.dir/jxl/splines.cc.obj
/usr/bin/clang++-7 --target=x86_64-w64-mingw32  -DJPEGXL_MAJOR_VERSION=0 -DJPEGXL_MINOR_VERSION=6 -DJPEGXL_PATCH_VERSION=0 -DJXL_INTERNAL_LIBRARY_BUILD -D__DATE__=\"redacted\" -D__TIMESTAMP__=\"redacted\" -D__TIME__=\"redacted\" -I../ -I../lib/include -I../third_party/highway -I../third_party/brotli/c/include -Ilib/include -DHWY_BASELINE_TARGETS=HWY_SCALAR -ffunction-sections -fdata-sections -funwind-tables -Xclang -mrelax-all -Xclang -mconstructor-aliases -O3 -DNDEBUG -O2 -fvisibility=hidden -fvisibility-inlines-hidden   -Wno-builtin-macro-redefined -Wall -fmerge-all-constants -fno-builtin-fwrite -fno-builtin-fread -Wextra -Wc++11-compat -Warray-bounds -Wformat-security -Wimplicit-fallthrough -Wno-register -Wno-unused-function -Wno-unused-parameter -Wnon-virtual-dtor -Woverloaded-virtual -Wvla -Wc++2a-extensions -Wdeprecated-increment-bool -Wfloat-overflow-conversion -Wfloat-zero-conversion -Wfor-loop-analysis -Wgnu-redeclared-enum -Winfinite-recursion -Wliteral-conversion -Wno-c++98-compat -Wno-unused-command-line-argument -Wprivate-header -Wself-assign -Wstring-conversion -Wtautological-overlap-compare -Wthread-safety-analysis -Wundefined-func-template -Wunreachable-code -Wunused-comparison -Wno-c++98-compat-pedantic -Wno-cast-align -Wno-double-promotion -Wno-float-equal -Wno-format-nonliteral -Wno-global-constructors -Wno-language-extension-token -Wno-missing-prototypes -Wno-shadow -Wno-shadow-field-in-constructor -Wno-sign-conversion -Wno-unused-member-function -Wno-unused-template -Wno-used-but-marked-unused -Wno-zero-as-null-pointer-constant -DJPEGXL_ENABLE_SKCMS=1 -DJPEGXL_BUNDLE_SKCMS=1 -std=c++11 -MD -MT lib/CMakeFiles/jxl_dec-obj.dir/jxl/splines.cc.obj -MF lib/CMakeFiles/jxl_dec-obj.dir/jxl/splines.cc.obj.d -o lib/CMakeFiles/jxl_dec-obj.dir/jxl/splines.cc.obj -c ../lib/jxl/splines.cc
fatal error: error in backend: Unable to copy EFLAGS physical register!
clang: error: clang frontend command failed with exit code 70 (use -v to see invocation)
clang version 7.0.0-3~ubuntu<IP_ADDRESS> (tags/RELEASE_700/final)
Target: x86_64-w64-windows-gnu
Thread model: posix
InstalledDir: /usr/bin
clang: note: diagnostic msg: PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace, preprocessed source, and associated run script.

FAILED: lib/CMakeFiles/jxl_dec-obj.dir/jxl/splines.cc.obj
/usr/bin/clang++-7 --target=x86_64-w64-mingw32  -DJPEGXL_MAJOR_VERSION=0 -DJPEGXL_MINOR_VERSION=6 -DJPEGXL_PATCH_VERSION=0 -DJXL_INTERNAL_LIBRARY_BUILD -D__DATE__=\"redacted\" -D__TIMESTAMP__=\"redacted\" -D__TIME__=\"redacted\" -I../ -I../lib/include -I../third_party/highway -I../third_party/brotli/c/include -Ilib/include -DHWY_BASELINE_TARGETS=HWY_SCALAR -ffunction-sections -fdata-sections -funwind-tables -Xclang -mrelax-all -Xclang -mconstructor-aliases -O3 -DNDEBUG -O2 -fvisibility=hidden -fvisibility-inlines-hidden   -Wno-builtin-macro-redefined -Wall -fmerge-all-constants -fno-builtin-fwrite -fno-builtin-fread -Wextra -Wc++11-compat -Warray-bounds -Wformat-security -Wimplicit-fallthrough -Wno-register -Wno-unused-function -Wno-unused-parameter -Wnon-virtual-dtor -Woverloaded-virtual -Wvla -Wc++2a-extensions -Wdeprecated-increment-bool -Wfloat-overflow-conversion -Wfloat-zero-conversion -Wfor-loop-analysis -Wgnu-redeclared-enum -Winfinite-recursion -Wliteral-conversion -Wno-c++98-compat -Wno-unused-command-line-argument -Wprivate-header -Wself-assign -Wstring-conversion -Wtautological-overlap-compare -Wthread-safety-analysis -Wundefined-func-template -Wunreachable-code -Wunused-comparison -Wno-c++98-compat-pedantic -Wno-cast-align -Wno-double-promotion -Wno-float-equal -Wno-format-nonliteral -Wno-global-constructors -Wno-language-extension-token -Wno-missing-prototypes -Wno-shadow -Wno-shadow-field-in-constructor -Wno-sign-conversion -Wno-unused-member-function -Wno-unused-template -Wno-used-but-marked-unused -Wno-zero-as-null-pointer-constant -DJPEGXL_ENABLE_SKCMS=1 -DJPEGXL_BUNDLE_SKCMS=1 -std=c++11 -MD -MT lib/CMakeFiles/jxl_dec-obj.dir/jxl/splines.cc.obj -MF lib/CMakeFiles/jxl_dec-obj.dir/jxl/splines.cc.obj.d -o lib/CMakeFiles/jxl_dec-obj.dir/jxl/splines.cc.obj -c ../lib/jxl/splines.cc
fatal error: error in backend: Unable to copy EFLAGS physical register!
clang: error: clang frontend command failed with exit code 70 (use -v to see invocation)
clang version 7.0.0-3~ubuntu<IP_ADDRESS> (tags/RELEASE_700/final)
Target: x86_64-w64-windows-gnu
Thread model: posix
InstalledDir: /usr/bin
clang: note: diagnostic msg: PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace, preprocessed source, and associated run script.

I propose we fix this issue by getting rid of clang-7 - debian stable has >=8 now and even 18.04 has 8 in the main repos (interestingly, 7 is not in the main repos, but is in the -updates repos...)

(It is likely that this bug is finally fixed only in clang-9; it has been rediscovered multiple times under different conditions)

@deymo WDYT, should we ramp-up clang version, or we have clients who (cross-)compile JXL on clang-7?

(It is likely that this bug is finally fixed only in clang-9; it has been rediscovered multiple times under different conditions)

clang-9 is also in both ubuntu 18.04 and debian stable - for that matter, debian stable even has clang-11...

@deymo WDYT, should we ramp-up clang version, or we have clients who (cross-)compile JXL on clang-7?

IIRC we don't, at least for cross-compilation purposes.


Activity bar items should always focus on child elements

Currently if you activate the explorer sidebar when there is no folder/workspace open the focus isn't set to the Open Folder button. Additionally when an extension contributes a view that has no items (say the Bookmarks extension when you have no bookmarks yet), the focus isn't placed into the view.
Originally reported: https://github.com/microsoft/vscode/issues/83328

This is because the explorer doesn't focus on the child elements, like the other views, and the focus is on the activity bar element. Notice the focus border:

When in an empty explorer view, the focus should change to the "Open Folder" button.

GIF from @Guema:

Yeah, makes sense that the no folder explorer gets focused in this case. I can look into this

Fixed via 655e3b3e99


compose: Update icons for formatting buttons.

Fixes: #27845
Screenshots and screen captures:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[ ] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

@alya @karlstolley it looks like this reworks some of the breakpoints due to different icon sizes, so may need some extra QA.

Please pull changes from https://github.com/zulip/zulip/pull/28003

Merged, thanks @N-Shar-ma!


add CI pipeline for testing / building / releasing deb/snap/homebrew/... packages (to drop the dependency on go for installing)

I'm interested in contribute in this issue :-D


prob_log

implement prob log at RandomVariable and ProbModel classes

Now log_prob and sample methods use dictionaries where the keys are strings with the variable names:
>>> model.sample()
{'y': array([[[4.87281385, 6.11311355]]]), 'x': array([[[ 0.80738106,  0.68161732],
        [-1.19498769,  0.93624021],
        [-0.2377974 ,  0.05938201]]])}


Update poky to the latest morty revision

Connected to https://github.com/resin-os/resinos/issues/241
This should fix the issue with the file package failing to build.

Can one of the admins verify this patch?

add to whitelist

ok to test


Remove one 1.8.7 build (on the latest rubygems) from the allowed failures list

@homu r+

:pushpin: Commit 9950dc8 has been approved by segiddins

:hourglass: Testing commit 9950dc8 with merge 745660b...

:broken_heart: Test failed - status

@homu r+
this will pass once https://github.com/bundler/bundler/pull/4929 is merged

:pushpin: Commit 9950dc8 has been approved by segiddins

:bulb: This pull request was already approved, no need to approve it again.

This pull request previously failed. You should add more commits to fix the bug, or use retry to trigger a build again.
There's another pull request that is currently being tested, blocking this pull request: #4929

:bulb: This pull request was already approved, no need to approve it again.

This pull request previously failed. You should add more commits to fix the bug, or use retry to trigger a build again.
There's another pull request that is currently being tested, blocking this pull request: #4929

@homu r+

:pushpin: Commit 08b3f72 has been approved by segiddins

:hourglass: Testing commit 08b3f72 with merge 1908c7b...

:sunny: Test successful - status


[Analytics] Instrumentation Update V2

Catch-all for any issues we come up with.

[ ] Auction events
[ ] Referral screens
[ ] Analytics in our process - e.g. Danger rules?
[ ] Updated readme (Force's one is great)

Tickets left over from round one:
#2264


chore(master): release 0.1.0

:robot: I have created a release beep boop
0.1.0 (2024-10-27)
Features

autocommit (#18) (db638bd)

Bug Fixes

ci badge in readme.md (#22) (658d4ca)
consolidate package version (#24) (badedff)
explicitly state version attributes (#29) (d97ffe4)
move version to top of module (#26) (250a279)
remove dunder version (#27) (96399e7)
remove spurious comments (#31) (4d11f2f)
try just dunder version (#28) (50478bc)
update the version already, please (#32) (64ac3b5)
use release-please-manifest.json to specify version files (#30) (cab809d)
use version string for version (#25) (86820f1)
windows drivers command on pypy >= v7.3.10 (#7) (7dc5fc8)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.1.0
:sunflower:


[Feature] Sync logs to local file

Why are these changes needed?
support sync log to file in pod.
this feature is controllered by log_file  parameter in command line, default only output log to std

Related issue number
https://github.com/ray-project/kuberay/issues/593

Checks

[ ] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[x] Manual tests
[ ] This PR is not tested :(

Usage
use -logFilePath=output.txt when executing apiserver
use -log-file-path=output.txt when executing ray-operator
you can add these parameter in ENTRYPOINT of Dockerfile
then swap the based image in Dockerfile which can exec into

manual testing through replace the based image in dockerfile.
the previous image can not exec into it.

Overall the change looks good to me beside the parameter pattern

@Basasuya can you help address @kevin85421's comment?

@kevin85421 sorry for the slow reply, I have rebase the master again.

Can you add more details about how to use this feature in your PR description? This PR will be very helpful for both users and developers to debug. Thank you! Overall, the code looks good to me, and I just added some nit comments on it.

I add the detail in PR description.

@Jeffwan is this PR ready to merge? The merge is blocked by your change requests. Thank you!

@kevin85421 Yeah, it looks good to me.


controller_torque_discontinuity settings

Hello,
I am wondering whether there is a way to change the behaviour of the torque_discontinuity error. Mostly to the point of allowing larger instant changes in torque?
-Josh

This threshold is enforced by Control and cannot be changed by the user. What you can do is perform rate limiting (see tau_d_saturated in examples/joint_impedance_control.cpp).

Ok thanks, also I was wondering will there be support for sending raw torques to the robot i.e. without the gravity and friction compensation added by the robot? or is that controlled by the control too?

I just realized I never answered you again, sorry for that! I'm not sure if this will still be useful after all this time, but: as the robot will add gravity, you could try calculating and subtracting it from the torques you send in your control loop and then add your own values. Other than that, there isn't a possibility to send raw torques.
We also added more documentation about the control parameters and how the robot is controlled by libfranka.


new notifications quicktweaks

[x] the text is red but not the [1] icon (see image)
[x] cursor: pointer; should only be on the links inside the notification, not the whole area otherwise people will try to open it clicking
[ ]  some names break the line weirdly (see martin murphy in image)
[x]  [1] stays after I seen the dropdown, closed browser tab, came back. But I didn't click 'All notifications'

activating list / thumbnail view while in feed brings you to notifications, not back to feed

thumbnail view button / list view button / all notifications button - use lighter gray so hover state is more obvious

match padding between icons in top bar (space between new channel / view mode / notifs are too large, match w/ space between notifs / avatar)

[ ] Needs empty state

remove notifications subsection from user dropdown

[ ] the space between the icon and dropdown should be padding not empty, if you move the mouse from icon to drowdown not fast enough it closes
https://www.dropbox.com/s/dje034yttry1lrn/Screenshot 2016-08-15 01.59.15.png?dl=0


Update repositories.txt

I am purposefully removing libraries that I contributed from this list due to the decision by Arduino to remove attribution on their forum after people die.

Hello, I am following your work and I am concerned about this change. I think I understand the issue, but I would like to know your stance more precisely, as we currently maintain a double compilation path (arduino-cli and platformio) for our project, and we would like to know what to expect in the future.
Also, is it correct that this PR is on your repo only? I can still see your libraries in the Arduino registry.

No, I just submitted the PR to the main branch.  Most of these are redundant anyway.  Most have been replaced by code in the core.  Those are going to be deleted from my GitHub as well so they don't end up leading someone down a dead end.  The rest like R4Touch I simply do not wish to share through the Arduino library manager anymore since I cannot support it from their forum.


Recognize force_default and force_override.

These were added in Chef 11.0.0.
This will fix #181.

Why were those not generated by :generate_chef_metadata? O.o

I had no idea that existed so I did the the normal patch-y way :-)

There must be something missing from foodcritic/chef_dsl_metadata/Rakefile, as it's not covering everything. Oh well.

Any chance we can get a new release published?  This particular bug is driving me crazy... I've added # ~FC019 ignores for now but I hate to do that.

I accidentally reverted this so fixed it the right way in #364


Add 'x-request-id' when it is missing on headers

Create a filter
[ ] If a request Id is received on the headers, keep the same on the response
[ ] If the request id is missing, should add one and include on the response header

Not sure if this will be added to the project, it is used for logging trace, maybe it is too much for this project... will check after finish the existing features


Translation to Brazilian Portuguese

Thanks for your pull request. We've started a translation project on CrowdIn and Brazilian Portuguese is an option there. Can you please add your translations to CrowdIn? It'll manage the merge into Muzei's source code and updating translations as time goes on.


Releases should include precompiled bootable images

Each release should include a bootable .iso, vmlinuz, and initrd for each supported genesis OS version. This would make it much easier for downstream users to get started, and seeing as the bootable image is basically static, is removing a huge speedbump from every potential user.

this has been happening for the last few releases


Update to jsdoc 4.0

This will pick up the fix for https://github.com/jsdoc/jsdoc/issues/2036

@lheberlie - will you test this?

@lheberlie have you had a chance to test this yet?

Done at https://github.com/bsvensson/jsdoc/tree/esrijs-sdk


Is this code incomplete?

Where is the file "cli.py"?

thanks for pointing it out. Yes, cli.py was missing. This is added to the repo now.


Extracting PFS stuck at 0%

@ultimaweapon where does the emulator save the settings? I want to change the directory where games are installed but I can't get this window to show up again so I can change the location, how do I change the location?

The PKG installation not yet fully functional (actually I just finished it about 5 minutes ago but I need to test it first). Currently there is no UI to edit location to install games so you need to update it manually. On Windows it will stored in Windows Registry at HKEY_CURRENT_USER\Software\Obliteration\Obliteration. Just delete that path and run Obliteration again.

now the new build extracts the full game and solves the issue, but I think apps/games can't run yet?

Right. It cannot run any app/game yet. It may take a coupled of months for me to make it able to run a simple game that Kyty already able to run. So let's hope I got more people to help on develop this :)


chore(main): release 3.0.1

:robot: I have created a release beep boop
3.0.1 (2024-09-23)
Bug Fixes

Removes print debugging statement (2e14685)
when package is not available in Mason, then display a message instead of throwing an error (01e2ca6)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v3.0.1
:sunflower:


Idea: "squared.js"

Often in graphics dev you only need the squared result and can avoid a sqrt operation. It might be cool to expose the following:
var distSq = require('euclidean-distance/squared')

It would also go well alongside this module:
https://github.com/mattdesl/magnitude

Hi @mattdesl. Six months later, your wish is granted! For some reason I wasn't subscribed to github notifications for this repo, so I missed this issue. I just published 1.0.0 with the above-suggested squared support.


Bump Terraform from 1.0.16 to 1.2.0

https://github.com/hashicorp/terraform/blob/v1.2.0/CHANGELOG.md

I'll recreate this PR using a branch other than main. 🤦

Superseded by https://github.com/dependabot/dependabot-core/pull/5170


Add two ed-tech ideas related to MIT OpenCourseWare.

Great stuff -- would love to see these two ideas built!


I want a way to break the polyline in two, how can i do it?

Actions before raising this issue

[X] I searched the existing issues and did not find anything similar.
[X] I read/searched the docs

Is your feature request related to a problem? Please describe.
No response
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

solve it like slice tool

solved