VMs are stuck in scheduling due to 0/2 nodes are available: 2 Insufficient devices.kubevirt.io/kvm

Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
I tried to launch a virtual machine, but it gets stuck in scheduling. Bug is simmilar to 1316
What you expected to happen:
The VM to be scheduled and then started. Describing the vmi I can see:
`Message:               0/2 nodes are available: 1 Insufficient devices.kubevirt.io/tun, 1 Insufficient devices.kubevirt.io/vhost-net, 2 Insufficient devices.kubevirt.io/kvm.
Reason:                Unschedulable
Status:                False
Type:                  PodScheduled
Guest OS Info:
Phase:      Scheduling
Qos Class:  Burstable
Events:
Type    Reason            Age   From                       Message

Normal  SuccessfulCreate  43m   virtualmachine-controller  Created virtual machine pod virt-launcher-testvmi-nocloud-bhx4b`
All pods are running and ready:
kubectl get pods -A
NAMESPACE     NAME                                                   READY   STATUS    RESTARTS   AGE
default       virt-launcher-testvmi-nocloud-bhx4b                    0/2     Pending   0          44m
kube-system   coredns-f9fd979d6-cj82f                                1/1     Running   1          6h30m
kube-system   coredns-f9fd979d6-p99p7                                1/1     Running   1          6h30m
kube-system   etcd-"cluster master hostname"                      1/1     Running   1          6h30m
kube-system   kube-apiserver-"cluster master hostname"            1/1     Running   1          6h30m
kube-system   kube-controller-manager-"cluster master hostname"   1/1     Running   3          6h30m
kube-system   kube-flannel-ds-hvpwn                                  1/1     Running   1          6h29m
kube-system   kube-flannel-ds-jt62k                                  1/1     Running   1          6h29m
kube-system   kube-proxy-h7dht                                       1/1     Running   1          6h30m
kube-system   kube-proxy-xr5wc                                       1/1     Running   1          6h29m
kube-system   kube-scheduler-"cluster master hostname"            1/1     Running   3          6h30m
kubevirt      virt-api-69879b6659-gjphd                              1/1     Running   1          6h21m
kubevirt      virt-api-69879b6659-p4wbw                              1/1     Running   1          6h21m
kubevirt      virt-controller-789bcb7458-f7zbl                       1/1     Running   6          6h19m
kubevirt      virt-controller-789bcb7458-kmg6x                       1/1     Running   6          6h19m
kubevirt      virt-handler-v4chs                                     1/1     Running   4          56m
kubevirt      virt-operator-589f5568b8-7w52x                         1/1     Running   1          6h26m
kubevirt      virt-operator-589f5568b8-csl5t                         1/1     Running   7          6h26m
How to reproduce it (as minimally and precisely as possible):
Installing kubernetes and kubevirt.
Add flannel CNI.
Create Virtual Machine.
Anything else we need to know?:
I tried creating a virtual machine and a virtual machine instance, meaning to have one started by virtctl and one start on its own, I get the same message when describing:
0/2 nodes are available: 1 Insufficient devices.kubevirt.io/tun, 1 Insufficient devices.kubevirt.io/vhost-net, 2 Insufficient devices.kubevirt.io/kvm.
I also have emulation enabled and nested virtualisation is enabled since I am doing it on a virtual machine.
kubectl create configmap -n kube-system kubevirt-config --from-literal debug.useEmulation=true
and
grep vmx /proc/cpuinfo returns vmx
I found no errors in kubevirt virt-handler:
kubectl logs virt-handler-v4chs -n kubevirt
{"component":"virt-handler","hostname":""worker node hostname","level":"info","pos":"virt-handler.go:171","timestamp":"2021-01-05T13:42:06.469353Z"}
{"component":"virt-handler","level":"info","msg":"Starting collector: node name="worker node hostname"","pos":"prometheus.go:506","timestamp":"2021-01-05T13:42:06.977566Z"}
{"component":"virt-handler","level":"info","msg":"STARTING informer extensionsKubeVirtCAConfigMapInformer","pos":"virtinformers.go:251","timestamp":"2021-01-05T13:42:06.977688Z"}
{"component":"virt-handler","level":"info","msg":"STARTING informer vmiInformer","pos":"virtinformers.go:251","timestamp":"2021-01-05T13:42:06.977773Z"}
{"component":"virt-handler","level":"info","msg":"STARTING informer configMapInformer","pos":"virtinformers.go:251","timestamp":"2021-01-05T13:42:06.977847Z"}
{"component":"virt-handler","level":"info","msg":"STARTING informer CRDInformer","pos":"virtinformers.go:251","timestamp":"2021-01-05T13:42:06.977906Z"}
{"component":"virt-handler","level":"info","msg":"STARTING informer kubeVirtInformer","pos":"virtinformers.go:251","timestamp":"2021-01-05T13:42:06.977938Z"}
{"component":"virt-handler","level":"info","msg":"certificate with common name 'kubevirt.io:system:node:virt-handler' retrieved.","pos":"cert-manager.go:196","timestamp":"2021-01-05T13:42:06.979537Z"}
{"component":"virt-handler","level":"info","msg":"metrics: max concurrent requests=3","pos":"virt-handler.go:380","timestamp":"2021-01-05T13:42:06.981361Z"}
{"component":"virt-handler","level":"info","msg":"certificate with common name 'kubevirt.io:system:client:virt-handler' retrieved.","pos":"cert-manager.go:196","timestamp":"2021-01-05T13:42:06.983273Z"}
{"component":"virt-handler","level":"info","msg":"Updating cluster config from KubeVirt to resource version '61623'","pos":"config-map.go:499","timestamp":"2021-01-05T13:42:06.992416Z"}
{"component":"virt-handler","level":"info","msg":"Starting virt-handler controller.","pos":"vm.go:994","timestamp":"2021-01-05T13:42:07.142657Z"}
{"component":"virt-handler","level":"info","msg":"refreshed device plugins for permitted/forbidden host devices","pos":"device_controller.go:211","timestamp":"2021-01-05T13:42:07.243698Z"}
{"component":"virt-handler","level":"info","msg":"enabled device-pluings for: []","pos":"device_controller.go:212","timestamp":"2021-01-05T13:42:07.243836Z"}
{"component":"virt-handler","level":"info","msg":"disabled device-pluings for: []","pos":"device_controller.go:213","timestamp":"2021-01-05T13:42:07.243878Z"}
{"component":"virt-handler","level":"info","msg":"refreshed device plugins for permitted/forbidden host devices","pos":"device_controller.go:211","timestamp":"2021-01-05T13:42:07.243930Z"}
{"component":"virt-handler","level":"info","msg":"enabled device-pluings for: []","pos":"device_controller.go:212","timestamp":"2021-01-05T13:42:07.244069Z"}
{"component":"virt-handler","level":"info","msg":"disabled device-pluings for: []","pos":"device_controller.go:213","timestamp":"2021-01-05T13:42:07.244108Z"}
{"component":"virt-handler","level":"info","msg":"Starting a device plugin for device: kvm","pos":"device_controller.go:88","timestamp":"2021-01-05T13:42:07.245505Z"}
{"component":"virt-handler","level":"info","msg":"Starting a device plugin for device: tun","pos":"device_controller.go:88","timestamp":"2021-01-05T13:42:07.246128Z"}
{"component":"virt-handler","level":"info","msg":"Starting a device plugin for device: vhost-net","pos":"device_controller.go:88","timestamp":"2021-01-05T13:42:07.247061Z"}
{"component":"virt-handler","level":"info","msg":"tun device plugin started","pos":"generic_device.go:178","timestamp":"2021-01-05T13:42:07.253869Z"}
{"component":"virt-handler","level":"info","msg":"device '/dev/net/tun' is present.","pos":"generic_device.go:318","timestamp":"2021-01-05T13:42:07.253978Z"}
{"component":"virt-handler","level":"info","msg":"kvm device plugin started","pos":"generic_device.go:178","timestamp":"2021-01-05T13:42:07.255555Z"}
{"component":"virt-handler","level":"warning","msg":"device '/dev/kvm' is not present, the device plugin can't expose it.","pos":"generic_device.go:315","timestamp":"2021-01-05T13:42:07.255711Z"}
{"component":"virt-handler","level":"info","msg":"device '/dev/kvm' is present.","pos":"generic_device.go:318","timestamp":"2021-01-05T13:42:07.257490Z"}
{"component":"virt-handler","level":"info","msg":"vhost-net device plugin started","pos":"generic_device.go:178","timestamp":"2021-01-05T13:42:07.262461Z"}
{"component":"virt-handler","level":"info","msg":"device '/dev/vhost-net' is present.","pos":"generic_device.go:318","timestamp":"2021-01-05T13:42:07.262570Z"}
{"component":"virt-handler","level":"info","msg":"resyncing virt-launcher domains","pos":"cache.go:385","timestamp":"2021-01-05T13:47:07.145769Z"}
{"component":"virt-handler","level":"info","msg":"resyncing virt-launcher domains","pos":"cache.go:385","timestamp":"2021-01-05T13:52:07.145425Z"}
Environment:

KubeVirt version (use virtctl version):
Client Version: version.Info{GitVersion:"v0.34.2", GitCommit:"48956f60864ece98118d7894327caf7513c5b942", GitTreeState:"clean", BuildDate:"2020-11-17T13:47:56Z", GoVersion:"go1.13.14", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{GitVersion:"{gitVersion}", GitCommit:"{gitCommit}", GitTreeState:"{gitTreeState}", BuildDate:"{buildDate}", GoVersion:"go1.13.14", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:50:19Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.6", GitCommit:"fbf646b339dc52336b55d8ec85c181981b86331a", GitTreeState:"clean", BuildDate:"2020-12-18T12:01:36Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}

VM or VMI specifications:
`apiVersion: kubevirt.io/v1alpha3
kind: VirtualMachineInstance
metadata:
name: testvmi-nocloud
spec:
terminationGracePeriodSeconds: 30
domain:
resources:
requests:
memory: 1024M
devices:
disks:
- name: containerdisk
disk:
bus: virtio
- name: emptydisk
disk:
bus: virtio
- disk:
bus: virtio
name: cloudinitdisk
volumes:

name: containerdisk
containerDisk:
image: kubevirt/fedora-cloud-container-disk-demo:latest
name: emptydisk
emptyDisk:
capacity: "2Gi"
name: cloudinitdisk
cloudInitNoCloud:
userData: |-
#cloud-config
password: fedora
chpasswd: { expire: False }`

Cloud provider or hardware configuration:

OS (e.g. from /etc/os-release):
NAME="Ubuntu"
VERSION="18.04.5 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.5 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

Kernel (e.g. uname -a):
Linux "cluster master hostname" 4.18.0-25-generic #26~18.04.1-Ubuntu SMP Thu Jun 27 07:28:31 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Install tools:

Others:

As you can see from the virt-handler log, it seems that /dev/kvm is not present on the node.
{"component":"virt-handler","level":"warning","msg":"device '/dev/kvm' is not present, the device plugin can't expose it.","pos":"generic_device.go:315","timestamp":"2021-01-05T13:42:07.255711Z"}
Could you please verify that the kvm module is loaded?
lsmod|grep kvm

As you can see from the virt-handler log, it seems that /dev/kvm is not present on the node.
{"component":"virt-handler","level":"warning","msg":"device '/dev/kvm' is not present, the device plugin can't expose it.","pos":"generic_device.go:315","timestamp":"2021-01-05T13:42:07.255711Z"}
Could you please verify that the kvm module is loaded?
lsmod|grep kvm

Hi @vladikr, yes I saw that but in the next message it was found:
{"component":"virt-handler","level":"warning","msg":"device '/dev/kvm' is not present, the device plugin can't expose it.","pos":"generic_device.go:315","timestamp":"2021-01-05T13:42:07.255711Z"}
{"component":"virt-handler","level":"info","msg":"device '/dev/kvm' is present.","pos":"generic_device.go:318","timestamp":"2021-01-05T13:42:07.257490Z"}
Also I do have it:
ls /dev/ | grep kvm
output: kvm
lsmod | grep kvm
kvm_intel             208896  0
kvm                   626688  1 kvm_intel
irqbypass              16384  2 vfio_pci,kvm

Hi @vladikr, yes I saw that but in the next message it was found:
{"component":"virt-handler","level":"warning","msg":"device '/dev/kvm' is not present, the device plugin can't expose it.","pos":"generic_device.go:315","timestamp":"2021-01-05T13:42:07.255711Z"}
{"component":"virt-handler","level":"info","msg":"device '/dev/kvm' is present.","pos":"generic_device.go:318","timestamp":"2021-01-05T13:42:07.257490Z"}
Also I do have it:
ls /dev/ | grep kvm
output: kvm
lsmod | grep kvm
kvm_intel             208896  0
kvm                   626688  1 kvm_intel
irqbypass              16384  2 vfio_pci,kvm

great, I didn't notice.
Can you please post the output of kubectl describe nodes?

great, I didn't notice.
Can you please post the output of kubectl describe nodes?

@vladikr Thanks for responding quickly.
kubectl describe nodes
Name:
Roles:
Labels:             beta.kubernetes.io/arch=amd64
beta.kubernetes.io/os=linux
kubernetes.io/arch=amd64
kubernetes.io/hostname=
kubernetes.io/os=linux
kubevirt.io/schedulable=true
Annotations:        flannel.alpha.coreos.com/backend-data: {"VNI":1,"VtepMAC":"62:c4:fb:b8:b3:1c"}
flannel.alpha.coreos.com/backend-type: vxlan
flannel.alpha.coreos.com/kube-subnet-manager: true
flannel.alpha.coreos.com/public-ip: <IP_ADDRESS>
kubeadm.alpha.kubernetes.io/cri-socket: /var/run/dockershim.sock
kubevirt.io/heartbeat: 2021-01-05T14:56:51Z
node.alpha.kubernetes.io/ttl: 0
volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Tue, 05 Jan 2021 16:16:29 +0200
Taints:
Unschedulable:      false
Lease:
HolderIdentity:
AcquireTime:
RenewTime:       Tue, 05 Jan 2021 16:57:07 +0200
Conditions:
Type                 Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message

NetworkUnavailable   False   Tue, 05 Jan 2021 16:17:35 +0200   Tue, 05 Jan 2021 16:17:35 +0200   FlannelIsUp                  Flannel is running on this node
MemoryPressure       False   Tue, 05 Jan 2021 16:54:02 +0200   Tue, 05 Jan 2021 16:16:29 +0200   KubeletHasSufficientMemory   kubelet has sufficient memory available
DiskPressure         False   Tue, 05 Jan 2021 16:54:02 +0200   Tue, 05 Jan 2021 16:16:29 +0200   KubeletHasNoDiskPressure     kubelet has no disk pressure
PIDPressure          False   Tue, 05 Jan 2021 16:54:02 +0200   Tue, 05 Jan 2021 16:16:29 +0200   KubeletHasSufficientPID      kubelet has sufficient PID available
Ready                True    Tue, 05 Jan 2021 16:54:02 +0200   Tue, 05 Jan 2021 16:16:31 +0200   KubeletReady                 kubelet is posting ready status
Addresses:
InternalIP:  <IP_ADDRESS>
Hostname:
Capacity:
cpu:                            4
devices.kubevirt.io/kvm:        110
devices.kubevirt.io/tun:        110
devices.kubevirt.io/vhost-net:  110
ephemeral-storage:              20509264Ki
hugepages-2Mi:                  13480Mi
memory:                         16425164Ki
pods:                           110
Allocatable:
cpu:                            4
devices.kubevirt.io/kvm:        0
devices.kubevirt.io/tun:        110
devices.kubevirt.io/vhost-net:  110
ephemeral-storage:<PHONE_NUMBER>2
hugepages-2Mi:                  13480Mi
memory:                         2519244Ki
pods:                           110
System Info:
Machine ID:                 813fd93e4b964ef6b929ca1ecbed231d
System UUID:                813fd93e-4b96-4ef6-b929-ca1ecbed231d
Boot ID:                    508800fe-ca59-411f-813e-01f54bc4a49a
Kernel Version:             4.18.0-25-generic
OS Image:                   Ubuntu 18.04.5 LTS
Operating System:           linux
Architecture:               amd64
Container Runtime Version:  docker://19.3.6
Kubelet Version:            v1.19.3
Kube-Proxy Version:         v1.19.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                 kube-flannel-ds-5wz59               100m (2%)     100m (2%)   50Mi (2%)        50Mi (2%)      40m
kube-system                 kube-proxy-rm8hk                    0 (0%)        0 (0%)      0 (0%)           0 (0%)         40m
kubevirt                    virt-api-69879b6659-fbrdx           0 (0%)        0 (0%)      0 (0%)           0 (0%)         35m
kubevirt                    virt-api-69879b6659-xcfmw           0 (0%)        0 (0%)      0 (0%)           0 (0%)         35m
kubevirt                    virt-controller-789bcb7458-2zdds    0 (0%)        0 (0%)      0 (0%)           0 (0%)         34m
kubevirt                    virt-controller-789bcb7458-mdr7x    0 (0%)        0 (0%)      0 (0%)           0 (0%)         34m
kubevirt                    virt-handler-5964v                  0 (0%)        0 (0%)      0 (0%)           0 (0%)         34m
kubevirt                    virt-operator-589f5568b8-dhcdj      0 (0%)        0 (0%)      0 (0%)           0 (0%)         38m
kubevirt                    virt-operator-589f5568b8-grpcp      0 (0%)        0 (0%)      0 (0%)           0 (0%)         38m
Allocated resources:
(Total limits may be over 100 percent, i.e., overcommitted.)
Resource                       Requests   Limits

cpu                            100m (2%)  100m (2%)
memory                         50Mi (2%)  50Mi (2%)
ephemeral-storage              0 (0%)     0 (0%)
hugepages-2Mi                  0 (0%)     0 (0%)
devices.kubevirt.io/kvm        0          0
devices.kubevirt.io/tun        0          0
devices.kubevirt.io/vhost-net  0          0
Events:
Type    Reason                   Age                From        Message

Normal  NodeHasSufficientMemory  40m (x7 over 40m)  kubelet     Node  status is now: NodeHasSufficientMemory
Normal  NodeHasNoDiskPressure    40m (x7 over 40m)  kubelet     Node  status is now: NodeHasNoDiskPressure
Normal  NodeHasSufficientPID     40m (x7 over 40m)  kubelet     Node  status is now: NodeHasSufficientPID
Normal  NodeReady                40m                kubelet     Node  status is now: NodeReady
Normal  Starting                 39m                kube-proxy  Starting kube-proxy.
Name:
Roles:              master
Labels:             beta.kubernetes.io/arch=amd64
beta.kubernetes.io/os=linux
kubernetes.io/arch=amd64
kubernetes.io/hostname=
kubernetes.io/os=linux
node-role.kubernetes.io/master=
Annotations:        flannel.alpha.coreos.com/backend-data: {"VNI":1,"VtepMAC":"5e:5e:43:72:99:f7"}
flannel.alpha.coreos.com/backend-type: vxlan
flannel.alpha.coreos.com/kube-subnet-manager: true
flannel.alpha.coreos.com/public-ip: <IP_ADDRESS>
kubeadm.alpha.kubernetes.io/cri-socket: /var/run/dockershim.sock
node.alpha.kubernetes.io/ttl: 0
volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Tue, 05 Jan 2021 16:11:01 +0200
Taints:             node-role.kubernetes.io/master:NoSchedule
Unschedulable:      false
Lease:
HolderIdentity:
AcquireTime:
RenewTime:       Tue, 05 Jan 2021 16:57:05 +0200
Conditions:
Type                 Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message

NetworkUnavailable   False   Tue, 05 Jan 2021 16:16:14 +0200   Tue, 05 Jan 2021 16:16:14 +0200   FlannelIsUp                  Flannel is running on this node
MemoryPressure       False   Tue, 05 Jan 2021 16:56:22 +0200   Tue, 05 Jan 2021 16:11:01 +0200   KubeletHasSufficientMemory   kubelet has sufficient memory available
DiskPressure         False   Tue, 05 Jan 2021 16:56:22 +0200   Tue, 05 Jan 2021 16:11:01 +0200   KubeletHasNoDiskPressure     kubelet has no disk pressure
PIDPressure          False   Tue, 05 Jan 2021 16:56:22 +0200   Tue, 05 Jan 2021 16:11:01 +0200   KubeletHasSufficientPID      kubelet has sufficient PID available
Ready                True    Tue, 05 Jan 2021 16:56:22 +0200   Tue, 05 Jan 2021 16:16:04 +0200   KubeletReady                 kubelet is posting ready status
Addresses:
InternalIP:  <IP_ADDRESS>
Hostname:
Capacity:
cpu:                4
ephemeral-storage:  20509264Ki
hugepages-1Gi:      0
hugepages-2Mi:      1Gi
memory:             8169724Ki
pods:               110
Allocatable:
cpu:                4
ephemeral-storage:<PHONE_NUMBER>2
hugepages-1Gi:      0
hugepages-2Mi:      1Gi
memory:             7018748Ki
pods:               110
System Info:
Machine ID:                 5255ead855cd4483af9ee14dcd8069d6
System UUID:                17617f19-f682-46d5-9b5d-7c9a5c53fcd6
Boot ID:                    35bd5e2e-2151-42c7-99e8-8f7cb7f9f151
Kernel Version:             4.18.0-25-generic
OS Image:                   Ubuntu 18.04.5 LTS
Operating System:           linux
Architecture:               amd64
Container Runtime Version:  docker://19.3.6
Kubelet Version:            v1.19.3
Kube-Proxy Version:         v1.19.3
PodCIDR:                      <IP_ADDRESS>/24
PodCIDRs:                     <IP_ADDRESS>/24
Non-terminated Pods:          (8 in total)
Namespace                   Name                                                    CPU Requests  CPU Limits  Memory Requests  Memory Limits  AGE

kube-system                 coredns-f9fd979d6-6sp2g                                 100m (2%)     0 (0%)      70Mi (1%)        170Mi (2%)     45m
kube-system                 coredns-f9fd979d6-75ff8                                 100m (2%)     0 (0%)      70Mi (1%)        170Mi (2%)     45m
kube-system                 etcd-                       0 (0%)        0 (0%)      0 (0%)           0 (0%)         45m
kube-system                 kube-apiserver-             250m (6%)     0 (0%)      0 (0%)           0 (0%)         45m
kube-system                 kube-controller-manager-    200m (5%)     0 (0%)      0 (0%)           0 (0%)         45m
kube-system                 kube-flannel-ds-kl5bx                                   100m (2%)     100m (2%)   50Mi (0%)        50Mi (0%)      41m
kube-system                 kube-proxy-xvq82                                        0 (0%)        0 (0%)      0 (0%)           0 (0%)         45m
kube-system                 kube-scheduler-             100m (2%)     0 (0%)      0 (0%)           0 (0%)         45m
Allocated resources:
(Total limits may be over 100 percent, i.e., overcommitted.)
Resource           Requests    Limits

cpu                850m (21%)  100m (2%)
memory             190Mi (2%)  390Mi (5%)
ephemeral-storage  0 (0%)      0 (0%)
hugepages-1Gi      0 (0%)      0 (0%)
hugepages-2Mi      0 (0%)      0 (0%)
Events:
Type    Reason                   Age   From        Message

Normal  Starting                 45m   kubelet     Starting kubelet.

Normal  NodeReady                41m   kubelet     Node  status is now: NodeReady

@vladikr Thanks for responding quickly.
kubectl describe nodes
Name:
Roles:
Labels:             beta.kubernetes.io/arch=amd64
beta.kubernetes.io/os=linux
kubernetes.io/arch=amd64
kubernetes.io/hostname=
kubernetes.io/os=linux
kubevirt.io/schedulable=true
Annotations:        flannel.alpha.coreos.com/backend-data: {"VNI":1,"VtepMAC":"62:c4:fb:b8:b3:1c"}
flannel.alpha.coreos.com/backend-type: vxlan
flannel.alpha.coreos.com/kube-subnet-manager: true
flannel.alpha.coreos.com/public-ip: <IP_ADDRESS>
kubeadm.alpha.kubernetes.io/cri-socket: /var/run/dockershim.sock
kubevirt.io/heartbeat: 2021-01-05T14:56:51Z
node.alpha.kubernetes.io/ttl: 0
volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Tue, 05 Jan 2021 16:16:29 +0200
Taints:
Unschedulable:      false
Lease:
HolderIdentity:
AcquireTime:
RenewTime:       Tue, 05 Jan 2021 16:57:07 +0200
Conditions:
Type                 Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message

NetworkUnavailable   False   Tue, 05 Jan 2021 16:17:35 +0200   Tue, 05 Jan 2021 16:17:35 +0200   FlannelIsUp                  Flannel is running on this node
MemoryPressure       False   Tue, 05 Jan 2021 16:54:02 +0200   Tue, 05 Jan 2021 16:16:29 +0200   KubeletHasSufficientMemory   kubelet has sufficient memory available
DiskPressure         False   Tue, 05 Jan 2021 16:54:02 +0200   Tue, 05 Jan 2021 16:16:29 +0200   KubeletHasNoDiskPressure     kubelet has no disk pressure
PIDPressure          False   Tue, 05 Jan 2021 16:54:02 +0200   Tue, 05 Jan 2021 16:16:29 +0200   KubeletHasSufficientPID      kubelet has sufficient PID available
Ready                True    Tue, 05 Jan 2021 16:54:02 +0200   Tue, 05 Jan 2021 16:16:31 +0200   KubeletReady                 kubelet is posting ready status
Addresses:
InternalIP:  <IP_ADDRESS>
Hostname:
Capacity:
cpu:                            4
devices.kubevirt.io/kvm:        110
devices.kubevirt.io/tun:        110
devices.kubevirt.io/vhost-net:  110
ephemeral-storage:              20509264Ki
hugepages-2Mi:                  13480Mi
memory:                         16425164Ki
pods:                           110
Allocatable:
cpu:                            4
devices.kubevirt.io/kvm:        0
devices.kubevirt.io/tun:        110
devices.kubevirt.io/vhost-net:  110
ephemeral-storage:<PHONE_NUMBER>2
hugepages-2Mi:                  13480Mi
memory:                         2519244Ki
pods:                           110
System Info:
Machine ID:                 813fd93e4b964ef6b929ca1ecbed231d
System UUID:                813fd93e-4b96-4ef6-b929-ca1ecbed231d
Boot ID:                    508800fe-ca59-411f-813e-01f54bc4a49a
Kernel Version:             4.18.0-25-generic
OS Image:                   Ubuntu 18.04.5 LTS
Operating System:           linux
Architecture:               amd64
Container Runtime Version:  docker://19.3.6
Kubelet Version:            v1.19.3
Kube-Proxy Version:         v1.19.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                 kube-flannel-ds-5wz59               100m (2%)     100m (2%)   50Mi (2%)        50Mi (2%)      40m
kube-system                 kube-proxy-rm8hk                    0 (0%)        0 (0%)      0 (0%)           0 (0%)         40m
kubevirt                    virt-api-69879b6659-fbrdx           0 (0%)        0 (0%)      0 (0%)           0 (0%)         35m
kubevirt                    virt-api-69879b6659-xcfmw           0 (0%)        0 (0%)      0 (0%)           0 (0%)         35m
kubevirt                    virt-controller-789bcb7458-2zdds    0 (0%)        0 (0%)      0 (0%)           0 (0%)         34m
kubevirt                    virt-controller-789bcb7458-mdr7x    0 (0%)        0 (0%)      0 (0%)           0 (0%)         34m
kubevirt                    virt-handler-5964v                  0 (0%)        0 (0%)      0 (0%)           0 (0%)         34m
kubevirt                    virt-operator-589f5568b8-dhcdj      0 (0%)        0 (0%)      0 (0%)           0 (0%)         38m
kubevirt                    virt-operator-589f5568b8-grpcp      0 (0%)        0 (0%)      0 (0%)           0 (0%)         38m
Allocated resources:
(Total limits may be over 100 percent, i.e., overcommitted.)
Resource                       Requests   Limits

cpu                            100m (2%)  100m (2%)
memory                         50Mi (2%)  50Mi (2%)
ephemeral-storage              0 (0%)     0 (0%)
hugepages-2Mi                  0 (0%)     0 (0%)
devices.kubevirt.io/kvm        0          0
devices.kubevirt.io/tun        0          0
devices.kubevirt.io/vhost-net  0          0
Events:
Type    Reason                   Age                From        Message

Normal  NodeHasSufficientMemory  40m (x7 over 40m)  kubelet     Node  status is now: NodeHasSufficientMemory
Normal  NodeHasNoDiskPressure    40m (x7 over 40m)  kubelet     Node  status is now: NodeHasNoDiskPressure
Normal  NodeHasSufficientPID     40m (x7 over 40m)  kubelet     Node  status is now: NodeHasSufficientPID
Normal  NodeReady                40m                kubelet     Node  status is now: NodeReady
Normal  Starting                 39m                kube-proxy  Starting kube-proxy.
Name:
Roles:              master
Labels:             beta.kubernetes.io/arch=amd64
beta.kubernetes.io/os=linux
kubernetes.io/arch=amd64
kubernetes.io/hostname=
kubernetes.io/os=linux
node-role.kubernetes.io/master=
Annotations:        flannel.alpha.coreos.com/backend-data: {"VNI":1,"VtepMAC":"5e:5e:43:72:99:f7"}
flannel.alpha.coreos.com/backend-type: vxlan
flannel.alpha.coreos.com/kube-subnet-manager: true
flannel.alpha.coreos.com/public-ip: <IP_ADDRESS>
kubeadm.alpha.kubernetes.io/cri-socket: /var/run/dockershim.sock
node.alpha.kubernetes.io/ttl: 0
volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Tue, 05 Jan 2021 16:11:01 +0200
Taints:             node-role.kubernetes.io/master:NoSchedule
Unschedulable:      false
Lease:
HolderIdentity:
AcquireTime:
RenewTime:       Tue, 05 Jan 2021 16:57:05 +0200
Conditions:
Type                 Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message

NetworkUnavailable   False   Tue, 05 Jan 2021 16:16:14 +0200   Tue, 05 Jan 2021 16:16:14 +0200   FlannelIsUp                  Flannel is running on this node
MemoryPressure       False   Tue, 05 Jan 2021 16:56:22 +0200   Tue, 05 Jan 2021 16:11:01 +0200   KubeletHasSufficientMemory   kubelet has sufficient memory available
DiskPressure         False   Tue, 05 Jan 2021 16:56:22 +0200   Tue, 05 Jan 2021 16:11:01 +0200   KubeletHasNoDiskPressure     kubelet has no disk pressure
PIDPressure          False   Tue, 05 Jan 2021 16:56:22 +0200   Tue, 05 Jan 2021 16:11:01 +0200   KubeletHasSufficientPID      kubelet has sufficient PID available
Ready                True    Tue, 05 Jan 2021 16:56:22 +0200   Tue, 05 Jan 2021 16:16:04 +0200   KubeletReady                 kubelet is posting ready status
Addresses:
InternalIP:  <IP_ADDRESS>
Hostname:
Capacity:
cpu:                4
ephemeral-storage:  20509264Ki
hugepages-1Gi:      0
hugepages-2Mi:      1Gi
memory:             8169724Ki
pods:               110
Allocatable:
cpu:                4
ephemeral-storage:<PHONE_NUMBER>2
hugepages-1Gi:      0
hugepages-2Mi:      1Gi
memory:             7018748Ki
pods:               110
System Info:
Machine ID:                 5255ead855cd4483af9ee14dcd8069d6
System UUID:                17617f19-f682-46d5-9b5d-7c9a5c53fcd6
Boot ID:                    35bd5e2e-2151-42c7-99e8-8f7cb7f9f151
Kernel Version:             4.18.0-25-generic
OS Image:                   Ubuntu 18.04.5 LTS
Operating System:           linux
Architecture:               amd64
Container Runtime Version:  docker://19.3.6
Kubelet Version:            v1.19.3
Kube-Proxy Version:         v1.19.3
PodCIDR:                      <IP_ADDRESS>/24
PodCIDRs:                     <IP_ADDRESS>/24
Non-terminated Pods:          (8 in total)
Namespace                   Name                                                    CPU Requests  CPU Limits  Memory Requests  Memory Limits  AGE

kube-system                 coredns-f9fd979d6-6sp2g                                 100m (2%)     0 (0%)      70Mi (1%)        170Mi (2%)     45m
kube-system                 coredns-f9fd979d6-75ff8                                 100m (2%)     0 (0%)      70Mi (1%)        170Mi (2%)     45m
kube-system                 etcd-                       0 (0%)        0 (0%)      0 (0%)           0 (0%)         45m
kube-system                 kube-apiserver-             250m (6%)     0 (0%)      0 (0%)           0 (0%)         45m
kube-system                 kube-controller-manager-    200m (5%)     0 (0%)      0 (0%)           0 (0%)         45m
kube-system                 kube-flannel-ds-kl5bx                                   100m (2%)     100m (2%)   50Mi (0%)        50Mi (0%)      41m
kube-system                 kube-proxy-xvq82                                        0 (0%)        0 (0%)      0 (0%)           0 (0%)         45m
kube-system                 kube-scheduler-             100m (2%)     0 (0%)      0 (0%)           0 (0%)         45m
Allocated resources:
(Total limits may be over 100 percent, i.e., overcommitted.)
Resource           Requests    Limits

cpu                850m (21%)  100m (2%)
memory             190Mi (2%)  390Mi (5%)
ephemeral-storage  0 (0%)      0 (0%)
hugepages-1Gi      0 (0%)      0 (0%)
hugepages-2Mi      0 (0%)      0 (0%)
Events:
Type    Reason                   Age   From        Message

Normal  Starting                 45m   kubelet     Starting kubelet.

Normal  NodeReady                41m   kubelet     Node  status is now: NodeReady

Thank you for the output.
Allocatable:
     cpu: 4
     devices.kubevirt.io/kvm: 0

Seems that there are no allocatable kvm devices available on the worker node.
This may happen if the device plugin decides that the provided device is not healthy.
When the device is re-appears it should be set as healthy again.
We log it as:                     logger.Infof("monitored device %s appeared", dpi.deviceName)
However,  from these logs, I see that the device was set to Unhealthy and then recovered, but I don't see any events that the device appeared, so I assume it's marked as Unhealty at this point.
I need some time to look into this, but in the meanwhile, perhaps you can restart the virt-handler - it should re-register the device plugins.
kubectl delete pod virt-handler-v4chs -n kubevirt

Thank you for the output.
Allocatable:
     cpu: 4
     devices.kubevirt.io/kvm: 0

Seems that there are no allocatable kvm devices available on the worker node.
This may happen if the device plugin decides that the provided device is not healthy.
When the device is re-appears it should be set as healthy again.
We log it as:                     logger.Infof("monitored device %s appeared", dpi.deviceName)
However,  from these logs, I see that the device was set to Unhealthy and then recovered, but I don't see any events that the device appeared, so I assume it's marked as Unhealty at this point.
I need some time to look into this, but in the meanwhile, perhaps you can restart the virt-handler - it should re-register the device plugins.
kubectl delete pod virt-handler-v4chs -n kubevirt

I believe I found the error but I don't have time to test it today. The server I've installed the virual machine on does not seem to support nested virtualization. I will Investigate and update this tomorrow.

I believe I found the error but I don't have time to test it today. The server I've installed the virual machine on does not seem to support nested virtualization. I will Investigate and update this tomorrow.

@vladikr Yes as I guessed the problem was with the node, for some reason the nested virtualization wasn't working properly. Creating new node on another server with working kvm nested virtualization worked. Thank you

@vladikr Yes as I guessed the problem was with the node, for some reason the nested virtualization wasn't working properly. Creating new node on another server with working kvm nested virtualization worked. Thank you

I had the same problem:
{"component":"virt-handler","level":"error","msg":"Error starting kvm device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: rpc error: code = Unknown desc = failed to dial device plugin: context deadline exceeded","timestamp":"2023-09-25T12:55:51.816054Z"}
{"component":"virt-handler","level":"error","msg":"Error starting sev device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: rpc error: code = Unknown desc = failed to dial device plugin: context deadline exceeded","timestamp":"2023-09-25T12:55:51.816095Z"}
{"component":"virt-handler","level":"error","msg":"Error starting tun device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: rpc error: code = Unknown desc = failed to dial device plugin: context deadline exceeded","timestamp":"2023-09-25T12:55:51.816079Z"}
{"component":"virt-handler","level":"error","msg":"Error starting vhost-net device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: rpc error: code = Unknown desc = failed to dial device plugin: context deadline exceeded","timestamp":"2023-09-25T12:55:51.905366Z"}
{"component":"virt-handler","level":"error","msg":"Error starting sev device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: rpc error: code = Unknown desc = failed to dial device plugin: context deadline exceeded","timestamp":"2023-09-25T12:56:12.819079Z"}
{"component":"virt-handler","level":"error","msg":"Error starting kvm device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: rpc error: code = Unknown desc = failed to dial device plugin: context deadline exceeded","timestamp":"2023-09-25T12:56:12.819119Z"}
{"component":"virt-handler","level":"error","msg":"Error starting tun device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: rpc error: code = Unknown desc = failed to dial device plugin: context deadline exceeded","timestamp":"2023-09-25T12:56:12.819103Z"}
{"component":"virt-handler","level":"error","msg":"Error starting vhost-net device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: rpc error: code = Unknown desc = failed to dial device plugin: context deadline exceeded","timestamp":"2023-09-25T12:56:12.917561Z"}

lsmod | grep kvm
kvm_intel             278528  0
kvm                   917504  1 kvm_intel
irqbypass              16384  1 kvm

error registering with device plugin manager: rpc error: code = Unknown desc = failed to dial device plugin: context deadline exceeded

@swq499809608 Is there anything interesting inside Kubelet logs?

kubectl logs -f  -n kubevirt virt-handler-7cjfn
{"component":"virt-handler","level":"error","msg":"Error starting vhost-net device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:13:41.299869Z"}
{"component":"virt-handler","level":"error","msg":"Error starting kvm device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:13:55.988984Z"}
{"component":"virt-handler","level":"error","msg":"Error starting sev device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:13:55.990066Z"}
{"component":"virt-handler","level":"error","msg":"Error starting tun device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:13:56.428113Z"}
{"component":"virt-handler","level":"error","msg":"Error starting vhost-net device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:13:57.308440Z"}
{"component":"virt-handler","level":"error","msg":"Error starting kvm device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:14:11.990716Z"}
{"component":"virt-handler","level":"error","msg":"Error starting sev device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:14:11.991819Z"}
{"component":"virt-handler","level":"error","msg":"Error starting tun device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:14:12.430704Z"}
{"component":"virt-handler","level":"error","msg":"Error starting vhost-net device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:14:13.320030Z"}
{"component":"virt-handler","level":"error","msg":"Error starting kvm device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:14:27.993427Z"}
{"component":"virt-handler","level":"error","msg":"Error starting sev device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:14:27.994486Z"}
{"component":"virt-handler","level":"error","msg":"Error starting tun device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:14:28.432340Z"}
{"component":"virt-handler","level":"error","msg":"Error starting vhost-net device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:14:29.330059Z"}
{"component":"virt-handler","level":"error","msg":"Error starting kvm device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:14:43.995878Z"}
{"component":"virt-handler","level":"error","msg":"Error starting sev device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:14:43.995901Z"}
{"component":"virt-handler","level":"error","msg":"Error starting tun device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:14:44.434756Z"}
{"component":"virt-handler","level":"error","msg":"Error starting vhost-net device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:14:45.338317Z"}
{"component":"virt-handler","level":"error","msg":"Error starting sev device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:14:59.997444Z"}
{"component":"virt-handler","level":"error","msg":"Error starting kvm device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:14:59.997474Z"}
{"component":"virt-handler","level":"error","msg":"Error starting tun device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:15:00.436212Z"}
{"component":"virt-handler","level":"error","msg":"Error starting vhost-net device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:15:01.350733Z"}
{"component":"virt-handler","level":"info","msg":"resyncing virt-launcher domains","pos":"cache.go:384","timestamp":"2023-09-26T07:15:14.094710Z"}
{"component":"virt-handler","level":"error","msg":"Error starting kvm device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:15:15.999795Z"}
{"component":"virt-handler","level":"error","msg":"Error starting sev device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:15:15.999821Z"}
{"component":"virt-handler","level":"error","msg":"Error starting tun device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:15:16.473682Z"}
{"component":"virt-handler","level":"error","msg":"Error starting vhost-net device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:15:17.358648Z"}
{"component":"virt-handler","level":"error","msg":"Error starting kvm device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:15:32.001459Z"}
{"component":"virt-handler","level":"error","msg":"Error starting sev device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:15:32.001483Z"}
{"component":"virt-handler","level":"error","msg":"Error starting tun device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:15:32.476328Z"}
{"component":"virt-handler","level":"error","msg":"Error starting vhost-net device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:15:33.365244Z"}
{"component":"virt-handler","level":"error","msg":"Error starting kvm device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:15:48.003295Z"}
{"component":"virt-handler","level":"error","msg":"Error starting sev device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:15:48.003305Z"}
{"component":"virt-handler","level":"error","msg":"Error starting tun device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:15:48.479274Z"}
{"component":"virt-handler","level":"error","msg":"Error starting vhost-net device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:15:49.374423Z"}
{"component":"virt-handler","level":"error","msg":"Error starting kvm device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:16:04.005460Z"}
{"component":"virt-handler","level":"error","msg":"Error starting sev device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:16:04.005440Z"}
{"component":"virt-handler","level":"error","msg":"Error starting tun device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:16:04.482426Z"}
{"component":"virt-handler","level":"error","msg":"Error starting vhost-net device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:16:05.383913Z"}
{"component":"virt-handler","level":"error","msg":"Error starting kvm device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:16:20.007914Z"}
{"component":"virt-handler","level":"error","msg":"Error starting sev device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:16:20.007895Z"}
{"component":"virt-handler","level":"error","msg":"Error starting tun device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:16:20.484598Z"}
{"component":"virt-handler","level":"error","msg":"Error starting vhost-net device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:16:21.394947Z"}
{"component":"virt-handler","level":"error","msg":"Error starting kvm device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:16:36.009371Z"}
{"component":"virt-handler","level":"error","msg":"Error starting sev device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:16:36.009399Z"}
{"component":"virt-handler","level":"error","msg":"Error starting tun device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:16:36.487312Z"}
{"component":"virt-handler","level":"error","msg":"Error starting vhost-net device plugin","pos":"device_controller.go:68","reason":"error registering with device plugin manager: context deadline exceeded","timestamp":"2023-09-26T07:16:37.403189Z"}

This is a virt-handler log indicating there might be something wrong in Kubelet.  Please check Kubelet logs.


Rigid body object pool

resolves #334
This will implement a rigid body object pool to prevent de-allocation on rigid body destroy.

Recent discussion #337 suggests this problem could be deeper than just the rigid body objects. Ill leave this PR up in case your interested in pooling rigid bodies, perhaps for performance but this may not properly address issue #334.


Azure Defender for IoT, wrong symmetric key path

in https://docs.microsoft.com/en-us/azure/defender-for-iot/device-builders/tutorial-standalone-agent-binary-installation the path /etc/defender_iot_micro_agent/connection_string.txt is used.
This /etc path works ok.

@sandervandevelde : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @sandervandevelde,
Thank you for the fix. I'll approve the change.
Thanks,
Pat
#sign-off


Add Attribute to all vector types

It is not possible to set the attributes to vector-types. This is currently achievable by converting to Robj, setting attribute, and converting back. This indirection should not be necessary.
Update: This was brought on due to the desire to include
fn as_is_col(x: impl IntoRobj) -> Robj {
    let robj = x.into_robj();
    List::from_values([robj])
        .into_robj()
        .set_class(&["AsIs"])
        .unwrap()
}

(due to @JosiahParry) as an analogue for I() in R.

This is great! We'll need to add some integration tests, though—I know, I know.
I can try to do it this evening.

At present this does not work because it requires the value to be mutable. It means that .set_attrib() cannot be used on a variable that is provided as an argument without first reassigning it a la let mut x = x. Note that .as_mut() will not work either because it returns a slice.
#[extendr]
fn strings_named(x: Strings) -> Strings {
    let mut x = x;
    x.set_attrib(
        "names",
        x.iter()
            .map(|xi| xi.as_str().to_string())
            .collect::<Vec<_>>(),
    )
    .unwrap();
    x
}

This implementation implies that it should only be used on items created inside the body of the function. Now, this makes sense to some degree because the attributes are added to the SEXP by reference and not by cloning.
Note that this behavior is true today, though it is more opaque:
library(rextendr)

rust_function(r"-(
fn tst(x: Robj) {
  x.set_attrib("hello", &["world"]);
}
)-")
#> ℹ build directory: '/private/var/folders/wd/xq999jjj3bx2w8cpg7lkfxlm0000gn/T/RtmpuaE5gG/file180d32dbc0427'
#> ✔ Writing '/private/var/folders/wd/xq999jjj3bx2w8cpg7lkfxlm0000gn/T/RtmpuaE5gG/file180d32dbc0427/target/extendr_wrappers.R'

x <- list()
tst(x)
x
#> list()
#> attr(,"hello")
#> [1] "world"

For this reason, I actually think this PR does a better job than the status quo for handling attributes. I think, however, this is another reason why  we should allow mutable arguments.

Snapshot tests generated, and various warnings have been eliminated.
I think the snapshot file with new in it should be deleted. Just did it.
@JosiahParry Maybe we should attempt to document the Attribute better?

@CGMossa thank you for your work! All checks except the latest on windows due to CI are passing. Integration tests are looking good as well.
Thank you again for your quick collaboration on getting this through!!


fix(project): upgrade vulnerable minimatch

To upgrade minimatch required typescript ^4.0.0 which required the removal of the depracated tslint.
PR summary

minimatch dependency updated due to vulnerability
deprecated tslint removed

Fixes: <! -- link to issue -->
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[x] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

:tada: This PR is included in version 0.0.12 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Support async API

Thank you for this wonderful project.
But can you provide an async version of this library? Async is now almost mandatory for any python web apps.

@zyddnys Hi, thanks for the suggestion. Indeed, this is already in planning ;)

Closing issue since @nidhaloff mentioned the change is in the pipeline


backend.status()

This might be actually a terra issue. @diego-plan9 and @ajavadia we need to decide on this. My view is I think backend.status() should not be required and be optional for remote backends. I know we may have discussed it to be required but this does not really make sense for a local backend. I am sure @atilag will agree with me on this :-).
This being said assuming it is is required then when i run

I think this is giving the qiskit-terra version, not the JKU version. So if we are going to keep status in local then we need to update the version.
Let's assume that we keep it in local then pending_job should not be required it should be just optional that you add for a backend that has a queue. Second, if the status message is empty should we show it?

Hmm, then we are talking about a specs change indeed! For simplicity (in the bureocracy deparment), I'd go for the quick fix of making jku_backend provide the right version (probably by implementing the method itself, with a variation of https://github.com/Qiskit/qiskit-terra/blob/master/qiskit/providers/basebackend.py#L71-L81), and move the discussion about the backend status being required or not to the terra repo.

If we implement the method we don’t need to add the pending jobs. If this is correct then I’m good we can keep it as required.  The reason I don’t like pending jobs is if I run 100 job locally and then look this does not update as there is no queue.

Don’t worry I see the above is not possible as it’s in the marshmallow schema.

Can we close this here?

We need to just update the backend status method to have the name fixed and the version taking from this repo not terra.

Fixed in #48.


Current links to connect-mapstate lead to "404 Not Found". They have been replaced with the correct one.

Fixed a couple of those updated links, which need to go to the file itself. Thanks!


[JENKINS-29322] ServletRequest.getEncoding may be null

JENKINS-29322
Note that extractRequestBody already uses ServletRequest.getReader to do some kind of decoding, so I am not sure if it even correct to ask for the request encoding when processing the URL decoding of that already-decoded text. However this is the most conservative change since if this was null, the code would definitely hit the bug, so we cannot be doing any worse.
@reviewbybees

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.


restoring original location for apigateway container image

Figure out how to re-configure docker hub image openwhisk/apigateway to point to new named git location openwhisk/openwhisk-apigateway
This is enable and building automatically.
https://hub.docker.com/r/openwhisk/apigateway/
I will delete bad location a week from now
https://hub.docker.com/r/openwhisk/openwhisk-apigateway/

PG 2 1101

@rabbah this is ready now


[Error] Cloud flare clearance failed, please wait one minute and try again

Hi.
I am using procuremnt for 2 weeks, since yesterday I have this Error, earlier it was working perfect.
Extract from DebugInfo:
"
[27-11-2019 19:13] Failed to build HTTP request and get response for: method=GET, url='https://www.pathofexile.com/login', allowAutoRedirects=, requestData='': Serwer zdalny zwrócił błąd: (503) Serwer jest niedostępny.
[27-11-2019 19:14] System.Exception: Cloud flare clearance failed, please wait one minute and try again ---> System.AggregateException: Wystąpił przynajmniej jeden błąd. ---> CloudFlareUtilities.CloudFlareClearanceException: Clearance failed after 3 attempt(s).
w CloudFlareUtilities.ClearanceHandler.d__20.MoveNext()
--- Koniec śladu stosu wyjątków wewnętrznych ---
w System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification)    w POEApi.Transport.HttpTransport.CloudFlareSessionIdLogin()    --- Koniec śladu stosu wyjątków wewnętrznych ---    w POEApi.Transport.HttpTransport.CloudFlareSessionIdLogin()    w POEApi.Transport.HttpTransport.Authenticate(String email, SecureString password)    w POEApi.Model.POEModel.Authenticate(String email, SecureString password, Boolean offline, String realm)    w Procurement.ViewModel.LoginWindowViewModel.<>c__DisplayClass23_0.<Login>b__0()    w System.Threading.Tasks.Task.Execute() [27-11-2019 19:14] Failed to build HTTP request and get response for: method=GET, url='https://www.pathofexile.com/login', allowAutoRedirects=, requestData='': Serwer zdalny zwrócił błąd: (503) Serwer jest niedostępny. [27-11-2019 19:14] System.Exception: Cloud flare clearance failed, please wait one minute and try again ---> System.AggregateException: Wystąpił przynajmniej jeden błąd. ---> CloudFlareUtilities.CloudFlareClearanceException: Clearance failed after 3 attempt(s).    w CloudFlareUtilities.ClearanceHandler.<SendAsync>d__20.MoveNext()    --- Koniec śladu stosu wyjątków wewnętrznych ---    w System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification)
w POEApi.Transport.HttpTransport.CloudFlareSessionIdLogin()
--- Koniec śladu stosu wyjątków wewnętrznych ---
w POEApi.Transport.HttpTransport.CloudFlareSessionIdLogin()
w POEApi.Transport.HttpTransport.Authenticate(String email, SecureString password)
w POEApi.Model.POEModel.Authenticate(String email, SecureString password, Boolean offline, String realm)
w Procurement.ViewModel.LoginWindowViewModel.<>c__DisplayClass23_0.b__0()
w System.Threading.Tasks.Task.Execute()
"

The POESESSID you get from the website is only valid for a limited time.  Make sure you are still logged in to the website, or log out and log in again and get a new session id.

Thx for response, unfoucountely it's not that. I took POESESSID from other browser, so it is fressh one. I also used password reset and then copied POESESSID or reinstall procurement and all of those did not work.

Having the same issue since today. Tried waiting hours & refreshing the session id :|

Yo! Same problem here, I've been lurking here for THREE days :(.. And today I really got fed up and decided to post.
I am still blocked from entering Procurement ( ver 1.27.2). Same error every single time.
Acquisition tool works perfectly though.

I Edited the source code and changed the nuget packages. If you clone my fork (https://github.com/Grzy7316/Procurement.git) and download visual studio community, you can compile it for yourself and have a working version

I Edited the source code and changed the nuget packages. If you clone my fork (Grzy7316/Procurement.git) and download visual studio community, you can compile it for yourself and have a working version

@Grzy7316 I'm aware of that though most ppl using the tool have no dev background. That's why I request a simple way for these ppl to install the fix :relaxed:

Procurement 1.28.0 has been released, which includes @Grzy7316 's fix.


Write a C program to find the maximum sum of a contiguous subarray (circular)

Description
Write a C program to find the maximum sum of a contiguous subarray (circular)
Maximum sum of a circular subarray is the task of finding the contiguous subarray within a circular one-dimensional array of numbers which has the largest sum. For example, for the sequence of values 10, -3, -4, 7, 6, 5, -4, -1; the contiguous subarray with the largest sum is 7, 6, 5, with sum 18.
Input  : [8, -8, 9, -9, 10, -11, 12]
Output : 22

How to contribute

Save the solution in program/FindTheMaximumSumOfAContiguousSubarray(circular).c file
Add FindTheMaximumSumOfAContiguousSubarray(circular).c file in find-the-maximum-sum-of-a-contiguous-subarray-(circular) folder

I want to work on this

!assign


Create CI workflow

Description
Add a release workflow
Warning
Do not forget to init a CHANGELOG file and a first tag 0.0.0

Actually it's better to not add the CHANGELOG file, it will be generated with a header by the action


Orbot can not reconnet to tor

Hi, I have issue with app. It can not reconnect to tor (after installation first connection is successful but if I want to connect a second time it says "connecting" stops after a second and connection is not created.
OS: iOS 16.5
Device: iPhone 14 plus

DI have this exact same issue. Using an iPad with iOS 16.5.
I installed Orbot after my Onion Browser app said I had to install Orbot to continue to use the app. Orbot worked the first time I installed it, but then cannot connect; just keeps trying to connect and then returns to start over. When I expand the window to see what is happening, I see “ Jun 17 10:02:20.000 [notice] {GENERAL} Parsing GEOIP IPv6 file /var/containers/Bundle/Application/A8425778-4EA2-442F-9109-E3A6F249D3AF/Orbot.app/Frameworks/Tor.framework/GeoIP.bundle/geoip6. Jun 17 10:02:21.000 [notice] {CONTROL} Bootstrapped 0% (starting): Starting”. I have another VPN on my device but it is disconnected and auto connect is off. If I delete the Orbot app and then re-install it, it again works the first time I use it, but then the above happens again if I try to use it a second time.

Cleaning the cache might help. (In the drop-down menu, Settings, at the very end.)
Unfortunately, Apple gives us a hard limit of 50 MByte RAM usage.
If the list of nodes, Tor acquires over time, gets too big. Then Tor hits the RAM limit on start and gets killed again. (This list is cached on disk and reused, so you can connect faster.)
Let me know, if this helps!
I get more and more notifications about this. Maybe, there's something with the network going on and we will need to rethink that cache handling. What do you think, @n8fr8?

Cleaning the cache might help. (In the drop-down menu, Settings, at the very end.)
Unfortunately, Apple gives us a hard limit of 50 MByte RAM usage.
If the list of nodes, Tor acquires over time, gets too big, Tor hits the RAM limit on start and gets killed again. (This list is cached on disk and reused, so you can connect faster.)
Let me know, if this helps!
I get more and more notifications about this. Maybe, there's something with the network going on and we will need to rethink that cache handling. What do you think, @n8fr8?

Clearing cache works 🙂
I suggest adding option to automatically clear cache when disconnecting or moving clear cache button to faster to access place (main view)

Thanks. That worked for me also (even though it took a minute to find the Clear Cache command because it wasn’t showing under Settings until I scrolled down). AndyOn Jun 17, 2023, at 3:07 PM, Benjamin Erhart @.***> wrote:
Cleaning the cache might help. (In the drop-down menu, Settings, at the very end.)
Unfortunately, Apple gives us a hard limit of 50 MByte RAM usage.
If the list of nodes, Tor acquires over time, gets too big. Then Tor hits the RAM limit on start and gets killed again. (This list is cached on disk and reused, so you can connect faster.)
Let me know, if this helps!
I get more and more notifications about this. Maybe, there's something with the network going on and we will need to rethink that cache handling. What do you think, @n8fr8?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

Thanks. That worked for me also (even though it took a minute to find the Clear Cache command because it wasn’t showing under Settings until I scrolled down). AndyOn Jun 17, 2023, at 5:19 PM, VGFP @.***> wrote:
Cleaning the cache might help. (In the drop-down menu, Settings, at the very end.)
Unfortunately, Apple gives us a hard limit of 50 MByte RAM usage.
If the list of nodes, Tor acquires over time, gets too big, Tor hits the RAM limit on start and gets killed again. (This list is cached on disk and reused, so you can connect faster.)
Let me know, if this helps!
I get more and more notifications about this. Maybe, there's something with the network going on and we will need to rethink that cache handling. What do you think, @n8fr8?
Clearing cache works 🙂
I suggest adding option to automatically clear cache when disconnecting or moving clear cache button to faster to access place (main view)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

https://twitter.com/tladesignz/status/1672202386310307840


Update headers are empty check on INJECT_HEADERS

An empty headers dict currently is not treated as having 'no headers to inject'
Discussed in: https://github.com/prisma/graphql-playground/issues/893
Fixes #893 (at least in the case where headers are empty).
Changes proposed in this pull request:

Fix logic in checking if headers are empty in INJECT_HEADERS

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

headers can be any in props:
https://github.com/prisma/graphql-playground/blob/master/packages/graphql-playground-react/src/components/Playground.tsx#L85
but are typed as strings in the injectheaders prop:
https://github.com/prisma/graphql-playground/blob/master/packages/graphql-playground-react/src/components/Playground.tsx#L102
and (as far as i can tell in my local use) are sent as a dictionary:
https://github.com/prisma/graphql-playground/blob/master/packages/graphql-playground-react/src/components/Playground.tsx#L102


Migrate PLUGS to space config

Having a separate PLUGS file for maintaining what plugs to activate made sense at the time. But by now we have a pretty robust alternative with space config and should just move to that.
This can be done in a backwards compatible way by supporting both, with space config becoming the new way.
To figure out: how to implement Plugs: Add, which currently updates your PLUGS file automatically.

Perhaps drop the Plugs: Add command... ?

Proposal:

Keep the plugs list in Space Config as:

```space-config
plugs:
  - github:silverbulletmd/silverbullet-git/git.plug.js
  - ghr:Maarrk/silverbullet-grep
```

Plugs: Add appends to this list on the current page

if there is no space-config block, add it at the end of the page
if the space-config block doesn't have plugs: at the top level, append it at the end of the block
append the URI into the list

If the command is ran on the PLUGS page, it changes the yaml block with a list into the space-config block with the list under plugs: - this way the update happens automatically for the user, but in front of their eyes

Potential problem: there is more ways to write a list in YAML
```space-config
plugs: [ github:silverbulletmd/silverbullet-git/git.plug.js, ghr:Maarrk/silverbullet-grep ]
```

But I think this can also be handled reasonably if the inserting is done on the YAML as a parsetree instead of just adding a line

I think this makes sense. The only nasty thing is you probably want to update YAML without rewriting it (e.g. so that comments get lost, reformat everything). For the PLUGS file the whole plug list was always rewritten when using Plugs: Add I think, but in the new system I wouldn't want to happen. It should somehow attempt a minimal change.

New idea: the Plugs: Add command accepts a string argument that fills the editor.prompt, there can be a button {[Plugs: Add|Install now](https://example.com/cool.plug.js)}. The prompt would still show the user the address before adding it, so I think it's OK
Because of that, I'm back to the idea that the command should edit the PLUGS page, even if they can be loaded from anywhere, updated the https://github.com/silverbulletmd/silverbullet/issues/1042#issuecomment-2413192106

Finally got around to finishing this in #1122

For the PLUGS file the whole plug list was always rewritten when using Plugs: Add I think, but in the new system I wouldn't want to happen. It should somehow attempt a minimal change.

This behaviour is separated into insertIntoPlugPage function, which got a bit large in order to support all the cases with minimal edits, but at least it's well commented (I think) and has tests written for a bunch of scenarios.


How to check if choice has been already selected for an element?

I have following function which selected mutiple fields and makes it searchable.
function createSearchableTargetFields() {
    var targetFields = document.querySelectorAll("*[id*=target]");
    targetFields.forEach(field => {
         choices = new Choices(field, {
              searchResultLimit: 10000
          });
      })
 }

If I call this function twice like below, I'll get the following error in my console log
 createSearchableTargetFields();

  /** Some event listener will call this*/
  createSearchableTargetFields();

Error:
choices.min.js:11 Trying to initialise Choices on element already initialised
n @ choices.min.js:11
targetFields.forEach.field @ edit:338
createSearchableTargetFields @ edit:336
addButton.addEventListener @ edit:349

Is there a way to check if an Choice has already been selected for an element?

I want following behaviour
function createSearchableTargetFields() {
    var targetFields = document.querySelectorAll("*[id*=target]");

    if choice not enabled for this field {
        targetFields.forEach(field => {
             choices = new Choices(field, {
                  searchResultLimit: 10000
              });
          })
    }
 }

Looking for something similar to this anyone found a solution?

I found a solution for this, but maybe not the best one - but so far it works.
After initializing the element, choicesJS adds the data-attribute data-active="true" to the element. As long as your element doesn't get disabled in some circumstances this should work.
$.each($(".choices-single"), function(key, value) {
  let element = $(this);

  if(element.data('choice') !== 'active') {
    const choices = new Choices(element.get(0), {
      ...Options
    });
  }
})

(I'm fetching this as an jQuery object for other purposes, but choicesJS can't handle the jQuery object and expects a DOM object)

how can i disable it, if already initialising or how can i add or remove values into already initialised element.

@Hel5ing what do you want to achieve in your ???? part?
The problem in this thread is, that you get an error if you initialize choicesJS twice.


Wrong page number

Attach (recommended) or Link to PDF file here:
https://www.jstage.jst.go.jp/article/jsmr/55/0/55_0502/_pdf/-char/en
Configuration:

Web browser and its version: Firefox current
Operating system and its version: Mac OS X
PDF.js version: 2.3.200 and native Firefox viewer

Steps to reproduce the problem:

Open PDF
The page selector shows the wrong number (+80), e.g. page 1 is 81, 2 is 82 etc.

This is intended behaviour, and this issue is thus INVALID, since the PDF document uses Page Labels; see http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#G11.1696265

This is intended behaviour, since the PDF document uses Page Labels; see http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#G11.1696265


ML module plans

Question
i know that ML module is not supported yet, any way i could help with that since i want to use CascadeClassifier i think its in the ml module (i didnt check )
if i cant help with it, any time plan for it?

@abdelaziz-mahdy
If you just need CascadeClassifier, it is included in objdetect module, and has been implemented, https://docs.opencv.org/4.x/d1/de5/classcv_1_1CascadeClassifier.html
https://github.com/rainyl/opencv_dart/blob/4af53eabbd7cd077b4f27d77de7b109186b78ec7/lib/src/objdetect/objdetect.dart#L15
https://github.com/rainyl/opencv_dart/blob/4af53eabbd7cd077b4f27d77de7b109186b78ec7/test/objdetect_test.dart#L6
It seems training machine learning models using python and other tools is a more common and fashion way nowadays, and I have no much free time, so ML module was not implemented and not planned recently, maybe it will be added several months later when I have some time.
Anyway, it is true that some people need ML module, I(and other users) will be grateful if you can implement it.

Thank you very much for the links and the awesome package, I will check what needs to be implemented and try to do it

:smile:

i am trying to make some guide lines so that i follow if its okay

Branch Selection:

Should I work on the main branch or the native assets branch? since The native assets branch has many changes.

Workflow with ffigen:

Add the desired implementation in the .h files.
Implement the logic in the .cpp files.
Add the interface in Dart.
Create the test cases for the Dart interface.

Checklist:

[ ] Determine the correct branch to work on.
[ ] Add desired implementation in .h files.
[ ] Implement logic in .cpp files.
[ ] Add interface in Dart.
[ ] Create test cases for the Dart interface.

Questions:

OpenCV on iOS:

Have you tried using OpenCV on a clean project in iOS?
I remember having an issue with iOS and FFI where the C++ files get ignored, and the developer has to import them manually. I will check if this is still a problem. The native assets should fix this issue.

wow, you are the author of pytorch_lite, cool 👍
For the questions:

Branch Selection: develop on a new branch based on main, it is easy to update native-assets once finished on main.
OpenCV on iOS: as you said, for ios the .framework is used, I have no apple devices so not tested, but other developers tested and it worked.

BTW, you can find more build instructions in workflow file, thanks for your efforts in advance.

One more thing, to speedup the build of opencv_dart, opencv itself is built in another repo with ML disabled, I have enabled it but the workflow has not finished yet, generally it will take about 40 min, once finished, the published tag will be 4.9.0+3 so you need to change the opencv version in conanfile.py to "4.9.0+3" at https://github.com/rainyl/opencv_dart/blob/4af53eabbd7cd077b4f27d77de7b109186b78ec7/conanfile.py#L10
You can check the build process here:

Oh thank you for that, is there is a guide you follow of what the headers are and the implementation for the functions? I checked gocv but looks like there is no ml module or I can't find it,
If there is something I can take a reference that will make it much easier

Yes, this project was originally developed based on gocv, but now nearly every API has been refactored to cache exceptions, the most important guide is the documentation of opencv, i.e., wrap the classes and functions with C-style functions.
You can take a look at cv.Subdiv2D in this PR: #60
headers:
https://github.com/rainyl/opencv_dart/blob/d4690613c53c88149b110cd127e0331eb512d019/src/imgproc/imgproc.h#L168-L187
implementation:
https://github.com/rainyl/opencv_dart/blob/d4690613c53c88149b110cd127e0331eb512d019/src/imgproc/imgproc.cpp#L751-L888

ffigen fails in files not related to the file i made

is that a problem from my side?
running  conan build . -b missing compiled successfully

Well, I developed on windows and it worked normally, maybe macos needs stddef.h, feel free to add it.

I have published a new branch ml with some data structures wrapped, but they were not tested, just for some detailed instructions and methods to provide some help, but forgive me that I have no more time to finish it, take a look and hoping it can help you~

Nice, thank you it helps, also now I know that you would prefer if each class has separate files, since I was implementing them in one file
And the cmake change, I forgot that part
Anyway I will try to implement it and let's see if I achieve something good ❤


Fix for heap buffer overflow in partition_kernel_impl()

Added check to partition kernel to prevent read and write out-of-bounds. The number of indices is partitions+1, this are also the number of threads necessary. The writes and reads out-of-bounds have the same value as the last value in the indices array.

All tests pass.  LGTM


problem with latest update

when using the latest version 3.2.0 of your plugin I get the following error in the console of safari and Chrome.
Uncaught TypeError: Cannot read property 'tagName' of undefined
a	@	iframeResizer.js:855
(anonymous function)	@	mootools-core.js:88
(anonymous function)	@	iframeResizer.js:876
Before I used version 2.8.6 so I reverted to that version for now, because there I don't get any mistakes....

Can you please add a link and I'll have a look.

Since I have to use the site that works (so I use iframeresizer 2.8.6) I unfortunately don't have a link to the site. The thing is I also get other Error messages on that site and on another environment 3.2.0 works. So its probably some sort of problem where 2 plugins interfere....

Could you add your call to the script here. Just wondering what settings your using.

iFrameResize({log : true,enablePublicMethods : true,enableInPageLinks : true});

Are you using an old version of mootools? To me it looks like the bug is with that. I expect you can work around it by passing the iframe directly, rather than searching for it.
 var myIFrame = document.getElementById('myIFrame');
 iFrameResize({log : true,inPageLinks : true},myIFrame);

Note the options in v3 have changed a little.


Update Discord invite link

Points to Nerd Cave Development server which is now archived.

New invite: https://discord.gg/rgK9cGTwEs


Sniffnet is closing itself on open v1.2.0 (MacOS)

To Reproduce

Download to MacOs Setup V1.1.4
Install
Try to open sniffnet
it prompt you to enter password
now it breaks and close back

Expected behavior
expected to start using the app after installation
Desktop

OS: MacOS Montrey Version 12.6

Thanks for reporting!
The problem is basically the same as before, now you just don't see the terminal.
To verify that the problem is the same, please type
sudo /*/Sniffnet.app/Contents/MacOS/sniffnet

Yes, it returns the same, Thank you for this good work

Thanks for having verified. I close this as a duplicate of #176
I will try to understand what the cause could be and let you know if I have updates.


Add shortcut to sourcefile of published version to sidepanel

Show source file in Loader. This enables a user to return to the original scene of any published version by copying a path and pasting it into the application Open Scene dialog.

Coverage decreased (-0.4%) to 35.257% when pulling 37e58899601dc40cc0713646f2acdf8e678b2f8b on mottosso:sourceFile into 0dde54024fdd952126ab10428d4dce24f3adf824 on mindbender-studio:master.


Interactive histogram is super jumpy on mouse over

Informations

Qiskit Terra version: master
Python version: 3.7
Operating system: OSX

What is the current behavior?
Interactive histogram is super jumpy when moving mouse over.

Steps to reproduce the problem
What is the expected behavior?
Suggested solutions

@filemaster

The problem is the 2D library is trying to make room for the labels scaling the graph.
A fix is in progress and it will be released asap.

See: #1358

and done. Thanks


not found 404 and missing open

The following is not found:
godoc.org / github.com/nanobox-io/golang-hatchet
from:

For an example of a qualified logger see here.

Using a nil Logger results in lumber for a console log, ok, for playing around.
Also, there isn't an Open for an existing database, so something like this would be nice:
// Open an existing scribble database at the desired directory location, and
// return a *Driver to then use for interacting with the database
func Open(dir string, logger Logger) (driver *Driver, err error) {
	dir = filepath.Clean(dir)

	// ensure the database location does exist
	if _, err := os.Stat(dir); err != nil {
		fmt.Printf("Database, '%s' does not exist.\n", dir)
		os.Exit(1)
	}

	if logger == nil {
		logger = lumber.NewConsoleLogger(lumber.INFO)
	}

	driver = &Driver{
		dir:     dir,
		mutexes: make(map[string]sync.Mutex),
		log:     logger,
	}

	logger.Info("Opening scribble database at '%v'...\n", dir)

	return driver, nil
}

... or perhaps that isn't a valid use case (well, it is for me).
Thanks for scribble.

Open... thats a great idea :), I'll work on getting that in first thing on monday.
As for hatchet, we decided that project isn't necessary so we discontinued it. I thought I removed all reference to it from the source, but I might have missed something. I'll comb through again and catch anything I missed.
A "qualified logger" is now anything that satisfies the interface at the top of scribble.go.

@cleesmith thank you for submitting this. This issue has been addressed here (https://github.com/nanobox-io/golang-scribble/pull/8). Now you can simply specify an existing database on New and it will use it if it exists, or create it if it doesn't.


Bigtable: 17. improve ranges

Add exactMatch overrides that take strings
Add equals & hashCode
add special handling for empty ByteString endpoints in reanges
add ability to create ByteStringRanges using a prefix

Rebased. Please merge when ready


Recover joint angles from mesh

Is there a way to recover joint angles from the resulting mesh vertices (like the case of joint positions via J regressor)? I want to access the joint angles quality produced by SMPL-based methods. Thanks in advance!

Hi:) There is no readily available solution. One way is to train a (mesh vertices -> SMPL parameters) neural network.

Thanks for your quick response!


[Bug] [Master] NullPointerException caused by deleting resource

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
version :3.1.2
When I delete the resources of a Spark task and start it, the job will fail with NullPointerException

I have found the problem code, please allow me to submit the code.
What you expected to happen
When I delete the resources of a Spark task and start it, the job will fail with NullPointerException ,

I don't think there should be any exception. It should prompt that the resource does not exist. I have found the problem code, please allow me to submit the code.
How to reproduce

Create a Spark-type workflow definition, reference a resource (such as jar), and then execute the workflow normally;

Offline the workflow, delete the resource, go online the workflow, and finally execute the workflow.

Anything else
No response
Version
3.1.x
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

guys, I hava same probloms in 3.0 , put file overwrite in hdfs can be useful.

The method you said can indeed replace resources, but I think that after deleting resources from the web page and running the task, we should still prompt that resources no longer exist, because not everyone knows that resources can be replaced from hdfs

Hi, @LiJie20190102 , this issue duplicates with https://github.com/apache/dolphinscheduler/issues/13596, you can leave message to work on this under that issue.

Hi, @JaayYoung , in dev, resource center has been refactored, and support re-upload operation in ds now, maybe release at version 3.2.0. Also, delete and upload resource with same name again in ds ui page should better not affect task execution, it's still under discussion, you can follow https://github.com/apache/dolphinscheduler/issues/13651.


Added commit confirm functionality

Commit confirm functionality added to napalm base. It introduces new optional
argument in commit_config method and new method commit_confirm for
confirmation pending commit. It was briefly discussed under napalm-junos#126

Hi @mirceaulinic,
Sure, I can change it to confirmed and I am happy to make PR for Junos driver. I have already tested it a little bit, so I'll try to create PR over the weekend :)
Best regards,
Kamil

@mirceaulinic , not sure about confirmed=60. What does confirmed mean? Is it going to confirm itself in 60 seconds? In plain english this confirmed option does the opposite of what the wording indicates. If you prefer rollback=60 or auto_rollback=60 or even revert=60 or something else i I am fine with alternatives to revert_in but confirmed feels counterintuitive.

Hmm, I think that rollback can be misleading as there is already method with the same name. I would vote for auto_rollback as an alternative or maybe revert_in is not a bad name as it seems to be the most descriptive.
BTW I was thinking about time unit for this parameter. Should we use seconds or minutes? Seconds seems to be the best choice but junos accepts rollback time in minutes (minimal time 1 min). IOSXR as far as I remember takes rollback time in seconds. Of course, we can normalize this inside drivers code but what if someone provides 10 sec as rollback time for junos? Should we throw an exception or just time should be increased to possible minimal value? I think we should discuss this aspect as well to have clear guidelines for implementations in all drivers.

I see your point @dbarrosop - confirmed is indeed less self-explanatory than revert_in.
The reason I would still prefer it is that I suspect network engineers are more used with this term. If you look at:

junos:

<EMAIL_ADDRESS>commit confirmed ?
Possible completions:
  <[Enter]>            Execute this command
  <timeout>            Number of minutes until automatic rollback (1..65535)

iosxr

RP/0/RSP0/CPU0:edge01.flw01(config)#commit confirmed ?
  <30-65535>  Seconds until rollback unless there is a confirming commit
  minutes     Specify the rollback timer in the minutes

Regarding the time unit @kderynski: yes, and I think we should specify the rollback time in minutes. This way we avoid any conflict with Junos and other drivers can easily convert minutes to seconds.

Yeah, I understand that most vendors are just copying junos nomenclature for this and going with the "confirmed" keyword, I think even EOS named it like that on their latest release. That doesn't make it right. I prefer the python philosophy of making things readable as a novel rather than just doing things because someone in the past made a poor naming decision. In addition, it might be the difference between being sued or not by some CLI industry standard maker ;)
Anyway, I don't want to drag this just because we don't agree on the name of the argument. I will delegate the naming decision to @mirceaulinic . Feel free to choose one by any criteria you prefer: going with the industry standard, the readable one or just flipping a coin : )

@mirceaulinic let me know when you decide which name should we use :) After that, I will change it in this PR and in PR for junos driver.
Using minutes instead of seconds sounds reasonable to me (I thought that IOS XR accepts only seconds). I was thinking originally to convert seconds to minutes (to maintain support for sub-minute rollback for a platform which supports it). Conversion for junos may look like this:
revert_in = 1 if revert_in and revert_in < 60 else revert_in // 60

@dbarrosop

Yeah, I understand that most vendors are just copying junos nomenclature for this and going with the "confirmed" keyword, I think even EOS named it like that on their latest release. That doesn't make it right. I prefer the python philosophy of making things readable as a novel rather than just doing things because someone in the past made a poor naming decision.

No, it doesn't make it right and I continue to agree with you on this. I just hope it would make it more intuitive for network engineers familiar with the context - as you said because copying the wrong nomenclature.

In addition, it might be the difference between being sued or not by some CLI industry standard maker ;)

LOL - good one! :)
@kderynski

I thought that IOS XR accepts only seconds

Yes, through the XML agent only seconds seems to allowed. So whoever will implement the changes for the XR driver, will need to convert the rollback time from minutes to seconds, i.e. rollback_time = confirmed * 60.
When updating the doc, please also add a note emphasising that this feature is not supported by all drivers. This is very important to be clear as daylight! Feel free to expand on this as much as you consider it's enough for someone completely new to understand!
Thanks,
Mircea

It would be great if you'd add in the docstring of commit_config a version of the text you have included in https://github.com/napalm-automation/napalm/pull/355. If could even be the same; I think it's very important to be clear what people should expect from this.

I think it is probably better to use confirmed for the name as this name has been adopted as the industry standard for this term (and I think it is reasonably logical i.e. you have to confirm the commit in this amount of time).
Either way we should just choose and get this done.


feat: document the server-side generation of Delta Artifacts

Changelog: Title
Ticket: MEN-5807
Signed-off-by: Fabio Tranchitella<EMAIL_ADDRESS>

@lluiscampos ready for a second round of reviews


fix embedded-hal is_low impl

fixes #137

Thank you for reporting this issue and providing a fix. That does indeed look like a bug.


RDS implementations (basic operations)

Hello :) I'm using ex_aws for a project for my master's thesis (only the S3 wrapper so far) and I need to use RDS also. Since you don't have a RDS implementation/wrapper I decided to try to contribute and do it myself instead of building a personal wrapper that would then go to waste.
I only need some basic operations from the RDS API (mainly the ones from the Instances endpoint and a couple from the Databases endpoint) and since I'm short on time this will be my main focus. However if all goes well I'll try to do a full implementation.
I've read the Contributing file and I'll stick to the guidelines :+1:

Hello @benwilson512 :) When possible, would you mind giving me some feedback about this PR so far?
Thank you :+1:

General notes:

[ ] I would go through each action and make sure that only mandatory parameters are dedicated function arguments, and that the rest are handled via opts.
[ ] Ensure that opts handle snake case atom keys
[ ] ALL optional parameters need documented via the typespec in the client module. See other client modules for examples.
[ ] new lines at the end of all files.

I'll work on it this week :+1:

I think everything's done like you asked @benwilson512. The only this missing are some specs for parameters like this one:
Filters.member.N
I looked around but I didn't find any other similar specs that you had already defined for the other API's. Maybe it could be something with a range?

@benwilson512 everything done based on your notes :100:

This is a grade A crazy amount of work, thank you so much. The primary step from here is writing some tests. Those should encompass a basic sanity test that actually hits S3 with something innocuous, like describe_db_instances, as well as tests which use a pass through client and tests the formatting on any of the more complicated functions.

Hi @benwilson512. Yes I understand. I'll try to write the tests this week. I'm gonna check out the other tests but I'm thinking about doing something like a real use case. Create an instance, grab it, check if it appears in describe_db_instances, update it, delete it, etc...

Closing in favor of https://github.com/CargoSense/ex_aws/pull/167


Doesn't respect CC or CXX flags in Archlinux

Arch defaults to using hardening-wrapper, which would be fine if it didn't break packages incompatible with gcc6, as there are gcc6 specific bins inside the hardening wrapper directory.
For multi-compiler systems, it would be nice if CC and CXX were respected since Arch is forcing this.

It intercepts calls to 'gcc' and then redirects them to 'gcc'. It doesn't have any impact on multiple compiler systems.


we can use _NPROCESSOR_CONF instead of a hack for tegra

I suggest we add -j$(ncpu) to luarocks so that every project can build such way

tegra runs out of memory if we do _NPROCESSOR_CONF, that's why this change was introduced.

It works fine for me at least this morning. I worried if we original is working around NPROCESS_ONLN is 1 then we manually hack around it to set it to 3.
Building on 4 cores
-- Found Torch7 in /home/ubuntu/torch/install
-- MAGMA not found. Compiling without MAGMA support
-- Autodetected CUDA architecture(s): 3.2
-- got cuda version 6.5
..........................
[ 82%] [ 83%] [ 84%] [ 85%] Building C object lib/THC/CMakeFiles/THC.dir/THCAllocator.c.o
Building C object lib/THC/CMakeFiles/THC.dir/THCGeneral.c.o
Building CXX object lib/THC/CMakeFiles/THC.dir/THCCachingAllocator.cpp.o
Building C object lib/THC/CMakeFiles/THC.dir/THCStorage.c.o
[ 86%] Building C object lib/THC/CMakeFiles/THC.dir/THCStorageCopy.c.o
[ 88%] [ 89%] Building C object lib/THC/CMakeFiles/THC.dir/THCTensor.c.o
Building C object lib/THC/CMakeFiles/THC.dir/THCStream.c.o
[ 90%] Building C object lib/THC/CMakeFiles/THC.dir/THCTensorCopy.c.o
[ 91%] Building C object lib/THC/CMakeFiles/THC.dir/THCThreadLocal.c.o
Linking CXX shared library libTHC.so
[ 91%] Built target THC
[ 92%] Generating TensorMath.c
Scanning dependencies of target cutorch
[ 94%] [ 95%] Building C object CMakeFiles/cutorch.dir/Storage.c.o
[ 97%] [ 96%] Building C object CMakeFiles/cutorch.dir/init.c.o
Building C object CMakeFiles/cutorch.dir/Tensor.c.o
Building C object CMakeFiles/cutorch.dir/TensorMath.c.o
[ 98%] Building C object CMakeFiles/cutorch.dir/TensorOperator.c.o
[100%] Building C object CMakeFiles/cutorch.dir/torch/utils.c.o
Linking C shared module libcutorch.so
[100%] Built target cutorch

From here: https://www.gnu.org/software/libc/manual/html_node/Processor-Resources.html
NPROCESSOR_CONF should return the same value as NPROCESSOR_ONLN on tegra

it is not true for the platform that supports dynamic power-off cores. Tegra is one. When the system is idle, NPROCESS_ONLN=1 while NPROCESSOR_CONF=4. When you are running some workload, the system will turn on more cores and you may get NPROCESS_ONLN=4 while NPROCESSOR_CONF is still 4.
The same change causes issue with OpenBLAS (https://github.com/xianyi/OpenBLAS/pull/981) and torch/distro to detect the right number of cores in such platform. this is relatively common on ARM platforms.

thanks!


small improvements

Bringing a few things from https://github.com/mui/mui-toolpad/pull/1959

Remove ID from component editor. It's unnecessary information as it changes very time Toolpad loads
Make sure application name is always the same in the regression test fixtures by using a subfolder in the temporary test folder
Move up playwright config one level

test