text:
feat(grpc status codes): report grpc status codes via mixer

This PR implements the changes approved in https://tinyurl.com/yy2cwmv5 to report gRPC status codes in metrics (and provide better alignment with logs and metrics when reporting protocol). It also cleans up unused metrics dimensions.
Other PRs will be required to support the same feature set in v2 telemetry and to update the operator/installer config templates.
Partial fix for https://github.com/istio/istio/issues/12846
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ X ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@douglas-reid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-dashboard_istio
b4d87e5e499df25940cc35554d9cc7775b4707bf
link
/test e2e-dashboard_istio

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

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-dashboard_istio
b4d87e5e499df25940cc35554d9cc7775b4707bf
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
b4d87e5e499df25940cc35554d9cc7775b4707bf
link
/test e2e-mixer-no_auth_istio

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

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-dashboard_istio
b4d87e5e499df25940cc35554d9cc7775b4707bf
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
b4d87e5e499df25940cc35554d9cc7775b4707bf
link
/test e2e-mixer-no_auth_istio

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

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

@douglas-reid: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

e2e-dashboard_istio
b4d87e5e499df25940cc35554d9cc7775b4707bf
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
b4d87e5e499df25940cc35554d9cc7775b4707bf
link
/test e2e-mixer-no_auth_istio

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

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

@douglas-reid: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

e2e-mixer-no_auth_istio
b4d87e5e499df25940cc35554d9cc7775b4707bf
link
/test e2e-mixer-no_auth_istio

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

unit-tests_istio
5b53184206cb2fb6ffabf8ee274f2d08e17fedb1
link
/test unit-tests_istio

e2e-dashboard_istio
5b53184206cb2fb6ffabf8ee274f2d08e17fedb1
link
/test e2e-dashboard_istio

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

@douglas-reid: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

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

unit-tests_istio
5b53184206cb2fb6ffabf8ee274f2d08e17fedb1
link
/test unit-tests_istio

e2e-dashboard_istio
5b53184206cb2fb6ffabf8ee274f2d08e17fedb1
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
5b53184206cb2fb6ffabf8ee274f2d08e17fedb1
link
/test e2e-mixer-no_auth_istio

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

@douglas-reid: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
5b53184206cb2fb6ffabf8ee274f2d08e17fedb1
link
/test unit-tests_istio

e2e-dashboard_istio
5b53184206cb2fb6ffabf8ee274f2d08e17fedb1
link
/test e2e-dashboard_istio

e2e-mixer-no_auth_istio
5b53184206cb2fb6ffabf8ee274f2d08e17fedb1
link
/test e2e-mixer-no_auth_istio

integ-istioio-k8s-tests_istio
5b53184206cb2fb6ffabf8ee274f2d08e17fedb1
link
/test integ-istioio-k8s-tests_istio

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

@douglas-reid: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

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

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

Ping. This now includes updates for the merged manifests/.

i am not qualified to review, lmk once a mixer owner approves and I can give it the approval

@douglas-reid: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

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

@douglas-reid: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
5ab8caf78373c87514495a35cab231fde0a4e6cf
link
/test gencheck_istio

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

@douglas-reid: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
5ab8caf78373c87514495a35cab231fde0a4e6cf
link
/test gencheck_istio

unit-tests_istio
5ab8caf78373c87514495a35cab231fde0a4e6cf
link
/test unit-tests_istio

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

@douglas-reid: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
5ab8caf78373c87514495a35cab231fde0a4e6cf
link
/test unit-tests_istio

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

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

@douglas-reid: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
5ab8caf78373c87514495a35cab231fde0a4e6cf
link
/test unit-tests_istio

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

gencheck_istio
9a2a26f587b090657a57006a66d71d9a6bc966b0
link
/test gencheck_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
9a2a26f587b090657a57006a66d71d9a6bc966b0
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

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

@douglas-reid: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

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

e2e-bookInfoTests-envoyv2-v1alpha3_istio
9a2a26f587b090657a57006a66d71d9a6bc966b0
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

gencheck_istio
412143a5ea1db61b2bca1683b6e684493fe80da8
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.

@douglas-reid: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

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

e2e-bookInfoTests-envoyv2-v1alpha3_istio
9a2a26f587b090657a57006a66d71d9a6bc966b0
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

gencheck_istio
412143a5ea1db61b2bca1683b6e684493fe80da8
link
/test gencheck_istio

unit-tests_istio
412143a5ea1db61b2bca1683b6e684493fe80da8
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.

Gentle ping on a review here. This PR brings the v1 telemetry pipeline in line with changes already made to v2.

Perhaps, could you update the Default Metrics page? https://istio.io/docs/reference/config/policy-and-telemetry/metrics/
I also see on that page the sentence They can be found here under the section with “kind: metric” while, that kind: metric looks non existent in the current config.yaml.

source: gharchive/pull-request

authors: douglas-reid howardjohn israel-hdez istio-testing

repo: istio/istio

license_type: permissive

license_source: github-api


text:
[release 1.7] fix istioctl authz check to print authz policies applied in pod

Fix https://github.com/istio/istio/issues/26675
This cherry-picks https://github.com/istio/istio/pull/26625 and https://github.com/istio/istio/pull/26697
Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

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

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.7
ba41f068241d4f651ea1c5d34920f5fecf02a72c
link
/test release-notes_istio_release-1.7

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.

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

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.7
13e88fbf2b758023217f2696c31fb8b862ed4236
link
/test release-notes_istio_release-1.7

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.

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

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.7
a4dc48f2b7d94ee1accfed6fa4ec4ddc76c4a849
link
/test release-notes_istio_release-1.7

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.

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

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.7
ff0fb28efcfc435ed41d1785c6530ec12ea9c4cf
link
/test release-notes_istio_release-1.7

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.

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

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.7
ff0fb28efcfc435ed41d1785c6530ec12ea9c4cf
link
/test release-notes_istio_release-1.7

integ-pilot-k8s-tests_istio_release-1.7
ff0fb28efcfc435ed41d1785c6530ec12ea9c4cf
link
/test integ-pilot-k8s-tests_istio_release-1.7

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

/test integ-pilot-k8s-tests_istio_release-1.7

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

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.7
ff0fb28efcfc435ed41d1785c6530ec12ea9c4cf
link
/test release-notes_istio_release-1.7

integ-pilot-k8s-tests_istio_release-1.7
ff0fb28efcfc435ed41d1785c6530ec12ea9c4cf
link
/test integ-pilot-k8s-tests_istio_release-1.7

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.

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio_release-1.7
ff0fb28efcfc435ed41d1785c6530ec12ea9c4cf
link
/test integ-pilot-k8s-tests_istio_release-1.7

release-notes_istio_release-1.7
48f66f30934d5d405a8aa3161a52af735a459b21
link
/test release-notes_istio_release-1.7

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.

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio_release-1.7
ff0fb28efcfc435ed41d1785c6530ec12ea9c4cf
link
/test integ-pilot-k8s-tests_istio_release-1.7

release-notes_istio_release-1.7
48f66f30934d5d405a8aa3161a52af735a459b21
link
/test release-notes_istio_release-1.7

unit-tests_istio_release-1.7
48f66f30934d5d405a8aa3161a52af735a459b21
link
/test unit-tests_istio_release-1.7

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.

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

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.7
48f66f30934d5d405a8aa3161a52af735a459b21
link
/test release-notes_istio_release-1.7

unit-tests_istio_release-1.7
48f66f30934d5d405a8aa3161a52af735a459b21
link
/test unit-tests_istio_release-1.7

integ-pilot-k8s-tests_istio_release-1.7
48f66f30934d5d405a8aa3161a52af735a459b21
link
/test integ-pilot-k8s-tests_istio_release-1.7

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.

@yangminzhu: PR needs rebase.

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

@yangminzhu Could you please fix the conflicts?

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

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.7
48f66f30934d5d405a8aa3161a52af735a459b21
link
/test unit-tests_istio_release-1.7

integ-pilot-k8s-tests_istio_release-1.7
48f66f30934d5d405a8aa3161a52af735a459b21
link
/test integ-pilot-k8s-tests_istio_release-1.7

release-notes_istio_release-1.7
eb837a220f5283bf9e7f6ad490b2a0331f0ae173
link
/test release-notes_istio_release-1.7

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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.7
48f66f30934d5d405a8aa3161a52af735a459b21
link
/test unit-tests_istio_release-1.7

integ-pilot-k8s-tests_istio_release-1.7
48f66f30934d5d405a8aa3161a52af735a459b21
link
/test integ-pilot-k8s-tests_istio_release-1.7

release-notes_istio_release-1.7
eb837a220f5283bf9e7f6ad490b2a0331f0ae173
link
/test release-notes_istio_release-1.7

integ-security-k8s-tests_istio_release-1.7
eb837a220f5283bf9e7f6ad490b2a0331f0ae173
link
/test integ-security-k8s-tests_istio_release-1.7

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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.7
48f66f30934d5d405a8aa3161a52af735a459b21
link
/test unit-tests_istio_release-1.7

integ-pilot-k8s-tests_istio_release-1.7
48f66f30934d5d405a8aa3161a52af735a459b21
link
/test integ-pilot-k8s-tests_istio_release-1.7

release-notes_istio_release-1.7
eb837a220f5283bf9e7f6ad490b2a0331f0ae173
link
/test release-notes_istio_release-1.7

integ-security-k8s-tests_istio_release-1.7
eb837a220f5283bf9e7f6ad490b2a0331f0ae173
link
/test integ-security-k8s-tests_istio_release-1.7

integ-multicluster-k8s-tests_istio_release-1.7
eb837a220f5283bf9e7f6ad490b2a0331f0ae173
link
/test integ-multicluster-k8s-tests_istio_release-1.7

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

/retest

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio_release-1.7
eb837a220f5283bf9e7f6ad490b2a0331f0ae173
link
/test integ-security-k8s-tests_istio_release-1.7

integ-multicluster-k8s-tests_istio_release-1.7
eb837a220f5283bf9e7f6ad490b2a0331f0ae173
link
/test integ-multicluster-k8s-tests_istio_release-1.7

release-notes_istio_release-1.7
eb837a220f5283bf9e7f6ad490b2a0331f0ae173
link
/test release-notes_istio_release-1.7

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

authors: istio-testing jwendell yangminzhu


text:
Automator: update proxy@master in istio/istio@master

Generated by Automator - 2022-04-17T22:24:56+00:00

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

Test name
Commit
Details
Required
Rerun command

integ-telemetry-istiodremote_istio
f437c36a2606db51db6b16c834b976e322a61f9e
link
true
/test integ-telemetry-istiodremote_istio

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

/test integ-telemetry-istiodremote_istio

authors: istio-testing zirain


text:
Install cleanup

Allow helm to configure few more istio config settings at install time.

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

Needs approval from an approver in each of these files:

install/OWNERS [costinm]

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

authors: costinm istio-testing


text:
Add mesh configuration verification for e2e test

Currently it only verifies EDS configuration. Verification is
performed by collecting the app's endpoints, which then are used to
compare with the mesh configuration returned by istioctl proxy-config.

[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: baodongli
If they are not already assigned, you can assign the PR to them by writing /assign @baodongli 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:

tests/OWNERS

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
947b352a1361e072b924a73ea1be890d6195636f
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.

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

Test name
Commit
Details
Rerun command

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

prow/istio-pilot-multicluster-e2e.sh
947b352a1361e072b924a73ea1be890d6195636f
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.

[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: costinm
If they are not already assigned, you can assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS
tests/OWNERS

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

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

Test name
Commit
Details
Rerun command

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

prow/istio-pilot-multicluster-e2e.sh
a21a3621835baa976a0ce916ebe27b5ad071ab24
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.

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

Test name
Commit
Details
Rerun command

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

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
6ae7b724a20e4b1f595e10d78f9f83db1488bd68
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.

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

Test name
Commit
Details
Rerun command

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

prow/istio-pilot-multicluster-e2e.sh
6ae7b724a20e4b1f595e10d78f9f83db1488bd68
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.

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

Test name
Commit
Details
Rerun command

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

prow/istio-pilot-multicluster-e2e.sh
6ae7b724a20e4b1f595e10d78f9f83db1488bd68
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests.sh
6ae7b724a20e4b1f595e10d78f9f83db1488bd68
link
/test e2e-simple

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.

circleci is misbehaving.  please rebase your PR.
Thanks
-steve

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
6a828584191f8862a1c69e04d6abd15e4a742821
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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
6a828584191f8862a1c69e04d6abd15e4a742821
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
117b5ac7d56311bfb0efa3ca701a38e72f894126
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.

/cc @costinm thanks.

[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: baodongli
If they are not already assigned, you can assign the PR to them by writing /assign @baodongli 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:

tests/OWNERS

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

/cc @costinm @rshriram Care to take a look? I can close it if you guys think it's not useful. Thanks

@baodongli: PR needs rebase.

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
1544a72476a965237a07a4f631cd9039c8093dc9
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.

/test istio-pilot-multicluster-e2e

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
1544a72476a965237a07a4f631cd9039c8093dc9
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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
1544a72476a965237a07a4f631cd9039c8093dc9
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
1544a72476a965237a07a4f631cd9039c8093dc9
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

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

/test istio-pilot-multicluster-e2e

authors: baodongli istio-testing sdake


text:
DO NOT MERGE! Fast Forward stable to 21f4cb412eab119f34c81ceec37bce3b71dc26bc.

This PR will be merged automatically once checks are successful.

Jenkins job manager/postsubmit passed

Jenkins job manager/e2e-suite passed

repo: istio/manager


text:
Update dependency to fix goroutine proliferation in zipkin-go (#1515)

Automatic merge from submit-queue.
Update dependency to fix goroutine proliferation in zipkin-go
This PR fixes goroutine proliferation issue with openzipkin-go.
https://github.com/istio/issues/issues/100#issuecomment-339468537
After the PR is upstreamed, we will update the dependency.
https://github.com/mandarjog/zipkin-go-opentracing/pull/1
Release note:
NONE

This change is

/lgtm

/approve

authors: douglas-reid jmuk mandarjog

repo: istio/mixer


text:
[Manage Journey] Journey page (list of journeys)

As any User I want to see all journeys (upcoming, current, and past) so that I can find necessary information about all my trips.
Mockup

Acceptance Criteria

User shall have access to the list of journeys after pushing Journey icon on the Ride Homepage (US ita-social-projects/Car-Back-End#23 ).
On the top User shall see current trips, then Upcoming and then Past journeys.
Each journey should be circled by the line and consist of such information: N&S of journey organizer, SS position, list of stops addresses during the journey, the ellipsis (at the right side, marked as "..."), time of the journey.
3.1. Requirements to date and time appearance are given in US#376
All: system shall show a list of all User's journeys.
Upcoming: system shall show a list of upcoming User's journeys only.
Past: system shall show a list of past User's journeys only.
6.1. Statistic of past journeys shall be stored in the DB for HR Marketing requests.

Assumptions & Constraints

User can scroll up and down the page.
Past journeys shall be deleted from the DB 14 days after the journey was fulfilled.
Upcoming:  journeys that will take place during the next 24h.
Past: journeys that took place during the last 24h.

Epic link
Epic ita-social-projects/Car-Back-End#70
Labels to be added
"User story" ("story"), Priority ("pri: ")
Tasks

[ ] sample task.

6 not about interaction with user (maybe another story)

3 Upcoming maybe not only 24 hour
4 Past maybe last two weeks

As any Users I want to have ability deleting some of my past journeys

As any Users I don't want to see an ellipsis menu for past journeys

Is 3. About list of journeys or journey detailed info screen.

source: gharchive/issue

authors: OlenaBobalo VikaUrzan YanaRudyi ivanstrilchuk

repo: ita-social-projects/Car-Back-End

license: MIT


text:
[Preferences] 'Comments' edit box is empty by default

Environment: Xiaomi MiA1, Android 9
Reproducible: always
Build found: v1.0.377
Preconditions

Open app.
Log in.

Steps to reproduce

Go to 'My Profile'.
Click on 'Preferences'.

Actual result
'Comments' edit box is empty by default
Expected result
'Comments' edit box has 'Input text' placeholder by default
User story and test case links
User story #21
Labels to be added
"Bug" ("bug"), Priority ("pri: low")

'Comments' edit box should  have 'Input text' placeholder by default not 'Write your comments'

fixed in v1.0.408

authors: Sydir VikaUrzan


text:
[Order Form. Step 1] UI inconsistencies between mockups and website

Environment: Windows 10 Pro 21H2 19044.1415, Chrome 100.0.4896.127 (Official Build) (64-bit)
Reproducible: always
Build found: 08.05.22
UI inconsistencies between mockups and website
Link to mockups: https://www.figma.com/file/JvDAu4MHnh1Vxc5FaokyiA/ITA-UBS-styles?node-id=15777%3A37659
Steps to reproduce

Go to https://ita-social-projects.github.io/GreenCityClient/#/
Log in to Green City
Click on the 'UBS кур'єр' tab
Click on the 'Замовити кур'єра' button
Select "Київ" city and click on "Продовжити" button.

Actual result

Certificate section includes 'Чи бажаєте Ви скористатись сертифікатом?' header, input field under header and "Активувати" button near input field.
'Номер сертифiката' isn`t colored green (#AFD85A) when the cursor focuses it.
Tab`s counters have size of number 11x22 px, size of round field 24x24 px (this problem is reproducible on the all tabs - 'Деталі замовлення', 'Особисті дані', 'Підтвердження')
'Кількість пакетів' input field has spinner on the right side, placeholder '0' is left aligned.
'Еко-магазин' section includes input field with placeholder and  'Номер замовлення' label and radiobuttons above these elements.

Expected result

Certificate section includes 'Якщо бажаєте скористатися сертифікатом, введіть номер сертифіката' header, input field under header with "Номер сертифiката" label and "Активувати" button near input field.
'Номер сертифiката' input field should be colored green (#AFD85A) when the cursor focuses it.
Tab`s counters have size of number 12x28 px, size of round field 30x30 px.
'Кількість пакетів' input field has '+' and '-' buttons, placeholder '0' is central aligned.
'Еко-магазин' section includes input field with placeholder and  'Номер замовлення' label.

User story and test case links
Test case https://jira.softserve.academy/browse/GC-1935

Defect also reproduces in desktop version.

repo: ita-social-projects/GreenCity


text:
[Data model] Workshop (Study group)

Unified information about a group of education seekers (class, study group, extended day group, workshop group, etc.), which is formed within a certain educational institution of any type or level in order to ensure the teaching of a certain set of educational subjects to this group, regardless of the peculiarities of the educational process.
Can include hierarchy of sections which are also a workshop (study group).
Is a business entity as in #1524

Parent.Name
Name
Data Type
Mandatory
Comment

Study group
identifier
GUID
TRUE

Study group
CoverImage
string
TRUE

Study group
Images
list
TRUE

Study group
Minimum age
int
TRUE

Study group
Maximum age
int
TRUE

Study group
Total number of seats in the group
int
TRUE

Study group
educational shift
Dictionary to educational shift
TRUE
Edited 21.09.2024 Dictionary will be implemented on Stage II. Currently can be a stub field.

Study group
Short stay
boolean
TRUE

Study group
Language of education
Dictionary of languages of study
TRUE
The dictionary is implemented in the current AIKOM, we can reuse it for the 1st stage

Study group
schedule
Schedule
TRUE

Study group
Works with funds from parents, benefactors
boolean
TRUE

Study group
Type of group by age composition
Type of group by age composition
TRUE
see below

Study group
there is a competitive selection in the group
boolean
TRUE

Study group
number of seats
int
TRUE
calculated from available seats minus taken

Study group
study from
Date
TRUE

Study group
study to
Date
TRUE

Study group
Educational disciplines that are taught
Educational subject #1533
TRUE
= Subcategory of group direction. Edited 21.09.2024: Will be implemented on stage II

Study group
workshop title
String
TRUE

Study group
direction
Dictionary of directions of the group
TRUE
see below. Edited 21.09.2024: Can re-use our current mechanism.

Study group
Category
Direction
TRUE
see below

Study group
formed in provider
Provider #1543
TRUE

Study group
group type
Classifier of types of educational groups
TRUE
Edited 21.09.2024: can be a stub, no dictionary at the moment.

Study group
member of the study group
member of the study group (children)
TRUE
We will put it on BE, on the FE we will not add it until 2nd stage

Study group
is paid
boolean
TRUE

Study group
is special
boolean
TRUE

Study group
is inclusive
boolean
TRUE

Study group
Number of occupied seats
int
FALSE
At the both workshop and section level

Study group
includes study groups
Workshop (Study group)
FALSE
links to other study groups, if this group is consolidated

Study group
group with special needs
Dictionary of types of special needs of children
FALSE
see below

Study group
additional description
String
FALSE

Study group
short title
String
FALSE

Study group
description of the enrollment procedure
String
FALSE
see below

Study group
Coverage
Dictionary
FALSE
see below

Study group
default teacher
Official #1532
FALSE
We will put it on BE, on the FE we will not add it until 2nd stage

Study group
planned format of classes (online/offline)
list
FALSE

Study group
status
Dictionary
FALSE

Study group
Price
int
FALSE
price 0 = free

Study group
Payrate
Dictionary to the basis for payment
FALSE
see below

Study group
are there benefits
boolean
FALSE

Study group
preferential terms of participation
String
FALSE

Type of group by age composition:

одновікова
різновікова.

Group with special needs:

слуху
мови
зору
інтелекту
опорно-рухового апарату
затримкою психічного розвитку

Direction:

науково-технічний
еколого-натуралістичний
туристсько-краєзнавчий
фізкультурно-спортивний
художньо-естетичний
дослідницько-експериментальний
бібліотечно-бібліографічний
військово-патріотичний
соціально-реабілітаційний
оздоровчий
гуманітарний
наукові товариства

Category:

Спорт
Музика
Наука і техніка
ІТ, Програмування
Співи
Танці
Малювання
Фотографія
Рукоділля
Книжки та про них
Скаутінг / Пласт
Театри і кіно
Мови
Садівництво
Туризм
Музеї, екскурсії
Волонтерство

description of the enrollment procedure:

Постійно (протягом року)
Певний місяць або місяці року (Можливість обрати місяці)

Coverage:

Локальний (Шкільний)
Міський
Районний
Обласний
Всеукраїнський
Міжнародний

Payrate:

Година
День
Місяць
Рік
Курс
Клас
Весь період

Following fields were removed

Parent.Name
Name
Data Type
Mandatory
Comment

~Study group~
~Age category~
~Dictionary of age categories~
~TRUE~

Changed fields marked with Edited 21.09.2024

repo: ita-social-projects/OoS-Backend


text:
Problemi pratica di immigrazione

Non riusciamo ad iscrivere un cittadino straniero, già precedentemente cancellato da ANPR. Dalla web app abbiamo verificato che appaiono diverse iscrizioni e cancellazioni tutte in sata 26/02/2019.
L'ID operazione ANPR è 53637684.

il cittadino è stato iscritto nel Comune di Altamura nel 2018 e cancellato per trasferimento all'estero nello stesso anno; ieri, sempre il Comune di Altamura,  ha effettuato per 5 volte consecutive l'iscrizione e la cancellazione del soggetto; di fatto, ad oggi il soggetto risulta cancellato, pertanto l'operazione di mutazione di residenza che il Comune di Altamura sta cercando di effettuare, non può andare a buon fine: deve essere utilizzato il servizio di iscrizione per altri motivi con l'indicazione dell'idanpr precedentemente assegnato.
Posso chiedere come mai state effettuando queste operazioni ?
Se può essere utile scrivetemi in privato un contatto telefonico:  frmariani@sogei.it

come da accordi intercorsi, chiudo la issue in quanto il problema risiede nel gestionale.

authors: Finalmentesubentrati frmariani

repo: italia/anpr


text:
Wallet Attestation request flow with OAuth 2.0 nonce endpoint

The steps 6 and 7 should be made according to
https://github.com/peppelinux/draft-demarco-nonce-endpoint
@rohe do you have any claims or requirements in the http request according to your analysis?

I am closing this issue given that the steps you mentioned concern obtaining a nonce from the Integrity Attestation Services made available by Apple and Google, therefore the endpoints will be the custom ones made available by the two manufacturers. How this will work will be defined here

authors: grausof peppelinux

repo: italia/eudi-wallet-it-docs


text:
Federation entity metadata

Title
Federation entity metadata
Content
Questa PR risolve #116 , tenendo conto di quanto riportato in https://bitbucket.org/openid/connect/issues/1702/federation-removal-of-trust_mark_issuer e in https://bitbucket.org/openid/connect/issues/1712/federation_entity-metadata.
Inoltre, ho aggiunto anche la sezione relativa ai metadata da federation_entity per il TA e per SA e modificato di conseguenza i relativi esempi non normativi.
Review

[ ] Ensure your files are written following RST specs (not MD!)
[x] Italian version
[x] English version
[x] Example files
[ ] Ask for review

organization_name è stato introdotto con questa PR?

Giusto integrato nell'esempio non normativo

authors: fmarino-ipzs peppelinux

repo: italia/spid-cie-oidc-docs


text:
Implement protocol to add custom output to rust-lightning channel

This is a preparatory step before we implement a protocol which adds a DLC output to a rust-lightning channel.
Vanilla Lightning channels can have outputs that pay to a party directly or HTLCs. Both of those types of outputs are involved in payments. With this ticket we want to be able to add a custom output that is not involved in a Lightning payment. Since DLC outputs will also be orthogonal to Lightning payments, we expect to be able to reuse/expand/rewrite the code written when working on this ticket when implementing the Lightning DLC protocol.
The outcome of this ticket should be adding a passing test to the lightning::ln::functional_tests module.

@luckysori are you working on a fork of this https://github.com/lightningdevkit ? I guess we should keep that aligned with https://github.com/itchysats/10101/issues/11

We have a fork here https://github.com/itchysats/rust-lightning

authors: bonomat holzeis luckysori


text:
broken external links at community tutorials page

At https://dvc.org/doc/tutorials/community you see all the links are pointing to dvc site and 404 although content/docs/tutorials/community.md is featuring proper external links.
Tried investigating root cause, might be something in redirects-list.json &         src/utils/shared/redirects.js
Also, not 100% relevant (and sure :)), but in gatsby-config both external-link-plugin & gatsby-remark-external-links are used which might be doing similar things

Great find! It applies to the first 3 links and to the last one. We'll investigate this ASAP...

@iAdramelk @pavelgrinchenko this doesn't seem to be a problem with the markdown or with the redirect list. The links in code are correct so the link checker doesn't catch these 404s. Maybe it's a Gatsby problem indeed?

p.s. seems to be replacing host names that have subdomains (e.g. blog.codecentric.de or www.linkedin.com) for the server host name.

p.p.s. it's affecting all external links everywhere in the website e.g. http://localhost:8000/doc/understanding-dvc/resources#articles

@jorgeorpinel not sure it's broken the same way in develop & build mode, but
This is happening for

external links
that end with trailing /
Because of redirect rule being applied and returning only relative part of URL

Details:
<Link> component is calling getRedirect here and
this "^/(.+)/$" pattern is being checked against path part of external URLs omitting the host, returning relative urls that are being rendered instead of original external url.
So as a quickfix, can just remove trailing / from external links to avoid this and might need to modify redirect matching/using results logic

@pavelgrinchenko Can you please check it?
I think @sudodoki is right, we should probably reapply host for the links if it's not equal to the current site or return original link without removing / for such links, but maybe I'm missing some edge case there.

@jorgeorpinel I made PR with fix, could you review it

@pavelgrinchenko thanks! 🙏  Merged.
@sudodoki

external-link-plugin & gatsby-remark-external-links

names are confusing indeed, buy yes, we need both - one to support custom HTML in blog (it is a a custom plugin we wrote), second one - is regular gatsby that deals with ext links.
Good catch, btw. Thanks for the report.

@pavelgrinchenko it looks like it is still broken :(

@shcheklein at which page are you seeing same behavior? https://dvc.org/doc/tutorials/community links from original issue seem fixed.

@sudodoki links are fixed, but when I click them they still redirect me to dvc.org Not Found. Is it only me? 🤔

@shcheklein I forgot to add domain check to click handler... Here is another fix

@shcheklein Hm, seems this logic outdated there at all as we are already replacing original href with redirected when it's necessary. So I removed it from the click handler

Awesome, geat fix. Thanks guys! And thanks again @sudodoki

Oops only the URLs are fixed. It works OK when you Cmd/Ctrl+click but regular click changes the page to dvc.org 404 still...

Cc @pavelgrinchenko
p.s. I tried with no cache

It works for me now. Not sure what was the issue after the deployment, but it works. @jorgeorpinel could you please confirm and reopen if it is still broken?

It works OK for me now as well.

authors: iAdramelk jorgeorpinel pavelgrinchenko shcheklein sudodoki


text:
Added new GitHub action to schedule blog post merges

We want to get to a point where a blog post PR that is approved can be scheduled to auto-merge on a specified date.
Here is the doc I used to make this YAML file and it explains all of the functionality.

@julieg18 Would you mind merging this for me? I don't have merge permissions in this repo yet.

Can we also have this documented in https://dvc.org/doc/user-guide/contributing/docs?

Maybe in https://dvc.org/doc/user-guide/contributing/blog but this seems like an internal tool so not sure it's needed there.

Can it be part of the PR template (+ check list of things to do that DevRel team usually includes these days)
https://github.com/iterative/dvc.org/blob/master/.github/PULL_REQUEST_TEMPLATE.md
can we create multiple templates?

authors: casperdcl flippedcoder jorgeorpinel shcheklein


text:
Feature/moving to mongodb

Moving the backend from NeDB to MongoDB using monk.

maybe you can query the database first, and then modify the data by using event and extrinsic.
if NewMultisig(approving, multisig, call_hash)
    id = event_id
    if not_exist_in_db(id, call_hash)
      create a new call in db
    end
end

if MultisigApproval(approving, timepoint, multisig, call_hash)
  id = calc(timepoint)
  call = find_in_db(id, call_hash)
  call.approvals << approving
end

...

maybe you can query the database first, and then modify the data by using event and extrinsic.
if NewMultisig(approving, multisig, call_hash)
    id = event_id
    if not_exist_in_db(id, call_hash)
      create a new call in db
    end
end

if MultisigApproval(approving, timepoint, multisig, call_hash)
  id = calc(timepoint)
  call = find_in_db(id, call_hash)
  call.approvals << approving
end

...

In one way this is implemented in the project,
the only difference is that it makes the payload and then check if it is present or not, and in case of approvals it is querying the DB first, like you suggested.
But I agree that matching the current timepoint, hieght and index and blocknumber and event index only is minimalist but  refactoring the current version to accommodate for that won't bring much of a performance difference and might leave code prone to bugs.

In one way this is implemented in the project,
the only difference is that it makes the payload and then check if it is present or not, and in case of approvals it is querying the DB first, like you suggested.
But I agree that matching the current timepoint, hieght and index and blocknumber and event index only is minimalist but  refactoring the current version to accommodate for that won't bring much of a performance difference and might leave code prone to bugs.

merged in error

merged in error

Moved the PR here: https://github.com/itering/subscan-multisig-backend/pull/6

Moved the PR here: https://github.com/itering/subscan-multisig-backend/pull/6

authors: nblogist wuminzhe

repo: itering/subscan-multisig-backend


text:
fix minor issue in /archive and adding a custom date range

There was an issue in /archive that resulted in an incomplete representation of the currencies, which was fixed by iterating on all the tables on the archive page.
A new endpoint was added to accept custom date ranges;/customrange that can be accessed by sending the startDate and endDate params.

Thank you for the final notes. I applied them!

repo: itsamirhn/Bonbast-API


text:
6413 Лаб. 4 Томашайтис Павел

ФИО: Томашайтис Павел Андреевич
Номер группы: 6413
Номер лабораторной: 4
Номер варианта: 19 (из курса "Базы данных")
Краткое описание предметной области: Аптекарская сеть города
Краткое описание добавленных фич:
Реализована клиентская часть с использованием фреймворка Blazor.
Отображение элементов на страницах было реализовано с применением CSS-фреймворка Blazorise.
Автоматически сгенерирован класс CityPharmacyChainApi, представляющий собой API для взаимодействия с серверной частью.
Добавлен класс CityPharmacyChainApiWrapper, являющийся обёрткой для класса CityPharmacyChainApi.
Добавлены компоненты Razor Components для отображения основных элементов на странице:

DataGrid - компоненты для отображения таблиц с данными;
CreateModal - компоненты для добавления новых данных на сервер.

Добавлены компоненты Razor Layouts для описания структуры страницы:

MainLayout - описание тела страницы;
NavMenu - описание панели навигации.

Добавлены компоненты Razor Pages для отображения страниц:

Page - основные страницы приложения;
EditPage - страницы, открываемые при редактировании данных.

Реализована возможность выполнения CRUD операций с основными структурами данных в приложении - Pharmacy, Product, PharmacyProduct, PharmaceuticaalGroup, PriceListEntry.
Вид главной страницы:

Вид страницы с данными:

Вид модального окна для добавления новых данных:

Вид страницы для редактирования данных:

Внёс улучшения в код на основании указанных замечаний.
Перенёс в отдельные директории страницы и компоненты схожего назначения (DataGrid, CreateModal, EditPages, MainPages).

+1 за реализацию UI для всех сущностей

authors: Tomashaytis kolyanch

repo: itsecd/enterprise-development


text:
Кудашев Н.И. Лаб. 2 Группа 6312

ФИО: Кудашев Никита
Номер группы: 6312
Номер лабораторной: 2 Номер варианта(при наличии): 2
Краткое описание исходного кода: Я взял(а) исходный код из интернета. Вот ссылка на него: https://github.com/emilybache/CustomerSync-Refactoring-Kata/tree/main/python/src
Краткое описание проделанной работы: Выполнение ревью кода.

Зачтено

repo: itsecd/prog-instruments-labs


text:
Inconsistency between SCT and ivadomed postprocessing names

See https://github.com/ivadomed/ivadomed/pull/498#discussion_r517787439

Per @andreanne-lemay's comment here, and the fact that "keep_largest" and "binarize_prediction" are now prevalent in the repo, I believe @andreanne-lemay  has already made all the necessary changes by this point. Closing.

repo: ivadomed/ivadomed


text:
Inserted text issue: selected position and placed position mismatch

I had an issue, while playing on with insert text feature.
I have selected a position and entered a few words and when i press on tick mark(i.e ok) the text size is getting enlarged and also the placed position varies with the one i wanted to be.
like as below

any solution for this?

Hi @kishandonepudi thanks for bug report!

you have a very good plugin.
but i got stuck because of this text insert issue.
text sizes changes randomly and the position too.
is it already fixed or you are still on it.
I am desperately waiting for the fix.
if you could let me know the source of issue, may be i would give it a try for fix.
let me know :)

@bhuwangothe , please try now, a lot of text issues were solved in latest releases.
Issue were:

in different scale modes (e.g. image larger then viewport was loaded into widget)
at different zoom level

@kishandonepudi fixed, please try and let me know

authors: bhuwangothe ivictbor kishandonepudi

repo: ivictbor/painterro

license: mit

license_source: bigquery


text:
Catalog service database schema

Create database schema (PostgreSQL) for the Catalog service.

done in scope of #5

repo: ivolynets/wide-cart


text:
Add support for better file download urls with HTTP Range requests + …

…streaming
curl -H "range: bytes=0-3,-2" http://127.0.0.1:3000/file/2/hello.txt

Fixes #34
Fixes #8
Fixes #9

I don't believe this issue should close #34

I agree.. reedited to mention #30 thanks @jkeck

:shakes-fist: autocomplete, ugh.

authors: cbeer jkeck mejackreed

repo: ivplus/aggregator


text:
🛑 21Eurkon is down

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

HTTP code: 0
Response time: 0 ms

Resolved: 21Eurkon is back up in cd9ad42 after 16 minutes.

repo: iwyang/check


text:
🛑 23心流 is down

In a586c34, 23心流 (https://blog.panghai.top/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 23心流 is back up in d6dd2c2.


text:
🛑 17张洪Heo is down

In ca916f2, 17张洪Heo (https://blog.zhheo.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 17张洪Heo is back up in 4147bc9.


text:
🛑 21Eurkon is down

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

HTTP code: 0
Response time: 0 ms

Resolved: 21Eurkon is back up in 170d017 after 18 minutes.


text:
🛑 21Eurkon is down

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

HTTP code: 0
Response time: 0 ms

Resolved: 21Eurkon is back up in 02c196c after 9 minutes.


text:
Current staging deployment doesn't work on Safari

This probably isn't an issue with the codebase, but I didn't know where else to file it. The link https://app_uat.ixo.world/ is inaccesible from Safari.

Turns out that we should be using https://app-uat.ixo.world/ instead of  https://app_uat.ixo.world/ (note the dash and underscore difference)

repo: ixofoundation/ixo-webclient


text:
🛑 N IXTANET is down

In a973609, N IXTANET ($N_IXTANET) was down:

HTTP code: 0
Response time: 0 ms

Resolved: N IXTANET is back up in d140351 after 8 minutes.

repo: ixtanet/upptime


text:
A subsection about extensible records is missing

http://elm-lang.org/docs/records

Thanks to @sofiapoh (#15)

authors: adius izdi

repo: izdi/elm-cheat-sheet


text:
Handle Input only / Output only comments

https://cloud.google.com/apis/design/documentation#field_and_parameter_descriptions

implemented in #29


text:
Packer command not installed

Hi @j3ssie. When running the osmedeus utils command, it complains about not finding the packer binary:
error checking core programs: /root/osmedeus-base/binaries/packer -h

I haven found any mention about Packer in the installation script. Is Packer a prerequisite before installing/using Osmedeus?
Meanwhile, I've added its installation to the Docker image.
Regards.

Thank you for reporting, I just fixed the option for that. It simply check cloud setup is okay or not which is a feature for premium package only.

OK, I wasn't aware this is a premium feature. I understand that I should remove Packer from the Docker image, shouldn't I?

Yeah sure, to reduce the image size


text:
Update readme.md

Fixed broken link to sdk development.

Thank you

repo: jMonkeyEngine/sdk


text:
Failed to generate build

I tried building from souce code but failed, no matter if i use the script or not.
CMakeError.log
CMakeOutput.log

I don't think those log files tell us anything. Can you post the output of the cmake and the command

@just12 Do you have pthread installed ? In the attached file, it tries to find pthread_create, but cannot.

pthread is installed but it doesn't find pthread_create.
Here are the outputs of build.sh and cmake ..
build.sh.txt
cmake.txt

When running the build.sh, you specified that you wanted to build with volume support, but your system doesn't have alsalib installed, that's why you get an error. If you run cmake .. and make inside a clean build directory, this shouldn't happen

Im doing this on a clean install and noticed that i din't have alsa installed, so i installed alsa-base. Isn't alsalib included in it?
Also, just for the sake of trying it, i removed the build/ directory and tried to build only saying yes to internal/i3 and polybar/msg and the same thing happens, it fails because it doesn't find pthread_create.
build.sh2.txt

What distro are you using? Did you check the Wiki to make sure that you have all dependencies installed?

Im on lubuntu 17.04 zesty. I forgot to check the wiki, so i installed the dependencies listed and cmake was able to finish. Now the problem is with make.
make.txt

Now we're getting somewhere. Seems this is a duplicate of #644
See the next section on the wiki for instructions on how to resolve this.

repo: jaagr/polybar


text:
Restructure test folder (Backend)

Create folders for unit tests, integration tests, acceptance tests

Story Points: 1 day

Structure should align to this


text:
Port Structured.scala to Structured.java

https://github.com/xebia-functional/Unwrapped/blob/main/unwrapped/src/main/scala/unwrapped/Structured.scala
https://github.com/xebia-functional/Unwrapped/blob/main/unwrapped/src/test/scala/unwrapped/StructuredTests.scala

https://github.com/ishwi/Chuu/blob/master/src/main/java/core/util/VirtualParallel.java
https://github.com/forax/loom-fiber/blob/master/src/main/java/fr/umlv/loom/example/_15_adhoc_scope.java
https://github.com/codetojoy/easter_eggs_for_java_loom/blob/main/egg__11_sc_utility/src/main/java/net/codetojoy/CustomScope.java
https://github.com/SvenWoltmann/structured-concurrency/blob/main/src/main/java/eu/happycoders/structuredconcurrency/demo3_suppliers/BestResultScope.java
https://github.com/daqingllm/Java21-for-backend-developers-code/blob/main/src/main/java/chapter2/MyScope.java

repo: jabrena/typed-errors


text:
Firestore permissions error following upgrade to latest firebase sdk

This was originally raised on PR https://github.com/jac-uk/admin/pull/2287 but has been moved here so that the code in that PR can be merged into main (as there are lots of changes which we don't want to go stale).
Before (fresh install of Admin running from previous main branch)
All looks fine, no console errors

After (fresh install of Admin running the upgraded firebase lib)
Console error

The back-end this is connecting to is unchanged however the error looks like a firestore permission error. Perhaps the new code is trying to access more from firestore than the previous code.

Another warning that I noticed is here:

And also the link doesnt seem to be working, see the video below:
https://github.com/jac-uk/admin/assets/115651787/6990745a-4ce2-4a51-93a0-40f8441bf0f0

authors: drieJAC warrensearle

repo: jac-uk/admin


text:
eligibility issues - renamed filename

Author checklist

[ ] Include primary ticket number in title - e.g. "#123 New styling for widget" - and any additional tickets in description
[ ] Fill in the details below and delete as appropriate
[ ] Be proactive in getting your work approved 💪

Who should test?
✅ Product owner
✅ Developers
✅ UTG
How to test?
Export the Eligibility Report. The filename should no longer be called Contacts.xlsx
Risk - how likely is this to impact other areas?
🟢 No risk - this is a self-contained piece of work
Additional context
Include screen grabs, notes etc.

PREVIEW:DEVELOP
can be OFF, DEVELOP or STAGING

The name is indeed different from Contacts.xls

authors: HalcyonJAC lloback


text:
You exceeded your currunt qouta

You exceeded your current quota, please check your plan and billing details. For more information on this error, read the docs: https://platform.openai.com/docs/guides/error-codes/api-errors.
require("chatgpt").setup({
  api_key = "my api key here",
    openai_params = {
      model = "gpt-3.5-turbo",
    },
})

vim.api.nvim_set_keymap('n', '<leader>cg', ':ChatGPT<CR>', { noremap = true, silent = true })

does the plugin require payed version of open ai?

yes you need an OpenAI API key  - you do not interact with ChatGPT here through the same means you would on the OpenAI UI. check the README.

thanks

yes you need an OpenAI API key - you do not interact with ChatGPT here through the same means you would on the OpenAI UI. check the README.

thanks i appreciate the response, I guess i need to buy an OpenAI API credit.

authors: kirubel-web riordant


text:
Support left and right (curried) positional arguments

This is a WIP PR to implement a possible way of addressing #134 , and needs input on whether it makes sense, is appropriate for inclusion in the arguments package, is a good solution, etc.
The essential change is to decompose positional arguments into two sets left and right, to be able to represent argument sets in curried functions.

At the moment, it is fully backwards compatible and all the tests pass.
There are no new docs or tests yet.
An interesting consideration is how composition of argument sets should be defined. Formerly for argument structures a and b, we simply compose the positional lists in the order supplied. With both left- and right-handed positional arguments, we could naively do left(a) ++ left(b) and right(a) ++ right(b), but somehow, it seems more correct to compose them as left(a) ++ left(b) and right(b) ++ right(a), i.e. with the order of composition reversed for the right-sided positional arguments. This seems to make sense if we treat the order of arguments provided to arguments-merge as "priority" of arguments. When we left-curry a function and provide additional arguments in sequence, each new argument takes up the left-most position not already claimed. Likewise with right-curry, each fresh argument takes up the right-most position not already claimed. It feels like argument composition ought to mirror this behavior, but I'm not sure. In any case that's the composition strategy in this PR at the moment.

With the changes in this PR, the downstream module referenced in #134 would look like this: https://github.com/countvajhula/relation/commit/e1917f75308843bed81df09c0fa08f59eb96caa6

See discussion in #134

repo: jackfirth/racket-mock


text:
下载文件时，可以定义保存的文件名吗

如果有怎么操作

不支持的，建议在外部文件名和url做映射

这个问题我也想问下 怎么在外部文件名和url做映射？目前下载了之后，文件名会被md5了，就是下载成功后，我的文件叫什么名字了

在外部维护一张映射表，这张表可以放在内存或者磁盘，url1=name1，url2=name2

大佬，谢谢你的回复，那个name要从哪拿到呢

name是你的业务内容，你想存什么name就存什么…

大佬，谢谢你的回复，那个name要从哪拿到呢

name是你的业务内容，你想存什么name就存什么…
大佬，下载时的地址可不可以自定义呢？

大佬，谢谢你的回复，那个name要从哪拿到呢

name是你的业务内容，你想存什么name就存什么… 大佬，下载时的地址可不可以自定义呢？

不支持的


text:
Ensure that paths passed to libclang are fully expanded

Ran into these two issues while playing around with my config. With this patch:

-include directives in arg lists now resolve out properly.
Before this patch:

Creating completion session with arguments cc [SNIP] -I/home/josh/Upstream/linux/include/generated/uapi, -include, ./include/linux/kconfig.h, [SNIP]
After:
``Creating completion session with arguments cc [SNIP] -I/home/josh/Upstream/linux/include/generated/uapi, -include, /home/josh/Upstream/linux/include/linux/kconfig.h, [SNIP]`

The clang_resource_dir supplied by cquery.el's  initParams would silently fail to do anything useful, littering diagnostics with "size_t is not defined" errors.

This also resolves https://github.com/jacobdufault/cquery/issues/101.

authors: jacobdufault jaelsasser

repo: jacobdufault/cquery


text:
jaeger query repeating log lines

The jaeger query has been deployed via the operator.
Version is 1.16.0
Platform: openshift 3.11
The logs for the query pod are being filled up with the following log line:
{"level":"info","ts":1582817795.8145893,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
This line is being logged every 0.5 second or so.

some info relevant to this issue: https://github.com/jaegertracing/jaeger-operator/issues/533#issuecomment-517216871

@samcrutt9900, unfortunately, it is quite possible that this code doesn't work properly in OpenShift 3.11. Would you be willing to test on a newer cluster, like OpenShift 4.3?
If you are seeing a reloading UI config there every 0.5 second, then we need to investigate and address that.

@jpkrohling Just now I checked our test logs. I see this issue on OCP 4.3. But it is not every 0.5 seconds.
this log captured for 15 minutes log:
{"level":"info","ts":1582209567.028163,"caller":"flags/service.go:115","msg":"Mounting metrics handler on admin server","route":"/metrics"}
{"level":"info","ts":1582209567.0287373,"caller":"flags/admin.go:108","msg":"Mounting health check on admin server","route":"/"}
{"level":"info","ts":1582209567.0288222,"caller":"flags/admin.go:114","msg":"Starting admin HTTP server","http-port":16687}
{"level":"info","ts":1582209567.0288553,"caller":"flags/admin.go:100","msg":"Admin server started","http-port":16687,"health-status":"unavailable"}
{"level":"info","ts":1582209567.1204472,"caller":"config/config.go:172","msg":"Elasticsearch detected","version":5}
{"level":"info","ts":1582209567.1219795,"caller":"app/static_handler.go:176","msg":"watching","file":"/etc/config/ui.json"}
{"level":"info","ts":1582209567.1220148,"caller":"app/static_handler.go:184","msg":"watching","dir":"/etc/config"}
{"level":"info","ts":1582209567.1222315,"caller":"healthcheck/handler.go:128","msg":"Health Check state change","status":"ready"}
{"level":"info","ts":1582209567.1222522,"caller":"app/server.go:135","msg":"Starting CMUX server","port":16686}
{"level":"info","ts":1582209567.122527,"caller":"app/server.go:112","msg":"Starting HTTP server","port":16686}
{"level":"info","ts":1582209567.1225536,"caller":"app/server.go:125","msg":"Starting GRPC server","port":16686}
{"level":"info","ts":1582209570.67485,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582209570.6750507,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582209570.6756234,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582209571.6826277,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582209571.682857,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582209571.6829314,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582209660.541147,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582209660.5419843,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582209660.542112,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582209722.4985597,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582209722.4993293,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582209722.4994016,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582209804.554374,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582209804.556744,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582209804.5568602,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582209893.5396142,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582209893.5463095,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582209893.5464492,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582209970.5723433,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582209970.5728827,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582209970.5729208,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582210034.498819,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582210034.4997246,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582210034.499803,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582210101.5289884,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582210101.5299835,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582210101.530103,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582210171.5974598,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582210171.5985246,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582210171.5986428,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582210232.5636551,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582210232.5658648,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582210232.5661654,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582210315.5537915,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582210315.554623,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582210315.5547082,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582210404.5289752,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582210404.5296063,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582210404.5299013,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582210468.5486624,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582210468.5494034,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}
{"level":"info","ts":1582210468.5495527,"caller":"app/static_handler.go:155","msg":"reloading UI config","filename":"/etc/config/ui.json"}

I assume there's no reason for this, right? Definitely sounds like a bug.

@jpkrohling looks like it a problem with https://github.com/fsnotify/fsnotify on the symbolic link.
References:

https://github.com/fsnotify/fsnotify/issues/199
https://github.com/istio/istio/issues/7877
https://github.com/istio/istio/pull/9370

jaeger-query ui.json on OCP cluster:
sh-4.2$ ls -alh /etc/config/
total 0
drwxrwsrwx. 3 root 1000540000 74 Feb 28 16:12 .
drwxr-xr-x. 1 root root       20 Feb 28 16:12 ..
drwxr-sr-x. 2 root 1000540000 21 Feb 28 16:12 ..2020_02_28_16_12_02.394721388
lrwxrwxrwx. 1 root root       31 Feb 28 16:12 ..data -> ..2020_02_28_16_12_02.394721388
lrwxrwxrwx. 1 root root       14 Feb 28 16:12 ui.json -> ..data/ui.json

I wrote a small program to monitor file events on OCP cluster jaeger-query pod,
package main

import (
	"fmt"
	"path/filepath"
	"time"

	"github.com/fsnotify/fsnotify"
)

var file = "/etc/config/ui.json"

func main() {
	watcher, err := fsnotify.NewWatcher()
	if err != nil {
		panic(err)
	}
	err = watcher.Add(file)
	if err != nil {
		panic(err)
	}
	err = watcher.Add(filepath.Dir(file))
	if err != nil {
		panic(err)
	}
	for {
		select {
		case event := <-watcher.Events:
			fmt.Printf("%s, Event: %s\n", time.Now().Format("2006-01-02T15:04:05"), event.String())
		case err, ok := <-watcher.Errors:
			if !ok {
				panic(err)
			}
		}
	}
}

Result:
2020-02-28T17:12:01, Event: "/etc/config": CHMOD
2020-02-28T17:12:01, Event: "/etc/config/..2020_02_28_16_12_02.394721388": CHMOD
2020-02-28T17:12:01, Event: "/etc/config/ui.json": CHMOD
2020-02-28T17:13:22, Event: "/etc/config": CHMOD
2020-02-28T17:13:22, Event: "/etc/config/..2020_02_28_16_12_02.394721388": CHMOD
2020-02-28T17:13:22, Event: "/etc/config/ui.json": CHMOD
2020-02-28T17:14:29, Event: "/etc/config": CHMOD
2020-02-28T17:14:29, Event: "/etc/config/..2020_02_28_16_12_02.394721388": CHMOD
2020-02-28T17:14:29, Event: "/etc/config/ui.json": CHMOD
2020-02-28T17:15:48, Event: "/etc/config": CHMOD
2020-02-28T17:15:48, Event: "/etc/config/..2020_02_28_16_12_02.394721388": CHMOD
2020-02-28T17:15:48, Event: "/etc/config/ui.json": CHMOD
2020-02-28T17:16:54, Event: "/etc/config": CHMOD
2020-02-28T17:16:54, Event: "/etc/config/..2020_02_28_16_12_02.394721388": CHMOD
2020-02-28T17:16:54, Event: "/etc/config/ui.json": CHMOD
2020-02-28T17:18:17, Event: "/etc/config": CHMOD
2020-02-28T17:18:17, Event: "/etc/config/..2020_02_28_16_12_02.394721388": CHMOD
2020-02-28T17:18:17, Event: "/etc/config/ui.json": CHMOD
2020-02-28T17:19:31, Event: "/etc/config": CHMOD
2020-02-28T17:19:31, Event: "/etc/config/..2020_02_28_16_12_02.394721388": CHMOD
2020-02-28T17:19:31, Event: "/etc/config/ui.json": CHMOD
2020-02-28T17:20:37, Event: "/etc/config": CHMOD
2020-02-28T17:20:37, Event: "/etc/config/..2020_02_28_16_12_02.394721388": CHMOD
2020-02-28T17:20:37, Event: "/etc/config/ui.json": CHMOD
2020-02-28T17:22:07, Event: "/etc/config": CHMOD
2020-02-28T17:22:07, Event: "/etc/config/..2020_02_28_16_12_02.394721388": CHMOD
2020-02-28T17:22:07, Event: "/etc/config/ui.json": CHMOD
2020-02-28T17:23:35, Event: "/etc/config": CHMOD
2020-02-28T17:23:35, Event: "/etc/config/..2020_02_28_16_12_02.394721388": CHMOD
2020-02-28T17:23:35, Event: "/etc/config/ui.json": CHMOD
2020-02-28T17:24:48, Event: "/etc/config": CHMOD
2020-02-28T17:24:48, Event: "/etc/config/..2020_02_28_16_12_02.394721388": CHMOD
2020-02-28T17:24:48, Event: "/etc/config/ui.json": CHMOD
2020-02-28T17:26:15, Event: "/etc/config": CHMOD
2020-02-28T17:26:15, Event: "/etc/config/..2020_02_28_16_12_02.394721388": CHMOD
2020-02-28T17:26:15, Event: "/etc/config/ui.json": CHMOD
2020-02-28T17:27:41, Event: "/etc/config": CHMOD
2020-02-28T17:27:41, Event: "/etc/config/..2020_02_28_16_12_02.394721388": CHMOD
2020-02-28T17:27:41, Event: "/etc/config/ui.json": CHMOD
2020-02-28T17:28:57, Event: "/etc/config": CHMOD
2020-02-28T17:28:57, Event: "/etc/config/..2020_02_28_16_12_02.394721388": CHMOD
2020-02-28T17:28:57, Event: "/etc/config/ui.json": CHMOD
2020-02-28T17:29:59, Event: "/etc/config": CHMOD
2020-02-28T17:29:59, Event: "/etc/config": CHMOD
2020-02-28T17:29:59, Event: "/etc/config/..2020_02_28_16_12_02.394721388": CHMOD
2020-02-28T17:29:59, Event: "/etc/config/ui.json": CHMOD

If we are really reloading the UI when no changes are happening, we might want to filter those events out. Otherwise, we can just do a better work in the logging.

authors: jkandasa jpkrohling samcrutt9900

repo: jaegertracing/jaeger-operator


text:
tooltip placement

The first thing I do each time I open a trace is "collapse all", but as I hover over the button a tooltip pops up obscuring it. I have to hover away, wait for the tooltip to disappear, and then I can click the button.
Its always the first time the tooltip displays - subsequent renderings are placed unobtrusively.

Thanks for reporting the bug, @delanym.
As this is a UI concern, please create this bug issue in https://github.com/jaegertracing/jaeger-ui/issues.

@albertteoh do you have rights for https://docs.github.com/en/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository ?

authors: albertteoh delanym

repo: jaegertracing/jaeger


text:
WIP - Adds sqlite storage

Which problem is this PR solving?

Adds an SQLite storage backend for traces thereby providing an alternative to badger. I realise Jaeger already has a solution for local storage using badger so understand if this contribution isn't welcome.

Short description of the changes

The PR adds a new storage backend using SQLite.

I was hoping I'd be able to tag this WIP until I add support for dependencies but it seems I can't use any tags. Please feel free to review but understand this isn't yet complete.

Can you elaborate why you want it? Pros/Cons?

Can you elaborate why you want it? Pros/Cons?

While trying out badger I was underwhelmed with its performance and thought it would be interesting to write an alternative backend to benchmark against. Having done that I could see no reason not to share it.
This could also be moved to a separate project as a gRPC plugin but that would defeat the whole purpose of SQLite which is to embed it with the program that uses it.
The cons are that it requires CGO so full integration would mean tweaking some of the makefiles and getting around possible issues w/ Alpine/musl.

I wonder what was your issue with the badger performance? On my machine I can write around ~30 000 spans / s to disk which far exceeds the capabilities of what my other parts of Jaeger can do.
Although I do notice that your PR does not actually store to the disk:
if _, err := db.Exec("PRAGMA journal_mode = MEMORY;", nil); err != nil {

So there's reduced integrity - the badger instance will store it to the disk always (even if application crashes, the WriteSync option will only reduce the amount of fsyncs to the physical disk). Are you testing the same things here?

I wonder what was your issue with the badger performance? On my machine I can write around ~30 000 spans / s to disk which far exceeds the capabilities of what my other parts of Jaeger can do.

I wonder if those are example spans or representative of production workloads with tags, logs, etc?

Although I do notice that your PR does not actually store to the disk:

That option controls where the transaction journal is kept, not the actual data. The actual value for the option should be user provided according to how they assess the risk/benefit.
To be clear, the current options are for benchmarking purposes and do persist to disk.

From sqlite3 documentation: The MEMORY journaling mode stores the rollback journal in volatile RAM, now journaling log / WAL / transaction log is the key to the integrity of a SQL database. The tables in the disk are not written after every write (as they need to be rebuit) but instead only during the checkpointing. I don't see SQLite doing this process any differently.
It's easy to check. Keep writing data, kill the process and reload. If you don't have all the transactions, you never wrote them to the disk. And this is what happens. It's great for benchmarketing purposes, sure, but only to replace in-memory storage. The WAL is a bottleneck for many DBs as those operations need to be acked from the disk interface before they can be acked back to the client. And they're raced by all the concurrent writers.
But, that aside, looking at the implementation - I noticed you don't write all the data to the SQLite. So the original span is not written anywhere? I guess you could rely on just the tables to rebuild them, but in that case you need to write all the fields (some are missing now). Logs need indexing (and storing) also, as well as duration (unless you sacrifice reading performance for write performance). Also "index spans by service_name, operation_name, start_time" is missing start_time in the actual index.
And yes, the amount of indexed tags plays a big role in badger (each one is a new write). So with 128 unique tags values per span I get 3k/s with large amount of time spent in the kernel processes. Although, none of this actually stresses my machine so there's clearly a bottleneck in some serial process, disk or something else.

I had mentioned this earlier, but the WAL mode and journal modes should be provided by the client when the PR is complete. I believe it's up to them to be the judges of risk/benefit of each combination for their use case. This, of course, means exposing the options and documenting them, which I have not done yet.

But, that aside, looking at the implementation - I noticed you don't write all the data to the SQLite. So the original span is not written anywhere?
I'm not sure I understand, the spans are stored and I can query and see them in the UI. Do you mean actually marshalling the model.Span struct and store it in some field in the db for faster recreation at query time?

you need to write all the fields (some are missing now).
This is why I tagged the PR "WIP". At the moment, as you mentioned, durations aren't indexed and logs aren't stored. They don't need indexing as there's no way of querying for them.

Also "index spans by service_name, operation_name, start_time" is missing start_time in the actual index.
Good catch, thanks!

By the way, this isn't obvious and I should have mentioned it before.

I'm not claiming this backend is faster than badger. I am writing it to benchmark against badger and submitted the PR in case someone is interested.
The choice of wal mode and synchronous mode should be exposed to the end user as they will be better informed about which makes more sense to their use case.
The benchmarks journal in memory but do persist to disk. Losing the journal during a restart is not something I consider an issue. Losing some spans or traces should be statistically insignificant and would happen anyway during a restart of an all-in-one deployment.

Closing due to inactivity.

authors: burmanm fcvarela jpkrohling yurishkuro


text:
Edited text doesn't change after refresh

I've followed your routing documentation on http://anvel.io/docs/routing.
Navigating to the Route.
Add this link anywhere accessible.
<a [routerLink]="['/contact']">Contact
Note: Don't forget to inject ROUTER_DIRECTIVES into the component.
Refresh the page and click on the link.
I've been refreshing 1000 times, nothing happened. Noob here, please help.

Hey, you need to run command webpack to recompile your assets after you make changes. But obviously you don't want to do that every time. So run the file watchers by running webpack --watch. Any time you make changes, the builder will automatically compile the assets for you and refresh the page at http://localhost:3000.

If you are still having this issue, feel free to reopen.


text:
Not validating nested fields

Hi.
I discovered problem with validating nested fields.
Here is meteorpad that describes my situation: http://meteorpad.com/pad/xzFTb3H55jSeF96tJ/Nested fields jag:astronomy validation
Generally speaking no fields that are in form of 'object.property' are validated.
During debugging I noticed that in validate.js file on line 20 you have var fieldValidator = Class.getValidator(fieldName); and it is always undefined for nested fields.
There is fieldName==='language' in my case but it would work if there would be fieldName==='configuration.language' or Class would be configuration object

It's not a correct way of defining validators:
    validators: {
        'domains'                                   : v.object(),
        'domains.default'                           : v.string(),
        'domains.custom'                            : v.or( v.string(), v.null() ),
        'configuration'                             : v.object(),
        'configuration.type'                        : [v.string(), v.choice(['shop'])],
        'configuration.pages'                       : v.number(),
        'configuration.title'                       : v.string(),
        'configuration.language'                    : [v.required(), v.choice( ['pl', 'en', 'de'] )],
    },

There is no single line in a documentation that you can do so. You have to define a nested class to allow validation of nested fields http://astronomy.jagi.io/#nested-fields
You can define parent.child fields but it was done only for backward compatibility reason.
You can also do it in the following way:
User = Astro.Class({
  /* ... */
  fields: {
    /* ... */
    'parent.child': {
      type: 'string',
      validator: Validator.minLength(3)
    }
  }
});

You can define parent.child fields but it was done only for backward compatibility reason.

That's the reason I wrote it this way. I thought validation also will work with that.
It looks like I need to rewrite my validators. Thanks anyway:)

No problem :)

authors: jagi matikucharski

repo: jagi/meteor-astronomy


text:
emitting custom events?

Is it possible for behaviors to emit custom events?  For example, I'm doing a slightly different variant on softdelete that actually just runs on a remove via beforeremove.  It flags the object as deleted and cancels the remove.  Because the remove was cancelled, the afterremove event no longer fires (I assume).  And it shouldn't.
But I'd like the ability to emit an "aftersoftdelete" event that objects with this behavior could handle.
Is that possible?

Yes it's possible. The beforesoftremove and aftersoftremove events are triggered in the softremove behavior. Take a look at this line https://github.com/jagi/meteor-astronomy-softremove-behavior/blob/master/lib/behavior/methods.js#L23. There is a little "error", because I'm calling camel case beforeSoftRemove event and in fact I should call beforesoftremove. However as far as events names are case insensitive you can use both ways. However according to the standard in JS you should use the lowercase form.

Got it.  Thanks.

authors: dovrosenberg jagi


text:
[Feature Request] Lyrics source.

Lyrics sources do not find music. Could you add ksoft as lyrics source? Ksoft is the best.
Thank you.
Ksoft.si

The source you suggested, ksoft, does not appear to have an open (unauthenticated) API. Do you have an example of a song that you were not able to find on one of the existing lyrics sources?

Yeah,
https://www.youtube.com/watch?v=-hMj_-F7Gus
Song name: Yıldız Tilbe - Şivesi Sensin Aşkın
I tried A-Z Lyrics with Genius and MusicMatch, but it doesn't find it.
Would you try it? Thanks!

My musicbot version: 0.2.6

Can you run the debug command and paste the output here?

Closing as this has been unanswered for several months

authors: HexaMetrics jagrosh

repo: jagrosh/MusicBot


text:
[Feature Request] locales

Is your feature request related to a problem? Please describe.
A feature that we can change languages through commands
Describe the solution you'd like
Replace this text with a clear and concise description of what you want to happen.
Describe the basic flow/steps of using this feature
How this feature would be used:

Change bot different languages

Additional context
Add any other context or screenshots about the feature request here.
Please check the following links to confirm that your feature has not already been requested:
https://github.com/jagrosh/MusicBot/labels/enhancement
https://github.com/jagrosh/MusicBot/wiki/Things-That-Won't-Be-Added

Duplicate of #689.


text:
Add a note about what options to toggle in GA4

Hi. While this might seem obvious to others, could you kindly add a note in the readme file about what options users need to toggle in their GA4 property? (I think pageview, scroll and search?). Perhaps as a new paragraph just before or after the "Getting Started" heading.

Hi @stullesha,
By default, the official GA4 script tracks page_view, user_engagement, scroll and click events "out of the box". No additional config is required in the UI, or elsewhere.
This minimal version is exactly the same, e.g it "Just Works".
I've actually just added click event tracking in v1.6.0, so you'll now get those events too, bringing it to default feature parity with the official script.
If I've missed something, or I haven't answered your question, please let me know.
Thanks

I am actually referring to the ''Enhanced measurement" section of GA4.

I think you are misunderstanding my question. If a user doesn't toggle search and scroll in the ga4 property, will your code still track those features? This is what I am referring to!

If a user doesn't toggle search and scroll in the ga4 property, will your code still track those features?
@stullesha Oh right, I see, yeh your question wasn't super clear, you probably should have lead with in the first place!

So, of the default events that GA4 can track, this package only supports the first four:

Page View
Scrolls
Outbound Links
Site Search

This is kind of briefly mentioned in the opening paragraph, but I see your point, it could be clearer 👍
But to answer your actual question:
If a user turns off, or does not turn on, one of the supported tracking event types, does it still track those events?
Yes, these will still be tracked. The reason being, we are not requesting or receiving any GA4 UI defined config here, we're merely sending data to an endpoint. The flow of data is one way.
If you want to have more fine grained control over the GA4 tracking events, it's advised you use the official library. Implementing the complete suite of features of GA4 is, as I say, out of scope unfortunately, for this particular package.
I hope that better answers your question!

Alright! Now you have answered my question.

Okay. Which event name is for outbound links?

@stullesha  It will show up in your GA4 reports as click:

You can see relevant event params tracked as part of that event by clicking on it. I'd suggest looking up the official docs on how to generate reports on these.
Also remember there's some lag between events being tracked, and showing up in your reports.

Thank you. I will keep that in mind.

I can confirm the click event is now live.

authors: jahilldev stullesha

repo: jahilldev/minimal-analytics


text:
Discord link doesn't work

Discord link in README.md doesn't work.
I was having problems with .claudeignore on windows (The program seems to ignore it), so I was going to check out discord before opening an issue.

Seems it was set to expire after 7 days.. here you go https://discord.gg/pR4qeMH4u4

repo: jahwag/ClaudeSync


text:
Replace Google calendar

Use a self hosted option
Etesync looks promising (https://www.etesync.com/)
love the idea that i could also just, like, build my own too

DaviCal/Baïkal/Radical/etc.. Caldav server

DaviCal/Baïkal/Radical/etc.. Caldav server

Nextcloud provides good carddav and caldav support

Nextcloud provides good carddav and caldav support

Done! Using Radicale.

Done! Using Radicale.

repo: jakeisnt/nix-cfg


text:
Set up declarative backups

Set up backups via syncthing and duplicati
Resolve #72

Currently vultr's broken but I think this is because of some stateful configuration. I think it's cool to merge

Currently vultr's broken but I think this is because of some stateful configuration. I think it's cool to merge

Resolve #55 as well
Notable that duplicati is /not/ declarative; i have to set the passwords for backblaze myself.
in the future, use duplicity and configure them in a config file

Resolve #55 as well
Notable that duplicati is /not/ declarative; i have to set the passwords for backblaze myself.
in the future, use duplicity and configure them in a config file


text:
Fix typo on 02.06-Boolean-Arrays-and-Masks

do ---> to, In phrase "We are then free do operate..."

Thanks!

authors: jakevdp ncclementi

repo: jakevdp/PythonDataScienceHandbook


text:
Add exception and error handling to all scripts

All the scripts need better error handling, to make the code more robust and fault tolerant

Exception and error handling added for stock and movie script, along with escape statements for the programs

added error handling to ip_list.rb

Error handling added to rest of IP scripts

added to weather script, project complete.

repo: jakewmeyer/Ruby-Scripts


text:
Update to bevy 0.7

Closes #54.

Thanks for the effort, but I already had a bevy-main branch which was ready to go that I just merged.

authors: jakobhellermann tversteeg

repo: jakobhellermann/bevy-inspector-egui


text:
On npmjs.com, usage example is wrong

Hi, on npmjs.com, the text there shows this usage example.
var CleanCSS = require('clean-css');
var input = 'a{font-weight:bold;}';
var options = { /* options */ };
var output = new CleanCSS(options).minify(source);

The last line should be this:
var output = new CleanCSS(options).minify(input);
I can see this is correct here on github - it just hasn't propagated to npmjs.com

npmjs.com pulls the Readme on successful releases - I'll pull it into next 4.0.11

I've pulled it into 4.0.11 release and it's on npmjs.com now.

authors: hungsu jakubpawlowicz

repo: jakubpawlowicz/clean-css


text:
Thumbs subscription keeps unsubscribing in prod environment

So I created a Meteor app that has an image upload feature based heavily on the image upload functionality in the Socially tutorial.  That tutorial has me doing the following on the server:
import { UploadFS } from 'meteor/jalik:ufs';
import { Images, Thumbs } from './collection';

export const ThumbsStore = new UploadFS.store.GridFS({
    collection: Thumbs,
    name: 'thumbs',
    transformWrite(from, to, fileId, file) {
        // Resize to 100x100
        const gm = require('gm');
        const WIDTH = 100;
        const HEIGHT = 100;

        gm(from, file.name)
            .resize(WIDTH, HEIGHT)
            .gravity('Center')
            .extent(WIDTH, HEIGHT)
            .quality(75)
            .stream()
            .pipe(to);
    }
});

export const ImagesStore = new UploadFS.store.GridFS({
    collection: Images,
    name: 'images',
    filter: new UploadFS.Filter({
        contentTypes: ['image/*']
    }),
    copyTo: [
        ThumbsStore
    ]
});

and then subscribing to these collections on the client:
        this.subscribe('thumbs', () => [
            this.getReactively('files', true) || []
        ]);

        this.subscribe('images');

        this.helpers({
            thumbs() {
                return Thumbs.find({
                    originalStore: 'images',
                    originalId: {
                        $in: this.getReactively('files', true) || []
                    }
                });
            },

            image() {
                return Images.findOne({
                    _id: this.getReactively('selectedImageId')
                });
            }
        });

When I run it locally on localhost:3000 it runs great, images get uploaded, and the thumbs collection gets populated correctly.
However, when I deploy my app to the production environment, the "thumbs" subscription keeps getting unsubscribed and uploaded files never get copied into it. So my "images" collection has all the images, but the "thumbs" collection is completely empty. Using the Meteor dev tools for Chrome I can see the following messages sent over DDP:
subscribing to thumbs with PEAbhgKe7eukJoj7y "{"msg":"sub","id":"zYjmkFEHB68QpvZQQ ... }
unsubscribing from thumbs "{"msg":"unsub","id":"PiZzG2W8uafKbsKta"}"
subscription ready for thumbs "{"msg":"ready","subs":["zYjmkFEHB68Q ... }
unsubscribed from thumbs "{"msg":"nosub","id":"PiZzG2W8uafKbsKta"}"

I would appreciate any help you all could provide.
Casey

Hi @CaseyDStein, you should investigate the behavior of your this.getReactively() method which is the one that make the subscription change. Otherwise this issue is out of the scope of UploadFS. Please post it on StackOverflow or Meteor forums.

authors: CaseyDStein jalik

repo: jalik/jalik-ufs


text:
[Feature] Feed synapse launcher

Thanks for your brilliant script, it is extremelly useful. However, it would be a complete killer if it would integrate into synapse. Is this possible? The guys out on synapse resist to put their project into github, but I suspect it would be relatively easy to add it as a plugin.

Thanks for the idea. I think we want to wait till this work has matured further till its integrated with anything else - maybe when we've got the rest of the issues closed we can revisit this.

authors: jamcnaughton lf-araujo

repo: jamcnaughton/hud-menu