Notification loop does not stop with GitHub Actions

Hi, I’m testing the new GitOps feature in AKS, and I may have misconfigured something in the connector, because it has entered in an infinite loop of notifications.
I’m following the tutorial for CI/CD with flux in AKS: Tutorial: Implement CI/CD with GitOps (Flux v2) in Azure Arc-enabled Kubernetes clusters - Azure Arc | Microsoft Docs. I’ve configured a short time of reconciliation (2 minutes) to do some demos, so I can show how the system automagically recovers from almost-any manual change in the cluster. All worked well, but when I configured the gitops-connectorI realized that it had created hundreds of PRs for the stage environment, one every two minutes, because the CD_stage workflow starts also every two minutes:

It looks like the gitops-connector it is continuously sending a dispatch event to GitHub for every kustomize reconciliation, because the notification-controller sends a message for every kustomize run, even if it didn’t apply anything. In my understanding, as it is still the same commit revision and nothing changed in the repo nor in the cluster, the kustomize didn’t apply anything new, it should not do anything. But it does, so I may have something misconfigured that is causing this error.
Once I merge one of the PRs for the stage deployment, it correctly deploys the changes and then the github action starts to fail because there are no artifacts anymore:

I paste below some configurations and logs output for reference:
Gitops-connector.yaml values
apiVersion: notification.toolkit.fluxcd.io/v1beta1
kind: Alert
metadata:
  name: gitops-connector
  namespace: cluster-config
spec:
  eventSeverity: info
  eventSources:
  - kind: GitRepository
    name: cluster-config
  - kind: Kustomization
    name: cluster-config-cluster-config
  providerRef:
    name: gitops-connector
---
apiVersion: notification.toolkit.fluxcd.io/v1beta1
kind: Provider
metadata:
  name: gitops-connector
  namespace: cluster-config
spec:
  type: generic
  address: http://gitops-connector:8080/gitopsphase

gitops-connector-cm
apiVersion: v1
data:
  CICD_ORCHESTRATOR_TYPE: GITHUB
  GIT_REPOSITORY_TYPE: GITHUB
  GITHUB_GITOPS_MANIFEST_REPO_NAME: arc-cicd-demo-gitops
  GITHUB_GITOPS_REPO_NAME: arc-cicd-demo-src
  GITHUB_ORG_URL: https://api.github.com/repos/jmenterprisedemo
  GITOPS_APP_URL: https://github.com/jmenterprisedemo/arc-cicd-demo-gitops/commit
  GITOPS_OPERATOR_TYPE: FLUX
kind: ConfigMap
metadata:
  annotations:
    meta.helm.sh/release-name: gitops-connector
    meta.helm.sh/release-namespace: flux-system
  creationTimestamp: "2022-02-09T21:44:32Z"
  labels:
    app.kubernetes.io/managed-by: Helm
  name: gitops-connector-cm
  namespace: flux-system
  resourceVersion: "148426"
  uid: f8aa9588-52e5-4076-b75a-88472f27531b

gitrepositories yaml output
apiVersion: v1
items:
- apiVersion: source.toolkit.fluxcd.io/v1beta1
  kind: GitRepository
  metadata:
    annotations:
      reconcile.fluxcd.io/requestedAt: "2022-02-09T13:55:50.683325194Z"
    creationTimestamp: "2022-02-09T13:55:50Z"
    finalizers:
    - finalizers.fluxcd.io
    generation: 1
    labels:
      clusterconfig.azure.com/is-managed: "true"
      clusterconfig.azure.com/name: cluster-config
      clusterconfig.azure.com/namespace: cluster-config
      clusterconfig.azure.com/operation-id: 3367b7b5-6c09-4d1e-9097-04f154d02bd2
    name: cluster-config
    namespace: cluster-config
    ownerReferences:
    - apiVersion: clusterconfig.azure.com/v1alpha1
      blockOwnerDeletion: true
      controller: true
      kind: FluxConfig
      name: cluster-config
      uid: 4aa3cdcd-e6d1-4b9d-b4b8-c1f542cd0d75
    resourceVersion: "610928"
    uid: 2806483d-e818-4a27-a1ad-cbe7a90e9baf
  spec:
    gitImplementation: go-git
    interval: 2m0s
    ref:
      branch: master
    secretRef:
      name: cluster-config-auth
    timeout: 10m0s
    url: https://github.com/jmenterprisedemo/arc-cicd-demo-gitops

Gitops-connector logs
DEBUG:root:GitOps phase: {'involvedObject': {'kind': 'Kustomization', 'namespace': 'cluster-config', 'name': 'cluster-config-cluster-config', 'uid': 'bd3b061b-c480-4588-a4b1-b6aed6479a37', 'apiVersion': 'kustomize.toolkit.fluxcd.io/v1beta2', 'resourceVersion': '606325'}, 'severity': 'info', 'timestamp': '2022-02-10T22:47:00Z', 'message': 'Reconciliation finished in 1.56626684s, next run in 2m0s', 'reason': 'ReconciliationSucceeded', 'metadata': {'commit_status': 'update', 'revision': 'master/2b73b2fc54020e415e25c1fc1c351f65e205fbe0'}, 'reportingController': 'kustomize-controller', 'reportingInstance': 'kustomize-controller-7fcd68df9b-kxp2n'}
DEBUG:root:Kind: Kustomization
INFO:root:Url [https://api.github.com/repos/jmenterprisedemo/arc-cicd-demo-gitops/statuses/2b73b2fc54020e415e25c1fc1c351f65e205fbe0](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapi.github.com%2Frepos%2Fjmenterprisedemo%2Farc-cicd-demo-gitops%2Fstatuses%2F2b73b2fc54020e415e25c1fc1c351f65e205fbe0&data=04%7C01%7Cjuanmanuel.serverabondroit%40microsoft.com%7Cba13a277e893487600ad08d9ecee2d11%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637801330309800815%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=g%2BNpbDJzy4HS3x7lA88c88afVtHraWMHHuTL8s%2FO%2FRg%3D&reserved=0): Headers {'Authorization': 'token [redacted]'}: Data {'state': 'success', 'description': 'Reconciliation finished in 1.56626684s, next run in 2m0s', 'context': 'Status'}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): api.github.com:443
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): api.github.com:443
DEBUG:urllib3.connectionpool:https://api.github.com:443 "GET /repos/jmenterprisedemo/arc-cicd-demo-gitops/commits/2b73b2fc54020e415e25c1fc1c351f65e205fbe0 HTTP/1.1" 200 None
INFO:root:CommitId 16996351e30612f6a5c8b1bbfd986eae54188685
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): api.github.com:443
DEBUG:urllib3.connectionpool:https://api.github.com:443 "POST /repos/jmenterprisedemo/arc-cicd-demo-gitops/statuses/2b73b2fc54020e415e25c1fc1c351f65e205fbe0 HTTP/1.1" 201 1376
DEBUG:urllib3.connectionpool:https://api.github.com:443 "POST /repos/jmenterprisedemo/arc-cicd-demo-src/dispatches HTTP/1.1" 204 0
INFO:root:Starting periodic PR cleanup
INFO:root:Finished PR cleanup, sleeping for 30 seconds...
INFO:root:Starting periodic PR cleanup
INFO:root:Finished PR cleanup, sleeping for 30 seconds...
INFO:root:Starting periodic PR cleanup
INFO:root:Finished PR cleanup, sleeping for 30 seconds...
INFO:root:Starting periodic PR cleanup
INFO:root:Finished PR cleanup, sleeping for 30 seconds...
DEBUG:root:GitOps phase: {'involvedObject': {'kind': 'Kustomization', 'namespace': 'cluster-config', 'name': 'cluster-config-cluster-config', 'uid': 'bd3b061b-c480-4588-a4b1-b6aed6479a37', 'apiVersion': 'kustomize.toolkit.fluxcd.io/v1beta2', 'resourceVersion': '606968'}, 'severity': 'info', 'timestamp': '2022-02-10T22:49:02Z', 'message': 'Reconciliation finished in 1.556804789s, next run in 2m0s', 'reason': 'ReconciliationSucceeded', 'metadata': {'commit_status': 'update', 'revision': 'master/2b73b2fc54020e415e25c1fc1c351f65e205fbe0'}, 'reportingController': 'kustomize-controller', 'reportingInstance': 'kustomize-controller-7fcd68df9b-kxp2n'}
DEBUG:root:Kind: Kustomization
INFO:root:Url [https://api.github.com/repos/jmenterprisedemo/arc-cicd-demo-gitops/statuses/2b73b2fc54020e415e25c1fc1c351f65e205fbe0](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapi.github.com%2Frepos%2Fjmenterprisedemo%2Farc-cicd-demo-gitops%2Fstatuses%2F2b73b2fc54020e415e25c1fc1c351f65e205fbe0&data=04%7C01%7Cjuanmanuel.serverabondroit%40microsoft.com%7Cba13a277e893487600ad08d9ecee2d11%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637801330309800815%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=g%2BNpbDJzy4HS3x7lA88c88afVtHraWMHHuTL8s%2FO%2FRg%3D&reserved=0): Headers {'Authorization': 'token [redacted]'}: Data {'state': 'success', 'description': 'Reconciliation finished in 1.556804789s, next run in 2m0s', 'context': 'Status'}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): api.github.com:443
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): api.github.com:443
DEBUG:urllib3.connectionpool:https://api.github.com:443 "GET /repos/jmenterprisedemo/arc-cicd-demo-gitops/commits/2b73b2fc54020e415e25c1fc1c351f65e205fbe0 HTTP/1.1" 200 None
INFO:root:CommitId 16996351e30612f6a5c8b1bbfd986eae54188685
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): api.github.com:443
DEBUG:urllib3.connectionpool:https://api.github.com:443 "POST /repos/jmenterprisedemo/arc-cicd-demo-gitops/statuses/2b73b2fc54020e415e25c1fc1c351f65e205fbe0 HTTP/1.1" 201 1377
DEBUG:urllib3.connectionpool:https://api.github.com:443 "POST /repos/jmenterprisedemo/arc-cicd-demo-src/dispatches HTTP/1.1" 204 0
INFO:root:Starting periodic PR cleanup
INFO:root:Finished PR cleanup, sleeping for 30 seconds...
INFO:root:Starting periodic PR cleanup
INFO:root:Finished PR cleanup, sleeping for 30 seconds...
INFO:root:Starting periodic PR cleanup
INFO:root:Finished PR cleanup, sleeping for 30 seconds...
INFO:root:Starting periodic PR cleanup
INFO:root:Finished PR cleanup, sleeping for 30 seconds...
DEBUG:root:GitOps phase: {'involvedObject': {'kind': 'Kustomization', 'namespace': 'cluster-config', 'name': 'cluster-config-cluster-config', 'uid': 'bd3b061b-c480-4588-a4b1-b6aed6479a37', 'apiVersion': 'kustomize.toolkit.fluxcd.io/v1beta2', 'resourceVersion': '607584'}, 'severity': 'info', 'timestamp': '2022-02-10T22:51:03Z', 'message': 'Reconciliation finished in 1.5964757s, next run in 2m0s', 'reason': 'ReconciliationSucceeded', 'metadata': {'commit_status': 'update', 'revision': 'master/2b73b2fc54020e415e25c1fc1c351f65e205fbe0'}, 'reportingController': 'kustomize-controller', 'reportingInstance': 'kustomize-controller-7fcd68df9b-kxp2n'}
DEBUG:root:Kind: Kustomization
INFO:root:Url [https://api.github.com/repos/jmenterprisedemo/arc-cicd-demo-gitops/statuses/2b73b2fc54020e415e25c1fc1c351f65e205fbe0](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapi.github.com%2Frepos%2Fjmenterprisedemo%2Farc-cicd-demo-gitops%2Fstatuses%2F2b73b2fc54020e415e25c1fc1c351f65e205fbe0&data=04%7C01%7Cjuanmanuel.serverabondroit%40microsoft.com%7Cba13a277e893487600ad08d9ecee2d11%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637801330309800815%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=g%2BNpbDJzy4HS3x7lA88c88afVtHraWMHHuTL8s%2FO%2FRg%3D&reserved=0): Headers {'Authorization': 'token [redacted]'}: Data {'state': 'success', 'description': 'Reconciliation finished in 1.5964757s, next run in 2m0s', 'context': 'Status'}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): api.github.com:443
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): api.github.com:443
DEBUG:urllib3.connectionpool:https://api.github.com:443 "GET /repos/jmenterprisedemo/arc-cicd-demo-gitops/commits/2b73b2fc54020e415e25c1fc1c351f65e205fbe0 HTTP/1.1" 200 None
INFO:root:CommitId 16996351e30612f6a5c8b1bbfd986eae54188685
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): api.github.com:443
DEBUG:urllib3.connectionpool:https://api.github.com:443 "POST /repos/jmenterprisedemo/arc-cicd-demo-gitops/statuses/2b73b2fc54020e415e25c1fc1c351f65e205fbe0 HTTP/1.1" 201 1375
DEBUG:urllib3.connectionpool:https://api.github.com:443 "POST /repos/jmenterprisedemo/arc-cicd-demo-src/dispatches HTTP/1.1" 204 0

Notification controller logs
{"level":"info","ts":"2022-02-10T22:49:02.102Z","logger":"event-server","msg":"Dispatching event: Reconciliation finished in 1.556804789s, next run in 2m0s","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config"}
{"level":"info","ts":"2022-02-10T22:51:03.712Z","logger":"event-server","msg":"Dispatching event: Reconciliation finished in 1.5964757s, next run in 2m0s","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config"}
{"level":"info","ts":"2022-02-10T22:53:05.290Z","logger":"event-server","msg":"Dispatching event: Reconciliation finished in 1.54985846s, next run in 2m0s","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config"}
{"level":"info","ts":"2022-02-10T22:55:06.902Z","logger":"event-server","msg":"Dispatching event: Reconciliation finished in 1.57785959s, next run in 2m0s","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config"}
{"level":"info","ts":"2022-02-10T22:57:08.458Z","logger":"event-server","msg":"Dispatching event: Reconciliation finished in 1.545596821s, next run in 2m0s","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config"}
{"level":"info","ts":"2022-02-10T22:57:46.005Z","logger":"event-server","msg":"Dispatching event: Fetched revision: master/444ee463530ca540cf52368fa3c79a94c91ba42d","reconciler kind":"GitRepository","name":"cluster-config","namespace":"cluster-config"}
{"level":"info","ts":"2022-02-10T22:57:47.509Z","logger":"event-server","msg":"Dispatching event: Deployment/stage/azure-vote-back configured\nDeployment/stage/azure-vote-front configured","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config"}
{"level":"info","ts":"2022-02-10T22:57:47.526Z","logger":"event-server","msg":"Dispatching event: Reconciliation finished in 1.526845864s, next run in 2m0s","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config"}
{"level":"info","ts":"2022-02-10T22:59:09.985Z","logger":"event-server","msg":"Dispatching event: Reconciliation finished in 1.52466977s, next run in 2m0s","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config"}
{"level":"info","ts":"2022-02-10T22:59:46.436Z","logger":"event-server","msg":"Dispatching event: Fetched revision: master/59703674c7f3526e1de3999c73f84d13c6941214","reconciler kind":"GitRepository","name":"cluster-config","namespace":"cluster-config"}
{"level":"info","ts":"2022-02-10T22:59:47.966Z","logger":"event-server","msg":"Dispatching event: Reconciliation finished in 1.536128865s, next run in 2m0s","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config"}
{"level":"info","ts":"2022-02-10T23:01:11.539Z","logger":"event-server","msg":"Dispatching event: Reconciliation finished in 1.55205511s, next run in 2m0s","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config"}
{"level":"info","ts":"2022-02-10T23:03:13.130Z","logger":"event-server","msg":"Dispatching event: Reconciliation finished in 1.57047581s, next run in 2m0s","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config"}

Kustomization controller logs
kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config","revision":"master/2b73b2fc54020e415e25c1fc1c351f65e205fbe0"}
I0210 22:55:06.376002       7 request.go:665] Waited for 1.045274513s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/snapshot.storage.k8s.io/v1beta1?timeout=32s
{"level":"info","ts":"2022-02-10T22:55:06.579Z","logger":"controller.kustomization","msg":"server-side apply completed","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config","output":{"Namespace/dev":"unchanged","Namespace/ingress-basic":"unchanged","Namespace/stage":"unchanged"}}
{"level":"info","ts":"2022-02-10T22:55:06.862Z","logger":"controller.kustomization","msg":"server-side apply completed","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config","output":{"Deployment/dev/azure-vote-back":"unchanged","Deployment/dev/azure-vote-front":"unchanged","Deployment/stage/azure-vote-back":"unchanged","Deployment/stage/azure-vote-front":"unchanged","HelmRelease/ingress-basic/ingress-nginx":"unchanged","HelmRepository/ingress-basic/ingress-nginx":"unchanged","Ingress/dev/az-vote-front-ingress":"unchanged","Ingress/stage/az-vote-front-ingress":"unchanged","Service/dev/azure-vote-back":"unchanged","Service/dev/azure-vote-front":"unchanged","Service/stage/azure-vote-back":"unchanged","Service/stage/azure-vote-front":"unchanged"}}
{"level":"info","ts":"2022-02-10T22:55:06.875Z","logger":"controller.kustomization","msg":"Reconciliation finished in 1.57785959s, next run in 2m0s","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config","revision":"master/2b73b2fc54020e415e25c1fc1c351f65e205fbe0"}
I0210 22:57:07.980448       7 request.go:665] Waited for 1.04500041s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/policy/v1?timeout=32s
{"level":"info","ts":"2022-02-10T22:57:08.187Z","logger":"controller.kustomization","msg":"server-side apply completed","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config","output":{"Namespace/dev":"unchanged","Namespace/ingress-basic":"unchanged","Namespace/stage":"unchanged"}}
{"level":"info","ts":"2022-02-10T22:57:08.435Z","logger":"controller.kustomization","msg":"server-side apply completed","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config","output":{"Deployment/dev/azure-vote-back":"unchanged","Deployment/dev/azure-vote-front":"unchanged","Deployment/stage/azure-vote-back":"unchanged","Deployment/stage/azure-vote-front":"unchanged","HelmRelease/ingress-basic/ingress-nginx":"unchanged","HelmRepository/ingress-basic/ingress-nginx":"unchanged","Ingress/dev/az-vote-front-ingress":"unchanged","Ingress/stage/az-vote-front-ingress":"unchanged","Service/dev/azure-vote-back":"unchanged","Service/dev/azure-vote-front":"unchanged","Service/stage/azure-vote-back":"unchanged","Service/stage/azure-vote-front":"unchanged"}}
{"level":"info","ts":"2022-02-10T22:57:08.448Z","logger":"controller.kustomization","msg":"Reconciliation finished in 1.545596821s, next run in 2m0s","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config","revision":"master/2b73b2fc54020e415e25c1fc1c351f65e205fbe0"}
I0210 22:57:47.066079       7 request.go:665] Waited for 1.045471167s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/policy/v1?timeout=32s
{"level":"info","ts":"2022-02-10T22:57:47.266Z","logger":"controller.kustomization","msg":"server-side apply completed","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config","output":{"Namespace/dev":"unchanged","Namespace/ingress-basic":"unchanged","Namespace/stage":"unchanged"}}
{"level":"info","ts":"2022-02-10T22:57:47.507Z","logger":"controller.kustomization","msg":"server-side apply completed","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config","output":{"Deployment/dev/azure-vote-back":"unchanged","Deployment/dev/azure-vote-front":"unchanged","Deployment/stage/azure-vote-back":"configured","Deployment/stage/azure-vote-front":"configured","HelmRelease/ingress-basic/ingress-nginx":"unchanged","HelmRepository/ingress-basic/ingress-nginx":"unchanged","Ingress/dev/az-vote-front-ingress":"unchanged","Ingress/stage/az-vote-front-ingress":"unchanged","Service/dev/azure-vote-back":"unchanged","Service/dev/azure-vote-front":"unchanged","Service/stage/azure-vote-back":"unchanged","Service/stage/azure-vote-front":"unchanged"}}
{"level":"info","ts":"2022-02-10T22:57:47.524Z","logger":"controller.kustomization","msg":"Reconciliation finished in 1.526845864s, next run in 2m0s","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config","revision":"master/444ee463530ca540cf52368fa3c79a94c91ba42d"}
I0210 22:59:09.526827       7 request.go:665] Waited for 1.04595049s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/scheduling.k8s.io/v1?timeout=32s
{"level":"info","ts":"2022-02-10T22:59:09.729Z","logger":"controller.kustomization","msg":"server-side apply completed","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config","output":{"Namespace/dev":"unchanged","Namespace/ingress-basic":"unchanged","Namespace/stage":"unchanged"}}
{"level":"info","ts":"2022-02-10T22:59:09.971Z","logger":"controller.kustomization","msg":"server-side apply completed","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config","output":{"Deployment/dev/azure-vote-back":"unchanged","Deployment/dev/azure-vote-front":"unchanged","Deployment/stage/azure-vote-back":"unchanged","Deployment/stage/azure-vote-front":"unchanged","HelmRelease/ingress-basic/ingress-nginx":"unchanged","HelmRepository/ingress-basic/ingress-nginx":"unchanged","Ingress/dev/az-vote-front-ingress":"unchanged","Ingress/stage/az-vote-front-ingress":"unchanged","Service/dev/azure-vote-back":"unchanged","Service/dev/azure-vote-front":"unchanged","Service/stage/azure-vote-back":"unchanged","Service/stage/azure-vote-front":"unchanged"}}
{"level":"info","ts":"2022-02-10T22:59:09.983Z","logger":"controller.kustomization","msg":"Reconciliation finished in 1.52466977s, next run in 2m0s","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config","revision":"master/444ee463530ca540cf52368fa3c79a94c91ba42d"}
I0210 22:59:47.493934       7 request.go:665] Waited for 1.044181943s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/rbac.authorization.k8s.io/v1?timeout=32s
{"level":"info","ts":"2022-02-10T22:59:47.701Z","logger":"controller.kustomization","msg":"server-side apply completed","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config","output":{"Namespace/dev":"unchanged","Namespace/ingress-basic":"unchanged","Namespace/stage":"unchanged"}}
{"level":"info","ts":"2022-02-10T22:59:47.948Z","logger":"controller.kustomization","msg":"server-side apply completed","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config","output":{"Deployment/dev/azure-vote-back":"unchanged","Deployment/dev/azure-vote-front":"unchanged","Deployment/stage/azure-vote-back":"unchanged","Deployment/stage/azure-vote-front":"unchanged","HelmRelease/ingress-basic/ingress-nginx":"unchanged","HelmRepository/ingress-basic/ingress-nginx":"unchanged","Ingress/dev/az-vote-front-ingress":"unchanged","Ingress/stage/az-vote-front-ingress":"unchanged","Service/dev/azure-vote-back":"unchanged","Service/dev/azure-vote-front":"unchanged","Service/stage/azure-vote-back":"unchanged","Service/stage/azure-vote-front":"unchanged"}}
{"level":"info","ts":"2022-02-10T22:59:47.963Z","logger":"controller.kustomization","msg":"Reconciliation finished in 1.536128865s, next run in 2m0s","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config","revision":"master/59703674c7f3526e1de3999c73f84d13c6941214"}
I0210 23:01:11.059355       7 request.go:665] Waited for 1.043187792s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/coordination.k8s.io/v1?timeout=32s
{"level":"info","ts":"2022-02-10T23:01:11.273Z","logger":"controller.kustomization","msg":"server-side apply completed","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config","output":{"Namespace/dev":"unchanged","Namespace/ingress-basic":"unchanged","Namespace/stage":"unchanged"}}
{"level":"info","ts":"2022-02-10T23:01:11.521Z","logger":"controller.kustomization","msg":"server-side apply completed","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config","output":{"Deployment/dev/azure-vote-back":"unchanged","Deployment/dev/azure-vote-front":"unchanged","Deployment/stage/azure-vote-back":"unchanged","Deployment/stage/azure-vote-front":"unchanged","HelmRelease/ingress-basic/ingress-nginx":"unchanged","HelmRepository/ingress-basic/ingress-nginx":"unchanged","Ingress/dev/az-vote-front-ingress":"unchanged","Ingress/stage/az-vote-front-ingress":"unchanged","Service/dev/azure-vote-back":"unchanged","Service/dev/azure-vote-front":"unchanged","Service/stage/azure-vote-back":"unchanged","Service/stage/azure-vote-front":"unchanged"}}
{"level":"info","ts":"2022-02-10T23:01:11.537Z","logger":"controller.kustomization","msg":"Reconciliation finished in 1.55205511s, next run in 2m0s","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config","revision":"master/59703674c7f3526e1de3999c73f84d13c6941214"}
I0210 23:03:12.609901       7 request.go:665] Waited for 1.045898838s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/discovery.k8s.io/v1beta1?timeout=32s
{"level":"info","ts":"2022-02-10T23:03:12.817Z","logger":"controller.kustomization","msg":"server-side apply completed","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config","output":{"Namespace/dev":"unchanged","Namespace/ingress-basic":"unchanged","Namespace/stage":"unchanged"}}
{"level":"info","ts":"2022-02-10T23:03:13.096Z","logger":"controller.kustomization","msg":"server-side apply completed","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config","output":{"Deployment/dev/azure-vote-back":"unchanged","Deployment/dev/azure-vote-front":"unchanged","Deployment/stage/azure-vote-back":"unchanged","Deployment/stage/azure-vote-front":"unchanged","HelmRelease/ingress-basic/ingress-nginx":"unchanged","HelmRepository/ingress-basic/ingress-nginx":"unchanged","Ingress/dev/az-vote-front-ingress":"unchanged","Ingress/stage/az-vote-front-ingress":"unchanged","Service/dev/azure-vote-back":"unchanged","Service/dev/azure-vote-front":"unchanged","Service/stage/azure-vote-back":"unchanged","Service/stage/azure-vote-front":"unchanged"}}
{"level":"info","ts":"2022-02-10T23:03:13.110Z","logger":"controller.kustomization","msg":"Reconciliation finished in 1.57047581s, next run in 2m0s","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"cluster-config-cluster-config","namespace":"cluster-config","revision":"master/59703674c7f3526e1de3999c73f84d13c6941214"}

@jmservera I fixed the issue. Use ghcr.io/azure/gitops-connector:isssue.27 image for the connector until it is released.


App request

Add Notion to the install tab in WinUtil

Unfortunately Notion is not Open Source and probably doesn't belong in the tool. Have you considered Logseq, Joplin or https://anytype.io/? All the tools above are Open Source Free and do not require cloud accounts so you own your data.


Data Science with Python : Glass Classification and Analysis #7797

Description 📜
Code for Glass Classification and Analysis using various Machine Learning Classification algorithms (Contains explanation of dataset, different algorithms and the code)
Fixes #7797

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] Datascience with Python

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

Please evaluate @prathimacode-hub @Yash621 @Nithin-Reddy-02
Name: Deepika Pavundoss
Issue: Data Science with Python : Glass Classification and Analysis #7797
Type: Documentation
Batch number: 5
Serial number: 161

Thank you ma'am 😄 @prathimacode-hub


AudioKit 5.3.0 MIDICallbackInstrument not working?

I'm new to AudioKit. I'm trying to get a naive case working where Midi is read from a file and have the AppleSequencer relay event information to the console via print. I am working with a command line program on xcode 11.
let path = "FullPath/To/MIDI_sample.mid"
let sequencer = AppleSequencer(fromURL:  URL(fileURLWithPath: path))
let callbackInstr = MIDICallbackInstrument()

func initializeSession() {
    sequencer.setGlobalMIDIOutput(callbackInstr.midiIn)
    callbackInstr.callback = myCallBack
    sequencer.enableLooping()

    sequencer.setTempo(85.0)
    sequencer.addTimeSignatureEvent(timeSignature: TimeSignature(topValue: 4, bottomValue: .four))
    sequencer.setLength(Duration(beats: 4.0))

    sequencer.play()
    print(sequencer.isPlaying)
    usleep(UInt32(5000000))
    print(sequencer.isPlaying)
}

func myCallBack(a: UInt8, b:MIDINoteNumber, c:MIDIVelocity) -> () {
    print(a,b,c);
}

initializeSession()

The console output right now is:
2022-01-07 11:33:36.507401-0600 audioKitCommandLine[84619:12905225] [seq]         SequenceTrack.cpp:927   Clear: Invalid beat range or track is empty
2022-01-07 11:33:36.507711-0600 audioKitCommandLine[84619:12905225] [seq]         SequenceTrack.cpp:1037  Merge: Invalid beat range
2022-01-07 11:33:36.507940-0600 audioKitCommandLine[84619:12905225] [midi] MIDI.swift:init():52:Initializing MIDI (MIDI.swift:init():52)
true
true
Program ended with exit code: 0

I have seen elsewhere that Clear: Invalid beat range or track is empty is a warning, but I am expecting the myCallBack function to be called and produce output. Any help would be appreciated!

Have you enabled background audio mode in your app's Info.plist file?

Closing until we hear back.


fix: check for margin-left and margin-right not present

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #52181

In this code update, I have checked to make sure that  margin-left and margin-right are not present so campers cannot use margin: 5px or margin: 5px 0 or margin: 5px 0 5px 0 which will set margin-left and margin-right. The campers have to compulsorily use margin-top: 5px and margin-bottom: 5px.

@naomi-lgbt The requested change has been made.

Thank you for your contribution to the page! 👍
We are happy to accept these changes and look forward to future contributions. 🎉


BUG tide

is this the bot in this script? bots should not have a name like this. this is likely a default bot from Valve or some other scripts

Hi Jojo, I think this issue and previous issues you had were all about the default bot script from Valve. Not mine.
Please follow the instructions to install this bot.
Bots in this script should have names in a format like teamName.playerName. For example: IG.Maybe
There is currently a bug in Vavle where all new bot scripts can not be loaded correctly. You will have to copy paste some files in your computer to be able to play this script.

Closing the issue now. Make sure to install the script correctly by following the README instructions or steps in the Workshop content of this script.


[5.8] Update JSON Blade Directive

continuation of #27802
please be gentle, code is a little ugly. This is an attempt to use "tokenization" rather than explode() to extract arguments from a Blade directive. The explode() is lacking because it cannot handle situations when the delimiter character also exists in one of the argument expressions.
The PR will correctly identify when an argument contains opening characters (( and [) in an argument and not move onto the next argument when a delimiter character is met until all the opening characters have been closed.
All current tests pass, and I have added some extras in for the additional behavior.
Currently, it is very easy to incorrectly use the @json directive with the assumption of the default 'safe encoding' options, and this PR fixes that as well.

It feels easier at this point to just pass a variable? 😄

so I understand correctly, you're suggesting something like:
@php
$var1 = [
    'value1',
    'value2',
    'value3',
];

$var2 = array_merge(['value1', 'value2'], ['value3', 'value4']);
@endphp

let var1 = @json($var1)

let var2 = @json($var2)

Ehhh, idk.  I can tell you I was definitely using this directive incorrectly. We were also using it incorrectly in Spark (although that was my fault on the PR, but it did get through).
Other than the code being ugly, I don't see a downside. It works as intended and is tested, helps prevents incorrect usage of the directive, and gives users more flexibility with what they are allowed to pass.
Maybe the argument extraction gets extracted to another place so all the Blade directives can use it, too?

I meant the whole point of the @json directive (from my memory), was... you are passing an array from your controller to the view, and you simply do:
@json($variable)

I don't think I necessarily set out to support arbitrary JSON inlined into the @json directive.

I think I'll keep things as they are on 5.8 at least.


remove education phase class to match field with new data

I have replaced both fields as I think it looks cleaner. Plus if the status codes ever change we won't need to update the code


Join lines in compiled markdown so lists render in Confluence without…

… extra whitespace

Looks good to me, thanks for the contribution!

Looks good to me, thanks for the contribution!


do not make this noarch

Fix PR#1 because it should not be no arch.

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_7cnb84kigd/clone/recipe/meta.yaml:20: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_a7ch5_0ucy/clone/recipe/meta.yaml:20: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found


M3-1065 Update email field to be text

Update email field to be text
There's general confusion between user email and account email address → we can help by removing fields you don't have that differentiate between items.  API doesn't allow changing user email address, let's use plain text instead to indicate to the user that it cannot be changed.
Type of Change

Non breaking change

account/users/[user]/profile

Coverage decreased (-0.001%) to 34.751% when pulling 0cb148e0759b0e87d6665902f054a1651d3b3711 on alioso:M3-1065 into b04405114b5f695eea2fca6c40687d6856b32792 on linode:develop.


Fix run_time issue

https://asciinema.org/a/kIxwrxpXKToVsqhCDmGWyEszh

@felipemeriga feel free to merge it! o/


Instantiate the FormioWizard class

I get this warning in the browser "You need to instantiate the FormioWizard class to use this form as a wizard" when I load a wizard form. However, I cannot find any information in the documentation on what to do apart from the old AngularJS documentation that says to use <formio-wizard .....> which doesn't work.
Can anyone help?

I'm not sure exact your situation without your code. I'm assuming you are trying to use wizard mode. This is what I did.
html: <formio [form]="json">
Use a panal type for a page of wizard and add "display":"wizard".
e.g.)
ts: this.json = {
"components": [
{
"type": "panel",
"title": "wiz1"
},
{
"type": "panel",
"title": "wiz2"
}
],
"display": "wizard"
}

The JSON has the panel type and display:wizard as I'm using the formio code to produce the JSON.
So for example the following very simple two pager produces the warning mentioned in the original post:
{"_id":"5cab40cfec9dd94d4f71f04b","type":"form","tags":["common"],"owner":"5cab3f5aec9dd94d4f71f04a","components":[{"type":"panel","title":"Page 1","components":[{"key":"page1Content","label":"Content","input":false,"tag":"h1","attrs":[{"value":"","attr":""}],"className":"","content":"Form X","type":"htmlelement","hideLabel":true,"tags":[],"conditional":{"show":"","when":null,"eq":""},"properties":{}}],"input":false,"key":"page1","clearOnHide":false,"theme":"default","tableView":false,"hideLabel":false},{"type":"panel","title":"Page 2","components":[{"key":"page2Content","label":"Content","input":false,"tag":"h1","attrs":[{"value":"","attr":""}],"className":"","content":"Form X - page 2","type":"htmlelement","hideLabel":true,"tags":[],"conditional":{"show":"","when":null,"eq":""},"properties":{}}],"input":false,"key":"page2","clearOnHide":false,"theme":"default","tableView":false,"hideLabel":false}],"display":"wizard","submissionAccess":[{"roles":["5cab3f42ec9dd94d4f71f03d"],"type":"create_own"},{"roles":["5cab3f42ec9dd94d4f71f03d"],"type":"read_own"},{"roles":["5cab3f42ec9dd94d4f71f03d"],"type":"update_own"},{"roles":["5cab3f42ec9dd94d4f71f03d"],"type":"delete_own"}],"path":"eligibility-x","title":"Eligibility check X","name":"eligibilityCheckX","access":[{"roles":["5cab3f42ec9dd94d4f71f03c","5cab3f42ec9dd94d4f71f03d","5cab3f42ec9dd94d4f71f03e"],"type":"read_all"}],"created":"2019-04-08T12:38:39.162Z","modified":"2019-04-12T13:35:09.865Z","machineName":"eligibilityCheckX"}

We're currently addressing a backlog of GitHub issues, and as part of this effort, some inactive issues may be marked as closed. This isn't a dismissal, but a step toward more efficient tracking.
If you feel the issue is still relevant, please re-open and we'll ensure it gets the attention it deserves. Your understanding is appreciated as we work to enhance our open-source responsiveness.


Add create client, connections and channels to the sidecar CLI

Add a CLI command for each of these scenarios:

Create clients on both chains
Create connections on both chains
Create channels on both chains (transfer only needed)

Completed in https://github.com/cosmos/interchain-attestation/commit/60e2f383981cca20d8fac6b90e430074d679a11b


denied: access forbidden for download container

Unfortunately, I do not have permission to download the image
registry.gitlab.com/tsuribori/docker-pleroma
can this be opened to the world?

It should be open now.
However it uses an outdated Pleroma version of 2.4.3 (current is 2.5.0) so I would recommend building your own image and using it instead: https://github.com/angristan/docker-pleroma

Thanks for info


Incorrect map key suggestions

Looks like this is no longer an issue :eyes:

This is still an issue: https://discordapp.com/channels/666020457568403505/666020458453270535/776309942826827776


Setup Cache for BuildKit

Setup Cache for BuildKit

Update actions

Add labels from meta action

Looks to have shaved about 4 min off... based on one sample size, thanks!


Make zinc-benchmarks tests (avoid compile->test)

As a workaround to https://youtrack.jetbrains.com/issue/SCL-8396.

To validate this pull request against other sbt modules, please visit this link.


Hyprland crashes on keypress after start from tty

I installed hyprland-git from the AUR earlier this evening, and when starting it from a tty it seems to initialize fine, but as soon as I press any key it segfaults. Any advice is appreciated!
coredump.txt
hyprland.log

reading the log yourself is not a terrible idea you know

It should perhaps make a default config if none is detected

it does that. It just sometimes can't for some reason on some people's pcs

I installed hyprland-git from the AUR earlier this evening, and when starting it from a tty it seems to initialize fine, but as soon as I press any key it segfaults. Any advice is appreciated!

Make sure there's a directory called "hypr" inside your ~/.config
Hope that helps ~

ah yeah that might explain why hyprland fails to autogenerate a config

closing, incativity and solved

Many thanks to @R-VL for the advice that helped me solve this!
I'm planning on making a PR sometime in the near future that will eliminate this problem (or at least provide more verbose logging) for other users.

@dgpalmieri it was already solved in https://github.com/vaxerski/Hyprland/pull/223


Containerd lost the control of shim

Description
When kubelet continuous call StopPodSandbox and StopContainer, the timestamp is Aug 7 19:07:50，there are no any TaskExit Event of this container but it has the following errors:
Aug  7 19:07:50 time="2024-08-07T19:07:50.950859134+08:00" level=error msg="StopContainer for \"f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09\" failed" error="rpc error: code = DeadlineExceeded desc = an error occurs during waiting for container \"f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09\" to be killed: wait container \"f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09\": context deadline exceeded"
Aug  7 19:07:50 time="2024-08-07T19:07:50.952326934+08:00" level=info msg="Kill container \"f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09\""
Aug  7 19:07:50 time="2024-08-07T19:07:50.950859134+08:00" level=error msg="StopContainer for \"f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09\" failed" error="rpc error: code = DeadlineExceeded desc = an error occurs during waiting for container \"f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09\" to be killed: wait container \"f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09\": context deadline exceeded"
Aug  7 19:07:50 time="2024-08-07T19:07:50.952326934+08:00" level=info msg="Kill container \"f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09\""

And in Aug 17 20:16:03  we found containerd recieved a TaskOOM event,  which means container is still alive at 2024-08-17T20:16:03
Aug 17 20:16:03 time="2024-08-17T20:16:03.466740501+08:00" level=info msg="TaskOOM event &TaskOOM{ContainerID:f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09,XXX_unrecognized:[],}"

except for this one,  there are no any other Task related events. At the same time, kubelet still attempt to access the container
Aug 17 20:16:00 containerd[2959773]: time="2024-08-17T20:16:00.504879132+08:00" level=error msg="ExecSync for \"f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09\" failed" error="failed to exec in container: failed to start exec \"44d18627e51386c9661f8f0253e6b63f4a7ea3f6dd5e812959c1567b1dcb50cd\": OCI runtime exec failed: exec failed: cannot exec in a stopped container: unknown"
Aug 17 20:16:00 containerd[2959773]: time="2024-08-17T20:16:00.505607821+08:00" level=debug msg="ExecSync for \"f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09\" with command [/bin/bash -c /home/xiaoju/disfv4-agent/control-internal alive] and timeout 1 (s)"
Aug 17 20:16:00 containerd[2959773]: time="2024-08-17T20:16:00.506365901+08:00" level=debug msg="Generated exec id \"25b8927f3cc4990588d601d86a9399103f23b7d17373be4f50abbe91cdc75297\" for container \"f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09\""
Aug 17 20:16:01 containerd[2959773]: time="2024-08-17T20:16:01.657220377+08:00" level=error msg="ExecSync for \"f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09\" failed" error="failed to exec in container: failed to start exec \"25b8927f3cc4990588d601d86a9399103f23b7d17373be4f50abbe91cdc75297\": OCI runtime exec failed: exec failed: cannot exec in a stopped container: unknown"
Aug 17 20:16:03 containerd[2959773]: time="2024-08-17T20:16:03.466740501+08:00" level=info msg="TaskOOM event &TaskOOM{ContainerID:f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09,XXX_unrecognized:[],}"
Aug 17 20:16:08 containerd[2959773]: time="2024-08-17T20:16:08.803047238+08:00" level=debug msg="ExecSync for \"f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09\" with command [/bin/bash -c /home/xiaoju/disfv4-agent/control-internal alive] and timeout 1 (s)"
Aug 17 20:16:08 containerd[2959773]: time="2024-08-17T20:16:08.803886857+08:00" level=debug msg="Generated exec id \"35e9846f03a6169d73a2b5706d21d007c4584217b26b2481760cd0402dc266ce\" for container \"f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09\""
Aug 17 20:16:09 containerd[2959773]: time="2024-08-17T20:16:09.617423587+08:00" level=error msg="ExecSync for \"f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09\" failed" error="failed to exec in container: failed to start exec \"35e9846f03a6169d73a2b5706d21d007c4584217b26b2481760cd0402dc266ce\": OCI runtime exec failed: exec failed: cannot exec in a stopped container: unknown"

And the status of container:
{"Version":"v1","Pid":1365945,"CreatedAt":1721705447203688248,"StartedAt":1721705447472944662,"FinishedAt":0,"ExitCode":0,"Reason":"00MKilled","Message":"","Resources":{"linux":{"cpu_period":100000,"cpu_quota":20 o00,"cpu_shares":2,"memory_limit_in_bytes":2147483648,"oom_score_adj":999,"memory_swap_limit_in_bytes":2147483648}}}

and the dockerinit of this container is not running
ps aux | grep 1365945
root 870590 0.0 0.0 16244 1128 pts/2 S+

but we could see the task is still running:
ctr -n k8s.io task ls | grep f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09
f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09 RUNNING

After all the weird thing,
the following errors continue to come out:
Aug 17 20:16:00 containerd[2959773]: time="2024-08-17T20:16:00.504879132+08:00" level=error msg="ExecSync for \"f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09\" failed" error="failed to exec in container: failed to start exec \"44d18627e51386c9661f8f0253e6b63f4a7ea3f6dd5e812959c1567b1dcb50cd\": OCI runtime exec failed: exec failed: cannot exec in a stopped container: unknown"
Aug 17 20:16:00 containerd[2959773]: time="2024-08-17T20:16:00.505607821+08:00" level=debug msg="ExecSync for \"f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09\" with command [/bin/bash -c /home/xiaoju/disfv4-agent/control-internal alive] and timeout 1 (s)"
Aug 17 20:16:00 containerd[2959773]: time="2024-08-17T20:16:00.506365901+08:00" level=debug msg="Generated exec id \"25b8927f3cc4990588d601d86a9399103f23b7d17373be4f50abbe91cdc75297\" for container \"f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09\""
Aug 17 20:16:01 containerd[2959773]: time="2024-08-17T20:16:01.657220377+08:00" level=error msg="ExecSync for \"f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09\" failed" error="failed to exec in container: failed to start exec \"25b8927f3cc4990588d601d86a9399103f23b7d17373be4f50abbe91cdc75297\": OCI runtime exec failed: exec failed: cannot exec in a stopped container: unknown"

Aug 21 14:29:17 containerd[2959773]: time="2024-08-21T14:29:17.196732583+08:00" level=error msg="stat task f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09" error="cgroups: cgroup deleted: unknown"
Aug 21 14:29:20 time="2024-08-21T14:29:20.988352033+08:00" level=error msg="collecting metrics for f25340780aa0d6357b69c6bd67596533ec12310e92284bf9f7b946cfe1ef9c09" error="cgroups: cgroup deleted: unknown"

Steps to reproduce the issue
It is a random problem and we don't know if it could be reproduced.
Describe the results you received and expected
Containerd should successfully delete the container, and there are no "cgroups: cgroup deleted: unknown" err of this container.
What version of containerd are you using?
containerd github.com/containerd/containerd v1.6.33-9-g519d5ad51 519d5ad51018267a2f00829494e68f36d3bb0657
Any other relevant information
$ /usr/local/bin/runc -version
runc version 1.1.12
commit: v1.1.12-0-g51d5e946
spec: 1.0.2-dev
go: go1.22.5
libseccomp: 2.5.1

$ kubelet version
Version: v1.20.13

Show configuration if it is related to CRI plugin.
cat /etc/containerd/config.toml
 [plugins."io.containerd.grpc.v1.cri".containerd.default_runtime]
        base_runtime_spec = ""
        cni_conf_dir = ""
        cni_max_conf_num = 0
        container_annotations = []
        pod_annotations = []
        privileged_without_host_devices = false
        runtime_engine = ""
        runtime_path = ""
        runtime_root = ""
        runtime_type = ""

        [plugins."io.containerd.grpc.v1.cri".containerd.default_runtime.options]

      [plugins."io.containerd.grpc.v1.cri".containerd.runtimes]

        [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]
          base_runtime_spec = ""
          cni_conf_dir = ""
          cni_max_conf_num = 0
          container_annotations = []
          pod_annotations = []
          privileged_without_host_devices = false
          runtime_engine = ""
          runtime_path = ""
          runtime_root = ""
          runtime_type = "io.containerd.runc.v2"

          [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]
            BinaryName = "/usr/local/bin/runc"
            CriuImagePath = ""
            CriuPath = ""
            CriuWorkPath = ""
            IoGid = 0
            IoUid = 0
            NoNewKeyring = false
            NoPivotRoot = false
            Root = ""
            ShimCgroup = ""
            SystemdCgroup = false

      [plugins."io.containerd.grpc.v1.cri".containerd.untrusted_workload_runtime]
        base_runtime_spec = ""
        cni_conf_dir = ""
        cni_max_conf_num = 0
        container_annotations = []
        pod_annotations = []
        privileged_without_host_devices = false
        runtime_engine = ""
        runtime_path = ""
        runtime_root = ""
        runtime_type = ""

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

https://github.com/awslabs/amazon-eks-ami/issues/1933

This sounds like the same issue as reported in https://github.com/containerd/containerd/issues/10589 (with a repro in https://github.com/containerd/containerd/pull/10649) and we have a fix in https://github.com/containerd/containerd/pull/10651.

https://github.com/containerd/containerd/releases/tag/v1.7.22 and https://github.com/containerd/containerd/releases/tag/v1.6.36 contain the fix for this issue.

thanks for the hard work @samuelkarp and @laurazard

Hi @samuelkarp I see you mentioned this issue is also fixed in v1.6.36. Do you know from which containerd version in 1.6.x that starts to have the issue? Thanks!


Does not work - authentication issue

Error says that the service principal does not have access to my WebApp, however I have added it to the IAM with owner permissions.
Erro text below:
{"error":{"code":"AuthenticationFailed","message":"The Azure AD object '' does not have permissions to perform action 'Microsoft.Insights/Metrics/write' over scope '/subscriptions//resourceGroups/testetokio/providers/Microsoft.Web/sites/teste'. "}}

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

ID: 78411727-ea56-aef5-4f04-b016c25afba9
Version Independent ID: 8687b7bc-a196-6fd0-fa57-9fa5dd2d4545
Content: Send custom metrics for an Azure resource to the Azure Monitor metric store by using a REST API
Content Source: articles/monitoring-and-diagnostics/metrics-store-custom-rest-api.md
Service: azure-monitor
GitHub Login: @anirudhcavale
Microsoft Alias: ancav

@henriquebrisola can you verify for me that your service principal has "Monitoring Metrics Publisher" role permissions? The Owner role of a resource doesn't automatically carry this permission. So it must also be explicitly added to the metric publisher role.

thanks, that worked!


Hydra Mesh MIR produces strange results

I was working with a user to understand discrepancies between two meshes created with HYDRA which are supposed to be the same. We made material volume fraction expressions to explore where the materials were and we noticed behavior that is mystifying.
Below is an image of the plot of the volume fractions for material 4 on the first mesh, which looks as we expect:

The second mesh contains the first mesh but extends further in the negative and positive x directions. If we use the clip operator to only see the portion of the second mesh that is supposed to be the same as the first mesh, we see what we would expect, minus the sides of the box, which disappear because of the way clip functions. This is the image on the left.

The image on the right is the same mesh and the same variable, but instead of using clip to get the part of the mesh that we want, we use subset selection to get only the 4th and 5th materials, which are only used in this section of the mesh. What we see is completely different even though the spatial extents are the same.
Data is on the CZ in the following tar file: /usr/workspace/visit/bug_data/visit_bug_19943.tar.xz
Run VisIt with the script repro1.py to get the first image, run with repro2.py to get the second image.
This issue was with VisIt 3.4.1 and 3.3.3.

Notify Jose Milovich when this issue is resolved.

matvf should not become meaningless once MIR has taken place. It should produce a field of 0s and 1s.

Or honestly, any zonal variable that is not material dependent ought to look exactly the same before and after MIR.

Do intensive vs. extensive variables play any role in this?

I'm guessing you're asking about material-dependent fields. They do play a role.
There are two things to figure out here:

why is matvf completely broken after MIR/how can we fix it
the HYDRA variable ireg similarly looks super wrong after MIR. Why is this the case?

Sorry to be terse, I mean this kind of thing.

Sorry, so then what exactly do you mean? Are you talking about volume dependent and/or material-dependent variables?


Introduce golangci-lint

Is your feature request related to a problem? Please describe.
I do not see any lint for this, enable lint makes project better I think.
Describe the solution you'd like
Introduce golangci-lint.
I have done at local, If possible, I will post it.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Hello @daixiang0,
There is already make lint in this project. Also the golangci-lint is run when pushing a commit by this Github Workflow: https://github.com/dapr/go-sdk/blob/main/.github/workflows/test-on-push.yaml#L41
Do you need anything else? Maybe we can update this to [push, pull_request] instead. But a PR from a fork doesn't trigger the Workflow by default anyway.
Best if people just remember to manually run make lint.

Yep, I think we should add it to CI in pr, we have little push event right?


Wallet: add default toast

Fix toasts (the provider was accidentally reverted)
Add check in header for not staking
Allow toast to render a default value

Just gonna pull these changes into feature/block-rewards


Failed to create blob containers

Storage Explorer Version: 1.14.2
Build Number: 20200715.2
Platform/OS:  Windows 10
Architecture:  x64
Regression From:  First time to use
Bug Description
Failed to create blob container.
Zscaler makes the internet safe for businesses by protecting their employees from malware, viruses, and other security threats
Steps to Reproduce

Launch Azurite via command line: azurite --silent --location c:\azurite --debug c:\azurite\debug.log
Launch Azure Storage Explorer
Create container on emulater.

Expected Experience
A document images container is expected to create.
Actual Experience
Popup an error, says failed to create blob container.

@lhf552004 do you have proxy settings enabled? If you don't then, can you check your Windows environment variable setting and see if you have a environment variable/s called HTTP_PROXY or HTTPS_PROXY?

Closing due to lack of response. Please open a new issue if you are still having problems.

Hi @MRayermannMSFT, yes it works! thank you. sorry delay to response.

Hi @MRayermannMSFT, yes it works! thank you. sorry delay to response.


SSL on npm admin page won‘t let me login (with access list)

I configured my nginx with a valid ssl cert to access the npm web interface (<IP_ADDRESS>:81). Cert is valid and I can see the login page when I open https://nginx.domain.com
But I am not able to login. I can enter my credentials but the admin page will not be shown. Instead I always see the blank login fields.
Logging in without access profile works perfectly with and without ssl.
What am I missing here?

Duplicate of https://github.com/jc21/nginx-proxy-manager/issues/334


Cancel process instance

There should be a button for in the process instance editor
"Remove" action in the process instances browser should probably also cancel the process first.

Original issue: https://youtrack.haulmont.com/issue/PL-10505

Git changesets by gorbunkov:
902f5422 in master - Cancel process instance from ProcInstanceEditor #28

Git changesets by gorbunkov:
437db117 in release_6_9 - Cancel process instance from ProcInstanceEditor #28


Invoke-BoltTask -Params returns json in different order than given

Describe the Bug
When using a powershell hash as a value for the params parameter in invoke-bolttask, the order of the json hash given back is different.
https://github.com/puppetlabs/bolt/pull/2147/checks?check_run_id=1057739739
Starting discovery in 2 files.
Discovery finished in 3.74s.
[+] D:\a\bolt\bolt\pwsh_module\autogenerated.tests.ps1 20.99s (6.56s|10.85s)
WARNING: The module manifest member 'ModuleToProcess' has been deprecated. Use the 'RootModule' member instead.
WARNING: this works but order is not same
WARNING: this works but order is not same
WARNING: this works but is not 100%
WARNING: requires params to not be positionl...is that a problem
WARNING: requires params to not be positionl...is that a problem
WARNING: Verify this
[-] test all bolt command examples.bolt task.bolt task run package --targets target1,target2 action=status name=bash 91ms (88ms|3ms)
 Expected strings to be the same, but they were different.
 String lengths are both 96.
 Strings differ at index 64.
 Expected: '...s '{"name"...'
 But was:  '...s '{"actio...'
 at $results | Should -Be "bolt task run 'package' --targets 'target1,target2' --params '{`"name`":`"bash`",`"action`":`"status`"}'", D:\a\bolt\bolt\pwsh_module\command.tests.ps1:267
 at <ScriptBlock>, D:\a\bolt\bolt\pwsh_module\command.tests.ps1:267
Tests completed in 23.21s
Tests Passed: 1112, Failed: 1, Skipped: 0 NotRun: 0
##[error]Process completed with exit code 1.

Expected Behavior
Invoke-BoltTask should return the json version of the powershell hash in the original order given
Steps to Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'

Environment

Version [e.g. 1.27.0]
Platform [e.g. Ubuntu 18.04]

Additional Context
Add any other context about the problem here.

This stems from the ConvertTo-JSON cmdlet behaving differently across PowerShell versions. Both 5.1 and 7.1 respect the order given, 7.0 does not. I haven't tested 6.2, but that is EOL on 9/4/2020 so I don't think it's a worry.
PS > $PSVersionTable.PSVersion
Major  Minor  Build  Revision
-----  -----  -----  --------
5      1      19041  1
PS > @{ name = 'spooler'; action = 'status' } | ConvertTo-Json -Compress
{"name":"spooler","action":"status"}

PS > $PSVersionTable.PSVersion
Major  Minor  Patch  PreReleaseLabel BuildLabel
-----  -----  -----  --------------- ----------
7      0      3
PS > @{ name = 'spooler'; action = 'status' } | ConvertTo-Json -Compress
{"action":"status","name":"spooler"}

PS > $PSVersionTable.PSVersion
Major  Minor  Patch  PreReleaseLabel BuildLabel
-----  -----  -----  --------------- ----------
7      1      0      preview.6
PS > @{ name = 'spooler'; action = 'status' } | ConvertTo-Json -Compress
{"name":"spooler","action":"status"}


Certificate exposed at LOCALSANDBOX_CERT_RETRIEVAL_URL expired

Seems the server is using the certificate exposed at LOCALSANDBOX_CERT_RETRIEVAL_URL. It has expired since December 13, 2024.
Executing azl command inside the container fails with
azl servicebus queue create --name default --namespace-name default --resource-group default
HTTPSConnectionPool(host='localhost.localsandbox.sh', port=7329): Max retries exceeded with url: /azure/default/v2.0/.well-known/openid-configuration (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1147)')))
Certificate verification failed. This typically happens when using Azure CLI behind a proxy that intercepts traffic with a self-signed certificate. Please add this certificate to the trusted CA bundle. More info: https://docs.microsoft.com/cli/azure/use-cli-effectively#work-behind-a-proxy.

@mxsdev could you please publish a new docker image with a new certificate? It's breaking my automated tests ;)


Fix JSONB encoding

Missing https://github.com/MagicStack/py-pgproto/blob/e7f1a02cd1530312f83b8069037f13e858816e4b/codecs/json.pyx#LL19C22-L19C22
Integrating this into the codebase may be challenging without making it special cased / hacky.

Fixed in #16


fix add project error and correct the wrong word

Purpose of this pull request

https://github.com/streamxhub/streamx/issues/1302#issue-1322905979

LGTM


Revert "update ace to 1.2.6"

This reverts commit 9cc8d06fe8e94777e51d85117ccc486504380e6b in order to undo the regression reported in https://github.com/rust-lang/rust-playpen/issues/262.
Should this close #262? If so, we should probably open another issue to track updating Ace without enabling auto-matching for single quotes.
r? @alexcrichton

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.


use sequencer-relayer

what I added:

reads and parses SequencerBlocks from celestia, gets the namespace-specific txs we want (set by chain-id at startup, defaults to ethereum for now to match what's in geth)
parses the cosmos txs into their generic data field and sends those to do_block
added a super basic Header type that's also passed to do_block, right now just contains the sequencer block hash, we will probs want to edit this + add protos for it
updated error handling to handle errors coming from the spawned JoinHandles, I was dealing with channel closed errors without proper error logs before. we might want to refactor a bit to deal with those better


Does not work with React Slick if Fade is enabled

I'm mostly leaving this here for anyone who is having trouble with slick integration. RIM doesn't work if you have the fade option set to true on React Slick.

Yes it doesn't work with when fade equals to true


Fix incorrect inference in bulk::sum and bulk::product

In the overloads of bulk::sum and bulk::product taking world references, this PR fixes std::accumulate specializing to int regardless of the argument types and adds a few tests.
This implementation requires that 1 can be cast to T in bulk::product, which can be fixed (we can reduce without a unit element), but I noticed this is also already the case for the other product overload.

Great, thanks!
If you want, you can add yourself to the 'also thanks to' section of the README :)

Thank you for the quick response and the library itself! If I have another PR I will add myself to the "also thanks to" section :wink:

Thanks again! And please do 👍


Is this allowed, two different type of files in single rule?

Like this?
 "lint-staged": {
    ".*rc", "*.json": [
      "prettier --write --parser json",
      "git add"
    ]
  }

I have seen this example in the readme but my use case is different.
{
  "*.{js,jsx}": ["prettier --parser flow --write", "git add"]
}

No, this isn't valid JSON. Why not make it like in second example?

I want to use the same rule for my .stylelintrc, .eslintrc and any *.json file

This is what I use on my projects:
{
  "*{rc,.json}": "jsonlint"
}


Update using-a-component-inf-file.md

Rectifying vocabulary to express that you don't -necessarily- need a function driver (as opposed to no function driver allowed at all).

@NabilFates,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Footer_Fixed

issue no:#559
Close #559
Video/Screenshots (mandatory)
https://github.com/apu52/Travel_Website/assets/93792490/ee9425c1-3631-4c19-98a8-8386b36be2b6

The FAQ and Terms & Conditions links are now vertically aligned. Additionally, all elements in the footer have same hover effect and Event the contact us link is responsive and redirect the page to the contact us page
Are you contributing under any Open-source programme?
GSSOC24

@apu52  I've made the requested changes and all checks have passed. Please review my code now
Thank you!!

Also please assign this issue the label of GSSOC 2024


Migrate to tokio 1.x

Since the kernels supporting only this interface and not gpio-cdev will continue with us "forever", it would be great to give this crate a revamp and migrate it to tokio 1.x.
However, I do not have the know-how to do this.
Could somebody help us here?
Maybe @benjumanji, @oll3 or somebody else?
Over at gpio-cdev is an example of the migration: https://github.com/rust-embedded/gpio-cdev/pull/55

Hi @eldruin ! Took a stab at it in #69 since looked similar to the gpio-cdev tokio bump :crab:

Awesome @oll3! thank you!

Fixed in #69. Thank you!


Using Multi Statement Files with MySQL & LoadFile

FIXME: this does not really work with multi-statement files for mattn/go-sqlite3 or the go-mysql-driver/mysql drivers; pq seems to be an exception here. Detecting this by requiring something with DriverName() and then attempting to split the queries will be difficult to get right, and its current driver-specific behavior is deemed at least not complex in its incorrectness.
I'm using the go-mysql-driver and having this functionality work would really facilitate unit testing. Is this a sqlx issue or a driver related issue?

Use multiStatements = true connection parameter for go-mysql-driver


Feature/simple noise simulator

Types of PR

[x] New Features
[ ] Upgrade of existing features
[ ] Bugfix

Link to the issue
Description
How to review this PR.
Others

@hakuturu583 @yamacir-kit
I am in the process of implementing a noise generator, but I would appreciate it if you could confirm that I am going in the right direction.


debugger loses changes when switching between coders

If you edit a method in a debugger coder and switch to another frame and back, the debugger reverts the changed source:
https://github.com/feenkcom/gtoolkit/assets/16563825/a6465d72-88bd-43b3-9a46-8e8eb7e6c69d

https://github.com/feenkcom/gtoolkit/assets/16563825/cb0169f0-4ed1-4f4f-8fe2-097c784f1c00


Bump versions and change error to failure

I'm going to assume this is no longer relevant since it's three years old.


fixed misleading message

when training RF instead of maximum offset value minimum was shown instead

a small fixed of confusing message.
@YoshikiOhtani  I will merge it tomorrow

Thanks @jsitarek, I did miss that. Let me merge it now to the master.


CI: drop Go 1.20

1.20 has already reached EOL

Should we also update 1.20 to 1.21 in website/go.mod?

The new go toolchain has some crazy auto-updating feature, if you bump go.mod

Should we also update 1.20 to 1.21 in website/go.mod?

I don't know how to update that file.
go mod tidy erases all the modules in the file.

I don't know how to update that file. go mod tidy erases all the modules in the file.

It seems go.mod is not used in website directory, so it can be removed.


koord-manager: use GenerationChangedPredicate to prevent unnessary repeated reconcile calls

Ⅰ. Describe what this PR does
This predicate will skip update events that have no change in the object's metadata.generation field. The metadata.generation field of an object is incremented by the API server when writes are made to the spec field of an object. This allows a controller to ignore update events where the spec is unchanged, and only the metadata and/or status fields are changed.

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[ ] I have written necessary docs and comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in make test

/lgtm

/lgtm
/approve


Propagate Event does not work.

When using let tg = new tourguide.TourGuideClient({autoScroll: false, propagateEvents: true, closeButton: false, exitOnClickOutside: false, exitOnEscape:false})
The content inside is still not clickable.

The code tries to get the propagateEvents option from the step's configuration, but this is an option on the tour's configuration.
Still, I have tried setting up propagate-events manually to none and the event is not propagated.


added techsweep overview .pdf for NMOST and PMOST

Sometimes I like to have an overview of the NMOST / PMOST gm/ID characteristics to quickly recap all the trade-offs.

@simi1505 Thank you, that is a good idea and useful to have! One question: How can we regenerate the PDFs when we update the underlying data, e.g., due to a model change? Thus, it would be great to e.g., provide a Jupyter NB or other mechanism (LaTeX?) to create these PDFs.


Can't build with yarn2

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
When I run yarn start I get:
Failed to compile.

./.yarn/cache/jss-plugin-rule-value-function-npm-10.1.1-f63c97f8af-2.zip/node_modules/jss-plugin-rule-value-function/dist/jss-plugin-rule-value-function.esm.js
Module not found: jss-plugin-rule-value-function tried to access tiny-warning, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.

Expected Behavior 🤔

Steps to Reproduce 🕹

Steps:

mkdir test
cd test
yarn set version berry
yarn dlx create-react-app my-app --template typescript
cd my-app
yarn add @material-ui/core
add a simple <Button>Test</Button> to App.tsx (with import Button from '@material-ui/core/Button';)
yarn start

Context 🔦
I'm trying to use yarn2 to get that sweet zero-Installs feature.

Your Environment 🌎
OS: NixOS unstable

Tech
Version

Material-UI
v4.9.12

React
16.13.1

Browser
Firefox

TypeScript
3.7.2

yarn
2.0.0-rc.32

tsconfig.json
{
  "compilerOptions": {
    "target": "es5",
    "lib": [
      "dom",
      "dom.iterable",
      "esnext"
    ],
    "allowJs": true,
    "skipLibCheck": true,
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "noEmit": true,
    "jsx": "react"
  },
  "include": [
    "src"
  ]
}

@bbigras Please open the issue in JSS, It's an issue on their end. Also, I would be in favor of dropping the dependency on tiny-warning.

Requires the release of https://github.com/cssinjs/jss/pull/1315

I am getting a similar issue on v4.9.12 when react and react-dom are added as a peer dependency in my app (moving them to a normal dependency made the issue disappear):
./.yarn/$$virtual/@material-ui-core-virtual-613969f2c4/0/cache/<EMAIL_ADDRESS>Module not found: @material-ui/core tried to access react (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

I tried applying a resolution within Yarn, but doesn't  seem to access sub-directory for the jss-package.
"resolutions": {
  "jss-plugin-rule-value-function": "https://github.com/cssinjs/jss.git#3f35178786018136d944a6fddff08e4c74d06fd1"
}

Might just have to make a local tarball 🤷

If you want to be notified when this issue is fixed watch https://github.com/cssinjs/jss for releases (click "watch" and then "releases only"). More specifically, watch for the next release of jss-plugin-rule-value-function.

JSS v10.2.0 was released, problem solved.


onLimitReached , or running custom code

Description
In v1.5.0 we used onLimitReached to log and record metrics of our limiting. onLimitReached is no more, as its not in express-rate-limit, however in express-rate-limit we can use a handler to perform those actions. As described in your readme.md, handler is not supported in slow-down. Is there an alternative way to run custom code, or are there plans to?
Why
Logging and metrics
Alternatives
Giving up on logging and recording these events

Oof, I'm sorry, I didn't think about that.
Here's a couple of options that are both a little dumb, but might be good enough:

Add a custom middleware that runs after express-slow-down and checks req.slowDown:
app.use(slowDown({
    // ...
}));
app.use((req, res, next) => {
    if (request.slowDown.current === request.slowDown.limit + 1) {
        // onLimitReached code here
    }
    next();
}));

The gotcha with this approach is that it now fires after the delay, whereas onLimitReached fired before the delay. That might be acceptable for logging purposes, though.

Drop express-slow-down, and instead use express-rate-limit with a custom handler as shown in the docs. However, make the custom handler slow down responses instead of blocking them:
app.use(rateLimit({
    // ...
    max: 1, // previous delayAfter value here
    handler: (request, response, next, options) => {
        if (request.rateLimit.used === request.rateLimit.limit + 1) {
            // onLimitReached code here
        }
        const delay = (request.used - request.limit) * 1000
        const timerId = setTimeout(next, delay)
        response.on('close', () => clearTimeout(timerId))
    },
})

(Basically recreate a simpler version of express-slow-down v2.0.0.)

thanks, made do with a variation based on 1. Found a bug see https://github.com/express-rate-limit/express-slow-down/issues/46.

There's not a plan at the moment, but I won't swear it off entirely.
onLimitReached was removed because it led to a lot of confusion and, as I mentioned above, there are ways of achieving a similar result without it.
I considered trying to add an event-based system to replace it, but haven't found something I'm really happy with yet.


How do you know a blob connection has been properly established?

Consider this little snippet:
    blob_service_client = BlobServiceClient.from_connection_string(
        config.get("AZURE_BLOB_CONNECTION_STRING")
    )
    blob_service_client.get_service_properties()

Let's say AZURE_BLOB_CONNECTION_STRING env var is pointing out locally to azurite but I don't have azurite up and running, this code would obviously lead to raise
azure.core.exceptions.ServiceRequestError: <urllib3.connection.HTTPConnection object at 0x0647CE98>: Failed to establish a new connection: [WinError 10061] No connection could be made because the target machine actively refused it

Which it's good, problem being it's that's taking quite a while to do so... So my question, is there any way to reduce the timeout for this specific request? And if there isn't, what'd the best way to check if the blob_service_client can connect with the server without waiting so much?
Thanks!

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Azure.Core:0.42908558,Storage:0.29378223,Service Bus:0.15017255'

Hi @brupelo Bruno, the delay in this error being shown is likely because of the automatic retry policy that the SDK has in place. This type of an error is a retriable error and therefore the retry policy will attempt the request a few times with some time in between each.
The default configuration for the retry policy results in usually around 90 seconds before any error would be shown due to a base delay of 15 seconds and exponential backoff. We are aware this is probably not the correct configuration and will probably be updating this to be much faster in an upcoming release but luckily, it's also configurable today. Some of this configuration can be found in the README; specifically, settings around retry count.
If you want to see the error immediately you can disable retries by setting retry_total=0 on your call to from_connection_string. Or you could set it to just 1 to still have retry but cut down on the wait time.
Additionally, you could configure the timing between retries be replacing the entire retry policy with one of your own. For example, you could construct your own instance of ExponentialRetry (our default retry policy) with different timing values like this:
from azure.storage.blob import BlobServiceClient, ExponentialRetry

# Create a retry policy with much faster timing
faster_retry = ExponentialRetry(initial_backoff=1, increment_base=1)
blob_service_client = BlobServiceClient.from_connection_string('<Connection String>', retry_policy=faster_retry)

Hopefully that helps. Thanks

Closing this issue, please let me know if you have any more questions. Thanks.


Unable to Reproduce Example as Described in Documentation

Hi,
Thank you for the great plugin.
I cannot reproduce the example written in the official documentation.
Input:
{
  "analyzer": "sudachi_analyzer",
  "text": "寿司がおいしいね"
}

Expected (as described in the document):
{
  "tokens": [
    {
      "token": "寿司",
      "start_offset": 0,
      "end_offset": 2,
      "type": "word",
      "position": 0
    },
    {
      "token": "美味しい",
      "start_offset": 3,
      "end_offset": 7,
      "type": "word",
      "position": 2
    }
  ]
}

Actual (v3.1.0 release with Opensearch 2.6.0)
{
    "tokens": [
        {
            "end_offset": 2,
            "position": 0,
            "start_offset": 0,
            "token": "寿司",
            "type": "word"
        },
        {
            "end_offset": 3,
            "position": 1,
            "start_offset": 2,
            "token": "が",
            "type": "word"
        },
        {
            "end_offset": 7,
            "position": 2,
            "start_offset": 3,
            "token": "美味しい",
            "type": "word"
        }
    ]
}

If you think of any possible causes, please leave a comment. I appreciate your assistance.

I assume you applied the sudachi_part_of_speech setting in the README, but I could not reproduce your results here.
Please let us know your configuration file and the dictionaries you are using.

We are using the full dict and base configuration.
My apologies, the example provided is not quite accurate. I think the problem is actually related to a change in how baseform, readingform and normalizedform are being applied..
I tried to put together a reproducible, minimal example,
{
  "settings": {
    "index": {
      "analysis" : {
        "analyzer" : {
          "sudachi_analyzer" : {
            "filter" : [
              "sudachi_ja_stop",
              "sudachi_baseform"
            ],
            "type" : "custom",
            "tokenizer" : "sudachi_tokenizer"
          }
        },
        "tokenizer" : {
          "sudachi_tokenizer" : {
            "type" : "sudachi_tokenizer"
          }
        }
      }
    }
  }
}

If we analyze this text,
{
  "analyzer": "sudachi_analyzer",
  "text": "および"
}

I expect to get no tokens, because および is defined in stopwords.txt, and it should be removed in the sudachi_ja_stop filter. However, I still get one token,
{
  "tokens" : [
    {
      "token" : "および",
      "start_offset" : 0,
      "end_offset" : 3,
      "type" : "word",
      "position" : 0
    }
  ]
}

This is in v3.1.0 running on OpenSearch 2.6.0
I have confirm in our old version, v2.1.0 running on Elasticsearch 7.10.2, this expected behavior occurs (no tokens).
I see from the changelog, in v3.0.0, there was a change related to how analysis chains are processed. Is this a side-effect of that?

On further investigation, this is the exact same issue as #111


Update roadmap for 2021! 🛣

Changes
This commit updates the roadmap from the things we hope to do in 2020 to
the things we hope to do in 2021! (since we're already 2 months in, a
couple of these things have been completed already :D)

Draft 2021 pipelines roadmap
Reflections on the 2020
roadmap

/kind misc
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[n/a] Includes tests (if functionality changed/added)
[x] Includes docs (if user facing)
[x] Commit messages follow commit message best practices
[x] Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
NONE

looks great and very exciting year ahead 🎉
/lgtm

/lgtm
/meow


Countries and Their Acronym Aliases Showing Up As Separate Nodes

From https://github.com/someshkar/covid19india-cluster/issues/148

@rohanrmallya would you like to work on this? It seems like I've note been able to devote enough time to this right now.

I'm on it!
Thanks.
On Sun, 5 Apr, 2020, 2:00 pm Nirant<EMAIL_ADDRESS>wrote:

@rohanrmallya https://github.com/rohanrmallya would you like to work on
this? It seems like I've note been able to devote enough time to this right
now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NirantK/coronaIndia/issues/14#issuecomment-609379263,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMAZP373ZIFSRISLLBXDL3RLA6UDANCNFSM4LV4BAKQ
.

Thanks for looking into this! Assigned the issue to you

Thanks for looking into this! Assigned the issue to you

Hi, have raised a PR. #23
Forgot to update here.


Fix snprintf() error handling

Imagine 32-bit machine, p = (char *)0xfffffff0; limit = (char *)0xfffffff5;
p += snprintf(p, limit - p, "111111111111111111111111111111111111");
if (p < limit) {
// oops
}

Interesting... But I'm wondering that your concern may not exist in reality - don't need to worry about it at all. E.g. my desktop is x86_64 (although it's 64 bit platform, it still tells something) Ubuntu with 3.13.0-88-generic linux kernel.
$ cat /proc/$BASHPID/maps
00400000-004ef000 r-xp 00000000 fc:01 1704090                            /bin/bash
006ef000-006f0000 r--p 000ef000 fc:01 1704090                            /bin/bash
006f0000-006f9000 rw-p 000f0000 fc:01 1704090                            /bin/bash
006f9000-006ff000 rw-p 00000000 00:00 0
00760000-00c13000 rw-p 00000000 00:00 0                                  [heap]
7f3952873000-7f3952877000 r-xp 00000000 fc:01 2229452                    /usr/lib/libnss_cache.so.2.0
7f3952877000-7f3952a76000 ---p 00004000 fc:01 2229452                    /usr/lib/libnss_cache.so.2.0
7f3952a76000-7f3952a77000 r--p 00003000 fc:01 2229452                    /usr/lib/libnss_cache.so.2.0
7f3952a77000-7f3952a78000 rw-p 00004000 fc:01 2229452                    /usr/lib/libnss_cache.so.2.0
7f3952a78000-7f3952a82000 r-xp 00000000 fc:01 1974505                    /lib/x86_64-linux-gnu/libnss_files-2.19.so
7f3952a82000-7f3952c81000 ---p 0000a000 fc:01 1974505                    /lib/x86_64-linux-gnu/libnss_files-2.19.so
7f3952c81000-7f3952c82000 r--p 00009000 fc:01 1974505                    /lib/x86_64-linux-gnu/libnss_files-2.19.so
7f3952c82000-7f3952c83000 rw-p 0000a000 fc:01 1974505                    /lib/x86_64-linux-gnu/libnss_files-2.19.so
7f3952c83000-7f3953b03000 r--p 00000000 fc:01 656280                     /usr/lib/locale/locale-archive
7f3953b03000-7f3953cbd000 r-xp 00000000 fc:01 1974389                    /lib/x86_64-linux-gnu/libc-2.19.so
7f3953cbd000-7f3953ebd000 ---p 001ba000 fc:01 1974389                    /lib/x86_64-linux-gnu/libc-2.19.so
7f3953ebd000-7f3953ec1000 r--p 001ba000 fc:01 1974389                    /lib/x86_64-linux-gnu/libc-2.19.so
7f3953ec1000-7f3953ec3000 rw-p 001be000 fc:01 1974389                    /lib/x86_64-linux-gnu/libc-2.19.so
7f3953ec3000-7f3953ec8000 rw-p 00000000 00:00 0
7f3953ec8000-7f3953ecb000 r-xp 00000000 fc:01 1973483                    /lib/x86_64-linux-gnu/libdl-2.19.so
7f3953ecb000-7f39540ca000 ---p 00003000 fc:01 1973483                    /lib/x86_64-linux-gnu/libdl-2.19.so
7f39540ca000-7f39540cb000 r--p 00002000 fc:01 1973483                    /lib/x86_64-linux-gnu/libdl-2.19.so
7f39540cb000-7f39540cc000 rw-p 00003000 fc:01 1973483                    /lib/x86_64-linux-gnu/libdl-2.19.so
7f39540cc000-7f39540f1000 r-xp 00000000 fc:01 1966537                    /lib/x86_64-linux-gnu/libtinfo.so.5.9
7f39540f1000-7f39542f0000 ---p 00025000 fc:01 1966537                    /lib/x86_64-linux-gnu/libtinfo.so.5.9
7f39542f0000-7f39542f4000 r--p 00024000 fc:01 1966537                    /lib/x86_64-linux-gnu/libtinfo.so.5.9
7f39542f4000-7f39542f5000 rw-p 00028000 fc:01 1966537                    /lib/x86_64-linux-gnu/libtinfo.so.5.9
7f39542f5000-7f3954318000 r-xp 00000000 fc:01 1973904                    /lib/x86_64-linux-gnu/ld-2.19.so
7f39544f7000-7f39544fa000 rw-p 00000000 00:00 0
7f395450e000-7f3954515000 r--s 00000000 fc:01 531560                     /usr/lib/x86_64-linux-gnu/gconv/gconv-modules.cache
7f3954515000-7f3954517000 rw-p 00000000 00:00 0
7f3954517000-7f3954518000 r--p 00022000 fc:01 1973904                    /lib/x86_64-linux-gnu/ld-2.19.so
7f3954518000-7f3954519000 rw-p 00023000 fc:01 1973904                    /lib/x86_64-linux-gnu/ld-2.19.so
7f3954519000-7f395451a000 rw-p 00000000 00:00 0
7ffd0b2ee000-7ffd0b30f000 rw-p 00000000 00:00 0                          [stack]
7ffd0b324000-7ffd0b326000 r-xp 00000000 00:00 0                          [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]
As you could see that [stack] and [heap] memory area wouldn't expand into 0xffffffff ???????? area.
In fact usually we have a '1:3' kernel_space : user_space virtual memory space split, i.e.:
for 32-bit system,
0xc000 0000 - 0xffff ffff -> kernel space
0x0000 0000 - 0xbfff ffff -> user space
We might have some other split of kernel : user virtual memory space, but anyway user space address wouldn't be placed into the high memory area.
So I think you don't need to worry about this 'issue'.
FYI I found this article: http://duartes.org/gustavo/blog/post/anatomy-of-a-program-in-memory/

On 12.07.2016 08:44, jonnyhsy wrote:

Interesting... But I'm wondering that your concern may not exist in
reality - don't need to worry about it at all. E.g. my desktop is x86_64
(although it's 64 bit platform, it still tells something) Ubuntu with
3.13.0-88-generic linux kernel.

For current amd64 CPUs, they only has 48 bits of (virtual) address
space, so, indeed, this issue is not applicable to them.
Still, it may be applicable for 64-bit applications on different  CPUs
(including future amd64 cpus).
[cut]

In fact usually we have a '1:3' kernel_space : user_space virtual memory
space split, i.e.:
for 32-bit system,
0xc000 0000 - 0xffff ffff -> kernel space
0x0000 0000 - 0xbfff ffff -> user space

"x:y split" was only used with 32-bit kernels. 64-bit kernels don't use
this trick.
32-bit applications running on 64-bit kernel are free to use all 4G of
address space, nothing is reserved by kernel.
Even if it is not a practical issue for your CPU, OS and allocator, it
can quickly become practical issue with different CPU, OS and allocator.

We might have some other split of kernel : user virtual memory space,
but anyway user space address wouldn't be placed into the high memory area.

However, it does.

So I think you don't need to worry about this 'issue'.

FYI I found this article:
http://duartes.org/gustavo/blog/post/anatomy-of-a-program-in-memory/

Obsolete/outdated.
P.S.
You can prove that bug exists if it shows up in any test.
You cannot prove bug does not exist if it does NOT show up in your
particular test scenario.

We reworked the POSIX logger, I don't think the concerns in this PR apply any longer. Sorry we couldn't get to it sooner!


Some links to desktop app miss the /desktop

Some links to desktop app miss the /desktop and only show the link to the main website

Verified this issue on keeper app v 1.2.20(419)


refactor(container-definitions): Add LoaderHeader enum value to override logger

The LoaderHeader enum in the container-runtime library has a new enum value, baseLogger, which is a header that can be used to override the base logger used by a Fluid Container on load. This is a breaking change because TypeScript enums are not compatible when new enum values are added.
BREAKING CHANGE: This is a breaking change because TypeScript enums are not compatible when new enum values are added.
Fixes AB#3350

Closing since we are reverting the related changes. See #14216.


Setting up the Technical GitHub Actions IAM User

What can we improve?
Hi,
I want to enable/automate the deployment of the project to my personal AWS account. In the appendix you mention to create an IAM user for this but not how to achieve this.
I am facing the following problems:

AWS does not allow to add more than 10 policies to a user or group. Could you explain how you did this?
The following policies listed in the appendix are not group policies managed by AWS[^1] and can't be found neither when I try to attach them via a CloudFormation stack I wrote to create this user nor via the AWS console:

AmazonEC2ContainerServiceFullAccess
Permissive_CloudFormation_permissions
Manage_Cognito_user_pools

Any help appreciated! 🙏
[^1]: I obtained the list of AWS managed policies with aws iam list-policies | jq -r '.Policies[] | .PolicyName'
Version
Revision 1.9 (2022-10-04)
Suggested Changes
Please give some explanation on how to create this IAM user, either by providing a CloudFormation stack (YAML/JSON file or in code using CDK) or with a short step by step guide for the AWS console.

Thanks for the feedback! Could you please try and use these AWS-managed policies instead?

AmazonEC2FullAccess
AmazonECS_FullAccess
AWSLambda_FullAccess
AWSCloudFormationFullAccess
AmazonCognitoPowerUser

The AWS-managed AmazonEC2ContainerServiceFullAccess policy has been phased out (see https://docs.aws.amazon.com/AmazonECS/latest/developerguide/security-iam-awsmanpol-amazonecs-full-access-migration.html )
Both Permissive_CloudFormation_permissions and Manage_Cognito_user_pools are custom policies we've set up ourselves (and hence won't work out of the box; so, thanks again for notifying us about this issue). The default AWS policies mentioned above are somewhat more permissive in that they allow actions which are probably not required by our setup, but they're easier to get started with than by setting up those customer policies in the IAM console individually.
I know this runs against the principle of least privilege. Hence, we'll consider describing these more restrictive permission sets in a future edition of the ebook. Anyway, the next minor release of the ebook will contain a modified list of policies including the ones mentioned above.

Thank you so much for the fast response. 💚 🚀
It works now. 👍

Moin,
I just wanted to give you additional feedback on this. Today I tried to push images to my private ECR repository and got An error occurred (AccessDeniedException) when calling the GetAuthorizationToken operation: User: arn:aws:iam::***:user/github is not authorized to perform: ecr:GetAuthorizationToken on resource: * because no identity-based policy allows the ecr:GetAuthorizationToken action.
After some google-foo I found an example on Accessing One Amazon ECR Repository which I then applied to the CF stack for my GitHub user. I'm not sure if those right are too broad but it made the login and pushing images to the private ECR repository finally possible.
Maybe you want to add this to the next minor release of the ebook too. 👍
    val managedGroupPolicies = listOf(
        "AmazonEC2FullAccess",
        "AmazonECS_FullAccess",
        "AmazonCognitoPowerUser",
        "AWSCloudFormationFullAccess",
        "AWSLambda_FullAccess",
    ).map { ManagedPolicy.fromAwsManagedPolicyName(it) }

    val gitHubActionsGroup = Group(
        gitHubActionsStack,
        "GitHubActionsGroup",
        GroupProps.builder()
            .groupName(gitHubActionsGroupName)
            .managedPolicies(managedGroupPolicies)
            .build()
    ).also {
        it.addToPolicy(
            PolicyStatement.Builder.create()
                .sid("GetAuthorizationToken")
                .effect(Effect.ALLOW)
                .actions(listOf("ecr:GetAuthorizationToken"))
                .resources(listOf("*"))
                .build()
        )
        it.addToPolicy(
            PolicyStatement.Builder.create()
                .sid("ListImagesInRepository")
                .effect(Effect.ALLOW)
                .actions(listOf("ecr:ListImages"))
                .resources(listOf("*"))
                .build()
        )
        it.addToPolicy(
            PolicyStatement.Builder.create()
                .sid("ManageRepositoryContents")
                .effect(Effect.ALLOW)
                .actions(
                    listOf(
                        "ecr:BatchCheckLayerAvailability",
                        "ecr:GetDownloadUrlForLayer",
                        "ecr:GetRepositoryPolicy",
                        "ecr:DescribeRepositories",
                        "ecr:ListImages",
                        "ecr:DescribeImages",
                        "ecr:BatchGetImage",
                        "ecr:InitiateLayerUpload",
                        "ecr:UploadLayerPart",
                        "ecr:CompleteLayerUpload",
                        "ecr:PutImage",
                    )
                )
                .resources(listOf("*"))
                .build()
        )
    }

    val gitHubActionsUser = User(
        gitHubActionsStack,
        "GitHubActionsUser",
        UserProps.builder()
            .userName(gitHubActionsUserName)
            .managedPolicies(managedGroupPolicies)
            .groups(listOf(gitHubActionsGroup))
            .build()
    )

Thanks for the additional feedback! The ecr:GetAuthorizationToken permissions is part of the AmazonEC2ContainerRegistryFullAccess policy, which I didn't mention in my comment (but which is listed in the appendix of the ebook).


What is the license for this repository?

Hello. Thank you for your great work.
What is the license for this repository?
MIT? Apache2.0? GPL3? other?

Hi, thank you for the interest in our work. The license has been added to the repository.

Thank you for your confirmation.


Update DynamicVestingEscrow.sol

Tokens such as USDT will fail with normal .transfer, you need safeTransfer
Immutables are great! :)

@boringcrypto Just want to make sure if all popular ERC20 tokens have safeTransfer?


Added some websites

What kind of change does this PR introduce?

[ ] Bug Fix
[ ] Documentation change
[x] Added a new website
[ ] Other(s)

Why was this change needed?

Other information

Please make the necessary adjustment