make dns record ttl configurable

If dns capture is enabled, different scenarios have different requirements for dns recording ttl, So making this configurable.

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[ ] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

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

Test name
Commit
Details
Rerun command

release-notes_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test release-notes_istio

lint_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test release-notes_istio

lint_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test release-notes_istio

lint_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test lint_istio

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test release-notes_istio

lint_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test lint_istio

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test lint_istio

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test lint_istio

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test lint_istio

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test lint_istio

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test lint_istio

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test lint_istio

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test lint_istio

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test lint_istio

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test lint_istio

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test lint_istio

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test lint_istio

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test lint_istio

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test lint_istio

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-security-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test lint_istio

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-security-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-security-k8s-tests_istio

lint_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-security-k8s-tests_istio

lint_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-security-k8s-tests_istio

lint_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test lint_istio

integ-cni-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-cni-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-security-k8s-tests_istio

lint_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test lint_istio

integ-cni-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-cni-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-security-k8s-tests_istio

lint_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test lint_istio

integ-cni-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-cni-k8s-tests_istio

integ-distroless-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-distroless-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-security-k8s-tests_istio

lint_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test lint_istio

integ-cni-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-cni-k8s-tests_istio

integ-distroless-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-distroless-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-security-k8s-tests_istio

lint_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test lint_istio

integ-cni-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-cni-k8s-tests_istio

integ-distroless-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-distroless-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-istiodremote-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-security-k8s-tests_istio

lint_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test lint_istio

integ-cni-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-cni-k8s-tests_istio

integ-distroless-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-distroless-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-istiodremote-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-security-k8s-tests_istio

lint_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test lint_istio

integ-cni-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-cni-k8s-tests_istio

integ-distroless-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-distroless-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-istiodremote-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-telemetry-mc-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-security-k8s-tests_istio

lint_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test lint_istio

integ-cni-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-cni-k8s-tests_istio

integ-distroless-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-distroless-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-istiodremote-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-telemetry-mc-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-security-k8s-tests_istio

lint_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test lint_istio

integ-cni-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-cni-k8s-tests_istio

integ-distroless-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-distroless-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-istiodremote-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-telemetry-mc-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-multicluster-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-security-k8s-tests_istio

lint_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test lint_istio

integ-cni-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-cni-k8s-tests_istio

integ-distroless-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-distroless-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-istiodremote-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-telemetry-mc-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-multicluster-k8s-tests_istio

integ-operator-controller-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-operator-controller-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-security-k8s-tests_istio

lint_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test lint_istio

integ-cni-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-cni-k8s-tests_istio

integ-distroless-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-distroless-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-istiodremote-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-telemetry-mc-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-multicluster-k8s-tests_istio

integ-operator-controller-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-operator-controller-tests_istio

integ-telemetry-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-telemetry-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-security-k8s-tests_istio

lint_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test lint_istio

integ-cni-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-cni-k8s-tests_istio

integ-distroless-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-distroless-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-istiodremote-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-telemetry-mc-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-multicluster-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-telemetry-k8s-tests_istio

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-security-k8s-tests_istio

lint_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test lint_istio

integ-cni-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-cni-k8s-tests_istio

integ-distroless-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-distroless-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-istiodremote-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-telemetry-mc-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-multicluster-k8s-tests_istio

integ-operator-controller-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-operator-controller-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a2fbc9e268ab36c14ba57a48f8692975eb838387
link
/test gencheck_istio

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-security-k8s-tests_istio

lint_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test lint_istio

integ-cni-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-cni-k8s-tests_istio

integ-distroless-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-distroless-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-istiodremote-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-telemetry-mc-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-multicluster-k8s-tests_istio

integ-operator-controller-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-operator-controller-tests_istio

integ-telemetry-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-telemetry-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-security-k8s-tests_istio

lint_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test lint_istio

integ-cni-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-cni-k8s-tests_istio

integ-distroless-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-distroless-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-istiodremote-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-telemetry-mc-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-multicluster-k8s-tests_istio

integ-operator-controller-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-operator-controller-tests_istio

integ-telemetry-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-telemetry-k8s-tests_istio

gencheck_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-notes_istio

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-security-k8s-tests_istio

lint_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test lint_istio

integ-cni-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-cni-k8s-tests_istio

integ-distroless-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-distroless-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-istiodremote-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-telemetry-mc-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-multicluster-k8s-tests_istio

integ-operator-controller-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-operator-controller-tests_istio

integ-telemetry-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-telemetry-k8s-tests_istio

gencheck_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-security-k8s-tests_istio

lint_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test lint_istio

integ-cni-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-cni-k8s-tests_istio

integ-distroless-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-distroless-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-istiodremote-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-telemetry-mc-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-multicluster-k8s-tests_istio

integ-operator-controller-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-operator-controller-tests_istio

integ-telemetry-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-telemetry-k8s-tests_istio

gencheck_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test gencheck_istio

release-notes_istio
7eac637b146c707dc2799f9f7175db1d547b41d9
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test unit-tests_istio

release-test_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test release-test_istio

integ-ipv6-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-helm-tests_istio

integ-pilot-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-security-k8s-tests_istio

lint_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test lint_istio

integ-cni-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-cni-k8s-tests_istio

integ-distroless-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-distroless-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-istiodremote-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-telemetry-mc-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-multicluster-k8s-tests_istio

integ-operator-controller-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-operator-controller-tests_istio

integ-telemetry-k8s-tests_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test integ-telemetry-k8s-tests_istio

gencheck_istio
1da7dbb06f9190fe1837f07d5bfa93479d361198
link
/test gencheck_istio

release-notes_istio
7eac637b146c707dc2799f9f7175db1d547b41d9
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
7ae02406bfacbd3c02f77c16734a3c5f472fd95e
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
7ae02406bfacbd3c02f77c16734a3c5f472fd95e
link
/test release-notes_istio

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

Can you discuss the use case a bit more? I think we want to ensure there are good reasons to configure things before we add more hacky env vars

For scenarios that run stably and require frequent domain name resolution, set the ttl to a larger value to reduce the number of times to access DNS; in other scenarios, ttl can be set to be more general.

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

Test name
Commit
Details
Rerun command

release-notes_istio
8562baf9abb57e92a5a1b120865e2ac2aa2c7514
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
8562baf9abb57e92a5a1b120865e2ac2aa2c7514
link
/test release-notes_istio

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

is it something that makes sense as a global option or per service? I
cannot imagine needing low TTL for a cluster ip - it literally never
changes. But for headless service smaller TTL makes more sense
On Thu, Aug 19, 2021, 7:49 PM Istio Automation @.***>
wrote:

@ChenglongGao327 https://github.com/ChenglongGao327: The following test
failed, say /retest to rerun all failed tests or /retest-required to
rerun all mandatory failed tests:
Test name Commit Details Rerun command
release-notes_istio 8562baf
https://github.com/istio/istio/commit/8562baf9abb57e92a5a1b120865e2ac2aa2c7514
link
https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio/34778/release-notes_istio/1428548965309091840 /test
release-notes_istio
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/34778#issuecomment-902389369, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXO3GJNFVGQ5ARNDNOTT5W7C5ANCNFSM5CNUH76A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

is it something that makes sense as a global option or per service? I cannot imagine needing low TTL for a cluster ip - it literally never changes. But for headless service smaller TTL makes more sense

Yes, the clusterIP ttl needs to be set larger, and the headless ttl needs to be set smaller.
I want to distinguish headless service and clusterIP，and set different ttl. such as through kubernetes and kube-dns clusterIP
When connecting to k8s, if the IP address corresponding to the service domain name is not in the same network segment as the kubernetes and kube-dns service cluster IP addresses, then the service is considered a headless service.

Do you have a real use case for this, or just saw a TODO? I would avoid fixing TODOs without a strong motivation, usually they mean "TODO [if we ever have a compelling use case])".

IP address corresponding to the service domain name is not in the same network segment as the kubernetes
We do not need this implicit logic, we know if its headless or not in the control plane

Do you have a real use case for this, or just saw a TODO? I would avoid fixing TODOs without a strong motivation, usually they mean "TODO [if we ever have a compelling use case])".

I saw a TODO and think that it is better to set different ttl for different scenarios, so making it configurable

I highly recommend not implementing TODOs like this - the reason they were
not done is that they add a lot of complexity and we haven't seen any real
world demand to warrant that complexity
On Sun, Aug 22, 2021, 6:18 PM ChenglongGao327 @.***>
wrote:

Do you have a real use case for this, or just saw a TODO? I would avoid
fixing TODOs without a strong motivation, usually they mean "TODO [if we
ever have a compelling use case])".
I saw a TODO and think that it is better to set different ttl for
different scenarios, so making it configurable
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/34778#issuecomment-903373820, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXP7QKWWB42TGHXBCDDT6GOVDANCNFSM5CNUH76A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

I highly recommend not implementing TODOs like this - the reason they were not done is that they add a lot of complexity and we haven't seen any real world demand to warrant that complexity

ok, i see. Thanks for your reviews


Node Join Flow: Join Credentials

Part of #99.
As defined in the Cluster Lifecycle DD, we don't want anyone to be able to contact a cluster claiming that they are a node that wishes to join it (after rebooting).
The target flow is the following:

During Bootstrap/Registration, next to generating a Node keypair for Node credentials, a node should generate a Join keypair.
The Node's Join Public Key should be submitted to the cluster as that node's Join PK.
The Node's Join Keypair should be saved to the ESP, sealed using TPM.
On Join, a Node will unseal its Join Keypair and use a saved Cluster Directory to contact its Cluster.
The Node and Cluster will mutually hardware attest eachother.
After mutual verification, the Cluster will give out the node's Cluster Unlock Key to the booting Node.
The Node will use the CUK to mount its Data partition.

Since we're currently skipping step 7 (hardware attestation) the Join keypair is effectively as powerful as the Node credentials/keypair. However, with the introduction of HA, this will not be the case anymore, and the Join keypair will instead act as a set of “Courtyard” credentials to be able to start performing HA (itself an expensive operation).
All the above steps of the flow need to be implemented.

Current WIP patch: https://review.monogon.dev/c/monogon/+/556
Still working on e2e tests.

Merged as part of #99


Telegram spam blocker timer got me

Hey, I tried to join the telegram chat and I didn't notice the tiny box at the bottom that said I would be locked out if I didn't click on it. I had scrolled up while reading the chat and missed the warning. Could someone please unblock me or something? I promise I won't spam 😄

Give me a moment and I will take care of it for you.

Please try again now. And remember to press the button.

Resolved


How often do AKS OIDC keys rotate?

The documentation says that

AKS rotates the key automatically and periodically

How often is "periodically"? It seems to be an important piece of information. If we are surprised by the automatic rotation, my understanding is that the old Issuer URLs will stop working after 24h (because part of the URL is the key). To avoid this, we should implement our own rotation mechanism and we need to make sure it is executed more frequently than the automatic rotation would be. For this we need to know the frequency of the automatic rotation.

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

ID: deab7eb6-9bbf-28ea-f8c3-4150e3c5d076
Version Independent ID: 0ae60dcc-0a65-20fc-e303-e4af9690e132
Content: Create an OpenID Connect provider for your Azure Kubernetes Service (AKS) cluster - Azure Kubernetes Service
Content Source: articles/aks/use-oidc-issuer.md
Service: azure-kubernetes-service
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

I think I misunderstood. The Issuer URLs probably don't rotate. Closing.

Is there way to your own signing key rotation period  for auto rotation ? also what is the default signing key rotation period ?


Exception when running default app on Samsung Galaxy Note 5

Error message
Seeing a strange behavior for the Galaxy Note 5 only when running the hello world application created by running flutter create. After a reboot of the phone, I can launch the application as expected. But trying to run the same application again for the 2nd time, the app gets stuck at the Flutter Debug Loader screen, with the message: "This is a hot-reload-enabled debug-mode Flutter application...".
The behavior is tied to the hot reload feature, when I disable it by using flutter run --no-hot, everything is working fine on the Galaxy Note 5.
Exception / error message shown: I've seen this exception a couple of times, but that doesn't seem to be the main problem, since the app get's stuck with different error messages as well.
 0 ms • I/flutter : ══╡ EXCEPTION CAUGHT BY RENDERING LIBRARY ╞═════════════════════════════════════════════════════════
   0 ms • I/flutter : The following ArgumentError was thrown during performLayout():
   0 ms • I/flutter : Invalid argument(s): 0.0

On an Nvidia Shield tablet or Lumigon T3 Android phone everything is working fine. These are the engine and framework revisions:

Framework revision 6777766d2d (57 minutes ago), 2016-10-11 15:51:35
Engine revision e8d046e9e2

When running the app as a release using flutter run --release, it launches as expected.
Steps to Reproduce
On a Galaxy Note 5 (Android 6.0.1, build MMB29K.N920SKSU2BPH3), run the following steps:

Reboot the phone
Create a new default app using flutter create helloworld.
Run the app by executing flutter run lib/main.dart or flutter run: Application should run as expected
Stop the app and run again: Application launches with black screen, or with the "Flutter Debug Loader" screen (This is a hot-reload-enabled debug-mode Flutter application...").
Now run the app with hot reload disabled: flutter run --no-hot, and the app will load again.

Logs
flutter run -v output:
Running app after a reboot of device for the first time (everything working fine)
https://gist.github.com/raju-bitter/080e446a570c512133936bbc35e245b0
Running app for second time, now it doesn't launch, stuck at loader screen
https://gist.github.com/raju-bitter/5e978edbf03145715039d7ae2ec193b2
flutter analyze output:
Analyzing lib/main.dart...
No analyzer warnings! (ran in 5.7s)

Flutter Doctor
[✓] Flutter (on Linux, channel master)
    • Flutter at /home/raju/dev/flutter
    • Framework revision 6777766d2d (57 minutes ago), 2016-10-11 15:51:35
    • Engine revision e8d046e9e2
    • Tools Dart version 1.20.0-dev.10.2

[✓] Android toolchain - develop for Android devices (Android SDK 24.0.3)
    • Android SDK at /home/raju/Android/Sdk
    • Platform android-24, build-tools 24.0.3
    • Java(TM) SE Runtime Environment (build 1.8.0_101-b13)

[✓] Atom - a lightweight development environment for Flutter
    • flutter plugin version 0.2.6
    • dartlang plugin version 0.6.40

[-] IntelliJ WebStorm (version 2016.2)
    • Dart plugin not installed; this adds Dart specific functionality.
    • Flutter plugin not installed; this adds Flutter specific functionality.
    • For information about managing plugins, see
      https://www.jetbrains.com/help/idea/2016.2/managing-plugins.html

[✓] Connected devices
    • SM N920S • 05157df5d93b793d • android-arm

For extra long logs like this gist.github.com can be useful for taking them out-of-band. :)

Looks like the first exception was:
   0 ms • I/flutter : ══╡ EXCEPTION CAUGHT BY RENDERING LIBRARY ╞═════════════════════════════════════════════════════════
   0 ms • I/flutter : The following ArgumentError was thrown during performLayout():
   0 ms • I/flutter : Invalid argument(s): 0.0
   0 ms • I/flutter : When the exception was thrown, this was the stack:
   0 ms • I/flutter : #0      _Double.clamp (dart:core-patch/double.dart)
   0 ms • I/flutter : #1      TextPainter.layout (package:flutter/src/painting/text_painter.dart)
   0 ms • I/flutter : #2      RenderParagraph.performLayout (package:flutter/src/rendering/paragraph.dart)
   0 ms • I/flutter : #3      RenderObject.layout (package:flutter/src/rendering/object.dart)

Presumably that's a bug in TextPainter?  @Hixie

Moved the log files into gist.github.com. Updated the description with more details after more testing. Was never able to reproduce that behavior on the two other Android devices I'm testing with.

@johnmccutchan the updated description suggests maybe hot reload is failing on the note 5?

@Hixie the DevFS failure in the log is a result of the VM process dying while we are copying files.
@raju-bitter Do you have any idea what all the filesystem errors (ENOTEMPTY, ENOENT) are coming from? I've never seen that and it appears to be coming from the Android system directly.

@eseidelGoogle Do we have a Galaxy Note 5?

We have a Note 3 and a Galaxy S5.

Did a factory rest of Galaxy Note 5 and tried again. Same behavior as before, here are the log files:
Testing flutter.io on Galaxy Note 5 after factory reset, 1st run of app with one hot reload
https://gist.github.com/raju-bitter/2dbaf3e5a92b261d6b0aef564c94f00b
Testing flutter.io on Galaxy Note 5 after factory reset, 2nd of app (error)
https://gist.github.com/raju-bitter/b3ac3e535cb5cd5e19b421c840c4d547
The 2nd time I'm running the app, I can see this extra exception:

Exception from flutter run: HttpException: Connection closed before full header was received, uri = http://<IP_ADDRESS>:8102/ws

https://gist.github.com/raju-bitter/b3ac3e535cb5cd5e19b421c840c4d547#file-flutter-run-log-galaxy-note5-factoryreset-second-run-log-L911

Thanks for double checking. I'll purchase a Note 5 right now.

This also repros if you run a Flutter app from the IntelliJ plugin against a Nexus 5X (but not if you run that same app against that same 5X from a terminal with flutter run): https://github.com/flutter/flutter-intellij/issues/289.
Some kind of timing issue?

I can also reproduce this problem on a Nexus 5X using flutter daemon; see my comment in the bug @mit-mit referenced.

@raju-bitter On the second run the HttpException is caused by the app on the phone crashing. It's unclear why it is crashing, I'm trying to reproduce locally with no luck. Could you gather the full logs from 'adb logcat' ? It might give us a clue about where the crash is occuring.

Looking at the logs I noticed the first error:
  25 ms • Exception from flutter run: FormatException: Overlong encoding of 0x0
          #0      _Utf8Decoder.convert (dart:convert/utf.dart:499)
          #1      _Utf8ConversionSink.addSlice (dart:convert/string_conversion.dart:333)
          #2      _Utf8ConversionSink.add (dart:convert/string_conversion.dart:329)
          #3      _ConverterStreamEventSink.add (dart:convert/chunked_conversion.dart:92)
          #4      _SinkTransformerStreamSubscription._handleData (dart:async/stream_transformers.dart:119)
          #5      StackZoneSpecification.registerUnaryCallback.<anonymous closure>.<anonymous closure> (package:stack_trace/src/stack_zone_specification.dart:135)
          #6      StackZoneSpecification._run (package:stack_trace/src/stack_zone_specification.dart:206)
          #7      StackZoneSpecification.registerUnaryCallback.<anonymous closure> (package:stack_trace/src/stack_zone_specification.dart:135)
          #8      _rootRunUnary (dart:async/zone.dart:1158)
          #9      _CustomZone.runUnary (dart:async/zone.dart:1037)
          #10     _CustomZone.runUnaryGuarded (dart:async/zone.dart:932)
          #11     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:331)
          #12     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:258)
          #13     _StreamController&&_SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:768)
          #14     _StreamController._add (dart:async/stream_controller.dart:635)
          #15     _StreamController.add (dart:async/stream_controller.dart:581)
          #16     _Socket._onData (dart:io-patch/socket_patch.dart:1675)
          #17     StackZoneSpecification.registerUnaryCallback.<anonymous closure>.<anonymous closure> (package:stack_trace/src/stack_zone_specification.dart:135)
          #18     StackZoneSpecification._run (package:stack_trace/src/stack_zone_specification.dart:206)
          #19     StackZoneSpecification.registerUnaryCallback.<anonymous closure> (package:stack_trace/src/stack_zone_specification.dart:135)
          #20     _rootRunUnary (dart:async/zone.dart:1162)
          #21     _CustomZone.runUnary (dart:async/zone.dart:1037)
          #22     _CustomZone.runUnaryGuarded (dart:async/zone.dart:932)
          #23     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:331)
          #24     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:258)
          #25     _StreamController&&_SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:768)
          #26     _StreamController._add (dart:async/stream_controller.dart:635)
          #27     _StreamController.add (dart:async/stream_controller.dart:581)
          #28     _RawSocket._RawSocket.<anonymous closure> (dart:io-patch/socket_patch.dart:1242)
          #29     _NativeSocket.issueReadEvent.issue (dart:io-patch/socket_patch.dart:776)
          #30     _microtaskLoop (dart:async/schedule_microtask.dart:41)
          #31     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50)
          #32     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:96)
          #33     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:149)

It's unclear from the stack trace what is happening but this happens before we even create the DevFS environment.

@raju-bitter I have made a change to flutter tools that will hopefully give a better stack trace for the above error. Could you sync to the latest master and try again?

@johnmccutchan Did another test run with today's version
[✓] Flutter (on Mac OS, channel master)
• Flutter at /Users/raju/dev/flutter
• Framework revision 729efa2501 (12 hours ago), 2016-10-20 23:28:30
• Engine revision 5e78e75122
• Tools Dart version 1.21.0-dev.0.0
Here is the complete log after rebooting and launching the Flutter app two times. First time reloading is working. Second time stuck, Flutter exception highlighted:
https://gist.github.com/raju-bitter/059c12d52cc7557648154d5b5e778e76#file-flutter-run-log-galaxy-note5-factoryreset-better-logging-txt-L1455-L1720

Thanks! Our Note 5 arrived, and it's on John's desk :)

I can confirm that I can reproduce the failure as described. It's flaky but I can make it happen.
Initial investigation points at a low level networking failure between the host machine and the phone. We fail to make the initial service protocol connection. The client receives and HTTP error but the server (running on the phone) never sees the connection attempt. Possibly something bad is happening at the adb level.

I've figured out what causes this problem: we get stale device logs and try and use the previous launch's service protocol port.

After a few attempted runs, I see the following from adb forward --list. Note the repeated device ports.
1115fbe3a1b01304 tcp:8104 tcp:47374
1115fbe3a1b01304 tcp:8105 tcp:48964
1115fbe3a1b01304 tcp:8106 tcp:47374
1115fbe3a1b01304 tcp:8107 tcp:48964
1115fbe3a1b01304 tcp:8108 tcp:47374
1115fbe3a1b01304 tcp:8109 tcp:48964
1115fbe3a1b01304 tcp:8110 tcp:47374
1115fbe3a1b01304 tcp:8111 tcp:48964
1115fbe3a1b01304 tcp:8112 tcp:54910
1115fbe3a1b01304 tcp:8113 tcp:33898
1115fbe3a1b01304 tcp:8114 tcp:54910
1115fbe3a1b01304 tcp:8115 tcp:33898

I've figured out what causes this problem

Nice! Thanks for tracking it down :)


⚠ Bofrost.lu has degraded performance

In 7a6f285, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2841 ms

Resolved: Bofrost.lu performance has improved in 27e2919 after 1 hour, 20 minutes.


distanceAndRelationship: missing "nephiew" in first line of relationship box

In first line of the relationship box where the relationship should be displayed, I am getting just "Your"
For my nephiew
Your
Your common ancestor, Jelena (Stupica) Trtnik (1942-), is his grandmother.
Your common ancestor, Mitja Dimitrij Trtnik (1940-1994), is his grandfather.
Aleš

Thanks. I'll take a look.

I've fixed this.


Update information displayed in project Activity feed

Describe the solution you'd like
The project activity feed needs to be updated as a result of the new payment request/invoice submission work. The activity feed needs to show information about the new statuses for payment requests. It needs to follow the same UI patterns.
UI Design

UI Wireframes

Priority

Medium (slowing you down)

Affected roles

Staff
Applicants
Partners

Ideal deadline
When the OTF Finance work is being delivered, ideally this update would be ready when the OTF Finance updates are ready.

@fourthletter  I am bit confused about what we need to hide/remove. Can you please clear a few of my queries.

Already displayed information.

We don't want to create activity for actions like Project creation, Approval, Contract Approval. Do we only want to have payment/invoice related things in activity feed?
Regarding the UI pattern, We want to show request change's messages in activity feed. right?
Conclusion: We want to reduce the project feed from left side of image(all previous action) to lower right side of image(only payment related actions). Am I right?

@ei8fdb I am bit confused about what we need to hide/remove. Can you please clear a few of my queries.

👍

Conclusion: We want to reduce the project feed from left side of image(all previous action) to lower right side of image(only payment related actions). Am I right?

Ah, I understand - I think the designs were confusing. Apologies.
We want the activity feed to contain:

activity for actions like Project creation, Approval, Contract Approval, PLUS
paymet/invoice related actions, AND
request change's message summary, with a link to the message in the communications tab

Im updating the the designs now, and will upload in a minute. Please let me know if that explains better.

@ei8fdb please move this issue to https://github.com/OpenTechFund/apply-app/issues -- thank you!

I've looked thru the issue management UI but I can't see how to move this.
You'll have to do it @fourthletter

@ei8fdb I moved it to https://github.com/OpenTechFund/apply-app/issues/24.


Create randomly generated document id

Hi, is there a way to generate a document ref without an id, the same way firestore sdk does it?

Hi, can anyine dekete this issue. i found the corresponding function


pyrealsense2: RuntimeError: Frame didn't arrive within 5000

Required Info

Camera Model
D435

Firmware Version
<IP_ADDRESS>

Operating System & Version
Win 10

Platform
PC

SDK Version
<IP_ADDRESS>4

Language
python3.7.5 64bit

Issue Description
I installed the RealSense SDK for the first time today and want to develop in python. Using RealSenseViewer works without problems.
But whatever I do in python, I run into
RuntimeError: Frame didn't arrive within 5000
The code I use is:
import pyrealsense2 as rs

rs.log_to_file(rs.log_severity.debug, file_path='./log.txt')

device = rs.context().devices[0]
serial_number = device.get_info(rs.camera_info.serial_number)
print(serial_number)

pipeline = rs.pipeline()
config = rs.config()
config.enable_stream(rs.stream.depth, 640, 480, rs.format.z16, 30)

pipeline.start(config)
frames = pipeline.wait_for_frames()
depth = frames.get_depth_frame()

It reads the serial number correctly and I can find further information about the camera debugging. But reading frames won't work.
I installed the SDK with the installer. Python is running in a virtual environment. I used  pip to install pyrealsense2.
To log of above code is:
06/08 16:41:22,027 DEBUG [16436] (win-helpers.cpp:87) res=pSensorManager->GetSensorsByCategory(SENSOR_CATEGORY_ALL, &pSensorCollection) returned: HResult 0x80070490: "Element nicht gefunden."
06/08 16:41:22,045 DEBUG [16436] (win-helpers.cpp:87) res=pSensorManager->GetSensorsByCategory(SENSOR_CATEGORY_ALL, &pSensorCollection) returned: HResult 0x80070490: "Element nicht gefunden."
06/08 16:41:22,061 DEBUG [16436] (ds5-factory.cpp:1109) try_fetch_usb_device(...) failed.
06/08 16:41:22,061 INFO [16436] (context.cpp:365) Found 1 RealSense devices (mask 254)
06/08 16:41:22,190 DEBUG [16436] (win-helpers.cpp:87) res=pSensorManager>GetSensorsByCategory(SENSOR_CATEGORY_ALL, &pSensorCollection) returned: HResult 0x80070490: "Element nicht  gefunden."
06/08 16:41:22,206 DEBUG [16436] (ds5-factory.cpp:1109) try_fetch_usb_device(...) failed.
06/08 16:41:22,206 INFO [16436] (context.cpp:365) Found 1 RealSense devices (mask 254)
06/08 16:41:22,207 DEBUG [16436] (win-helpers.cpp:87) res=pSensorManager->GetSensorsByCategory(SENSOR_CATEGORY_ALL, &pSensorCollection) returned: HResult 0x80070490: "Element nicht gefunden."
 06/08 16:41:22,225 DEBUG [16436] (ds5-factory.cpp:1109) try_fetch_usb_device(...) failed.
 06/08 16:41:22,225 INFO [16436] (context.cpp:365) Found 2 RealSense devices (mask 255)
 06/08 16:41:22,368 DEBUG [16436] (win-helpers.cpp:87) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "Die angegebene Datenstromnummer war ungültig."
 06/08 16:41:22,368 DEBUG [16436] (win-helpers.cpp:87) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "Die angegebene Datenstromnummer war ungültig."
 06/08 16:41:22,369 DEBUG [16436] (win-helpers.cpp:87) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "Die angegebene Datenstromnummer war ungültig."
 06/08 16:41:22,385 DEBUG [16436] (win-helpers.cpp:87) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "Die angegebene Datenstromnummer war ungültig."
 06/08 16:41:22,385 DEBUG [16436] (win-helpers.cpp:87) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "Die angegebene Datenstromnummer war ungültig."
 06/08 16:41:22,385 DEBUG [16436] (win-helpers.cpp:87) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "Die angegebene Datenstromnummer war ungültig."
 06/08 16:41:22,385 DEBUG [16436] (win-helpers.cpp:87) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "Die angegebene Datenstromnummer war ungültig."
 06/08 16:41:22,396 INFO [16436] (sensor.cpp:1341) Request: Z16 Depth,
Resolved to: Z16 Depth,
 06/08 16:41:22,413 DEBUG [16436] (win-helpers.cpp:87) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "Die angegebene Datenstromnummer war ungültig."
 06/08 16:41:22,414 DEBUG [16436] (win-helpers.cpp:87) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "Die angegebene Datenstromnummer war ungültig."
 06/08 16:41:22,414 DEBUG [16436] (win-helpers.cpp:87) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "Die angegebene Datenstromnummer war ungültig."
 06/08 16:41:22,418 DEBUG [16436] (global_timestamp_reader.cpp:141) time_diff_keeper::start: _users_count = 1
 06/08 16:41:27,432 DEBUG [16436] (win-helpers.cpp:87) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "Die angegebene Datenstromnummer war ungültig."
 06/08 16:41:27,432 DEBUG [16436] (win-helpers.cpp:87) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "Die angegebene Datenstromnummer war ungültig."
 06/08 16:41:27,433 DEBUG [16436] (win-helpers.cpp:87) _reader->GetNativeMediaType(sIndex, k, &pMediaType.p) returned: HResult 0xc00d36b3: "Die angegebene Datenstromnummer war ungültig."
 06/08 16:41:27,434 DEBUG [16436] (global_timestamp_reader.cpp:152) time_diff_keeper::stop: _users_count = 0
 06/08 16:41:27,434 DEBUG [16436] (global_timestamp_reader.cpp:155) time_diff_keeper::stop: stop object.
 06/08 16:41:27,434 DEBUG [6448] (global_timestamp_reader.cpp:226) Notification: time_diff_keeper polling loop is being shut-down

Happy for any help. Thank you.

Hi @JLo9   Apologies for the delay in responding.   Do you still experience the error if you add the following line to the end of your script please?
pipeline.stop()

Hi @MartyG-RealSense ,
thanks for your help. Adding pipeline.stop() doesn't change the behaviour. The
RuntimeError: Frame didn't arrive within 5000

is an exception thrown at frames = pipeline.wait_for_frames(). Therefore, the script wouldn't reach the stop() bit anyways. Catching the exception and running multiple times doesn't help either.
I have tried up to 50.000ms for the timeout, but frames just do not arrive.

Hi jLo9,
you can run the python example code python-tutorial-1-depth.py that come with the SDK to see if you are able to get the depth stream ,this sample  use while loop to wait for the frame continuously
in your code, seems you only wait for the frame once (no while or for loop seen)

Hi @RealSenseSupport
This doesn't work either. The line frames = pipeline.wait_for_frames() throws an Exception which will cause the python-tutorial-1-depth.py to stop executing after the first iteration.
I can catch the exception inside the loop of course, but just get exceptions in a loop. There are no frames arriving.
If I run the align-depth2color.py example, the output will be:
Depth Scale is:  0.0010000000474974513
Traceback (most recent call last):
  File "align-depth2color.py", line 47, in <module>
    frames = pipeline.wait_for_frames()
RuntimeError: Frame didn't arrive within 5000

So it gets a connection to the D435 and can read the depth_scale, same as in my example it can read the serial number but as soon as it waits for frames, it fails.
Any other ideas? Thanks.

Case closed due to no further comments received.

Hi @carrinodue  The official script pages for the Python examples do not include '5000' in the brackets of the wait_for_frames instruction.
https://github.com/IntelRealSense/librealsense/blob/master/wrappers/python/examples/python-tutorial-1-depth.py#L25
Do you still experience the error if you remove the number from the brackets and just use frames = pipeline.wait_for_frames() please?

Hi @MartyG-RealSense, thank you for your prompt reply.
If I understand well, pipeline.wait_for_frames() has 5000 as a default value for the optional parameter timeout_ms.
https://intelrealsense.github.io/librealsense/python_docs/_generated/pyrealsense2.pipeline.html#pyrealsense2.pipeline.wait_for_frames
But, yes, I tried with and without 5000, with 50'000 and also tried the function try_wait_for_frames().  While in debug mode it works fine, when I run the script (in PyCharm or in a Jupyter lab) I never get a frame. Thanks

Yes, the pipeline will timeout after 5 seconds if frames are not received.
It's no trouble at all, it's great to hear that you found a solution for the PyCharm aspect of your problem.  Thanks so much for sharing the method that you found for dealing with this problem  :)
When librealsense is built in Release mode then it takes advantage of compiler optimizations.  I have not seen a previous case of Release mode causing problems with a Jupyter project though.

Ok, final update from my side. What caused problems to run the code on Jupyter was.... Kaspersky endpoint security 😣. I had just to turn it off and everything worked fine.
Thanks again.

I'm pleased that you found a solution to the remaining Jupyter issue!


Conflict with Ouijaboard keybind

Every time I press O in the terminal/console when typing it opens up the Ouijaboard UI and takes me out of the terminal.
Maybe disable the Ouijaboard when using the terminal or add a rebind option.

Should be fixed in v1.2.1, but a keybind would still be nice

This was a bug in v1.3.0, this should be patched in the latest version.


kep <-> equi fixed, with tests

Reverted to the equinoctial elements by Broucke and Cefola (1972) using tan(i/2) rather than sin(i/2), since these seem both more prevalent, and since this was the reference given in the comments in the code.  Conversion between keplerian and equinoctial elements implemented, with a couple of tests.
Also added function to check for equivalence for Keplerian elements when degenerated (i and/or e equal to zero), but this functions needs unit tests.
Added a separate module for constants, which will not allow redefinition or deletion of existing constants (but imports to other packages can be overwritten, obviously).

Awesome, ill add some code to get this into the class API too, then we should be good to go


shorter log path

current log file path is too long:
2023-01-11T11:02 WRN ../../../../workspace/kubefirst/kubefirst/internal/terraform/terraform.go:241 > Failed to destroy security group: operation error EC2: DeleteSecurityGroup, https response error StatusCode: 400, RequestID: 91a38626-44d1-41b2-857e-0841fca50fdf, api error InvalidGroup.NotFound: The security group 'sg-095ce6aff03c7cdcc' does not exist

goal: make log path shorter
AC1: following the example above, log path will be:
2023-01-11T11:02 WRN terraform.go:241 > Failed to destroy security group: operation error EC2: DeleteSecurityGroup, https response error StatusCode: 400, RequestID: 91a38626-44d1-41b2-857e-0841fca50fdf, api error InvalidGroup.NotFound: The security group 'sg-095ce6aff03c7cdcc' does not exist

We need to be able to know the module the log was reported, not just the file. Multiple files have the same name.
I don't agree with that reversion.

Details: https://github.com/kubefirst/kubefirst/pull/970

I was not able to find a similar solution to the previous logger that was showing just the application level path.
With the use of trimpath, the built binary improve a bit that, but it is not ideal too:
go build  -trimpath  .

Sample:
[90m2022-12-27T13:07 DBG github.com/kubefirst/kubefirst/internal/flagset/common.go:81 > Enviroment Variable(gitops-repo) not set

The log need to be a tool help us to find the source of the issue, or it will create more problems than solution.

The ideal size would be, as most loggers do like default go and zap:
internal/flagset/common.go:81

I think we keep changing/reverting this property, because we could achieve the common "shortpath" that  includes module path.


Cargo allows publishing a crate that is missing files for examples

If you make a Cargo.toml:
[package]
…
include = ["Cargo.toml"]

[[example]]
path = "foo/bar.rs"
name = "broken"

this will publish without error, but the package will be missing files required by the example (causing unexpected error as in #4751)
https://github.com/pornel/rust-rgb/commit/08d2a21979a1e0af8c157fc6eb010fffb0a247a0

Is this actually a bug? Especially when considering that #4751 is, this here may be not: Examples are not built if a package is built so they do not need to be packaged. Same reason path-dev-dependencies may find their way into a published crate.

If #4751 is not supposed to happen, then this may be OK.


Mapping Bonanza Part 9: Structure stuff

Decided to go on a mapping bonanza, here's part 9: the structure package.

Hmm, is there any convention on whether to shorten structureManager? IMO manager is too generic.

Many other classes already refer to it as manager, I was simply adding it where it was missing


Configuration for using braces in a switch statement

Some example code:
switch (test) {
    case 5: { return 5; }
    case 6: {
        return 6;
    }
    case 7:
        return 7;
}

This would tie into the "useBraces" configuration and could be turned off by setting switchCase.useBraces to false.

I think this would've re-implemented https://github.com/sindresorhus/eslint-plugin-unicorn/blob/main/docs/rules/switch-case-braces.md .
I guess a pure formatter (no static analysis) may not be able to know when it is safe to add/remove braces or not.


Validate simulations

While the simulations do work, we do not yet know if they provide data that helps in real world scenarios. We should compare simulations with known drifts and see if the predictions are even close to reality.

Duplicate of #3


Assets UI

This issue is a placeholder for an epic, which is a collection of issues related to a single area of development.
In order to view these issues it's necessary to install https://www.zenhub.com/


Add dSYM folder to C.gitignore for OSX env

See https://github.com/github/gitignore/pull/527

For C.gitignore add dSYM folder from Mac OS X to gitignore

Thanks!


[JS] Decimal-type conversions result in errors/inaccuracies in Arrow JS

Describe the bug, including details regarding any error messages, version, and platform.
Thanks for all the work on Arrow! Unfortunately, I've run into problems in the JS API around both encoding and decoding of Decimal-typed data.
Encoding:
arrow = require('apache-arrow')
arrow.vectorFromArray([1, 12, 34], new arrow.Decimal(3, 18))

Results in TypeError: d.subarray is not a function
(Incidentally it also seems that the Decimal type constructor uses a different argument order than pyarrow.)
Decoding:
Since encoding failed in JS, let's do it in pyarrow:
import pyarrow as pa
v = pa.array([1, 12, 34], type=pa.decimal128(18, 3))
batch = pa.record_batch([v], names=['d'])

sink = pa.BufferOutputStream()
with pa.ipc.new_stream(sink, batch.schema) as writer:
   writer.write_batch(batch)
sink.getvalue().hex()

and then we can carry the resulting byte string over to JavaScript and try to decode it:
const hex = 'FFFFFFFF780000001000000000000A000C000600050008000A000000000104000C000000080008000000040008000000040000000100000014000000100014000800060007000C00000010001000000000000107100000001C0000000400000000000000010000006400000008000C0004000800080000001200000003000000FFFFFFFF8800000014000000000000000C0016000600050008000C000C0000000003040018000000300000000000000000000A0018000C00040008000A0000003C00000010000000030000000000000000000000020000000000000000000000000000000000000000000000000000003000000000000000000000000100000003000000000000000000000000000000E8030000000000000000000000000000E02E0000000000000000000000000000D0840000000000000000000000000000FFFFFFFF00000000';
const bytes = Uint8Array.from(hex.match(/.{1,2}/g).map(s => parseInt(s, 16)));
const vec = arrow.tableFromIPC(bytes).getChild('d');

vec.get(0)         // [1000, 0, 0, 0] <- byte array looks correct
`${vec.get(0)}`    // "1000" <- incorrect, should be 1; ignores scale
Number(vec.get(0)) // 2.2136092888451462e+23 <- incorrect, should be 1
+vec.get(0)        // TypeError: can't convert BigInt to number <- ???

While the basic byte encoding looks OK, all of the built-in conversions appear to be faulty.
Related: #28804, #35745
cc: @domoritz
Component(s)
JavaScript

Whats the status on this? Thanks!

Converting from 64 and 128-bit decimals to 64-bit floats isn't implemented yet. I don't have the bandwidth to do it currently, but PR's are welcome. libcudf's C++ implementation would be a great starting point: https://github.com/rapidsai/cudf/blob/branch-24.04/cpp/include/cudf/fixed_point/fixed_point.hpp

I wrote our own converter for Mosaic if it helps: https://github.com/uwdata/mosaic/blob/main/packages/core/src/util/convert-arrow.js#L132

Thanks guys, we wrote our own yesterday too. Will push a PR shortly.

We just ran into this using DuckDB-Wasm. Here’s a simple query that demonstrates the problem:
SELECT<PHONE_NUMBER>0::INT128 AS n

This returns a DecimalBigNum consisting of
[2521176508, 2, 0, 0]

And likewise string coercion returns the expected "11111111100", but number coercion gives 4.460189873590169e+44.

https://github.com/apache/arrow/pull/40729 starts to fix decimal support. More to come.


⚠ Bofrost.de has degraded performance

In 083a0f1, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1617 ms

Resolved: Bofrost.de performance has improved in 7f6c525.