Too many warn & error messages in Argo Workflow Controller (msg="error in entry template execution" error="Deadline exceeded")

Summary
Too many warning and error messages inside Argo workflow controllers
Argo workflow controller logs
$ kubectl logs --tail=20 workflow-controller-cb99d68cf-znssr
time="2020-09-16T13:46:45Z" level=error msg="error in entry template execution" error="Deadline exceeded" namespace=argo workflow=internal-data-ingestionczpht
time="2020-09-16T13:46:45Z" level=warning msg="Deadline exceeded" namespace=argo workflow=internal-data-ingestioncbmt6
time="2020-09-16T13:46:45Z" level=error msg="error in entry template execution" error="Deadline exceeded" namespace=argo workflow=internal-data-ingestioncbmt6
time="2020-09-16T13:46:46Z" level=warning msg="Deadline exceeded" namespace=argo workflow=internal-data-ingestionvz4km
time="2020-09-16T13:46:46Z" level=error msg="error in entry template execution" error="Deadline exceeded" namespace=argo workflow=internal-data-ingestionvz4km
time="2020-09-16T13:46:46Z" level=warning msg="Deadline exceeded" namespace=argo workflow=internal-data-ingestionhvnhs
time="2020-09-16T13:46:46Z" level=error msg="error in entry template execution" error="Deadline exceeded" namespace=argo workflow=internal-data-ingestionhvnhs
time="2020-09-16T13:46:46Z" level=warning msg="Deadline exceeded" namespace=argo workflow=internal-data-ingestionnnsbb
time="2020-09-16T13:46:46Z" level=error msg="error in entry template execution" error="Deadline exceeded" namespace=argo workflow=internal-data-ingestionnnsbb
time="2020-09-16T13:46:46Z" level=warning msg="Deadline exceeded" namespace=argo workflow=internal-data-ingestionkc5sb
time="2020-09-16T13:46:46Z" level=error msg="error in entry template execution" error="Deadline exceeded" namespace=argo workflow=internal-data-ingestionkc5sb
time="2020-09-16T13:46:46Z" level=warning msg="Deadline exceeded" namespace=argo workflow=internal-data-ingestionc9fcz
time="2020-09-16T13:46:46Z" level=error msg="error in entry template execution" error="Deadline exceeded" namespace=argo workflow=internal-data-ingestionc9fcz
time="2020-09-16T13:46:46Z" level=warning msg="Deadline exceeded" namespace=argo workflow=internal-data-ingestionpjczx
time="2020-09-16T13:46:46Z" level=error msg="error in entry template execution" error="Deadline exceeded" namespace=argo workflow=internal-data-ingestionpjczx
time="2020-09-16T13:46:46Z" level=warning msg="Deadline exceeded" namespace=argo workflow=internal-data-ingestionftmdh
time="2020-09-16T13:46:46Z" level=error msg="error in entry template execution" error="Deadline exceeded" namespace=argo workflow=internal-data-ingestionftmdh
time="2020-09-16T13:46:46Z" level=warning msg="Deadline exceeded" namespace=argo workflow=internal-data-ingestionbfrc5
time="2020-09-16T13:46:46Z" level=error msg="error in entry template execution" error="Deadline exceeded" namespace=argo workflow=internal-data-ingestionbfrc5

Workflows are getting stuck after some time and not completing in 12+ hours while normal execution is around 1 minute.
I am creating almost 1000 workflows with each workflow containing 4 Pods in short span of time. There are enough worker nodes to do processing so no issues as such from K8s cluster side.
internal-data-ingestiontj79x error in entry template execution: Deadline exceeded github.com/argoproj/argo/errors.New  /go/src/github.com/argoproj/argo/errors/errors.go:49 github.com/argoproj/argo/workflow/controller.init  /go/src/github.com/argoproj/argo/workflow/controller/operator.go:102 runtime.doInit  /usr/local/go/src/runtime/proc.go:5222 runtime.doInit  /usr/local/go/src/runtime/proc.go:5217 runtime.main  /usr/local/go/src/runtime/proc.go:190 runtime.goexit  /usr/local/go/src/runtime/asm_amd64.s:1357
--

Diagnostics
What version of Argo Workflows are you running?
Argo v2.10.1

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Deadline exceeded message as expected for each workflow which takes more than 10 seconds for one-time processing.
The message was printing for each workflow.

Do you have withparam or FromValue in your workflow?

Maybe fixed by #3905.
Does the workflow have a DAG with 1000s of items?

@sarabala1979  Yes we have withparam in our workflows.
I didn't understand what is meaning of 10 secs of one-time processing ?
Does this over all workflow execution time or any individual step/pod execution or something else ?
Expected means should I ignore these warns & error messages ?
@alexec  No, the workflow do not a DAG with 1000s of items. However it has DAGs with about 8 items.
And  there are 500+ workflows are running concurrently.
Still you suspect, it is related to fix #3905  ?

When deadline is exceeded it maybe possible for workflow to get corrupted, so the reconciliation aborts. Reconciliation is allowed 10s and can take longer if, for example:

Kubernetes API request are taking a long time - e.g. due to a lot of work happening.
There are many Kubernetes API being made- e.g. because the DAG is large.

As you are running many workflows, it is probably flooding the Kubernetes API. Have you tried limiting work in progress this, e.g. using parallelism or semaphores.
We are working on various improvements in v2.11 and v2.12 to support large scale.

@alexec  Yes I can see that Kubernetes API request are taking a long time during my large workload execution.
After using parallelism  it solves the problem but we loose scaling & concurrent execution of workflows while sufficient worker nodes are available to do processing.
Should I ignore these warn & error log messages ?
What kind of improvements you are trying to do to support large scale ?

I would upgrade to v2.11.0 and try with that version. I'm not sure we will have fully fixed this problem until v2.12 mind you.

@alexec  After upgrading to v2.11.0 also I can see these warnings and errors
time="2020-09-21T07:09:52Z" level=error msg="error in entry template execution" error="Deadline exceeded" namespace=argo workflow=internal-data-ingestion5z894
time="2020-09-21T07:10:03Z" level=warning msg="Deadline exceeded" namespace=argo workflow=internal-data-ingestion9p7qr
time="2020-09-21T07:10:03Z" level=warning msg="Deadline exceeded" namespace=argo workflow=internal-data-ingestionbrpb8
time="2020-09-21T07:10:03Z" level=error msg="error in entry template execution" error="Deadline exceeded" namespace=argo workflow=internal-data-ingestionbrpb8
time="2020-09-21T07:10:03Z" level=warning msg="Deadline exceeded" namespace=argo workflow=internal-data-ingestionckccs
time="2020-09-21T07:10:03Z" level=error msg="error in entry template execution" error="Deadline exceeded" namespace=argo workflow=internal-data-ingestionckccs
time="2020-09-21T07:10:04Z" level=warning msg="Deadline exceeded" namespace=argo workflow=internal-data-ingestiongcv4c
time="2020-09-21T07:10:04Z" level=error msg="error in entry template execution" error="Deadline exceeded" namespace=argo workflow=internal-data-ingestiongcv4c
time="2020-09-21T07:10:04Z" level=warning msg="Deadline exceeded" namespace=argo workflow=internal-data-ingestionwcx7n
time="2020-09-21T07:10:04Z" level=error msg="error in entry template execution" error="Deadline exceeded" namespace=argo workflow=internal-data-ingestionwcx7n
time="2020-09-21T07:10:14Z" level=warning msg="Deadline exceeded" namespace=argo workflow=internal-data-ingestiongcv4c
time="2020-09-21T07:10:14Z" level=error msg="error in entry template execution" error="Deadline exceeded" namespace=argo workflow=internal-data-ingestiongcv4c

This is when I started 100 concurrent workflows with each workflow having about 6-7 Pods.

This workflow is interesting in case of 200 concurrent running workflows.

get-data-and-further is a DAG with 3 children of it. All 3 Pod got succeeded but overall workflow is Failed
Attached all logs related to this workflow for further debugging.
failed-ingestionrkc5f.log
Highlights of logs
time="2020-09-21T09:26:18Z" level=info msg="Step group node internal-data-ingestionrkc5f-2608704937 deemed failed: child 'internal-data-ingestionrkc5f-3985201543' failed" namespace=argo workflow=internal-data-ingestionrkc5f
time="2020-09-21T09:26:18Z" level=info msg="node internal-data-ingestionrkc5f-2608704937 phase Running -> Failed" namespace=argo workflow=internal-data-ingestionrkc5f
time="2020-09-21T09:26:18Z" level=info msg="node internal-data-ingestionrkc5f-2608704937 message: child 'internal-data-ingestionrkc5f-3985201543' failed" namespace=argo workflow=internal-data-ingestionrkc5f
time="2020-09-21T09:26:18Z" level=info msg="node internal-data-ingestionrkc5f-2608704937 finished: 2020-09-21 09:26:18.805091638 +0000 UTC" namespace=argo workflow=internal-data-ingestionrkc5f

@alexec  Can you tell me meaning for Step group node internal-data-ingestionrkc5f-2608704937 deemed failed: child 'internal-data-ingestionrkc5f-3985201543' failed ?   Pod is succeeded but workflow got Failed due to some other error in Argo workflow execution.

What I expect from my observations is that.
Due to lot of concurrent workflows there is sudden increase in Pods resulting into K8s API server timeouts (or API failures). And due to that Argo workflow controller getting into inconsistent state. Some workflows are in forever Pending state while controller is not picking up those at all. Some are failing randomly as Argo workflow controller is not able to commit states for workflows even though DAG task or sequentially step succeeded. Workflow controller is taking more time to process workflows due to slowness in K8s APIs.
Slowness is expected and it's fine but inconsistent state of workflows worries me a lot.
Argo should have a better handling while keeping healthy state machine for each workflow considering such network failures.

Can anyone please provide some executable reproduction steps? I.e. can you provide a workflow that reproduces this behaviour.  It is extremely time consuming (and often impractical) to fix bugs where this has not been provided.

This is the line of code deeming failure:
https://github.com/argoproj/argo/blob/5be254425e3bb98850b31a2ae59f66953468d890/workflow/controller/steps.go#L285

@alexec: Workflow
coin_flip.yml
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: dag-diamon-coinflip-
spec:
  podGC:
    strategy: OnWorkflowSuccess
  entrypoint: diamond
  templates:
  - name: diamond
    nodeSelector:
      agentpool: "argoworkload"
    dag:
      tasks:
        - name: A
          template: coinflip
        - name: B
          dependencies: [A]
          template: coinflip
        - name: C
          dependencies: [A]
          template: coinflip
        - name: D
          dependencies: [B, C]
          template: coinflip

  - name: coinflip
    nodeSelector:
      agentpool: "argoworkload"
    steps:
      - - name: flip-coin
          template: flip-coin
      - - name: heads
          template: found-heads
          when: "{{steps.flip-coin.outputs.result}} == heads"
        - name: tails
          template: coinflip
          when: "{{steps.flip-coin.outputs.result}} == tails"

  - name: flip-coin
    nodeSelector:
      agentpool: "argoworkload"
    script:
      image: python:alpine3.6
      command: [python]
      source: |
        import random
        import time
        time.sleep(60)
        result = "heads" if random.randint(0,1) == 0 else "tails"
        print(result)

  - name: found-heads
    container:
      image: alpine:3.6
      command: [sh, -c]
      args: ["echo \"it was heads\""]

submit a 1000 of them at once - load_argo.sh
./load_argo.sh coin_flip.yml 1000

load_argo.sh
#!/bin/bash
for ((i=1;i<=$2;i++));
do
        argo submit -n argo $1
done

Using an Azure kubernetes cluster.

Do you have time for a Zoom?

Hey @alexec - sure. Let me know of a time that works for you..

Hi @alexec  - I am in IST time zone. I was also wondering how will we connect.. You most likely don't see my email address. I can't see yours at least. Is there someway I can message you?

I'm in PST, so we do not have overlapping working hour with IST AFAIK - so no Zoom.

We'll adjust the timing at our end. Please let us know your availability or email address to have Zoom call. I'll send you an invite there. It will be very helpful if we are able to nail down to the exact issue.

@BlackRider97 which TZ are you in please? Could you do between 4:30pm and 6pm PST today? 9am and 10am tomorrow (Thursday)?

@alexec @AbhishekMallick I am in IST (GMT+5:30) time zone.
Lets do it on Thursday, 24 September 2020 9AM PST ( Thursday, 24 September 2020 9:30 PM IST).
@alexec  Please let me know how I can send you a Zoom call invite to you ?

I'm busy at 9am, but free at 9:30am. Find me here: https://intuit.zoom.us/j/9471219298?pwd=L3dwWklkclZNUk1VYkJBOTE0SGREdz09

I'd like to understand the exact state change a broken workflow has goes through. This can be done either:
(a) using a named workflow (i.e. not metadata.name not metadata.generatedName)
kubectl apply my-wf.yaml && kubectl get --watch wf-name

I've a script that'll turn that into a sequence of JSON patches that show the exact changes.
(b) enabling detailed logging on the workflow controller:
--logelevel=debug --gloglevel=0

That'll log each message sent to Kubernetes. Would that be possible please?

@BlackRider97 @AbhishekMallick, I've started work to fix the throttling issue, but the invalid state issue is a much bigger concern.
I'd like to discount this being a problem caused by any kind of mutating webhook. We've seen this on both Azure and AWS. Can I please ask you to confirm if you have these installed?
These are often found alongside log lines from the workflow controller with the word "conflict" in them.
https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/

Yes there are Mutating Admission Webhook installed but those are for cloud provider specific security and other side-car ingestion use cases. They should not cause any harm to Argo pods.
kubectl api-versions  | grep admissionregistration
admissionregistration.k8s.io/v1
admissionregistration.k8s.io/v1beta1

I also searched for word conflict in our Argo controller logs but there was no such incident regarding it.
However I enabled --logelevel=debug --gloglevel=0 as per your suggestion and I can still see lot of warning messages around
Deadline exceeded
Full stack-trace:
internal-data-ingestiong2qhc error in entry template execution:
Deadline exceeded github.com/argoproj/argo/errors.New
/go/src/github.com/argoproj/argo/errors/errors.go:49
github.com/argoproj/argo/workflow/controller.init
/go/src/github.com/argoproj/argo/workflow/controller/operator.go:109
runtime.doInit
/usr/local/go/src/runtime/proc.go:5222
runtime.doInit
/usr/local/go/src/runtime/proc.go:5217
runtime.main
/usr/local/go/src/runtime/proc.go:190
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1357

Yes there are Mutating Admission Webhook installed but those are for cloud provider specific security and other side-car ingestion use cases. They should not cause any harm to Argo pods.
kubectl api-versions  | grep admissionregistration
admissionregistration.k8s.io/v1
admissionregistration.k8s.io/v1beta1

I also searched for word conflict in our Argo controller logs but there was no such incident regarding it.
However I enabled --logelevel=debug --gloglevel=0 as per your suggestion and I can still see lot of warning messages around
Deadline exceeded
Full stack-trace:
internal-data-ingestiong2qhc error in entry template execution:
Deadline exceeded github.com/argoproj/argo/errors.New
/go/src/github.com/argoproj/argo/errors/errors.go:49
github.com/argoproj/argo/workflow/controller.init
/go/src/github.com/argoproj/argo/workflow/controller/operator.go:109
runtime.doInit
/usr/local/go/src/runtime/proc.go:5222
runtime.doInit
/usr/local/go/src/runtime/proc.go:5217
runtime.main
/usr/local/go/src/runtime/proc.go:190
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1357

Yes there are Mutating Admission Webhook installed but those are for cloud provider specific security and other side-car ingestion use cases. They should not cause any harm to Argo pods.
kubectl api-versions  | grep admissionregistration
admissionregistration.k8s.io/v1
admissionregistration.k8s.io/v1beta1

I also searched for word conflict in our Argo controller logs but there was no such incident regarding it.
However I enabled --logelevel=debug --gloglevel=0 as per your suggestion and I can still see lot of warning messages around
Deadline exceeded
Full stack-trace:
internal-data-ingestiong2qhc error in entry template execution:
Deadline exceeded github.com/argoproj/argo/errors.New
/go/src/github.com/argoproj/argo/errors/errors.go:49
github.com/argoproj/argo/workflow/controller.init
/go/src/github.com/argoproj/argo/workflow/controller/operator.go:109
runtime.doInit
/usr/local/go/src/runtime/proc.go:5222
runtime.doInit
/usr/local/go/src/runtime/proc.go:5217
runtime.main
/usr/local/go/src/runtime/proc.go:190
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1357

@BlackRider97 that probably discounts mutating webhook as the cause.
There are three builds you could try out:

argoproj/workflow-controller:v2.11.2 this contains several changes to improve performance - including a reduction in the number of API requests it makes to Kubernetes
argoproj/workflow-controller:easyjson -  an improved JSON marshaller that also serves diagnostics on port 6060 (https://golang.org/pkg/net/http/pprof/)
argoproj/workflow-controller:easyjson-v2 - as :easyjson but with another performance improvement

@alexec  still no luck with argoproj/workflow-controller:v2.11.2  or argoproj/workflow-controller:easyjson
I can see still workflows are getting stuck in forever Running state. This is causing issues in running Argo in reliable way in production.
Consider following example

Workflow internal-data-ingestionlz5g4 is running since last 13 hours while according to UI there are two DAG steps which are pending, pod named as internal-data-ingestionlz5g4-918231932 and internal-data-ingestionlz5g4-1950258784.
kubectl get workflows | grep internal-data-ingestionlz5g4
internal-data-ingestionlz5g4              Running   13h

kubectl get pod | grep internal-data-ingestionlz5g4-918231932
internal-data-ingestionlz5g4-918231932               0/2     Completed         0          13h

kubectl get pod | grep internal-data-ingestionlz5g4-1950258784
internal-data-ingestionlz5g4-1950258784              0/2     Completed   0          13h

kubectl describe pod internal-data-ingestionlz5g4-1950258784
Name:         internal-data-ingestionlz5g4-1950258784
Namespace:    argo
Priority:     0
Node:         aks-argoworkload-35111968-vmss00005j/<IP_ADDRESS>
Start Time:   Fri, 09 Oct 2020 21:58:57 +0530
Labels:       workflows.argoproj.io/completed=false
              workflows.argoproj.io/workflow=internal-data-ingestionlz5g4
Annotations:  workflows.argoproj.io/node-name:
                internal-data-ingestionlz5g4[1].get-data-and-further(1:1c901ff2-ed94-4a33-8f0b-89e448b829ae).process-boundary(0)
              workflows.argoproj.io/outputs: {"exitCode":"0"}
              workflows.argoproj.io/template:
                {"name":"ingestion-template","arguments":{},"inputs":{"parameters":[{"name":"source","value":"from satellite_sentinelhub_ingestion.batch_u...
Status:       Succeeded
IP:           <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  Workflow/internal-data-ingestionlz5g4
Init Containers:
  init:
    Container ID:  docker://e03afbe74c41be4ab1bcc666dba52cc3d037db2cffe0cc52d5eade3b48eb46d7
    Image:         argoproj/argoexec:v2.11.0
    Image ID:      docker-pullable://argoproj/argoexec@sha256:068d5a5e7ea4f0f816af8a40b24533a18df4a8db9b4b27a91c5b90a63aca3370
    Port:          <none>
    Host Port:     <none>
    Command:
      argoexec
      init
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Fri, 09 Oct 2020 21:58:59 +0530
      Finished:     Fri, 09 Oct 2020 21:58:59 +0530
    Ready:          True
    Restart Count:  0
    Environment:
      ARGO_POD_NAME:  internal-data-ingestionlz5g4-1950258784 (v1:metadata.name)
    Mounts:
      /argo/podmetadata from podmetadata (rw)
      /argo/staging from argo-staging (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-z74lt (ro)
Containers:
  wait:
    Container ID:  docker://4f8ed9003218fc38bc76db44b511a5c186382684c086b854faa2496b58d6e1a6
    Image:         argoproj/argoexec:v2.11.0
    Image ID:      docker-pullable://argoproj/argoexec@sha256:068d5a5e7ea4f0f816af8a40b24533a18df4a8db9b4b27a91c5b90a63aca3370
    Port:          <none>
    Host Port:     <none>
    Command:
      argoexec
      wait
      State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Fri, 09 Oct 2020 21:59:00 +0530
      Finished:     Fri, 09 Oct 2020 22:02:44 +0530
    Ready:          False
    Restart Count:  0
    Environment:
      ARGO_POD_NAME:  internal-data-ingestionlz5g4-1950258784 (v1:metadata.name)
    Mounts:
      /argo/podmetadata from podmetadata (rw)
      /mainctrfs/argo/staging from argo-staging (rw)
      /mainctrfs/tmp from temp-dir (rw)
      /var/run/docker.sock from docker-sock (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-z74lt (ro)
  main:
    Container ID:  docker://2ce3b58dc9ad2523082d293dd01f491e38832051ac70a449890157deade29ecf
    Image:          ingestion:1.0.38
    Image ID:      docker-pullable://ingestion@sha256:b5fd8067a7eb1e39872dc7d26e43edb8847357b6a89555440ce32cbaddac
0397
    Port:          <none>
    Host Port:     <none>
    Command:
      python
    Args:
      /argo/staging/script
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Fri, 09 Oct 2020 21:59:00 +0530
      Finished:     Fri, 09 Oct 2020 22:02:33 +0530
    Ready:          False
    Restart Count:  0
    Environment:
      env:                         dev
    Mounts:
      /argo/staging from argo-staging (rw)
      /tmp from temp-dir (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-z74lt (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  podmetadata:
    Type:  DownwardAPI (a volume populated by information about the pod)
    Items:
      metadata.annotations -> annotations
  docker-sock:
    Type:          HostPath (bare host directory volume)
    Path:          /var/run/docker.sock
    HostPathType:  Socket
  temp-dir:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  argo-staging:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  default-token-z74lt:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-z74lt
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  agentpool=argoworkload
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:          <none>

kubectl describe pod internal-data-ingestionlz5g4-918231932
Name:         internal-data-ingestionlz5g4-918231932
Namespace:    argo
Priority:     0
Node:         aks-argoworkload-35111968-vmss00004z/<IP_ADDRESS>
Start Time:   Fri, 09 Oct 2020 21:58:57 +0530
Labels:       workflows.argoproj.io/completed=false
              workflows.argoproj.io/workflow=internal-data-ingestionlz5g4
Annotations:  workflows.argoproj.io/node-name:
                internal-data-ingestionlz5g4[1].get-data-and-further(0:d9660377-9d3f-4d66-9e92-ba1172041168).process-boundary(0)
              workflows.argoproj.io/outputs: {"exitCode":"0"}
              workflows.argoproj.io/template:
                {"name":"ingestion-template","arguments":{},"inputs":{"parameters":[{"name":"source","value":"from satellite_sentinelhub_ingestion.batch_u...
Status:       Succeeded
IP:           <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  Workflow/internal-data-ingestionlz5g4
Init Containers:
  init:
    Container ID:  docker://1562f74a6dfa283c70927769c61ff6c7c521a70e6a9b808263cede5a29172c50
    Image:         argoproj/argoexec:v2.11.0
    Image ID:      docker-pullable://argoproj/argoexec@sha256:068d5a5e7ea4f0f816af8a40b24533a18df4a8db9b4b27a91c5b90a63aca3370
    Port:          <none>
    Host Port:     <none>
    Command:
      argoexec
      init
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Fri, 09 Oct 2020 21:58:58 +0530
      Finished:     Fri, 09 Oct 2020 21:58:58 +0530
    Ready:          True
    Restart Count:  0
    Environment:
      ARGO_POD_NAME:  internal-data-ingestionlz5g4-918231932 (v1:metadata.name)
    Mounts:
      /argo/podmetadata from podmetadata (rw)
      /argo/staging from argo-staging (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-z74lt (ro)
Containers:
  wait:
    Container ID:  docker://39987728958ebb4b6b3670d200d9e0674003e93336c0950054a97f1d9157678f
    Image:         argoproj/argoexec:v2.11.0
    Image ID:      docker-pullable://argoproj/argoexec@sha256:068d5a5e7ea4f0f816af8a40b24533a18df4a8db9b4b27a91c5b90a63aca3370
    Port:          <none>
    Host Port:     <none>
    Command:
      argoexec
      wait
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Fri, 09 Oct 2020 21:58:59 +0530
      Finished:     Fri, 09 Oct 2020 22:04:22 +0530
    Ready:          False
    Restart Count:  0
    Environment:
      ARGO_POD_NAME:  internal-data-ingestionlz5g4-918231932 (v1:metadata.name)
    Mounts:
      /argo/podmetadata from podmetadata (rw)
      /mainctrfs/argo/staging from argo-staging (rw)
      /mainctrfs/tmp from temp-dir (rw)
      /var/run/docker.sock from docker-sock (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-z74lt (ro)
  main:
    Container ID:  docker://3b70d83a2d00ef52a3a52d4b07cd4ee45e573091597099505b3515d5aee1470d
    Image:         ingestion:1.0.38
    Image ID:      docker-pullable://ingestion@sha256:b5fd8067a7eb1e39872dc7d26e43edb8847357b6a89555440ce32cbaddac
0397
    Port:          <none>
    Host Port:     <none>
    Command:
      python
    Args:
      /argo/staging/script
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Fri, 09 Oct 2020 21:58:59 +0530
      Finished:     Fri, 09 Oct 2020 22:04:19 +0530
    Ready:          False
    Restart Count:  0
    Environment:
      env:                         dev
    Mounts:
      /argo/staging from argo-staging (rw)
      /tmp from temp-dir (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-z74lt (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  podmetadata:
    Type:  DownwardAPI (a volume populated by information about the pod)
    Items:
      metadata.annotations -> annotations
  docker-sock:
    Type:          HostPath (bare host directory volume)
    Path:          /var/run/docker.sock
    HostPathType:  Socket
  temp-dir:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  argo-staging:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  default-token-z74lt:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-z74lt
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  agentpool=argoworkload
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:          <none>

kubectl describe workflow internal-data-ingestionlz5g4 | grep "internal-data-ingestionlz5g4-918231932\|internal-data-ingestionlz5g4-1950258784" -B10 -A2
            f:id:
            f:inputs:
              .:
              f:parameters:
            f:name:
            f:phase:
            f:startedAt:
            f:templateName:
            f:templateScope:
            f:type:
          f:internal-data-ingestionlz5g4-1950258784:
            .:
            f:boundaryID:
--
              f:exitCode:
            f:phase:
            f:resourcesDuration:
              .:
              f:cpu:
              f:memory:
            f:startedAt:
            f:templateName:
            f:templateScope:
            f:type:
          f:internal-data-ingestionlz5g4-918231932:
            .:
            f:boundaryID:
--
      Inputs:
        Parameters:
          Name:        boundary_id
          Value:       d9660377-9d3f-4d66-9e92-ba1172041168
      Name:            internal-data-ingestionlz5g4[1].get-data-and-further(0:d9660377-9d3f-4d66-9e92-ba1172041168)
      Phase:           Running
      Started At:      2020-10-09T16:28:57Z
      Template Name:   ingestion-dag-flow
      Template Scope:  local/internal-data-ingestionlz5g4
      Type:            DAG
    internal-data-ingestionlz5g4-1950258784:
      Boundary ID:     internal-data-ingestionlz5g4-161541463
      Display Name:    process-boundary(0)
      Finished At:     <nil>
      Host Node Name:  aks-argoworkload-35111968-vmss00005j
      Id:              internal-data-ingestionlz5g4-1950258784
      Inputs:
        Parameters:
--

      Name:            internal-data-ingestionlz5g4[1].get-data-and-further(1:1c901ff2-ed94-4a33-8f0b-89e448b829ae).process-boundary(0)
      Phase:           Running
      Started At:      2020-10-09T16:28:57Z
      Template Name:   ingestion-template
      Template Scope:  local/internal-data-ingestionlz5g4
      Type:            Pod
    internal-data-ingestionlz5g4-2187362093:
      Boundary ID:  internal-data-ingestionlz5g4-1898179939
      Children:
        internal-data-ingestionlz5g4-918231932
      Display Name:  process-boundary
      Finished At:   <nil>
--

      Name:            internal-data-ingestionlz5g4[1].get-data-and-further(0:d9660377-9d3f-4d66-9e92-ba1172041168).process-boundary
      Phase:           Running
      Started At:      2020-10-09T16:28:57Z
      Template Name:   ingestion-template
      Template Scope:  local/internal-data-ingestionlz5g4
      Type:            Retry
    internal-data-ingestionlz5g4-2427204537:
      Boundary ID:  internal-data-ingestionlz5g4-161541463
      Children:
        internal-data-ingestionlz5g4-1950258784
      Display Name:  process-boundary
      Finished At:   <nil>
--
      Outputs:
        Exit Code:  0
      Phase:        Succeeded
      Resources Duration:
        Cpu:           201
        Memory:        201
      Started At:      2020-10-09T16:28:57Z
      Template Name:   ingestion-template
      Template Scope:  local/internal-data-ingestionlz5g4
      Type:            Pod
    internal-data-ingestionlz5g4-918231932:
      Boundary ID:     internal-data-ingestionlz5g4-1898179939
      Display Name:    process-boundary(0)
      Finished At:     <nil>
      Host Node Name:  aks-argoworkload-35111968-vmss00004z
      Id:              internal-data-ingestionlz5g4-918231932
      Inputs:
        Parameters:

I have seen another incident for long running workflow where workflow is in Running state while corresponding Pods already completed.  May be Argo controller is not able read Pod's completion state or some race conditions.
FYI I ran 100k workflows with 100 parallelism limit, and 2 workflows went into this in-consistent state.
@alexec

Did you have any luck restarting the controller? This would force a reconciliation of your workflow.

I'd like to have another Zoom on your issue if you can be free please.

As you are aware, we are taking this seriously. We have already rolled out one key for large numbers of items (i.e. withParams or withItems) and have two other PRs in review to address the throttler bug and support controller HA.
What I don't have for this issue is a way to reproduce it. People are able to successfully run 10k+ node workflow on v2.11.3.
In there anyway we can get a workflow that repos the issue please?
Thank you,
Alex

Can we reopen this issue? We are running into this issue as well consistently running long workflows and can provide more information as well as some telemetry information.

@jayz28 did you previously have this problem? Or is it a new problem?

@jayz28 did you previously have this problem? Or is it a new problem?

We have only recently started noticing this issue when we moved to pre-production scale.  Previously at testing loads we didn't notice the issue.

@jayz28 we have 3 users running a massive scale now having similar issues. Essentially, at some point we don't see the pod updates.
Can I ask you try this image argoproj/workflow-controller:no-sig and see if that works? It typically takes 30m to fix problems, so you may have to wait.

@jayz28 we have 3 users running a massive scale now having similar issues. Essentially, at some point we don't see the pod updates.
Can I ask you try this image argoproj/workflow-controller:no-sig and see if that works? It typically takes 30m to fix problems, so you may have to wait.

Sure, making the update now.  Would it resolve workflows already in progress or do I need to launch new workflows?

I think you'll find if you restart the controller, your zombie workflows will come alive again.

I think you'll find if you restart the controller, your zombie workflows will come alive again.

Looks like the :no-sig image has resolved the problem, we are no longer seeing the error and all the workflows are now progressing.  Curious what was specific issue?  Hopefully the fix will be merged soon.

Looks like the :no-sig image has resolved the problem, we are no longer seeing the error and all the workflows are now progressing. Curious what was specific issue? Hopefully the fix will be merged soon.

Can you confirm if this was an issue resolves straight-away, or after 30m?

Looks like the :no-sig image has resolved the problem, we are no longer seeing the error and all the workflows are now progressing. Curious what was specific issue? Hopefully the fix will be merged soon.

Can you confirm if this was an issue resolves straight-away, or after 30m?

It appears to have resolved right away.

Can you please try :latest?

So far so good using the :latest image.

Is it resolved straight away?

Is it resolved straight away?

Yes, it started to resolve very quickly after applying the changes.  Curious what was the cause for the issue?

Can I confirm that they were resolved using :latest or using :no-sig?

Can I confirm that they were resolved using :latest or using :no-sig?

Initially trying :no-sig resolved or stuck workflows.  We have since been load testing using :latest and have not encountered the issue, running similar loads.

Ok. So we can shelve :no-sig.

The issue description and comments sound exactly like what we're experiencing on 2.11.6. "stuck" workflow steps without running pods. @alexec we briefly chatted in Slack and you suggested upgrading to 2.11.7 - would :latest be a better idea instead?

@ebr try them both.

Still an issue with 2.11.7 (i can share some screenshots privately or Zoom). I also raised --qps, --burst and --pod-workers to 10x-20x above than the defaults.
:latest is 2.12.x - will trying it prevent me from reverting to 2.11.7 (we're offloading to Postgres)

You should be able to revert, but I'd recommend you try in a test env.

We are not lucky enough to have a test env :) In a middle of a massive production run right now. so we're doing it live.
I went for 2.12.0-rc2, and as soon as I upgraded the controller, a lot of the step nodes got "unstuck" and shot for the moon, creating all the pods. but some kind of upper bound still exists. E.g., deploying a workflow with a withItems step which is supposed to create ~8000 iterations of the item, it only gets to item ~`(3600:3600) and stalls, like before. In 2.11.7, this upper bound was around 2100 items, but it also seems to depend on the total number of pods the workflow controller is currently handling. I can't find a concrete pattern to it, but the symptoms are reproducible. So 2.12 definitely helps, but not entirely. We are currently working around this by breaking our workflows into chunks that will not create more than 2000 iterations of any step.

Does it come unstuck after 20m (at which time there is a resync)?

Unfortunately, no. E.g. we have a couple of wfs right now that have been "stuck" this way with 0 pods (because they have been GC'd), but no new pods are being created for those wfs. Other wfs (like the chunked-up ones i described above) are happily creating pods though.

Can we Zoom? I'd like to investigate online.

That would be fantastic. Could we organize it for tomorrow, as it's getting late here (EST)? I'll make sure to keep the stuck workflows around (though it's reproducible, so that's not an issue). I can message you on Slack to organize, if that's ok.

I'm in PST.

We're seeing the exact issues in 2.11 as well, when submitting hundreds of workflows. If possible, I'd be delighted to join the call.

Ping me on the Slack channel.

Closing as we have #4560 now.


Add py.typed to mark package as type annotated

Hi, thank you for your work on this nice ORM :smile:
Can you please add file py.typed to ormar folder?
I already see it is mentioned in setup.py package_data={PACKAGE: ["py.typed"]}, but no actual file is present, which causes mypy to give errors:
error: Skipping analyzing 'ormar': found module but no type hints or library stubs  [import]

Thanks for the nice word :)
Sure, will do in next release.

Should be closed in #66


Show price in USD in Drops

our drops now have different price not only 0.5 DOT. To make it easier to collect it would be nice to see the price on https://kodadot.xyz/ahp/drops. With small text - gray. Maybe in USD? Lets make it easy to collect the art. So people are not discouraged if they open drop that is expensive first.

there is already quite a lot of info

either we drop the minted by section or decide to have it without the USD price

linking

https://github.com/kodadot/nft-gallery/issues/7881

I dont want to drop the number of minted pieces... so idk lets leave this open for discussion

Continue in https://github.com/kodadot/nft-gallery/issues/10731


Convert from UTC to different time zone

I would appreciate a way to convert the mongo UTC fields to different time zone as it make the viewing of the reports very difficult including queries between specific hours

This will be added in the solution to #2564.


P135: _.rest should be _.drop with newer versions of lodash

_.rest creates a function that invokes func with the this binding of the created function and arguments from start and beyond provided as an array. (https://lodash.com/docs#rest)
_.drop creates a slice of array with n elements dropped from the beginning. (https://lodash.com/docs#drop)

Latest versions of the book (since the release on May 1) use _.tail instead of _.rest.  Please see the change notes in the update email or contact me if you haven't received one.


Implement search page

https://open.spotify.com/search

Implemented the Search page and Artist search via https://github.com/apollographql/spotify-showcase/pull/87 so I'll close this out 🎉
Linking some new issues for future Search page improvements:

https://github.com/apollographql/spotify-showcase/issues/88
https://github.com/apollographql/spotify-showcase/issues/89


Merge client

What was wrong?
The ethereum-tester-client was an external dependency of eth-testrpc, however it no longer made sense to keep the code out of this repo.
How was it fixed?
The python source and its history have been extracted from ethereum-tester-client and merged into eth-testrpc.
Cute Animal Picture

TODO

[x] fix failing filter tests (all in tests/filters/test_new_filter.py)
[ ] remove now redundant code

change rpc_client -> client
endpoint tests

@pipermerriam: am I right in thinking that all instances of rpc_client can now be replaced with client in the tests?

@rainbeam yes, feel free to do that.

@rainbeam wait, no, that is not correct.  The client fixture interacts with it directly from python.  The rpc_client interacts with it over HTTP via the JSON-RPC server.  We want to keep this distinction in place.

Tests are all passing now. There is an error that comes up at the end though:
Exception ignored in: <bound method state.__del__ of <ethereum.tester.state object at 0x7f6a06f54828>>
Traceback (most recent call last):
  File "/home/rain/src/miniconda/envs/testrpc/lib/python3.5/site-packages/ethereum/tester.py", line 187, in __del__
AttributeError: 'NoneType' object has no attribute 'rmtree'

Not sure if you'd been seeing this before? I can see something similar to this on master.

Interesting, that lends some possible insight as to where that error comes from.  Thanks for reporting.
In other news, this still has a WIP in the title.  Is that the case or is it ready for review and merge?

@pipermerriam: please review.


(853a) Delete course participation page

Changes in this PR
This adds the delete course participation page. It doesn't implement the destroy action - that will come in another PR
Screenshots of UI changes

Release checklist
Release process documentation
As part of our continuous deployment strategy we must ensure that this work is
ready to be released once merged.
Pre-merge

[ ] There are changes required to the Accredited Programmes API for this change to work...

[ ] ... and they have been released to production already

Post-merge

[x] This adds, extends or meaningfully modifies a feature...

[ ] ... and I have written or updated an end-to-end test for the happy path in the Accredited Programmes E2E repo

[ ] This makes new expectations of the API...

[ ] ... and I have notified the API developer(s) of changes to the contract tests (Pact), or the API is already compliant

[x] Manually approve release to preprod
[x] Manually approve release to prod

 Add page for deleting previous programme (course participation) (UI) (M)


Picking a date does not set the value in ngForm

Inside a template driven from (ngForm) when I choose a date using the datetime-picker the value is not set in the form object.
But once i manually change something or input the date myself the form object once submitted is correct.
Plunker Example
I don't think this should be the expected behaviour.
Am I doing something wrong? This seems quite simple and intuitive.
Thank you for your time.

Please use example given from README.md
   <form [formGroup]="myForm">
     <input
       required
       [(ngModel)]='myVar'
       formControlName="date"
       ngui-datetime-picker
        date-only="true"/>
   </form>
   myForm.controls.date: {{myForm.controls.date.value}}

https://plnkr.co/edit/su2aiL?p=preview
You are missing formControlName

@allenhwkim this is what i did in the end.
You do not have to have formGroup and formControlName for this template driven form to work. My example is a completely working form, there is nothing missing and everything was working, except the plugin.


Update RabbitMQ cookbook to the latest community version

The community cookbook has added some features that the Entry Management team needs for configuring Rabbit. This PR updates simply pulls the latest master directly.

$ knife search node "recipes:rabbitmq"
1 items found
Node Name:   dev23-entry-management-mq01.aws.tfly-internal.com
Environment: dev23
FQDN:        dev23-entry-management-mq01.aws.tfly-internal.com
IP:          <IP_ADDRESS>
Run List:    role[entry-management-mq]
Roles:       entry-management-mq, base
Recipes:     tfly-bootstrap::slack-handler, tfly-bootstrap::network, apt, build-essential, cron, git, ntp, screen, tfly-sudo, users, tfly-sysctl, tfly-root_user, tfly-tools, vim, postfix, tfly-sensu, chef-client::cron, tfly-chef-client, motd-tail, tfly-newrelic, rabbitmq, rabbitmq::mgmt_console, rabbitmq::plugin_management, apt::default, build-essential::default, build-essential::_debian, cron::default, git::default, ntp::default, screen::default, tfly-sudo::default, users::default, users::sysadmins, users::tfly-staff, users::platform-group, users::wheel, users::htpasswd, tfly-sysctl::default, sysctl::default, sysctl::service, tfly-root_user::default, tfly-tools::default, vim::default, postfix::default, tfly-sensu::default, tfly-sensu::_config, tfly-sensu::_packages, sensu::default, sensu::_linux, sensu::client_service, tfly-chef-client::default, logrotate::default, motd-tail::default, tfly-newrelic::default, newrelic::default, newrelic::server_monitor_agent, tfly-newrelic::install, rabbitmq::default, erlang::default, erlang::package
Platform:    ubuntu 14.04
Tags:

$ knife cookbook upload rabbitmq --freeze -o $PWD/../ -c ../../ticketfly-chef-repo/.chef/knife.rb
Uploading rabbitmq       [4.6.0]
ERROR: Cookbook rabbitmq depends on cookbooks which are not currently
ERROR: being uploaded and cannot be found on the server.
ERROR: The missing cookbook(s) are: 'erlang' version '~> 1.5.0', 'yum-erlang_solutions' version '>= 0.0.0'

[jmiller@jmillertf112451 ~/Development/ticketfly-chef-repo (master)]
$ knife cookbook list|grep erlang
erlang                               1.3.2
[jmiller@jmillertf112451 ~/Development/ticketfly-chef-repo (master)]
$ knife search node "recipes:erlang"
0 items found
[jmiller@jmillertf112451 ~/Development/ticketfly-chef-repo (master)]
$ knife cookbook list|grep yum-erlang_solutions

$ knife cookbook upload yum-erlang_solutions --freeze -o $PWD/../ -c ../../ticketfly-chef-repo/.chef/knife.rb
Uploading yum-erlang_solutions [0.3.1]
Uploaded 1 cookbook.

$ knife cookbook upload erlang --freeze -o $PWD/../ -c ../../ticketfly-chef-repo/.chef/knife.rb
Uploading erlang         [2.0.1]
Uploaded 1 cookbook.

$ git checkout v1.5.8
Note: checking out 'v1.5.8'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b
HEAD is now at 589995b... release v1.5.8
[jmiller@jmiller-tf11-2451 ~/Development/TFLY_COOKBOOKS_MASTER/erlang ((v1.5.8))]
$ knife cookbook upload erlang --freeze -o $PWD/../ -c ../../ticketfly-chef-repo/.chef/knife.rb
Uploading erlang         [1.5.8]
Uploaded 1 cookbook.
[jmiller@jmiller-tf11-2451 ~/Development/TFLY_COOKBOOKS_MASTER/erlang ((v1.5.8))]
$ git co master
Previous HEAD position was 589995b... release v1.5.8
Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.
[jmiller@jmiller-tf11-2451 ~/Development/TFLY_COOKBOOKS_MASTER/erlang (master)]
$ cd ../rabbitmq/
[jmiller@jmiller-tf11-2451 ~/Development/TFLY_COOKBOOKS_MASTER/rabbitmq (master)]
$ knife cookbook upload rabbitmq --freeze -o $PWD/../ -c ../../ticketfly-chef-repo/.chef/knife.rb
Uploading rabbitmq       [4.6.0]
Uploaded 1 cookbook

Done


Implement second order accurate time discretization

Presently it would be useful to demonstrate a second order method in time, e.g. Crank-Nicholson ($\theta = 1$), as a way to demonstrate the accuracy of the monolithic approach.

After looking into this, implementing BDF2 is actually much more simple that the theta-family of schemes; and I expect BDF2 to work better (i.e. be more stable for our problem) than Crank-Nicholson anyway.

Completed BDF2 as of PR. #254. Still need to verify second order accuracy.


Update mujoco_py environment initialization deprecation warning

Mentions that v5 is available when v2 or v3 are initialized

Shall we merge once v5 is merged?


rapidjson 1.0-beta

Updated rapidjson to its first beta release.
I'm wondering if it's appropriate to keep it in this repo? Should I move this formula to homebrew-devel-only or the main repo?

see homebrew/homebrew#39005


Update all crates

All current crates in volaris are SEVERLY outdated, thought it didn't make any security issues, Clap V3 does have an issue with atty, which would be nice to get rid off.
TL:DR: Update everything, make updating in the future less painful

Still going, got sidetracked with Volaris-GUI.
I might fully rewrite this, I'm not quite sure to be honest.
Seeing as this is ment to be safe code, I don't know if I should, but I'll have another look today.


Mutable app state example mentions web::Data which does not (any more) seem to exist

The mutable app state example at https://ntex.rs/docs/application#shared-mutable-state mentions web::Data.
Maybe web::types::State is meant?
Since what is being created is a plain struct, this could be reworded to // Note: App state created _outside_ HttpServer::new closure.
Please let me know if I misunderstood. If not, then I'll be happy to PR the fix.

Hey @LeoniePhiline, sorry for the late reply, i didn't get notified.
You're right web::types::State is meant!
You can open a pull request if you want!


Player is very strong

Plz nerf powerwalking!

This was also pointed out a few days ago.
https://discordapp.com/channels/310555209753690112/560845886263918612/628263053938524161
Basically, players are supposed to be able to push multiple lockers, but it should get incrementally slower for each one pushed.

Working as intended, what's the issue here?

Alright I've changed the friction code around resulting in not being able to push more than 1 locker. I can reduce the friction on floors to counteract this or reduce mass of lockers or increase mass of the spaceman.
How many lockers do people want to push in most cases?

When trying to imagine pushing a locker that size (about human width) i would say 1 or at most 2.


There is a long time bug under VC++ [bug]

do{
    printf("test");
    continue;
    }
while (0);

It only prints once!
This problem has existed for several years.
MSVC: 14.33.31424  in VS2022 17.3.0 preview 1.1

@nil-ref
If you think you've found a bug in the compiler, we can't do anything about it in the documentation. Bugs should be reported on the C++ Developer Community page. For more information, see How to report a problem with the Microsoft C++ toolset. As a result, I'm closing the issue.
However, in this case, the behavior is not a bug. A continue statement in a loop jumps directly to the loop's conditional test, skipping any intervening code. The code is doing exactly what you told it to do: it jumps to the while (0); statement and exits the loop. Every C and C++ compiler behaves this way, and always has.


Select multiple does not respect ngModel updates

Bug, feature request, or proposal:
Bug
What is the expected behavior?
When you update the ngModel of a select with multiple, it should update the selection
What is the current behavior?
When you have a select with an [(ngModel)] and multiple and update the ngModel outside of the select, the select doesn't update with the correct selection
What are the steps to reproduce?
https://stackblitz.com/edit/angular-select-multi-bug
What is the use-case or motivation for changing an existing behavior?
I have a form that I'd like to dynamically update the selection,
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 5.2.5
Material 5.2.1
Is there anything else we should know?

That's because Angular's change detection compares by reference. When you pop the array, there's no way for the select to know that anything changed. You can work around it either by reassigning the array or setting the value through a FormControl, e.g.:
this.toppings = this.toppings.slice(0, -1);

Hi crisbeto,
working like charmsssssssssssssssssss
:)\
thank you

Bug, feature request, or proposal:
Bug
What is the expected behavior?
When you update the ngModel of a select with multiple, it should update the selection
What is the current behavior?
When you have a select with an [(ngModel)] and multiple and update the ngModel outside of the select, the select doesn't update with the correct selection
What are the steps to reproduce?
https://stackblitz.com/edit/angular-select-multi-bug
What is the use-case or motivation for changing an existing behavior?
I have a form that I'd like to dynamically update the selection,
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 5.2.5
Material 5.2.1
Is there anything else we should know?

Steps to reproduce not found in stackblitz


[qt5-base] Build error on x64-windows

Package<EMAIL_ADDRESS>Host Environment

Host: x64-windows
Compiler: MSVC 19.41.34120.0
vcpkg-tool version: 2024-07-10-d2dfc73769081bdd9b782d08d27794780b7a99b9
vcpkg-scripts version: 350898514 2024-08-23 (34 hours ago)

To Reproduce
vcpkg install kf5guiaddons
Failure logs
-- Figuring out qt target mkspec. Target arch x64
-- Target mkspec set to: win32-msvc
-- Host mkspec not set. Qt's own buildsystem will try to figure out the host system
-- Using cached qtbase-everywhere-opensource-src-5.15.14.tar.xz.
-- Cleaning sources at P:/dev/vcpkg/buildtrees/qt5-base/src/5.15.14-8973c16543.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source P:/dev/vcpkg/downloads/qtbase-everywhere-opensource-src-5.15.14.tar.xz
-- Applying patch patches/CVE-2023-32763-qtbase-5.15.diff
-- Applying patch patches/CVE-2023-34410-qtbase-5.15.diff
-- Applying patch patches/CVE-2023-37369-qtbase-5.15.diff
-- Applying patch patches/CVE-2023-38197-qtbase-5.15.diff
-- Applying patch patches/CVE-2023-43114-5.15.patch
-- Applying patch patches/0001-CVE-2023-51714-qtbase-5.15.diff
-- Applying patch patches/0002-CVE-2023-51714-qtbase-5.15.diff
-- Applying patch patches/CVE-2024-25580-qtbase-5.15.diff
-- Applying patch patches/CVE-2024-39936-qtbase-5.15.patch
-- Applying patch patches/winmain_pro.patch
-- Applying patch patches/windows_prf.patch
-- Applying patch patches/qt_app.patch
-- Applying patch patches/gui_configure.patch
-- Applying patch patches/xlib.patch
-- Applying patch patches/egl.patch
-- Applying patch patches/qtbug_96392.patch
-- Applying patch patches/mysql_plugin_include.patch
-- Applying patch patches/mysql-configure.patch
-- Applying patch patches/cocoa.patch
-- Applying patch patches/xcode-15.patch
-- Applying patch patches/patch-qtbase-memory_resource.diff
-- Applying patch patches/Qt5BasicConfig.patch
-- Applying patch patches/Qt5PluginTarget.patch
-- Applying patch patches/create_cmake.patch
-- Applying patch patches/Qt5GuiConfigExtras.patch
-- Applying patch patches/fix_angle.patch
-- Applying patch patches/mingw9.patch
-- Applying patch patches/XKB_KEY_dead_lowline.patch
-- Using source at P:/dev/vcpkg/buildtrees/qt5-base/src/5.15.14-8973c16543.clean
Package harfbuzz was not found in the pkg-config search path.
Perhaps you should add the directory containing `harfbuzz.pc'
to the PKG_CONFIG_PATH environment variable
Package 'harfbuzz' not found
CMake Error at installed/x64-windows/share/vcpkg-pkgconfig-get-modules/x_vcpkg_pkgconfig_get_modules.cmake:40 (execute_process):
  execute_process failed command indexes:

    1: "Child return code: 1"

Call Stack (most recent call first):
  ports/qt5-base/portfile.cmake:223 (x_vcpkg_pkgconfig_get_modules)
  scripts/ports.cmake:192 (include)

We are a pile of problems!

Solved be reinstall harfbuzz


Resolve the library directory thing

What to do with the lib now that configure and cmake don't put the library there anymore. Probably change the documentation?

Hello All, after a fresh build from today's master branch, this remains an issue.  Making does not place a lib directory in CPPUTEST_HOME, no directory, no objects.  There is neither lib\libCppUTest.a nor lib\libCppUTestExt.a available to the default target in examples/Makefile

Hi Gary
Did you do a local install?  Did you use the cpputest_build directory?
You'll find cpputest_build/lib is where the libs are.  Unfortunately
this is incompatible with my stuff that uses MakefileWorker.mk
If you build like this, it is compatible
cd ~/tools/cpputest
./configure
make tdd

You can add this to .bash_profile
export CPPUTEST_HOME=~/tools/cpputest

It would be good to fix this for local installs and apt-get and brew
installs too.
James
On 14 Jul 2016, at 13:50, Gary Hendrick wrote:

Hello All, after a fresh build from today's master branch, this
remains an issue.  Making does not place a lib directory in
CPPUTEST_HOME, no directory, no objects.  There is neither
lib\libCppUTest.a nor lib\libCppUTestExt.a available to the
default target in examples/Makefile

You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/cpputest/cpputest/issues/115#issuecomment-232757353

What @jwgrenning proposes works to run the available example. However CMake doesn't:
cd ~/tools/cpputest
cmake .
make
cd examples
make all

This throws make: *** No rule to make target '../lib/libCppUTest.a', needed by 'CppUTestExamples_tests'. because it puts the library is at ~/tools/cpputest/src/CppUTest/libCppUTest.a. I think the readme should be updated because not being able to run the only example is a big deal for new users.
I would happily update it, but I'd also like to fix CMake compilation and I haven't found a solution for that. If you point me where to look I can try.


Add maneuver and modifier to visual instructions

Closes: https://github.com/mapbox/MapboxDirections.swift/issues/238
Adds maneuverType  and maneuverDirection to the VisualInstruction class.
/cc @lyzidiamond @mapbox/navigation-ios

@mapbox/navigation-ios this is ready for review.

Unwrapping type and modifier still crashes on the majority of the routes.

@frederoni noting, the fix was not fully deployed until now.


App CSS get loaded inside carte-blanche

I don't know if it's an expected behavior, but in my app.js I import some css files that are loaded in the global scope (styling for the HTML tags, body, etc).
When I open carte blanche and I visit the home page, everything is okay. When I open one of the components pages, the document.styl get loaded globally and changes the style of the whole Carte Blanche page.
To note that it doesn't happen with all the files I load, for example, only document.styl get loaded, even if I load at the exact same way even other two styl files.
I would expect those files to be loaded inside the iframes, not inside the top page.
I don't understand why this is happening tho.

That's definitely a bug, those styles shouldn't be injected into the main CarteBlanche. Do you have some sample code by chance? How are you importing the files?

I'm importing them with import './styles/document.styl
No code to show sorry :(

Alright, will try to replicate!


Pinning Ubuntu Desktop icon between stable releases

Per #1793 I have switched from 7.3.119 to 7.3.247. I have downloaded and used the provided .deb
I have the icon for Toggle pinned to the launcher. After the upgrade, on clicking the icon it launched, but was not pinned to the same icon (thus the icon is duplicated on the launcher)

With the current releases, the desktop file is located in a standard location and it does not change between releases. This issue is now resolved.


What is the correction pronunciation for On-premise?

What is the correction pronunciation for On-premise?

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

ID: a42a45e5-803c-10f4-c652-294bfab95e96
Version Independent ID: d372c810-b04c-f3fa-acbe-fd8c2f89d505
Content: Cloud migration - Cloud Adoption Framework
Content Source: docs/migrate/index.md
Service: cloud-adoption-framework
Sub-service: migrate
GitHub Login: @BrianBlanchard
Microsoft Alias: brblanch

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 461535


Command: next_field

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1379638-command-next_field?utm_campaign=plugin&utm_content=tracker%2F282001&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F282001&utm_medium=issues&utm_source=github).

Migrated to limetext/lime-backend#8.


add translatable=false when there is single language to avoid lint error

add translatable=false when there is single language to avoid lint error

@yannickpulver :)

Hi @anthony-fresneau-kiplin
Thanks for your pull request 🙌
I think we can combine this with #30 and add the tools:ignore="MissingTranslation" on top of the file, instead to each of the keys. Hope that works for you :)

Closing it in favour of tag/0.2.8


add support to enable Z3 Theorem Prover

Add support to enable the Z3 Theorem Prover if it is available during analysis.
This option is only available for the clang static analyzer.
If we choose to extend our top level command line with it, it should be under
the clang static analyzer flags like ctu.
We should give some warning to the user if Z3 is enabled on the command line but the clang used for analysis is not built with it.

I am not sure if Z3 support is ready for the users as its performance is really bad. But using Z3 for refutation is great and probably should be the default when Z3 support is available.

It will not be turned on by default it will be just an option so the user can experiment with it. Later if the performance is good enough we could enable it by default. We will see.

I see. I just wanted to be sure that there is no misunderstanding and you really wanted to add Z3 support (as in using Z3 as the default constraint solver) rather than adding refutation support (as in using Z3 for cross checking the built in constraint solver for bugs).

For the refutation I think I will create a separate issue. It depends on a clang with Z3 but needs to be enabled with different flags.


Error while installing FFmpeg Java

Describe the bug
it seems that the plugin "maven-gpg-plugin" was unable for some reason to complete the ffmpeg project artifact signing operation due to an error generated by gpg.
To Reproduce
run mvn install in the ffmpeg-cli-wrapper-master directory (the error also happen if you run Building & Releasing commands)

Expected behavior
theoretically it should compile the final .jar file to use as an external library.
Version (if applicable):

OS: macOS (intellij idea 2022.3.1)
Java Version: openjdk 19.0.1 2022-10-18
gpg (GnuPG) 2.4.0
Apache Maven 3.8.7

Additional context
12:53:27.460 [TcpProgressParser(tcp://<IP_ADDRESS>:49170)] WARN net.bramp.ffmpeg.progress.Progress - skipping unhandled key: out_time_us = 5269333 (and other similar warnings)
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-gpg-plugin:3.0.1:sign (sign-artifacts) on project ffmpeg: Exit code: 2 -> [Help 1]
Please let me know if I'm doing something wrong and if there's a way to fix it.
Thank you.

I haven't updated the plugins in a while. Maybe that would help... But a quick Google search, shows others with a similar issue and fixes: https://stackoverflow.com/a/54325356/88646

I've updated a bunch of things, and been unable to repro this myself. If this is still a problem please reopen this thread.


Callback when using "disableInitialLoad: true"

Following a previous comment about lazy loading, I would like to use "disableInitialLoad: true" and then refresh the ad units below the fold when they com into view.  Manually it works great, as long as I call the refresh after DFP has registered the ads.
However, when I use disableInitialLoad: true, the callback 'afterAllAdsLoaded' never fires.  Is there a callback event or another method that I can use to get notified when the ads are all registered?
Updated:
For now, I am pushing a command into googletag after calling .dfp, which seems to work.
        $.dfp(...);
        window.googletag.cmd.push(
            function () {
                 //Define scrollSpy for lazy load ads
                 .....
            }
        );

I have refactored the code, and no longer use disableInitialLoad.


Maybe not a mistake in 04_error?

In the code for the "2-digit precision base 2 system" in the 04_error notebook, we see the system defined as follows:
axes.plot( (d1 + d2 * 0.1) * 2E, 0.0, 'r+', markersize=20)
axes.plot(-(d1 + d2 * 0.1) * 2E, 0.0, 'r+', markersize=20)
Shouldn't the 0.1 be 0.5, since this is binary and not decimal (or maybe I am missing something)?

Yeah, that was a typo.


Flake8 rule 'E999' reported an invalid point

Flake8 reported an invalid point for the rule E999, with the messge SyntaxError: EOL while scanning string literal.
Debug information:
Atom version: 1.21.1
Flake8 version: 3.4.1 (mccabe: 0.6.1, pycodestyle: 2.3.1, pyflakes: 1.5.0) CPython 3.6.3 on Windows

Duplicate of #505

@Arcanemagus Unfortunately not as the issue dissappeared on it's own..

That's unfortunately the nature of most of these: They depend on the exact state of the document when the error was thrown (hence why it's impossible to guess what was triggering this). If you see it again save the file immediately so it can possibly be reproduced 😉.

@Arcanemagus Sure! 👍


Contributors page added to Navbar

Pull Request
Fixes #223 and #222
Description

I have added a new icon for "contributors" page on navbar!
Fixed Text issue in "WorkTracker" page too!

Screenshots
Navbar :

Text on WorkTracker Page :
Before :

After :

Thank you for assigning issues! (I know I spam a lot here xD)

Good job @Saaarthak0102 .

Good job @Saaarthak0102 .

🫡


Won't get the Clover boot menu

To Reproduce
Steps to reproduce the behavior:

Follow onscreen instruction with success until step 6
After restarted up the WM, I'm getting the UEFI interactive shell interface
Mapping table displays FS1 and FS0 but I'm not able to find how to switch into Clover boot menu

Expected behavior
Start macOS in the Clover boot menu
Additional context
Tried fs1: and fs0: where I enter \EFI\Boot\Bootx64.efi
No luck.

Thanks much Alexander but in which directory I should run make ?

created: /tmp/macOS-MojaveClover.dmg
cp: /Volumes/Clover-v2.4k-4533-X64/*: No such file or directory
cp: directory /Volumes/NO NAME/EFI/CLOVER does not exist
cp: directory /Volumes/NO NAME/EFI/CLOVER/drivers64UEFI does not exist```
Let me see it.

I believe that I have an issue with xz which is installed but not linked in /usr/local due to macOS SIP
/Applications/RunMojaveVirtualbox.app/Contents/Resources/runMojaveVirtualbox.sh: line 213: xz: command not found
tar: Error opening archive: Failed to open 'clover.tar'

I'm trying running brew link xz then I rebuild from scratch (step 1) after erased everything.

Fixed
Issue
On macOS SIERRA or sup, xy can be installed but not properly linked making Clover.tar to fail on decompression.
Workaround
Prerequis

Brew

Step

Install xy with Brew if not installed by the script
Run $ brew link xz
Delete previous Mojave VM from VirtualBox (Delete All Files)
Empty tmp or reboot computer
Re start from step 1

/usr/local is not protected by SIP. I added another additional brew link xz to the setup script. Hope this would fix the issue for others. Thanks.

Until I'm wrong, since SIERRA, /usr/local permissions can't no longer be modified with chown. I believe it is due on new SIP polcies (?). It makes necessary to create a subfolder in /usr/local prior to be able to install and set any file with appropriate permissions or links; one of the reason why Brew can get some issues.

Just tried this today and I’m getting the same issue
Ps: xz already linked

Can you provide the output of the log file?


Still interested!

Hi Immo,
just wanted to let you know that there are some people still interested in a continuation of this series.
Thanks,
Flo

October, almost november and I'm istill interested. Please, continue with the series.

 I hope you are alright.

Heads up for all folks that don't monitor twitter ;)
The series will continue today (8 AM PST ~ 9h from now)
https://www.youtube.com/watch?v=F0ZeU0aSkfQ&list=PLRAdsfhKI4OWNOSfS7EUu5GRAVmze1t2y

He is back!


FIX graphics autoport setting in examples

The examples are using spice for display with autoport value as
true. This causes no connection to VM display. In fact
any value except "yes" makes autoport to be set to "no" in the
VM XML configuration.

Coverage remained the same at 57.383% when pulling 926a03f669dd644981cf1815677ff7ee62f12899 on rsjethani:master into 8367c0506c19ab7900f3540cd0e293f96472c179 on dmacvicar:master.


feat(chart): mount host's /etc on Longhorn manager for NFS configuration check

Which issue(s) this PR fixes:
Issue longhorn/longhorn#9830
What this PR does / why we need it:
LH manager's node controller checks the NFS configuration for LH node runtime status. It needs host's /etc/ to read /etc/nfsmount.conf
Special notes for your reviewer:
Additional documentation or context

Doc PR: longhorn/website#1019

@mergify backport v1.7.x
The change doesn't need to backport to v1.6.x which doesn't support CLI and node.status.conditions.


move deeplake dataset to _orig_dataset to enable ld.dataset variable …

…for integration like mmdet
🚀 🚀 Pull Request
Impact

[ x] Bug fix (non-breaking change which fixes expected existing functionality)
[ ] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

fixed the issue related to the enterprise dataloader's dataset property overwriting, as the integrations are using that property in the pipelines
Description

Things to be aware of

Things to worry about

Additional Context

This was the change which introduced broken shuffling. We reverted it to fix the shuffling. Can you please explain what is this doing?

The issue was that our mmdet integration requires that the dataloader should have the dataloader.dataset property. So the training pipeline will get from the dataloader the dataset MMdetDataset  and extract the properties in train/val/test loops moved all the dataset related logics into the internal _orig_dataset , property and we reserve the dataset property for the
training frameworks.
so the workflow looks like this

we create dataloader
set the dataloader's dataset property to be MMdetDataset here
and the dataloader was failing here and all the pleas where we wanted to access self.datset as if was changed from deeplake dtaset to MMdetDataset object.


Observable client-side preferences and configs

Its always been a little strange that preferences and configs are only updated on the client when the entire page is refreshed.    We think it would be very natural to push or poll for updates, and make the collections observable on the client.
Just doing so will not automatically make all hoist and app code reactive to these, but it is the first step, and we think its a capability that could be gradually exercised if we made it available.

For configs, we discussed admin option to push changes, rather than pushing after each modification or a client-side refresh.  Would allow admin to change several configs, validate, then push to clients. Also discussed how this puts an extra burden on developers to document if configs would be read again.

For preferences, discussed how making them observable (within a single client) could save some boilerplate code and is a clear win, but refreshing might or might not be worth implementing.


[MGDSTRM-10786] Disable java-operator-sdk controller metrics by default

what is the effect of this on any metrics that we may be capturing from this endpoint for management purposes?

what is the effect of this on any metrics that we may be capturing from this endpoint for management purposes?

The operator will no longer store or return metrics in the operator_sdk_ prefix. I haven't found anywhere they are actually used for anything currently.


gpt-3.5-turbo-instruct?

I am not seeing support for this, curious if you are planning to add it or if I'm missing something?
I was happy to see Completions getting some love.

In the next version (7.4.0), I am going to add it to the model list. However, in the meantime, you can pass the model name as a string to use your instruct model without waiting for the next update.


just test

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run performance

run performance

run performance

run performance

run performance

run performance

run buildall

run buildall

run performance

run performance


feat: Add og:url and og:image:alt

og:image:alt is a nice addition.
og:url is according to ogp.me mandatory.

Also wanted to push the propTypes change 😆 Wasn't sure as you mix propTypes with ||


Tmp: use nullTracer for network layer

Issue Number
A bit related to #1398

Overview

Need windows artefact from CI for this

Comments

Proper fix in #1484


October topics

https://b10c.me/observations/07-invalid-block-809478/

https://github.com/bitcoin/bitcoin/pull/28550

https://github.com/bitcointranscripts/bitcointranscripts/pull/276

https://blog.mutinywallet.com/fixing-payment-reliability/

https://github.com/bitcoin/bitcoin/pull/27596

https://github.com/lightningnetwork/lnd/releases/tag/v0.17.0-beta

https://github.com/lightningnetwork/lnd/issues/7961

https://twitter.com/rot13maxi/status/1709011253350334887

https://github.com/lightningdevkit/rust-lightning/releases/tag/v0.0.117

https://t.co/Itf9UHos0C

https://ishaana.com/blog/wallet_fingerprinting/

https://x.com/m1sterc001guy/status/1712545382226645329?s=20

https://twitter.com/peterktodd/status/1712738205160632347
On Thu, Oct 12, 2023, 2:35 PM benthecarman @.***> wrote:

https://x.com/m1sterc001guy/status/1712545382226645329?s=20
—
Reply to this email directly, view it on GitHub
https://github.com/austinbitdevs/austinbitdevs.com/issues/26#issuecomment-1760254656,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAYW5TDEPHML2RBF4DLOOLX7BBBBAVCNFSM6AAAAAA5GJOSS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRQGI2TINRVGY
.
You are receiving this because you commented.Message ID:
@.***>

https://GitHub.coo/bennyhodl/baywallet

mononaut adds two 31 bit unsigned integers in a bitvm circuit https://x.com/mononautical/status/1713291840638599206?s=46

https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-October/021997.html

https://gitlab.com/-/snippets/3611229

https://lists.linuxfoundation.org/pipermail/lightning-dev/2023-October/004122.html

https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-October/022030.html
On Mon, Oct 16, 2023, 1:39 PM benthecarman @.***> wrote:

https://lists.linuxfoundation.org/pipermail/lightning-dev/2023-October/004122.html
—
Reply to this email directly, view it on GitHub
https://github.com/austinbitdevs/austinbitdevs.com/issues/26#issuecomment-1765073266,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAYW5RCBZNRBOJPK5I3VLTX7V5MJAVCNFSM6AAAAAA5GJOSS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRVGA3TGMRWGY
.
You are receiving this because you commented.Message ID:
@.***>


Load cache from local or remote zip

Solves https://github.com/Dezinater/osrscachereader/issues/1
Added cache loading via downloading and unzipping remote and local zip files
Prevents https://github.com/Dezinater/osrscachereader/issues/3
Resolves undefined when the xteas file is not found, it crashed on my cache version
Pinned web-worker 1.2 since 1.3.0 gave me an error.
NOTE: package-lock.json not updated since prebuilt binaries for canvas are not available for ARM mac, and npm fails to build it. I succeeded with pnpm, but did not want to include that lock file, so you have to run npm i yourself after this PR

@Dezinater You said you have a couple of more ideas for the zip loading, I'm interested, could you reveal them?

The idea was basically just being able to load either the latest cache or a specific cache version number from passing a number to it
Maybe latest can be something like this
let cache = new RSCache("latest", (x) => { console.log(x) }, "./");
let cache = new RSCache(-1, (x) => { console.log(x) }, "./");
let cache = new RSCache(Infinity, (x) => { console.log(x) }, "./");
And then loading a specific version
let cache = new RSCache(219, (x) => { console.log(x) }, "./");
It should just be a small change but this would be very useful for testing I think
Also another somewhat related concept, there is an API on OpenRS2 to directly load cache file data. I was told about it in the OpenRS2 discord and they sent me this code https://github.com/Pazaz/RT5-Server/blob/main/util/OpenRS2.js

Interesting concepts, the version number based retrieval indeed seems to be very useful for testing...
As for the dynamic cache loading, interesting as well, might be useful depending on the requirements of your application e.g displaying icons and models on a regular website. Downloading tens of MB for just that is not going to work. I guess for a lot of other applications direct, fast access to a local version of the cache is important for speed and reliability reasons as well as the offline availability of the data.
What I'm thinking is: We could make a cache loading API that supports various cache loading strategies.

On demand: only load the files when they are needed and store retrieved items for future usage. Fast initial load and limits the applications data usage. Unreliable for offline usage and suffers from delays when loading new items.
Full download: Download and store the full cache. Slow initial load and causes a large data usage. Fully available offline and fast item retrieval.
Hybrid: Use the on demand strategy until the full download is complete. Fast initial load and once completed, fully available offline and fast item retrieval

We could also support various storage mechanisms behind an interface, e.g. fs like the sample above, but also innodb for in-browser caching. I guess caching should be optional so consumers could do their own caching via e.g. service-workers with workbox

I like the idea of having different modes and especially like the hybrid idea of having it use the on demand mode until the cache is loaded. For caching I did originally have something for it but I ended up having to remove it because a user had issues with it. I think now would be a good time to look into it again.
Also I've created a discussions section on this repo so we can post ideas in there now

@Dezinater Is this PR good enough to get merged so we can load local and remote zips? Or do you want to implement additional features first?

I think it is good to merge but I would like to add the additional features first. I've just been a bit busy but I should be able to add it in this weekend or you can add  the changes if you'd like
Also there's multiple caches per version because of how they patch the game. Do we want a feature to grab by closest timestamp as well or should version number only be good enough?

I've added a few ways of loading the cache. You can load it by version, date or latest.
For latest it can either be the string 'latest' or undefined
let cache = new RSCache();
let cache = new RSCache("latest");
For timestamp it has to be a Date object
let cache = new RSCache(new Date(12345));
And version is just a number
let cache = new RSCache(220);
I also had to add a new promise in CacheLoader since it wasn't able to use async functions. There would be some async race conditions so I added a cachePromise which resolves whenever CacheLoader is done it's job


[ST] iOS user unable to connect wallet

Describe the bug
A user on iOS is unable to connect their wallet to the bridge site. They tried Metamask, Trust, OKX wallet, and also different browsers.
On Metamask, this error shows up:

The error doesn't go away after clearing cache and cookies.
Trust wallet meanwhile stays like this:

Ticket 216 on Intercom

@just-a-node For Chrome/Safari it works with Metamask. Do we still have this problem?

I don't think we have any new issues about this. Plus, mobile compatibility is something we need to specifically design for later.


forms in react added

Related Issue
Fixes #675
Description
added Forms in react in very depth
added these sections

Controlled component
select tag
textarea tag
input tag
handling multiple input
handling null
alternatives

Type of PR

[x] Feature enhancement
[x] Documentation update

Screenshots / Videos (if applicable)

[Attach any relevant screenshots or videos demonstrating the changes]
Checklist

[x] I have performed a self-review of my code.
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

Additional Context
[Include any additional information or context that might be helpful for reviewers.]
Resources for Guidance
Here are some resources that may be helpful as you contribute to CodeHarborHub:

Code Harbor Hub Community Features
Docusaurus Documentation
React.js Documentation
Markdown Guide
MDX Documentation
Mermaid Documentation

Resources for DSA Features on Our Site:

Tabs: Switch Languages
Line Numbering
Math Equations

@Ajay-Dhangar
done forms in react
also i think you forget to add labels in my merged PR
can you please add it
https://github.com/CodeHarborHub/codeharborhub.github.io/pull/662


Add option to disable automatic reporting of queue depth metrics

Problem
The current approach for most sidekiq metrics is to report them when a job is processed. While this is good for some metrics is less than ideal for others. If you want to monitor the status of your queues you will need queue size and queue latency metrics even when no jobs are being processed. With the current approach that is not possible so we cannot set alerts when the queues are not being consumed.
Solution
We have to disable the automatic reporting of queue size and latency metrics during the processing of a job and also add a new way of reporting this metric that doesn't depend on sidekiq actually working.
For that purpose I added a configuration attribute to manually disable queue depth metrics (size and latency). I also added a method that will report the status of all queues when it's called. That method should be called by a clock process in the main app

Both comments addressed @pipt

Pinging @timminkov to be in the loop of this change

👍


Updated README.md

Fixes Issue#7.

Hey @Archi-shaw  your PR contains some changes in package-lock.json file, create a new branch & just change the README.md file or while adding just do "git add change_file_name". Also add screenshot of what did change in README.md.  Rest of all is fine. Do the neccessary changes I will merge your PR !!!

Note : While creating PR mention me @PratikMane0112 about it in comment. So, I can quickly look over your PR.


Add kml:Orientation

Changes:
Add Orientation struct.
Add reader and writer for Orientation.
closes #5

Rebased, ready for reviews


No Coverage report available

VSTS Extension you are using
Pester
Where are you running it?
VSTS
Version of Extension/Task
current public - 6.*
Expected behaviour and actual behaviour
Now #209  is fixed (thanks) and I can see coverage in the console for my .psm1 files I want to display the report in the VSTS interface but there is no html report generated.
I can see from the build log that coverage ran:
Tests Passed: 39,
Failed: 0,
Skipped: 0,
Pending: 0,
Inconclusive: 0
Code coverage report:
Covered 21.20 % of 500 analyzed Commands in 13 Files.
Missed commands:
File                                                    Function
----                                                    --------
builds\common\Push-ToArtifactory.ps1
builds\common\VSTSPowershellUtils-Build.psm1            Read-MavenVersions

And coverage-pester.xml gets generated.
Then when the publish code coverage task runs I can see this in the build logs:
2018-01-11T17:15:53.0706319Z Reading code coverage summary from 'F:\vstsAgents\pr\int-ss\_work\1\s\Coverage-Pester.XML'
2018-01-11T17:15:53.4596319Z ##[section]Async Command Start: Publish code coverage
2018-01-11T17:15:53.4596319Z Publishing coverage summary data to TFS server.
2018-01-11T17:15:53.4596319Z  Instruction- 106 of 500 covered.
2018-01-11T17:15:53.4596319Z  Line- 82 of 419 covered.
2018-01-11T17:15:53.4596319Z  Method- 11 of 43 covered.
2018-01-11T17:15:53.4596319Z  Class- 2 of 13 covered.
2018-01-11T17:15:53.9716319Z Modifying Cobertura Index file
2018-01-11T17:15:53.9716319Z Publishing code coverage files to TFS server.
2018-01-11T17:15:54.4856319Z Uploading 1 files
2018-01-11T17:15:54.7376319Z File upload succeed.
2018-01-11T17:15:54.7386319Z Published 'F:\vstsAgents\pr\int-ss\_work\_temp\Code Coverage Report_2236' as artifact 'Code Coverage Report_2236'

But when I click on the code coverage tab I see this message
Code coverage data cannot be displayed. Please verify that a valid directory containing code coverage files, including an index.html was used to publish data.
I don't even see the summary data. I don't know if this is an issue with pester itself, with the plugin or perhaps with vsts displaying jacoco reports...
Steps to reproduce the problem
Create a VSTS build with a pester task:

And then publish code coverage:

Then run a build and click on the code coverage tab.

I potential alternative solution has been suggested via the extensions Q&A page on the market place

Would you consider adding option for exporting report results with ReportUnit? I've found the beautifully formatted report on test results very nice to use, and would be a useful optional export format from the test xml that is generated.
If not, a custom powershell script probably could run and do the same thing, but might be an option you and others would benefit from. Github link: https://github.com/reportunit/reportunit
I use command similar to Start-Process "C:\packages\ReportUnit.1.5.0-beta1\tools\ReportUnit.exe" -ArgumentList '"C:\temp.pester" "C:\temp.pester"' and the result from the folder contents is a beautiful interactive report.

Seems a viable suggestion to investigate


[fix](regression test) fix test_schema_change_cold_heat case

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Support custom wrappers

This feature enables custom elements and components for the container element wrapping the video(s).  It accepts either a string or a component.
const CustomWrapper = ({ children, ...props ) => <div {...props}>{children}</div>

<ReactPlayer url={url} as={CustomWrapper} />

Thanks for the PR @nathanforce! I've renamed the prop to wrapper to make it a bit clearer when taken out of context. Nice work 👍

@CookPete Thanks!  Any idea when this will be published?

I'll cut a new minor release once I've cleared up the open issues, which also include some new functionality. Will be later today or tomorrow.

Published in 1.2.0 🎉


[Issue] A bug hide in here.

Describe the bug
0 division bug can occur
Project Version (please complete the following information):

Version v0.4

Operating System (please complete the following information):

Name: Ventura (but this doesn't matter)
Version 13.3

Device (please complete the following information):

Model: 2021 MBP 16 (this also doesn't matter)
CPU: Apple M1 Pro

Additional context
https://github.com/BitesPotatoBacks/SocPowerBuddy/blob/b899acef74cdb87a7d36f6a9df95063cc72b6315/SocPowerBuddy/sampler.m#L279
In sampler.m line 279, [vd->core_use[i][iii] floatValue] / ([vd->core_sums[i][iii] floatValue] + [vd->core_use[i][iii] floatValue]).
This can occur 0 division bug. But this bug hide in 0% usage. I find this bug when I closed my macbook display while running my neoasitop.

@op06072 i Currently don’t have access to my Apple Silicon machine but I will fix this when I patch #8 👍


Typo in example

https://github.com/MicrosoftDocs/pipelines-python-django/blob/master/azure-pipelines.acr.yml#L52

Thanks for fixing!


One-way transfer from PL to PS

Hi,
I'm trying to transfer data from PL to PS using the AXI DMA IP (with SG) using this xilinx_axidma driver.
The first test I did is the loopback test. For this test, I've connected the M_AXIS_MM2S port of the DMA to the slave ports of a AXI-stream FIFO. The master ports of the AXI-stream FIFO are then connected to the S_AXIS_S2MM port of the DMA.
The loopback test was successful as I'm able to transfer data from PS to PL and read back the same data from PL to PS. Here is the ILA waveform for this test:

The next test I did is to just transfer data from PL to PS as this is what I needed in my design. For this, I only have the connection between the master ports of the AXI-stream FIFO and the S_AXIS_S2MM port of the DMA. The data generation in the PL is controlled from the PS and the generated data in PL is then written to the FIFO through the slave ports of the AXI-stream FIFO. However, I observed the problem where the s_axis_s2mm_tready line remaining low after the first 4 transfers (see ILA waveform below). For this test, I'm using the axidma_oneway_transfer() function call instead of the axidma_twoway_transfer() function call.

As a result, I couldn't get any subsequent transfers and the DMA transfer eventually timeout with the following error:
Failed to perform the AXI DMA transfer: Timer expired
I also got the following kernel error message:
axidma: axidma_dma.c: axidma_start_transfer: 301: DMA receive transaction timed out.
Has anyone encounter this issue before?
If anyone had success with one-way transfer from PL to PS using this driver, it'll be appreciated if you can share how you did it.
Thanks in advance.

I have same issue, in pl before dma initialization give data to dma and then it exit synchronisation (according to tlast)

@eric950722  I have same issue. Have you solved the problem yet?


Improve documentation and error messages when adding fields for facetting which contain unsuitable data

I tried to configure some attributes_for_faceting on an existing index by "brute force", i.e. just taking all existing fields and configuring them and see if it raises an error.
I'm using server version 0.16 installed using brew on mac. I was using the meilisearch-ruby client 0.14.0, but I think the specific client is not relevant here.
Case 1: Invalid attribute type mentions attribute value but not field name
Output was of index.get_all_update_status was
  ...
  "error"=>"error processing facet filter: invalid document attribute 2, accepted types: String and [String]",
  "errorType"=>"invalid_request_error",
  "errorCode"=>"invalid_facet",
  "errorLink"=>"https://docs.meilisearch.com/errors#invalid_facet",
  ...

Solution I'd like: Please also mention the attribute name and not only the field value which caused the error.
Case 2: Internal error instead of specific error
  "error"=>"heed error; MDB_BAD_VALSIZE: Unsupported size of key/DB name/data, or wrong DUPFIXED size",
  "errorType"=>"internal_error",
  "errorCode"=>"internal",
  "errorLink"=>"https://docs.meilisearch.com/errors#internal",

I'm still in progress of investigating what the specific case is, but in Slack, @Kerollmops hinted at a possible limit of 512 bytes for facet values.
Solutions:

Add limitations in value size to the facet documentation
Raise invalid_facet error instead of internal

maybe solved by this: provide the invalid value
maybe solved by this and solution for case 1 above: provide the invalid field

Thanks a lot @bb, for this very detailed report. You are right those points need to be addressed, I will create the relevant issues so this gets done 👍

closing in favor of #1071 and #1072


Support streaming parquet from lazy DF to S3

Main issue: https://github.com/elixir-explorer/explorer/issues/705

I chose to open just the Parquet version first, because I encounter a problem with the IPC cloud writer (it's panicking).


Added files for pwned or not

Description
The python script helps users to know if their passwords were ever part of a data breach, and thus helping them stay aware and change their passwords accordingly
Fixes #931
Replace issue_no with the issue number which is fixed in this PR
Have you read the Contributing Guidelines on Pull Requests?

[x] Yes
[ ] No

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update
[ ] Documentation Update

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have created a helpful and easy to understand README.md
[x] I have commented my code, particularly in hard-to-understand areas
[x] My documentation follows Template for README.md
[x] My changes generate no new warnings
[x] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works.

@RohiniRG your code is working fine, just add a button to hide/show password.

@RohiniRG your code is working fine, just add a button to hide/show password.

@santushtisharma10 I'm not really getting how to do this, although I tried it. Could you please provide a reference or alternative as to how to do this?

@santushtisharma10 @kaustubhgupta I figured out the hide/show password. Please let me know if the changes are fine.


created requirements.txt

created requirements.txt but there is some error in importing from utils

I can't see the contents of the requirements.txt file.


--editor option does not work for post command

On windows, at least, the post command doesn't accept the -e or --editor options, however, or at least I can't get it to work.
jekyll 3.1.3 | Error: Whoops, we can't understand your command.
jekyll 3.1.3 | Error: invalid option: -e
jekyll 3.1.3 | Error: Run your command again with the --help switch to see available options.

--help isn't very...helpful.
From https://talk.jekyllrb.com/t/a-tool-for-automatic-browser-refreshes/2150#post_3

Appears to not be a Windows specific issue.  Looks like just a bug on my part. :scream:

As noted in the talk discussion, 2.0.2 fixes -e but not --editor. For my purposes this is sufficient, but if --editor should work then this might need to be reopened.

Strange. --editor is working for me.  I wonder if this is actually a Windows issue with the double hyphen options not being recognized.  Does jekyll post --help work?
Also could you post the entire command you're running with --editor and the subsequent output?
Here's what I get (and gedit opens the appropriate file)
% jekyll post --editor gedit Hello
Configuration file: /home/awood/devel/website/_config.yml
Wrote /home/awood/devel/website/_posts/2016-05-16-hello.md


A new action temporally blocks the previous action until the selected object is dropped

The visible behaviour:
When an action occurs, like moving to a player, another action can temporarily block it until the selected object for the action is dropped manually.
https://user-images.githubusercontent.com/3787206/119730008-8d89c700-be75-11eb-8c92-11f00e66e6b8.mp4
The anticipated behaviour:
A new action should entirley cancel and override the previous action.

@quepas this should be resolved in #145
You can check it here: https://the-game-staging.herokuapp.com/


[Enhancement] speed up trash sweep

What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Currently, when the disk water level is high, the sweeper thread removes the trash directory files to reclaim disk space, but the sweeper thread sleeps too long, the default value ranges from 3 minutes to 1 hour, which could cause data GC to be delayed when the critical water level is reached.
This PR ensures that the sweeper thread is awakened in time when the critical disk water level is reached. At the same time the original behavior of the sweeper thread is preserved.
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

run starrocks_be_unittest

run starrocks_admit_test

@Mergifyio backport branch-2.4  branch-2.3  branch-2.2


dispatch duration as part of RESOURCE_RECEIVED and RESOURCE_ERROR

Pulled this down locally and all looks good to me! Thanks!