TLS origination by Egress Gateway integration tests

Ref: https://github.com/istio/istio/issues/14039
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[x] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

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

Test name
Commit
Details
Rerun command

lint_istio
4b9b0d3a2c918b6e3d6a5cc4ad009218f85efa83
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.

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

Test name
Commit
Details
Rerun command

lint_istio
4fa6fac4fb6b8ca9e853a57520f296365ad4392c
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.

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

Test name
Commit
Details
Rerun command

lint_istio
4fa6fac4fb6b8ca9e853a57520f296365ad4392c
link
/test lint_istio

gencheck_istio
4fa6fac4fb6b8ca9e853a57520f296365ad4392c
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.

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

Test name
Commit
Details
Rerun command

lint_istio
4fa6fac4fb6b8ca9e853a57520f296365ad4392c
link
/test lint_istio

gencheck_istio
4fa6fac4fb6b8ca9e853a57520f296365ad4392c
link
/test gencheck_istio

integ-security-k8s-tests_istio
4fa6fac4fb6b8ca9e853a57520f296365ad4392c
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.

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

Test name
Commit
Details
Rerun command

lint_istio
4fa6fac4fb6b8ca9e853a57520f296365ad4392c
link
/test lint_istio

gencheck_istio
4fa6fac4fb6b8ca9e853a57520f296365ad4392c
link
/test gencheck_istio

integ-security-k8s-tests_istio
4fa6fac4fb6b8ca9e853a57520f296365ad4392c
link
/test integ-security-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
4fa6fac4fb6b8ca9e853a57520f296365ad4392c
link
/test lint_istio

gencheck_istio
4fa6fac4fb6b8ca9e853a57520f296365ad4392c
link
/test gencheck_istio

integ-security-k8s-tests_istio
4fa6fac4fb6b8ca9e853a57520f296365ad4392c
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
4fa6fac4fb6b8ca9e853a57520f296365ad4392c
link
/test integ-multicluster-k8s-tests_istio

release-test_istio
bb20325b863c85ad84e340266e1dfedde8f745d9
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
4fa6fac4fb6b8ca9e853a57520f296365ad4392c
link
/test integ-security-k8s-tests_istio

release-test_istio
bb20325b863c85ad84e340266e1dfedde8f745d9
link
/test release-test_istio

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

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

Test name
Commit
Details
Rerun command

release-test_istio
bb20325b863c85ad84e340266e1dfedde8f745d9
link
/test release-test_istio

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

integ-security-k8s-tests_istio
bb20325b863c85ad84e340266e1dfedde8f745d9
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.

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

Test name
Commit
Details
Rerun command

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

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

release-test_istio
3d720c1c59be13e11493805c5f246ebba900f5f2
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.

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

Test name
Commit
Details
Rerun command

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

release-test_istio
3d720c1c59be13e11493805c5f246ebba900f5f2
link
/test release-test_istio

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

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

Test name
Commit
Details
Rerun command

release-test_istio
3d720c1c59be13e11493805c5f246ebba900f5f2
link
/test release-test_istio

integ-multicluster-k8s-tests_istio
3d720c1c59be13e11493805c5f246ebba900f5f2
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
3d720c1c59be13e11493805c5f246ebba900f5f2
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.

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

Test name
Commit
Details
Rerun command

release-test_istio
3d720c1c59be13e11493805c5f246ebba900f5f2
link
/test release-test_istio

integ-multicluster-k8s-tests_istio
3d720c1c59be13e11493805c5f246ebba900f5f2
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
3d720c1c59be13e11493805c5f246ebba900f5f2
link
/test integ-security-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
7f61b6cb31d9c69e2733f9987bd8129549f485cb
link
/test lint_istio

integ-security-k8s-tests_istio
7f61b6cb31d9c69e2733f9987bd8129549f485cb
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
c7dce0f08d28c0ff19d9c4f41bb2c94e73e8f0f7
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.

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

Test name
Commit
Details
Rerun command

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

lint_istio
42d1ae7d7e4a5872d23bb9d812aae0987df8523b
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.

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

Test name
Commit
Details
Rerun command

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

lint_istio
42d1ae7d7e4a5872d23bb9d812aae0987df8523b
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
42d1ae7d7e4a5872d23bb9d812aae0987df8523b
link
/test lint_istio

integ-multicluster-k8s-tests_istio
42d1ae7d7e4a5872d23bb9d812aae0987df8523b
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
42d1ae7d7e4a5872d23bb9d812aae0987df8523b
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.

cc:@JimmyCYJ

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
42d1ae7d7e4a5872d23bb9d812aae0987df8523b
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
42d1ae7d7e4a5872d23bb9d812aae0987df8523b
link
/test integ-security-k8s-tests_istio

lint_istio
93945f31641522bb70eea343f1abaf83db448f18
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.

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
42d1ae7d7e4a5872d23bb9d812aae0987df8523b
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
42d1ae7d7e4a5872d23bb9d812aae0987df8523b
link
/test integ-security-k8s-tests_istio

lint_istio
93945f31641522bb70eea343f1abaf83db448f18
link
/test lint_istio

gencheck_istio
93945f31641522bb70eea343f1abaf83db448f18
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.

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
42d1ae7d7e4a5872d23bb9d812aae0987df8523b
link
/test integ-multicluster-k8s-tests_istio

lint_istio
93945f31641522bb70eea343f1abaf83db448f18
link
/test lint_istio

gencheck_istio
93945f31641522bb70eea343f1abaf83db448f18
link
/test gencheck_istio

integ-security-k8s-tests_istio
93945f31641522bb70eea343f1abaf83db448f18
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
93945f31641522bb70eea343f1abaf83db448f18
link
/test integ-security-k8s-tests_istio

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

/retest

Remove .DS_Store files from PR.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
49795d15e3cf33b506d2229d2b0f815c6d17735b
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
a252019c893bd4cd9d3733cff460aa53b7e74e27
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
ba5b70be8e067efba1ee0c4f8a1744150b08b378
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
14b8714aac69ba08a49e9c7dc0c7370db8f71a44
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
14b8714aac69ba08a49e9c7dc0c7370db8f71a44
link
/test integ-security-k8s-tests_istio

lint_istio
46c1724a9333a6062aee8332dad41fba511fe31e
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
14b8714aac69ba08a49e9c7dc0c7370db8f71a44
link
/test integ-security-k8s-tests_istio

lint_istio
46c1724a9333a6062aee8332dad41fba511fe31e
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
46c1724a9333a6062aee8332dad41fba511fe31e
link
/test lint_istio

integ-multicluster-k8s-tests_istio
46c1724a9333a6062aee8332dad41fba511fe31e
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
46c1724a9333a6062aee8332dad41fba511fe31e
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.

I think for the egress SDS integration test, maybe we can try this way:
client--request-->egress gateway---mTLS/TLS--->ingress gateway-->server. We can configure egress gateway and ingress gateway to set up a TLS connection or mTLS connection.

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
46c1724a9333a6062aee8332dad41fba511fe31e
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
46c1724a9333a6062aee8332dad41fba511fe31e
link
/test integ-security-k8s-tests_istio

lint_istio
1c369b996502b9682d7b896012653dab2e4941aa
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.

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

Test name
Commit
Details
Rerun command

lint_istio
1c369b996502b9682d7b896012653dab2e4941aa
link
/test lint_istio

integ-security-k8s-tests_istio
1c369b996502b9682d7b896012653dab2e4941aa
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
1c369b996502b9682d7b896012653dab2e4941aa
link
/test integ-security-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
c91623e3eab152fea1421b0151674e1070658bac
link
/test lint_istio

integ-security-k8s-tests_istio
c91623e3eab152fea1421b0151674e1070658bac
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
b61ed6999796f663a7d7a4f79b44bccb52a4a139
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.

/retest

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
b61ed6999796f663a7d7a4f79b44bccb52a4a139
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.

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

Test name
Commit
Details
Rerun command

lint_istio
741c40b4f04021aa8fa2df703949419970f7c395
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.

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

Test name
Commit
Details
Rerun command

lint_istio
741c40b4f04021aa8fa2df703949419970f7c395
link
/test lint_istio

gencheck_istio
741c40b4f04021aa8fa2df703949419970f7c395
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.

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

Test name
Commit
Details
Rerun command

lint_istio
741c40b4f04021aa8fa2df703949419970f7c395
link
/test lint_istio

gencheck_istio
741c40b4f04021aa8fa2df703949419970f7c395
link
/test gencheck_istio

integ-security-k8s-tests_istio
741c40b4f04021aa8fa2df703949419970f7c395
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.

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

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

Test name
Commit
Details
Rerun command

lint_istio
741c40b4f04021aa8fa2df703949419970f7c395
link
/test lint_istio

gencheck_istio
741c40b4f04021aa8fa2df703949419970f7c395
link
/test gencheck_istio

integ-security-k8s-tests_istio
741c40b4f04021aa8fa2df703949419970f7c395
link
/test integ-security-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
741c40b4f04021aa8fa2df703949419970f7c395
link
/test lint_istio

gencheck_istio
741c40b4f04021aa8fa2df703949419970f7c395
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
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.

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

Test name
Commit
Details
Rerun command

lint_istio
741c40b4f04021aa8fa2df703949419970f7c395
link
/test lint_istio

gencheck_istio
741c40b4f04021aa8fa2df703949419970f7c395
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-security-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
741c40b4f04021aa8fa2df703949419970f7c395
link
/test lint_istio

gencheck_istio
741c40b4f04021aa8fa2df703949419970f7c395
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-security-k8s-tests_istio

unit-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test unit-tests_istio

release-test_istio
7a98a96a3d85ce572206a170d344154a5586dd08
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.

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

Test name
Commit
Details
Rerun command

lint_istio
741c40b4f04021aa8fa2df703949419970f7c395
link
/test lint_istio

gencheck_istio
741c40b4f04021aa8fa2df703949419970f7c395
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-security-k8s-tests_istio

unit-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test unit-tests_istio

release-test_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test release-test_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
741c40b4f04021aa8fa2df703949419970f7c395
link
/test lint_istio

gencheck_istio
741c40b4f04021aa8fa2df703949419970f7c395
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-security-k8s-tests_istio

unit-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test unit-tests_istio

release-test_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test release-test_istio

integ-pilot-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
741c40b4f04021aa8fa2df703949419970f7c395
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-security-k8s-tests_istio

unit-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test unit-tests_istio

release-test_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test release-test_istio

integ-pilot-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-telemetry-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
741c40b4f04021aa8fa2df703949419970f7c395
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-security-k8s-tests_istio

unit-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test unit-tests_istio

release-test_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test release-test_istio

integ-pilot-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-telemetry-k8s-tests_istio

lint_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test lint_istio

integ-galley-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-galley-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.

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

Test name
Commit
Details
Rerun command

gencheck_istio
741c40b4f04021aa8fa2df703949419970f7c395
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-security-k8s-tests_istio

unit-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test unit-tests_istio

release-test_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test release-test_istio

integ-pilot-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-telemetry-k8s-tests_istio

lint_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test lint_istio

integ-galley-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-galley-k8s-tests_istio

integ-mixer-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-mixer-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.

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

Test name
Commit
Details
Rerun command

gencheck_istio
741c40b4f04021aa8fa2df703949419970f7c395
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-security-k8s-tests_istio

unit-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test unit-tests_istio

release-test_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test release-test_istio

integ-pilot-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-telemetry-k8s-tests_istio

lint_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test lint_istio

integ-galley-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-galley-k8s-tests_istio

integ-mixer-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-mixer-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
741c40b4f04021aa8fa2df703949419970f7c395
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-security-k8s-tests_istio

unit-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test unit-tests_istio

release-test_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test release-test_istio

integ-pilot-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-telemetry-k8s-tests_istio

lint_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test lint_istio

integ-galley-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-galley-k8s-tests_istio

integ-mixer-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-mixer-k8s-tests_istio

integ-operator-controller-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-operator-controller-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
741c40b4f04021aa8fa2df703949419970f7c395
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-security-k8s-tests_istio

unit-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test unit-tests_istio

release-test_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test release-test_istio

integ-pilot-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-telemetry-k8s-tests_istio

lint_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test lint_istio

integ-galley-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-galley-k8s-tests_istio

integ-mixer-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-mixer-k8s-tests_istio

integ-operator-controller-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-security-k8s-tests_istio

unit-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test unit-tests_istio

release-test_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test release-test_istio

integ-pilot-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-telemetry-k8s-tests_istio

lint_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test lint_istio

integ-galley-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-galley-k8s-tests_istio

integ-mixer-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-mixer-k8s-tests_istio

integ-operator-controller-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-distroless-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-security-k8s-tests_istio

unit-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test unit-tests_istio

release-test_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test release-test_istio

integ-pilot-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-galley-k8s-tests_istio

integ-mixer-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-mixer-k8s-tests_istio

integ-operator-controller-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test integ-distroless-k8s-tests_istio

gencheck_istio
7a98a96a3d85ce572206a170d344154a5586dd08
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
cf8dece99baa41755f7dd475d05aec8d632bbd8e
link
/test lint_istio

integ-security-k8s-tests_istio
cf8dece99baa41755f7dd475d05aec8d632bbd8e
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
888ec56e25a4b7c39d97ab617155347f97a22336
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
888ec56e25a4b7c39d97ab617155347f97a22336
link
/test integ-security-k8s-tests_istio

lint_istio
0e051211f1c9a32f881e1c66bbce18b33b804a2b
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
888ec56e25a4b7c39d97ab617155347f97a22336
link
/test integ-security-k8s-tests_istio

lint_istio
0e051211f1c9a32f881e1c66bbce18b33b804a2b
link
/test lint_istio

gencheck_istio
0e051211f1c9a32f881e1c66bbce18b33b804a2b
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
888ec56e25a4b7c39d97ab617155347f97a22336
link
/test integ-security-k8s-tests_istio

gencheck_istio
0e051211f1c9a32f881e1c66bbce18b33b804a2b
link
/test gencheck_istio

lint_istio
0e051211f1c9a32f881e1c66bbce18b33b804a2b
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
888ec56e25a4b7c39d97ab617155347f97a22336
link
/test integ-security-k8s-tests_istio

lint_istio
0e051211f1c9a32f881e1c66bbce18b33b804a2b
link
/test lint_istio

gencheck_istio
0e051211f1c9a32f881e1c66bbce18b33b804a2b
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
e267c5ced6a6e3f6d03b163d02b48d2c238fe1fd
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
6dea298bf586828f04c911710fa04aedbb157b68
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.

/retest


Make assertion helpers easier to debug

No longer appear in stack traces etc

@hughbe,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

This brings up a bunch of warnings (for conversion of float to double). These are legit warnings that I'll fix


Next set of P4 subjects to unpause

We're close to completing the current set of data live on Planet Four. We'd like the subjects that have associated name entry with these HiRISE filenames below to be unpaused:
PSP_002758_0945
PSP_002759_0855
PSP_003179_0945
PSP_003180_0945
PSP_003181_0855
PSP_003363_0945
PSP_003364_0945
PSP_003614_0945
PSP_003680_0945
PSP_003970_0945
PSP_004062_0945
PSP_004181_0945
PSP_004748_0945
PSP_004880_0945
We do want to finish completely the current data live, so I'll reply to this to ask for this to happen when we need it actually go live if that works for you @astopy .  I wanted to make sure to give a heads up first.  Likely in a few weeks or less depending on the response to the newsletter. Thanks

Sure, that’ll be fine. Just let me know.

On 29 Feb 2016, at 19:48, Meg Schwamb<EMAIL_ADDRESS>wrote:
We're close to completing the current set of data live on Planet Four. We'd like the subjects that have associated name entry with these HiRISE filenames:
PSP_002758_0945
PSP_002759_0855
PSP_003179_0945
PSP_003180_0945
PSP_003181_0855
PSP_003363_0945
PSP_003364_0945
PSP_003614_0945
PSP_003680_0945
PSP_003970_0945
PSP_004062_0945
PSP_004181_0945
PSP_004748_0945
PSP_004880_0945
We do want to finish completely the current data live, so I'll reply to this to ask for this when we need it go live if that works for you @astopy https://github.com/astopy . Likely in a few weeks or less depending on the response to the newsletter. Thanks
—
Reply to this email directly or view it on GitHub https://github.com/zooniverse/MarsZoo/issues/156.

Hi @astopy looks likes the newsletter is doing the trick. We're at 99% complete. Before you leave for the day would you be able to switch this on if possible? . If not when we can tomorrow?  Thanks.

I won’t get a chance to do it today, but I’ll make a note to do it first thing tomorrow.

On 7 Mar 2016, at 16:13, Meg Schwamb<EMAIL_ADDRESS>wrote:
Hi @astopy https://github.com/astopy looks likes the newsletter is doing the trick. We're at 99% complete. Before you leave for the day would you be able to switch this on if possible? . If not when we can tomorrow? Thanks.
—
Reply to this email directly or view it on GitHub https://github.com/zooniverse/MarsZoo/issues/156#issuecomment-193321440.

Great. Thanks very much @astopy

@mschwamb Those subjects are all active now -- that's 4607 new subjects.

Thanks @astopy!


Reduce whitespace imageviewer-screen

Hi there,
a few days ago I noticed that the new Main-Screen on Sunlit 3.0 had a white bar at the bottom on iPhones with a Homebutton. So I asked for help and as far as I can tell, you folks already fixed the issue before I found out about Sunlit being open source today. (Sidenote: It's so awesome, that Sunlit is open source. Thank you so much!)
Nevertheless, I wanted to have a look at the app and found out, that the bar at the bottom appeared appears on other screens as well. This PR offers a fix for the ImageViewer. It looks good now on iPhones with a home button and with a home indicator.

Excellent, thanks @zeitschlag! I just submitted Sunlit 3.0.2 to Apple for approval earlier today, so we'll roll this fix into the next update.

This is great! I'll review and merge once 3.0.2 is out.


Mupen64plus-video-glide64mk2 feature request

Hi I've been scouting youtube and seen a performance increase with this plugin just wondering if it's possible to add to arkos
https://github.com/mupen64plus/mupen64plus-video-glide64mk2

This is already included as standalone-glide64mk2 in ArkOS.


chore(main): release 0.39.0

:robot: I have created a release beep boop
0.39.0 (2024-05-15)
Features

add list_push_front and list_push_back (#294) (ace68b8)
add response suffix to control commands (#313) (1c197d4)
add response suffix to dictionary response types (#300) (1f4c80b)
add response suffix to list types (#305) (da538af)
add response suffix to scalar types (#307) (51bd289)
add response suffix to set type (#311) (374b499)
add response suffix to sorted set types (#312) (70d45ac)
basic subscriptions should return only SubscriptionValues (#316) (789cf02)
implement custom debug and display traits for byte-array types (#323) (4eaf53d), closes #282

Bug Fixes

clippy error on gh with doctest signature (#325) (4b75542), closes #326
impl Display for CredentialProvider (#295) (ade83f2)

Miscellaneous

Add / tweak doc examples for use in dev docs (#317) (6e4de64)
add docs to improve discoverability for client instantiation (#320) (e883d20)
add integration tests and doctests for TopicClient (#292) (a93b319)
add links to response docstrings showing how to handle hits/misses (#318) (9af89af)
add lint rule to check usage of expect (#293) (be547e4)
add missing links in docs, small docs fixes (#301) (14e909e)
add more docstrings for errors and utils, remove unused file (#310) (7e46916)
add top-level docs for the crate, including 'into' conventions etc. (#304) (e6d9ebe)
enable missing_docs lint rule and fill in missing docs (#321) (ce4a1ed)
improve error messages in tests (#322) (db927a2)
move docs examples into subdir (#319) (1300e83)
remove obsolete protoc scripts and ci references (#328) (dc0a3f0)
Templatize example README, expand to include topics example (#309) (54a181b)
upgrade codeql action upload sarif version (#330) (e09d933)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/momentohq/client-sdk-rust/releases/tag/v0.39.0 :sunflower:


support mailgun reply_to

Thanks for contributing to fastlane! Before you submit your pull request, please make sure to check the following boxes:

[ ] Run bundle exec rspec from the subdirectory of each tool you modified. Alternatively, run rake test_all from the root directory.
[ ] Run bundle exec rubocop -a to ensure the code style is valid
[ ] Read the Contribution Guidelines
[x] We currently don't accept new actions, please publish a plugin instead, more information in Plugins.md

Before submitting a pull request, we appreciate if you create an issue first to discuss the change :+1:

Hey @iCell, have you had the time to look into the proposed changes and update the PR? 👍

@KrauseFx Sorry for not responding, I'm really busy with my recent work, I'll update the PR in a few days.

I have run the command bundle exec rspec, but it raised an exception Fastlane Fastlane::FastFile Mailgun Action raises an error if no mailgun apikey is given, is this exception normal？

I have run bundle exec rspec from the subdirectory of each tool I've modified, and the result is 0 failure. But through the results of Github CI, these errors are not caused by my code in the PR.


button-icon issue on click | Ionic v1

http://codepen.io/anon/pen/BKLqZy
Hi, I've an issue with a button-icon click. On my android phone when I click on it, it stays black. With a normal button-color I don't have this issue.
Am I missing something?
Thanks

Hello! Are you still having this issue? Thanks!

Hello! As it has been a little while since there was any activity on this issue I will be closing it. Thanks for using ionic!


Suggestion: Alternative wrapper

Instead of having to decide between using ahash::HashMap and ahash::AhashMap, I was wondering if they could be merged using a builder. The idea is to export a struct with only the new() method(s) that returns a std::collections::HashMap. I'm not sure which considerations has been put into the current wrappers and aliases, so I might be missing something. The idea looks as follows:
pub use hash::{HashMapBuilder, HashSetBuilder};
pub use std::collections::hash_map::*;
pub use std::collections::hash_set::*;

mod hash {
    use ahash::{HashMap, HashMapExt};

    pub type HashSetBuilder<K> = HashMap<K, ()>;
    pub struct HashMapBuilder;

    impl HashMapBuilder {
        pub fn new<K, V>() -> HashMap<K, V> {
            HashMap::new()
        }

        pub fn with_capacity<K, V>(capacity: usize) -> HashMap<K, V> {
            HashMap::with_capacity(capacity)
        }
    }
}

#[cfg(test)]
mod tests {
    use super::{HashMap, HashMapBuilder};

    #[test]
    fn test_hash_map() {
        let map = HashMapBuilder::new();
        let mut map = identity(map);
        map.insert(1, 2);
        assert_eq!(map.get(&1), Some(&2));
    }

    fn identity<K, V, S>(x: HashMap<K, V, S>) -> HashMap<K, V, S> {
        x
    }
}

The only downside, I've been able to find, is that the following function does not work. This is because the two Random state variants are not identical. Maybe someone smarter than me can find a way to solve that.
fn identity<K, V>(
    x: HashMap<K, V>,
) -> HashMap<K, V> {
    x
}

Is it something that makes sense to include?

Closing again as this did not make usage any simple than use ahash::{HashMap, HashMapExt}


Remove skip encoding in GraphRbac when possible

CLI issues:
https://github.com/Azure/azure-cli/issues/4775
We used x-ms-skip-url-encoding a little too much:

For App, Group and SP, it's pointless since it's an UUID (i.e. no characters of an uuid change when encoded)
For users, it can be UUID (so encoding is pointless) or a UserPrincipalName. In this case, encoding is important, since UPN can contains characters like # that MUST be encoded.

This is technically breaking if a customer found the bug, and workarounded it by encoding its UPN before using the SDK (in this case, after this PR this will be double-encoded). For everybody else, it's not breaking (most likely scenario). CLI is not broken by this PR, since CLI was not pre-encoding the UPN (hence the issue).
Fix strategy discussed with @amarzavery already.
Tested in Python already:
https://github.com/Azure/azure-sdk-for-python/pull/1594

No modification for AutorestCI/azure-sdk-for-python

No modification for AutorestCI/azure-sdk-for-node

 https://github.com/Azure/azure-sdk-for-ruby/pull/1105


Include windows illegal file name character '?'

As mentioned in #286 the small addition of the question mark when replacing file names

Closing this one as the file has been moved, but co-authored you in a commit fixing this: https://github.com/chhoumann/quickadd/commit/e99e549c5d3984031fd785bcb9dff508dd8f75f7
Thank you!


Add loop limit for second args

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Ville Manninen seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Add API endpoint to clear strava subscription

Of course, this would require specific admin-like rights.

Won't handle this for now.


Update tested Ruby versions

Remove Ruby versions for which Ruby lang support has ended, and
add 2.3 and 2.4.

Codecov Report

Merging #116 into master will increase coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #116      +/-   ##
==========================================
+ Coverage   99.48%   99.53%   +0.05%
==========================================
  Files          19       19
  Lines        1932     1933       +1
==========================================
+ Hits         1922     1924       +2
+ Misses         10        9       -1

Impacted Files
Coverage Δ

lib/google/gax/util.rb
97.77% <0%> (+0.05%)
:arrow_up:

spec/google/gax/bundling_spec.rb
100% <0%> (+0.3%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3dd98b5...47c194f. Read the comment docs.


Year bump in copyright declaration

git grep -P '\d{4}\sAdobe' | \
    awk -F: '{print $1}' | \
    xargs -I {} sh -c 'year=`date +"%Y"`; sed -i -ne "s/[[:digit:]]\{4\}\( Adobe\)/${year}\1/;p" {}'

[x] Please sign Adobe's CLA if this is your first time contributing to an Adobe open source repo. Thanks!

hey @ariel-anieli , thanks for the PR. our CLA CI check has a bug for first time contributors. try opening a new PR with the same code and see if it turns green? be happy to merge this

:slightly_smiling_face:, sure, @novaugust: here is it, all green: https://github.com/adobe/elixir-styler/pull/144


[BUG/ISSUE] Invalid time stamp in GC-Classic restart file

Report a technical issue for GEOS-Chem on the AWS cloud
HEMCO ERROR: Cannot find field with valid time stamp
Hello, this picture shows the problem I encountered.

This picture shows the list of files in my current folder.

This picture shows the modified content of the input。geo file.

To Reproduce
I tried to search this question in Google browser and got some reference answers（http://wiki.seas.harvard.edu/geos-chem/index.php/GEOS-Chem_restart_files#Restart_files_in_GEOS-Chem_12）. Unfortunately, I still haven't solved this problem.
Hope to get help, thank you.

It looks like your simulation starts on May 1 but your restart file is for April 1. The restart file date must match your simulation start date. Did you try to fix this problem using the instructions at the wiki page you linked to and it did not work?

It looks like your simulation starts on May 1 but your restart file is for April 1. The restart file date must match your simulation start date. Did you try to fix this problem using the instructions at the wiki page you linked to and it did not work?

Thank you for your reply. I have made two more attempts to solve the problem according to your message.

I adjusted the simulation time, and I downloaded the data again. But this problem has not been solved.

For wiki link (http://wiki.seas.harvard.edu/geos-chem/index.php/GEOS-Chem_restart_files#Restart_files_in_GEOS-Chem_12), i have captured these information in web as  pictures.

Then， I tried to change Restart.fields:  '''SpeciesRst_?ALL?   to Restart.fields:  '''SPC_?ALL? .  And i have a error again.

Hope to get a solution to the problem.

It's crazy that this problem happens again and again.  I can't understand why I should check hemco_ Config. rc
error

hemco_ Config. rc

hemco_ Config. rc

Hi @StrangeFrog, what version are you using? It would also be helpful if you upload your config and log files by adding extension '.txt' and dragging and dropping into the comment box. Finally, how did you generate your restart file?

@StrangeFrog, I'd recommend starting fresh with a more recent version (like 13.3.1), so that you get a good restart file.

Thank you for your reply.  I reconfigured geochem according to the method from yantosca. But I encountered this problem again. I guess there is a problem with my steps.

Show me the configured process.

First, I launched a geoschem service in AWS.
Then, I configured the compilation environment according to the following code
$ mkdir ~/GC  # make you own folder instead using the "tutorial" folder.
$ cd ~/GC
$ git clone https://github.com/geoschem/GCClassic.git Code.GC
$ cd Code.GC
$ git submodule update --init --recursive
$ cd ~/GC/Code.GC/run
$ ./createRunDir.sh
$ cd ~/GC/rundirs/YOUR_RUN_DIRECTORY
$ cd build/
$ cmake ../CodeDir -DRUNDIR=..
$ make -j
$ make install
$ cd ..
$ ls
I modify the simulation time in the input.geo file.
Then execute the following code.
$ ./gcclassic --dryrun | tee log.dryrun
$ ./download_data.py log.dryrun --aws
After executing the above code, there will be some missing files, and then I execute the following code.
$ ./gcclassic --dryrun > log.dryrun.2
$   grep "NOT FOUND"  	log.dryrun.2
$  ./download_data.py log.dryrun.2 washu
Finally, I'll get the restart file and run the simulation and get the following errors.
$ ./gcclassic | tee run.log

Screenshot of current folder list and some files

HEMco_Configure.rc
HEMCO_Config.txt
run.log
run.txt
HISTORY.rc
HISTORY.txt
inpur.geos
input.txt
We look forward to your reply and thank you again.

Thank you very much. I have solved this problem.

Glad you were able to solve it. Could you follow-up with a post here on what ended up working to fix the issue? This may help other users in the future who experience the same problem.

The first step to solve this problem is to determine that there is a match between the restart file and the simulation start time.

Check the internal time of restart file,
$ ncdump -h GEOSChem.SpeciesConc.20190701_0000z.nc4

netcdf GEOSChem.SpeciesConc.20190701_0000z {
dimensions:
time = UNLIMITED ; // (1 currently)
lev = 72 ;
ilev = 73 ;
lat = 46 ;
lon = 72 ;
variables:
double time(time) ;
time:long_name = "Time" ;
time:units = "minutes since 2019-07-01 00:00:00 UTC" ;
time:calendar = "gregorian" ;
time:axis = "T" ;
...

Make sure “ time:units = minutes since 2019-07-01 00:00:00 UTC” and the file name and time are consistent.
If the time is inconsistent, please modify it（https://github.com/geoschem/geos-chem/issues/712）.


Selectable TLS Versions

This PR resolves issue #535 by allowing a minimum TLS version to be specified for an entrypoint.

Thanks @dtomcej !
But I thought that #535 was about selecting cipher suites, am I wrong?

You are not wrong, BUT:

I reviewed the cipher suite provided by "crypto/tls", and they are all strong ciphers.
Disabling TLS 1.0 and 1.1 suffices our needs for the time being
Extending the toml parsing to allow for the dynamic list is more ambitious than I am willing to do for a first commit ;)

@emilevauge I have updated the PR to include:

TLS MinVersion selection (properly included in the TLS Struct)
TLS CipherSuite selection (coded as a slice in the TLS Struct)

Both pieces of Issue 535 are resolved by this PR.

Hi, traefik v1.1 developments will be frozen this week, on Thursday 29th. If you want your PR to be part of this release, please update your PR as soon as possible :)

I have made the requested changes, as well as updated the docs to include a sample of the MinVersion and CipherSuites vars.


GrafikAI

GrafikAI

This PR is a fully integrated into https://github.com/Zujus/Artificial-Intelligence-Group/pull/17

I've included this PR into the https://github.com/Zujus/Artificial-Intelligence-Group/pull/17


Shift-Tab on Console

Prerequisites

[X] I've checked the existing issues and I'm not duplicating a report.
[X] I've checked the zimfw Changelog and I'm not being affected by documented changes.
[X] I've checked the zimfw 📢 Announcements and I'm not being affected by announced changes.

Bug description
Shift-Tab works in terminal emulators but not on linux console
Steps to reproduce

cd ${$(mktemp -d):A} && \
    ZDOTDIR=${PWD} HOME=${PWD} ZIM_HOME=${PWD}/.zim && \
    curl -fsSL https://raw.githubusercontent.com/zimfw/install/master/install.zsh | zsh && \
    exec zsh

Add more steps here ...

Current behavior
Shift-Tab works in terminal emulators but not on linux console
Expected behavior
Shift-Tab works in terminal emulators but not on linux console
zimfw info
No response
Additional context
No response

What do you get when you type cat<ENTER><SHIFT-TAB> in your shell prompt? (You can exit cat with <CONTROL-C>.) I get:
% cat
^[[Z

Then what do you get as output of print -n ${key_info[BackTab]} | xxd? I get:
% print -n ${key_info[BackTab]} | xxd
00000000: 1b5b 5a                                  .[Z

Both should match, as they do above.

Terminal :
cat
^[[Z

print -n ${key_info[kcbt]} | xxd
00000000: 1b5b 5a                                  .[Z

Console:
cat
^[

print -n ${key_info[kcbt]} | xxd
00000000: 1b09                                  ''

@oukemi hard to see the output of cat in the console. Please try cat | xxd<ENTER><SHIFT-TAB><ENTER><CTRL-D>
I get in my terminal:
% cat | xxd
^[[Z
00000000: 1b5b 5a0a                                .[Z.

(0a in the end is the line feed, which we ignore)

Also, please note that this module will not be initialized if [[ ${TERM} == dumb ]]

@oukemi end the cat input with <ENTER><CTRL-D> (that's D instead of C) instead of <CTRL-C>.


CI improvements: add out-of-box, remove timing self-test, more 32-bit

Add an out-of-box component to all.sh: just run make, make test and programs/test/selftest, without any fancy configuration.
Run ssl-opt.sh on a 32-bit build with ASan.
Remove the self-test from the timing module. It randomly fails on overloaded CI executors and isn't useful.

Internal ref: IOTSSL-2792
Needs backports: 2.7, 2.16, crypto (partial).

CI hit the GitHub API rate limit. Will need CI testing later.

I added a changelog entry for the removal of the timing self-test. I also removed the function from the header file, which I'd forgotten to do earlier.
This is an API change. Is it acceptable to remove it in the backports? We normally don't do this.
I'm actually leaning to keeping the timing self-test function even in development, and just remove it from the test suite and from the selftest program.

Tagging as "needs work" until we take a decision about mbedtls_timing_self_test. On second thoughts I don't think we can remove it. It's part of our API, even if it isn't a useful part.

After internal discussion, I've rescoped this PR to just add the things that were missing in all.sh. The problem with the timing self-tests is out of scope.


WIP: apply patched version of "enable parallelized writes with ParquetSink"

⚠ This will not be merged. ⚠
This PR is based on https://github.com/apache/datafusion/commit/671cef85c550969ab2c86d644968a048cb181c0c which was merged to DataFusion on April 13, 2024.
All the patches in the previous temporary dependency branch (WIP(iox-10577): patched df upgrade 202-04-14) are caught up at the end of April 13 commit (https://github.com/apache/datafusion/commit/671cef85c550969ab2c86d644968a048cb181c0c), so creating a new branch for @wiedld's "enable parallelized writes with ParquetSink" patch

This is what I did on this branch:

On influxdata/arrow-datafusion repo, start with the main branch

git checkout main

Check out a new branch which based on the April 13 commit https://github.com/apache/datafusion/commit/671cef85c550969ab2c86d644968a048cb181c0c to catch up with all the fixes

git co -b chunchun/denise-df-11 671cef85c550969ab2c86d644968a048cb181c0c

Cherry pick the commits from https://github.com/influxdata/arrow-datafusion/pull/11

git cherry-pick 391e07466b5c5a381e578e50a1abc89f509e0a69 60fbdac7afd25e1670a25dc46afc7b80b8f16a97 c964df58820ffe29abc0eb6f8e8ef1fae776db91 8beb16ad037cdd7f33da5b4f8277bb3bc2baa305

Commenting here for myself (😆 ):
Current main is up to this April 26th commit: https://github.com/influxdata/arrow-datafusion/commit/c9bd2910c353ffe4efcf888737b6ee4011f172a6

Closing as the update is done without issue


WIP: max, min, timedelta

Thanks, Todd. There is a lot to do here but this is a good start. There are test errors related to aggregate but they are minor; I'll fix them after merge.


Add --cluster option on ceph require-osd-release command

On DCN environments, or when multiple ceph cluster are configured,
we need to specify the cluster name before running the command or
the rolling_update playbook will fail during minor updates.
Closes: https://bugzilla.redhat.com/1876447
Signed-off-by: Francesco Pantano<EMAIL_ADDRESS>(cherry picked from commit cb64df30b687d95704bac76ed0b4f83dfc3ca992)

jenkins test centos-non_container-update

jenkins test centos-container-update

unrelated failures


Expense workflow failures

Looks like we missed somethng with this workflow:
https://github.com/webdriverio-community/wdio-electron-service/actions/runs/8116095466
https://github.com/webdriverio-community/wdio-electron-service/actions/runs/8115379138

Seems like the expense.yml was committed as folder:

Ahahaha. :facepalm:


Accept non-canonical encodings of X25519 public keys

Currently agreement::PublicKey only implements TryFrom<[u8;32]> instead of From
This prevents using non-canonical curve elements. However, the standardised x25519 function has a signature of  x25519(k: [u8; 32], u: [u8; 32]) -> [u8; 32] which doesn't fail and silently canonicalize the public type.
For example x25519-dalek implements From.

It looks like https://github.com/ycrypto/salty/commit/01404bc260e1b5ef12206996cae515d794caea61 should have instead used from_unreduced_bytes?

I think this is a weird use case to use [0xFF; 32] as public key, but RFC 7748 agrees.


Simplify nlprule build

This PR applies the changes discussed which were out of scope for #35 by:

making TransformPathFn and TransformDataFn a type instead of trait.
removing the need for Seeks by wrapping data in cursors as late as possible.
adjusting docs accordingly

@drahnr would be great if you could review this.

Will do, either tonight or tomorrow


Fix image ref in mesheryctl docs

Signed-off-by: Aadhitya A<EMAIL_ADDRESS>Description
This PR fixes #
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Codecov Report

Merging #5908 (fbc7b7f) into master (07b6118) will decrease coverage by 4.34%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #5908      +/-   ##
==========================================
- Coverage   17.80%   13.45%   -4.35%
==========================================
  Files         107      107
  Lines        9994     9994
==========================================
- Hits         1779     1345     -434
- Misses       7779     8359     +580
+ Partials      436      290     -146

Flag
Coverage Δ

gointegrationtests
?

unittests
13.45% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

mesheryctl/internal/cli/root/app/list.go
33.33% <ø> (ø)

mesheryctl/internal/cli/root/app/onboard.go
27.84% <ø> (ø)

mesheryctl/internal/cli/root/app/view.go
51.94% <ø> (ø)

mesheryctl/internal/cli/root/pattern/apply.go
24.02% <ø> (ø)

mesheryctl/internal/cli/root/pattern/list.go
46.96% <ø> (ø)

mesheryctl/internal/cli/root/pattern/view.go
36.06% <ø> (ø)

mesheryctl/internal/cli/root/perf/apply.go
43.52% <ø> (ø)

mesheryctl/internal/cli/root/perf/result.go
72.72% <ø> (ø)

mesheryctl/internal/cli/root/system/check.go
1.03% <ø> (-23.03%)
:arrow_down:

mesheryctl/internal/cli/root/system/context.go
47.39% <ø> (ø)

... and 12 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 20129e0...fbc7b7f. Read the comment docs.

🚀 Preview for commit 1ba48aa22ffd68167d416355ddf378e4a60bcfb1 at: https://62e38436b24aea504951ac23--meshery-docs-preview.netlify.app

@alphaX86 you found the bug I mentioned previously. Excellent.

@alphaX86 you found the bug I mentioned previously. Excellent.

Finally I found where it went wrong, now it's resolved 🙂

🚀 Preview for commit 25b8774a9c9b27859edea7648b00923c64823380 at: https://62ea8fbaa9d7e8006aeca0a9--meshery-docs-preview.netlify.app

@nishantwrp is this a fix for the bug that you filed?

🚀 Preview for commit f048cd2fe38f9e448743a3b2722b7e6227ce9119 at: https://62eda9d7f3c82a518dad3fe5--meshery-docs-preview.netlify.app

I broke the DCO by updating the branch :/

🚀 Preview for commit 97f6fed3fdedfd477d8c02f9e44abcdfb9754662 at: https://62ee29f14d1e7c263ec70174--meshery-docs-preview.netlify.app

I broke the DCO by updating the branch :/

Well you could've ticked the commit with sign-off option in GitHub itself... It's ok..

🚀 Preview for commit 90aa6ebb27861d79f20e46140d48f6aa0a8b7863 at: https://62ee857cac35f86118d93b59--meshery-docs-preview.netlify.app

🚀 Preview for commit 78896ce039d6aefabd8514c7105f6d19f0887002 at: https://62f0b309ce17ee2a3494a3b4--meshery-docs-preview.netlify.app

🚀 Preview for commit a1d005313eac85e000e17285d5de030291f49395 at: https://62f1fdad23d9f972ffec2103--meshery-docs-preview.netlify.app

Thanks, @alphaX86 👍


ExoPlayer .setEnableFloatOutput(true) crashes on AVD (api 28)

I noticed crashes if setEnableFloatOutput == true, in DefaultRendersFactory.
ExoPlayer could be instantiated in the simplest way :
ExoPlayer.Builder(this@Service, renderersFactory)             .build()
And rendersFactory:
object : DefaultRenderersFactory(app){

        override fun buildAudioSink(
            context: Context,
            enableFloatOutput: Boolean,
            enableAudioTrackPlaybackParams: Boolean,
            enableOffload: Boolean
        ): AudioSink {

            return DefaultAudioSink.Builder()
                .setEnableFloatOutput(true)
                .build()
        }
    }

It crashes on AVD with api level 28 and lower, and does not on api 34. But also it does not crash on a real device with api 28.
Logcat shows only these lines:
 [OMX.google.mp3.decoder] BAD CODEC: Output format changed unexpectedly from (diff) AMessage(what = 0x00000000) = {                                                                                int32_t pcm-encoding = 4                                                                                } to (diff) AMessage(what = 0x00000000) = {                                                                                int32_t pcm-encoding = 2                                                                                }
Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 7552
Could it be a problem with api level, or more like with AVD itself.

Hi @MrBzik,
Thank you for your report. From the log you pasted, it looks like pcm-encoding 4 (i.e. ENCODING_PCM_FLOAT) got changed to 2 (i.e. ENCODING_PCM_16BIT).
There is some SDK-version-logic indeed, so I wonder if you are ending up in the wrong if-branch
https://github.com/androidx/media/blob/5328d6464acb077a7e8cba61b8cac1973c4943d7/libraries/exoplayer/src/main/java/androidx/media3/exoplayer/audio/MediaCodecAudioRenderer.java#L862-L871
Do you have more information about the Format of the media you are playing?

Hi @oceanjules
I checked sampleMimeType of exoplayer. I play different radio streams, and it seems when mime type is audio/mp4a-latm, it does not crash. When type is audio/mpeg, it does crash.

@oceanjules Great research, thank you for looking into it. Based on this info guess the only work around would be to check api in renders factory builder.


Show packages that do not support Python 2?

I'd like to see a visualization of which latest releases only support Python 3 (and do not support Python 2). i.e., NumPy will not support Python 2 after Jan. 1, 2019 (source). I'd like to see a representation of that.

Thanks for request. I think it is out of scope for this project.
However, there is something similar https://hugovk.github.io/drop-python/
@hugovk


perlPackages.CPAN: 2.28 -> 2.29

Motivation for this change
Fixes CVE-2020-16156
https://metacpan.org/release/ANDK/CPAN-2.29/source/Changes
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

perl532Packages.CPAN
perl534Packages.CPAN

@GrahamcOfBorg eval

@GrahamcOfBorg build perlPackages.CPAN


Add control, invariant, maybe to the package-set

Should we also add these as dependencies to the test suite just to check that the package-set compiles?

Should we also add these as dependencies to the test suite just to check that the package-set compiles?

Ah yes, great idea

Actually I can't do that in this PR yet. Waiting for the new spago for that.

I'd like to merge this, I need it for other package updates. I can add the test deps later.


Update readme

Issue #, if available:
Description of changes:
Updates readme
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


fix: duplicate transaction entry in keysend payments

Fixes https://github.com/getAlby/hub/issues/360
This is due to the transaction entry in the DB initially not having a payment hash, and we will not know it until the LNClient keysend method returns (which internally may fire a pay_keysend notification in the LDK/LND case)

Closing in favor of https://github.com/getAlby/hub/pull/385 (WIP)


Error: You must log in first. - When using environment variable to set CIRCLECI_TOKEN

We have had no issues with this provider up until recently (maybe related to the CircleCI security leak...). We are always getting this error when using the environment variable CIRCLECI_TOKEN:
│ Error: You must log in first.
│
│   with module.platforms.module.circleci.data.circleci_context.this,
│   on platforms/circleci/main.tf line 21, in data "circleci_context" "this":
│   21: data "circleci_context" "this" {

When I set the value in the provider block directly we don't get this error...
Versions
Terraform v1.1.6
circleci = {
      source  = "mrolla/circleci"
      version = "0.6.1"
 }

hi @markandersontrocme just to confirm, would the value set in the block be the same value as stored in your CIRCLECI_TOKEN environment variable?
If they are not, likely the value stored under the CIRCLECI_TOKEN environment variable is no longer valid.
You can always confirm the validity of the CircleCI API token with:
$ curl -H "Circle-Token: ${CIRCLECI_TOKEN}" https://circleci.com/api/v2/me


Specific changes made to document page.

[Would like to understand what changes were made to this page from the previous publication? Which line items were changed and which IPs were added and removed.]

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

ID: e1a62365-4312-8aad-d2f1-bb5c4184adf1
Version Independent ID: 2ba5b809-8025-d7ee-c756-d6d1bab033fb
Content: Azure SQL Database Connectivity Architecture - Azure SQL Database and Azure Synapse Analytics
Content Source: articles/azure-sql/database/connectivity-architecture.md
Service: sql-database
Sub-service: development
GitHub Login: @rohitnayakmsft
Microsoft Alias: rohitna

@sjt0325
Thanks for your feedback! We will investigate and update as appropriate.

@sjt0325 Please refer to below screenshot for changes made.

Please let me know if this helps.

@sjt0325 We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


rr_graph: Adding more sanity checking.

Only allow valid edge types to be added to the routing graph. Also adds a lot of tests to prove things work.


fix(app): fix double rendering labware in basedeck component

Closes RQA-1899

Overview
Adds logic to prevent duplicate rendering of labware if it has already been rendered on top of a module. This bug is only noticeable on the thermocycler, since labware is rendered on the TC at an offset.
Current Behavior

With Fix

Test Plan

AppUI is set up to test! Here's a protocol.
LPC Test (2).json
Launch LPC and proceed to a step with labware. Confirm in devtools there's no double rendering of labware.
Perform LPC until step 4. Confirm the TC labware does not render directly on slot B1.

Changelog

Fix double rendering of labware while performing LPC.

Risk assessment
low

Because BaseDeck and related components are in active development, I didn't want to refactor this too much as things will likely change. I think utilizing the filter method directly on the array is fine for now.

nice i'm glad this ended up being an easy fix and not some weird TC labware positioning issue. There are other components that renders both modules and labware like DeckThumbnail and SetupLabwareMap - i wonder if they also are double rendering labware on a module or not. If not, maybe we should follow the pattern that they have? This way is fine though but would defer to what @brenthagen thinks!

Good call - @jerader ! I double checked these other spots, and they are fortunately working as expected. The exact code shape in these components is relatively different than PrepareSpace. I do agree that we should keep things consistent, but I'd rather not refactor all of PrepareSpace at the moment given how quickly we are changes this part of the codebase. Totally down to circle back on this once the 7.1 work slows down!


Formatting changes to ISSUE_TEMPLATE for improved readability

Primarily, this PR is to slightly improve readability of the ISSUE template that github presents to users pressing "new issue"
But as a hidden agenda, I wanted to verify that Travis correctly builds a PR with changes only in markdown files (since it could not correctly build my PR #1058)

Closed via https://github.com/angular/angular-cli/commit/c31e8cbad1050b93b3ffaba7d0c33686d358b818


add Wilson's Theorem for check if number is prime

it's not the proper way

Why this is not the proper way, for the last line?

mentioned full program with proper syntax

mentioned full program with proper syntax

Do you refer an explanation of theorem and an example?

yeah! sort of... It might help to understand.

yeah! sort of... It might help to understand.

Oh, sorry for the misunderstanding. Later I fix it.

No issue!


explore detail page | team tab | creator should not remove themselves

team tab

creator should not see remove button for themselves

archive due to #33


20 create time function

Fixed both issues #20 and #52

consolidated query selectors
created event listeners
created function to change selected time
created function to find index for data to display


Fix default version of pip3 to 21.1.3

Description
https://scalar-labs.atlassian.net/browse/DLT-9543
https://scalar-labs.atlassian.net/browse/DLT-9544
TestEndToEndTerraform 2021-07-25T15:12:30Z command.go:158: module.network.module.bastion.module.bastion_provision.null_resource.ansible (local-exec): fatal: [bastion-1-terratest-adlniey.westus.cloudapp.azure.com]: FAILED! => {"changed": false, "cmd": ["/bin/pip3", "install", "ansible"], "msg": "stdout: Collecting ansible\n  Downloading ansible-4.3.0.tar.gz (35.1 MB)\nCollecting ansible-core<2.12,>=2.11.3\n  Downloading ansible-core-2.11.3.tar.gz (6.8 MB)\n\n:stderr: WARNING: pip is being invoked by an old script wrapper. This will fail in a future version of pip.\nPlease see https://github.com/pypa/pip/issues/5599 for advice on fixing the underlying issue.\nTo avoid this problem you can invoke Python with '-m pip' instead of running pip directly.\nWARNING: Value for scheme.platlib does not match. Please report this to <https://github.com/pypa/pip/issues/10151>\ndistutils: /usr/local/lib64/python3.6/site-packages\nsysconfig: /usr/lib64/python3.6/site-packages\nWARNING: Value for scheme.purelib does not match. Please report this to <https://github.com/pypa/pip/issues/10151>\ndistutils: /usr/local/lib/python3.6/site-packages\nsysconfig: /usr/lib/python3.6/site-packages\nWARNING: Value for scheme.headers does not match. Please report this to <https://github.com/pypa/pip/issues/10151>\ndistutils: /usr/local/include/python3.6m/UNKNOWN\nsysconfig: /usr/include/python3.6m/UNKNOWN\nWARNING: Value for scheme.scripts does not match. Please report this to <https://github.com/pypa/pip/issues/10151>\ndistutils: /usr/local/bin\nsysconfig: /usr/bin\nWARNING: Value for scheme.data does not match. Please report this to <https://github.com/pypa/pip/issues/10151>\ndistutils: /usr/local\nsysconfig: /usr\nWARNING: Additional context:\nuser = False\nhome = None\nroot = None\nprefix = None\nERROR: Exception:\nTraceback (most recent call last):\n  File \"/usr/local/lib/python3.6/site-packages/pip/_internal/cli/base_command.py\", line 173, in _main\n    status = self.run(options, args)\n  File \"/usr/local/lib/python3.6/site-packages/pip/_internal/cli/req_command.py\", line 203, in wrapper\n    return func(self, options, args)\n  File \"/usr/local/lib/python3.6/site-packages/pip/_internal/commands/install.py\", line 316, in run\n    reqs, check_supported_wheels=not options.target_dir\n  File \"/usr/local/lib/python3.6/site-packages/pip/_internal/resolution/resolvelib/resolver.py\", line 95, in resolve\n    collected.requirements, max_rounds=try_to_avoid_resolution_too_deep\n  File \"/usr/local/lib/python3.6/site-packages/pip/_vendor/resolvelib/resolvers.py\", line 472, in resolve\n    state = resolution.resolve(requirements, max_rounds=max_rounds)\n  File \"/usr/local/lib/python3.6/site-packages/pip/_vendor/resolvelib/resolvers.py\", line 366, in resolve\n    failure_causes = self._attempt_to_pin_criterion(name)\n  File \"/usr/local/lib/python3.6/site-packages/pip/_vendor/resolvelib/resolvers.py\", line 212, in _attempt_to_pin_criterion\n    criteria = self._get_updated_criteria(candidate)\n  File \"/usr/local/lib/python3.6/site-packages/pip/_vendor/resolvelib/resolvers.py\", line 203, in _get_updated_criteria\n    self._add_to_criteria(criteria, requirement, parent=candidate)\n  File \"/usr/local/lib/python3.6/site-packages/pip/_vendor/resolvelib/resolvers.py\", line 172, in _add_to_criteria\n    if not criterion.candidates:\n  File \"/usr/local/lib/python3.6/site-packages/pip/_vendor/resolvelib/structs.py\", line 151, in __bool__\n    return bool(self._sequence)\n  File \"/usr/local/lib/python3.6/site-packages/pip/_internal/resolution/resolvelib/found_candidates.py\", line 140, in __bool__\n    return any(self)\n  File \"/usr/local/lib/python3.6/site-packages/pip/_internal/resolution/resolvelib/found_candidates.py\", line 128, in <genexpr>\n    return (c for c in iterator if id(c) not in self._incompatible_ids)\n  File \"/usr/local/lib/python3.6/site-packages/pip/_internal/resolution/resolvelib/found_candidates.py\", line 32, in _iter_built\n    candidate = func()\n  File \"/usr/local/lib/python3.6/site-packages/pip/_internal/resolution/resolvelib/factory.py\", line 209, in _make_candidate_from_link\n    version=version,\n  File \"/usr/local/lib/python3.6/site-packages/pip/_internal/resolution/resolvelib/candidates.py\", line 301, in __init__\n    version=version,\n  File \"/usr/local/lib/python3.6/site-packages/pip/_internal/resolution/resolvelib/candidates.py\", line 156, in __init__\n    self.dist = self._prepare()\n  File \"/usr/local/lib/python3.6/site-packages/pip/_internal/resolution/resolvelib/candidates.py\", line 227, in _prepare\n    dist = self._prepare_distribution()\n  File \"/usr/local/lib/python3.6/site-packages/pip/_internal/resolution/resolvelib/candidates.py\", line 306, in _prepare_distribution\n    self._ireq, parallel_builds=True\n  File \"/usr/local/lib/python3.6/site-packages/pip/_internal/operations/prepare.py\", line 508, in prepare_linked_requirement\n    return self._prepare_linked_requirement(req, parallel_builds)\n  File \"/usr/local/lib/python3.6/site-packages/pip/_internal/operations/prepare.py\", line 552, in _prepare_linked_requirement\n    self.download_dir, hashes\n  File \"/usr/local/lib/python3.6/site-packages/pip/_internal/operations/prepare.py\", line 249, in unpack_url\n    unpack_file(file.path, location, file.content_type)\n  File \"/usr/local/lib/python3.6/site-packages/pip/_internal/utils/unpacking.py\", line 256, in unpack_file\n    untar_file(filename, location)\n  File \"/usr/local/lib/python3.6/site-packages/pip/_internal/utils/unpacking.py\", line 226, in untar_file\n    with open(path, \"wb\") as destfp:\nUnicodeEncodeError: 'ascii' codec can't encode character '\\xe9' in position 117: ordinal not in range(128)\n"}

https://github.com/pypa/pip/issues/10151
Done
Fix the version of pip3 as a workaround.
Confirm
[centos@bastion-1 ~]$ pip3 --version
pip 21.1.3 from /usr/local/lib/python3.6/site-packages/pip (python 3.6)
[centos@bastion-1 ~]$ ansible --version
[DEPRECATION WARNING]: Ansible will require Python 3.8 or newer on the controller starting with Ansible 2.12. Current version: 3.6.8 (default, Nov 16 2020, 16:55:22) [GCC 4.8.5
20150623 (Red Hat 4.8.5-44)]. This feature will be removed from ansible-core in version 2.12. Deprecation warnings can be disabled by setting deprecation_warnings=False in
ansible.cfg.
ansible [core 2.11.3]
  config file = None
  configured module search path = ['/home/centos/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python3.6/site-packages/ansible
  ansible collection location = /home/centos/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/local/bin/ansible
  python version = 3.6.8 (default, Nov 16 2020, 16:55:22) [GCC 4.8.5 20150623 (Red Hat 4.8.5-44)]
  jinja version = 3.0.1
  libyaml = True

Was the terratest failed due to this?

@feeblefakie Yes! Sorry for the late reply.


SSL directive is deprecated

Details
Description
The "ssl" directive is deprecated, use the "listen ... ssl" directive instead.
Steps to reproduce
All generated nginx.conf will encounter this warning.
Expected behavior
No warning should be returned when reloading nginx.
Screenshots

👋 This is intentional behaviour in the tool -- we utilise the SSL directive to ensure that SSL is disabled on all versions of NGINX whilst certbot is configured. Subsequent setup steps in the nginxconfig UI will instruct you to run another sed command that will remove the SSL directive again.

Oops, apologies! Better safe than sorry 😅


Change gantry sampling from cylinder to half-sphere

Closing this because the previous problem with "difficult to sample gantry" is largely solved by the fix of the "incorrect break statement"


Allow parsing of API_KEY to get more info from geo.ipify.org/api [Suggestion]

Thank you for this useful API.
I was working with it and wanted to use the geo.ipify api to get more details like ISP, since ipify api does does not support this out of the box unless you use the geo.ipify api and create an apikey to add to the endpoint url.

If possible, it would be cool to add the geo.ipify api endpint as well to the list of constants and call that if the user provides a valid api key to the ipify() function; e.g ipify(API_KEY).
If this would be useful, if need be I can make this addition myself if contributions are accepted. I did not see a contribution guild file so I decided to raise an issue to ask the team.

Cheers.

Thanks for the suggestion. It's not something I plan to add to this package. I prefer to keep it simple and focused on only getting the IP address.


fix problem:The IValidator doesn't regist

I find the IValidator doesn't regist, so I try to fix it

You are right, registration vanished "somehow" 😄  Thanks @jin337359649

Hello, I have read your post and I think it is very great, I want to share this with more people. So I want to translate the post to mandarin and post on a Chinese platform called "博客园", I hope you can agree with this, thank you very much!
P.S. I will mark the origin resource
------------------ 原始邮件 ------------------
发件人: "Kamil<EMAIL_ADDRESS>发送时间: 2019年10月30日(星期三) 下午5:59
收件人<EMAIL_ADDRESS>抄送: "沐雨轻尘"<337359649<EMAIL_ADDRESS>主题: Re: [kgrzybek/modular-monolith-with-ddd] fix problem:The IValidator doesn't regist (#27)
You are right, registration vanished "somehow"   Thanks @jin337359649
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


change mirrors to centos8 stream repo's to vault

That's a clever place to do it.  I was looking to do it around line 623 instead but it had issues with the name change of the stream repos.  Where you're doing it looks like it will just work without much issue at all.

I'm not sure the second commit will work because of the way that the centos-stream repository names are changed part way through so as not to clash with the Rocky Linux repo names.  Will need to test this and see.

@pajamian the extras-common repo doesn't seem to be in the rocky linux vault?

It is: https://dl.rockylinux.org/vault/centos/8-stream/extras/x86_64/extras-common/
Also since extras-common is not a Rocky Linux repo it may not require renaming (looking into that).

http://debuginfo.centos.org/8-stream seems not to be mirrored at rocky? (but is still up at it's original url and has a mirror at https://linuxsoft.cern.ch/centos-debuginfo/

That and epel-next may cause issues since it will be archived as well.  It will require some testing to find out for sure if it actually matters.

Okay, let me know.  I'll also try running on a clean stream-8 install probably tomorrow and see how it goes.
Thanks for your work in this, BTW, it's really appreciated!

there are a few stream-xxx repo files now that can be cleaned up,

Yes We can either automatically remove them now (they are no longer needed) or just put instructions to do so.  Previously they were kept because there might still be newer packages left from them on the system.

and I think the text at the end of the move can also be revised, since there will never be a centos8-stream update anymore?

Indeed.  In fact this changes the whole dynamic of migrating from CentOS Stream.


Update documentation

Before making it official we have to ensure documentation is updated. Could you take a look?
https://napalm.readthedocs.io/en/latest/support/index.html
Also, you will need a PR to tell napalm this is py3 compliant. Something like this:
https://github.com/napalm-automation/napalm-base/pull/177/files

Oh, and it has to be added here as well:
https://github.com/napalm-automation/napalm/blob/develop/requirements.txt

We have to consolidate those but while we work on making them py3 compliant we need to keep them separate : (

Note that the getters support matrix will be filled automatically as soon as we officially launch the driver so you can ignore that part : )

Here are PR's
Here travis is having problem with installing napalm-vyos package
https://github.com/napalm-automation/napalm/pull/344
Support in ansible module
https://github.com/napalm-automation/napalm-ansible/pull/44
added comment, If needed separate PR probably would be easier if this pr is merged first before next similar
https://github.com/napalm-automation/napalm-base/pull/177

Ok, everything is done : )
Here is the docs (we have to merge with master soon):
https://napalm.readthedocs.io/en/develop/support/index.html#getters-support-matrix

Let's close this one, reopen it if you have any doubt.
Thanks for the hard work : )


[Documentation] clean up tutorial code and consolidate all instructions

[ ] consolidate all uses of tornjak agent vs tornjak backend terms
[ ] create versioning system for all images
[ ] remove the dev instructions from the front page - maybe make separate docs for development
[ ] quickstart files need renaming and maybe one central file to point to the rest

#114 takes care of the third and fourth bullet points

@mamy-CS recent changes to the quickstart via #138 - does this address your comment?


Rename our Port to Xpod, Xflow or alternative

The original license has limitations using the name ‘Xembly’. We should rename it. I came up with the name Xpod. Pod is a capsule, which fits nicely for what it is, an Xml pod. Or Xflow because Xml manipulation is fluent using it.  Or Xbuild, Xjoin, Xup, Xfluid, Xiver, Xackage, Xbag...
Or XugFedic ^^
What do you think, @ICACLE @icaOBU @aveXcaesar @koeeenig ?

What about the name Xamble, a combination of XML and Assembly. It`s close to the origin 'Xembly' but i little bit different :)

Csembly for C#-Xembly? Same pronunciation, but different spelling?

Personally I would like to keep the X in the name.
I like Xamble, didn't think of that - maybe we can even call it just Xambly?

Xambly sounds good for me too. I am not quite sure how different the name has to be in terms of the licence used in Xembly repo.


ASA-2205

Able to show the correct error statement in the Jenkins console output.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Spec: void arrow setters should allow any rhs type

This is the language specification specific issue for #29679.

Being addressed by this CL (which also addresses #28942).

Landed as 26d6e3596d034024605ecf9dcfa489b544fa6245.


Track Docker image hashes for stronger reproducibility

Currently, we're tracking the docker image tag used to run each simulation, but we're allowing simulators to replace Docker image tags. This means were missing a little information needed to fully reproduce a run.

[ ] Add image hashes to Image
[ ] Add image hashes to SimulationRun
[ ] Change related database models and controllers
[ ] Make BioSimulators-test-suite push hashes information (during or prior to post_entry_to_biosimulators_api)
[ ] Store image sha to SimulationRun during execution

:tada: This issue has been resolved in version 5.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket: