Auto mTLS for beta peer authn policy.

blocked by https://github.com/istio/istio/pull/20829

That's a good idea. One of the problems at the moment is the mix/fallback
to alpha API, which has service and port. But it's quite possible to make
some optimization in the future.
On Wed, Feb 5, 2020 at 7:42 PM Jianfei Hu<EMAIL_ADDRESS>wrote:

@incfly commented on this pull request.
In pilot/pkg/proxy/envoy/v2/eds.go
https://github.com/istio/istio/pull/20881#discussion_r375627218:

@@ -914,8 +914,12 @@ func buildLocalityLbEndpointsFromShards(
localityEpMap[ep.Locality] = locLbEps
}
if ep.EnvoyEndpoint == nil {

		tlsLabel := ep.TLSMode

		if !push.BetaPolicyAbleAcceptMTLS(ep.Labels) {

right. i will reuse as much as possible from the existing resolution.
on the caching part, the would that also be applied to the inbound filter
chain construction? a.k.a the PR you currently working on? or it's because
LDS code path are invoked once per push context construction, and we lack
the data structure that can be shared among multiple proxy's LDS code path?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/20881?email_source=notifications&email_token=AF7X24ITOEPXB6XLG53SEQDRBOBKDA5CNFSM4KQTRW4KYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCUOG53I#discussion_r375627218,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF7X24JTUVGQOZI7UBVNUW3RBOBKDANCNFSM4KQTRW4A
.

--
Diem Vu | Software Engineer |<EMAIL_ADDRESS>| +1<PHONE_NUMBER>

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

Test name
Commit
Details
Rerun command

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

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

Test name
Commit
Details
Rerun command

lint_istio
ec0d4fe3138e7610c833ea6d617a40b75dfd20d9
link
/test lint_istio

gencheck_istio
ec0d4fe3138e7610c833ea6d617a40b75dfd20d9
link
/test gencheck_istio

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

I dig a bit of Pilot pushing sequences/logic. And end up something POC like this.

config update handler has a special code for PeerAuthenticationPolicy, which then chain additional CDS/EDS update.

If a namespace policy or workload level policy changed, we trigger CDS/EDS updates on corresponding namespace.
If mesh level policy changes, we trigger update for everything.

within the edsIncremental() ---> buildLocalityLbEndpointsFromShards this function stacks, I have additional check whether that particular endpoint is able to serve mTLS.

this check, reuse the logic of beta policy resolutoin
we can cache the result into a map to avoid resolution for every single endpoint.

@howardjohn @rshriram  could you shed some light on whether this is on the right track? Mostly from pilot pushing organization and perf perspective, thanks!

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

Test name
Commit
Details
Rerun command

gencheck_istio
ec0d4fe3138e7610c833ea6d617a40b75dfd20d9
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
b3d353e8b12851a835f3e14d4a403217b05c8c87
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
b3d353e8b12851a835f3e14d4a403217b05c8c87
link
/test lint_istio

gencheck_istio
b3d353e8b12851a835f3e14d4a403217b05c8c87
link
/test gencheck_istio

integ-security-local-tests_istio
b3d353e8b12851a835f3e14d4a403217b05c8c87
link
/test integ-security-local-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.

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

Test name
Commit
Details
Rerun command

lint_istio
b3d353e8b12851a835f3e14d4a403217b05c8c87
link
/test lint_istio

gencheck_istio
b3d353e8b12851a835f3e14d4a403217b05c8c87
link
/test gencheck_istio

integ-security-local-tests_istio
b3d353e8b12851a835f3e14d4a403217b05c8c87
link
/test integ-security-local-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
b3d353e8b12851a835f3e14d4a403217b05c8c87
link
/test lint_istio

gencheck_istio
b3d353e8b12851a835f3e14d4a403217b05c8c87
link
/test gencheck_istio

integ-security-local-tests_istio
b3d353e8b12851a835f3e14d4a403217b05c8c87
link
/test integ-security-local-tests_istio

unit-tests_istio
b3d353e8b12851a835f3e14d4a403217b05c8c87
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
b3d353e8b12851a835f3e14d4a403217b05c8c87
link
/test gencheck_istio

integ-security-local-tests_istio
b3d353e8b12851a835f3e14d4a403217b05c8c87
link
/test integ-security-local-tests_istio

unit-tests_istio
b3d353e8b12851a835f3e14d4a403217b05c8c87
link
/test unit-tests_istio

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

lint_istio
7139a42f8bd3c97a0087299e8e595d0eba777723
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.

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

Test name
Commit
Details
Rerun command

integ-security-local-tests_istio
b3d353e8b12851a835f3e14d4a403217b05c8c87
link
/test integ-security-local-tests_istio

unit-tests_istio
b3d353e8b12851a835f3e14d4a403217b05c8c87
link
/test unit-tests_istio

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

lint_istio
7139a42f8bd3c97a0087299e8e595d0eba777723
link
/test lint_istio

gencheck_istio
7139a42f8bd3c97a0087299e8e595d0eba777723
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.

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

Test name
Commit
Details
Rerun command

lint_istio
7139a42f8bd3c97a0087299e8e595d0eba777723
link
/test lint_istio

gencheck_istio
7139a42f8bd3c97a0087299e8e595d0eba777723
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
7139a42f8bd3c97a0087299e8e595d0eba777723
link
/test gencheck_istio

integ-distroless-k8s-tests_istio
7139a42f8bd3c97a0087299e8e595d0eba777723
link
/test integ-distroless-k8s-tests_istio

lint_istio
9e322993a94197028a623f1ff4685513ea1bfd57
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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
7139a42f8bd3c97a0087299e8e595d0eba777723
link
/test integ-distroless-k8s-tests_istio

lint_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test lint_istio

gencheck_istio
9e322993a94197028a623f1ff4685513ea1bfd57
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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
7139a42f8bd3c97a0087299e8e595d0eba777723
link
/test integ-distroless-k8s-tests_istio

lint_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test lint_istio

gencheck_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test gencheck_istio

unit-tests_istio
9e322993a94197028a623f1ff4685513ea1bfd57
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.

will add unit test in background.

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

Test name
Commit
Details
Rerun command

lint_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test lint_istio

gencheck_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test gencheck_istio

unit-tests_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test unit-tests_istio

integ-galley-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-local-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.

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

Test name
Commit
Details
Rerun command

lint_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test lint_istio

gencheck_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test gencheck_istio

unit-tests_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test unit-tests_istio

integ-galley-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-security-local-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.

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

Test name
Commit
Details
Rerun command

lint_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test lint_istio

gencheck_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test gencheck_istio

unit-tests_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test unit-tests_istio

integ-galley-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-security-local-tests_istio

integ-conformance-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-local-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.

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

Test name
Commit
Details
Rerun command

lint_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test lint_istio

gencheck_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test gencheck_istio

integ-galley-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-security-local-tests_istio

integ-conformance-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-local-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test lint_istio

gencheck_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test gencheck_istio

integ-galley-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-security-local-tests_istio

integ-conformance-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-local-tests_istio

unit-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test unit-tests_istio

integ-pilot-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-pilot-local-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.

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

Test name
Commit
Details
Rerun command

lint_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test lint_istio

gencheck_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test gencheck_istio

integ-galley-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-security-local-tests_istio

integ-conformance-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-local-tests_istio

unit-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test unit-tests_istio

integ-pilot-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-pilot-local-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

lint_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test lint_istio

gencheck_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test gencheck_istio

integ-galley-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-security-local-tests_istio

integ-conformance-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-local-tests_istio

unit-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test unit-tests_istio

integ-pilot-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-pilot-local-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

lint_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test lint_istio

gencheck_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test gencheck_istio

integ-galley-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-security-local-tests_istio

integ-conformance-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-local-tests_istio

unit-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test unit-tests_istio

integ-pilot-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-pilot-local-tests_istio

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

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

integ-istioio-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-istioio-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.

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

Test name
Commit
Details
Rerun command

lint_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test lint_istio

gencheck_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test gencheck_istio

integ-galley-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-security-local-tests_istio

integ-conformance-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-local-tests_istio

unit-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test unit-tests_istio

integ-pilot-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-pilot-local-tests_istio

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

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

integ-istioio-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-istioio-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test lint_istio

gencheck_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test gencheck_istio

integ-galley-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-security-local-tests_istio

integ-conformance-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-local-tests_istio

unit-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test unit-tests_istio

integ-pilot-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-pilot-local-tests_istio

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

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

integ-istioio-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-istioio-k8s-tests_istio

release-test_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test release-test_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test lint_istio

gencheck_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test gencheck_istio

integ-galley-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-security-local-tests_istio

integ-conformance-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-local-tests_istio

unit-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test unit-tests_istio

integ-pilot-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-pilot-local-tests_istio

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

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

integ-istioio-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-istioio-k8s-tests_istio

release-test_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test release-test_istio

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

integ-galley-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
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.

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

Test name
Commit
Details
Rerun command

lint_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test lint_istio

gencheck_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test gencheck_istio

integ-galley-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-security-local-tests_istio

integ-conformance-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-local-tests_istio

unit-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test unit-tests_istio

integ-pilot-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-pilot-local-tests_istio

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

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

integ-istioio-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-istioio-k8s-tests_istio

release-test_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test release-test_istio

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

integ-galley-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-k8s-tests_istio

e2e-dashboard_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test e2e-dashboard_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test lint_istio

gencheck_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test gencheck_istio

integ-galley-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-security-local-tests_istio

integ-conformance-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-local-tests_istio

unit-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test unit-tests_istio

integ-pilot-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-pilot-local-tests_istio

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

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

integ-istioio-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-istioio-k8s-tests_istio

release-test_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test release-test_istio

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

integ-galley-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-k8s-tests_istio

e2e-dashboard_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test e2e-mixer-no_auth_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test lint_istio

gencheck_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test gencheck_istio

integ-galley-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-security-local-tests_istio

integ-conformance-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-local-tests_istio

unit-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test unit-tests_istio

integ-pilot-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-pilot-local-tests_istio

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

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

integ-istioio-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-istioio-k8s-tests_istio

release-test_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test release-test_istio

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

integ-galley-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-k8s-tests_istio

e2e-dashboard_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test e2e-mixer-no_auth_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test lint_istio

gencheck_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test gencheck_istio

integ-galley-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-security-local-tests_istio

integ-conformance-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-local-tests_istio

unit-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test unit-tests_istio

integ-pilot-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-pilot-local-tests_istio

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

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

integ-istioio-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-istioio-k8s-tests_istio

release-test_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test release-test_istio

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

integ-galley-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-k8s-tests_istio

e2e-dashboard_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test e2e-mixer-no_auth_istio

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

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

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

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

Test name
Commit
Details
Rerun command

lint_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test lint_istio

gencheck_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test gencheck_istio

integ-galley-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-security-local-tests_istio

integ-conformance-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-local-tests_istio

unit-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test unit-tests_istio

integ-pilot-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-pilot-local-tests_istio

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

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

integ-istioio-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-istioio-k8s-tests_istio

release-test_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test release-test_istio

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

integ-galley-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-k8s-tests_istio

e2e-dashboard_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test e2e-mixer-no_auth_istio

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

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

pilot-multicluster-e2e_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test pilot-multicluster-e2e_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test lint_istio

gencheck_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test gencheck_istio

integ-galley-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-security-local-tests_istio

integ-conformance-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-local-tests_istio

unit-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test unit-tests_istio

integ-pilot-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-pilot-local-tests_istio

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

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

integ-istioio-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-istioio-k8s-tests_istio

release-test_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test release-test_istio

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

integ-galley-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-k8s-tests_istio

e2e-dashboard_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test e2e-mixer-no_auth_istio

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

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

pilot-multicluster-e2e_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test pilot-multicluster-e2e_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test gencheck_istio

integ-galley-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-security-local-tests_istio

integ-conformance-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-local-tests_istio

unit-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test unit-tests_istio

integ-pilot-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-pilot-local-tests_istio

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

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

integ-istioio-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-istioio-k8s-tests_istio

release-test_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test release-test_istio

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

integ-galley-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-k8s-tests_istio

e2e-dashboard_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test e2e-mixer-no_auth_istio

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

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

pilot-multicluster-e2e_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test pilot-multicluster-e2e_istio

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

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test gencheck_istio

integ-galley-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-security-local-tests_istio

integ-conformance-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-local-tests_istio

unit-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test unit-tests_istio

integ-pilot-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-pilot-local-tests_istio

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

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

integ-istioio-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-istioio-k8s-tests_istio

release-test_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test release-test_istio

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

integ-galley-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-k8s-tests_istio

e2e-dashboard_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test e2e-mixer-no_auth_istio

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

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

pilot-multicluster-e2e_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test pilot-multicluster-e2e_istio

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

lint_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
9e322993a94197028a623f1ff4685513ea1bfd57
link
/test gencheck_istio

integ-galley-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-security-local-tests_istio

integ-conformance-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-local-tests_istio

unit-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test unit-tests_istio

integ-pilot-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-pilot-local-tests_istio

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

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

integ-istioio-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-istioio-k8s-tests_istio

release-test_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test release-test_istio

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

integ-galley-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-k8s-tests_istio

e2e-dashboard_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test e2e-mixer-no_auth_istio

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

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

pilot-multicluster-e2e_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test pilot-multicluster-e2e_istio

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

lint_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test lint_istio

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

integ-conformance-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-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.

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

Test name
Commit
Details
Rerun command

integ-galley-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-security-local-tests_istio

integ-conformance-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-local-tests_istio

unit-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test unit-tests_istio

integ-pilot-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-pilot-local-tests_istio

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

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

integ-istioio-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-istioio-k8s-tests_istio

release-test_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test release-test_istio

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

integ-galley-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-k8s-tests_istio

e2e-dashboard_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test e2e-mixer-no_auth_istio

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

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

pilot-multicluster-e2e_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test pilot-multicluster-e2e_istio

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

lint_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test lint_istio

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

integ-conformance-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-galley-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-security-local-tests_istio

integ-conformance-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-local-tests_istio

unit-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test unit-tests_istio

integ-pilot-local-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-pilot-local-tests_istio

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

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

integ-istioio-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-istioio-k8s-tests_istio

release-test_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test release-test_istio

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

integ-galley-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-k8s-tests_istio

e2e-dashboard_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test e2e-mixer-no_auth_istio

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

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

pilot-multicluster-e2e_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test pilot-multicluster-e2e_istio

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

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

integ-conformance-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-conformance-k8s-tests_istio

gencheck_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test gencheck_istio

lint_istio
382180bd08242c7f7a50c9dbe2f1a4d01d263855
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test unit-tests_istio

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

integ-istioio-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-istioio-k8s-tests_istio

release-test_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test release-test_istio

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

integ-galley-k8s-tests_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test integ-galley-k8s-tests_istio

e2e-mixer-no_auth_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test e2e-mixer-no_auth_istio

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

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

pilot-multicluster-e2e_istio
afda72c77def9447cca4ccd86d1193d019a0ff07
link
/test pilot-multicluster-e2e_istio

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

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

lint_istio
382180bd08242c7f7a50c9dbe2f1a4d01d263855
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
382180bd08242c7f7a50c9dbe2f1a4d01d263855
link
/test lint_istio

integ-distroless-k8s-tests_istio
382180bd08242c7f7a50c9dbe2f1a4d01d263855
link
/test integ-distroless-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
382180bd08242c7f7a50c9dbe2f1a4d01d263855
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
382180bd08242c7f7a50c9dbe2f1a4d01d263855
link
/test integ-security-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
382180bd08242c7f7a50c9dbe2f1a4d01d263855
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
382180bd08242c7f7a50c9dbe2f1a4d01d263855
link
/test integ-security-k8s-tests_istio

lint_istio
7b8ef631c7690ec21156af92b9124448a350ff38
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
382180bd08242c7f7a50c9dbe2f1a4d01d263855
link
/test integ-security-k8s-tests_istio

lint_istio
7b8ef631c7690ec21156af92b9124448a350ff38
link
/test lint_istio

gencheck_istio
7b8ef631c7690ec21156af92b9124448a350ff38
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
382180bd08242c7f7a50c9dbe2f1a4d01d263855
link
/test integ-security-k8s-tests_istio

lint_istio
7b8ef631c7690ec21156af92b9124448a350ff38
link
/test lint_istio

gencheck_istio
7b8ef631c7690ec21156af92b9124448a350ff38
link
/test gencheck_istio

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

integ-security-local-tests_istio
7b8ef631c7690ec21156af92b9124448a350ff38
link
/test integ-security-local-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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
382180bd08242c7f7a50c9dbe2f1a4d01d263855
link
/test integ-security-k8s-tests_istio

lint_istio
7b8ef631c7690ec21156af92b9124448a350ff38
link
/test lint_istio

gencheck_istio
7b8ef631c7690ec21156af92b9124448a350ff38
link
/test gencheck_istio

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

integ-security-local-tests_istio
7b8ef631c7690ec21156af92b9124448a350ff38
link
/test integ-security-local-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
382180bd08242c7f7a50c9dbe2f1a4d01d263855
link
/test integ-security-k8s-tests_istio

gencheck_istio
7b8ef631c7690ec21156af92b9124448a350ff38
link
/test gencheck_istio

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

integ-security-local-tests_istio
7b8ef631c7690ec21156af92b9124448a350ff38
link
/test integ-security-local-tests_istio

unit-tests_istio
7b8ef631c7690ec21156af92b9124448a350ff38
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
382180bd08242c7f7a50c9dbe2f1a4d01d263855
link
/test integ-security-k8s-tests_istio

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

unit-tests_istio
7b8ef631c7690ec21156af92b9124448a350ff38
link
/test unit-tests_istio

lint_istio
6a522583396f63ca5e86be0b348bdbeebe85dcc4
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
382180bd08242c7f7a50c9dbe2f1a4d01d263855
link
/test integ-security-k8s-tests_istio

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

lint_istio
6a522583396f63ca5e86be0b348bdbeebe85dcc4
link
/test lint_istio

unit-tests_istio
6a522583396f63ca5e86be0b348bdbeebe85dcc4
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
382180bd08242c7f7a50c9dbe2f1a4d01d263855
link
/test integ-security-k8s-tests_istio

lint_istio
6a522583396f63ca5e86be0b348bdbeebe85dcc4
link
/test lint_istio

unit-tests_istio
6a522583396f63ca5e86be0b348bdbeebe85dcc4
link
/test unit-tests_istio

e2e-dashboard_istio
6a522583396f63ca5e86be0b348bdbeebe85dcc4
link
/test e2e-dashboard_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
382180bd08242c7f7a50c9dbe2f1a4d01d263855
link
/test integ-security-k8s-tests_istio

lint_istio
6a522583396f63ca5e86be0b348bdbeebe85dcc4
link
/test lint_istio

unit-tests_istio
6a522583396f63ca5e86be0b348bdbeebe85dcc4
link
/test unit-tests_istio

e2e-dashboard_istio
6a522583396f63ca5e86be0b348bdbeebe85dcc4
link
/test e2e-dashboard_istio

integ-istioio-k8s-tests_istio
6a522583396f63ca5e86be0b348bdbeebe85dcc4
link
/test integ-istioio-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.

Major piece is done. Could you take a fast/first pass? @rshriram @istio/wg-networking-maintainers thanks!

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

Test name
Commit
Details
Rerun command

unit-tests_istio
6a522583396f63ca5e86be0b348bdbeebe85dcc4
link
/test unit-tests_istio

integ-istioio-k8s-tests_istio
6a522583396f63ca5e86be0b348bdbeebe85dcc4
link
/test integ-istioio-k8s-tests_istio

gencheck_istio
3c882d1fd3d3ed6e6c6867b953f36844c38859a7
link
/test gencheck_istio

lint_istio
5e6b923525cc6ee8f99dce7971b0d2e8547ccf66
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
6a522583396f63ca5e86be0b348bdbeebe85dcc4
link
/test unit-tests_istio

integ-istioio-k8s-tests_istio
6a522583396f63ca5e86be0b348bdbeebe85dcc4
link
/test integ-istioio-k8s-tests_istio

lint_istio
5e6b923525cc6ee8f99dce7971b0d2e8547ccf66
link
/test lint_istio

gencheck_istio
5e6b923525cc6ee8f99dce7971b0d2e8547ccf66
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.

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

Test name
Commit
Details
Rerun command

integ-istioio-k8s-tests_istio
6a522583396f63ca5e86be0b348bdbeebe85dcc4
link
/test integ-istioio-k8s-tests_istio

lint_istio
5e6b923525cc6ee8f99dce7971b0d2e8547ccf66
link
/test lint_istio

gencheck_istio
5e6b923525cc6ee8f99dce7971b0d2e8547ccf66
link
/test gencheck_istio

unit-tests_istio
5e6b923525cc6ee8f99dce7971b0d2e8547ccf66
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.

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

Test name
Commit
Details
Rerun command

integ-istioio-k8s-tests_istio
6a522583396f63ca5e86be0b348bdbeebe85dcc4
link
/test integ-istioio-k8s-tests_istio

lint_istio
5e6b923525cc6ee8f99dce7971b0d2e8547ccf66
link
/test lint_istio

gencheck_istio
5e6b923525cc6ee8f99dce7971b0d2e8547ccf66
link
/test gencheck_istio

unit-tests_istio
5e6b923525cc6ee8f99dce7971b0d2e8547ccf66
link
/test unit-tests_istio

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

is this change desired to be backported to 1.5? This is EXTREMELY risky change to make this late in the 1.5 cycle. It's not my call but I would be very hesitant to allow this in 1.5

We do want to ship mTLS beta API in 1.5, and want to keep auto-mTLS working
with both, so unfortunately the answer is yes.
I think we can run some performance tests, and/or long running tests before
merging. Do you have other suggestions to minimize the risk? Tkx
On Tue, Feb 11, 2020 at 9:41 PM John Howard<EMAIL_ADDRESS>wrote:

is this change desired to be backported to 1.5? This is EXTREMELY risky
change to make this late in the 1.5 cycle. It's not my call but I would be
very hesitant to allow this in 1.5
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/20881?email_source=notifications&email_token=AF7X24J5SL6UY22EIR3666LRCODZ3A5CNFSM4KQTRW4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELPP73Y#issuecomment-585039855,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF7X24PN5UTF3BE5RKRKOALRCODZ3ANCNFSM4KQTRW4A
.

--
Diem Vu | Software Engineer |<EMAIL_ADDRESS>| +1<PHONE_NUMBER>

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

Test name
Commit
Details
Rerun command

gencheck_istio
5e6b923525cc6ee8f99dce7971b0d2e8547ccf66
link
/test gencheck_istio

unit-tests_istio
5e6b923525cc6ee8f99dce7971b0d2e8547ccf66
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
5e6b923525cc6ee8f99dce7971b0d2e8547ccf66
link
/test integ-pilot-k8s-tests_istio

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

maybe not an actionable suggestion, but maybe we should have done this 3 months ago like the other risky pilot changes we have made so they have sufficient time to test instead of trying to force them into the release last minute. Since that's not an option, we will need to do extensive perf testing here

did TOC approve an exception to land new features in 1.5?

to be clear, I don't really care too much if you add a new API after the freeze. The concern is touching core pilot code

agree definitely quite some risk, complexity.
on the one hand though, the push is not happening if customer is not using beta mTLS policy (PeerAuthenticationPolicy), to mitigate somewhat a bit. so it'll be an opt-in model, impacting who use beta policy.
having said that, there's still some portion of the code is not conditioned.

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
5e6b923525cc6ee8f99dce7971b0d2e8547ccf66
link
/test integ-pilot-k8s-tests_istio

lint_istio
f5e527d5f29a7aa22b72f0c748427d4917f54c9c
link
/test lint_istio

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

if more of this was "opt in" so only users with the new API i would feel much more comfortable with the changes. except diem also changed the install to use the new API by default so it's more opt out I suppose?

if more of this was "opt in" so only users with the new API i would feel much more comfortable with the changes. except diem also changed the install to use the new API by default so it's more opt out I suppose?

right. the bootstrap/discovery.go config handler has a check on the whether GroupKindResource is new API and only populate PushRequest fields if so.
thus a (maybe) difficult compromise could be not changing how we generate the default installation manifest, i.e, still use the meshpolicy and old api for installation. customers who use beta API need to use new API explicitly. just a thought.
opt-in mode to trigger new pushes in pilot core is how this PR's intention, if implemented correctly. will appreciate another pair of eyes on the review.
will && should do perf testing anyway.

if more of this was "opt in" so only users with the new API i would feel much more comfortable with the changes. except diem also changed the install to use the new API by default so it's more opt out I suppose?

right. the bootstrap/discovery.go config handler has a check on the whether GroupKindResource is new API and only populate PushRequest fields if so.
thus a (maybe) compromise solution could be not changing how we generate the default installation manifest, i.e, still use the meshpolicy and old api for installation. customers who use beta API need to use new API explicitly. we can wait a bit to deprecate meshconfig.
just a thought.
opt-in mode to trigger new pushes in pilot core is how this PR's intention, if implemented correctly. will appreciate another pair of eyes on the review.
will && should do perf testing anyway.

Imo, it seems bad to have beta API but install meshpolicy (alpha) by default. I rather trade the auto mTLS feature for that :).

did TOC approve an exception to land new features in 1.5?

Yes. + @smawson @louiscryan

if more of this was "opt in" so only users with the new API i would feel much more comfortable with the changes. except diem also changed the install to use the new API by default so it's more opt out I suppose?

right. the bootstrap/discovery.go config handler has a check on the whether GroupKindResource is new API and only populate PushRequest fields if so.
thus a (maybe) compromise solution could be not changing how we generate the default installation manifest, i.e, still use the meshpolicy and old api for installation. customers who use beta API need to use new API explicitly. we can wait a bit to deprecate meshconfig.
just a thought.
opt-in mode to trigger new pushes in pilot core is how this PR's intention, if implemented correctly. will appreciate another pair of eyes on the review.
will && should do perf testing anyway.

Imo, it seems bad to have beta API but install meshpolicy (alpha) by default. I rather trade the auto mTLS feature for that :).

Another possible trade-off option is support auto-mTLS with mesh & namespace policy only. I.e my reverted change in cluster.go that I did in https://github.com/istio/istio/pull/20829.

Closing this PR. Further testing turns out that even if Pilot push new label on endpoints, somehow, Envoy can still exhibit residue of previous transport socket match result, which results into connection failure/503.


API discussion re. sortBy

Current gridModel constructor supports a sortBy parameter that is tied to the grid vs. the store.
Larger discussion that could be prioritized for work or tabled for now:

This is currently at the level of the grid vs. the store itself. One downside to this is that you must have the column in your grid (not just your store) in order to sort on it. I ran into this limitation when I wanted to use an internal sortOrder field to fully specify a particular sort, but had no desire to show that in the grid.
We see another limitation to this in the new DataView component, which does not currently offer support for sorting.
Should we revisit adding sorting support to the store?

Minor API tweak I would suggest we could make now:

Sorter objects take a colId property - would suggest renaming to field to be more general / portable, match what we are using in the column defs.

I think one main concern here was with hooking into AG grid's sorting affordances to actually control the sort.  We would need to figure out how to listen to those clicks, and also force the grid to render the current sort state.  We didn't have to do this in Ext where the Grid and the Store were both part of the Ext layer.
We can try to look more closely at AG grid and see if there are hooks there that we missed initially.
This also relates to absolute value sorting, which we don't currently support.

We also thought about the sorter object definition use of colId vs. Field and went back and forth on that.  At the time, and because the sort was on the grid we decided to go with the simpler API aligned with AG Grid.  Did not realize we were using field for the Column Defs.

I was able to implement custom sorting (abs sort -> trim data -> value sort) for a client app by setting enableServerSideSorting=true in the grid options and handling sortChanged events from the grid api. I used ag-grid's internal sort model to maintain the sort state, which took care of the rendering in the column headers. The un-ideal part of my implementation was that I just replaced the grid data after I applied the sort, which would cause the grid to tear down and re-create all of the row elements. There are much more efficient methods for updating the grid data detailed here: https://www.ag-grid.com/javascript-grid-data-update/

This is great new John -- Anselm mentioned the possibility of this approach -- glad it worked for you!

Were you actually able to 'control' the sort state externally?
How did you render abs sort vs. regular sort?  Did you have a way to actually customize the column headers?
I am less worried about re-supplying all the data -- we have to do that fairly frequently on reloads and it needs to be snappy.  It seems to me that this might be fast enough for sorting on most grids

At this point, can / should we break this ticket up into some more concrete issues? We're looking to deal with:

Column filters #858
Pivoting #783
Ongoing review of tree support / handling (e.g. #750)

...all of which seem related. Would like to touch base about how we want to prioritize and tackle these interrelated issues overall.


Better standalone support

I know using Symmetric Encryption with rails is pretty straight forward. However, trying to use it outside of rails can be cumbersome especially for generating configurations etc. How do you feel about a symmetric-encryption executable to be packaged with the gem to aid in generating outside of a rails application?

Absolutely love the idea. :tada:
Would be awesome if the bin file could also replace the existing rake tasks.

If I get a chance this week I can take a crack at it. I did something similar for my Groovy library. https://github.com/amedeiros/symmetric-encryption/blob/master/README.md#command-line-runner-usage .

This is what I got going so far.
symmetric-encryption <options>
    -e, --encrypt                    Encrypt a plain text value. Requires --env and --file.
    -d, --decrypt VALUE              Decrypt a encrypted value. Requires --env and --file.
    -r, --random                     Generate a random password.
    -k, --keys                       Generate encryption keys Requires --env and --file.
    -c, --config                     Generate a configuration file. Requires --path and --name
    -p, --path KEY_PATH              Key path for configuration generator.
    -n, --name NAME                  Name for configuration generator
    -v, --env ENVIRONMENT            Which environment are we using.
    -f, --file FILE_PATH             File path of your configuration file.

± |master S:1 U:3 ?:2 ✗| → symmetric-encryption --encrypt --env development --file ~/Documents/ruby_projects/symmetric-encryption-1/examples/symmetric-encryption.yml
Enter the value to encrypt:
*********
Re-enter the value to encrypt:
*********

Encrypted: ClfV19NzS/hjZeAMGHOTOA==

± |master S:1 U:3 ?:2 ✗| → symmetric-encryption --decrypt ClfV19NzS/hjZeAMGHOTOA== --env development --file ~/Documents/ruby_projects/symmetric-encryption-1/examples/symmetric-encryption.yml
Decrypted: PlainText

± |master S:1 U:3 ?:2 ✗| → symmetric-encryption -r --env development --file ~/Documents/ruby_projects/symmetric-encryption-1/examples/symmetric-encryption.yml

Generated Password: 9vL5RCntPkoDoQ9zshmV+w
Encrypted: YMBUjk74WoIsjixxYviHc+hme1XlXyMx8CU+rrDMlaA=

± |master S:1 U:3 ?:2 ✗| → symmetric-encryption -k --env development --file ~/Documents/ruby_projects/symmetric-encryption-1/examples/symmetric-encryption.yml

Please add the key: F/MVgcK62zaX2erG9LLKJA== to your config file
Please add the iv: 4aWpVlv9eLuKMWBML3Td2w== to your config file

± |master S:1 U:3 ?:2 ✗| → symmetric-encryption -c --path /etc/rails --name test_app
New configuration at: /Users/amedeiros/Documents/ruby_projects/symmetric-encryption-1/config/symmetric-encryption.yml

Very nice, looking forward to giving it a try. 👍

Thank you @amedeiros for the PR.
When do you want a gem release?
Now that I think about it we can add docs for it under /docs/rake_tasks.md. Then we can rename that page and its link. To see the docs as they are changed:

cd docs
bundle
jekyll serve

I wonder how difficult it would be to add heroku support: https://github.com/rocketjob/symmetric-encryption/issues/56

As far as a new gem release I'm in no rush. I wanted the standalone support for a open source project I'm working on https://github.com/amedeiros/micro-rb. My CLI for the project generator has an option to include symmetric-encryption but I wanted to also generate the symmetric encryption config file. Figured it would be better to just contribute that in the form of a bin file.

v4 of Symmetric Encryption is now at beta3 and includes an all new CLI that addresses the above issues.


The audioElement isn't necessary on iOS 9

I don't know why we use the audio element on video-proxy. It seems not working. I use the video element on iOS 9 directly and test play/pause function. Everything is ok.

@wuyingfengsui does this cause an actual bug or is it just unnecessary code?


Error on port 80. Please try to change the port through settings or report on GitHub.

I am getting below error:
Error on port 80. Please try to change the port through settings or report on GitHub.
Code in my .vscode\settings.json
{     "liveServer.settings.port":80, }

You can set port 80, if it is available. [Most of case, you'll not]

@duplicate #80, #74, #57

Yes! Most of thethe case, you can't.
You can't even kill the process which is running on port 80. At least, I can't kill port80 in my laptop (even IIS is disabled).
I'm not sure but I think system reserves this port.

thanks bro @hipartha


"ruby -wKU: No such file or directory"

I tried 'gist list ', and I got this error. Looks like the very first line in the script. I am new to ruby and not sure how to fix this. I think these are required switches for the program, but not able to find a fix after searching the internet.

#!/usr/bin/env ruby -wKU

Looks like it's a linux-mac change. I am ubuntu and changing the 1st like to below worked.

#!/usr/bin/ruby -wKU


Update power-bi-data-sources.md

Adding a documentation of limitation for oracle direct query data types

#label:"aq-pr-triaged"


Template Studio doesnmt like the template when its uploaded(after download)

I downloaded the supplyagreement V 0.12.1, then immediately uploaded it back up into a new project (newsupplyagreement)
to change it. It tells me :
"[Change Model] Namespace is not defined for type org.accordproject.usa.state.* File 'model/model.cto': "
Its like it cant see the Namespace model, past6ing the URL into the web browser downloads the cto file. for usa.state

I also found that most model imports do not work properly. I needed to copy the contents of the URL into the model.


Puck indicator is not keeping up with the device actual location

Android API: 26-33
Maplibre Navigation SDK version: 3.0.0
When driving to a destination, the Puck (MyLocation) indicator is getting behind the current device location
which is misleading during navigation
for example, I get past an intersection in real, but the map shows 10-20 meters behind

This is a known problem of the MapLibre native project.
The biggest problem is the implementation of the animation for the movement of the puck.
If you are using the raw GPS information, the puck is jumping and moves jerkily every second to the current position. For a smooth view, the puck is animated. This animation is calculated from the last position to the newest position. The duration is calculated also for a second. When the animation ends, the puck is then on the current location. But the real location has also moved forward and is not no longer up to date.
With this implementation the location puck is always a step behind. A solution were to use the current position as start point and calculate the most probable future point. @boldtrn has mentioned the Kalman filter for this.
Feel free to start working and create a PR for this topic :-)

Closed. Not part of the navigation project.

@Fabi755 @boldtrn
Please give me some clues on where to start.
Should I work on the MapLibre native project or are other projects involved in this change?

Yes, if you would like to improve the Puck, maplibre  native is the right place. You might want to join the Slack if you are having issues getting started.


Transparent Window Background

Implement Transparent Window Background for both 'Randomizer' and its 'Settings' window.

It seems there is some bug in undocumented 'SetWindowCompositionAttribute' function, cause windows are flickering or blinking on resizing.
Currently available Simple blur and Acrylic Blur.
New Randomizer Look:


Proposed solution to Ruby client problem when verifying requests

Hi,
Please could you review my problem and proposed solution. All feedback is welcome.
Solution
To transform the base-64 encoded body value back to a string so that verification does not error when there is a stored response.
Detailed problem
I had a problem when using the client's verify method. It would error with the following stack trace:
[2015-04-29 13:01:40] DEBUG [MockServer::MockServerClient] URL: /retrieve. Payload: {"httpRequest"=>{"method"=>#<MockServer::Model::HTTPMethod:0x007fc6ab6e1288 @value=:POST>, "path"=>"/login"}}
[2015-04-29 13:01:40] DEBUG [MockServer::MockServerClient] Got retrieve response: 200
gems/ruby-2.0.0-p643/gems/mockserver-client-1.0.4/lib/mockserver/model/enum.rb:16:in `initialize': Supplied value: BINARY is not valid. Allowed values are: BINARY (RuntimeError)

client gem version=1.0.4
Docker mock-server (both in the registry and one build locally)
java -Dfile.encoding=UTF-8 -Dmockserver.logLevel=WARN -jar /opt/mockserver/mockserver-netty-3.9.1-jar-with-dependencies.jar  -serverPort 8080 -proxyPort 9090
In the context of calling retrieve, I get the stored responses with a response body whose value is base-64 encoded. Using puts request I saw that the body.value looked suspiciously like a base-64 which it turned out to be.
Here is the code which exercises the problem:
require 'mockserver-client'
require "net/http"
require "uri"
require 'json'

include MockServer
include MockServer::Model::DSL

docker_host = ENV["DOCKER_HOST"]
docker_host_ip = /([0-9]{1,3}[.]){3}[0-9]{1,3}/.match(docker_host)
mock_server_port = 8080

def sendLoginRequest(mock_server_hostname_or_ip, mock_server_port)
    uri_string = "http://#{mock_server_hostname_or_ip}:#{mock_server_port}/login"
    uri = URI.parse(uri_string)
    http = Net::HTTP.new(uri.host, uri.port)
    request  = Net::HTTP::Post.new(uri.request_uri)

    request.body = "{username: 'foo', password: 'bar'}"
    response = http.request(request).to_json
end

client = MockServerClient.new(docker_host_ip, mock_server_port)
expectation = expectation do |expectation|
    expectation.request do |request|
        request.method = 'POST'
        request.path = '/login'
        request.body = exact("{username: 'foo', password: 'bar'}")
    end

    expectation.response do |response|
        response.status_code = 401
        response.headers << header('Content-Type', 'application/json; charset=utf-8')
        response.headers << header('Cache-Control', 'public, max-age=86400')
        response.body = body("{ message: 'incorrect username and password combination' }")
        response.delay = delay_by(:SECONDS, 1)
    end
end
client.register(expectation)

sendLoginRequest(docker_host_ip, mock_server_port)

client.verify(request(:POST, '/login') do |request|
    request.body = exact("{username: 'foo', password: 'bar'}")
end)

Thanks, I'm very backed up now but I'll try to take a look at this in the next week or so.

I am ready to merge this however I can't seem to merge this using github web tool and when I do it from the command line it marks all the commit against my name.  Do you know why the web tool is not allowing me to merge your changes?

I also have some review comments as follows:
Can you uncomment enum.rb:16 instead I created a simpler version of this method in the Boolean class as follows:
class Boolean < Enum
  def allowed_values
    [true, false]
  end

  def !
    !@value
  end

  def initialize(supplied_value)
    @value = pre_process_value(supplied_value)
  end
end

In addition can you revert the changes to .travis.yml as the maven build is already supposed to run the ruby tests.  However there was a bug in the way maven was configured so please add the spec argument to exec-maven-plugin plugin configuration in mockserver-client-ruby/pom.xml as follows:
<execution>
    <id>ruby_make</id>
    <phase>prepare-package</phase>
    <goals>
        <goal>exec</goal>
    </goals>
    <configuration>
        <skip>${skipRubyBuild}</skip>
        <executable>bundle</executable>
        <arguments>
            <argument>exec</argument>
            <argument>rake</argument>
            <argument>build</argument>
            <argument>spec</argument>
        </arguments>
        <environmentVariables>
            <BUNDLE_GEMFILE>${basedir}/Gemfile</BUNDLE_GEMFILE>
        </environmentVariables>
    </configuration>
</execution>

Then to run just the mockserver-ruby-client (as it runs on Travis) just:
cd ./mockserver-client-ruby && mvn clean install

If you can make these changes hopefully I can use the github web tool for merging and then your commit will appear under your name.  If you're not bothered then I'm also happy to merge using the command line tool and add your name into the comment.

Thanks for the feedback. I have made the suggested changes.
Please I note I have rebased so that the merge is clean (this removed the comment enum.rb:16 in an earlier commit).

If you can't get the Travis build to work don't worry as I can run the build locally, the Travis build for pull requests seems flaky, if it fails the first time I re-run it but if it fails again for something unrelated to your change I'll merge if it passes on my local machine.
Also I'll be out of the country on business until Thursday so I may not get a chance to look at this until end of the week.


what's this

2d sandbox game which is developed on unity (PS: I wrote this in README)
and this is the script part of that, it contains all the functions of the game
By the way, have you ever developed with C# ?


Generating just one word

Hi @ankush-me, can I change something so the script generate just one word without paragraphs or lines?

I have same doubt... Please help


Adding error message for azure client errors

Currently, in the azure client class, dependabot raises an appropriate error depending on the error response code. For e.g here, it raises InternalServerError when response code == 500
The problem, here, is just raising appropriate error isn't entirely helpful to detect the exact root cause of the failure. If we can also add the error message from the response to the raised error, then it would help analyse the exact issue of the failure. For example, AzureDevops(ADO) allows repos to specify policies like allowing commit only for identities having emails or having emails ending with a particular suffix like @xyz.com,etc. If now an identity having email other than what is allowed by such policies tries to create a source branch, it returns a 500 response code i.e InternalServerError. Without the error message, it would be difficult to know that the failure was caused due to this policy. Similarly, while PR creation in azure client, it passes labels (code) in the request body. If the label already does not exist, then it tries to create a new one and if the requesting identity does not have the permission to create a new label in ADO, then it returns a 403 response code. In this case too, it would be difficult to know that the error was caused due to missing label creation permissions from only the response code
@jurre @feelepxyz I wanted to understand if you guys have come across such issues reported by other ADO customers or for any other clients supported in dependabot and if you have plans on making these errors more descriptive with the response error message

Azure Devops support is very much community supported. I'm sure all the point you raise could be improved. You've done a great job with PR's in the past, and we'd happily review/merge any new ones you open.
I'm going to close as this issue is honestly a bit spaghetti with intertwined issues, comments, and questions so isn't super actionable. But feel free to break them out as distinct issues that are more easily tracked / fixed by separate PR's.


fix: #687 - safer product list load

Not sure if it solves #687, that I could not reproduce.
Impacted file:

product_list.dart: reordering the load of fields

@M123-dev Could you actually reproduce the crash without this PR, and not reproduce it with this PR, or do you just assume that anyway it's safer?


.Net: RC1 support for SKNameAttribute

Given a native function such as:
[KernelFunction, Description("...")]
public async Task<string> MethodName(
    [Description("...")] string input,
    [SKName("testVar"), Description("...")] string? fooBar = null)
{ ... }

where function arguments are given a custom name: looks like RC1 is missing a port of SKNameAttribute, blocking some upgrades from beta8 to RC1.

where function arguments are given a custom name

An explicit decision was made to remove that (cc: @matthewbolanos). What's the scenario where you need to give it a name that you can't just use as the parameter name?

here's an example:
var args = new KernelArguments
{
    [MemoryPlugin.FilePathParam] = DocFilename,
    [MemoryPlugin.DocumentIdParam] = "NASA001"
};
await memoryPlugin["SaveFile"].InvokeAsync(kernel, args);

When doing this over and over, it's better using constants than hard coding param names that could change over time. Plus (separate feature) there's a need to allow overriding descriptions and names to get better results from planners (few tokens, better plans, etc.), so there should be an infrastructure that allows to manage the mapping from C# var name to external names.

Without a mechanism to link the constant to the var name, that's bound to lead to errors, e.g. while refactoring code, without any mechanism to find them. About planners, it's not only about description, also the var name affect LLM's ability to choose a function and pass the correct data, so for instance it's better using "limit" instead of "l", and there's a case for LLMs trained on specific foreign languages, so var names need to be translatable for planners to work with more precision. (side note: most LLMs are English centric, causing up to 8x more tokens when processing foreign data, so there are models being trained differently, e.g. that's the case with Chinese, Hindi, Arabic, etc)

Without a mechanism to link the constant to the var name, that's bound to lead to errors, e.g. while refactoring code, without any mechanism to find them.

I don't think that's worth needing to complicate the programming model.  If someone is really worried about that, they can enforce that with an analyzer, no? It doesn't require that SK supply it: they can use whatever mechanism they want to ensure that their constant value matches their parameter name.

About planners, it's not only about description, also the var name affects LLM's ability to choose a function and pass the correct data, so for instance it's better using "limit" instead of "l"

So we can name the parameter limit rather than l.  I'm still not clear why the C# parameter name can't just be the parameter name.
To me this seems like unnecessary complication for little gain. But I'll defer to @matthewbolanos.

We've gotten some additional feedback from the Bing team on the desire for overriding the parameter names. The most compelling case is so that you can use prompt engineering to improve the parameter names over time (and so you aren't locked into language specific naming conventions).

Bumping further since you often need to change the names of parameter names to snake case to improve the model's ability to call the function

This can be achieved by transforming the plugin, see: https://devblogs.microsoft.com/semantic-kernel/transforming-semantic-kernel-functions/


Update Globals “theme”

Automatically generated by Netlify CMS

👷 Deploy Preview for shiny-babka-998c7e processing.

Name
Link

🔨 Latest commit
395d3613074cd2acf7c000ec5254fdfb23da4314

🔍 Latest deploy log
https://app.netlify.com/sites/shiny-babka-998c7e/deploys/65e82a1fd6320d00089ef5eb


How To Use It ?

Can You Provide Database -Table Here?

download database from here
https://github.com/thasneemilm/CodeIgniterESMS092015/blob/master/codeigniter3tests (1).sql

download database from here
https://github.com/thasneemilm/CodeIgniterESMS092015/blob/master/codeigniter3tests (1).sql

can you reupload your database, please.

No database

can anyone help me, where is the db?

download database from here
https://github.com/thasneemilm/CodeIgniterESMS092015/blob/master/codeigniter3tests (1).sql

broken link... plz guide me, where is the db?

yep link is broken.

pls upload the database, mentioned link is broken!


Restrict option is not working properly

Hello sir♥
First of all, thank you very much for the panel you made and provided to us.
My problem is that when I activate the restrict option for a user and then deactivate it, that user is deleted from my panel.

Hello sir♥
First of all, thank you very much for the panel you made and provided to us.
My problem is that when I activate the restrict option for a user and then deactivate it, that user is deleted from my panel.

Hi! I'm glad you liked it! I'm wondering are you using the latest version?

https://github.com/user-attachments/assets/17ec79f9-8e5f-4f8a-ba23-d6ba497db54d
Hi! I did a testing on the latest version,  and it works fine. If it is still not working for you after installing the latest version, could you please run it in .wgd.sh debug and let me know what’s the output is in your terminal please?

I see, may I know how do you back it up?

Ohhhhhkay, let me try this on my side since you mentioned a lot of peers.. maybe is a bug?

What do you suggest for backing up and transferring users from the previous panel to version 4?

Honestly I think you're doing the right thing.. I don't see any problems with it but still let me do some testing and I'll let you know :)

Hi! I tested on my side and even simulated what you provided in the screenshot.. It still works perfectly fine.. maybe it was hidden on your mobile UI?

@Mortezajl Is it working?


Further improvement suggestion (and implementation) for systemd unit and timer files

I don't know how to submit a PR, so here are my files for your use for now.
# /etc/systemd/system/fedifetcher.service
[Unit]
Description=FediFetcher Service
After=network.target mastodon-web.service mastodon-sidekiq.service<EMAIL_ADDRESS>
[Service]
Type=simple
User=mastodon
# WorkingDirectory is your checked-out FediFetcher repo directory
# I don't like having only case-seperate same paths, so this is mine
WorkingDirectory=/opt/fedifetcher/venv/FediFetcher
# ExecStart must use the python binary created in the venv
ExecStart=/opt/fedifetcher/venv/bin/python3 find_posts.py -c=artifacts/config.json

# /etc/systemd/system/fedifetcher.timer
[Unit]
Description=FediFetcher Timer

[Timer]
# don't start until system has settled (adjust as you need)
OnBootSec=15min
# after the unit has run once, wait a minute, then run again (removes dependency on lockfile, I think)
OnUnitActiveSec=1min

[Install]
WantedBy=timers.target

Thanks for this!
A couple of comments please:

I believe your WorkingDirectory and ExecStart directives don't match the rest of the guide. Can you please either adjust these, or (and maybe that is better, given the confusion of upper/lowercase directories) tell me about changes that would be needed for the rest of the guide to bring these inline?
Your system files seem to indicate you are using the python venv. The current guide suggests in step 8 to disable the venv. Should that step be removed?

PRs to the Wiki can be filed here: https://github.com/nanos/FediFetcher-docs Apologies, I need to update the README file

I wrote a .service and .timer in the AUR package: https://aur.archlinux.org/packages/fedi-fetcher


[4029] Adjust Hesa::Client to handle new HESA login page

Context
https://trello.com/c/xgQ17ac7/4029-fix-hesa-login
Changes proposed in this pull request

Update Hesa::Client to handle the recent update to HESA's login form

Important business

[ ] Does this PR introduce any PII fields that need to be overwritten or deleted in db/scripts/sanitise.sql?
[ ] Does this PR change the database schema? If so, have you updated the config/analytics.yml file and considered whether you need to send 'import_entity' events?

NB: Please notify the #twd_data_insights team and ask for a review if new fields are being added to analytics.yml

 Fix HESA login


Update free-programming-playgrounds.md

Adding some latest online platform for practicing JS, Perl, PHP, Python, Scala
What does this PR do?
Improve Repo
For resources
Description
Why is this valuable (or not)
All in one online-IDE
How do we know it's really free?
It's an open-source IDE and can be used by anyone.
For book lists, is it a book?
Checklist:

[x] Not a duplicate
[ ] Included author(s) if appropriate
[x] Lists are in alphabetical order
[ ] Needed indications added (PDF, access notes, under construction)

Why put this in the Javascript section? To align with our books list, maybe we need a "language agnostic" section.
Pay attention to alphabetization and the Travis output!

I don't think language agnostic is a good idea.
Because the playground does not support all languages.
Index language by language should be easier to find.