text:
remove deprecated proxy_init.resources from default profile

Please provide a description of this PR:
The proxy_init.resources value is deprecated and has no effect since the value of proxy.resources is actually used for setting this. It can be removed from the default profile.

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

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

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

Test name
Commit
Details
Required
Rerun command

gencheck_istio
3007ffbea450988f0dcb7e6034e7880b7152dc59
link
true
/test gencheck

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

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

Test name
Commit
Details
Required
Rerun command

gencheck_istio
8cb37883a2a5479a5438e5c97f9f898b7abf171e
link
true
/test gencheck

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

authors: istio-testing ufUNnxagpM


text:
use maps.MergeCopy

Please provide a description of this PR:

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

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
719725105d08d1070da2c8eb904b6f92fe746427
link
true
/test unit-tests-arm64

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.

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

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
719725105d08d1070da2c8eb904b6f92fe746427
link
true
/test unit-tests-arm64

unit-tests_istio
719725105d08d1070da2c8eb904b6f92fe746427
link
true
/test unit-tests

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

source: gharchive/pull-request

authors: hzxuzhonghu istio-testing

repo: istio/istio

license_type: permissive

license_source: github-api


text:
use configurable paths for envoy and envoy config locations

ran into a problem with this hardcoded envoy path the other day. use the suggested util paths instead.
thanks,
Utako

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

Needs approval from an approver in each of these files:

mixer/test/client/OWNERS

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

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

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

/ok-to-test

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
373ac50cb6858a58e0955130cd29f24c62568fcb
link
/test istio-pilot-e2e

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
373ac50cb6858a58e0955130cd29f24c62568fcb
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests-v1alpha3.sh
373ac50cb6858a58e0955130cd29f24c62568fcb
link
/test e2e-bookInfo-envoyv2-v1alpha3

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

All tests passed. circleci dependencies is not reporting status but it definitely passes (its common requirement across all circleci tasks)

authors: istio-testing rshriram utako zachgersh


text:
Support zipkin collector endpoint configuration

Please provide a description of this PR:
This PR aims to support customized endpoint of this feature request https://github.com/istio/istio/issues/53086.

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

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

/ok-to-test

need a release notes

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test release-notes

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

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test release-notes

unit-tests-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test unit-tests-arm64

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-sigs/prow repository. I understand the commands that are listed here.

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test release-notes

unit-tests-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test unit-tests-arm64

lint_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test lint

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

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test release-notes

unit-tests-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test unit-tests-arm64

lint_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test lint

integ-basic-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-basic-arm64

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-sigs/prow repository. I understand the commands that are listed here.

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test release-notes

unit-tests-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test unit-tests-arm64

lint_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test lint

integ-basic-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-basic-arm64

integ-cni_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-cni

integ-ipv6_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ipv6

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-sigs/prow repository. I understand the commands that are listed here.

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test release-notes

unit-tests-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test unit-tests-arm64

lint_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test lint

integ-basic-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-basic-arm64

integ-cni_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-cni

integ-ipv6_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ipv6

integ-telemetry-discovery_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-discovery

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-sigs/prow repository. I understand the commands that are listed here.

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test release-notes

unit-tests-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test unit-tests-arm64

lint_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test lint

integ-basic-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-basic-arm64

integ-cni_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-cni

integ-ipv6_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ipv6

integ-telemetry-discovery_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-discovery

integ-pilot_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot

integ-distroless_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-distroless

integ-ds_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ds

integ-security-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-istiodremote

gencheck_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test gencheck

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

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test release-notes

unit-tests-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test unit-tests-arm64

lint_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test lint

integ-basic-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-basic-arm64

integ-cni_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-cni

integ-ipv6_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ipv6

integ-telemetry-discovery_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-discovery

integ-pilot_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot

integ-distroless_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-distroless

integ-ds_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ds

integ-security-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-istiodremote

gencheck_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test gencheck

integ-telemetry_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry

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-sigs/prow repository. I understand the commands that are listed here.

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test release-notes

unit-tests-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test unit-tests-arm64

lint_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test lint

integ-basic-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-basic-arm64

integ-cni_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-cni

integ-ipv6_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ipv6

integ-telemetry-discovery_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-discovery

integ-pilot_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot

integ-distroless_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-distroless

integ-ds_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ds

integ-security-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-istiodremote

gencheck_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test gencheck

integ-telemetry_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry

integ-pilot-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-istiodremote

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

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test release-notes

unit-tests-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test unit-tests-arm64

lint_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test lint

integ-basic-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-basic-arm64

integ-cni_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-cni

integ-ipv6_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ipv6

integ-telemetry-discovery_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-discovery

integ-pilot_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot

integ-distroless_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-distroless

integ-ds_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ds

integ-security-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-istiodremote

gencheck_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test gencheck

integ-telemetry_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry

integ-pilot-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-istiodremote

integ-security-multicluster_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-multicluster

integ-pilot-multicluster_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-multicluster

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-sigs/prow repository. I understand the commands that are listed here.

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test release-notes

unit-tests-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test unit-tests-arm64

lint_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test lint

integ-basic-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-basic-arm64

integ-cni_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-cni

integ-ipv6_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ipv6

integ-telemetry-discovery_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-discovery

integ-pilot_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot

integ-distroless_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-distroless

integ-ds_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ds

integ-security-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-istiodremote

gencheck_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test gencheck

integ-telemetry_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry

integ-pilot-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-istiodremote

integ-security-multicluster_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-multicluster

integ-pilot-multicluster_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-multicluster

macbuildcheck_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test macbuildcheck

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-sigs/prow repository. I understand the commands that are listed here.

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test release-notes

unit-tests-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test unit-tests-arm64

lint_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test lint

integ-basic-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-basic-arm64

integ-cni_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-cni

integ-ipv6_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ipv6

integ-telemetry-discovery_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-discovery

integ-pilot_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot

integ-distroless_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-distroless

integ-ds_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ds

integ-security-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-istiodremote

gencheck_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test gencheck

integ-telemetry_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry

integ-pilot-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-istiodremote

integ-security-multicluster_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-multicluster

integ-pilot-multicluster_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-multicluster

macbuildcheck_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test macbuildcheck

integ-helm_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-helm

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-sigs/prow repository. I understand the commands that are listed here.

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test release-notes

unit-tests-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test unit-tests-arm64

lint_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test lint

integ-basic-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-basic-arm64

integ-cni_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-cni

integ-ipv6_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ipv6

integ-telemetry-discovery_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-discovery

integ-pilot_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot

integ-distroless_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-distroless

integ-ds_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ds

integ-security-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-istiodremote

gencheck_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test gencheck

integ-telemetry_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry

integ-pilot-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-istiodremote

integ-security-multicluster_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-multicluster

integ-pilot-multicluster_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-multicluster

macbuildcheck_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test macbuildcheck

integ-helm_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-helm

integ-pilot-istiodremote-mc_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-istiodremote-mc

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

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test release-notes

unit-tests-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test unit-tests-arm64

lint_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test lint

integ-basic-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-basic-arm64

integ-cni_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-cni

integ-ipv6_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ipv6

integ-telemetry-discovery_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-discovery

integ-pilot_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot

integ-distroless_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-distroless

integ-ds_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ds

integ-security-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-istiodremote

gencheck_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test gencheck

integ-telemetry_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry

integ-pilot-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-istiodremote

integ-security-multicluster_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-multicluster

integ-pilot-multicluster_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-multicluster

macbuildcheck_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test macbuildcheck

integ-helm_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-helm

integ-pilot-istiodremote-mc_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-istiodremote-mc

integ-security_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security

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-sigs/prow repository. I understand the commands that are listed here.

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test release-notes

unit-tests-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test unit-tests-arm64

lint_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test lint

integ-basic-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-basic-arm64

integ-cni_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-cni

integ-ipv6_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ipv6

integ-telemetry-discovery_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-discovery

integ-pilot_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot

integ-distroless_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-distroless

integ-ds_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ds

integ-security-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-istiodremote

gencheck_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test gencheck

integ-telemetry_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry

integ-pilot-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-istiodremote

integ-security-multicluster_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-multicluster

integ-pilot-multicluster_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-multicluster

macbuildcheck_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test macbuildcheck

integ-helm_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-helm

integ-pilot-istiodremote-mc_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-istiodremote-mc

integ-security_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security

integ-ambient_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ambient

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-sigs/prow repository. I understand the commands that are listed here.

wait for https://github.com/istio/istio/pull/53115?

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test release-notes

unit-tests-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test unit-tests-arm64

lint_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test lint

integ-basic-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-basic-arm64

integ-cni_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-cni

integ-ipv6_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ipv6

integ-telemetry-discovery_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-discovery

integ-pilot_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot

integ-distroless_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-distroless

integ-ds_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ds

integ-security-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-istiodremote

gencheck_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test gencheck

integ-telemetry_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry

integ-pilot-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-istiodremote

integ-security-multicluster_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-multicluster

integ-pilot-multicluster_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-multicluster

macbuildcheck_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test macbuildcheck

integ-helm_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-helm

integ-pilot-istiodremote-mc_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-istiodremote-mc

integ-security_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security

integ-ambient_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ambient

unit-tests_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test unit-tests

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

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test release-notes

unit-tests-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test unit-tests-arm64

lint_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test lint

integ-basic-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-basic-arm64

integ-cni_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-cni

integ-ipv6_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ipv6

integ-telemetry-discovery_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-discovery

integ-pilot_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot

integ-distroless_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-distroless

integ-ds_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ds

integ-security-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-istiodremote

gencheck_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test gencheck

integ-telemetry_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry

integ-pilot-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-istiodremote

integ-security-multicluster_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-multicluster

integ-pilot-multicluster_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-multicluster

macbuildcheck_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test macbuildcheck

integ-helm_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-helm

integ-pilot-istiodremote-mc_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-istiodremote-mc

integ-security_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security

integ-ambient_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ambient

unit-tests_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test unit-tests

release-test_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test release-test

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-sigs/prow repository. I understand the commands that are listed here.

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test release-notes

unit-tests-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test unit-tests-arm64

lint_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test lint

integ-basic-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-basic-arm64

integ-cni_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-cni

integ-ipv6_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ipv6

integ-telemetry-discovery_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-discovery

integ-pilot_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot

integ-distroless_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-distroless

integ-ds_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ds

integ-security-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-istiodremote

gencheck_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test gencheck

integ-telemetry_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry

integ-pilot-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-istiodremote

integ-security-multicluster_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-multicluster

integ-pilot-multicluster_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-multicluster

macbuildcheck_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test macbuildcheck

integ-helm_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-helm

integ-pilot-istiodremote-mc_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-istiodremote-mc

integ-security_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security

integ-ambient_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ambient

unit-tests_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test unit-tests

release-test_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test release-test

integ-telemetry-mc_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-mc

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

wait for #53115?

I think so

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

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-basic-arm64

integ-cni_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-cni

integ-ipv6_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ipv6

integ-telemetry-discovery_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-discovery

integ-pilot_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot

integ-distroless_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-distroless

integ-ds_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ds

integ-security-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-istiodremote

integ-telemetry-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-istiodremote

integ-telemetry_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry

integ-pilot-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-istiodremote

integ-security-multicluster_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-multicluster

integ-pilot-multicluster_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-multicluster

integ-helm_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-helm

integ-pilot-istiodremote-mc_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-istiodremote-mc

integ-security_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security

integ-ambient_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ambient

unit-tests_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test unit-tests

release-test_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test release-test

integ-telemetry-mc_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-mc

lint_istio
216dd3ef177ff9650a572c6fe1fe94d515c7c8e2
link
true
/test lint

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

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

Test name
Commit
Details
Required
Rerun command

integ-cni_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-cni

integ-ipv6_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ipv6

integ-pilot_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot

integ-ds_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-ds

integ-security-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-istiodremote

integ-pilot-istiodremote_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-istiodremote

integ-security-multicluster_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security-multicluster

integ-pilot-multicluster_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-multicluster

integ-pilot-istiodremote-mc_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-pilot-istiodremote-mc

integ-security_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-security

release-test_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test release-test

integ-telemetry-mc_istio
aedc6acedc8710a4cc49afbae63eecdbeb3e8bfe
link
true
/test integ-telemetry-mc

lint_istio
216dd3ef177ff9650a572c6fe1fe94d515c7c8e2
link
true
/test lint

integ-ambient_istio
216dd3ef177ff9650a572c6fe1fe94d515c7c8e2
link
true
/test integ-ambient

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-sigs/prow repository. I understand the commands that are listed here.

authors: Kuromesi istio-testing zirain


text:
[release-1.22] use upstream_cluster_raw for json access log

This is an automated cherry-pick of #54224

@zirain i think we may need to revert this; I scrolled up and I don't see UPSTREAM_CLUSTER_RAW in the text log format. So this change may not be in 1.22 yet

authors: istio-testing keithmattix


text:
update gcp deployment for 1.0.1

update gcp deployment for 1.0.1 release
this needs to be merged as soon as 1.0,1 is released

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

Needs approval from an approver in each of these files:

install/OWNERS

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

this needs to be merged as soon as 1.0,1 is released. So hold until then
/hold

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

Test name
Commit
Details
Rerun command

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

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

/test istio-pilot-e2e-envoyv2-v1alpha3

authors: istio-testing rkpagadala


text:
Fix helper script for extending the mesh to VMs

It was broken by #7694.

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

Needs approval from an approver in each of these files:

install/OWNERS

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

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

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

/assign @ostromart

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

Needs approval from an approver in each of these files:

install/OWNERS [rshriram]

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
5b53106999d1a199823f3fded7f82769b9272e78
link
/test istio-unit-tests

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

/test istio-unit-tests

@MrTrustor: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test istio-unit-tests

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

/ok-to-test

authors: MrTrustor fisherxu istio-testing


text:
Managed VM platform

Root issue for constructing a managed VM platform support:

[ ] service model compatibility for managed VMs
[ ] service registry and event handling for VMs
[ ] docker-based sidecar for VMs
[ ] traffic capture for VMs
[ ] discovery services for VMs

This is a duplicate of #333 . The solution is pretty much the same. And finally, lets not pollute the VMs with docker unless absolutely necessary.

No, this is specifically for GCE environment. I mentioned docker to ease deployment (dealing with DEBs and RPM is too much for beta)

Dude, VMs is the same whether it's GCE or AWS or Bluemix softlayer.
On Fri, May 19, 2017 at 7:31 PM Kuat notifications@github.com wrote:

No, this is specifically for GCE environment. I mentioned docker to ease
deployment (dealing with DEBs and RPM is too much for beta)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/istio/manager/issues/797#issuecomment-302832948, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AH0qd0gNDrs-N6Hrd1fWzf3qL5bXn0HHks5r7iZAgaJpZM4NhGsF
.

--
~shriram

source: gharchive/issue

authors: kyessenov rshriram

repo: istio/manager


text:
Add build infra for proto to Go structs

This adds infra required to generate Go structs from the IstioContolPlane proto.

Created https://github.com/istio/istio/issues/14960 to track the deepcopy issue.

Other than my comment above, it lgtm, I'd go ahead and merge this first because most of the other PRs are depending on these generated structs.

Probably the way to go is to have a docker based build as we do in istio/api. I'm part way to having that working but it needs a little more work. Have created https://github.com/istio/istio/issues/15017 to track it. Anyway, it's good enough to use the checked in generated go structs for now changes will not be so large for a while.
If you could approve, mergify will merge - thanks.

authors: martonsereg ostromart

repo: istio/operator

license_source: bigquery


text:
Improvements of the Documentation Generator

Methods arguments are added to the word document.
BaseObjects are added to the word document.
MultiStateValueItemTypes are described in the document.
Example sources for the document generation were added.

Execute it as following:
    - npm install
    - sudo npm cache clean -f
    - sudo npm install -g n
    - sudo npm install -g typescript
    - sudo n latest
    - node -v
    - tsc
    - node src/main.js -n example/Opc.Ua.Example.NodeSet2.xml -t example/opcua_example_template.docx -d example/multistatevaluediscretetype_example_description.xlsx

license: MIT


text:
Zuweisung von anderen Objekten frontendseitig möglich

Describe the bug
Es ist möglich verschiendeste HTML-Objekte, wie z.B.: die Links im Navigation-Drawer auf die Praktikumsstellen zuzuweisen. Dem User wird eine erfolgreiche Zuweisung als Antwort zurückgegeben.
Wenn man diese Zuweisung wieder entfernt, dann wird eine NWK ohne vorhande Daten in die Liste der NWKs eingefügt.
Nach dem Reloaden der Seite ist das Objekt wieder weg.
To Reproduce
Steps to reproduce the behavior:

Gehe zu 'Zuweisung'
Öffene den Navigation-Drawer
Ziehe ein Element aus dem Navigation-Drawer
Drope es auf eine Praktikumsstelle ohne zugewiesene NWK
Eine "leere NWK" wurde erfolgreich der Praktikumssstelle zugewiesen
Siehe den ersten Fehler
Entferne die Zuweisung
Sieh, dass ein Element der NWK-Liste zugewiesen wurde.
Siehe den weiteren Fehler

Expected behavior
Es sollte nicht möglich sein etwas Anderes als eine NWK auf eine Praktikumsstelle zuweisen zu können.
Screenshots

[ ] Nwk Store aus Drag-n-Drop Lösung eliminieren
[ ] DragEvent für DnD Datenübermittlung nutzen
[ ] filter in drop function, um nur korrekte daten durchzulassen

authors: Tuckerle danielnwz

repo: it-at-m/Praktikumsplaner


text:
[Maintenance] Stack update: Add configuration for pgAdmin automatic db connection

Relevant component
No response
Problem description (optional)
See https://github.com/it-at-m/refarch-templates/issues/323
Desired solution
https://github.com/it-at-m/refarch-templates/pull/324
Considered alternatives (optional)
No response
Additional context (optional)
No response
No duplicate

[X] I confirm that this issue is not a duplicate

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Doesn't contain pgAdmin as not synced with refarch-tempaltes anymore.

authors: devtobi simonhir

repo: it-at-m/refarch


text:
[Order form] A pop-up 'Welcome to UBS...' appears twice at the zero step of the 'Order form'

Environment: Windows 10 Pro 20H2
Google Chrome 113.0.5672.93
Reproducible: sometimes
Build found: 23.08.2023
Preconditions

User is logged in https://www.greencity.social/#/greenCity

Steps to reproduce

Click on the icon in the upper right corner
Click on the 'UBS-USER'
Click on the 'New order' button
Chose your location (e.g. Kyiv, Kyiv Oblast)
Click on the 'Continue' button

Actual result
A pop-up 'Welcome to UBS...' with a drop-down to select a location appears
Expected result
The system redirects the user to the first step of the 'Order form'
User story https://github.com/ita-social-projects/GreenCity/issues/3033
Labels to be added
"Bug", Priority ("Medium"), Severity ("Minor"), Type ("UI")
https://github.com/ita-social-projects/GreenCity/assets/131760121/a6a9f0a9-8445-4c68-90e3-14c08eb39cdc

Need to fix, actual result after fixing- the same as before fixing.

authors: HalynaChornevych Priadkohrystyna

repo: ita-social-projects/GreenCity


text:
[API/GET/club-registration] Missed information in 'body' section when valid manager is specified

Environment: Windows 10 Pro Version 22H2
Version 120.0.6099.130 (Official Build) (64-bit)
Reproducible: always
Build found:
front 2024-01-04 d5b9ee
back 2024-01-04 7dd789
Preconditions

Site http://speak-ukrainian.eastus2.cloudapp.azure.com/dev/ is opened.
Method: GET
Endpoint: /api/club-registration/{managerId}
Token in Postman is received (as for User Manager)

Steps to reproduce

Go to Postman
Create GET request
Use valid value (e.g. 1) instead of {managerId}
Click 'SEND' button

Actual result
'Body' section doesn't contain any information in square brackets in response.

Postconditions
The results should look like the following example:

When choosing for example Manager ID 11, then 'body' response is showing full information

repo: ita-social-projects/TeachUA


text:
Purtroppo non è stato possibile accedere al servizio

Buongiorno,
Non molto tempo fa avevo un normale accesso al portale, ora appare questo messaggio di errore:
https://www.anagrafenazionale.interno.it/servizi-al-cittadino/
Purtroppo non è stato possibile accedere al servizio, ti consigliamo di rivolgerti al tuo comune di residenza (o di iscrizione all'AIRE) per maggiori informazioni, al fine di sanare l'anomalia nei tuoi dati che non ci ha consentito di individuare in modo univoco la tua scheda anagrafica.
Torna alla homepage
Cosa devo  fare?
Marcos Antonio Orlandini Fedato
codice fiscale rlnmc
Brasile

salve se è lei la persona nata nel 1987 - le consiglio di rivolgersi presso il suo comune di competenza - quello che lo ha iscritto all' AIRE, perché la sua scheda in Anpr non c'è.  - si chiude la issue  -

authors: cmigliardi marcosaof

repo: italia/anpr


text:
Problemi con il cambio di residenza

Buongiorno,
sto provando a completare la procedura di cambio residenza sul portale dell'anagrafe di stato dal comune di San Giuliano Milanese a quello di Napoli. Non appena provo a fare accesso con SPID  al portale, appare questo messaggio di errore.
"Purtroppo non è stato possibile accedere al servizio, ti consigliamo di rivolgerti al tuo comune di residenza (o di iscrizione all'AIRE) per maggiori informazioni, al fine di sanare l'anomalia nei tuoi dati che non ci ha consentito di individuare in modo univoco la tua scheda anagrafica."
Potreste darmi supporto per risolvere il problema?
Grazie
Giancarlo

Buonasera,
come suggerito nel messaggio di errore, deve rivolgersi al suo comune di residenza (o di iscrizione all'AIRE) per verificare se i sui dati sono correttamente registrati nella sua scheda anagrafica.
Assistenza ANPR


text:
[webapp]: Estratto per riassunto nascita

Ambiente
produzione
Provenienza segnalazione
Comune
Riferimenti operatore/comune
Grottaferrata
Data del test (yyyy-mm-dd)
No response
Caso d'uso
No response
Descrivi il problema
Negli estratti per riassunto di nascita si segnala la mancanza dello stato estero di nascita

Come riprodurre il problema
No response

Con la patch 1.34.5 è stata corretta la segnalazione. Chiudiamo la issue

repo: italia/ansc


text:
Citazioni: problema padding ed elemento decorativo dark

Versione di Bootstrap Italia
v2.0.2

Comportamento atteso
Il testo non dovrebbe essere attaccato al bordo, nel caso di card dark non dovrebbe essere visualizzato l'elemento decorativo di colore ciano.

Comportamento attuale
Quando si usa l'opzione blockquote-simple con text-end il testo della citazione è attaccato all'elemento grafico decorativo della citazione.

Quando si usa l'opzione blockquote-card dark con text-end viene visualizzato un elemento decorativo di colore ciano che non dovrebbe esserci

Ciao

@arturu fixata da @OscarBresolin e rilasciata nuova versione 2.0.3

authors: arturu astagi

repo: italia/bootstrap-italia


text:
Richiesta di validazione dei metadati - Comune di Castel Mella

Buongiorno,
per conto del Comune si richiede la verifica e il deploy dei metadati esposti all'URL:
https://sportellotelematico.comune.castelmella.bs.it/simplesaml/module.php/saml/sp/metadata.php/castelmella

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

authors: AntonioGiovanniSchiavone globogis

repo: italia/spid


text:
Update README.md

enhancers

please have a look at the CONTRIBUTING.MD before proposing a new company. You cannot modify the README file directly.

replaced with another pr

authors: edoardocostantinidev marcopestrin

repo: italiaremote/awesome-italia-remote


text:
Adaptive lighting

Continuation of #60 to add support for Adaptive Lighting (#30).

Rebased #60 on top of master (no bigger changes where necessary, only some smaller conflicts to the configuration schema and to tests).
Made Adaptive Lighting opt-in (enable by setting defaults.adaptive_lighting.enabled to true).
Generated documentation.

I've been testing this with Homebridge v1.5.0, z2m v1.26.0, and three Hue lights.
One oddity that I've found is that HomeKit does not seem to respect disabling adaptive lighting for a light once it has been enabled the first time, it's still unclear if there is anything I can do to support this.

I haven't reviewed everything yet. I'll hope I have time for that soon.
One thing I did already notice: the adaptive lighting configuration should probably be a converter specific configuration as was introduced in #458.

Quite enthousiat about this new feature ! Let me know how to try when it will ne merged !

@zegl Did you see my previous comment?
Also curious if you have an update with regards to:

One oddity that I've found is that HomeKit does not seem to respect disabling adaptive lighting for a light once it has been enabled the first time, it's still unclear if there is anything I can do to support this.

@itavero Thanks for your ping!

the adaptive lighting configuration should probably be a converter specific configuration

Yes, I looked a bit into this but didn't code anything. It makes sense and seems to be a straightforward change to make. I'll get around to work on it soon. :-)
I have no new knowledge with regards to the disabling of adaptive lightning. My first thought was that Apple might not support it too well. I'm guessing that it's rare for non-HomeBridge devices to drop support for adaptive lighting.

Any updates? Still waiting. Would love see this happening before the holidays

Hey. I've now rebased and reworked this PR to incorporate the earlier feedback. Would appreciate another review and hear your thoughts.
Changes since 283d5e75c70563e2816b6430701f954735e5e569 (last push):

Rebased on top of v1.9.2
Changed the configuration to be a "converter" configuration
Removed the documentation generation changes. If this gets merged, we can work on update the generated device documentation afterwards.
Removed the configuration for using transitions (which caused light "flickering" on my Hue lights) and the minimum temperature changes (unclear how necessary this limitation was). If these configurations are needed for some setups, they can always be added again later.
Removed the code to prevent enabling adaptive lighting if using Homebridge versions earlier than v1.3.0-beta.46. (Adaptive Lighting is disabled by default, so this should not be a problem).

Thanks again for your work on this. I'll try to have another peek in the coming days.

Took me a bit longer to get to this, but at least of got the easy To Do items taken care of.
I'll start looking into the remarks I've added earlier now, as well as the automated tests.
Again, no promises on when it will be finished, my 3 month old son is kinda the boss of my spare time now. 👶

The documentation for AdaptiveLightingController mentions:

Detecting changes on the lightbulb side: Any manual change to ColorTemperature or Hue/Saturation is considered as a signal to turn AdaptiveLighting off. In order to notify the AdaptiveLightingController of such an event happening OUTSIDE of HomeKit you must call disableAdaptiveLighting manually!

This is currently not implemented. I'll see if there is a good way to detect this.
Additionally, it also mentions:

When using Hue/Saturation: When using Hue/Saturation in combination with the ColorTemperature characteristic you need to update the respective other in a particular way depending on if being in "color mode" or "color temperature mode". When a write happens to Hue/Saturation characteristic in is advised to set the internal value of the ColorTemperature to the minimal (NOT RAISING an event). When a write happens to the ColorTemperature characteristic just MUST convert to a proper representation in hue and saturation values, with RAISING an event. As noted above you MUST NOT call the setValue method for this, as this will be considered a write to the characteristic and will turn off AdaptiveLighting. Instead, you should use updateValue for this. You can and SHOULD use the supplied utility method colorTemperatureToHueAndSaturation for converting mired to hue and saturation values.

This is also not implemented yet.

Added some code that should handle the first point mentioned (regarding disabling Adaptive Lighting when an external change is detected).
For the second point mentioned, I think this is similar to what is also done in the experimental feature COLOR_MODE.

I'll merge this for now, so I can make a prerelease. Based on the feedback from the community, we might have to make improvements in the future.

Wow, huge! Thanks for working on this and pushing it over the finish line! ❤
I'll update my installation from the homebaked version built on an earlier version of this PR to the latest release once ready.

And congrats on the baby!

Please add any feedback you might have to #590

authors: itavero lcsjandrey macfr76 zegl


text:
🛑 Impulso Humano is down

In 3c14ceb, Impulso Humano (https://impulsohumano.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Impulso Humano is back up in 35e9376 after 10 minutes.

repo: itbm-services/projects


text:
Allow to customize status line in terminal windows

Motivation

readonly, filename, modified... They're boring in terminal windows.
In there, I want to see other informations in the terminal.

Change point

Add a new configuration parameter g:lightline.terminal like g:lightline.active and g:lightline.inactive
Change a function lightline#statusline(inactive) that it can receive terminal parameter.
Hook a new event TerminalOpen to update lightline status.
Add new useful components, termtitle and buftype for terminal mode.

Customizing the statusline in terminal windows is currently available via component functions. The following configuration may be boring, but terminal is nothing but a buffer where buftype is terminal. Adding terminal as a special support target in lightline results into increasing number of special buffers support, help buffer, preview window, etc. As terminal windows can be easily detectable in user's configuration and component functions works well, I cannot accept your pull request.
let g:lightline = {
      \ 'active': {
      \   'left': [ [ 'mode', 'paste' ], [ 'readonly', 'filename', 'modified', 'terminalinfo' ] ],
      \ },
      \ 'component_function': {
      \   'filename': 'LightlineFilename',
      \   'modified': 'LightlineModified',
      \   'terminalinfo': 'LightlineTerminalInfo',
      \ },
      \ }

function! LightlineModified() abort
  return &buftype ==# 'terminal' ? '' : &modified ? '+' : &modifiable ? '' : '-'
endfunction

function! LightlineFilename() abort
  return &buftype ==# 'terminal' ? '' : expand('%:t') !=# '' ? expand('%:t') : '[No Name]'
endfunction

function! LightlineTerminalInfo() abort
  return &buftype ==# 'terminal' ? 'TERMINAL INFORMATION' : ''
endfunction

Adding terminal as a special support target in lightline results into increasing number of special buffers support, help buffer, preview window, etc.

I see. Thanks!

license: mit


text:
Show info box if a new version is available on GitHub

Resolves #2233
Note: our latest version 0.4.20.1 is not a valid semver version hence, I added a small logic which uses coerce to parse the version string. The resulting version of 0.4.20.1 will be 0.4.20.

bors r+

repo: itchysats/itchysats


text:
Introduce versionInfo in metrics CRD

Is your feature request related to a problem? Please describe the problem.
Currently, metric definitions are complicated due to two reasons

The use of interpolation for version information, which makes metric definitions complex to begin with.
The fact that the placeholders for interpolation are inside the metrics resource, and the variables used for substituting placeholders are inside the experiment resource, which makes interpolation not just complex, but really complicated.

Describe the feature/solution you'd like
Alter the definition of custom metrics as follows ... there will now be a single placeholder called ${elapsedTime}, which has nothing to do with a version. Conceptually, this is a far more easier definition to follow than having to link between two different resources and define complex interpolation logic.
apiVersion: iter8.tools/v2alpha2
kind: Metric
metadata:
  name: request-count
spec:
  description: A Prometheus example
  provider: prometheus
  versionInfo: # number of versions here need to match number of versions in the experiment object
  - params:
    - name: query
      value: >-
        sum(increase(revision_app_request_latencies_count{service_name='hello'}[${elapsedTime}s])) or on() vector(0)
    # alternatively, for POST queries, `params` above can be replaced with `body`
  - params:
    - name: query
      value: >-
        sum(increase(revision_app_request_latencies_count{service_name='hello-candidate'}[${elapsedTime}s])) or on() vector(0)
  type: Counter
  jqExpression: ".data.result[0].value[1] | tonumber"
  urlTemplate: http://myprometheusservice.com/api/v1

Alter the definition of mock metrics as follows ...
apiVersion: iter8.tools/v2alpha2
kind: Metric
metadata:
  name: request-count
spec:
  mock: true # this is now a boolean field
  versionInfo: # number of versions here need to match number of versions in the experiment object
  - level: "20.0"
  - level: "15.0"

Note: no changes are needed for builtin metrics due to #912
Note: versionInfo for metrics will be a list of versionDetail objects. This object has three optional  fields, namely,
params, body, and level. First two are for custom metrics, and the last one is for a mock metric.
Will this feature/solution bring new benefits for Iter8 users? What are they?
The above change effectively decouples metrics and experiment resources, apart from the basic requirement that the number of versions in the metrics object should equal the number of versions in the experiment object.
Making metrics and experiment objects self-contained in the above ways simplifies definition of both.
Does this issue require a design doc/discussion? If there is a link to the design document/discussions, please provide it below.
Yes, please see above.
How will this feature be tested?

[ ] Metrics tests need to pass (i.e., there will be equivalent of tests we have right now for current metrics).

How will this feature be documented?

[ ] iter8.tools documentation.

This seems like a good idea. But it means metrics are specific to versions. Where version is generated in a CI pipeline, the version may change on every use. Won't I have to define new metrics for every experiment?

Yes and no.

If metrics are named consistently, example hello and hello-candidate are names of baseline and candidate services respectively in the above example... in every experiment ... no changes are needed for metrics.

Otherwise, yes. Create metrics for an experiment everytime you create a new experiment. Even in this situation, note that, in HelmX and SimpleX experiments, metrics can be templated as part of Helm templates alongside the experiment resource, which again means, from the CI perspective, the only change is to the values file.

So, the additional complexity of creating metrics for each experiment happens only if:

You don't use HelmX
You don't use SimpleX
You choose to change the version name under which metrics are collected for every new version (instead of using more standardized names like baseline and candidate). Clearly, the latter will be the recommended best practice for metrics collection in the context of Iter8 experiments (since it will avoid the need to create metrics alongside experiments).

Note: This issue is now subsumed and superseded by #934

authors: kalantar sriumcp


text:
docs: rename dvc lock -> dvc freeze

Per https://github.com/iterative/dvc/pull/3915

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

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

things to take care of:

[ ] add redirects lock -> freeze (redirects.json)
[ ] rename in the prism dvc-commands.js
[ ] fix completion scripts
[ ] grep dvc lock - to make sure that we renamed it everywhere

@shcheklein Done.

Tests fail because they try to check links that are not yet deployed.

@efiop yep, it's a well know and unfortunate limitation, gonna fix this in #1000 /cc @casperdcl

Couple minor issues. Is this released though? Otherwise no rush no merge this, right? Thanks

@jorgeorpinel It is merged. I think current approach is to just merge 1.0 changes into master, no?

current approach is to just merge 1.0 changes into master, no?

I'm not sure. I thought we were timing all of these meaning just letting them be approved to merge them all at once when 1.0 is released.

@jorgeorpinel We have a mix of all of them right now. E.g. plots is from 1.0. It makes sense to continue merging.

Post moretm review/ questions @efiop:

What about phrase "always locked" used in the import(_url) cmd refs?
What about locked field in YAML files? Did it change to frozen? (Should it?) — mentioned in examples and DVC files & dirs guide
.dvc/lock, .dvc/tmp/lock, and .dvc/tmp/rwlock stay the same?
dvc show --locked ?

Thanks

@jorgeorpinel

What about phrase "always locked" used in the import(_url) cmd refs?

Oops, missed that one. https://github.com/iterative/dvc.org/pull/1404 Thank you! :pray:

What about locked field in YAML files? Did it change to frozen? (Should it?) — mentioned in examples and DVC files & dirs guide
I didn't touch that one because it will need to be removed/reworked for 1.0. I'll leave a comment in https://github.com/iterative/dvc.org/pull/1370/files , since it is already there.

.dvc/lock, .dvc/tmp/lock, and .dvc/tmp/rwlock stay the same?
Correct.

dvc show --locked ?
no such command in 1.0, dvc dag replaced it and didn't implement locked yet

Awesome.

.dvc/lock, .dvc/tmp/lock, and .dvc/tmp/rwlock stay the same?

@jorgeorpinel Just to clarify: .dvc/lock is no more, it has been moved to .dvc/tmp/lock. https://dvc.org/doc/user-guide/dvc-files-and-directories already reflects that.

authors: efiop jorgeorpinel shcheklein


text:
guide: Persisting experiments

Fixes #2736

Ping @iesahin let's prioritize iterating on this before your other PRs first please 🙂

committing experiments to Git

I like this one. It's explicit.
Otherwise, this goes back to https://github.com/iterative/dvc.org/pull/2845#pullrequestreview-773089561 a little
There we say "When your experiments are good enough to save or share, you may want to store them persistently as Git commits in your repository."
Are saving or sharing the only reasons to commit experiments to Git? Depending on that we can find a good title, I think.

Are saving or sharing the only reasons to commit experiments to Git?

p.s. and if so should this content be summarized a bit more into a single section of https://dvc.org/doc/user-guide/experiment-management/sharing-experiments instead?

What do you think about "retrieving experiments"? dvc exp apply and dvc exp branch are both about getting experiment results into a user's normal workflow (either their working directory or a branch of their Git repo).

@jorgeorpinel are you good here?

This seems ready @jorgeorpinel

authors: dberenbaum iesahin jorgeorpinel shcheklein


text:
lightning: Find a better way to handle next_step.

It was the DeviceStatsMonitor callback from Lightning! It tried to log every single validation step and really slowed the whole thing down.

We still need to figure out a better way of deciding when to call next_step in the lightning integration.
In other frameworks, the callbacks for integrations have a clear interface with events like on_epoch_end, but lightning Logger is a little messy because you only have access to log_metrics, and this can be called by other callbacks and at different paces.

tldr: Let's call next_step for train metrics but not for val metrics. A lot of what's below is for reference so I can remember how lightning logging works 😄 .
To clarify what's happening here, let's assume https://pytorch-lightning.readthedocs.io/en/stable/common/lightning_module.html#log is called with on_step=True and on_epoch=True. This is what will happen:

Lightning first iterates over all train batches for an epoch. By default, it will log every 50 train steps/batches.
Only after all train batches for an epoch have been run, then all val batches are run. By default, it will log every 1 step/batch.
After all train and val batches have been run, then val epoch metrics are logged (but the step is now the train step and not the val step), and finally the train epoch metrics are logged.

Example:

train size: 800
val size: 200
batch size: 10
epochs: 2

Lightning will log metrics with the following values:
step: 49, metrics: train_loss_step...
step: 99, metrics: train_loss_step...
...
step: 799, metrics: train_loss_step...
step: 0, metrics: val_loss_step...
step: 1, metrics: val_loss_step...
step: 2, metrics: val_loss_step...
...
step: 19, metrics: val_loss_step...
step: 999, metrics: val_loss_epoch...
step: 999, metrics: train_loss_epoch...
step: 1049, metrics: train_loss_step...
step: 1049, metrics: train_loss_step...
...
step: 1999, metrics: train_loss_step...
step: 1999, metrics: train_loss_step...
step: 20, metrics: val_loss_step...
step: 21, metrics: val_loss_step...
...
step: 39, metrics: val_loss_step...
step: 1999, metrics: train_loss_step...
step: 1999, metrics: train_loss_step...

This all very flexible and configurable, but the default setup means no val metrics will be recorded for a long time, followed by a lot of val metrics, each with their own step count unrelated to the train steps.
We could call next_step when we see the epoch metric get updated, which would get us close to what we do with other frameworks like keras where we currently only log at the end of each epoch. I think it would be better to try to respect the logging configuration so that, for example, updates can get shown more than once per epoch. We could instead try to call next_step for train metrics but not val metrics. This seems closer to the lightning philosophy, where Trainer.log_every_n_steps controls when logging happens but is completely separate from validation logging, which is instead controlled by Trainer.val_check_interval and Trainer.check_val_every_n_epoch (see https://pytorch-lightning.readthedocs.io/en/stable/common/trainer.html#trainer-class-api).

We could instead try to call next_step for train metrics but not val metrics.

I missed that there's no way to differentiate between them except by however the user decides to name them.

We could call next_step when we see the epoch metric get updated

I think this is the best we can do.

authors: daavoo dberenbaum

repo: iterative/dvclive


text:
VW MEB Voltage or current changed with car software  3.2 exworks

VW MEB Voltage or current changed with car software  3.2 exworks.
On my ID.4 2021 after 3.2 got installed in VW maintenance used power calculations are way off in EVNotify. Since if I recall ABRP and EVNotify both use @spot2000 PIDS and math this might be a problem for your users driving any MEB car and using Bluetooth BLE.

3.2 has multi frame messages for current. This is already handled correctly in ABRP

The PID in question nor the calculation hasn't changed in this repository in two years. So the data presented by this repository is incorrect?

It's not the pid or calculation that changed, but the way the data is returned from the car. Also these files are not always up to date with the latest version we have internally.

Nice to know, I know how multiframe responses are parsed so maybe I can get EVNotify fixed to restore legacy BT support to ABRP.

authors: MattiJarvinen SamuelBrucksch

repo: iternio/ev-obd-pids


text:
a11y revamp: Pharos Buttons

This change: (check at least one)

[x] Adds a new feature
[ ] Fixes a bug
[ ] Improves maintainability
[ ] Improves documentation
[ ] Is a release activity

Is this a breaking change? (check one)

[x] Yes
[ ] No

Is the: (complete all)

[x] Title of this pull request clear, concise, and indicative of the issue number it addresses, if any?
[ ] Test suite(s) passing?
[ ] Code coverage maximal?
[x] Changeset added?
[ ] Component status page up to date?

What does this change address?
This updates the Pharos Button to allow consumers to pass in attributes (listed below) following a specific naming convention (a11y-) that assign the appropriate ARIA attribute to the inner <button> element. This addresses the issues with custom web components and the shadow DOM and use of ARIA not being properly being parsed by assistive technologies.

a11y-label = aria-label (String)
a11y-expanded = aria-expanded (true, false, undefined (default))
a11y-pressed = aria-pressed (true, false, mixed, undefined (default))
a11y-haspopup = aria-haspopup (true, menu, listbox, tree, grid, dialog, false (default))

Linked issue #642
How does this change work?
Consumers can add these attributes along with the proper value to the Pharos Button and the appropriate ARIA attribute will be added to the underlying <button> element.
Additional context
This is a breaking change. The previous versions of Pharos has the label attribute that would apply the aria-label attribute to the button. This will need to be updated. Additionally, all uses of ARIA listed above will need to be updated accordingly.
This is an effort to address ADR #0009 (#559)

don't see any reason verify test would be failing now... triggered a rerun just to check

Let's figure out to make sure the diff here is up to date, free of conflicts, and doesn't show others' changes—hard to review until then.

There're a few linting warnings/errors that I think I'm confused about as to why they're arising here in your PR. Several are readily fixed, which I already did but accidentally pushed as a new branch rather than back to your fork; I'll fix that, but ultimately there's a test that might need a closer look that I couldn't fix in the couple of minutes I spent.

There're a few linting warnings/errors that I think I'm confused about as to why they're arising here in your PR. Several are readily fixed, which I already did but accidentally pushed as a new branch rather than back to your fork; I'll fix that, but ultimately there's a test that might need a closer look that I couldn't fix in the couple of minutes I spent.

It looks like the one error also appears in the release/14.0.0 branch, the one related to the any type. Not sure what's what there. But did manage to clean up the earlier errors referencing unknown ARIA after removing the aria-description bits.

the one related to the any type

Yeah, that's the one. If that's the case, let's get this merged in after I push up what I've fixed, since it's not new to this change, and we can attack that error on a different timeline.

authors: chrisjbrown daneah sirrah-tam

repo: ithaka/pharos


text:
Firmware update

Firmware update patched vulnerabilities and require MessageId, TimeStamp, and Sign values to be different each time.  A unique key is used when creating the values that comes from Meross when logging in.   You can get the key by using this script
https://github.com/bapirex/meross-api/blob/master/login.py
I haven't been able to test this on previous firmware versions since I already updated and don't have another device with an older version.

@coKaliszewski sorry for the delay will try and test this out this week

@coKaliszewski can you rebase and see if https://github.com/ithinkdancan/hubitat-meross/pull/5 covered the firmware update?

authors: coKaliszewski ithinkdancan

repo: ithinkdancan/hubitat-meross


text:
Enable readonly-access to AttributesIndex from multiple threads.

Enable readonly-access to AttributesIndex from multiplethreads. This would fix issues related to #53 and #54 and improve performance.

This is more related to:
https://github.com/itinero/reminiscence

repo: itinero/routing


text:
Add button to disable app

Currently, it's not possible to disable the scanning. There should be a button either in the application or in the app's notification to turn off the app.

Idea:
maybe something like "At home". When you are at home you are most like in safe environment and you dont have to scan and advertise itself because contact with infected people is very unlikely (except family).

When I was thinking about this, I came to the conclusion that this may not be the best way to go about it.
Reasons: When I am at home and get a parcel delivered, I want the tracing to be active should the postman turn out to be infected. However it is unlikely that I think to turn it on in this case.
I guess it would be better to allow the user to exclude the upload of certain ids that are only seen by people he does not want to see he his sick, like his neighbours. But then again: Do you really want your neighbour not to know that there is a covid infection in the house?

I would maybe add a geofence option or a disable for x hours button since probably many people would forget to enable it later on again.

authors: ann0see assert-not-singularity chegewara dwt

repo: ito-org/Android-App


text:
Syntax Question

I've been reading here to try and decode how to create a grammar to parse some text.
I see here your use you use ~ but I can't quite figure out what that is for. I think it means take the entire string up to <.
Here is an example of what I am trying to parse:
title: This is a tile of this document

participant name as "Some friendly name"
participant name1 as "Some friendly name1"

The keywork title has a string that is terminated by \n.
The keywork participant has two parts where the second is optional.
Do you have any documentation that defines the built in types like QuotedString and what the ~ is used for?

I found this answer which looks pretty easy to map to what I need. Looks like I don't need the ~ char.

README.md has been updated which contains sufficient information for this issue.

repo: itod/pegkit


text:
feat(style): 添加选择的 hover 样式

Hi~
我加了一些选择菜单 hover 的样式，增强下网页的交互细节。

感谢 pull！
添加 hover 会导致手机端上点选交互和 PC 不统一，不是适合这个项目的设计

噢好的，明白

authors: GlintonLiao itorr

repo: itorr/china-ex


text:
Keycloak reports Invalid parameter: id_token_hint during logout

Sometimes (usually when the user is already logged in for a while) during logout Keycloak reports Invalid parameter: id_token_hint and does not redirect back to the application again, leaving the user at an error page where no meaningful link is shown.
Is this a bug? How could this be avoided?

When the user session is expired and cannot be renewed, the user session will be locked out. The error you referenced is a hint that there is no client side id_token, but you are using a post logout redirect.
Please check if you haven't accidentially overwritten the exposeIdToken with false and are still using the post logout redirect.
The next version will also change the error behavior to hide most of the errors from the user and instead clearing the session and redirecting to the login page.

You can already try the new behavior in 1.0.0-beta.1.

authors: itpropro patrsc

repo: itpropro/nuxt-oidc-auth


text:
TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/58606

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.


text:
HDR enabling in Windows but not selectable in games.

HDR is working on the desktop perfectly, but for some reason any game launched isn't seeing it. I've tried two different clients to the same effect. Weirdly, Windows offers Auto HDR if the game is known to support it which works perfectly well.

To make it clearer, RE2 for example won't be able to select, Dead Space Remake on the other hand is able to be selected.

Seeing the same behavior with RE2 in particular - not detecting the display as HDR. Windows pops up "auto HDR" and everything when the game is launched, but nothing. Using the Windows 11 HDR files with W11 23H2.

Was the IDD monitor set as the primary display?  If not, try that!
On Wed, Dec 27, 2023, 3:46 PM Porkchopp @.***> wrote:

Seeing the same behavior with RE2 in particular - not detecting the
display as HDR. Windows pops up "auto HDR" and everything when the game is
launched, but nothing. Using the Windows 11 HDR files with W11 23H2.
—
Reply to this email directly, view it on GitHub
https://github.com/itsmikethetech/Virtual-Display-Driver/issues/15#issuecomment-1870696304,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAERAHPDPVPKKLD5ZJJM2TDYLSXMFAVCNFSM6AAAAABAXRQBM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZQGY4TMMZQGQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>

Was the IDD monitor set as the primary display? If not, try that!

Yes, I believe so. I have a script running in Sunshine ahead of launching that enables and makes primary the virtual display.
I should note that I have a LG C2 locally attached that has zero HDR issues. I have not tried streaming with that as the display to see if that solves the issue (to confirm that the virtual display is the problem, not moonlight/Sunshine), so I will give that a shot.

mind sharing the script please? i need it as well running hyper-v due to a bug in sunshine-moonlight which disconnects me first time when attempting connection. thank you!

I use a tweaked version of what is described here:
https://www.reddit.com/r/MoonlightStreaming/comments/12fxk2v/stream_4k_without_any_screen/
EnableForStream.bat:
start /wait c:\multimonitortool\multimonitortool.exe /SetMonitors "Name=\\.\DISPLAY5 BitsPerPixel=32 Width=3840 Height=2160 DisplayFlags=0 DisplayFrequency=60 DisplayOrientation=0 PositionX=0 PositionY=0

start /wait c:\multimonitortool\multimonitortool.exe /SetPrimary \\.\DISPLAY5

DisableForStream.bat:
start /wait c:\multimonitortool\multimonitortool.exe /SetPrimary \\.\DISPLAY3
start /wait c:\multimonitortool\multimonitortool.exe /disable \\.\DISPLAY5

I haven't used moonlight more than a time or two with this setup, and previously had issues with a ready-made script that did not revert properly, but so far so good with this.

So I'm in the same boat.
My problem, the game Mortal Kombat 11 does not let me select HDR on the settings page
My conf.
Client
Win11@23H2 with HDR enabled connected to a Samsung Q85R TV with HDR ON
Graphic Card Nvidia 1030
CPU Ryzen 5 5600g
Host
Win11@23H2 with HDR enabled connected to this Video Driver
Graphic Card RTX4070
CPU 12600KF
Sunshine
Default values
Moonlight
HDR experimental enabled and showing
Game runs installed locally on the client machine with HDR ON
Need to test if it runs with HDR ON on HOST PC but I think it will

I made it's primary, but it didn't help. My game where I don't see it is RDR2

Hi, I'm having the same problem with Doom Eternal. HDR on windows works correctly, and some games work too (Devil May Cry, Death Stranding). Auto HDR also works, but some titles like Doom Eternal say that the display don't support HDR when enabling it.
The virtual display is the only one enabled and set to primary.

Since I don't have  any of those game or a rig to test em on, and then the "might work depending o game" gives me the idea, that those games might need a certified hdr connection, which this driver doesn't have at the moment and i'm guessing won't have by default in the future. But long term goals are to be able to import EDID from a display and use it for the base configuration, hopefully without recompilation.

@zjoasan thank you for your response. At least good to know that currently we do everything correct

I made it's primary, but it didn't help. My game where I don't see it is RDR2

try set game graphic API to DirectX

I'm having the same problem here, HDR is enabled in Windows / Moonlight, and it works great in (for example) Hogwarts Legacy, Ori & The Will of the Wisps. But in Tetris Effect: Connected, or Assassin's Creed Origins, the option is greyed out. In all cases, the VDD monitor is the only active monitor (Sunshine disconnects my main monitor), and the game is set to full screen.
Any ideas on why it works in some games and not others? Thanks!

Yes! Some games use calls to applications such as Nvidia control panel in order to control HDR configuration or even check of its existence, since the virtual display driver doesn't take a physical port on the GPU, therefore cannot retrieve HDR status for some games! The games will need to be converted to allow for DirectX HDR, and even then, no guarantee it will work!

Yes! Some games use calls to applications such as Nvidia control panel in order to control HDR configuration or even check of its existence, since the virtual display driver doesn't take a physical port on the GPU, therefore cannot retrieve HDR status for some games! The games will need to be converted to allow for DirectX HDR, and even then, no guarantee it will work!

Ah okay. So there's nothing I can do myself then, right? Thanks for the explanation

I mean, not really, other than you can try the things mentioned above. But as of right now, that's about it

authors: Experien1985 MwenDavo Porkchopp WoundedBum bitedxh bud3699 nhac-lly philhzss roshkins vladimir-fsh zjoasan

repo: itsmikethetech/Virtual-Display-Driver


text:
Not working - Payload structure changed

I see that they introduced the 'ExecuteQuery' and 'FindResultDataByJob', but I'm not sure what functions to replace (query_result_id, query_result, job_result) or if now one of them is not needed anymore.

Did anybody find a solution?

repo: itzmestar/duneanalytics


text:
Dynamic Bullet/Numbered List

This may be a more general Mail Merge question, but I want to have a bullet/numbered list in my template and then pass a list of items to be included in that list as part of the mail merge. Do you know if that is possible with Word Mail Merge? If so, is it possible with this library? If so, could you point me to the relevant code please?
Thank you.

Not sure if this is possible with Word, and I am pretty sure it is not possible with docx-mailmerge. But just to be sure, you would want a bullet list to be just like a table row.
Have you tried to make a table of one row and one column, hide the margins, and inside the one cell add the bullet/numbered list with the mailmerge code. Then, you can use the merge_table feature or just give the list of values for the mailmerge keyword and use the merge_templates. I don't know if it will work, but it's worth a try.
If you provide a sample docx and python code I can give it a try myself.

Thank you for the quick response. I did try the table implementation and it did work as expected. I was hoping to avoid using tables for formatting because that can be confusing to the user if they want to edit the resulting merged document. However, I decided to change the format of my document and make use of more columns in that table. You can consider this resolved.
As a side note, I also attempted merge_templates but it copied the entire page for each item in the list.

You most probably used the merge_templates wrong, like this:
document.merge_templates([
{'field1': "Foo"},
{'field1': "Bar"},
], separator='page_break')
Each dictionary is a copy of the entire document. What you want is that 'field1' is a list instead of just one value, like this:
document.merge_templates([
{'field1': ["Doc1 Foo", "Doc1 Bar"], 'field_outside_list': 'value document1'},
{'field1': ["Doc2 Foo", "Doc2 Bar", "Doc2 John"], 'field_outside_list': 'value document2'},
], separator='page_break')
This will create a 2 page document, each page containing the table with the rows for the field1.
If you only need one document, use merge instead of merge_templates or just use one dict in the array.

authors: iulica keith-gray-powereng

repo: iulica/docx-mailmerge


text:
Obsidian freezes completely if a notification daemon is not running (Linux)

Describe the bug
As the title states, on task switch if a notification daemon is not running, raising a libnotify error in the console. I'm currently running arch linux.
To Reproduce
Steps to reproduce the behavior:

Create a new task
Ensure that no notification daemon is running
When the task begins obsidian becomes completely unresponsive (nor closing the application works nor SIGTERM works, only SIGKILL)

Expected behavior
Either throw an error about the daemon not running or ignore the issue
Additional context
Plugin version: 0.12.2
Obsidian version: 1.4.16-1
Also the GUI isn't frozen, IE the cursor blinks, but nothing really responds
Obviously starting a daemon like Dunst fixes the problem, but it took me a while to realize that was the issue.

Hello, @ErenKyojin,
Unfortunately, I don't have a Linux system at hand to test and fix this. A pull-request from a person with Linux would be awesome.
In the meantime, did you try to just turn off the notification feature?

Unfortunately, I don't have a Linux system at hand to test and fix this. A pull-request from a person with Linux would be awesome.
I can try to look into this as soon as i have some free time

In the meantime, did you try to just turn off the notification feature?
Just tried it and this also fixes the issue.

Also thank you for the fast respone!

authors: ErenKyojin ivan-lednev

repo: ivan-lednev/obsidian-day-planner


text:
Coinslot was cancelled

mga boss ano po kaya issue pag ganito. may error kac Coinslot was Cancelled

@Wawatop alisin mo sa settings yung clear pin at ilipat mo ng pin yung coinSlotPin. Baka may issue na nodeMcu mo, same sakin yan before.

authors: MeeeMaaaaw Wawatop


text:
Added Codacy badge & Revive linting

Related to https://github.com/iver-wharf/iver-wharf.github.io/issues/47

Added Codacy badge & Revive linting
Fixed minor naming lint issues

I'm not touching the "exported" linting issues that Codacy is complaining about in this PR. I'll fix that in a different PR

repo: iver-wharf/wharf-provider-gitlab


text:
🛑 21Eurkon is down

In df59815, 21Eurkon (https://blog.eurkon.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 21Eurkon is back up in 2c1b9a2 after 29 minutes.

repo: iwyang/check


text:
🛑 21Eurkon is down

In e354123, 21Eurkon (https://blog.eurkon.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 21Eurkon is back up in 127b6f8 after 11 minutes.