[provider] pending ghost deployments causing insufficient resources

Have tried akash 0.14.0 and 0.14.1-rc6.
Provider: akash1nxq8gmsw2vlz3m68qvyvcf3kh6q269ajvqw6y0
Having 0 active leases, 0 open bids
$ akash query market lease list --provider akash1nxq8gmsw2vlz3m68qvyvcf3kh6q269ajvqw6y0 --page 1 --limit 100 -o json --state active
{"leases":[],"pagination":{"next_key":null,"total":"0"}}

$ akash query market bid list --provider akash1nxq8gmsw2vlz3m68qvyvcf3kh6q269ajvqw6y0 --page 1 --limit 100 -o json --state open
{"bids":[],"pagination":{"next_key":null,"total":"0"}}

made sure to clean manifests (just in case)
# kubectl get providerhosts -A
No resources found
# kubectl -n lease get manifest
No resources found in lease namespace.
# systemctl restart akash-provider

20 pending deployments ...
pstats.sh script from https://gist.github.com/arno01/db7199a08d8bcf5d921122fb881cd480
$ pstats.sh https://akash-provider.nixaid.com:8443
host                                    num  num-p  cpu  cpu-a  cpu-p  mem  mem-a    mem-p  fs  fs-a     fs-p
https://akash-provider.nixaid.com:8443  0    20     0    26.05  17.7   0    68.9595  33.75  0   1578.54  87.625

Akash provider logs
akash-provider.log
These are the 20 ghosts, I think:
root@akash-master-01:~# cat akash-provider.log | grep 'reservation requested' | cut -f5 -d=
akash10th527knwhvx8x085lw9uxxv9wmlzxf44y7n57/3328818/1/1 resources
akash15ljdqcqzhzzqg0t9320k7h90xl4wqghe3403zh/2451225/1/1 resources
akash15yd3qszmqausvzpj7n0y0e4pft2cu9rt5gccda/1346631/1/1 resources
akash14s4tlmlvy0vsps05csf8l80m7nqxmau38tehp9/3299297/1/1 resources
akash15yd3qszmqausvzpj7n0y0e4pft2cu9rt5gccda/1598194/1/1 resources
akash15yd3qszmqausvzpj7n0y0e4pft2cu9rt5gccda/1842661/1/1 resources
akash1fnc04mjln6y0y7qgkkz9nwkjane50nnjxq32yf/2885243/1/2 resources
akash14s4tlmlvy0vsps05csf8l80m7nqxmau38tehp9/3021227/1/1 resources
akash14s4tlmlvy0vsps05csf8l80m7nqxmau38tehp9/2805762/1/1 resources
akash14s4tlmlvy0vsps05csf8l80m7nqxmau38tehp9/2778040/1/1 resources
akash14s4tlmlvy0vsps05csf8l80m7nqxmau38tehp9/3202496/1/1 resources
akash15egam89a3qruarxh3xe24fuuadea0ajre85meh/2872733/1/1 resources
akash1fnc04mjln6y0y7qgkkz9nwkjane50nnjxq32yf/2779907/1/2 resources
akash15egam89a3qruarxh3xe24fuuadea0ajre85meh/1965165/1/1 resources
akash15egam89a3qruarxh3xe24fuuadea0ajre85meh/3292664/1/1 resources
akash14s4tlmlvy0vsps05csf8l80m7nqxmau38tehp9/2805770/1/1 resources
akash14s4tlmlvy0vsps05csf8l80m7nqxmau38tehp9/3289647/1/1 resources
akash19v0usdgaglcaqp2xp873q0s0t76dra4fhh6ust/3299391/1/1 resources
akash19v0usdgaglcaqp2xp873q0s0t76dra4fhh6ust/3299325/1/1 resources
akash1e4nlht6dfvet0sjyfktse7cqvjdwucg27jy3wz/3275704/1/1 resources

root@akash-master-01:~# cat akash-provider.log | grep 'reservation requested' | cut -f5 -d= |wc -l
20

additional info
# kubectl -n akash-services describe pod $(kubectl -n akash-services get pods -l app=akash-hostname-operator -o jsonpath='{.items[0].metadata.name}') | grep Image
    Image:         ghcr.io/ovrclk/akash:0.14.1-rc6
    Image ID:      ghcr.io/ovrclk/akash@sha256:7dc73136e05c351a193432b837615ef0b6bb88601e81a277dae4c41702b736f8
root@akash-master-01:~#

root@akash-master-01:~# kubectl get nodes -o wide
NAME                         STATUS   ROLES                  AGE     VERSION   INTERNAL-IP      EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION     CONTAINER-RUNTIME
akash-master-01.nixaid.com   Ready    control-plane,master   3d22h   v1.22.3   <IP_ADDRESS>    <none>        Ubuntu 20.04.3 LTS   5.4.0-89-generic   containerd://1.5.7
akash-master-02.nixaid.com   Ready    control-plane,master   3d22h   v1.22.3   <IP_ADDRESS>    <none>        Ubuntu 20.04.3 LTS   5.4.0-89-generic   containerd://1.5.7
akash-master-03.nixaid.com   Ready    control-plane,master   3d22h   v1.22.3   <IP_ADDRESS>     <none>        Ubuntu 20.04.3 LTS   5.4.0-89-generic   containerd://1.5.7
akash-worker-01.nixaid.com   Ready    <none>                 3d21h   v1.22.3   <IP_ADDRESS>     <none>        Ubuntu 20.04.3 LTS   5.4.0-89-generic   containerd://1.5.7
akash-worker-02.nixaid.com   Ready    <none>                 29h     v1.22.3   <IP_ADDRESS>     <none>        Ubuntu 20.04.3 LTS   5.4.0-89-generic   containerd://1.5.7
akash-worker-03.nixaid.com   Ready    <none>                 17h     v1.22.3   <IP_ADDRESS>   <none>        Ubuntu 20.04.3 LTS   5.4.0-89-generic   containerd://1.5.7

kubectl describe nodes
root@akash-master-01:~# kubectl describe nodes
Name:               akash-master-01.nixaid.com
Roles:              control-plane,master
Labels:             beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/os=linux
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=akash-master-01.nixaid.com
                    kubernetes.io/os=linux
                    node-role.kubernetes.io/control-plane=
                    node-role.kubernetes.io/master=
                    node.kubernetes.io/exclude-from-external-load-balancers=
Annotations:        kubeadm.alpha.kubernetes.io/cri-socket: unix:///run/containerd/containerd.sock
                    node.alpha.kubernetes.io/ttl: 0
                    projectcalico.org/IPv4Address: <IP_ADDRESS>/32
                    projectcalico.org/IPv4IPIPTunnelAddr: <IP_ADDRESS>
                    volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Sat, 30 Oct 2021 21:36:48 +0200
Taints:             node-role.kubernetes.io/master:NoSchedule
Unschedulable:      false
Lease:
  HolderIdentity:  akash-master-01.nixaid.com
  AcquireTime:     <unset>
  RenewTime:       Wed, 03 Nov 2021 18:53:01 +0100
Conditions:
  Type                 Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----                 ------  -----------------                 ------------------                ------                       -------
  NetworkUnavailable   False   Sat, 30 Oct 2021 21:52:03 +0200   Sat, 30 Oct 2021 21:52:03 +0200   CalicoIsUp                   Calico is running on this node
  MemoryPressure       False   Wed, 03 Nov 2021 18:52:49 +0100   Sat, 30 Oct 2021 21:36:43 +0200   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure         False   Wed, 03 Nov 2021 18:52:49 +0100   Sat, 30 Oct 2021 21:36:43 +0200   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure          False   Wed, 03 Nov 2021 18:52:49 +0100   Sat, 30 Oct 2021 21:36:43 +0200   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready                True    Wed, 03 Nov 2021 18:52:49 +0100   Sat, 30 Oct 2021 21:37:06 +0200   KubeletReady                 kubelet is posting ready status. AppArmor enabled
Addresses:
  InternalIP:  <IP_ADDRESS>
  Hostname:    akash-master-01.nixaid.com
Capacity:
  cpu:                4
  ephemeral-storage:  203310184Ki
  hugepages-1Gi:      0
  hugepages-2Mi:      0
  memory:             8152720Ki
  pods:               110
Allocatable:
  cpu:                4
  ephemeral-storage:<PHONE_NUMBER>65
  hugepages-1Gi:      0
  hugepages-2Mi:      0
  memory:             8050320Ki
  pods:               110
System Info:
  Machine ID:                 86a903cccac0598ed9c92e55fca2efd8
  System UUID:                f1bd9f1c-0750-4291-b02b-4faf1a3aebc6
  Boot ID:                    3438790a-9029-4634-8c95-0d3036bb9167
  Kernel Version:             5.4.0-89-generic
  OS Image:                   Ubuntu 20.04.3 LTS
  Operating System:           linux
  Architecture:               amd64
  Container Runtime Version:  containerd://1.5.7
  Kubelet Version:            v1.22.3
  Kube-Proxy Version:         v1.22.3
PodCIDR:                      <IP_ADDRESS>/24
PodCIDRs:                     <IP_ADDRESS>/24
Non-terminated Pods:          (9 in total)
  Namespace                   Name                                                  CPU Requests  CPU Limits  Memory Requests  Memory Limits  Age
  ---------                   ----                                                  ------------  ----------  ---------------  -------------  ---
  kube-system                 calico-kube-controllers-75f8f6cc59-zncsv              0 (0%)        0 (0%)      0 (0%)           0 (0%)         3d22h
  kube-system                 calico-node-8n5q8                                     250m (6%)     0 (0%)      0 (0%)           0 (0%)         3d22h
  kube-system                 coredns-78fcd69978-85qgm                              100m (2%)     0 (0%)      70Mi (0%)        170Mi (2%)     3d22h
  kube-system                 coredns-78fcd69978-r78dz                              100m (2%)     0 (0%)      70Mi (0%)        170Mi (2%)     3d22h
  kube-system                 etcd-akash-master-01.nixaid.com                       100m (2%)     0 (0%)      100Mi (1%)       0 (0%)         3d22h
  kube-system                 kube-apiserver-akash-master-01.nixaid.com             250m (6%)     0 (0%)      0 (0%)           0 (0%)         3d22h
  kube-system                 kube-controller-manager-akash-master-01.nixaid.com    200m (5%)     0 (0%)      0 (0%)           0 (0%)         3d22h
  kube-system                 kube-proxy-nw2vs                                      0 (0%)        0 (0%)      0 (0%)           0 (0%)         3d22h
  kube-system                 kube-scheduler-akash-master-01.nixaid.com             100m (2%)     0 (0%)      0 (0%)           0 (0%)         3d22h
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource           Requests     Limits
  --------           --------     ------
  cpu                1100m (27%)  0 (0%)
  memory             240Mi (3%)   340Mi (4%)
  ephemeral-storage  0 (0%)       0 (0%)
  hugepages-1Gi      0 (0%)       0 (0%)
  hugepages-2Mi      0 (0%)       0 (0%)
Events:              <none>

Name:               akash-master-02.nixaid.com
Roles:              control-plane,master
Labels:             beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/os=linux
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=akash-master-02.nixaid.com
                    kubernetes.io/os=linux
                    node-role.kubernetes.io/control-plane=
                    node-role.kubernetes.io/master=
                    node.kubernetes.io/exclude-from-external-load-balancers=
Annotations:        kubeadm.alpha.kubernetes.io/cri-socket: /run/containerd/containerd.sock
                    node.alpha.kubernetes.io/ttl: 0
                    projectcalico.org/IPv4Address: <IP_ADDRESS>/32
                    projectcalico.org/IPv4IPIPTunnelAddr: <IP_ADDRESS>
                    volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Sat, 30 Oct 2021 21:37:42 +0200
Taints:             node-role.kubernetes.io/master:NoSchedule
Unschedulable:      false
Lease:
  HolderIdentity:  akash-master-02.nixaid.com
  AcquireTime:     <unset>
  RenewTime:       Wed, 03 Nov 2021 18:53:10 +0100
Conditions:
  Type                 Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----                 ------  -----------------                 ------------------                ------                       -------
  NetworkUnavailable   False   Sat, 30 Oct 2021 21:52:00 +0200   Sat, 30 Oct 2021 21:52:00 +0200   CalicoIsUp                   Calico is running on this node
  MemoryPressure       False   Wed, 03 Nov 2021 18:49:28 +0100   Sat, 30 Oct 2021 21:37:42 +0200   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure         False   Wed, 03 Nov 2021 18:49:28 +0100   Sat, 30 Oct 2021 21:37:42 +0200   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure          False   Wed, 03 Nov 2021 18:49:28 +0100   Sat, 30 Oct 2021 21:37:42 +0200   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready                True    Wed, 03 Nov 2021 18:49:28 +0100   Sat, 30 Oct 2021 21:37:55 +0200   KubeletReady                 kubelet is posting ready status. AppArmor enabled
Addresses:
  InternalIP:  <IP_ADDRESS>
  Hostname:    akash-master-02.nixaid.com
Capacity:
  cpu:                4
  ephemeral-storage:  203310184Ki
  hugepages-1Gi:      0
  hugepages-2Mi:      0
  memory:             8152716Ki
  pods:               110
Allocatable:
  cpu:                4
  ephemeral-storage:<PHONE_NUMBER>65
  hugepages-1Gi:      0
  hugepages-2Mi:      0
  memory:             8050316Ki
  pods:               110
System Info:
  Machine ID:                 86a903cccac0598ed9c92e55fca2efd8
  System UUID:                0960bc6d-da2d-4256-ac48-a87d9c0e80af
  Boot ID:                    4d062992-de01-42dc-b2de-b82850337bee
  Kernel Version:             5.4.0-89-generic
  OS Image:                   Ubuntu 20.04.3 LTS
  Operating System:           linux
  Architecture:               amd64
  Container Runtime Version:  containerd://1.5.7
  Kubelet Version:            v1.22.3
  Kube-Proxy Version:         v1.22.3
PodCIDR:                      <IP_ADDRESS>/24
PodCIDRs:                     <IP_ADDRESS>/24
Non-terminated Pods:          (6 in total)
  Namespace                   Name                                                  CPU Requests  CPU Limits  Memory Requests  Memory Limits  Age
  ---------                   ----                                                  ------------  ----------  ---------------  -------------  ---
  kube-system                 calico-node-lr98d                                     250m (6%)     0 (0%)      0 (0%)           0 (0%)         3d22h
  kube-system                 etcd-akash-master-02.nixaid.com                       100m (2%)     0 (0%)      100Mi (1%)       0 (0%)         3d22h
  kube-system                 kube-apiserver-akash-master-02.nixaid.com             250m (6%)     0 (0%)      0 (0%)           0 (0%)         3d22h
  kube-system                 kube-controller-manager-akash-master-02.nixaid.com    200m (5%)     0 (0%)      0 (0%)           0 (0%)         3d22h
  kube-system                 kube-proxy-js2rj                                      0 (0%)        0 (0%)      0 (0%)           0 (0%)         3d22h
  kube-system                 kube-scheduler-akash-master-02.nixaid.com             100m (2%)     0 (0%)      0 (0%)           0 (0%)         3d22h
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource           Requests    Limits
  --------           --------    ------
  cpu                900m (22%)  0 (0%)
  memory             100Mi (1%)  0 (0%)
  ephemeral-storage  0 (0%)      0 (0%)
  hugepages-1Gi      0 (0%)      0 (0%)
  hugepages-2Mi      0 (0%)      0 (0%)
Events:              <none>

Name:               akash-master-03.nixaid.com
Roles:              control-plane,master
Labels:             beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/os=linux
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=akash-master-03.nixaid.com
                    kubernetes.io/os=linux
                    node-role.kubernetes.io/control-plane=
                    node-role.kubernetes.io/master=
                    node.kubernetes.io/exclude-from-external-load-balancers=
Annotations:        kubeadm.alpha.kubernetes.io/cri-socket: /run/containerd/containerd.sock
                    node.alpha.kubernetes.io/ttl: 0
                    projectcalico.org/IPv4Address: <IP_ADDRESS>/32
                    projectcalico.org/IPv4IPIPTunnelAddr: <IP_ADDRESS>
                    volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Sat, 30 Oct 2021 21:41:09 +0200
Taints:             node-role.kubernetes.io/master:NoSchedule
Unschedulable:      false
Lease:
  HolderIdentity:  akash-master-03.nixaid.com
  AcquireTime:     <unset>
  RenewTime:       Wed, 03 Nov 2021 18:53:02 +0100
Conditions:
  Type                 Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----                 ------  -----------------                 ------------------                ------                       -------
  NetworkUnavailable   False   Sun, 31 Oct 2021 07:06:42 +0100   Sun, 31 Oct 2021 07:06:42 +0100   CalicoIsUp                   Calico is running on this node
  MemoryPressure       False   Wed, 03 Nov 2021 18:52:13 +0100   Sun, 31 Oct 2021 07:06:34 +0100   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure         False   Wed, 03 Nov 2021 18:52:13 +0100   Sun, 31 Oct 2021 07:06:34 +0100   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure          False   Wed, 03 Nov 2021 18:52:13 +0100   Sun, 31 Oct 2021 07:06:34 +0100   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready                True    Wed, 03 Nov 2021 18:52:13 +0100   Sun, 31 Oct 2021 07:06:44 +0100   KubeletReady                 kubelet is posting ready status. AppArmor enabled
Addresses:
  InternalIP:  <IP_ADDRESS>
  Hostname:    akash-master-03.nixaid.com
Capacity:
  cpu:                4
  ephemeral-storage:  203310184Ki
  hugepages-1Gi:      0
  hugepages-2Mi:      0
  memory:             8152716Ki
  pods:               110
Allocatable:
  cpu:                4
  ephemeral-storage:<PHONE_NUMBER>65
  hugepages-1Gi:      0
  hugepages-2Mi:      0
  memory:             8050316Ki
  pods:               110
System Info:
  Machine ID:                 86a903cccac0598ed9c92e55fca2efd8
  System UUID:                b170a347-1ffb-4cde-adf0-7988914fea3d
  Boot ID:                    9ec21fac-d36d-415e-8e63-88d6c97a9a7e
  Kernel Version:             5.4.0-89-generic
  OS Image:                   Ubuntu 20.04.3 LTS
  Operating System:           linux
  Architecture:               amd64
  Container Runtime Version:  containerd://1.5.7
  Kubelet Version:            v1.22.3
  Kube-Proxy Version:         v1.22.3
PodCIDR:                      <IP_ADDRESS>/24
PodCIDRs:                     <IP_ADDRESS>/24
Non-terminated Pods:          (6 in total)
  Namespace                   Name                                                  CPU Requests  CPU Limits  Memory Requests  Memory Limits  Age
  ---------                   ----                                                  ------------  ----------  ---------------  -------------  ---
  kube-system                 calico-node-fg6b6                                     250m (6%)     0 (0%)      0 (0%)           0 (0%)         3d22h
  kube-system                 etcd-akash-master-03.nixaid.com                       100m (2%)     0 (0%)      100Mi (1%)       0 (0%)         3d22h
  kube-system                 kube-apiserver-akash-master-03.nixaid.com             250m (6%)     0 (0%)      0 (0%)           0 (0%)         3d22h
  kube-system                 kube-controller-manager-akash-master-03.nixaid.com    200m (5%)     0 (0%)      0 (0%)           0 (0%)         3d22h
  kube-system                 kube-proxy-n5fxr                                      0 (0%)        0 (0%)      0 (0%)           0 (0%)         3d22h
  kube-system                 kube-scheduler-akash-master-03.nixaid.com             100m (2%)     0 (0%)      0 (0%)           0 (0%)         3d22h
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource           Requests    Limits
  --------           --------    ------
  cpu                900m (22%)  0 (0%)
  memory             100Mi (1%)  0 (0%)
  ephemeral-storage  0 (0%)      0 (0%)
  hugepages-1Gi      0 (0%)      0 (0%)
  hugepages-2Mi      0 (0%)      0 (0%)
Events:              <none>

Name:               akash-worker-01.nixaid.com
Roles:              <none>
Labels:             akash.network/role=ingress
                    beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/os=linux
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=akash-worker-01.nixaid.com
                    kubernetes.io/os=linux
Annotations:        kubeadm.alpha.kubernetes.io/cri-socket: /run/containerd/containerd.sock
                    node.alpha.kubernetes.io/ttl: 0
                    projectcalico.org/IPv4Address: <IP_ADDRESS>/32
                    projectcalico.org/IPv4IPIPTunnelAddr: <IP_ADDRESS>
                    volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Sat, 30 Oct 2021 22:27:05 +0200
Taints:             <none>
Unschedulable:      false
Lease:
  HolderIdentity:  akash-worker-01.nixaid.com
  AcquireTime:     <unset>
  RenewTime:       Wed, 03 Nov 2021 18:53:00 +0100
Conditions:
  Type                 Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----                 ------  -----------------                 ------------------                ------                       -------
  NetworkUnavailable   False   Sat, 30 Oct 2021 22:27:58 +0200   Sat, 30 Oct 2021 22:27:58 +0200   CalicoIsUp                   Calico is running on this node
  MemoryPressure       False   Wed, 03 Nov 2021 18:52:58 +0100   Sat, 30 Oct 2021 22:27:05 +0200   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure         False   Wed, 03 Nov 2021 18:52:58 +0100   Sat, 30 Oct 2021 22:27:05 +0200   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure          False   Wed, 03 Nov 2021 18:52:58 +0100   Sat, 30 Oct 2021 22:27:05 +0200   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready                True    Wed, 03 Nov 2021 18:52:58 +0100   Sat, 30 Oct 2021 22:27:46 +0200   KubeletReady                 kubelet is posting ready status. AppArmor enabled
Addresses:
  InternalIP:  <IP_ADDRESS>
  Hostname:    akash-worker-01.nixaid.com
Capacity:
  cpu:                6
  ephemeral-storage:  409733672Ki
  hugepages-1Gi:      0
  hugepages-2Mi:      0
  memory:             16397520Ki
  pods:               110
Allocatable:
  cpu:                6
  ephemeral-storage:<PHONE_NUMBER>90
  hugepages-1Gi:      0
  hugepages-2Mi:      0
  memory:             16295120Ki
  pods:               110
System Info:
  Machine ID:                 86a903cccac0598ed9c92e55fca2efd8
  System UUID:                a9b8cf06-6f81-40e0-8c46-81e8c35bad44
  Boot ID:                    e12ce24b-9ab8-4228-a4ea-9de7bec7be29
  Kernel Version:             5.4.0-89-generic
  OS Image:                   Ubuntu 20.04.3 LTS
  Operating System:           linux
  Architecture:               amd64
  Container Runtime Version:  containerd://1.5.7
  Kubelet Version:            v1.22.3
  Kube-Proxy Version:         v1.22.3
PodCIDR:                      <IP_ADDRESS>/24
PodCIDRs:                     <IP_ADDRESS>/24
Non-terminated Pods:          (6 in total)
  Namespace                   Name                                         CPU Requests  CPU Limits  Memory Requests  Memory Limits  Age
  ---------                   ----                                         ------------  ----------  ---------------  -------------  ---
  cert-manager                cert-manager-55658cdf68-qz9wc                0 (0%)        0 (0%)      0 (0%)           0 (0%)         44h
  cert-manager                cert-manager-cainjector-967788869-6rchj      0 (0%)        0 (0%)      0 (0%)           0 (0%)         44h
  cert-manager                cert-manager-webhook-6668fbb57d-m8kf5        0 (0%)        0 (0%)      0 (0%)           0 (0%)         44h
  ingress-nginx               ingress-nginx-controller-6b4b785659-6b6lj    100m (1%)     0 (0%)      90Mi (0%)        0 (0%)         3d21h
  kube-system                 calico-node-s5plx                            250m (4%)     0 (0%)      0 (0%)           0 (0%)         3d21h
  kube-system                 kube-proxy-5n68c                             0 (0%)        0 (0%)      0 (0%)           0 (0%)         3d21h
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource           Requests   Limits
  --------           --------   ------
  cpu                350m (5%)  0 (0%)
  memory             90Mi (0%)  0 (0%)
  ephemeral-storage  0 (0%)     0 (0%)
  hugepages-1Gi      0 (0%)     0 (0%)
  hugepages-2Mi      0 (0%)     0 (0%)
Events:              <none>

Name:               akash-worker-02.nixaid.com
Roles:              <none>
Labels:             akash.network/role=ingress
                    beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/os=linux
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=akash-worker-02.nixaid.com
                    kubernetes.io/os=linux
Annotations:        kubeadm.alpha.kubernetes.io/cri-socket: /run/containerd/containerd.sock
                    node.alpha.kubernetes.io/ttl: 0
                    projectcalico.org/IPv4Address: <IP_ADDRESS>/32
                    projectcalico.org/IPv4IPIPTunnelAddr: <IP_ADDRESS>
                    volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Tue, 02 Nov 2021 13:34:54 +0100
Taints:             <none>
Unschedulable:      false
Lease:
  HolderIdentity:  akash-worker-02.nixaid.com
  AcquireTime:     <unset>
  RenewTime:       Wed, 03 Nov 2021 18:53:00 +0100
Conditions:
  Type                 Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----                 ------  -----------------                 ------------------                ------                       -------
  NetworkUnavailable   False   Tue, 02 Nov 2021 13:35:26 +0100   Tue, 02 Nov 2021 13:35:26 +0100   CalicoIsUp                   Calico is running on this node
  MemoryPressure       False   Wed, 03 Nov 2021 18:52:34 +0100   Tue, 02 Nov 2021 13:34:54 +0100   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure         False   Wed, 03 Nov 2021 18:52:34 +0100   Tue, 02 Nov 2021 13:34:54 +0100   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure          False   Wed, 03 Nov 2021 18:52:34 +0100   Tue, 02 Nov 2021 13:34:54 +0100   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready                True    Wed, 03 Nov 2021 18:52:34 +0100   Tue, 02 Nov 2021 13:35:14 +0100   KubeletReady                 kubelet is posting ready status. AppArmor enabled
Addresses:
  InternalIP:  <IP_ADDRESS>
  Hostname:    akash-worker-02.nixaid.com
Capacity:
  cpu:                6
  ephemeral-storage:  409733672Ki
  hugepages-1Gi:      0
  hugepages-2Mi:      0
  memory:             16397528Ki
  pods:               110
Allocatable:
  cpu:                6
  ephemeral-storage:<PHONE_NUMBER>90
  hugepages-1Gi:      0
  hugepages-2Mi:      0
  memory:             16295128Ki
  pods:               110
System Info:
  Machine ID:                 86a903cccac0598ed9c92e55fca2efd8
  System UUID:                ab1cc03e-8706-4c24-9020-ee785ca2df53
  Boot ID:                    247e4ff8-9f3e-465d-b240-1dfc4424f9e5
  Kernel Version:             5.4.0-89-generic
  OS Image:                   Ubuntu 20.04.3 LTS
  Operating System:           linux
  Architecture:               amd64
  Container Runtime Version:  containerd://1.5.7
  Kubelet Version:            v1.22.3
  Kube-Proxy Version:         v1.22.3
PodCIDR:                      <IP_ADDRESS>/24
PodCIDRs:                     <IP_ADDRESS>/24
Non-terminated Pods:          (4 in total)
  Namespace                   Name                                         CPU Requests  CPU Limits  Memory Requests  Memory Limits  Age
  ---------                   ----                                         ------------  ----------  ---------------  -------------  ---
  akash-services              akash-hostname-operator-7969d58c45-tlhds     0 (0%)        0 (0%)      0 (0%)           0 (0%)         19h
  ingress-nginx               ingress-nginx-controller-6b4b785659-6ppvb    100m (1%)     0 (0%)      90Mi (0%)        0 (0%)         28h
  kube-system                 calico-node-sjs4s                            250m (4%)     0 (0%)      0 (0%)           0 (0%)         29h
  kube-system                 kube-proxy-96k9l                             0 (0%)        0 (0%)      0 (0%)           0 (0%)         29h
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource           Requests   Limits
  --------           --------   ------
  cpu                350m (5%)  0 (0%)
  memory             90Mi (0%)  0 (0%)
  ephemeral-storage  0 (0%)     0 (0%)
  hugepages-1Gi      0 (0%)     0 (0%)
  hugepages-2Mi      0 (0%)     0 (0%)
Events:              <none>

Name:               akash-worker-03.nixaid.com
Roles:              <none>
Labels:             akash.network/role=ingress
                    beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/os=linux
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=akash-worker-03.nixaid.com
                    kubernetes.io/os=linux
Annotations:        kubeadm.alpha.kubernetes.io/cri-socket: /run/containerd/containerd.sock
                    node.alpha.kubernetes.io/ttl: 0
                    projectcalico.org/IPv4Address: <IP_ADDRESS>/32
                    projectcalico.org/IPv4IPIPTunnelAddr: <IP_ADDRESS>
                    volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Wed, 03 Nov 2021 01:49:38 +0100
Taints:             <none>
Unschedulable:      false
Lease:
  HolderIdentity:  akash-worker-03.nixaid.com
  AcquireTime:     <unset>
  RenewTime:       Wed, 03 Nov 2021 18:53:05 +0100
Conditions:
  Type                 Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----                 ------  -----------------                 ------------------                ------                       -------
  NetworkUnavailable   False   Wed, 03 Nov 2021 01:50:09 +0100   Wed, 03 Nov 2021 01:50:09 +0100   CalicoIsUp                   Calico is running on this node
  MemoryPressure       False   Wed, 03 Nov 2021 18:49:42 +0100   Wed, 03 Nov 2021 01:49:38 +0100   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure         False   Wed, 03 Nov 2021 18:49:42 +0100   Wed, 03 Nov 2021 01:49:38 +0100   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure          False   Wed, 03 Nov 2021 18:49:42 +0100   Wed, 03 Nov 2021 01:49:38 +0100   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready                True    Wed, 03 Nov 2021 18:49:42 +0100   Wed, 03 Nov 2021 01:49:58 +0100   KubeletReady                 kubelet is posting ready status. AppArmor enabled
Addresses:
  InternalIP:  <IP_ADDRESS>
  Hostname:    akash-worker-03.nixaid.com
Capacity:
  cpu:                6
  ephemeral-storage:  409733672Ki
  hugepages-1Gi:      0
  hugepages-2Mi:      0
  memory:             16397528Ki
  pods:               110
Allocatable:
  cpu:                6
  ephemeral-storage:<PHONE_NUMBER>90
  hugepages-1Gi:      0
  hugepages-2Mi:      0
  memory:             16295128Ki
  pods:               110
System Info:
  Machine ID:                 86a903cccac0598ed9c92e55fca2efd8
  System UUID:                727b9cec-962c-427e-ae8d-0d8da61b92c6
  Boot ID:                    bd1c21ba-3db8-4447-a23f-d60f45144adb
  Kernel Version:             5.4.0-89-generic
  OS Image:                   Ubuntu 20.04.3 LTS
  Operating System:           linux
  Architecture:               amd64
  Container Runtime Version:  containerd://1.5.7
  Kubelet Version:            v1.22.3
  Kube-Proxy Version:         v1.22.3
PodCIDR:                      <IP_ADDRESS>/24
PodCIDRs:                     <IP_ADDRESS>/24
Non-terminated Pods:          (3 in total)
  Namespace                   Name                                         CPU Requests  CPU Limits  Memory Requests  Memory Limits  Age
  ---------                   ----                                         ------------  ----------  ---------------  -------------  ---
  ingress-nginx               ingress-nginx-controller-6b4b785659-dr9dg    100m (1%)     0 (0%)      90Mi (0%)        0 (0%)         17h
  kube-system                 calico-node-tgg4l                            250m (4%)     0 (0%)      0 (0%)           0 (0%)         17h
  kube-system                 kube-proxy-hv82z                             0 (0%)        0 (0%)      0 (0%)           0 (0%)         17h
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource           Requests   Limits
  --------           --------   ------
  cpu                350m (5%)  0 (0%)
  memory             90Mi (0%)  0 (0%)
  ephemeral-storage  0 (0%)     0 (0%)
  hugepages-1Gi      0 (0%)     0 (0%)
  hugepages-2Mi      0 (0%)     0 (0%)
Events:              <none>

kubectl get ns & kubectl get pods -A -o wide
root@akash-master-01:~# kubectl get ns
NAME              STATUS   AGE
akash-services    Active   3d21h
cert-manager      Active   44h
default           Active   3d22h
ingress-nginx     Active   3d21h
kube-node-lease   Active   3d22h
kube-public       Active   3d22h
kube-system       Active   3d22h
lease             Active   3d20h

root@akash-master-01:~# kubectl get pods -A -o wide
NAMESPACE        NAME                                                 READY   STATUS      RESTARTS         AGE     IP               NODE                         NOMINATED NODE   READINESS GATES
akash-services   akash-hostname-operator-7969d58c45-tlhds             1/1     Running     0                19h     <IP_ADDRESS>    akash-worker-02.nixaid.com   <none>           <none>
cert-manager     cert-manager-55658cdf68-qz9wc                        1/1     Running     0                45h     <IP_ADDRESS>    akash-worker-01.nixaid.com   <none>           <none>
cert-manager     cert-manager-cainjector-967788869-6rchj              1/1     Running     0                45h     <IP_ADDRESS>    akash-worker-01.nixaid.com   <none>           <none>
cert-manager     cert-manager-webhook-6668fbb57d-m8kf5                1/1     Running     0                45h     <IP_ADDRESS>    akash-worker-01.nixaid.com   <none>           <none>
ingress-nginx    ingress-nginx-admission-create--1-478dl              0/1     Completed   0                3d21h   <IP_ADDRESS>    akash-worker-01.nixaid.com   <none>           <none>
ingress-nginx    ingress-nginx-admission-patch--1-fxvgp               0/1     Completed   1                3d21h   <IP_ADDRESS>    akash-worker-01.nixaid.com   <none>           <none>
ingress-nginx    ingress-nginx-controller-6b4b785659-6b6lj            1/1     Running     0                3d21h   <IP_ADDRESS>    akash-worker-01.nixaid.com   <none>           <none>
ingress-nginx    ingress-nginx-controller-6b4b785659-6ppvb            1/1     Running     0                28h     <IP_ADDRESS>    akash-worker-02.nixaid.com   <none>           <none>
ingress-nginx    ingress-nginx-controller-6b4b785659-dr9dg            1/1     Running     0                17h     <IP_ADDRESS>   akash-worker-03.nixaid.com   <none>           <none>
kube-system      calico-kube-controllers-75f8f6cc59-zncsv             1/1     Running     0                3d22h   <IP_ADDRESS>     akash-master-01.nixaid.com   <none>           <none>
kube-system      calico-node-8n5q8                                    1/1     Running     0                3d22h   <IP_ADDRESS>    akash-master-01.nixaid.com   <none>           <none>
kube-system      calico-node-fg6b6                                    1/1     Running     1 (3d11h ago)    3d22h   <IP_ADDRESS>     akash-master-03.nixaid.com   <none>           <none>
kube-system      calico-node-lr98d                                    1/1     Running     0                3d22h   <IP_ADDRESS>    akash-master-02.nixaid.com   <none>           <none>
kube-system      calico-node-s5plx                                    1/1     Running     0                3d21h   <IP_ADDRESS>     akash-worker-01.nixaid.com   <none>           <none>
kube-system      calico-node-sjs4s                                    1/1     Running     0                29h     <IP_ADDRESS>     akash-worker-02.nixaid.com   <none>           <none>
kube-system      calico-node-tgg4l                                    1/1     Running     0                17h     <IP_ADDRESS>   akash-worker-03.nixaid.com   <none>           <none>
kube-system      coredns-78fcd69978-85qgm                             1/1     Running     0                3d22h   <IP_ADDRESS>     akash-master-01.nixaid.com   <none>           <none>
kube-system      coredns-78fcd69978-r78dz                             1/1     Running     0                3d22h   <IP_ADDRESS>     akash-master-01.nixaid.com   <none>           <none>
kube-system      etcd-akash-master-01.nixaid.com                      1/1     Running     3                3d22h   <IP_ADDRESS>    akash-master-01.nixaid.com   <none>           <none>
kube-system      etcd-akash-master-02.nixaid.com                      1/1     Running     0                3d22h   <IP_ADDRESS>    akash-master-02.nixaid.com   <none>           <none>
kube-system      etcd-akash-master-03.nixaid.com                      1/1     Running     21 (3d10h ago)   3d22h   <IP_ADDRESS>     akash-master-03.nixaid.com   <none>           <none>
kube-system      kube-apiserver-akash-master-01.nixaid.com            1/1     Running     3                3d22h   <IP_ADDRESS>    akash-master-01.nixaid.com   <none>           <none>
kube-system      kube-apiserver-akash-master-02.nixaid.com            1/1     Running     0                3d22h   <IP_ADDRESS>    akash-master-02.nixaid.com   <none>           <none>
kube-system      kube-apiserver-akash-master-03.nixaid.com            1/1     Running     21 (3d10h ago)   3d22h   <IP_ADDRESS>     akash-master-03.nixaid.com   <none>           <none>
kube-system      kube-controller-manager-akash-master-01.nixaid.com   1/1     Running     5 (3d22h ago)    3d22h   <IP_ADDRESS>    akash-master-01.nixaid.com   <none>           <none>
kube-system      kube-controller-manager-akash-master-02.nixaid.com   1/1     Running     0                3d22h   <IP_ADDRESS>    akash-master-02.nixaid.com   <none>           <none>
kube-system      kube-controller-manager-akash-master-03.nixaid.com   1/1     Running     1 (3d11h ago)    3d22h   <IP_ADDRESS>     akash-master-03.nixaid.com   <none>           <none>
kube-system      kube-proxy-5n68c                                     1/1     Running     0                3d21h   <IP_ADDRESS>     akash-worker-01.nixaid.com   <none>           <none>
kube-system      kube-proxy-96k9l                                     1/1     Running     0                29h     <IP_ADDRESS>     akash-worker-02.nixaid.com   <none>           <none>
kube-system      kube-proxy-hv82z                                     1/1     Running     0                17h     <IP_ADDRESS>   akash-worker-03.nixaid.com   <none>           <none>
kube-system      kube-proxy-js2rj                                     1/1     Running     0                3d22h   <IP_ADDRESS>    akash-master-02.nixaid.com   <none>           <none>
kube-system      kube-proxy-n5fxr                                     1/1     Running     1 (3d11h ago)    3d22h   <IP_ADDRESS>     akash-master-03.nixaid.com   <none>           <none>
kube-system      kube-proxy-nw2vs                                     1/1     Running     0                3d22h   <IP_ADDRESS>    akash-master-01.nixaid.com   <none>           <none>
kube-system      kube-scheduler-akash-master-01.nixaid.com            1/1     Running     5 (3d22h ago)    3d22h   <IP_ADDRESS>    akash-master-01.nixaid.com   <none>           <none>
kube-system      kube-scheduler-akash-master-02.nixaid.com            1/1     Running     0                3d22h   <IP_ADDRESS>    akash-master-02.nixaid.com   <none>           <none>
kube-system      kube-scheduler-akash-master-03.nixaid.com            1/1     Running     1 (3d11h ago)    3d22h   <IP_ADDRESS>     akash-master-03.nixaid.com   <none>           <none>

Related
Probably related https://github.com/ovrclk/akash/issues/1421

cc @boz @dmikey

Yeah, these are the ghosts..
When stopping the Akash provider it is trying to close those 20 ghosts, but they fail with failed to execute message; message index: 0: unknown lease for bid message.
ov 03 20:29:37 akash-master-01.nixaid.com start-provider.sh[3662562]: I[2021-11-03|20:29:37.364] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: 2B07C00E171414BA84D345B594E66329799076FA4A4A61884202854D331CD49B\n  Raw Log: []\n  Logs: []" err=null
Nov 03 20:29:37 akash-master-01.nixaid.com start-provider.sh[3662562]: I[2021-11-03|20:29:37.428] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: 613CDB92D786F83A574E169E88E40A6EAD823C45F547C882FE8F7D770214AB44\n  Raw Log: []\n  Logs: []" err=null
Nov 03 20:29:37 akash-master-01.nixaid.com start-provider.sh[3662562]: I[2021-11-03|20:29:37.482] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: 51D7CA0002A0E3A472687CD279281034388C8D235D5826BDCA325FE12BDBADE8\n  Raw Log: []\n  Logs: []" err=null
Nov 03 20:29:37 akash-master-01.nixaid.com start-provider.sh[3662562]: I[2021-11-03|20:29:37.549] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: F47DF7FB20A37594703D5617BA4323F6DF725D61D7B00A8B3A29F41A7BE750A0\n  Raw Log: []\n  Logs: []" err=null
Nov 03 20:29:37 akash-master-01.nixaid.com start-provider.sh[3662562]: I[2021-11-03|20:29:37.605] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: FAA21EE94CEFD50C7406208753D8A0E8030BD14508955B2A7EC11401328207B0\n  Raw Log: []\n  Logs: []" err=null
Nov 03 20:29:37 akash-master-01.nixaid.com start-provider.sh[3662562]: I[2021-11-03|20:29:37.660] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: F7B4FFA70F0D51FDEA520E3F1E25AA060F4A9A126A7C698FDDBD6F7AEA4E7FFF\n  Raw Log: []\n  Logs: []" err=null
Nov 03 20:29:37 akash-master-01.nixaid.com start-provider.sh[3662562]: I[2021-11-03|20:29:37.727] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: C0D925AF65BCF6DAEAC0EC15F62CDF61D3F5200C1018DF49F75D66AA5332DB2E\n  Raw Log: []\n  Logs: []" err=null
Nov 03 20:29:37 akash-master-01.nixaid.com start-provider.sh[3662562]: I[2021-11-03|20:29:37.789] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: 5A89E7B88CFD37BCD2DC6441DD6F6F14D78CE73B3C1F1F6185153C2631F48817\n  Raw Log: []\n  Logs: []" err=null
Nov 03 20:29:37 akash-master-01.nixaid.com start-provider.sh[3662562]: I[2021-11-03|20:29:37.850] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: 8B087549DCE858647EA590B3DEFD852D6030817E5B5E07B6E736D83BC5CFB51F\n  Raw Log: []\n  Logs: []" err=null
Nov 03 20:29:37 akash-master-01.nixaid.com start-provider.sh[3662562]: I[2021-11-03|20:29:37.913] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: B6549BD6121681A3CF3F7839A316EB38932AD97E2C3A5E750FD681CA2485758F\n  Raw Log: []\n  Logs: []" err=null
Nov 03 20:29:37 akash-master-01.nixaid.com start-provider.sh[3662562]: I[2021-11-03|20:29:37.974] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: 23DFD2B3621F393E9734355CD851491EE2C15026DDD350ED3D1F05A313A5B30F\n  Raw Log: []\n  Logs: []" err=null
Nov 03 20:29:38 akash-master-01.nixaid.com start-provider.sh[3662562]: I[2021-11-03|20:29:38.036] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: 2C6E1EB12A5F11B4C539DB0CCDCA82C085128B69A684395D07AEF4A2EA17652B\n  Raw Log: []\n  Logs: []" err=null
Nov 03 20:29:38 akash-master-01.nixaid.com start-provider.sh[3662562]: I[2021-11-03|20:29:38.091] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: C6D32EC786A9485FF510A9A401C0599292EEA59F74F7A9494411AF0986D27D06\n  Raw Log: []\n  Logs: []" err=null
Nov 03 20:29:38 akash-master-01.nixaid.com start-provider.sh[3662562]: I[2021-11-03|20:29:38.147] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: 29EADBE2EA91F51F2F93AC55F4CE781D53E0CA323C245BB6453A14A26F0D9046\n  Raw Log: []\n  Logs: []" err=null

Nov 03 20:29:38 akash-master-01.nixaid.com start-provider.sh[3662562]: I[2021-11-03|20:29:38.211] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: DCB2278DE985D1BB2EF7CB022E25718CB15A30A9FD6B8BDCBF6A2A8F1148B593\n  Raw Log: []\n  Logs: []" err=null
Nov 03 20:29:38 akash-master-01.nixaid.com start-provider.sh[3662562]: I[2021-11-03|20:29:38.273] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: DB50FB7FA7C0B0C7538FD56E28E308EC3FE2E9A3B1B1B4C65682C82B4DCD261D\n  Raw Log: []\n  Logs: []" err=null
Nov 03 20:29:38 akash-master-01.nixaid.com start-provider.sh[3662562]: I[2021-11-03|20:29:38.326] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: 64C4F717467D318DB540A572CB04DB3B9199B364246F89B4EAA137F34D0C4E7F\n  Raw Log: []\n  Logs: []" err=null
Nov 03 20:29:38 akash-master-01.nixaid.com start-provider.sh[3662562]: I[2021-11-03|20:29:38.390] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: 82531614ABD019E6DD3237E8DA4AD16D5F1DAC44CF5A490873E90D404AEA0BA3\n  Raw Log: []\n  Logs: []" err=null

Nov 03 20:29:38 akash-master-01.nixaid.com start-provider.sh[3662562]: I[2021-11-03|20:29:38.448] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: 971365D28416C1A5AEB5B871B0A326820BC5243B5EEB64846D96561753A3DE18\n  Raw Log: []\n  Logs: []" err=null
Nov 03 20:29:38 akash-master-01.nixaid.com start-provider.sh[3662562]: I[2021-11-03|20:29:38.511] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: 5DEDD82E8256092A541CDD427C74BBD617E9B2FB9AE38F1CC2C52E3FC2C49A98\n  Raw Log: []\n  Logs: []" err=null
Nov 03 20:29:38 akash-master-01.nixaid.com start-provider.sh[3662562]: I[2021-11-03|20:29:38.511] Waiting on provider attributes service       module=bidengine-service
Nov 03 20:29:38 akash-master-01.nixaid.com systemd[1]: akash-provider.service: Succeeded.
Nov 03 20:29:38 akash-master-01.nixaid.com systemd[1]: Stopped Akash Provider.

Looks like all providers are affected. I have been in talk with Chiroxo, he's having the same issue:
Chiroxo's logs when he stops his akash provider
Nov 03 23:59:59 vmi567667.contaboserver.net start-provider.sh[178039]: I[2021-11-03|23:59:59.546] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: AD8BACA69B94C4A25302F6B8D77999BFA31132A1B99406EE88DDAF4E5414051B\n  Raw Log: []\n  Logs: []" err=null
Nov 03 23:59:59 vmi567667.contaboserver.net start-provider.sh[178039]: I[2021-11-03|23:59:59.606] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: 90B2CA847026DD52A0F1F8F022D5FF99ACA9370D5E76AB51BFFEC479CACE57B4\n  Raw Log: []\n  Logs: []" err=null
Nov 03 23:59:59 vmi567667.contaboserver.net start-provider.sh[178039]: I[2021-11-03|23:59:59.657] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: 12AFBBA891F1C4E7C6AE429CF53C99B921D4BE3594FA636C9D59C0F2DEFF0A53\n  Raw Log: []\n  Logs: []" err=null
Nov 03 23:59:59 vmi567667.contaboserver.net start-provider.sh[178039]: I[2021-11-03|23:59:59.708] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: FA0334463F50206FB74BACF2264F21A55E43E3AEA5FBE7CDEF31D074B4C0B799\n  Raw Log: []\n  Logs: []" err=null
Nov 03 23:59:59 vmi567667.contaboserver.net start-provider.sh[178039]: I[2021-11-03|23:59:59.766] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: B0041593486A5F5413A993AD9F047CD5A79A95B15D2E5E1A2D8C5FA44A89F30F\n  Raw Log: []\n  Logs: []" err=null

Same error: failed to execute message; message index: 0: unknown lease for bid
All active providers seem to be having the same issue
$ akash query provider list -o json | jq -r '.providers[] | [ .host_uri, .owner ] | @sh' | xargs -P30 -n2 sh -c 'curl -m1 -o /dev/null -skw "%{http_code}" $0/status | grep -qw 200 && echo $0' | xargs -r -P30 -I@ sh -c "pstats.sh @" | column -t
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://akash-provider.nixaid.com:8443                0    21     0       22.05    21.7   0        68.4595  34.25    0        1578.29  87.875
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://akash01.bridgetower-dc.org:8443               0    13     0       36.525   13.5   0        73.08    28.5     0        436.236  71.5
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://akash01.swiss01.bridgetower-dc.org:8443       0    13     0       36.525   13.5   0        73.08    28.5     0        436.236  71.5
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://sia25.cosow.com:8443                          0    5      0       45.275   8      0        365.859  22       0        4544.06  626
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://sia22.cosow.com:8443                          0    6      0       22.55    8.5    0        185.676  18.5     0        2580.73  28.5
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://provider.karukera-mining.com:8443             0    7      0       5.45     5.4    0        15.1798  14       0        389.752  9
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://provider.aksh.bv.cubus.ro:8443                0    8      0       68.9     1.552  0        84.9696  4.35714  0        1084.36  219.5
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://provider.provider-0.prod.ams1.akash.pub:8443  196  55     597.26  505.865  78.3   206.266  5848.53  109.25   692.766  4599.54  535.938
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://internal.ingotstudios.com:8443                3    6      3.5     18.3     5.3    3.5      38.078   15.125   5.5      2464.74  222.125
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://akashprovider.theminershive.com:8443          0    0      0       22.775   0      0        62.3863  0        0        441.592  0
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://supernaut.ddns.net:8443                       0    14     0       93.425   16.8   0        106.829  39.625   0        2468.46  670.625
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://akash.pogchia.world:8443                      0    10     0       21.8     8      0        17.988   17       0        1262.16  28
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://provider.provider-2.prod.ewr1.akash.pub:8443  133  68     284.3   1562.4   117.3  133.875  9913.3   135.25   444.813  10602.4  769.938
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://akash.pogchia.world:8443                      0    10     0       21.8     8      0        17.988   17       0        1262.16  28
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://supernaut.ddns.net:8443                       0    14     0       93.425   16.8   0        106.829  39.625   0        2468.46  670.625
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://provider.ewr1p0.mainnet.akashian.io:8443      73   0      422.7   116.672  0      172      1267.02  0        572.75   1028.38  0
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://earthlab.handyhost.computer:8443              0    10     0       21.8     8      0        17.988   17       0        1262.16  28
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://earthlab.handyhost.computer:8443              0    10     0       21.8     8      0        17.988   17       0        1262.16  28
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://stanzo.handyhost.computer:8443                4    9      4.9     16.9     5.1    5.25     12.7382  9.125    9.25     1252.91  26.125
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://provider.sm1.smartnodes.cloud:8443            1    12     1.5     43.775   14.7   1.5      224.304  35.5     2.5      11142.2  669.5
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://earthlab.handyhost.computer:8443              0    10     0       21.8     8      0        17.988   17       0        1262.16  28
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://earthlab.handyhost.computer:8443              0    10     0       21.8     8      0        17.988   17       0        1262.16  28
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://provider.sjc1p0.mainnet.akashian.io:8443      68   6      121.5   90.315   4.534  133.531  515.983  21.75    169.55   1407.25  52.625
host                                                  num  num-p  cpu     cpu-a    cpu-p  mem      mem-a    mem-p    fs       fs-a     fs-p
https://provider.provider-0.prod.sjc1.akash.pub:8443  124  58     207.7   410.95   94.3   103.324  3191.02  92.25    181.695  4426.38  636.938

workaround that works for me right now:
$ git diff
diff --git a/provider/bidengine/order.go b/provider/bidengine/order.go
index 886f5bb2..7f8ddba3 100644
--- a/provider/bidengine/order.go
+++ b/provider/bidengine/order.go
@@ -300,7 +300,7 @@ loop:
                        if o.bidPlaced {
                                o.log.Info("Fulfillment already exists")
                                // fulfillment already created (state recovered via queryExistingOrders)
-                               break
+                               break loop
                        }
                        pricech = runner.Do(metricsutils.ObserveRunner(func() runner.Result {
                                // Calculate price & bid

$ pstats.sh https://akash-provider.nixaid.com:8443
host                                    num  num-p  cpu  cpu-a  cpu-p  mem  mem-a    mem-p  fs  fs-a     fs-p
https://akash-provider.nixaid.com:8443  1    1      1    25.05  1      1    67.9595  2      1   1577.54  20

Though, provider is still trying to close the "catchup" orders, e.g.:
Nov 08 23:34:58 akash-master-01.nixaid.com start-provider.sh[3807667]: I[2021-11-08|23:34:58.698] broadcast response                           cmp=client/broadcaster response="Response:\n  TxHash: E26FB7FE40B326C8392E07150C99012A3F870117BB5B5307546EA9BD559FADA0\n  Raw Log: []\n  Logs: []" err=null

https://www.mintscan.io/akash/txs/3E12A6C607FC3D542D57D6A5D5F2D364B78899B9E1A5DF25A6AA7C86E2D1256B
still getting failed to execute message; message index: 0: unknown lease for bid for all 20 bids though

@arno01 I agree that should be break loop, I'll see about adding a test for that and making the change.

Thinking about this some more, I think the order manager doesn't use break loop there because it wants to wait for events. It needs to create event.LeaseWon if the bid is accepted.

'reservation requested' is logged whenever a reservation is requested. Not when a reservation is made. It's almost irrelevant, as the provider is continously checking new orders on the blockchain to see if they
can be reserved
When you see something like this a reservation has actually been made in the available inventory
Nov 03 18:43:29 akash-master-01.nixaid.com start-provider.sh[3630261]: I[2021-11-03|18:43:29.718] Reservation fulfilled                        module=bidengine-order order=akash10th527knwhvx8x085lw9uxxv9wmlzxf44y7n57/3328818/1/1

When you see something like this it means the provider believes there is a bid on the chain
Nov 03 18:43:29 akash-master-01.nixaid.com start-provider.sh[3630261]: I[2021-11-03|18:43:29.718] Fulfillment already exists                   module=bidengine-order order=akash10th527knwhvx8x085lw9uxxv9wmlzxf44y7n57/3328818/1/1

The provider has bids on the block chain that are currently out there and no one has created a lease for them. Presently, a bid that exists on the blockchain on startup is never automatically closed. My suggestion
would to be stop the provider, manually issue transactions to close unwanted bids, then start your provider back up.
Transactions such as this one https://www.mintscan.io/akash/txs/2B07C00E171414BA84D345B594E66329799076FA4A4A61884202854D331CD49B are from a bug in the provider where it issues a transaction to close a bid which does not exist at that time.
That likely is coming from here
https://github.com/ovrclk/akash/blob/mainnet/main/provider/bidengine/order.go#L381
losing bids are automatically closed by the network.
https://github.com/ovrclk/akash/blob/mainnet/main/x/market/handler/server.go#L214
Submitting this TX in that case is a waste of transaction fees and network capacity but otherwise not a technical problem at this time. You can safely ignore this problem for now.
I'm going to propose a separate PR with a number of changes to address this and some other issues.
Please don't refer to these as ghost deployments. The provider sees active bids on the blockchain and tries to act on them accordingly. The blockchain has a very high duration for the maximum time a bid can remaining pending presently.
Exactly when a provider may choose to close pending bids is sort of open question. There could be lots of strategies I can think of around this. For now we're going to stick to the strictly time out based strategy as it is the simplest
one to act upon.

@hydrogen18 thank you for explaining the nature of the issue and addressing it!
I've compiled akash off of https://github.com/ovrclk/akash/pull/1456 -- problems seem to have resolved now! :tada:
P.S.
I called those as "ghost deployments" since that's what I've seen (or I thought I've seen 🤔) over provider:8443/status - never closing pending deployments [reservations] (cluster.inventory.pending) which were holding up the resources, without the payment [since no lease was created for those reservations], in a way that my provider could not accommodate the new ones.
There might be a better wording for these than the "ghost deployments", probably "dangling stale reservations" would sound better? 🤷♂

There seem to be a different issue now - whenever I'm closing the deployment, the cluster.inventory.active is not decrementing.
Let's discuss that issue here https://github.com/ovrclk/akash/pull/1456#issuecomment-976336487

Closing, since the main issue is resolved


How to set offset?

Heya - building a project with WLED and I decided to use this library, but I can't figure out how to set the offset of the data I'm sending. Calling write(&[255, 255, 255]) lights up only the first pixel on my LED strip and I'm not sure how to move it (and sending the entire block starting from zero is wasteful).

@NotNite Hey NotNite, tbh I never really considered the usecase of sending something with a fixed offset since the data is so small that i just send it all every frame (you can push 87,950 pixels @ 45 FPS over a 100M link with DDP) so bandwidth wasn't really... something I did care about.
HOWEVER, for the purity of it i'll add a function that allows you to send with an offset.

Thank you!

I ended up attempting to build the project by spamming packets and ran into issues. My strip is 600 LEDs long (two strips together), but the max data length is 480. Sending 480 * 3 bytes works:

But trying to send the full 600 at once results in corruption:

It seems that anything not guaranteed to fit into one packet will corrupt.

Yeah tbh I realized I implemented the offset wrong and I don't slice it correctly so this is on me to fix. Will get to it

@NotNite just published a new version, there's now a write_offset(data, offset) function and I fixed the garbage data bug you discovered. Lmk if that works for you.

Seems to work, thanks!


When is support for GroupBy expected?

The Python SDK for CosmosDB seems to be the only one missing support for group-by querries.
NodeJS, .NET already have than implemented.
Can we have a date on when the Python SDK will support it? It says somewhere in the docs that it's on the roadmap for 2021, but that is kind of vague.

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

ID: f09cf24a-d276-8afc-f5d2-2406185cadfc
Version Independent ID: 926eeac4-2776-2d7c-b05e-250b982d0ef1
Content: Azure Cosmos DB SQL Python API, SDK & resources
Content Source: articles/cosmos-db/sql/sql-api-sdk-python.md
Service: cosmos-db
Sub-service: cosmosdb-sql
GitHub Login: @Rodrigossz
Microsoft Alias: rosouz

@lukipro Thank you for the feedback. We are actively investigating and will get back to you soon.

Hello @AnuragSharma-MSFT , @lukipro
Due to internal priorities, this capability ISN'T in immediately roadmap for now.
#please-close


subprocess.CalledProcessError: Command '['python3', 'dataset-generation.py', '--file', '../mit-bih\114']' returned non-zero exit status 9009.

when i come to the third step (Generate 1D and 2D data files running), it shows this error
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "dataset-generation-pool.py", line 21, in
p.map(run, ecg_data)
File "C:\Users\Weber\AppData\Local\Programs\Python\Python37\lib\multiprocessing\pool.py", line 268, in map
return self._map_async(func, iterable, mapstar, chunksize).get()
File "C:\Users\Weber\AppData\Local\Programs\Python\Python37\lib\multiprocessing\pool.py", line 657, in get
raise self._value
subprocess.CalledProcessError: Command '['python3', 'dataset-generation.py', '--file', '../mit-bih\114']' returned non-zero exit status 9009.

Hello @Wilbur0912,
Thank you for your feedback!
Same as #24.

I've used UNIX for the development that's why I didn't manage this behavior. If you still need this to be resolved, please, let me know.

Best regards,
Alex


Column-wise covariance and correlation matrices

Adds cov, cor and mean_and_cov functions.
Tests correctness by comparing with Statistics.cov/Statistics.cor.
Adds a section "Basic statistics" in the docs, where standardize is also moved.
Increments version to 1.5 and updates change log.

Fixes #23.

Should I pin Documenter to 0.27 here too, so the docs can build?  (ref https://github.com/JuliaDynamics/CausalityTools.jl/issues/358)

I don't get the documenter problem. The doctheme pins documenter by itself:
https://github.com/JuliaDynamics/doctheme/blob/master/build_docs_with_style.jl#L4

The CI doc build fails, though. So we can't inspect any preview docs, because they're not being pushed.

Yes, I know the docbuilds fail but I can't understand why documenter v1 is being installed. In any case, pinning it here to v1 is not an option, as then I would have to undo the pin in the 10+ packages that compose DynamicalSystems.jl.
The only solution is to solve https://github.com/JuliaDynamics/doctheme/issues/2  as far as the docs are concerned.

@kahaaga shall we finish this? I think you replace x.data with vec(x) and its done.

docs have been fixed for a while now.

Do we keep the Julia version at 1.5? The LTS is 1.6 at the moment

As for the distinction between correlation and covariance, I don't think it's necessary to specify here. This is common knowledge. The Statistics.jl package also doesn't give any details on the relationship between the two quantities.

I am not sure whether the docs fail now because of a repo-intrinsic issue, or if it is due to the organisation wide repo build. Maybe you know more, @Datseris ?

i'll fix it...


pretrained model

Thanks for your work. Could you kindly provide a pretrained model for the evaluation?

Hi @lgx-tech ,
I think the best pre-trained model is found here:
https://github.com/event-driven-robotics/hpe-core/blob/main/example/movenet/models/h36m_finetuned.pth
but @gaurvigoyal can confirm.
All the best.

Hey @lgx-tech,
The latest and best pre-trained model is this one: https://github.com/event-driven-robotics/hpe-core/blob/main/example/movenet/models/e97_valacc0.81209.pth.
All the best!

Thank you very much. I will close the issue.


Stop relying on model#getFielError with wildcard

This stopped working as of Spring Framework 6.1.x

This should be fixed now with #1814 .


Adding new token to re.al tokens

Adding USDR to real tokens list
yarn tokens was not working for me so if I can get an admin to perform that action that would be very helpful.
Thanks

this stablecoin is depegged and they are planning a migration to a different CA

yes, like for every coin we need valid coingecko price data though.. the only CG page i found was for the old coin

@sekuba Its the same token.. just bridged. It’s not a different contract address.

so the price of 40 cents is correct?
we would be very hesitant to add a token with a price feed from a different chain while the price is unpegged.

Yes the price is correct. And what “migration” are you referring to?

@sekuba Is there anything additionally I can provide for you?

@sekuba Just nudging here

sir, we are not adding the token in this state.

formally, we do not add any tokens with nonexisting price data for the chain they are added to. (this is why you could not succeed with the tokens script)
informally, the info around this asset is chaotic at best and actually misleading from my short research (why is it - one year later - still not fully redeemed if that was what the team communicated as their goal... why are there farming campaigns for an asset that is illiquid, unpegged, and supposed to be sunset)

If you really are confident it is an essential asset in you eco, please put in some effort and help us understand what use-case there is for this token and what is the actual goal of the 'redemptions'/'migration' and we can make an exception for the formal problem mentioned above

@sekuba We understand. Once redemption is completed the remaining USDR is going to be burned and deprecated anyway so it's not worth the hassle. Thanks for your help nonetheless.

I am completely new to cryptocurrency and and wasn't aware of the many
layers too it. On top of I am completely technologically declined. I
started a coinbase account, than a wallet, than I started to see NFT's and
Dapps.....needless to say I am trying to break generational poverty and to
try something completely knew, with a lack of computer skills and noone to
really learn from
On Fri, Nov 1, 2024, 11:50 AM Chase Brown @.***> wrote:

@sekuba https://github.com/sekuba We understand. Once redemption is
completed the remaining USDR is going to be burned and deprecated anyway so
it's not worth the hassle. Thanks for your help nonetheless.
—
Reply to this email directly, view it on GitHub
https://github.com/l2beat/l2beat/pull/5436#issuecomment-2452107871, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BCUYQTRYWMVLJAFM2ZS63ZLZ6OPMBAVCNFSM6AAAAABP65PFRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJSGEYDOOBXGE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Apologies for the misspelled words. I obtain a new phone am struggling a
bit to get everything half operable again. I do appreciate any guidance or
knowledge so this doesn't happen again I found a couple more address on the
block chains that look to be getting steady income on my behalf. I need to
relinquish the wallet apparently?!
On Fri, Nov 1, 2024, 12:38 PM Danielle Daschke @.***>
wrote:

I am completely new to cryptocurrency and and wasn't aware of the many
layers too it. On top of I am completely technologically declined. I
started a coinbase account, than a wallet, than I started to see NFT's and
Dapps.....needless to say I am trying to break generational poverty and to
try something completely knew, with a lack of computer skills and noone to
really learn from
On Fri, Nov 1, 2024, 11:50 AM Chase Brown @.***>
wrote:

@sekuba https://github.com/sekuba We understand. Once redemption is
completed the remaining USDR is going to be burned and deprecated anyway so
it's not worth the hassle. Thanks for your help nonetheless.
—
Reply to this email directly, view it on GitHub
https://github.com/l2beat/l2beat/pull/5436#issuecomment-2452107871, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BCUYQTRYWMVLJAFM2ZS63ZLZ6OPMBAVCNFSM6AAAAABP65PFRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJSGEYDOOBXGE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

On Fri, Nov 1, 2024, 12:42 PM Danielle Daschke @.***>
wrote:

Apologies for the misspelled words. I obtain a new phone am struggling a
bit to get everything half operable again. I do appreciate any guidance or
knowledge so this doesn't happen again I found a couple more address on the
block chains that look to be getting steady income on my behalf. I need to
relinquish the wallet apparently?!
On Fri, Nov 1, 2024, 12:38 PM Danielle Daschke @.***>
wrote:

I am completely new to cryptocurrency and and wasn't aware of the many
layers too it. On top of I am completely technologically declined. I
started a coinbase account, than a wallet, than I started to see NFT's and
Dapps.....needless to say I am trying to break generational poverty and to
try something completely knew, with a lack of computer skills and noone to
really learn from
On Fri, Nov 1, 2024, 11:50 AM Chase Brown @.***>
wrote:

@sekuba https://github.com/sekuba We understand. Once redemption is
completed the remaining USDR is going to be burned and deprecated anyway so
it's not worth the hassle. Thanks for your help nonetheless.
—
Reply to this email directly, view it on GitHub
https://github.com/l2beat/l2beat/pull/5436#issuecomment-2452107871,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCUYQTRYWMVLJAFM2ZS63ZLZ6OPMBAVCNFSM6AAAAABP65PFRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJSGEYDOOBXGE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Remove Horizontal Scroll

On the about page while scrolling down i observed an issue, there is an infinite horizontal scroll there, which degrades User experience.
I would like to raise an issue regarding same.
https://github.com/Prajwal0225/My-Favorite-SuperHero/assets/146264364/db560b35-495e-4136-bf52-8d4d23105ceb

@Prajwal0225 can you assign  this to me?

@madhurafulkar PR Raised!

@madhurafulkar PR Raised! please merge it. Thank You!

Please review and merge the PR


Tenant info action test

Description
waitForInit was copied in few different tests classes. This PR abstracts it into SingleClusterTests and changes it from being recursive to iterative with a maxRetries of 3. (i.e. waiting a max of 1.5 seconds for security plugin initialization).
While abstracting the function I noticed that some of the tests its applied to correctly identify that the plugin is initialized, but swallow an error that the user making the health request does not have the correct permissions. This PR keeps the same behavior.
This also adds waitForInit inside of tests in TenantInfoActionTest

Category (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation)

Maintenance, Test Reliability

Why these changes are required?

Reduce code duplication and improve reliability

What is the old behavior before changes and new behavior after changes?

Issues Resolved
Test reliability is impacting CI workflows #1917
Testing
[Please provide details of testing done: unit testing, integration testing and manual testing]
Check List

[X] New functionality includes testing
[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1935 (0b90eb4) into main (be876c0) will increase coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main    #1935   +/-   ##
=========================================
  Coverage     61.00%   61.01%
- Complexity     3233     3234    +1
=========================================
  Files           256      256
  Lines         18088    18088
  Branches       3224     3224
=========================================
+ Hits          11035    11036    +1
+ Misses         5470     5468    -2
- Partials       1583     1584    +1

Impacted Files
Coverage Δ

...iance/ComplianceIndexingOperationListenerImpl.java
62.31% <0.00%> (+1.44%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update be876c0...0b90eb4.
Note; the bulk run of integration tests github workflow has been merged if you'd like to use for verification of these changes.


Allow assemblies to have separately defined names

At the moment (due to the mash interface) samples are referred to by the filename of their assembly, but it would be convenient to be able to give each sample an arbitrary name in the --r-files or --q-files input:
sample1 assemblies/sample1.contigs.fa

Easy enough to update the PopPUNK side, but the mash sketch names are always the file name. Two possible ways of doing this I think:

Create temporary symlinks of the assemblies at their given names. This would best be done inside a tmp directory to avoid any clashes (copying the resulting sketches into the output dir)
Keep a table of file names to sample names as part of the database. Less hacky but more work.

For a local system, I don’t see a problem with the first option – if anything, have a renamed directory of sequences might be helpful for the user (rather than having to manually look up which FASTA files correspond to which isolates). I don’t know if there’s a loss of flexibility on multi-user systems, or if there are any special characters mash won’t accept as inputs?
From: John Lees <notifications<EMAIL_ADDRESS>Reply-To: johnlees/PopPUNK <reply<EMAIL_ADDRESS>Date: Thursday, 28 February 2019 at 20:14
To: johnlees/PopPUNK <PopPUNK<EMAIL_ADDRESS>Cc: Subscribed <subscribed<EMAIL_ADDRESS>Subject: [johnlees/PopPUNK] Allow assemblies to have separately defined names (#43)
At the moment (due to the mash interface) samples are referred to by the filename of their assembly, but it would be convenient to be able to give each sample an arbitrary name in the --r-files or --q-files input:
sample1 assemblies/sample1.contigs.fa
Easy enough to update the PopPUNK side, but the mash sketch names are always the file name. Two possible ways of doing this I think:

Create temporary symlinks of the assemblies at their given names. This would best be done inside a tmp directory to avoid any clashes (copying the resulting sketches into the output dir)
Keep a table of file names to sample names as part of the database. Less hacky but more work.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/johnlees/PopPUNK/issues/43, or mute the threadhttps://github.com/notifications/unsubscribe-auth/APz7QyVjAgX7ycJg0JIviFa3IY1u-x0fks5vSDidgaJpZM4bXpbI.

Closed in 620aa4a7f63b01c97f8cbd66f7bee1e7d314b2bb


Hackstead not appearing

My hackstead is flickering between existing and not existing (it shows the Monopolize on Adorableness? message). I think my hackstead has just recently become large enough to cause this issue. I tried transferring 20 warp powder to an alt (Robespierre) but this did not fix the issue.

The problem appears to have disappeared on its own.

For future reference this is a duplicate of #47


CocoaPods-specific tag for the Firebase pod

To avoid confusion with Swift Package Manager

Also for any future readers: Swift Package Manager will automatically pull in the last tag that matches sem-ver, so the moment we tag a X.Y.Z that becomes available as an update for developers, which doesn't go well with our release process right now where we tag and stage the pending release before publishing the other release artifacts at a later date.


Left join select issue

Laravel Version: 5.4.25
PHP Version: 5.6.4
Database Driver & Version: MySQL 5.5.55

Description:
I've got mysql query:
$tournaments = DB::table('tournaments')->select(DB::raw('tournaments.id, name, start_date, end_date, slots, registration_end_date, registration_start_date, opened, count(tournament_id) AS occ'))->leftJoin('tournament_registrations', 'tournaments.id', '=', 'tournament_registrations.tournament_id')->get();

but I getting this error:
Syntax error or access violation: 1140 Mixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clause

Please ask on the forums.


App fixes

This PR contains a conflict due to late merge of upstream changes. I'm abandoning this PR. New PR of this work with the upsrteam merge done in the right order: #19


Deploying of portfolio desktop version

this pull request was created to check whether the project deployed correctly via GitHub pages or not.

Many reviewers mentioned "Every comment with the [OPTIONAL] prefix won't stop the approval of this PR." really I did not understand, please tell me an example.


FourVector versus Event: the code/docs seems to conflate these two.

FourVector is more generic than Event.
The transformations should apply to any four-vector, not just any event. Correct?

I'm sticking now to kinematics only. No need to model 4-vectors in general. At present, I only need an Event class.


Add logo to login form

Before
After

something is wrong with a layout

Yes, max-width being set on the title and paragraph for some reason.

The reason is Grommet. It is adding max-width to many components out of a box. We will have to use fill prop in Paragraph and Header.

Fixed (added fill, but also limited modal width, otherwise it gets super wide)

1
2
3


Support single-line comments in template literals

import styled from 'styled-components';
const Title = styled.h1`
  // single-line comment
`;

Gives:
3:3 error Unknown word (CssSyntaxError)

style components uses stylis behind the scenes, a preprocessor that supports single-line comments.
It'd be great if this PostCSS syntax can cope with single-line comments too.

I think this issue should be in https://github.com/gucong3000/postcss-jsx, because we use postcss-jsx only in stylelint.


How to implement  "Clearance-based pathfinding"?

Thanks for the great path-finding library, it's extreme fast and easy to use.Now I'm mixing them into my potential fields system.Is there any Idea about how to implement the "Clearance-based pathfinding" with this algorithm? The reference is here:https://harablog.wordpress.com/category/pathfinding/

You can just Minkowski sum the map with whatever shape you want to handle clearance.  This can be done using any of the mathematical morphology libraries for ndarray.  For example:
https://www.npmjs.com/package/ball-morphology
Or:
https://www.npmjs.com/package/ndarray-convolve

Appreciate it!
I read the Mathematical Morphology algorithm, that will solve the problem, but it also has to create a new 'ndarray' for each size of the unit, Is there a way for l1-path-finder' to do the clearence and do it only once?
Thanks again, I've forked this repo, and have a try.


Displaying images in GitPitch

Please, can somebody let me know how to display successfully images in gitPitch ? Take a look at this PITCHME.md https://gitpitch.com/koffisani/github-rep-for-iai/pitchme

Hi @koffisani if you want to display an image on any slide and that images lives in the img directory within your git repo, you can just use a relative path to the image when you declare your image in your PITCHME.md markdown file. For example:
![Image](img/git.png)

I can see from your sample PITCHME.md that you are using absolute URLs to the blob. Try changing your markdown to use relative paths as indicated above.
See more details on working with image slides in the GitPitch Wiki.

Thanks, @gitpitch. Right.


[nixos-20.03] haskellPackages.hakyll-contrib-hyphenation: jailbreak

Motivation for this change
This is a backport of https://github.com/NixOS/nixpkgs/pull/80397.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Looks good. Thanks!


Update to Cadence v1.0.0-preview.29

Description
Automatically update to:

onflow/cadence v1.0.0-preview.29
onflow/flow-go-sdk v1.0.0-preview.30
onflow/flow-go 55f862b45dfd084f95ea2eaf0a167a9e416b9ae5

Maybe we can update to .30 right away?

@turbolent Thank you for fixing the build! I was confused why it was giving errors in the go.mod/go.sum, and didn't realize it was due to actual code changes.

Yeah, Go basically checks if older versions may provide a package and then attempts to use that older version.
A bit too much magic IMHO


initial config_parser, using angstrom. partially hooked to the unikernel

/cc @reynir (and others) for review.

FWIW the grammar description from the dnsmasq manpage is not precise: a dnsmasq --dhcp-range=<IP_ADDRESS> fails with "bad command line options". So one of the end-addr | mode  must be present.
Also note that it would be great if we can figure a path to run the examples as unit tests. May require, similar to MirageVPN, to have a library (+ alcotest suite) and separate unikernel. We'll get there. :D

This is ready for review. I'm happy to go through the changes in a pairing session //cc @reynir

Thanks! \o/


strftime: garbage from %z, garbage and segfaults from %Z

This is the same underlying problem as issue #321 but without the distraction of leapseconds which confused the original report.
Because none of the PosixTm functions make any attempt to preserve tm_gmtoff and tm_zone, then on platforms which use those extra members of struct tm, any use of %z in strftime produces garbage due to reading an uninitialized value, and any use of %Z has the potential to crash due to accessing an uninitialized pointer.
Making reproducible test cases is hard because the uninitialized data is on the stack and therefore the result may be compiler dependent. However it is easy to observe that the result of strftime("%z", localtime()) is correct only by coincidence (e.g. on my system it is almost always +0000 regardless of timezone) and that %Z can produce garbage or segfaults.

Thanks for the report and the diagnosis.
Actually a reproducible failure is less important than a reproducible success case that proves everything is fixed correctly.
Are you interested in working on a patch?

Thanks for the report and the diagnosis.
Actually a reproducible failure is less important than a reproducible success case that proves everything is fixed correctly.
Are you interested in working on a patch?

Actually fixing the problem is relatively straightforward (though I ran into some other bugs along the way, like the fact that optstringfield doesn't work at all (fortunately, nothing uses that) and checkstringfield uses lua_tolstring unsafely).
The hard part is the question of maintaining build compatibility with platforms that don't have tm_gmtoff or tm_zone; I don't know if there is any existing way to make luke check for that.

Actually fixing the problem is relatively straightforward (though I ran into some other bugs along the way, like the fact that optstringfield doesn't work at all (fortunately, nothing uses that) and checkstringfield uses lua_tolstring unsafely).
The hard part is the question of maintaining build compatibility with platforms that don't have tm_gmtoff or tm_zone; I don't know if there is any existing way to make luke check for that.

Please file separate issues for any new bugs you find, so I don’t lose track - luaposix is a fairly large project for one person to maintain, so I do rely on issues raised and am always delighted with pull requests.
I wrote luke to provide autoconf-like machinery without requiring m4 and Perl and then generating a 500k shell script to carry around. I’d be happy to help add a means to test for struct members and pass a cpp define at compile time based on the result if that’s the only thing holding you back from a patch for this issue?

Please file separate issues for any new bugs you find, so I don’t lose track - luaposix is a fairly large project for one person to maintain, so I do rely on issues raised and am always delighted with pull requests.
I wrote luke to provide autoconf-like machinery without requiring m4 and Perl and then generating a 500k shell script to carry around. I’d be happy to help add a means to test for struct members and pass a cpp define at compile time based on the result if that’s the only thing holding you back from a patch for this issue?

Yes, a way to get a cpp define for the presence of a struct member would be enough.

Yes, a way to get a cpp define for the presence of a struct member would be enough.

Done!
If you pull the latest build-aux/luke (version 0.2.2) from https://github.com/gvvaughan/luke into luaposix/build-aux/luke, you can then change the relevant section of lukefile to something like:
   ['posix.time']      = {
      defines   = {
         HAVE_TM_TM_GMTOFF = {checkmember='struct tm.tm_gmtoff', include='time.h'},
         HAVE_TM_TM_TZONE   = ...
      },
     ...
   },

And then patch ext/posix/time.c as necessary.
...in the lukefile for

Done!
If you pull the latest build-aux/luke (version 0.2.2) from https://github.com/gvvaughan/luke into luaposix/build-aux/luke, you can then change the relevant section of lukefile to something like:
   ['posix.time']      = {
      defines   = {
         HAVE_TM_TM_GMTOFF = {checkmember='struct tm.tm_gmtoff', include='time.h'},
         HAVE_TM_TM_TZONE   = ...
      },
     ...
   },

And then patch ext/posix/time.c as necessary.
...in the lukefile for

First attempt isn't working on linux because apparently different CFLAGS are being used when testing for the members in luke, as compared to doing the actual compile; specifically, defining _POSIX_C_SOURCE or _XOPEN_SOURCE looks like it's turning off __USE_MISC, which changes the names of the struct members (which is insane, but I have never regarded linux as sane).
Is there any reason not to add _DEFAULT_SOURCE to the defines when building for linux?

First attempt isn't working on linux because apparently different CFLAGS are being used when testing for the members in luke, as compared to doing the actual compile; specifically, defining _POSIX_C_SOURCE or _XOPEN_SOURCE looks like it's turning off __USE_MISC, which changes the names of the struct members (which is insane, but I have never regarded linux as sane).
Is there any reason not to add _DEFAULT_SOURCE to the defines when building for linux?

I’m afraid of changing those defines... it took a lot of trial and error to reach a selection that exposes all the right POSIX2008 APIs that we rely on.
It sounds like a bug in Luke to me. I’ll take a look at whether it makes sense to try and propagate the default flags at configure time.
In the mean time, if you add _DEFAULT_SOURCE to the Linux platform flags in lukefile, does everything still build and pass the test suite on your Linux?

I’m afraid of changing those defines... it took a lot of trial and error to reach a selection that exposes all the right POSIX2008 APIs that we rely on.
It sounds like a bug in Luke to me. I’ll take a look at whether it makes sense to try and propagate the default flags at configure time.
In the mean time, if you add _DEFAULT_SOURCE to the Linux platform flags in lukefile, does everything still build and pass the test suite on your Linux?

I don't have a linux to test on (I never use it). I only got the error from the CI build of the pull request. I will try that again with _DEFAULT_SOURCE to see what happens.
Fixing it in luke without setting _DEFAULT_SOURCE doesn't solve the underlying problem, since then luke will just say that tm_gmtoff and tm_zone don't exist, and we're back to crashing.

I don't have a linux to test on (I never use it). I only got the error from the CI build of the pull request. I will try that again with _DEFAULT_SOURCE to see what happens.
Fixing it in luke without setting _DEFAULT_SOURCE doesn't solve the underlying problem, since then luke will just say that tm_gmtoff and tm_zone don't exist, and we're back to crashing.

Well that obviously didn't work, it looks like some require() is now failing, but the CI output does not indicate what.

Well that obviously didn't work, it looks like some require() is now failing, but the CI output does not indicate what.

OK, that turned out to be my fault, a stray reference to lua53 rather than lua in luke.
Build with _DEFAULT_SOURCE is now passing tests on Travis-CI.

OK, that turned out to be my fault, a stray reference to lua53 rather than lua in luke.
Build with _DEFAULT_SOURCE is now passing tests on Travis-CI.


Update: Revamp UI/UX for the wallet with refined flows - GMGN wallet

Description

Updated all the core functionalities for the wallet
Added Pay + Request feature for requesting payment
Added transaction memo to aid with identifying tx id
Added faucet for Kaia Kairos to help onboarding flow
Revised Send and Receive flow for better UX
Added validation to various input
Revised Sign and Signature features for better validation and UX

Reference issue

#124
https://dorahacks.io/buidl/15990

Category

Other

Looking great. Approved

Link: https://www.gmgn.app/
Source code: https://github.com/gmgn-app/gmgn

Great improvements. The faucet is implementation is great.
Approved the max 2500 KLAY payout.

Closing for payout


Validate contact form

Implement validation on the contact form to achieve the following

The content of the email field has to be in lowercase.

The following interactions were also implemented

When the user submits the form, a check is performed to check if it is in lowercase.
If the validation is OK, the form is sent.
If the validation is not OK, an error message is sent and the form is not summited

Please my partner made a contribution in the circled portion of the image below.
This is a link to his contribution as well.
https://github.com/erickma1/Module1_Portfolio_Setup/commit/617612f8c47f49c96a8037f0b6e9e2a2b1fd5b69

Add font format for error message to match Figma design


Fix typo

.Net -> .NET

@changeworld : Thanks for your contribution! The author, @muralikk, has been notified to review your proposed change.

Merging the editorial fix.


Flag --incompatible_disable_starlark_host_transitions will break Bazel watcher in Bazel 7.0

Incompatible flag --incompatible_disable_starlark_host_transitions will be enabled by default in the next major release (Bazel 7.0), thus breaking Bazel watcher. Please migrate to fix this and unblock the flip of this flag.
The flag is documented here: bazelbuild/bazel#17032.
Please check the following CI builds for build and test results:

MacOS OpenJDK 11
MacOS OpenJDK 11
Ubuntu 16.04 OpenJDK 8
Ubuntu 18.04 OpenJDK 11
Windows OpenJDK 11

Never heard of incompatible flags before? We have documentation that explains everything.
If you have any questions, please file an issue in https://github.com/bazelbuild/continuous-integration.

Not stale - errors still need to be fixed

@keertk maybe I'm misreading, but when I click the links that are above they look like the bazel-watcher tasks are passing. Could you clarify a bit more?

When I click on the provided link for OpenJDK 11, Xcode, I see a page with a green check as well?

Hi @achew22 you can look under Running Bazel with --incompatible_disable_starlark_host_transitions

This is one of the errors:
bazel build --show_progress_rate_limit=5 --curses=yes --color=yes --terminal_columns=143 --show_timestamps --verbose_failures --jobs=36 --announce_rc --experimental_repository_cache_hardlinks --disk_cache= --sandbox_writable_path=/var/tmp/_bazel_buildkite/cache/repos/v1 --test_env=REPOSITORY_CACHE=/var/tmp/_bazel_buildkite/cache/repos/v1 --remote_cache=http://<IP_ADDRESS> --remote_timeout=60 --remote_max_connections=200 --remote_default_platform_properties=properties:{name:"cache-silo-key" value:"49e868fd19c783d6f53c975f6ca88acfc8b5830b0793f4698cbc32cefcda8c8b"} --build_tag_filters=-nomacos --test_env=HOME --test_env=BAZELISK_USER_AGENT --test_env=USE_BAZEL_VERSION --incompatible_disable_starlark_host_transitions -- ...
--
  | (11:23:10) WARNING: Option 'remote_default_platform_properties' is deprecated: --remote_default_platform_properties has been deprecated in favor of --remote_default_exec_properties.
  | (11:23:10) INFO: Invocation ID: 36a72a2f-5429-466f-a795-8a0d7e495e6e
  | (11:23:10) INFO: Options provided by the client:
  | Inherited 'common' options: --isatty=1 --terminal_columns=0
  | (11:23:10) INFO: Reading rc options for 'build' from /Users/buildkite/builds/bk-imacpro-15/bazel-downstream-projects/bazel-watcher/.bazelrc:
  | 'build' options: --workspace_status_command=python3 tools/workplace_status.py
  | (11:23:11) WARNING: Option 'remote_default_platform_properties' is deprecated: --remote_default_platform_properties has been deprecated in favor of --remote_default_exec_properties.
  | (11:23:11) INFO: Current date is 2022-12-15
  | (11:23:11) ERROR: Traceback (most recent call last):
  | File "/private/var/tmp/_bazel_buildkite/62aafb6863f3e91c21fe2c420944323e/external/io_bazel_rules_go/extras/embed_data.bzl", line 133, column 29, in <toplevel>
  | "_embed": attr.label(
  | Error in label: 'cfg = "host"' is deprecated and should no longer be used. Please use 'cfg = "exec"' instead.
  | (11:23:11) ERROR: Skipping '...': error loading package under directory '': error loading package 'internal/ibazel/output_runner': at /private/var/tmp/_bazel_buildkite/62aafb6863f3e91c21fe2c420944323e/external/io_bazel_rules_go/go/def.bzl:58:5: initialization of module 'extras/embed_data.bzl' failed
  | (11:23:11) WARNING: Target pattern parsing failed.
  | (11:23:11) ERROR: error loading package under directory '': error loading package 'internal/ibazel/output_runner': at /private/var/tmp/_bazel_buildkite/62aafb6863f3e91c21fe2c420944323e/external/io_bazel_rules_go/go/def.bzl:58:5: initialization of module 'extras/embed_data.bzl' failed
  | (11:23:11) INFO: Elapsed time: 0.953s
  | (11:23:11) INFO: 0 processes.
  | (11:23:11) FAILED: Build did NOT complete successfully (0 packages loaded)

Sorry that this was confusing! I hope this helps.

I've run this down now and I'm blocked on https://github.com/bazelbuild/rules_go/issues/3403. I've removed my dependency  on the old go embed data stuff in https://github.com/bazelbuild/bazel-watcher/pull/589 but this will be blocked until rules_go actually removes that.
That said, the go_embed_data feature has been deprecated for a while and deletion might be an easy fix if people are amenable.

Hi @achew22, Could you please share any significant update on this issue ?


show pending CDN invalidations on queue page

Since #1880 raised some more open questions, here a simple addition to the queue page. I'll finish up #1880 separately, same for actually querying the cloudfront API to get the invalidations.
This is IMO the last piece missing to really enable #1552 in the CDN configuration.

r? @jsha @jyn514 ?

This is how it looks like right now:

ping @rust-lang/docs-rs
I would love a review / feeback here.
This is the last piece missing before we can activate the full page caching for docs.