Update to kind 1.20.0

[ ] 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.

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

Test name
Commit
Details
Rerun command

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

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

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

Test name
Commit
Details
Rerun command

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

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

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

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

Test name
Commit
Details
Rerun command

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

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

integ-telemetry-mc-k8s-tests_istio
3b7ef498743797ada22b0de09a8ffcdfdeac6876
link
/test integ-telemetry-mc-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

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

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

integ-telemetry-mc-k8s-tests_istio
3b7ef498743797ada22b0de09a8ffcdfdeac6876
link
/test integ-telemetry-mc-k8s-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

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

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

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

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

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

Test name
Commit
Details
Rerun command

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

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

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

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

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

Test name
Commit
Details
Rerun command

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

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

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

lint_istio
de6a804cdec8e6fc8708e87a3e86e67b2b25fbd9
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

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

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

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

lint_istio
de6a804cdec8e6fc8708e87a3e86e67b2b25fbd9
link
/test lint_istio

gencheck_istio
de6a804cdec8e6fc8708e87a3e86e67b2b25fbd9
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

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

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

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

lint_istio
de6a804cdec8e6fc8708e87a3e86e67b2b25fbd9
link
/test lint_istio

gencheck_istio
de6a804cdec8e6fc8708e87a3e86e67b2b25fbd9
link
/test gencheck_istio

unit-tests_istio
de6a804cdec8e6fc8708e87a3e86e67b2b25fbd9
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

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

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

lint_istio
de6a804cdec8e6fc8708e87a3e86e67b2b25fbd9
link
/test lint_istio

gencheck_istio
de6a804cdec8e6fc8708e87a3e86e67b2b25fbd9
link
/test gencheck_istio

unit-tests_istio
de6a804cdec8e6fc8708e87a3e86e67b2b25fbd9
link
/test unit-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

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

lint_istio
de6a804cdec8e6fc8708e87a3e86e67b2b25fbd9
link
/test lint_istio

gencheck_istio
de6a804cdec8e6fc8708e87a3e86e67b2b25fbd9
link
/test gencheck_istio

unit-tests_istio
de6a804cdec8e6fc8708e87a3e86e67b2b25fbd9
link
/test unit-tests_istio

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

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

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

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

Test name
Commit
Details
Rerun command

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

lint_istio
de6a804cdec8e6fc8708e87a3e86e67b2b25fbd9
link
/test lint_istio

gencheck_istio
de6a804cdec8e6fc8708e87a3e86e67b2b25fbd9
link
/test gencheck_istio

unit-tests_istio
de6a804cdec8e6fc8708e87a3e86e67b2b25fbd9
link
/test unit-tests_istio

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

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

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

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

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

Test name
Commit
Details
Rerun command

lint_istio
de6a804cdec8e6fc8708e87a3e86e67b2b25fbd9
link
/test lint_istio

gencheck_istio
de6a804cdec8e6fc8708e87a3e86e67b2b25fbd9
link
/test gencheck_istio

unit-tests_istio
de6a804cdec8e6fc8708e87a3e86e67b2b25fbd9
link
/test unit-tests_istio

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

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

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

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

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

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

Test name
Commit
Details
Rerun command

lint_istio
de6a804cdec8e6fc8708e87a3e86e67b2b25fbd9
link
/test lint_istio

gencheck_istio
de6a804cdec8e6fc8708e87a3e86e67b2b25fbd9
link
/test gencheck_istio

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

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

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

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

unit-tests_istio
2bdb154a3ffd47f93348c8aa2b23a0721a27ffb1
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
de6a804cdec8e6fc8708e87a3e86e67b2b25fbd9
link
/test gencheck_istio

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

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

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

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

unit-tests_istio
2bdb154a3ffd47f93348c8aa2b23a0721a27ffb1
link
/test unit-tests_istio

lint_istio
2bdb154a3ffd47f93348c8aa2b23a0721a27ffb1
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

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

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

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

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

unit-tests_istio
2bdb154a3ffd47f93348c8aa2b23a0721a27ffb1
link
/test unit-tests_istio

lint_istio
2bdb154a3ffd47f93348c8aa2b23a0721a27ffb1
link
/test lint_istio

gencheck_istio
2bdb154a3ffd47f93348c8aa2b23a0721a27ffb1
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

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

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

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

unit-tests_istio
2bdb154a3ffd47f93348c8aa2b23a0721a27ffb1
link
/test unit-tests_istio

lint_istio
2bdb154a3ffd47f93348c8aa2b23a0721a27ffb1
link
/test lint_istio

gencheck_istio
2bdb154a3ffd47f93348c8aa2b23a0721a27ffb1
link
/test gencheck_istio

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

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

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

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
97cfadef64d7cf6ad58ae5e114b78fee853a0841
link
/test integ-telemetry-mc-k8s-tests_istio

lint_istio
d9f17e26b357b16c34c3dc5b09874dcb821b3a13
link
/test lint_istio

gencheck_istio
d9f17e26b357b16c34c3dc5b09874dcb821b3a13
link
/test gencheck_istio

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

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

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

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

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

Test name
Commit
Details
Rerun command

lint_istio
d9f17e26b357b16c34c3dc5b09874dcb821b3a13
link
/test lint_istio

gencheck_istio
d9f17e26b357b16c34c3dc5b09874dcb821b3a13
link
/test gencheck_istio

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

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

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

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

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

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

Test name
Commit
Details
Rerun command

lint_istio
d9f17e26b357b16c34c3dc5b09874dcb821b3a13
link
/test lint_istio

gencheck_istio
d9f17e26b357b16c34c3dc5b09874dcb821b3a13
link
/test gencheck_istio

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

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

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

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

unit-tests_istio
dd2d911503ed0dea866c37d7cf4f322968be3284
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
d9f17e26b357b16c34c3dc5b09874dcb821b3a13
link
/test gencheck_istio

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

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

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

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

unit-tests_istio
dd2d911503ed0dea866c37d7cf4f322968be3284
link
/test unit-tests_istio

lint_istio
dd2d911503ed0dea866c37d7cf4f322968be3284
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

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

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

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

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

unit-tests_istio
dd2d911503ed0dea866c37d7cf4f322968be3284
link
/test unit-tests_istio

lint_istio
dd2d911503ed0dea866c37d7cf4f322968be3284
link
/test lint_istio

gencheck_istio
dd2d911503ed0dea866c37d7cf4f322968be3284
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

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

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

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

unit-tests_istio
dd2d911503ed0dea866c37d7cf4f322968be3284
link
/test unit-tests_istio

lint_istio
dd2d911503ed0dea866c37d7cf4f322968be3284
link
/test lint_istio

gencheck_istio
dd2d911503ed0dea866c37d7cf4f322968be3284
link
/test gencheck_istio

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

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

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

Test name
Commit
Details
Rerun command

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

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

lint_istio
dd2d911503ed0dea866c37d7cf4f322968be3284
link
/test lint_istio

gencheck_istio
dd2d911503ed0dea866c37d7cf4f322968be3284
link
/test gencheck_istio

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

unit-tests_istio
91f8abce6a9e01cbf61c21ba6f1a8412dc9e5adf
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

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

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

lint_istio
dd2d911503ed0dea866c37d7cf4f322968be3284
link
/test lint_istio

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

unit-tests_istio
91f8abce6a9e01cbf61c21ba6f1a8412dc9e5adf
link
/test unit-tests_istio

gencheck_istio
91f8abce6a9e01cbf61c21ba6f1a8412dc9e5adf
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

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

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

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

unit-tests_istio
91f8abce6a9e01cbf61c21ba6f1a8412dc9e5adf
link
/test unit-tests_istio

gencheck_istio
91f8abce6a9e01cbf61c21ba6f1a8412dc9e5adf
link
/test gencheck_istio

lint_istio
91f8abce6a9e01cbf61c21ba6f1a8412dc9e5adf
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
91f8abce6a9e01cbf61c21ba6f1a8412dc9e5adf
link
/test unit-tests_istio

gencheck_istio
91f8abce6a9e01cbf61c21ba6f1a8412dc9e5adf
link
/test gencheck_istio

lint_istio
91f8abce6a9e01cbf61c21ba6f1a8412dc9e5adf
link
/test lint_istio

integ-security-multicluster-tests_istio
91f8abce6a9e01cbf61c21ba6f1a8412dc9e5adf
link
/test integ-security-multicluster-tests_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
91f8abce6a9e01cbf61c21ba6f1a8412dc9e5adf
link
/test unit-tests_istio

gencheck_istio
91f8abce6a9e01cbf61c21ba6f1a8412dc9e5adf
link
/test gencheck_istio

integ-security-multicluster-tests_istio
91f8abce6a9e01cbf61c21ba6f1a8412dc9e5adf
link
/test integ-security-multicluster-tests_istio

lint_istio
82a566aada3338215e2827d4be7c74552736018f
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
91f8abce6a9e01cbf61c21ba6f1a8412dc9e5adf
link
/test unit-tests_istio

integ-security-multicluster-tests_istio
91f8abce6a9e01cbf61c21ba6f1a8412dc9e5adf
link
/test integ-security-multicluster-tests_istio

lint_istio
82a566aada3338215e2827d4be7c74552736018f
link
/test lint_istio

gencheck_istio
82a566aada3338215e2827d4be7c74552736018f
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
91f8abce6a9e01cbf61c21ba6f1a8412dc9e5adf
link
/test integ-security-multicluster-tests_istio

lint_istio
82a566aada3338215e2827d4be7c74552736018f
link
/test lint_istio

gencheck_istio
82a566aada3338215e2827d4be7c74552736018f
link
/test gencheck_istio

unit-tests_istio
82a566aada3338215e2827d4be7c74552736018f
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
91f8abce6a9e01cbf61c21ba6f1a8412dc9e5adf
link
/test integ-security-multicluster-tests_istio

lint_istio
82a566aada3338215e2827d4be7c74552736018f
link
/test lint_istio

gencheck_istio
82a566aada3338215e2827d4be7c74552736018f
link
/test gencheck_istio

unit-tests_istio
82a566aada3338215e2827d4be7c74552736018f
link
/test unit-tests_istio

integ-telemetry-k8s-tests_istio
82a566aada3338215e2827d4be7c74552736018f
link
/test integ-telemetry-k8s-tests_istio

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

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


[Presentation] Falco and TAG Environmental Sustainability Partnership

Title

Falco and TAG Environmental Sustainability Partnership
...
Speaker

Melissa Kilby (@incertum) - Falco Core Maintainer
...
Description

Discuss options available

(1) to provide adopters with a self-service option for making informed decisions on configuring and tuning security monitoring in their unique environment -> measure the impact of Falco's resource utilization and ensure transparency in its utilization for production environments.
(2) for tracking Falco's resource utilization between release by leveraging a formal testing infrastructure.

https://github.com/falcosecurity/falco/issues/2435.
https://falco.org/
...
Time

15 min total (presentation only 5 min)
...
Availability

July 19th - 8am PST
...
Steps

[x] First, contact one of TAG ENV
Co-Chairs or TLs to confirm your presentation. You can tag them in this GitHub issue or contact them through the CNCF Slack channel #tag-environmental-sustainability.
[x] Then, add the topic to the Agenda of the upcoming regular meeting in the
meeting notes.
Format: [NAME] Presentation: "<title of your presentation>" <link to this issue>
[x] Post a message in the CNCF Slack channel #tag-environmental-sustainability to inform other TAG ENV members so that they can join!

We are already engaged in a formal discussion

Added to the meeting notes.  I'll put @incertum  as the presenter when we tweet a week ahead, and then with the slack channel as well.  @leonardpahlke  can we do something regarding the event in the calendar for this?

Sure, good idea! Let me open a ticket to change the title of the meeting invitation.
Thanks @incertum 🙌

Thanks for hosting @leonardpahlke cross-posting updates and action items from our tracking issue https://github.com/falcosecurity/falco/issues/2435#issuecomment-1642509056.
Was lovely meeting all of you!

I'm going to close this issue as it relates to a presentation that took place a few weeks ago.


perf: lazy model extras and IPython canary short-circuitry

What I did
perf: evaluates extras lazily
perf: short-circuit during IPython canary check
the combo of these makes it not compile at weird times! people kept saying ape always compiles so much, I think this was the cause.
watch this:
go to ape main branch in an uncompiled projet and launch a console:
ape console

# THEN TYPE `project`
[1] project

it immediately starts compiling the project :[ but why doh
How I did it

first i tried repr in project manager, didnt matter though :/ but it seemed like it helped kinda
then i added the lazy eval for the extras. this is great. now, itll calculate the extras if you ask it to making ape seem a lot faster
finally, what the heck ipython was triggering stuff in Ape it shouldnt have, like compiling, via this canary attribute: https://stackoverflow.com/questions/56068348/what-is-ipython-canary-method-should-not-exist
so to handle this, I short-circuit with what it actually wants. It just wants to make sure we are not saying we have all the full attribute name space because that would crash IPython, so it just wants an attribute error. by raising early, we avoid all the stuff we thought we were to begin with!

for example, when you do project.MyContract, if the contract is not found, Ape will compile the missing sources and then check again. So ape console then typing project, IPython sends this canary message and ape is like "whattttt this aint something i know, but i realize there are uncompiled contracts here so lemme just go away and compile dose and then check again.... ok, i still didnd find _ipython_canary_bullshit_ so ima just raise AttributeError. and then IPython is like "wow thanks, i was just making sure you ain't bat-shit nuts and claiming you have all these random attributes because that would be really bad for me" and then Ape is like "we gooooood"... and so me as a dev is like, why not just formalize our little chat, skip the check for uncompiled sources because we know it aint in there, we have done this every single time we launch ape console for the past 3 years or whatever, so heyyy, performance me upppp. happy friday.

Check this out.
Running from main branch:
In [1]: %time project
CPU times: user 3 µs, sys: 1 µs, total: 4 µs
Wall time: 5.96 µs
Out[1]: INFO: Compiling 'manifest_dependency.json'.
WARNING: Unable to parse ContractType from 'manifest_dependency.json'.
INFO: Compiling 'manifest_dependency.json'.
WARNING: Unable to parse ContractType from 'manifest_dependency.json'.
INFO: Compiling 'manifest_dependency.json'.
WARNING: Unable to parse ContractType from 'manifest_dependency.json'.
INFO: Compiling 'manifest_dependency.json'.
WARNING: Unable to parse ContractType from 'manifest_dependency.json'.
<ape.managers.project.manager.ProjectManager at 0x121f03be0>

WTF
Now, running from this branch:
In [2]: %time project
CPU times: user 3 µs, sys: 0 ns, total: 3 µs
Wall time: 11 µs
Out[2]: <ProjectManager $HOME/PycharmProjects/more_apes/1/ape>


Administrator group role

@jamesrwelch - please see #409
I have checked the user groups and all the testers are assigned to Administrators.
We wanted to use Administrators rather than the administrators. As per Peter's comment on 11 July 2024, would it be possible to fix this, or do we have to use administrators?
Thanks

16/07/2024 - James has changed core Mauro so we can use Administrators. James will ask Peter if he will delete the extra group.


ERROR while running Acoustic pinger_tutorial

Describe the bug
Error with tutorials "Acoustic Beacon".
Error while trying to read acoustic beacon messages.
Getting warning messages while launching the gymkhana_task.
Please say what is broken. Include whether you think this is a problem with the code or the documentation / tutorials.
Expected behavior
I was trying to read the data published by the acoustic sensor.
To Reproduce
Steps to reproduce the problem:

ros2 launch vrx_gz competition.launch.py world:=gymkhana_task
ros2 topic echo /wamv/pingers/pinger/range_bearing

System Configuration:
About my system.

OS: Ubuntu 22.04
ROS Version:  ROS 2, Humble
Gazebo Version: Gazebo Sim 7.0.0
Graphics Card: Nvidia GTX 1650
I am using VRX .

Screenshots

error message
Error_file.txt

Solution:
instead of :
ros2 topic echo /wamv/pingers/pinger/range_bearing
Run:
ros2 topic echo /wamv/sensors/acoustics/receiver/range_bearing


No warning when starting a new project

I had and active project going, then selected "start a new project".  It started without any warning about the previous project.0.
https://user-images.githubusercontent.com/9283127/115442066-35590880-a1d7-11eb-9688-64e1c36f3f27.mov

fixed with commits 3972b57924b4495f8ad217f27c7bf9cf6340a43d, 7a99f0332b4d13dbc1734013aad1cc81584ba95a, and a95456a38cb5075f8d4533b0baf80d6361ab4641


Refresh is not working Properly (Dev)

https://github.com/bithyve/bitcointribe/assets/62699947/bb0f297f-5b8d-4ca4-98ec-c283176a06b5

refresh loader of checking account and Test account doesn't go just keeps rotating.
Also unable to see the transactions in checking account.

It is taking too long to refresh the accounts.
Mostly happening on android device.

Verified this issue on Tribe app v 2.3.0(619)


Use ActionPage to render universities

@schneems this is done now - open to feedback on the API for ActionPage here.

.fm

That would work it looks like it's currently only used for a weird adobe thing https://fileinfo.com/extension/fm .
I didn't know "Front matter" was a thing until you told me though. I think if you explain it in the readme, then it makes sense

After giving it some more thought, I think .yaml is the best way forward because I do want to be able to support (.html.erb.).json and .toml in the future, and I don't think there's as good a way to differentiate those with file hints as there is with file extensions.

Updated gem name to frontmatter


Fails under VS Code

Fails under VS Code complaining about AndroidX. My code works perfectly when file_picker is remover from pubspec.yaml

Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, v1.5.4-hotfix.2, on Microsoft Windows [Version 10.0.17763.475], locale en-GB)
[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[√] Android Studio (version 3.1)
[√] VS Code (version 1.33.1)
[√] Connected device (1 available)

Launching lib\main.dart on F5321 in debug mode...
D8: Program type already present: android.support.v4.os.ResultReceiver$1
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'.

com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives: F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\4.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\5.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\6.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\7.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\8.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\9.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\10.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\11.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\12.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\13.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\14.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\15.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\16.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\17.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\18.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\19.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\20.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\21.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\22.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\23.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\24.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\25.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\26.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\27.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\28.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\29.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\30.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\31.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\32.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\33.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\34.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\35.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\36.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\37.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\38.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\39.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\40.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\41.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\42.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\43.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\44.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\45.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\46.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\47.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\48.jar, F:\flutter-projects\tvmaze\build\app\intermediates\transforms\dexBuilder\debug\49.jar

Program type already present: android.support.v4.os.ResultReceiver$1
Learn how to resolve the issue at https://developer.android.com/studio/build/dependencies#duplicate_classes.

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

Get more help at https://help.gradle.org

BUILD FAILED in 17s

The Gradle failure may have been because of AndroidX incompatibilities in this Flutter app.
See https://goo.gl/CP92wY for more information on the problem and how to fix it.

Gradle task assembleDebug failed with exit code 1
Exited (sigterm)

H. @roidy, this kind of bug is usually related to project dependencies or conflicts between them, otherwise it wouldn't build for any other user. Using the VS Code shouldn't have any impact, it's just the build process.
Can you show me your android/app/build.gradle file? Also, can you try to run the package's example app and see if it builds for you?

I've narrowed the fail down to also including simple_permissions: ^0.1.9 in pubspec.yaml
def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
    localPropertiesFile.withReader('UTF-8') { reader ->
        localProperties.load(reader)
    }
}

def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
    throw new GradleException("Flutter SDK not found. Define location with flutter.sdk in the local.properties file.")
}

def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
    flutterVersionCode = '1'
}

def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
    flutterVersionName = '1.0'
}

apply plugin: 'com.android.application'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"

android {
    compileSdkVersion 28

    lintOptions {
        disable 'InvalidPackage'
    }

    defaultConfig {
        // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
        applicationId "com.example.tvmaze"
        minSdkVersion 16
        targetSdkVersion 28
        versionCode flutterVersionCode.toInteger()
        versionName flutterVersionName
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
    }

    buildTypes {
        release {
            // TODO: Add your own signing config for the release build.
            // Signing with the debug keys for now, so `flutter run --release` works.
            signingConfig signingConfigs.debug
        }
    }
}

flutter {
    source '../..'
}

dependencies {
    testImplementation 'junit:junit:4.12'
    androidTestImplementation 'com.android.support.test:runner:1.0.2'
    androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.2'
}

This line likely explains where the problem is:
Program type already present: android.support.v4.os.ResultReceiver$1

Yes, I saw that as well. So is there a fix?

No problem, I was going to suggest to check your gradle.properties file and make sure that you have these two lines below there:
android.useAndroidX=true
android.enableJetifier=true

Anyway, since you've found a solution, I'm going to close this. Feel free to reopen if you still find any issue related to this.


Opening Ahead/Behind files isn't showing the desire diff (e.g. diff with the merge base)

Earlier there used to be an option to switch between three/two dot comparisons. I can't seem to find that option now (after moving to Source Control tab). It's by default comparing in full-mode.

That option was removed with the change in how the comparison works now -- with the Behind and After groupings.
Is there a particular use case that you are trying to accomplish?

I'm missing this one, too. It's more close to the way Git works, i.e. I'm using the shell:gitlens:bitbucket ui in approximately 1:1:1 fractions, that means I still need to know what gitlens is doing since I need to reproduce it in the terminal, too. By looking at the log I could see that there are still two and three dot comparisons, but it's not that clear anymore from the UI.
Use case is to switch between a "full diff" and a "merge diff", e.g. to check pull requests.

@eamodio I used the three dot diff to perform code reviews. With Gitlens now, if I compare two branches it has sections for Behind and Ahead, and within those sections it shows the changed files within those commits (e.g. 48 files in the Behind section and 15 files in the Ahead section), except if you open the files to see how they were changed it shows a diff with changes from both branches - so you can't tell if the changes were added in the current branch or changes made to the comparison branch (which I'm not code reviewing.)
With winmerge configured as my diff viewer If I run git difftool branchA...branchB then it shows me 15 files that have been changed in branchB. Within winmerge if I open one of those files it only shows changes that have been introduced from branchB's commits - its not showing any changes from the same file that may have occurred in branchA's commits since branchB branched (but if I open that same file from GitLens, as it appears under both the Behind and Ahead file changes it isn't showing the changes from either branch but both branches.)

I used frequently the two/three dot comparison when cherry-picking. A very common use case is when one is developing in a devel branch and wants to cherry-pick a subset of relevant commits that will go in a feature branch which will then be submitted as a PR.
The new comparison mode with behind and after groupings is convenient when merging branches, but is not well suited for cherry picking: it can happen that the diff of a file between the two branches is empty (as per e.g. git diff devel-branch feature-branch my_file.txt), but the new comparison mode still shows the file because the commits are different.
Being able to choose the comparison mode would be a great feature, it is the only thing keeping me from upgrading at the moment to version >= 11.

except if you open the files to see how they were changed it shows a diff with changes from both branches - so you can't tell if the changes were added in the current branch or changes made to the comparison branch (which I'm not code reviewing.)

Same here.
I used the three-dots comparison to code-review changes from a branch that might now be a bit behind.
For the code-review use case Ahead > x files changed would be a good replacement for ..., if the diff was coherent.
Ahead shows the files like diff A...B --name-only would 👍
When you diff a file, showing diff A..B -- somefile.js is incoherent and makes the feature unusable for code review.
Hopefully it's just a temporary bug!

I too used this feature for doing code reviews.
I'm not familiar with the details of the different comparison modes, but I remember switching between them fixed my issues where the changed files in pull requests was not the same as the ones in Gitlens compare. Usually this was to do with the development branch being merged into the feature branch periodically to stay up to date.
Is there a way without changing the compare mode to ignore changes that are from merge commits?

Agree with all comments above. Three-dot comparison is essential for code reviews, so from that perspective the feature is broken. Please please raise the priority of this issue. Thank you for all the hard work Eric!

@jods4 Can you expand upon the diff not being coherent?

When you diff a file, showing diff A..B -- somefile.js is incoherent and makes the feature unusable for code review.

What do you mean by this? Are you saying that when you click on a file under Ahead > x files changed the actual diff is not correct?

Also can anyone give me an example from a repo that shows the desired behavior in GitLens 10 vs the undesired in GitLens 11?

@eamodio
It's just one dot, so it is subtle: the diff of files always uses 2 dots.
The incoherence is that under Ahead you have the file list that is the output of diff A...B --name-only (3 dots) but when you click on a file it's diff A..B (2 dots) that is displayed. What would be coherent is that the same diff command is used in this single context, i.e. that the file diff was three-dots as well, just like the list.
That makes sense because Behind is what you missed from the other branch, i.e. B...A, Ahead is what this branch did, i.e. A...B and the unnamed root category is simply the direct comparison A..B.
Looks like currently the files lists match this behaviour, but when I open the actual file diff it is always 2 dots A..B that is used, no matter where I open it from.
If it worked properly, for me it would be a good enough substitute for the v10 three-dots feature (which was arguably rather obscure to people who aren't very familiar with git).

I've made a change to the x files changed nodes under both Ahead & Behind, now when opening a diff it will be a diff between the merge base and the tip. So x files changed under Behind will now only show changes that were made on the comparee branch, while under Ahead it will only show changes that were made on the comparer branch. While the root x files changes node will continue to be a comparison between the comparee and comparer as it is today.
Can you please verify this fix in tomorrow's insiders edition?
You can install the insiders edition from here. Be sure to disable/uninstall the stable version of GitLens first.

@jods4 @jopotts @fevb @obambrough @jankap @SamBreaksThings Thoughts? 😄

@eamodio I disabled gitlens, reloaded VS Code, installed the insider edition (2020.12.2304) and reloaded VS Code again. I then compared a branch against the master branch but there was no difference in behaviour for the ahead/behind files. If I expand the ahead node and then expand the files changed node and look at one of the files that I know was changed in both branches I am seeing a diff that contains the changes from both branches, not just the changes in the current branch (which is what the triple dot diff would give me.)
e.g.
master/task.py:
   +     if start >= stop:
   +        start = stop - 1

pr-343/task.py:
   + last_time = get_last_time(account_id)
then do the compare of pr-343 with master I only want to see the one line that was changed in that PR but what I see under the ahead/files changed node is:
   -     if start >= stop:
   -        start = stop - 1
   ...
   + last_time = get_last_time(account_id)

This was the same behaviour I was seeing with the regular gitlens (not insiders edition.)

@obambrough Hrm -- what do you get if you run git merge-base --fork-point <ref1> <ref2>, where <ref1> is your branch and <ref2> is master (or whatever 2 branches you are comparing)?

Nothing is returned when I run the git merge-base --fork-point command with the branches in either order. If it helps when I remove the --fork-point mode modifier then it returns the commit that I believe would be appropriate for performing the diff against.

Awesome. Thanks for the info. Should make an easy fix!

@obambrough I pushed the fix to both the latest insiders and the 11.1 stable release.

I tested against the GitLens (Insiders) 2020.12.2400 and it worked great! The ahead/behind files changed nodes provide a diff that shows what changed in the respective branches and the files changed node (that isn't underneath the ahead/behind node) shows a diff between the current HEAD of each branch.
I can't speak for the others but I think this achieves allowing me to perform a code review which is what I used the three dot option for in the older Gitlens version. Thank you!

@eamodio sorry I was on a holiday break.
The new behavior is a perfect substitute for the old three-dots buttons for me.
Thank you and have a great 2021!

@eamodio sorry I was on a holiday break.
The new behavior is a perfect substitute for the old three-dots buttons for me.
Thank you and have a great 2021!

Sorry for the late response, I am also satisfied with the new behavior for the cherry-picking use case I mentioned before. Thank you!

Sorry for the late response, I am also satisfied with the new behavior for the cherry-picking use case I mentioned before. Thank you!


Feature Request: Support for Buildstream (buildstream.build)

Hi, this product is really nice especially since it has an easy configuration to work with. However it runs into some compatibility issues with buildstream (buildstream.build). I figured since there is no issue here yet I'd go ahead and create one. The two issues i've run into and some solutions i've found:

Direct use of nativelink as the artifact cache server fails when buildstream tries to initialize remote caches with:

[--:--:--][        ][    main:core activity                 ] WARNING Failed to initialize remote http://localhost:50051: Remote initialisation failed with status UNKNOWN: FetchBlob: 2: Stream removed

I was able to work around this funny enough by putting a buildbox-casd local cache via
buildbox-casd --cas-remote grpc://localhost:50051 --cas-instance main --bind <IP_ADDRESS>:50052 /tmp/casd

Then it looks like everything was happy

And similar to with buildbarn it runs into this fun shenanigans:

Staging the input root as the filesystem root[](https://docs.buildstream.build/2.3/using_configuring_remote_execution.html#staging-the-input-root-as-the-filesystem-root)

BuildStream requires that the input root given to the remote execution service be treated as the absolute filesystem root.

This is because BuildStream provides guarantees that all build dependencies, including the base runtime and compilers, are defined by elements and run within a sandboxed and isolated build environment, but the [REAPI](https://github.com/bazelbuild/remote-apis) was originally developped without this determinism and control in mind. Instead, typically it is up to the user to configure a cluster to use a docker image to build payloads with, rather than allowing the REAPI client to control the entire sandbox.

Unfortunately the ability to dictate that the input root be treated as the filesystem root in a container on remote workers in the cluster is not yet standardized in the REAPI protocol.

Note

The input root is referred to as the input_root_digest member of the Action message as defined in the [protocol](https://github.com/bazelbuild/remote-apis/blob/main/build/bazel/remote/execution/v2/remote_execution.proto)

This manifests in having permission denied on the work environment since it expects to use absolute paths, One way to address this could be to allow some sort of method to tell nativelink workers to run everything through buildbox-run-bubblewrap or something of the sort.

Thank you for raising the issue. We will prioritize this it internally and revert back.

Thanks! Let me know if there is anything you want me to try, I'm also going to poke around and see what I can find out myself.

Any chance you have a cluster configuration yaml (k8 or docker or something) we can use to debug this?

I used the docker-compose example you have in your repo for my testing and setup buildstream with the following:
~/.config/buildstream.conf
artifacts:
  servers:
  - url: http://localhost:50051 (or cas port)
     type: push
remote-execution:
  execution-service:
    url: http://localhost:50051
  action-cache-service:
    url: http://localhost:50051
  storage-service:
    url: http://localhost:50051

I also used the base usage tutorial for a simplet est project: https://docs.buildstream.build/2.3/using_tutorial.html specifically the running commands hello.c example


Small Warehouse not present on Enbesan Tiers (Shepherds and Elders)

Hi everyone!
As the title says, I noticed that the Small Warehouse is present on every tier, except Shepherds and Elders.

I forgotten to add this one on the tree there, will be fixed next version


in SSR/SST how could work?

Hello!
I am trying to use the plugin with React (as scssModule) to generate bundle which could run with nodejs, I am using ReactDOMServer.renderToStaticNodeStream to render the html.
import styles from './Ping.module.scss';

const Ping() => (<div className={styles.hello} />);

I don't known If I am seeing correctly, but I don't find good option to do that, I mean the (styleModule) document.head.appendChild DOM Injection could not work with NodeJS and the (cssTextModule) export default css either won't work with className={styles.hello}.
So I created an own transform which collect all css text with a custom function addSpecCss if it is exists. Did I see it right, or miss some option which I could do that?
Sample:
const { sassPlugin, postcssModules } = require('esbuild-sass-plugin');

module.exports = {
	createPlugins: (outfile, needCssDef) => {
		const context = { needCssDef };

		return [
			sassPlugin({
				transform: specTransform(context),
			}),
		];
	},
};

const postcssModulesTransform = postcssModules({
	generateScopedName: '[name]__[local]___[hash:base64:5]',
});

const specTransform = (ctx) => async (cssText, resolveDir, filePath) => {
	const transf = postcssModulesTransform.bind(this);

	const out = await transf(cssText, resolveDir, filePath);
	const name = path.basename(filePath);

	parseTransformOut(out, name, ctx);

	return out;
};

function parseTransformOut(out, name, ctx) {
	const selectors = JSON.parse(
		out.contents
			.split('document.head')[1]
			.split('export default ')[1]
			.replace(';', '')
	);

	const css = eval(
		out.contents.replace('const css =', '').split('document.head')[0]
	);

	const cssDef = ctx.needCssDef
		? `typeof(addSpecCss) === "function" && addSpecCss(\`${css}\`);\n`
		: '';

	out.contents =
		cssDef +
		'export default ' +
		out.contents.split('document.head')[1].split('export default ')[1];
}

since v2.9.0 css modules can be rendered into the css that esbuild bundles therefore solving this issue if I got it right...
it should be as easy as just leave the default css type. Feel free to reopen if it's not the case.

@glromeo I'm running into this issue as well migrating from Webpack. To clarify your suggestion, are you saying that rather than inlining, we can just attach the produced CSS?

unfortunately I don't have time to re-create these sort of issues and play with them myself so my answer is purely logical...
but yes, by relying on the bundled css I don't see how you can have problems if it will be served as asset from your server

I see, that's somewhat sub-optimal since if we were publishing a library, it would require asking the user to import the CSS file as well.
That said, for anybody who runs into this in the future- I managed to solve my particular problem via conditional imports


fix replicate 401

The explicit setting of REPLICATE_API_TOKEN with get_env_var() is not working, since the env var is accessed somewhere implicitly during model invocation. We need to go back to set_env_var().
https://github.com/ibm-granite-community/granite-kitchen/blob/main/recipes/Getting_Started/Getting_Started_with_Replicate.ipynb
Also fix the https://github.com/ibm-granite-community/granite-kitchen/blob/main/recipes/Components/Langchain_LLMs.ipynb
Manually propagate the changes to recipes using Replicate in other repos.

PR - merged.

Getting Started with Replicate works on colab
RAG with Langchain works on colab
Text to Shell works in colab


Add logging events to track interactions

We have a use case where we'd like to be able to pull more data out of python-saml, especially to help analyze cases where single sign-on fails for our users. This pull request adds some basic analytical logging at the info level, using the Python standard library's logging module, which is also used in Django and Flask.

https://github.com/onelogin/python-saml/issues/98#issuecomment-207567189

@pitbulk, thanks for the quick reply. I had seen you had mentioned that in the past, but I did want to check to see if your thoughts had changed at all. Specifically because you had mentioned the plethora of different logging systems as a concern, but at this point, both Flask and Django are using the standard library's option. But that's beside the point.
The trick is that for our use case, debug mode isn't a good option for troubleshooting - we need to be able to have a secure pathway to get this information even when running in production. We've also worked with get_last_error_reason() and find ourselves in a situation where we'd love to be able to get more context.
What I'm getting at is, we'd like to work with you on a way to extend python-saml to be able to troubleshoot more thoroughly in a live production state. Obviously, logging isn't something you want in python-saml, so what would be more acceptable to you? One option is that we could possibly create an event emitter that could be subscribed to by passing a callback method. But the specific implementation isn't as important to us as just being able to dig into the raw data that's available when an error occurs.
I'll go ahead and close this PR, but please let me know if you have any thoughts on how we can implement a rich for python-saml that meets your standards.


[WIP] Cypress test. Reset zoom in tag annotation mode

Cypress test. Reset zoom in tag annotation mode
Motivation and context

How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[x] I have updated the license header for each file (see an example below)

# Copyright (C) 2020 Intel Corporation
#
# SPDX-License-Identifier: MIT

Coverage increased (+0.02%) to 63.142% when pulling acb53d952ffb56edacc39a5e6c9407b8868d2253 on DmitriyOparin:upstream/do/cypress_test_issue_2174_reset_zoom_in_tag_annotation_mode into 75d2826a3d35324f3cc1f867fd8d1b8821ef1bce on openvinotoolkit:develop.


Update tsan suppressions to ignore protobuf DebugString and ShortDebugString

What problem does this PR solve?
Issue Number: ref #8285
Problem Summary:
In PR #8499, try add AssignDescriptors to tsan suppression to ignore false positive warnings. However, the tool fails to recognize and ignore some cases(write code is protected by call_once):

What is changed and how it works?
Ignore high level functions: DebugString and ShortDebugString
Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[x] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-all-tests

/run-integration-test


Cannot unset option 'guicursor'

Hi @karb94
Thank you for this great plugin.
Recently I got a problem.
Here is my reproduce steps.

Start nvim
type :help
type <c-f> got error

type :verbose map <c-f>

nvim version
NVIM v0.6.0-dev+162-g2ae9ff128
Build type: Release
LuaJIT 2.1.0-beta3

neoscroll.nvim version: 54879c6957ee5e833924064ff7fc17c144502ae9
Some config from my init.vim
set guicursor=

require('neoscroll').setup({
    mappings = {'<C-u>', '<C-d>', '<C-b>', '<C-f>',
                '<C-y>', '<C-e>', 'zt', 'zz', 'zb'},
    hide_cursor = true,          -- Hide cursor while scrolling
    stop_eof = true,             -- Stop at <EOF> when scrolling downwards
    respect_scrolloff = false,   -- Stop scrolling when the cursor reaches the scrolloff margin of the file
    cursor_scrolls_alone = true, -- The cursor will keep on scrolling even if the window cannot scroll further
    easing = false,              -- easing_function will be used in all scrolling animations with some defaults
    easing_function = function(x) return math.pow(x, 2) end -- default easing function
})

local t = {}
-- Syntax: t[keys] = {function, {function arguments}}
t['<C-u>'] = {'scroll', {'-vim.wo.scroll', 'true', '8'}}
t['<C-d>'] = {'scroll', { 'vim.wo.scroll', 'true', '8'}}
t['<C-b>'] = {'scroll', {'-vim.api.nvim_win_get_height(0)', 'true', '7'}}
t['<C-f>'] = {'scroll', { 'vim.api.nvim_win_get_height(0)', 'true', '7'}}
t['<C-y>'] = {'scroll', {'-0.10', 'false', '20'}}
t['<C-e>'] = {'scroll', { '0.10', 'false', '20'}}
t['zt']    = {'zt', {'7'}}
t['zz']    = {'zz', {'7'}}
t['zb']    = {'zb', {'7'}}

require('neoscroll.config').set_mappings(t)

When I disable neoscroll.nvim, I get no error.
If my config or something wrong, please let me know.
Thanks.

I'm seeing the same behavior.
Disabling neoscroll, the error goes away.
NVIM v0.6.0-dev+163-g599af7451
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /Library/Developer/CommandLineTools/usr/bin/cc<EMAIL_ADDRESS>-I/opt/homebrew/opt/readline/include -I/opt/homebrew/opt/jemalloc/include -I/opt/homebrew/opt/gmp/include -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_TS_HAS_SET_MATCH_LIMIT -O2 -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/Users/jay/repos/neovim/build/config -I/Users/jay/repos/neovim/src -I/Users/jay/repos/neovim/.deps/usr/include -I/Library/Developer/CommandLineTools/SDKs/MacOSX11.3.sdk/usr/include -I/opt/homebrew/opt/gettext/include -I/Users/jay/repos/neovim/build/src/nvim/auto -I/Users/jay/repos/neovim/build/include
Compiled by<EMAIL_ADDRESS>
Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/Users/jay/repos/neovim/build/share/nvim"

Run :checkhealth for more info

My minimal vimrc:
call plug#begin('~/.vim/plugged')
Plug 'karb94/neoscroll.nvim'
call plug#end()

lua <<EOF
require('neoscroll').setup()
EOF

To reproduce:

Open up a file that's long enough to scroll
Scroll with neovim mappings

Does the error disappear if you set termguicolors? I thinkI know where the issue is.

Does the error disappear if you set termguicolors? I thinkI know where the issue is. Unfortunately I don't have access to my computer till Monday so hopefully this temporary fix works for you.

I have already set vim.o.termguicolors = true in my bufferline.lua
The error doesn't disappear.

I have set termguicolors in my full vimrc file and see the issue.

I disable  from mappings ={} and error disappear

@hungrybirder @jaydorsey Is this issue specific to version 0.6? I can see that both of you are using that version and I can't reproduce the issue in version 0.5.

@hungrybirder @jaydorsey Is this issue specific to version 0.6? I can see that both of you are using that version and I can't reproduce the issue in version 0.5.

yes, I'm using v0.6.0-dev+162-g2ae9ff128.
I switch nvim to v0.5.0 and get the same error.

Can you try the latest commit? This is a shot in the dark as I haven't been able to reproduce the issue but it may solve the issue.

Can you try the latest commit? This is a shot in the dark as I haven't been able to reproduce the issue but it may solve the issue.

I use the lastest commit and it works well.
Thank you for fixing this issue. 👍

Fixed the issue for me as well. Thanks!


Double line when code statement is also a hyperlink

Example:

When a code statement is also a hyperlink, that underline (double line) is bothering me a little. 🙈

I'm not sure what even this should look like if this is changed. Any specific thoughts on how else this could be stylized?
@sethmlarson Any opinions on this?

Maybe removing the underline on code block links would be good? I think that's how Github styles things.
example

Nice! I'mma copy GitHub. :)

Didn't remove the underline, but removed the border in 9a59e6e610a30a12d3d1548df13073b49d5c799e.
Looks like this now:  -- see https://pradyunsg.me/furo/demo/demo.html.
Feel free to close this if it looks good. If not, lemme know what you'd say needs tweaking. :)

@pradyunsg I like it! Thank you so much. :)


Export solution to branch directory

Not sure if I have understood the export function. The export function completes and I read in the log that the directory path is: D:../../..solution.zip - however, where is the solution located? Is it uploaded to the specified branch directory, in this case Azure DevOps online? If that is true, I am not seeing it  uploaded to my specified directory.

Hi @MarcusAurelio
This directory is on the build agent VM, not as I suspect you think: into a repo.
This file (which in the screenshot below shows the Solution is being exported at the start of the set of tasks) can then be copied to a directory which in turn can be published as an artifact:

Publish the artifact that includes the solution .zip file:

The artifact can then be used as part of a release, and the deployment task in our case as below is using PackageDeployer as we are deploying both solution and also data:

Hope this helps.
Stephen

@stephenacrown thanks for the clarification :)

Hi @MarcusAurelio
This directory is on the build agent VM, not as I suspect you think: into a repo.
This file (which in the screenshot below shows the Solution is being exported at the start of the set of tasks) can then be copied to a directory which in turn can be published as an artifact:

Publish the artifact that includes the solution .zip file:

The artifact can then be used as part of a release, and the deployment task in our case as below is using PackageDeployer as we are deploying both solution and also data:

Hope this helps.
Stephen

Do you mind explaining how you are moving Portal data? There isn't much documentation on the tools.

Hi @MarcusAurelio
We have two elements to promoting to production via a sort of "clone" phase:

Solutions (to support the portal data)

fully automated for export and deployment

Config and data

manually driven for export only via:

<driveletter>:\ConfigurationMigrationTool\ConfigurationMigration\DataMigrationUtility.exe - yes a manual GUI driven tool in 2018!

automated deployment via <driveletter>:\ConfigurationMigrationTool\PackageDeployment\PackageDeployer.exe

My advice is to get this all working via the GUI tools (export and deploy) in early days to validate the data/config etc. is all working before moving onto this Azure DevOps extension for full pipeline automation.
We are moving data through the (simplified and summarised) phases:

lab environment (experimental/high risk working out how to do things - manually driven)
integration environment (where understood work gets integrated into an environment ready to be "cloned" and Continuous Integration and the partially automated "clone" of the two elements is kicked off)
Test environment(s) (this is the Continuous Delivery part - and covers automated deployment of a new test environment(s), manually (no API yet!) connecting the portal add-on to this new env., and then deploying the solution and data exported from phase 2 (integration) to this environment)
Sign-off/Acceptance environment (fully automated deployment covers automated deployment of a new test environment(s), manually (no API yet!) connecting the portal add-on to this new env., and then deploying the solution and data exported from phase 2 (integration) to this environment assuming earlier testing was successful)
Ring based production deployments with a pause between each customer to understand if the release should proceed

See here for portal data migration:
https://docs.microsoft.com/en-us/dynamics365/customer-engagement/portals/migrate-portal-configuration
Does this help/answer your question?


Fix spelling and replacing some words with better alternatives (pt-BR)

Thanks for the contribution 👍


Determine if error source locations on statements should include semicolon

Currently, we include the semicolon most (all?) of the time

Looks like the rust compiler doesn't, although the line between statement and expression is blurry there

im ok leaving the semicolons


Options arent documented

Options to walk are not documented, looking at code it is not very apparent what they are.

This issue has been mentioned in multiple reports, and it's happening to me as well.
Please add an "Options" section in the README that clearly states all the available options and what they do.
Putting them in the example is great, but does not generally imply that those options are the exhaustive list.

I think he wanted you to fix it yourself and open a PR


[KARAF-4600] RBAC - MBean fails to resolve ACL if the order of properties in object name differs

https://issues.apache.org/jira/browse/KARAF-4600
This fix makes KarafMBeanServerGuard always use the canonical object name when resolving ACL.

See also: https://issues.jboss.org/browse/ENTESB-5775


Tags: wildcard query not supported? 🤷

Describe the bug
The wiql-editor supports Tag queries of the query form ✅
But it doesn't offer any additional capability, on the querying of Tags 😭
Environment:

all

Screenshots

not applicable

To Reproduce

In your Azure Boards project, select the Wiql editor menu nav option
Create a query with the existing capability: AND [System.Tags] CONTAINS 'Release'
But try wildcard and doesn't work: AND [System.Tags] CONTAINS 'Release%'

Expected behavior
Support wildcard for Tag 'contains' queries.
E.g. "Release%" would allow return of all items with Tag starting with 'Release'.
Without this we have to specify each and every Tag instance, which can be excruciating when there are many (dozens or more). I.e. we have Release 1, Release 2, Release 3 on so on ... releasing weekly.
Additional context
The Jira equivalent extension "JQL tricks" supports this, so kinda sets a bar/expectation (justSayin').

I will test the issues and get back to you.

Thanks @AminTi . It's probably an Improvement/Enhancement rather than a Bug, but still, it would add enormous value to have it.  The extension has so much potential 📈.


Update false-positive.md

Fixing formatting.

Thanks, @zeinjaber , but I'm fixing these and a few more issues in a separate PR -- #3679.


Various compatibility fixes

This PR introduces a few compatibility fixes, found while attempting to compile the library on an OSX 12.7.3 system with Apple Clang 14.0.0, linking against libhttpserver 0.19.0.

Update github workflow to latest libhttpserver version
Fix linking against Boost and libhttpserver libraries
Fix return value for render() and render_GET() methods of the file_resource class (libhttpserver 0.19.0 dropped the const modifier)
Fix parsing of returned content (libhttpserver 0.19.0 uses std::string_view here)
Use a C++11-style for-loop in test suite to avoid errors on systems without the C++20 STL.

(Thanks - you made that very easy!)


Add cards widget

It is basically the timeline widget with the timeline removed.
Fixes #54

The current version looks like this with the example site content:

This is fine for my purposes, but I'm interested to hear if you would change anything @negrel

An idea would be to be able to disable the empty space left and right of the cards, and just opting for an X times Y grid of cards.


Missing quest elements

When importing a quest with elements there are two errors:

Elements with a missing description display null. Same is true for organisation members.
Elements that are not linked to entities are not displayed at all,

Quest status icons does not seem to work on 0.9.x


CSV support: tax.crypto.com

That'd be cool to see https://tax.crypto.com support!

Considering tax.crypto.com is the only really free option out there, support would be tremendous.

Okay, I'll try and add it tomorrow.

Deployed tax.crypto.com CSVs to stake.tax.
I believe there's some inherent issues with tax.crypto.com like limited currencies and incorrect restrictions but added best support given limitations.


Better handling of list of IDs when there are more than 50

I found out that when providing more than 50 tracks, the other tracks will be silently ignored:
https://github.com/rinukkusu/spotify-dart/blob/f86276b49510cff05de762ad4c3f1a9f7e3ee1cb/lib/src/endpoints/tracks.dart#L77-L81
Maybe it would be better if we throw an exception instead? WDYT?

Yeah, I am suggesting something like
Future<void> save(List<String> ids) async {
   assert(ids.isNotEmpty, 'No track ids were provided');
   assert(ids.length <= 50, 'Track id length exceeded');
// ...
}

Doesn't assert() only work in development? This means once compiled these asserts will be disabled 🤔
I'm not familiar with the Dart language but I read it here: https://dart.dev/language/error-handling#assert
I would keep this check every time, no matter the env, and I would also explicitly tell about this limit of 50 in the error message so the dev knows exactly why this error happened.

oh okay, I didn't know about this. This also means, that all the other asserts are practically useless, once the library is compiled.
@rinukkusu I wonder now, what the use cases of the assert statements might be if they are ignored. Is it only for debug purposes?
Plus, if we throw exceptions e.g. for empty ids or exceeded ids-length, the users of this library then have to catch them. This would indicate "breaking changes" in the library, which imho I would avoid.
Having this in mind, I would suggest to return a Future.error() with some ArgumentErrors (or we create our own). So something like
Future<void> save(List<String> ids) async {
   if (ids.isEmpty) {
      return Future.error(ArgumentError('No track ids were provided');
   }
   if (ids.length > 50) {
      return Future.error(ArgumentError('Number of track ids exceeds limit of 50');
   }
   // ...
}

@rinukkusu what do you think?

This would indicate "breaking changes" in the library, which imho I would avoid.

No need to completely avoid it. Such change can be done in a new major version (v1).

@rinukkusu I wonder now, what the use cases of the assert statements might be if they are ignored. Is it only for debug purposes?

@hayribakici I don't really remember - I think this is something that got introduced by other collaborators like yourself. 🤔

Having this in mind, I would suggest to return a Future.error() with some ArgumentErrors (or we create our own). So something like

@hayribakici from what I could gather, it looks like returning Future.error(...) and throwing exceptions behave the same. Both can be caught with a try-catch block or in the .catchError(...) method of the Future. That's why I'd vouch for throwing exception objects like ArgumentError directly instead of returning Future.error(...). A little less fluff.
I don't think it's that breaking anyway, since if we don't "protect" from it, in most cases we'll just get an HTTP error then from the Spotify API, if not undefined behavior, right?

@hayribakici I don't really remember - I think this is something that got introduced by other collaborators like yourself. 🤔

tbh, I just went with it 😅

Both can be caught with a try-catch block or in the .catchError(...) method of the Future. That's why I'd vouch for throwing exception objects like ArgumentError directly instead of returning Future.error(...). A little less fluff.

okay, sounds good 👍
@rinukkusu should we create a specific issue for this, that indicates all assert statements?

@hayribakici yeah, a new issue sounds sensible. Thanks!

Closing, since we created another issue for this.


Wired layout behavior maybe caused by release 1.5.2

If use PinLayout, scrolling tableView will be relayout repeatedly and acts wired. Using frame will be fine. I have an issue demo here:  https://github.com/wjling/PinTestDemo1
Since update to 1.5.6，I found many issues in my app except I mentioned above😭, not only transform. I think these layout issues have something to do with 1.5.2 or 1.5.3. Maybe PinLayout changes its mechanism about seting frame or bounds

Hi @lucdion . I want to share my thoughts about the release 1.5.2, only about the transform. I think this release make PinLayout a bit different with manual layout when we apply transforms. If we apply a rotation in a view, we can't use PinLayout to layout its final frame. We should calculate view's layout before we apply rotation, then we use PinLayout. If a view has been rotated, we can't use PinLayout to apply something like top(), marginLeft(3). Because these top(), margin is relative to the status that the view hasn't been transformed. But previous release can. Finally I think PinLayout doesn't do well when there are transforms. It is my feedback after experiencing the changes in 1.5.2. What do you think about my problem?

Hi @wjling, thanks for sharing your tought. Could you share me a sample of your problem?
If I understand correctly, you have a view with a rotated transform, and you'd like to pin it at the top. Your view is non-square?
First think I want to understand correctly the issue, then we could think of different solutions to configure how PinLayout apply layout to its view that contains a transform.
But it could help me a lot if you could just share me a little piece of code that expose this situation.
Thanks

Hi @lucdion .Maybe some pictures can help to explain myself. Sorry about the poor painting😅.
I have picture in a imageView (the red border one):

I perform a 90° rotation on it and I want it to be the same frame, like this:

But PinLayout make it like this:

If a view has applied some transformation, I think is hard to use top(), left() or other constraints to layout it. The reference system has been changed because of transformation. top() or left() is not performing the way we think about it in current reference system.
Maybe you can understand what I say. I also update the demo: https://github.com/wjling/PinTestDemo1

Hi @wjling, thanks for the details.
Since release 1.5.2, PinLayout now respect the view's transform and doesn't modify it. So if for example you have applied a rotation transform, PinLayout will adjust the position and the size of the untransformed view.
In your case you want to update the position/size of the rotated view. But suppose you would like to obtain the PinLayout's result, i.e. keep the rotation transform but change the position and the size of the view, you wouldn't be able by setting the frame property.
This is in fact two different scenarios. I think it requires a mechanism to specify which one we want to use.
I propose to keep's PinLayout current behaviour (I think its easier for animations), but  adds a pinFrame property to really apply the new position/size to the view's frame.
In your example it would replace:
  tableView.pin.top(80).left().right().height(100)

By:
  tableView.pinFrame.top(80).left().right().height(100)

I'm not sure yet about the name pinFrame.
Comments?

Yes, there is two different scenarios. I am in such scenario that I should operate a lot of animations in a view. In this scenario using manual layout maybe less calculation and more understandable than PinLayout.
If we can choose which way of Pin to use in different scenarios could be a nice solution. It will make PinLayout more flexible

Hi @wjling, the following release (https://github.com/mirego/PinLayout/releases/tag/1.5.9) add a pinFrame property.
https://github.com/mirego/PinLayout#uiviews-transforms


Failed to run migrations

I attempted a brew reinstall screenpipe, then ran into a migration error:
➜  ~ screenpipe --audio-device "MacBook Pro Microphone (input)" --self-healing
[2024-08-19T16:08:42Z INFO  screenpipe] Available audio devices:
[2024-08-19T16:08:42Z INFO  screenpipe]   iPhone (119) Microphone (input)
[2024-08-19T16:08:42Z INFO  screenpipe]   CalDigit Thunderbolt 3 Audio (input)
[2024-08-19T16:08:42Z INFO  screenpipe]   MacBook Pro Microphone (input)
[2024-08-19T16:08:42Z INFO  screenpipe]   Universal Audio Thunderbolt (input)
[2024-08-19T16:08:42Z INFO  screenpipe]   ZoomAudioDevice (input)
[2024-08-19T16:08:42Z INFO  screenpipe]   Universal Audio Thunderbolt (output)
[2024-08-19T16:08:42Z INFO  screenpipe]   ZoomAudioDevice (output)
[2024-08-19T16:08:42Z INFO  screenpipe] Using audio devices:
[2024-08-19T16:08:42Z INFO  screenpipe]   MacBook Pro Microphone (input)
[2024-08-19T16:08:42Z ERROR screenpipe_server::db] Failed to run migrations: migration<PHONE_NUMBER>0008 was previously applied but has been modified
Failed to initialize database: Migrate(VersionMismatch(20240808120008))
Error: migration<PHONE_NUMBER>0008 was previously applied but has been modified

Caused by:
    migration<PHONE_NUMBER>0008 was previously applied but has been modified
➜  ~

I just deleted the ~/.screenpipe dir and tried again. Worked fine.


Port First Application Version to /develop

Completed on call Feb 19/22. Tested and working one everyone's platform.


Cache Rainloop

i am currently trying to develop plugins for rainloop which is a nightmare...
i am having trouble with th apps cache. When i change html code for example...and consequently refreshing the browser the changes do not take immediate effect.
could you please help?

./data/_data_/.../configs/application.ini
[labs]
cache_system_data = Off

Thank you

@Agustors may I ask the purpose of your plugin? I am thinking of writing a wrapper to include a calendar. Maybe we can join forces?
Regards
Stephan
#1275


CIV-7154 Set Up camunda

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/CIV-7154
Change description
Sending Mediation data as CVS
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

Please can you upload before and after screenshot. looking at the file - feels like you are introducing a bug to a live functionality


[Issue] No baseline for 15.1.845.39

There is no baseline file for 15.1.845.39 available, which results in numerous "NoHashMatch" entries in the result CSV when executing CompareExchangeHashes.ps1

Created a single task for tracking all missing baselines, please follow: https://github.com/microsoft/CSS-Exchange/issues/313


[Profile] Deprecate --sdk-auth

Description
Rework https://github.com/Azure/azure-cli/pull/17362
Because consumers of the JSON output - Azure SDKs has deprecated the usage of get_client_from_json_dict (https://github.com/Azure/azure-sdk-for-python/issues/15075), Azure CLI should deprecate --sdk-auth as well.
It will be totally removed after MSAL migration (https://github.com/Azure/azure-cli/issues/18944).
Reference email: Deprecate generating JSON auth file in Azure CLI
History Notes
[Profile] az account show: Deprecate --sdk-auth
[Role] az ad sp create-for-rbac: Deprecate --sdk-auth

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Profile


MainRemote reads files too soon

That's why sometimes the file content is empty

@rultor release, tag is 0.23.1

@rultor release, tag is 0.23.1

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.23.1

@yegor256 Done! FYI, the full log is here (took me 10min)


refactor(selection-panel): improved open/close flow and animation

This PR aims to solve the problems relative to the open/close events emitted by the selection-panel.
We have received no complaints, so I expect nobody is using them so far.
Might solve #2309
Changes

Converted the open/close animation from css-transition to css-animation. CSS animation provides a more consistent behavior and always emits animationend events.
Refactored the code so that we have a single method that takes care of checking the state and to open/close the panel

To discuss

Should a panel that uses force-open emit events?
Should a panel that uses force-open animate?

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (main@331bac3). Click here to learn what that means.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2360   +/-   ##
=======================================
  Coverage        ?   93.60%
=======================================
  Files           ?      222
  Lines           ?    23269
  Branches        ?     2072
=======================================
  Hits            ?    21781
  Misses          ?     1451
  Partials        ?       37

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

Now there is an initial animation which should not be there (compare to current version).
Should a panel that uses force-open emit events? -> In my opinion yes, you don't have to listen to it if you don't care ;) Should a panel that uses force-open animate? -> no

I will clarify the current and past situation.
Before the update:

No animation on init (by looking at the code, it seemed not intentional but just a happy outcome)
force-open did animate (except if it was initialized with it)
events were always emitted (there were some broken cases where it would only emit the willOpen)

I suggest that we keep the same behavior, so:

No animation on init
force-open does animate (except if init with it)
events always emitted

@jeripeierSBB what do you think?

Now there is an initial animation which should not be there (compare to current version).
Should a panel that uses force-open emit events? -> In my opinion yes, you don't have to listen to it if you don't care ;) Should a panel that uses force-open animate? -> no

I will clarify the current and past situation.
Before the update:

No animation on init (by looking at the code, it seemed not intentional but just a happy outcome)
force-open did animate (except if it was initialized with it)
events were always emitted (there were some broken cases where it would only emit the willOpen)

I suggest that we keep the same behavior, so:

No animation on init
force-open does animate (except if inited with it)
events always emitted

@jeripeierSBB what do you think?

@TomMenga sounds good to me


specify verification callbacks for schannel

adds a trait in the connectorBuilder that allows users to specify a
verification callback to use in the event that a new connection's
validation fails

Just a random thought, that's in my oppinion worth thinking about:
Wouldn't it be better to expose a generic ValidationCallback (non-schannel) specific here?
This could have a raw_callback (similar to raw_stream) which would return
a schannel::CertValidationCallback for schannel
(AFAIK rust-openssl also already has such a callback?).
Additionally one could abstract CertChain/Certificate later on top of it,
which would allow a unified callback interface in the long term.
Just a thought though, @sfackler thoughts?

@steffengy Oh yeah, that's definitely the right approach for most users. We're just doing this first because it's a good thing to have around in any case, and creating the high level interface will require some somewhat nontrivial API work. These low-level accessors are here for things that the high-level API doesn't yet support, and to give people more power than the high-level APIs offer when they do exist.


Send output item data as VSBuffer

Currently output items send data as number array. That's not ideal and use send things a VSBuffer for which the IPC layer is fast. This is a bigger change because it requires to stop using IOutputItemDto from extHost.protocol.ts

kinda blocked by https://github.com/microsoft/vscode/issues/125668

@jrieken even the current output data array is chopped off: https://github.com/RandomFractals/vscode-data-table/issues/30#issuecomment-886771648
would be nice to be able to read raw binary data from cell output.

I looked into this a little since I'd done something similar for webviews. I think there are two potential approaches to optimize NotebookOutputItemDto:
Pass the the output data buffers as top level arguments to ipc calls
For any ipc call that deals with an cell output, pass the list of output VSBuffers as top level arguments:
$tryApplyEdits(editorId: string, modelVersionId: number, cellEdits: ICellEditOperationDto[], ...outputBuffers: VSBuffer[]): Promise<boolean>

This ensures that they are efficiently serialized by our existing ipc implementation
Then for NotebookOutputItemDto, we use a reference to tell us which output buffer from the list of buffers to use:
export interface NotebookOutputItemDto {
	readonly mime: string;
	readonly bufferIndex: number;
}

Making this change is sort of a pain because it requires updating a lot of to/from conversation functions to take an array of output buffers
Add ipc support for efficiently serializing VSBuffers inside of objects
First  update NotebookOutputItemDto to use a VS Buffer
export interface NotebookOutputItemDto {
	readonly mime: string;
	readonly buffer: VSBuffer;
}

On its own, this would result in the buffer being very inefficiently serialized. So we'd also need update our IPC implementation to deeply detect and VSBuffers inside of passed in arguments and then serialize them more efficiently
This efficiently serialization would likely be similar to what we do for webviews:

While serializing the arguments, walk each object to extract all buffers and replace them with references (just indexes into the list of extracted buffers)
The write the serialized object and buffers to the wire
On the receiving side while deserializing objects, walk though them again and replace all buffer references with the corresponding buffer

I feel this approach is probably better since it not specific to notebooks. However I'm not sure if it would significantly degrade performance for all ipc calls. I believe we already walk objects during serialization/deserialization to handle URIs so it may be ok. We could also make the behavior opt-in and only enable it for specific calls that need it

I have not looked at what constitutes a VSBuffer. Would it be possible to instead use application/octet-stream mime type for cell outputs with binary data, and allow renderers to read them with a standard ReadableStream? See Using Readable Streams
I liked that current cell output API exposes blob(), but I was not able to read the whole data blob either in my tests.


fix possible data race in pkg/fs

part of #3523

Codecov Report
Patch coverage has no change and project coverage change: -31.58 :warning:

Comparison is base (11bac39) 56.47% compared to head (53e90bf) 24.90%.

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #3524       +/-   ##
===========================================
- Coverage   56.47%   24.90%   -31.58%
===========================================
  Files         149       24      -125
  Lines       36323    14124    -22199
===========================================
- Hits        20514     3517    -16997
+ Misses      13552    10227     -3325
+ Partials     2257      380     -1877

see 146 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Please modify only the code that is necessary, and use another standalone PR if you want to do some style refactor.

fixed, please take another look