Update gRPC library to 1.23.0

Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
40af0183c11f4ce845da9c3185877d2015a56ba0
link
/test istio-unit-tests

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
8ca0a8317838fa894bd4ab338639445ec1bbb737
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
8ca0a8317838fa894bd4ab338639445ec1bbb737
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
8ca0a8317838fa894bd4ab338639445ec1bbb737
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR 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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
8ca0a8317838fa894bd4ab338639445ec1bbb737
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
8ca0a8317838fa894bd4ab338639445ec1bbb737
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
8ca0a8317838fa894bd4ab338639445ec1bbb737
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
8ca0a8317838fa894bd4ab338639445ec1bbb737
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
8ca0a8317838fa894bd4ab338639445ec1bbb737
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
fb70a7ccedbbcd459293776d3e9b83b016d3358b
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR 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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
fb70a7ccedbbcd459293776d3e9b83b016d3358b
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
fb70a7ccedbbcd459293776d3e9b83b016d3358b
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
fb70a7ccedbbcd459293776d3e9b83b016d3358b
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
fb70a7ccedbbcd459293776d3e9b83b016d3358b
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR 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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
fb70a7ccedbbcd459293776d3e9b83b016d3358b
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
9b6bc3b9b0bbc2b04f48cbf5483465859094f10e
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
9b6bc3b9b0bbc2b04f48cbf5483465859094f10e
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
9b6bc3b9b0bbc2b04f48cbf5483465859094f10e
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
9b6bc3b9b0bbc2b04f48cbf5483465859094f10e
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
591b64117e8929085de967987c87b6cd5ae22feb
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
591b64117e8929085de967987c87b6cd5ae22feb
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
591b64117e8929085de967987c87b6cd5ae22feb
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
591b64117e8929085de967987c87b6cd5ae22feb
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
591b64117e8929085de967987c87b6cd5ae22feb
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-unit-tests.sh
4dcd3e4f46ee366f85ce1b3e67e051b142cafd77
link
/test istio-unit-tests

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
591b64117e8929085de967987c87b6cd5ae22feb
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
591b64117e8929085de967987c87b6cd5ae22feb
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-unit-tests.sh
e74021e27cefe6587c511f5b7be6e971d995c787
link
/test istio-unit-tests

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
591b64117e8929085de967987c87b6cd5ae22feb
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
591b64117e8929085de967987c87b6cd5ae22feb
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-unit-tests.sh
fa37b268ff0855894021a58a990c4255f29d84ad
link
/test istio-unit-tests

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
591b64117e8929085de967987c87b6cd5ae22feb
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
fa37b268ff0855894021a58a990c4255f29d84ad
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
fa37b268ff0855894021a58a990c4255f29d84ad
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
fa37b268ff0855894021a58a990c4255f29d84ad
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
fa37b268ff0855894021a58a990c4255f29d84ad
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
fa37b268ff0855894021a58a990c4255f29d84ad
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
fa37b268ff0855894021a58a990c4255f29d84ad
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
fa37b268ff0855894021a58a990c4255f29d84ad
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
314b4a3194f394624eb3af935497d23988a79541
link
/test istio-unit-tests

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
fa37b268ff0855894021a58a990c4255f29d84ad
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
314b4a3194f394624eb3af935497d23988a79541
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
314b4a3194f394624eb3af935497d23988a79541
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
314b4a3194f394624eb3af935497d23988a79541
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
314b4a3194f394624eb3af935497d23988a79541
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
314b4a3194f394624eb3af935497d23988a79541
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
314b4a3194f394624eb3af935497d23988a79541
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
2df44adb34ce9b23e1262a3df4ff56535b3ea201
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
2df44adb34ce9b23e1262a3df4ff56535b3ea201
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
2df44adb34ce9b23e1262a3df4ff56535b3ea201
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
2df44adb34ce9b23e1262a3df4ff56535b3ea201
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
2df44adb34ce9b23e1262a3df4ff56535b3ea201
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-simpleTests

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
2df44adb34ce9b23e1262a3df4ff56535b3ea201
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
2df44adb34ce9b23e1262a3df4ff56535b3ea201
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-simpleTests

prow/istio-unit-tests.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test istio-unit-tests

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
2df44adb34ce9b23e1262a3df4ff56535b3ea201
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
2df44adb34ce9b23e1262a3df4ff56535b3ea201
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-simpleTests

prow/istio-unit-tests.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test istio-unit-tests

prow/e2e-bookInfoTests-v1alpha3.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
2df44adb34ce9b23e1262a3df4ff56535b3ea201
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
2df44adb34ce9b23e1262a3df4ff56535b3ea201
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-simpleTests

prow/istio-unit-tests.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test istio-unit-tests

prow/e2e-bookInfoTests-v1alpha3.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
2df44adb34ce9b23e1262a3df4ff56535b3ea201
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
2df44adb34ce9b23e1262a3df4ff56535b3ea201
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-simpleTests

prow/istio-unit-tests.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test istio-unit-tests

prow/e2e-bookInfoTests-v1alpha3.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test istio_auth_sds_e2e

prow/e2e-dashboard.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-dashboard

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
2df44adb34ce9b23e1262a3df4ff56535b3ea201
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-simpleTests

prow/istio-unit-tests.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test istio-unit-tests

prow/e2e-bookInfoTests-v1alpha3.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test istio_auth_sds_e2e

prow/e2e-dashboard.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-dashboard

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
2df44adb34ce9b23e1262a3df4ff56535b3ea201
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-simpleTests

prow/istio-unit-tests.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test istio-unit-tests

prow/e2e-bookInfoTests-v1alpha3.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test istio_auth_sds_e2e

prow/e2e-dashboard.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-dashboard

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-mixer-no_auth

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
2df44adb34ce9b23e1262a3df4ff56535b3ea201
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-simpleTests

prow/istio-unit-tests.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test istio-unit-tests

prow/e2e-bookInfoTests-v1alpha3.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test istio_auth_sds_e2e

prow/e2e-dashboard.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-dashboard

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-mixer-no_auth

prow/e2e-bookInfoTests-trustdomain.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-bookInfoTests-trustdomain

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-simpleTests

prow/istio-unit-tests.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test istio-unit-tests

prow/e2e-bookInfoTests-v1alpha3.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test istio_auth_sds_e2e

prow/e2e-dashboard.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-dashboard

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-mixer-no_auth

prow/e2e-bookInfoTests-trustdomain.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-bookInfoTests-trustdomain

prow/istio-pilot-multicluster-e2e.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR 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

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

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test istio_auth_sds_e2e

prow/e2e-bookInfoTests-trustdomain.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-bookInfoTests-trustdomain

prow/istio-pilot-multicluster-e2e.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
15bbeda06be541ea274e750975db271cab525d3f
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
042672550df6c880baec4060c641d6a40b6cda08
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
15bbeda06be541ea274e750975db271cab525d3f
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
15bbeda06be541ea274e750975db271cab525d3f
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
15bbeda06be541ea274e750975db271cab525d3f
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
15bbeda06be541ea274e750975db271cab525d3f
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
15bbeda06be541ea274e750975db271cab525d3f
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
15bbeda06be541ea274e750975db271cab525d3f
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
15bbeda06be541ea274e750975db271cab525d3f
link
/test istio-pilot-multicluster-e2e

prow/e2e_pilotv2_auth_sds.sh
65eb22e365e8c76cfd12697ea8ff102751b61061
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
15bbeda06be541ea274e750975db271cab525d3f
link
/test istio-pilot-multicluster-e2e

prow/e2e_pilotv2_auth_sds.sh
65eb22e365e8c76cfd12697ea8ff102751b61061
link
/test istio_auth_sds_e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
65eb22e365e8c76cfd12697ea8ff102751b61061
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
15bbeda06be541ea274e750975db271cab525d3f
link
/test istio-pilot-multicluster-e2e

prow/e2e_pilotv2_auth_sds.sh
65eb22e365e8c76cfd12697ea8ff102751b61061
link
/test istio_auth_sds_e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
65eb22e365e8c76cfd12697ea8ff102751b61061
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-unit-tests.sh
65eb22e365e8c76cfd12697ea8ff102751b61061
link
/test istio-unit-tests

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/e2e_pilotv2_auth_sds.sh
65eb22e365e8c76cfd12697ea8ff102751b61061
link
/test istio_auth_sds_e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
65eb22e365e8c76cfd12697ea8ff102751b61061
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-unit-tests.sh
65eb22e365e8c76cfd12697ea8ff102751b61061
link
/test istio-unit-tests

prow/istio-pilot-multicluster-e2e.sh
65eb22e365e8c76cfd12697ea8ff102751b61061
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/e2e_pilotv2_auth_sds.sh
65eb22e365e8c76cfd12697ea8ff102751b61061
link
/test istio_auth_sds_e2e

prow/istio-unit-tests.sh
65eb22e365e8c76cfd12697ea8ff102751b61061
link
/test istio-unit-tests

prow/istio-pilot-multicluster-e2e.sh
65eb22e365e8c76cfd12697ea8ff102751b61061
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
dc1eacd82bf4b90a07a81af580ac4e55112c6eaa
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
65eb22e365e8c76cfd12697ea8ff102751b61061
link
/test istio-unit-tests

prow/istio-pilot-multicluster-e2e.sh
65eb22e365e8c76cfd12697ea8ff102751b61061
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
dc1eacd82bf4b90a07a81af580ac4e55112c6eaa
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
dc1eacd82bf4b90a07a81af580ac4e55112c6eaa
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
dc1eacd82bf4b90a07a81af580ac4e55112c6eaa
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
dc1eacd82bf4b90a07a81af580ac4e55112c6eaa
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
dc1eacd82bf4b90a07a81af580ac4e55112c6eaa
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/e2e_pilotv2_auth_sds.sh
dc1eacd82bf4b90a07a81af580ac4e55112c6eaa
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
dc1eacd82bf4b90a07a81af580ac4e55112c6eaa
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
a7f0ddb6c716377361812502eeca1ced2e4252c2
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
dc1eacd82bf4b90a07a81af580ac4e55112c6eaa
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
a7f0ddb6c716377361812502eeca1ced2e4252c2
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
a7f0ddb6c716377361812502eeca1ced2e4252c2
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
a7f0ddb6c716377361812502eeca1ced2e4252c2
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
a7f0ddb6c716377361812502eeca1ced2e4252c2
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
a7f0ddb6c716377361812502eeca1ced2e4252c2
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/e2e_pilotv2_auth_sds.sh
a7f0ddb6c716377361812502eeca1ced2e4252c2
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
a7f0ddb6c716377361812502eeca1ced2e4252c2
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
a7f0ddb6c716377361812502eeca1ced2e4252c2
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/e2e_pilotv2_auth_sds.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
1313fb318c216814da92169e97f7bb7f4499b817
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
1313fb318c216814da92169e97f7bb7f4499b817
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
1313fb318c216814da92169e97f7bb7f4499b817
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
1313fb318c216814da92169e97f7bb7f4499b817
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
1313fb318c216814da92169e97f7bb7f4499b817
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio-unit-tests

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
1313fb318c216814da92169e97f7bb7f4499b817
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
1313fb318c216814da92169e97f7bb7f4499b817
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio-unit-tests

prow/e2e_pilotv2_auth_sds.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
f106123a61460a2ef2cc2b888a76101ad577c12e
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio-unit-tests

prow/istio-pilot-multicluster-e2e.sh
ae3dafec1e7ce4ef5e56505b5f50c31276ac0002
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
f106123a61460a2ef2cc2b888a76101ad577c12e
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
f106123a61460a2ef2cc2b888a76101ad577c12e
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
f106123a61460a2ef2cc2b888a76101ad577c12e
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
f106123a61460a2ef2cc2b888a76101ad577c12e
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
f106123a61460a2ef2cc2b888a76101ad577c12e
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/e2e_pilotv2_auth_sds.sh
f106123a61460a2ef2cc2b888a76101ad577c12e
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
f106123a61460a2ef2cc2b888a76101ad577c12e
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
47e9ec73d50991ccf5a664dccb212dad41945e7c
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
47e9ec73d50991ccf5a664dccb212dad41945e7c
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
47e9ec73d50991ccf5a664dccb212dad41945e7c
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
47e9ec73d50991ccf5a664dccb212dad41945e7c
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
859f2f54490f13542ab568ca99e4fb05fe767f89
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
859f2f54490f13542ab568ca99e4fb05fe767f89
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
859f2f54490f13542ab568ca99e4fb05fe767f89
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR 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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
859f2f54490f13542ab568ca99e4fb05fe767f89
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
859f2f54490f13542ab568ca99e4fb05fe767f89
link
/test istio-pilot-multicluster-e2e

prow/e2e-bookInfoTests-trustdomain.sh
d8284e8974d8729a7063a0bfc380445a232821b8
link
/test e2e-bookInfoTests-trustdomain

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

/test e2e-bookInfoTests-trustdomain

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
859f2f54490f13542ab568ca99e4fb05fe767f89
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
859f2f54490f13542ab568ca99e4fb05fe767f89
link
/test istio-pilot-multicluster-e2e

prow/e2e-bookInfoTests-trustdomain.sh
d8284e8974d8729a7063a0bfc380445a232821b8
link
/test e2e-bookInfoTests-trustdomain

prow/istio-unit-tests.sh
d8284e8974d8729a7063a0bfc380445a232821b8
link
/test istio-unit-tests

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

/test istio-unit-tests

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

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-trustdomain.sh
d8284e8974d8729a7063a0bfc380445a232821b8
link
/test e2e-bookInfoTests-trustdomain

prow/istio-unit-tests.sh
d8284e8974d8729a7063a0bfc380445a232821b8
link
/test istio-unit-tests

prow/istio-pilot-multicluster-e2e.sh
d8284e8974d8729a7063a0bfc380445a232821b8
link
/test istio-pilot-multicluster-e2e

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

/test istio-pilot-multicluster-e2e

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
d8284e8974d8729a7063a0bfc380445a232821b8
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR 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.


github webhook is failing, not enough information to debug

I'm a member of the GA4GH team. We are trying to setup RTD to build our docs at https://ga4gh-schemas.readthedocs.org/en/latest/.
I first used my personal github repo, reece/schemas, to set this up. That worked fine.
I then attempted to transition the RTD project to watch the official repo, ga4gh/schemas. When I do that, I can force build the project (under the RTD build tab) and I can trigger it with curl, but the new webhook on the ga4gh/schemas repo does NOT trigger a build and the github "test service" button does not work.
I've tried the migration twice with extra care regarding spelling. Both attempts failed.
Do you you have any tips for debugging webhook failures (other than curl)?

Maybe this will help debugging at RTD:
At apx Mon Nov 23 06:27:00 UTC 2015, I triggered a build using the github "test service button" with the project configured against reece/schemas. That worked fine.
I reconfigured the project github URL for ga4gh/schemas and added a webhook by 06:29, and attempted several tests. All failed.
My hope in providing this is for you to be able to extract github webhook attempts for this time period.

@reece This sounds like the lookup on the Github webhook is failing. Can you check that the repo url set up in the RTD project matches the Github https url exactly -- that is, matches case/etc as well.

Hi Anthony-
I think I figured out what happened.
The main problem was that we had a mistaken branch, "f242434e", on master.
That meant that the github service test created a payload with that branch
name. We weren't building docs on that branch, of course. The nice folks at
github fetched this http reply from RTD:
"(URL Build) Not Building: github.com/ga4gh/schemas [f242434e]"
They also said that reporting webhook replies was on the wishlist.
I'll close the ticket.  Thanks for your help.
-Reece


Atosplit+3dfx

Greetings.
I do not know English well, so I use google.translate.
The split program does not work well with the 3dfx mode. The game after alt + tab "freezes" and after that the split does not work.
Everything was fine in version 0.31

Hi, unfortunately 0.3.1 to current version are lots of changes in code :( And i cannot launch D2 in 3dfx mode, so unable to reproduce this problem. I put the help wanted tag. Maybe someone else can fix this.


[MINOR] Fix typos

What changes were proposed in this pull request?
Fix some typos.
Why are the changes needed?
Ditto.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Not needed.

cc @pan3793


"Mailto" links not detected correctly using getUrls()

Please see example below.
Code:
(new UrlHighlight)->getUrls('<a<EMAIL_ADDRESS>
Actual output:
[
<EMAIL_ADDRESS>]

Expected output:
[
<EMAIL_ADDRESS>]

// Or

[
<EMAIL_ADDRESS>]

// Or

[
   // An empty array
]

Hi @bastones 👋,
Good catch, this is definitely not expected (correct) behaviour. Thank you for reporting the valid issue.
I had a quick look, and it seems like the regex in Matcher class is not properly matching the userinfo for this case.
Unfortunately I'm a bit short on time at the moment. So I can't tackle it directly. But I believe it can be fixed.

Adding a few notes and references for future myself.
userinfo = *( unreserved / pct-encoded / sub-delims / ":" )

unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~"
pct-encoded (percent encoded) = "%" followed by the hexadecimal representation of the ASCII value
sub-delims = "!" / "$" / "&" / "'" / "(" / ")" / "*" / "+" / "," / ";" / "="

References:

RFC 3986 Uniform Resource Identifier (URI): Generic Syntax
RFC 6068  The 'mailto' URI Scheme

Issue is resolved in #49, and it's available from v3.1.0.


super-select: catch keydown and open if not multiple

For super_select fields that don't allow multiple selections, this introduces these improvements:

When clicking on the field, the focus goes onto the search text input field
When closed, but the field has focus, if you start typing, the field opens and lets you type directly into the search text input field.

Closes https://github.com/bullet-train-co/bullet_train-fields/issues/35
Requires https://github.com/bullet-train-co/bullet_train-fields/pull/33 (a commit from that PR's branch is included in this branch)
Co-dependent PRs:

https://github.com/bullet-train-co/bullet_train-fields/pull/36
https://github.com/bullet-train-co/bullet_train/pull/435

Replaced with https://github.com/bullet-train-co/bullet_train-core/pull/63


Still having issue #230 (Cant save edited Flowchart due to app.diagram.net not working anymore)

I'm still having the same issue as @bijwaard , in 2023.
I can open the drawing and its showing the mentioned warning:

But if i make any changes to the Flowchart, the whole thing disappeared after closing the editor:

How can I edit my drawing / how can we move to embed.diagrams.net ?
Changing the url in the "Source Content" does not work:

I really like the Flowchart extension and would be great to hear about a fix for my issue.
Originally posted by @MxPie200 in https://github.com/algenty/grafana-flowcharting/issues/230#issuecomment-1519039570

Hi @MxPie200,
Have you tried to specify editor? This works for me!

Kind regards,
Dennis

@bijwaard
Yes, I've tried it.
It opens the editor correctly, but after clicking on "Save" the Flowchart disappears as shown in my second screenshot

Aha, just tried editing my drawing, set it to light theme, and get the following back:

Looks like it reverts to the default diagram for some reason.

Hm ok, so it looks like it's a new bug with currently no solution for?

Looks like a new bug indeed. What version of the plugin are you using? I'm using 1.0.0d
$ sudo grafana-cli plugins ls
installed plugins:
ae3e-plotly-panel @ 0.5.0
agenty-flowcharting-panel @ 1.0.0d
alexandra-trackmap-panel @ 2.3.0
marcuscalidus-svg-panel @ 0.3.4
natel-plotly-panel @ 0.0.7
simpod-json-datasource @ 0.3.0

@bijwaard
I have Version 0.9.1. , but grafana doesn't show updates, can i update via commandline?

Yes, you can update via the command line. You move the old plugin away from /var/lib/grafana/plugins and unzip the latest the beta release in the /var/lib/grafana/plugins folder, then restart grafana. Depending on which version you had previously, you may need to rename the folder to the old name.

Which files do i have to copy from github?

just tried on another grafana instance with plugin version 1.0.0b on grafana 9.1.5, and here the editor keeps working, but after saving the result stays blank in the panel, but further editing still works.

Latest snapshot is here. Current and older snapshots are here:

you can rename your ticket to say that embed.diagrams.net is not working....

hm ok, i've had same as you that changes lead to reset to default flowchart..

Hopefully Arnaud just has to update/refresh the embed.diagrams.net library in the plugin....

looks like the same problem reported in #395


After installing the plugin computed custom field,got internal error if we would like to create a new custom field.

Hi all,
I got a problem as after installing the plugin computed custom field,got internal error if we would like to create a new custom field.Thanks in advanced.
Environment:
1.Platform:Windows server 2008 R2.
2.Redmine version:v3.3.0
3.Production log:
Started GET "/redmine/custom_fields/new?utf8=%E2%9C%93&type=IssueCustomField" for <IP_ADDRESS> at 2017-07-24 23:36:04 -0700
Processing by CustomFieldsController#new as HTML
Parameters: {"utf8"=>"✓", "type"=>"IssueCustomField"}
Current user: user (id=1)
Rendered custom_fields/formats/_regexp.html.erb (0.0ms)
Rendered custom_fields/formats/_string.html.erb (15.6ms)
Rendered plugins/computed_custom_field/app/views/hooks/_view_custom_fields_form_upper_box.html.erb (0.0ms)
Rendered custom_fields/_form.html.erb (46.8ms)
Rendered custom_fields/new.html.erb within layouts/admin (62.4ms)
Completed 500 Internal Server Error in 109ms (ActiveRecord: 46.8ms)
ActionView::Template::Error (undefined method is_computed' for #<IssueCustomField:0x7a935b0>):     1: <% if custom_field.new_record? || custom_field.is_computed? %>     2:
<%= form.check_box :is_computed,     3:                         data: { enables: '#custom_field_formula, #available_cfs' },     4:                         disabled: !custom_field.new_record? %>
     5:
<%= form.text_area :formula, rows: 7 %>
   lib/redmine/views/labelled_form_builder.rb:34:in check_box'
plugins/computed_custom_field/app/views/hooks/_view_custom_fields_form_upper_box.html.erb:2:in _plugins_computed_custom_field_app_views_hooks__view_custom_fields_form_upper_box_html_erb__690406413_62986860'   lib/redmine/hook/view_listener.rb:59:in block (2 levels) in render_on'
lib/redmine/hook/view_listener.rb:57:in map'   lib/redmine/hook/view_listener.rb:57:in block in render_on'
lib/redmine/hook.rb:61:in block (2 levels) in call_hook'   lib/redmine/hook.rb:61:in each'
lib/redmine/hook.rb:61:in block in call_hook'   lib/redmine/hook.rb:58:in tap'
lib/redmine/hook.rb:58:in call_hook'   lib/redmine/hook.rb:96:in call_hook'
app/views/custom_fields/_form.html.erb:20:in _app_views_custom_fields__form_html_erb___289715540_63878472'   app/views/custom_fields/new.html.erb:4:in block in _app_views_custom_fields_new_html_erb___490847271_64243584'
app/helpers/application_helper.rb:1051:in labelled_form_for'   app/views/custom_fields/new.html.erb:3:in _app_views_custom_fields_new_html_erb___490847271_64243584'
lib/redmine/sudo_mode.rb:63:in `sudo_mode'

You should run migrations https://github.com/annikoff/redmine_plugin_computed_custom_field#installation

Hi annikoff,
I have tried to do plugins migration but got failed,please refer to fail log as attached picture.
Need your kindly support to check this issue.

You should run migrations from your Redmine folder.

Hi annikoff,
It's embarrassing that I just tried the migration as you mentioned but got failed.Still need your help.

I never tried to install Redmine (or any RoR app) on Windows. I couldn't help you. Try to find an answer in StackOverflow for example.

If you found a solution please share it.

Hi annioff,
I tried to re-install Redmine system on ubuntu v16.04,but got another fail as blow,need your kindly support to commend.Thanks in advanced.

Hi. There is something wrong with access permissions in your Redmine directory. You'd better install Redmine in your home directory. Or you could try chmod -R 0777 /usr/share/redmine/

You could find help here https://www.redmine.org/projects/redmine/boards/2

Or here https://stackoverflow.com/questions/tagged/redmine

It works,thanks for your kindly support.


GPU usage decreasing with epochs

I'm having a similar issue to #373 with gradual slowing down while training.
The model works fine but gradually with each epoch GPU utilization is decreasing, and the time needed to complete it increases.

GPU memory usage is also slowly decreasing at the same rate, so I don't think there's a memory leak, and i/o usage is roughly constant at 1200 K/s, well below the sustained speed my HD will support. CPU usage is 20-40%, total CPU memory is <30%, and GPU usage, power and temperature are all in regime where there should be no throttling, so I don't think it's a hardware issue.
Stopping the run, letting things cool down, and restarting with loaded weights doesn't revert speed, and continues with the same slower speed.
I don't have these issues if I replace lightning with a basic training loop.
Has there been any other indication as to what might be causing this?

On closer look it seems I/O does increase as epochs roll on, trying to figure out what is writing to disk so much since aside from default logging my model doesn't write anything, and epochs are long so weights shouldn't be an issue either.

maybe the tensorboard logger is doing that? it’s the only thing that would write

Thanks, the writes aren't to the local folder during an epoch, but it's running within an nvidia-docker, so there's some filesystem writes but it's a bit obscured where exactly.

The I/O issue seemed to be an issue between tqdm and screen, running the model outside of screen eliminates the high IO load, back to normal < 1M/s.
The gradual slowing with epochs remains, so I think there's another issue, I'll try to test more to narrow it down, but if you have any suggestions, I'm happy to follow up if I can.

got it. you can turn off thr prog bar in the trainer as an arg

Avoiding screen seems to solve the I/O issue, but to be safe I restarted with turned off progress bar, there is now almost zero writing to disk, yet GPU usage drops to 30% during epochs (starts at 70%!), though interestingly during validation step usage jumps back up to 60%, so it must be something related to back-propogation (since I evaluate the same loss during validation).
Any other ideas for what I can test? I'm testing lightning for us to use it, other than this issue everything else works great, would like to resolve it so we can migrate.

I have also experienced the problem of training slowing per epoch. I found a few causes to be aware of ...
Pytorch tensors will accumulate history so you have to be careful to NOT create a tensor outside of training/val/test loops that accumulate history, or to append to evergrowing lists unnecessarily. See this for discussion: https://discuss.pytorch.org/t/training-gets-slow-down-by-each-batch-slowly/4460
This was not my problem, unfortunately.
In the above discussion, the recommendation is also made to periodically make this call:
torch.cuda.empty_cache()
I put this in on_epoch_start() - and almost all of my problems disappeared.
However, I still have an important amount of this when using torch.optim.lr_scheduler.ReduceLROnPlateau(). Each time the learning rate is reduced the epoch time goes up by about 2 seconds in my case. The increase starts following the first time lr is reduced, persists, and increases again each time the lr is reduced.
I have not tried any other lr schedulers, and am just starting to track down if there is something in ReduceLROnPlateau() or lightning. If I learn any more, I will post here.

empty cache will make your code really slow... we make sure to release all tensors, so look where you store any tensors to make sure you do too

Got it. Have removed - def a few seconds quicker per epoch. And do not see the slowdown EXCEPT with lr scheduler as above. I looked at the scheduler code and nothing jumps out. All tensors are properly managed. thx

Thanks for the info, I'll also try to see if I have any tensors stored outside that loop that are getting appended to and see if that resolves this issue

The pytorch optimizer documentation says that optimizers should be constructed after moving the model to gpu. Inspection of dp_mixin.py shows them being constructed before, however. Could this be the problem?

I have also done a similar exercise and the code does not slow down with epochs when using it with my own training loop. Hope this can be further investigated and resolved

hi @williamFalcon , I'm experiencing a similar GPU utilization issue, dropping from 20% to 10% in ~20k steps. Is there any recommended way to set up performance profiling in pytorch-lighting?

After setting logger=False, the issue has been mitigated. Previously the save_dir of TestTubeLogger was set to a path in a shared folder, hence the high-frequency logging file I/O becomes the bottleneck.

how's this going?
dp is very slow btw compared with ddp

I haven't seen is issue in .60 or master.
Sent from mobile device - sorry for typos and brevity.
This entire message is confidential. If it isn't intended for you, you may not use it - so please throw it away and forget about it.
On Mar 6, 2020, at 4:28 PM, William Falcon<EMAIL_ADDRESS>wrote:

how's this going?
dp is very slow btw compared with ddp
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/PyTorchLightning/pytorch-lightning/issues/581?email_source=notifications&email_token=AA6YDOT2OOPZDEWFVEQIPU3RGGII5A5CNFSM4JVAGJRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEODISCA#issuecomment-596019464, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AA6YDOSDVI25754HEY5AGZDRGGII5ANCNFSM4JVAGJRA.

Any update here? feel free t reopen if needed... :robot:

@sneiman  @williamFalcon  Did you find any solutions for this issue? I tried all those things you mentioned above but GPU utilization gradually drop down every iterations.

I'm having the same problem, which slowly drives me crazy as I can't find the cause.
The complexity of my model and training setup makes investigating the problem not easy, but here a list what I tried to so far without success:

Replacing the actual data module with a toy one to exclude I/O issues
Setting num_workers in the dataloader to 0 (no subprocesses)
Deactivating model checkpointing
Deactivating the W&B logger
Completely resetting the env and updating all packages

@YonyBresler @sneiman @huntzhan @congvmit, were you able to resolve the issue in the end and if so, what was the cause? Could you maybe provide the different components (loggers, callbacks, lr schedulers, etc.) that you used within your training setup?


Incorrect Given/When/Then behavior (according to Gherkin Reference)

I believe, according to the behavior I am seeing in some of my tests, and in the source code, that step definitions are implemented in a way that is different than the Gherkin definition.
https://docs.cucumber.io/gherkin/reference/#steps
According to the definition the key word (Given, When, or Then) should not be taken into account when initially loading a step definition. However, you should not be allowed to use Given and Then on the same step definition within the same scenario.
I have the case where I've defined a When step definition using the When Attribute, but I am invoking that step definition underneath a Give (using And however). When running with Xunit, I am told that I am missing a step definition.
My setup looks something like the following, for clarity:
Step definition
let [<When>] ``I have defined a step definition`` () = ()

Feature: Test Feature

  Scenario: All initial keywords are fair game
    Given I am writing a test
      And I have defined a step definition
    When I call it with a different keyword initially
    Then the step definition should succeed

Please let me know if this is not intended functionality, or if it is functioning as intended. This was just unexpected behavior compared to my previous BDD experience.

I would call this intended functionality.
TickSpec isn't the only BDD framework which differentiates the step types, e.g. I think SpecFlow does the same. However, SpecFlow has both [<When>], [<Then>], [<Given>] attributes and it also has [<StepDefinition>] attribute which would be closer to what Cucumber does but I didn't see that used much.
We could potentially have such attribute but you can do the same today by writing:
let [<Given; When; Then>] ``I have defined a step definition`` () = ()

Semantically the And and But keywords can be seen just as a replacement for one of Given, When, and Then keywords based on context.

Ah, I did not realize I could add Given, When, and Then to the same step definition. That allows me to accomplish what I'm looking for I believe. I've always treated all the keywords as the exact same thing in my mind. Thank you for the help :)


Reveal modal pop z-index incorrect on Safari on iOS 8 using Foundation 6.0.4

Reveal popups are appearing incorrectly in Safari on iOS8, there appears to be a z-index issue and the modal is appearing behind the overlay. This is Foundation 6.0.4

I noticed that while using reveals in tabs.

All fixed up in 6.0.6
Thanks for all the Issues on this and being so thorough, man!


Motions weights clarification

Hi @xbpeng,
I wish to train the agent with custom motion capture animations, but I wish to understand better how to tune the motion dataset weights. I mean the following weights (from 'humanoid3d_clips_walk_punch.txt'):
{
	"Motions":
	[
		{"Weight": 3, "File": "data/motions/sie/sie_humanoid3d_punch_forward00.txt"},
		{"Weight": 3, "File": "data/motions/sie/sie_humanoid3d_punch_forward01.txt"},
		{"Weight": 3, "File": "data/motions/sie/sie_humanoid3d_punch_forward02.txt"},
		{"Weight": 3, "File": "data/motions/sie/sie_humanoid3d_punch_left00.txt"},

		{"Weight": 2, "File": "data/motions/amass/humanoid3d_ready_to_walk_mirror.txt"},
		{"Weight": 2, "File": "data/motions/amass/humanoid3d_walk_to_ready_mirror.txt"},

		{"Weight": 1, "File": "data/motions/humanoid3d_walk.txt"},
		{"Weight": 1, "File": "data/motions/long/humanoid3d_long_walk0.txt"},
		{"Weight": 1, "File": "data/motions/long/humanoid3d_long_walk1.txt"},
		{"Weight": 1, "File": "data/motions/long/humanoid3d_long_walk2.txt"},
		{"Weight": 1, "File": "data/motions/long/humanoid3d_long_walk3.txt"},
		{"Weight": 1, "File": "data/motions/long/humanoid3d_long_walk0_mirror.txt"},
		{"Weight": 1, "File": "data/motions/long/humanoid3d_long_walk1_mirror.txt"},
		{"Weight": 1, "File": "data/motions/long/humanoid3d_long_walk2_mirror.txt"},
		{"Weight": 1, "File": "data/motions/long/humanoid3d_long_walk3_mirror.txt"}
	]
}

The weights must be assigned based on "how difficult" the movement is (i.e.: the more difficult a movement is to learn, the greater the weight needed) or they only affect the selection of the movement (i.e.: greater weight => greater probability that the movement will be used during test)? Or something else?
In any case, can you give me some guideline on how to choose such weights?
In my case, I have the following movements:
{
	"Motions":
	[
		{"Weight": 2, "File": "data/motions/AGPX/JabL.txt"},
		{"Weight": 2, "File": "data/motions/AGPX/JabR.txt"},

		{"Weight": 1, "File": "data/motions/AGPX/TurnL90.txt"},
		{"Weight": 1, "File": "data/motions/AGPX/TurnR90.txt"},
		{"Weight": 1, "File": "data/motions/AGPX/TurnL180.txt"},
		{"Weight": 1, "File": "data/motions/AGPX/TurnR180.txt"},

		{"Weight": 1, "File": "data/motions/AGPX/WalkFwd.txt"}
	]
}

I've seen that the "TurnL/R" movements are more difficult to learn than the others. With the weights above, the agent finds awkward strategies to make a turn, using Jab or even a backward walk (like a moonwalk!) instead of simply turn and going towards the goal like it does in your example (I'm using the SceneStrikeAMP as scene). The example you provided for this scene works well, but with my MOCAP files I can't get a decent result and I believe the weights can be one of the problems.
Another difference is that you also have a long walk animation, where the actor walks continuously (with turns), instead in mine I've separate files that model the turn (note that all the animations listed above start and end in the same pose). I believe a long walk gives better results, but unfortunately I'm using already existing MOCAP files and I couldn't find a long walk animation that fit my purposes (and building one through motion blending is quite a nightmare), so I can only rely on these separate moves.
I also seen that setting the 'sync_char_root_rot' flag to true is useful in my case (although I'm not 100% sure what it does... maybe when a looped animation ends, the kinematic actor restarts from the current rigid body actor orientation?), probably because the turning animations ends in a different orientation (however in your example this flag is set to false).
So many questions... but we have soo many parameters and achieving a decent result is amazingly difficult (especially since each attempt takes so long to evaluate). Maybe it would be useful to add a functionality to the software that help visualize the impact of these flags/parameters on training.
Thanks in advance,
AGPX

Ok, but when 2 actions can be considered different/same? For example, in my case, which of the following groups are more correct in your opinion?
Case 1:
group 1) TurnL90, TurnL180, TurnR90, TurnR180, WalkFwd
group 2) JabL, JabR

Case 2:
group 1) TurnL90, TurnL180, TurnR90, TurnR180
group 2) WalkFwd
group 3) JabL, JabR

Case 3:
group 1) TurnL90, TurnL180
group 2) TurnR90, TurnR180
group 3) WalkFwd
group 4) JabL, JabR

Case 4:
group 1) TurnL90, TurnR90
group 2) TurnL180, TurnR180
group 3) WalkFwd
group 4) JabL, JabR

Another question: With the current shape / size of the network, how many actions can I expect the network to learn? I mean, by increasing the number of actions, will it be better to "enhance" the network? If yes, looking at the following code (in build_net):
layers = [1024, 512]
gate_common_layers = [128]
gate_layers = [64]

in your opinion, is better to increase the number of layers (e.g. layers = [1024, 1024, 512]), the size (e.g. layers = [2048, 1024]), or both?
Thanks.

Hi, thanks. I discovered that the turning animations can't be learned by DeepMimic (tested by training a single animation for 300M of samples). Not sure why, maybe due to some rotation that cannot be realized by the rigid body actor (the animation is the following: https://www.youtube.com/watch?v=2bk2nYO-bVw ).


Add Heroku Pipelines support

Hey guys,
I'd be very interested to hear if you use the Beta release of Heroku Pipelines yet...
https://devcenter.heroku.com/articles/pipelines
Best,
Rikki

We happily do.

Hi @tute, sorry for the delay. What I was eluding to was whether or not this will supersede how suspenders currently handles staging and production apps? I'd be very interested to hear how you guys make use of this new lab feature in the coming months. Do you have any plans to write up a blog article about the subject?
Cheers!

Hi @tute, sorry for the delay. What I was eluding to was whether or not this will supersede how suspenders currently handles staging and production apps? I'd be very interested to hear how you guys make use of this new lab feature in the coming months. Do you have any plans to write up a blog article about the subject?

Thanks for your questions, @rikkipitt! I haven't personally used it yet, so I'm not sure what code changes would be appropriate for suspenders yet, or if at all.
Delegating the questions to @bernerdschaefer and @calebthompson, who have had good experiences with this. Thank you all!

Thanks guys, I've had chance to sit down and have a play with this today. It looks like you probably won't need to change how it creates separate apps for each environment as that is a requirement of pipelines. We could, however, automate the creation of the pipeline (add each of the apps) and possibly add "promote" functionality to ./bin/deploy when this all becomes stable...

I've found that when promoting an app from staging to production, some asset paths aren't updated and have the full path of the staging version... Have you guys experienced this yet? I assume it's because of the use of the asset_host config.
config.action_controller.asset_host = ENV.fetch("ASSET_HOST", ENV.fetch("HOST"))

We'll need a template for app.json, and add heroku pipeline commands during setup.

See also: https://gist.github.com/elle/966fbf9d37924f991209

Useful, thanks @tute. Do you think it's worth re-compiling assets in a postdeploy/promotion command to mitigate the above assets issue? Unless I simply have incorrect ASSET_HOST settings... what do you folks use for staging and production?

@rikkipitt I was looking into this, too, and found this warning in Heroku's help article on Pipelines helpful:

When promoting slugs between apps, Heroku will copy the slug verbatim between apps, without changes. In particular, the slug is not rebuilt with the environment of the target app. If your builds tend to bake in environment from the build-app context, then your slugs will not be portable between apps, and will not work correctly when promoted from the app where they were built. This may be the case, for example, if you’re using Ruby on Rails and the asset pipeline to build assets hosted at a CDN defined by a URL in your build environment. This is because URLs specific to the build-app will be baked into css and js-files, and those will not work or not work correctly when promoted.

When Heroku starts a dyno, it loads the application from the slug; with pre-compiled assets, the slug will contain references to your environment's ASSET_HOST value, as you observed.
Heroku automatically runs rake assets:precompile in the process of building the slug when you push a new commit. As far as I know, re-running that task after the slug has been compiled (i.e., if you were to change the value of ASSET_HOST, but without pushing a new commit) won't actually make any changes to the already-compiled slug.
This leads me to believe that Pipelines won't play well with the asset_host configuration, but I'd be happy to be proven wrong.

Thanks @reshleman. It's starting to sound like we might not be able to make use of the Pipeline benefits... I'll conduct some tests tomorrow to see if the slug is immutable or not.

@tute those crowdwise links in https://github.com/thoughtbot/suspenders/issues/617#issuecomment-148787534 seem to be broken, are they internal to you folks?

@tute those links in #617 (comment) seem to be broken, are they internal to you folks?

yes, I removed them

Sadly, I've just heard from Heroku support that there are no triggers for Rake tasks after promotion.

One idea would be to use the same ASSET_HOST across apps. If your CDN is using proper expiration, and your app is using the asset pipeline, unique files will be created such that they can all exist on the same CDN without running into each other.
Jon @ Heroku Support

Is Amazon Cloudfront an option here?

Just got this back from Jon at Heroku:

Hey Rikki --
It's actually being worked on as we speak. We should have something in Beta in the next few weeks.
-Jon

I've found that when promoting an app from staging to production, some asset paths aren't updated and have the full path of the staging version... Have you guys experienced this yet? I assume it's because of the use of the asset_host config.
config.action_controller.asset_host = ENV.fetch("ASSET_HOST", ENV.fetch("HOST"))

@iwz did you deal with this issue in your setup? If so, how do you work it out?

Another issue with suspenders is rack-canonical, which redirects the app to staging with current configuration.

Useful, thanks @tute. Do you think it's worth re-compiling assets in a postdeploy/promotion command to mitigate the above assets issue? Unless I simply have incorrect ASSET_HOST settings... what do you folks use for staging and production?

Something like this in staging makes it work:
config.action_controller.asset_host = "#{ENV.fetch("HEROKU_APP_NAME")}.herokuapp.com"

Useful commands while setting up an app today (notes to myself):
# Set up heroku pipelines plugin
heroku plugins:install heroku-pipelines

# Create a pipeline, add applications
heroku pipelines:create -a app-name-staging
heroku pipelines:add -a app-name-staging app-name
heroku pipelines:add -a app-name-production app-name

# Set up (by hand for now) an initial database from staging, plus branch migrations
heroku pg:pull DATABASE_URL app_name_development --app app-name-staging
rake db:migrate
heroku pg:reset DATABASE_URL --app app-name-staging-pr-### --confirm app-name-staging-pr-###
heroku pg:push app_development DATABASE_URL --app app-name-staging-pr-132

Will work on this on Friday.

I've found that when promoting an app from staging to production, some asset paths aren't updated and have the full path of the staging version... Have you guys experienced this yet? I assume it's because of the use of the asset_host config.

config.action_controller.asset_host = ENV.fetch("ASSET_HOST", ENV.fetch("HOST"))

@iwz did you deal with this issue in your setup? If so, how do you work it out?

@tute no, i haven't gotten that far along yet in my greenfield app.

Another note: we might need to remove auto deploy from Circle CI after this.

Pipelines and github deploy are technically separate features. I like both.

On Oct 23, 2015, at 1:06 PM, Tute Costa<EMAIL_ADDRESS>wrote:
Another note: we might need to remove auto deploy from Circle CI after this.
—
Reply to this email directly or view it on GitHub.

Closing in favor of PR: https://github.com/thoughtbot/suspenders/pull/639. Thank you! :clap:

I said "closing in favor of PR: #639" but didn't close. Here it goes!

Cheers @tute, I'll keep an eye on #639
Rikki

Apologies in advance for appending/hijacking this closed discussion, however you're the only other folk I've found discussing this issue so I hoped we could help each other out regarding Heroku pipelines using the same assets and so asset_host for staging and production.
@rikkipitt Did you happen to hear back from Jon at Heroku on running post-promotion rake tasks?
I believe I'm encountering a similar issue to what you were discussing, in that the compiled application.css contains hardcoded CDN URLs. As a result, the staging CDN URL is in the application.css asset served by the production environment.
The fix I'm considering:

Set asset_host to a replaceable token, e.g. @CDN_HOST@ for the CSS files only:

config.action_controller.asset_host = Proc.new do |source, _request|
  if source.end_with?('.css')
    '@CDN_HOST@'
  else
    ENV['ASSET_HOST']
  end
end

Then add a rack middleware before the Static middleware to replace @CDN_HOST@ in any *.css files with ENV['ASSET_HOST'].

response_body.gsub!('@CDN_HOST@', ENV['ASSET_HOST'])

There will be a small cost the first time a new version of a *.css file is requested, however after that it will be cached by the current environment's CDN so the above gsub! won't happen often.
Can you see any issues with this or do you happen to have an alternative solution?


Feature Suggestion: horizontal Tabs for inline (TabularInline, StackedInline)

first thanks for this awesome work, but it would be great if you consider enabling to display the inline admin as horizontal tabs instead of making it display vertically as when we have several inline models the data is got messed and be hard for navigation.
Current View:

Target View(as you can see there is bookings tab section so i can see all the user bookings)

+1 for this.
I'm currently looking for a replacement for Suit in an old app that I'm modernising, and this for me is the #1 missing feature that prevents me choosing Unfold over Baton.

+1 for this.
I'm currently looking for a replacement for Suit in an old app that I'm modernising, and this for me is the #1 missing feature that prevents me choosing Unfold over Baton.
Unfold stands out as the superior choice for Django admin panels, offering an extensive array of options alongside a visually attractive interface. The integration of this essential feature, pivotal for managing complex applications, would significantly enhance its utility and effectiveness, so hope they consider it.

+1 for this.
I'm currently looking for a replacement for Suit in an old app that I'm modernising, and this for me is the #1 missing feature that prevents me choosing Unfold over Baton.

Unfold stands out as the superior choice for Django admin panels, offering an extensive array of options alongside a visually attractive interface. The integration of this essential feature, pivotal for managing complex applications, would significantly enhance its utility and effectiveness, so hope they consider it.

Hi, and thanks for the great job already accomplished ! It would be nice to be able to only display Inline fieldset in a specific tab. For now, I do it by playing with Alpine.js and template override, but a simple declaration like tab class in admin fieldsets would be wonderful !

@linuxipho Would you plz share an example how you doing it?

The below idea works for me.

Create an empty fieldset

class MODELAdmin(BaseAdminMixin):
    change_form_template = "admin/APP/MODEL/change_form.html"

    inlines = [SubModelInline]

    fieldsets = (
        ...
        ...

        (
            "INLINE TAB NAME",
            {
                "classes": ["tab"],
                "fields": (),
            },
        ),
    )

Add this JS that targets your SubModelInline's CSS class in your overridden template
{% extends "admin/change_form.html" %}
{% load i18n admin_urls admin_modify unfold static %}

{% block extrahead %}
    {{ block.super }}

    <script type="text/javascript">
    window.onload = function() {
        var inlineTab = document.querySelector('.tab-wrapper.fieldset-TAB_CLASS .aligned');
        var modelInline = document.getElementById('APP_NAME_MODELNAME-group');
        inlineTab appendChild(modelInline);
    };
    </script>

{% endblock %}

+1

+1

Added #549


Button to TOP and Pagination

Hello, could you please to add button to Top page and modify the pagination since if the post more than 100 look the number is so many especially on mobile ...

How to push the code into your repository theme. Since I am newbie for go especially hugo.
Anyway..thanks for great theme 👍😊

Thanks for opening an issue!
I am not sure if this matches the style of the theme. If we are to add this functionality we should make it optional.
If you want to contribute, please push the code to your own repository and then open a pull request here. Have fun!


compound terms for modifications

I don't think we should have these compound modification terms:
increased histone H4-K5, H4-K8, H4-K12 and H4-K16 acetylation at centromere outer repeat during vegetative growth
a) it isn't sustainable
b) we will only get data  for  proximal residues  (i.e the size of the mass spec fragment)
c) it would be better to be able to retrieve  all
increased H4-K5
increased  H4-K8
increased  H4-K12
individually but some modifications don't have terms, so the individual modifications are not inherited
d) Because the are observed together at the same time  doesn't indicate a dependency
So, if you could check that the individual modification phenotypes exist for all of the compound terms, I'll decompose the annotations.
tks

note to self: add "at otr" terms for H4K5 | H4K8 | H4K12 | H4K16 Ac.

OK, these have gone obsolete:
FYPO:0002383
FYPO:0002384
FYPO:0003219
FYPO:0003220
FYPO:0004323
FYPO:0005317
FYPO:0005337
and these are new:
increased histone H4-K5 acetylation at centromere outer repeat during vegetative growth FYPO:0007308
increased histone H4-K8 acetylation at centromere outer repeat during vegetative growth FYPO:0007309
increased histone H4-K12 acetylation at centromere outer repeat during vegetative growth FYPO:0007310
increased histone H4-K16 acetylation at centromere outer repeat during vegetative growth FYPO:0007311
increased histone H4-K5 acetylation at centromere central core during vegetative growth FYPO:0007312
increased histone H4-K8 acetylation at centromere central core during vegetative growth FYPO:0007313
increased histone H4-K12 acetylation at centromere central core during vegetative growth FYPO:0007314
increased histone H4-K8 acetylation at subtelomeric heterochromatin during vegetative growth FYPO:0007315
edit file: 6679a5c6c8160582564d6e8b3d4fa3e1c8bcde4a
release: 9d31f52f720cc68d43dfdf1fedacbeea6c7a5906


Fixing API reference

This PR fixes the docstrings of the roms-tools classes so that they show up nicer in the API reference. It also adds docformatter to pre-commit, and adds pre-commit to the docs environment.

@dafyddstephenson I added docformatter to pre-commit, but there is an issue:
https://github.com/CWorthy-ocean/roms-tools/actions/runs/11411703114/job/31756447960?pr=170
Have you seen this before?  Strange because I'm using the same version for pre-commit-hooks and docformatter as C-Star.
Looks like this is a known issue: https://github.com/PyCQA/docformatter/issues/293

sorry, apparently my email app was closed and I didn't notice - I do recognise this , I got around it by pinning the version of pre-commit to 3.8: (https://github.com/CWorthy-ocean/C-Star/blob/main/.github/workflows/pre-commit.yaml).

Thanks @dafyddstephenson!

@dafyddstephenson should we pin the pre-commit version here as well?
https://github.com/CWorthy-ocean/C-Star/blob/47de1ebd5ff70f92c52beff1f1bc7f796029ebc0/ci/environment.yml#L16


delete path with DEBUG=6, there is no compiler_explorer.py to run

You have to clone it!

sorry, opened a new pull request


Update NyaaPy APIs, add missing dependencies and add CLI argument to set player

Hi, I found that you are using old nyaa APIs, so I updated them to the current nyaapy APIs.

I aslo add some usge to Readme


fix(enhanced): allow dts plugin to be disabled

Description

DTS Plugin will crash if project is not DTS or has no tsconfig

Related Issue

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Checklist

[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] I have updated the documentation.

https://github.com/module-federation/universe/pull/2322
i fix some issues as well , you can merge it to your pr , and then merge to main


Your ubuntu repo is out of date!

Reading package lists... Done
E: The repository 'https://ppa.launchpadcontent.net/nateshmbhat/rm-trash/ubuntu jammy Release'  does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Thought mayhaps that you might be interested. Looks otherwise like an interesting utility!

Seems same on Debian


Popover: prop type anchorOrigin is invalid

On the initial load without showing the popover, the PropType validation is causing anchorOrigin and targetOrigin props to throw warnings.

here is my state:
this.state = {
            anchorOrigin: {horizontal:"left", vertical:"center"},
            targetOrigin: {horizontal:"left", vertical:"top"},
};

Here is how I am using the popover:
<Popover open={this.state.extensionsPopover === 'pop'}
                            anchorEl={this.state.anchorEl}
                            anchorOrigin={this.state.anchorOrigin}
                            targetOrigin={this.state.targetOrigin}
                            onRequestClose={this.closePopover.bind(this, 'pop')} >

Here is an arbitrary popover

Hi - here is some content

                                <RaisedButton primary={true} label="Here is a button"/>

</Popover>

It's expecting a function not an object. Maybe try wrapping it in a function:
anchorOrigin={() => {return this.state.anchorOrigin}}
targetOrigin ={() => {return this.state.targetOrigin}}

That seems inconsistent with the Docs: http://material-ui.com/#/components/popover
Or am I missing something....

I would say that it's an issue on your side since the example on the documentation works fine.

Thanks for your feedback guys. I am reviewing what I am doing and all I am doing is passing an object {horizontal:"left", vertical:"center"} to the anchorOrigin property.
I am confused and maybe you can give me some clarity before I continue spinning my wheels.
@anthony-dandrea is saying anchorOrigin prop should receive a function.
Now when I refer to the docs and follow the flow of data,the docs suggest anchorObject is passed in as an object to the anchorOrigin prop, not a function that returns an object.
From the docs
<RadioButton onClick={this.setAnchor.bind(this, 'horizontal', 'left')} label="Left" checked={this.state.anchorOrigin.horizontal === "left"} />
Notice this.state.anchorOrigin.horizontal is being used like an object.
Now the following sets the key/values of the anchorOrigin object from state.
setAnchor(positionElement, position, e) {
  let {anchorOrigin} = this.state;
  anchorOrigin[positionElement] = position;

  this.setState({
      anchorOrigin:anchorOrigin,
  });
},

Now in the next example from the docs, you will notice we are passing the anchorOrigin object from above into the anchorOrigin prop.
<Popover open={this.state.activePopover === 'pop'}
  anchorEl={this.state.anchorEl}
  anchorOrigin={this.state.anchorOrigin}
  targetOrigin={this.state.targetOrigin}
  onRequestClose={this.closePopover.bind(this, 'pop')} >

Here is an arbitrary popover

Hi - here is some content

    <RaisedButton primary={true} label="Here is a button"/>

</Popover>

So which is it, an object or a function?
I will keep digging into what is happening to see if I can pinpoint the discrepancy on either end.

Hi, anchorOrigin is an object.  The example code is more complex than necessary, as it deals with a configurable position.
<Popover open={this.state.activePopover === 'pop'}
  anchorEl={this.state.anchorEl}
  anchorOrigin: {{horizontal:"left", vertical:"center"}},
  targetOrigin: {{horizontal:"left", vertical:"top"}},
  onRequestClose={this.closePopover.bind(this, 'pop')} >

Here is an arbitrary popover

Hi - here is some content

    <RaisedButton primary={true} label="Here is a button"/>

</Popover>

This should work just fine.

@matsilva Any update on this?

Hey not quite sorry. Caught up with current startup life. Let me see if I can test this out again later tonight to verify.

Just tested outside the scope of my app with a clean install. Works fine.

Awesome, thanks.


Sussy Scan: WebView don't show content!

Source information
Sussy Scan 1.4.42
Source language
Portuguese
Steps to reproduce
WebView don't show content.
Expected behavior
Show content.
Actual behavior
WebView don't show content.

Mihon/Tachiyomi version
0.17.1-7044
Android version
Android 14
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Add a :+1: reaction to issues you find important.

Mude seu user-agent


feat: delete Nat.shiftr and Nat.shiftl

These already exists upstream (with minorly different but equal definitions) as Nat.shiftRight and Nat.shiftLeft.

bors r+

bors r+

bors r+


Add PodDisruptionBudget to Atlassian DC Helm Charts

PodDisruptionBudget is a critical resource when it comes to high availability and (un)planned disruptions like worker node upgrades, evictions etc.
This PR adds a pdb template and a pbd stanza in values.yaml. Note that when both minAvailable and maxUnavailable are set, maxUnavailable takes precedence. By default PDB is disabled.
Just in case, custom pdb labels and annotations can be defined in values. Covered with unit tests.
Checklist

[x] I have added unit tests
[x] I have applied the change to all applicable products
[x] The E2E test has passed (use e2e label)

Can you describe a scenario in which pod disruption budget is used with our products?

@nanux thanks for your comments! In more than 50% of helm charts that I have recently installed, pdb is pdb :) Though, there are ones where it's PodDisruptionBudget.  I have changed the name.
As to how pdb can be used with Atlassian DC products, it's not different from any deployment or statefulset. PDB is a guard rail to prevent a node from draining if pdb says there must be, say, at least 2 pods at all times. DPB is ofted used in combo with anti affinity rules to make sure your app always has some quorum. In case of DC products, you may want to make sure that there are at least 3 running and ready Jira pods at all times.
I can't explain it better than Kube docs do 😃


Parse error in php 5.6

Line 54 of RegisterUserHandler produces a parse error in Php 5.6
Parse error:  syntax error, unexpected '(' in /var/www/src/Model/User/Handler/RegisterUserHandler.php on line 54

This will create a problem when installing with Docker or Vagrant, since Php 5.6 is still the used version

Wanna submit a PR? Master and develop branch both at best.


Changed filename to match class name.

Description of the Change
File name is changed to message_verifier to match MessageVerifier class.

I'm merging this tonight if there are no other comments.


Thanks for the effort to the repo, I made some super tiny enhancements for you to check

setup simple unit tests with vitest.
change devDep node-html-parser as dep to fix module NOT FOUND errors.
i met a import.env.LEGACY undefined errors in plugin.configResolved reproduce with 9f2ace00caac581380fd259e45325e8029eb9687 and fixed with aa2e90f43921dbae6d6bb6d0fd5265d29e54a964.

This is all great, thank you so much for your contribution.
tests\__snapshots__  I think it should be ignored by default, what do you think?

Maybe we should keep the snapshots in repo and reviewed as part of your code review process. As quote from jest doc:
https://jestjs.io/docs/snapshot-testing#snapshot-testing-with-jest

The snapshot artifact should be committed alongside code changes, and reviewed as part of your code review process. Jest uses pretty-format to make snapshots human-readable during code review. On subsequent test runs, Jest will compare the rendered output with the previous snapshot. If they match, the test will pass. If they don't match, either the test runner found a bug in your code (in the  component in this case) that should be fixed, or the implementation has changed and the snapshot needs to be updated.

I got another issue with the plugin in truly project. When we using vite-plugin-dynamic-base along with vite-plugin-pwa. It seems that we should both using the publicPath of vite-plugin-dynamic-base with base of vite-plugin-pwa. Any idea to go through it?

Our snapshots will be a bit special. The content involves file directories. Everyone’s device is different, and the project storage address is different, so there will be different answers. At the time, I didn’t think it was a big problem.

Our snapshots will be a bit special. The content involves file directories. Everyone’s device is different, and the project storage address is different, so there will be different answers. At the time, I didn’t think it was a big problem.

Well, i'll add shots to .gitignore for this PR

我在真正的项目中遇到了另一个插件问题。当我们vite-plugin-dynamic-base与vite-plugin-pwa. 看来我们都应该使用publicPathofvite-plugin-dynamic-base和baseof vite-plugin-pwa。有什么想法可以通过吗？

We are actually using base and publicpath as a match.

@zhoujinfu 方便提个issue 讨论下你那个问题么

@zhoujinfu Thanks for your contribution, a new version has been released.


Apply style guide to Optimus workflow

@jsotobroad thanks for making this change! I have a few comments, mostly around including descriptions for all parameters. Also please bring this branch up to date with develop.

We should update the test wdls as well (e.g. https://github.com/HumanCellAtlas/skylab/blob/master/test/optimus/pr/test_optimus_PR.wdl) but I'm fine with implementing that in a separate PR/ticket

I wanted to focus on wdls required for our pipeline to run all in one go and then I think we can have a slower approach to fixing the rest of the wdls.  I made a ticket to address these other wdls in the future - https://elastc.com/c/d8btzqAt/649-add-style-guide-to-other-wdls

I added some docs where requested. I also made a proposal to how we deal with some of the boilerplate/default arguments in a commit against Attach10xbarcodes.wdl and made some minor updates across the documentation.

@ambrosejcarr @samanehsan i think ive answered all comments / made changes if you guys coudl take another look when you get a chance

@samanehsan all inputs should have descriptions now, sorry ><


add fuk

Sorry, no, the name is against the rules laid out in the PR template. In English that is a homophone for a vulgar word. If you want to rename the project, I'd reconsider adding it.