cluster: use downstream protocol

Use downstream protocol for upstream connection. It will help to onboard the protocol sniffing for h2. Otherwise, we will need to split http1 vs h2.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

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

Test name
Commit
Details
Rerun command

e2e-simpleTests-distroless_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-distroless_istio

e2e-mixer-no_auth_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-simpleTests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests_istio

e2e-bookInfoTests-trustdomain_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-trustdomain_istio

e2e-dashboard_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-dashboard_istio

integ-new-install-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-new-install-k8s-tests_istio

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

integ-mixer-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
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.

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

Test name
Commit
Details
Rerun command

e2e-simpleTests-distroless_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-distroless_istio

e2e-mixer-no_auth_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-simpleTests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests_istio

e2e-bookInfoTests-trustdomain_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-trustdomain_istio

e2e-dashboard_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-dashboard_istio

integ-new-install-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-new-install-k8s-tests_istio

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

integ-mixer-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-mixer-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

e2e-simpleTests-distroless_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-distroless_istio

e2e-mixer-no_auth_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-simpleTests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests_istio

e2e-bookInfoTests-trustdomain_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-trustdomain_istio

e2e-dashboard_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-dashboard_istio

integ-new-install-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-new-install-k8s-tests_istio

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

integ-mixer-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-mixer-k8s-tests_istio

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

pilot-e2e-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-e2e-envoyv2-v1alpha3_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.

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

Test name
Commit
Details
Rerun command

e2e-simpleTests-distroless_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-distroless_istio

e2e-mixer-no_auth_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-simpleTests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests_istio

e2e-bookInfoTests-trustdomain_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-trustdomain_istio

e2e-dashboard_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-dashboard_istio

integ-new-install-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-new-install-k8s-tests_istio

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

integ-mixer-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-mixer-k8s-tests_istio

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

pilot-e2e-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-e2e-envoyv2-v1alpha3_istio

pilot-multicluster-e2e_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-multicluster-e2e_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.

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

Test name
Commit
Details
Rerun command

e2e-simpleTests-distroless_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-distroless_istio

e2e-mixer-no_auth_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-simpleTests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests_istio

e2e-bookInfoTests-trustdomain_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-trustdomain_istio

e2e-dashboard_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-dashboard_istio

integ-new-install-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-new-install-k8s-tests_istio

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

integ-mixer-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-mixer-k8s-tests_istio

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

pilot-e2e-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-e2e-envoyv2-v1alpha3_istio

pilot-multicluster-e2e_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-multicluster-e2e_istio

e2e-simpleTests-cni_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-cni_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.

Close this pr.
Duplicate with https://github.com/istio/istio/pull/16452

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

Test name
Commit
Details
Rerun command

e2e-mixer-no_auth_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-simpleTests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests_istio

e2e-bookInfoTests-trustdomain_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-trustdomain_istio

e2e-dashboard_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-dashboard_istio

integ-new-install-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-new-install-k8s-tests_istio

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

integ-mixer-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-mixer-k8s-tests_istio

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

pilot-e2e-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-e2e-envoyv2-v1alpha3_istio

pilot-multicluster-e2e_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-multicluster-e2e_istio

e2e-simpleTests-cni_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-cni_istio

e2e-simpleTests-distroless_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-distroless_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.

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

Test name
Commit
Details
Rerun command

e2e-bookInfoTests-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-simpleTests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests_istio

e2e-bookInfoTests-trustdomain_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-trustdomain_istio

e2e-dashboard_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-dashboard_istio

integ-new-install-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-new-install-k8s-tests_istio

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

integ-mixer-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-mixer-k8s-tests_istio

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

pilot-e2e-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-e2e-envoyv2-v1alpha3_istio

pilot-multicluster-e2e_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-multicluster-e2e_istio

e2e-simpleTests-cni_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-cni_istio

e2e-simpleTests-distroless_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-distroless_istio

e2e-mixer-no_auth_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-mixer-no_auth_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.

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

Test name
Commit
Details
Rerun command

e2e-simpleTests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests_istio

e2e-dashboard_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-dashboard_istio

integ-new-install-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-new-install-k8s-tests_istio

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

integ-mixer-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-mixer-k8s-tests_istio

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

pilot-e2e-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-e2e-envoyv2-v1alpha3_istio

pilot-multicluster-e2e_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-multicluster-e2e_istio

e2e-simpleTests-cni_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-cni_istio

e2e-simpleTests-distroless_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-distroless_istio

e2e-mixer-no_auth_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-bookInfoTests-trustdomain_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-trustdomain_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.

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

Test name
Commit
Details
Rerun command

e2e-simpleTests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests_istio

e2e-dashboard_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-dashboard_istio

integ-new-install-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-new-install-k8s-tests_istio

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

integ-mixer-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-mixer-k8s-tests_istio

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

pilot-e2e-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-e2e-envoyv2-v1alpha3_istio

pilot-multicluster-e2e_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-multicluster-e2e_istio

e2e-simpleTests-distroless_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-distroless_istio

e2e-mixer-no_auth_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-bookInfoTests-trustdomain_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-trustdomain_istio

e2e-simpleTests-cni_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-cni_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.

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

Test name
Commit
Details
Rerun command

e2e-dashboard_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-dashboard_istio

integ-new-install-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-new-install-k8s-tests_istio

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

integ-mixer-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-mixer-k8s-tests_istio

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

pilot-e2e-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-e2e-envoyv2-v1alpha3_istio

pilot-multicluster-e2e_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-multicluster-e2e_istio

e2e-simpleTests-distroless_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-distroless_istio

e2e-mixer-no_auth_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-bookInfoTests-trustdomain_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-trustdomain_istio

e2e-simpleTests-cni_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-cni_istio

e2e-simpleTests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests_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.

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

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-new-install-k8s-tests_istio

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

integ-mixer-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-mixer-k8s-tests_istio

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

pilot-e2e-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-e2e-envoyv2-v1alpha3_istio

pilot-multicluster-e2e_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-multicluster-e2e_istio

e2e-simpleTests-distroless_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-distroless_istio

e2e-mixer-no_auth_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-bookInfoTests-trustdomain_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-trustdomain_istio

e2e-simpleTests-cni_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-cni_istio

e2e-simpleTests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests_istio

e2e-dashboard_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-dashboard_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.

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

Test name
Commit
Details
Rerun command

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

integ-mixer-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-mixer-k8s-tests_istio

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

pilot-e2e-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-e2e-envoyv2-v1alpha3_istio

pilot-multicluster-e2e_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-multicluster-e2e_istio

e2e-simpleTests-distroless_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-distroless_istio

e2e-mixer-no_auth_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-bookInfoTests-trustdomain_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-trustdomain_istio

e2e-simpleTests-cni_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-cni_istio

e2e-simpleTests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests_istio

e2e-dashboard_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-dashboard_istio

integ-new-install-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-new-install-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.

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

Test name
Commit
Details
Rerun command

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

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

pilot-e2e-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-e2e-envoyv2-v1alpha3_istio

pilot-multicluster-e2e_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-multicluster-e2e_istio

e2e-simpleTests-distroless_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-distroless_istio

e2e-mixer-no_auth_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-bookInfoTests-trustdomain_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-trustdomain_istio

e2e-simpleTests-cni_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-cni_istio

e2e-simpleTests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests_istio

e2e-dashboard_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-dashboard_istio

integ-new-install-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-new-install-k8s-tests_istio

integ-mixer-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
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.

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

Test name
Commit
Details
Rerun command

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

pilot-e2e-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-e2e-envoyv2-v1alpha3_istio

pilot-multicluster-e2e_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-multicluster-e2e_istio

e2e-simpleTests-distroless_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-distroless_istio

e2e-mixer-no_auth_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-bookInfoTests-trustdomain_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-trustdomain_istio

e2e-simpleTests-cni_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-cni_istio

e2e-simpleTests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests_istio

e2e-dashboard_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-dashboard_istio

integ-new-install-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-new-install-k8s-tests_istio

integ-mixer-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-mixer-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

pilot-e2e-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-e2e-envoyv2-v1alpha3_istio

pilot-multicluster-e2e_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-multicluster-e2e_istio

e2e-simpleTests-distroless_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-distroless_istio

e2e-mixer-no_auth_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-bookInfoTests-trustdomain_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-trustdomain_istio

e2e-simpleTests-cni_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests-cni_istio

e2e-simpleTests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-simpleTests_istio

e2e-dashboard_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-dashboard_istio

integ-new-install-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-new-install-k8s-tests_istio

integ-mixer-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-mixer-k8s-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

pilot-e2e-envoyv2-v1alpha3_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-e2e-envoyv2-v1alpha3_istio

pilot-multicluster-e2e_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-multicluster-e2e_istio

e2e-bookInfoTests-trustdomain_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-trustdomain_istio

integ-mixer-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-mixer-k8s-tests_istio

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

integ-new-install-k8s-tests_istio
72cff5ce4d84b67198cf0b43bec461b2c183ba3c
link
/test integ-new-install-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.

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

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-multicluster-e2e_istio

e2e-bookInfoTests-trustdomain_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test e2e-bookInfoTests-trustdomain_istio

integ-mixer-k8s-tests_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test integ-mixer-k8s-tests_istio

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

integ-new-install-k8s-tests_istio
bbf1ba1b540e4a616f4b878effc5a4ab5cc7a917
link
/test integ-new-install-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.

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

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio
d06634c0e44a01d689ebfb3558abf34a1a097489
link
/test pilot-multicluster-e2e_istio

integ-new-install-k8s-tests_istio
bbf1ba1b540e4a616f4b878effc5a4ab5cc7a917
link
/test integ-new-install-k8s-tests_istio

integ-mixer-k8s-tests_istio
bbf1ba1b540e4a616f4b878effc5a4ab5cc7a917
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.

/cherrypick release-1.3

@yxue: #17073 failed to apply on top of branch "release-1.3":
Applying: use downstream protocol for sniffing port only
error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	pilot/pkg/networking/core/v1alpha3/cluster.go
M	pilot/pkg/networking/core/v1alpha3/cluster_test.go
Falling back to patching base and 3-way merge...
Auto-merging pilot/pkg/networking/core/v1alpha3/cluster_test.go
CONFLICT (content): Merge conflict in pilot/pkg/networking/core/v1alpha3/cluster_test.go
Auto-merging pilot/pkg/networking/core/v1alpha3/cluster.go
Patch failed at 0002 use downstream protocol for sniffing port only

In response to this:

/cherrypick release-1.3

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.

Erm, negotiated downstream protocol doesn't imply that the selected protocol is supported by upstream, so this is going to break things (and did in the past, see: #6158, #6421, #6611).
Please revert this, unless you think that this issue is mitigated, somehow...

@PiotrSikora I want use Cluster_USE_DOWNSTREAM_PROTOCOL only for upstream clusters that the service port protocol is not defined. If the user doesn't specify the port for the service, the Envoy also doesn't know which protocol should be used for upstream.
client -- http 2 --> envoy --- ? ---> service

For these scenarios, we apply Cluster_USE_DOWNSTREAM_PROTOCOL to the cluster. Does it make sense?

In the case you described, HTTP/2 will be used between sidecar and the service, but there is no guarantee that this service understands HTTP/2, which might break things (see linked issue).
Notably, HTTP/2 is negotiated between hops, so the service that supports only HTTP/1.1 works fine with clients that support both HTTP/1.1 and HTTP/2, and the request flow without Istio looks like this:
[HTTP client] --http/1.1--> [HTTP/1.1 service]

With Istio, prior to this change, this would either be turned into:
[HTTP client] --http/1.1--> [Istio Proxy's TCP proxy] --http/1.1--> [HTTP/1.1 service]

when service protocol wasn't configured as HTTP, or:
[HTTP client] --http/2--> [Istio Proxy's HTTP proxy] --http/1.1--> [HTTP/1.1 service]

when service protocol was configured as HTTP/1.1.
However, when using Cluster_USE_DOWNSTREAM_PROTOCOL, the first case will now use HTTP/2:
[HTTP client] --http/2--> [Istio Proxy's HTTP proxy] --http/2--> [HTTP/1.1 service]

breaking service that supports only HTTP/1.1.

With Istio, prior to this change, this would either be turned into:

[HTTP client] --http/1.1--> [Istio Proxy's TCP proxy] --http/1.1--> [HTTP/1.1 service]
when service protocol wasn't configured as HTTP

or
[HTTP client] --http/1.1--> [Istio Proxy's TCP proxy] --TCP proxy ?? --> [HTTP/1.1 service]

I think the inbound listener will use TCP proxy to proxy the traffic to service if the port protocol is not specified.

With Istio, prior to this change, this would either be turned into:

[HTTP client] --http/1.1--> [Istio Proxy's TCP proxy] --http/1.1--> [HTTP/1.1 service]
when service protocol wasn't configured as HTTP

or
[HTTP client] --http/1.1--> [Istio Proxy's TCP proxy] --TCP proxy ?? --> [HTTP/1.1 service]

I think the inbound listener will use TCP proxy to proxy the traffic to service if the port protocol is not specified.

Yes, with TCP proxy, the client will negotiate the HTTP version at L7 (i.e. directly with the service), so it's going to use HTTP/1.1 end-to-end in that case... Sorry if that wasn't clear from my description.
In any case, this PR will break this scenario, so please revert it.

The reason that I want to use this configuration is that we don't need to create the different outbound clusters for http/1.1 and h2. I didn't know that it will break such scenario.
@rshriram do you have any idea on reverting the change?

I understand the concern that alpn is losing upstream request.
However, I don't understand how envoy is negotiating with upstream server.
Isn't http2 or http1 client is selected at envoy before the negotiation?
On Mon, Sep 16, 2019 at 5:29 PM Piotr Sikora<EMAIL_ADDRESS>wrote:

In the case you described, HTTP/2 will be used between sidecar and the
service, but there is no guarantee that this service understands HTTP/2,
which might break things (see linked issue).
Notably, HTTP/2 is negotiated between hops, so the service that supports
only HTTP/1.1 works fine with clients that support both HTTP/1.1 and
HTTP/2, and the request flow without Istio looks like this:
[HTTP client] --http/1.1--> [HTTP/1.1 service]
With Istio, prior to this change, this would either be turned into:
[HTTP client] --http/1.1--> [Istio Proxy's TCP proxy] --http/1.1--> [HTTP/1.1 service]
when service protocol wasn't configured as HTTP, or:
[HTTP client] --http/2--> [Istio Proxy's HTTP proxy] --http/1.1--> [HTTP/1.1 service]
when service protocol was configured as HTTP/1.1.
However, when using Cluster_USE_DOWNSTREAM_PROTOCOL, the first case will
now use HTTP/2:
[HTTP client] --http/2--> [Istio Proxy's HTTP proxy] --http/2--> [HTTP/1.1 service]
breaking service that supports only HTTP/1.1.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/17073?email_source=notifications&email_token=AABTGPT3JZNFOICMKN5EEOLQKAJE7A5CNFSM4IWMOUD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD62Z7JQ#issuecomment-531996582,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABTGPROJR5MREIRJD4QPQTQKAJE7ANCNFSM4IWMOUDQ
.

@lambdai this has nothing to do with ALPN (although, having HTTP protocol version negotiated with upstream using ALPN, which is what @incfly is working on, would help here).
The point is that with Cluster_USE_DOWNSTREAM_PROTOCOL the protocol to upstream is not negotiated, but whatever was negotiated with downstream is selected, which ends up breaking HTTP/1.1-only upstreams.

I don't see a negotiation after tcp connection is created. If we don't specify Cluster_USE_DOWNSTREAM_PROTOCOL, but through USE_CONFIGURED_PROTOCOL
I think the critical part is for inbound cluster we should set USE_CONFIGURED_PROTOCOL and generate http1/2 config upon user's service definition.
However it's safe for outbound cluster, and for the unspecified protocol which doesn't specify http1 or http2.

@yxue could you please either revert this PR, or add a test case with client supporting both: HTTP/1.1 and HTTP/2 and service supporting only HTTP/1.1 proving that this PR doesn't break it?

@PiotrSikora I think it will break the traffic when the port protocol is not specified. Applying this change is the tradeoff of enabling sniffing for h2 in Pilot. We might have alternatives to have multiple clusters for http/1.1 and h2 at this moment. @rshriram what do you think about using multiple clusters instead of using this flag?

@yxue Breaking existing traffic is not an option, please revert this PR... Also, it would be useful to add that test case, so this won't be reintroduced again in a few months.
cc @duderino

@PiotrSikora I am going to revert this change. Is there any Envoy issue to track the ALPN negotiation? I think it's a blocking issue for protocol sniffing with h2.
Currently, when http inspector detects the traffic to be h2, it will use TCP proxy, which will not break the traffic for both http/1.1 and h2 service. In the future, if we want to use HTTP proxy for h2, the Envoy should be able to negotiate the ALPN with upstream.

@PiotrSikora I am going to revert this change. Is there any Envoy issue to track the ALPN negotiation? I think it's a blocking issue for protocol sniffing with h2.

envoyproxy/envoy#3431, @incfly is working on it.

Currently, when http inspector detects the traffic to be h2, it will use TCP proxy, which will not break the traffic for both http/1.1 and h2 service. In the future, if we want to use HTTP proxy for h2, the Envoy should be able to negotiate the ALPN with upstream.

Erm, using TCP proxy after detecting HTTP traffic seems wrong to me, since it's going to bypass all the HTTP routing rules. What was the reason for this choice?

H2 traffic will be proxied by TCP proxy when port's name is not specified whether protocol sniffing is used or not.
Even though H2 is detected by the http inspector, but we don't know how to set the upstream cluster connection, i.e., use HTTP2 or HTTP1 since we cannot get the service port protocol.


How to train the cnn model?

I used
python train.py
--data_dir data/split-by-sequence-identity-30/data/
--mode train
--batch_size 16
--num_epochs 50
--learning_rate 1e-4
(very similar to gnn and enn model training method)
but I got:
Traceback (most recent call last):
File "train.py", line 173, in
parser.add_argument('--data_dir', type=str, default=os.environ['LBA_DATA'])
File "/home/xzhang/miniconda3/envs/atom3d/lib/python3.6/os.py", line 669, in getitem
raise KeyError(key) from None
KeyError: 'LBA_DATA'

The code of the 3DCNN models has a bit different options from the other ones. The three methods were built by adapting three different existing models.
You can avoid the KeyError in os.environ() by pre-defining the variables in question. For example, define the directories:
export LOG_DIR=~/atom3d/examples/lba/cnn3d/log/
export LBA_DATA=~/atom3d-data/lba/

You can then check all the other options via the --help option:
python train.py --help

This provides the following (for me):

usage: train.py [-h] [--data_dir DATA_DIR] [--mode {train,test}]
[--output_dir OUTPUT_DIR] [--unobserved]
[--learning_rate LEARNING_RATE]
[--conv_drop_rate CONV_DROP_RATE]
[--fc_drop_rate FC_DROP_RATE] [--num_epochs NUM_EPOCHS]
[--num_conv NUM_CONV] [--batch_norm] [--no_dropout]
[--batch_size BATCH_SIZE] [--random_seed RANDOM_SEED]
optional arguments:
-h, --help            show this help message and exit
--data_dir DATA_DIR
--mode {train,test}
--output_dir OUTPUT_DIR
--unobserved
--learning_rate LEARNING_RATE
--conv_drop_rate CONV_DROP_RATE
--fc_drop_rate FC_DROP_RATE
--num_epochs NUM_EPOCHS
--num_conv NUM_CONV
--batch_norm
--no_dropout
--batch_size BATCH_SIZE
--random_seed RANDOM_SEED

I am closing this issue.
Feel free to re-open it if the above does not solve this error for you.
Please open a new issue if you run into another problem.


Consumer rebalancing

We require the automatic consumer rebalancing throughout a new project using Kafka 0.9.
This PR contains tested code to support the automatic rebalancing in a consumer group using a round-robin partition assignment scheme.
This PR introduces a topicConsumer, providing a Messages and Error channel which is published to by all the partitionConsumer to allow the client to consume from one single stream.
In addition, the client API is extended with a RebalanceEvent channel, which informs the client of partition consumer changes, inspired by the Consumer Rebalance Listener in the Java API. The SubscriptionOperation constant specifies the type of operation (addition, removal).
Example:

select {
case msg := <-topicConsumer.Messages():
log.Printf("Consumed message offset %d\n", msg.Offset)
consumed++
case event := <-rebalanceEvents:
log.Printf("Performing rebalance with %d changes", len(event.Subscriptions))
case <-signals:
break ConsumerLoop
}

As I'm new to golang and to sarama, I expect that some code will be out of place or already present somewhere else. If so, please point this out to me, I had a hard time figuring out al the different parts of the sarama consumer.
I'd appreciate all feedback towards making this production ready and merge-able.
Thanks!

I believe @dim was also working on this, you may want to pool your resources.

Hey, I have created it as a separate package with extensive tests, but it can be ultimately merged into Sarama I guess: https://github.com/bsm/sarama-cluster

Great, no need for this PR then. The only thing that seems missing in sarama-cluster is a Consumer Rebalance Listener alternative, I'll open an issue to discuss this.
Thanks!


Log terminal output

Capture and log the terminal output. Currently, sys_call sends this to stdout/stderr, but it is not showing up in the unraid log.

Addressed in #8


Add doc for new buildpacks

Closes #201.

Adds missing architecture item to table of contents.
Reorders contents to group user docs before developer docs.
Add into sentence to design doc.

Going to merge this, because better docs is always better :)


related to incoming call using call kit

Hello there,
I was implementing text,audio and video chat so is it possible to we can use same voIP certificate which generated from "developer.apple.com" for audio as well as video?
For demo I used this link:-https://github.com/twilio/video-quickstart-swift
I already refer this link :- https://github.com/twilio/video-quickstart-swift/issues/234
Thank you

Yes, using that same certificate should work. You would need to manage sending the push notifications using some mechanism, such as Twilio Notify. In that notification you could provide payload information that alerts your app whether its a voice only or video call and your app could then respond as required.
Ryan

@paynerc thanks for response I got it.
👍

@paynerc I have some question like:-

can twilio provides a trigger until participant didn't;t join or we use "TVIRoomDelegate" for this?
2.can we have chat option available during audio as well video call?
3.Is twilio provide call logs?
4.can we start recording during call or when we stared from?

Thanks

I see you have moved your questions to #320. I will answer them there and closing this issue.


twister: bugfix: Fix twister output

Fix twister output. "Test suite" used previously did not correspond
to what was counted (test scenarios). Also replace the amount of
preselectd platforms with the amount of platforms that were not
filtered out and actually tested.
Signed-off-by: Maciej Perkowski<EMAIL_ADDRESS>

Looks good, however, it would be helpful to define terminology used in the documentation, i.e. scenario, test suite, configuration, test case and how all of this relates to testcase.yaml and the test cases when using ztest for example.

I based the output on the definitions we are trying to sort and clean out. It is based on the proposition given in https://github.com/zephyrproject-rtos/zephyr/discussions/31090 To recap, a test scenario is an entry from testcase/sample.yaml under tests, which specify configuration used to build a test. Added this also to PR commit. Changes in docs will follow later on.


Add missing comma

Avoiding errors when other application service providers are above fortify UI.

Thanks for this!

Thanks for this!


audit: make keg_only_style non-strict

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

No audit failures in core.

Makes sense, thanks again @commitay!


Weird Data being returned.

"Error": "Key not found: header"

stdClass Object

(
[responseContext] => stdClass Object
(
[serviceTrackingParams] => Array
(
[0] => stdClass Object
(
[service] => GFEEDBACK
[params] => Array
(
[0] => stdClass Object
(
[key] => has_unlimited_entitlement
[value] => False
)
                                [1] => stdClass Object
                                    (
                                        [key] => browse_id
                                        [value] => MPREb_mBlg6YmJiXY
                                    )

                                [2] => stdClass Object
                                    (
                                        [key] => browse_id_prefix
                                        [value] =>
                                    )

                                [3] => stdClass Object
                                    (
                                        [key] => logged_in
                                        [value] => 0
                                    )

This is over 7,000+ lines

YouTube Music just made some pretty dramatic updates so things may not work right anymore. Please provide a code sample to recreate the issue and we can look into it.

So i used the search method
 $yt = new Ytmusicapi\YTMusic();  $song = $yt->search('drake - views', 'songs', null, 1, true); echo $song;

Unfortunately I couldn't recreate the issue you are experiencing. The issue you are seeing is probably either from an A/B test that YouTube Music is conducting or a location specific issue.
I'd still like to see if we can help solve the issue, if possible. I'm not sure what your experience level is, but I'm hoping you can do the following to help us figure the issue out.
Edit the file vendor/ytmusicapi/ytmusicapi/src/mixins/search.php.
Look for the line that reads $response = $this->_send_request($endpoint, $body);. This should be on or around line 77.
Directly after this line, add something like:
file_put_contents("search.json", json_encode($response, JSON_PRETTY_PRINT));

Then run your test program.
Copy the contents of search.json (I usually load it up in a text editor, select all, then copy)
Paste the contest into a new gist at https://gist.github.com and post the link to it here.
I can then try to parse the data and see if I get the same error.
Feel free to use an alternative method to get the contests on the $response variable to me. The above is just one possible way to do it.

I've just attempted to match the current version of the python library, version 1.7.3. It had some changes for search. This also fixes issues with playlists due to a different response format now being sent by Google. Can you try your test search again to see if it works? If it doesn't, please try to get the response data from YouTube based on information in the above post.

Thanks. it works now. as you said issue is with the response format.


Support custom nginx locations and upstreams

custom locations with directives are now
supported. Assume a boxy-rails application
spec like so:
{
 name: 'wheel',
 ssl: true,
 domain: 'wheel.com'
}

We can add custom_locations like so:
{
 name: 'wheel', ssl: true, domain: 'wheel.com',
 custom_locations: [
   {
     uri: '~ ^/somelocation',
     directives: {
       'proxy_http_version' => 1.1,
       'proxy_set_header' => ['Upgrade $http_upgrade', 'Connection $connection_upgrade'],
       'proxy_pass' => 'http://localhost:8800'
     },
     {
       uri: '/otheruri',
       directives: {
         'proxy_pass' => 'http://localhost:9219'
       }
     }
   }
 ]
}

custom upstreams are also supported:
custom_upstreams: [
  {
  name: 'websocket',
  uri: 'localhost:8800'
  },
  {
  name:
    'java-app',
    uri: 'localhost:9219'
  }
]

See spec/nginx_applications_spec.rb'for detailed usage
examples.

Added a bunch of tests to verify behaviour.
Unit tests run via ChefSpec and depend on Berkshelf.
They run quite slow :(

@vipulnsward I've merged the HTTP & HTTPS configuration into a single Nginx config file. Tested it using a self-signed cert. Also fixed other issues like indentation and s/extra/custom/

@sahilm Please squash the commits.

@vipulnsward Done.


isomeric smiles representation mismatch with other drawers

first off, big thanks for smilesDrawer.  love it and use it a lot at fpbase.org
I'm struggling with cis/trans representation of an isomeric SMILES string grabbed from the protein databank.  This is just a representative example, but I see this with a lot of similar structures, and I unfortunately don't know enough about SMILES to know whether this is an issue with smilesDrawer, the string itself, or something else.
see the CRO ligand at PDB.
isomeric SMILES string:  C[C@@H](O)[C@H](N)C1=N\C(=C/c2ccc(O)cc2)C(=O)N1CC(O)=O
their image:

note the benzene ring points in the opposite direction as the C=O bond on the other ring...
same with pubchem sketcher and chemdraw:

and with molview:

but in smilesDrawer the benzene ring points in the same direction as the C=O bond on the other ring:

full smilesDrawer code example here:
https://codesandbox.io/s/boring-lehmann-22o1d
would love to know if this is on my end or in smilesDrawer.  Thanks!

any thoughts on this?  If you're pretty confident it's just user error on my end, I'm open to that as well :)

bump


Ubuntu returns distro release file info as 'debian'

Problem:
On Ubuntu 14.04, the information from distro release files returns:
ld._ldi.dist = "debian"
ld._ldi.distro_release_info() = {'codename': '', 'name': '', 'version_id': ''}

This is caused by using the /etc/debian_version file as the distro release file, because that matches the search pattern for distro release files, and 'debian' is found in DIST_TO_BASE.
When using the consolidated result, the os-release information supersedes the distro release file information, but if a user uses distro_release_info() or get_distro_release_attr(), this discrepancy will surface.
Proposed solution:
All of the following:

Remove *version from the file search pattern for distro release files. Out of all distros that I know of having such a file (Ubuntu, Debian, Mageia, Slackware), none of these files follows the <name> release <release> (<codename>) pattern.

In function _attempt_to_get_release_file() which determines the file name of the default distro release file to be used, make the decision to use a file not only based upon presence of its first part of the file name in the DIST_TO_BASE dict, but in addition based upon whether it provides at least some information when parsing it with the usual pattern. Ideally, this should be done such that the parsing is performed only once.

This approach leaves the possibility to add support for parsing *version files with their specific format in the future. It just removes today's inconsistency of searching for these files but then not understanding their format.

Solved with PR #49. I am closing this issue.


refactor(organisms:) SfHeader

awaiting #849
Scope of work

replaced SfCircleicon with Sficon
adjusted styling to new designs

Checklist

[x] No commented blocks of code left
[x] Run tests and docs
[x] Self code-reviewed

 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.


Issue during building SRT

The script exit on building SRT
I did a common install on Ubuntu Focal Fossa.

building srt
=======================
Downloading https://github.com/Haivision/srt/archive/v1.4.1.tar.gz
... Done
$ ./configure --prefix=/root/ffmpeg-build-script/workspace --disable-shared --enable-static
./build-ffmpeg: ./configure: /usr/bin/tclsh: bad interpreter: No such file or directory

Failed to Execute ./configure --prefix=/root/ffmpeg-build-script/workspace --disable-shared --enable-static

I've tried to cleanup then try again but the same issue occured.
What's wrong ? Thanks

Remove the configure line above the cmake line; I think it was included incorrectly, have pinged @markus-perl

Fixed in v1.16


This tool did not work recently. The site changed to https.

Thanks. http still works. New version 0.1.3 published. If you want to use https, install 0.1.3. If you want to use http, install 0.1.2.


can't rename meter device to a meaningful name

I have a multiple meter account, and trying to rename the meter device and give it a meaningful name, rather than stick with the meter serial number:

The new device name is kept some time for some time (not sure if it's hours or days),after which it is overrun by the original name with the serial number. Is that the add on or homeassistant responsible for this behavior ?

Similar issue for me. I change the icons for some entities, but thay revert to default after few days (never happened with other integrations)

you can change the device name and it will update nested entity's names, pls let me know if it works for you
thanks

Thanks @elad-bar
It works. Modified name 2 days ago, and it hadn't change back. Closing the issue


Delay of rendering

Hi Manu, hi Ricardo,
if I start the actionbarextra logic after openening of window then I see shortly the standard actionbar and ofter a couple of time the rendering of your module (+ subtitle,+ other font).
What can I do to avoid this. Or is it a mistake by me?

Not your fault. This is a Titanium limitation. See #91

Yes I see it. I have changed the ordering of code.


InvokeGlobalListeners is not called when RegisterStore is used

Describe the bug
InvokeGlobalListeners is not called when RegisterStore is used
To Reproduce
Steps to reproduce the behavior:

Register a manually created store using GlobalStore.RegisterStore
subscribe to global state using globalStore.SubscribeToGlobalState(..)
trigger any store actions
global listeners are not triggered

Expected behavior
global listeners are called for state changes in any store.

I will investigate a bit more on this and get back on this issue. For clarification when you say you are triggering any store actions, are you triggering the action on the store directly or via the Global Store methods?

so for stores which are RegisterStore'd rather than CreateStore'd.
You can see that in CreateStore you've called appStore.subscribe(this.InvokeGlobalListeners.bind(this));
but in RegisterStore you haven't.
In fact it looks almost like if you move line 71 to bellow line 98 you'd cover both scenarios.

Actually I was thinking of the same thing. I will fix and release a new version on Monday. Does that work for you?

Sorry I got busy with some critical work. Thanks for the PR @rotty3000

No problem at all! Thanks for merging 😊
On Sun., Mar. 28, 2021, 9:50 a.m. Pratik Bhattacharya, <
@.***> wrote:

Sorry I got busy with some critical work. Thanks for the PR @rotty3000
https://github.com/rotty3000
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/redux-micro-frontend/issues/16#issuecomment-808899774,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABD2TA3ZGJSPXGC4MENNNDTF4XZHANCNFSM4ZCVPGYQ
.

Version 1.1.0 was release which will have the changes


Fix disc full enumeration by checking that $(MonoAndroidAssetsPrefix) is not empty string

During AndroidX and GooglePlaySerivces/Firebase/MLKit builds experienced following warning (which was crashing one of  Mac boxes with running out of application memory):
MSBUILD : warning MSB5029: The value “\**\.*\**” of the “Exclude” attribute in element <ItemGroup> in file “/Users/moljac/.nuget/packages/xamarin.legacy.sdk/0.2.0-alpha2/Sdk/AutoImport.Android.props (26,61)” is a wildcard that results in enumerating all files on the drive, which was likely not intended. Check that referenced properties are always defined.

This PR fixes this warning by adding check for $(MonoAndroidAssetsPrefix) not being empty string.

Do you have a .binlog of when this problem occurred?

Attached. This time it took long time to crash mac.
Compressed binlog:
restore.binlog.zip

My memory is the latest workload wasn't installed, maybe we can error on that as well?

Anything would help. Otherwise digging what is going on is quite time consuming.

 The changes here are just slightly different.
@moljac feel free to review the new PR, thanks!


Tidy up release sections

Refs https://github.com/ComposeGears/Valkyrie/pull/121#discussion_r1713282566.

Release snapshots instead of nightlys.
Add more release template categories.

https://github.com/ComposeGears/Valkyrie/actions/runs/10347838861/job/28638863729

If we should remove -p for non-snapshot release? Which means it will not be a pre-release.
https://github.com/ComposeGears/Valkyrie/blob/0032ffc7dbcb0a9083fd3be8d710e2f62abb38e4/.github/workflows/release.yml#L77

If we should remove -p for non-snapshot release? Which means it will not be a pre-release.
https://github.com/ComposeGears/Valkyrie/blob/0032ffc7dbcb0a9083fd3be8d710e2f62abb38e4/.github/workflows/release.yml#L77

I think it should be a pre-release due to it's just a latest dev build to test if some feature works as expected, some issue fixed and so on.
Release means stable build + published into marketplace

I think it should be a pre-release due to it's just a latest dev build to test if some feature works as expected, some issue fixed and so on.
Release means stable build + published into marketplace

If I understand correctly, you made them pre-release for rearranging release notes, now this manual step has been replaced by this template.

For a release, it will be sent to the marketplace and released from GH.
For a snapshot, it will not be sent to the marketplace and pre-released from GH.

I mean we can remove -p for the second case here.

I mean we can remove -p for the second case here.

Agree

https://github.com/ComposeGears/Valkyrie/actions/runs/10348719007/job/28641545831

it compares old branch

I see, deleted now.

https://github.com/ComposeGears/Valkyrie/releases/tag/0.6.0-SNAPSHOT

Amazing)


_auxLemmas

The following example:
import Mathlib

open Real Nat in
example (n : Nat) : Gamma (↑n + 1) * Gamma (↑n + 1) = (n ! * n !) := by
  calcify simp only [←cast_mul, Gamma_nat_eq_factorial]

... produces the following suggestion:
calc
  Gamma (↑n + 1) * Gamma (↑n + 1)
  _ = ↑n ! * Gamma (↑n + 1) := (congrArg (fun x => x * Gamma (↑n + 1)) (Gamma_nat_eq_factorial n))
  _ = ↑n ! * ↑n !           := (congrArg (fun x => ↑n ! * x) (Gamma_nat_eq_factorial n))
  _ = ↑(n ! * n !)          := (MWE.Basic._auxLemma.1 n ! n !)
  _ = ↑n ! * ↑n !           := (MWE.Basic._auxLemma.1 n ! n !).symm

Is looks like cast_mul is being turned into MWE.Basic._auxLemma.1, which breaks the proof.

I have no clue where these aux lemmas come from. Do they correspond to cast_mul in some form?

I don't know the details when that happens, but the simplifier sometimes put parts of the proof into a self contained theorem, as an optimization. So it makes sense for calcify to look though them.


cocomac: Watch <IP_ADDRESS>

cocomac requests the watch of the watch_keyword 54\.251\.52\.106. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

54\.251\.52\.106 has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Rejected by Makyen in Charcoal HQ. Reason: 'I made a separate watch for this, because I didn't notice the PR had been created.'


Issue with 'state list' and 'import' while using flag --terragrunt-source

Hi!
I have an issue with importing/checking state using flag --terragrunt-source.
I have installed:

terragrunt version v0.21.2
Terraform v0.12.13

I succeed with import/state list when I do not use the flag (code of module on remote and local repos are the same):
terragrunt state list --terragrunt-source-update --terragrunt-source ~/code/tf-modules
terragrunt import aws_route53_zone.this Z2IDF07EG6TTDU --terragrunt-source-update
I'm getting failure using the following command:
terragrunt state list --terragrunt-source-update --terragrunt-source ~/code/tf-modules
terragrunt import aws_route53_zone.this ***** --terragrunt-source-update --terragrunt-non-interactive --terragrunt-source ~/code/tf-modules
Log of failure with 'state list':
[terragrunt] 2019/11/03 15:53:47 Reading Terragrunt config file at /Users/ilyag/code/infra-deployment/shared/route53/public-hosted-zone/terragrunt.hcl
[terragrunt] [/Users/ilyag/code/infra-deployment/shared/route53/public-hosted-zone] 2019/11/03 15:53:47 Running command: terraform --version
[terragrunt] 2019/11/03 15:53:47 WARNING: no double-slash (//) found in source URL /Users/ilyag/code/tf-modules. Relative paths in downloaded Terraform code may not work.
[terragrunt] 2019/11/03 15:53:47 The --terragrunt-source-update flag is set, so deleting the temporary folder /Users/ilyag/code/infra-deployment/shared/route53/public-hosted-zone/.terragrunt-cache/82PJTGypR9ac4MN-m2j4lfaTq-o/b4g_FK4aQVtCHnT8JUB6_CFMO4I before downloading source.
[terragrunt] 2019/11/03 15:53:47 Downloading Terraform configurations from file:///Users/ilyag/code/tf-modules into /Users/ilyag/code/infra-deployment/shared/route53/public-hosted-zone/.terragrunt-cache/82PJTGypR9ac4MN-m2j4lfaTq-o/b4g_FK4aQVtCHnT8JUB6_CFMO4I
[terragrunt] 2019/11/03 15:53:47 Copying files from /Users/ilyag/code/infra-deployment/shared/route53/public-hosted-zone into /Users/ilyag/code/infra-deployment/shared/route53/public-hosted-zone/.terragrunt-cache/82PJTGypR9ac4MN-m2j4lfaTq-o/b4g_FK4aQVtCHnT8JUB6_CFMO4I
[terragrunt] 2019/11/03 15:53:47 Setting working directory to /Users/ilyag/code/infra-deployment/shared/route53/public-hosted-zone/.terragrunt-cache/82PJTGypR9ac4MN-m2j4lfaTq-o/b4g_FK4aQVtCHnT8JUB6_CFMO4I
[terragrunt] [/Users/ilyag/code/infra-deployment/shared/route53/public-hosted-zone] 2019/11/03 15:53:47 Initializing remote state for the s3 backend
[terragrunt] [/Users/ilyag/code/infra-deployment/shared/route53/public-hosted-zone] 2019/11/03 15:53:49 Running command: terraform init -backend-config=bucket=**** -backend-config=dynamodb_table=***** -backend-config=encrypt=true -backend-config=key=shared/route53/public-hosted-zone/terraform.tfstate -backend-config=region=us-east-1 -lock-timeout=20m
Terraform initialized in an empty directory!

The directory has no Terraform configuration files. You may begin working
with Terraform immediately by creating Terraform configuration files.
[terragrunt] 2019/11/03 15:53:49 Running command: terraform state list
No state file was found!

State management commands require a state file. Run this command
in a directory where Terraform has been run or use the -state flag
to point the command to a specific state location.
[terragrunt] 2019/11/03 15:53:49 Hit multiple errors:
exit status 1

Log of failure with 'import':
[terragrunt] 2019/11/03 16:05:48 Reading Terragrunt config file at /Users/ilyag/code/infra-deployment/shared/route53/public-hosted-zone/terragrunt.hcl
[terragrunt] [/Users/ilyag/code/infra-deployment/shared/route53/public-hosted-zone] 2019/11/03 16:05:48 Running command: terraform --version
[terragrunt] 2019/11/03 16:05:48 WARNING: no double-slash (//) found in source URL /Users/ilyag/code/tf-modules. Relative paths in downloaded Terraform code may not work.
[terragrunt] 2019/11/03 16:05:48 The --terragrunt-source-update flag is set, so deleting the temporary folder /Users/ilyag/code/infra-deployment/shared/route53/public-hosted-zone/.terragrunt-cache/82PJTGypR9ac4MN-m2j4lfaTq-o/b4g_FK4aQVtCHnT8JUB6_CFMO4I before downloading source.
[terragrunt] 2019/11/03 16:05:48 Downloading Terraform configurations from file:///Users/ilyag/code/tf-modules into /Users/ilyag/code/infra-deployment/shared/route53/public-hosted-zone/.terragrunt-cache/82PJTGypR9ac4MN-m2j4lfaTq-o/b4g_FK4aQVtCHnT8JUB6_CFMO4I
[terragrunt] 2019/11/03 16:05:48 Copying files from /Users/ilyag/code/infra-deployment/shared/route53/public-hosted-zone into /Users/ilyag/code/infra-deployment/shared/route53/public-hosted-zone/.terragrunt-cache/82PJTGypR9ac4MN-m2j4lfaTq-o/b4g_FK4aQVtCHnT8JUB6_CFMO4I
[terragrunt] 2019/11/03 16:05:48 Setting working directory to /Users/ilyag/code/infra-deployment/shared/route53/public-hosted-zone/.terragrunt-cache/82PJTGypR9ac4MN-m2j4lfaTq-o/b4g_FK4aQVtCHnT8JUB6_CFMO4I
[terragrunt] 2019/11/03 16:05:48 Skipping var-file /Users/ilyag/code/infra-deployment/shared/environment.tfvars.json as it does not exist
[terragrunt] [/Users/ilyag/code/infra-deployment/shared/route53/public-hosted-zone] 2019/11/03 16:05:48 Initializing remote state for the s3 backend
[terragrunt] [/Users/ilyag/code/infra-deployment/shared/route53/public-hosted-zone] 2019/11/03 16:06:10 Running command: terraform init -backend-config=key=shared/route53/public-hosted-zone/terraform.tfstate -backend-config=region=us-east-1 -backend-config=bucket=**** -backend-config=dynamodb_table=**** -backend-config=encrypt=true -lock-timeout=20m
Terraform initialized in an empty directory!

The directory has no Terraform configuration files. You may begin working
with Terraform immediately by creating Terraform configuration files.
[terragrunt] 2019/11/03 16:06:10 Running command: terraform import -lock-timeout=20m -var-file=/Users/ilyag/code/infra-deployment/commons.tfvars.json aws_route53_zone.this ****

Error: No Terraform configuration files

The directory
/Users/ilyag/code/infra-deployment/shared/route53/public-hosted-zone/.terragrunt-cache/82PJTGypR9ac4MN-m2j4lfaTq-o/b4g_FK4aQVtCHnT8JUB6_CFMO4I
does not contain any Terraform configuration files (.tf or .tf.json). To
specify a different configuration directory, use the -config="..." command
line option.

[terragrunt] 2019/11/03 16:06:10 Hit multiple errors:
exit status 1

This is a bit hard to tell what the problem is without seeing your terragrunt config and folder structure, but guessing from the logs and commands you are trying to run, you are most likely passing in the wrong argument to --terragrunt-source.
(Assuming ~/code/tf-modules is pointing to your module repo root) Specifically, you need to pass in the path to the terraform module you are deploying, not the root of your modules (see the docs reference for --terragrunt-source). The module repo root for --terragrunt-source only works if you are using xxx-all commands.

The issue can be closed
You are absolutely right (I did not understand that part of documentation), after launching the following command, I've got what I wanted:
terragrunt state list --terragrunt-source-update --terragrunt-source ~/code/tf-modules//route53/hosted-zone


Start testing files in /views

Currently, only files in components is being testsed.
However, the UI + UX can be tested by increasing coverage.
Furthermore, ensuring local modification for testing creeping through is mandatory.
This revision should edit jest.config.js such that the code coverage is increased to /views.

This may be obsolete with the switch to vite and vue3. I think that uses cypress instead...


Fix mouse stucking in raw mode

Before:
https://streamable.com/bpa50
After:
https://streamable.com/rdx1d

I get error back.


Only publish coverage data for en_US build

Coverage remained the same at 31.625% when pulling 6cbea215e918426fdc3cc6adcf80e1a4af1963dd on justinedelson:issue/coverage-only-once-per-pr into 66dfe0b323a3dd290fc5906a28424d2d2a0100e4 on Adobe-Consulting-Services:master.

seems to have worked.


Editor & Python console - Sharing exact syntax highlighting and color theme (similar to default in PyCharm)

Hello,
Thank you very much for VS code.
In PyCharm, the Python console shares the exact syntax highlighting and color theme of the editor. This occurs automatically without any changes to the settings. For example:

In VS code, as far as I can tell, it is a lot more work (perhaps even impossible) to get the editor and Python console to share the same theme exactly. Out of the box we get the following, which is much less easy on the eyes.

For folks who work interactively in the console it is very helpful to have the equivalent theme in both areas. This may be especially true for beginners who can use the consistency between the editor and the Python console as a way to help them catch syntactical errors.
From what I can understand from looking into this is that there are ways of customizing just about any property of the Python console if you know which properties you need to adjust. I am not able to easily determine how to take the exact properties of the editor theme, and reflect them to the Python console.
Please let me know if I am missing something straightforward and if you think this would be a reasonable feature request.

The Python extension owns the Python experience in VS Code, please report to https://github.com/microsoft/vscode-python/

Thank you very much.


Stub-based DataTypes

Making MessageNode, EnumNode and GroupNode stub-based.
Full and short name indices for DataTypes.
Depends on https://github.com/kshchepanovskyi/antlr4-jetbrains-adapter/pull/4

Build fails: https://jenkins.ksprojects.org/job/protostuff/job/protobuf-jetbrains-plugin/view/change-requests/job/PR-78/1/console
Can you please change 3.0.+ to concrete version.

3.0.snapshot.efd2349681fbe1719e7115f0a4e8b82ecafe21b9

@kaathewise is it done, or you are planning to add something more?

It is done, can be merged as is. I will probably have a follow-up PR that would use the indices in GoToClassContributor, but it's better to do that separately.

Agree.
On Fri, Aug 25, 2017 at 11:56 AM, Svyatoslav Usachev <
<EMAIL_ADDRESS>wrote:

It is done, can be merged as is. I will probably have a follow-up PR that
would use the indices in GoToClassContributor, but it's better to do that
separately.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/protostuff/protobuf-jetbrains-plugin/pull/78#issuecomment-324862109,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD2luLS1MAxhioMPI2wgljXMpwpyWoPHks5sbowrgaJpZM4O-kIt
.

--
KS

Thank you for help with stubs. I will release new version of a plugin on a next week or two.

@kshchepanovskyi I don't know if that's worth releasing -- the stubs and indices are not used yet, so there is (small) degradation in UX (because the indices are now being built), with no benefit.


Error: Cannot find module 'common-tags'

when i open terminal and type in node index.js it shows up as
Error: Cannot find module 'common-tags'
Require stack:

C:\Users\HP\Desktop\GenBot-master\index.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)
at Function.Module._load (internal/modules/cjs/loader.js:725:27)
at Module.require (internal/modules/cjs/loader.js:952:19)
at require (internal/modules/cjs/helpers.js:88:18)
at Object. (C:\Users\HP\Desktop\GenBot-master\index.js:7:34)
at Module._compile (internal/modules/cjs/loader.js:1063:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
at Module.load (internal/modules/cjs/loader.js:928:32)
at Function.Module._load (internal/modules/cjs/loader.js:769:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12) {
code: 'MODULE_NOT_FOUND',
requireStack: [ 'C:\Users\HP\Desktop\GenBot-master\index.js' ]

@coogamer352757
This error occurs if you have a missing module. Make sure you have discord.js and common-tags installed.
Run npm install common-tags in the terminal
Next just start the bot using node index.js.
The bot must work as expected now. If this helps you out please close the issue, if not, I'll try to help you out


FIX a missing bracket in old documentation

Read and sign the CLA. This needs to be done only once. PRs that haven't signed it won't be accepted.
Make sure your PR complies with the writer's guide.
Read through the PR diff carefully as sometimes this can reveal issues. The work will be reviewed, but this can save some effort.
Remove these instructions from your PR as they are for your eyes only.

👍


terminator doesn't work on 10.9.5

On OS X 10.9.5 or 10.11, when I brew install terminator and then launch it with terminator &, it just gives me a blank, nonresponsive window with a single header line at the top. No running terminal session inside. The context menu will appear, but doing anything with it tends to make it lock up. (And resizing the window tends to make terminator segfault.
The output shows this, including a complaint about a missing config file.
$ terminator
2015-10-03 19:16:06.882 Python[99257:d07] *** WARNING: Method userSpaceScaleFactor in class NSView is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead.
ConfigBase::load: Unable to open /Users/janke/.config/terminator/config ([Errno 2] No such file or directory: '/Users/janke/.config/terminator/config')
Warning: python-keybinder is not installed. This means the hide_window shortcut will be unavailable
Unable to bind hide_window key, another instance/window has it.
PluginRegistry::load_plugins: Importing plugin __init__.py failed: 'module' object has no attribute 'AVAILABLE'
ActivityWatch plugin unavailable: please install python-notify
PluginRegistry::load_plugins: Importing plugin activitywatch.py failed: 'module' object has no attribute 'AVAILABLE'

But creating that config file, either as blank or copying https://gist.github.com/jacaetevha/1719840, doesn't fix it: no error message about the missing file, but still no shell session inside the window. Same behavior for both Terminator 0.97 and 0.98.
Anyone know what I need to do to get Terminator working?

Same error, has anyone found a fix?
Regards

Unable to bind hide_window key, another instance/window has it.
PluginRegistry::load_plugins: Importing plugin init.py failed: 'module' object has no attribute 'AVAILABLE
happened after i installed 'rxvt-unicode-256color' package

No luck. I think it might be time to boneyard terminator if it just gives us a broken install.

We'll accept PRs for this but we're not actively working on it at this time.


remove :: from params

This was causing problems with merge in the Neo4j gem when a class's name included ::.

(And to not nitpick too much, by the way!  Thanks so much for doing this in the first place!)

Coverage decreased (-0.59%) to 95.14% when pulling 79c9382ac28183164c05efdf709c884f5c5193e4 on param_module_cleanup into 2fa37caba534a3bb7851c9ed0f3686b66aab4420 on master.


refactor: drop Node 6 support & upgrade packages

Breaking Change:

[x] refactor: drop Node 6 support

Changes

[x] chore: upgrade dependencies
[x] refactor: remove need for babel transpilling
[x] simplify eslint setting
[x] refactor: remove Bluebird

i'd like the "remove babel transpilation" commit to mention that losing ES5 browser support is a breaking change

Also, the bluebird-killing commit should mention that it's a breaking change that returned promises are no longer Bluebird promises (people might have written code that uses .spread() or whatnot)

Also, the bluebird-killing commit should mention that it's a breaking change that returned promises are no longer Bluebird promises (people might have written code that uses .spread() or whatnot)

actually, scratch this, looks like the lib itself wasn't bluebird-wrapping; we were just using it in the tests

Also, shall we take this major bump occasion to also drop node 8 support?

@dbushong

that losing ES5 browser support

The use case is client tests via testem and PhantomJS?

Also, shall we take this major bump occasion to also drop node 8 support?

sure why not.

The use case is client tests via testem and PhantomJS?

Yeah, that's probably going to be the major stumbling block


About the RMSE unit

First, Thanks yours wonderful research, i have some question about your code, in the test stage, you define the RMSE as pred_rmse = torch.pow(lossVals / counts, 0.5) * 0.3048, but in my opinion, this equation is transformer the unit of feet to the unit of meter, However, in your research, you have change the unit of lossVals to polar coordinate, so I wonder if it is reasonable to directly use the above equation？Thanks

Thanks for your comment and interest in our work. Yes, the formula you refer to, is used to convert from feet to meter. In case of polar coordinates, there are two variables radius (in feet) and angle (in radians). Since a radian represents the ratio of arc length to radius length, it can be considered as a "dimensionless" quantity. Thus, the same formula holds for the polar coordinates case.

Thanks for your comment and interest in our work. Yes, the formula you refer to, is used to convert from feet to meter. In case of polar coordinates, there are two variables radius (in feet) and angle (in radians). Since a radian represents the ratio of arc length to radius length, it can be considered as a "dimensionless" quantity. Thus, the same formula holds for the polar coordinates case.

Thank you for your reply.


[CI] Add Continuous Integration workflow

Hi @cparata
here the workflow to apply codespell and build all example for each Pull Request and on push of the master branch.
Astyle is not applied as there is no source code.
You can take it as an example for other Libraries when yo update them.
I will continue also in my side to deploy when I get some time.
Here the executed actions:
https://github.com/fpistm/X-NUCLEO-IKS01A1/actions

Ok thanks Frederic. I will try to add the same files at the other libraries when I will have time for that.
Best Regards,
Carlo


Move openassetio dependency to extras

What
Remove hard dependency on openassetio and move to an extras
Why
openassetio should always be provided by the host runtime (to ensure we don't have multiple copies loaded simultaneously). Having it as a hard dependency anywhere up the stack causes problems, as pip will try and provision it too, which usually results in a separate static build being installed in addition to whatever the host provides (unless the host is pure python).
ACs

openassetio moved to an extras dep under the runtime name.

Closing in favour of #58


Centered mode doesn't work when views are split in horizontal mode

VSCode Version: 1.21
OS Version: Mac 10.12.16

Steps to Reproduce:

Split editor mode should be in vertical mode
Turn on centered layout with one tab, you should see it is centered
Change split editor mode to horizontal mode
The centered layout will no longer work until you switch back to vertical mode

Does this issue occur when all extensions are disabled?: Yes

Thanks for figuring this out. I spent a while trying to figure out what the problem was. Thank to you, I changed splitting to vertical mode and now centered layout works.
I can affirm that this big is happening to me too. I'm on a mac as well.

@SrTobi I would expect centered mode to work if I have horizontal layout and only one editor. I tried removing the check to simply also enable it for horizontal layout but somehow the layout gets broken in that case.
I plan to fix this in the following week but just to let you know that a PR is more than welcome :)

@isidorn I just let you know that money is more than welcome :smile: Just kidding... I run on fun xD you shall have your PR :) it has the number #45671.
The problem was, that the available size was calculated by using silosSize[Position.ONE] which holds the height and not the width of the editor when in horizontal mode.
As bonus I fixed two typos (one of whom I made myself :smile:)

@SrTobi thanks a lot for your PR, I just merged it in 🍻
I tried it out and it works nicely, also thanks for fixing typos.
For money feel free to apply for our internshipts if you are a student or to our open positions :)

@isidorn :smile: I'll finish university in 4 month... so... I might very well do that xD

@isidorn, which version the fix should be shipped with?


Fixed missing set state path in MorphToSelect

MorphToSelect currently blows up because of the missing state path.

Added fix for the morph type $get selector, needs to be 'thingable.thingable_type', not just 'thingable_type'.  Without this fix, second selector will never show on a new record.

Aaaand ... data isn't submitting, something messing up in getState ... it's returning the array, like ['reportable']['reportable_type'] and ['reportable']['reportable_id'] rather than shifting the individual items up into the main $data state path.
Working on it.

Hmmm.  And, when creating a new record, ONLY the dotted path exists for $get(), when editing a record both paths exist (dotted and not dotted) and when saving, only the non-dotted.  So this is beyond my pay grade, there's something funky going on deep in the guts.

As mentioned on Discord, please explain "blows up if there is no state path"


Describe the bug
For version 1.10.0 :
While docker initialize container, getting create error and we understand after looking the https://docs.chain.link/chainlink-nodes/configuration-variables/#root link we dont need this because parameter has configured as default anyway.
Its tried and no problem.
To Reproduce

Go to ~/.chainlink-goerli and ~/.chainlink location
find ROOT line both .env files
See error while starting node with docker

URLs

in requirements.
configuration reference.

Expected behavior
Explained in describe the bug section
Additional context
No response

Root ENV has been removed from the example config. All of our examples use the default now.
https://github.com/smartcontractkit/documentation/pull/1108


Missing version on Nuget source

Version 11.0.0-a10 is missing on the Nuget source. Do I need to add a custom package source in order to install the latest version?

I just noticed 11.0.0-a10 is in the middle of the versions list. VS versioning may have some bug

11.0.0-a10 doesn't display for me, I think it's missing from NuGet:

Did you search Markdown.Avalonia instead of Markdown.Avalonia.Tight?
For now, I hove not release Markdown.Avalonia and Markdown.Avalonia.SyntaxHigh to wait for AvaloniaEdit released.

What I uploaded above is the version list of Markdown.Avalonia, but Markdown.Avalonia.Tight also doesn't have the a10 version:

What I uploaded above is the version list of Markdown.Avalonia, but Markdown.Avalonia.Tight also doesn't have the a10 version:

It's in the middle of the list, can you scroll down a little bit?

What I uploaded above is the version list of Markdown.Avalonia, but Markdown.Avalonia.Tight also doesn't have the a10 version:

It's in the middle of the list, can you scroll down a little bit?

Indeed, @whistyun sorry for confusion.

Thanks for all your help.
"a10" is hard to see on the list. So I will change version to "b1".


ng test fails with "Error in config file!" for new project using linked angular-cli

I just created a new project to test something but ng test is failing.

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

macOS El Capitan
Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

angular-cli: 1.0.0-beta.26
node: 5.12.0
os: darwin x64
@angular/common: 2.4.4
@angular/compiler: 2.4.4
@angular/core: 2.4.4
@angular/forms: 2.4.4
@angular/http: 2.4.4
@angular/platform-browser: 2.4.4
@angular/platform-browser-dynamic: 2.4.4
@angular/router: 3.4.4
@angular/compiler-cli: 2.4.4

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

ng new test-app
cd test-app
ng test

The log given by the failure.

Normally this include a stack trace and some more information.

23 01 2017 11:37:18.541:ERROR [config]: Error in config file!
 { [TSError: ⨯ Unable to compile TypeScript
<EMAIL_ADDRESS>(46,25): Cannot find name 'Promise'. (2304)
<EMAIL_ADDRESS>(142,43): Property 'assign' does not exist on type 'ObjectConstructor'. (2339)
<EMAIL_ADDRESS>(267,25): Cannot find name 'Promise'. (2304)]
  diagnostics:
   [<EMAIL_ADDRESS>(46,25): Cannot find name \'Promise\'. (2304)',
<EMAIL_ADDRESS>(142,43): Property \'assign\' does not exist on type \'ObjectConstructor\'. (2339)',
<EMAIL_ADDRESS>(267,25): Cannot find name \'Promise\'. (2304)' ] }
TSError: ⨯ Unable to compile TypeScript
<EMAIL_ADDRESS>(46,25): Cannot find name 'Promise'. (2304)
<EMAIL_ADDRESS>(142,43): Property 'assign' does not exist on type 'ObjectConstructor'. (2339)
<EMAIL_ADDRESS>(267,25): Cannot find name 'Promise'. (2304)
    at getOutput (/Users/haurhan/ts/cli-test-app/node_modules/ts-node/src/index.ts:258:17)
    at /Users/haurhan/ts/cli-test-app/node_modules/ts-node/src/index.ts:267:16
    at Object.compile (/Users/haurhan/ts/cli-test-app/node_modules/ts-node/src/index.ts:403:17)
    at loader (/Users/haurhan/ts/cli-test-app/node_modules/ts-node/src/index.ts:289:33)
    at Object.require.extensions.(anonymous function) [as .ts] (/Users/haurhan/ts/cli-test-app/node_modules/ts-node/src/index.ts:306:14)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Function.Module._load.parent [as _load] (/Users/haurhan/ts/angular-cli/lib/bootstrap-local.js:69:24)
    at Module.require (module.js:367:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/haurhan/ts/angular-cli/packages/@ngtools/webpack/src/index.ts:3:1)
    at Module._compile (module.js:413:34)
    at loader (/Users/haurhan/ts/cli-test-app/node_modules/ts-node/src/index.ts:289:14)
    at Object.require.extensions.(anonymous function) [as .ts] (/Users/haurhan/ts/cli-test-app/node_modules/ts-node/src/index.ts:306:14)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Function.Module._load.parent [as _load] (/Users/haurhan/ts/angular-cli/lib/bootstrap-local.js:56:22)
    at Module.require (module.js:367:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/haurhan/ts/angular-cli/packages/angular-cli/models/webpack-build-test.js:5:17)
    at Module._compile (module.js:413:34)
    at Object.Module._extensions..js (module.js:422:10)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Function.Module._load.parent [as _load] (/Users/haurhan/ts/angular-cli/lib/bootstrap-local.js:69:24)
    at Module.require (module.js:367:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/haurhan/ts/angular-cli/packages/angular-cli/plugins/karma.js:4:30)
    at Module._compile (module.js:413:34)
    at Object.Module._extensions..js (module.js:422:10)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Function.Module._load.parent [as _load] (/Users/haurhan/ts/angular-cli/lib/bootstrap-local.js:62:22)
    at Module.require (module.js:367:17)
    at require (internal/module.js:20:19)
    at module.exports (/Users/haurhan/ts/cli-test-app/karma.conf.js:12:7)
    at Object.parseConfig (/Users/haurhan/ts/cli-test-app/node_modules/karma/lib/config.js:342:5)
    at new Server (/Users/haurhan/ts/cli-test-app/node_modules/karma/lib/server.js:56:20)
    at /Users/haurhan/ts/cli-test-app/node_modules/angular-cli/tasks/test.js:32:31
    at Class.exports.default.Task.extend.run (/Users/haurhan/ts/cli-test-app/node_modules/angular-cli/tasks/test.js:15:16)
    at Class.TestCommand.extend.run (/Users/haurhan/ts/cli-test-app/node_modules/angular-cli/commands/test.js:30:25)
    at Class.<anonymous> (/Users/haurhan/ts/cli-test-app/node_modules/angular-cli/ember-cli/lib/models/command.js:147:17)
    at process._tickCallback (internal/process/next_tick.js:103:7)

Mention any other details that might be useful.

Thanks! We'll be in touch soon.

You should have mentioned you're actually using a linked version of angular-cli btw, this doesn't happen on published versions.
It turns out karma auto-registers ts-node: https://github.com/karma-runner/karma/blob/0bec015ede1c04e4d286c1ed2068c294e517364a/lib/config.js#L29
This messes up our dev setup transpiling. Temporary solution is to rm -rf node_modules/ts-node in the generated project. This in turn will mess up your ng e2e :/
Don't really have a solution for this at the moment. Not terribly important since it's a dev-only issue.

Thanks, your solution fixed it for my case since I don't need ng e2e.
Actually I was trying it at first with my local angular-cli linked, when it fails I tried it on a new project with published @latest angular-cli but apparently forgot to unlink. That's why I didn't mention.

Fixed via https://github.com/angular/angular-cli/pull/4997


Results from tiled models in wrong location

With certain combinations of tiled models for certain regions, results from one model are moved to another.  For example, when using the model combination cencal,cca,cvms426 for a large CyberShake region, the point (-125, 40, 0.0) is first set in cencal, but is then reset in cca, which is incorrect.
The cause of this bug is in ucvm_model_plugin.c .  The query code works by assembling all points which have not already been populated into the pointsBuffer.  Then the query is run, and the results are copied back into the data array which was passed into the query function, in lines 246-251.  However, this copy-back code assumes that the points which were queried were contiguous in the data array.  This is not necessarily the case, and if it's not, then points which were already populated by a higher-priority model might be overwritten.
The same bug exists in at least ucvm_model_cvmsi.c , lines 177-180, and may exist in other models as well.
I implemented a fix for cvmsi in 2016, which is to keep track of the mapping between the index in the full data array and the index in the query buffer.  In ucvm_model_cvmsi.c, I added the following at line 151:
int* index_mapping = malloc(sizeof(int)*CVMSI_MAX_POINTS);
if (index_mapping==NULL) {
fprintf(stderr, "Memory allocation of index_mapping failed, aborting.\n");
exit(1);
}
Then, I changed lines 177-180 to:
data[index_mapping[j]].crust.source = ucvm_cvmsi_id;
data[index_mapping[j]].crust.vp = dataBuffer[j].prop.vp;
data[index_mapping[j]].crust.vs = dataBuffer[j].prop.vs;
data[index_mapping[j]].crust.rho = dataBuffer[j].prop.rho;
and lines 202-205 to:
data[index_mapping[j2]].crust.source = ucvm_cvmsi_id;
data[index_mapping[j2]].crust.vp = dataBuffer[j2].prop.vp;
data[index_mapping[j2]].crust.vs = dataBuffer[j2].prop.vs;
data[index_mapping[j2]].crust.rho = dataBuffer[j2].prop.rho;
A similar approach works with ucvm_model_plugin.c to fix the issue.

patched ucvm_model_plugin.c and ucvm_model_cvmsi.c


add pagination

🛠 Issue (Number)

Closes #1674
Description
Added pagination to the front-end side of the project. It is responsive as well
Type of change

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

Checklist:

[x] I have made this from my own
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] The title of my pull request is a short description of the requested changes.

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

Resolve conflicts

resolved @TusharKesarwani

@TusharKesarwani @harshit-paneri @zugzwang03 Kindly merge this pr, works well, if there is some issue, kindly tell


Staff Eng

Federation related document above shows that for a user external to the domain to login using smart card, Admin has to expose a web proxy.  The way I understand this is that user would need to login to windows locally (with SC) and then login to this web proxy using smart card again to gain access to AAD.  Is this correct?  Is there a way to configure windows login to authenticate through web proxy either always or at least while external to the network?  Are there more articles regarding this available?

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

ID: ba868b78-f9a5-ec37-f8fc-f386d7d6c137
Version Independent ID: 02f46536-6674-69cc-18ec-05be500b8baf
Content: Azure AD Connect: User sign-in
Content Source: articles/active-directory/connect/active-directory-aadconnect-user-signin.md
Service: active-directory
GitHub Login: @billmath
Microsoft Alias: billmath

@minhaj-dell Thanks for your feedback! We will investigate and update as appropriate.

@minhaj-dell Which specific section you are talking about ?

@minhaj-dell We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

@Saurabhsharma Ironically The Federation that uses a new or existing farm with AD FS in Windows Server 2012 R2 section. Below I've copied what it says in case you have difficulty finding it!
With federated sign-in, your users can sign in to Azure AD-based services with their on-premises passwords. While they're on the corporate network, they don't even have to enter their passwords. By using the federation option with AD FS, you can deploy a new or existing farm with AD FS in Windows Server 2012 R2. If you choose to specify an existing farm, Azure AD Connect configures the trust between your farm and Azure AD so that your users can sign in.
If you're deploying a new farm, you need:
•A Windows Server 2012 R2 server for the federation server.
•A Windows Server 2012 R2 server for the Web Application Proxy.
•A .pfx file with one SSL certificate for your intended federation service name. For example: fs.contoso.com.
If you're deploying a new farm or using an existing farm, you need:
•Local administrator credentials on your federation servers.
•Local administrator credentials on any workgroup servers (not domain-joined) that you intend to deploy the Web Application Proxy role on.
•The machine that you run the wizard on to be able to connect to any other machines that you want to install AD FS or Web Application Proxy on by using Windows Remote Management.


removeHeader is not removing header

As the title says.
If I use an interceptor to remove headers as suggested, this is not working:
public Response intercept(Chain chain) throws IOException {
    Request request = chain.request()
        .newBuilder().removeHeader("User-Agent").build();
    return chain.proceed(request);
}

With calling a proxy I can see that okhttp adds its own User-Agent (as okhttp/3.10.0).
However setting my own header seems to be working:
public Response intercept(Chain chain) throws IOException {
    Request request = chain.request()
        .newBuilder().addHeader("User-Agent", "test").build();
    return chain.proceed(request);
}

In my case, the server does not accept the call unless I set specific headers (and nothing else). So the header cannot be empty, it must not be present. However it seems to me that there is no way to actually remove headers from the final call (Host, Keep-Alive, Connection, User-Agent seem to be added automatically)?
Any solution for this?

removeHeader("User-Agent") will only work in a network interceptor. Not in an application interceptor.
https://square.github.io/okhttp/features/interceptors/


light/dark theme widget appears right of custom search bar (in wrong spot)

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[X] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
Hello,
In 2.0.0-beta-18, the dark/light theme widget now appears to the right of my search bar, rather than the left:

In previous builds, this widget always appear to the left of the search bar. I assume this is a bug and not a new feature (main docusaurus site doesn't reflect this change).
Reproducible demo
https://codesandbox.io/s/inspiring-surf-81gury
Steps to reproduce

Swizzle and override the searchbar component.
Add the following code:

  {
            type: 'search',
            position: 'right',
    },

...into the docusaurus.config,js file in the navbar items array.

Check that the search field is now left of the dark/light widget.

Expected behavior
I expect the dark/light widget to appear left of the search bar.
Actual behavior
The dark/light widget appears right of the search bar.
Your environment

Public source code:
Public site URL:
Docusaurus version used: 2.0.0-beta-18
Environment name and version: Chrome Version 99.0.4844.84 (Official Build) (x86_64)
Operating system and version (e.g. Ubuntu 20.04.2 LTS):

Self-service

[ ] I'd be willing to fix this bug myself.

Are you sure it's not like that in previous versions? I tried in beta.17 and a few older ones and got the exact same result.
The reason for that is because we render all navbar items declared in themeConfig, then render the rest (color mode toggle and search bar). If search bar is not part of theme config, it will be rendered as an extra item and hence right of the color mode toggle; if it's explicitly declared, it's a normal navbar item and therefore comes before the color mode toggle.
If you want to make it appear on the right anyways, why declare it as navbar item? This API is mostly useful to make it appear on the left instead.
I'll leave this open though, we have TODOs in our code about letting user specify the position of all navbar items, including the mobile sidebar toggle and the color mode toggle. That could solve the confusion here.


fix: failed to build debugtalk.go without go.mod

修改：保留项目plugin目录下的go.mod，仅在第一次初始化go.mod时go get funplugin@latest，减少go mod init、go get 重复下载带来的不必要耗时

Codecov Report

Merging #1325 (f539e2a) into master (036b063) will decrease coverage by 10.21%.
The diff coverage is 30.00%.

@@             Coverage Diff             @@
##           master    #1325       +/-   ##
===========================================
- Coverage   58.68%   48.46%   -10.22%
===========================================
  Files          82       48       -34
  Lines        9868     6516     -3352
===========================================
- Hits         5791     3158     -2633
+ Misses       3801     3076      -725
- Partials      276      282        +6

Flag
Coverage Δ

unittests
48.46% <30.00%> (-10.22%)
:arrow_down:

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

Impacted Files
Coverage Δ

hrp/build.go
57.73% <30.00%> (-1.41%)
:arrow_down:

hrp/boomer.go
68.65% <0.00%> (-14.93%)
:arrow_down:

hrp/step_request.go
48.40% <0.00%> (-0.77%)
:arrow_down:

httprunner/loader_test.py

httprunner/utils_test.py

httprunner/step_sql_request.py

httprunner/make.py

httprunner/utils.py

httprunner/__init__.py

httprunner/client.py

... and 27 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 036b063...f539e2a. Read the comment docs.