make file debounce duration configurable

In some baremetal cases we are seeing it is taking lot more time to write both key and certs. So making this configurable.

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[X] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[X] Does not have any user-facing changes.

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.

@ramaraochavali: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

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

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

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

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

release-test_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test release-test_istio

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

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

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

release-test_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test release-test_istio

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

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

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

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

release-test_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test release-test_istio

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

unit-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
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.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

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

release-test_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test release-test_istio

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

unit-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test unit-tests_istio

analyze-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test analyze-tests_istio

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

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

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

release-test_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test release-test_istio

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

unit-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test unit-tests_istio

analyze-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test analyze-tests_istio

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

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

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

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

release-test_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test release-test_istio

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

unit-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test unit-tests_istio

analyze-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test analyze-tests_istio

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

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

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

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

release-test_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test release-test_istio

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

unit-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test unit-tests_istio

analyze-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test analyze-tests_istio

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

lint_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test lint_istio

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

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

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

release-test_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test release-test_istio

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

unit-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test unit-tests_istio

analyze-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test analyze-tests_istio

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

lint_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test lint_istio

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

integ-helm-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test integ-helm-tests_istio

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

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

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

release-test_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test release-test_istio

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

unit-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test unit-tests_istio

analyze-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test analyze-tests_istio

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

lint_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test lint_istio

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

integ-helm-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test integ-helm-tests_istio

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

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

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

release-test_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test release-test_istio

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

unit-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test unit-tests_istio

analyze-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test analyze-tests_istio

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

lint_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test lint_istio

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

integ-helm-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test integ-helm-tests_istio

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

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

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

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

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

release-test_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test release-test_istio

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

unit-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test unit-tests_istio

analyze-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test analyze-tests_istio

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

lint_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test lint_istio

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

integ-helm-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test integ-helm-tests_istio

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

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

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

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

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

release-test_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test release-test_istio

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

unit-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test unit-tests_istio

analyze-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test analyze-tests_istio

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

lint_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test lint_istio

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

integ-helm-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test integ-helm-tests_istio

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

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

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

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

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

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

release-test_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test release-test_istio

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

unit-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test unit-tests_istio

analyze-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test analyze-tests_istio

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

lint_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test lint_istio

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

integ-helm-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test integ-helm-tests_istio

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

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

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

gencheck_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test gencheck_istio

integ-istiodremote-k8s-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test integ-istiodremote-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.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

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

release-test_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test release-test_istio

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

unit-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test unit-tests_istio

analyze-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test analyze-tests_istio

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

lint_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test lint_istio

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

integ-helm-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test integ-helm-tests_istio

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

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

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

gencheck_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test gencheck_istio

integ-istiodremote-k8s-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test integ-istiodremote-k8s-tests_istio

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

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

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

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

release-test_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test release-test_istio

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

unit-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test unit-tests_istio

analyze-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test analyze-tests_istio

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

lint_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test lint_istio

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

integ-helm-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test integ-helm-tests_istio

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

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

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

gencheck_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test gencheck_istio

integ-istiodremote-k8s-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test integ-istiodremote-k8s-tests_istio

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

release-notes_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test release-notes_istio

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

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

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

release-test_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test release-test_istio

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

unit-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test unit-tests_istio

analyze-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test analyze-tests_istio

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

lint_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test lint_istio

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

integ-helm-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test integ-helm-tests_istio

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

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

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

gencheck_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test gencheck_istio

integ-istiodremote-k8s-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test integ-istiodremote-k8s-tests_istio

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

release-notes_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test release-notes_istio

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

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

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

release-test_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test release-test_istio

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

unit-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test unit-tests_istio

analyze-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test analyze-tests_istio

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

lint_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test lint_istio

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

integ-helm-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test integ-helm-tests_istio

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

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

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

gencheck_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test gencheck_istio

integ-istiodremote-k8s-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test integ-istiodremote-k8s-tests_istio

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

release-notes_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test release-notes_istio

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

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

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

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

release-test_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test release-test_istio

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

unit-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test unit-tests_istio

analyze-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test analyze-tests_istio

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

lint_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test lint_istio

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

integ-helm-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test integ-helm-tests_istio

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

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

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

gencheck_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test gencheck_istio

integ-istiodremote-k8s-tests_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test integ-istiodremote-k8s-tests_istio

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

release-notes_istio
f8693a56ae2f3dfc4d935a61e1be8ed16480188b
link
/test release-notes_istio

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

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

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

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

In response to a cherrypick label: #34738 failed to apply on top of branch "release-1.9":
Applying: make file debounce duration configurable
Using index info to reconstruct a base tree...
A	pilot/cmd/pilot-agent/options/agent.go
A	pilot/cmd/pilot-agent/options/options.go
A	pilot/cmd/pilot-agent/options/security.go
M	pkg/security/security.go
M	security/pkg/nodeagent/cache/secretcache.go
Falling back to patching base and 3-way merge...
Auto-merging security/pkg/nodeagent/cache/secretcache.go
Auto-merging pkg/security/security.go
CONFLICT (content): Merge conflict in pkg/security/security.go
CONFLICT (modify/delete): pilot/cmd/pilot-agent/options/security.go deleted in HEAD and modified in make file debounce duration configurable. Version make file debounce duration configurable of pilot/cmd/pilot-agent/options/security.go left in tree.
CONFLICT (modify/delete): pilot/cmd/pilot-agent/options/options.go deleted in HEAD and modified in make file debounce duration configurable. Version make file debounce duration configurable of pilot/cmd/pilot-agent/options/options.go left in tree.
CONFLICT (modify/delete): pilot/cmd/pilot-agent/options/agent.go deleted in HEAD and modified in make file debounce duration configurable. Version make file debounce duration configurable of pilot/cmd/pilot-agent/options/agent.go left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 make file debounce duration configurable
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to a cherrypick label: new issue created for failed cherrypick: #34750

In response to a cherrypick label: #34738 failed to apply on top of branch "release-1.10":
Applying: make file debounce duration configurable
Using index info to reconstruct a base tree...
M	pilot/cmd/pilot-agent/options/agent.go
M	pilot/cmd/pilot-agent/options/options.go
M	pilot/cmd/pilot-agent/options/security.go
M	pkg/security/security.go
M	security/pkg/nodeagent/cache/secretcache.go
Falling back to patching base and 3-way merge...
Auto-merging security/pkg/nodeagent/cache/secretcache.go
Auto-merging pkg/security/security.go
CONFLICT (content): Merge conflict in pkg/security/security.go
Auto-merging pilot/cmd/pilot-agent/options/security.go
Auto-merging pilot/cmd/pilot-agent/options/options.go
Auto-merging pilot/cmd/pilot-agent/options/agent.go
CONFLICT (content): Merge conflict in pilot/cmd/pilot-agent/options/agent.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 make file debounce duration configurable
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to a cherrypick label: new issue created for failed cherrypick: #34751

In response to a cherrypick label: #34738 failed to apply on top of branch "release-1.11":
Applying: make file debounce duration configurable
Using index info to reconstruct a base tree...
M	pilot/cmd/pilot-agent/options/options.go
M	pilot/cmd/pilot-agent/options/security.go
M	pkg/security/security.go
M	security/pkg/nodeagent/cache/secretcache.go
Falling back to patching base and 3-way merge...
Auto-merging security/pkg/nodeagent/cache/secretcache.go
Auto-merging pkg/security/security.go
CONFLICT (content): Merge conflict in pkg/security/security.go
Auto-merging pilot/cmd/pilot-agent/options/security.go
Auto-merging pilot/cmd/pilot-agent/options/options.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 make file debounce duration configurable
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to a cherrypick label: new issue created for failed cherrypick: #34752


[doc] Issue in "Components Versions"

Components Versions:
https://documentation.suse.com/suse-edge/3.0/html/edge/id-release-notes.html#id-components-versions-3
Add an explanation what entries being boldfaced means. I'm assuming it means the component version has changed but this isn't explicitly mentioned anywhere as far as I can see.

This was fixed via https://github.com/suse-edge/suse-edge.github.io/pull/364


useRefinementList not working as expected on a geopoint field

Description
The refine method on a geopoint field is giving an error.
Steps to reproduce
const { refine } = useRefinementList({ attribute: 'location_geo' });
// Tried the below
refine('(-44.50, 170.29, 20 mi)')

Expected Behavior
It should be able to refine results with lat, long and radius.
Actual Behavior
The error is
Error: 400 - Value of filter field location_geo: must be in the ([-44.50, 170.29], radius: 0.75 km, exact_filter_radius: 5 km) or ([56.33, -65.97, 23.82, -127.82], exact_filter_radius: 7 km) format.
Metadata
Typesense Version: 0.26.0.rc25
OS: Ubuntu
Ref: https://typesense-community.slack.com/archives/C01P749MET0/p1698234116317759

Hi! any eta on this issue?

Hi! any eta on this issue?

Hey, I ended up using this to get my use case working. Doesn't look like refinement lists work with geopoint fields.

Hi! any eta on this issue?

Hey, I ended up using this to get my use case working. Doesn't look like refinement lists work with geopoint fields.

Thank you very much.
I use this temporary solution for now:
const finalLocation = location ? location : undefined;
const finalRadius = finalLocation ? radius * 1000 : undefined;
<InstantSearch searchClient={searchClient} indexName={'candidats'}>
  <Configure
    aroundLatLng={finalLocation}
    aroundRadius={finalRadius}
  />

finalLocation:  45.5764258, -73.5466107
finalRadius:  75000

Hi! any eta on this issue?

Hey, I ended up using this to get my use case working. Doesn't look like refinement lists work with geopoint fields.

Thank you very much.
I use this temporary solution for now:
const finalLocation = location ? location : undefined;
const finalRadius = finalLocation ? radius * 1000 : undefined;
<InstantSearch searchClient={searchClient} indexName={'candidats'}>
  <Configure
    aroundLatLng={finalLocation}
    aroundRadius={finalRadius}
  />

finalLocation: 45.5764258, -73.5466107 finalRadius: 75000

Yeah, I had tried the configure widget as well. That's good to apply the initial filter, but when the values change dynamically from the FE it wasn't filtering then, but the initial filter was working well with the Configure widget.


运行WOE  OOM  失败的问题

Issue Type
Running
Search for existing issues similar to yours
Yes
OS Platform and Distribution
Linux 20.04.1-Ubuntu
Kuscia Version
kuscia 0.8.0b0
Deployment
docker
deployment Version
Docker version 24.0.5
App Running type
secretflow
App Running version
secretflow  1.6.1b0
Configuration file used to run kuscia.
mode: autonomy
domainID: p208
domainKeyData: LS0tLS1CRUdJTiBSU0EgUFJJVkFURSBLRVktLS0tLQpNSUlFb3dJQkFBS0NBUUVBelRMK2paWEVneHNleTB2L1YyM0VnV0pHODBhNSt6WTBRZDduNHBKajNmR2JCK2w4Cit6aFhUbWw5YVRic04zQnIrSHZsRkJxMlJLTjNjalNrcVgyaXVPL0Joc0puNWJNVVA1RTBVMlBnSXlvQ3JFSmUKK3dGUFJoSVRPNS9sMFVUejFORFRSc0NLUXd2K0tkb3I4SGppbklaR0Q0V1V3cVdFMUdtNGhwb3oxcXBZU2gzVQp1dDRjRUtseWxOVG1nZUJaRTZjWVFMaHp4VlVzT0VxV2thejdqS3p1VlRtczRUUEZCdEV3dU1ZL1ZoVkM3RE5XCkkyWHpaY2k2ektmdkN1OTVabUVJY0ZzdlY2ZVJTYVJSeWpZS2l6NVlXVm8wcmRyaUkvSkcwVEl6eFdKSlJOT1EKbjJVL2hubUd4THlYZExXb0wvNkZ1cjJ4a0tBVnpsZDJCeVFJTFFJREFRQUJBb0lCQUI4R2g5QjJoWmpoSDkzVApKczljVEdyWHBpeWdVL3gwcktBTkNQaUw4OGVhQVR2SUJOcWpJU2c4OFBaWWxJeXBWZG5qT2JhNWR6ZVhrN2JUCjJOVzdwai9hR0dPOHZ5TE8yYy9tcjRld1FUSnY1cW1PKzNkdU1rTkE5bUY4Z3E0S2crZDRqNGxTRVZXajJaRVEKYUxaYVFNRXoyQ0grcTRobXFGZkppRm5wdE03Tyt3UzhmYytxMTR4NXJsRUFkdkVpdGozSkZNblNZd3E3T2RWOQo5S0kvc3p1bzBDYkZ0OXBWV3R5eWt3d3VVWlpFZnorS3NoSlRwTkpTUWV3OFJzcEpyaENrRFFEam1CR2FMeHRzClYzQjE1Z2pqdmlQa28wS1VPMituVUhGdG1FaGltMHMzazNBeFVmZG80YkVLWEZoMzM1dlJKOVRUa2FvbEZVdTMKYkRjUFFFMENnWUVBLzN0OFV3MmYzZnE5WHRkTjZxMnNSYTZIYTRjVnNBRi9BVUx5Q2JhTDY4QUVoZnRkcGF2bApJVEg0ZUFkTmxzMlBSUFpIUFh0ZnRqT2JwRk4ydnJvSUZhc043THREcjVrN215cUZMWG9KUUZQZXFtaFdXR3BUCjBnbElEaVY2akI0Z1BCcHZtWGNVelVrSE5iSGoyY2M0RVRQR2NRdkc5RzdNem11N1pIVUxjZThDZ1lFQXpaMXQKZklGdmpsOTRBV0U1WUdPelZHaTdlS3QvM1hFb1NIR0thS0UvK1ZCSlZ0OFJrWE5VOXVwdTlZcU4zL3h4ZmRGSwpIc2RZQjNXN25SejdSUzBjTC9uS2ViK3JNd2pMWU1EUDI0UFdJRTNvWDBoeVlRWldYUVNvN1ZlZmlFcEJKODVlCmhlMmZoZndxU1N1TExJcGdBYkV6TlFEdG9kVHlVajI1Y2VXMlU2TUNnWUJUblUybVBQcEtnMHJCSklRcXYyWjMKYzlSOFc3eThXdkQvTDdMWmZQWTBWU2JsMXN2aWNlek92WFVOaTQ1WVFiU1hKR2RTZHZOdlJWcTJJRjduc3lqOApObnliTXZySEdNYUtWUk03UEFxVkZCMzI5YWowek8vYitRK3RHWlVQRUxrS0VyamRxRHlWcDBZRnk4Ky9zZFRtCnhHUTVFVnF2R3loS2tyWEUvZzJkM3dLQmdGTFh1L1l2SEdoTGxNbFJoOUdMT2dTblVlbFRoK2dMb0lSWG9zRjMKUHBSUHdjekxnWU9ONlV5MnRkQWVhLzB6OC9JU2NmK21wNVFSM201MTc5TTJVcVlOeVlOMk14OFR5d1dIaWZmUwp6V0lrb1p4S1R6TkNYMmVJNmhyK2M5dHd0NEczUnlSRTBrSWtrRkQ4eDAxQnoxNi9LM2VPa1MvajRXSTdWazFLCmxVUnJBb0dCQUovNnE4ZkhkNlZvYUlDQXhMM0grcmRUQ254bUxiTVV1ZUc3c3dmb29BdVo2UU5TNzIvM3VoRG4KY1g1R3c1Q3FXYTRqMTlJdG9CWEdGZXBMbHhoUSt6eG52YWM3cGVrRG1vY3Rham9RcVVqMEtKOVNKL09GQW56RwpRaEd6L0NnZTRkbm90MjNJMVZMRnpRNkorMkZnNDRRTEJPS3cvZXNkeWpmU3Rod1NXYTQ1Ci0tLS0tRU5EIFJTQSBQUklWQVRFIEtFWS0tLS0tCg==
logLevel: INFO
runtime: runc
runk:
  namespace: ""
  dnsServers: []
  kubeconfigFile: ""
capacity:
  cpu: ""
  memory: ""
  pods: ""
  storage: ""
image:
  pullPolicy: ""
  defaultRegistry: ""
  registries: []
datastoreEndpoint: ""

What happend and What you expected to happen.
我点对点部署了kuscai，使用其api进行WOE分箱任务，希望运行成功；在较小数据量的情况下可以运行成功，然而当我将数据量提升到50W*450维时运行却不成功了，在运行过程查看我的内存有很多的空闲，但还是报了OOM。

Kuscia log output.
详见文件

机器资源状况：

Kuscia log：
Uploading p207.log…
Uploading p208.log…

p207.log
p208.log

kuscia API的调用参数和测试数据可以发一下吗？

通过命令docker update --memory 32g --memory-swap 40g 增加了容器的可用内存，同时使用了heu设备，重新运行该任务在data目录有结果数据产生，但在日志还是报错：status = StatusCode.RESOURCE_EXHAUSTED
2024-06-26T11:42:04.915790123+08:00 stderr F 	details = "grpc: received message larger than max (4598659 vs. 4194304)"
2024-06-26T11:42:04.915792996+08:00 stderr F 	debug_error_string = "UNKNOWN:Error received from peer ipv4:<IP_ADDRESS>:8071 {grpc_message:"grpc: received message larger than max (4598659 vs. 4194304)", grpc_status:8, created_time:"2024-06-26T03:42:04.914109278+00:00"}"；看上去是grpc的消息大小限制了传输，下面是完整的日志文件：
p208.log
p207.log

kuscia API的调用参数和测试数据可以发一下吗？

目录里面是有一个bin-rule的文件，但通过api查询任务状态是失败的，所以也不知道结果是不是正确的

通过命令docker update --memory 32g --memory-swap 40g 增加了容器的可用内存，同时使用了heu设备，重新运行该任务在data目录有结果数据产生，但在日志还是报错：status = StatusCode.RESOURCE_EXHAUSTED 2024-06-26T11:42:04.915790123+08:00 stderr F details = "grpc: received message larger than max (4598659 vs. 4194304)" 2024-06-26T11:42:04.915792996+08:00 stderr F debug_error_string = "UNKNOWN:Error received from peer ipv4:<IP_ADDRESS>:8071 {grpc_message:"grpc: received message larger than max (4598659 vs. 4194304)", grpc_status:8, created_time:"2024-06-26T03:42:04.914109278+00:00"}"；看上去是grpc的消息大小限制了传输，下面是完整的日志文件： p208.log p207.log

能够解除这个grpc通信量的设置吗

通过命令docker update --memory 32g --memory-swap 40g 增加了容器的可用内存，同时使用了heu设备，重新运行该任务在data目录有结果数据产生，但在日志还是报错：status = StatusCode.RESOURCE_EXHAUSTED 2024-06-26T11:42:04.915790123+08:00 stderr F details = "grpc: received message larger than max (4598659 vs. 4194304)" 2024-06-26T11:42:04.915792996+08:00 stderr F debug_error_string = "UNKNOWN:Error received from peer ipv4:<IP_ADDRESS>:8071 {grpc_message:"grpc: received message larger than max (4598659 vs. 4194304)", grpc_status:8, created_time:"2024-06-26T03:42:04.914109278+00:00"}"；看上去是grpc的消息大小限制了传输，下面是完整的日志文件： p208.log p207.log

能够解除这个grpc通信量的设置吗

暂时不支持设置的。
问题原因是：woe 分箱产生的report文件太大了，超过了 4M，目前grpc 最大的数据传输量是 4M。
解决方式：
1.可以将数据维数改小一点试下
2.可以通过二开kuscia来修改传输量大小限制，在此处上方增加opts = append(opts, grpc.MaxRecvMsgSize(1010241024))，尝试一下


Modify QNX NTO platform support

Modify QNX NTO dl_iterate_phdr to toke * mut. All other platforms use * mut, and while this is technically a breaking change, most likely noone is using it directly.
NTO does not define last four fields of the dl_phdr_info, so might as well exclude them for cleanliness.
v7.0: link
v7.1: link
v8.0: link
See also https://github.com/rust-lang/backtrace-rs/pull/648
r? @joshtriplett

Can you change this to target main? We can cherry-pick from there.
@rustbot label +stable-nominated

Thanks for the separate PR, this can be closed now since I will cherry pick that commit directly once it merges.

Closing as superseded by https://github.com/rust-lang/libc/pull/3815


Use pathway descriptions

Set pathway descriptions for each pathway

I'm asking for a review request on our WikiPathways fork before opening a pull request to the SuLab repo. For future pull requests, I'll probably make them directly to the SuLab repo.


Add requires-python option to the project config

Problem statement
Since we deprecated Python 3.8 in #473, we should set the minimal Python version that wrapanapi requires in its project settings.
Solution
Add requires-python option to pyproject.toml and set it to 3.9+.

@mshriver Is it enough to add only requires-python? I can also add classifiers.

requires-python is the important one, IIRC pip won't even list it if you're on an older version of python.


RHEL 9.2 uses LVM 2.03.17 please update

Describe the Enhancement:
RHEL 9.2 uses LVM 2.03.17
Describe the Need:
Support for latest LVM
Current Alternative
No
Can We Help You Implement This?:
Update latest version support

rpm -q lvm2
lvm2-2.03.17-7.el9.x86_64

Unable to load lvm attributes [lvs.yaml] for version [2.03.17(2)]. The version/object may not be supported or you may need to upgrade the chef-ruby-lvm-attrib gem

Waiting on this update also? Thanks!

I have created PR for this today:
https://github.com/sous-chefs/chef-ruby-lvm-attrib/pull/53
I hope someone will merge it soon

closing this as completed with #53


Options param support for create method

Fix for #25

Thanks @rafalszemraj. Ideally we'd want to test for this. Since this is a such a benign change I'll add it and we can go back an add a specific test for passing options to Sequelize.

I've publish v1.1.3 that contains this fix.

I'm not sure if this is the best fix.There is a chance that you can mess directly with the database by passing arbitrary query parameters from the client.
Instead of using params directly it should probably use params.sequelize to set those options.

@daffl Probably you're right. The reason I wanted to have this was to be able to create records with n:m association . I'm just starting with feathers and I can see that relation model form sequelize is not yet provided (maybe you do not have any plans to do so?). Anyway, starting this with change like this it's not best idea I guess - whole thing needs to be planned beforehand. I can leave without that, you can revert that if you do not feel this is right way to do it.

 I missed that. Good catch @daffl. I think we should roll this change back then. Looks like we are missing documentation on the params.sequelize object and we really need an example of showing many-to-many relationships.

No need to roll it back, this is a good fix. We just need to change https://github.com/feathersjs/feathers-sequelize/blob/master/src/index.js#L83-L89 to
  create(data, params) {
    const options = params.sequelize || {};
    if (Array.isArray(data)) {
      return this.Model.bulkCreate(data, options).catch(utils.errorHandler);
    }

    return this.Model.create(data, options).catch(utils.errorHandler);
  }

Then one can set params.sequelize to whatever it needs to be e.g. in a before hook.

Ah ok cool. I'll fix that right away and do a new patch release.

@rafalszemraj I hope that works for you as well and many thanks again for the PR!

:+1:


Add test-clang-format github action

This currently uses the clang-format lint action from DoozyX/clang-format-lint-action with clang-format version 6 as this was the version I was using on my laptop and version 9 formatted a few things differently. I've currently set it to only run on pull requests.

I'm merging this now, then we can test it out on my pull request :-)

Ah, sorry, I just saw that @draenog was tagged for review... Hopefully its ok that I merged it. It should not break anything, and would be easy to revert.


updaing providers list

Strange, it still treats is as binary :(

@davidebbo yup, I just sent you an Email about that, will have to look further.

PowerShell scripts default to UTF-16 when saved from ISE for some reason. There may be more to this.  I changed the script to generate utf8 and regenerated the latest.

Thanks @davidebbo


OCPBUGS-43823: Rebase to upstream v1.31.1 for OCP 4.18

Issue link:
https://issues.redhat.com/browse/OCPBUGS-43823
Diff to upstream v1.30.4:
https://github.com/kubernetes-sigs/azuredisk-csi-driver/compare/v1.30.4...dfajmon:rebase-v1.31.1
Changes between v1.30.4 (OCP 4.18) and v1.31.1 (OCP 4.18):
v1.30.5

https://github.com/kubernetes-sigs/azuredisk-csi-driver/pull/2549

v1.30.6

https://github.com/kubernetes-sigs/azuredisk-csi-driver/pull/2564

v1.31.0

https://github.com/kubernetes-sigs/azuredisk-csi-driver/pull/2213
https://github.com/kubernetes-sigs/azuredisk-csi-driver/pull/2258
https://github.com/kubernetes-sigs/azuredisk-csi-driver/pull/2383
https://github.com/kubernetes-sigs/azuredisk-csi-driver/pull/2388
https://github.com/kubernetes-sigs/azuredisk-csi-driver/pull/2429
https://github.com/kubernetes-sigs/azuredisk-csi-driver/pull/2446
https://github.com/kubernetes-sigs/azuredisk-csi-driver/pull/2344
https://github.com/kubernetes-sigs/azuredisk-csi-driver/pull/2309
https://github.com/kubernetes-sigs/azuredisk-csi-driver/pull/2223

v1.31.1

https://github.com/kubernetes-sigs/azuredisk-csi-driver/pull/2629
https://github.com/kubernetes-sigs/azuredisk-csi-driver/pull/2571
https://github.com/kubernetes-sigs/azuredisk-csi-driver/pull/2562

Full changelogs:
https://github.com/kubernetes-sigs/azuredisk-csi-driver/releases/tag/v1.31.1
https://github.com/kubernetes-sigs/azuredisk-csi-driver/releases/tag/v1.31.0
https://github.com/kubernetes-sigs/azuredisk-csi-driver/releases/tag/v1.30.6
https://github.com/kubernetes-sigs/azuredisk-csi-driver/releases/tag/v1.30.5
@openshift/storage

closed in favor of #88


How to get the current user email when the user tags the @bot in a teams conversation?

We’re trying to build a Microsoft Teams compose extension so that our Teams users can reference tasks from projects on a third party task management platform.
We need to get the current user email on teams, but we couldn't find any references on how to do that.
We're using Bot Builder SDK V4 for NodeJS (Typescript)

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

ID: 896e3726-f7fb-8fbd-925d-bb149d6169f2
Version Independent ID: cea27271-72f4-4832-3d7d-74ff2598913e
Content: Develop messaging extensions - Teams
Content Source: msteams-platform/concepts/messaging-extensions/messaging-extensions-overview.md
Product: msteams
GitHub Login: @o365devx
Microsoft Alias: o365devx

You can get the email Id by fetching the team roaster. This documentation has code for SDK v3, please take a look at the samples present on GitHub for beta SDK v4.

Please reopen if you are still facing any issues.


MTL-1695 Overhaul 1.3 Documentation

This pull-request is very large and is virtually impossible to review.
The bulk of the actual content change is confined to the install/ folder, the rest of the changes are implementing new linting and shell prompts to facilitate copy-paste function.
There have not been any official 1.3 installs yet, this change ideally should go in before 1.3 installs start.
There will likely be follow-up changes after this, those bugs and enhancements should be linked to MTL-1695 as "discovered while testing."
Primary Changes:

New install workflow

New usage of the SHCD validation and cabling
New usage of validating the SHCD
New usage of csi commands to generate csi input files from an SHCD

Pre-installation setup
Validation of cabling is now done during deploy management nodes
Workflow has been reorganized into Pre-Installation and Installation

Secondary Changes:

All LiveCD pages were moved into operations/livecd
Remove all anchor references for Stash support; use headers verbatim. This addresses broken links in several IDEs and Text Editors, and prevents maintainers/contributors from remembering extra steps. Additionally the anchors were in most cases not matching their respective header.
All index.md files were renamed to README.md for auto-displaying in GitHub
Move all prompts outside of their codeblocks to support copy-paste.

I've gone through every single page and tried my best to:

Fix the prompts; make the code snippets "copy-paste" friendly
Fix hyperlinks; I corrected every broken hyper-link that my human eyeball saw, due to statistical human error there may be a handful that are wrong or flat-out still broken
I've removed all  references, these were almost never in alignment to their matching header and were technically links to appear broken in several editors. Now everything follows markdown convention. We only had the  references because I added them for STASH compatibility, that we no longer use.

I literally went through every page one-by-one, scanned, and fixed it. Some pages needed more TLC.
This "extra" effort was for the sake of promoting new conventions and removing potential regressions. This merge will of course be susceptible to scrutiny and bugs in the days to come, but this PR sets us up for success.


store jid only. check if the job is still there before rescheduling

Scheduling a job in a very quick timescale (10 milliseconds) will result in job not being found when reschedule is called.
Also, schedule_set now uses the jid instead of the whole serialised object to find the job. It was not finding it before at all.

Solved by #8 and #9


API Plugin SubscriptionOperation Implementation of subscription management

ConnectionProvider provides events for connections and subscriptions. in this case, only a SubscriptionConnection cares about the ConnectionProvider events, while holding onto all of the subscribers for the connection.
for example, when connection provider sends a connected event, connection will listen to this and react to this by checking if there are any subscribers in memory which need to start the subscription process.
when we move over to the case where SubscriptionConnection creates SubscriptionOperations which manage their own subscription to the connection provider, then there is see a need to register multiple listeners on the connection provider.
in the SubscriptionConnection and SubscriptionOperation model. the SubscriptionConnection holds a queue of subscriptionOperations. SubscriptionOperation is instantiated with the connection provider. Connection registers a listener with the connection provider and reacts to connection related events such as disconnected, try reconnect. Subscriptions also register their own listener with the connection provider and reacts to the connection provider events in the way that is relevant for them. ie. when disconnected event comes, it is responsible for setting its own subscription state to disconnected. when subscriptionDisconnect event comes, it is responsible for removing the listener from the connection provider, and calling finish() on the operation (which then removes it from the queue inside the SubscriptionConnection.

this is no longer relevant as we move towards the shared common package


Migrate to V2 of the unthink stack

This PR serves as the migration of the stack from V1 to V2 and will track progress to a stable V2.

Closing this PR in preference of #35 - the feature branch will hang around shortly to ensure I have everything ported to the packages.

Ha. Closed wrong PR.

@lxndrdagreat This should just work when you pull it down. Ported the hello world resource and version resource over.
The two packages this depends have also been pushed to NPM as "beta" packages and this project is pulling them in via NPM vs the old stack which was using specific git commits for the unthink layer.
As noted in my commit message I have stripped out:

MongoDb
Inversify
The base resource (don't need it)
The error model we had in there - the new foundation layer includes a default error that is in parity with the one removed.

I wanted to "reset" the project and add these things back in within the context of V2 where applicable vs blindly porting them.

@lxndrdagreat One step closer. Nothing changed in stack, but the dependent foundation packages were bumped.
We now have support for headers/cookies. The ResourceContext each route gets has headers/cookies property that is set based on the incoming request and now and both Data/View result supports setting cookies/headers on the various factory methods.
I think this is largely in parity of not beyond what the features V2 with the exception of file handling which was only partial included in V1.  File handling can wait for now.
One minor thing that is missing is the 'printing' of routes when it generates them. I'm going to try to tackle that tonight.
As noted in the post before this we do need to add back some of the features we had in the stack like MongoDB etc. That will be the next thing I start looking at that might can line up with features.

I've been working on a project in the stack this weekend (still V1) and am really happy with it, but we definitely need to focus heavily on documentation after the V2 release. These things especially (though they might be different/gone in V2): middleware, @body, @local, @path.

Once this is stable I want to have a conversation about documentation.
We need a few levels of it I think:

source code level of the foundation packages
Proper project level docs either via a generated static site or wiki pages on the unthink-foundation package. This project houses the core comments and API used in the unithink-cli. So I want docs to leave there vs here for it that explain how it all works and semantics enforced.
docs in this project for any remaining concepts or built in things copied out when the cli inits a project.

Would also like to see if can't get group of us tackling this once we define the formats for it.

Added mongodb back to the stack and slightly different than V1

The mongodb service is no longer class based
No dependency injection is used

The interface now looks like this:
import { getClient, getDefaultDb, getDefaultCollection } from '

@lxndrdagreat here is what I have so far for docs on the unthink-foundation.
I ended up putting it in a docs folder and separating it out of the README.md because it's going to be fairly long.
Open to changing that. I just didn't want to load that README down with this.


MAINT, CI: bump to latest stable OpenBLAS

bump our infrastructure to use the latest stable
release of OpenBLAS (0.3.10)

will be automatically synced to wheels repo
master branch as well, via openblas_support.py

I've added the full complement of sha256 vals from the upstream binaries this time, though we don't really use all of them just yet.

The 64-bit integer OpenBLAS Windows Azure run is timing out.. I'll try a restart on it, not sure if related, but since this is an OpenBLAS version bump have to be careful.

@pv @martin-frbg Is the slowdown surprising for 64-bit integer handling with 0.3.10 vs. 0.3.9. I'm guess this is unexpected, but then Azure seems to fluctuate pretty wildly on test times sometimes..

@tylerjereddy certainly unexpected, and I am not aware of any change affecting 64bit int builds (except on ARMV8 where those used to be completely broken previousy). Do you know what kind of hardware that particular run was using ?

To debug this, test suite could be run with -v to see if it gets stuck in some specific test?

Hm, I'm not entirely sure what the log from a normal run should look like, but to me this near the end of the log
2020-06-24T10:33:36.7877918Z ..............................Entering debug mode. Use h or ? for help.

suggests something tried to switch into interactive mode (and there are a few lines of what looks like a syntax error in a script
following that) ?

I think that's probably the error message from the shell, after Azure kills the job due to it taking too long.

Thanks both, I should probably check locally indeed--that looks like a ~10-13 minute increase in test timing for ilp64 case. No big rush on adopting 0.3.10 into master at the moment but I'll make a note to try to check soon.

I'm going to close this since it probably isn't worth solving with two more recent stable releases of OpenBLAS now available. I'm a little hesitant to bump to 0.3.12 because of the 45+ comment thread of NumPy-related concerns in https://github.com/xianyi/OpenBLAS/issues/2970 ; I may try the PR just to see what happens though


Do these work via the ESPHome BLE proxy?

I am running my eTRVs far away from my HA, so I was trying with the ESPHome bluetooth proxy nearby.
It doesn't seem to work. The keytool never finds anything when I press the button (I already had the MAC), and the etrv scan just shows:
Start scanning
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/local/lib/python3.9/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/usr/local/lib/python3.9/site-packages/libetrv/cli.py", line 80, in <module>
    fire.Fire(CLI)
  File "/usr/local/lib/python3.9/site-packages/fire/core.py", line 141, in Fire
    component_trace = _Fire(component, args, parsed_flag_args, context, name)
  File "/usr/local/lib/python3.9/site-packages/fire/core.py", line 466, in _Fire
    component, remaining_args = _CallAndUpdateTrace(
  File "/usr/local/lib/python3.9/site-packages/fire/core.py", line 681, in _CallAndUpdateTrace
    component = fn(*varargs, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/libetrv/cli.py", line 22, in scan
    for device, key in eTRVDevice.scan(timeout):
  File "/usr/local/lib/python3.9/site-packages/libetrv/device.py", line 41, in scan
    devices = btle.Scanner().scan(1)
  File "/usr/local/lib/python3.9/site-packages/bluepy/btle.py", line 852, in scan
    self.start(passive=passive)
  File "/usr/local/lib/python3.9/site-packages/bluepy/btle.py", line 790, in start
    self._mgmtCmd("le on")
  File "/usr/local/lib/python3.9/site-packages/bluepy/btle.py", line 312, in _mgmtCmd
    raise BTLEManagementError("Failed to execute management command '%s'" % (cmd), rsp)
bluepy.btle.BTLEManagementError: Failed to execute management command 'le on' (code: 17, error: Invalid Index)
Detected eTRV devices:
Done scanning

in the logs..
Is this something that can work and if so, is it something that has to be addressed on the ESPHome side, or here?

Hi.
We've encountered the same error and assume the problem is the update to Python 3.10 and the associated non-functionality of the bluepy. At least in new installations.
https://www.home-assistant.io/blog/2022/07/06/release-20227/#breaking-changes
Is there any chance that the code will be rewritten based on this information?
Thanks.


batch_get doesn't return all results when encountering a memory lock

Bug Report

What version of TiKV are you using?
Master
What did happened?
Here we check the lock table and when we meet the first memory lock, we return it back to the client: https://github.com/tikv/tikv/blob/f5409492a862e6ead06b2cbf4b7818fd6dc655e1/src/storage/mod.rs#L493
However, TiDB incrementally gets the locked keys if some keys are locked: https://github.com/pingcap/tidb/blob/aa9f7584f8fbcdb1dec35e3fa520224825000112/store/tikv/snapshot.go#L339
The behavior requires TiKV to return all existing KV pairs instead of returning the first lock.

Solution 1
Solve it at TiKV side. We keep the semantics of BatchGet. Check all keys in the lock table and query all the unlocked keys. However, there is some trouble to support it in follower read. We need to modify the protocol  to support checking all keys and returning all the locks in the lock table.

Advantage: Consistent semantics
Disadvantage: Lots of changes.

Solution 2
Solve it at TiDB side. Handle async commit locks specially in BatchGet. If the returned lock is an async-commit lock, do not change pending keys and resend the original BatchGet request directly.

Advantage: Change is small.
Disadvantage: Increase a special case in the interface.

/cc @youjiali1995 @cfzjywxk @MyonKeminta

Maybe solution 2 is better to avoid much extra test works since we already have much work to do?

Closed by https://github.com/tikv/tikv/pull/9077 and https://github.com/pingcap/tidb/pull/21157


Section <IP_ADDRESS> para 428, FCS_DTLSS_EXT.1.9

FCS_DTLSS_EXT.1.9 states: “FCS_DTLSS_EXT.1.8 Test 2a, 3a or 4a”. This appears to be an incorrect reference. Similar issue with FCS_TLSS_EXT.1.6 in para 558.

Fixed in TLSWG-v3-editorial-fixes branch.


[ BUG ] Sitemap generation is so slow if I have large list of URLs (Problem in streamToPromise)

Describe the bug
I have around 20000 URLs that should go to the sitemap. I am using an example from your readme, just without createGzip. Here is how it looks like:
  async generateSitemapXML(data: SitemapUrlObject[]): Promise<Buffer> {
    return new Promise((resolve, reject) => {
      const smStream = new SitemapStream({
        hostname: process.env.FRONTEND_HOST
      });
      data.map(urlObject => {
        smStream.write(urlObject);
      });

      smStream.end();
      streamToPromise(smStream)
        .then(resolve)
        .catch(e => reject(e));
    });
  }

When I have around 2000, 3000 URLs, it was working normally, but when I added more it was unacceptably slow. I started to investigate which part is causing the issue and realized that the problem is in streamToPromise function. Then I tried to replace your streamToPromise with stream-to-promise package, and everything was much faster.
This is the example, please check the response time, same data, just different streamToPromise:

response time using integrated streamToPromise

response time using third party streamToPromise
If you think this is the problem, I would be glad to submit PR and replace existing streamToPromise :)
Expected behavior
This should not happen, streapToPromise is a bottleneck for some reason.
Context:

Library Version 6.1.4
Typescript Version 3.7.5
Node Version 12.13.0

Additional context
I am using Nest framework

@fr1sk That's odd. I'll try to reproduce it using the performance tests in the repo. I'd be happy if you opened a PR. I'd also love to know what's causing the slowdown.

oof yeah this is 1000x as slow on my machine.

Ok I think I've got it fixed
========= streamToPromise =============
median: 943.0±46.4ms
99th percentile: 1056.5ms
median: 307.0±42.5mb
99th percentile: 307.0mb
========= stream =============
median: 789.0±43.6ms
99th percentile: 998.5ms
median: 79.0±2.0mb
99th percentile: 79.0mb


feat: support multiple spaces before line comments

Currently yamlfmt enforces using a single space before line comments :
# Before yamlfmt
key: "value"  # line comment

# After yamlfmt
key: "value" # line comment

This behavior triggers a warning from yamllint :
$ echo 'key: "value" # line comment' | yamllint -d "{extends: default, rules: {document-start: false}}" -
stdin
  1:14      warning  too few spaces before comment  (comments)

From https://github.com/adrienverge/yamllint/blob/6bfd6756e2414e0a16a256eaf6575e922d7e2ac9/yamllint/rules/comments.py#L86, the default number of spaces before line comments is 2
What do you think about adding an option to format line comments with multiple spaces ?
I am thinking about an option similar to indent: 2 such that users can set a number of spaces before line comments

Interesting setting, I never knew that was the default.
I checked in the yaml library and I think I'll be able to add this without too much trouble. I will do it in the next release.

@badouralix Thanks for the PR! The next step would be to make a PR here that updates braydonk/yaml and adds a setting to the basic formatter config. #103 is a good reference. If you have time to do it that would be great, or I can do it tomorrow before I cut the release.

Thanks for the feature! This will be in the release today.


Investigate/Implement Hideout area EQUIPMENT_PRESETS_STAND

[x] Allow creation of area
[x] Allow upgrading of area (client gets soft-locked when upgrading from level 1 to 2) - BSG BUG - Client requires restart on live.
[x] Refactor changes made to addUpdateInventoryItemToProfile() into their own function
[x] Check/implement adding gear to mannequin
[x] Check/implement equipping mannequin preset from preset page
[x] Check/implement uploading current gear to mannequin

Originally written by chomp

Currently in need of a live profile with this area ready to build to proceed further

Originally written by chomp

Live data acquired, progress can continue

Originally written by chomp

Attached is a profile with equipment area ready to upgrade from level 1 to 2
Error occurring on upgrade:
EXCEPTION: System.InvalidOperationException: Sequence contains no matching element
  at System.Linq.Enumerable.First[TSource] (System.Collections.Generic.IEnumerable`1[T] source, System.Func`2[T,TResult] predicate) [0x00011] in <351e49e2a5bf4fd6beabb458ce2255f3>:0
  at InteractionsHandlerClass.smethod_24 (TraderControllerClass inventoryController, EFT.InventoryLogic.CompoundItem oldStash, EFT.InventoryLogic.CompoundItem newStash) [0x00084] in <d792a9492dc243568fdbad799e71f838>:0
  at InteractionsHandlerClass.UpdateAreaStashes (System.Collections.Generic.Dictionary`2[TKey,TValue] addedHideoutAreaStashes, EFT.InventoryLogic.InventoryController inventoryController, ItemFactoryClass itemFactory) [0x00067] in <d792a9492dc243568fdbad799e71f838>:0
  at GClass1957.method_8 (GClass1963 stashChanges, System.Collections.Generic.Dictionary`2[TKey,TValue] changesHideoutAreaStashes) [0x00000] in <d792a9492dc243568fdbad799e71f838>:0
  at GClass1957.GInterface168.UpdateProfile (ProfileChangesPocoClass changes) [0x00024] in <d792a9492dc243568fdbad799e71f838>:0
  at ProfileEndpointFactoryAbstractClass.method_18 (Comfort.Common.Result`1[T] queueResult) [0x0004b] in <d792a9492dc243568fdbad799e71f838>:0
  at ProfileEndpointFactoryAbstractClass.method_17 (System.Object[] commandsToSend, Comfort.Common.Result`1[T] result) [0x00046] in <d792a9492dc243568fdbad799e71f838>:0
  at ProfileEndpointFactoryAbstractClass+Class1358.method_0 (Comfort.Common.Result`1[T] result) [0x00000] in <d792a9492dc243568fdbad799e71f838>:0
  at Class282+Struct19`1[T].MoveNext () [0x0007a] in <d792a9492dc243568fdbad799e71f838>:0
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <eae584ce26bc40229c1b1aa476bfa589>:0
  at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.<ThrowAsync>b__6_0 (System.Object state) [0x00000] in <eae584ce26bc40229c1b1aa476bfa589>:0
  at UnityEngine.UnitySynchronizationContext+WorkRequest.Invoke () [0x00002] in <ca21460feb9c47d0ac337b9893474cc6>:0
2024-08-26 15:05:41.572 +01:00|<IP_ADDRESS>.32197|Error|Default|InvalidOperationException: Sequence contains no matching element
System.Linq.Enumerable.First[TSource] (System.Collections.Generic.IEnumerable`1[T] source, System.Func`2[T,TResult] predicate) (at <351e49e2a5bf4fd6beabb458ce2255f3>:0)
InteractionsHandlerClass.smethod_24 (TraderControllerClass inventoryController, EFT.InventoryLogic.CompoundItem oldStash, EFT.InventoryLogic.CompoundItem newStash) (at <d792a9492dc243568fdbad799e71f838>:0)
InteractionsHandlerClass.UpdateAreaStashes (System.Collections.Generic.Dictionary`2[TKey,TValue] addedHideoutAreaStashes, EFT.InventoryLogic.InventoryController inventoryController, ItemFactoryClass itemFactory) (at <d792a9492dc243568fdbad799e71f838>:0)
GClass1957.method_8 (GClass1963 stashChanges, System.Collections.Generic.Dictionary`2[TKey,TValue] changesHideoutAreaStashes) (at <d792a9492dc243568fdbad799e71f838>:0)
GClass1957.GInterface168.UpdateProfile (ProfileChangesPocoClass changes) (at <d792a9492dc243568fdbad799e71f838>:0)
ProfileEndpointFactoryAbstractClass.method_18 (Comfort.Common.Result`1[T] queueResult) (at <d792a9492dc243568fdbad799e71f838>:0)
ProfileEndpointFactoryAbstractClass.method_17 (System.Object[] commandsToSend, Comfort.Common.Result`1[T] result) (at <d792a9492dc243568fdbad799e71f838>:0)
ProfileEndpointFactoryAbstractClass+Class1358.method_0 (Comfort.Common.Result`1[T] result) (at <d792a9492dc243568fdbad799e71f838>:0)
Class282+Struct19`1[T].MoveNext () (at <d792a9492dc243568fdbad799e71f838>:0)

Attachments

6691031200028e10efc75236.json (316 KiB)

Originally written by chomp

Here's the response the server sends the client:
{
    "profileChanges": {
        "6691031200028e10efc75236": {
            "_id": "6691031200028e10efc75236",
            "items": {
                "new": [{
                        "_id": "66cc8bb5253b449c1c031395",
                        "_tpl": "55d7217a4bdc2d86028b456d",
                        "parentId": "65e5bb1713227bb7690cea0a",
                        "slotId": "Stand2"
                    }
                ],
                "change": [],
                "del": []
            },
            "changedHideoutStashes": {
                "26": {
                    "Id": "65e5bb1713227bb7690cea0a",
                    "Tpl": "65e597266017f07a3204b775"
                }
            }
        }
    }
}

Originally written by chomp

The above is looking to be a game client bug, waiting on next eft patch

Originally written by chomp


Empty string in database renders admin unusable.

IMHO, a wrong value stored in the database shouldn't break the django admin. Also, an empty string doesn't feel like a faulty value to me.

Related to #100

Hi. This has been generally fixed by handling all invalid JSON values. A RuntimeWarning is issued, however the value is still loaded as a string.


Split one output C/C++ file into multiple ~100KB chunks, to make a file feasible to compile.

Sorry to bug you again.
The title has it all.
Thanks in advance.

I do not understand what you mean. I do not understand why you would need to split a generated file. This test shows that files up to 10 megabytes can be compiled without a problem, on all platforms.
Assuming that splitting would be required, how do you expect the whole thing to work? I do not know if there would be away to "join" the data from multiple source files as one consecutive stream.
Could you elaborate on what you are expecting?

I mean that if I have some sort of binary file that I would write to disk from my app, the *.cpp file for that would usually be several gigabytes long. I tried compiling it overnight, turns out my SSD got full of swap mem and had to reboot my computer (Windows 11 if it helps).

After typing all of this up and realizing what I'm doing is crazy and I'm gonna switch to a 64GB mem Mac soon:
Nevermind. Sorry for the trouble, I'm just crazy about breaking limits even if I'm doing something pointless.


getPluralClassName addded

I think for pluralizing it would probably make more sense to use something like Humanizer (https://github.com/Humanizr/Humanizer#pluralize). if you want to include it and submit a new pull request i'd be glad to add it.

Hi,
Thanks for your comments
I didn't know humanizer.  But last night İ examined humanizer and İ like it.
I Will try to implement humanizer .
Thanks.
On Feb 20, 2016 19:50, "Omar Elabd"<EMAIL_ADDRESS>wrote:

I think for pluralizing it would probably make more sense to use something
like Humanizer (https://github.com/Humanizr/Humanizer#pluralize). if you
want to include it and submit a new pull request i'd be glad to add it.
—
Reply to this email directly or view it on GitHub
https://github.com/OmarElabd/RepositoryGenerator/pull/1#issuecomment-186658358
.


physics determinism fails when recreating the same scene

Describe the bug
When all bodies part of a simulation are contained in a scene that is recreated the outcome can vary
To Reproduce
Turn on visible collision shapes in the Editor
Open the project and hit RESET a couple of times and eventually the ragdoll will fall down the stairs differently
Expected behavior
The ragdoll falls down identically, never changing the outcome
Environment:

OS: Windows 11
Version 0.7.6
Godot Version v4.2.1.stable.official
Type enhanced determinism 2d

Example project(zip)
determintest.zip

Strange, seems to be quite deterministic for on my machine. Always falls the same. I'll test a bit more.

For reference, I am checking the state of the space by running:
var file = FileAccess.open("user://space.json", FileAccess.WRITE)
var space_state = RapierPhysicsServer2D.space_export_json(get_viewport().world_2d.space)

And making sure that after resets it doesn't change.

https://github.com/appsinacup/godot-rapier-physics/assets/2369380/b22a31f5-dd0c-44f4-a1e7-2cc07a128f0a


Multi-histogram bug

Replication:

In prod, add a trace, choose histogram, put any column in 'x'
Click +Trace ... nothing happens. Console error

Due to https://github.com/plotly/plotly.js/issues/3336


Repeating branching logic

Hi @mmcev106, @grezniczek,
I implemented a fix to EM branching logic on repeating instances. Which will allow branching logic condition to be executed only on the correct level based on the branching logic field level. For example from below json, If you type USA as a country then states repeating instance fields will show up. And if you add another country instance states list wont show up. Same behavior will happen if you select CA then descriptive field will show up only within CA boundaries.
I am available to go over this if you have any question or need more details.
Test EM config.json below:
	"project-settings": [       {         "key": "top-level",         "name": "Top Level",         "type": "checkbox"       },       {         "key": "child-project-id",         "name": "Projects List",         "required": true,         "type": "project-id"       },       {         "key": "countries",         "name": "Country",         "type": "sub_settings",         "repeatable": true,         "sub_settings": [           {             "key": "country-name",             "name": "Country Name (on the bottom just to test a different order)",             "type": "text"           },           {             "key": "states",             "name": "State",             "type": "sub_settings",             "repeatable": true,             "branchingLogic": {               "field": "country-name",               "op": "=",               "value": "USA"             },             "sub_settings": [               {                 "key": "state-name",                 "name": "State Name",                 "type": "dropdown",                 "choices": [                   {                     "name": "Arizona",                     "value": "AZ"                   },                   {                     "name": "California",                     "value": "CA"                   }                 ]               },               {                 "key": "state-top-level",                 "name": "Top Level is True",                 "type": "descriptive",                 "branchingLogic": {                   "field": "top-level",                   "op": "=",                   "value": "1"                 }               },               {                 "key": "cities",                 "name": "City",                 "type": "sub_settings",                 "repeatable": true,                 "sub_settings": [                   {                     "key": "city-name",                     "name": "City Name",                     "type": "text"                   },                   {                     "key": "desc-california",                     "name": "You are in California",                     "type": "text",                     "branchingLogic": {                       "field": "state-name",                       "op": "=",                       "value": "CA"                     }                   },                   {                     "key": "desc-usa",                     "name": "You are in the USA",                     "type": "descriptive",                     "branchingLogic": {                       "field": "country-name",                       "op": "=",                       "value": "USA"                     }                   },                   {                     "key": "city-size",                     "name": "City Size",                     "type": "text"                   }                 ]               }             ]           }         ]       } 	],
Thanks,
@123andy

Thanks very much @ihabzee!  Setting branching logic definitely needed some love.  It looks like there are some conflicts with the testing branch preventing merging unfortunately.  Would you mind merging the latest version of testing into your branch?  It looks like your editor might have normalized a bunch of whitespace, which might make a lot more merge conflicts than necessary.  I'm happy merging whitespace changes, but just wanted to let you know in case you wanted to redo this without the whitespace changes just to avoid the conflicts.

@mmcev106 I updated my pull request with testing branch. Regarding white spaces I added .editorconfig to try to mimc your coding style but PHPStorm adds more stuff when I try to enforce the coding styles. So would you mind test and merge existing code?
Thanks,

I would be very quick to merge a PR that is only about fixing branching logic.  However, it looks like this is mostly about introducing/enforcing a coding standard.  I do not feel comfortable taking the time to review, test, & merge this without my team's approval of this standard, and maybe some sort of automated way to enforce it.  I will bring it up in our team meeting on Monday since it's time to revisit this anyway.  However, a discussion could take weeks, and even then we may decided a coding standard is not worth the effort to enforce.  If we do approve a standard, there will likely be some differences from what the PR currently contains (for example, we may follow StandardJS which would exclude the semicolons this PR adds currently).
If you would like the branching logic changes to get merged sometime soon, they will likely need to be split out into their own PR separate from all the other changes.


New crate for the common types for DCF and DPF

Delay new version release for this

Reuse dcf export for them


Adding two new components

Adds

ScrollIfNeeded to wrap views that could run out of space and would need to scroll if they do so
EnumeratedList, a list having circled numbers on the left hand side and text on the right hand side, can be used for instructions and such

we should not need ScrollIfNeeded anymore. ".scrollBounceBehavior(.basedOnSize)" modifier is sufficient and native.

we should not need ScrollIfNeeded anymore. ".scrollBounceBehavior(.basedOnSize)" modifier is sufficient and native.

I think it'd more convenient to have a view wrapper for this, as otherwise you'd have to implement a ScrollView here and there and remember to use .scrollBounceBehaviour(.basedOnSize) on it. Thus we'd just have a ScrollIfNeeded  wrapper for parts of views that should scroll. In case the implementation is about to change or we see unintended behaviour with the .scrollBounceBehaviour modifier we can change it for all occasions of the same intention


Distribute - Automatic resigning does not work

Describe the solution you'd like
Whenever a new user is added to an app center organization group and they try to download one of the apps or if they get a new iOS device and try to download an old build, the ipa should automatically be resigned and distributed to them since we already have the certificates configured.
Describe alternatives you've considered
The only possible alternative is to manually go to a release and click distribute and under devices section for a group click resign manually. But this is a tedious manual process
Additional context
We are using fastlane to create the builds and upload to app center. We are not using app center to build. I think I read that it is available for app groups but it's just as tedious to maintain all users for each app. We would instead like to use organization groups.

might be related to #1072

It is not related. I’ll update my description. But basically we are only using distribute. The builds are produced by our CI using fastlane.

Hi @tahirmt! Do you mind opening a support ticket and leave the id here so that our engineering team can take a look into this? Thank you!

I used the contact support form to send a message about this. I did not receive any email immediately following that regarding created ticked so I suspect I will know about it once someone replies to it. I will update the thread here once that happens. Thank you.

Hi @wisdeom I created a ticket on app center. #KU3WRJ9D. The response I got is that the option is not available for org level groups and it is only available for app level groups. I would like it if it can be available for org level groups too.

i still get error


Suggestion/Request - include @angular2-material

can you include angular2-material in the project?

@jtc10005 I wanted to keep the UI layer of this project as thin as possible and leaving the design decision  with user of this project. In future, I will have a separate fork of this project when material becomes more mature.
Thanks for the suggestion :).


Custom grafana image

Description
Using a custom Grafana image with all the plugins already downloaded would allow to run the container without needing internet access. This will fix mainly k3d issues when running in restrictive networks
Fixes #1353
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

[x] Deployed with k3d

Checklist:

[x] I have made corresponding changes to the documentation
[x] I have made corresponding changes to the changelog (if needed).
[x] I have made corresponding notices to the upgrade instructions (if needed)

Changelog changes
Custom Grafana image with pre-installed plugins
Upgrade instructions
Not needed

Need to test upgrading from previous version

Ready to be merged 🚀


golang struct split doesn't work on struct names

When the cursor is on struct name and i type the command gS , nothing happens, this command only works when i am inside the {} brackets of go struct. is that the expected behaviour?

Yes, it's intentional.
In general, it can be difficult to to resolve ambiguity when you decide to split something from the outside. If you have a nested struct and you are on the name of the "inside" one, do you split that one, or the surrounding? It's also difficult to resolve these kind of things implementation-wise.
A short explanation of this behaviour can be found here: https://github.com/AndrewRadev/splitjoin.vim/blob/e7e5e1a41ce991fc14a570e85f3ae6f3472bed87/doc/splitjoin.txt#L136-L138. Although I suppose that doesn't give you much new information.

Okay. Thanks. much clear now.


Add example for Service-Worker-Allowed

I imagine a lot of people will want to do this:
navigator.serviceWorker.register("/js/sw.js", {scope: "./"});

Because having a sw.js sitting in the root is just ugly.
However, the Service-Worker-Allowed header is mega confusing to use, and the corresponding spec text is (for me?) very hard to understand.
Can we please add an example for how to use this in the common case above... also, can we please add some examples for how the {scope: "whatever"} and the Service-Worker-Allowed header value are combined to come up with maxScope, etc.?
Thanks! :heart:

(FWIW, Chrome's error messages when using Service-Worker-Allowed are super helpful... I was trying to do this in Firefox and it currently provides little help apart from the security error :crying_cat_face:).

gecko console reporting bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1220757


Error building on ROCm 4.0

Hi, while building the roctracer I am getting the error stating HCC support dropped. Is there a workaround or fix for this?
Steps to produce:
ROCm 4.0 + Docker image rocm/pytorch:rocm4.0_ubuntu18.04_py3.6_pytorch_1.7.0
Following the instructions, the error shows up at "make" state.
Error:
Scanning dependencies of target roctracer64
make[2]: Leaving directory '/rocDistributed/megatron-pytorch-distributed/roctracer/build'
make  -f CMakeFiles/roctracer64.dir/build.make CMakeFiles/roctracer64.dir/build
make[2]: Entering directory '/rocDistributed/megatron-pytorch-distributed/roctracer/build'
[ 21%] Building CXX object CMakeFiles/roctracer64.dir/src/core/roctracer.cpp.o
/opt/cache/bin/c++ -DAMD_INTERNAL_BUILD -DHIP_PROF_HIP_API_STRING=1 -DHIP_VDI=0 -DHSA_DEPRECATED="" -DHSA_LARGE_MODEL="" -DLINUX -DLITTLEENDIAN_CPU=1 -DLOCAL_BUILD=1 -DUNIX_OS -D__AMD64__ -D__HIP_PLATFORM_HCC__=1 -D__linux__ -D__x86_64__ -Droctracer64_EXPORTS -I/rocDistributed/megatron-pytorch-distributed/roctracer/src -I/rocDistributed/megatron-pytorch-distributed/roctracer -I/rocDistributed/megatron-pytorch-distributed/roctracer/inc -I/opt/rocm/include/hsa -I/opt/rocm/hip/include -I/opt/rocm/lib/../include -I/rocDistributed/megatron-pytorch-distributed/roctracer/build/inc -std=c++11 -Wall -Werror -Werror=return-type -fexceptions -fvisibility=hidden -fno-math-errno -fno-threadsafe-statics -fmerge-all-constants -fms-extensions -fmerge-all-constants -fPIC -m64  -msse -msse2 -O3 -DNDEBUG -fPIC -o CMakeFiles/roctracer64.dir/src/core/roctracer.cpp.o -c /rocDistributed/megatron-pytorch-distributed/roctracer/src/core/roctracer.cpp
In file included from /rocDistributed/megatron-pytorch-distributed/roctracer/src/core/roctracer.cpp:44:0:
/rocDistributed/megatron-pytorch-distributed/roctracer/src/core/loader.h:314:2: error: #error HCC support dropped
 #error HCC support dropped
  ^~~~~
CMakeFiles/roctracer64.dir/build.make:84: recipe for target 'CMakeFiles/roctracer64.dir/src/core/roctracer.cpp.o' failed
make[2]: *** [CMakeFiles/roctracer64.dir/src/core/roctracer.cpp.o] Error 1
make[2]: Leaving directory '/rocDistributed/megatron-pytorch-distributed/roctracer/build'
CMakeFiles/Makefile2:289: recipe for target 'CMakeFiles/roctracer64.dir/all' failed

Thanks!

I just got the same error.  It seems that adding
-DHIP_VID=1
to cmake fixed it.  Maybe.

@cagery Apologies for the lack of response. Did adding "-DHIP_VDI=1" to cmake resolve your issue? If so, please close the ticket. Thanks!


Cannot convert string to double: "" [DITA-OT2.0.M3]

Processing a DITA Map to XHTML (it has a topic which has colspecs with fixed widths):

[xslt] C:\Users\radu_coravu\Desktop\DITA-OT2.0.M3\plugins\org.dita.xhtml\xsl\xslhtml\dita2htmlImpl.xsl:2329: Fatal Error! Cannot convert string to double: ""

The XSLT template:
<xsl:template match="*[contains(@class, ' topic/colspec ')]" mode="count-colwidth">

has a variable, probably the "otherwise" branch of the "xsl:choose" breaks:
<xsl:variable name="thiswidth">
  <xsl:choose>
    <xsl:when test="@colwidth"><xsl:value-of select="substring-before(@colwidth, '*')"/></xsl:when>
    <xsl:otherwise>1</xsl:otherwise>
  </xsl:choose>
</xsl:variable>

In order to fix the code, we need to check what the browser support is for mixing absolute and relative widths.

  <col style="width: 66%">
  <col style="width: 40px">

Testing a HTML5 table with Chrome, regardless of the table-layout property, width of the table was always respected. However, when a same table had one table in percentages and one in absolute units, the results varied:

fixed: the absolute unit overrode the relative unit.
auto: the relative unit overrode the abolute unit.

The problem with OASIS table model `width="1*" is that it cannot be converted to percentages without knowing the width of the table.
<fo:table table-layout="fixed"
          width="100%;">
  <fo:table-column column-width="proportional-column-width(2)"/>
  <fo:table-column column-width="40px"/>

Testing XSL-FO with AHF, table width was always respected and in column-width and absolute unit always took precedence.

Is there any progress regarding this issue? I've came across is while generating HTML5 output out of DITA map. Would appreciate any help!

FWIW, using 2.0M3, I cannot reproduce the issue by simply introducing <colspec> elements with fixed widths like this:

  <tgroup cols="2">
    <colspec colname="c1" colnum="1" colwidth="171.0px"/>
    <colspec colname="c2" colnum="2" colwidth="171.0px"/>
    ...

I can reproduce the issue with 2.0M3 if I change the other <colspec> element to use
a relative width:

  <tgroup cols="2">
    <colspec colname="c1" colnum="1" colwidth="1*"/>
    <colspec colname="c2" colnum="2" colwidth="171.0px"/>
    ...

I cannot reproduce the issue using the latest code in the develop branch.

@eerohele are you able to reproduce this with develop code? I've refactored the code there for cases when relative and absolute columns are mixed.

@eerohele are you able to reproduce this with develop code? I've refactored the code there for cases when relative and absolute columns are mixed.

Nope, can't reproduce it.

Ok, closing as fixed.


If setup fails, kill container

When setup fails, we currently keep the container around, but setup will never be re-run.
Kill the container when any of the setup steps fails.

[x] test
[x] implement
[x] document

Done. Will be released with 1.2.0.


berkeley-qa: Crashed Mina Daemon With Multiple ZkApp Tx and User Tx

Preliminary Checks

[X] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/MinaProtocol/mina/issues
[X] This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/MinaProtocol/mina/discussions

Description
I was sending multiple zkapp transactions along with many user transactions and crashed the daemon:
2022-05-06 16:12:57 UTC [Fatal] Unhandled top-level exception: $exn
Generating crash report
	exn: {
  "commit_id": "552f5479ccccc7b501a84a843024bf62bb845d4a",
  "sexp": [
    "monitor.ml.Error",
    [
      "Failure",
      "Tried to handle a committed transaction in the pool but its nonce doesn't match the head of the queue for that sender"
    ],
    [
      "Raised at Stdlib.failwith in file \"stdlib.ml\", line 29, characters 17-33",
      "Called from Network_pool__Transaction_pool.Make0.Resource_pool.handle_transition_frontier_diff.(fun) in file \"src/lib/network_pool/transaction_pool.ml\", line 666, characters 18-36",
      "Called from Stdlib__list.fold_left in file \"list.ml\", line 121, characters 24-34",
      "Called from Base__List0.fold in file \"src/list0.ml\" (inlined), line 21, characters 22-52",
      "Called from Network_pool__Transaction_pool.Make0.Resource_pool.handle_transition_frontier_diff in file \"src/lib/network_pool/transaction_pool.ml\", line 605, characters 8-1023",
      "Called from Base__Result.try_with in file \"src/result.ml\", line 179, characters 9-15",
      "Caught by monitor coda"
    ]
  ],
  "backtrace": [
    "Raised at Stdlib.failwith in file \"stdlib.ml\", line 29, characters 17-33",
    "Called from O1trace.exec_thread in file \"src/lib/o1trace/o1trace.ml\", line 68, characters 6-27",
    "Called from Pipe_lib__Strict_pipe.Reader0.Merge.iter.read_deferred.(fun) in file \"src/lib/pipe_lib/strict_pipe.ml\", line 162, characters 30-39",
    "Called from Async_kernel__Deferred0.bind.(fun) in file \"src/deferred0.ml\", line 54, characters 64-69",
    "Called from Async_kernel__Job_queue.run_job in file \"src/job_queue.ml\" (inlined), line 128, characters 2-5",
    "Called from Async_kernel__Job_queue.run_jobs in file \"src/job_queue.ml\", line 169, characters 6-47"
  ]
}
2022-05-06 16:12:57 UTC [Fatal] Unhandled top-level exception: $exn
Generating crash report
	exn: {
  "commit_id": "552f5479ccccc7b501a84a843024bf62bb845d4a",
  "sexp": [
    "monitor.ml.Error",
    [
      "Failure",
      "timing task `processing_transaction_pool_transition_frontier_diffs` failed, exception reported to parent monitor"
    ],
    [
      "Raised at Stdlib.failwith in file \"stdlib.ml\", line 29, characters 17-33",
      "Called from O1trace.exec_thread in file \"src/lib/o1trace/o1trace.ml\", line 68, characters 6-27",
      "Called from Pipe_lib__Strict_pipe.Reader0.Merge.iter.read_deferred.(fun) in file \"src/lib/pipe_lib/strict_pipe.ml\", line 162, characters 30-39",
      "Called from Async_kernel__Deferred0.bind.(fun) in file \"src/deferred0.ml\", line 54, characters 64-69",
      "Called from Async_kernel__Job_queue.run_job in file \"src/job_queue.ml\" (inlined), line 128, characters 2-5",
      "Called from Async_kernel__Job_queue.run_jobs in file \"src/job_queue.ml\", line 169, characters 6-47",
      "Caught by monitor coda"
    ]
  ],
  "backtrace": [
    "Raised at Stdlib.failwith in file \"stdlib.ml\", line 29, characters 17-33",
    "Called from O1trace.exec_thread in file \"src/lib/o1trace/o1trace.ml\", line 68, characters 6-27",
    "Called from Pipe_lib__Strict_pipe.Reader0.Merge.iter.read_deferred.(fun) in file \"src/lib/pipe_lib/strict_pipe.ml\", line 162, characters 30-39",
    "Called from Async_kernel__Deferred0.bind.(fun) in file \"src/deferred0.ml\", line 54, characters 64-69",
    "Called from Async_kernel__Job_queue.run_job in file \"src/job_queue.ml\" (inlined), line 128, characters 2-5",
    "Called from Async_kernel__Job_queue.run_jobs in file \"src/job_queue.ml\", line 169, characters 6-47"
  ]
}
2022-05-06 16:12:57 UTC [Fatal] libp2p_helper process died unexpectedly: "died after receiving sigkill (signal number 9)"
2022-05-06 16:12:57 UTC [Error] Encountered $error while asking libp2p_helper for peers
	error: {
  "commit_id": "552f5479ccccc7b501a84a843024bf62bb845d4a",
  "string": "libp2p_helper process died before answering"
}
2022-05-06 16:12:57 UTC [Error] Encountered $error while asking libp2p_helper for peers
	error: {
  "commit_id": "552f5479ccccc7b501a84a843024bf62bb845d4a",
  "string": "libp2p_helper process died before answering"
}
2022-05-06 16:12:57 UTC [Fatal] Unhandled top-level exception: $exn
Generating crash report
	exn: {
  "commit_id": "552f5479ccccc7b501a84a843024bf62bb845d4a",
  "sexp": [
    "monitor.ml.Error",
    [ "Mina_net2__Libp2p_helper.Libp2p_helper_died_unexpectedly" ],
    [
      "Raised at Mina_net2__Libp2p_helper.handle_libp2p_helper_termination in file \"src/lib/mina_net2/libp2p_helper.ml\", line 144, characters 8-45",
      "Called from Async_kernel__Deferred0.bind.(fun) in file \"src/deferred0.ml\", line 54, characters 64-69",
      "Called from Async_kernel__Job_queue.run_job in file \"src/job_queue.ml\" (inlined), line 128, characters 2-5",
      "Called from Async_kernel__Job_queue.run_jobs in file \"src/job_queue.ml\", line 169, characters 6-47",
      "Caught by monitor at file \"src/lib/gossip_net/libp2p.ml\", line 234, characters 31-31"
    ]
  ],
  "backtrace": [
    "Raised at Gossip_net__Libp2p.Make.T.create_libp2p.handle_mina_net2_exception in file \"src/lib/gossip_net/libp2p.ml\", line 218, characters 12-21",
    "Called from Base__Result.try_with in file \"src/result.ml\", line 179, characters 9-15"
  ]
}
2022-05-06 16:12:57 UTC [Error] Encountered $error while asking libp2p_helper for peers
	error: {
  "commit_id": "552f5479ccccc7b501a84a843024bf62bb845d4a",
  "string": "helper process already exited (doing RPC ListPeers)"
}
2022-05-06 16:14:00 UTC [Error] Encountered $error while asking libp2p_helper for peers
	error: {
  "commit_id": "552f5479ccccc7b501a84a843024bf62bb845d4a",
  "string": "helper process already exited (doing RPC ListPeers)"
}
2022-05-06 16:14:00 UTC [Error] Encountered $error while asking libp2p_helper for peers
	error: {
  "commit_id": "552f5479ccccc7b501a84a843024bf62bb845d4a",
  "string": "helper process already exited (doing RPC ListPeers)"
}
2022-05-06 16:14:29 UTC [Error] Encountered $error while asking libp2p_helper for peers
	error: {
  "commit_id": "552f5479ccccc7b501a84a843024bf62bb845d4a",
  "string": "helper process already exited (doing RPC ListPeers)"
}
2022-05-06 16:14:29 UTC [Info] Running async shutdown handler: "Close transition frontier, if exists"
2022-05-06 16:14:29 UTC [Info] Running async shutdown handler: "Remove daemon lockfile"

  ☠  Mina Daemon crashed.
   The Mina Protocol developers would like to know why!

    Please:
      Open an issue:
        <https://github.com/MinaProtocol/mina/issues/new>

      Briefly describe what you were doing and attach the crash report /root/.mina-config/coda_crash_report_2022-05-06_16-14-00.286842.tar.gz

Steps to Reproduce

Start Daemon and Sync
Send a large number of zkapps and user transactions
Observe crash
...

Expected Result
No Daemon Crash
Actual Result
Daemon Crash
How frequently do you see this issue?
Rarely
What is the impact of this issue on your ability to run a node?
Blocker
Status
N/A Mina Daemon Crashed

Additional information
Messaging Deepthi on Discord with the Logs

Docker Version: minaprotocol/mina-daemon:1.3.1beta1-release-2.0.0-552f547-bionic-berkeley


Nitrous shutdown

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


Interference of database authentication and tip of the day on startup

Description
I have a database set up without storing the password in DBeaver. Additionally, I have activated the "Tip of the day" feature, which displays a message box with a usage tip on startup.
Now on startup, first the authentication dialog appears to enter my password, which I start to enter. About one or two seconds later while typing my password the tip of the day box comes up. I can switch back to the authentication dialog, but it doesn't receive any keyboard input any more. So I have to switch back to close the tip of the day box before I can finish the authentication dialog.
Now that I know it, this is only a little annoying for me. But when running DBeaver the second time after initial database configuration it took me a while to figure out why I couldn't finish my password before looking at the tip of the day.
DBeaver Version
Community Edition <IP_ADDRESS>306251800
Operating System
Ubuntu 22.04
Database and driver
Database: PostgreSQL 14.8 (Ubuntu 14.8-0ubuntu<IP_ADDRESS>)
Driver: PostgreSQL JDBC Driver 42.5.2
Steps to reproduce

Setup a database connection without storing the password
Activate Tip of the day in help menu
Exit DBeaver
Restart DBeaver

Additional context
No response

Thank you for bug report.

I forgot to mention that I'm running DBeaver on the KDE/Plasma desktop.