text:
Support rewriting gRPC probes

Please provide a description of this PR:
Support rewriting gRPC probes for Kubernetes v1.23
Fix #36314
I'm not very familiar with the integration test, but I've tested it in my local environment, and here's the result:
1. Apply strict mtls:
kubectl apply -f - <<EOF
apiVersion: security.istio.io/v1beta1
kind: PeerAuthentication
metadata:
  name: "default"
  namespace: "istio-system"
spec:
  mtls:
    mode: STRICT
EOF

2. Create a pod with a grpc probe
Before rewriting(an example in k8s doc):
apiVersion: v1
kind: Pod
metadata:
  name: etcd-with-grpc
spec:
  containers:
  - name: etcd
    image: k8s.gcr.io/etcd:3.5.1-0
    command: [ "/usr/local/bin/etcd", "--data-dir",  "/var/lib/etcd", "--listen-client-urls", "http://0.0.0.0:2379", "--advertise-client-urls", "http://127.0.0.1:2379", "--log-level", "debug"]
    ports:
    - containerPort: 2379
    readinessProbe:
      grpc:
        port: 2379
      initialDelaySeconds: 10

After rewriting:
...........
      readinessProbe:
        failureThreshold: 3
        httpGet:
          path: /app-health/etcd/readyz
          port: 15020
          scheme: HTTP
        initialDelaySeconds: 10
        periodSeconds: 10
        successThreshold: 1
        timeoutSeconds: 1
...........
      - name: ISTIO_KUBE_APP_PROBERS
        value: '{"/app-health/etcd/readyz":{"grpc":{"port":2379,"service":""},"timeoutSeconds":1}}'
      image: docker.io/istio/proxyv2:1.12.1
...........

And the container stays ready
[root@new grpc-health]# kubectl get po
NAME             READY   STATUS    RESTARTS   AGE
etcd-with-grpc   2/2     Running   0          5m3s

3. Set rewrite to false and recreate the pod
......
metadata:
  annotations:
    sidecar.istio.io/rewriteAppHTTPProbers: "false"
......

Turns out the probe would not be rewrited:
      readinessProbe:
        failureThreshold: 3
        grpc:
          port: 2379
          service: ""
        initialDelaySeconds: 10
        periodSeconds: 10
        successThreshold: 1
        timeoutSeconds: 1

The container would become unready
[root@new grpc-health]# kubectl get po
NAME                             READY   STATUS    RESTARTS   AGE
etcd-7c7d558878-bv8dd            1/2     Running   0          4m22s

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

Test name
Commit
Details
Required
Rerun command

lint_istio
7cc0f8bd3ed2ee1254c9dfbf4bdbee25ec7b4e72
link
true
/test lint_istio

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

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

Test name
Commit
Details
Required
Rerun command

lint_istio
7cc0f8bd3ed2ee1254c9dfbf4bdbee25ec7b4e72
link
true
/test lint_istio

gencheck_istio
7cc0f8bd3ed2ee1254c9dfbf4bdbee25ec7b4e72
link
true
/test gencheck_istio

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

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

Test name
Commit
Details
Required
Rerun command

gencheck_istio
7cc0f8bd3ed2ee1254c9dfbf4bdbee25ec7b4e72
link
true
/test gencheck_istio

lint_istio
b39a464e6110dc60b9061543b183440e4a509a03
link
true
/test lint_istio

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

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

Test name
Commit
Details
Required
Rerun command

lint_istio
b39a464e6110dc60b9061543b183440e4a509a03
link
true
/test lint_istio

gencheck_istio
b39a464e6110dc60b9061543b183440e4a509a03
link
true
/test gencheck_istio

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

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

Test name
Commit
Details
Required
Rerun command

lint_istio
b39a464e6110dc60b9061543b183440e4a509a03
link
true
/test lint_istio

gencheck_istio
b39a464e6110dc60b9061543b183440e4a509a03
link
true
/test gencheck_istio

unit-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test unit-tests_istio

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

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

Test name
Commit
Details
Required
Rerun command

lint_istio
b39a464e6110dc60b9061543b183440e4a509a03
link
true
/test lint_istio

gencheck_istio
b39a464e6110dc60b9061543b183440e4a509a03
link
true
/test gencheck_istio

unit-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test unit-tests_istio

analyze-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test analyze-tests_istio

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

Cool, i just learned grpc prove has been supported in k8s 1.23

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

Test name
Commit
Details
Required
Rerun command

lint_istio
b39a464e6110dc60b9061543b183440e4a509a03
link
true
/test lint_istio

gencheck_istio
b39a464e6110dc60b9061543b183440e4a509a03
link
true
/test gencheck_istio

unit-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test unit-tests_istio

analyze-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test analyze-tests_istio

release-test_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test release-test_istio

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

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

Test name
Commit
Details
Required
Rerun command

lint_istio
b39a464e6110dc60b9061543b183440e4a509a03
link
true
/test lint_istio

unit-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test unit-tests_istio

analyze-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test analyze-tests_istio

release-test_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test release-test_istio

gencheck_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test gencheck_istio

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

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test unit-tests_istio

analyze-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test analyze-tests_istio

release-test_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test release-test_istio

gencheck_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test gencheck_istio

lint_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test lint_istio

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

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test unit-tests_istio

analyze-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test analyze-tests_istio

release-test_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test release-test_istio

gencheck_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test gencheck_istio

lint_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test lint_istio

integ-telemetry-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-k8s-tests_istio

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

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test unit-tests_istio

analyze-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test analyze-tests_istio

release-test_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test release-test_istio

gencheck_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test gencheck_istio

lint_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test lint_istio

integ-telemetry-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-operator-controller-tests_istio

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

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test unit-tests_istio

analyze-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test analyze-tests_istio

release-test_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test release-test_istio

gencheck_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test gencheck_istio

lint_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test lint_istio

integ-telemetry-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test unit-tests_istio

analyze-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test analyze-tests_istio

release-test_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test release-test_istio

gencheck_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test gencheck_istio

lint_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test lint_istio

integ-telemetry-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-ipv6-k8s-tests_istio

integ-security-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/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.

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test unit-tests_istio

analyze-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test analyze-tests_istio

release-test_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test release-test_istio

gencheck_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test gencheck_istio

lint_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test lint_istio

integ-telemetry-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-ipv6-k8s-tests_istio

integ-security-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-distroless-k8s-tests_istio

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

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test unit-tests_istio

analyze-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test analyze-tests_istio

release-test_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test release-test_istio

gencheck_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test gencheck_istio

lint_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test lint_istio

integ-telemetry-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-ipv6-k8s-tests_istio

integ-security-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/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.

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test unit-tests_istio

analyze-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test analyze-tests_istio

release-test_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test release-test_istio

gencheck_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test gencheck_istio

lint_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test lint_istio

integ-telemetry-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-ipv6-k8s-tests_istio

integ-security-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-pilot-k8s-tests_istio

integ-telemetry-istiodremote-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-istiodremote-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.

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test unit-tests_istio

analyze-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test analyze-tests_istio

release-test_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test release-test_istio

gencheck_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test gencheck_istio

lint_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test lint_istio

integ-telemetry-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-ipv6-k8s-tests_istio

integ-security-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-pilot-k8s-tests_istio

integ-telemetry-istiodremote-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-istiodremote-tests_istio

integ-helm-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-helm-tests_istio

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

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test unit-tests_istio

analyze-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test analyze-tests_istio

release-test_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test release-test_istio

gencheck_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test gencheck_istio

lint_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test lint_istio

integ-telemetry-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-ipv6-k8s-tests_istio

integ-security-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-pilot-k8s-tests_istio

integ-telemetry-istiodremote-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-istiodremote-tests_istio

integ-helm-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-helm-tests_istio

integ-cni-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-cni-k8s-tests_istio

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

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test unit-tests_istio

analyze-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test analyze-tests_istio

release-test_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test release-test_istio

gencheck_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test gencheck_istio

lint_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test lint_istio

integ-telemetry-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-ipv6-k8s-tests_istio

integ-security-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-pilot-k8s-tests_istio

integ-telemetry-istiodremote-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-istiodremote-tests_istio

integ-helm-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-helm-tests_istio

integ-cni-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-cni-k8s-tests_istio

integ-security-istiodremote-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-security-istiodremote-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.

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test unit-tests_istio

analyze-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test analyze-tests_istio

release-test_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test release-test_istio

gencheck_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test gencheck_istio

lint_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test lint_istio

integ-telemetry-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-ipv6-k8s-tests_istio

integ-security-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-pilot-k8s-tests_istio

integ-telemetry-istiodremote-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-istiodremote-tests_istio

integ-helm-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-helm-tests_istio

integ-cni-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-cni-k8s-tests_istio

integ-security-istiodremote-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-security-istiodremote-tests_istio

integ-pilot-istiodremote-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-pilot-istiodremote-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.

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test unit-tests_istio

analyze-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test analyze-tests_istio

release-test_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test release-test_istio

gencheck_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test gencheck_istio

lint_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test lint_istio

integ-telemetry-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-ipv6-k8s-tests_istio

integ-security-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-pilot-k8s-tests_istio

integ-telemetry-istiodremote-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-istiodremote-tests_istio

integ-helm-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-helm-tests_istio

integ-cni-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-cni-k8s-tests_istio

integ-security-istiodremote-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-security-istiodremote-tests_istio

integ-pilot-istiodremote-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-pilot-istiodremote-tests_istio

integ-security-multicluster-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-security-multicluster-tests_istio

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

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test unit-tests_istio

analyze-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test analyze-tests_istio

release-test_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test release-test_istio

gencheck_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test gencheck_istio

lint_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test lint_istio

integ-telemetry-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-ipv6-k8s-tests_istio

integ-security-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-pilot-k8s-tests_istio

integ-telemetry-istiodremote-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-istiodremote-tests_istio

integ-helm-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-helm-tests_istio

integ-cni-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-cni-k8s-tests_istio

integ-security-istiodremote-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-security-istiodremote-tests_istio

integ-pilot-istiodremote-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-pilot-istiodremote-tests_istio

integ-security-multicluster-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-mc-k8s-tests_istio

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

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test unit-tests_istio

analyze-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test analyze-tests_istio

release-test_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test release-test_istio

gencheck_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test gencheck_istio

lint_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test lint_istio

integ-telemetry-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-ipv6-k8s-tests_istio

integ-security-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-pilot-k8s-tests_istio

integ-telemetry-istiodremote-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-istiodremote-tests_istio

integ-helm-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-helm-tests_istio

integ-cni-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-cni-k8s-tests_istio

integ-security-istiodremote-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-security-istiodremote-tests_istio

integ-pilot-istiodremote-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-pilot-istiodremote-tests_istio

integ-security-multicluster-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

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

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test unit-tests_istio

analyze-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test analyze-tests_istio

release-test_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test release-test_istio

gencheck_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test gencheck_istio

lint_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test lint_istio

integ-telemetry-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-ipv6-k8s-tests_istio

integ-security-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-pilot-k8s-tests_istio

integ-telemetry-istiodremote-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-istiodremote-tests_istio

integ-helm-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-helm-tests_istio

integ-cni-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-cni-k8s-tests_istio

integ-security-istiodremote-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-security-istiodremote-tests_istio

integ-pilot-istiodremote-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-pilot-istiodremote-tests_istio

integ-security-multicluster-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
9410b4294201b09875d183fe63123379a1c8a97f
link
true
/test integ-pilot-multicluster-tests_istio

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

@howardjohn Thank you! I've addressed your comments

We will want an integ test for this - we have ones for the other protocols so should be able to expand them for this.

OK, I will take a stab

@hzxuzhonghu Thank you!

There's a problem that the rewrited probe does not work with strict mtls, the agent reports the error:
Failed to create grpc connection to probe app: context deadline exceeded

I'm looking into it, so far have no idea what's going wrong

/test all

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test unit-tests_istio

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

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test unit-tests_istio

lint_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test lint_istio

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

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test unit-tests_istio

lint_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test lint_istio

analyze-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test analyze-tests_istio

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

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test unit-tests_istio

lint_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test lint_istio

analyze-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test analyze-tests_istio

integ-pilot-istiodremote-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-pilot-istiodremote-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.

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test unit-tests_istio

lint_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test lint_istio

analyze-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test analyze-tests_istio

integ-pilot-istiodremote-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-pilot-istiodremote-tests_istio

integ-cni-k8s-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-cni-k8s-tests_istio

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

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test unit-tests_istio

lint_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test lint_istio

analyze-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test analyze-tests_istio

integ-pilot-istiodremote-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-pilot-istiodremote-tests_istio

integ-cni-k8s-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-cni-k8s-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

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

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test unit-tests_istio

lint_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test lint_istio

analyze-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test analyze-tests_istio

integ-pilot-istiodremote-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-pilot-istiodremote-tests_istio

integ-cni-k8s-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-cni-k8s-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-pilot-multicluster-tests_istio

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

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test unit-tests_istio

lint_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test lint_istio

analyze-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test analyze-tests_istio

integ-pilot-istiodremote-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-pilot-istiodremote-tests_istio

integ-cni-k8s-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-cni-k8s-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-pilot-multicluster-tests_istio

integ-pilot-k8s-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/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.

/test integ-pilot-k8s-tests_istio

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test unit-tests_istio

lint_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test lint_istio

analyze-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test analyze-tests_istio

integ-pilot-istiodremote-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-pilot-istiodremote-tests_istio

integ-cni-k8s-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-cni-k8s-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-pilot-multicluster-tests_istio

integ-pilot-k8s-tests_istio
04fe7059892fa169b50c18cc1fd4f658472ff000
link
true
/test integ-pilot-k8s-tests_istio

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

/retest

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

Test name
Commit
Details
Required
Rerun command

integ-cni-k8s-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-cni-k8s-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-pilot-multicluster-tests_istio

integ-pilot-k8s-tests_istio
04fe7059892fa169b50c18cc1fd4f658472ff000
link
true
/test integ-pilot-k8s-tests_istio

integ-pilot-istiodremote-tests_istio
04fe7059892fa169b50c18cc1fd4f658472ff000
link
true
/test integ-pilot-istiodremote-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.

/test integ-pilot-istiodremote-tests_istio

/test integ-pilot-istiodremote-tests_istio

/test integ-pilot-istiodremote-tests_istio

/retest

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

Test name
Commit
Details
Required
Rerun command

integ-cni-k8s-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-cni-k8s-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
7b8006e8ae99bcc20c3fc8d63a8fa8e473deb113
link
true
/test integ-pilot-multicluster-tests_istio

lint_istio
e90373026da1e3a100639d6e5bf1f36394d46aa6
link
true
/test lint_istio

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

/test integ-pilot-istiodremote-tests_istio

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

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-tests_istio
3336d2a09584179fee6dbce3455413084fa83224
link
unknown
/test integ-pilot-istiodremote-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.

authors: dddddai hzxuzhonghu istio-testing


text:
feat: add --revision  flags for istioctl upgrade

Please provide a description of this PR:
Add --revision  flags for istioctl upgrade

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
fa96269684dc4d6d65bc929d9919bb035e3c68b6
link
true
/test release-notes

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.

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
4f41499c4c5d60058b9f0f5ac390818e8bf0f026
link
true
/test release-notes

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.

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
313b7385e6eda48d87b7a9d33ac046000033ab69
link
true
/test release-notes

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.

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

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote_istio
02d74a05c2ab39fd7083696424e4d943642d6933
link
true
/test integ-pilot-istiodremote

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.

/test integ-pilot-istiodremote

source: gharchive/pull-request

repo: istio/istio

license_type: permissive

license_source: github-api


text:
refactor waypoint inbound cluster build

Please provide a description of this PR:

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
5f58600d521b4c174a77a19b081561d5e5de10dc
link
true
/test unit-tests

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.

/test unit-tests

authors: hzxuzhonghu istio-testing


text:
Adding configManager and implementing the higher level Check logic.

This CL introduces a new component, ConfigManager, which is responsible for managing the configuration.
In addition, the higher-level of the check call is implemented: When a request comes in, the Check logic extracts well known serverName and peerId facts, finds the associated ListChecker configurations, obtains adapter instances with the appropriate fact checkers and applies them in sequence.

This change is

PTAL.

Updated the wrong comment and rebased to HEAD. PTAL (and merge? :)

repo: istio/mixer


text:
[DO NOT MERGE] Auto PR to update dependencies of pilot

This PR will be merged automatically once checks are successful.

@istio-testing: Adding do-not-merge/release-note-label-needed because the release note process has not been followed.

One of the following labels is required "release-note", "release-note-action-required", or "release-note-none".
Please see: https://github.com/kubernetes/community/blob/master/contributors/devel/pull-requests.md#write-release-notes-if-needed.
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.

repo: istio/pilot


text:
[DO NOT MERGE] Auto PR to update dependencies of pilot

This PR will be merged automatically once checks are successful.
none

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
62e13437c7ef36f8a3e350093652fceb081fec57
link
/test pilot-presubmit

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.


text:
Possible segfault

From cargo bench connections/hbone -- --profile-time 10
(gdb) bt
#0  0x00007ffff7f9e8ee in ?? () from /lib/x86_64-linux-gnu/libgcc_s.so.1
#1  0x00007ffff7fa064b in _Unwind_Backtrace () from /lib/x86_64-linux-gnu/libgcc_s.so.1
#2  0x0000555555a44eeb in perf_signal_handler ()
#3  <signal handler called>
#4  0x0000555555e03cf0 in ecp_nistz256_ord_mul_mont ()
#5  0x0000000000000212 in ?? ()
#6  0x6f05ab71aa947b60 in ?? ()
#7  0xe8ef83dd782ece3a in ?? ()
#8  0xdda4b5e439a881af in ?? ()
#9  0x0000555555e04a9e in ecp_nistz256_mul_mont ()
#10 0x00007fff7d5e1a70 in ?? ()
#11 0x0000555555dfe020 in ONE ()
#12 0x00007fff7d5e1a10 in ?? ()
#13 0x00007fff7d5e1ab0 in ?? ()
#14 0x00007fff7d5e1ba0 in ?? ()
#15 0x000000000000000a in ?? ()
#16 0x0000555555dd2ec9 in ecp_nistz256_inv0_mod_ord (group=<optimized out>, out=0x7fff7d5e1970, in=<optimized out>) at /boringssl/build/../crypto/fipsmodule/ec/p256-x86_64.c:551
#17 0x0000555555d8fe9c in ec_scalar_inv0_montgomery (group=0x555556144a58, r=0x7fff7d5e1ba0, a=0x7fff7d5e1f20) at /boringssl/build/../crypto/fipsmodule/ec/scalar.c:169
#18 ecdsa_sign_impl (group=<optimized out>, group@entry=0x555556144a58, out_retry=out_retry@entry=0x7fff7d5e1dfc, priv_key=priv_key@entry=0x7fffb8001690, k=<optimized out>,
    k@entry=0x7fff7d5e1f20, digest=<optimized out>,
    digest@entry=0x7fff7d5e2090 "\342\377\f\213(\343\002Y\231\276(\a|\b\357i \374\034 t\303-\201\346틷\224\377\242H\300!^}\377\177", digest_len=digest_len@entry=32)
    at /boringssl/build/../crypto/fipsmodule/ecdsa/ecdsa.c:247
#19 0x0000555555d904f9 in ECDSA_do_sign (digest=0x7fff7d5e2090 "\342\377\f\213(\343\002Y\231\276(\a|\b\357i \374\034 t\303-\201\346틷\224\377\242H\300!^}\377\177", digest_len=32,
    eckey=<optimized out>, eckey@entry=0x7fffb8001538) at /boringssl/build/../crypto/fipsmodule/ecdsa/ecdsa.c:334
#20 0x0000555555e5fd26 in ECDSA_sign (type=<optimized out>, digest=<optimized out>, digest_len=<optimized out>, sig=0x7fffb4026b90 "", sig_len=0x7fff7d5e2024, eckey=0x7fffb8001538)
    at ../crypto/ecdsa_extra/ecdsa_asn1.c:77
#21 0x0000555555e6669c in pkey_ec_sign (ctx=<optimized out>, sig=0x7fffb4026b90 "", siglen=0x7fff7d5e21c0,
    tbs=0x7fff7d5e2090 "\342\377\f\213(\343\002Y\231\276(\a|\b\357i \374\034 t\303-\201\346틷\224\377\242H\300!^}\377\177", tbslen=32) at ../crypto/evp/p_ec.c:131
#22 0x0000555555e63529 in EVP_DigestSignFinal (ctx=0x7fff7d5e2118, out_sig=0x7fffb4026b90 "", out_sig_len=0x7fff7d5e21c0) at ../crypto/evp/digestsign.c:165
#23 0x0000555555edb4a7 in bssl::ssl_private_key_sign (hs=<optimized out>, hs@entry=0x7fffb4047fc8, out=0x7fffb4026b90 "", out_len=out_len@entry=0x7fff7d5e21c0,
    max_out=max_out@entry=72, sigalg=1027, in=...) at ../ssl/ssl_privkey.cc:229
#24 0x0000555555eeedf0 in bssl::tls13_add_certificate_verify (hs=hs@entry=0x7fffb4047fc8) at ../ssl/tls13_both.cc:604
#25 0x0000555555eefa4a in bssl::do_send_client_certificate_verify (hs=0x7fffb4047fc8) at ../ssl/tls13_client.cc:801
#26 bssl::tls13_client_handshake (hs=hs@entry=0x7fffb4047fc8) at ../ssl/tls13_client.cc:904
#27 0x0000555555ec33e3 in bssl::do_tls13 (hs=0x7fffb4047fc8) at ../ssl/handshake_client.cc:791
#28 bssl::ssl_client_handshake (hs=<optimized out>) at ../ssl/handshake_client.cc:1757
#29 0x0000555555ec21e3 in bssl::ssl_run_handshake (hs=0x7fffb4047fc8, out_early_return=out_early_return@entry=0x7fff7d5e27bf) at ../ssl/handshake.cc:726
#30 0x0000555555ed6c13 in SSL_do_handshake (ssl=0x7fffb4046ed8) at ../ssl/ssl_lib.cc:888
#31 0x00005555557a4654 in <tokio_boring::HandshakeFuture<S> as core::future::future::Future>::poll ()
#32 0x0000555555782a48 in ztunnel::proxy::outbound::OutboundConnection::proxy_to::{{closure}} ()
#33 0x0000555555774864 in ztunnel::proxy::socks5::handle::{{closure}}::{{closure}} ()
#34 0x000055555571be72 in tokio::runtime::task::raw::poll ()

I am not 100% sure its a real issue vs some corrupted state I had in my local env, I was doing some wonky things.

Moved off boring, so closing this for now

source: gharchive/issue

repo: istio/ztunnel

license_source: bigquery


text:
Update Arch-Documentation Pics

Update Pics
Pics now Include Draw.IO Diagram

@darenegade Ist der PR noch aktuell? Können wir den mergen?

@lmoesle Ja, ich wollte noch die neuen Bilder hochladen. Hab da noch ein paar. Dann kann man das hier mergen

PR Analysis

🎯 Main theme: Updating documentation pictures
📝 PR summary: This PR is focused on updating the pictures used in the project's architecture documentation. The new pictures include Draw.IO diagrams.
📌 Type of PR: Documentation
🧪 Relevant tests added: No
⏱ Estimated effort to review [1-5]: 1, because the PR is straightforward and only involves updating documentation pictures.
🔒 Security concerns: No

PR Feedback

💡 General suggestions: It would be beneficial to provide a brief description of the changes made in the pictures. This will help reviewers understand the changes more effectively.

 🤖 Code feedback:

How to use
  Instructions

Tag me in a comment '@CodiumAI-Agent' and add one of the following commands:
/review: Request a review of your Pull Request.
/describe: Update the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback.
/ask <QUESTION>: Ask a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.
/add_docs: Generate docstring for new components introduced in the PR.
/generate_labels: Generate labels for the PR based on the PR's contents.
see the tools guide for more details.

To edit any configuration parameter from the configuration.toml, add --config_path=new_value.
For example: /review --pr_reviewer.extra_instructions="focus on the file: ..."
To list the possible configuration parameters, add a /config comment.

authors: CodiumAI-Agent darenegade lmoesle

repo: it-at-m/digiwf-core

license: MIT


text:
repeat achieving the goal multiple times

As a registered logged in user I want to add again to my goals list in my personal cabinet already achieved goal so that I can repeat to achieve the same goal
Acceptance criteria

When registered logged in user checks goal in my goals list in the personal cabinet, this goal becomes unchecked in the popup window again

Assumption and constraints:
The same goal can be in the list of checked and unchecked goals in the personal cabinet.
The same goal can be added to the goals list in the personal cabinet multiply times only if this goal was checked

Not relevant.

authors: rsyvulko sofiya-kozak

repo: ita-social-projects/GreenCity


text:
Aggiornamenti ambiente di produzione ANPR

Nella giornata di domani, dopo le ore 18, non sarà disponibile la porta di dominio ANPR per manutenzione: non funzioneranno le operazioni che richiamano i servizi AE.
Lunedì a partire  dalle ore 18 saranno effettuati gli aggiornamenti relativi alle le mutazioni del nucleo famigliare da utilizzare per:
• ripristinare la residenza nel comune antecedente al subentro (tipo mutazione 6 disponibile sia per il servizio 5001 che 5005)
• comunicare contestualmente alla variazione di residenza (attuale tipo di mutazione 4), il possesso di veicoli e patente da parte dei componenti del nucleo famigliare (tipo mutazione 5 del servizio 5001).

saranno caricate anche le modifiche che permettono di indicare tutti i soggetti di un procedimento in un'unica chiamata 1014 ?

No questa modifica sarà trasferita successivamente

... anche il servizio 5014 (rettifica della data di decorrenza della residenza e del motivo di iscrizione in modalita’ WS) sarà trasferito successivamente in ambiente di subentro?

authors: ATropeano busaster gcarbonin

repo: italia/anpr


text:
Blocco su ANPR

Buongiorno,
Ambiente PRE SUBENTRO
alcuni comuni stanno ricevendo il seguente messaggio da questo pomeriggio
"Aborting...IdSede Attribute inconsistent with IdPostazione (from client)"
potete verificare?
Grazie

@SAlberto potrebbe indicare il comune /fornitore?
Grazie

Buongiorno,
il problema è dovuto al fatto che abbiamo inserito dei controlli sull'esatta corrispondenza tra il Codice Istat presente nel campo IdSede e quello ricavato dai primi 6 caratteri dell'IdPostazione. Risulta che i Comuni che hanno nel codice Istat gli zeri iniziali questi, per alcuni Comune, vengono troncati (ex 018160 viene comunicato nell'IdSede come 18160). Se correggete questo comportamento le richieste andranno a buon fine.

authors: SAlberto gife67 mccalv


text:
Aggiunta icona PagoPA

Esiste già una discussione sul tema che ti interessa, o su un tema simile?

[X] Ho verificato e non esiste

Versione della libreria
2.9.0
Cosa
Salve, sarebbe utile aggiungere il logo PagoPA all'iconset di default, così da rendere più semplice realizzare i bottoni di attivazione di pagamento dei contributi.
Perché
Ci sono loghi per ogni tipo di piattaforma social, ma PagoPA manca. Avere un riferimento built-in aiuterebbe anche a assicurare il rispetto delle linee guida sul branding previste da PagoPA (https://www.pagopa.gov.it/assets/download/pagoPA-brand-guidelines.pdf).
Contesto
No response
Altro
No response

Ciao @lscorcia, grazie per la segnalazione.
Non sarebbe propriamente un'icona... ci ragioneremo nella prossima fase di ricerca, in particolar modo magari rispetto all'utilità di simboli grafici utili all'implementazione di diversi servizi (SPID, PagoPA, CIE, ...).
Daniele T.

@Fupete @lscorcia chiusa in favore di questa https://github.com/italia/bootstrap-italia/issues/1297

authors: Fupete astagi lscorcia

repo: italia/bootstrap-italia


text:
Richiesta aggiornamento metadati Comune di Bari

Buongiorno,
in seguito all'aggiunta di un nuovo ACS, è richiesta la verifica ed aggiornamento dei metadati relativi al Service Provider Comune di Bari.
I metadati sono raggiungibili all'indirizzo: https://www.comune.bari.it/sp/metadata.xml
Grazie.

Il Metadata è stato inoltrato verso gli IdP e da essi caricato.

authors: AntonioGiovanniSchiavone Gianluke

repo: italia/spid


text:
Write legends of lightning post about bitcoin integration & scalability

⚡ Bitcoin Integration & Scalability: Have they used bitcoin/lightning? If so, how many features? How well will this product scale for either local or global adoption?

@luckysori I think this category will be nicely addressed by the design discussions @bonomat and you had around integrating dlc with lightning. Just ensure when writing this post that you address the above mentioned questions as well.

leaving that issue #8 as reference here.


text:
test union of chains with different columns

Closes https://github.com/iterative/dvcx/issues/1202
~Adds a regression test for the bug shown in the above issue which is no longer relevant.~
There is an issue in Clickhouse with out.append(sqlalchemy.cast(sqlalchemy.null(), col.type).label(n))
In order to fix the syntax / fields need to be updated to be Nullable, i.e. :
63f81a59e8fe :) SELECT cast(Null,'Nullable(String)') as name FROM system.databases;

SELECT CAST(NULL, 'Nullable(String)') AS name
FROM system.databases

Query id: 27a1bb4c-8e70-4110-bca5-bd93f2c56adb

   ┌─name─┐
1. │ ᴺᵁᴸᴸ │
2. │ ᴺᵁᴸᴸ │
3. │ ᴺᵁᴸᴸ │
4. │ ᴺᵁᴸᴸ │
5. │ ᴺᵁᴸᴸ │
   └──────┘

5 rows in set. Elapsed: 0.010 sec.

63f81a59e8fe :) SELECT cast(Null,'String') as name FROM system.databases;

SELECT CAST(NULL, 'String') AS name
FROM system.databases

Query id: 4faa70fb-ac15-48c0-a604-140fe53aa36c

Elapsed: 0.006 sec.

Received exception from server (version 24.5.3):
Code: 70. DB::Exception: Received from localhost:9010. DB::Exception: Cannot convert NULL to a non-nullable type: In scope SELECT CAST(NULL, 'String') AS name FROM system.databases. (CANNOT_CONVERT_TYPE)

Call this a failed experiment

repo: iterative/datachain


text:
checks: allow for multi-line code blocks

per https://github.com/iterative/dvc.org/pull/2054#pullrequestreview-558337058

You may disregard these recommendations if you used the Edit on GitHub button from dvc.org to improve a doc in place.

❗ Please read the guidelines in the Contributing to the Documentation list if you make any substantial changes to the documentation or JS engine.
🐛 Please make sure to mention Fix #issue (if applicable) in the description of the PR. This causes GitHub to close it automatically when the PR is merged.
Please choose to allow us to edit your branch when creating the PR.
Thank you for the contribution - we'll try to review it as soon as possible. 🙏

I ran yarn format-all after the prettier config change and this is what happened. Waiting for test app deployment to double check the rendered results... ⌛

I still don't quite understand what does this change exactly mean

@shcheklein per https://prettier.io/docs/en/options.html#prose-wrap this means to "wrap markdown text as-is" (which BTW is the default behavior). So we should rather see why it was "always" before (which means "wrap if it exceeds the print width"). I guess it's about auto-breaking long lines... So perhaps you're right that this might have big implications...

Ivan was right!

authors: jorgeorpinel shcheklein


text:
docs: add missing instruction for MLEM<>DVC workflow

close #120

@alex000kim, please review. Now it should work!


text:
Шестериков Б. В. Лаб. 4 Группа 6312

ФИО: Шестериков Борис
Номер группы: 6312
Номер лабораторной: 4  Номер варианта(при наличии): нет
Краткое описание исходного кода: Я взял часть исходного кода из своей курсовой. Вот ссылка на него: https://github.com/BarMan555/Virtual-Piano.
Краткое описание проделанной работы: Я сделал логирование с помощью loguru. Логирование производится в файл debug.log

логирование в файл в main.py на 20-21 строчках
# Добавляем логирование в файл
logger.add("debug.log", format="{time} - {level} - {message}", level="DEBUG")

Зачтено

repo: itsecd/prog-instruments-labs


text:
Show method / Modal not working

Throws an exception nil found.

I met the same problem, anyone can help?

In order to get help please explain further how you got the issue:

Library version used - please make sure to use the latest version.
How you integrated the library: via Cocoapods / SPM / Carthage?
Steps to reproduce.

Closing for inactivity, let me know if problem still persists - with detailed steps of course.

authors: dpalme3160 eschao itsmeichigo

repo: itsmeichigo/DateTimePicker

license: mit


text:
Added a new Testamonial

Description
Adding a new "Testimonial section" on the homepage
Related Issues*

Fixes #187

Screenshots!
After changes:

Checklist
Replace "[ ]" with "[x]" to mark them as completed.

[x] I have forked the repo and pushed the changes according to contribution guidelines.
[x] I have tested these changes locally.
[x] I have tried to maintain the consistency of the code.
[x] I have tested these changes locally.
[x] I have updated the documentation accordingly.

Contribution guidelines were not followed properly
You do not have to push changes in main branch you just have to opt a branch.
Kindly refer the contribution.md file


text:
investigate/fix gazebo realtime factor

gazebo real time factor starts at ~1.00 when the simulation is started. after some time it slows down to the level of ~0.05. possible causes may be:

unnecessarily big sea world
something related to our usage of gazebo
some problem in gazebo 11 unrelated to us

we need to determine the reason and fix it if possible.

Lets try the pool environment and try to eliminate the first cause

Also what about the cpu usage? Does it start low and go up when rtf drops? Or is it always high?

Could you add your findings as comments under the card?  @eminmeydanoglu @optimistprime21
Did the issue get resolved after transitioning to the pool environment?
What is the average real-time factor of the data we are receiving?
As Sencer Yazici mentioned, how is the CPU usage?
What conclusions have you reached based on your research?
Adding these outputs to the card would help us make better progress.

Some observations

In seabed, rtf is pretty much always low, even at the start.
In pool world, rtf is pretty high and stable.
Couldn't observe the rtf going down with time, at least with the pool world. The cpu usage is around 150 (I don't know what the number represents, check ss) and doesn't seem to go up with time.

authors: eminmeydanoglu ozanhakantunca senceryazici talhabw

repo: itu-auv/auv-software


text:
Fabric 1.19 doesn't start, unplayable

Describe the problem
just reinstalled my minecraft fabric server to change to a new modpack, just get this error and it doesnt even generate the server files like 'config' 'mods' etc
Container definition
docker run -d -v /home/rae/mc-docker:/data \
-e TYPE=FABRIC \
-p 25565:25565 -e EULA=TRUE --name mc itzg/minecraft-server:java17-jdk \
-e VERSION=1.19 \
-e MEMORY=6G \
--restart unless-stopped \
-e FABRIC_LOADER_VERSION=0.14.11

Container logs
user@server:~$ docker logs mc
[init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 3 1000 1000 4096 Dec 18 01:47 /data'
[mc-image-helper] 02:27:47.697 ERROR : 'get' command failed: launchermeta.mojang.com: Temporary failure in name resolution
[init] ERROR: version lookup failed:

oh and when i visit the website its trying to pull from, i just see

The log shows you have a DNS issue
Temporary failure in name resolution

The screenshot also looks like some strange networking issue on your system with invalid HTTPS certificate.

repo: itzg/docker-minecraft-server


text:
Forge 1.16.5 Issue

I just did a fresh pull and tried to start a forge server (1.16.5) with the following docker-compose file:
version: "3.7"

services:
  mc:
    image: itzg/minecraft-server
    restart: unless-stopped
    #network_mode: host
    ports:
    # expose the Minecraft server port outside of container
    - 25565:25565
    #- 24454:24454
    environment:
      # REQUIRED for all types
      EULA: "TRUE"
      # Set server type (vs the default of vanilla)
      TYPE: FORGE
      VERSION: 1.16.5

    volumes:
    # use a named, managed volume for data volume
    - ./data:/data
    # attach local host directory "mods" in same directory as this compose file
    # all mods in this directory get copied into /data/mods at startup
    - ./mods:/mods:ro

This downloads forge and everything is expected, but eventually it just crashes: here is the short log:
[init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 6 1000 1000 4096 Jun 10 03:00 /data'
[init] Resolved version given 1.16.5 into 1.16.5
[init] Resolving type given FORGE
[init] **********************************************************************
[init] WARNING: The image tag itzg/minecraft-server:java8 is recommended
[init]          since some mods require Java 8
[init]          Exception traces reporting ClassCastException: class jdk.internal.loader.ClassLoaders$AppClassLoader
[init]          can be fixed with java8
[init] **********************************************************************
[init] Checking Forge version information.
[init] Copying any mods over...
[init] server.properties already created, skipping
[init] Checking for JSON files.
[init] Setting initial memory to 1G and max to 1G
[init] Starting the Minecraft server...
2021-06-10 03:01:50,417 main WARN Advanced terminal features are not available in this environment
[03:01:50] [main/INFO] [cp.mo.mo.Launcher/MODLAUNCHER]: ModLauncher running: args [--gameDir, ., --launchTarget, fmlserver, --fml.forgeVersion, 36.1.0, --fml.mcpVersion, 20210115.111550, --fml.mcVersion, 1.16.5, --fml.forgeGroup, net.minecraftforge]
[03:01:50] [main/INFO] [cp.mo.mo.Launcher/MODLAUNCHER]: ModLauncher 8.0.9+86+master.3cf110c starting: java version 16.0.1 by AdoptOpenJDK
2021-06-10T03:01:50.558Z	WARN	mc-server-runner	sub-process failed	{"exitCode": 1}
2021-06-10T03:01:50.558Z	INFO	mc-server-runner	Done

Any help you can provide would be appreciated! Thanks!
Note this is on Docker 20.10.2, build 20.10.2-0ubuntu1~20.10.1 running on Pop!_OS 20.10

Try using the Java 8 image itzg/minecraft-server:java8

That did it - I should have paid closer attention.
Thank you for the fast response!

authors: ekiel itzg


text:
When removing a container, confirmation dialog falls under header

I believe adding:
  .modal {
    top: 10%;
  }

To theme.scss -> theme will fix it.

Cool, I was hoping just a CSS offset tweak would do it.

authors: DanTheColoradan itzg

repo: itzg/minecraft-container-yard


text:
Proposal to change subscription administration to prevent missing messaging while not overloading plugin

See comment at other pull request:
https://github.com/iuriaranda/signalk-mqtt-bridge/pull/4#issuecomment-1485344917

Hey @avanlievenoogen , first of all thanks for the contribution.
About your changes, I see two problems:

the initial idea was to have a very flexible subscription mechanism, that mimics how the Venus MQTT integration works (as explained in the README). As of now this mechanism allows users to subscribe to topics like "vessels/self/electrical/batteries/+/current" or "vessels/+/navigation/#", which is not possible at all with the .getBus(topic) method, so we would be loosing an important feature there.
the "delta overload issue" (for lack of a better term) could potentially cause problems in the connection between the plugin and the MQTT broker, rather than in the plugin itself, and it would only occur with the deltas on topics already subscribed, since the non-subscribed deltas won't hit MQTT anyways. And this specific situation is not prevented in the proposed implementation.

As I mentioned in the other PR, I ported the debounceImmediate function in particular from the signalk-mqtt-gw plugin, and I'm not 100% sure that the original intention still applies here. So with that in mind, and considering it's currently doing more harm than good, I'm going to remove the debounceImmediate.
If we then have overload problems, we could add throttling as an option in the plugin configuration page, or find a buffering mechanism to store deltas and send them in batches to MQTT. But I wouldn't waste efforts right now on a problem that might not even exist.

authors: avanlievenoogen iuriaranda

repo: iuriaranda/signalk-mqtt-bridge


text:
Issue with test_adaptative.py

Issue description
Current behavior
I have noticed when running tests locally, test_adaptative.py always fails, while the tests on GitHub are running. @gisellemartel I believe you had this issue as well?
When the tests are run in GitHub, they seem to be running fine. I think the issue might be to do with hdf5 files and read/write issues.
Steps to reproduce
pytest testing/unit_tests/test_adaptative.py

 An example summary message
======================================= FAILURES =======================================
______________________________________ test_hdf5 _______________________________________

    def test_hdf5():
        print('[INFO]: Starting test ... \n')
        train_lst = ['sub-unf01']

        training_transform_dict = {
            "Resample":
                {
                    "wspace": 0.75,
                    "hspace": 0.75
                },
            "CenterCrop":
                {
                    "size": [48, 48]
                },
            "NumpyToTensor": {}
        }
        transform_lst, _ = imed_transforms.prepare_transforms(training_transform_dict)

        roi_params = {"suffix": "_seg-manual", "slice_filter_roi": None}

        bids_to_hdf5 = imed_adaptative.BIDStoHDF5(PATH_BIDS,
                                                    subject_lst=train_lst,
                                                    path_hdf5='testing_data/mytestfile.hdf5',
                                                    target_suffix=["_lesion-manual"],
                                                    roi_params=roi_params,
                                                    contrast_lst=['T1w', 'T2w', 'T2star'],
                                                    metadata_choice="contrast",
                                                    transform=transform_lst,
                                                    contrast_balance={},
                                                    slice_axis=2,
                                                    slice_filter_fn=imed_loader_utils.SliceFilter(filter_empty_input=True,
                                                                                filter_empty_mask=True))

        # Checking architecture
        def print_attrs(name, obj):
            print("\nName of the object: {}".format(name))
            print("Type: {}".format(type(obj)))
            print("Including the following attributes:")
            for key, val in obj.attrs.items():
                print("    %s: %s" % (key, val))

        print('\n[INFO]: HDF5 architecture:')
        with h5py.File(bids_to_hdf5.path_hdf5, "a") as hdf5_file:
            hdf5_file.visititems(print_attrs)
            print('\n[INFO]: HDF5 file successfully generated.')
            print('[INFO]: Generating dataframe ...\n')

            df = imed_adaptative.Dataframe(hdf5_file=hdf5_file,
                                           contrasts=['T1w', 'T2w', 'T2star'],
                                           path='testing_data/hdf5.csv',
                                           target_suffix=['T1w', 'T2w', 'T2star'],
                                           roi_suffix=['T1w', 'T2w', 'T2star'],
                                           dim=2,
                                           filter_slices=True)

            print(df.df)

            print('\n[INFO]: Dataframe successfully generated. ')
            print('[INFO]: Creating dataset ...\n')

            model_params = {
                    "name": "HeMISUnet",
                    "dropout_rate": 0.3,
                    "bn_momentum": 0.9,
                    "depth": 2,
                    "in_channel": 1,
                    "out_channel": 1,
                    "missing_probability": 0.00001,
                    "missing_probability_growth": 0.9,
                    "contrasts": ["T1w", "T2w"],
                    "ram": False,
                    "path_hdf5": 'testing_data/mytestfile.hdf5',
                    "csv_path": 'testing_data/hdf5.csv',
                    "target_lst": ["T2w"],
                    "roi_lst": ["T2w"]
                }
            contrast_params = {
                "contrast_lst": ['T1w', 'T2w', 'T2star'],
                "balance": {}
            }

            dataset = imed_adaptative.HDF5Dataset(root_dir=PATH_BIDS,
                                                  subject_lst=train_lst,
                                                  target_suffix="_lesion-manual",
                                                  slice_axis=2,
                                                  model_params=model_params,
                                                  contrast_params=contrast_params,
                                                  transform=transform_lst,
                                                  metadata_choice=False,
                                                  dim=2,
                                                  slice_filter_fn=imed_loader_utils.SliceFilter(filter_empty_input=True,
                                                                                filter_empty_mask=True),
                                                  roi_params=roi_params)

            dataset.load_into_ram(['T1w', 'T2w', 'T2star'])
            print("Dataset RAM status:")
            print(dataset.status)
            print("In memory Dataframe:")
            print(dataset.dataframe)
            print('\n[INFO]: Test passed successfully. ')

            print("\n[INFO]: Starting loader test ...")

            device = torch.device("cuda:" + str(GPU_NUMBER) if torch.cuda.is_available() else "cpu")
            cuda_available = torch.cuda.is_available()
            if cuda_available:
                torch.cuda.set_device(device)
                print("Using GPU number {}".format(device))

            train_loader = DataLoader(dataset, batch_size=BATCH_SIZE,
                                      shuffle=False, pin_memory=True,
                                      collate_fn=imed_loader_utils.imed_collate,
                                      num_workers=1)

>           for i, batch in enumerate(train_loader):

testing/unit_tests/test_adaptative.py:135:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
env/lib/python3.8/site-packages/torch/utils/data/dataloader.py:345: in __next__
    data = self._next_data()
env/lib/python3.8/site-packages/torch/utils/data/dataloader.py:856: in _next_data
    return self._process_data(data)
env/lib/python3.8/site-packages/torch/utils/data/dataloader.py:881: in _process_data
    data.reraise()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = <torch._utils.ExceptionWrapper object at 0x17cefba30>

    def reraise(self):
        r"""Reraises the wrapped exception in the current thread"""
        # Format a message such as: "Caught ValueError in DataLoader worker
        # process 2. Original Traceback:", followed by the traceback.
        msg = "Caught {} {}.\nOriginal {}".format(
            self.exc_type.__name__, self.where, self.exc_msg)
        if self.exc_type == KeyError:
            # KeyError calls repr() on its argument (usually a dict key). This
            # makes stack traces unreadable. It will not be changed in Python
            # (https://bugs.python.org/issue2651), so we work around it.
            msg = KeyErrorMessage(msg)
>       raise self.exc_type(msg)
E       OSError: Caught OSError in DataLoader worker process 0.
E       Original Traceback (most recent call last):
E         File "/Users/work/Coding/NeuroPoly/ivadomed/env/lib/python3.8/site-packages/torch/utils/data/_utils/worker.py", line 178, in _worker_loop
E           data = fetcher.fetch(index)
E         File "/Users/work/Coding/NeuroPoly/ivadomed/env/lib/python3.8/site-packages/torch/utils/data/_utils/fetch.py", line 44, in fetch
E           data = [self.dataset[idx] for idx in possibly_batched_index]
E         File "/Users/work/Coding/NeuroPoly/ivadomed/env/lib/python3.8/site-packages/torch/utils/data/_utils/fetch.py", line 44, in <listcomp>
E           data = [self.dataset[idx] for idx in possibly_batched_index]
E         File "/Users/work/Coding/NeuroPoly/ivadomed/ivadomed/loader/adaptative.py", line 601, in __getitem__
E           with h5py.File(self.path_hdf5, "r") as f:
E         File "/Users/work/Coding/NeuroPoly/ivadomed/env/lib/python3.8/site-packages/h5py/_hl/files.py", line 406, in __init__
E           fid = make_fid(name, mode, userblock_size,
E         File "/Users/work/Coding/NeuroPoly/ivadomed/env/lib/python3.8/site-packages/h5py/_hl/files.py", line 173, in make_fid
E           fid = h5f.open(name, flags, fapl=fapl)
E         File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
E         File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
E         File "h5py/h5f.pyx", line 88, in h5py.h5f.open
E       OSError: Unable to open file (unable to lock file, errno = 35, error message = 'Resource temporarily unavailable')

env/lib/python3.8/site-packages/torch/_utils.py:395: OSError

Environment
System description
MacOSX (Big Sur)
Radeon Pro 560X 4 GB
16 GB 2400 MHz DDR4
Installed packages
Using Python 3.8

 Output of pip freeze
absl-py==0.11.0
alabaster==0.7.12
anyio==2.0.2
appnope==0.1.2
argon2-cffi==20.1.0
async-generator==1.10
attrs==20.3.0
Babel==2.9.0
backcall==0.2.0
bids-neuropoly==0.2
bids-validator==1.5.8
bleach==3.2.1
cachetools==4.2.0
certifi==2020.12.5
cffi==1.14.4
chardet==4.0.0
click==7.1.2
csv-diff==1.0
cycler==0.10.0
decorator==4.4.2
defusedxml==0.6.0
dictdiffer==0.8.1
docopt==0.6.2
docutils==0.16
entrypoints==0.3
flake8==3.8.4
future==0.18.2
google-auth==1.24.0
google-auth-oauthlib==0.4.2
grpcio==1.34.0
h5py==2.10.0
idna==2.10
imageio==2.9.0
imagesize==1.2.0
iniconfig==1.1.1
ipykernel==5.4.2
ipython==7.19.0
ipython-genutils==0.2.0
ipywidgets==7.6.3
-e git+https://github.com/ivadomed/ivadomed.git@546c023f23f181da6cc5385e6b2074be61d74245#egg=ivadomed
jedi==0.17.0
Jinja2==2.11.2
joblib==1.0.0
json5==0.9.5
jsonschema==3.2.0
jupyter==1.0.0
jupyter-client==6.1.10
jupyter-console==6.2.0
jupyter-core==4.7.0
jupyter-server==1.2.0
jupyterlab==3.0.1
jupyterlab-pygments==0.1.2
jupyterlab-server==2.1.0
jupyterlab-widgets==1.0.0
kiwisolver==1.3.1
Markdown==3.3.3
MarkupSafe==1.1.1
matplotlib==3.3.3
mccabe==0.6.1
mistune==0.8.4
nbclassic==0.2.5
nbclient==0.5.1
nbconvert==6.0.7
nbformat==5.0.8
nest-asyncio==1.4.3
networkx==2.5
nibabel==3.2.1
notebook==6.1.6
num2words==0.5.10
numpy==1.19.5
oauthlib==3.1.0
onnxruntime==1.4.0
packaging==20.8
pandas==1.2.0
pandocfilters==1.4.3
parso==0.8.1
patsy==0.5.1
pexpect==4.8.0
pickleshare==0.7.5
Pillow==8.1.0
pluggy==0.13.1
prometheus-client==0.9.0
prompt-toolkit==3.0.10
protobuf==3.14.0
ptyprocess==0.7.0
py==1.10.0
pyasn1==0.4.8
pyasn1-modules==0.2.8
pybids==0.12.4
pycodestyle==2.6.0
pycparser==2.20
pyflakes==2.2.0
Pygments==2.7.3
pyparsing==2.4.7
pyrsistent==0.17.3
pytest==6.2.1
python-dateutil==2.8.1
pytz==2020.5
PyWavelets==1.1.1
pyzmq==20.0.0
qtconsole==5.0.1
QtPy==1.9.0
requests==2.25.1
requests-oauthlib==1.3.0
rsa==4.6
scikit-image==0.18.1
scikit-learn==0.24.0
scipy==1.6.0
seaborn==0.11.1
Send2Trash==1.5.0
six==1.15.0
sniffio==1.2.0
snowballstemmer==2.0.0
Sphinx==3.4.3
sphinx-rtd-theme==0.5.1
sphinxcontrib-applehelp==1.0.2
sphinxcontrib-devhelp==1.0.2
sphinxcontrib-htmlhelp==1.0.3
sphinxcontrib-jsmath==1.0.1
sphinxcontrib-programoutput==0.16
sphinxcontrib-qthelp==1.0.3
sphinxcontrib-serializinghtml==1.1.4
SQLAlchemy==1.3.22
tensorboard==2.4.0
tensorboard-plugin-wit==1.7.0
terminado==0.9.2
testpath==0.4.4
threadpoolctl==2.1.0
tifffile==2020.12.8
toml==0.10.2
torch==1.5.0
torchvision==0.6.0
tornado==6.1
tqdm==4.55.1
traitlets==5.0.5
urllib3==1.26.2
wcwidth==0.2.5
webencodings==0.5.1
Werkzeug==1.0.1
widgetsnbextension==3.5.1

@ahill187 appears to be the same issue I came across related to h5py and MacOS. I was able to resolve it by changing an env variable in .bashrc (see https://github.com/h5py/h5py/issues/1101) as a workaround.

@ahill187 appears to be the same issue I came across related to h5py and MacOS. I was able to resolve it by changing an env variable in .bashrc (see https://github.com/h5py/h5py/issues/1101) as a workaround.

@ahill187 could you confirm if you managed to address the issue and workaround you used? I think we might be running into similar issues on Yuan's BigSur Mac. We might need to update Doc to address future Mac user/dev on this OS level setting that needs to be addressed.

@ahill187 appears to be the same issue I came across related to h5py and MacOS. I was able to resolve it by changing an env variable in .bashrc (see h5py/h5py#1101) as a workaround.

@ahill187 appears to be the same issue I came across related to h5py and MacOS. I was able to resolve it by changing an env variable in .bashrc (see h5py/h5py#1101) as a workaround.

If the user is using the zsh shell, they need to add an env variable in .zshrc instead of .bashrc

repo: ivadomed/ivadomed


text:
[Feature Request] Choosing different styles for tasks

Fantastic plugin! I'm very grateful!
Suggestion: It would be amazing to have more styling options for my scheduled tasks. Right now, the only customization available is through heading levels, but I'd prefer to format my tasks like this:

>[!Daily tasks]
> - [ ] 8:00 - 8:30 Make coffee
> - [ ] 8:30 - 9:00 Review emails

Could there be a feature to include code in the heading text and offer more flexibility in task formatting?

Hello, @doschroeder,
I think those tasks should already be visible in the planner, since it collects all the tasks in daily notes by default. The heading from the config serves only as a destination point for tasks created with drag-and-drop.

Hello @ivan-lednev,
many thanks for the reply. No, unfortunately not. If I am writing >[!Daily tasks] then it inserts #>[!Daily tasks]

Oh, I see what you meant now. For now, if you want to use a custom section, you can create a daily note template with that > [!Daily tasks]

Yes, this is what it did. But when I insert a new time block in the week planer, it adds a new section. Many thanks for your great work! =)

authors: doschroeder ivan-lednev

repo: ivan-lednev/obsidian-day-planner


text:
「评论」<%- document..title %>

利用清华源安装gcc9.3.0 | Blog of IvisTang：https://www.ivistang.com/articles/336/

你好，请问一下，我按照上面的步骤可以成功安需要的gcc版本，但是系统原来的gcc版本被覆盖了。现在想要恢复到原来的gcc版本该怎么做呢？非常希望能够给与帮助，感谢！

@fyaft2012
你好，请问一下，我按照上面的步骤可以成功安需要的gcc版本，但是系统原来的gcc版本被覆盖了。现在想要恢复到原来的gcc版本该怎么做呢？非常希望能够给与帮助，感谢！原版本是在/usr/bin/里面，新安装的版本是在/usr/local/bin/里面，感谢帮助！

可以考虑用apt或者yum（视系统而定）安装默认版本的gcc、gfortran和g++

你好，请问一下，我按照上面的步骤正确安装了想要的gcc版本。但是我现在想要恢复到系统默认的版本，该怎么做呢？

repo: ivistang/blog-comment


text:
Fix ttgo feature

Without this, a cargo c --features "ttgo" fails with:
error[E0308]: mismatched types
   --> src/main.rs:809:5
    |
768 | ) -> Result<()> {
    |      ---------- expected `std::result::Result<(), anyhow::Error>` because of return type
...
809 |     led_draw(&mut display.cropped(&Rectangle::new(top_left, size)))
    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `anyhow::Error`, found enum `st7789::Error`
    |
    = note: expected enum `std::result::Result<_, anyhow::Error>`
               found enum `std::result::Result<_, st7789::Error<EspError>>`

I included fixes for heltec, kaluga, ...

Sorry for the missing cargo fmt. I should add a git pre-commit hook I guess :\


text:
Proposal: Add color to output

I got forwarded here from Microsoft/TypeScript#6363:

It's currenty hard to read TypeScript errors in VS Code:

There is a --pretty option for TypeScript, but AFAIK it can't be used when using gulp-typescript.
So I'd like to suggest to add color to the output of gulp-typescript.

I'd like to suggest to give colors so the message and code positions can easily be read, too (not just the - rather uninformative - constant word "error", like it is output by tsc when applying the --pretty compiler option):

(Suggested colors are: green for code position, red for error keyword/code and dark yellow for the error message.)

Errors are already colored in gulp-typescript, though it seems VSCode ignores these. I'm not sure why, but you can try to add the --color flag (like gulp --color tscProject).
For a better integration between gulp and VSCode, you could also use a problem matcher, see Using VSCode with gulp-typescript.

You are absolutely right. After giving it another thought today I realized that coloring the errors in the Output panel is a sole task of VS Code's Problem Matcher functionality.
So I amended my corresponding suggestion at Microsoft/vscode#1801 a few minutes ago.

authors: SetTrend ivogabe

repo: ivogabe/gulp-typescript