text:
Simple E2E Tests are flaky

Init failures:
E.g. https://circleci.com/gh/istio/istio/241378
TestSImpleIngress failure:
E.g. https://gubernator.k8s.io/build/istio-prow/logs/e2e-simpleTests/12365

@hklai could you create specific issues (one for each related set of failures) and link them here?

simpleTests has improved after recent fixes.
https://github.com/istio/istio/pull/11408
https://github.com/istio/istio/pull/11356
Filed https://github.com/istio/istio/issues/11480 for the most recent one I found in presubmit, and updated this issue description.

https://circleci.com/gh/istio/istio/331808?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
e2e-simple filed with Too long with no output (exceeded 10m0s).  The last thing it did before that was Running command kubectl -n istio-system rollout status deployments/istio-galley --kubeconfig=

@esnible I had a PR which timed out to record more information as to why these test flakes happen in a 10 minute timeout scenario.  See: https://github.com/istio/istio/pull/10758.  I will reopen the PR on master as the problem continues to persist.

one recent flaky:
https://prow.k8s.io/view/gcs/istio-prow/pr-logs/directory/e2e-simpleTests-master/1701

From ingress-gateway logs, seems cds update fails

2019-06-10T05:17:25.635429Z	info	Envoy proxy is ready
[2019-06-10 05:17:25.887][20][warning][config] [external/envoy/source/common/config/grpc_mux_subscription_impl.cc:73] gRPC config for type.googleapis.com/envoy.api.v2.Cluster rejected: Error adding/updating cluster(s) outbound|80||default-http-backend.kube-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|80||heapster.kube-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|53||kube-dns.kube-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|443||metrics-server.kube-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|44134||tiller-deploy.kube-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8060||istio-citadel.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15014||istio-citadel.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|80||istio-egressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|443||istio-egressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15443||istio-egressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|443||istio-galley.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15014||istio-galley.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|9901||istio-galley.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15020||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|80||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|443||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|31400||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15029||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15030||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15031||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15032||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15443||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15010||istio-pilot.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15011||istio-pilot.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8080||istio-pilot.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15014||istio-pilot.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|443||istio-sidecar-injector.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|9090||prometheus.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8080||echosrv.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8079||echosrv.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8080||echosrv-extrap.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8079||echosrv-extrap.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8088||echosrv-extrap.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8080||fortio-noistio.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8079||fortio-noistio.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem
[2019-06-10 05:17:31.487][20][warning][config] [external/envoy/source/common/config/grpc_mux_subscription_impl.cc:73] gRPC config for type.googleapis.com/envoy.api.v2.Cluster rejected: Error adding/updating cluster(s) outbound|80||default-http-backend.kube-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|80||heapster.kube-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|53||kube-dns.kube-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|443||metrics-server.kube-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|44134||tiller-deploy.kube-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8060||istio-citadel.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15014||istio-citadel.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|80||istio-egressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|443||istio-egressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15443||istio-egressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|443||istio-galley.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15014||istio-galley.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|9901||istio-galley.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15020||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|80||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|443||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|31400||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15029||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15030||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15031||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15032||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15443||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15010||istio-pilot.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15011||istio-pilot.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8080||istio-pilot.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15014||istio-pilot.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|443||istio-sidecar-injector.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|9090||prometheus.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8080||echosrv.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8079||echosrv.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8080||echosrv-extrap.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8079||echosrv-extrap.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8088||echosrv-extrap.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8080||fortio-noistio.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8079||fortio-noistio.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem
[2019-06-10T05:17:39.782Z] "GET / HTTP/1.1" 404 NR "-" "-" 0 0 5 - "10.60.3.1" "Go-http-client/1.1" "527a02b8-1d31-4021-90a0-8c9a3bcefde9" "34.73.168.175" "-" - - 10.60.3.5:80 10.60.3.1:53958 -
[2019-06-10T05:17:40.498Z] "GET /fortio/debug HTTP/1.1" 503 NR "-" "-" 0 0 3 - "10.60.3.1" "fortio.org/fortio-1.3.0-pre" "d2f0fcc6-951f-400b-af68-d5274546c6b7" "34.73.168.175" "-" - - 10.60.3.5:80 10.60.3.1:53962 -
[2019-06-10T05:17:41.637Z] "GET /fortio/debug HTTP/1.1" 503 NR "-" "-" 0 0 0 - "10.142.0.57" "fortio.org/fortio-1.3.0-pre" "e4bf8c3a-8086-49aa-a072-46b8a0e43432" "34.73.168.175" "-" - - 10.60.3.5:80 10.142.0.57:53964 -
[2019-06-10T05:17:42.773Z] "GET /fortio/debug HTTP/1.1" 503 NR "-" "-" 0 0 0 - "10.142.0.57" "fortio.org/fortio-1.3.0-pre" "336a0b94-2b82-4df5-8fa5-477a1dd951c9" "34.73.168.175" "-" - - 10.60.3.5:80 10.142.0.57:53968 -
[2019-06-10T05:17:43.910Z] "GET /fortio/debug HTTP/1.1" 503 NR "-" "-" 0 0 0 - "10.142.0.60" "fortio.org/fortio-1.3.0-pre" "2698d489-ac62-972d-9740-1f63f9cec369" "34.73.168.175" "-" - - 10.60.3.5:80 10.142.0.60:53970 -

@PiotrSikora ,  invalid path error above is because secret files not found ?

pilot logs for istio-ingressgateway-c97f7f6bd-5dl82 at same time

2019-06-10T05:17:25.885615Z	warn	ads	ADS:CDS: ACK ERROR 10.60.3.5:51550 router~10.60.3.5~istio-ingressgateway-c97f7f6bd-5dl82.istio-system~istio-system.svc.cluster.local-4 (istio-ingressgateway-c97f7f6bd-5dl82.istio-system) node:<id:"router~10.60.3.5~istio-ingressgateway-c97f7f6bd-5dl82.istio-system~istio-system.svc.cluster.local" cluster:"istio-ingressgateway" metadata:<fields:<key:"CONFIG_NAMESPACE" value:<string_value:"istio-system" > > fields:<key:"ISTIO_META_INSTANCE_IPS" value:<string_value:"10.60.3.5,10.60.3.5,fe80::6440:8bff:feb2:91eb" > > fields:<key:"ISTIO_PROXY_SHA" value:<string_value:"istio-proxy:542b4fda35046fc9dad5014dbe81f3d5969e63f7" > > fields:<key:"ISTIO_PROXY_VERSION" value:<string_value:"1.1.3" > > fields:<key:"ISTIO_VERSION" value:<string_value:"1.0-dev" > > fields:<key:"POD_NAME" value:<string_value:"istio-ingressgateway-c97f7f6bd-5dl82" > > fields:<key:"ROUTER_MODE" value:<string_value:"sni-dnat" > > fields:<key:"istio" value:<string_value:"sidecar" > > > locality:<region:"us-east1" zone:"us-east1-c" > build_version:"542b4fda35046fc9dad5014dbe81f3d5969e63f7/1.11.0-dev/Clean/RELEASE/BoringSSL" > type_url:"type.googleapis.com/envoy.api.v2.Cluster" response_nonce:"49144a22-4404-4c1e-9d10-a2b17f37ccc9" error_detail:<code:13 message:"Error adding/updating cluster(s) outbound|80||default-http-backend.kube-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|80||heapster.kube-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|53||kube-dns.kube-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|443||metrics-server.kube-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|44134||tiller-deploy.kube-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8060||istio-citadel.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15014||istio-citadel.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|80||istio-egressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|443||istio-egressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15443||istio-egressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|443||istio-galley.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15014||istio-galley.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|9901||istio-galley.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15020||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|80||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|443||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|31400||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15029||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15030||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15031||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15032||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15443||istio-ingressgateway.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15010||istio-pilot.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15011||istio-pilot.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8080||istio-pilot.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|15014||istio-pilot.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|443||istio-sidecar-injector.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|9090||prometheus.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8080||echosrv.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8079||echosrv.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8080||echosrv-extrap.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8079||echosrv-extrap.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8088||echosrv-extrap.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8080||fortio-noistio.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem, outbound|8079||fortio-noistio.istio-system.svc.cluster.local: Invalid path: /etc/certs/cert-chain.pem" >

citadel logs

2019-06-10T05:16:59.762414Z	info	Istio secret for service account "istio-ingressgateway-service-account" in namespace "istio-system" has been created

This test seems to be solid for past few dozen PRs

authors: duderino esnible fpesce hklai quanjielin sdake


text:
patch deprecated field

Signed-off-by: Kuat Yessenov kuat@google.com

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: kyessenov
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ostromart
If they are not already assigned, you can assign the PR to them by writing /assign @ostromart in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/pkg/networking/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kyessenov: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
2c39dc0ea9b2cd65bd396ac77cfad1b03b07deed
link
/test istio-integ-k8s-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.

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

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
2c39dc0ea9b2cd65bd396ac77cfad1b03b07deed
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
2c39dc0ea9b2cd65bd396ac77cfad1b03b07deed
link
/test istio-pilot-multicluster-e2e

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

I'm trying to understand the backwards compatibility implications of this before I merge it

/hold

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
2c39dc0ea9b2cd65bd396ac77cfad1b03b07deed
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
9b0889d3b46b62580ca16776b6c2ff52f3da4c94
link
/test istio-integ-k8s-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.

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

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
9b0889d3b46b62580ca16776b6c2ff52f3da4c94
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
9b0889d3b46b62580ca16776b6c2ff52f3da4c94
link
/test istio-pilot-multicluster-e2e

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.

/lgtm
/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: kyessenov, ostromart
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/pkg/networking/OWNERS [ostromart]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

source: gharchive/pull-request

authors: duderino istio-testing kyessenov ostromart

repo: istio/istio

license_type: permissive

license_source: github-api


text:
Update helloworld sample instructions

Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@frankbu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
ba8ae4be2f2eb5ab691c9bc88a473632a71af8d6
link
/test lint

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.

Rebase in order to fix CI problem.

/retest

authors: frankbu geeknoid howardjohn istio-testing


text:
WIP create generic webhook config controller for istiod and operator

Galley's webhook config controller hasn't aged well. This PR adds a standalone controller implementation that can eventually be shared between Galley, istiod, and the operator.
The current controller will defer to the legacy galley controller if the galley deployment is detected.

@ayj: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_istio
f956601b90aeb349d305f612d38546ad75af3ebc
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
f956601b90aeb349d305f612d38546ad75af3ebc
link
/test gencheck_istio

lint_istio
f956601b90aeb349d305f612d38546ad75af3ebc
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
f956601b90aeb349d305f612d38546ad75af3ebc
link
/test gencheck_istio

lint_istio
f956601b90aeb349d305f612d38546ad75af3ebc
link
/test lint_istio

unit-tests_istio
f956601b90aeb349d305f612d38546ad75af3ebc
link
/test unit-tests_istio

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

authors: ayj istio-testing


text:
test framework: cleanup pilot component

Follow up to https://github.com/istio/istio/pull/25655 to fully remove pilot component from test framework
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[X] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

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

Test name
Commit
Details
Rerun command

release-notes_istio
2d171be580badc7055b8e02b5d6b6b8c53463f6f
link
/test release-notes_istio

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

/test release-notes_istio

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

Test name
Commit
Details
Rerun command

release-notes_istio
2d171be580badc7055b8e02b5d6b6b8c53463f6f
link
/test release-notes_istio

lint_istio
2d171be580badc7055b8e02b5d6b6b8c53463f6f
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
ef50ad0984c2a934fdc633d8c3345edd6967889f
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
ef50ad0984c2a934fdc633d8c3345edd6967889f
link
/test lint_istio

gencheck_istio
ef50ad0984c2a934fdc633d8c3345edd6967889f
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
23a8c1751eec0ebfd977a010288fd483d5f75d4d
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
23a8c1751eec0ebfd977a010288fd483d5f75d4d
link
/test unit-tests_istio

integ-multicluster-k8s-tests_istio
23a8c1751eec0ebfd977a010288fd483d5f75d4d
link
/test integ-multicluster-k8s-tests_istio

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

/retest

@stevenctl: PR needs rebase.

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

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

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-galley-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-telemetry-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-telemetry-k8s-tests_istio

lint_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-telemetry-k8s-tests_istio

lint_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test lint_istio

gencheck_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-telemetry-k8s-tests_istio

lint_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test lint_istio

gencheck_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test gencheck_istio

integ-security-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-security-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-telemetry-k8s-tests_istio

lint_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test lint_istio

gencheck_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test gencheck_istio

integ-security-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-telemetry-k8s-tests_istio

lint_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test lint_istio

gencheck_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test gencheck_istio

integ-security-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-pilot-k8s-tests_istio

integ-ipv6-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-telemetry-k8s-tests_istio

lint_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test lint_istio

gencheck_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test gencheck_istio

integ-security-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-pilot-k8s-tests_istio

integ-ipv6-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-ipv6-k8s-tests_istio

integ-mixer-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-mixer-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-telemetry-k8s-tests_istio

lint_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test lint_istio

gencheck_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test gencheck_istio

integ-security-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-pilot-k8s-tests_istio

integ-ipv6-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-ipv6-k8s-tests_istio

integ-mixer-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-mixer-k8s-tests_istio

unit-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test unit-tests_istio

release-test_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test release-test_istio

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

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

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-telemetry-k8s-tests_istio

lint_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test lint_istio

gencheck_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test gencheck_istio

integ-security-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-pilot-k8s-tests_istio

integ-ipv6-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-ipv6-k8s-tests_istio

integ-mixer-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-mixer-k8s-tests_istio

unit-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test unit-tests_istio

release-test_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test release-test_istio

integ-distroless-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-distroless-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-telemetry-k8s-tests_istio

lint_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test lint_istio

gencheck_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test gencheck_istio

integ-security-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-pilot-k8s-tests_istio

integ-ipv6-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-ipv6-k8s-tests_istio

integ-mixer-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-mixer-k8s-tests_istio

unit-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test unit-tests_istio

release-test_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test release-test_istio

integ-distroless-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-distroless-k8s-tests_istio

integ-operator-controller-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-operator-controller-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-telemetry-k8s-tests_istio

lint_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test lint_istio

gencheck_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test gencheck_istio

integ-security-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-pilot-k8s-tests_istio

integ-ipv6-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-ipv6-k8s-tests_istio

integ-mixer-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-mixer-k8s-tests_istio

unit-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test unit-tests_istio

release-test_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test release-test_istio

integ-distroless-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-distroless-k8s-tests_istio

integ-operator-controller-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-operator-controller-tests_istio

release-notes_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-multicluster-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-telemetry-k8s-tests_istio

gencheck_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test gencheck_istio

integ-security-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-pilot-k8s-tests_istio

integ-ipv6-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-ipv6-k8s-tests_istio

integ-mixer-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-mixer-k8s-tests_istio

unit-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test unit-tests_istio

release-test_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test release-test_istio

integ-distroless-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-distroless-k8s-tests_istio

integ-operator-controller-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-multicluster-k8s-tests_istio

lint_istio
fae46f281b4f2c492c1218006620eeac325e719a
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-pilot-k8s-tests_istio

integ-ipv6-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-ipv6-k8s-tests_istio

integ-mixer-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-mixer-k8s-tests_istio

unit-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test unit-tests_istio

release-test_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test release-test_istio

integ-distroless-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-distroless-k8s-tests_istio

integ-operator-controller-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-multicluster-k8s-tests_istio

lint_istio
fae46f281b4f2c492c1218006620eeac325e719a
link
/test lint_istio

gencheck_istio
fae46f281b4f2c492c1218006620eeac325e719a
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-security-k8s-tests_istio

integ-mixer-k8s-tests_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test integ-mixer-k8s-tests_istio

release-test_istio
75f5c09b8cdfd84db6e959e492952703c37e73e7
link
/test release-test_istio

lint_istio
fae46f281b4f2c492c1218006620eeac325e719a
link
/test lint_istio

gencheck_istio
fae46f281b4f2c492c1218006620eeac325e719a
link
/test gencheck_istio

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

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

authors: istio-testing stevenctl


text:
[release-1.9] Fix istioctl install IOP ns error

This is an automated cherry-pick of #31518

@googlebot I consent.

@googlebot I consent

@kebe7jun Thanks. will merge this after 1.9.2 is released.

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

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio_release-1.9
0b7c47fe6f5cbb910411531e1d6705d8ce1fe83d
link
/test integ-security-multicluster-tests_istio_release-1.9

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-security-multicluster-tests_istio_release-1.9

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

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio_release-1.9
0b7c47fe6f5cbb910411531e1d6705d8ce1fe83d
link
/test integ-security-multicluster-tests_istio_release-1.9

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-security-multicluster-tests_istio_release-1.9

cc @kebe7jun We neeed your consent for this PR

@googlebot I consent.

cc @kebe7jun We neeed your consent for this PR

I have done that but it doesn't seem to work. What's the matter?

@googlebot I consent

@shamsher31 This PR is still not merged, I am not sure what is wrong, do you need to deal with it manually?

@stevenctl can you please help to resolve CLA issue?


text:
Update BASE_VERSION to 1.12.2-2022-01-15T19-01-29

@istio-testing: 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-cni-k8s-tests_istio_release-1.12
be3a8e6c6a9e1ce248651931796fc94b1bdc40c2
link
true
/test integ-cni-k8s-tests_istio_release-1.12

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-cni-k8s-tests_istio_release-1.12

@istio-testing: 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-cni-k8s-tests_istio_release-1.12
be3a8e6c6a9e1ce248651931796fc94b1bdc40c2
link
true
/test integ-cni-k8s-tests_istio_release-1.12

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.

closing in favor of https://github.com/istio/istio/pull/36857

authors: dgn istio-testing zirain


text:
EnvoyFilter is also applied to HTTP Proxy Listener

The function patchOneListener, that applies the EnvoyFilter patches in the listener, is called in buildHTTPProxyListener(). However, the envoyFilterWrapper is only populated in the patchListener(), so the call to patchOneListener in buildHTTPProxyListener() do not apply any changes to the listener created for the HTTP Proxy.
So, to fix this bug, the patchOneListener for the HTTP Proxy listener moved to inside the patchListener(), where the other listener are patched. A new test were added to ensure that the listener are indeed removed.
Closes #38673

Hi @alandiegosantos. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

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.

@alandiegosantos: 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
ea4861b00fe85e0748dacdd574c281b889cea9f7
link
true
/test release-notes_istio

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

/release-notes-none

@zirain Could you add the release-notes-none label in the pull request? I do not think I have permissions to do it.

/retest


text:
integration tests for sidecar egress tls origination

Signed-off-by: Faseela K faseela.k@est.tech
This PR adds integration tests for the sidecar egress TLS termination feature using credentialName support
in DestinationRule.
Documentation can be found at: https://istio.io/latest/docs/tasks/traffic-management/egress/egress-tls-origination/#mutual-tls-origination-for-egress-traffic

@kfaseela: 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

release-notes_istio
28ad6a33a12c1e2dc23b2b7b7eacc4deb1480563
link
true
/test release-notes

lint_istio
28ad6a33a12c1e2dc23b2b7b7eacc4deb1480563
link
true
/test lint

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.

@kfaseela: 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

release-notes_istio
28ad6a33a12c1e2dc23b2b7b7eacc4deb1480563
link
true
/test release-notes

lint_istio
28ad6a33a12c1e2dc23b2b7b7eacc4deb1480563
link
true
/test lint

gencheck_istio
28ad6a33a12c1e2dc23b2b7b7eacc4deb1480563
link
true
/test gencheck

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.

@kfaseela: 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-telemetry-mc_istio
5992c8a8652ef2852c1f7afb4f3df5f99cb25515
link
true
/test integ-telemetry-mc

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-telemetry-mc

authors: istio-testing kfaseela


text:
Add a Helm chart for remote Kubernetes clusters

This Helm chart enables remote Kubernetes clusters running envoy
to discover and communicate with Pilot and Mixer.  --set must
be used to override the pilotIp and mixerIp.  This work will be
iterated upon prior to 1.0 to remove the various problems that
reviewers may see with specifying a static IP that could potentially
change on a pilot or mixer pod restart.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: greghanson
Assign the PR to them by writing /assign @greghanson in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/assign @greghanson

@sdake: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-v1alpha3.sh
a3d8b404c07b3b71538b4845b860019596e46ecf
link
/test istio-pilot-e2e-v1alpha3

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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-v1alpha3.sh
a3d8b404c07b3b71538b4845b860019596e46ecf
link
/test istio-pilot-e2e-v1alpha3

prow/istio-pilot-e2e.sh
a3d8b404c07b3b71538b4845b860019596e46ecf
link
/test istio-pilot-e2e

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.

Thanks @sdake /lgtm

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: linsun
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS [linsun]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

authors: istio-testing linsun sdake


text:
Update proxy SHA.

Update SHA to afde635a247835e58447e1a7eab65632e00bb9c2

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: hklai
If they are not already assigned, you can assign the PR to them by writing /assign @hklai in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@JimmyCYJ: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
398c30e358deeae643b9e9cd28d040892ab2b354
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
398c30e358deeae643b9e9cd28d040892ab2b354
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/istio-pilot-multicluster-e2e.sh
398c30e358deeae643b9e9cd28d040892ab2b354
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
dcb2260d45697a324ac4d48ca9c1d5f696b5c8a3
link
/test istio-pilot-e2e-envoyv2-v1alpha3

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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
dcb2260d45697a324ac4d48ca9c1d5f696b5c8a3
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
dcb2260d45697a324ac4d48ca9c1d5f696b5c8a3
link
/test istio-pilot-multicluster-e2e

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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
dcb2260d45697a324ac4d48ca9c1d5f696b5c8a3
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
dcb2260d45697a324ac4d48ca9c1d5f696b5c8a3
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
93e04c40fffb837d74942748641b59b6a9a1ef32
link
/test istio-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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
93e04c40fffb837d74942748641b59b6a9a1ef32
link
/test istio-unit-tests

prow/e2e-mixer-no_auth-mcp.sh
93e04c40fffb837d74942748641b59b6a9a1ef32
link
/test e2e-mixer-no_auth-mcp

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 istio-pilot-e2e-envoyv2-v1alpha3
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

/test istio-pilot-e2e-envoyv2-v1alpha3
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

@JimmyCYJ: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
b0577e213d9b392ad5512c2ea369d9fcea08f8e4
link
/test istio-pilot-e2e-envoyv2-v1alpha3

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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
b0577e213d9b392ad5512c2ea369d9fcea08f8e4
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
0615549f10d867fd2ceac757805b6ae215602cca
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
0615549f10d867fd2ceac757805b6ae215602cca
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0615549f10d867fd2ceac757805b6ae215602cca
link
/test istio-pilot-e2e-envoyv2-v1alpha3

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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
0615549f10d867fd2ceac757805b6ae215602cca
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0615549f10d867fd2ceac757805b6ae215602cca
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
0615549f10d867fd2ceac757805b6ae215602cca
link
/test istio-pilot-multicluster-e2e

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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
0615549f10d867fd2ceac757805b6ae215602cca
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0615549f10d867fd2ceac757805b6ae215602cca
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
0615549f10d867fd2ceac757805b6ae215602cca
link
/test istio-pilot-multicluster-e2e

prow/e2e-mixer-no_auth-mcp.sh
0615549f10d867fd2ceac757805b6ae215602cca
link
/test e2e-mixer-no_auth-mcp

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.

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

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth-mcp.sh
0615549f10d867fd2ceac757805b6ae215602cca
link
/test e2e-mixer-no_auth-mcp

prow/istio-pilot-multicluster-e2e.sh
356fca7f7ca4c1d60d9172e501434f442095a073
link
/test istio-pilot-multicluster-e2e

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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
356fca7f7ca4c1d60d9172e501434f442095a073
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
829f6858ba441f1437e6f43b105e8c390bfb4a2e
link
/test istio-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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
356fca7f7ca4c1d60d9172e501434f442095a073
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
829f6858ba441f1437e6f43b105e8c390bfb4a2e
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
829f6858ba441f1437e6f43b105e8c390bfb4a2e
link
/test istio-pilot-e2e-envoyv2-v1alpha3

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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
356fca7f7ca4c1d60d9172e501434f442095a073
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
829f6858ba441f1437e6f43b105e8c390bfb4a2e
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
829f6858ba441f1437e6f43b105e8c390bfb4a2e
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
829f6858ba441f1437e6f43b105e8c390bfb4a2e
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
829f6858ba441f1437e6f43b105e8c390bfb4a2e
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
829f6858ba441f1437e6f43b105e8c390bfb4a2e
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
829f6858ba441f1437e6f43b105e8c390bfb4a2e
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/istio-pilot-multicluster-e2e.sh
829f6858ba441f1437e6f43b105e8c390bfb4a2e
link
/test istio-pilot-multicluster-e2e

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: JimmyCYJ istio-testing


text:
Update the binary version to 1.4.4

Update the binary version to 1.4.4
$ mesh version
version.BuildInfo{Version:"1.4.4", GitRevision:"unknown", GolangVersion:"go1.13.4", BuildStatus:"unknown", GitTag:"unknown"}

/retest

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

Test name
Commit
Details
Rerun command

test_operator_release-1.4
35229f8c20c946642561dcbd0f98e1f81c26a836
link
/test test_operator_release-1.4

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

I will approve but re-iterate my stance that this is the wrong way to handle versioning

@howardjohn Now the binary will also read version from BuildInfo, if there is one it will override the hardcoded one.

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

Test name
Commit
Details
Rerun command

test_operator_release-1.4
35229f8c20c946642561dcbd0f98e1f81c26a836
link
/test test_operator_release-1.4

mandiff_operator_release-1.4
b7994fced5bc1fdc3e0b99380e5234f740905685
link
/test mandiff_operator_release-1.4

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.

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

Test name
Commit
Details
Rerun command

mandiff_operator_release-1.4
b7994fced5bc1fdc3e0b99380e5234f740905685
link
/test mandiff_operator_release-1.4

test_operator_release-1.4
b7994fced5bc1fdc3e0b99380e5234f740905685
link
/test test_operator_release-1.4

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.

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

Test name
Commit
Details
Rerun command

test_operator_release-1.4
b7994fced5bc1fdc3e0b99380e5234f740905685
link
/test test_operator_release-1.4

mandiff_operator_release-1.4
5f47e9786fa4387646790bea7c346c4fb9d06874
link
/test mandiff_operator_release-1.4

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: elfinhe istio-testing

repo: istio/operator

license_source: bigquery


text:
✨ 用户退出登录，之前的token，不可以再被使用

项目
至轻云大数据创新团队
需求内容
标题即是需求内容

目前身份认证使用jwt作为token
存在用户退出登录后token 依旧生效的问题
需要将token存到数据库，每次都判断一下token 是否生效   token为主键，查询token则可用，查不到则不可用

source: gharchive/issue

repo: isxcode/spark-yun


text:
TL-9: Wiedervorlage | Cypress

Umsetzung von Testfall als Cypress Test
https://confluence.muenchen.de/display/MPdZ/Test-Dokumentation#TestDokumentation-TL-9:Wiedervorlage
Akzeptanzkriterien

Testfall komplett automatisiert
Test läuft lokal & in der Pipe

Testfälle werden mit #1395 überarbeitet und bei Bedarf neu erstellt

authors: darenegade simonhir

repo: it-at-m/digiwf-core

license: MIT


text:
placed blocks stats

place_block i think, why even that doesn't added?
And please as i requested for mine_block add option for all blocks there

Even though Minecraft doesn't keep track of place_block as its own category, it is being tracked - it's part of use_item, so you can look it up that way.
If you do "use_item stone", for example, that will tell you the amount of stone you placed.

repo: itHotL/PlayerStats


text:
Dockerise the application by adding a docker file

Creating a Dockerfile to containerise the application.
while running docker image, it should accept one variable (-e ) that will serve as environment variable for API_KEY .
example:
docker run -e API_KEY = <API_KEY> <image_name>

Hi, can you please assign this issue to me?

Hi @Badrri-Narayanan , can you please create a pull request by forking?


text:
[R002] request timed out

Tentando di ottenere l'estratto per copia integrale, il servizio va in timeout (10 secondi).
Di seguito il payload della richiesta:
{
"idAnsc": "2023-1112770-2-108028",
"idEvento": "1112770",
"richiedente": {
"codiceFiscale": "GROMTN86D46G999I",
"cognome": "GORI",
"nome": "MARTINA",
"sesso": "F",
"dataNascita": "1986-04-06",
"idComuneNascita": "7631",
"nomeComuneNascita": "PRATO",
"idProvinciaNascita": "48",
"siglaProvinciaNascita": "FI",
"idStatoNascita": "90",
"nomeStatoNascita": "ITALIA",
"idComuneResidenza": "7630",
"nomeComuneResidenza": "PRATO",
"idProvinciaResidenza": "100",
"siglaProvinciaResidenza": "PO",
"idStatoResidenza": "90",
"nomeStatoResidenza": "ITALIA",
"indirizzoResidenza": "",
"idNazionalita": "90",
"nazionalita": "ITALIANA"
},
"intestatario": {
"id": "2212336"
},
"idTipoCertificato": "3",
"conPaternitaMaternita": false,
"testataRichiesta": {
"idComune": 5000,
"idOperazioneComune": "4338",
"dataOraRichiesta": "2023-09-25T17:03:50.293+02:00",
"nomeApplicativo": "urbi",
"versioneApplicativo": "0.1.0",
"fornitoreApplicativo": "padigitale"
}
}

Buongiorno @biadanpad
Abbiamo preso in carico la sua segnalazione.
Cordiali Saluti.
Supporto ANSC.

Salve @biadanpad
Il problema dovrebbe essere rientrato. Potrebbe verificare?
Nel caso le chiediamo di chiudere la issue.
Cordiali Saluti.
Supporto ANSC.

Il problema sembra essere risolto

authors: amusarra biadanpad

repo: italia/ansc


text:
Connection warnings without any effect

I do see this warning in the maker logs, but it appears the taker is actually still connected to the maker:
2021-11-04 18:55:48  WARN Maker was unable to negotiate a new connection: early eof

more logs:
2021-11-04 18:55:06  INFO POST /api/cfd/e0d42219-f50b-4e08-adde-6bfd1a82d3be/acceptOrder:
2021-11-04 18:55:06 DEBUG Maker accepts an order order_id=e0d42219-f50b-4e08-adde-6bfd1a82d3be
2021-11-04 18:55:06  INFO Exchanged setup parameters
2021-11-04 18:55:09  INFO Created CFD transactions
2021-11-04 18:55:09  INFO Exchanged CFD transactions
2021-11-04 18:55:23  INFO Verified all signatures
2021-11-04 18:55:35  INFO Exchanged signed lock transaction
2021-11-04 18:55:35  INFO Lock transaction published with txid 85333d7fc67853400ca2c17a0aa11a76c8e8f90c78a2f2cd36a426d344de2b8e
2021-11-04 18:55:39  INFO New taker 186660d2-7d17-4aa4-baef-e9be63ece289 connected on 45.148.10.241:46612
2021-11-04 18:55:48  WARN Maker was unable to negotiate a new connection: early eof
2021-11-04 18:56:03 DEBUG Bitcoin transaction status changed txid=85333d7fc67853400ca2c17a0aa11a76c8e8f90c78a2f2cd36a426d344de2b8e new_status=in mempool old_status=unseen
2021-11-04 18:57:43 DEBUG Got notification for new block block_height=2102514

In the taker there is no warning / error:
2021-11-04 18:55:00  INFO POST /api/cfd/order text/plain:
2021-11-04 18:55:00  INFO Taking current order: Order { id: OrderId(Hyphenated(e0d42219-f50b-4e08-adde-6bfd1a82d3be)), trading_pair: BtcUsd, position: Short, price: Price(62711.4), min_quantity: Usd(10), max_quantity: Usd(100), leverage: Leverage(2), liquidation_price: Price(41807.6), creation_timestamp: Timestamp(1636012497), settlement_time_interval_hours: Duration { seconds: 86400, nanoseconds: 0 }, origin: Theirs, oracle_event_id: BitMexPriceEventId { timestamp: OffsetDateTime { utc_datetime: PrimitiveDateTime { date: Date { year: 2021, ordinal: 309 }, time: Time { hour: 8, minute: 0, second: 0, nanosecond: 0 } }, offset: UtcOffset { hours: 0, minutes: 0, seconds: 0 } }, digits: 20 } }
2021-11-04 18:55:06  INFO Order got accepted order_id=e0d42219-f50b-4e08-adde-6bfd1a82d3be
2021-11-04 18:55:06  INFO Exchanged setup parameters
2021-11-04 18:55:09  INFO Created CFD transactions
2021-11-04 18:55:09  INFO Exchanged CFD transactions
2021-11-04 18:55:23  INFO Verified all signatures
2021-11-04 18:55:46  INFO Exchanged signed lock transaction
2021-11-04 18:55:46  INFO Setup complete, publishing on chain now
2021-11-04 18:55:46  INFO Lock transaction published with txid 85333d7fc67853400ca2c17a0aa11a76c8e8f90c78a2f2cd36a426d344de2b8e
2021-11-04 18:56:06 DEBUG Found relevant Bitcoin transaction txid=85333d7fc67853400ca2c17a0aa11a76c8e8f90c78a2f2cd36a426d344de2b8e status=in mempool
2021-11-04 18:57:46 DEBUG Got notification for new block block_height=2102514

I find the warning confusing, is that expected behaviour?

@rishflab is this expected behavior?

Likely outdated.

authors: da-kami thomaseizinger

repo: itchysats/itchysats


text:
Allow running taker with limited functionality without the maker online

Some functions should be still possible when the user cannot connect to the maker.
For example:

withdrawing funds,
checking the status of the open/closed CFDs,
closing a CFD

The UI should clearly indicate that only a subset of normal actions is possible and that there is no connection to the maker.

I think at least withdrawing funds should be doable without the need of connecting to a maker for the Umbrel milestone already.
Since we cannot easily "detach" that feature and want it in the UI - see #608 - I think this ticket needs to be on the milestone. I added it. @scratchscratchscratchy @itchymax

authors: da-kami klochowicz


text:
Performance improvements for projection

Instead of rehydrating all CFDs whenever any CFD or the quote changes we now:

Only rehydrate the specific CFD whenever it changes
Keep the hydrated CFD around (this is basically an in-memory persistent read model)
Only apply the new quote to the CFDs whenever the quote changes

As a follow-up, we can eventually take apart the projection::Cfd struct into two structs:

The aggregate hydrated from all events
The struct that is actually serialized over the wire

bors r+


text:
iTeaTime(技术清谈)【000期】【代号：技术清谈简介】

iTeaTime(技术清谈)【000期】【代号：技术清谈】

i组织来源
英文名：iTeaTime
中文名：技术清谈/i组织来源
i组织来源：最初来自“iOS开发-多线程交流”的微信群，最后演变为“iTeaTime(技术清谈)”群，此群500人已满，不再加人。
往期清谈汇总

《技术清谈--已发布，附带答案》
《技术清谈--未发布，不一定附带答案》

中文名：技术清谈
就是“清谈误国，实干兴邦”里的“清谈”，群里讨论的技术，不考虑生产力。如果我们讨论的技术刚好有生产力，那就太幸运了。绝对算是彩蛋了。
引用 《清談- 维基百科》 的解释：

清谈，又称清言，流行于魏晋时期。汉末黄巾之乱，中央政权瓦解，地方势力抬头，儒家经典随之衰落，乱世之中，老庄思想逐渐抬头，一般文人不谈俗事，不谈民生，祖述老庄立论，大振玄风，最常谈的是《周易》、《老子》、《庄子》称为“三玄”。何晏、王弼、夏侯玄、王衍、郭象等人皆有辩才。何晏“好老庄言”，认为“天地万物，皆以无为为本”，和夏侯玄、王弼等倡导玄学，成为一时风气，往往废寝忘食，甚至可以把人累病谈死。“当时名士清谈，特如斗智。”是后世国学大师钱穆对当时清谈的叙述。

用于表明，我们讨论的问题，用于探究问题的本质，远离功利目的，以技术讨论过程的乐趣为主。
英文名：iTeaTime

IT + TeaTime = iTeaTime

谐音 IT Time，意义为 It's tea-time for IT Gossip. 与中文名意义相近，取清谈之意。
Tea Time 原意为茶话时间，茶歇时间，就是没事闲聊，讨论技术，偶尔水水群放松下。与此群清谈之风相近。
技术清谈 slogan
热情让技术更严谨，
技术让优异更稳定。
形式
三策三答，问答形式。
其他
提出问题的能力，远胜于搜索答案、收集知识的能力。能提出问题，就证明你已经掌握一半了。这便是主动思考与被动思考的区别。
壁纸

横屏字-light mode 壁纸-WeChat微信版
横屏字-light mode 壁纸
横屏字-dark mode 壁纸

微信聊天背景
群专属壁纸-第06版（绝对不挡群昵称版本+适配非齐刘海版本+适配iPhoneX版本）.jpg

竖屏字- light mode
竖屏字- dark mode
居中版本

Wow, you opened a new channel to discuss technology, is it true?
@ChenYilong  Thank you so much...
What is the content of technology you are ready to discuss?

repo: iteatimeteam/Friday-QA


text:
view.ls: filter out path before trying to get metadata information

On top of #510.
We have a index, which is a collection of tracked paths, and view which provides a filtered view over a index. This view is used on granular push/pull and other operations.
Ths PR changes the view.ls() API. Before, we were listing the path from the index, with detail=True which calls the underlying filesystem with fs.info() to get the metadata. Then, we were filtering path after the fact we initialized the filesystem and called fs.info().
This PR changes it to list the paths first, then filters it and only then fetch the metadata information.
I might need to do some cleanups here (and add a test on dvc side), but it would be nice to get a confirmation that this fixes the https://github.com/iterative/dvc/issues/10309.

cc @pmrowla

Thanks @skshetry! It works for me.

Codecov Report
Attention: Patch coverage is 33.33333% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 62.94%. Comparing base (632a420) to head (df5ff4d).

Files
Patch %
Lines

src/dvc_data/index/view.py
33.33%
1 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #517      +/-   ##
==========================================
- Coverage   63.04%   62.94%   -0.11%
==========================================
  Files          62       62
  Lines        4343     4342       -1
  Branches      738      622     -116
==========================================
- Hits         2738     2733       -5
- Misses       1447     1452       +5
+ Partials      158      157       -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: codecov-commenter dberenbaum skshetry

repo: iterative/dvc-data


text:
docs: review Prev and Next button links in all docs

Some of the links are outdated as evidenced in #569
E.g. Prev in https://dvc.org/doc/changelog skips all of Understanding DVC and goes to Tutorial.

Duplicate #559

authors: jorgeorpinel shcheklein


text:
redirects: add bench.dvc.org

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. 🙏

Ok, looks like this is not needed after all. Continuing on slack.


text:
support for dynamically shaped/sized symbolic data types

Currently data types such as DictType, NumpyNdarrayType do not support dynamic size or shape. The types are bound to static data sources. This is problematic when inference output type size/shape can vary based on input size/shape. The onnx supports dynamically shaped/sized symbolic shapes. Similar kind of datatypes should also be supported in MLEM. The ONNX majorly supports NDArray tensor, sequence and map types. NDArray shape can have unknown or named values. Sequence and map does not have size attribute.
Changes needed:

NDArray equivalent NumpyNdarrayType can be modified to support unknown/dynamic values in its shape. Named values support can be added in future if need be. Currently first dimension is treated as unknown.
Sequence equivalent ArrayType supports dynamic size. The size needs to be -1.
Map equivalent DictType is hard to modify to support dynamic size because in current implementation the dataset is tightly bound with the DictType. The keys of dataset are part of DictType. Need to add new datatype for Dict.  Need to see how often maps with dynamic set of keys are used in real world models.

Rn numpy type has it's first shape element as None, which means any type. This way models can accept datasets of different sizes. If you specify all dimensions as None, this will mean dynamic shape. The only thing that will be not dynamic is number of dimensions. Is this not enough to support ONNX?
As for arrays and dicts I agree, we can add special size values for unbounded arrays and "unbounded" dicts (like ListType vs ArrayType, it will have arbitrary number of keys, but all values should be of the same type)

Can shape=[3, None, None] cover 1. and shape=[1, None,4] cover 2.? Can we use shape=Nonefor A1?  As for A3.2, where is this identifier used after? Can we drop it and just use A3.3 everywhere represented byNone`  as dimesion size?

repo: iterative/mlem


text:
Can't build docker image if requirements aren't installed

Can't build docker image if requirements aren't installed
$ mlem deploy run flyio fly.mlem -m ../mlem/emoji/lyrics2emoji --app_name hat
💾 Saving deployment to fly.mlem
⏳ Loading model from ../mlem/emoji/lyrics2emoji.mlem
2022-12-28 15:53:50,224 [WARNING] mlem.utils.module: Fail to determine package name for module 'spacy', using module name instead. If that's incorrect, fix metadata manually, either in `.mlem` file or in your MLEM Python object.
2022-12-28 15:53:50,375 [WARNING] mlem.utils.module: Fail to determine package name for module 'transformers', using module name instead. If that's incorrect, fix metadata manually, either in `.mlem` file or in your MLEM Python object.
❌ Unexpected error: No module named 'transformers'
Use the --tb or --traceback option to include the traceback in the output
Please report it here: <https://github.com/iterative/mlem/issues>

$ yq eval .requirements ../mlem/emoji/lyrics2emoji.mlem
- module: spacy
  version: 3.4.4
- is_package: false
  module: __main__
  name: __main__
  source64zip: eJx1VMFu2zgQvesrCF1EdRVus0cDPrRJLwWaFtjsyQgEmhzHTCiSy6Fiu1+/Q0pW4rRr2JI5fDOcefOGZgg+JubGIZyYROZCZSZTkE6Tgb5Bn23JR7WvKr1ja7KKCFL3Cl94Lf7UMklB/8XRYt0SROxpl7fV2ReDVKeqcjaQc1kI6wlRg+uVj9AfYNvjQL6Vhh1TFqTrExwTz492VTH6aK/Im2JMxmI7+KiRrJuyyp/kn8GJjFhMOx8nMzMuR1k2zG6GB489cz5lwKb5dPuj6Vhzc/P97mv+c/vlPr9+/HN3c988FO/pmU+hwxvWiCdvHC/ZTIlFSGN0BVFVM66+3xucnJR3SRpH/I5OpVEm413HQgTKxOQFdox6kHFPGZEtoq5CNC7x9/QQa9Uu+oGlKB1StQNEZDP1twaTsZ8hpvtcqvkJsXtj/OY1WMrwvEdp/sZD5PA9pUcnGAeaN7qAtgS62kqEK0qSXrppqyFHvAhTzvglRP0/Ic4iICjBvQJE/iLtCCuGKc5aAKcoqO6NC2Omdsl/gnYz/0SSQx9x3YTUTI3xY5pcSp78w4eLUBfNm6DCSkz93mhNYsUkEwj8dwT4Cfxju7m6fhAaklR73ooySfSOgHsZgF937OqayoHBP5kehi1obdxjFqwLgnqrKJqjH6eRkSHYE7dy2GrJjquL+o+ihLiTA2BLyjgaXF+Xvk+Nx2eSRHRiIHaNQhGkiQeDcBaBIlU56NEMxspoEs1i4XhnHA2x9QiYino75ijwxPELKJr5PO1vMsmgiaQlmIFc0C9H8PdVd3PEC44tiSBXX8AojPVq8zayiPKF2tQKGR+pk4kT5W71sFmtiPmHdq6jCN8Ska9T0bHnpZJlW+cprKvzpZCLySP/fqAEBmvoqNVyU8wckftvKXtuX++f17P+WJ/9skzybWOII5KQU8Dnna4w0DKw1K3ZdnGBLOGo1Hdl1l+JVgtsC9YSu08Xq3lPWsvSHthBnupXvQwWBhKcOesDieRqmdy84pdnday2pyytv0qj6o5AQ7DQ56t/Xf/t/IENIxH06Jl3dNJ/os0lFQ==
  type: custom
- module: transformers
  version: 4.25.1
- module: sklearn
  package_name: scikit-learn
  version: 1.1.1
- module: pandas
  version: 1.5.2
- module: numpy
  version: 1.23.5
- extra_index: https://download.pytorch.org/whl/cpu
  module: torch
  version: 1.13.0

long tb
$ mlem --tb deploy run flyio fly.mlem -m ../../mlem/emoji/lyrics2emoji --app_name hat                                  92ms
💾 Saving deployment to fly.mlem
⏳ Loading model from ../../mlem/emoji/lyrics2emoji.mlem
2022-12-28 16:08:08,117 [WARNING] mlem.utils.module: Fail to determine package name for module 'spacy', using module name instead. If that's incorrect, fix metadata manually, either in `.mlem` file or in your MLEM Python object.
2022-12-28 16:08:08,261 [WARNING] mlem.utils.module: Fail to determine package name for module 'transformers', using module name instead. If that's incorrect, fix metadata manually, either in `.mlem` file or in your MLEM Python object.
Traceback (most recent call last):
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/bin/mlem", line 8, in <module>
    sys.exit(app())
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/typer/main.py", line 328, in __call__
    raise e
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/typer/main.py", line 311, in __call__
    return get_command(self)(*args, **kwargs)
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/typer/core.py", line 778, in main
    return _main(
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/typer/core.py", line 216, in _main
    rv = self.invoke(ctx)
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/mlem/cli/main.py", line 174, in invoke
    return super().invoke(ctx)
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/typer/main.py", line 683, in wrapper
    return callback(**use_params)  # type: ignore
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/mlem/cli/main.py", line 475, in inner
    f(*iargs, **ikwargs)
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/mlem/cli/deployment.py", line 139, in deploy_run_command
    deploy(
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/mlem/telemetry.py", line 50, in inner
    return f(*args, **kwargs)
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/mlem/api/commands.py", line 478, in deploy
    model_meta = get_model_meta(model)
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/mlem/api/utils.py", line 35, in get_model_meta
    model.load_value()
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/mlem/core/objects.py", line 830, in load_value
    self.model_type.load(self.relative_artifacts)
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/mlem/core/model.py", line 277, in load
    self.model = self.io.load(artifacts)
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/mlem/contrib/callable.py", line 89, in load
    refs[uuid] = io.load(ref_artifacts.get(uuid, {}))
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/mlem/contrib/torch.py", line 188, in load
    return load(f)
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/torch/serialization.py", line 789, in load
    return _load(opened_zipfile, map_location, pickle_module, **pickle_load_args)
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/torch/serialization.py", line 1131, in _load
    result = unpickler.load()
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/torch/serialization.py", line 1124, in find_class
    return super().find_class(mod_name, name)
  File "/Users/aguschin/Git/iterative/mlem-fly/.venv/lib/python3.9/site-packages/mlem/ext.py", line 256, in load_module
    module = importlib.import_module(fullname)
  File "/Users/aguschin/.pyenv/versions/3.9.5/lib/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
ModuleNotFoundError: No module named 'transformers'

I guess it's connected with #525

At the same time, mlem --tb build docker -m ../mlem/emoji/lyrics2emoji --image.name lyrics2emoji --image.tag v1 works 🤷🏻♂


text:
Refactor revm_spec function to simplify hardfork detection logic

Replaced individual hardfork checks in revm_spec with a loop-based approach using find. Moved hardfork-to-SpecId mapping logic to a separate helper function (map_hardfork_to_spec_id) for cleaner and more maintainable code.

Thank you for the feedback. I'll keep your suggestions in mind and continue looking for ways to support the team. Let's close this thread, as these changes are not the right fit.

appreciate it

authors: cypherpepe mattsse

repo: ithacaxyz/odyssey


text:
misc improvements (see desc)

I've been working off my own fork of Reacord and have been fixing / extending it in ways as they come up, some of these I think make sense to be merged back into the original however the organization of it isn't great for making individual PRs, so I'm opening this PR to highlight some of the areas I think would be good to be merged in

Left some comments in the areas that I think would be relevant to be merged in

Thanks for this! I added some replies, and the comments I thumbed up are changes I'd definitely be interested in accepting. If you do  make separate PRs for those changes, make sure:

Files are formatted with prettier
Consistent variable casing is used, pascalCase not snake_case
There are no type errors

I'm also wary of exposing too much public API surface, which increases the chance of needing to make breaking changes later 😅

The tester in particular I wasn't confident enough in to expose publicly

Yeah a lot of these changes were just me kind of breaking it apart a bit for my own personal use, some of the changes I was making seemed like they might be helpful so your comments were good for knowing what to create individual PRs for
I'll create those prs soon^TM pretty busy with other things but I'd love to help improve this

The tester in particular I wasn't confident enough in to expose publicly

Yeah a lot of these changes were just me kind of breaking it apart a bit for my own personal use, some of the changes I was making seemed like they might be helpful so your comments were good for knowing what to create individual PRs for
I'll create those prs soon^TM pretty busy with other things but I'd love to help improve this

Ok, me and you are gonna get together and try to get this across the line @RhysSullivan lol

Would love to see this get merged. A few little issues that I've experienced are resolved by this PR.

authors: JacobMGEvans RhysSullivan ethndotsh itsMapleLeaf

repo: itsMapleLeaf/reacord


text:
Messages should not be limited to 255 chars

This is because the underlying column has type character varying(255).

Yes, we should switch this to TEXT

Hey guys, is the column in question named 'sentence' in the 'messages' table?

Yup! We'd need a new pair of up/down migrations to modify that column.
To get the timestamp like the other migrations have, try $ date +%s

Are you creating the migrations by hand or is there some package/library helping you with it? Another follow up question: as a general rule/guideline what command/s do I run to check if I haven't broken anything(tests!)? I can't find that in the contributing guide or elsewhere. Thanks in advance. 😄

I tried go test but I get
2016/04/21 22:14:48 failed to start server could not connect to database: dial tcp 127.0.0.1:5432: getsockopt: connection refused

Probably something wrong with my Db..

Yes, that's an error in trying to connect to your DB. Did you run cmd/setup.sh? Did it skip DB setup or run through everything there? Do you have Postgres running?
There's no tool to make migrations. Just create the files and write the SQL--should be one line.

Is this output normal?
➜  abot git:(master) go test ./...
ok  	github.com/itsabot/abot	7.197s
ok  	github.com/itsabot/abot/core	0.177s
?   	github.com/itsabot/abot/core/log	[no test files]
?   	github.com/itsabot/abot/core/template	[no test files]
?   	github.com/itsabot/abot/core/websocket	[no test files]
?   	github.com/itsabot/abot/data/ner	[no test files]
?   	github.com/itsabot/abot/shared/datatypes	[no test files]
?   	github.com/itsabot/abot/shared/helpers/address	[no test files]
?   	github.com/itsabot/abot/shared/helpers/timeparse	[no test files]
?   	github.com/itsabot/abot/shared/interface/cal	[no test files]
?   	github.com/itsabot/abot/shared/interface/cal/driver	[no test files]
?   	github.com/itsabot/abot/shared/interface/email	[no test files]
?   	github.com/itsabot/abot/shared/interface/email/driver	[no test files]
?   	github.com/itsabot/abot/shared/interface/emailsender	[no test files]
?   	github.com/itsabot/abot/shared/interface/emailsender/driver	[no test files]
?   	github.com/itsabot/abot/shared/interface/payment	[no test files]
?   	github.com/itsabot/abot/shared/interface/payment/driver	[no test files]
?   	github.com/itsabot/abot/shared/interface/sms	[no test files]
?   	github.com/itsabot/abot/shared/interface/sms/driver	[no test files]
?   	github.com/itsabot/abot/shared/knowledge	[no test files]
ok  	github.com/itsabot/abot/shared/language	0.047s
?   	github.com/itsabot/abot/shared/nlp	[no test files]
?   	github.com/itsabot/abot/shared/plugin	[no test files]
?   	github.com/itsabot/abot/shared/task	[no test files]

Sorry I deleted my earlier post before you replied.. my db wasn't running. 😛

Yup, that means it all passed! When you create a pull request TravisCI will automatically run all the tests as well.

Thanks, I'll get to work and send in some code soon hopefully!

authors: egtann eviltoylet sharang-d

repo: itsabot/abot

license: mit


text:
Register

@JuliaRegistrator register() VisualSearchACTR

@JuliaRegistrator register() VisualSearchACTR

Registration pull request created: JuliaRegistries/General/38119
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" ebc568f0a29c4eddcb6712156e3a77f418506e7c
git push origin v0.1.0

authors: JuliaRegistrator itsdfish


text:
タイミングゲームを作成する

ゲーム概要
左右に動くバーを真ん中にタイミングよくクリックするゲーム。
真ん中により近くでクリックするほどポイントが多くもらえるようにする。
1分間の間にポイントが規定以上であればゲームクリア、以下であればゲームオーバー。
規定ポイントは10_000ポイントとする。
ゲーム情報

ゲームタイトル、Timing Game
画面サイズ、640x480
背景色、R: 64 G: 64 B: 64

ゲーム状態
ゲームの状態はMainmenu, Ingame, Gameoverの3つを使用する。

Mainmenu: ゲームを起動するときに最初に移行する状態。画面をクリックすることでゲームを開始する。またIngame状態に遷移する。
Ingame: ゲームをすることができる状態。ゲームが終了した際にGameover状態に遷移する。
Gameover: ゲームが終了した時に移行する状態。画面をクリックすることでゲームを再び開始する。またIngame状態に遷移する。

[ ] 以下のアセットを準備する

バー（範囲を決める横に長い棒）

キュー（左右に動く棒）

ゲーム開始画面の画像

クリックした時のサウンド

フォント

repo: ittokunvim/bevy-timing-game


text:
create auv_common_sim and taluy_sim

I made changes to follow the same structure in taluy_descriptions

move the sensor and actuator plugins to auv_common_sim_descriptions package.
move the base and dynamics to taluy_sim_descriptions package
fix the find commands in xacros accordingly

Should I also move the content of taluy_sim_description to auv_sim_description or is this structure better? I thought this makes more sense, since everything in the taluy_sim_description package is spesific to taluy.

repo: itu-auv/auv-software


text:
check if connect! actually returns something sensible

have gotten :badarg.

apparently this was an asynchronous error?  Haven't seen it in a bit.

repo: ityonemo/librarian


text:
Unable to access Forge

2017-02-28 10:29:14	stdout	Error: Unable to access jarfile forge-1.11.2--universal.jar
2017-02-28 10:29:14	stdout	+ exec java -XX:+UseG1GC -Xms4G -Xmx4G -jar forge-1.11.2--universal.jar
2017-02-28 10:29:14	stdout	+ '[' -f /data/bootstrap.txt ']'
2017-02-28 10:29:14	stdout	+ [[ FORGE == \F\E\E\D-\T\H\E-\B\E\A\S\T ]]
2017-02-28 10:29:14	stdout	Setting ops
2017-02-28 10:29:14	stdout	Error: Unable to access jarfile forge-1.11.2--installer.jar
2017-02-28 10:29:14	stdout	Installing forge-1.11.2--universal.jar
2017-02-28 10:29:14	stdout	wget: server returned error: HTTP/1.1 404 Not Found
2017-02-28 10:29:14	stdout	Downloading forge-1.11.2--installer.jar ...
2017-02-28 10:29:14	stdout	-z Lines are terminated by NUL, not newline
2017-02-28 10:29:14	stdout	-u Suppress duplicate lines
2017-02-28 10:29:14	stdout	-s Stable (don't sort ties alphabetically)
2017-02-28 10:29:14	stdout	-r Reverse sort order
2017-02-28 10:29:14	stdout	-k N[,M] Sort by Nth field
2017-02-28 10:29:14	stdout	-t CHAR Field separator
2017-02-28 10:29:14	stdout	-n Sort numbers
2017-02-28 10:29:14	stdout	-M Sort month
2017-02-28 10:29:14	stdout	-g General numerical sort
2017-02-28 10:29:14	stdout	-d Dictionary order (blank or alphanumeric only)
2017-02-28 10:29:14	stdout	-i Ignore unprintable characters
2017-02-28 10:29:14	stdout	-f Ignore case
2017-02-28 10:29:14	stdout	-b Ignore leading blanks
2017-02-28 10:29:14	stdout	-c Check whether input is sorted
2017-02-28 10:29:14	stdout	-o FILE Output to FILE
2017-02-28 10:29:14	stdout
2017-02-28 10:29:14	stdout	Sort lines of text
2017-02-28 10:29:14	stdout
2017-02-28 10:29:14	stdout	Usage: sort [-nrugMcszbdfiokt] [-o FILE] [-k start[.offset][opts][,end[.offset][opts]] [-t CHAR] [FILE]...
2017-02-28 10:29:14	stdout
2017-02-28 10:29:14	stdout	BusyBox v1.25.1 (2016-10-26 16:15:20 GMT) multi-call binary.
2017-02-28 10:29:14	stdout	sort: unrecognized option: V
2017-02-28 10:29:14	stdout	/start-minecraft: line 125: [: =: unary operator expected
2017-02-28 10:29:14	stdout	cat: can't open '/tmp/forge.json': No such file or directory
2017-02-28 10:29:14	stdout	-Y Use proxy ('on' or 'off')
2017-02-28 10:29:14	stdout	-U STR Use STR for User-Agent header
2017-02-28 10:29:14	stdout	-O FILE Save to FILE ('-' for stdout)
2017-02-28 10:29:14	stdout	-T SEC Network read timeout is SEC seconds
2017-02-28 10:29:14	stdout	-P DIR Save to DIR (default .)
2017-02-28 10:29:14	stdout	-q Quiet
2017-02-28 10:29:14	stdout	-c Continue retrieval of aborted transfer
2017-02-28 10:29:14	stdout	-s Spider mode - only check file existence
2017-02-28 10:29:14	stdout
2017-02-28 10:29:14	stdout	Retrieve files via HTTP or FTP
2017-02-28 10:29:14	stdout
2017-02-28 10:29:14	stdout	Usage: wget [-csq] [-O FILE] [-Y on/off] [-P DIR] [-U AGENT] [-T SEC] URL...
2017-02-28 10:29:14	stdout
2017-02-28 10:29:14	stdout	BusyBox v1.25.1 (2016-10-26 16:15:20 GMT) multi-call binary.
2017-02-28 10:29:14	stdout	wget: unrecognized option: S
2017-02-28 10:29:14	stdout	Checking Forge version information.
2017-02-28 10:29:14	stdout	Checking type information.
2017-02-28 10:29:13	stdout	Checking version information.
2017-02-28 10:29:13	stdout	Switching to user 'minecraft'

This appears to be a side effect of switching to the alpine base image. I'll investigate later today.

Thanks for reporting this. The fix is now pushed to Hub.

authors: itzg medvidek

repo: itzg/dockerfiles