WIP: do not merge: more assertion tests

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

/test all

/test all

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

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
af5e31a237a0877cc0f0720352ee1f1a44b37c8e
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 all

/test all

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

Test name
Commit
Details
Rerun command

unit-tests_istio
68d2c7744dce449169a51eb742a47f19236f7809
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: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
68d2c7744dce449169a51eb742a47f19236f7809
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
68d2c7744dce449169a51eb742a47f19236f7809
link
/test integ-pilot-k8s-tests_istio

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

/test all

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

Test name
Commit
Details
Rerun command

unit-tests_istio
68d2c7744dce449169a51eb742a47f19236f7809
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
68d2c7744dce449169a51eb742a47f19236f7809
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
68d2c7744dce449169a51eb742a47f19236f7809
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
68d2c7744dce449169a51eb742a47f19236f7809
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
68d2c7744dce449169a51eb742a47f19236f7809
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
68d2c7744dce449169a51eb742a47f19236f7809
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test analyze-tests_istio

release-test_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test release-test_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
68d2c7744dce449169a51eb742a47f19236f7809
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
68d2c7744dce449169a51eb742a47f19236f7809
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test analyze-tests_istio

release-test_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test release-test_istio

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

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
68d2c7744dce449169a51eb742a47f19236f7809
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
68d2c7744dce449169a51eb742a47f19236f7809
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test analyze-tests_istio

release-test_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test release-test_istio

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

lint_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test lint_istio

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

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
68d2c7744dce449169a51eb742a47f19236f7809
link
/test integ-pilot-k8s-tests_istio

analyze-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test analyze-tests_istio

release-test_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test release-test_istio

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

lint_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test lint_istio

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

unit-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
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: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test analyze-tests_istio

release-test_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test release-test_istio

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

lint_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test lint_istio

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

unit-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test analyze-tests_istio

release-test_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test release-test_istio

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

lint_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test lint_istio

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

unit-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test unit-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test analyze-tests_istio

release-test_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test release-test_istio

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

lint_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test lint_istio

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

unit-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test unit-tests_istio

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

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

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test analyze-tests_istio

release-test_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test release-test_istio

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

lint_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test lint_istio

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

unit-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test unit-tests_istio

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

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

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

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test analyze-tests_istio

release-test_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test release-test_istio

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

lint_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test lint_istio

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

unit-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test unit-tests_istio

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

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

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

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

integ-helm-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
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.

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test analyze-tests_istio

release-test_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test release-test_istio

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

lint_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test lint_istio

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

unit-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test unit-tests_istio

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

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

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

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

integ-helm-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test integ-helm-tests_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test analyze-tests_istio

release-test_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test release-test_istio

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

lint_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test lint_istio

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

unit-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test unit-tests_istio

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

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

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

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

integ-helm-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test integ-helm-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test analyze-tests_istio

release-test_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test release-test_istio

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

lint_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test lint_istio

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

unit-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test unit-tests_istio

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

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

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

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

integ-helm-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test integ-helm-tests_istio

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

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

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test analyze-tests_istio

release-test_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test release-test_istio

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

lint_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test lint_istio

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

unit-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test unit-tests_istio

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

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

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

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

integ-helm-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test integ-helm-tests_istio

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

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

gencheck_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test analyze-tests_istio

release-test_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test release-test_istio

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

lint_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test lint_istio

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

unit-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test unit-tests_istio

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

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

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

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

integ-helm-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test integ-helm-tests_istio

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

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

gencheck_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test gencheck_istio

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

integ-security-multicluster-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
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.

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test analyze-tests_istio

release-test_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test release-test_istio

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

lint_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test lint_istio

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

unit-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test unit-tests_istio

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

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

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

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

integ-helm-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test integ-helm-tests_istio

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

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

gencheck_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test gencheck_istio

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

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

integ-pilot-multicluster-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
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 all

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test analyze-tests_istio

release-test_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test release-test_istio

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

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

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

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

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

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

integ-helm-tests_istio
fb91c4717cedd39522c83b66c387050d9c1d4eb9
link
/test integ-helm-tests_istio

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

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

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

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

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

unit-tests_istio
4b7239d13754f8f8c380100bd4eaf6b2e801d137
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: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

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

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

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

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

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

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

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

unit-tests_istio
4b7239d13754f8f8c380100bd4eaf6b2e801d137
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

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

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

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

unit-tests_istio
4b7239d13754f8f8c380100bd4eaf6b2e801d137
link
/test unit-tests_istio

integ-pilot-multicluster-tests_istio
4b7239d13754f8f8c380100bd4eaf6b2e801d137
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
4b7239d13754f8f8c380100bd4eaf6b2e801d137
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 all

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

Test name
Commit
Details
Rerun command

unit-tests_istio
4b7239d13754f8f8c380100bd4eaf6b2e801d137
link
/test unit-tests_istio

integ-pilot-multicluster-tests_istio
4b7239d13754f8f8c380100bd4eaf6b2e801d137
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
4b7239d13754f8f8c380100bd4eaf6b2e801d137
link
/test integ-security-multicluster-tests_istio

lint_istio
214460c6ab12ebf332da097123cb1e596079ce75
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.

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

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
4b7239d13754f8f8c380100bd4eaf6b2e801d137
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
4b7239d13754f8f8c380100bd4eaf6b2e801d137
link
/test integ-security-multicluster-tests_istio

lint_istio
214460c6ab12ebf332da097123cb1e596079ce75
link
/test lint_istio

unit-tests_istio
214460c6ab12ebf332da097123cb1e596079ce75
link
/test unit-tests_istio

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

/test all

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

Test name
Commit
Details
Rerun command

unit-tests_istio
214460c6ab12ebf332da097123cb1e596079ce75
link
/test unit-tests_istio

lint_istio
2ae9fced0369c8c00d1d9ab9a794a7ae0f7ca52d
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.

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

Test name
Commit
Details
Rerun command

lint_istio
2ae9fced0369c8c00d1d9ab9a794a7ae0f7ca52d
link
/test lint_istio

unit-tests_istio
2ae9fced0369c8c00d1d9ab9a794a7ae0f7ca52d
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: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
2ae9fced0369c8c00d1d9ab9a794a7ae0f7ca52d
link
/test lint_istio

unit-tests_istio
2ae9fced0369c8c00d1d9ab9a794a7ae0f7ca52d
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
2ae9fced0369c8c00d1d9ab9a794a7ae0f7ca52d
link
/test lint_istio

unit-tests_istio
2ae9fced0369c8c00d1d9ab9a794a7ae0f7ca52d
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
2ae9fced0369c8c00d1d9ab9a794a7ae0f7ca52d
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
2ae9fced0369c8c00d1d9ab9a794a7ae0f7ca52d
link
/test lint_istio

unit-tests_istio
2ae9fced0369c8c00d1d9ab9a794a7ae0f7ca52d
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
2ae9fced0369c8c00d1d9ab9a794a7ae0f7ca52d
link
/test integ-ipv6-k8s-tests_istio

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

integ-distroless-k8s-tests_istio
2ae9fced0369c8c00d1d9ab9a794a7ae0f7ca52d
link
/test integ-distroless-k8s-tests_istio

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

/test all

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

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
3fbdd1ed5f818a89d20891bf7e445edc9fd6faee
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
3fbdd1ed5f818a89d20891bf7e445edc9fd6faee
link
/test integ-pilot-multicluster-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
3fbdd1ed5f818a89d20891bf7e445edc9fd6faee
link
/test integ-security-multicluster-tests_istio

lint_istio
ca30a6dc94a6dc08c22995d232c24a08427742d2
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
ca30a6dc94a6dc08c22995d232c24a08427742d2
link
/test lint_istio

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

integ-security-multicluster-tests_istio
ca30a6dc94a6dc08c22995d232c24a08427742d2
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 all

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

Test name
Commit
Details
Rerun command

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

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

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

/test all

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

Test name
Commit
Details
Rerun command

lint_istio
083daaf6f798af95775431c80fea66b96e4f5548
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.

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

Test name
Commit
Details
Rerun command

lint_istio
083daaf6f798af95775431c80fea66b96e4f5548
link
/test lint_istio

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

issue now is some ordering of token and shard ver:
2021-06-29T00:00:39.667110Z     error   ads     howardjohn: starting proxy=istio-eastwestgateway-7c47fd96fd-bsg8p.istio-system,token=3070,debug=<pending>,key=outbound|80||b.echo-1-54513.svc.cluster.local~network-1~remote~false~us-west1/us-west1-a~notunnel~d41d8cd98f00b204e9800998ecf8427e~b.echo-1-54513.svc.cluster.local/echo-1-54513~~network-1
2021-06-29T00:00:39.667189Z     error   ads     howardjohn: writing proxy=istio-eastwestgateway-7c47fd96fd-bsg8p.istio-system,token=3070,debug=ver:1,shards:0xc0044f8300,key=outbound|80||b.echo-1-54513.svc.cluster.local~network-1~remote~false~us-west1/us-west1-a~notunnel~d41d8cd98f00b204e9800998ecf8427e~b.echo-1-54513.svc.cluster.local/echo-1-54513~~network-1
2021-06-29T00:00:39.667201Z     error   ads     howardjohn: wrote proxy=istio-eastwestgateway-7c47fd96fd-bsg8p.istio-system,token=3070,debug=ver:1,shards:0xc0044f8300,key=outbound|80||b.echo-1-54513.svc.cluster.local~network-1~remote~false~us-west1/us-west1-a~notunnel~d41d8cd98f00b204e9800998ecf8427e~b.echo-1-54513.svc.cluster.local/echo-1-54513~~network-1
2021-06-29T00:00:39.745416Z     error   ads     howardjohn: starting proxy=tproxy-v1-5cc4747b45-mtl9n.echo-1-54513,token=3083,debug=<pending>,key=outbound|80||b.echo-1-54513.svc.cluster.local~network-1~remote~false~us-west1/us-west1-a~notunnel~d41d8cd98f00b204e9800998ecf8427e~b.echo-1-54513.svc.cluster.local/echo-1-54513
2021-06-29T00:00:39.746652Z     error   ads     howardjohn: writing proxy=tproxy-v1-5cc4747b45-mtl9n.echo-1-54513,token=3083,debug=ver:1,shards:0xc0044f8300,key=outbound|80||b.echo-1-54513.svc.cluster.local~network-1~remote~false~us-west1/us-west1-a~notunnel~d41d8cd98f00b204e9800998ecf8427e~b.echo-1-54513.svc.cluster.local/echo-1-54513
2021-06-29T00:00:39.821186Z     error   ads     howardjohn: wrote proxy=tproxy-v1-5cc4747b45-mtl9n.echo-1-54513,token=3083,debug=ver:1,shards:0xc0044f8300,key=outbound|80||b.echo-1-54513.svc.cluster.local~network-1~remote~false~us-west1/us-west1-a~notunnel~d41d8cd98f00b204e9800998ecf8427e~b.echo-1-54513.svc.cluster.local/echo-1-54513
2021-06-29T00:00:39.836117Z     error   ads     howardjohn: starting proxy=b-v1-5db4fc987c-xqmqk.echo-1-54513,token=3083,debug=<pending>,key=outbound|80||b.echo-1-54513.svc.cluster.local~network-1~remote~false~us-west1/us-west1-a~notunnel~d41d8cd98f00b204e9800998ecf8427e~b.echo-1-54513.svc.cluster.local/echo-1-54513
2021-06-29T00:00:39.836217Z     error   ads     howardjohn: writing proxy=b-v1-5db4fc987c-xqmqk.echo-1-54513,token=3083,debug=ver:2,shards:0xc0044f8300,key=outbound|80||b.echo-1-54513.svc.cluster.local~network-1~remote~false~us-west1/us-west1-a~notunnel~d41d8cd98f00b204e9800998ecf8427e~b.echo-1-54513.svc.cluster.local/echo-1-54513
2021-06-29T00:00:39.836237Z     error   ads     howardjohn: wrote proxy=b-v1-5db4fc987c-xqmqk.echo-1-54513,token=3083,debug=ver:2,shards:0xc0044f8300,key=outbound|80||b.echo-1-54513.svc.cluster.local~network-1~remote~false~us-west1/us-west1-a~notunnel~d41d8cd98f00b204e9800998ecf8427e~b.echo-1-54513.svc.cluster.local/echo-1-54513

token increments before shard does... it should be invalidating

/test all

/test all

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

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
083daaf6f798af95775431c80fea66b96e4f5548
link
/test integ-pilot-multicluster-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
083daaf6f798af95775431c80fea66b96e4f5548
link
/test integ-pilot-multicluster-tests_istio

lint_istio
d16cf1b096e4b057fd4fbb913d3858b73cca3e2e
link
/test lint_istio

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

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

/test all

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

Test name
Commit
Details
Rerun command

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

lint_istio
2e2dd2ef02d4bb3c21705ba7a6fdbd2e9180dffe
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.

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

Test name
Commit
Details
Rerun command

lint_istio
2e2dd2ef02d4bb3c21705ba7a6fdbd2e9180dffe
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
2e2dd2ef02d4bb3c21705ba7a6fdbd2e9180dffe
link
/test lint_istio

integ-security-k8s-tests_istio
2e2dd2ef02d4bb3c21705ba7a6fdbd2e9180dffe
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
2e2dd2ef02d4bb3c21705ba7a6fdbd2e9180dffe
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 all

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
2e2dd2ef02d4bb3c21705ba7a6fdbd2e9180dffe
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
2e2dd2ef02d4bb3c21705ba7a6fdbd2e9180dffe
link
/test integ-security-multicluster-tests_istio

lint_istio
2e2dd2ef02d4bb3c21705ba7a6fdbd2e9180dffe
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.

/test all

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

Test name
Commit
Details
Rerun command

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

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

Test name
Commit
Details
Rerun command

lint_istio
b480deb1ab882651357a38e3657dcb8d8b7b88c4
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
b480deb1ab882651357a38e3657dcb8d8b7b88c4
link
/test lint_istio

gencheck_istio
b480deb1ab882651357a38e3657dcb8d8b7b88c4
link
/test gencheck_istio

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

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

/test all

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

Test name
Commit
Details
Rerun command

gencheck_istio
b480deb1ab882651357a38e3657dcb8d8b7b88c4
link
/test gencheck_istio

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

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

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

Test name
Commit
Details
Rerun command

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

lint_istio
b480deb1ab882651357a38e3657dcb8d8b7b88c4
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
b480deb1ab882651357a38e3657dcb8d8b7b88c4
link
/test lint_istio

gencheck_istio
b480deb1ab882651357a38e3657dcb8d8b7b88c4
link
/test gencheck_istio

integ-pilot-multicluster-tests_istio
b480deb1ab882651357a38e3657dcb8d8b7b88c4
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 all

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

Test name
Commit
Details
Rerun command

gencheck_istio
b480deb1ab882651357a38e3657dcb8d8b7b88c4
link
/test gencheck_istio

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

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

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

Test name
Commit
Details
Rerun command

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

lint_istio
fc98fefc45eaafae13296596f048f382f565582c
link
/test lint_istio

gencheck_istio
fc98fefc45eaafae13296596f048f382f565582c
link
/test gencheck_istio

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

/test all

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

Test name
Commit
Details
Rerun command

gencheck_istio
fc98fefc45eaafae13296596f048f382f565582c
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
fc98fefc45eaafae13296596f048f382f565582c
link
/test lint_istio

gencheck_istio
fc98fefc45eaafae13296596f048f382f565582c
link
/test gencheck_istio

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

/test all

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

Test name
Commit
Details
Rerun command

gencheck_istio
fc98fefc45eaafae13296596f048f382f565582c
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
fc98fefc45eaafae13296596f048f382f565582c
link
/test lint_istio

gencheck_istio
fc98fefc45eaafae13296596f048f382f565582c
link
/test gencheck_istio

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

/test all

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

Test name
Commit
Details
Rerun command

lint_istio
fc98fefc45eaafae13296596f048f382f565582c
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
fc98fefc45eaafae13296596f048f382f565582c
link
/test gencheck_istio

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

@howardjohn: PR needs rebase.

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


Revamp WebSocket, TCP, UDP BBEs

Description:
Part of the revamping process of network library BBE revamp.

PR: https://github.com/ballerina-platform/ballerina-distribution/pull/3451


Updated to nightly-2022-04-18

This also fixes #907.

Yes, if not compiling from source the spirv binaries in PATH are used, so any time the github runners change those binaries there is a risk of breakage.

Yes, if not compiling from source the spirv binaries in PATH are used, so any time the github runners change those binaries there is a risk of breakage.

Can't we just pass a version to brew install? These don't even come with GHA, we appear to install them ourselves in CI explicitly.

In that case I guess you could specify the exact version, however one does that with brew.

In that case I guess you could specify the exact version, however one does that with brew.

Turns out that one does not do that with brew, and after having my optimism crushed I ended up with:

https://github.com/EmbarkStudios/rust-gpu/pull/910

(which involved digging through the spirv-tools Google Cloud Storage bucket for the right URL...)


Default Ranks (per world) not applying

Howdy Y'all,
I'm using the latest spigot (1.9.2) build and pex 1.23.4.
I have the following groups set up:
http://d.l33t.tech/uPUv/5rYZALBL
and when I join the worlds listed there... pex lists them.. but they do not apply to any users:
http://d.l33t.tech/13cCI/2KZPBA7v
Please assist! :)

Based on previous reports, there are some issues with per-world permissions on spigot 1.9. The spigot folks say the issue isn't on their side though, so we're still trying to pin down the exact cause of these issues.

Bugger. Alright. Hope we can get this fixed soon. 👍

I'm using PermissionsEx v1.22.10 with KCauldron 1.7.10 and I'm the same problem : default rank not applying to new players
simplified version of my permissions.yml :
groups:
  Ombre:
    default: true
    permissions:
    - essentials.help
    inheritance: []
    options:
      rank: '1000'
      rank-ladder: global
  Arrivant:
    permissions:
    - essentials.home
    inheritance:
    - Ombre
    options:
      rank: '990'
      rank-ladder: global
schema-version: 1
users:
  21d68a0d-15c8-432a-8e30-aa77d2e0bb4c:
    options:
      name: SkydeFR

@SkydeFR you have a different problem: the default line is an option, not at the top level.

@zml2008 Sorry I didn't know, should I open a new ticket?

@SkydeFR No, you just need to move it down:
groups:
  Ombre:
    permissions:
    - permissions.ombre
    inheritance: []
    options:
      rank: '1000'
      rank-ladder: global
      default: true

Unfortunately PermissionsEx is currently unmaintained and no further updates are planned. Because of this, all pull requests are being closed. If you are looking for an actively maintained permissions plugin, take a look at LuckPerms. It is compatible with major server platforms and can import data from PEX.


Remove markdown help files since they have moved to docs repo

PR Summary
Deleting the markdown help files. The changes have been copied to the MicrosoftDocs/PowerShell-Docs-PSGet repo. The docs repo is now the source of truth for the user documentation.
PR Context

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[ ] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Documentation needed

[ ] Issue filed:

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary.

Closing this PR in favor of #1113


What should I do to handle this RGBA issue?

error: proc macro panicked
 --> src/main.rs:6:10
  |
6 |     .run(tauri::generate_context!())
  |          ^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = help: message: icon /home/runner/work/paint-board/paint-board/src-tauri/icons/icon.png is not RGBA

error: could not compile `app` (bin "app") due to previous error
       Error failed to build app: failed to build app
Error: Command failed with exit code 1: pnpm tauri build

Well, rgba is a hard requirement for the icon so either try to export it differently from whatever program you used to create it, or try the tauri icon command which should forcefully add transparency.
p.s. this issue is actually unrelated to this repo, tauri-action simply invokes tauri's cli & build command so this comes from tauri directly.


2 years old 👦

Our baby is turning 2 years old. 🥺

happy birthday 🎉🎉🎉

Thank you @Lincerossa 🙏 ❤


[ITEM] - Egg

Item name:
Egg
Current method of obtaining:
Collected from chickens
Link to wiki:
https://minecraft.gamepedia.com/Egg

Used in cake and pumpkin pie - need some other kind of binder. Honey? Slime?? Clay?!?!

This is suggested for cake, and...

this shapelessly for pumpkin pie.


[FLINK-13708] [table-planner-blink] transformations should be cleared after execution in blink planner

What is the purpose of the change
transformations should be cleared after execution in blink planner, cherry pick https://github.com/apache/flink/pull/9433 to release-1.9
Brief change log

clear transformations in ExecutorBase

Verifying this change
This change added tests and can be verified as follows:

Added testExecuteTwiceUsingSameTableEnv to verify this bug

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@flinkbot run travis


[WIP] RF classifier -- first steps

I started looking at how an RF classifier may perform on the different kinds of data. As we discussed I used a temporal split to avoid correlation issues as good as possible.
Preliminary classification results for the charge data look like

and for the distance data like

Not horrible but far from sufficiently good I'd say. Not sure if this is a matter of hyperparameter optimization (I tried a few settings by hand) or a more fundamental flaw.

Very interesting to see the charge data is out performing the geometric data.


[MBL-801] Update survey response viewmodel to RX2

📲 What
Updating the survey response viewmodel to Rx2
🤔 Why
Need to update these last few classes
🛠 How
🧠
👀 See
📋 QA
Make sure surveys still work as expected
Story 📖
MBL-801

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 70.00000% with 6 lines in your changes missing coverage. Please review.

Project coverage is 67.50%. Comparing base (435976f) to head (2ca2e18).

Files
Patch %
Lines

.../kickstarter/viewmodels/SurveyResponseViewModel.kt
70.00%
5 Missing and 1 partial :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##             master    #2082      +/-   ##
============================================
- Coverage     67.51%   67.50%   -0.02%
  Complexity     2126     2126
============================================
  Files           363      363
  Lines         22097    22103       +6
  Branches       3106     3106
============================================
+ Hits          14919    14920       +1
- Misses         5535     5540       +5
  Partials       1643     1643

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fix capitalization of "Id" in field selector

Field editor: packages/react/src/SearchFieldEditor/SearchFieldEditor.tsx
buildFieldNameString: packages/react/src/SearchControl/SearchUtils.tsx
It's calling buildFieldNameString, which includes a special case for id/ID, not sure why this isn't working.

Looks like the buildFieldNameString is checking for id but not Id as well.

I would like to take on this issue if it hasn’t already been solved.


Solution Planning - Mapping

7/29/21 - Per LADOH, Precision will continue to work with them directly, as we are not ready to assist with reportables other than COVID at this present time.
Marking all additional tickets as "CLOSED."


Allowing arbitrary constraints to be added.

@KarishmaDaga : You able to have a look at this one? Note that there's a pending invite for you to get admin access here (can't add you as an official reviewer until you confirm that ;) )

hey! oh sorry, i was knocked out after the second vaccine last week so I definitely missed that invite :')
yes I'll look at this latest tomorrow!

the second vaccine last week

Awesome news!
Thanks for having a gander, and glad to have you back!

@KarishmaDaga Comme ça?


Database BR

Hello guys, I am working in a logistics company in Brazil.
we are using Pelias to do the geolocation of addresses in Brazil, among the data sources we use openaddress.
internally we have several address data that are not in your database.
there are about 1M of addresses.
my data are in a table in dynamoBD, I can generate a csv as in the example if it is useful.
"latitude (S)","longitude (S)","city (S)","country (S)","neighborhood (S)","postal_code (S)","state (S)","street (S)","street_number (S)","address (S)"
"-20.0288417","-48.9297093","Frutal","Brazil","Centro","38200-000","Minas Gerais","Rua Dom Bôsco","450",
"-22.73891","-45.59074","Campos do Jordão","Brasil","Campos do Jordão","12460-000","São Paulo","Rua Miguel Pereira","69",
"-22.73891","-45.59281","Campos do Jordão","Brasil","Campos do Jordão","12460-000","São Paulo","Avenida Frei Oreste Girardi","1025",
"-22.93478","-43.33513","Rio de Janeiro","Brasil","Freguesia (Jacarepaguá)","22745-271","Rio de Janeiro","Rua Araguaia","1266",
"-22.93663","-45.46028","Pindamonhangaba","Brasil","Centro","12410-740","São Paulo","Rua Godofredo Pestana","158",
"-22.95696","-43.33464","Rio de Janeiro","Brasil","Anil","22753-530","Rio de Janeiro","Rua Barra do Mendes","20",
"-22.96247","-45.54753","Tremembé","Brasil","Tremembé","12120-000","São Paulo","Rua 7 de Setembro","335",
"-22.96247","-45.54773","Tremembé","Brasil","Tremembé","12120-000","São Paulo","Rua Rodrigues Alves","229",

Hi @erdmanncross. Thanks for the offer. We would really prefer to use primary/government sources for data. If you can find a new dataset for us to download that has these missing addresses, that'd be really helpful.


uv add jax  ,    all  jax code indent are     in  disorder

indent error

win 11
uv latest version

just   uv   add  jax , you can try   out to do

uv  pip install jax    as  well

JAX uses 2 space intending:

https://github.com/jax-ml/jax/blob/jaxlib-v0.4.32/jax/_src/tree_util.py#L332
https://github.com/jax-ml/jax/blob/jaxlib-v0.4.32/pyproject.toml#L112

The fact that your IDE is warning about that (probably because there is a user setting to 4 spaces) is unrelated to the traceback you are getting. If you care about the IDE warning you should seek out support for that IDE.
If you think the exception you are getting is related to uv, you need to provide steps on how you got to that exception for someone to be able to help you.


Change terminology from 'asynchronous' to something else

I think it might be confusing to say 'asynchronous', since that usually implies some promise or timeout - outside the current call stack.
I've talked with many developers who think the state updates won't happen during this event loop because state updates are asynchronous.
In fact, that's what I thought until I started experimenting with it and reading the source code.
I suggested a few options, don't know if any of them make sense to you more.
Thanks

You're correct that today the state updates can be synchronously flushed in the same event loop, but that's not always the case. For example, you can debug clicking the button in this sandbox that runs concurrent mode the latest experimental build to see state updates happening asynchronously.
It's best to think of setState as running asynchronously, even if the implementation details of a particular update run in the same event loop.

Yes, I realize that it might be either. Just saying it was confusing when the docs say asynchronous, and I run a sandbox without concurrent and see that it's synchronous.

It is asynchronous with respect to the setState call, but can be synchronous within event loop. React has used this language for awhile, and in the future it will also be asynchronous within the event loop so I don't think it makes sense to churn the language now.

Thanks for the detailed explanation :)


wrong floating position in Android (Chrome or native)

When I pick an input box, most times datepicker appear far away, almost outside the window in android native browser and android chrome browser.
Desktop works flawless.
btw: Excelent datepicker, congrats !

I suggest you to use other datepicker in mobile browser.


Item frames cannot be broken by punching

When placing item frames on a block unreinforced or reinforced, they cannot be broken by punching. The same applies when trying to remove an item from an item frame. They can however be broken by smothering with a block or breaking the block they're on

Does it say any message when trying to break it?

Does it say any message when trying to break it?

No, nothing

https://i.imgur.com/U0QRZq8.gif

https://i.imgur.com/ViDyDvN.mp4
Using version 5.0.0-SNAPSHOT if that matters

Can confirm I have consistently had this issue and many other reporting as well, still a problem

This issue is in Finale
Was reproduced and fixed


Can't use material  with more than 2 layers

Implemented here https://github.com/GPUOpen-LibrariesAndSDKs/FireRays_SDK/commit/8691e3bacd35e6719e284bcb0397bc01ab3bcc92


Introduce combined modules

This PR introduces combined modules (and interfaces) for AXI4, AXI4-Lite and AXI3.
With this you no longer need to instantiate two separate modules for RD and WR.
This change is entirely optional and does not break existing usages.
Besides this, the PR also gets rid of the compiler warnings produced by the dummy modules.

Replaced the GetS interfaces in the combined modules with the more common Get.
This makes the "normal" usage more in-line with the existing, split modules. But it does not allow snooping of values (for the combined modules).
If snooping is something which we want, we need to to figure out a good way to do this without impacting the "normal" usage. (Also until now snooping was implemented only in some of the split modules)


Save all logs when the -o option using with like ?

from https://github.com/hahwul/dalfox/issues/248#issuecomment-877618737

flag name

[ ] --oA
[x] --output-all

Test
$ ./dalfox url https://xss-game.appspot.com/level1/frame\?d\=fd --output-all -o out

$ cat out
[*] Using single target mode
[*] Start Scan 🦊
[*] 🦊 Start scan [SID:Single] / URL: https://xss-game.appspot.com/level1/frame?d=fd
[*] Valid target [ code:200 / size:508 ]
[*] [SA: ✓ PA: ✓ BAV: ✓ ] Waiting for analysis 🔍
[I] Found 2 testing point in DOM base parameter mining
[*] [SA: ✓ PA: ✓ BAV: ✓ ] Waiting for analysis 🔍
[*] [SA: ✓ PA: ✓ BAV: ✓ ] Waiting for analysis 🔍
[I] Found 1 testing point in Dictionary base paramter mining
[*] [SA: ✓ PA: ✓ BAV: ✓ ] Waiting for analysis 🔍
[I] Content-Type is text/html; charset=utf-8
[I] Reflected query param => Injected: /inHTML-none(1)  ,  :  ]  }  -  `  \  {  '  |  <  >  =  ;  $  [  .  )  "  (  +
    13 line:  Sorry, no results were found for DalFox. Try again
[*] Generate XSS payload and optimization.Optimization.. 🛠
[*] Start XSS Scanning.. with 297 queries 🗡
[*] [ Make 100 workers ] [ Allocated 297 queries ]
[W] Reflected Payload in HTML: query=<audio controls ondurationchange=alert(1)><source src=1.mp3 type=audio/mpeg></audio>
    13 line:  s were found for <audio controls ondurationchange=alert(1)><source src=1.mp3
[POC] [R][GET] https://xss-game.appspot.com/level1/frame?d=fd&query=%3Caudio+controls+ondurationchange%3Dalert%281%29%3E%3Csource+src%3D1.mp3+type%3Daudio%2Fmpeg%3E%3C%2Faudio%3E
[V] Triggered XSS Payload (found DOM Object): query='"><iframe srcdoc="<input onauxclick=alert(1)>" class=dalfox>
    13 line:  s were found for '"><iframe srcdoc="<input onauxclick=alert(1)>" class=dalfox
[POC] [V][GET] https://xss-game.appspot.com/level1/frame?d=fd&query=%27%22%3E%3Ciframe+srcdoc%3D%22%3Cinput+onauxclick%3Dalert%281%29%3E%22+class%3Ddalfox%3E%3C%2Fiframe%3E


Add "Install multiple JDKs" README section

Description:
The PR it to clarify how to use multiple JDKs during build
Related issue:
link to the related issue.

Hi,
setup-java already set some of environment like: JAVA_HOME_11_X64 maybe simple should set JAVA_HOME_11 also ...

JAVA_HOME_11_X64

As I learned is not from the setup action (@v3) but from the container itself.

Hi, setup-java already set some of environment like: JAVA_HOME_11_X64 maybe simple should set JAVA_HOME_11 also ...

I would leave the naming on the pipeline owner will and prefer to avoid any "standard" names because the can clash with same predefined variables. It is kind of naive namespacing.


[C++] Arrow build failed with error C2039

Describe the bug, including details regarding any error messages, version, and platform.
Hello, I'm a member of Microsoft VCPKG, when I built arrow:x64-windows in an internal version of Visual Studio, it failed with following errors:
arrow/json/object_writer.h(39): error C2039: 'string': is not a member of 'std'
This issue caused by the STL PR: microsoft/STL#4633, and according to the recommendations of the STL developers, the affected files need to include the Standard <string> header.
I have applied this change in vcpkg by https://github.com/microsoft/vcpkg/pull/39160. Since this VS internal version has not been released yet, I am submitting this issue just to inform you.
Component(s)
C++

Thanks @Cheney-W for the report!

It seems object_writer.h was already patched here:

https://github.com/apache/arrow/pull/42004

Closing as already done but thanks for reporting.


[cleanup] Remove AndroidX warning

Remove AndroidX warnings since now the tool provides warnings.

@blasten @mklim Should we be doing this in the flutterfire repo too?

@bparrishMines 👍


Humbly requesting a release...

Hi folks,
I'd love to get the new Add map valued (string->string, string->int) flags (see below for the diff) without having to point to the master branch. This is so useful, any chance we could see a release soonish?
https://github.com/spf13/pflag/compare/v1.0.2...master

Merry Christmas.

🎉‼🙏


#4374: Benchmarking for bloom TT model

This PR contains benchmarking for Bloom TT model:-
BLoom Causal LM is benchmarked with hellaswag dataset.
Bloom question answering is benchmarked with squadv2 dataset.

Here is the passing CI Links
[post-commit] Run all post-commit workflows Link


getting the following error when i try to create an invoice

var invoice = bitpay.CreateInvoice(new Invoice()
			{
				Price = 1.0m,
				Currency = "USD",
				PosData = Guid.NewGuid().ToString(),
				OrderId = Guid.NewGuid().ToString(),
				ItemDesc = "My awesome 2-Beds Room"
			});

Newtonsoft.Json.JsonSerializationException: Cannot deserialize the current JSON object (e.g. {"name":"value"}) into type 'System.Int64' because the type requires a JSON primitive value (e.g. string, number, boolean, null) to deserialize correctly.
To fix this error either change the JSON to a JSON primitive value (e.g. string, number, boolean, null) or change the deserialized type so that it is a normal .NET type (e.g. not a primitive type like integer, not a collection type like an array or List<T>) that can be deserialized from a JSON object. JsonObjectAttribute can also be added to the type to force it to deserialize from a JSON object.
Path 'minerFees.BTC', line 42, position 10.

any ideas?
looks like the minerFeets.BTC is deserialised incorrectly

ok /invoices api delivers a minerFees object instead of a long now
  "minerFees": {
    "BTC": {
      "satoshisPerByte": 1.99,
      "totalFee": 300
    },
    "BCH": {
      "satoshisPerByte": 15.192,
      "totalFee": 2200
    }
  }

Pushed new version with a proper type <IP_ADDRESS>


I do not see label event in list

The event label is not shown on list, I have  just "Category / Action". Is it a feature or bug ?
:)

The event label (and value) don't show in the beacon list but they are visible in the beacon inspector under the "Event Data" heading. Originally this was by design but I've already added the label and value ready for the next release.

Ok, thanks!


At the very least, should it be more stable according to the official tutorial?

i simply follow the step by this https://plugins.jetbrains.com/docs/intellij/gradle-prerequisites.html ,but it
cant work ,error are

A problem occurred configuring root project 'idea-plugin-v1'.
Could not resolve all artifacts for configuration ':classpath'.
Could not resolve org.jetbrains.intellij.plugins:gradle-intellij-plugin:1.1.4.
Required by:
project : > org.jetbrains.intellij:org.jetbrains.intellij.gradle.plugin:1.1.4
No matching variant of org.jetbrains.intellij.plugins:gradle-intellij-plugin:1.1.4 was found. The consumer was configured to find a runtime of a library compatible with Java 8, packaged as a jar, and its dependencies declared externally but:
- Variant 'apiElements' capability org.jetbrains.intellij.plugins:gradle-intellij-plugin:1.1.4 declares a library, packaged as a jar, and its dependencies declared externally:
- Incompatible because this component declares an API of a component compatible with Java 11 and the consumer needed a runtime of a component compatible with Java 8
- Variant 'runtimeElements' capability org.jetbrains.intellij.plugins:gradle-intellij-plugin:1.1.4 declares a runtime of a library, packaged as a jar, and its dependencies declared externally:
- Incompatible because this component declares a component compatible with Java 11 and the consumer needed a component compatible with Java 8

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

my idea is 2021.1.2  and my gradle file is :
plugins {
id 'java'
id 'org.jetbrains.intellij' version '1.1.4'
}
group 'org.alibaba.dc.delivery.support'
version '1.0-SNAPSHOT'
//sourceCompatibility = 1.8
repositories {
mavenCentral()
}
dependencies {
testImplementation 'org.junit.jupiter:junit-jupiter-api:5.7.0'
testRuntimeOnly 'org.junit.jupiter:junit-jupiter-engine:5.7.0'
}
// See https://github.com/JetBrains/gradle-intellij-plugin/
intellij {
version '2021.1.2'
}
patchPluginXml {
changeNotes """
Add change notes here.
most HTML tags may be used"""
}
test {
useJUnitPlatform()
}

I had the same problem when building my library with jitpack: https://jitpack.io/com/github/vivid-money/elmslie/coroutines-support-34f5ff5bd6-1/build.log
I managed to fix it by instructuing jitpack to build with jdk 11. It seems to me that this issue is not releated to the plugin.

I am also encountering this issue. Lowering the version to 1.1.2 has no problem at all. The plugin builds fine for me using gradlew buildPlugin, but gradlew verifyPlugin crashes with this error

For future Googlers. The solution is this.

Make sure your gradle JVM is set to "jbr-11" in IntelliJ, AND make sure you have JDK 11 installed on your computer and the env vars pointing to it.. It may not have been clear enough in some documentations to do this, or for current devs that just updated to new versions (since it was changed abruptly and everything worked before)
Beginning from 1.1.3 this plugin requires JDK 11 on the command line.

Indeed, Java 11 is now required. README has been updated accordingly.


can't remove an icon on a MAP that has special character on the name of the label

On the editor of weathermap (console-.>weathermap-> edition of a map
I have a NODE that is juste a label, and I neet to specify ICON NONE
NODE DC_Praz-SÃ©chaud         LABEL DC_Praz-SÃ©chaud         POSITION 1740 75
I got this error when I try to do it:
30/01/2023 14:20:56 - CMDPHP PHP ERROR NOTICE Backtrace: (/plugins/weathermap/weathermap-cacti-plugin-editor.php[173]:setNodeProperties(), /plugins/weathermap/lib/editor.actions.php[314]:WeatherMap->WriteConfig(), /plugins/weathermap/lib/WeatherMap.class.php[3381]:CactiErrorHandler()) 30/01/2023 14:20:56 - ERROR PHP NOTICE in Plugin 'weathermap': Undefined property: stdClass::$defined_in in file: /usr/share/cacti/plugins/weathermap/lib/WeatherMap.class.php on line: 3381 30/01/2023 14:20:56 - CMDPHP PHP ERROR NOTICE Backtrace: (/plugins/weathermap/weathermap-cacti-plugin-editor.php[173]:setNodeProperties(), /plugins/weathermap/lib/editor.actions.php[314]:WeatherMap->WriteConfig(), /plugins/weathermap/lib/WeatherMap.class.php[3380]:CactiErrorHandler()) 30/01/2023 14:20:56 - ERROR PHP NOTICE in Plugin 'weathermap': Undefined property: stdClass::$name in file: /usr/share/cacti/plugins/weathermap/lib/WeatherMap.class.php on line: 3380 30/01/2023 14:20:56 - CMDPHP PHP ERROR NOTICE Backtrace: (/plugins/weathermap/weathermap-cacti-plugin-editor.php[173]:setNodeProperties(), /plugins/weathermap/lib/editor.actions.php[314]:WeatherMap->WriteConfig(), /plugins/weathermap/lib/WeatherMap.class.php[3381]:CactiErrorHandler()) 30/01/2023 14:20:56 - ERROR PHP NOTICE in Plugin 'weathermap': Undefined property: stdClass::$defined_in in file: /usr/share/cacti/plugins/weathermap/lib/WeatherMap.class.php on line: 3381 30/01/2023 14:20:56 - CMDPHP PHP ERROR NOTICE Backtrace: (/plugins/weathermap/weathermap-cacti-plugin-editor.php[173]:setNodeProperties(), /plugins/weathermap/lib/editor.actions.php[314]:WeatherMap->WriteConfig(), /plugins/weathermap/lib/WeatherMap.class.php[3380]:CactiErrorHandler()) 30/01/2023 14:20:56 - ERROR PHP NOTICE in Plugin 'weathermap': Undefined property: stdClass::$name in file: /usr/share/cacti/plugins/weathermap/lib/WeatherMap.class.php on line: 3380 30/01/2023 14:20:56 - CMDPHP PHP ERROR WARNING Backtrace: (/plugins/weathermap/weathermap-cacti-plugin-editor.php[173]:setNodeProperties(), /plugins/weathermap/lib/editor.actions.php[294]:CactiErrorHandler()) 30/01/2023 14:20:56 - ERROR PHP WARNING in Plugin 'weathermap': Creating default object from empty value in file: /usr/share/cacti/plugins/weathermap/lib/editor.actions.php on line: 294
I suspect the error is related to the name of the NODE (the LABEL is the same)
NODE DC_Praz-SÃ©chaud
And on the edit it shown as
DC_Praz-S�chaud
But the icone is shown as:
DC_Praz-Séchaud
It's the only one who give me this error, that's why I'm thinking about the name of the LABEL..
By the way changin tht line 169 of ../lib/editor.inc.php
From return str_replace($drop_char_match, $drop_char_replace, urldecode($str));
To return str_replace($drop_char_match, $drop_char_replace, html_escape($str))
Didn't solve the issue

Okay, cool.  There is over-escaping going on.  Just have to find it.

This is interesting, cause I can use those characters on my version after switching the html_escape().  Also though there is an odd behavior.  If I have a link that is connecting to the node, and I rename the node, the link get's lost.  Is that legacy behavior too?

Yes it's correct, happen also on 0.98a
Because when you do an 'edit' (that let you change the configuration directly on the file), instead of changing the value on the GUI, it's not propagated on every line where your node is used.
When you look at the LINK there is NODES (plural) line that define both end, and that's where the new name is not propagated.

I am not able to reproduce this.  I've created a WeatherMap file and added and deleted a node.  What I'm suspecting is that your need to change your OS' default language to an international charset so that the config files are not ASCII but UTF8.
One your Servers console, run the locale command, all the locales should have a UTF-8 suffix.  See the below.
LANG=en_US.UTF-8
LANGUAGE=en_US:en
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=


Allow time.Time types to be converted to string labels

Some bigquery tables use timestamps as part of their schema and right now should one try to export the data, the resulting data points in prometheus have "invalid string" instead of string converted versions of the timestamps. This change would allow users to convert timestamps to strings and keep the labels as is.

This change is

Hi Peter! Firstly, thanks for this awesome tool - saved me a lot of time :)
I'm wondering what you think of this change - I would like my points in prometheus to show actual timestamps rather than "invalid string", but this may set a bad precedent for checking individually against each potential data type there may be.

Hi Stephen,
I thin your suggestion is a much better idea than my changes. I had a gut feeling this wasn't the right way to go, so I'm glad you pointed it out! Thanks! I agree with you that keeping the function pure for just string types is better, and that is native to how Prometheus expects its labels anyway.
Closing.


Integration/compass 1.0.0

Description Of Changes
Integration branch containing all work dependent upon Compass 1.0.0 migration
Code Changes

[x] update System and PrivacyDeclaration models to incorporate new TCF-based fields, surface them in TCF overlay as needed: https://github.com/ethyca/fides/pull/4228

[ ] ❓ TCF overlay UI support to leverage these new TCF-based fields ❓ -- not covered in this PR, split out into https://github.com/ethyca/fides/issues/4255 as a followup

[x] update TCF preference backend API to handle universal vendor ID (GVL vendor IDs supported, AC vendor ID still not yet supported): https://github.com/ethyca/fides/pull/4256
[x] update system/vendor suggestion UX to incorporate new Compass schema: https://github.com/ethyca/fides/pull/4254
[x] support new TCF fields in admin UI: https://github.com/ethyca/fides/pull/4271

Steps to Confirm

[x] collectively we covered the testing broadly described here: https://ethyca.atlassian.net/wiki/spaces/EN/pages/2808283140/Integration+branch+for+2.22.0+release#Testing-with-the-integrated-environment

Pre-Merge Checklist

[ ] All CI Pipelines Succeeded
Documentation:

[ ] documentation complete, PR opened in fidesdocs
[ ] documentation issue created in fidesdocs

[ ] Issue Requirements are Met
[x] Relevant Follow-Up Issues Created
[x] Update CHANGELOG.md
[ ] For API changes, the Postman collection has been updated

i think we're ready to merge this into main and then release-2.22.0!
to keep a clean paper trail -- i added two additional commits here since last manual testing/review:

updated to the latest GVL.json (still hardcoding this on the BE for now): https://github.com/ethyca/fides/pull/4261/commits/9bf6a3c7ff4b2a280826d44e76c71a3f76d4a2bd
bumped to fideslang==2.2.0 since that was officially released/published: https://github.com/ethyca/fides/pull/4261/commits/f9410aff218264df11bcbc1eb53d3e839a041a16


Update README.md to specify this is mac only

While technically it's only bundled for macOS at the moment, it should be somewhat trivial to make bundles for Windows and Linux too.
I'd rather do that than keep the app macOS only.
Thanks for the PR anyway.

@finp as of v2.0.0 Noty is cross-platform.


current dontStrip = true default causes some python packages to hold on to GCC as a runtime dependency

Just opening this to document trouble I had in case it helps someone save a few days of flailing--I don't have enough perspective on what kinds of problems were caused by stripping to understand which default is ideal.
Hodgepodge of observations in case they make this more searchable:

In the process of switching a project over from mach-nix to dream2nix, I noticed that a container containing the environment generated with dockerTools.buildLayeredImage was nearly twice as large as the old mach-nix-based container.
I added the environment to the new container by including packages.blah.pyEnv in its contents.
Unpacking the container filesystem and fishing around led me to identify the most-conspicuous difference as the presence of GCC.
Using nix-tree on it (I needed something like nix build .#blah && nix run github:nixos/nixpkgs#nix-tree -- --dot .#blah helped identify 5 packages as depending on GCC: libsass, misaka, psycopg2 rjsmin, sqlalchemy.
After a good bit of flailing about with override mechanisms, I eventually tracked this down by expanding my search beyond dream2nix stuff and finding a discourse thread where the same basic problem (unexpected runtime dependency on GCC) was identified as a side-effect of stripping being disabled. #673 disabled stripping by default here.
I ended up getting what I need with pip.overrideAll.mkDerivation.dontStrip = false;, but overriding this on the individual problem-packages also worked just fine if you need to be more precise (i.e., pip.overrides.misaka.mkDerivation.dontStrip = false;).

Since I extracted a minimal reproducible example in the process of figuring this out, I'll include links in case they help (ignore the repo name, I added it on top of a repro for a different problem I had):

adding a package that holds on to GCC via https://github.com/abathur/flake_dream2nix_patchelf/commit/d5a0b66793d697342046f39bd9054b321e60765b with demonstration in CI at https://github.com/abathur/flake_dream2nix_patchelf/actions/runs/9470568588/job/26091792723#step:8:17

adding fix via https://github.com/abathur/flake_dream2nix_patchelf/commit/a9ed2275a9cc47e3610318860573cef6382a882d with demonstration in CI at https://github.com/abathur/flake_dream2nix_patchelf/actions/runs/9470810183/job/26092560974#step:8:16

It's a tangent, but one bit of this does still puzzle me if anyone knows what's missing from my mental model.
When I do something like nix run github:nixos/nixpkgs#nix-tree -- --dot .#blah | grep misaka I'll see:
...
  "python3.9-misaka-2.1.1" -> "gcc-13.2.0" [];
  "python3.9-misaka-2.1.1" -> "glibc-2.39-31" [];
  "python3.9-misaka-2.1.1" -> "python3.9-cffi-1.16.0" [];
  "python3.9-misaka-2.1.1" -> "bash-5.2p26" [];
  "python3.9-misaka-2.1.1" -> "python3.9-cffi-1.16.0" [];
  "python3.9-misaka-2.1.1" -> "python3.9-pycparser-2.22" [];
  "python3.9-misaka-2.1.1" -> "glibc-2.39-31-dev" [];
  "python3.9-misaka-2.1.1" -> "python3-3.9.19" [];
...

But then if I just do, say, nix run github:nixos/nixpkgs#nix-tree -- --dot .#prod.pyEnv.pkgs.misaka | grep misaka l only see:
  "python3.9-misaka-2.1.1" -> "glibc-2.39-31" [];
  "python3.9-misaka-2.1.1" -> "python3.9-cffi-1.16.0" [];
  "python3.9-misaka-2.1.1" -> "bash-5.2p26" [];
  "python3.9-misaka-2.1.1" -> "python3.9-pycparser-2.22" [];
  "python3.9-misaka-2.1.1" -> "python3-3.9.19" [];

Anyone know why the latter doesn't indicate the same dependency on GCC as the former?


Config Document Suggestions

Some documentation observations:

AWS lambdas were created with 128 MB RAM setting by default. However the general documentation indicates the default is 512 MB. https://nitric.io/docs/deployment
need to add vpc content to the AWS https://nitric.io/docs/reference/providers/aws/configuration

config:
  default:
    lambda:
      # only functions that require DB access should be in this VPC
      vpc:
        security-group-ids:
          - sg-xxxx
        subnet-ids:
          - subnet-xxx
          - subnet-xxx

This should be avaialable in out latest config reference now


Add connectable property to BLE Scan result

Is your feature request related to a problem?
Asking for near by BLE devices don't tell me if they are connectable or not:
AT+BLEINIT=1
AT+BLESCANPARAM=1,0,0,1480,1480
AT+BLESCAN=1,3

  +BLESCAN:"2a:47:c4:d5:63:e0",-78,1eff060001092022c46a7a8bda0a542bd5141db069a0ad42393763cf091bae,,1
  +BLESCAN:"34:64:f4:2b:4b:97",-63,13ff0600010f210a1acca4f60ae0534330303934,,1
  +BLESCAN:"52:83:e4:05:8f:d9",-98,0303f3fe,,1

based on discussion in comments here:
https://stackoverflow.com/questions/28467590/detecting-whether-a-ble-device-is-connectable-on-android
"connectable" status doesn't come from Advertisement Flags but from environment (ESP AT).
Describe the solution you'd like.
is connectable
+BLESCAN:"52:83:e4:05:9f:d9",-98,0303f3fe,,1,yes
+BLESCAN:"52:83:e4:05:9f:d9",-98,0303f3fe,,1,no
or in number
Describe alternatives you've considered.
only other way to test is trying to connect but that's VERY slow.
Additional context.
version
AT+GMR
AT+GMR
AT version:<IP_ADDRESS>(s-ec2dec2 - ESP32 - Jul 28 2023 07:05:28)
SDK version:v5.0.2-376-g24b9d38a24-dirty
compile time(6118fc22):Jul 28 2023 10:14:50
Bin version:v<IP_ADDRESS>(PICO-D4)

@mrx23dot , thank you for your good idea. We will consider adding it to our future feature development plans.


Can you submit other ABI than arm64-v8a please? armeabi-v7a, x86, x86_64

Hi Gaurav, thank you for sharing your great value project!
I'am a Java developer, don't know how to compile C++ to obtain all libandroid_dlib.so files.
Can you please submit other ABI than arm64-v8a? I mean armeabi-v7a, x86, x86_64
Thank you

Hi Vitiello,
sorry for the late reply
I have updated the code to work with other ABIs

Many thanks Gaurav you were really very kind!
Greetings,
Antonio.


should we be building the plotting object iteratively instead of all at once?

curious of views and other things should be built as you add to the gsplot object, or if they should be done all at once as part of print.
breaking it up would help us w/ development debugging. Not sure how I feel on the topic, but since we are talking about modifying the render object structure I thought I would bring this up.

also, one advantage of this is that if we have conflicting things specified in the views, the graceful failover is just to use the most recent setting. So if you had
gs <- gsplot() %>%
  points(1:2,1:2,xlab='dog') %>%
  lines(3:4, 5:6, xlab='cat')
gs

the xlab would be cat. More advantageous for more complicated examples, but you get the point.

Interesting...might be helpful to people using it debugging too.

I was thinking about this as well, and I think it is reasonable as long as there isn't too much to deal with as far as maintaining the integrity of the object.  I've been writing this comment for a while and trying to come up with drawbacks, but can't come up with anything specific.  If you want to discuss, I probably have some strong opinions one way or another.

are we doing this?

It's my vote.

I think I'm convinced.

I am trying this

:+1:

WIP here: https://github.com/jread-usgs/gsplot/tree/iterative-builder
but I broke legend and I think I broke logged axes when using multiple calls to the same side

that PR is ready for review


RFE: allow unsafe MappedFileVol.ensureAvailable

I suggest to allow disable calling of raf.getFD().sync(); in MappedFileVol.ensureAvailable without MapDB recompilation.
'sync' will ENABLED by default.
My test case (on SSD):
sync ENABLED: 3min 50s
sync DISABLED: 2min 40s

I will run a few tests. I think sync is no longer necessary on JVM 8. Filling space prevents crash if there is not enough free space

Moving to 3.0


fix some typo in Selection.md

selection.clear() does not need any parameters
move iterate method code & add map reduce method doc

Oh waow, I must have been tired when writing this haha. Thanks!


Patch Tuya wifi switch without beken module

Hey,
can I patch WIFI Switch Module (model: QS-WIFI-SO5) by Tuya-CloudCutter?
My Wifi switch module has insite ESP module (not Beken module).
Specs:
https://templates.blakadder.com/QS-WIFI-S05.html

No, ESP is not currently support.  While technically vulnerable to the same exploit, a working exploit path is not currently know (and may or may not even be possible)

Can I check?

No, CloudCutter doesn't support a path for ESP, there are no profiles that would work with it, and no support for flashing that type of firmware.  Unless you know assembly well, there isn't anything you can do.
You can try Tuya-Convert or serial flashing.

Tuya-convert is old repository and not works in my device :( I'm afraid to solder, I'm developer 🙂
I want to try flashing by your cutter.

Again, unless you know assembly and building stack redirection, there is no other starting point.  As ESP is Xtensa and not ARM Thumb, we're not even sure if the stack redirection is even possible, we don't have anyone knowledgeable on that subject.
As-Is, CloudCutter is not designed to work with ESP.


Further fixes to getting the right objectTemplate in object prototype…

… injections

Looks fine to me.

I'm fine with the changes.


Feature: Include Code Completion reading from INC files

See if I can implement the VSCode Code Completion capabilities to provide the ability to give code suggestions when certain keywords are typed, from the standard INC files. Consider user created INC files in a later feature addition if this works.

Initial code completion working with basic library INC files!