Loosen race on TestCrdsRetryAsynchronouslyStoreClose

Hack around https://github.com/istio/istio/issues/17147 to unblock PRs

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

Test name
Commit
Details
Rerun command

gencheck_istio
a1e55e205098954e0af29921df9a98a4d8c4b691
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 them all:

Test name
Commit
Details
Rerun command

gencheck_istio
a1e55e205098954e0af29921df9a98a4d8c4b691
link
/test gencheck_istio

e2e-simpleTestsMinProfile_istio
a1e55e205098954e0af29921df9a98a4d8c4b691
link
/test e2e-simpleTestsMinProfile_istio

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

/retest

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

Test name
Commit
Details
Rerun command

integ-istioctl-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-istioctl-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 them all:

Test name
Commit
Details
Rerun command

integ-istioctl-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-istioctl-k8s-tests_istio

integ-galley-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-galley-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 them all:

Test name
Commit
Details
Rerun command

integ-istioctl-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-istioctl-k8s-tests_istio

integ-galley-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
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 them all:

Test name
Commit
Details
Rerun command

integ-istioctl-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-istioctl-k8s-tests_istio

integ-galley-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-framework-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 them all:

Test name
Commit
Details
Rerun command

integ-istioctl-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-istioctl-k8s-tests_istio

integ-galley-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-framework-k8s-tests_istio

e2e-simpleTests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions 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 them all:

Test name
Commit
Details
Rerun command

integ-istioctl-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-istioctl-k8s-tests_istio

integ-galley-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-framework-k8s-tests_istio

e2e-simpleTests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests_istio

e2e-dashboard_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-dashboard_istio

e2e-simpleTestsMinProfile_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTestsMinProfile_istio

Instructions for interacting with me using PR comments are available here.  If you have questions 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 them all:

Test name
Commit
Details
Rerun command

integ-istioctl-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-istioctl-k8s-tests_istio

integ-galley-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-framework-k8s-tests_istio

e2e-simpleTests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests_istio

e2e-dashboard_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-dashboard_istio

e2e-simpleTestsMinProfile_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTestsMinProfile_istio

e2e-simpleTests-distroless_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests-distroless_istio

Instructions for interacting with me using PR comments are available here.  If you have questions 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 them all:

Test name
Commit
Details
Rerun command

integ-istioctl-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-istioctl-k8s-tests_istio

integ-galley-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-framework-k8s-tests_istio

e2e-simpleTests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests_istio

e2e-dashboard_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-dashboard_istio

e2e-simpleTestsMinProfile_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTestsMinProfile_istio

e2e-simpleTests-distroless_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests-distroless_istio

pilot-e2e-envoyv2-v1alpha3_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test pilot-e2e-envoyv2-v1alpha3_istio

Instructions for interacting with me using PR comments are available here.  If you have questions 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 them all:

Test name
Commit
Details
Rerun command

integ-istioctl-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-istioctl-k8s-tests_istio

integ-galley-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-framework-k8s-tests_istio

e2e-simpleTests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests_istio

e2e-dashboard_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-dashboard_istio

e2e-simpleTestsMinProfile_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTestsMinProfile_istio

e2e-simpleTests-distroless_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests-distroless_istio

pilot-e2e-envoyv2-v1alpha3_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-security-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
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 them all:

Test name
Commit
Details
Rerun command

integ-istioctl-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-istioctl-k8s-tests_istio

integ-galley-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-framework-k8s-tests_istio

e2e-simpleTests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests_istio

e2e-dashboard_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-dashboard_istio

e2e-simpleTestsMinProfile_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTestsMinProfile_istio

e2e-simpleTests-distroless_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests-distroless_istio

pilot-e2e-envoyv2-v1alpha3_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-security-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
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 them all:

Test name
Commit
Details
Rerun command

integ-istioctl-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-istioctl-k8s-tests_istio

integ-galley-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-framework-k8s-tests_istio

e2e-simpleTests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests_istio

e2e-dashboard_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-dashboard_istio

e2e-simpleTestsMinProfile_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTestsMinProfile_istio

e2e-simpleTests-distroless_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests-distroless_istio

pilot-e2e-envoyv2-v1alpha3_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-security-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-telemetry-k8s-tests_istio

e2e-mixer-no_auth_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-mixer-no_auth_istio

Instructions for interacting with me using PR comments are available here.  If you have questions 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 them all:

Test name
Commit
Details
Rerun command

integ-istioctl-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-istioctl-k8s-tests_istio

integ-galley-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-framework-k8s-tests_istio

e2e-simpleTests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests_istio

e2e-dashboard_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-dashboard_istio

e2e-simpleTestsMinProfile_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTestsMinProfile_istio

e2e-simpleTests-distroless_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests-distroless_istio

pilot-e2e-envoyv2-v1alpha3_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-security-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-telemetry-k8s-tests_istio

e2e-mixer-no_auth_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

Instructions for interacting with me using PR comments are available here.  If you have questions 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 them all:

Test name
Commit
Details
Rerun command

integ-istioctl-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-istioctl-k8s-tests_istio

integ-galley-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-framework-k8s-tests_istio

e2e-simpleTests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests_istio

e2e-dashboard_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-dashboard_istio

e2e-simpleTestsMinProfile_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTestsMinProfile_istio

e2e-simpleTests-distroless_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests-distroless_istio

pilot-e2e-envoyv2-v1alpha3_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-security-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-telemetry-k8s-tests_istio

e2e-mixer-no_auth_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-simpleTests-cni_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests-cni_istio

release-test_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
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 them all:

Test name
Commit
Details
Rerun command

integ-istioctl-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-istioctl-k8s-tests_istio

integ-galley-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-framework-k8s-tests_istio

e2e-simpleTests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests_istio

e2e-dashboard_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-dashboard_istio

e2e-simpleTestsMinProfile_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTestsMinProfile_istio

e2e-simpleTests-distroless_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests-distroless_istio

pilot-e2e-envoyv2-v1alpha3_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-security-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-telemetry-k8s-tests_istio

e2e-mixer-no_auth_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-simpleTests-cni_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests-cni_istio

release-test_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test release-test_istio

integ-security-local-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-security-local-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 them all:

Test name
Commit
Details
Rerun command

integ-istioctl-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-istioctl-k8s-tests_istio

integ-galley-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-framework-k8s-tests_istio

e2e-simpleTests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests_istio

e2e-dashboard_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-dashboard_istio

e2e-simpleTestsMinProfile_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTestsMinProfile_istio

e2e-simpleTests-distroless_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests-distroless_istio

pilot-e2e-envoyv2-v1alpha3_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-security-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-telemetry-k8s-tests_istio

e2e-mixer-no_auth_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-simpleTests-cni_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test e2e-simpleTests-cni_istio

release-test_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test release-test_istio

integ-security-local-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-security-local-tests_istio

integ-pilot-local-tests_istio
72bbad74606a756953ed8d41d3e84b35a289c7b0
link
/test integ-pilot-local-tests_istio

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

/retest


Build Fail_ Yosemite 10.10.

I am a  newbie to Ruby and ROR. I am trying to get my dev environment up but to no avail. I keep getting the following when trying to install 2.2.4:
BUILD FAILED (OS X 10.10.5 using ruby-build 20160330)

Inspect or clean up the working tree at /var/folders/nz/cwp6snk10_s6xgdxb5rly5mm0000gn/T/ruby-build.20160403003341.51083
Results logged to /var/folders/nz/cwp6snk10_s6xgdxb5rly5mm0000gn/T/ruby-build.20160403003341.51083.log

Last 10 log lines:
    from /private/var/folders/nz/cwp6snk10_s6xgdxb5rly5mm0000gn/T/ruby-build.20160403003341.51083/ruby-2.2.4/lib/rubygems/dependency_installer.rb:373:in `install'
    from /private/var/folders/nz/cwp6snk10_s6xgdxb5rly5mm0000gn/T/ruby-build.20160403003341.51083/ruby-2.2.4/lib/rubygems.rb:558:in `install'
    from ./tool/rbinstall.rb:722:in `block (2 levels) in <main>'
    from ./tool/rbinstall.rb:721:in `each'
    from ./tool/rbinstall.rb:721:in `block in <main>'
    from ./tool/rbinstall.rb:757:in `call'
    from ./tool/rbinstall.rb:757:in `block in <main>'
    from ./tool/rbinstall.rb:754:in `each'
    from ./tool/rbinstall.rb:754:in `<main>'
make: *** [do-install-all] Error 1

macOS 10.10 is EOL now.


Support fot building on Android

Hi, I am trying to build fastembed for Android through cross compilation
But I am getting error:
Error fail to run custom build comment for ort-sys v2. 0.0-rc.0

Just wanted to know if fastembed is supported for Android
Command used for cross compilation
cargo-ndk --target aarch64-linux-android --platform 21 -- build

I don't think ort supports building for Android.

Confirmed with the ort community, "Android is supported but needed to build onnxruntime from source " is what they said
Just wanted to confirm the support of fastembed for Android

If you can build FastEmbed for Android it should work then.


Mention that path field can be a URL as well

What issue type does this pull request address? (keep at least one, remove the others)
/kind documentation
Please provide a short message that should be published in the DevSpace release notes
Modification the documentation to mention that path field can be a URL as well

@alexissellier thanks for the PR! LGTM!


Update estravere version

The new 2 tests failed beacause this change - https://github.com/estools/estraverse/pull/72
is still not added by the owners of estraverse.


Collecting signatures from slashed nodes bug

I don't see anything in our code that would prevent us from collecting signatures from slashed validators: that means I can no longer assume that the Header.validators contains only enrolled and non-slashed validators.

Are you aware that there are queries in ValidatorSet that exclude the slashed nodes?
https://github.com/bosagora/agora/blob/dc5f739c64768e978deb65b4d2b5b8470976d8a7/source/agora/consensus/state/ValidatorSet.d#L315

The part I cannot find is where exactly are we checking if the validator is slashed in the 'receiveBlockSignature' method?
Either a bug in the agora implementation or just a malicious validator could produce a signed block even though the validator is slashed. If that signed block is processed later in 'receiveBlockSignature' then it would mess up header.validators

My original intention here was that map slot_sigs should only valid contain signatures from non-slashed validators, so it is easier to reason about/use slot_sigs. Sadly slot_sigs is updated even during the balloting phase when the externalized value is not yet decided upon. Instead of trying to fix this, I will just leave a comment on slot_sigs that it might contain signatures from slashed validators too.
The original reason of why I wanted to use slot_sigs is block rewards are distributed based on non-slashed validators who also signed.

My original intention here was that map slot_sigs should only valid contain signatures from non-slashed validators, so it is easier to reason about/use slot_sigs. Sadly slot_sigs is updated even during the balloting phase when the externalized value is not yet decided upon. Instead of trying to fix this, I will just leave a comment on slot_sigs that it might contain signatures from slashed validators too.
The original reason of why I wanted to use slot_sigs is block rewards are distributed to non-slashed validators who also signed.

My original intention here was that map slot_sigs should only valid contain signatures from non-slashed validators, so it is easier to reason about/use slot_sigs. Sadly slot_sigs is updated even during the balloting phase when the externalized value is not yet decided upon. Instead of trying to fix this, I will just leave a comment on slot_sigs that it might contain signatures from slashed validators too.
The original reason of why I wanted to use slot_sigs is block rewards are distributed to non-slashed validators who also signed.

I think it is best to use the validators fields in the block header to identify who has signed. The other map is just a local map of signatures that is not synched between the nodes.

My original intention here was that map slot_sigs should only valid contain signatures from non-slashed validators, so it is easier to reason about/use slot_sigs. Sadly slot_sigs is updated even during the balloting phase when the externalized value is not yet decided upon. Instead of trying to fix this, I will just leave a comment on slot_sigs that it might contain signatures from slashed validators too.
The original reason of why I wanted to use slot_sigs is block rewards are distributed to non-slashed validators who also signed.

I think it is best to use the validators field in the block header to identify who has signed. The map is just a local map of signatures that is not synched between the nodes.

Ugh, I just chekced and I was using the validator in the block header in the block reward ticket.


Infotip for iteration and custom query doesn't work

Infotio doesn't work when user hovers on iteration and custom query title.
Infotip icon should come and infotip should come on hovering respective icons.

Fixed via https://github.com/fabric8-ui/fabric8-planner/pull/2661


Is "Test the real-time endpoint" available now?

I couldn't find the Test menu on the endpoint I made.

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

ID: 2d019e5f-d971-b4f4-5fcf-2072ad30dec7
Version Independent ID: 14a7de84-6cd6-ebeb-df6c-2d93dfadb742
Content: Tutorial: Deploy ML models with designer - Azure Machine Learning
Content Source: articles/machine-learning/tutorial-designer-automobile-price-deploy.md
Service: machine-learning
Sub-service: core
GitHub Login: @PeterCLu
Microsoft Alias: peterlu

@damochiz we will review your feedback and get back to you shortly. Thanks.

@damochiz Yes, if you created and deployed your model as real-time pipeline, you should be able to follow these instructions to test the real time endpoint. Hope this helps. Thanks.

Hello @damochiz sorry, I probably didn't understand your question. From what I've gathered from the product team, this is a bug and a fix has been deployed. Can you try again? It may take a while to reach all regions, let us know if you're still experiencing any more issues. Thanks.

Thanks for confirming. I could see Test tab now. There is no problem to close this ticket. :)

Awesome, glad it's working now, thanks for confirming as well :).


Send a single stream to multiple sinks?

Hey,
So I have an mpsc where I named the stream endpoint rx and then I have a stream of sinks. I want to stream from rx to every sink in the order they come. So I stream to the first sink until send_start returns an error and then I continue to stream to the second sink until send_start returns an error and so on. I'm obviously a noob at tokio and maybe what I'm trying to do is really weird or completely wrong..
So the code is something like this:
        let x = child_writers.fold(rx, move |rx, writer| {
            writer.send_all(rx).map(|(_, rx)| rx)
        }).map_err(|_| ());

But I get the following compiler error:
error: internal compiler error: /checkout/src/librustc_trans/type_of.rs:157: Unexpected tail in unsized_info_ty: futures::future::join::MaybeDone<futures::MapErr<futures::stream::Fold<child::ProcessWriters, [closure@src/telnet_server.rs:94:40: 96:10], futures::Map<futures::sink::SendAll<pty::PtySink, futures::stream::MapErr<futures::stream::FilterMap<futures::sync::mpsc::Receiver<(std::net::SocketAddr, rust_telnet::codec::TelnetIn)>, [closure@src/telnet_server.rs:82:32: 93:10 process:std::rc::Rc<std::cell::RefCell<child::Process>>]>, [closure@src/telnet_server.rs:93:20: 93:68]>>, [closure@src/telnet_server.rs:95:37: 95:49]>, futures::stream::MapErr<futures::stream::FilterMap<futures::sync::mpsc::Receiver<(std::net::SocketAddr, rust_telnet::codec::TelnetIn)>, [closure@src/telnet_server.rs:82:32: 93:10 process:std::rc::Rc<std::cell::RefCell<child::Process>>]>, [closure@src/telnet_server.rs:93:20: 93:68]>>, [closure@src/telnet_server.rs:96:20: 96:26]>> for ty=futures::future::join::MaybeDone<futures::MapErr<futures::stream::Fold<child::ProcessWriters, [closure@src/telnet_server.rs:94:40: 96:10], futures::Map<futures::sink::SendAll<pty::PtySink, futures::stream::MapErr<futures::stream::FilterMap<futures::sync::mpsc::Receiver<(std::net::SocketAddr, rust_telnet::codec::TelnetIn)>, [closure@src/telnet_server.rs:82:32: 93:10 process:std::rc::Rc<std::cell::RefCell<child::Process>>]>, [closure@src/telnet_server.rs:93:20: 93:68]>>, [closure@src/telnet_server.rs:95:37: 95:49]>, futures::stream::MapErr<futures::stream::FilterMap<futures::sync::mpsc::Receiver<(std::net::SocketAddr, rust_telnet::codec::TelnetIn)>, [closure@src/telnet_server.rs:82:32: 93:10 process:std::rc::Rc<std::cell::RefCell<child::Process>>]>, [closure@src/telnet_server.rs:93:20: 93:68]>>, [closure@src/telnet_server.rs:96:20: 96:26]>>
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports
thread 'rustc' panicked at 'Box<Any>', /checkout/src/librustc_errors/lib.rs:418

Here is the function on github:
https://github.com/NickeZ/rups/blob/tokio-2/src/telnet_server.rs#L78

That.... looks like a rustc bug :) I would page @alexcrichton for this!

btw, I also think the "sum" variable in the fold example should be named "sum" instead of "a". It is not possible to see if it is "a" or "b" that is the sum variable.
https://docs.rs/futures/0.1.13/futures/stream/trait.Stream.html#method.fold

Fails on stable, beta and nightly: https://travis-ci.org/NickeZ/rups

I also think the "summing" variable in the fold example should be named "summing" instead of "a". It is not possible to see if it is "a" or "b" that is the sum variable.

The tipical name for that is accumulator, shortened as acc, as you can see in this std example. You can open a PR to change that example!

The rustc error here may be similar to https://github.com/rust-lang/rust/issues/40274, although I don't recognize it off hand :(

I got around the compiler error by simply adding features to handle.spawn() instead.
I don't understand how I should gracefully indicate that my sink cannot receive more items. It seems like the only way is to return an error. But if I return an error send_all() will also return an error instead of (stream, sink) which is what I need to continue..

@NickeZ ah yeah right now most standard combinators throw away intermediate state on errors, so if you need to preserve state on an error you may need to copy the combinator locally to tweak its implementation.

@alexcrichton thanks for pointing me in the right direction. I now have a working fork of SendAll that returns whether the stream or the sink ended instead of erroring. I'm not sure if this is useful to you. Anyway here is the code:
https://github.com/NickeZ/toy-tokio/blob/master/src/main.rs

Ok sounds like ICEs and functionality have been resolved/worked around, so yay! In that case I'm going to close this, but please let me know if that's in error!


Feat: Search results

Describe the feature
Display a message to user "No results found" when the search result is null for better user experience
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'23 contributor
[X] I want to work on this issue

I opened a PR related to this issue and added the desired result. It passed the tests. The issue should be handled now.

I opened a PR related to this issue and added the desired result. It passed the tests. The issue should be handled now.

But bro, I wanted to work on this issue


Make Y/n (Yes by default)

By default Y is what is entered when just pressing enter. I think you should do the same in this script.

I would rather keep it as a fail-safe, if one accidentally hit enter with wrong answer.


Remove trailing '/' in appLoc

:tada: This issue has been resolved in version 1.13.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Error in Slybot tests

Hi,
I have an enconding error when running some of the the Slybot Tests.
The error seems to be linked to the use of the scrapely library.
Here is for example what I have for test_spider.SpiderTest:
Traceback (most recent call last):
  File "/opt/amass-trainer-0.0.1-SNAPSHOT/slybot/slybot/tests/test_spider.py", line 317, in test_variants
    spider = self.smanager.create(name)
  File "/opt/amass-trainer/TRAINER_ENV/lib/python2.7/site-packages/slybot/spidermanager.py", line 61, in create
    **args)
  File "/opt/amass-trainer/TRAINER_ENV/lib/python2.7/site-packages/slybot/spider.py", line 41, in __init__
    settings, spec, item_schemas, all_extractors)
  File "/opt/amass-trainer/TRAINER_ENV/lib/python2.7/site-packages/slybot/spider.py", line 201, in _configure_plugins
    instance.setup_bot(settings, spec, schemas, extractors)
  File "/opt/amass-trainer/TRAINER_ENV/lib/python2.7/site-packages/slybot/plugins/scrapely_annotations/annotations.py", line 41, in setup_bot
    ), key=lambda x: x[0])
  File "/opt/amass-trainer/TRAINER_ENV/lib/python2.7/site-packages/slybot/plugins/scrapely_annotations/annotations.py", line 40, in <genexpr>
    for t in templates if t.get('page_type', 'item') == 'item'
  File "/opt/amass-trainer/TRAINER_ENV/lib/python2.7/site-packages/scrapely/htmlpage.py", line 49, in dict_to_page
    return HtmlPage(url, headers, body, page_id, encoding)
  File "/opt/amass-trainer/TRAINER_ENV/lib/python2.7/site-packages/scrapely/htmlpage.py", line 78, in __init__
    assert isinstance(body, unicode), "unicode expected, got: %s" % type(body).__name__
AssertionError: unicode expected, got: str

I am using python 2.7, Portia 16.06.1, slybot 0.13.0b18 and scrapely 0.12.0.
Any clues?
Note that this error is not only happening in the tests but also at run time when running the scrapely extraction on some webpages.

Hi @leorocher is this still happening for you? The slybot tests run fine on the CI server

Tried again today after upgrading to slybot 0.13.0b19, I still have the same issue
FYI here is what I have installed:
pip freeze

Pillow==3.2.0
PyYAML==3.11
Scrapy==1.0.0
Twisted==15.4.0
adblockparser==0.5
autobahn==0.10.4
bcrypt==2.0.0
cffi==1.5.2
characteristic==14.3.0
chardet==2.3.0
cryptography==1.3.1
cssselect==0.9.1
dateparser==0.2.0
dulwich==0.9.7
enum34==1.1.2
funcparserlib==0.3.6
functools32==3.2.3.post2
idna==2.1
ipaddress==1.0.16
jdatetime==1.7.4
jsonschema==2.4.0
loginform==1.0
lxml==3.4.1
monotonic==0.3
mysql-connector-python==1.2.3
ndg-httpsclient==0.4.0
numpy==1.11.0
page-finder==0.1.1
parse==1.6.6
psutil==4.1.0
psycopg2==2.6.1
pyOpenSSL==16.0.0
pyasn1==0.1.9
pyasn1-modules==0.0.8
pycparser==2.14
pysqlite==2.8.2
python-dateutil==2.4.2
pytz==2016.3
qt5reactor==0.3
queuelib==1.4.2
re2==0.2.23
regex==2016.4.3
requests==2.7.0
scrapely==0.12.0
scrapyjs==0.1.1
service-identity==14.0.0
six==1.10.0
slybot==0.13.0b19
slyd==0.0.0
splash==2.1
txaio==2.2.2
umalqurra==0.2
w3lib==1.13.0
wsgiref==0.1.2
xvfbwrapper==0.2.8
zope.interface==4.1.3

@leorocher: Can you try again with slybot 0.13.0b20?

MBS:portia samirfor$ git log -1
commit 0526b932479cd9fe28ce587c676ec27719345d3d
Author: Ruairi Fahy<EMAIL_ADDRESS>Date:   Wed Oct 26 14:37:12 2016 +0100

    Release slybot 0.13.0b26

    Fix issue with empty css selectors
    Change IblItem to be a subclass of scrapy.Item
...
MBS:portia samirfor$ docker run -itp 9001:9001 --rm -v $PWD/data:/app/slyd/slyd/data:rw --name portia portia
2016-11-01 02:50:27+0000 [-] Log opened.
2016-11-01 02:50:27.947515 [-] Splash version: 2.2.1
2016-11-01 02:50:27.950249 [-] WARNING: Lua scripting is not available because 'lupa' Python package is not installed
2016-11-01 02:50:27.952117 [-] Qt 5.5.1, PyQt 5.5.1, WebKit 538.1, sip 4.17, Twisted 15.4.0
2016-11-01 02:50:27.954090 [-] Python 2.7.6 (default, Jun 22 2015, 17:58:13) [GCC 4.8.2]
2016-11-01 02:50:27.955168 [-] Open files limit: 1048576
2016-11-01 02:50:27.956392 [-] Can't bump open files limit
2016-11-01 02:50:28.434613 [-] Xvfb is started: ['Xvfb', ':1', '-screen', '0', '1024x768x24']
2016-11-01 02:50:30.906415 [-] /app/slyd/slyd/bot.py:25: scrapy.exceptions.ScrapyDeprecationWarning: Module `scrapy.log` has been deprecated, Scrapy now relies on the builtin Python library for logging. Read the updated logging entry in the documentation to learn more.
2016-11-01 02:50:30.925776 [-] /app/slyd/slyd/bot.py:32: scrapy.exceptions.ScrapyDeprecationWarning: Module `scrapy.spider` is deprecated, use `scrapy.spiders` instead
2016-11-01 02:50:32.917288 [-] /app/slyd/slyd/bot.py:60: scrapy.exceptions.ScrapyDeprecationWarning: log.msg has been deprecated, create a python logger and log through it instead
2016-11-01 02:50:32.939310 [-] Site starting on 9002
2016-11-01 02:50:32.941136 [-] Starting factory <slyd.server.Site instance at 0x7f87c15cb128>
...
QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
2016-11-01 02:50:16.956547 [-] "<IP_ADDRESS>" - - [01/Nov/2016:02:50:16 +0000] "GET /proxy?url=https%3A%2F%2Fwww.bilheteriavirtual.com.br%2Fimg%2Fheader-bg.png&tabid=139648766211024&referer=www.bilheteriavirtual.com.br HTTP/1.0" 200 48394 "http://<IP_ADDRESS>:9001/proxy?url=https%3A%2F%2Fwww.bilheteriavirtual.com.br%2Fcss%2Fstyle.css&tabid=139648766211024&referer=www.bilheteriavirtual.com.br" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36"
Traceback (most recent call last):
  File "/app/slyd/slyd/splash/ferry.py", line 165, in sendMessage
    self.protocol.sendMessage(metadata(self.protocol))
  File "/app/slyd/slyd/splash/commands.py", line 100, in metadata
    res.update(extract(socket))
  File "/app/slyd/slyd/splash/commands.py", line 116, in extract
    js_items, js_links = extract_data(url, html, socket.spider, templates)
  File "/app/slyd/slyd/splash/utils.py", line 26, in extract_data
    for value in spider.parse(page(url, html)):
  File "/app/slybot/slybot/spider.py", line 228, in _handle
    for item_or_request in itertools.chain(*generators):
  File "/app/slybot/slybot/plugins/scrapely_annotations/annotations.py", line 121, in handle_html
    htmlpage = htmlpage_from_response(response, _add_tagids=True)
  File "/app/slybot/slybot/utils.py", line 103, in htmlpage_from_response
    encoding=response.encoding)
  File "/usr/local/lib/python2.7/dist-packages/scrapely/htmlpage.py", line 78, in __init__
    assert isinstance(body, unicode), "unicode expected, got: %s" % type(body).__name__
AssertionError: unicode expected, got: str
Aborted

Should be fixed with latest scrapely


WEB: Updated the PR Handler

Fixed issue #608
This commit is to fixe the issue #608.
Signed-off-by: Geunsik Lim<EMAIL_ADDRESS>

:memo: Version: 1.3.20190927. Thank you for submitting PR #610. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

After this PR:


fix nodeIsActive()

this fixes isActive.image() mentioned in #225
nodeIsActive was only checking parent nodes and missed the node
currently selected.

Thanks marius!


Fix .avi video seeking and Android playback when HW acceleration is enabled

Closes #4858 and fixes both problems that I mentioned in #4860
Android's MediaCodec unfortunately turned out to be a lost cause, I just couldn't get it to work properly no matter what I tried, so I added a check that disables HW decoding if the source is an AVI file...
As before, I only got to test this with the following HW devices, I highly recommend testing this on everything before merging.

[x] NVDEC
[x] QuickSync
[x] DXVA
[ ] VDPAU
[x] VA-API
[x] MediaCodec
[ ] VideoToolbox - MacOS
[ ] VideoToolbox - iOS

Patch for testing:
Index: osu.Framework.Tests/Visual/Sprites/TestVideo.cs
===================================================================
diff --git a/osu.Framework.Tests/Visual/Sprites/TestVideo.cs b/osu.Framework.Tests/Visual/Sprites/TestVideo.cs
--- a/osu.Framework.Tests/Visual/Sprites/TestVideo.cs	(revision bb82b3c57715f2f26532053ea1436b9102e5c34b)
+++ b/osu.Framework.Tests/Visual/Sprites/TestVideo.cs	(date<PHONE_NUMBER>869)
@@ -14,7 +14,7 @@
     {
         private static MemoryStream consumeVideoStream()
         {
-            var wr = new WebRequest("https://assets.ppy.sh/media/landing.mp4");
+            var wr = new WebRequest("https://file-examples-com.github.io/uploads/2018/04/file_example_AVI_480_750kB.avi");
             Task.Run(() => wr.PerformAsync());

             while (!wr.Completed)

The FPS counter should show 30, if it's ~20 then I have to go back to the drawing board because it means that the returned timestamps are wrong.

VDPAU also runs at 30fps :+1:

macOS is also correct. iOS we can ignore for the moment (should be fine though, if macOS is).

@Opelkuh thanks for the quality contribs. make sure to submit a request for bounty if interested in compensation!


pass missing argument to oauth2_error in _oauth2_dpop_jti_validate

Fixes a crash in test/check_oauth2.c
Signed-off-by: Alexander Bokovoy<EMAIL_ADDRESS>

@zandbelt this crash is present on master on any architecture.


Add support for single test method execution (GRADLE-2865)

Add support to specify list of test method names using test.single property, with the (optional) format: -Dtest.single=TestClassName#method1,method2.
I show all tests passing on subprojects/plugins. Played around with some real testng and junit test code and was able to successfully run only the method(s) specified. Also tested to make sure not specifying any test method names still does indeed run all test methods in the class.

Seems like ability to run a single test method is still relevant today. Any progress on this issue?

I am trying to run a single test method with *gradlew test --tests TestName.testMethod, but I have this error:
**What went wrong:
Execution failed for task ':test'.

No tests found for given includes: [TestName.testMethod]*

Can someone tell what am I doing wrong?
Thank you!

Please post this kind of questions in the Gradle discussion forum:
https://discuss.gradle.org/c/help-discuss
Anyhow, the test section you described above should work with the current Gradle release (3.1).


Namespace blob

Implements #62

I think this one's done.  Anyone care to sign off before I merge?

:+1:


Add Example for passing props in md files

Note this doesn't work - it seemed to but now fails. But the docs DO need updating
I can't think of any yml syntax allowing layout to both be a value and have object for props. Only make it an object with a file prop and pops prop.
##
What kind of changes does this PR include?

[] Minor content fixes (broken links, typos, etc.)
[x] New or updated content
[ ] Translated content
[ ] Changes to the docs site code
[ ] Something else!

Description
Add Example for passing props in md files

closing as is document in previous section. Confusing and really could do wit hsome rework.
https://docs.astro.build/en/guides/markdown-content/#markdown-layouts


MvcCoreServiceCollectionExtensions retrieves first registered service instead of last

This line:
https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNetCore.Mvc.Core/DependencyInjection/MvcCoreServiceCollectionExtensions.cs#L90
Per @danroth27 :

When you request a service from the built service provider it will give you the last service added, not the first one. This method should mimic the DI behavior.

This issue doesn't generally affect user scenarios today, because this method is used to extract the hosting environment service and there is typically only one of those. I hit this issue as part of my module prototyping when I added a new hosting environment for each module. The added hosting environment should override the existing one, but currently it doesn't because this method picks the first instead of the last. I'm working around this right now by simply removing the app hosting environment for each module and then replacing it with a new one.

Fix ready in #5540 but I'll get a PR out that builds on that and adds a test.

f32d0f2 and 48546db

Thanks for f32d0f2 @danroth27 !


[GHSA-58xm-mxjf-254g] Multiple vulnerabilities allow bypassing path filtering of agent-to-controller access control in Jenkins

Updates

Affected products
References

Comments
Add patch link related to CVE-2021-21685.

Hi @sunSUNQ, SECURITY-2455 covers 11 separate CVEs. How do you know that https://github.com/jenkinsci/jenkins/commit/104c751d907919dd53f5090f84d53c671a66457b fixes CVE-2021-21685 specifically?

Hello, I found three patches related to SECURITY-2455. The current vulnerability information only provides two of them, without specifying which part of the code specifically fixes the current vulnerability. I believe it is necessary to provide all three patches for a complete understanding.


Route docs Issue

while configuring Tracee and Postee, I noticed that if I follow the docs at https://github.com/aquasecurity/postee/blob/main/docs/routes.md and use this for my route
input: contains(input.SigMetadata.ID,"TRC-")

I get errors
Error while evaluating rego rule input: contains(input.SigMetadata.ID,"TRC-") :1 error occurred: 1 error occurred: postee.rego:6: rego_parse_error: unexpected : token: expected \n or ; or }
        input: contains(input.SigMetadata.ID,"TRC-")

removing the input: from the start fixes it, should we updated the docs for that?

@jerbia  we could create a documentation page about cfg.yaml.
When we use the config file, we will need input:. https://github.com/aquasecurity/postee/blob/main/cfg.yaml#L17
When we use the postee-UI we don't need it. I think so.
@raesene  could you confirm if you use the postee-UI or the cfg.yaml ?

@jerbia, @krol3, @raesene
from what I can understand input:  is part of yaml structure. UI parses yaml so everything from yaml properties goes to corresponding fields


ModuleNotFoundError: No module named 'pkg_resources'

Bug description
> poetry add apache-superset
Using version ^4.0.2 for apache-superset
Resolving dependencies... Downloading https://files.pythonhosted.org/packages/9c/e2/1a3507af7c8f91f8a4975d651d4aeb6a846dfdf74713954186ade4205
Resolving dependencies... (25.1s)
...

> superset db upgrade
Traceback (most recent call last):
  File "/Users/me/git/gl/myorg/myproj/.venv/bin/superset", line 5, in <module>
    from superset.cli.main import superset
  File "/Users/me/git/gl/myorg/myproj/.venv/lib/python3.11/site-packages/superset/cli/main.py", line 28, in <module>
    from superset.cli.lib import normalize_token
  File "/Users/me/git/gl/myorg/myproj/.venv/lib/python3.11/site-packages/superset/cli/lib.py", line 20, in <module>
    from superset import config
  File "/Users/me/git/gl/myorg/myproj/.venv/lib/python3.11/site-packages/superset/config.py", line 39, in <module>
    import pkg_resources
ModuleNotFoundError: No module named 'pkg_resources'

How to reproduce the bug
see above
Screenshots/recordings
No response
Superset version
4.0.2
Python version
3.11
Node version
Not applicable
Browser
Not applicable
Additional context
No response
Checklist

[X] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

fixed with:
> poetry add setuptools

and re-running superset command


Wrong/Corrupt files (FileSource) parameter in ResponseTransformer#transform method

Hallo, I am using wiremock 2.19.0 and found something strange by implementing of custom ResponseTransformer.
My WireMock Server configuration are;
this.wireMockServer = new WireMockServer(           WireMockConfiguration.options()              .port(properties.getPort())              .bindAddress(properties.getHost())              .usingFilesUnderClasspath("wiremock")             .extensions(CustomResponseTransformer.class) )
My CustomResponseTransformer gets the wrong files - Parameter in transform method with double "__files" in the path like  "wiremock/__files/__files"

:thumbsup:


96 vulnerabilities after running npx create-react-app my-app command

node version 16.3.0
nom version 7.15.1

While executing the command npx create-react-app my-app, I am getting
96 vulnerabilities (85 moderate, 11 high)

Please check.
Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts with cra-template...

added 1922 packages, and audited 1923 packages in 60s

145 packages are looking for funding
  run `npm fund` for details

96 vulnerabilities (85 moderate, 11 high)

To address all issues, run:
  npm audit fix

Run `npm audit` for details.

Initialized a git repository.

Installing template dependencies using npm...

added 32 packages, and audited 1955 packages in 9s

145 packages are looking for funding
  run `npm fund` for details

96 vulnerabilities (85 moderate, 11 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.
Removing template package using npm...

removed 1 package, and audited 1954 packages in 7s

145 packages are looking for funding
  run `npm fund` for details

96 vulnerabilities (85 moderate, 11 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

Created git commit.

Success! Created my-app at /Users/bikashagrawal/react-projects/my-app
Inside that directory, you can run several commands:

  npm start
    Starts the development server.

  npm run build
    Bundles the app into static files for production.

  npm test
    Starts the test runner.

  npm run eject
    Removes this tool and copies build dependencies, configuration files
    and scripts into the app directory. If you do this, you can’t go back!

We suggest that you begin by typing:

  cd my-app
  npm start

Happy hacking!

I tried to run npm audit fix and npm audit fix --force, but it didn't help.

I got the same result

i got this too

same problem

same problem

Does not justify another tread, I have a similar issue with create-react-app. I use Windows 10 with VSCode.
"dependencies": {
"@testing-library/jest-dom": "^5.14.1",
"@testing-library/react": "^11.2.7",
"@testing-library/user-event": "^12.8.3",
"react": "^17.0.2",
"react-dom": "^17.0.2",
"react-scripts": "^4.0.3", <--- (Is this it?)
"web-vitals": "^1.1.2"
},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test",
"eject": "react-scripts eject"
},
---- I deleted "react-scripts": "^4.0.3", from the file package.json. Found that Uninstalling react-scripts returns the following.

npm install
removed 1843 packages and audited 83 packages in 52.197s

3 packages are looking for funding
run npm fund for details
found 0 vulnerabilities
---- But wait need react-scripts to work.  I tried a different version from 4 months ago, but got the same results.

npm i<EMAIL_ADDRESS>--save
---- Why are these packages deprecated? OMG
npm WARN deprecated<EMAIL_ADDRESS>babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated<EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>This package has been deprecated and is no longer maintained. Please use @rollup/plugin-babel.
npm WARN deprecated<EMAIL_ADDRESS>Switch to 'npm install joi'
npm WARN deprecated<EMAIL_ADDRESS>Moved to 'npm install @sideway/address'
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated and is no longer supported or maintained
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated and is no longer supported or maintained
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated and is no longer supported or maintained
npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:

https://opencollective.com/core-js
https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

<EMAIL_ADDRESS>postinstall D:\Web Apps\myappnamehere\node_modules\core-js
node -e "try{require('./postinstall')}catch(e){}"

<EMAIL_ADDRESS>postinstall D:\Web Apps\myappnamehere\node_modules\ejs
node ./postinstall.js

Thank you for installing EJS: built with the Jake JavaScript build tool (https://jakejs.com/)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\react-scripts\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\watchpack-chokidar2\node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\webpack-dev-server\node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.

<EMAIL_ADDRESS>added 1847 packages from 648 contributors and audited 1933 packages in 192.476s

145 packages are looking for funding
run npm fund for details
found 86 vulnerabilities (82 moderate, 4 high)
run npm audit fix to fix them, or npm audit for details

I encountered the same, this is my prompt, can you ask what your prompt is?
我遇到了相同，这是我的提示，能问下你们的是什么吗？

Secondly, running npm init and then npx can solve the above problem; but a new problem has emerged: My project is MyReact / my-app, why does MyReact prompt an error? Is it because I am running npx under MyReact? (But if npx runs in the root directory, it will report an error “npm ERR! 404 Not Found - GET https://registry.npmjs.com/creat-react-app - Not found” and cannot be run directly.)
二次补充，先运行 npm init 再运行 npx 可以解决上面的问题；但新的问题又出来了：我的项目是 MyReact / my-app ，为什么 MyReact 会提示错误呢？是因为我是在 MyReact 下运行的 npx 吗？（但 npx 在根目录下是没法运行啊，报错 404）

Same here.

Thanks to everyone who commented and it seems everyone is facing the same issue. What is the solution to this issue?

@bcagarwal The more comments, the more visibility to the issue.

@DancingColors Got it. Thank you.

Node JS version 14.16.1
npm version 6.14.12
found 89 vulnerabilities (1 low, 82 moderate, 6 high)

感谢所有评论的人， 似乎每个人都面临着同样的问题。这个问题的解决方案是什么

Upgrade npm to npm7

The problems encountered during the two days of learning this step (win10, nodejsv14.17.0):

Prompt 404
1.1 Install create-react-app globally, and then execute npx
The file idealTree already exists
2.1 Create file A, run npx in folder A
Prompt that there are vulnerabilities
3.1 Upgrade npm to 7, automatically install dependencies
After the npx command is executed, it prompts that folder A lacks package.json
4.1 Before executing npx, execute npm init first, manually create package.json, and then execute npx
4.2 Or before executing npx, install yarn globally, and then execute npx.

Supplement: 4.2 Unresolved errors: When the installation reaches 3/4, there will be two error messages, and no solution has been found yet.
这两天学习这一步遇到的问题（win10,nodejsv14.17.0）:
1.提示404
1.1 全局安装 create-react-app，然后再执行 npx
2. 文件 idealTree 已存在
2.1 创建文件A，在文件夹A中运行 npx
3. 提示存在漏洞
3.1 升级npm 到7，自动安装依赖
4. npx命令执行后，提示文件夹A 缺少package.json
4.1 在执行 npx 之前，先执行 npm init ，手动创建 package.json，然后再执行 npx
4.2 或者在执行 npx 之前，先全局安装 yarn，然后再执行 npx。
补充：4.2 未解决的错误： 安装到3/4时，会有两个错误提示，暂未找到解决办法。

I am getting this issue as well

A lot of this has to do with the fact that react-scripts is added as a dependency in stead of a devDependency. Technically, the vulnerabilities will not be deployed unless they are also dependencies of your package or another dependency that will get deployed.

Is adding a label required? If yes, I am unable to do so. Could someone please help to add a label to this issue?

This is extremely important to be fixed as soon as possible.

Big upvote on the necessity of fixing that one.

Im having the same issue.
Node: 16.3.0
npm: 7.15.1

the immer vulnerability from ages ago that still hasnt been resolved.

I recognize that technically these may not actually cause vulnerabilities for our applications, but that is just such an unrealistic view of how things really work. Bureaucracy is going to bureaucracy, so not fixing these just causes headaches for so many people.

Same there !!

I have the same issue, running on Win10, Npm7
# npm audit report

browserslist  4.0.0 - 4.16.4
Severity: moderate
Regular Expression Denial of Service - https://npmjs.com/advisories/1747
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/react-dev-utils/node_modules/browserslist
  react-dev-utils  >=6.0.0-next.03604a46
  Depends on vulnerable versions of browserslist
  node_modules/react-dev-utils
    react-scripts  >=0.10.0-alpha.328cb32e
    Depends on vulnerable versions of @svgr/webpack
    Depends on vulnerable versions of mini-css-extract-plugin
    Depends on vulnerable versions of react-dev-utils
    Depends on vulnerable versions of resolve-url-loader
    Depends on vulnerable versions of webpack
    Depends on vulnerable versions of webpack-dev-server
    node_modules/react-scripts

We don't see any attention to this issue and we don't know whether it would be fixed. Is there anyway we can get desired attention to this issue so that it would be fixed on priority?

Can this be cosed in favor of: https://github.com/facebook/create-react-app/issues/11012 ?

These vulnerabilities have been around for a long time. Is there any plan to fix them??

Same problem here...

There are no actual vulnerabilities here.
Unfortunately, npm audit has no idea that these packages are development-only dependencies. From what I can tell, none of these "vulnerabilities" actually affect your application (or even development machine) in any way.
This is pure security theater. Which is unfortunate, because it teaches people to ignore real vulnerabilities (which these are not, in the context of how they're used in CRA).
Yes, it would be good to cut a patch to remove the warnings, but we are all unfortunately wasting time here.

These warnings are false positives. There are no actual vulnerabilities affecting your app here. To remove npm audit warnings, move react-scripts from dependencies to devDependencies in your package.json.
I agree with the point in https://github.com/facebook/create-react-app/issues/11102 and will make this change so that new projects don't keep having these false positive warnings.

Please see https://github.com/facebook/create-react-app/issues/11174.


CCDB GE/004 - Section <IP_ADDRESS>.3

Para 43
Comment:
Test 2, Step 4: why clear" instead of "destroy"?"
Proposal:
Priority: 1

This could be changed in v1.1. I do not see this as a serious issue though, as you are having the system "clear" the key and then seeing if "clearing" properly destroys the key. I do not see there is any actual conflict in the language, though changing it would likely provide somewhat more clarity.
This would need to be changed in Test 2, Step 4 and Test 3, Step 3

I'd accept the comment and change "clear" to "destroy" to match the wording of "key destruction." We can make the change in v1.1.


1.8.1 upgrade breaks SSL compatibility with some servers

I'm trying to connect to a network I had configured perfectly fine in 1.6 and I now get the following error:
Disconnected from IRC (error:1408F10B:SSL routines:ssl3_get_record:wrong version number). Reconnecting...
How do I fix this?  It's a vague error message.

How did you compile ZNC? Did you do it yourself? Did you do an OS upgrade? Some OSs disable some versions of the TLS protocol in OpenSSL.

How do I fix this? It's a vague error message.

The error is something like "the other end tried to talk TLS 1.0, but I do not want to talk that". I am not entirely sure and I also find OpenSSL's error messages cryptic.
You could try connecting on the command line with something like openssl s_client -connect irc.freenode.org:6697. This says something like New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384 somewhere in the middle (after the certificates). So, this is TLS 1.3. If your IRC server has something else here, my guess about what the issue is could be right.

What happened? Did you fix your problem? What was the solution?

I have the same problem, reported in https://github.com/znc/znc/issues/1781.


Barcodes are blurry when printed from Chrome and other browsers

Even the example page at: http://lindell.me/JsBarcode/ is producing a blurry barcode when you go to print from Chrome.
IE is a little more crisp, but not by much.

@jwrb had the same problem. That's one one the reasons why SVG support is added for JsBarcode 3.
It does still have a beta tag but seems to be stable. The only known bug with it was patched 1 hour ago. I will create a new release with the changes as soon as possible.
Just use
<svg id="barcode"></svg>

Instead of IMG or canvas and it should render much more nicely.

Just added the new release. Could you confirm this is solving the issue?

That fixed the blurriness issue completely.
Just a side note, the print preview shows the barcodes like this:

But once you print them, they do render correctly and you can scan them no problem. May just want to make a note about that so people are aware.
Thanks a bunch for the quick solution. Great job.

This seems strange. Could you give the entire query you are using for the rendering and also what browser you are using?

And if you try to zoom in on the print preview. Is the problem gone?

Only browser not rendering print preview correctly, that I can see, is Chrome. I'm using version 49 (latest I believe)
Print preview renders correctly in Firefox, Safari, and Opera.

Zoom fixed it, it renders properly in print preview once you zoom in a bit.
Thanks again for the assistance.

Perfect, then it's no problem but might be good to know as you said :smile:. Closing the issue.

2020 still the rendering with <img> tag is blurry. my workaround is the set the width to 6 or 10. and then use CSS to scale down image for better quality. I use svg but the printing is suffer with my electron app. so <img>  is a go to for now.

2020 still the rendering with <img> tag is blurry. my workaround is the set the width to 6 or 10. and then use CSS to scale down image for better quality. I use svg but the printing is suffer in speed with my electron app. so <img> is a go to for now.

Add image-rendering: nearest-neighbor; image-rendering: pixelated; to the  CSS and the result is almost identical to SVG


Add declaration context as object to function class block

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: IIFE sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


SEG-665 Azure SQL Without Elastic DB Pools

Description
[Describe what this change achieves]
Issues Resolved
[List any existing issues this PR resolves]
Contribution Check List

[ ] All tests pass.
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable
[ ] New functionality has been documented in CHANGELOG.MD

          3 Errors

:no_entry_sign:
Please add a ‘default_frequency’ property field and value. operational/azure/azure_sql_using_elastic_pool/risc-azure-migrate.pt

:no_entry_sign:
Please add the info field. operational/azure/azure_sql_using_elastic_pool/risc-azure-migrate.pt

:no_entry_sign:
Please add labels to this Pull Request

  Generated by :no_entry_sign: Danger


correction minActiveVoltage

207V ist die untere zulässige Grenze (-10%)

If it's a problem for phase detection - perhaps it's worth it to go even lower? 200V ?

I think it will be no problem, but let's wait and see what the chief electrician has to say about it ;)

Thanks @VolkerK62 !


Org static slug

This commit is basically a cleanup of things related to demo organizations. It provides two simple methods – Organization.is_demo() and Event.is_demo() – which can be used to check whether the organization or event is a demo.
In practical terms, this PR results in a few extra bits of helpful text being displayed, slugs not being modifiable, and new events being set to use test APIs.
It might make more sense to handle the demo slug as a setting rather than an attribute on Organization, but this is easier and it's not really ever going to be customized...

Looks good.


PermissionError: Operation not permitted

Hello,
Before all thanks for the work you gave in this.
When running the container, Python throw back an error, see the logs:

And I can confirm from the shell:

From what I could find this comes from a broken Python version for Raspbian
see here: https://stackoverflow.com/questions/70195968/dockerfile-raspberry-pi-python-pip-install-permissionerror-errno-1-operation
and here: https://bugs.python.org/issue45960
Although I am not sure it's Raspbian you use since the package manager is apk ?

However when looking at your image I cannot get what Python you use and that layer ADD is a bit obscure to me ( I am a docker noob ):

Can someone provide pointers on how to identify further that Python version and how to modify that first layer please ?
Many thanks,

So the first stupid answer to find what is that ADD layer is "go look at the Dockerfile" (in Portainer they show the ADD rather than FROM) and from there we see it's  alpine:3.16
For the Python exception, I tried running the container on Bookworm and it works. Indeed I was previously running the container  was a raspberry, I thought Docker was abstracting it so it would use whatever OS image is pulled but lacking Docker knowledge.
Looking for modifying the image to be Raspberry friendly


Managed dependencies requires only access to only https://www.powershellgallery.com to download modules?

Hi Team,
This page says as following.
"Managed dependencies requires access to https://www.powershellgallery.com to download modules. When running locally, make sure that the runtime can access this URL by adding any required firewall rules."
But it seems to access to https://psg-prod-eastus.azureedge.net as well.
If there are any other sites it requires access to, please let me know.
Best Regards,
Takeshi Katayama

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

ID: efae763f-03a9-b3b0-e7ad-52f9b1559438
Version Independent ID: 2afd9c78-e5b0-5d34-b809-47d9576399d0
Content: PowerShell developer reference for Azure Functions
Content Source: articles/azure-functions/functions-reference-powershell.md
Service: azure-functions
GitHub Login: @eamonoreilly
Microsoft Alias: glenga

Thanks for the feedback! We are currently investigating and will update you shortly.

@take-4c Looks like there are a couple of endpoints that must be considered.
Thanks for the feedback! We have assigned this issue to the content author to review and update accordingly.

@PramodValavala-MSFT -san,
Thank you for the prompt response! I see!
You might want to make one of them a link so that you don't have to manage the information twice.
Thanks.


Old screenshots

Great article! It would be nice to update the steps and screenshots to reflect the ARM environment though in the "Setup the Application" section.

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

ID: 1e31ea14-f6b0-0cd8-0aee-64427a665a36
Version Independent ID: 60879db1-8dff-b97b-3051-c129181f1c97
Content: Set up Azure Key Vault with end-to-end key rotation and auditing
Content Source: articles/key-vault/key-vault-key-rotation-log-monitoring.md
Service: key-vault
GitHub Login: @swgriffith
Microsoft Alias: jodehavi;stgriffi

@jpr2016git Thanks for reporting! I have assigned the issue to the author to investigate and update as appropriate.
@msmbaldwin I have assigned this issue to you as unable to find swgriffith GitHub login.

@MohitGargMSFT I have a PR open to update the screenshots. I'll update once that the changes have merged.

@jpr2016git Thank you very much for your feedback. I have updated the screenshots.

#please-close


Use cog to perform codegen in grafana-app-sdk

For go types: https://github.com/grafana/grafana-app-sdk/blob/324159db30045da4deb4f204b05f627998e89217/codegen/jennies/gotypes.go#L100-L108 (and other places too)
As well as typescript, instead of cuetsy.

A PR is open in grafana-app-sdk is open to showcase how a cog integration could look like: https://github.com/grafana/grafana-app-sdk/pull/296

Done in https://github.com/grafana/grafana-app-sdk/pull/485


Configurations with circular references cause Karma to fail to run

Expected behaviour
Karma runs even if there are circular references in the configuration.
These can happen with custom keys added directly to the configuration, or inside plugin modules. The internal data structure should not cause Karma to fail to run.
Actual behaviour
Karma fails to run with TypeError: Converting circular structure to JSON.
Environment Details

Karma version (output of karma --version): 3.0.0
Relevant part of your karma.config.js file

const selfRefObject = {};
selfRefObject.ref = selfRefObject;

module.exports = function (config) {
  config.set({
    basePath: '',
    frameworks: ['jasmine'],
    plugins: [
      require('karma-jasmine'),
      require('karma-chrome-launcher'),
    ],
    browsers: ['ChromeHeadless'],
    files: ['./simple.spec.js'],
    selfRefObject
  });
};

Steps to reproduce the behaviour

git clone https://github.com/filipesilva/karma-circular-structure
npm install
npm test

This error happens because JSON.stringify is called on the final configuration in these two lines:
https://github.com/karma-runner/karma/blob/20eab32345a2e47334aada35ab6cf7c0a0000b7b/lib/server.js#L65
https://github.com/karma-runner/karma/blob/20eab32345a2e47334aada35ab6cf7c0a0000b7b/lib/server.js#L363
Since the configuration contains arbitrary data, objects, modules, and functions, JSON.stringify might not be the best way way of serializing it.
Related to https://github.com/karma-runner/karma/issues/3075

I had the similar error when I was using karma-webpack. When I had ForkTsCheckerWebpackPlugin defined in the plugins of my webpack configuration I had the same problem. My workaround was to remove this plugin from the Webpack Test Configuration.

@djusv as a workaround you can also add a toJSON: () => { }, method to the problematic configuration object.
In the repro above, it would be:
const selfRefObject = {};
selfRefObject.ref = selfRefObject;
selfRefObject.toJSON = () => { };

When that method is present, JSON.stringify() will use it instead of parsing the object.

karma=> 3.1.1
getting this error
Converting circular structure to JSON
Is this error  fixed in any version?

Closing as this issue has been fixed in 3.1.2 and then improved in 4.2.0


Crash With IGListDiffKit  SIGABRT ABORT

Crashlytics - Stack trace
Platform: apple
Crashed: com.apple.main-thread
0  libsystem_kernel.dylib         0x7674 __pthread_kill + 8
1  libsystem_pthread.dylib        0x71ac pthread_kill + 268
2  libsystem_c.dylib              0x20c8c abort + 180
3  libsystem_malloc.dylib         0x1de2c malloc_vreport + 908
4  libsystem_malloc.dylib         0x1e0d0 malloc_zone_error + 100
5  libsystem_malloc.dylib         0x1382c free_list_checksum_botch + 40
6  libsystem_malloc.dylib         0x69d4 small_free_list_remove_ptr_no_clear + 980
7  libsystem_malloc.dylib         0x4210 small_malloc_from_free_list + 344
8  libsystem_malloc.dylib         0x1e38 small_malloc_should_clear + 220
9  libsystem_malloc.dylib         0x63b8 szone_malloc_should_clear + 120
10 libc++abi.dylib                0x138b0 operator new(unsigned long) + 32
11 xxx                           0x51f80c std::__1::deque<long, std::__1::allocator >::__add_back_capacity() +<PHONE_NUMBER> (deque:4305745932)
12 xxx                           0x51f6b4 std::__1::deque<long, std::__1::allocator >::push_back(long const&) + 1162 (deque:1162)
13 xxx                           0x51df84 IGListDiffing(bool, long, long, NSArray<id >*, NSArray<id >, IGListDiffOption, long) + 1572 (vector:1572)
14 xxx                           0x51eb48 IGListDiffPaths + 331 (IGListDiff.mm:331)
15 xxx                           0x216c3c -[ViewModel insertMessages:] + 61 (ViewModel.m:61)
16 xxx                           0x218234 __41-[ViewModel sendMessage:]_block_invoke_2 + 195 (ViewModel.m:195)
17 libdispatch.dylib              0x2460 _dispatch_call_block_and_release + 32
18 libdispatch.dylib              0x3f88 _dispatch_client_callout + 20
19 libdispatch.dylib              0x127f4 _dispatch_main_queue_drain + 928
20 libdispatch.dylib              0x12444 _dispatch_main_queue_callback_4CF + 44
21 CoreFoundation                 0x9a6c8 CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE + 16
22 CoreFoundation                 0x7c02c __CFRunLoopRun + 2036
23 CoreFoundation                 0x80eb0 CFRunLoopRunSpecific + 612
24 GraphicsServices               0x1368 GSEventRunModal + 164
25 UIKitCore                      0x3a1668 -[UIApplication _run] + 888
26 UIKitCore                      0x3a12cc UIApplicationMain + 340
27 xxx                           0x75fc main + 18 (main.m:18)
28 ???                            0x1ef358960 (缺少)
General information

IGListKit version: 4.0.0
iOS version(s):  16.3.1
CocoaPods/Carthage version: 1.11.3
Xcode version: 14.2
Devices/Simulators affected: iPhone 12 Pro Max

crash_info_entry_0
abort() called
crash_info_entry_1
xxx(16295,0x226d749c0) malloc: Incorrect checksum for freed object 0x1429e9000: probably modified after being freed. Corrupt value: 0x482036d01e800d0

Hi @sugite. Thanks for the issue. Sorry to see you're having an issue here.
There's not enough info to really diagnose what's going on here. In the meantime can you please,

Try installing the latest copy of IGListKit from the main branch and try again.
Failing that, can you please show us the IGListDiffable objects you're trying to diff here.

Thanks!

Hi @TimOliver . Thank you for your reply.

Since the project has not been migrated to Swift yet, the current version of IGListDiffKit being used is Objective-C version 4.0.0.
The object that needs to be diffed is XXXBaseModel, defined as follows:

@interface XXXBaseModel : NSObject<IGListDiffable>
@end

@implementation XXXBaseModel
- (nonnull id<NSObject>)diffIdentifier {
    return @(self.message.mid);
}

- (BOOL)isEqualToDiffableObject:(nullable XXXBaseModel<IGListDiffable> *)object {
    if (self != object) {
        return NO;
    }
    return self.message.sendStatus == object.message.sendStatus;
}

@end


Add docs for rethinkdb proxy

We don't have any docs for rethinkdb proxy and it's actually a very useful feature that I've described to a number of people over IRC and had them be delighted. Let's add docs for it.

Now that we have changefeeds, rethinkdb proxy is extremely useful because it lets us deduplicate changefeed traffic between the actual cluster and the machine hosting the clients.  I think we should probably keep it, and should definitely document it in the meantime.  (If we decide not to keep it, we should make sure we have another way of deduplicating changefeed messages before dropping it.)
@chipotle asked for a brief overview of what rethinkdb proxy does.  Basically it adds a node to the cluster that doesn't store any data.  So you can run this node on the same machine as your clients and connect to it over localhost.  This has three main uses:

It can save intracluster network traffic by routing your query straight to the correct machine.
It can do some processing itself, lessening CPU load on machines that store data on disk.
It can deduplicate changefeed messages send to it by other nodes in the cluster.

In addition to the points @mlucy mentioned, a rethinkdb proxy node is also aware of other nodes that might become unavailable so is the best tool we have to keep a stable connection to the cluster when things go bad.
Personally I see the poxy nodes as becoming more and more important as our ability to scale increases.

So: if you have a RethinkDB cluster, you can set up a proxy node on your application server and have the application connect to the proxy rather than to a (non-proxy) machine on the cluster. The proxy will route queries more efficiently, deduplicate changefeed messages and make sure queries don't get sent to unavailable nodes.
If you have more than one application server in this scenario, should each application server run its own proxy, or should there be only one machine running rethinkdb proxy in a cluster?

I talked to @chipotle in person, and my answer is that in a big setup it would be a good pattern to have a rethinkdb proxy process running on each application server. This is especially true the more you use changefeeds.

a good pattern to have a rethinkdb proxy process running on each application server

:+1: that was the intention when we built it.

To update on my earlier comments about raft's impact on this: It seems like we will keep the proxy mode as it is for 2.1.

Really like the new documentation for the proxy mode. Very concise. :+1:

For anyone using docker and rethinkdb, you need to use --bind-all on the proxy to make it accessible from your linked containers.

@larkost @coffeemug  In a microservice system running containers, in my case is kubernetes. Should I have each microservice use its own rethinkdb proxy inside the pod? My concern is that could make hundreds of rethinkdb proxy, could that make the rethinkdb cluster performance worse or not at all?

@ntquyen We haven't really tested anything of that scale. I suspect that there won't be any problems if you stay below 100 proxies or so, but there might be some unexpected slowdowns when getting to a multitude of that.
Also note that proxies are not completely light-weight. While they need less RAM than "proper" RethinkDB servers, and don't need any storage, they will still need a significant amount of RAM for processing queries (depending on which types of queries you're running).

@ntquyen imo this is a great use case for a daemon controller [0]
That will give you a rethinkdb proxy per node rather than per pod. It should have the same performance characteristics but you won't have to worry about scaling up your controller slowing down the db.
[0] https://github.com/kubernetes/kubernetes/blob/master/docs/admin/daemons.md


Leaflet fitBounds not working properly with ajax loaded layer

Hello,
Could you check if this is my bug or bug with leaflet 1.0-rc2?
I'm loading layers with ajax (in loop) and after added each layer to map I'm:

creating "big" array with all added bounds,
executing fitBounds function for current layer (map.fitBounds(layer.getBounds))

And after all ajax files are loaded I call map.fitBounds(bigArray).
Here is stackoverflow question: http://stackoverflow.com/questions/38437523/leaflet-1-0-fitbounds-working-as-expected
Thanks in advance!

Can you set up a minimal JSFiddle test case that reproduces the bug?

here is when fitBounds is fitting map randomly: http://jsfiddle.net/nyhh0g2w/17/
you can check in console.log in what order is map.fitBounds called.
here is screencast how it looks (same effect on two different computers, chromium and firefox):
https://youtu.be/l4FeQ3NjwKw

map.fitBounds is supposed to take a LatLngBounds or the simple array form of that...You are passing it an 8 element array of coordinate pairs.
I'd recommend adding all your grabbed layers to a FeatureGroup then using map.fitBounds(myFeatureGroup.getBounds()) to simplify what you are trying to do.

you mean something like this - http://jsfiddle.net/nyhh0g2w/20/
maybe it's my misunderstanding of deferred object, I have no idea, but the effect is the same.
It is random which fitBounds will be called in the end...

I personally don't use jQuery deferreds, I prefer Bluebird for this type of work, so I'm not sure how much help I can be there.
Do you need to fitBounds after each download? Wouldn't just one fitBounds at the end be enough?

my maps sometimes are big and I want show anything for the user after first initial map, so I first decided to fitBounds two times - at first map load and last map load.
But than I have to have two deferred object, one just for first time load so I fitBound after first ajax is called and second which I already have,
So I decided to fitBounds in each iteration, it look fine at localhost, but in the web it looks as you see it...

Hi,
Not sure exactly what you are trying to do, but it seems to me that Leaflet behaves exactly the way your code requests it to do:

The code sends a few AJAX requests, each returning different markers and polylines, at different places across Americas.
At each AJAX success, the code performs a fitBounds on the received layers only (converted from GeoJSON response)

var newLayer = L.geoJson(geojson);
map.fitBounds(newLayer.getBounds());

Therefore, the map pans to different places across Americas, giving this impression of "random" fitBounds effect.
Finally, your last AJAX request resolves, and your jQuery.when deferred on all requests executes, fitting the map to your entire layers.

map.fitBounds(boundsObjectForEachMap.featureGroup.getBounds());

So for your intermediate steps, why not simply fitting bounds to your updated boundsObjectForEachMap.featureGroup, so that the map shows all that you already received, rather than just what it received last?
That way, it will gradually zoom out to show more content, instead of just the small pieces that belong to the last AJAX request data at "random" place.
Additionally, you will be able to get rid of your last fitBounds in jQuery.when, since the last AJAX success will complete your entire set of data / layers, and its fitBounds will therefore show your entire content already.
Updated JSFiddle: http://jsfiddle.net/nyhh0g2w/22/

@ghybs thanks for help.
Could you try to click run in the fiddle multiple times? Is it always showing 'both Americas' for you?
Because in my web browsers it is not always fitting to the last jQuery.when...

Just in case, notice that you have set your map container height to 800px, so the map may actually extend below your screen (you have to scroll down somehow to see the bottom of the map), leading to the impression that the fitBounds did not work...

but map div has to have height as far as I understand.
if I don't set height, I have 0px map - http://jsfiddle.net/nyhh0g2w/26/

Use CSS with height as percentage of parent's height?
Updated JSFiddle: http://jsfiddle.net/nyhh0g2w/27/

to sum up here.
With big help of @ghybs I made the newest jsfiddle https://jsfiddle.net/nyhh0g2w/28/ .
When calling multiple fitBounds 'too quickly' than the last one has no effect...
Look here: https://youtu.be/Qh4iguoXUFc
and of course look in stackoverflow: http://stackoverflow.com/questions/38437523/leaflet-1-0-fitbounds-not-working-as-expected-with-ajax-loading/38597854?noredirect=1#comment64943145_38597854


HoloLens Commander: Allow specifying dependency files and certificate during app install

This will be paired with Issue #67 and Issue #69


Default AnonAddy instance is open relay :/

Hello,
This is not a bug but a misconfiguration on my setting, however, i don't find many documentation about my issue.
Behaviour
Steps to reproduce this issue

Setup AnonAddy (docker-compose)
Configure DNS & mail security (DKIM etc)
Test to check if the server is open relay

Expected behaviour
SMTP Server should not be open relay.
Actual behaviour
I did some test and my server is open relay (so I can't expose it :p ).
Configuration

Docker version (type docker --version) : Docker version 20.10.5, build 55c4c88 (I do some tests on MacOS)
Docker compose version if applicable (type docker-compose --version) : docker-compose version 1.29.0, build 07737305
Platform (Debian 9, Ubuntu 18.04, ...) : MacOS BigSur 11.5.2 (20G95)
System info (type uname -a) : Darwin redacted.local 20.6.0 Darwin Kernel Version 20.6.0: Wed Jun 23 00:26:31 PDT 2021; root:xnu-7195.141.2~5/RELEASE_X86_64 x86_64
Include all necessary configuration files : docker-compose.yml, .env, ...

docker-compose.yml and .env are based on the template without many change.
Docker info
N/A
Logs
~$ telnet my.domain 25
Trying xx.xx.xx.xx...
Connected to *******.
Escape character is '^]'.
220 my.domain ESMTP
helo .
250 my.domain
MAIL<EMAIL_ADDRESS>250 2.1.0 Ok
RCPT<EMAIL_ADDRESS>250 2.1.5 Ok
data
354 End data with <CR><LF>.<CR><LF>
Hello!
.
250 2.0.0 Ok: queued as D440F1027C4
quit
221 2.0.0 Bye
Connection closed by foreign host.

What are the setting to use AnonAddy without having the server as open relay?
Thank you!

Some details:
My lab seems like that:
Internet -----> Firewall (PAT TCP/25) -----> Host (MacOS) -----> AnnoAddy (Container)

Postfix logs (container AnonAddy) show the connection from the Docker Host (my MacOS with IP <IP_ADDRESS>).
As mynetworks contains the network  <IP_ADDRESS>/12, messages are relayed..
anonaddy    | Sep 16 07:56:00 alias postfix/smtpd[1076]: connect from unknown[<IP_ADDRESS>]
anonaddy    | Sep 16 07:56:10 alias postfix/smtpd[1076]: disconnect from unknown[<IP_ADDRESS>] quit=1 unknown=0/1 commands=1/2
anonaddy    | Sep 16 07:56:41 alias postfix/smtpd[1076]: connect from unknown[<IP_ADDRESS>]
anonaddy    | Sep 16 07:56:41 alias postfix/smtpd[1076]: CEFCE1027C4: client=unknown[<IP_ADDRESS>]
anonaddy    | Sep 16 07:56:42 alias postfix/cleanup[1085]: CEFCE1027C4<EMAIL_ADDRESS>anonaddy    | Sep 16 07:56:42 alias postfix/qmgr[1059]: CEFCE1027C4<EMAIL_ADDRESS>size=829, nrcpt=1 (queue active)
anonaddy    | Sep 16 07:56:42 alias postfix/smtpd[1076]: disconnect from unknown[<IP_ADDRESS>] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
anonaddy    | Sep 16 07:56:49 alias postfix/smtp[1086]: CEFCE1027C4<EMAIL_ADDRESS>relay=mail.protonmail.ch[<IP_ADDRESS>]:25, delay=7.5, delays=0.33/0.01/6.2/0.93, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4H95v44ZRkz3hhcs)
anonaddy    | Sep 16 07:56:49 alias postfix/qmgr[1059]: CEFCE1027C4: removed

I remove (for testing) the network <IP_ADDRESS>/12 in mynetworks (in /etc/postfix/main.cf) and reload postfix (docker-compose exec anonaddy postfix reload ), message are not relayed:
anonaddy    | Sep 16 09:23:30 alias postfix/smtpd[1390]: connect from unknown[<IP_ADDRESS>]
anonaddy    | Sep 16 09:23:30 alias postfix/smtpd[1390]: NOQUEUE: reject: RCPT from unknown[<IP_ADDRESS>]: 450 4.7.1 Client host rejected: cannot find your reverse hostname, [<IP_ADDRESS>]<EMAIL_ADDRESS><EMAIL_ADDRESS>proto=ESMTP helo=<smtptester.[redacted].com>
anonaddy    | Sep 16 09:23:30 alias postfix/smtpd[1390]: disconnect from unknown[<IP_ADDRESS>] ehlo=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=4/5

So... How can I retrieve the real IP address of the sender instead the IP of the docker host?

I exported my container on a Linux machine (Ubuntu) and the container is NOT open relay.
Conclusion: there something between Docker on MacOS witch works differently than Docker on Linux... (and I will not investigated more!). I will do my PoC on Linux.
If this can help someone to NOT loose his time :)

It's actually an issue, which should be documented briefly. If someone can point me to the right place, I'm happy to create a PR.
I seem to have run into the same issue as you did. The main issue is that the mynetworks is set to all private IP ranges and if Docker or Kubernetes isn't forwarding the Clients real IP everyone can relay as they please.
For example, you'll see the following in your logs:
postfix/smtpd[1415]: connect from unknown[<IP_ADDRESS>]
Which will pass through and let you relay everything.
On Kubernetes, you'll need to set up the Service with externalTrafficPolicy: Local in order to get the correct IP.