Re-enable protocol sniffing test and add external

This re-enables the sniffing tests, only skipping the TCP which is
currently flaky due to issues with our echo client which is being
addressed separately. In addition, we add testing of the external
service. To support this change, I added a way for an echo instance to
declare its default hostname. This way, we can treat it like any regular
service
Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

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

Test name
Commit
Details
Rerun command

release-notes_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test release-notes_istio

lint_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test release-notes_istio

lint_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test lint_istio

analyze-tests_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test release-notes_istio

lint_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test lint_istio

analyze-tests_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test release-notes_istio

lint_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test lint_istio

analyze-tests_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test integ-telemetry-k8s-tests_istio

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

@howardjohn: PR needs rebase.

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test release-notes_istio

lint_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test lint_istio

analyze-tests_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test integ-telemetry-k8s-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test release-notes_istio

lint_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test lint_istio

analyze-tests_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test integ-telemetry-k8s-tests_istio

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

release-test_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test release-test_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test release-notes_istio

lint_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test lint_istio

integ-pilot-k8s-tests_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test integ-telemetry-k8s-tests_istio

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

release-test_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test release-test_istio

analyze-tests_istio
c1ce9007602e283edd36f4648553ab4971934de0
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test release-notes_istio

lint_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test lint_istio

integ-pilot-k8s-tests_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test integ-telemetry-k8s-tests_istio

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

release-test_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test release-test_istio

analyze-tests_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test analyze-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test release-notes_istio

lint_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test lint_istio

integ-pilot-k8s-tests_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test integ-telemetry-k8s-tests_istio

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

release-test_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test release-test_istio

analyze-tests_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test analyze-tests_istio

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

integ-operator-controller-tests_istio
c1ce9007602e283edd36f4648553ab4971934de0
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test release-notes_istio

lint_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test lint_istio

integ-pilot-k8s-tests_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test integ-telemetry-k8s-tests_istio

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

release-test_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test release-test_istio

analyze-tests_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test analyze-tests_istio

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

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

integ-distroless-k8s-tests_istio
c1ce9007602e283edd36f4648553ab4971934de0
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test release-notes_istio

lint_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test lint_istio

integ-pilot-k8s-tests_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test integ-pilot-k8s-tests_istio

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

release-test_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test release-test_istio

analyze-tests_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test analyze-tests_istio

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

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

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

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

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test release-notes_istio

lint_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test lint_istio

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

release-test_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test release-test_istio

analyze-tests_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test analyze-tests_istio

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

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

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

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

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

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test release-notes_istio

lint_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test lint_istio

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

release-test_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test release-test_istio

analyze-tests_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test analyze-tests_istio

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

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

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

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

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

unit-tests_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test lint_istio

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

release-test_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test release-test_istio

analyze-tests_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test analyze-tests_istio

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

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

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

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

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

unit-tests_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test unit-tests_istio

release-notes_istio
c1ce9007602e283edd36f4648553ab4971934de0
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.

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

Test name
Commit
Details
Rerun command

lint_istio
550706eb42e7b66c0fcda36f0ba0cfd5b6835d18
link
/test lint_istio

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

release-test_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test release-test_istio

analyze-tests_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test analyze-tests_istio

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

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

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

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

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

unit-tests_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test unit-tests_istio

release-notes_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test release-notes_istio

integ-ipv6-k8s-tests_istio
c1ce9007602e283edd36f4648553ab4971934de0
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.

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

Test name
Commit
Details
Rerun command

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

release-test_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test release-test_istio

analyze-tests_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test analyze-tests_istio

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

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

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

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

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

unit-tests_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test unit-tests_istio

release-notes_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test release-notes_istio

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

lint_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

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

release-test_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test release-test_istio

analyze-tests_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test analyze-tests_istio

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

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

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

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

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

unit-tests_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test unit-tests_istio

release-notes_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test release-notes_istio

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

lint_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test lint_istio

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

I've already reenabled the test with tcp.

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

Test name
Commit
Details
Rerun command

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

release-test_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test release-test_istio

analyze-tests_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test analyze-tests_istio

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

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

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

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

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

unit-tests_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test unit-tests_istio

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

gencheck_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test gencheck_istio

lint_istio
41c10bb1422bab86928de67cf075de133c18ff48
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

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

release-test_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test release-test_istio

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

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

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

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

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

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

lint_istio
41c10bb1422bab86928de67cf075de133c18ff48
link
/test lint_istio

analyze-tests_istio
41c10bb1422bab86928de67cf075de133c18ff48
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.

I've already reenabled the test with tcp.

Agreed, so this is more about adding external test then now. But TCP is still disabled with your PR as far as I can tell?

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

Test name
Commit
Details
Rerun command

release-test_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test release-test_istio

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

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

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

lint_istio
41c10bb1422bab86928de67cf075de133c18ff48
link
/test lint_istio

analyze-tests_istio
d240660af24eb64beb14b4018b322c83fc4388a1
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.

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

Test name
Commit
Details
Rerun command

release-test_istio
c1ce9007602e283edd36f4648553ab4971934de0
link
/test release-test_istio

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

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

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

analyze-tests_istio
d240660af24eb64beb14b4018b322c83fc4388a1
link
/test analyze-tests_istio

lint_istio
d240660af24eb64beb14b4018b322c83fc4388a1
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

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

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

analyze-tests_istio
d240660af24eb64beb14b4018b322c83fc4388a1
link
/test analyze-tests_istio

lint_istio
d240660af24eb64beb14b4018b322c83fc4388a1
link
/test lint_istio

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

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

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

Test name
Commit
Details
Rerun command

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

analyze-tests_istio
d240660af24eb64beb14b4018b322c83fc4388a1
link
/test analyze-tests_istio

lint_istio
d240660af24eb64beb14b4018b322c83fc4388a1
link
/test lint_istio

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

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

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

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

Test name
Commit
Details
Rerun command

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

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

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

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

Test name
Commit
Details
Rerun command

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

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

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

/retest

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

Test name
Commit
Details
Rerun command

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

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

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

Test name
Commit
Details
Rerun command

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

unit-tests_istio
377d4210edd5e2abcacdbcff573b29223076e918
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.

/retest

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
377d4210edd5e2abcacdbcff573b29223076e918
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.

/retest


Appstudio update mvp-test-component

Pipelines as Code configuration proposal

Pipelines as Code CI/mvp-test-component-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
14 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
14 seconds
inspect-image

✅ Succeeded
13 seconds
deprecated-base-image-check

✅ Succeeded
16 seconds
clair-scan

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
12 seconds
sbom-json-check

✅ Succeeded
7 seconds
label-check

✅ Succeeded
7 seconds
optional-label-check

✅ Succeeded
4 seconds
show-summary

Pipelines as Code CI/mvp-test-component-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
14 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
13 seconds
deprecated-base-image-check

✅ Succeeded
14 seconds
inspect-image

✅ Succeeded
16 seconds
clair-scan

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
12 seconds
sbom-json-check

✅ Succeeded
7 seconds
optional-label-check

✅ Succeeded
7 seconds
label-check

✅ Succeeded
4 seconds
show-summary


Several fixes and enhancements

This series provide the following changes:

a fix for download-image script to exit on error
a fix to mk-ssh-config to set 0600 permissions on the private key file (git does not store information about full permissions, only about the executable bit)
ability to configure VM parameters with variables

Thanks! As you're changing the default number of CPUs to 2, can we now remove --ignore-preflight-errors=NumCPU from the README?

@sebastian-philipp Yes. Sorry, I totally forgot about mentioning the change of vCPUs to 2 and I wasn't even sure whether I should commit it. ;) But from my experience, when you use just 1 vCPU, the Kubernetes cluster is barely usable and I had hard time with setting up Cilium on it. 2 vCPUs seem to be way better.
If you have no objections to the change of vCPU count, I'm going to change the README. :)

Done.

You're using it for Cilium? that's totally awesome


chore(docs): fix missing sandbox dependency and add vanilla examples

Resolves #877

@davidjerleke done :)

@meirroth fantastic work. Thanks for this 🚀!


Redundant space in outcome printing of constructors

Thanks for the report. Is this the full code for that module?

Yes, a closing brace is missing in the screenshot.


Possible Sockets regression causing server test flakiness

We're getting quite a bit of flakiness in server tests. We suspect a regression in Sockets because we haven't changed code here, other than accepting a new runtime.
@halter73 @BrennanConroy we can use this issue to track/monitor work on investigating this.

Or maybe thread-pool starvation?
Either way we need to investigate and mitigate these failures.

Can we capture a dump?

(@davidfowl failing at reading comprehension in https://github.com/aspnet/AspNetCore/pull/16853#issuecomment-550808037)
We certainly could. We also talked about the fact that if we double down on transitioning tests that are working well in Helix to use Helix exclusively we might gain some reliability here. We have a hunch (with some anecdata to back it up) that because AzDO builds run a whole bunch of test projects in the same xUnit batch, they starve the thread-pool causing timeouts. Helix runs each test project in a separate work item (which means a separate machine) and would improve reliability.
Is that a correct interpretation of our Helix model @HaoK ?

Yep you got it @anurse , currently our Helix jobs run each unit test project by itself on a dedicated machine, so each test runs in isolation, with the tradeoff that we spend more time waiting for helix machines than running tests typically.

FYI, longer term we might want to repackage things a bit since we've been getting some pushback about how we aren't utilizing machines efficiently this way.  It might be better if we aggregated things so that each feature area has one single helix work item that ran all of its related tests, instead of having every test project get a dedicated machine

It might be better if we aggregated things so that each feature area has one single helix work item that ran all of its related tests, instead of having every test project get a dedicated machine

Hrm, that may bring us back to the problems we're seeing in AzDO. Perhaps there's a compromise that makes sense though, bundling a few test projects together instead of doing each individual one, but also not just running all the tests in one batch.

Yeah we don't need to run them in parallel on helix, since we are running all the feature areas at once, we could just run each test project by itself per machine

I'll file an issue for this helix enhancement as it will take some new functionality/complexity in the helix scripts/build stuff

The, somewhat higher-priority, item I'd like to look at is to start migrating some test suites to be run exclusively in Helix. In general we think there are test suites that are more reliable when run in Helix than in AzDO (because they run in separate processes rather than overloading a single process with a huge number of tests).

I filed https://github.com/aspnet/AspNetCore/issues/16901
Yeah seems reasonable to just add a reverse skipOnHelix attribute?  Maybe [HelixOnly] that you would slap on azdo starved tests ?

Although now that we are running helix as a required PR check, we could actually consider only running SkipOnHelix tests across the board for the azdo jobs now right?

@anurse we discussed this a bit in the build meeting today, and I created https://github.com/aspnet/AspNetCore/issues/16910 to look into seeing if we can stop tests that are happy in helix entirely.


0.11.0: pyo3_runtime.PanicException: Failed to acquire lock on Vega-Lite converter: PoisonError { .. }

After updating vl-convert-python to 0.11.0 in the VegaFusion CI test suite, tests are failing with:
FAILED tests/test_transformed_data.py::test_transformed_data_exclude - pyo3_runtime.PanicException: Failed to acquire lock on Vega-Lite converter: PoisonError { .. }

This seems to be a regression from 0.10.3

Root cause reported in https://github.com/RazrFalcon/resvg/issues/638


#4270 set http status code to 409 if dir already exists

What problem are we solving?
Filer API returns 500 Internal server error status code if path/dir already exists. It should return 4XX client error.
How are we solving the problem?
If error message has suffix already exists, 409 Conflict will be returned
How is the PR tested?
PR is tested manually as I am not able to find related test cases. weed binary is generated using go build ./weed and empty storage started using below commands.
./weed master -mdir="." -ip=localhost
./weed volume -max=100 -mserver="localhost:9333" -dir="./data"
./weed filer -ip=localhost -port=8888 -master=localhost:9333

Then API is tested with help of curl.
> curl -vvv -X POST "http://localhost:8888/foo/"
*   Trying <IP_ADDRESS>:8888...
* Connected to localhost (<IP_ADDRESS>) port 8888 (#0)
> POST /foo/ HTTP/1.1
> Host: localhost:8888
> User-Agent: curl/7.81.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 201 Created
< Content-Type: application/json
< Server: SeaweedFS Filer 30GB 3.43
< Date: Wed, 08 Mar 2023 12:00:24 GMT
< Content-Length: 14
<
* Connection #0 to host localhost left intact
{"name":"foo"}%

> curl -vvv -X POST "http://localhost:8888/foo/"

*   Trying <IP_ADDRESS>:8888...
* Connected to localhost (<IP_ADDRESS>) port 8888 (#0)
> POST /foo/ HTTP/1.1
> Host: localhost:8888
> User-Agent: curl/7.81.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 409 Conflict
< Content-Type: application/json
< Server: SeaweedFS Filer 30GB 3.43
< Date: Wed, 08 Mar 2023 12:00:27 GMT
< Content-Length: 35
<
* Connection #0 to host localhost left intact
{"error":"dir /foo already exists"}%

There are multiple places where error is returned with message having suffix already exists.
> grep -irn 'already exists' weed/

weed/filer/redis3/ItemList.go:94:	// case 1: the name already exists as one leading key in the batch
weed/filer/filer.go:194:			glog.V(3).Infof("EEXIST: entry %s already exists", entry.FullPath)
weed/filer/filer.go:195:			return fmt.Errorf("EEXIST: entry %s already exists", entry.FullPath)
weed/s3api/bucket_metadata.go:174:	//check if already exists
grep: weed/weed: binary file matches
weed/server/volume_grpc_copy.go:33:		glog.V(0).Infof("volume %d already exists. deleted before copying...", req.VolumeId)
weed/server/volume_grpc_tier_upload.go:48:			return fmt.Errorf("destination %s already exists", req.DestinationBackendName)
weed/server/filer_server_handlers_write_autochunk.go:318:		replyerr = fmt.Errorf("dir %s already exists", path)
weed/server/volume_grpc_tier_download.go:32:	// check whether the local .dat already exists
weed/storage/store.go:163:		return fmt.Errorf("Volume Id %d already exists!", vid)
weed/mount/weedfs_xattr.go:66://	the attribute already exists.  To modify these semantics, one of
weed/mount/weedfs_rename.go:61:              newpath already exists.
weed/util/skiplist/name_list.go:69:	// case 1: the name already exists as one leading key in the batch

I haven't tested all such occurances except one mentioned in #4270. But IMO even other places also 409 makes sense if 500 is being returned. So even though  already exists suffix could cover broader scenarios, it should not be an issue.
Checks

[ ] I have added unit tests if possible.
[ ] I will add related wiki document changes and link to this PR after merging.

Thanks for so many details!

fixes #4270


[Enhancement][scan] No scan report output when some images scan failed

Description
No scan report output when some of the images failed to scan.
Need to output scan report even if some image still scan failed.

Done in v1.8.3.


How to use with request-promise-native

I depend on request-promise-native but still i want to use this cache library, is this possible?

I wouldn't use both, either use this lib request-promise-cache which already uses the native Promise by default, OR use request-promise-native with your own caching logic, the cache lib i use here is https://github.com/akhoury/nano-cache.
If you use version 2.0.0 of this lib (which I just published and added resolveWithFullResponse option), keep in mind that it doesn't support "verbs" sugar functions, like request.get() or request.post(), you have to do it the original way, as in
request({ url: '...', type: 'post' ... })

Thanks for your reply and explanation.
The sugar verbs is what i do use and why it maybe didn't work for what i was trying.
Maybe you can make a new release/tag on Github?


Thinning binaries

Cilium provides the network infrastructure of a kubernetes cluster and commonly is deployed as a daemonset, this means that nodes has to pull the images with cilium before being able to create pods (NetworkReady)
Reducing the image size and all the additional dependencies can help with this, but this issue is focused on the binaries size only
From @aanm in slack https://cilium.slack.com/archives/C2B917YHE/p1685450392602539?thread_ts=1685356302.877679&cid=C2B917YHE
I just did a quick check on v1.13.3:
top 6 cilium bins

   80.1 MiB [##########]  cilium-agent
   62.2 MiB [#######   ]  cilium
   27.7 MiB [###       ]  cilium-envoy
   20.9 MiB [##        ]  hubble
   14.3 MiB [#         ]  cilium-health

   27.1 MiB [##########]  cilium-cni

Just checking one of the binaries we can found that there is some room of improvement, I'm using this tool https://github.com/nikolaydubina/go-binsize-treemap but I still trying to understand the discrepancy between the reported size by the tool and the size on disk
cd cilium
go build .
ls -alrh cilium
-rwxr-x--- 1 aojea primarygroup 93M Jun  7 10:24 cilium
go tool nm -size cilium | go-binsize-treemap > cilium_binsize.svg

cd daemon
go build .
ls -alrh daemon
-rwxr-x--- 1 aojea primarygroup 121M Jun  7 10:39 daemon
go tool nm -size daemon | go-binsize-treemap > daemon_binsize.svg

cd cilium-cni/
go build .
ls -altrh cilium-cni
-rwxr-x--- 1 aojea primarygroup 43M Jun  7 10:57 cilium-cni
$ go tool nm -size cilium-cni | go-binsize-treemap > cni_binsize.svg

/cc @aanm @borkmann @squeed

The google/gopacket dependency is huge and seems only imported in hubble and
pkg/monitor/dissect.go: "github.com/google/gopacket"
pkg/monitor/dissect.go: "github.com/google/gopacket/layers"

possible candidate for a quick win

I think that the gopacket dependency would be hard to replace without a performance penalty in Hubble.


[test only] Improve filesIn test-helper function

Bug/issue #, if applicable:
Summary
This is a test-only change that improves the flexibility of the filesIn integration test-helper in the integration tests.
This PR is in preparation for another change. Whenever I've asked people about how they that I structure my PRs they've said that they prefer multiple smaller single-purpose PRs. I'm trying to do just that with this PR. The purpose of this change is to support writing a new test for a follow up PR that intercepts and customizes the --output-dir argument.
Dependencies
None.
Testing
Run bin/tests.
Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[x] ~Added~ Updated tests
[x] Ran the ./bin/test script and it succeeded
[x] ~Updated documentation if necessary~ Not applicable.

@swift-ci please test

@swift-ci please test

@swift-ci please test


Code editor automatically pastes clipboard data

VSCode Version: 1.18.1 (but also earlier versions)
OS Version: Ubuntu 17.10, Ubuntu 16.04, macOS High Sierra 10.13.1

Steps to Reproduce:

Copy some text
Work in VS Code

It is hard to reproduce but me and my co-workers experience the same thing: sometimes text seems to be pasted automatically at multiple locations.
I initially thought it might be my touchpad that I accidentally touch when typing. But also after disabling it, the problem keeps occuring. It happens multiple times per day.

@Keuter can you try code --disable-extensions to see if it still happens?


Warning using unquote()

Hi, I'm using Codekit with Sass 3.4.10 + Libsass 3.1 and I'm having a lot of this kind of warning :
DEPRECATION WARNING: Passing null, a non-string value, to unquote()
will be an error in future versions of Sass.

Do you have a workaround ? I tried to modify some code of Unsemantic but without success. I'd rather not to disable warnings. Thanks !

Same problem on one of my project. unquote args has to be quoted
unquote('something');

A solution to this is to create a safe version of unquote. It only gets called if it's a string.
Add this function:
@function safe-unquote($param) {
@return if(type-of($param) == string, unquote($param), $param);
}
Then, change all unquote() functions to safe-unquote() inside of _unsemantic-vars.scss.

I was having issue parsing unsemantic through libsass as well and @shawn458 solution worked for me.

I can confirm it works, thanks @shawn458. The function can be simply copy/pasted in the beginning of _unsemantic-vars.scss.


Enable raycast nodes by default

Closes #31637.

Since we're breaking compatibility, tt makes sense to make the "Disabled" property into an "Enabled" one.

Since we're breaking compatibility, it makes sense to make the "Disabled" property into an "Enabled" one at the same time.

I think this applies to CollisionShape/Polygon, doesn't it?

@KoBeWi Indeed, I confused CollisionShape and RayCast.

I think it's fine to break compat now?
Note that the changes are quite simple because the raycasts are actually enabled and disabled on enter/exit callbacks:
https://github.com/godotengine/godot/blob/0ee0fa42e6639b6fa474b7cf6afc6b1a78142185/scene/2d/ray_cast_2d.cpp#L136-L141

16:02 <Akien> reduz: ok with enabling RayCasts by default in 4.0? #36307
16:03 <reduz> Akien: i dont have the slightest clue why they were disabled by default
16:05 <Akien> Hehe
16:05 <Akien> I guess that settles it :P

Thanks!

Shouldn't initialization be moved from constructors to declaration for these classes?

@Anutrix kinda yes, but should likely be done as coordinate effort (not all cases got converted), see also Akien response at https://github.com/godotengine/godot/pull/39695#issuecomment-646967961.


Error on lines with only spaces

When I run beancount-black on a file with some lines that only contain spaces, I get an error. This error is the same using CLI or the online beancount-formatter on beanhub.
Example: Note that the "blank" line between the two transactions contains three spaces.
2022-04-20 * "First transaction"
  Assets:Account1  -1 USD
  Assets:Account2     1 USD

2022-04-20 * "Second transaction"
   Assets:Account1 1 USD
   Assets:Account2  -1 USD

This gives the error
Something is wrong when parsing: Unexpected token Token('_NL', '\r\n') at line 4, column 4. Expected one of: * ACCOUNT * OPTION * $END * SECTION_HEADER * FLAG * METADATA_KEY * COMMENT * DATE * INCLUDE * PLUGIN Previous tokens: [Token('_NL', '\r\n')]

Hey @catanzaromj,
Thanks for reporting the issue, I will look into this soon when I have time.


Use Uniprot primary label for labelling protein items in Wikidata

While doing some entity mapping from scientific data to Wikidata, I came across the problem that the scientific data did not have identifiers for the proteins, which is not good, but what they did have is the exact Uniprot primary protein name label, so label matching would be possible.
The issue is that Wikidata frequently does not use these Uniprot primary labels, but some more verbose derivative. (nor can they be found in the aliases) Example (https://www.wikidata.org/wiki/Q21108705) with http://www.uniprot.org/uniprot/Q13003
So it would be helpful if the Uniprot primary label was at least part of the aliases, so it could be found while doing a string based mapping. (which is frequently the only mapping possible for data extracted from a paper).

Looks like it is (at least in this example) in the "other_names" field in mygene
Easy fix, to here: https://github.com/SuLab/scheduled-bots/blob/master/scheduled_bots/geneprotein/ProteinBot.py#L121

ok, if that's readily available in mygene
You can also get the labels with this SPARQL query from sparql.uniprot.org
PREFIX up:<http://purl.uniprot.org/core/>
PREFIX taxon:<http://purl.uniprot.org/taxonomy/>
PREFIX skos:<http://www.w3.org/2004/02/skos/core#>

SELECT ?protein ?name WHERE {
	?protein a up:Protein .
	?protein up:organism taxon:9606 .
        ?protein up:recommendedName ?recommended .
	?recommended up:fullName ?name .
}

Implemented with commits: https://github.com/SuLab/wdbiothings/commit/b76386135eb10d8717fc1aac4d50c3e1d7c620e4 https://github.com/SuLab/wdbiothings/commit/e9ceb27d163b1e0528cfc8cfb2c0093ed12dd38c https://github.com/SuLab/scheduled-bots/commit/23a6051066bb6b39deba897dce3f04206f5b350d
Example revision: https://www.wikidata.org/w/index.php?title=Q21100363&diff=prev&oldid=486569401


Update docs for multi-bot LLM and name change.

Summary
Updates to the docs for multi-bot capabilities, name change from AI Copilot to Copilot, and removing Beta label for v10 release.

Thank you, @crspeller! Is this docs PR associated with the v9.9 or v9.10 release?

@cwarnermm The plugin is released now. It will be prepackaged with 9.10

Thanks, @crspeller! I'm wondering whether multi-LLM support is releasing as part of v9.9 or v9.10.

@cwarnermm So the multi-bot stuff will be prepackaged with 9.10, but I think we can update the docs whenever given that I think many users at this point are going to go to the repository to download the plugin. Not exactly sure what the best practice here would be.

@crspeller - I agree that updating the terminology/naming needs to happen sooner than v9.10. I'm inclined to split this PR into 2: one for the language updates & one focusing on multi-LLM support queued for v9.10. I'll get the language updates into production early next week.

@crspeller @cwarnermm Docs look great! Left a few comments and made some adjustments for readability and clarity.

Thank you @crspeller and @azigler for the team effort updating our Copilot documentation!!

I'm going to make some updates to the configuration page based on the learnings from building the Academy course (such as the Ollama URL and how to fetch the correct Azure information).
You'll see a follow-up commit from me later this week @cwarnermm @crspeller.
I also accounted for this in the v10 release deliverables spreadsheet.

Very much appreciated, @azigler. Happy to support you wherever needed!

@cwarnermm The doc improvements based on the Academy videos are now done!


bug: Configuration from CLI is not working properly

Meltano Version
2.17.1
Python Version
3.8
Bug scope
Configuration (settings parsing, validation, etc.)
Operating System
Linux-debian??
Description
Configurations from running cli is giving an error while from meltano.yml works fine.
configuration - working
  loaders:
  - name: target-bigquery
    variant: z3z1ma
    pip_url: git+https://github.com/z3z1ma/target-bigquery.git
    config:
      overwrite: true

from CLI - not working
meltano config target-bigquery set overwrite true

gives you an error like below
2023-04-12T02:14:10.761972Z [info     ]     return schema.get(property, "") cmd_type=loader name=target-bigquery run_id=f241cfdd-bc93-4025-bc94-293f348f58e3 state_id=2023-04-12T021408--tap-salesforce--target-bigquery stdio=stderr
2023-04-12T02:14:10.762031Z [info     ] AttributeError: 'str' object has no attribute 'get' cmd_type=loader name=target-bigquery run_id=f241cfdd-bc93-4025-bc94-293f348f58e3 state_id=2023-04-12T021408--tap-salesforce--target-bigquery stdio=stderr

Code
No response

@drbjim I've logged https://github.com/meltano/hub/issues/1266 but it seems that it can also be an array:

A value of true will write to a temporary table and then overwrite the target table inside a transaction (so it is safe).
A value of false will write to the target table directly (append).
A value of an array of strings will evaluate the strings in order using fnmatch. At the end of the array, the value of the last match will be used.

I'm closing this since it's not a problem with Meltano but rather a plugin. Logged in the Hub repo: https://github.com/meltano/hub/issues/1266.


[Question] fail to submit flink Job

Which version of DolphinScheduler:
-[1.3.4-release]
flink:1.12.0
Additional context

使用海豚调度器提交flink出现以上问题，之后我修改了海豚的源码重新打包server.jar，把命令改成
flink run -m yarn-cluster -c 类名 jar包 -ys 1 -yn 2 -yjm 1G -ytm 2G -d --qu default 就能运行，

flink使用的版本是1.12.0，请问这是什么问题？

@Chaunceyctx This problem has been resolved in 1.3.5, the related issue is #3457, please use 1.3.5 or the latest 1.3.6

@Chaunceyctx This problem has been resolved in 1.3.5, and the related issue is #3457, so please use 1.3.5 or the latest 1.3.6

Thx!


chore: setup semantic release

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Import "X" could not be resolvedPylancereportMissingImports

Type: Bug
After updating to the latest VS code and pylance, my import doesn't work for the local module under the same project folder. It used to work well, but now it cannot detect the module.
Extension version: 2023.5.20
VS Code version: Code 1.78.2 (b3e4e68a0bc097f0ae7907b217c1119af9e03435, 2023-05-10T14:39:26.248Z)
OS version: Windows_NT x64 10.0.22000
Modes:
Sandboxed: No

I've tried re-install Pylance, VS code, or added extra path for root directory, but all seems not work. Anything I missed here?

This could be a dupe of #4357. Are your net drives UNC paths or did you mount them?

Yeah I am using a UNC path


how do i predict my model after i loaded the model

hi ... everyone
i can not find the suitable answer for my question?
https://stackoverflow.com/questions/60394098/how-do-i-predict-my-machine-translation-after-i-loaded-model-5
the problem is how do make a predict in seq2seq machine translation build with keras

ubuntu 18.04
python 3.6
keras 2.2.4
tensorflow 1.14

model.save('model.h5')
from tensorflow.keras.models import load_model
model = load_model('model.h5')
model.predict(sample(s))

hi thanks for replying but can you explain for me
i know about model.predict
but what should be the sample and S

hi thanks for replying but can you explain for me
i know about model.predict
but what should be the sample and S

What do you mean? This is where you supply your sample or samples for the model to predict on.

text = np.array(['how can i solve this question'])
print(text.shape)

res = model.predict(text)

i tried the above code but it gives me an error:
ValueError: Error when checking input: expected embedding_1_input to have shape (4,) but got array with shape (1,)
i tried

hi thanks for replying but can you explain for me
i know about model.predict
but what should be the sample and S

What do you mean? This is where you supply your sample or samples for the model to predict on.

hi thanks for replying but can you explain for me
i know about model.predict
but what should be the sample and S

What do you mean? This is where you supply your sample or samples for the model to predict on.

text = np.array(['how can i solve this question'])
print(text.shape)

res = model.predict(text)

i tried the above code but it gives me an error:
ValueError: Error when checking input: expected embedding_1_input to have shape (4,) but got array with shape (1,)
i mean i think the way am i trying to test is wrong i mean variable text initialized is wrong

Not to be rude but you need to take a few steps backs. Look up basic
tutorials on nueral networks.
On Tue, Feb 25, 2020, 5:17 PM BlackSnow76<EMAIL_ADDRESS>wrote:

text = np.array(['how can i solve this question'])
print(text.shape)
res = model.predict(text)
i tried the above code but it gives me an error:
ValueError: Error when checking input: expected embedding_1_input to have
shape (4,) but got array with shape (1,)
i tried
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/keras-team/keras/issues/13828?email_source=notifications&email_token=AB5OIMLNANR5ME3O4NHYXETREWKIRA5CNFSM4K3HLTX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEM5XMBI#issuecomment-591099397,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB5OIMOPIKJDGL772HEN6H3REWKIRANCNFSM4K3HLTXQ
.

Not to be rude but you need to take a few steps backs. Look up basic tutorials on nueral networks.
…
On Tue, Feb 25, 2020, 5:17 PM BlackSnow76 @.***> wrote: text = np.array(['how can i solve this question']) print(text.shape) res = model.predict(text) i tried the above code but it gives me an error: ValueError: Error when checking input: expected embedding_1_input to have shape (4,) but got array with shape (1,) i tried — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#13828?email_source=notifications&email_token=AB5OIMLNANR5ME3O4NHYXETREWKIRA5CNFSM4K3HLTX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEM5XMBI#issuecomment-591099397>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB5OIMOPIKJDGL772HEN6H3REWKIRANCNFSM4K3HLTXQ .

i am thankful for you but you know i am new in neural network i am sorry if my question is not make any sense

@BlackSnow76
Moving this issue to closed status as there has been no activity, in case you still face the error please create a new issue.


example usage

example will add in few days :)

ty, it is possible with this library to push a mp4 file to a rtmp server?

possible

thank you


Merging slightly-moved-around version of what Junbo and Haowen have been working on

@jimbozhang @qindazhu, FYI.

Also @pzelasko and @freewym, you might want to follow this repo.
It's super rough right now, I am not stressing about the structure, just treating it as a scratch pad and trying to move as fast as possible.

I was thinking the repo name is icefall..

I was thinking the repo name is icefall..

Snowfall as the draft of icefall, cool~ 👍

Cool (or cold)!
czw., 12 lis 2020, 02:51 użytkownik Junbo Zhang<EMAIL_ADDRESS>napisał:

I was thinking the repo name is icefall..
Snowfall as the draft of icefall, cool~ 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/k2-fsa/snowfall/pull/1#issuecomment-725904437, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADZRKQDSEEZUDAY3TM6DUPTSPOHX3ANCNFSM4TS54KBQ
.

BTW. I tried to install k2 from the source on CLSP grid, got the error msg when cmake:
-- Could NOT find CUDNN (missing: CUDNN_INCLUDE_DIR CUDNN_LIBRARY)
CMake Warning at /home/ywang/anaconda3/lib/python3.7/site-packages/torch/share/cmake/Caffe2/public/cuda.cmake:110 (message):
Caffe2: Cannot find cuDNN library.  Turning the option off
Call Stack (most recent call first):
/home/ywang/anaconda3/lib/python3.7/site-packages/torch/share/cmake/Caffe2/Caffe2Config.cmake:88 (include)
/home/ywang/anaconda3/lib/python3.7/site-packages/torch/share/cmake/Torch/TorchConfig.cmake:40 (find_package)
cmake/torch.cmake:10 (find_package)
CMakeLists.txt:101 (include)
-- Autodetected CUDA architecture(s):  6.1 6.1 6.1 6.1
-- Added CUDA NVCC flags for: -gencode;arch=compute_61,code=sm_61
CMake Error at /home/ywang/anaconda3/lib/python3.7/site-packages/torch/share/cmake/Caffe2/Caffe2Config.cmake:96 (message):
Your installed Caffe2 version uses cuDNN but I cannot find the cuDNN
libraries.  Please set the proper cuDNN prefixes and / or install cuDNN.
Call Stack (most recent call first):
/home/ywang/anaconda3/lib/python3.7/site-packages/torch/share/cmake/Torch/TorchConfig.cmake:40 (find_package)
cmake/torch.cmake:10 (find_package)
CMakeLists.txt:101 (include)
I don't know why it automatically located Python in  /home/ywang/anaconda3. Do you know how to change that path? Also, how to fix this cuDNN issue?

I attempted it before and these steps almost worked: maybe you can pick up from here and figure it out.
conda create -n k2 python=3.7
conda activate k2
conda install gxx_linux-64
conda install -c nvidia cudnn=7.6.5 cudatoolkit=10.2 nvcc_linux-64
conda install -c pytorch pytorch

mkdir build
cd build
cmake -DCMAKE_C_COMPILER=/home/pzelasko/miniconda3/envs/k2/bin/x86_64-conda_cos6-linux-gnu-gcc -DCMAKE_CXX_COMPILER=/home/pzelasko/miniconda3/envs/k2/bin/x86_64-conda_cos6-linux-gnu-g++ -DCMAKE_CUDA_COMPILER=/usr/local/cuda/bin/nvcc -DPYTHON_EXECUTABLE=/home/pzelasko/miniconda3/envs/k2/bin/python -DCUDNN_LIBRARY_PATH=/home/pzelasko/miniconda3/envs/k2/lib/libcudnn.so -DCUDNN_INCLUDE_PATH=/home/pzelasko/miniconda3/envs/k2/include/ ..

BTW. I tried to install k2 from the source on CLSP grid, got the error msg when cmake:

@freewym
Have you fixed this problem?

BTW. I tried to install k2 from the source on CLSP grid, got the error msg when cmake:

@freewym
Have you fixed this problem?

Yes, by following exactly what @pzelasko suggested.

Great

By the way, the latest k2  can be installed without compiling it from source by downloading the artifacts from k2's GitHub actions.
For example, by following this link https://github.com/k2-fsa/k2/actions/runs/359678465

Cool!
On Thu, Nov 12, 2020 at 7:15 PM Fangjun Kuang<EMAIL_ADDRESS>wrote:

By the way, the latest k2 can be installed without compiling it from
source by downloading the artifacts from k2's GitHub actions.
For example, by following this link
https://github.com/k2-fsa/k2/actions/runs/359678465
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/k2-fsa/snowfall/pull/1#issuecomment-726421152, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2YBETXEQM26AVHHZRCJULSPR3CZANCNFSM4TS54KBQ
.

--
Yiming Wang
Department of Computer Science
The Johns Hopkins University
3400 N. Charles St.
Baltimore, MD 21218

@csukuangfj regarding the compilation method:
do you think @pzelasko's method is a good one?
Other than creating conda environments, is there a recommended way to tell cmake which python version it is supposed to use?

is there a recommended way to tell cmake which python version it is supposed to use?

Yes, I think I mentioned before that we can use
cmake -DPYBIND11_PYTHON_VERSION=3.6 ..

to use a specified Python version 3.6 instead of the latest Python found on $PATH.

-DPYTHON_EXECUTABLE=xxxxx is also an alternative.

It has been discussed in https://github.com/k2-fsa/k2/issues/225

Mm, after thinking about it I dont think I want to add that back right now.
The issue is that that compose() is really not the same as FST compose,
because the 'labels' are matched, so we can't
just identify the 'labels' with ilabels and aux_labels with olabels.
I think by adopting that name we would just be confusing people.
On Fri, Nov 13, 2020 at 3:30 PM Fangjun Kuang<EMAIL_ADDRESS>wrote:

@csukuangfj commented on this pull request.
In egs/librispeech/asr/simple_v1/train.py
https://github.com/k2-fsa/snowfall/pull/1#discussion_r522729090:

return total_objf

+def main():

load L, G, symbol_table

lang_dir = 'data/lang_nosp'
with open(lang_dir + '/L.fst.txt') as f:

   L = k2.Fsa.from_openfst(f.read(), acceptor=False)

with open(lang_dir + '/G.fsa.txt') as f:

   G = k2.Fsa.from_openfst(f.read(), acceptor=True)

with open(lang_dir + '/words.txt') as f:

   symbol_table = k2.SymbolTable.from_str(f.read())

L = k2.arc_sort(L.invert_())

I implemented compose in k2-fsa/k2#282
https://github.com/k2-fsa/k2/pull/282 but it was later removed.
The code is available at k2-fsa/k2@99d7b14
#diff-e02b2cfd8da9130757f0c5a4c623125f76185c37680c67919999f65b2d450187R167
https://github.com/k2-fsa/k2/commit/99d7b14c363655f3a86d4a207b8180e9178f15ce#diff-e02b2cfd8da9130757f0c5a4c623125f76185c37680c67919999f65b2d450187R167
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/k2-fsa/snowfall/pull/1#discussion_r522729090, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZFLO5Z6EHZSMM5SPAX2CTSPTOAVANCNFSM4TS54KBQ
.

The code that is supposed to do that is in fsa_algo.py:

    # now copy tensor attributes that are in b_fsa but are not in a_fsa

    *for* name, b_value *in* b_fsa.named_tensor_attr():

        *if* *not* *hasattr*(out_fsa, name):

            value = index_select(b_value, b_arc_map)

            *setattr*(out_fsa, name, value)

(assuming it was in b).
You could add debugging code in there to see what happened, maybe.
On Sun, Nov 22, 2020 at 6:16 PM Yiming Wang<EMAIL_ADDRESS>wrote:

@freewym commented on this pull request.
In egs/librispeech/asr/simple_v1/train.py
https://github.com/k2-fsa/snowfall/pull/1#discussion_r528313112:

return total_objf

+def main():

load L, G, symbol_table

lang_dir = 'data/lang_nosp'
with open(lang_dir + '/L.fst.txt') as f:

   L = k2.Fsa.from_openfst(f.read(), acceptor=False)

with open(lang_dir + '/G.fsa.txt') as f:

   G = k2.Fsa.from_openfst(f.read(), acceptor=True)

with open(lang_dir + '/words.txt') as f:

   symbol_table = k2.SymbolTable.from_str(f.read())

L = k2.arc_sort(L.invert_())

@freewym https://github.com/freewym currently that is not supported, it
will crash. But you can fix it by moving the aux_labels of B to a different
name. Currently the result would end up with 3 sets of labels in that case,
the labels, aux_labels and new_labels. If you really only wanted 2 of those
you could, say, copy the new_labels to labels and delete new_labels.
Assuming that was the one you wanted as the 'labels'.
@danpovey https://github.com/danpovey Assuming C=k2.intersect(A, B), it
looks like the renamed aux_labels in B (renamed as temp_labels) does not
appear in C (i.e., hasattr(C, "temp_labels") == False)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/k2-fsa/snowfall/pull/1#discussion_r528313112, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZFLO5G556L7PIPVFGC73LSRDQIHANCNFSM4TS54KBQ
.


Change logic for BGV modulus switching in the AUTO* modes

https://gitlab.com/palisade/palisade-development/-/issues/365

We decided not to implement this change because:

It does not make sense for FlexibleAutoExt because the logic of choosing moduli in this mode depends on the rescaling to occur, and the for the ciphertext noise scaling degree to always be 2.
It does not make sense for CKKS because we have to keep track of arbitrarily large floating-point scaling factors.

Given the above, to implement this change, we have to create BGV-specific logic for the modes FIXEDAUTO and FLEXIBLEAUTO, which makes the code unnecessarily complicated and more difficult to debug without a significant performance increase. We prefer the BGV code to be as similar as possible to CKKS, unless there are significant gains to be made from having scheme-specific code.


Add bot to manage stale issues and pull requests

https://github.com/apps/stale looks like a good option

We should discuss if we still want this functionality in Apposdy repositories, and how this affects our workflow, before adding this.

Does not look like a thing we need right now.


feat: Locations Formats the layout if it does not exist

Purpose of the pull request
refer to #11534

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

Codecov Report

Merging #11535 (6847732) into dev (a974ba7) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev   #11535      +/-   ##
============================================
- Coverage     39.69%   39.66%   -0.03%
+ Complexity     4696     4693       -3
============================================
  Files           993      993
  Lines         37692    37674      -18
  Branches       4198     4190       -8
============================================
- Hits          14962    14944      -18
- Misses        21159    21166       +7
+ Partials       1571     1564       -7

Impacted Files
Coverage Δ

...r/plugin/registry/zookeeper/ZookeeperRegistry.java
43.54% <0.00%> (-6.46%)
:arrow_down:

...erver/master/processor/queue/TaskEventService.java
75.00% <0.00%> (-5.36%)
:arrow_down:

...org/apache/dolphinscheduler/remote/utils/Host.java
42.55% <0.00%> (-2.13%)
:arrow_down:

...e/dolphinscheduler/remote/NettyRemotingClient.java
51.38% <0.00%> (-1.39%)
:arrow_down:

...r/plugin/task/sqoop/parameter/SqoopParameters.java
55.12% <0.00%> (-1.29%)
:arrow_down:

...rver/master/runner/task/BlockingTaskProcessor.java
75.86% <0.00%> (-0.55%)
:arrow_down:

...eduler/api/service/impl/DataSourceServiceImpl.java
27.90% <0.00%> (ø)

...cheduler/server/master/utils/DependentExecute.java
0.00% <0.00%> (ø)

.../dolphinscheduler/plugin/task/datax/DataxTask.java
0.00% <0.00%> (ø)

...phinscheduler/plugin/task/chunjun/ChunJunTask.java
0.00% <0.00%> (ø)

... and 8 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


issue when using flex box?

I'm not sure what's going on here, but given a two column layout, using flex box, the side column (which has hc-sticky applied) is getting it's width reset incorrectly.
Not much to go on, I know, but any ideas of where to start looking? What can I give  you to help debug?

If it's any help, it appears to be picking up margin: auto, but I'm not sure why.

Close this. I figured it out. I needed to set a width.


Add support of Dragon Bones 5.5 skeleton format

I have the following error when parsing DB 5.5 skeleton files:
Error: Nonsupport data version.
	at dragonBones.parsers::ObjectDataParser/parseDragonBonesData()
	at dragonBones.factories::BaseFactory/parseDragonBonesData()
	at creature::Tree$/setupFactory()
	at DragonBonesTest/onAssetsReady()
	at DragonBonesTest/onLoadQueueProgressed()
	at Function/AssetManager.as$3:anonymous()
	at Function/http://adobe.com/AS3/2006/builtin::apply()
	at SetIntervalTimer/onTimer()
	at flash.utils::Timer/_timerDispatch()
	at flash.utils::Timer/tick()

Thanks in advance for supporting it. 🙂

Hi, AS can not support 5.5 version yet, you could export data to 5.0 version.

Hello, ok thanks for the workaround.
Are you waiting for something specific? Perhaps we could open an issue on the Starling-Framework repository if you are waiting on a special feature.

Currently we are developing TS, CPP and C # runtimes, and still developing some new features, the future plan is to wait for these three runtimes stability, and then consider to synchronize the AS and other runtimes to the latest version, this may take a long time.

已经过去大半年了，有更新计划了么？5.5才有网格的吧？

AS3 runtime is dead?


Security handeshake fails with FD shutdown in forked child

I am trying to make c++ grpc server a daemon process by forking a child and making parent exit. But after that the client handshake starts to fail.
E0307 01:15:58.221786152   27094 handshake.c:128]            Security handshake failed: {"created":"@1488878158.221756436","description":"Handshake read failed","file":"src/core/lib/security/transport/handshake.c","file_line":237,"referenced_errors":[{"created":"@1488878158.221740996","description":"FD shutdown","file":"src/core/lib/iomgr/ev_epoll_linux.c","file_line":948}]}
This happens when fork() is called after the call to BuildAndStart(). If the same fork is done before BuildAndStart() everything works fine.
Wondering if this a bug or not ?

See http://stackoverflow.com/questions/42867461/ssl-handshake-fails-in-grpc-server-after-calling-fork/


Add Alpine-based (*-unknown-linux-musl) Docker image.

On aarch64, an Alpine-based vercel-log-drain image is 29.4MiB, compared to the current Debian-based image at 146MiB.
Everything here is functionally identical to the current Dockerfile.

@miceg willing to take a stab at updating the GitHub actions workflows? Otherwise, I'll merge this and update them.


Added a docstring to paulistring module.

Fixes: #2022

@googlebot I signed it!

Automerge cancelled: A status check is failing.


Turn on/off file plugin after before/scan

@klauer Will this cause you any trouble?

closes https://github.com/NSLS-II/ophyd/issues/133

Probably not. You might have seen from some of my recent changes to the area_detector module that I like the ability to at least toggle functionality like this.
Sometimes non-optional features/settings/whatever are buried so deeply into the class hierarchy you have no choice but to re-implement everything surrounding it just to skip it in your subclass.

This needs to go in before the deployment to CHX

@klauer Yeah I agree that's a major flaw with the current design. I think we can do better in the medium term.

@danielballan should this go in before too much longer?

Merged so that we don't break CSX. A more customizable AreaDetector is high on the to-do list, but it's not going to make the cutoff for September 30.


Improved support for OpenCL

Jenkins, test this please.

Jenkins, test this please.

The failures in sanity checks are terminating all other tests.
https://ci.tensorflow.org/job/tensorflow-pull-requests-sanity/2184/console

I fixed the sanity check failure.

Looks like after this PR on MacOS, one shard of the cwise_ops_test is consistently failing with the following error:
FAIL: testBCast_15B (__main__.BinaryOpTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/private/var/tmp/_bazel_jenkins/47802726cfb6783f0513af299bd0e285/execroot/tensorflow-master-mac/bazel-out/local-opt/bin/tensorflow/python/kernel_tests/cwise_ops_test.runfiles/org_tensorflow/tensorflow/python/kernel_tests/cwise_ops_test.py", line 1031, in testBCast_15B
    self._testBCastB([10, 3, 1, 2], [3, 1, 2])
  File "/private/var/tmp/_bazel_jenkins/47802726cfb6783f0513af299bd0e285/execroot/tensorflow-master-mac/bazel-out/local-opt/bin/tensorflow/python/kernel_tests/cwise_ops_test.runfiles/org_tensorflow/tensorflow/python/kernel_tests/cwise_ops_test.py", line 829, in _testBCastB
    self._testBCastByFunc(funcs, xs, ys)
  File "/private/var/tmp/_bazel_jenkins/47802726cfb6783f0513af299bd0e285/execroot/tensorflow-master-mac/bazel-out/local-opt/bin/tensorflow/python/kernel_tests/cwise_ops_test.runfiles/org_tensorflow/tensorflow/python/kernel_tests/cwise_ops_test.py", line 814, in _testBCastByFunc
    self._compareBCast(ys, xs, dtype, np_func, tf_func)
  File "/private/var/tmp/_bazel_jenkins/47802726cfb6783f0513af299bd0e285/execroot/tensorflow-master-mac/bazel-out/local-opt/bin/tensorflow/python/kernel_tests/cwise_ops_test.runfiles/org_tensorflow/tensorflow/python/kernel_tests/cwise_ops_test.py", line 795, in _compareBCast
    self._compareGpu(x, y+ 0.1, np_func, tf_func)
  File "/private/var/tmp/_bazel_jenkins/47802726cfb6783f0513af299bd0e285/execroot/tensorflow-master-mac/bazel-out/local-opt/bin/tensorflow/python/kernel_tests/cwise_ops_test.runfiles/org_tensorflow/tensorflow/python/kernel_tests/cwise_ops_test.py", line 575, in _compareGpu
    self.assertAllClose(np_ans, tf_gpu)
  File "/private/var/tmp/_bazel_jenkins/47802726cfb6783f0513af299bd0e285/execroot/tensorflow-master-mac/bazel-out/local-opt/bin/tensorflow/python/kernel_tests/cwise_ops_test.runfiles/org_tensorflow/tensorflow/python/framework/test_util.py", line 449, in assertAllClose
    np.testing.assert_allclose(a, b, rtol=rtol, atol=atol)
  File "/Library/Python/2.7/site-packages/numpy-1.11.0-py2.7-macosx-10.11-intel.egg/numpy/testing/utils.py", line 1391, in assert_allclose
    verbose=verbose, header=header)
  File "/Library/Python/2.7/site-packages/numpy-1.11.0-py2.7-macosx-10.11-intel.egg/numpy/testing/utils.py", line 733, in assert_array_compare
    raise AssertionError(msg)
AssertionError:
Not equal to tolerance rtol=1e-06, atol=1e-06

(mismatch 1.66666666667%)
 x: array([[[[   1.000000  +0.j      ,    1.474711  +0.703009j]],

        [[   2.064002  +1.518696j,    2.834290  +2.474841j]],...
 y: array([[[[   1.000000  +0.j      ,    1.474711  +0.703009j]],

        [[   2.064002  +1.518697j,    2.834289  +2.47484j ]],...

----------------------------------------------------------------------
Ran 3 tests in 13.699s

FAILED (failures=1)

@benoitsteiner @lukeiwanski I looked at the code, and I see that in _compareBCast in cwise_ops_test we add 0.1 to one of the args.
Is it by any chance a leftover?
I will send a PR to fix.


Upgrading from 1.0 to 2.0.alpha* causes severe lag

[x] I confirm that this is an issue rather than a question.

Bug report
I recently tried to update Hyperion.NG running on my Vero 4k+ from 1.0 (380f9b5d) to 2.0.alpha.5 (e796155) and 2.0.alpha.6 (f5583de) but the newer versiones introduced severe lagging of both effects and grabbing on my device.
I have not tried the earlier versions of 2.0, just the two latest, but if it would be useful I can test those too and see if earlier versions are better compared to the newer ones, I've also not tested the latest commit.
I have a NodeMCU attached trough WiFi which controls the LED's (277 LEDs) and Hyperion.NG connects to this trough the UDPRAW configuration. The NodeMCU is running WLED 0.10 and any animations set by it works fine, nothing is changed on the NodeMCU side between the upgrade of Hyperion.NG.
If I downgrade (Uninstall -> Install) 380f9b5d it's back to be butter smooth in both grabbing and effects with no lagging effects.
Steps to reproduce
Upgrade to any of the mentioned new versions.
What is expected?
That effects and grabbing is butter smooth.
What is actually happening?
Both effects and grabbing introduces severe lagging.
System
Hyperion Server:

Build:       (HEAD detached at f5583de8) (Sersch-f7865b45/f5583de8-1590611619)
Build time:  Jul 16 2020 09:05:52
Git Remote:  https://github.com/hyperion-project/hyperion.ng.git
Version:     2.0.0-alpha.6
UI Lang:     auto (BrowserLang: sv-SE)
UI Access:   expert
Avail Capt:  v4l2,framebuffer,amlogic,qt

Hyperion Server OS:

Distribution: Open Source Media Center
Arch:         arm64
Kernel:       linux (3.14.29-158-osmc (WS: 32))
Browser:      Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.116 Safari/537.36

we have a loooot of changes with the next release, i would recommend to wait for next release before we investigate too much time, if the problems still occure then we can have a deeper look, is this okay for you?

@tpmodding I think I have narrowed it down, I continued yesterday and tested a few things. What I did do that got it all to work as expected, was that I removed all previous configuration and did a full uninstall.
Then I installed the latest commit in the repository and configured everything from scratch, then it all worked perfectly. I'm not sure if it's something fixed in the latest version compared to the released alpha.6, or if there perhaps is something in the configuration that have changed between 1.0 -> 2.0 that can cause it to behave like that?
One thing that stood out to me, is that in 1.0 I had Latch Time set and it caused no problems (I think I used some default value possibly) but in 2.0 it's 0. Not sure if the behaviour of that have changed? It was the only thing that stood out too me when I compared the configuration for the working 2.0 version, and my old backup of 1.0.

@orecus i will close this...if you still have a need of the latch time, i would ask you to open a new issue.
thanks


[python] add lint check for src code in CI

Add lint check in CI. After this PR merge, please remember to run following command to make sure src code is clean before trigger CI:
PS D:\dev\typespec\packages\http-client-python> npm run format
PS D:\dev\typespec\packages\http-client-python> npm run lint:py

No changes needing a change description found.

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs


What is New Requests section?

I'm a brand new visitor to the website, so maybe I have the same question(s) as other new people(?)
I don't understand what the New Requests section is for? If I click on the title it shows a project's details. Maybe add some text about what/how/why it exists and how things get added to it?

Better? I'm not a native English speak so I'm not sure if it's understable?
Thanks for opening the issue!


When will the code be released?

Nice work! And when will the code be released?

Hope the code and weight release.

It looks so cool. I really can't wait for the code. PS: Is the code in the huggingface space not enough to work with?

The model is here: https://huggingface.co/wangfuyun/AnimateLCM

How to use this model? Could you share the example code? thx a lot  https://huggingface.co/wangfuyun/AnimateLCM

Hi, every one. I just upload a beta version t2v space for your testing, see AnimateLCM.

Thanks for the update! I'm very hyped for the image to video release. Great work! I was always looking for a low latency solution

Is there a way to run it on my local machine?

Hi @G-U-N,
Congrats on this! Are there any plans to release the trainer code or train a v3 version?


Create a TsGroup from an iterable of Ts/Tsd objects

It doesn't seem to make a ton of sense to me to require that users manually package their timestamp/series objects into a dict when creating TsGroup objects, since the keys are required to be unique integers. I would guess that the vast majority of the time, users would be just doing {0: ts0, 1: ts1, ...}. Sure, this can be easily done by saying data = dict(enumerate(ts_list)), but why not just allow the user to say data = ts_list and do the dict creation automatically?
If the change described above is not desired, the second commit is probably still worth including. It ensures that the keys in .data and .index are in the same order by doing this:
data = {k: data[k] for k in self.index}

This might not be assured if bypass_check == True.
I added some tests for the new functionality. Again, any and all feedback/concerns/thoughts are welcome!

You can check the linting with the following commands :
black --check pynapple
isort --check pynapple --profile black
flake8 pynapple --max-complexity 10
coverage run --source=pynapple --branch -m pytest tests/
coverage report -m

Reformatted with black, hopefully all good now. Let me know if you have any further comments/requests/suggestions.

Great thanks Eric


Installation on ARM64 - Missing Dependency (linux-arm64)

Expected Behavior
I attempted to install insomnia from the AUR on arch linux, but the installation fails due to an unavailable http resource (linux-arm64). I also tried bootstrapping manually from the cloned repo and it yielded the same behavior.
Actual Behavior
Hello,
I'm attempting to install insomnia from the AUR on my linux setup using yay(package manager). I was using nodejs-v19.x, but the bootstrap script warned it was too new and haulted. I downgraded from 19.x to 16.19.0(gallium) using nvm and tried again. The bootstrap script passed the environment checks, but haulted again due to what appears to be a missing dependency. It wasn't able to pull down linux-arm64 from a web resource.
Error: response status 404 Not Found on https://node-precompiled-binaries.grpc.io/grpc-tools/v1.12.3/linux-arm64.tar.gz
I'm running arch linux 6.1.0 and attempting to install insomnia marked insomnia-core-2022.7.5 according to the logs.
Reproduction Steps
Installation from AUR using yay

Open terminal
Type yay -Sy insomnia
Wait for installation to complete. It should fail looking for linux-arm64 dependency

Installation from cloned repo

cd <cloned-repo-dir>
npm run bootstrap
Installation should fail due to missing dependency

Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
N/A
Insomnia Version
2022.7.5
What operating system are you using?
Other Linux
Operating System Version
6.1.0
Installation method
yay package manager / cloned repo
Last Known Working Insomnia version
N/A - Fresh installation

Log file details...
...
674 timing build:link:node_modules/mocha Completed in 44ms
675 timing build:link:node_modules/prettier Completed in 44ms
676 timing build:link:node_modules/nopt Completed in 44ms
677 timing build:link:node_modules/semver Completed in 44ms
678 timing build:link:node_modules/resolve Completed in 44ms
679 timing build:link:node_modules/rimraf Completed in 44ms
680 timing build:link:node_modules/update-browserslist-db Completed in 44ms
681 timing build:link:node_modules/ts-node Completed in 44ms
682 timing build:link:node_modules/uglify-js Completed in 44ms
683 timing build:link:node_modules/which Completed in 44ms
684 timing build:link:node_modules/typescript Completed in 44ms
685 timing build:link:node_modules/uuid Completed in 44ms
686 timing build:link:node_modules/mocha/node_modules/which Completed in 43ms
687 timing build:link Completed in 46ms
688 info run<EMAIL_ADDRESS>install node_modules/grpc-tools node-pre-gyp install
689 info run<EMAIL_ADDRESS>install { code: 1, signal: null }
690 timing reify:rollback:createSparse Completed in 560ms
691 timing reify:rollback:retireShallow Completed in 0ms
692 timing command:install Completed in 11227ms
693 verbose stack Error: command failed
693 verbose stack     at ChildProcess.<anonymous> (/home/<my-username>/.cache/yay/insomnia/src/insomnia-core-2022.7.5/.nvm/versions/node/v16.17.0/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:63:27)
693 verbose stack     at ChildProcess.emit (node:events:513:28)
693 verbose stack     at maybeClose (node:internal/child_process:1093:16)
693 verbose stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
694 verbose pkgid<EMAIL_ADDRESS>695 verbose cwd /home/<my-username>/.npm/_cacache/tmp/git-clone3bSRDW
696 verbose Linux 6.1.0-asahi-2-2-edge-ARCH
697 verbose node v16.17.0
698 verbose npm  v8.15.0
699 error code 1
700 error path /home/<my-username>/.npm/_cacache/tmp/git-clone3bSRDW/node_modules/grpc-tools
701 error command failed
702 error command sh /tmp/install-f0a1bab9.sh
703 error response status 404 Not Found on https://node-precompiled-binaries.grpc.io/grpc-tools/v1.12.3/linux-arm64.tar.gz
704 error node-pre-gyp info it worked if it ends with ok
704 error node-pre-gyp info using<EMAIL_ADDRESS>704 error node-pre-gyp info using<EMAIL_ADDRESS>| linux | arm64
704 error node-pre-gyp info check checked for "/home/<my-username>/.npm/_cacache/tmp/git-clone3bSRDW/node_modules/grpc-tools/bin/grpc_tools.node" (not found)
704 error node-pre-gyp http GET https://node-precompiled-binaries.grpc.io/grpc-tools/v1.12.3/linux-arm64.tar.gz
704 error node-pre-gyp ERR! install response status 404 Not Found on https://node-precompiled-binaries.grpc.io/grpc-tools/v1.12.3/linux-arm64.tar.gz
704 error node-pre-gyp ERR! install error
704 error node-pre-gyp ERR! stack Error: response status 404 Not Found on https://node-precompiled-binaries.grpc.io/grpc-tools/v1.12.3/linux-arm64.tar.gz
704 error node-pre-gyp ERR! stack     at /home/<my-username>/.npm/_cacache/tmp/git-clone3bSRDW/node_modules/@mapbox/node-pre-gyp/lib/install.js:67:15
704 error node-pre-gyp ERR! stack     at processTicksAndRejections (node:internal/process/task_queues:96:5)
704 error node-pre-gyp ERR! System Linux 6.1.0-asahi-2-2-edge-ARCH
704 error node-pre-gyp ERR! command "/home/<my-username>/.cache/yay/insomnia/src/insomnia-core-2022.7.5/.nvm/versions/node/v16.17.0/bin/node" "/home/<my-username>/.npm/_cacache/tmp/git-clone3bSRDW/node_modules/.bin/node-pre-gyp" "install"
704 error node-pre-gyp ERR! cwd /home/<my-username>/.npm/_cacache/tmp/git-clone3bSRDW/node_modules/grpc-tools
704 error node-pre-gyp ERR! node -v v16.17.0
704 error node-pre-gyp ERR! node-pre-gyp -v v1.0.10
704 error node-pre-gyp ERR! not ok
705 verbose exit 1
706 timing npm Completed in 11260ms
707 verbose unfinished npm timer reify<PHONE_NUMBER>452
708 verbose unfinished npm timer reify:build<PHONE_NUMBER>734
709 verbose unfinished npm timer build<PHONE_NUMBER>737
710 verbose unfinished npm timer build:deps<PHONE_NUMBER>737
711 verbose unfinished npm timer build:run:install<PHONE_NUMBER>906
712 verbose unfinished npm timer build:run:install:node_modules/grpc-tools<PHONE_NUMBER>906
713 verbose code 1
714 error A complete log of this run can be found in:
714 error     /home/<my-username>/.npm/_logs/2023-02-14T14_00_36_419Z-debug-0.log

I have run into the same issue, it seems grpc-tools started shipping linux-arm64 binaries since v1.12.4 and the Kong's fork of grpc-reflection-js uses v1.12.3, bumping the version there should fix this issue.

I have run into the same issue, it seems grpc-tools started shipping linux-arm64 binaries since v1.12.4 and the Kong's fork of grpc-reflection-js uses v1.12.3, bumping the version there and bumping version of the fork in insomnia should fix this issue.

Hi @jkbz64, I have no experience with AUR and arch, but bought a nice Pinetab2 running arch on arm64 and need to use Insomnia. Could you please explain how to bump the grpc-tools binary version in order to build the package?
Any help would be greatly appreciated.
Regards,
Nicolas

@filfreire any ideas?

I don't have arm64 but if someone here who does can confirm that PR #6158 works I can get it into the next release.
Thanks!

I don't have arm64 but if someone here who does can confirm that PR #6158 works I can get it into the next release. Thanks!

Can confirm this has worked for me, compiling process went smoothly.

While trying to package it with npm run app-package (not sure if it's intended way?) I'm getting ../insomnia/packages/insomnia/node_modules/app-builder-bin/linux/arm64/app-builder process failed ERR_ELECTRON_BUILDER_CANNOT_EXECUTE Exit code: 1.

You may need to tinker with the electron-builder.js file, perhaps @filfreire can shed some light as I believe he's had it building on his M1 before.

Hi @filfreire and @jackkav, I was able finally to install Insomnia in my Pinetab2 (AARCH64) using "yay -S insomnia" and editing the packages.json in the downloaded source folder (.cache/yay/insomnia/packages) using the change in #6158.
Thanks for your valuable help!
Regards from Colombia

Should be able to avoid that last step once we have a full release out 🤞

Hey all,
What's the anticipated timing on an arm64 release? Would love to get this running on Ubuntu on an arm64 chip.
Thanks for all of the work!!

@tc-mccarthy It should already work if you use the beta version.

@jackkav thanks! I am trying to use the beta's deb file but ubuntu is throwing an error that the architecture doesn't match. Am I missing something?

@jackkav quick follow up. I pulled the git repo, switched to<EMAIL_ADDRESS>and have tried npm run app-build && npm run app-package.
It yields
Could not open '/lib/ld-linux.so.2': No such file or directory

could be releated to your glibc version, make sure you're on a recent version of Ubuntu, this isn't really an insomnia issue, its electron or electron-builder.

@jackkav just wanted to reach out and thank you for your help on this. It ended up being an issue with electron-builder, just like you said. Evidently there is a known issue where electron-builder fetches the x86 version of the FPM package, which it uses for compiling debs. I was able to install ruby-dev and then the fpm gem natively into my system and then exported USE_SYSTEM_FPM=true, which instructs electron-builder to use the gem instead of the node_module, which allowed everything to compile as needed. HOURS of research and trial and error. but I have it running on arm64 now!


Setup your Mac: Wait for dialog to close before exiting

When running the Setup your Mac.bash script from a Jamf policy, the dialog window will automatically close once Jamf is done executing the policy. This does not give the user a chance to review the status and read the final message update.
To resolve this issue, I added a wait statement before the exit "${exitCode}" in the finalise function.

Nice, @pyther.
You're welcome to submit a PR (after I fix Issue #3).

@pyther
Can you supply the wait statement you added? I'm encountering a similar issue with Jamf closing the dialog too quickly

PR: https://github.com/dan-snelson/dialog-scripts/pull/5

https://snelson.us/2022/09/setup-your-mac-via-swiftdialog-1-2-7/#completion-action


Windows Use

I would like to use this package on Windows. However, when trying to import the package the following error is raised:
RuntimeError:` Couldn't find jackserver library
I suppose this is related to this issue. Any hints for me attempting to fix this? :)
Thanks

I will try to compile jack myself. I had JACK 1.9.22 installed and noticed that jackserver.lib is not in the lib folder...

I think, I made it work somehow a year ago, at the time I published the issue you mentioned. Did you try doing what @falkTX suggested here: https://github.com/jackaudio/jack2/issues/856#issuecomment-1070965955?

Previously, jackserver library was included in official package. Did something changed?

If it didn’t, we could probably find a way to make jack_server work without any hacks on windows consistently after installing JACK

Previously, jackserver library was included in official package. Did something changed?

No, sorry, I was mistaken. Anyhow, I managed to fix the problem (in an ugly way by adding my JACK2 install path - C:\Program Files\JACK2) to the PATH environment variable.

I think, I made it work somehow a year ago, at the time I published the issue you mentioned. Did you try doing what @falkTX suggested here: jackaudio/jack2#856 (comment)?

Hey, it looks like I have figured how to use winreg to find the JACK install folder. I will have to look into the source code a little deeper to understand how to use this with Windows :)
>>> import winreg
>>>
>>> handle = winreg.OpenKey(winreg.HKEY_LOCAL_MACHINE,
...     r"Software\JACK")
>>>
>>> num_values = winreg.QueryInfoKey(handle)[1]
>>> for i in range(num_values):
...     print(winreg.EnumValue(handle, i))
...
('ServerExecutable', 'C:\\Program Files\\JACK2\\jackd.exe', 1)
('InstallPath', 'C:\\Program Files\\JACK2', 1)
('Version', 'v1.9.22', 1)


Firefox dev bin

Might this repo be a better host for firefox developer edition?

This change is

@garbas this builds fine for me


Feature: special workspace option: blur area around special workspace

Good day to you!
suggesting  option for special workspace: blurring area outside windows, for minimizing distractions around workarea
before:

after:

thank you!

why?

@vaxerski
for minimizing distractions around workarea
similar to popup windows in iphone
or maybe not blurring but dimming backgroun

UPD.
I think it will be universal to add option to dimm all background except some windows, if they are focused, so we can even apply it in special workspace scenario,
windowrule=dimm_arround,^(confirm_dialogue)$

and some rules with constraints like "if window in special workspace"

added dim_special in b5f5c26be3074a16556c2b7982029fbfcf502b16

added dimaround window rule in a6699ef30c0a7f66c4b1ff6e38ea836b8e898015
this is as far as I'm probably going to go.
Cheers

@vaxerski
checked it: there is some artifacts, when i'm killing window with dim_around rule
everything else is good!

759490689c3bcb897c900874fcf3be30d72ec74f

Is there any way to disable the dimaround on special workspace windows, just like i3?

blur aint cheap


Fix PEP-8 Violations

@mambocab to review.

I'm aware of the failing Travis complaing, and it is okay. Just an existing 600 char line that I didn't have the stamina to fix

Go for it. Thanks!


Use class-based NamedTuple for readability

This defines the exact same way, but doesn't rely on the functional form.

coverage: 94.072% (+0.02%) from 94.049%
when pulling 630443d7890150eb676b21fd3aedfa2eb9a577fa on PaarthShah:class-namedtuple
into dd5aa76c458c3517c62409db4a2a211fbb6ed3df on pbelskiy:master.

Hi! Yes, thanks for PR!


docs: updates task testing instructions to use tabs for with|without external load balancer

What type of PR is this?
Updates tasks in docs to use tabs for testing with & without load balancer support:

tasks/traffic/http3.md
tasks/security/tls-passthrough.md
tasks/security/secure-gateways.md
tasks/security/backend-tls.md
tasks/security/mutual-tls.md
tasks/security/tls-termination.md

Also reverses the order: with lb support first, without second.
Fixes #3259

/retest

/retest


Project Structure

"There is one branch for each development part (i.e. backend, Android, master for releases and general stuff) within this project. If you have any suggestions regarding this approach, please let me know in the comments, or open an issue."
I'd heavily suggest against using one Repo for all project parts. Seperating into multiple branches is a really bad idea. Keeping everything on one branch forces contributors working on different applications to pull/rebase constantly. Issues/PRs are not seperated. Wiki and documentation are not seperated. The entire repo has to be forked if necessary, ....
Try creating multiple Repos and grouping them using an organization.
e.g.: https://github.com/FAForever

This is just true, will work on it.
Organization is already created, but... Multi repo approach was unwieldy last time implemented, but was probably just because of me...
Thanks!

Now created some new repositories, documentation and deletion of old branches etc. is in work