Endpoint label test

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

/test all

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
96fea84a2e2e6b0d2f8a8140b92d3c3271b6064a
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
96fea84a2e2e6b0d2f8a8140b92d3c3271b6064a
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
96fea84a2e2e6b0d2f8a8140b92d3c3271b6064a
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
96fea84a2e2e6b0d2f8a8140b92d3c3271b6064a
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
96fea84a2e2e6b0d2f8a8140b92d3c3271b6064a
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
96fea84a2e2e6b0d2f8a8140b92d3c3271b6064a
link
/test integ-telemetry-k8s-tests_istio

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

/test all

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
96fea84a2e2e6b0d2f8a8140b92d3c3271b6064a
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
96fea84a2e2e6b0d2f8a8140b92d3c3271b6064a
link
/test integ-telemetry-k8s-tests_istio

analyze-tests_istio
c09dcafb10273416a400eaf679ad1a9024a355bc
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
96fea84a2e2e6b0d2f8a8140b92d3c3271b6064a
link
/test integ-telemetry-k8s-tests_istio

analyze-tests_istio
c09dcafb10273416a400eaf679ad1a9024a355bc
link
/test analyze-tests_istio

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

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

/test all

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

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
96fea84a2e2e6b0d2f8a8140b92d3c3271b6064a
link
/test integ-telemetry-k8s-tests_istio

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

analyze-tests_istio
5b84cc807f2f75a07be3d52701d28ed9673126ac
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
96fea84a2e2e6b0d2f8a8140b92d3c3271b6064a
link
/test integ-telemetry-k8s-tests_istio

analyze-tests_istio
5b84cc807f2f75a07be3d52701d28ed9673126ac
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
5b84cc807f2f75a07be3d52701d28ed9673126ac
link
/test integ-pilot-k8s-tests_istio

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

/test all

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

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
96fea84a2e2e6b0d2f8a8140b92d3c3271b6064a
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-k8s-tests_istio
57c632b41a44d29aa7f75625a06304f880699041
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
57c632b41a44d29aa7f75625a06304f880699041
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
57c632b41a44d29aa7f75625a06304f880699041
link
/test integ-telemetry-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
57c632b41a44d29aa7f75625a06304f880699041
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
57c632b41a44d29aa7f75625a06304f880699041
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
57c632b41a44d29aa7f75625a06304f880699041
link
/test integ-security-k8s-tests_istio

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

/test all

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

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
57c632b41a44d29aa7f75625a06304f880699041
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
57c632b41a44d29aa7f75625a06304f880699041
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
04b85df4866a91327b0a126b4999cc7722391be3
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
04b85df4866a91327b0a126b4999cc7722391be3
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
04b85df4866a91327b0a126b4999cc7722391be3
link
/test integ-telemetry-k8s-tests_istio

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

/test all

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

Test name
Commit
Details
Rerun command

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

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

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

/retest

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

Test name
Commit
Details
Rerun command

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

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

@bianpengyuan: PR needs rebase.

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

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

Test name
Commit
Details
Rerun command

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

release-notes_istio
909c7e2e878a513f9718f5587eb0b9b3df826963
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

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

release-notes_istio
909c7e2e878a513f9718f5587eb0b9b3df826963
link
/test release-notes_istio

integ-multicluster-k8s-tests_istio
909c7e2e878a513f9718f5587eb0b9b3df826963
link
/test integ-multicluster-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
909c7e2e878a513f9718f5587eb0b9b3df826963
link
/test integ-multicluster-k8s-tests_istio

analyze-tests_istio
6b0313ead223de363097f87bb8d76e6020b6a3dc
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
909c7e2e878a513f9718f5587eb0b9b3df826963
link
/test integ-multicluster-k8s-tests_istio

analyze-tests_istio
6b0313ead223de363097f87bb8d76e6020b6a3dc
link
/test analyze-tests_istio

unit-tests_istio
6b0313ead223de363097f87bb8d76e6020b6a3dc
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
6b0313ead223de363097f87bb8d76e6020b6a3dc
link
/test analyze-tests_istio

unit-tests_istio
6b0313ead223de363097f87bb8d76e6020b6a3dc
link
/test unit-tests_istio

integ-telemetry-k8s-tests_istio
6b0313ead223de363097f87bb8d76e6020b6a3dc
link
/test integ-telemetry-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

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

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

@bianpengyuan: PR needs rebase.

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

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

Test name
Commit
Details
Rerun command

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

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

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

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

Test name
Commit
Details
Rerun command

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

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

release-test_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test release-test_istio

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

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

Test name
Commit
Details
Rerun command

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

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

release-test_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test release-test_istio

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

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

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

Test name
Commit
Details
Rerun command

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

release-test_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test release-test_istio

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

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

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

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

Test name
Commit
Details
Rerun command

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

release-test_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test release-test_istio

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

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

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

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

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

Test name
Commit
Details
Rerun command

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

release-test_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test release-test_istio

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

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

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

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

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

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

Test name
Commit
Details
Rerun command

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

release-test_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test release-test_istio

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

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

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

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

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

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

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

Test name
Commit
Details
Rerun command

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

release-test_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test release-test_istio

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

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

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

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

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

unit-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

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

release-test_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test release-test_istio

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

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

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

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

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

unit-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test unit-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

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

release-test_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test release-test_istio

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

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

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

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

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

unit-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test unit-tests_istio

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

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

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

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

Test name
Commit
Details
Rerun command

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

release-test_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test release-test_istio

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

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

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

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

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

unit-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test unit-tests_istio

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

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

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

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

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

Test name
Commit
Details
Rerun command

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

release-test_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test release-test_istio

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

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

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

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

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

unit-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test unit-tests_istio

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

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

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

integ-helm-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test integ-helm-tests_istio

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

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

Test name
Commit
Details
Rerun command

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

release-test_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test release-test_istio

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

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

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

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

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

unit-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test unit-tests_istio

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

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

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

integ-helm-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test integ-helm-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

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

release-test_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test release-test_istio

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

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

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

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

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

unit-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test unit-tests_istio

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

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

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

integ-helm-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test integ-helm-tests_istio

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

analyze-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

release-test_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test release-test_istio

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

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

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

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

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

unit-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test unit-tests_istio

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

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

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

integ-helm-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test integ-helm-tests_istio

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

analyze-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test analyze-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

release-test_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test release-test_istio

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

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

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

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

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

unit-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test unit-tests_istio

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

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

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

integ-helm-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test integ-helm-tests_istio

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

analyze-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test analyze-tests_istio

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

lint_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

release-test_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test release-test_istio

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

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

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

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

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

unit-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test unit-tests_istio

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

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

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

integ-helm-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test integ-helm-tests_istio

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

analyze-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test analyze-tests_istio

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

lint_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test lint_istio

gencheck_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

release-test_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test release-test_istio

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

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

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

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

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

unit-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test unit-tests_istio

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

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

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

integ-helm-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test integ-helm-tests_istio

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

analyze-tests_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test analyze-tests_istio

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

lint_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test lint_istio

gencheck_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test gencheck_istio

release-notes_istio
d1d260c73f9e740cbbd08fa84c38c6fc65b6a397
link
/test release-notes_istio

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

Superseded by https://github.com/istio/istio/pull/30137

Superseded by https://github.com/istio/istio/pull/30137


Bump several go.mod libs.

Signed-off-by: yanggang<EMAIL_ADDRESS>Bump hcsshim , go-systemd , go-restful , otel go.mods..

@fangn2
Oh, maybe i first go mod tidy , then update again , and forget go mod tidy it.....
:bowtie: :bowtie:
thanks for the review..
Had updated.

There's another PR open to pull in a new hcsshim https://github.com/containerd/containerd/pull/7810. I'd say lets leave that off here as we figure out the issue @thaJeztah is mentioning

There's another PR open to pull in the same hcsshim tag #7810. I'd say lets leave that off here as we figure out the issue @thaJeztah is mentioning

Ah, thanks for linking that one; let me know if you need brainstorming @dcantah

Outdated, suggest bumping individually or when the changes are dependent on each other.


If the table field is Chinese report error

If the table field is Chinese report error

Come to China's product needs and willingness to cooperate.
Hello, we are using your company's product Qwik. But there are a few requirements that you want to know if you can do it: you can group when you have more dimensions, similar to a tree directory. Measurements can dynamically change the summary method (sum, avg), do not know if it can be developed and time, cost.
In addition, we are a Qlik partner and your products are great. I hope that further agency and cooperation will be required. Looking forward to your reply. Thank you
<EMAIL_ADDRESS>


Run tests on GitHub actions

Hmm, the benchmarks aren't completing for some reason.

Also Safari 10 (OS X 10.12) and Firefox (Linux) are consistently timing out.


chore(master): release 1.2.3

:robot: I have created a release beep boop
1.2.3 (2023-05-11)
Miscellaneous

deps: update dependency phpunit/phpunit to v10.1.3 (0b375e1)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/php-cs-fixer-config/releases/tag/v1.2.3 :sunflower:


[MINOR] New Fields.CODE and Formatting

Minor auth-related changes:

New Fields.CODE
Use Fields constants whenever possible
Formatting

@creechy Please review 🙏


Transifex needs better maintaining

Our transifex isn't maintained at all. I tried to help by offering translate the docs to Hebrew. That was two months ago. I also had to push and send more and more messages. And over two months, Alvin (who's the only one who's in charge of the materialize transifex) didn't respond. It needs more maintainers that can easily add people into the editing teams and the new languages needed into the project so the people added can actually edit.
I'm not the only one suffering from this: https://github.com/Dogfalo/materialize/issues/4654

I personally think we don't need translations at all. I don't know a single web framework that actually supports officially translations and I think this is for a reason. In my opinion is English a must. If you're not able to speak English and try to become a developer you are literally fucked. On the other hand it is cool and practical, but if @Dogfalo is not able to maintain it we should discontinue the service

I add new languages when there is enough contributor demand so that the entire translation does not depend on just one person. In any case I accepted your request for a Hebrew translation since you are so motivated, in addition I made you a coordinator for the language so you can invite people who you think will help with the translation effort for the language.


migrate regression/address-book to cypress [waiting for #1216]

See #1102 for original spike.
Take a look at big happy path for example.
See cypress video in our wiki.
This one needs login so do after #1216.

PR: #1471


fix(autocomplete): reopen panel on input click

Currently if the user clicks an autocomplete to open it, selects an option and then clicks again, the panel won't open, because we use focus and the input was focused already. These changes add an extra click listener so the panel can reopen.
Fixes #15177.

Addressed the feedback @jelbourn.

Is there any chance this will get merged?

what is the news on this. Is this something that material agrees with and is just not focusing on or is this antithetical to how material wants this to be handled

This PR (and any other that get stalled out) was blocked by some number of test failures when we ran it against Google internal CI/presubmit test system. It's in the backlog to investigate, but has been lower priority than other work going on.

Is there a good workaround in the meantime?


StateMachine: balancing_{debit,credit}

Add Transfer flags:

balancing_debit
balancing_credit

When set during account creation, the transfer's amount will be reduced to the highest nonzero amount that fulfills the debit/credit accounts' invariants (respectively).
Flag compatibility:

The flags can be used together or apart.
They are compatible with each other, as well as linked and pending.
~They are presently incompatible with post_pending and void_pending (see "open questions" below).~ https://github.com/tigerbeetledb/tigerbeetle/pull/449#issuecomment-1442780421

In my first-pass implementation I created two new error codes: at_most_no_debits and at_most_no_credits, returned when the respective flag is set but no money could be moved. But I realized that by removing them and using the existing error codes conveys additional information (i.e. which constraint is the limiting factor).
Open questions:

~Naming improvements?~
~How should this flag interact with post/void transfers? (Currently it panics with a "TODO"). Either:~

(We could just implement this as "if > pending amount, send pending amount", but since we already can send the full amount via post amount=0 there isn't really any reason to...)
~Return a new error code.~
~If we support partial post/void of pending transfers, then we can extend post/void to support balancing_debit/balancing_credit.~
-~ How should this flag interact with exists_with_different_amount?~
We could expect an exact-amount match, and return exists_with_different_amount otherwise. This is simplest to implement, but is probably surprising API behavior.
~When balancing_debit or balancing_credit, only return exists_with_different_amount when the incoming transfer's amount is less than the saved transfer's amount. Otherwise return exists.~

~(Still pretty simple to implement. Slightly more intuitive, hopefully.)~
~This is a bit fuzzy since the incoming transfer's amount might actually be different than it was originally, and we would still return exists. - I'm leaning towards this anyway, since it is a little simpler.~

~Use an extra field in the durable transfer to store its original "maximum" amount.~

Pre-merge checklist
Performance:

I am very sure this PR could not affect performance.

Updated!

Rename {debits,credits}_at_least to balancing_{debit,credit} (thanks for excellent naming suggestion, @jorangreef!). I used these names instead of closing_{debit,credit} since the feature is more general than just closing accounts.
Refactor the amount = { ... } block. I know you suggested splitting it into a separate function, but unless there is something nice & reusable there that I'm not seeing, I'd prefer to keep it inline because I think it's easier to follow.
Improve the "Close Account" example in the docs.
I'm still a little divided wrt supporting balancing_{debit,credit} for post/void transfer, but don't feel strongly about it one way or the other, so it is included.

(The flag's meaning for post/void is different than it is for single-phase/pending.
In particular, the flags are interchangeable, and have nothing in particular to do with the debit or credit accounts, so the flag name is (somewhat pedantically) not really correct.
I can't think of any concrete+practical examples where either of these would be useful (that is not already covered by amount=0).
That said, implementing it does provide symmetry by avoiding "incompatible flags" so this may well be the lesser of two evils.)

The failing Java CI appears to be some sort of client coverage check. (@batiati can you take a look?)

We could expect an exact-amount match, and return exists_with_different_amount otherwise. This is simplest to implement, but is probably surprising API behavior.
if transfer ID already exists then we can make sure that the given amount is more than or equal to the existing transfer amount. You should not expect an exact match because it would ruin idempotence.

Thanks, @batiati!

I'm still a little divided wrt supporting balancing_{debit,credit} for post/void transfer

Would be great to walk and talk this later today.

@kakserpom

If transfer ID already exists then we can make sure that the given amount is more than or equal to the existing transfer amount. You should not expect an exact match because it would ruin idempotence.

When dealing with balancing debit/credit transfers, there are two amounts:

A₁: The amount in the create_transfers event.
A₂: The actual amount transferred.

(A₂ ≤ A₁.)
Because of this, exists_with_different_amount is tricky when paired with balancing_debit and/or balancing_credit.
Here are just a few of the different approaches we could take:

Return exists_with_different_amount if the retry amount doesn't match A₁.
Return exists_with_different_amount if the retry amount doesn't match A₂. (Implemented in this PR.)
Return exists_with_different_amount if the retry amount is greater-than-or-equal-to A₂. (As you described above).

Reasons for picking number 2:

The error is more precise & literally accurate — "exists with different amount" — the created transfer's amount is A₂, not A₁.
The behavior corresponds more closely with that of non-balancing transfers. (No special case in the implementation).
Approach 1 is precise (albeit using the A₁ rather than A₂), but we don't presently store A₁, and it isn't clear that it would be useful.
This does mean that retries with the original A₁ can return exists_with_different_amount. I wouldn't say that this "ruins idempotence" any more than exists does, it is just something to be aware of when using balancing transfers.

@sentientwaffle

I thought we were not going to store the requested amount (A₁) (which in my case will always be 2**64).
If we are going to end up storing it, then the approach no. 1 makes the most sense. Otherwise, the approach no. 3 is the way to go.
Approach no. 2 is not a good option because of its non-idempotent behavior: a retry is likely to produce an error which you have to ignore. Imagine a situation where you are retrying to create a balancing transfer with the exact same transfer structure and you are bound to get an error unless A₁ matches A₂, an error which you wouldn't have gotten on the first try and which you don't really care for.

I thought we were not going to store the requested amount (A₁) (which in my case will always be 2**64).

Correct; I only mentioned approach 1 by way of my explanation.

If we are going to end up storing it, then the approach no. 1 makes the most sense. Otherwise, the approach no. 3 is the way to go.

Another issue with approach 3 is that it incorrectly implies that any amount greater than A₂ would have resulted in the same A₁. Suppose you have an account with $100, and create a balancing transfer to deduct $10. The account's balance is now $90. If you retry the same balancing transfer (i.e. same id), but with an amount of $120, then approach 3 would return exists, as if the original balancing transfer had tried the same thing and could only move $10 (when in fact if the original A₁ was $120, A₂ would be $100).
I can certainly see why, with the balancing amount A₁ always equal to 2**64, approach 3 is best.
But this feature is more general than that. In your case you can just ignore exists_with_different_amount like you would exists.

@sentientwaffle so what approach have you chosen in the end?

@sentientwaffle so what approach have you chosen in the end?

Approach 2, i.e. return exists_with_different_amount if the retry amount doesn't match A₂.

@sentientwaffle Approach no. 2 has an unfortunate side effect: exists_with_different_amount makes the whole chain (of linked transfers) fail.

To be clear, it only returns exists_with_different_amount on the retry, not on the first attempt.

Approach no. 2 has an unfortunate side effect: exists_with_different_amount makes the whole chain (of linked transfers) fail.

This is true of exists as well, so approaches 1, 2, and 3 all share this behavior.

Updated to add mutually_exclusive_flags, which replaces 4 create-transfer result codes. This was a more extensive change than just that, though:

Rename CreateAccountsResult.mutually_exclusive_flags to CreateAccountsResult.flags_are_mutually_exclusive.
In both CreateAccountsResult and CreateTransferResult, reorder mutually_exclusive_flags so that it immediately follows the id errors. Even though flags follows ledger/code in the structs, it makes sense to check it first since it can change behavior that follows. (This is important in the transfer — in accounts, it is just to correspond to transfers).
Also fix CreateTransferResult code ordering:

pending_id_must_* are now above ledger errors — not sure why they were so far down before.
Move timeout_reserved_for_pending_transfer below the pending_id errors. Previously it preceded them; not sure why. (This was a change to both the code and the enum).

@jorangreef Please sanity-check the result-code reordering to make sure I didn't miss something silly. I think this better reflects our result-precedence philosophy but I might have missed something. :crossed_fingers:

Thanks @sentientwaffle.

Also fix CreateTransferResult code ordering:
pending_id_must_* are now above ledger errors — not sure why they were so far down before.
Move timeout_reserved_for_pending_transfer below the pending_id errors. Previously it preceded them; not sure why. (This was a change to both the code and the enum).

Nice. Can you explain though why this is a fix? Or is this more to follow the struct field order for consistency?
Do our tests still pass with the reordering (they're supposed to catch any reordering—to enforce determinism)?

Nice. Can you explain though why this is a fix? Or is this more to follow the struct field order for consistency?

The "fix" was to the enum order — the StateMachine code was already correct (except inasmuch as it did not match the enum order).
In particular, many errors were below the "exists" codes, despite being higher-precedence.
exists_with_different_pending_id and exists_with_different_user_data were also swapped with one another.

Do our tests still pass with the reordering (they're supposed to catch any reordering—to enforce determinism)?

Yes; I updated the tests where appropriate. But for the most part the tests were already correct, since they test the state machine code, not the order of enum variants.

(Above issue was resolved offline; replica version was outdated.)


[INFRA] Remove some spark file.

What changes were proposed in this pull request?
XSQL copied some file from Spark. These file looks not needed.
This PR will remove them.
How was this patch tested?
No UT.

LGTM

Thanks! Merged to master and branch-0.6


Modin scalability issues

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Centos 7
Modin version (modin.__version__): 0.11.1
Python version: 3.8.5
Code we can use to reproduce: yes

Describe the problem
hi all,
I am evaluating modin and I am trying to test the scalability (strong scaling). Following is a snippet of the code.
I have been running this while varying the number of CPUs in the ray cluster. I have a 10 node cluster with 16 CPUs each. So, I am testing for 1, 2, 4, …, 128, 160 CPUs (each time the entire cluster has been stopped and restarted with new configuration).
For 100M rows, following are the average timings I got (discarding the 0th iteration).

world
AVERAGE of time (ms)

1
48879.18562

2
42504.13573

4
38960.01136

8
43442.16764

16
45417.99891

32
47339.0817

64
45241.66238

128
48524.96344

160
52743.6024

It looks like I might be doing something wrong here, because I couldn’t get any speed up, while adding more resources for the operation.
I tried assigning NPartitions the same as number of CPUs in the cluster. But that didn’t help as well.
import modin.config
modin.config.NPartitions.put(w)

I am wondering what I am missing here?
Thanks in advance
Source code / logs
r = 100* 10**6
it = 5

import ray
ray.init(address='v-001:6379', _redis_password=RAY_PW, _node_ip_address='v-001')

frame_data = np.random.randint(0, r, size=(r, 2))
frame_data1 = np.random.randint(0, r, size=(r, 2))

os.environ["MODIN_ENGINE"] = "ray"
import modin.pandas as pd

for i in range(it):

    df_l = pd.DataFrame(frame_data).add_prefix("col")
    df_r = pd.DataFrame(frame_data1).add_prefix("col")
    print(f"data loaded", flush=True)

    t1 = time.time()
    out = df_l.merge(df_r, on='col0', how='inner')
    t2 = time.time()

    print(f"timings {r} {i} {(t2 - t1) * 1000:.0f} ms, {out.shape[0]}", flush=True)

    del df_l
    del df_r
    del out
    gc.collect()

Hi @nirandaperera! I'm marking this issue as resolved since it hasn't been updated recently! If you have any further questions, please feel free to reopen this issue, or open a new one!


setNames(...) does not take effect for Spark VectorSlicer

Tested with this Spark example code for VectorSlicer:
    val data = Arrays.asList(
      Row(Vectors.sparse(3, Seq((0, -2.0), (1, 2.3)))),
      Row(Vectors.dense(-2.0, 2.3, 0.0))
    )

    val defaultAttr = NumericAttribute.defaultAttr
    val attrs = Array("f1", "f2", "f3").map(defaultAttr.withName)
    val attrGroup = new AttributeGroup("userFeatures", attrs.asInstanceOf[Array[Attribute]])

    val dataset = spark.createDataFrame(data, StructType(Array(attrGroup.toStructField())))

    val slicer = new VectorSlicer().setInputCol("userFeatures").setOutputCol("features")
slicer.setIndices(Array(1)).setNames(Array("f3"))

Mleap transform result only has [2.0], while it should  be [2.0, 1.0] where 1.0 is for column f3.
Cause is that in VectorSlicerOp, only obj.indices are persisted/loaded but not obj.names. Also the names are not handled in MLeap VectorSlicerModel.

Looks like we will be requiring metadata about the dataframe if someone wants to use names. The MLeap model will store just the indices, when serializing the model, if the user sets the names field, MLeap will check with the dataframe meta data to determine the index of the element.

An issue with this is that we need to know the column name of the VectorSlicer in order to create the model, but the model is supposed to be independent of the transformer itself. Let's come back to this one.


"lodash/defaultsDeep" systemJS Error

I just rebuild my whole node_modules folder and I ran into this error message

(SystemJS) Module not already loaded loading "lodash/defaultsDeep"

I'm on angular 4.0.2 and atc 3.3.1. I also tried using atc 3.2.4 which did work in that regard.
This is my atc entry in the systemJS config:
           'angular-tree-component': 'npm:angular-tree-component/dist/angular-tree-component.umd.js',

I am also getting same error. Please let me know the solution.

Hi all,
Adding the following block to system.config.js seems to do the trick for now. I'm sure there is a better way of doing this.
    meta: {
          'angular-tree-component': {
              deps: [
                  'lodash/first.js',
                  'lodash/last.js',
                  'lodash/compact.js',
                  'lodash/find.js',
                  'lodash/includes.js',
                  'lodash/remove.js',
                  'lodash/indexOf.js',
                  'lodash/pullAt.js',
                  'lodash/pick.js',
                  'lodash/defaultsDeep.js']
          }

      },

@gpapp I tried that but still getting the same error!

I change every step to angular2-tree-component instead of angular-tree-component and it's worked.
Install
npm install --save angular2-tree-component
Add to system.config.js
'angular2-tree-component': 'node_modules/angular2-tree-component/dist/angular2-tree-component.umd.js',
Import module
import { TreeModule } from 'angular2-tree-component';

@gpapp how the rest of your system.config file looks like? I'm still getting the same error

@MonkeyDoll that's an older version of the component. You will get a warning message while installing the package.

This is probably not going to help a lot, but I switched over to webpack and the problem disappeared, so it is definitely a problem related to systemjs.

Hi.. can some one help me here ?? No response on the below question from the owner as well...
npm install angular-tree-component
I have installed angular-tree-component version 3.3.0 . In appmodule.ts when i try to import the Tree Module, I am not able to get the reference by just using import { TreeModule } from 'angular-tree-component';
I need to reach dist/angular-tree-component and then TreeModule can be imported. and when running the app in IE 11 , chrome this gives me an error " Unexpected Token import " .
I am using Webpack with angular version 2.4.8 .
Any suggestions ?

where i can find system.config.js ? ( where is located? )
i've latest angular 4 and angular-cli
npm install --save angular-tree-component

Hi all,
Adding the following block to system.config.js seems to work for me now.
......
map: {
.....
            'lodash': 'npm:lodash',
            'angular-tree-component': 'npm:angular-tree-component/dist'
.....
},
packages: {
....
lodash: { defaultExtension: 'js' },
'angular-tree-component': { format: 'cjs', main: 'angular-tree-component.umd.js', defaultExtension: 'js' }
.....
}

I have issues when using it with webpack . Any idea how it's done. I have
raised issue on this, but no one has replied yet.
On Apr 29, 2017 2:23 PM, "Andrey"<EMAIL_ADDRESS>wrote:

Hi all,
Adding the following block to system.config.js seems to work for me now.
......
map: {
.....
'lodash': 'npm:lodash',
'angular-tree-component': 'npm:angular-tree-component/dist'
.....
},
packages: {
....
lodash: { defaultExtension: 'js' },
'angular-tree-component': { format: 'cjs', main: 'angular-tree-component.umd.js', defaultExtension: 'js' }
.....
}
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/500tech/angular-tree-component/issues/262#issuecomment-298156660,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AStMS6uohZauUZPpXufkhTeEhNsOvC-Oks5r0vqTgaJpZM4NB2b8
.

First of all - I recommend everyone to switch to webpack, it's much better in any case than SystemJS.
Second - I added lodash to the bundle in 3.4.1. Can you check with that version?

@adamkleingi, I tried with 3.4.1 also no luck.  I could not use webpack in my project as we commited to use systemjs only. Any other possibilities.?

sasinandrei's worked
the key for me was missing this (I think it was the format 'cjs')
'angular-tree-component': { format: 'cjs', main: 'angular-tree-component.umd.js', defaultExtension: 'js' }

Thanks @sasinandrei , helped me out a lot.

@sasinandrei - thanks.
I dropped support for SystemJS, closing this one.


standalonepublisher editorial from image sequences

 Freshdesk Ticket ID: 345
 Freshdesk Ticket Agent: Jakub Jezek
 Freshdesk Ticket Agent Email<EMAIL_ADDRESS> Ticket Priority: High
 Freshdesk Ticket Description: Dear Pype,Thank you for the Skype yesterday. Everything is looking very promising and I am looking forward to testing the new pipeline soon! I have added 2 test shots in your folder. Will this be enough?/prod/sourceserver/PYPE_dev_project/shots/pyp_0003_0010_composite (.exr Aces 2065-1)pyp_0003_0020_composite (.exr Aces 2065-1)Also 2 offline reference.pyp_0003_0010_offline (.jpg sRGB)pyp_0003_0020_offline (.jpg sRGB)I preferably have the offlines in a separate folder if possible or convenient. The shots are from a project called 'Werewolf'. You can have a look at that project, I have given you access. Also, you spit in the Nuke scripts. Hereby the project specs:Resolution: 3168x1782Output colorspace: Aces AP0 / Aces 2065-1Working resolution: Aces API / AcesCGOCIO config: Aces v1.0.1 No RRTHandles: 0ViewLUT: sRGB Compress HighlightsNuke version: 10.0v5Let me know if you have any questions.Best,    Stefan

Stefan Beekhuijzen

VFX Supervisor

IMDb page

VFX Showreel

Entrepotdok 66NL-1018 AD Amsterdam

T: +31 20 530 9696F: +31 20 530 9697

www.filmmore.eu

Agent Jakub Jezek linked Freshdesk ticket 345 for this issue.


⚠ DDoS-Relay lin-US-W-lax-01 has degraded performance

In 88f72ee, DDoS-Relay lin-US-W-lax-01 (http://<IP_ADDRESS>:42069/;csv) experienced degraded performance:

HTTP code: 200
Response time: 141 ms

Resolved: DDoS-Relay lin-US-W-lax-01 performance has improved in d43fdea after 17 minutes.


Contribution correct 1 crucial command starter npx

I correct 1 crucial command for starters or begginers,
always all commands must proceed with "npx/pnpx/yarn" at the beggining.

Thanks for raising this, @miguelgargallo... we're actually looking in to how to deal with these commands right now. It's kind of complicated:

if we leave the prefix off, people copy the command and it doesn't work, which as you say is bad for beginners
if we just add npx (the most common choice), that's great for those users but no good for yarn or pnpx
if we add all three in the command, as in your PR, it's clearer but still doesn't copy correctly, and also people could use yet other options
if we leave the prefix off but make a note about it somewhere, people might not see the note

Given this discussion we're going to close the PR, but we have made a new issue to track this - feel free to comment there.


openstack-ardana: Trello job status reporting

Enable the periodic openstack-ardana jobs to report their status on the
SUSE Cloud Jenkins Green Trello board, same as the openstack-mkcloud jobs.

Successfully tested that https://ci.suse.de/blue/organizations/jenkins/cloud-ardana9-job-demo-x86_64/detail/cloud-ardana9-job-demo-x86_64/2/pipeline/84 was publishing notifications to the Trello board, but changing the Trello card label is currently broken for everyone, so the result isn't visible.


dW doesn't work with top-level forms

Given (cursor at |):
|(set! *warn-on-reflection* true)

(defdescribe dogfooding-test
  (it "no diagnostics in splint"
    (match? {:result {:diagnostics []
                      :exit 0}}
      (-> (splint/run ["--quiet" "--no-parallel" "dev" "src" "test"])
        (with-out-str-data-map)))))

Typing dW throws the error below:

Versions:

neovim: v0.10.0
nvim-paredit commit: dd851b3

I forgot to write that the intended behavior is that the (set! *warn-on-reflection* true) line and following blank line should be deleted.

thank you!!!


jQuery not defined knockout template

I created a new knockout project with yoman and when I start it I get in the browser :
Uncaught ReferenceError: jQuery is not defined.
I checked webpack.config.vendor.js and I have this line :
new webpack.ProvidePlugin({ $: 'jquery', jQuery: 'jquery' }),
And vendo.js is loaded correctly. I don't understand why $ is defined but not jQuery.
Any idea ?

I just tried to repro this by creating a new KO application using generator-aspnetcore-spa version 0.9.3, but no such problem occurred.
I'm guessing therefore that this doesn't just happen out of the box for you, but rather you are writing some code of your own that fails with this error. That being the case, this is a webpack config question, so could you check Webpack docs or raise it with the Webpack community? Thanks!

It certainly is a problem with the generator version 0.9.3 - a new, unmodified, Knockout project fails with the unresolved reference error.
The original poster has probably given up on this, that's why there was no further reply.
But the problem exists. Makes you wonder how many people are actually using this generator to begin with, eh?


feat: resetState func

I miss the reference to the resetState functionality in README.md.

@Q-back Added some draft of docs, please take a look ;)

@Q-back could you take a look a final look?


Load font on current protocol

uses the current protocol http/https to load the external assets
this will break if loading over file:// protocol (unlikely). alternate solution is to always use https.
Fixes #2

Thanks!


⚠ Minecraft has degraded performance

In 26c3a18, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 1296 ms

Resolved: Minecraft performance has improved in b39a7b3.


[Contribution] Script for making the necessary files for a new model

I've made a script for making the necessary files for a new model that:

Make a model file in cogdl/models/nn/
Make an example file in examples
Add to tests/tasks/ file
Add to match.yml
Remind the user to add their model to README.md

The script can be tested by
$ python scripts/model_maker.py

@cenyk1230 Hello, the issues raised by Travis are not from parts I added. Am I expected to fix them for my pull request to be accepted? Let me know if that's the case. Thank you

Hi @Sahandfer, I have fixed the issues with the code in the master. Please wait for the re-run.

@Sahandfer Nice job. But I wonder whether the template model should be also tested.

Thank you @cenyk1230! I think the template files I created serve as an interface for new models to be added; since they don't have any logic or calculations within them, I don't see it as necessary to test them. However, one improvement that I can think of is modifying the templates in the future after establishing a global style for cogdl models.

Hi @Sahandfer, I think maybe the template files can be moved to a new folder such as template/ (maybe template/nn/) in the root directory since each file in the cogdl/ will be used for computing coverage.

Hello @cenyk1230, I think that's a great suggestion. I have moved the two templates to a new template folder and they are now called: base_model and base_example. I have also updated the script to use these templates.

@Sahandfer It seems that you moved the wrong model file. I think you should git mv the cogdl/models/nn/template.py rather than cogdl/models/base_model.py.

@cenyk1230 Sorry for that. I fixed my mistake; however, the coverage has decreased but I'm not sure what the reason for that is. Thank you and sorry for the trouble.

Well done!


More robust cwd in tests

Fixes #261. Supersedes #265. I squashed and rebased @hantek 's commits so we can benefit from his good work.

LGTM

Thanks Vincent and Bart for picking this up : )


Getting issue with the helm install

Hi ,
I have installed the repo using helm install command and my secret-store driver is throwing error.
Its not coming up and thus restarts each time.
Error:
kubectl logs csi-secrets-store-provider-azure-1619547838-secrets-store-b8lx8 secrets-store -n my-ns
I0427 18:36:15.862229       1 exporter.go:33] metrics backend: prometheus
F0427 18:36:25.899047       1 main.go:132] failed to start manager, error: an error on the server ("") has prevented the request from succeeding
goroutine 1 [running]:
k8s.io/klog/v2.stacks(0xc00000e001, 0xc0001f4000, 0x91, 0x9b)
/go/pkg/mod/k8s.io/klog/v2@v2.5.0/klog.go:1026 +0xb9
k8s.io/klog/v2.(*loggingT).output(0x26219c0, 0xc000000003, 0x0, 0x0, 0xc00017e700, 0x1ed1099, 0x7, 0x84, 0x0)
/go/pkg/mod/k8s.io/klog/v2@v2.5.0/klog.go:975 +0x191
k8s.io/klog/v2.(*loggingT).printf(0x26219c0, 0xc000000003, 0x0, 0x0, 0x0, 0x0, 0x19a03a7, 0x23, 0xc0004a1d90, 0x1, ...)
/go/pkg/mod/k8s.io/klog/v2@v2.5.0/klog.go:750 +0x191
k8s.io/klog/v2.Fatalf(...)
/go/pkg/mod/k8s.io/klog/v2@v2.5.0/klog.go:1514
main.main()
/go/src/sigs.k8s.io/secrets-store-csi-driver/cmd/secrets-store-csi-driver/main.go:132 +0x94c
goroutine 6 [chan receive]:
k8s.io/klog/v2.(*loggingT).flushDaemon(0x26219c0)
/go/pkg/mod/k8s.io/klog/v2@v2.5.0/klog.go:1169 +0x8b
created by k8s.io/klog/v2.init.0
/go/pkg/mod/k8s.io/klog/v2@v2.5.0/klog.go:417 +0xdf
goroutine 7 [sleep]:
time.Sleep(0x6fc23ac00)
/usr/local/go/src/runtime/time.go:193 +0xd2
sigs.k8s.io/controller-runtime/pkg/log.init.0.func1()
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.8.2/pkg/log/log.go:63 +0x45
created by sigs.k8s.io/controller-runtime/pkg/log.init.0
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.8.2/pkg/log/log.go:62 +0x35
Please help.

Could you provide more details on how you're installing and what is the cluster configuration?

What cluster is this? AKS/AKS-engine?
Kubernetes version
CSI Driver and provider version
What are the steps taken to install?
kubectl get pods -A output?

I am using AKS cluster

kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.0", GitCommit:"**", GitTreeState:"clean", BuildDate:"2021-04-08T16:31:21Z", GoVersion:"go1.16.1", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.7", GitCommit:"****", GitTreeState:"clean", BuildDate:"2021-03-10T23:40:01Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}

CSI Driver image used: Image:      mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.1.0

Steps taken to install: Followed official doc: https://docs.microsoft.com/en-us/azure/key-vault/general/key-vault-integrate-kubernetes
helm  repo add ...
helm repo install

@vsaxena6 Are you using the latest helm charts to deploy the driver? It looks like there might be an issue connecting to the kube-apiserver when the client is initializing. Do you have any firewall rules or restricted egress enabled in the cluster?
If yes, could you try deploying the charts in kube-system namespace?

Thanks!! It worked in kube-system. We had firewall rules applied in our AKS, that could be the reason behind failing of driver.

Hi,
I could run the  driver in kube-system, however when I am trying to call the driver from my namespace I am getting following error:
MountVolume.SetUp failed for volume "secrets-store-inline" : kubernetes.io/csi: mounter.SetUpAt failed to get CSI client: driver name secrets-store.csi.k8s.io not found in the list of registered CSI drivers
This is how my deployment file look like:

Hi,
After adding node-selector, I could see that the driver has been found by the pod, however it still fails giving following errors:

Hello @vsaxena6 ,
It can be related to your network firewall rule blocking egress from the host  .
Please take a look at the similar issue:
https://github.com/Azure/secrets-store-csi-driver-provider-azure/issues/292
https://github.com/Azure/secrets-store-csi-driver-provider-azure/issues/471

@vsaxena6 Here is our troubleshooting guide: https://azure.github.io/secrets-store-csi-driver-provider-azure/troubleshooting/

There is no secretProviderClassNamespace. The SecretProviderClass will be looked up from the same namespace as the pod referencing it in the volume.
If the mount fails, you can look at the logs from the driver and provider running on the same node as your application. Steps to retrieve the logs are in the troubleshooting guide.

@vsaxena6 Any updates on this? Is the issue resolved?

Closing this issue due to inactivity. Please feel free to reopen if this is still an ongoing issue.


Styled Not Working In General With Vite

Environment

npx envinfo --system --binaries --npmPackages styled-components,babel-plugin-styled-components --markdown --clipboard
## System:
 - OS: Linux 5.4 Ubuntu 20.04.4 LTS (Focal Fossa)
 - CPU: (4) x64 AMD Ryzen 9 5900X 12-Core Processor
 - Memory: 13.65 GB / 15.73 GB
 - Container: Yes
 - Shell: 5.0.17 - /bin/bash
## Binaries:
 - Node: 18.2.0 - /home/laradock/.nvm/versions/node/v18.2.0/bin/node
 - Yarn: 1.22.19 - /home/laradock/.yarn/bin/yarn
 - npm: 8.9.0 - /home/laradock/.nvm/versions/node/v18.2.0/bin/npm
## npmPackages:
 - styled-components: ^5.3.5 => 5.3.5

Reproduction
I am running Docker version 20.10.16 build aa7e414. I am using Docker compose v1 because Docker compose v2 doesn't work with Laradock yet (MAKE SURE TO DISABLE v2!!!).
I containerized the backend and frontend in separate containers

Clone the fresh installation of Laravel from (USE THE next BRANCH!!) https://github.com/ericwang401/pastry-clicker/tree/next
Clone Laradock in the project folder using git clone https://github.com/laradock/laradock.git
CD to the Laradock folder and make .env file with cp .env.example .env
Inside .env file set PHP_VERSION to PHP_VERSION=8.1 AND DO NOT EDIT MYSQL SETTINGS
Now edit docker-compose.yml inside laradock
Edit these specific lines

I deleted the conflicting ports that conflicted with 3000 in this config. You can copy and paste this ports section directly into the docker-compose file
### Workspace Utilities ##################################
    workspace:
    ....
      ports:
        - "${WORKSPACE_SSH_PORT}:22"
        - "${WORKSPACE_VUE_CLI_SERVE_HOST_PORT}:8080"
        - "${WORKSPACE_VUE_CLI_UI_HOST_PORT}:8000"
        - "${WORKSPACE_ANGULAR_CLI_SERVE_HOST_PORT}:4200"
        - 3000:3000

Now edit the Laravel environment file

DB_CONNECTION=mysql
DB_HOST=mysql
DB_PORT=3306
DB_DATABASE=default
DB_USERNAME=default
DB_PASSWORD=secret

Start up the Laravel app in Laradock folder using docker-compose up -d nginx mysql
Enter into bash mode in the Docker container docker-compose exec workspace bash
Run npm i && composer i
Run npm run dev
Now navigate to localhost in your browser and open console and the errors should be there

Steps to reproduce
They are above
Expected Behavior
A card should appear aligned center horizontally inside a div.
Actual Behavior
Importing css from styled-components/macro results in this error in the browser console
Uncaught SyntaxError: The requested module '/node_modules/.vite/deps/styled-components_macro.js?v=849f7612' does not provide an export named 'css' (at Container.tsx:1:1)

If I don't use the css macro and just import styled, I get this error in the browser console
Uncaught ReferenceError: process is not defined
    at<EMAIL_ADDRESS>(core.js:23:17)
    at __require2 (chunk-5537U2Q2.js?v=849f7612:47:50)
    at<EMAIL_ADDRESS>(index.js:70:1)
    at __require2 (chunk-5537U2Q2.js?v=849f7612:47:50)
    at<EMAIL_ADDRESS>(validate.js:10:20)
    at __require2 (chunk-5537U2Q2.js?v=849f7612:47:50)
    at<EMAIL_ADDRESS>(validateNode.js:8:17)
    at __require2 (chunk-5537U2Q2.js?v=849f7612:47:50)
    at<EMAIL_ADDRESS>(index.js:259:21)
    at __require2 (chunk-5537U2Q2.js?v=849f7612:47:50)

At first, I went through all the docs for styled components and Vite, searched existing issues, and checked out various Stackoverflow threads that suggested certain Babel plugins.
I tried using vite-plugin-babel-macros in my vite.config.ts file. It worked, but I get type errors saying that content is a non-boolean attribute, which is wrong because I specified content as a boolean or undefined attribute in https://github.com/ericwang401/pastry-clicker/blob/c7d7af77603044cabb8715eee3b4281406d38c4f/resources/scripts/components/elements/Container.tsx

I made a new React app with yyarn create vite --template react react-styled-components and created a minimal example and it worked okay for me. I wonder if this is something specific in your config?


Fix compile warnings in mantis-server-agent module

There are compile warnings in the code due to:

deprecated APIs
missing @Nullable/@NotNull annotations
incomplete javadocs
lambda can be replaced with method references
raw usage of generic types
unnecessary type parameters (like Map<String> m = new HashMap<String>())
anonymous class can be replaced with lambdas
and more.

We don't need to solve all of them, but a good coding exercise is to address most those compile warnings when possible. Guidelines are:

Not change code logic, which should be addressed and filed PR separately
Not change public interfaces (class, methods and fields) that would break other modules or applications. But it's safe to rename private fields or methods when necessary.
Prefer readability to more concise code
Improve tests in the module is welcome but not required
Compile and pass all existing tests.

This tracks the effort for the mantis-server-agent module to make the code change scoped.

Hi @liuml07 can you please assign this task to me?

Hi @liuml07 can you please assign this task to me?

can i work on this?


JDBC - MSSQL - getLivenessCheckPortNumbers() shouldn't that be the mapped port and not the internal?

https://github.com/testcontainers/testcontainers-java/blob/600d235d220d5e507405921b4e241aa73c067a2a/modules/mssqlserver/src/main/java/org/testcontainers/containers/MSSQLServerContainer.java#L64-L67
Mysql has the ports mapped
https://github.com/testcontainers/testcontainers-java/blob/600d235d220d5e507405921b4e241aa73c067a2a/modules/mysql/src/main/java/org/testcontainers/containers/MySQLContainer.java#L56-L60
If the overrides are removed you would receive mapped ports of the exposedPorts.

Hey @npetzall, thanks for raising this issue. Your observation seems correct. In which scenarios would this lead to issues for you?

If I remember correctly I couldn't use the MSSQLServerContainer and had to extend it. Since it failed the liveliness check.
This was on Windows so testcontainers tried to connect to 1433 or something like that but it was reachable on a different port.

I do also have a a custom wait strategy
@Override
    protected void waitUntilContainerStarted() {
        new WaitAllStrategy()
                .withStrategy(Wait.forListeningPort())
                .withStrategy(Wait.forLogMessage("(?s).*default collation was successfully changed.*",1))
                .waitUntilReady(this);
        super.waitUntilContainerStarted();
    }

So it might be related to changes done that affect what is exposed or how the strategies work.

Thanks, this example makes sense.

It's a bit tricky since the JavaDoc only says ports to check if ready, but Wait.forListeningPort seems to assume that it's a published port.

This issue should be closed now. It's in the 1.17.4 release


Sorting messages old-new?

Team,
api.messages.list returns messages in descending order (creation date)
Messages in the Webex Teams client are displayed in ascending order.
Q: How can I sort the messages?

The API doesn’t have a sort option, the default is “The list sorts the
messages in descending order by creation date.”
You need to sort clientside if you need them sorted some other way.
On Tue, Feb 19, 2019 at 09:56 DJF3<EMAIL_ADDRESS>wrote:

Team,
api.messages.list returns messages in descending order (creation date)
Messages in the Webex Teams client are displayed in ascending order.
Q: How can I sort the messages?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/CiscoDevNet/webexteamssdk/issues/72, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AND35Qk9MlnDZrcgXYds9zc-Xen3-YOjks5vPBCGgaJpZM4bDJUq
.

Ok, that example seems to put all messages in a list first and then sort it. Maybe I'll add that step to convert it to a lists first.
Thanks,
DJ


Module 'CleverAdsSolution' not found

I'm trying build game in xcode, but every time i got error "Module 'CleverAdsSolution' not found", I tried everything what I found in documentation, all setuped correctly, but always getting this error. Build file was creat in macbook and windows, but still got this error

Hello @Harlampey, thank you for creating the issue.
Please note that in order to successfully build the iOS project, it is essential to run Cocoapods install iOS frameworks to your project. Usually, Unity on macOS triggers Cocoapods at the end of the iOS build process, but this step may fail and result in an error in the Unity console.

Make sure there are no errors during the Unity build process. If any issues occur, please share the build logs with us.
If you are building the iOS project on Windows, after transferring the Xcode project to macOS, you must run the pod update command in your project directory from the terminal. This will perform important steps for installing the frameworks.

Also the pod update command may return errors or instructions in the terminal.
Let us know if this helps.


[minor polish] add space before y/n in question

Summary
How was it tested?

Current dependencies on/for this PR:

main

PR #534   👈

This comment was auto-generated by Graphite.


App crashes while adding multiple contacts

Hi, i want to add 300 contacts within loop.
Here is my code
ls.forEach((f) async {
       f["avatar"] = null;
      ContactsService.addContact(Contact.fromMap(f));
  });

Contacts adding successfully but app crashes while adding. Loader widget not working and Android occurs "This app is not responding" alert.

Fixed with this.
for (var i = 0; i < contacts.length; i++) {
       var f = contacts[i];
       f["avatar"] = null;
       ContactsService.addContact(Contact.fromMap(f));
       await Future.delayed(Duration(milliseconds: 100));
       setState(() {
         loadingText = f["displayName"];
       });
     }


Release on Pypi?

The latest release on Pypi was a year and a half ago. Could it be updated? Thank you in advance

@wdm0006, could we make a new release? It would solve #176.

Version 2.0.0 is out.


Assignable Scopes seems to incorrectly state you cannot assign to the root

The doc's say
An array of strings that specifies the scopes that the custom role is available for assignment. Currently cannot be set to the root scope ("/") or a management group scope. For more information, see AssignableScopes and Organize your resources with Azure management groups.
However on the Assignable Scopes page this shows
Role is available for assignment in all scopes 	"/"

So which one is correct?

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

ID: eac44e5e-65e1-d989-4afe-0463e8ff51d0
Version Independent ID: 5665dd03-d06e-ca29-668f-7cb91e5f9ffd
Content: Custom roles for Azure resources
Content Source: articles/role-based-access-control/custom-roles.md
Service: role-based-access-control
GitHub Login: @rolyon
Microsoft Alias: rolyon

@kilasuit Thanks for reporting this. We are looking into this and will get back to you shortly.

@rolyon can you explain this? Is it only assignable to the root for built-in scopes, or is there another sort of discrepancy going on?

Hi @kilasuit
Built-in roles have AssignableScopes set to the root scope ("/"). However, if you are creating your own custom role, you can't set AssignableScopes to the root scope ("/"). You must set to one or more subscriptions or resource groups.
thanks

We will now proceed to close this thread. If you have further questions feel free to tag us in the comments and we will gladly continue the discussion.


Bug: 'builtin_function_or_method' object is not iterable. && AUC on CelebDF is far away from paper's.

I follow your instruction to prepare CelebDF test dataset, trying to validate lipforensics_ff.pth on CelebDF. However I came across:
Traceback (most recent call last):
  File "evaluate.py", line 179, in <module>
    main()
  File "evaluate.py", line 174, in main
    auc = validate_video_level(model, loader, args)
  File "evaluate.py", line 109, in validate_video_level
    for data in tqdm(loader):
  File "/data/users/kaixuanzhang/anaconda3/envs/torch14/lib/python3.6/site-packages/tqdm/std.py", line 1180, in __iter__
    for obj in iterable:
  File "/data/users/kaixuanzhang/anaconda3/envs/torch14/lib/python3.6/site-packages/torch/utils/data/dataloader.py", line 345, in __next__
    data = self._next_data()
  File "/data/users/kaixuanzhang/anaconda3/envs/torch14/lib/python3.6/site-packages/torch/utils/data/dataloader.py", line 856, in _next_data
    return self._process_data(data)
  File "/data/users/kaixuanzhang/anaconda3/envs/torch14/lib/python3.6/site-packages/torch/utils/data/dataloader.py", line 881, in _process_data
    data.reraise()
  File "/data/users/kaixuanzhang/anaconda3/envs/torch14/lib/python3.6/site-packages/torch/_utils.py", line 394, in reraise
    raise self.exc_type(msg)
TypeError: Caught TypeError in DataLoader worker process 0.
Original Traceback (most recent call last):
  File "/data/users/kaixuanzhang/anaconda3/envs/torch14/lib/python3.6/site-packages/torch/utils/data/_utils/worker.py", line 178, in _worker_loop
    data = fetcher.fetch(index)
  File "/data/users/kaixuanzhang/anaconda3/envs/torch14/lib/python3.6/site-packages/torch/utils/data/_utils/fetch.py", line 44, in fetch
    data = [self.dataset[idx] for idx in possibly_batched_index]
  File "/data/users/kaixuanzhang/anaconda3/envs/torch14/lib/python3.6/site-packages/torch/utils/data/_utils/fetch.py", line 44, in <listcomp>
    data = [self.dataset[idx] for idx in possibly_batched_index]
  File "/data/users/kaixuanzhang/repos/LipForensics/data/dataset_clips.py", line 169, in __getitem__
    sample = self.transform(sample)
  File "/data/users/kaixuanzhang/anaconda3/envs/torch14/lib/python3.6/site-packages/torchvision/transforms/transforms.py", line 70, in __call__
    img = t(img)
  File "/data/users/kaixuanzhang/anaconda3/envs/torch14/lib/python3.6/site-packages/torchvision/transforms/transforms.py", line 247, in __call__
    return F.center_crop(img, self.size)
  File "/data/users/kaixuanzhang/anaconda3/envs/torch14/lib/python3.6/site-packages/torchvision/transforms/functional.py", line 382, in center_crop
    image_width, image_height = img.size
TypeError: 'builtin_function_or_method' object is not iterable

I noticed that the transform input is np.ndarray but the PIL Image is required, so I substitute the CenterCrop with VideoCenterCrop:
class VideoCenterCrop:
    def __init__(self, outputsize):
        self.output_size = outputsize

    def __call__(self, img):
        """
        param img (numpy.ndarray): THWC
        """
        if isinstance(self.output_size, numbers.Number):
            output_size = (int(self.output_size), int(self.output_size))
        #print("img shape", img.shape)
        image_width, image_height = img.shape[2], img.shape[1]
        crop_height, crop_width = self.output_size
        crop_top = int(round((image_height - crop_height) / 2.))
        crop_left = int(round((image_width - crop_width) / 2.))
        return img[:, crop_top:crop_top + crop_height, crop_left:crop_left + crop_width, :]

Then run
python evaluate.py --dataset CelebDF --weights_forgery ./models/weights/lipforensics_ff.pth

It works, but I got only AUC of 57.7% on CelebDF. I am wondering which step did I get wrong.
I really appreciate it if you could give me some advice. Thank you!

In the CelebDFClips class' __getitem__ method, the sample is cast to torch.Tensor type (line 165 in data/dataset_clips.py) before the transform is applied, and torchvision.transforms.CenterCrop can handle torch.Tensor inputs. Perhaps, the torchvision library version that you have installed is older? You can install using the requirements.txt file to make sure.
Also, have you preprocessed the mouth crops according to the instructions? Do your mouth crops look similar to the examples in the examples directory?

In the CelebDFClips class' __getitem__ method, the sample is cast to torch.Tensor type (line 165 in data/dataset_clips.py) before the transform is applied, and torchvision.transforms.CenterCrop can handle torch.Tensor inputs. Perhaps, the torchvision library version that you have installed is older? You can install using the requirements.txt file to make sure.
Also, have you preprocessed the mouth crops according to the instructions? Do your mouth crops look similar to the examples in the examples directory?

I updated torchvision and everything works fine now, and got 80.8% on CelebDF test set. It was preprocessing problem. I got landmarks on the cropped faces so it looks different from your examples. Problem solved. Thank you!

In the CelebDFClips class' __getitem__ method, the sample is cast to torch.Tensor type (line 165 in data/dataset_clips.py) before the transform is applied, and torchvision.transforms.CenterCrop can handle torch.Tensor inputs. Perhaps, the torchvision library version that you have installed is older? You can install using the requirements.txt file to make sure.
Also, have you preprocessed the mouth crops according to the instructions? Do your mouth crops look similar to the examples in the examples directory?

I updated torchvision and everything works fine now, and got 80.8% on CelebDF test set. It was preprocessing problem. I got landmarks on the cropped faces so it looks different from your examples. Problem solved. Thank you!

@zkxcongming  Can you please share details of your preprocessing?
I get only 76.2% for the same evaluation.
I described detailes of reproducibility test in another issue -   https://github.com/ahaliassos/LipForensics/issues/9


Code Polishing & Optimization & Migration to Java 8 & Fixed Deprecations

Required merge on tinyMediaManager/api-scraper#8
It has been refactored mostly by Intellij idea by my close interventions and inspections.
-Removed final modifier from static methods.
-Replaced redundant Ifs with an inline return on simple logic functions.
-Replaced classic fors with foreaches where it is applicable.
-Removed legacy & obsolete code.
-Resolved many Unchecked Calls and Unchecked Assignments.
-Simplified boolean expressions.
-Removed redundant local variables.
-Used Collection.singletonList() instead of Arrays.asList on single argument lists to improve performance.
-Replaced += & + string concatenations with String builder in for loops.
-Replaced == evaluation with equals on strings.
-Replaced redundant type arguments with diamond operator <>
-Renamed empty catch blocks' Exception argument to "ignored".
-Added final modifier to objects that are used in synchronized methods.
-Removed unnecessary throws declarations on methods.
-Replaced ThreadLocal anonymous classes having initialValue() to ThreadLocal.withInitial()
-Replaced try-finally with try with resource management.
-Removed unnecessary private accessor on enum constructors.
-Removed unnecessary  access modifiers from interfaces.

Thanks for your contribution


stirling-pdf: 0.30.1 -> 0.33.1

https://github.com/Stirling-Tools/Stirling-PDF/releases
https://github.com/Stirling-Tools/Stirling-PDF/releases/tag/v0.32.0
https://github.com/Stirling-Tools/Stirling-PDF/releases/tag/v0.33.0
https://github.com/Stirling-Tools/Stirling-PDF/releases/tag/v0.33.1
The web app opens as expected

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Rebased on master, since OfBorg seemed to error out for some reason.
Maybe it works correctly now.


Airlock to space on the Hunter's ship

When exiting the Hunter's ship, the airlock opens to reveal the skybox.

Details
When inside the Hunter's ship during the main questline, as you leave through the airlock back to your own ship, space can be seen through a gap in the model.
Game Version
<IP_ADDRESS>
New Game
Yes
Reproduction Steps
Visit the Hunter's ship interior (I do not know the COC location yet!)

This can be fixed by adding either a black plane behind the airlock or adding a dummy ship piece to make it look like you're opening back onto your own ship.


Does the latest version support prompt tuning for Fine-tuning?

i see "prompt tuning" as supported technology in main page, but i do not how to configure this feature

same question


Protocol test framework improvements

I made these changes when debugging Ruby head's hanging issue and they did make the build failures easier to catch.

Both debuggee connection and workflows should have timeout
Rename WebSocketClient#cleanup to #close because that's all it does
Only perform cleanup logic when the socket/threads are present, which may not be the case when the error happens during test setup.

@peterzhu2118 I could also use your help on this test improvement. You can run protocol tests with bundle exec rake test_protocol, which is not included in rake test.


Peer ID doesn't match libp2p public key

Issue description
I've see a couple of errors related to "Peer ID doesn't match libp2p public key."
And i'm not sure if it's the issue with my/remote node configuration or not.
See attached screenshot with 2 seemingly unrelated cases.
Specifications
Node version: v6.0.0-beta.1.19
Platform: Ubuntu 20.04
Node wallet: 0x490618BE2457f2789e580335F7171C70E7E511b1
Node libp2p identity: QmZwiL4gYeemM1kHUX76g9VbsiCkHZFBn3rzWsGs6aFTJH
Contact details

Email:

Error logs

Disclaimer
Please be aware that the issue reported on a public repository allows everyone to see your node logs, node details, and contact details. If you have any sensitive information, feel free to share it by sending an email to<EMAIL_ADDRESS>

How do you publish and how to replicate ?

This issue is being closed as inactive due to the date of the last activity on it. If you believe this is still a problem, please create a new issue and confirm that it is reproducible in the current ot-node release version. We are working towards closing open issues that meet specific criteria and ask you to create a new one for those that that are truly bugs in current release. We'll be monitoring those issues so that they are properly managed.
Thank you,
OriginTrail Team