add istioctl validate command

Add a dedicated command for offline validation of Istio kubernetes resources. This new commend is intended to replace existing usage of the now deprecated istioctl create command.

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

Needs approval from an approver in each of these files:

istioctl/OWNERS
pilot/OWNERS

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

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
8d990510e3b99af2aba117029f46cb7996a3a35d
link
/test istio-presubmit

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

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

Needs approval from an approver in each of these files:

OWNERS

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

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
8d990510e3b99af2aba117029f46cb7996a3a35d
link
/test istio-presubmit

prow/istio-unit-tests.sh
0cb5c9f7bd1569800c8e1dfa149ab5e2b467e499
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
0cb5c9f7bd1569800c8e1dfa149ab5e2b467e499
link
/test istio-unit-tests

prow/istio-presubmit.sh
0cb5c9f7bd1569800c8e1dfa149ab5e2b467e499
link
/test istio-presubmit

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
0cb5c9f7bd1569800c8e1dfa149ab5e2b467e499
link
/test istio-unit-tests

prow/istio-presubmit.sh
a4654ace665a83b0dc9b7d8891e54f820595730b
link
/test istio-presubmit

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

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
a4654ace665a83b0dc9b7d8891e54f820595730b
link
/test istio-presubmit

prow/istio-unit-tests.sh
a4654ace665a83b0dc9b7d8891e54f820595730b
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
a4654ace665a83b0dc9b7d8891e54f820595730b
link
/test istio-presubmit

prow/istio-unit-tests.sh
a4654ace665a83b0dc9b7d8891e54f820595730b
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
a4654ace665a83b0dc9b7d8891e54f820595730b
link
/test istio-unit-tests

prow/istio-presubmit.sh
c1a69abac9da9517b42193e9cac1da0ab0a9af40
link
/test istio-presubmit

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

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
c1a69abac9da9517b42193e9cac1da0ab0a9af40
link
/test istio-presubmit

prow/istio-unit-tests.sh
c1a69abac9da9517b42193e9cac1da0ab0a9af40
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
d35ed44a715652b04ee3e2a684500a7154d02733
link
/test istio-presubmit

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

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
3d209c73459f1ba0c3585098cd9fd01a555ae2b4
link
/test istio-presubmit

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

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

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-dashboard

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

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

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

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

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

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-mixer-no_auth

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

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

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-mixer-no_auth

prow/e2e-simpleTests.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-simpleTests

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

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

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-mixer-no_auth

prow/e2e-simpleTests.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-simpleTests

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

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

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

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-mixer-no_auth

prow/e2e-simpleTests.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-simpleTests

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

prow/e2e-mixer-no_auth-mcp.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-mixer-no_auth-mcp

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

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

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-mixer-no_auth

prow/e2e-simpleTests.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-simpleTests

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

prow/e2e-mixer-no_auth-mcp.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-mixer-no_auth-mcp

prow/istio-unit-tests.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-mixer-no_auth

prow/e2e-simpleTests.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-simpleTests

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

prow/e2e-mixer-no_auth-mcp.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-mixer-no_auth-mcp

prow/istio-unit-tests.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test istio-unit-tests

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

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

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

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-simpleTests

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

prow/e2e-mixer-no_auth-mcp.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-mixer-no_auth-mcp

prow/istio-unit-tests.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test istio-unit-tests

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

prow/e2e-mixer-no_auth.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-mixer-no_auth

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

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

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-simpleTests

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

prow/e2e-mixer-no_auth-mcp.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-mixer-no_auth-mcp

prow/istio-unit-tests.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test istio-unit-tests

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

prow/e2e-mixer-no_auth.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-dashboard

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

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

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-simpleTests

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

prow/e2e-mixer-no_auth-mcp.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-mixer-no_auth-mcp

prow/istio-unit-tests.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test istio-unit-tests

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

prow/e2e-mixer-no_auth.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

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

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

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth-mcp.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-mixer-no_auth-mcp

prow/istio-unit-tests.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test istio-unit-tests

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

prow/e2e-mixer-no_auth.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-simpleTests

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

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

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

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth-mcp.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-mixer-no_auth-mcp

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

prow/e2e-mixer-no_auth.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-simpleTests

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

prow/istio-unit-tests.sh
f2c3352df8c9973f76e11356bd49f058ec0d38e7
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth-mcp.sh
b13cf677ea9daae49f34bee433d59f433333c12f
link
/test e2e-mixer-no_auth-mcp

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

prow/e2e-mixer-no_auth.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-simpleTests

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

prow/istio-unit-tests.sh
f2c3352df8c9973f76e11356bd49f058ec0d38e7
link
/test istio-unit-tests

prow/istio-presubmit.sh
f2c3352df8c9973f76e11356bd49f058ec0d38e7
link
/test istio-presubmit

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

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

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-simpleTests

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

prow/istio-unit-tests.sh
f2c3352df8c9973f76e11356bd49f058ec0d38e7
link
/test istio-unit-tests

prow/istio-presubmit.sh
f2c3352df8c9973f76e11356bd49f058ec0d38e7
link
/test istio-presubmit

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

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

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

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
ae9abddf11aa43536ef12404e1e4e1a88c5ca4da
link
/test e2e-simpleTests

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

prow/istio-presubmit.sh
f2c3352df8c9973f76e11356bd49f058ec0d38e7
link
/test istio-presubmit

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

prow/istio-unit-tests.sh
870af04eeca784e06fec2cd4b57c45f845bd0eca
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth-mcp.sh
870af04eeca784e06fec2cd4b57c45f845bd0eca
link
/test e2e-mixer-no_auth-mcp

prow/istio-unit-tests.sh
55e0f6fbb7969f3b1a0ac29b5b5cda67fa1df002
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth-mcp.sh
3a4c12145a94d7e99e185c2a864280d4aefc82df
link
/test e2e-mixer-no_auth-mcp

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

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

Needs approval from an approver in each of these files:

istioctl/OWNERS [rshriram]
pilot/OWNERS [rshriram]

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


Networking in MacOS.  info out of date

i struck being unable to connect with network on MacOS.
This...
https://github.com/flutter/flutter/issues/47606#issuecomment-568264294
is out of date.  The page refered to (that it refers to) does not mention this problem, such that it helps.
I have solved th problem but the docs are stale

This... #47606 (comment)
is out of date. [...] I have solved th problem but the docs are stale

That's a three-year old comment in an issue; issue comments aren't documentation.
The actual documentation is up to date.


[Bug]: GenerateSequence is broken on SDF

What happened?
The transform GenerateSequence.from(0).to(...).withRate(...) that is expanded into a streaming source (that is bounded, as there's a maximum number of records read) is broken after it was migrated from an UnboundedSource based implementaion.
For smaller data sizes, the source works as expected, and a sequence is generated properly.
For larger data sizes, the transform causes workers to OOM and never make progress.
Reasons:

Firstly, the maximum number of initial splits is 100: https://github.com/apache/beam/blob/master/sdks/java/core/src/main/java/org/apache/beam/sdk/io/BoundedReadFromUnboundedSource.java#L157-L161

This makes it such that each individual split can be very large for medium data sizes (over 100k elements per split).

Secondly, the consumption is implemented as a simple DoFn that consumes the whole source without checkpointing halfway: https://github.com/apache/beam/blob/master/sdks/java/core/src/main/java/org/apache/beam/sdk/io/BoundedReadFromUnboundedSource.java#L189-L212

This is what causes ooms for workers before they can make any progress.
(here's the expansion for GenerateSequence: https://github.com/apache/beam/blob/master/sdks/java/core/src/main/java/org/apache/beam/sdk/io/GenerateSequence.java#L242-L258)
I found that the expansion always became a BoundedReadFromUnboundedSource if we had from and to parameters.
Issue Priority
Priority: 1 (data loss / total loss of function)
Issue Components

[ ] Component: Python SDK
[X] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[X] Component: IO connector
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[X] Component: Google Cloud Dataflow Runner

@lukecwik could you take a quick look at this and let me know if my assessment is correct?

The expectation is that the runner will checkpoint the bundle allowing the SDF to be checkpointed if it detects that the bundle has been running long enough or has done enough meaningful work.
Also the conversion only outputs one record at a time, is there a DoFn buffering all the intermediate output downstream?

After looking through the code the issue is that the https://github.com/apache/beam/blob/6ba647333c4c69fb6dfc65929456c7c11570382f/sdks/java/core/src/main/java/org/apache/beam/sdk/io/BoundedReadFromUnboundedSource.java#L184 is a normal DoFn which forces outputting all the records that are part of the split. This doesn't support checkpointing which causes OOMs in Dataflow since it buffers all the output for the bundle.
https://github.com/apache/beam/blob/6ba647333c4c69fb6dfc65929456c7c11570382f/sdks/java/core/src/main/java/org/apache/beam/sdk/io/Read.java#L455 is an SDF wrapper for unbounded sources.

If this has never worked on SDF, is it P1? It does seem like trouble that it cannot be used in portable runners in some cases. How widespread is the problem it causes?

It is primarily uses for benchmarks and slowly changing side input patterns.

this is only for streaming GenerateSequence with a to and a from parameter. And for very large sequences. If it's being used for slowly changing side inputs, it usually doesn't have a to parameter, (I think?) so in that case it is not broken

I would say since this has been broken for a long time without too much complaint P2 should be OK. We don't need it included in our alert email of urgent things being neglected.


[CREATE MEASURES V2] add base sceleton for V2 version (separated namespace, controllers, new associations so on)

TRELLO CARD

 [DIT] Create measures - iteration


Bird misses when you both remember a skill and learn a skill at the same level up

2020-10-07 16:38:01.205 FFTBattleground: Nizaha, you advanced to Level 19! Your gil floor has increased to 676! You learned the skill: Gobbledeguck! You remembered the skill: EquipPerfume!

Won't fix in Bird 1.0, fixed in Bird 2.0


Connections topbar button opens Network tab of the info window instead of Peers tab.

The problem is as stated in the title.

Issue is solved in #26 so closing this issue.


Enhancement to drag_target

Steps to Reproduce
LongPressDraggable ALWAYS provides haptic feedback. This is not always required or wanted.
Could this be made an option.

If you would like to submit a PR to add this feature we would certainly be happy to review and land it.

From my understatement, this was fixed with the PR. Should the issue be closed.


Allow recorder inheritance

When trying to build a custom recorders which all inherited from a base class I ran into some issues where the config object was resolving values from the base class name, causing the recorder not to run.
Technically only the Concerns need to be updated to fix this, but I've gone ahead and updated the built-in recorders as well so that they can be extended and have their own configs.

I don’t think the recorders should be updated at this point, only the concerns.

@timacdonald thanks for the feedback, have removed those extra changes now


add support for untracked files (git only) - version2

Hello,
I'm sorry but I use git only ... at least I am sending a cleaner solution. When you have time, check it. I hope it could be acceptable.
Thanks
Hugo

I have just finished with the release of the new 2017 PyCon web site, and will try to get to this issue this week!


feat(handler) expose healthiness of targets of upstreams

Based on https://github.com/Kong/kong-plugin-prometheus/pull/70
Thanks @cedar715

:tada: now tests are passing \o/

design discussion: what if a targets is removed from upstream, do we want to remove it from metrics? the targets might be last seen in a certain state and may cause trouble if someone creates alerts around those metrics

@fffonion IMHO prometheus collects the metrics of the moment. To query the past we could use the time-series db, and increase the collect time for a more granular view.

@carnei-ro yeah you are right on prometheus part. however in this plugin we never expire or delete a metrics (though i believe it's supported by the underlying library). that means a certain metrics will be present in the /metrics output forever, unless kong restarts.
when it comes to upstream/targets, it's very likely some of them goes away, and we will end up putting legacy metrics into prometheus.

@fffonion I'm a little confused about "putting legacy metrics into prometheus". Do you have any tip to I implement it on the code and keep this PR going?

Yeah, @fffonion good catch and we need to solve this problem before we can merge this PR in.
@carnei-ro, what he is saying is if you remove a target from upstream, the target should not be present in the /metrics output. With the current code in the PR, that is not the case. If a user removes a healthy target from an upstream, the plugin will continue to report the target as healthy in the /metrics output. What should happen here is that the target in question should be removed from the output of /metrics.

@hbagdi is there any examples of things that are removed from the prometheus collects, for reference that what I have to do?

@hbagdi is there any examples of things that are removed from the prometheus collects, for reference that what I have to do?

None at the moment. Let's wait for @fffonion to respond. I'm hoping he has an idea of how to work around this problem.

gotcha, I can do an metrics.upstream_target_health:reset()
It makes the targets and upstreams metrics "ephemeral", once, every loop it is wiped out and recreated.

@hbagdi @fffonion I wrote tests to ensure old metrics are not showing.

rebased

@fffonion @kikito Let's make sure to do 0.9.0 release once this is merged in and then bump the dependency in kong/kong.
We should ensure that this feature ships with Kong 2.1.0.

Apart from one outstanding question, the changes look good. I'll leave the approval to @fffonion.

Thank you for the perseverance in getting this in @carnei-ro!
If you have not already done so, please fill in the contributor form for some swag.

Thank you for the perseverance in getting this in @carnei-ro!
If you have not already done so, please fill in the contributor form for some swag.

Thank you @hbagdi! I will fill the form, I have this other PR merged too https://github.com/Kong/kong/pull/5969


Add CSVs and instructions for downloading images

Here's the CSVs and download instructions.
We still need the citation for the Monteiro Data from @C-G-L. I can update the STRI taxonomic labels after @C-G-L has a chance to resolve the lingering questions (so it's published on HF).
The notebooks setting these all up from the full CSV you gave me are here.

@ramirezmichelle, I updated the STRI image taxa information from @C-G-L and updated the distribution graphs accordingly.
I also set up source URLs for the STRI data pointing to the HF repo (as they should be once uploaded).
I'm just waiting on confirmation of the appropriate citation for the STRI sample, then this will be ready to go.


add threading tests

Description
Adds tests for #1210.
Note, turns out testing coverage of stuff running in another thread is tricky.  So in addition to actually running stuff in the other thread, I run the workers in the main thread here to test various methods.
Type of change

[x] tests

How has this been tested?

[x] the test suite for my feature covers the qt.threading module
[x] all tests pass with my change

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

I added a note, since we don't want people looking through tests and thinking calling worker.work() is a good practice.


Ollama GPU Process does not automatically terminate after inactivity

Noticed with recent releases the ollama process does not get automatically terminated after a period of inactivity, idling the GPU process and keeping the last used model in VRAM. This also increases the time required to load a new model into VRAM and increases 'standby' power usage of the GPU.
I am deploying ollama via Docker and tested with the latest version v0.1.20.

me to!!!

Same here. Model gets unloaded after some time but still ~120MB on the GPU preventing to switch into lower power states.

Closing as dup of #1848


ClassNotFoundException Using Log4j and Grails 2.4.4

I'm trying to get raven up and running in Grails 2.4.4 with Log4j. I'm able to call vanilla Raven in my source, but whenever I try and instantiate a SentryAppender I get a ClassNotFoundException.
My buildconfig.groovy and source are here:
http://pastebin.com/MuVWUpf3
Relevant stacktrace:
http://pastebin.com/dtV3Cguv
I have tried both 7.0.0 and 7.0.1-SNAPSHOT and neither work. I've also tried including just raven-log4j and both raven-log4j and raven.

I tried with both 6.0.0 and 5.0.x. with no luck.

Yeah, I've recreated the issue locally. It seems to be related to Grails + Tomcat, it looks like people have had issues with other Appenders. I'm trying to figure out a solution now, hmm.

OK, the only way I've been able to get it work is by disabling Grails forking in BuildConfig.groovy:
grails.project.fork = [
    // configure settings for compilation JVM, note that if you alter the Groovy version forked compilation is required
    //  compile: [maxMemory: 256, minMemory: 64, debug: false, maxPerm: 256, daemon:true],

    // configure settings for the test-app JVM, uses the daemon by default
    test: false, // [maxMemory: 768, minMemory: 64, debug: false, maxPerm: 256, daemon:true],
    // configure settings for the run-app JVM
    run: false, // [maxMemory: 768, minMemory: 64, debug: false, maxPerm: 256, forkReserve:false],
    // configure settings for the run-war JVM
    war: false, // [maxMemory: 768, minMemory: 64, debug: false, maxPerm: 256, forkReserve:false],
    // configure settings for the Console UI JVM
    console: false // [maxMemory: 768, minMemory: 64, debug: false, maxPerm: 256]
]

This is some real class loading wonkiness. It works fine in Grails 3 FWIW (though the new default is logback, but I don't think that's related).

Hey @bretthoerner. Disabling forking did fix the ClassNotFoundException. Forking helps us load a bunch of environmental data and also allows grails to autocompile files while we're in dev mode. It definitely wouldn't be a permanent solution.
When I loaded the sentryAppender I started running into a whole series of issues actually getting it to log properly. I'm investigating if this is an issue with my config or grails integration with raven.
I may also look into using another logger or upgrading to grails 3 (we've discussed that separately). Most likely I'll end up writing a wrapper around Raven itself to play nicely with our codebase.

Thanks for the update @mattgerstman, do you mind letting us know if you find anything else out?

@bretthoerner. I finally got a chance to spend some more time looking into this. I discovered we really only use forking for our development environment NOT in production. In prod we compile a grails war and run it under tomcat which seemed to resolve all the class loading wonkiness.
I had to clone the SentryAppender file and include it directly in our package to set up sentry in development. Once I got it working locally, I removed the local version and set up an environments block to only load SentryAppender in production. Here is my appenders block for posterity:
appenders {
    environments {
        // This block is set up to use the stock raven SentryAppender in
        // production. Sentry Appender runs into all kinds of
        // class loading weirdness when used in a forked grails environment
        production {
            appender new com.getsentry.raven.log4j.SentryAppender(
                name: 'sentryAppender',
                dsn: 'REDACTED',
                threshold: org.apache.log4j.Level.WARN
            )
        }

        // Uncomment this block if you need to test sentry
        // in a dev environment
        // development {
        //    appender new com.REDACTED.REDACTED.SentryAppender(
        //        name: 'sentryAppender',
        //        dsn: 'REDACTED',
        //        threshold: org.apache.log4j.Level.WARN
        //    )
        // }
    }
}

Thanks for the update. I'm surprised there's not a different dependency scope in Grails/Gradle we can use. For example I recently discovered that for Gretty you need to use the gretty scope (instead of compile) to make loggers available to the containers before the application even starts. I feel like something similar would prevent you from having to copy the class.

Guys, some time has passed but I found a solution based in @mattgerstman answer that might be useful for someone else. At least, something better (for me) than disabling  forking.
It has nothing to be with raven but with grails the problem.
At least in my case, what I did was add the maven dependency and then try to add the appender in log4j.
The thing is that grails first executes the piece of code for the log4j initialization and then compiles the maven dependencies.
Different to what @mattgerstman  did, was going to the raven-log4j github repository https://github.com/getsentry/raven-java/tree/master/raven-log4j/src/main/java/com/getsentry/raven/log4j  downloaded the latest SentryAppender.java and stored it in src/java/my/package/sentry and left it there always.
Then in Config.groovy did something similar to what was suggested:
`
appenders {
environments {
// This block is set up to use the stock raven SentryAppender in
// production. Sentry Appender runs into all kinds of
// class loading weirdness when used in a forked grails environment
production {
appender new my.package.sentry.SentryAppender(
name: 'sentry',
dsn: 'REDACTED',
threshold: org.apache.log4j.Level.WARN
)
}
    // Uncomment this block if you need to test sentry
    // in a dev environment
    development {
        appender new my.package.sentry.SentryAppender(
            name: 'sentry',
            dsn: 'REDACTED',
            threshold: org.apache.log4j.Level.WARN
        )
    }
}

}
root {
warn 'stdout', 'sentry'
error 'stdout', 'sentry'
additivity = false
}
`
and it's working in development and production... I guess I could also remove the environments since the behavior is the same always.
hope it helps!

@andresarslanian First off. Thanks for getting involved in this. Somehow seeing this issue come back up brightened my mood on this awful day.
To clarify your solution, you downloaded the sentryAppender and checked it in to source, is that correct?

Hi @mattgerstman
Yes. In steps:

Went to https://github.com/getsentry/raven-java/tree/master/raven-log4j/src/main/java/com/getsentry/raven/log4j and downloaded the latest SentryAppender.java

Added the SentryAppender.java to src/java/my/package/sentry

Modified the original package name of SentryAppender.java to be my.package.sentry

Modified Config.groovy in the log4j section and added:

  appenders {
    environments {
        // This block is set up to use the stock raven SentryAppender in
        // production. Sentry Appender runs into all kinds of
        // class loading weirdness when used in a forked grails environment
        production {
            appender new my.package.sentry.SentryAppender(
                name: 'sentry',
                dsn: 'REDACTED',
                threshold: org.apache.log4j.Level.WARN
            )
        }

        // Uncomment this block if you need to test sentry
        // in a dev environment
        development {
            appender new my.package.sentry.SentryAppender(
                name: 'sentry',
                dsn: 'REDACTED',
                threshold: org.apache.log4j.Level.WARN
            )
        }
    }

  }

  root {
    warn 'stdout', 'sentry'
    error 'stdout', 'sentry'
    additivity = false
  }

Everything is working in development and production!

Hope it helps!

That's effectively what we ended up doing. I also modified that source a bit to do some fun stuff with tagging. I submitted a PR back to master for it, but I never got around to doing it for the other appenders so we closed it.

Thanks for the update, both of you. Should we still consider this open or is this firmly on the Grails side of things?

@bretthoerner I think you can close it. This is a grails ~2.4.x issue.

Thanks, if it comes up any more I'll try to document this. For now we'll depend on Google. ;)


code smell

Refactoring some of the SOC method code I faced a structure that smells  run in L37
In this structure you checke twice if year == 0. My question is the following, is it normal that we don't perform the same thing ?

If yes then you should put it outside the for loop and start at range(1, io.end-io.start) to avoid the if tests at each loop.

If not then then init of  organic_carbon_change and lc_transition should be done outside to make sure that every year have the same computation

Illustration using arrays
Instead of
for i in range(10)
    if i == 0:
        toto = [f'fill {i}']
    else:
        toto.append(f'fill {i}')

You would prefer
toto = []
for i in range(10)
    toto.append(f'fill {i}']

I tried to fix the code smell by removing the if clause in the for loop. I still have some doubt on These lines of code. I have used the same lines  here. What can be done to improve this section?

Based on the documentation, the remapmethod return the actual object so you don't need to create a tmp lc_transition_climate_coef_temporary
lc_transition_climate_coef =  lc_transition \
    .remap(pm.IPCC_lc_change_matrix, pm.c_conversion_factor) \
    .where(lc_transition_climate_coef_temporary.eq(333),climate_conversion_coef) \
    .where(lc_transition_climate_coef_temporary.eq(-333), ee.Image(1).divide(climate_conversion_coef))


Limits of analysis doesn't work

From #908, you had added the new options to limit the analysis. But we test that it doesn't work as wished.
Such as analysis.limits.maxFunctionAnalysisTime，we set the time arbitrarily and test the results, but we got lots of functions with analysis more than 0.00002, the code shows:
bv = BinaryViewType.get_view_of_file_with_options(bndb_file_path, update_analysis=True, options={"analysis.limits.maxFunctionAnalysisTime":0.00002})     for func in   ##bv.functions:         print(func.analysis_performance_info.values())
and the partial results is that:

dict_values([0.00223859])
dict_values([0.001841212])
dict_values([0.007671538])
dict_values([0.001371252])
dict_values([0.004085607])
dict_values([0.008869185])
dict_values([0.003579045])
dict_values([0.00389014])

and we got the same numbers of functions(4897) and total analysis time(73s) with the analysis without limits.
Such as analysis.limits.maxFunctionSize，we set the size arbitrarily and test the results, but we got lots of functions with size more than 30, the code shows:
    bv = BinaryViewType.get_view_of_file_with_options(bndb_file_path, update_analysis=True, options={"analysis.limits.maxFunctionSize":30})     for func in bv.functions:         print(func.analysis_skipped)         print(func.total_bytes)
and the partial results is that:

False
30
True
34
False
26
True
96
False
30

and we got more numbers of functions(5860) and less total analysis time(17s) with the analysis without limits.
But when we got the disassembly_text of each basic block, we found there is a great difference between limited analysis and unlimited analysis, and the function name is odd and lots disassembly_text of the block is meaningless or wrong compared with the correct disassembly text.
and some functions name like this:

sub_1f17c4
sub_1f17d4
sub_1f17f4
sub_1f1804
sub_1f1824
sub_1f1844
sub_1f1af4
sub_1f1c84
sub_1f1ca4
sub_1f1cc4
sub_1f1ce4
sub_1f1d04

We aim to analyze a mass of ".so" files in apps and get the disassembly text of every block. Because we've run into situations where analysis takes up a lot of time and we want to jump these files or only jump the timeout function and get correct disassembly text, so we try to add some limits during analysis. Some files with the size of 2M take up more than 2000 seconds and some are 7M only take up 300 seconds. So we can't know in advance which ones will take more time from the size of the file without analysis.
We tried some timeout monitoring like eventlet and signal in python, but it doesn't work until the analysis is done. And the added options in #908 seem doesn't work as wishes.
Are there any good methods? Or is there something wrong with my implementation?
If so, please give an example to guide me on what to do, thanks!

Please have a look at theanalysis.mode setting.

Please keep in mind that a setting like analysis.limits.maxFunctionAnalysisTime is a best effort type of limit. Analysis of a function that exceeds that limit will be halted, once the analysis reaches the next checkpoint. The analysis time for a function with a time limit will be n (limit) + ε (some small additional time).
As far as for the size. The rational is very similar. The maxFunctionSize limit is used to limit the size of a function that Binary Ninja will analyze and decompile. For example, I set a limit to 30 bytes, and main is 44 bytes the following output would be realized:
>>> current_function.total_bytes
44
>>> current_function.analysis_skip_reason
<AnalysisSkipReason.ExceedFunctionSizeSkipReason: 2>

Thanks! It is very useful, and I want to try some other limits. But I can't find the detailed description of each limit as you showed above in Python API. Such as the optional parameters of analysis.mode. So where can I get it including the other limits?

Open SettingsView in the UI. You can open it via menu or Cmd or Ctrl +.
The Settings are also documented online in the getting started guide.

This issue seems to be resolved.


Bugfix/assertion result issue

Which issue ticket is this pull request for, and is the ticket now complete?
https://github.com/usebruno/bruno/issues/**121** (Complete)
Briefly describe your change.
Issue : Assertions are still displayed in the Tests tab after deletion
After Fix: When we delete the assertion in the request tab, it is getting deleted in the Tests result tab too.
What parts of the application are affected by your change?
Tests result tab
How did you test your change? If relevant, which role(s) and/or customer configuration(s) did you use?
Created a request
Add assertions in Assert tab.
Save and execute request.
Assert results should display in Tests tab.

Save and execute request.
Assert results are not displayed in Tests tab.

Thanks for this @bharathbdev
Congrats on your getting your fist PR merged! Welcome to the project!


How to print only the equations of sub models, such as the Swelling only model in particle models

You have to print the equations of the full model and look for the lines corresponding to the part you are interested in


Design and Deploy Your First Integration Flow

Tutorials: https://developers.sap.com/tutorials/cp-starter-integration-cpi-design-iflow.html
Write here how you think we can improve the tutorial ...

in  Step 4: Add JSON to XML converter
<<< 2. Connect the converter to the message path by clicking on the message path.
TIP: When you place your cursor on the message processing path, you see it change to green color. >>>
The message processing path is never changing to green color,eve after correctly placing the converter on the path

@veeraa83 - thanks for noticing the issue and letting us know.
With the recent enhancement, the color changing scheme is removed. I'll update the tutorial accordingly. All that you have to do now is to place the connector in the message path.
Regards,
Karuna


chore: quantitative diff

Quantitative test is not going to fail even if more false positives are detected
A comment is added to the PR showing the results of the testing
Quantitative test is executed only if there are changes under rules/ folder

Example of printed comment in a PR:
📊 Quantitative test results:
⚠ Quantitative testing detected new false positives
📝 Total false positives: 408 -> 10407

Diff details

3c3
<   "falsePositives": 408,
---
>   "falsePositives": 10407,
10c10
<     "933160": 1,
---
>     "933160": 10000,
15c15
<   "totalTime":<PHONE_NUMBER>
---
>   "totalTime":<PHONE_NUMBER>

@M4tteoP Do you want to merge this one?

Yes 💯


Add Venmo to intent filter list in AndroidManifest.xml

cc @chiragsalian
Fixed Issues
Fixes https://github.com/Expensify/Expensify.cash/issues/3692
Tests

Sign-up to Expensify.cash with a US phone number and validate that account (Account A)
Create another account with a different US phone number (Account B) that has the Venmo app installed on their mobile device.
As account A, Complete the request money flow and send a payment request to account B (make sure the IOU report currency is USD).
Log-in as account B and click the pay button
Verify that Pay with Venmo is visible as an option in the dropdown

QA Steps
Steps above.
Tested On

[ ] Web
[ ] Mobile Web
[ ] Desktop
[ ] iOS
[X] Android

Android Screenshots

Self merging after all tests passed.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

CP staging label is needed.

:warning: :warning: Heads up! This pull request has the CP Staging label. :warning: :warning:
Merging it will cause it to be immediately deployed to staging, even if the open StagingDeployCash deploy checklist is locked.

🚀 Cherry-picked to staging in version: 1.0.73-2🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production in version: 1.0.73-3🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to staging in version: 1.0.73-4🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production in version: 1.0.74-0🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


A11y_Finance Digital Assistant_Profile_like_AI4W-Ensures buttons have discernible text (.webchat__suggested-action__button[aria-keyshortcuts="Alt\ +\ Shift\ +\ A"])

Environment Details:

Application Name: Finance Digital Assistant.
#URL: Finance Digital Assistant (microsoft.com)
OS Details:
Microsoft Windows 11 Enterprise Version 21H2(OS build: 22000.318)
Chromium Edge Version: Version 100.0.1185.44 (Official build) (64-bit)

Issue:
Ensures buttons have discernible text (button-name - https://accessibilityinsights.io/info-examples/web/button-name)
Target application:
Finance Digital Assistant - https://staging-fda.microsoft.com/fda/?&hostappid=1ED4BBD7-CF02-41D2-8363-8F21EF7F07F5
Element path:
.react-film__filmstrip__item:nth-child(1) > .webchat__suggested-action.webchat--css-ohhjn-xccdat.webchat--css-ohhjn-oe4onf > .webchat__suggested-action__button[aria-keyshortcuts="Alt\ +\ Shift\ +\ A"]
Snippet:

How to fix:
Fix any of the following:

Element does not have inner text that is visible to screen readers
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Element has no title attribute
Element's default semantics were not overridden with role="none" or role="presentation"

MAS Reference:
MAS 4.1.2 – Name, Role, Value

#A11yMAS;#A11ySev2;#HCL;#WCAG4.1.2;#Accessibility;#Win11-Edge(Chromium);#BotFrameworkWebChat-Aug21;#Linked:Bug8884824;#LinkedBug;

Bug copied from Azurebot team Bug id:-BUG 8884824

Thanks @KattaBhargav. This will take some time, my backlog of accessibility stuff is quite full right now. 😁

There are two things need to be done to resolve this issue:

Web Chat to support imageAltText field

Currently, the schema did specify the imageAltText field
However, the schema did not specify where to use this field
https://github.com/microsoft/botframework-sdk/issues/6527

Bot author needs to use this field

Currently, the bot does not reply with imageAltText

This is fixed on Web Chat side in #4441.
The bot author would still need to modify their bot to use this field. Instructions have been given above.


Mocked the Logout process (#214)

closes #214
Updated reducer and actions related to auth to mock the logout process.
I have also set the user manually in the auth state check  src\reducers\auth.js

Logged In

Logged Out

Great work! Thanks for your help.

👍 I would love to mock the login process as well, if that is required in the future assign it to me.


hive_flutter : getLibraryDirectory option  for IOS

If we on the 'UISupportsDocumentBrowser' or  'UIFileSharingEnabled'  in IOS plist,  the default getApplicationDocumentsDirectory will expose the all data in default  iOS  Files  app or iTune.
If we have an option to choose the getLibraryDirectory then this problem will be solve
Version

Platform: iOS, Android, Mac, Windows, Linux, Web
Flutter version: [e.g. 1.5.4]
Hive version: [e.g. 0.5.0]

Hey, I believe this is the way to fix this issue. (iOS and Android only)
    if (Platform.isAndroid) {
      // If Android use default location
      await Hive.initFlutter();
    }else{
      // This will not show up in Files app.
      await Hive.initFlutter((await getLibraryDirectory()).path);
    }


⚠ Bofrost.lu has degraded performance

In 1ccf1a5, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1462 ms

Resolved: Bofrost.lu performance has improved in d41a57d after 8 minutes.


NEXT Date Picker and Date Handling

[!WARNING]
This issue is a work in progress.

This will act as a hub to centralize this information.
Maintainer Requests
The following requests are coming straight from the Skeleton team. These are highly likely be implemented:

[ ] Review: https://date-fns.org/
[ ] Review: https://react-day-picker.js.org/

Community Requests
The following requests have come from the community and are under consideration:

https://github.com/skeletonlabs/skeleton/issues/1452

Bugs and Issues

n/a

Feedback
If you have additional updates or requests for this feature, please do so in the comments section below.

Haven't used day picker yet, but date-fns is my current go to for Date Functionalities.

bits datepicker integrates very well with Skeleton.

https://vanilla-calendar.pro/


Possible race condition for killed Docker containers

I'm running datadog-agent 6.1.0 on Kubernetes 1.8.9 (running on GKE).
I deleted a handful of pods in my cluster and for each corresponding container I saw two logs from datadog-agent:
[ AGENT ] 2018-03-26 09:31:44 UTC | ERROR | (docker_main.go:118 in fetchForDockerID) | Failed to inspect container cfc65ca71e3fc63124d582317f54d07e51d9f4ba2ad6a4593ed7e79362146c45 - Error: No such container: cfc65ca71e3fc63124d582317f54d07e51d9f4ba2ad6a4593ed7e79362146c45
[ AGENT ] 2018-03-26 09:31:44 UTC | WARN | (tagger.go:245 in Tag) | error collecting from docker: Error: No such container: cfc65ca71e3fc63124d582317f54d07e51d9f4ba2ad6a4593ed7e79362146c45

These logs come from https://github.com/DataDog/datadog-agent/blob/e84f7ad7829543acb2f9ac1fe6a4d1a53d3426bc/pkg/collector/corechecks/containers/docker.go#L218 and https://github.com/DataDog/datadog-agent/blob/c98beb40bbaee155152cf43e63ebe794a918625b/pkg/tagger/tagger.go#L245.
This doesn't look like an error condition to me (or even something that should be warned about). Indeed it appears in the second case that the code is trying to handle this condition explicitly in the clause before. (This looks like it's somewhat related to #1345, so perhaps that just isn't working as expected yet.)

We're seeing similar behavior on containers that were cleaned up by docker-gc using datadog-agent 6.1.2 on kube.

We use datadog-agent 6.5.2. The problem still exists. Looks like because of this we don't see certain docker events.

This is also affecting us. We have an automated system that deletes old containers. We're getting spammed with these "errors" in our logs.

Also seeing this problem, besides our agents are getting restarted and I'm not sure if thisis the reason (probe just fails with 12 unhealthy components after a minute)

All,
Apologies for the delay on this issue. This log can occur in a few scenarios. Especially if the containers churn - As you can see we readjusted the logging in #2485 so we do not log misleading errors that are actually info/debug.
We will be releasing the new version of the agent 6.8.1 shortly, which will embed this fix.
Thank you very much for your patience.
Best,
.C

@CharlyF did this fix make it out yet? We're still seeing the issue in 6.9.0 on Kubernetes 1.11.7.

Closing as this fix was released. Feel free to reach out if you are still having issues.

I still have Agent 6.10 flooding the logs with these exact same error messages at the same log levels.

I have the same error message and seems that the stats metrics API doesn't work. I am not sure if the error causes the problem.

Same with 6.13.

v6.14.0 does the same

Confirm it happens in 6.10.1


Update Language Models to have a boolean flag supports_tools

First part supports_tools. Should the migration set support_tools to false for non-OpenAI models?
Fixed #435

@stephan-buckmaster Nice PR, this is great! I flagged one small copy edit, and I do agree with your question that we should default things. So two small additions:

In registerable.rb let's add an explicit boolean flag when we initialize and set them to true and false, appropriately.

OpenAI says: gpt-4o, gpt-4-turbo, and gpt-4o-mini) have been trained to both detect when a function should be called
It looks like all the Anthropic models support tools
All the Groq models we're initializing support tools

Let's update that migration so that right after adds the column it sets the OpenAI models which don't support tools to false

Since OpenAI calls this Function Calling, should the check box include that in the label too?

Supports tools (function calling)

When I look over  the OpenAI list,  Which models support function calling? only these do not:

gpt-3.5-turbo-instruct and
gpt-3.5-turbo-16k-0613

Searching by LLM name and function calling, I find these don't either: mixtral-8x7b-32768, llama3-70b-8192, llama3-8b-8192

I am guessing @jlvallelonga's comment above taken care of with the recent merge into main?

I'll see you removed the context size from this issue. So it would be complete for now.

Good idea, I think like the copy you just wrote since it works in both phrases.
For these open-source models it's more confusing as to whether they support function calling because even if the original model didn't inherently support it, later fine-tunings of the model sometimes add it in. In our case, all the open source models that come pre-configured are through Groq and here's their documentation where they claim that they all support it: https://console.groq.com/docs/tool-use
Yes, main is merged in with some fixes for system tests so it's worth pulling that into your branch. They still aren't 100% fixed, they're still flaky sometimes and I haven't totally gotten to the bottom of it, but they're better.

Ok this could be ready. (Upstream was already merged)
The UPDATE statement in the db migration could be a bit more specific (has a groq-api-service), hard to tell if users are adding their own language models. I feel it becomes a bit unwieldy as users may have more than one such API service also (with different tokens).


Multiple line comments in code blocks disappearing

The code blocks generated by three back ticks in markdown are not allowing multiple single line comments to show past the first line ('//' lines after the first one are now invisible). No longer appearing as it did previously on Pub

This might be either a package:markdown issue or an issue with dart code syntax highlighting based on the analyzer package.

CL out for review: https://codereview.chromium.org/1410073003/

This was fixed in dbc4c7413889d5746f0dc13e958e2dc7f64f1e2d.

Nice one. That only took 138 days to fix.


Allow Duplicate Open Graph Image Tags

This PR adds the Open Graph image tag to the allowed duplicates. It also adds it's supporting tags that normally appear with an image tag.
Normally you can/would add multiple og:image tags to your page. An example use case for this is when sharing on Facebook the user will have a choice of the cover photo.

Hey @timneutkens, added some tests as suggested 😄

@timneutkens @garmeeh has this been bundled into any of the recent versions of next? I'm still seeing the same issue on 7.0.2 and 7.0.3-alpha.5.

The correct fix for this issue is #5800, and that is out on next@canary right now.

@timneutkens got it. I updated to @canary but seem to be hitting a separate issue now:
><EMAIL_ADDRESS>dev /Users/joncursi/Sites/cheddur/web
> dotenv node server.js

/Users/joncursi/Sites/cheddur/web/node_modules/next/dist/client/link.js:2
import { resolve, format, parse } from 'url';
       ^

SyntaxError: Unexpected token {
    at new Script (vm.js:83:7)
    at createScript (vm.js:267:10)
    at Object.runInThisContext (vm.js:319:10)
    at Module._compile (internal/modules/cjs/loader.js:685:28)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:733:10)
    at Module.load (internal/modules/cjs/loader.js:620:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:560:12)
    at Function.Module._load (internal/modules/cjs/loader.js:552:3)
    at Module.require (internal/modules/cjs/loader.js:658:17)
    at require (internal/modules/cjs/helpers.js:22:18)

Looks like there's a breaking change inside canary, but I'm not sure what. Could you help point me to the change I need to make to migrate from 7.0.2 --> canary, or would you be able to pluck these commits into a 7.0.2 canary release so I could have access to it?
Currently battling og:image duplication issues in production so that's why I'm pressing for it. Thank you!

It means you're doing something you shouldn't be doing in the first place, eg importing next/link in a custom server.

I'll fix it on the Next.js side, but this is really just wrong usage of next/link.


Unable to dump update + base_game.nca

I'm using this command line to use the update.nca with the base_game.nca to dump the full game:
hactool location\of\update.nca --romfsdir=C:\location\of\romfs --exefsdir=C:\location\of\exefs --basenca C:\location\of\base_game.nca
And I can -i the update or the base_game.nca separately and they'll show the correct titlekeys, because I have the titlekeys in the ~/.switch folder
however when used together with that command line, I get this: [WARN] Unable to match rights id to titlekey. Update title.keys?
but again, when I -i them separately, their correct titlekeys show up beneath the rightsID in the headers
And all that is output is:
Saving main.npdm to C:\Switch\Games\01007EF00011E000 - Breath of the Wild - Test\exefs\main.npdm...
Saving rtld to C:\Switch\Games\01007EF00011E000 - Breath of the Wild - Test\exefs\rtld...
Saving sdk to C:\Switch\Games\01007EF00011E000 - Breath of the Wild - Test\exefs\sdk...
Saving subsdk0 to C:\Switch\Games\01007EF00011E000 - Breath of the Wild - Test\exefs\subsdk0...

and it stops dumping, nothing in romfs

hactool doesn't support titlekey encrypted NCAs with the --basenca option for whatever reason, you can work around this by dumping a decrypted version of the base NCA using --plaintext and then using that as the base.


Support using both DESCRIPTION and environment.yml at the same time

I would like to be able to have an R-package repository with a DESCRIPTION file and environment.yml and have both listed dependencies installed.

I already have a package which uses DESCRIPTION. But when using it with Binder I want to have additional dependencies installed I only need in Binder.
e.g. jupyterlab-git or something like jupytext+r-rmarkdown to read Rmarkdown files as notebook.
Or would you say, that those should also go into the DESCRIPTION (not sure about python packages) or just install everything in postBuild?
postBuild is probably the way I will go for now (e.g. install the 2nd environment.yml), but this could make for a neat feature.
Ideas below
Something similar would be the dependecies vs dev_dependencies in npm or dart.
I would like to be able to define binder only dependencies, which do not make sense in a context without binder.
One approach would be to check for dependency files in binder/ and root.
├── binder
│   ├── environment.yml <- My Binder specific dependencies (e.g. jupyter-git)
│   └── postBuild
├── environment.yml <- My normal dependencies (could also be DESCRIPTION or requirements.txt)
└── notebook.ipynb

My background: I am working a platform to conduct health intervention studies. (as part of my Master thesis).
For the analysis of data, I want to provide the researchers with ways to easily work with Jupyter Lab (or RStudio). Binder would be perfect both for study conducting researchers and other researchers going through their results and findings (reproducibility).
Therefore dividing having 2 dependencies:

Dependencies I as the platform developer manage (like jupyterlab-git)
Additional dependencies the researcher wants to use

I will be looking into this tipp: Having a Binder Repo with just the default dependencies and pulling in the content later. But then I will also have to install researcher deps later on.

This is related to the underlying build tool, so I'm transferring it to repo2docker


Update Apache Datasketches to 3.3.0

This upgrades the version of Apache Datasketches to the latest version which includes fixes for corner cases and improvements to performance.
Tests were added to the existing integration tests in order to cover set difference.
See issue #10240

looks good to me


Overriding check config from plan

is there any way to override particular check config via plan JSON?
e.g I want to use oakpal basic checklist with one exception, with allowing subpackages inside.
how to do that?
I mean... http://adamcin.net/oakpal/oakpal-core/the-basic-checklist.html

@pun-ky yes, it should be possible to override specific configs. You should define a child of .checks[] with a .name property that matches the [[{moduleName}/]{checklist}/]{checkName} of the check you wish to override, an empty .impl property, and a .config object with key/value pairs to add/override wrt to the overridden check config.
Per your example:
    {
      "name": "basic/subpackages",
      "config": {
        "denyAll": false
      }

You can also use the override to completely skip the check:
    {
      "name": "basic/subpackages",
      "skip": true
    }

Cool. Thanks for explanation. Is such info available in docs?


Features

We fork based version. Now is time to fully extend it potential.
To have simple solution there will be some rules to follow in future:

one branch with github page
only styled aware elements are allowed (picture tag don't do anythink beside switch img)
elements duplicated if more than one setting to show (example: list type="disc")
only built in browser to test (not allowed example: list type="xyz")
proper footer with author attribution and us as maintainer this repo and license
change visibility of test page by collapsing as multi level detail tag.
Example code and preview:

  TITLE

ANYTHINK

HTML5

Headers
h1

update to all elements
segregate by:
-- doctype (html5 open by default, rest closed) and by
--- active (open by default)
--- obsolete (closed by default)
easier in nuxt/next enviroment to test page
-- snippets add to readme.md to get by ajax page

footer as iframe position fixed and non selectable from other repo
-- webo logo with link to website, original author, button to copy code for simple usage. Author as a param from iframe to have snippet for any website with example code


Add trim bar to preview seek bar

Currently broken because I have no clue how to use Flutter, but I got part of the way there so I'm making this PR now.
( The trim bar exists as RangeSlider, but the thumbs do not move. I have no clue why. :) )

So I'm going to want this to be integrated into the seek bar itself, instead of adding another separate slider. Like how trimming video on a phone works would be a good example. This is why I said it would need a lot more custom work, since it would need to be a custom slider that integrates both the functionality of RangeSlider and Slider together.

Ah that makes more sense. Due to my lack of Dart experience this will be a no-go for me...

No problem, I'll open an issue for it and take it on at some point


Issue with currency in customer order section, currency code doesn't get converted at orders page of customer.

Framework Version: 0.1.6

Framework Version: 0.1.6

Fixed


Error with docker compose

I am able to run the app on my local windows but I am facing an issue when running on a linux server.
This is the error I am getting
ERROR: for deb7f8db0841_bertsearch-master_bertserving_1  Cannot start service bertserving: OCI runtime create failed: container_linux.go:345: starting container process caused "exec: "/app/entrypoint.sh": permission denied": unknown
ERROR: for bertserving  Cannot start service bertserving: OCI runtime create failed: container_linux.go:345: starting container process caused "exec: "/app/entrypoint.sh": permission denied": unknown
I have tried adding RUN ["chmod", "+x", "/entrypoint.sh"] before the entrypoint in the dockerfile but its still not working

It is working. I had to add "/app/entrypoint.sh


#664 Enable support to specify AWS region for signing requests

Implemented adding a flag of --awsRegion to allow a user to specify which region to use when signing AWS requests.

closes #664


Publish releases on Github as well

According to Github the latest release was in 2017, which isn't the case. Apart from the discrepancy with crates.io, it also gives the impression of an unmaintained crate if someone only judges by GH releases. It'd be best if maintainers added changelog/notes to the tags to mark them as releases. Providing release notes is a best practice any way.
Just a suggestion for doing things better. Feel free to ignore. :)

We already tag releases.  Why should we publish them on Github?  Does anybody download Rust releases from Github anymore?

We already tag releases.  Why should we publish them on Github?  Does anybody download Rust releases from Github anymore?

We already tag releases.

Just a tag, doesn't count as a release by Github. On the main page of this repo, you'll find a very old release as the latest release.

Why should we publish them on Github? Does anybody download Rust releases from Github anymore?

No, it's not about the download/release artifacts but presenting information. AFAIK, there are no release notes on crates.io. I think I provided the reasons you should do this in the description of this MR.
If you don't see the point, feel free to close this issue and ignore me. :)

We already tag releases.

Just a tag, doesn't count as a release by Github. On the main page of this repo, you'll find a very old release as the latest release.

Why should we publish them on Github? Does anybody download Rust releases from Github anymore?

No, it's not about the download/release artifacts but presenting information. AFAIK, there are no release notes on crates.io. I think I provided the reasons you should do this in the description of this MR.
If you don't see the point, feel free to close this issue and ignore me. :)

Tags do show up on https://github.com/nix-rust/nix/releases
The problem is that you've done at least one "proper release publish" thing in the past, and it takes priority on the main page. If it's possible to delete, it should be deleted.

Tags do show up on https://github.com/nix-rust/nix/releases
The problem is that you've done at least one "proper release publish" thing in the past, and it takes priority on the main page. If it's possible to delete, it should be deleted.

I deleted the only Github Release.  The tags are still there.

I deleted the only Github Release. The tags are still there.

Great so there is no confusion at least. :+1:


When CNI is installed, Pods cannot communicate with each other

Bug description
When installing Istio with CNI enabled on GKE, I have the impression that pods cannot communicate with each other. For testing, I'm installing the following chart with default values, in the default namespace (which is labelled for Istio injection). All 3 Mongo pods are able to start and seems fine, but in reality there are 3 different replica sets with only one host in each one.
If I disable Istio injection, I have only one replica set with the 3 nodes in it.
I am not seeing any error in Istio logs, but maybe I'm not looking in the right place.
Affected product area
[X] Networking
Expected behavior
The MongoDB pods should be able to communicate with each other and form a single replica set.
Steps to reproduce the bug
Platform setup, then:
$ istioctl manifest apply -f manifest.yaml  (with the manifest provided below)
$ kubectl label namespace default istio-injection=enabled
$ helm3 install mongo stable/mongodb-replicaset

From this point, I can check if the replica set is correct by running:
$ kubectl exec mongodb-mongodb-replicaset-0 -c mongodb-replicaset -- sh -c 'mongo --eval="printjson(rs.isMaster())"'

I should have the following response:
"hosts" : [
        "mongodb-mongodb-replicaset-0.mongodb-mongodb-replicaset.default.svc.cluster.local:27017",
        "mongodb-mongodb-replicaset-1.mongodb-mongodb-replicaset.default.svc.cluster.local:27017",
        "mongodb-mongodb-replicaset-2.mongodb-mongodb-replicaset.default.svc.cluster.local:27017"
]

But I'm seeing:
"hosts" : [
        "mongodb-mongodb-replicaset-0.mongodb-mongodb-replicaset.default.svc.cluster.local:27017"
]

Version
$ istioctl version --remote
client version: 1.5.1
control plane version: 1.5.1
data plane version: 1.5.1 (5 proxies)

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.0", GitCommit:"9e991415386e4cf155a24b1da15becaa390438d8", GitTreeState:"clean", BuildDate:"2020-03-25T14:58:59Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15+", GitVersion:"v1.15.9-gke.24", GitCommit:"39e41a8d6b7221b901a95d3af358dea6994b4a40", GitTreeState:"clean", BuildDate:"2020-02-29T01:24:35Z", GoVersion:"go1.12.12b4", Compiler:"gc", Platform:"linux/amd64"}

How was Istio installed?
From https://istio.io/docs/setup/install/istioctl/ with the following manifest:
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  addonComponents:
    grafana:
      enabled: true
    kiali:
      enabled: true
    tracing:
      enabled: true
  components:
    cni:
      enabled: true
      namespace: kube-system
  values:
    sidecarInjectorWebhook:
      enabled: true
    cni:
      cniBinDir: /home/kubernetes/bin
      excludeNamespaces:
        - istio-system
        - kube-system
      logLevel: info

Prerequisites for GKE were followed (enable-network-policy and cluster admin permissions).
Environment where bug was observed (cloud vendor, OS, etc)
GKE with 3 n2-standard-2 nodes, Container-Optimized OS. Kubernetes version 1.15.9-gke.24 (same problem with 1.16.8-gke.8)
I have observed the exact same problem with a Kubernetes cluster on Scaleway (1.16.8 and 1.17.4)
istio-dump.tar.gz

Any news on this ? :) Do you need more for debugging ?


Latest build broke being able to update the List of Figures

Hi David,
I just noticed you pushed a new build onto the app. Any new updates to the build? The latest build broke creating/updating the List of Figures, as I had just finished cross-referencing all of the images onto my document and now update the list of figures. I also had attempted to delete the list and recreate the list. Nothing happened.
If you intended to remove the feature in the meantime I would appreciate the warning.
Thanks for all your hard work.

@CaptainMurasa I've pushed a fix. Is it still broken for you?

No, that's fixed! Thanks!
I do have some things to note:
The issue noticed was initially raised on Firefox (I'll check the version later) with no apps installed. When you pushed the fix, the List of Figures populated but it took forever to populate the pages where the figures were on.
It works perfectly right now on Chrome (v. 66.0.3359.139), but this is on a computer with (most likely) not the latest version of Chrome with no apps installed. (Work computer, the IT department at my workplace doesn't keep up with the latest updates for their software).
I agree with keeping with the beta label, it might be too finicky for Firefox users at the moment and it might not have worked at all last patch before this fix.
I appreciate your time and effort. Thank you!

Thanks for responding. The reason it takes forever is that Google Docs
Script does not allow access to page numbers, so the workaround is to
export the document to PDF and process it using PDF.js. This is painfully
slow for longer documents and those with many images.
On Fri, 22 Jun 2018 at 12:19, CaptainMurasa<EMAIL_ADDRESS>wrote:

No, that's fixed! Thanks!
I do have some things to note:
The issue noticed was initially raised on Firefox (I'll check the version
later) with no apps installed. When you pushed the fix, the List of Figures
populated but it took forever to populate the pages where the figures were
on.
It works perfectly right now on Chrome (v. 66.0.3359.139), but this is on
a computer with (most likely) not the latest version of Chrome with no apps
installed. (Work computer, the IT department at my workplace doesn't keep
up with the latest updates for their software).
I agree with keeping with the beta label, it might be too finicky for
Firefox users at the moment and it might not have worked at all last patch
before this fix.
I appreciate your time and effort. Thank you!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/davidrthorn/cross_reference/issues/24#issuecomment-399409454,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AI_q0JY8zZ39hTBQpNgmA-14AjeI_Onaks5t_NKlgaJpZM4UyssG
.

--
David Rowthorn
Full Stack Web Developer
www.davidrowthorn.net


Fix win line endings

Fixes:

per:
https://stackoverflow.com/questions/9845681/does-python-csv-writer-always-use-dos-end-of-line-characters
https://docs.python.org/3/library/csv.html#csv.reader
https://docs.python.org/3/library/csv.html#csv.writer
Specifically:

If csvfile is a file object, it should be opened with newline='' 1

[X] ❗ I have followed the Contributing to DVCLive guide.

[X] 📖 If this PR requires documentation updates, I have created a separate PR (or issue, at least) in dvc.org and linked it here.

Thank you for the contribution - we'll try to review it as soon as possible. 🙏

Codecov Report

:exclamation: No coverage uploaded for pull request base (1.0@9157570). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@          Coverage Diff           @@
##             1.0     #346   +/-   ##
======================================
  Coverage       ?   95.00%
======================================
  Files          ?       36
  Lines          ?     1682
  Branches       ?      132
======================================
  Hits           ?     1598
  Misses         ?       60
  Partials       ?       24

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Opening against main instead


Add Duration of AWS Video

Add Duration of AWS Video

@lucaswte Did you miss the extractVideoDuration function?

@lucaswte Did you miss the extractVideoDuration function?

Oh, I am sorry, I just added it.


don't report in progress until processing update after rootkey infra

rmv oob in-progress reporting when rootkey processed
add back as 1st state into handler entry state transition table so in-progress report is sent at beginning of update processing

@nihmenstr Would it be possible to review this. We are getting desperate for a fix. Thanks!

Closing this draft PR since PR https://github.com/Azure/iot-hub-device-update/pull/659 on which this was merged via this commit: https://github.com/Azure/iot-hub-device-update/commit/389755389a2922caa1b410935f99be7242ce3d5c


[Backport] Suppressing false positive CVE-2020-7791

Backport of #11215 to 0.21.1.

travis failure seems unrelated since is also failing on #11216


Infinite Scrolling Pagination

Thanks for the awesome package. Makes animating and sorting list so easy.
Will infinite scrolling pagination be part of the lib? Or do we have to handle it ourselves?
Hopefully the package being called what it is, could handle it internally :)

I thank you sincerely for your appreciation, unfortunately I abandoned the project due to lack of time and motivation, which was also partly due to the lack of donations received. Paginations was a feature I had planned to implement after fixing all bugs related to item moving animations (which was the most complex thing to implement).


Shahakl/merge dev main

Force merging to solve the CI error ClassiqAPIError: You are using an unsupported version of Classiq SDK


GET /api/user no match 403

Logs:
casdoor-1  | subOwner = built-in, subName = filwaline, method = GET, urlPath = /api/userinfo, obj.Owner = , obj.Name = , result = allow
casdoor-1  | 2024/05/01 07:47:44.420 [I]  (<IP_ADDRESS>: ) subOwner = built-in, subName = filwaline, method = GET, urlPath = /api/userinfo, obj.Owner = , obj.Name = , result = allow
casdoor-1  | 2024/05/01 07:47:44.423 [D]  |  <IP_ADDRESS>| 200 |   7.161392ms|   match| GET      /api/userinfo   r:/api/userinfo
casdoor-1  | 2024/05/01 07:47:44.543 [D]  |  <IP_ADDRESS>| 403 |   3.948479ms| nomatch| GET      /api/get-user
casdoor-1  | subOwner = built-in, subName = filwaline, method = GET, urlPath = /api/get-account, obj.Owner = , obj.Name = , result = allow
casdoor-1  | 2024/05/01 07:47:44.638 [I]  (<IP_ADDRESS>: ) subOwner = built-in, subName = filwaline, method = GET, urlPath = /api/get-account, obj.Owner = , obj.Name = , result = allow

The request to /api/get-user received a 403 error. The logs indicate that there is no match. Could this be an issue with the Casbin enforcer?
When a request does not match, it returns nothing like subOwner = built-in, subName = filwaline, method = GET, urlPath = /api/get-account, obj.Owner = , obj.Name = , result = allow. How can I debug this error?

@filwaline see docs about how to authenticate the Casdoor API: https://casdoor.org/docs/basic/public-api#how-to-authenticate-with-casdoor-public-api
And, don't mess with the Casdoor built-in Casbin policy, if you don't know how to do it correctly

@filwaline and, don't ask "cheap" questions in this issue list. This issue list is for bug reports, or more complicated questions. Not some place to answer the question that can be figured out in 3 minutes by reading docs. Please go to Discord if you want to ask.