Upgrading to macOS Sierra 10.12 (16A323) from Yosemite loses seems to unlink brew

bash-3.2$ ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/uninstall)"
Failed to locate Homebrew!
bash-3.2$ ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
It appears Homebrew is already installed. If your intent is to reinstall you
should do the following before running this installer again:
    ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/uninstall)"
The current contents of /usr/local are bin Caskroom Cellar etc Frameworks Homebrew include jamf lib libexec opt sbin share standalone var
bash-3.2$

Seems like homebrew is no longer in /usr/local after upgrade.
I found brew, ran brew doctor, in /usr/local/Homebrew/bin/brew doctor:
Warning: Your Homebrew is not installed to /usr/local
You can install Homebrew anywhere you want but some bottles (binary
packages) can only be used in /usr/local and some formulae (packages)
may not build correctly unless you install in /usr/local. Sorry!

Running brew doctor seems to fixed it in bash.
I use fish shell, and it got unlinked, so running echo 'set -g fish_user_paths "/usr/local/Homebrew/bin" $fish_user_paths' >> ~/.config/fish/config.fish fixed it.

running ... fixed it

That's not right, brew should be linked into /usr/local/bin.

Reinstalled brew, linked ok now.
$ pwd
/usr/local/bin
$ ls -l brew
lrwxr-xr-x  1 jason  admin  28 Sep 20 16:41 brew -> /usr/local/Homebrew/bin/brew
$ which brew
/usr/local/Homebrew/bin/brew

You can remove that set -g fish_user_paths "/usr/local/Homebrew/bin" $fish_user_paths line from your config.fish now.

Right. Removed and works. Thanks!

Just for interest. If mac os 10.13 upgrade.   Can brew don't do any thing and all my software installed by brew don't need change?


Crash on init() with no parameter passed

Apologies, I introduced this bug.
The recently modified version of init() crashes if no options table is passed.

I didn't catch this either in my code review!


Reduce number of sets in Conditional Prob. viz from 3 to 2

I'm not sure that having a third set adds any value to the visualization. It might be better to keep things simple and stick with 2 sets.


Absolute path in XML feature

When I save the XML file, it saves my "absolute path" to the file with  tag. Is it possible to add a feature (toggle on/off) and when we click, instead of absolute path, it could save relative path (working directory)?

**OS: Linux Ubuntu
**PyQt version: 5

it should be easy to change this. But it seems it is not urgent.

it should be easy to change this. But it seems it is not urgent.

yes, easy and not urgent.
I already wrote to give an idea :)


LITE-19504: Fix Cookiecutter hooks on bundles

Codecov Report

Merging #60 (f00f177) into master (73989c0) will increase coverage by 0.17%.
The diff coverage is 96.80%.

@@            Coverage Diff             @@
##           master      #60      +/-   ##
==========================================
+ Coverage   89.05%   89.22%   +0.17%
==========================================
  Files          49       49
  Lines        3344     3426      +82
  Branches      550      570      +20
==========================================
+ Hits         2978     3057      +79
- Misses        262      264       +2
- Partials      104      105       +1

Impacted Files
Coverage Δ

connect/cli/__init__.py
83.33% <75.00%> (-16.67%)
:arrow_down:

connect/cli/plugins/project/utils.py
99.12% <98.59%> (-0.88%)
:arrow_down:

connect/cli/core/utils.py
88.88% <100.00%> (+1.38%)
:arrow_up:

connect/cli/plugins/project/extension_helpers.py
99.00% <100.00%> (+0.08%)
:arrow_up:

connect/cli/plugins/project/report_helpers.py
99.16% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 73989c0...f00f177. Read the comment docs.


Automatic light-sleep feature and FreeRTOS integration

Refer to this link for how to enable automatic light sleep: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/system/power_management.html

Automatic Light-sleep is based on FreeRTOS Tickless Idle functionality. If automatic Light-sleep is requested while the option CONFIG_FREERTOS_USE_TICKLESS_IDLE is not enabled in menuconfig, esp_pm_configure() will return the error ESP_ERR_NOT_SUPPORTED.

Also here: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/system/sleep_modes.html

If Wi-Fi/Bluetooth connections need to be maintained, enable Wi-Fi/Bluetooth Modem-sleep mode and automatic Light-sleep feature (see Power Management APIs). This allows the system to wake up from sleep automatically when required by the Wi-Fi/Bluetooth driver, thereby maintaining the connection.

This will likely wait until 1.0.0


Support custom Codecs

There is a method to load custom codecs.
https://lucene.apache.org/core/7_5_0/core/org/apache/lucene/codecs/Codec.html#reloadCodecs-java.lang.ClassLoader-
Users scenario (an idea):

Click "Load custom codecs" button or link on the "open index" dialog.
Select JAR files including custom codecs on a file chooser dialog.
Press "OK" (then Luke loads the jars, and calls reloadCodecs() method.)

For contributors: Now Luke is a part of Apache Lucene. Please create an issue (if there is not exist) to Lucene Jira if you want to help with this.


Fix/ builder: restore assignment edges when submission is restored

Restores assignment edges or desk-reject/withdrawal reversion
Not sure how we can revert the /Proposed_Assignment edges. For /Assignment edges, I am checking the paper groups to make sure I am not restoring old assignment edges.

I like the solution, I'm not sure what to do with proposed assignments.


Implement the upload page

A page where the user can upload their document for identification and blurring of PII

I can work on this.

I can work on this.

Assigned!

i can work on this issue

i can work on this issue

Assigned

Completed by @avnigoyal25


VM Stuck in Pending State on macOS M1 when Running Kubevirt Using Experimental Arm64 Build

What happened:
Attempting to run kubevirt using the experimental arm64 build, but the VM is stuck in a Pending state.
What you expected to happen:
Pod should have status Running.
How to reproduce it (as minimally and precisely as possible):
kind create cluster

LATEST=$(curl -L https://storage.googleapis.com/kubevirt-prow/devel/nightly/release/kubevirt/kubevirt/latest-arm64)
kubectl apply -f https://storage.googleapis.com/kubevirt-prow/devel/nightly/release/kubevirt/kubevirt/${LATEST}/kubevirt-operator-arm64.yaml
kubectl apply -f https://storage.googleapis.com/kubevirt-prow/devel/nightly/release/kubevirt/kubevirt/${LATEST}/kubevirt-cr-arm64.yaml

 ❯ echo $LATEST
20230706

curl -L -o virtctl https://github.com/kubevirt/kubevirt/releases/download/v1.0.0-rc.1/virtctl-v1.0.0-rc.1-darwin-arm64
chmod +x virtctl
sudo install virtctl /usr/local/bin

❯ kubectl apply -f examples/vm-cirros.yaml
virtualmachine.kubevirt.io/vm-cirros created

❯ kubectl get vm
NAME        AGE   STATUS    READY
vm-cirros   31m   Stopped   False

❯ virtctl start vm-cirros
VM vm-cirros was scheduled to start

❯ kubectl get pods
NAME                            READY   STATUS    RESTARTS   AGE
virt-launcher-vm-cirros-b84rf   0/2     Pending   0          58s

vm/vm-cirros
apiVersion: kubevirt.io/v1
kind: VirtualMachine
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"kubevirt.io/v1","kind":"VirtualMachine","metadata":{"annotations":{},"labels":{"kubevirt.io/vm":"vm-cirros"},"name":"vm-cirros","namespace":"default"},"spec":{"running":false,"template":{"metadata":{"labels":{"kubevirt.io/vm":"vm-cirros"}},"spec":{"domain":{"devices":{"disks":[{"disk":{"bus":"virtio"},"name":"containerdisk"},{"disk":{"bus":"virtio"},"name":"cloudinitdisk"}]},"resources":{"requests":{"memory":"128Mi"}}},"terminationGracePeriodSeconds":0,"volumes":[{"containerDisk":{"image":"registry:5000/kubevirt/cirros-container-disk-demo:devel"},"name":"containerdisk"},{"cloudInitNoCloud":{"userData":"#!/bin/sh\n\necho 'printed from cloud-init userdata'\n"},"name":"cloudinitdisk"}]}}}}
    kubevirt.io/latest-observed-api-version: v1
    kubevirt.io/storage-observed-api-version: v1
  creationTimestamp: "2023-07-06T16:44:14Z"
  finalizers:
  - kubevirt.io/virtualMachineControllerFinalize
  generation: 2
  labels:
    kubevirt.io/vm: vm-cirros
  name: vm-cirros
  namespace: default
  resourceVersion: "11554"
  uid: e6e6339d-815e-4d47-8366-b68b83d79ea7
spec:
  running: true
  template:
    metadata:
      creationTimestamp: null
      labels:
        kubevirt.io/vm: vm-cirros
    spec:
      architecture: arm64
      domain:
        devices:
          disks:
          - disk:
              bus: virtio
            name: containerdisk
          - disk:
              bus: virtio
            name: cloudinitdisk
        machine:
          type: virt
        resources:
          requests:
            memory: 128Mi
      terminationGracePeriodSeconds: 0
      volumes:
      - containerDisk:
          image: registry:5000/kubevirt/cirros-container-disk-demo:devel
        name: containerdisk
      - cloudInitNoCloud:
          userData: |
            #!/bin/sh

            echo 'printed from cloud-init userdata'
        name: cloudinitdisk
status:
  conditions:
  - lastProbeTime: "2023-07-06T17:18:32Z"
    lastTransitionTime: "2023-07-06T17:18:32Z"
    message: Guest VM is not reported as running
    reason: GuestNotRunning
    status: "False"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: "2023-07-06T17:18:32Z"
    message: '0/1 nodes are available: 1 Insufficient devices.kubevirt.io/kvm. preemption:
      0/1 nodes are available: 1 No preemption victims found for incoming pod..'
    reason: Unschedulable
    status: "False"
    type: PodScheduled
  created: true
  desiredGeneration: 2
  observedGeneration: 2
  printableStatus: ErrorUnschedulable
  volumeSnapshotStatuses:
  - enabled: false
    name: containerdisk
    reason: Snapshot is not supported for this volumeSource type [containerdisk[]
  - enabled: false
    name: cloudinitdisk
    reason: Snapshot is not supported for this volumeSource type [cloudinitdisk[]

vmi/vm-cirros
apiVersion: kubevirt.io/v1
kind: VirtualMachineInstance
metadata:
  annotations:
    kubevirt.io/latest-observed-api-version: v1
    kubevirt.io/storage-observed-api-version: v1
    kubevirt.io/vm-generation: "2"
  creationTimestamp: "2023-07-06T17:18:32Z"
  finalizers:
  - kubevirt.io/virtualMachineControllerFinalize
  - foregroundDeleteVirtualMachine
  generation: 4
  labels:
    kubevirt.io/vm: vm-cirros
  name: vm-cirros
  namespace: default
  ownerReferences:
  - apiVersion: kubevirt.io/v1
    blockOwnerDeletion: true
    controller: true
    kind: VirtualMachine
    name: vm-cirros
    uid: e6e6339d-815e-4d47-8366-b68b83d79ea7
  resourceVersion: "11553"
  uid: 896aa024-54ce-4653-9c98-fdfb7ec2cd5d
spec:
  architecture: arm64
  domain:
    cpu:
      cores: 1
      model: host-passthrough
      sockets: 1
      threads: 1
    devices:
      disks:
      - disk:
          bus: virtio
        name: containerdisk
      - disk:
          bus: virtio
        name: cloudinitdisk
      interfaces:
      - bridge: {}
        name: default
    features:
      acpi:
        enabled: true
    firmware:
      bootloader:
        efi:
          secureBoot: false
      uuid: 0d2a2043-41c0-59c3-9b17-025022203668
    machine:
      type: virt
    resources:
      requests:
        memory: 128Mi
  networks:
  - name: default
    pod: {}
  terminationGracePeriodSeconds: 0
  volumes:
  - containerDisk:
      image: registry:5000/kubevirt/cirros-container-disk-demo:devel
      imagePullPolicy: IfNotPresent
    name: containerdisk
  - cloudInitNoCloud:
      userData: |
        #!/bin/sh

        echo 'printed from cloud-init userdata'
    name: cloudinitdisk
status:
  activePods:
    b39e0ecd-6fb5-4504-8ac4-dac9273c4566: ""
  conditions:
  - lastProbeTime: "2023-07-06T17:18:32Z"
    lastTransitionTime: "2023-07-06T17:18:32Z"
    message: Guest VM is not reported as running
    reason: GuestNotRunning
    status: "False"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: "2023-07-06T17:18:32Z"
    message: '0/1 nodes are available: 1 Insufficient devices.kubevirt.io/kvm. preemption:
      0/1 nodes are available: 1 No preemption victims found for incoming pod..'
    reason: Unschedulable
    status: "False"
    type: PodScheduled
  currentCPUTopology:
    cores: 1
    sockets: 1
    threads: 1
  guestOSInfo: {}
  launcherContainerImageVersion: quay.io/kubevirt/virt-launcher:20230706_534bda181-arm64
  phase: Scheduling
  phaseTransitionTimestamps:
  - phase: Pending
    phaseTransitionTimestamp: "2023-07-06T17:18:32Z"
  - phase: Scheduling
    phaseTransitionTimestamp: "2023-07-06T17:18:32Z"
  qosClass: Burstable
  runtimeUser: 107
  virtualMachineRevisionName: revision-start-vm-e6e6339d-815e-4d47-8366-b68b83d79ea7-2

pod/virt-launcher-vm-cirros-b84rf
apiVersion: v1
kind: Pod
metadata:
  annotations:
    kubectl.kubernetes.io/default-container: compute
    kubevirt.io/domain: vm-cirros
    kubevirt.io/migrationTransportUnix: "true"
    kubevirt.io/vm-generation: "2"
    post.hook.backup.velero.io/command: '["/usr/bin/virt-freezer", "--unfreeze", "--name",
      "vm-cirros", "--namespace", "default"]'
    post.hook.backup.velero.io/container: compute
    pre.hook.backup.velero.io/command: '["/usr/bin/virt-freezer", "--freeze", "--name",
      "vm-cirros", "--namespace", "default"]'
    pre.hook.backup.velero.io/container: compute
  creationTimestamp: "2023-07-06T17:18:32Z"
  generateName: virt-launcher-vm-cirros-
  labels:
    kubevirt.io: virt-launcher
    kubevirt.io/created-by: 896aa024-54ce-4653-9c98-fdfb7ec2cd5d
    kubevirt.io/vm: vm-cirros
    vm.kubevirt.io/name: vm-cirros
  name: virt-launcher-vm-cirros-b84rf
  namespace: default
  ownerReferences:
  - apiVersion: kubevirt.io/v1
    blockOwnerDeletion: true
    controller: true
    kind: VirtualMachineInstance
    name: vm-cirros
    uid: 896aa024-54ce-4653-9c98-fdfb7ec2cd5d
  resourceVersion: "11550"
  uid: b39e0ecd-6fb5-4504-8ac4-dac9273c4566
spec:
  automountServiceAccountToken: false
  containers:
  - command:
    - /usr/bin/virt-launcher-monitor
    - --qemu-timeout
    - 354s
    - --name
    - vm-cirros
    - --uid
    - 896aa024-54ce-4653-9c98-fdfb7ec2cd5d
    - --namespace
    - default
    - --kubevirt-share-dir
    - /var/run/kubevirt
    - --ephemeral-disk-dir
    - /var/run/kubevirt-ephemeral-disks
    - --container-disk-dir
    - /var/run/kubevirt/container-disks
    - --grace-period-seconds
    - "15"
    - --hook-sidecars
    - "0"
    - --ovmf-path
    - /usr/share/AAVMF
    - --run-as-nonroot
    env:
    - name: XDG_CACHE_HOME
      value: /var/run/kubevirt-private
    - name: XDG_CONFIG_HOME
      value: /var/run/kubevirt-private
    - name: XDG_RUNTIME_DIR
      value: /var/run
    - name: POD_NAME
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: metadata.name
    image: quay.io/kubevirt/virt-launcher:20230706_534bda181-arm64
    imagePullPolicy: IfNotPresent
    name: compute
    resources:
      limits:
        devices.kubevirt.io/kvm: "1"
        devices.kubevirt.io/tun: "1"
        devices.kubevirt.io/vhost-net: "1"
      requests:
        cpu: 100m
        devices.kubevirt.io/kvm: "1"
        devices.kubevirt.io/tun: "1"
        devices.kubevirt.io/vhost-net: "1"
        ephemeral-storage: 50M
        memory: 510208Ki
    securityContext:
      allowPrivilegeEscalation: false
      capabilities:
        add:
        - NET_BIND_SERVICE
        drop:
        - ALL
      privileged: false
      runAsGroup: 107
      runAsNonRoot: true
      runAsUser: 107
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /var/run/kubevirt-private
      name: private
    - mountPath: /var/run/kubevirt
      name: public
    - mountPath: /var/run/kubevirt-ephemeral-disks
      name: ephemeral-disks
    - mountPath: /var/run/kubevirt/container-disks
      mountPropagation: HostToContainer
      name: container-disks
    - mountPath: /var/run/libvirt
      name: libvirt-runtime
    - mountPath: /var/run/kubevirt/sockets
      name: sockets
    - mountPath: /var/run/kubevirt/hotplug-disks
      mountPropagation: HostToContainer
      name: hotplug-disks
  - args:
    - --copy-path
    - /var/run/kubevirt-ephemeral-disks/container-disk-data/896aa024-54ce-4653-9c98-fdfb7ec2cd5d/disk_0
    command:
    - /usr/bin/container-disk
    image: registry:5000/kubevirt/cirros-container-disk-demo:devel
    imagePullPolicy: IfNotPresent
    name: volumecontainerdisk
    resources:
      limits:
        cpu: 10m
        memory: 40M
      requests:
        cpu: 1m
        ephemeral-storage: 50M
        memory: 1M
    securityContext:
      allowPrivilegeEscalation: false
      capabilities:
        drop:
        - ALL
      runAsNonRoot: true
      runAsUser: 107
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /var/run/kubevirt-ephemeral-disks/container-disk-data/896aa024-54ce-4653-9c98-fdfb7ec2cd5d
      name: container-disks
    - mountPath: /usr/bin
      name: virt-bin-share-dir
  dnsPolicy: ClusterFirst
  enableServiceLinks: false
  hostname: vm-cirros
  initContainers:
  - command:
    - /usr/bin/cp
    - /usr/bin/container-disk
    - /init/usr/bin/container-disk
    env:
    - name: XDG_CACHE_HOME
      value: /var/run/kubevirt-private
    - name: XDG_CONFIG_HOME
      value: /var/run/kubevirt-private
    - name: XDG_RUNTIME_DIR
      value: /var/run
    image: quay.io/kubevirt/virt-launcher:20230706_534bda181-arm64
    imagePullPolicy: IfNotPresent
    name: container-disk-binary
    resources:
      limits:
        cpu: 100m
        memory: 40M
      requests:
        cpu: 10m
        memory: 1M
    securityContext:
      allowPrivilegeEscalation: false
      capabilities:
        drop:
        - ALL
      privileged: false
      runAsGroup: 107
      runAsNonRoot: true
      runAsUser: 107
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /init/usr/bin
      name: virt-bin-share-dir
  - args:
    - --no-op
    command:
    - /usr/bin/container-disk
    image: registry:5000/kubevirt/cirros-container-disk-demo:devel
    imagePullPolicy: IfNotPresent
    name: volumecontainerdisk-init
    resources:
      limits:
        cpu: 10m
        memory: 40M
      requests:
        cpu: 1m
        ephemeral-storage: 50M
        memory: 1M
    securityContext:
      allowPrivilegeEscalation: false
      capabilities:
        drop:
        - ALL
      runAsNonRoot: true
      runAsUser: 107
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /var/run/kubevirt-ephemeral-disks/container-disk-data/896aa024-54ce-4653-9c98-fdfb7ec2cd5d
      name: container-disks
    - mountPath: /usr/bin
      name: virt-bin-share-dir
  nodeSelector:
    kubernetes.io/arch: arm64
    kubevirt.io/schedulable: "true"
  preemptionPolicy: PreemptLowerPriority
  priority: 0
  readinessGates:
  - conditionType: kubevirt.io/virtual-machine-unpaused
  restartPolicy: Never
  schedulerName: default-scheduler
  securityContext:
    fsGroup: 107
    runAsGroup: 107
    runAsNonRoot: true
    runAsUser: 107
  serviceAccount: default
  serviceAccountName: default
  terminationGracePeriodSeconds: 30
  tolerations:
  - effect: NoExecute
    key: node.kubernetes.io/not-ready
    operator: Exists
    tolerationSeconds: 300
  - effect: NoExecute
    key: node.kubernetes.io/unreachable
    operator: Exists
    tolerationSeconds: 300
  volumes:
  - emptyDir: {}
    name: private
  - emptyDir: {}
    name: public
  - emptyDir: {}
    name: sockets
  - emptyDir: {}
    name: virt-bin-share-dir
  - emptyDir: {}
    name: libvirt-runtime
  - emptyDir: {}
    name: ephemeral-disks
  - emptyDir: {}
    name: container-disks
  - emptyDir: {}
    name: hotplug-disks
status:
  conditions:
  - lastProbeTime: null
    lastTransitionTime: "2023-07-06T17:18:32Z"
    message: '0/1 nodes are available: 1 Insufficient devices.kubevirt.io/kvm. preemption:
      0/1 nodes are available: 1 No preemption victims found for incoming pod..'
    reason: Unschedulable
    status: "False"
    type: PodScheduled
  - lastProbeTime: "2023-07-06T17:18:32Z"
    lastTransitionTime: "2023-07-06T17:18:32Z"
    message: the virtual machine is not paused
    reason: NotPaused
    status: "True"
    type: kubevirt.io/virtual-machine-unpaused
  phase: Pending
  qosClass: Burstable

Additional context:

https://kubevirt.io/user-guide/operations/installation/#experimental-arm64-developer-builds
https://github.com/kubevirt/kubevirt/pull/3415#issuecomment-628569863
https://github.com/kubevirt/kubevirt/issues/7305
https://github.com/kubevirt/kubevirt/pull/9832

Environment:

KubeVirt version (use virtctl version):Server Version: version.Info{GitVersion:"v1.0.0-beta.0.525+534bda181a078a", GitCommit:"534bda181a078a90215763f849eb4eabcb8d8da2", GitTreeState:"clean", BuildDate:"2023-07-06T01:08:35Z", GoVersion:"go1.19.9", Compiler:"gc", Platform:"linux/arm64"}

Kubernetes version (use kubectl version):Client Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.2", GitCommit:"7f6f68fdabc4df88cfea2dcf9a19b2b830f1e647", GitTreeState:"clean", BuildDate:"2023-05-17T14:20:07Z", GoVersion:"go1.20.4", Compiler:"gc", Platform:"darwin/arm64"}
Kustomize Version: v5.0.1
Server Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.3", GitCommit:"25b4e43193bcda6c7328a6d147b1fb73a33f1598", GitTreeState:"clean", BuildDate:"2023-06-15T00:38:14Z", GoVersion:"go1.20.5", Compiler:"gc", Platform:"linux/arm64"}

VM or VMI specifications: https://github.com/kubevirt/kubevirt/blob/main/examples/vm-cirros.yaml
Cloud provider or hardware configuration: N/A
OS (e.g. from /etc/os-release): macOS Ventura 13.2.1 (22D68)
Kernel (e.g. uname -a): N/A
Install tools: N/A
Others: N/A

'0/1 nodes are available: 1 Insufficient devices.kubevirt.io/kvm

You do not have kvm virtualization support. In theory, you can try software emulation https://kubevirt.io/user-guide/operations/installation/#installing-kubevirt-on-kubernetes, though I am not sure how it will work on a mac.

@vasiliy-ul thanks for the suggestion. I enabled emulation with,
kubectl -n kubevirt patch kubevirt kubevirt --type=merge --patch '{"spec":{"configuration":{"developerConfiguration":{"useEmulation":true}}}}'

which got past Pending, but the VM I was using needed CDI which I didn't have setup, so it couldn't pull the image from localhost.
So I switched to installing https://kubevirt.io/labs/manifests/vm.yaml per the quickstart for Kind. Now, the VM is in a CrashLoopBackoff

vm/testvm
apiVersion: kubevirt.io/v1
kind: VirtualMachine
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"kubevirt.io/v1","kind":"VirtualMachine","metadata":{"annotations":{},"name":"testvm","namespace":"default"},"spec":{"running":false,"template":{"metadata":{"labels":{"kubevirt.io/domain":"testvm","kubevirt.io/size":"small"}},"spec":{"domain":{"devices":{"disks":[{"disk":{"bus":"virtio"},"name":"containerdisk"},{"disk":{"bus":"virtio"},"name":"cloudinitdisk"}],"interfaces":[{"masquerade":{},"name":"default"}]},"resources":{"requests":{"memory":"64M"}}},"networks":[{"name":"default","pod":{}}],"volumes":[{"containerDisk":{"image":"quay.io/kubevirt/cirros-container-disk-demo"},"name":"containerdisk"},{"cloudInitNoCloud":{"userDataBase64":"SGkuXG4="},"name":"cloudinitdisk"}]}}}}
    kubevirt.io/latest-observed-api-version: v1
    kubevirt.io/storage-observed-api-version: v1
  creationTimestamp: "2023-07-07T15:36:33Z"
  finalizers:
  - kubevirt.io/virtualMachineControllerFinalize
  generation: 2
  name: testvm
  namespace: default
  resourceVersion: "3650"
  uid: 0a835fc3-5381-4d97-9d1e-88e6639eebe2
spec:
  running: true
  template:
    metadata:
      creationTimestamp: null
      labels:
        kubevirt.io/domain: testvm
        kubevirt.io/size: small
    spec:
      architecture: arm64
      domain:
        devices:
          disks:
          - disk:
              bus: virtio
            name: containerdisk
          - disk:
              bus: virtio
            name: cloudinitdisk
          interfaces:
          - masquerade: {}
            name: default
        machine:
          type: virt
        resources:
          requests:
            memory: 64M
      networks:
      - name: default
        pod: {}
      volumes:
      - containerDisk:
          image: quay.io/kubevirt/cirros-container-disk-demo
        name: containerdisk
      - cloudInitNoCloud:
          userDataBase64: SGkuXG4=
        name: cloudinitdisk
status:
  conditions:
  - lastProbeTime: "2023-07-07T15:45:29Z"
    lastTransitionTime: "2023-07-07T15:45:29Z"
    message: VMI does not exist
    reason: VMINotExists
    status: "False"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: null
    status: "True"
    type: LiveMigratable
  desiredGeneration: 2
  observedGeneration: 2
  printableStatus: CrashLoopBackOff
  startFailure:
    consecutiveFailCount: 5
    lastFailedVMIUID: a10d0ea5-7a65-4828-99ce-ec851e017af9
    retryAfterTimestamp: "2023-07-07T15:49:33Z"
  volumeSnapshotStatuses:
  - enabled: false
    name: containerdisk
    reason: Snapshot is not supported for this volumeSource type [containerdisk[]
  - enabled: false
    name: cloudinitdisk
    reason: Snapshot is not supported for this volumeSource type [cloudinitdisk[]

events/SyncFailed
apiVersion: v1
count: 1
eventTime: null
firstTimestamp: "2023-07-07T15:45:17Z"
involvedObject:
  apiVersion: kubevirt.io/v1
  kind: VirtualMachineInstance
  name: testvm
  namespace: default
  resourceVersion: "3591"
  uid: a10d0ea5-7a65-4828-99ce-ec851e017af9
kind: Event
lastTimestamp: "2023-07-07T15:45:17Z"
message: |
  failed to configure vmi network: setup failed, err: failed setup pod network phase1: Critical network error: error creating tap device named tap0; failed to execute command in launcher namespace 5110: failed running command /usr/bin/virt-chroot create-tap --tap-name tap0 --uid 107 --gid 107 --queue-number 0 --mtu 65535, err: exit status 1, output: Error: failed to set MTU on tap device named tap0. Reason: invalid argument
  Usage:
    virt-chroot create-tap [flags[]

  Flags:
        --gid uint              the group of the owner of the tap device
    -h, --help                  help for create-tap
        --mtu uint32            the link MTU of the tap device (default 1500)
        --queue-number uint32   the number of queues to use on multi-queued devices
        --tap-name string       the name of the tap device (default "tap0")
        --uid uint              the owner of the tap device

  Global Flags:
        --cpu uint       cpu time in seconds for the process
        --memory uint    memory in bytes for the process
        --mount string   mount namespace to use
        --user string    switch to this targetUser to e.g. drop privileges

  failed to set MTU on tap device named tap0. Reason: invalid argument
metadata:
  creationTimestamp: "2023-07-07T15:45:17Z"
  name: testvm.176fa05f9a5d7810
  namespace: default
  resourceVersion: "3593"
  uid: 5801bd70-5fb4-4685-b122-655e462b0b9f
reason: SyncFailed
reportingComponent: ""
reportingInstance: ""
source:
  component: virt-handler
  host: kind-control-plane
type: Warning

virt-launcher-testvm-5t52j logs
stream logs failed container "volumecontainerdisk-init" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (volumecontainerdisk-init)
stream logs failed container "compute" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (compute)
stream logs failed container "volumecontainerdisk" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (volumecontainerdisk)
Stream closed EOF for default/virt-launcher-testvm-5t52j (container-disk-binary)
stream logs failed container "volumecontainerdisk" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (volumecontainerdisk)
stream logs failed container "compute" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (compute)
Stream closed EOF for default/virt-launcher-testvm-5t52j (volumecontainerdisk-init)
stream logs failed container "compute" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (compute)
stream logs failed container "volumecontainerdisk" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (volumecontainerdisk)
stream logs failed container "volumecontainerdisk" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (volumecontainerdisk)
stream logs failed container "compute" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (compute)
stream logs failed container "volumecontainerdisk" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (volumecontainerdisk)
stream logs failed container "compute" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (compute)
stream logs failed container "volumecontainerdisk" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (volumecontainerdisk)
stream logs failed container "compute" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (compute)
stream logs failed container "compute" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (compute)
stream logs failed container "volumecontainerdisk" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (volumecontainerdisk)
stream logs failed container "volumecontainerdisk" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (volumecontainerdisk)
stream logs failed container "compute" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (compute)
stream logs failed container "volumecontainerdisk" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (volumecontainerdisk)
stream logs failed container "compute" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (compute)
stream logs failed container "volumecontainerdisk" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (volumecontainerdisk)
stream logs failed container "compute" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (compute)
stream logs failed container "compute" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (compute)
stream logs failed container "volumecontainerdisk" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (volumecontainerdisk)
stream logs failed container "compute" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (compute)
stream logs failed container "volumecontainerdisk" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (volumecontainerdisk)
stream logs failed container "compute" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (compute)
stream logs failed container "volumecontainerdisk" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (volumecontainerdisk)
stream logs failed container "compute" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (compute)
stream logs failed container "volumecontainerdisk" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (volumecontainerdisk)
stream logs failed container "volumecontainerdisk" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (volumecontainerdisk)
stream logs failed container "compute" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (compute)
stream logs failed container "compute" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (compute)
stream logs failed container "volumecontainerdisk" in pod "virt-launcher-testvm-5t52j" is waiting to start: PodInitializing for default/virt-launcher-testvm-5t52j (volumecontainerdisk)
compute {"component":"virt-launcher","level":"info","msg":"Collected all requested hook sidecar sockets","pos":"manager.go:86","timestamp":"2023-07-07T15:39:05.163462Z"}
compute {"component":"virt-launcher","level":"info","msg":"Sorted all collected sidecar sockets per hook point based on their priority and name: map[]","pos":"manager.go:89","timestamp":"2023-07-07T15:39:05.163555Z"}
compute {"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon: qemu+unix:///session?socket=/var/run/libvirt/virtqemud-sock","pos":"libvirt.go:545","timestamp":"2023-07-07T15:39:05.164003Z"}
compute {"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon failed: virError(Code=38, Domain=7, Message='Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory')","pos":"libvirt.go:553","timestamp":"2023-07-07T15:39:05.164602Z"}
compute {"component":"virt-launcher","level":"info","msg":"libvirt version: 9.0.0, package: 3.el9<EMAIL_ADDRESS>2023-02-01-12:59:20, )","subcomponent":"libvirt","thread":"42","timestamp":"2023-07-07T15:39:05.174000Z"}
compute {"component":"virt-launcher","level":"info","msg":"hostname: testvm","subcomponent":"libvirt","thread":"42","timestamp":"2023-07-07T15:39:05.174000Z"}
compute {"component":"virt-launcher","level":"error","msg":"internal error: Unable to get session bus connection: Cannot spawn a message bus without a machine-id: Unable to load /var/lib/dbus/machine-id or /etc/machine-id: Failed to open file “/var/lib/dbus/machine-id”: No such file or directory","pos":"virGDBusGetSessionBus:126","subcomponent":"libvirt","thread":"42","timestamp":"2023-07-07T15:39:05.174000Z"}
compute {"component":"virt-launcher","level":"error","msg":"internal error: Unable to get system bus connection: Could not connect: No such file or directory","pos":"virGDBusGetSystemBus:99","subcomponent":"libvirt","thread":"42","timestamp":"2023-07-07T15:39:05.174000Z"}
compute {"component":"virt-launcher","level":"info","msg":"Connected to libvirt daemon","pos":"libvirt.go:561","timestamp":"2023-07-07T15:39:05.667859Z"}
compute {"component":"virt-launcher","level":"info","msg":"Registered libvirt event notify callback","pos":"client.go:543","timestamp":"2023-07-07T15:39:05.674277Z"}
compute {"component":"virt-launcher","level":"info","msg":"Marked as ready","pos":"virt-launcher.go:75","timestamp":"2023-07-07T15:39:05.675526Z"}
volumecontainerdisk Fri Jul  7 15:39:20 2023
volumecontainerdisk error: socket /var/run/kubevirt-ephemeral-disks/container-disk-data/0df14d8c-e67b-4304-a2fd-1e1ba6e96670/disk_0.sock does not exist anymore
Stream closed EOF for default/virt-launcher-testvm-5t52j (volumecontainerdisk)
compute {"component":"virt-launcher","level":"info","msg":"Received signal terminated","pos":"virt-launcher.go:457","timestamp":"2023-07-07T15:39:22.123728Z"}
compute {"component":"virt-launcher","level":"info","msg":"stopping cmd server","pos":"server.go:611","timestamp":"2023-07-07T15:39:22.124263Z"}
compute {"component":"virt-launcher","level":"error","msg":"timeout on stopping the cmd server, continuing anyway.","pos":"server.go:622","timestamp":"2023-07-07T15:39:23.125036Z"}
compute {"component":"virt-launcher","level":"info","msg":"Exiting...","pos":"virt-launcher.go:493","timestamp":"2023-07-07T15:39:23.125407Z"}
compute {"component":"virt-launcher-monitor","level":"info","msg":"Reaped pid 16 with status 0","pos":"virt-launcher-monitor.go:125","timestamp":"2023-07-07T15:39:23.138270Z"}
Stream closed EOF for default/virt-launcher-testvm-5t52j (compute)

I'm currently running Kind on a MacBook M1. My objective is to create a Windows VM for local development purposes.
Switching to bridge is still resulting in a CrashLoopBackoff

vm/testvm
apiVersion: kubevirt.io/v1
kind: VirtualMachine
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"kubevirt.io/v1","kind":"VirtualMachine","metadata":{"annotations":{},"name":"testvm","namespace":"default"},"spec":{"running":false,"template":{"metadata":{"labels":{"kubevirt.io/domain":"testvm","kubevirt.io/size":"small"}},"spec":{"domain":{"devices":{"disks":[{"disk":{"bus":"virtio"},"name":"containerdisk"},{"disk":{"bus":"virtio"},"name":"cloudinitdisk"}],"interfaces":[{"bridge":{},"name":"default"}]},"resources":{"requests":{"memory":"64M"}}},"networks":[{"name":"default","pod":{}}],"volumes":[{"containerDisk":{"image":"quay.io/kubevirt/cirros-container-disk-demo"},"name":"containerdisk"},{"cloudInitNoCloud":{"userDataBase64":"SGkuXG4="},"name":"cloudinitdisk"}]}}}}
    kubevirt.io/latest-observed-api-version: v1
    kubevirt.io/storage-observed-api-version: v1
  creationTimestamp: "2023-07-07T16:38:04Z"
  finalizers:
  - kubevirt.io/virtualMachineControllerFinalize
  generation: 2
  name: testvm
  namespace: default
  resourceVersion: "8753"
  uid: e88a8a6f-67d8-4631-806d-44617d7b9b63
spec:
  running: true
  template:
    metadata:
      creationTimestamp: null
      labels:
        kubevirt.io/domain: testvm
        kubevirt.io/size: small
    spec:
      architecture: arm64
      domain:
        devices:
          disks:
          - disk:
              bus: virtio
            name: containerdisk
          - disk:
              bus: virtio
            name: cloudinitdisk
          interfaces:
          - bridge: {}
            name: default
        machine:
          type: virt
        resources:
          requests:
            memory: 64M
      networks:
      - name: default
        pod: {}
      volumes:
      - containerDisk:
          image: quay.io/kubevirt/cirros-container-disk-demo
        name: containerdisk
      - cloudInitNoCloud:
          userDataBase64: SGkuXG4=
        name: cloudinitdisk
status:
  conditions:
  - lastProbeTime: "2023-07-07T16:40:52Z"
    lastTransitionTime: "2023-07-07T16:40:52Z"
    message: VMI does not exist
    reason: VMINotExists
    status: "False"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: null
    message: cannot migrate VMI which does not use masquerade to connect to the pod
      network or bridge with kubevirt.io/allow-pod-bridge-network-live-migration VM
      annotation
    reason: InterfaceNotLiveMigratable
    status: "False"
    type: LiveMigratable
  desiredGeneration: 2
  observedGeneration: 2
  printableStatus: CrashLoopBackOff
  startFailure:
    consecutiveFailCount: 3
    lastFailedVMIUID: 7c0ee460-8399-4ac0-810f-43f809ab6c99
    retryAfterTimestamp: "2023-07-07T16:42:11Z"
  volumeSnapshotStatuses:
  - enabled: false
    name: containerdisk
    reason: Snapshot is not supported for this volumeSource type [containerdisk[]
  - enabled: false
    name: cloudinitdisk
    reason: Snapshot is not supported for this volumeSource type [cloudinitdisk[]

Please provide the logs of virt-launcher pod.

Stream closed EOF for default/virt-launcher-testvm-49jgt (volumecontainerdisk-init)
volumecontainerdisk Fri Jul  7 16:50:36 2023
volumecontainerdisk error: socket /var/run/kubevirt-ephemeral-disks/container-disk-data/86849278-f067-46b9-a979-0e0ca787154e/disk_0.sock does not exist anymore
compute {"component":"virt-launcher","level":"info","msg":"Collected all requested hook sidecar sockets","pos":"manager.go:86","timestamp":"2023-07-07T16:50:23.104040Z"}
compute {"component":"virt-launcher","level":"info","msg":"Sorted all collected sidecar sockets per hook point based on their priority and name: map[]","pos":"manager.go:89","timestamp":"2023-07-07T16:50:23.104138Z"}
compute {"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon: qemu+unix:///session?socket=/var/run/libvirt/virtqemud-sock","pos":"libvirt.go:545","timestamp":"2023-07-07T16:50:23.104617Z"}
compute {"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon failed: virError(Code=38, Domain=7, Message='Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory')","pos":"libvirt.go:553","timestamp":"2023-07-07T16:50:23.105126Z"}
compute {"component":"virt-launcher","level":"info","msg":"libvirt version: 9.0.0, package: 3.el9<EMAIL_ADDRESS>2023-02-01-12:59:20, )","subcomponent":"libvirt","thread":"42","timestamp":"2023-07-07T16:50:23.115000Z"}
compute {"component":"virt-launcher","level":"info","msg":"hostname: testvm","subcomponent":"libvirt","thread":"42","timestamp":"2023-07-07T16:50:23.115000Z"}
compute {"component":"virt-launcher","level":"error","msg":"internal error: Unable to get session bus connection: Cannot spawn a message bus without a machine-id: Unable to load /var/lib/dbus/machine-id or /etc/machine-id: Failed to open file “/var/lib/dbus/machine-id”: No such file or directory","pos":"virGDBusGetSessionBus:126","subcomponent":"libvirt","thread":"42","timestamp":"2023-07-07T16:50:23.115000Z"}
compute {"component":"virt-launcher","level":"error","msg":"internal error: Unable to get system bus connection: Could not connect: No such file or directory","pos":"virGDBusGetSystemBus:99","subcomponent":"libvirt","thread":"42","timestamp":"2023-07-07T16:50:23.115000Z"}
compute {"component":"virt-launcher","level":"info","msg":"Connected to libvirt daemon","pos":"libvirt.go:561","timestamp":"2023-07-07T16:50:23.607585Z"}
compute {"component":"virt-launcher","level":"info","msg":"Registered libvirt event notify callback","pos":"client.go:543","timestamp":"2023-07-07T16:50:23.611678Z"}
compute {"component":"virt-launcher","level":"info","msg":"Marked as ready","pos":"virt-launcher.go:75","timestamp":"2023-07-07T16:50:23.612277Z"}
compute {"component":"virt-launcher","level":"info","msg":"Received signal terminated","pos":"virt-launcher.go:457","timestamp":"2023-07-07T16:50:38.060273Z"}
compute {"component":"virt-launcher","level":"info","msg":"stopping cmd server","pos":"server.go:611","timestamp":"2023-07-07T16:50:38.060839Z"}
compute {"component":"virt-launcher","level":"error","msg":"timeout on stopping the cmd server, continuing anyway.","pos":"server.go:622","timestamp":"2023-07-07T16:50:39.061457Z"}
compute {"component":"virt-launcher","level":"info","msg":"Exiting...","pos":"virt-launcher.go:493","timestamp":"2023-07-07T16:50:39.061837Z"}
compute {"component":"virt-launcher-monitor","level":"info","msg":"Reaped pid 15 with status 0","pos":"virt-launcher-monitor.go:125","timestamp":"2023-07-07T16:50:39.075218Z"}
Stream closed EOF for default/virt-launcher-testvm-49jgt (container-disk-binary)
Stream closed EOF for default/virt-launcher-testvm-49jgt (volumecontainerdisk)

virt-launcher + '[' '!' -e /dev/kvm ']'
virt-launcher + '[' -n '' ']'
virt-launcher + '[' -e /dev/kvm ']'
virt-launcher + '[' -e /dev/sev ']'
virt-launcher + virtqemud -d
virt-launcher + virsh domcapabilities --machine virt --arch aarch64 --virttype qemu
virt-launcher + cp -r /usr/share/libvirt/cpu_map /var/lib/kubevirt-node-labeller
virt-handler {"component":"virt-handler","level":"info","msg":"VMI does not exist | Domain does not exist","pos":"vm.go:1782","timestamp":"2023-07-07T16:50:47.430554Z"}
virt-handler {"component":"virt-handler","kind":"VirtualMachineInstance","level":"info","msg":"Performing final local cleanup for vmi with uid ","name":"testvm","namespace":"default","pos":"vm.go:2041","timestamp":"2023-07-07T16:50:47.430612Z","uid":""}
virt-handler {"component":"virt-handler","kind":"Domain","level":"info","msg":"Removing domain from cache during final cleanup","name":"testvm","namespace":"default","pos":"vm.go:2075","timestamp":"2023-07-07T16:50:47.430702Z","uid":""}
virt-handler {"component":"virt-handler","level":"error","msg":"failed to remove mdev types: failed to read the content of /sys/bus/mdev/devices directory","pos":"mediated_devices_types.go:275","reason":"open /sys/bus/mdev/devices: no such file or directory","timestamp":"2023-07-07T16:51:13.924784Z"}
virt-launcher + '[' aarch64 == x86_64 ']'
virt-launcher + virsh capabilities
virt-handler {"component":"virt-handler","level":"info","msg":"refreshed device plugins for permitted/forbidden host devices","pos":"device_controller.go:345","timestamp":"2023-07-07T16:51:13.924878Z"}
virt-handler {"component":"virt-handler","level":"info","msg":"enabled device-plugins for: []","pos":"device_controller.go:346","timestamp":"2023-07-07T16:51:13.924899Z"}
virt-handler {"component":"virt-handler","level":"info","msg":"disabled device-plugins for: []","pos":"device_controller.go:347","timestamp":"2023-07-07T16:51:13.924919Z"}
virt-handler {"component":"virt-handler","level":"info","msg":"Generic Allocate: resourceName: tun","pos":"generic_device.go:242","timestamp":"2023-07-07T16:51:17.490769Z"}
virt-handler {"component":"virt-handler","level":"info","msg":"Generic Allocate: request: [&ContainerAllocateRequest{DevicesIDs:[tun823],}]","pos":"generic_device.go:243","timestamp":"2023-07-07T16:51:17.490825Z"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"VMI is in phase: Scheduled | Domain does not exist","name":"testvm","namespace":"default","pos":"vm.go:1777","timestamp":"2023-07-07T16:51:45.379368Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"Bind mounting container disk at root: /proc/1/root, relative: /run/containerd/io.containerd.runtime.v2.task/k8s.io/7e8b95794a9dd52f4e532821bb84987f7d41ef9e5c1f67214a8bca9ef9475aee/rootfs/disk/downloaded to root: /var/lib/kubelet/pods/91479e89-07da-42fc-b67e-33631ac72cd7/volumes/kubernetes.io~empty-dir/container-disks, relative: /disk_0.img","name":"testvm","namespace":"default","pos":"mount.go:307","timestamp":"2023-07-07T16:51:45.382137Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"mounting kernel artifacts","name":"testvm","namespace":"default","pos":"mount.go:405","timestamp":"2023-07-07T16:51:45.424364Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"kernel boot not defined - nothing to mount","name":"testvm","namespace":"default","pos":"mount.go:408","timestamp":"2023-07-07T16:51:45.424399Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","level":"info","msg":"[ContextExecutor]: Executing... Switching from original () to desired () context","pos":"context_executor.go:75","timestamp":"2023-07-07T16:51:45.446502Z"}
virt-handler {"component":"virt-handler","level":"error","msg":"failed to create tap device named tap0","pos":"bridge.go:142","reason":"error creating tap device named tap0; failed to execute command in launcher namespace 10570: failed running command /usr/bin/virt-chroot create-tap --tap-name tap0 --uid 107 --gid 107 --queue-number 0 --mtu 65535, err: exit status 1, output: Error: failed to set MTU on tap device named tap0. Reason: invalid argument\nUsage:\n  virt-chroot create-tap [flags]\n\nFlags:\n      --gid uint              the group of the owner of the tap device\n  -h, --help                  help for create-tap\n      --mtu uint32            the link MTU of the tap device (default 1500)\n      --queue-number uint32   the number of queues to use on multi-queued devices\n      --tap-name string       the name of the tap device (default \"tap0\")\n      --uid uint              the owner of the tap device\n\nGlobal Flags:\n      --cpu uint       cpu time in seconds for the process\n      --memory uint    memory in bytes for the process\n      --mount string   mount namespace to use\n      --user string    switch to this targetUser to e.g. drop privileges\n\nfailed to set MTU on tap device named tap0. Reason: invalid argument\n","timestamp":"2023-07-07T16:51:45.482505Z"}
virt-handler {"component":"virt-handler","level":"error","msg":"failed to configure pod network: default","pos":"configstate.go:108","reason":"error creating tap device named tap0; failed to execute command in launcher namespace 10570: failed running command /usr/bin/virt-chroot create-tap --tap-name tap0 --uid 107 --gid 107 --queue-number 0 --mtu 65535, err: exit status 1, output: Error: failed to set MTU on tap device named tap0. Reason: invalid argument\nUsage:\n  virt-chroot create-tap [flags]\n\nFlags:\n      --gid uint              the group of the owner of the tap device\n  -h, --help                  help for create-tap\n      --mtu uint32            the link MTU of the tap device (default 1500)\n      --queue-number uint32   the number of queues to use on multi-queued devices\n      --tap-name string       the name of the tap device (default \"tap0\")\n      --uid uint              the owner of the tap device\n\nGlobal Flags:\n      --cpu uint       cpu time in seconds for the process\n      --memory uint    memory in bytes for the process\n      --mount string   mount namespace to use\n      --user string    switch to this targetUser to e.g. drop privileges\n\nfailed to set MTU on tap device named tap0. Reason: invalid argument\n","timestamp":"2023-07-07T16:51:45.482543Z"}
virt-handler {"component":"virt-handler","kind":"","level":"error","msg":"Synchronizing the VirtualMachineInstance failed.","name":"testvm","namespace":"default","pos":"vm.go:1923","reason":"failed to configure vmi network: setup failed, err: failed setup pod network phase1: Critical network error: error creating tap device named tap0; failed to execute command in launcher namespace 10570: failed running command /usr/bin/virt-chroot create-tap --tap-name tap0 --uid 107 --gid 107 --queue-number 0 --mtu 65535, err: exit status 1, output: Error: failed to set MTU on tap device named tap0. Reason: invalid argument\nUsage:\n  virt-chroot create-tap [flags]\n\nFlags:\n      --gid uint              the group of the owner of the tap device\n  -h, --help                  help for create-tap\n      --mtu uint32            the link MTU of the tap device (default 1500)\n      --queue-number uint32   the number of queues to use on multi-queued devices\n      --tap-name string       the name of the tap device (default \"tap0\")\n      --uid uint              the owner of the tap device\n\nGlobal Flags:\n      --cpu uint       cpu time in seconds for the process\n      --memory uint    memory in bytes for the process\n      --mount string   mount namespace to use\n      --user string    switch to this targetUser to e.g. drop privileges\n\nfailed to set MTU on tap device named tap0. Reason: invalid argument\n","timestamp":"2023-07-07T16:51:45.482594Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"migration is block migration because of containerdisk volume","name":"testvm","namespace":"default","pos":"vm.go:2447","timestamp":"2023-07-07T16:51:45.497153Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"migration is block migration because of cloudinitdisk volume","name":"testvm","namespace":"default","pos":"vm.go:2447","timestamp":"2023-07-07T16:51:45.497222Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","level":"error","msg":"virt-launcher crashed due to a network error. Updating VMI testvm status to Failed","pos":"vm.go:1355","timestamp":"2023-07-07T16:51:45.497251Z"}
virt-handler {"component":"virt-handler","level":"info","msg":"re-enqueuing VirtualMachineInstance default/testvm","pos":"vm.go:1567","reason":"failed to configure vmi network: setup failed, err: failed setup pod network phase1: Critical network error: error creating tap device named tap0; failed to execute command in launcher namespace 10570: failed running command /usr/bin/virt-chroot create-tap --tap-name tap0 --uid 107 --gid 107 --queue-number 0 --mtu 65535, err: exit status 1, output: Error: failed to set MTU on tap device named tap0. Reason: invalid argument\nUsage:\n  virt-chroot create-tap [flags]\n\nFlags:\n      --gid uint              the group of the owner of the tap device\n  -h, --help                  help for create-tap\n      --mtu uint32            the link MTU of the tap device (default 1500)\n      --queue-number uint32   the number of queues to use on multi-queued devices\n      --tap-name string       the name of the tap device (default \"tap0\")\n      --uid uint              the owner of the tap device\n\nGlobal Flags:\n      --cpu uint       cpu time in seconds for the process\n      --memory uint    memory in bytes for the process\n      --mount string   mount namespace to use\n      --user string    switch to this targetUser to e.g. drop privileges\n\nfailed to set MTU on tap device named tap0. Reason: invalid argument\n","timestamp":"2023-07-07T16:51:45.504391Z"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"VMI is in phase: Failed | Domain does not exist","name":"testvm","namespace":"default","pos":"vm.go:1777","timestamp":"2023-07-07T16:51:45.504437Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"Performing final local cleanup for vmi with uid ff6ed114-501c-4e6d-a694-90939fc419a0","name":"testvm","namespace":"default","pos":"vm.go:2041","timestamp":"2023-07-07T16:51:45.504471Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"Found container disk mount entries","name":"testvm","namespace":"default","pos":"mount.go:353","timestamp":"2023-07-07T16:51:45.504493Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"Looking to see if containerdisk is mounted at path /var/lib/kubelet/pods/91479e89-07da-42fc-b67e-33631ac72cd7/volumes/kubernetes.io~empty-dir/container-disks/disk_0.img","name":"testvm","namespace":"default","pos":"mount.go:355","timestamp":"2023-07-07T16:51:45.504508Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"unmounting container disk at path root: /, relative: /var/lib/kubelet/pods/91479e89-07da-42fc-b67e-33631ac72cd7/volumes/kubernetes.io~empty-dir/container-disks/disk_0.img","name":"testvm","namespace":"default","pos":"mount.go:367","timestamp":"2023-07-07T16:51:45.504596Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"Cleaning up remaining hotplug volumes","name":"testvm","namespace":"default","pos":"mount.go:769","timestamp":"2023-07-07T16:51:45.524197Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"Domain","level":"info","msg":"Removing domain from cache during final cleanup","name":"testvm","namespace":"default","pos":"vm.go:2075","timestamp":"2023-07-07T16:51:45.524563Z","uid":""}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"VMI is in phase: Failed | Domain does not exist","name":"testvm","namespace":"default","pos":"vm.go:1777","timestamp":"2023-07-07T16:51:45.524643Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"Performing final local cleanup for vmi with uid ff6ed114-501c-4e6d-a694-90939fc419a0","name":"testvm","namespace":"default","pos":"vm.go:2041","timestamp":"2023-07-07T16:51:45.524686Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"closing notify pipe listener for vmi","name":"testvm","namespace":"default","pos":"vm.go:340","timestamp":"2023-07-07T16:51:45.524609Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"No container disk mount entries found to unmount","name":"testvm","namespace":"default","pos":"mount.go:349","timestamp":"2023-07-07T16:51:45.524777Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"Cleaning up remaining hotplug volumes","name":"testvm","namespace":"default","pos":"mount.go:769","timestamp":"2023-07-07T16:51:45.524799Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"Domain","level":"info","msg":"Removing domain from cache during final cleanup","name":"testvm","namespace":"default","pos":"vm.go:2075","timestamp":"2023-07-07T16:51:45.524874Z","uid":""}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"VMI is in phase: Failed | Domain does not exist","name":"testvm","namespace":"default","pos":"vm.go:1777","timestamp":"2023-07-07T16:51:45.529187Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"Performing final local cleanup for vmi with uid ff6ed114-501c-4e6d-a694-90939fc419a0","name":"testvm","namespace":"default","pos":"vm.go:2041","timestamp":"2023-07-07T16:51:45.529334Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"No container disk mount entries found to unmount","name":"testvm","namespace":"default","pos":"mount.go:349","timestamp":"2023-07-07T16:51:45.529432Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"Cleaning up remaining hotplug volumes","name":"testvm","namespace":"default","pos":"mount.go:769","timestamp":"2023-07-07T16:51:45.529487Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"Domain","level":"info","msg":"Removing domain from cache during final cleanup","name":"testvm","namespace":"default","pos":"vm.go:2075","timestamp":"2023-07-07T16:51:45.529557Z","uid":""}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"VMI is in phase: Failed | Domain does not exist","name":"testvm","namespace":"default","pos":"vm.go:1777","timestamp":"2023-07-07T16:51:45.536599Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"Performing final local cleanup for vmi with uid ff6ed114-501c-4e6d-a694-90939fc419a0","name":"testvm","namespace":"default","pos":"vm.go:2041","timestamp":"2023-07-07T16:51:45.536655Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"No container disk mount entries found to unmount","name":"testvm","namespace":"default","pos":"mount.go:349","timestamp":"2023-07-07T16:51:45.536786Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"Cleaning up remaining hotplug volumes","name":"testvm","namespace":"default","pos":"mount.go:769","timestamp":"2023-07-07T16:51:45.536800Z","uid":"ff6ed114-501c-4e6d-a694-90939fc419a0"}
virt-handler {"component":"virt-handler","kind":"Domain","level":"info","msg":"Removing domain from cache during final cleanup","name":"testvm","namespace":"default","pos":"vm.go:2075","timestamp":"2023-07-07T16:51:45.536847Z","uid":""}
virt-handler {"component":"virt-handler","level":"info","msg":"VMI does not exist | Domain does not exist","pos":"vm.go:1782","timestamp":"2023-07-07T16:51:56.734870Z"}
virt-handler {"component":"virt-handler","kind":"VirtualMachineInstance","level":"info","msg":"Performing final local cleanup for vmi with uid ","name":"testvm","namespace":"default","pos":"vm.go:2041","timestamp":"2023-07-07T16:51:56.734927Z","uid":""}
virt-handler {"component":"virt-handler","kind":"Domain","level":"info","msg":"Removing domain from cache during final cleanup","name":"testvm","namespace":"default","pos":"vm.go:2075","timestamp":"2023-07-07T16:51:56.735000Z","uid":""}
virt-handler {"component":"virt-handler","level":"error","msg":"failed to remove mdev types: failed to read the content of /sys/bus/mdev/devices directory","pos":"mediated_devices_types.go:275","reason":"open /sys/bus/mdev/devices: no such file or directory","timestamp":"2023-07-07T16:53:11.618391Z"}
virt-handler {"component":"virt-handler","level":"info","msg":"refreshed device plugins for permitted/forbidden host devices","pos":"device_controller.go:345","timestamp":"2023-07-07T16:53:11.618487Z"}
virt-handler {"component":"virt-handler","level":"info","msg":"enabled device-plugins for: []","pos":"device_controller.go:346","timestamp":"2023-07-07T16:53:11.618514Z"}
virt-handler {"component":"virt-handler","level":"info","msg":"disabled device-plugins for: []","pos":"device_controller.go:347","timestamp":"2023-07-07T16:53:11.618867Z"}
virt-handler {"component":"virt-handler","level":"info","msg":"Generic Allocate: resourceName: tun","pos":"generic_device.go:242","timestamp":"2023-07-07T16:53:27.797111Z"}
virt-handler {"component":"virt-handler","level":"info","msg":"Generic Allocate: request: [&ContainerAllocateRequest{DevicesIDs:[tun856],}]","pos":"generic_device.go:243","timestamp":"2023-07-07T16:53:27.797164Z"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"VMI is in phase: Scheduled | Domain does not exist","name":"testvm","namespace":"default","pos":"vm.go:1777","timestamp":"2023-07-07T16:53:57.981430Z","uid":"a324e0eb-5c54-499c-86c5-1b0a11a546f6"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"Bind mounting container disk at root: /proc/1/root, relative: /run/containerd/io.containerd.runtime.v2.task/k8s.io/9ee40d8aa063280c7276eb608a3379415e0d1203509e982729af81135d4b4619/rootfs/disk/downloaded to root: /var/lib/kubelet/pods/38537c8c-3018-40ee-bf4c-ac6e41cbf5e1/volumes/kubernetes.io~empty-dir/container-disks, relative: /disk_0.img","name":"testvm","namespace":"default","pos":"mount.go:307","timestamp":"2023-07-07T16:53:57.984628Z","uid":"a324e0eb-5c54-499c-86c5-1b0a11a546f6"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"mounting kernel artifacts","name":"testvm","namespace":"default","pos":"mount.go:405","timestamp":"2023-07-07T16:53:58.027643Z","uid":"a324e0eb-5c54-499c-86c5-1b0a11a546f6"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"kernel boot not defined - nothing to mount","name":"testvm","namespace":"default","pos":"mount.go:408","timestamp":"2023-07-07T16:53:58.027689Z","uid":"a324e0eb-5c54-499c-86c5-1b0a11a546f6"}
virt-handler {"component":"virt-handler","level":"info","msg":"[ContextExecutor]: Executing... Switching from original () to desired () context","pos":"context_executor.go:75","timestamp":"2023-07-07T16:53:58.049390Z"}
virt-handler {"component":"virt-handler","level":"error","msg":"failed to create tap device named tap0","pos":"bridge.go:142","reason":"error creating tap device named tap0; failed to execute command in launcher namespace 11100: failed running command /usr/bin/virt-chroot create-tap --tap-name tap0 --uid 107 --gid 107 --queue-number 0 --mtu 65535, err: exit status 1, output: Error: failed to set MTU on tap device named tap0. Reason: invalid argument\nUsage:\n  virt-chroot create-tap [flags]\n\nFlags:\n      --gid uint              the group of the owner of the tap device\n  -h, --help                  help for create-tap\n      --mtu uint32            the link MTU of the tap device (default 1500)\n      --queue-number uint32   the number of queues to use on multi-queued devices\n      --tap-name string       the name of the tap device (default \"tap0\")\n      --uid uint              the owner of the tap device\n\nGlobal Flags:\n      --cpu uint       cpu time in seconds for the process\n      --memory uint    memory in bytes for the process\n      --mount string   mount namespace to use\n      --user string    switch to this targetUser to e.g. drop privileges\n\nfailed to set MTU on tap device named tap0. Reason: invalid argument\n","timestamp":"2023-07-07T16:53:58.085352Z"}
virt-handler {"component":"virt-handler","level":"error","msg":"failed to configure pod network: default","pos":"configstate.go:108","reason":"error creating tap device named tap0; failed to execute command in launcher namespace 11100: failed running command /usr/bin/virt-chroot create-tap --tap-name tap0 --uid 107 --gid 107 --queue-number 0 --mtu 65535, err: exit status 1, output: Error: failed to set MTU on tap device named tap0. Reason: invalid argument\nUsage:\n  virt-chroot create-tap [flags]\n\nFlags:\n      --gid uint              the group of the owner of the tap device\n  -h, --help                  help for create-tap\n      --mtu uint32            the link MTU of the tap device (default 1500)\n      --queue-number uint32   the number of queues to use on multi-queued devices\n      --tap-name string       the name of the tap device (default \"tap0\")\n      --uid uint              the owner of the tap device\n\nGlobal Flags:\n      --cpu uint       cpu time in seconds for the process\n      --memory uint    memory in bytes for the process\n      --mount string   mount namespace to use\n      --user string    switch to this targetUser to e.g. drop privileges\n\nfailed to set MTU on tap device named tap0. Reason: invalid argument\n","timestamp":"2023-07-07T16:53:58.085388Z"}
virt-handler {"component":"virt-handler","kind":"","level":"error","msg":"Synchronizing the VirtualMachineInstance failed.","name":"testvm","namespace":"default","pos":"vm.go:1923","reason":"failed to configure vmi network: setup failed, err: failed setup pod network phase1: Critical network error: error creating tap device named tap0; failed to execute command in launcher namespace 11100: failed running command /usr/bin/virt-chroot create-tap --tap-name tap0 --uid 107 --gid 107 --queue-number 0 --mtu 65535, err: exit status 1, output: Error: failed to set MTU on tap device named tap0. Reason: invalid argument\nUsage:\n  virt-chroot create-tap [flags]\n\nFlags:\n      --gid uint              the group of the owner of the tap device\n  -h, --help                  help for create-tap\n      --mtu uint32            the link MTU of the tap device (default 1500)\n      --queue-number uint32   the number of queues to use on multi-queued devices\n      --tap-name string       the name of the tap device (default \"tap0\")\n      --uid uint              the owner of the tap device\n\nGlobal Flags:\n      --cpu uint       cpu time in seconds for the process\n      --memory uint    memory in bytes for the process\n      --mount string   mount namespace to use\n      --user string    switch to this targetUser to e.g. drop privileges\n\nfailed to set MTU on tap device named tap0. Reason: invalid argument\n","timestamp":"2023-07-07T16:53:58.085431Z","uid":"a324e0eb-5c54-499c-86c5-1b0a11a546f6"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"migration is block migration because of containerdisk volume","name":"testvm","namespace":"default","pos":"vm.go:2447","timestamp":"2023-07-07T16:53:58.100628Z","uid":"a324e0eb-5c54-499c-86c5-1b0a11a546f6"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"migration is block migration because of cloudinitdisk volume","name":"testvm","namespace":"default","pos":"vm.go:2447","timestamp":"2023-07-07T16:53:58.100684Z","uid":"a324e0eb-5c54-499c-86c5-1b0a11a546f6"}
virt-handler {"component":"virt-handler","level":"error","msg":"virt-launcher crashed due to a network error. Updating VMI testvm status to Failed","pos":"vm.go:1355","timestamp":"2023-07-07T16:53:58.100703Z"}
virt-handler {"component":"virt-handler","level":"info","msg":"re-enqueuing VirtualMachineInstance default/testvm","pos":"vm.go:1567","reason":"failed to configure vmi network: setup failed, err: failed setup pod network phase1: Critical network error: error creating tap device named tap0; failed to execute command in launcher namespace 11100: failed running command /usr/bin/virt-chroot create-tap --tap-name tap0 --uid 107 --gid 107 --queue-number 0 --mtu 65535, err: exit status 1, output: Error: failed to set MTU on tap device named tap0. Reason: invalid argument\nUsage:\n  virt-chroot create-tap [flags]\n\nFlags:\n      --gid uint              the group of the owner of the tap device\n  -h, --help                  help for create-tap\n      --mtu uint32            the link MTU of the tap device (default 1500)\n      --queue-number uint32   the number of queues to use on multi-queued devices\n      --tap-name string       the name of the tap device (default \"tap0\")\n      --uid uint              the owner of the tap device\n\nGlobal Flags:\n      --cpu uint       cpu time in seconds for the process\n      --memory uint    memory in bytes for the process\n      --mount string   mount namespace to use\n      --user string    switch to this targetUser to e.g. drop privileges\n\nfailed to set MTU on tap device named tap0. Reason: invalid argument\n","timestamp":"2023-07-07T16:53:58.110803Z"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"VMI is in phase: Failed | Domain does not exist","name":"testvm","namespace":"default","pos":"vm.go:1777","timestamp":"2023-07-07T16:53:58.110938Z","uid":"a324e0eb-5c54-499c-86c5-1b0a11a546f6"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"Performing final local cleanup for vmi with uid a324e0eb-5c54-499c-86c5-1b0a11a546f6","name":"testvm","namespace":"default","pos":"vm.go:2041","timestamp":"2023-07-07T16:53:58.111062Z","uid":"a324e0eb-5c54-499c-86c5-1b0a11a546f6"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"Found container disk mount entries","name":"testvm","namespace":"default","pos":"mount.go:353","timestamp":"2023-07-07T16:53:58.111115Z","uid":"a324e0eb-5c54-499c-86c5-1b0a11a546f6"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"Looking to see if containerdisk is mounted at path /var/lib/kubelet/pods/38537c8c-3018-40ee-bf4c-ac6e41cbf5e1/volumes/kubernetes.io~empty-dir/container-disks/disk_0.img","name":"testvm","namespace":"default","pos":"mount.go:355","timestamp":"2023-07-07T16:53:58.111211Z","uid":"a324e0eb-5c54-499c-86c5-1b0a11a546f6"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"unmounting container disk at path root: /, relative: /var/lib/kubelet/pods/38537c8c-3018-40ee-bf4c-ac6e41cbf5e1/volumes/kubernetes.io~empty-dir/container-disks/disk_0.img","name":"testvm","namespace":"default","pos":"mount.go:367","timestamp":"2023-07-07T16:53:58.111352Z","uid":"a324e0eb-5c54-499c-86c5-1b0a11a546f6"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"Cleaning up remaining hotplug volumes","name":"testvm","namespace":"default","pos":"mount.go:769","timestamp":"2023-07-07T16:53:58.133171Z","uid":"a324e0eb-5c54-499c-86c5-1b0a11a546f6"}
virt-handler {"component":"virt-handler","kind":"Domain","level":"info","msg":"Removing domain from cache during final cleanup","name":"testvm","namespace":"default","pos":"vm.go:2075","timestamp":"2023-07-07T16:53:58.133284Z","uid":""}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"VMI is in phase: Failed | Domain does not exist","name":"testvm","namespace":"default","pos":"vm.go:1777","timestamp":"2023-07-07T16:53:58.133314Z","uid":"a324e0eb-5c54-499c-86c5-1b0a11a546f6"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"Performing final local cleanup for vmi with uid a324e0eb-5c54-499c-86c5-1b0a11a546f6","name":"testvm","namespace":"default","pos":"vm.go:2041","timestamp":"2023-07-07T16:53:58.133331Z","uid":"a324e0eb-5c54-499c-86c5-1b0a11a546f6"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"No container disk mount entries found to unmount","name":"testvm","namespace":"default","pos":"mount.go:349","timestamp":"2023-07-07T16:53:58.133353Z","uid":"a324e0eb-5c54-499c-86c5-1b0a11a546f6"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"Cleaning up remaining hotplug volumes","name":"testvm","namespace":"default","pos":"mount.go:769","timestamp":"2023-07-07T16:53:58.133362Z","uid":"a324e0eb-5c54-499c-86c5-1b0a11a546f6"}
virt-handler {"component":"virt-handler","kind":"Domain","level":"info","msg":"Removing domain from cache during final cleanup","name":"testvm","namespace":"default","pos":"vm.go:2075","timestamp":"2023-07-07T16:53:58.133393Z","uid":""}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"closing notify pipe listener for vmi","name":"testvm","namespace":"default","pos":"vm.go:340","timestamp":"2023-07-07T16:53:58.133444Z","uid":"a324e0eb-5c54-499c-86c5-1b0a11a546f6"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"VMI is in phase: Failed | Domain does not exist","name":"testvm","namespace":"default","pos":"vm.go:1777","timestamp":"2023-07-07T16:53:58.139648Z","uid":"a324e0eb-5c54-499c-86c5-1b0a11a546f6"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"Performing final local cleanup for vmi with uid a324e0eb-5c54-499c-86c5-1b0a11a546f6","name":"testvm","namespace":"default","pos":"vm.go:2041","timestamp":"2023-07-07T16:53:58.139708Z","uid":"a324e0eb-5c54-499c-86c5-1b0a11a546f6"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"No container disk mount entries found to unmount","name":"testvm","namespace":"default","pos":"mount.go:349","timestamp":"2023-07-07T16:53:58.140671Z","uid":"a324e0eb-5c54-499c-86c5-1b0a11a546f6"}
virt-handler {"component":"virt-handler","kind":"","level":"info","msg":"Cleaning up remaining hotplug volumes","name":"testvm","namespace":"default","pos":"mount.go:769","timestamp":"2023-07-07T16:53:58.140688Z","uid":"a324e0eb-5c54-499c-86c5-1b0a11a546f6"}
virt-handler {"component":"virt-handler","kind":"Domain","level":"info","msg":"Removing domain from cache during final cleanup","name":"testvm","namespace":"default","pos":"vm.go:2075","timestamp":"2023-07-07T16:53:58.140723Z","uid":""}
virt-handler {"component":"virt-handler","level":"info","msg":"VMI does not exist | Domain does not exist","pos":"vm.go:1782","timestamp":"2023-07-07T16:54:09.332312Z"}
virt-handler {"component":"virt-handler","kind":"VirtualMachineInstance","level":"info","msg":"Performing final local cleanup for vmi with uid ","name":"testvm","namespace":"default","pos":"vm.go:2041","timestamp":"2023-07-07T16:54:09.332370Z","uid":""}
virt-handler {"component":"virt-handler","kind":"Domain","level":"info","msg":"Removing domain from cache during final cleanup","name":"testvm","namespace":"default","pos":"vm.go:2075","timestamp":"2023-07-07T16:54:09.332429Z","uid":""}
virt-handler {"component":"virt-handler","level":"error","msg":"failed to remove mdev types: failed to read the content of /sys/bus/mdev/devices directory","pos":"mediated_devices_types.go:275","reason":"open /sys/bus/mdev/devices: no such file or directory","timestamp":"2023-07-07T16:54:24.809470Z"}
virt-handler {"component":"virt-handler","level":"info","msg":"refreshed device plugins for permitted/forbidden host devices","pos":"device_controller.go:345","timestamp":"2023-07-07T16:54:24.809604Z"}
virt-handler {"component":"virt-handler","level":"info","msg":"enabled device-plugins for: []","pos":"device_controller.go:346","timestamp":"2023-07-07T16:54:24.809639Z"}
virt-handler {"component":"virt-handler","level":"info","msg":"disabled device-plugins for: []","pos":"device_controller.go:347","timestamp":"2023-07-07T16:54:24.809655Z"}
Stream closed EOF for kubevirt/virt-handler-sh4h7 (virt-launcher)

Just to note: I am not sure that it is going to work on a mac. AFAIK, Kind runs k8s in containers. For KubeVirt you need a Linux host. As an option, you may try spinning a VM, install k8s there and deploy KubeVirt on top. But likely you will have to use software emulation, and that is going to be extremely slow.

Apologies, but we have only verified KubeVirt on the Arm64 Linux platform. After reviewing the logs, I don't immediately know the root cause of these issues. I highly recommend running KubeVirt on a native Linux platform.

Have similar situation here, is there any way to extract more debug logs from kubevirt scheduler?

Hey @hugeps ,Kubevirt doesn't have a special scheduler. You need to check your default scheduler for more info.
@ByteFlyCoding in this case you need to enable emulation, please see https://github.com/kubevirt/kubevirt/blob/main/docs/software-emulation.md


SwiftUI image not found on older iOS versions.

dyld: Library not loaded: /System/Library/Frameworks/SwiftUI.framework/SwiftUI
Referenced from: /var/containers/Bundle/Application/MyApp.app/MyApp
Reason: image not found
I worked around this by adding:
 -weak_framework SwiftUI

to the Other Linter Flags in the Parchment build as suggested by Apple in the iOS 13 release notes:
https://developer.apple.com/documentation/ios-ipados-release-notes/ios-13-release-notes

Hi! Could you check if this is still a problem with the v3.1.0 release?

But we don't commit Pods.xcodeproj, and then how can I save -weak_framework SwiftUI code changes?

@torburg
Here is a nice post install code you put at the bottom of your Podfile, which will do this every time you run pod install.
post_install do |installer|
  installer.pods_project.targets.each do |target|
    if target.name == 'Parchment'
      target.build_configurations.each do |config|
        config.build_settings['OTHER_LDFLAGS'] = '-weak_framework SwiftUI'
      end
    end
  end
end

This should be fixed in the master branch now thanks to @kambala-decapitator 🙌 Will release a new version soon


[BUG] Carousel Loop not working in Category Cards on Homepage

Description
The Category Cards carousel on homepage does not loop like other carousel on the page
Screenshots

Any additional information?
No response
What browser are you seeing the problem on?
Chrome
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I have read the discussion tab thoroughly and got the project idea
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

@rohansx Please assign this issue to me under GSSoC 23

@ManasMadan go ahead

@ManasMadan Also needs a feature where using our mouse we can slide the carousel, it is already implemented on the books cards but it is not there in the category card, so you can create an issue and I'll assign it to you


Fix a missing unconditional branch, remove an unnecessary branch chain.

@rajatd please review

Looks good. Can you add unit tests for this?

@dotnet-bot test this please

@dotnet-bot test Ubuntu ubuntu_linux_release_static please


Don't use these files on Mojave!

It's obviously deprecated and should be declared as such.
I spend a whole day to install all tools on a new Macbook pro including node and Homebrew and all such things. Everything worked. Then (way to late I guess) I applied the dotfiles. Nothing is working anymore. Node doesn't find anything. "npm install xxx" will give "xxx not found". Same with Homebrew.
Even a bash-shell can't be opened any more. Any ideas?

This just sounds like your Node environment needs a bit of attention. Starting from scratch is really not necessary.

$ echo $PATH
/usr/local/Cellar//usr/local/Cellar/:/Users/hagen/bin:/Users/hagen/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
$ git clone git@github.com:itinance/ncd-token.git
-bash: /usr/local/bin/git: No such file or directory
Nothing out of /usr/local/bin can be reached any more, although its in the PATH

Opening a new shell:
bash: /usr/local/bin/bash: No such file or directory
bash: line 0: exec: /usr/local/bin/bash: cannot execute: No such file or directory

https://github.com/mathiasbynens/dotfiles#installation

Warning: If you want to give these dotfiles a try, you should first fork this repository, review the code, and remove things you don’t want or need. Don’t blindly use my settings unless you know what that entails. Use at your own risk!

I was my own fork that always worked well (unless I used it on a new Mojave installation).
Any ideas, why /usr/local/bin/bash can't be found in a new shell although it can be found in a current active shell?

I heard that the upcoming macOS version switches to zsh over bash by default. This might have something to do with that? Either way, I haven't played with Mojave yet so I cannot really help here.

I'm using most of these files on Mojave 10.14.5 without any issue. I've used them both on an upgraded installation and a fresh one
FWIW, I'm not using .macos or .osx by my personal choice, so I don't know if the problem is there

I can confirm @tagliala’s experience; I’ve been on Mojave since it was released, using my fork of these dot files, and they work fine. I also, however, don’t run the .macos script, though I used to.
I’m sure they’ll need some work once zsh becomes the default shell in macOS 10.15, though I’m planning on probably sticking with bash myself.

@itinance as for not finding /usr/local/bin/bash in a new shell, that sounds like your $PATH isn’t being set early enough? Seems odd, that… you can take a look at how I scripted my initial Brew setup here: https://github.com/jeffbyrnes/dotfiles/blob/master/brew.sh#L21-L24

To be fair @jeffbyrnes has done some great work on here of late. Thanks Jeff!

@itinance as for not finding /usr/local/bin/bash in a new shell, that sounds like your $PATH isn’t being set early enough? Seems odd, that… you can take a look at how I scripted my initial Brew setup here: https://github.com/jeffbyrnes/dotfiles/blob/master/brew.sh#L21-L24

https://scriptingosx.com/2019/02/install-bash-5-on-macos/

Many thanks to @jeffbyrnes! I switched to https://github.com/jeffbyrnes/dotfiles and it works brilliant.
One of my issue was, that somehow the base shell was changed to /usr/local/bin/bash without any /usr/local/bin/bash existing. And somehow issues with $PATH after installation.

That would definitely cause you some trouble. Glad my fork helped you out!

And as a second step, I solved the node-issues with this line:
`npm config set prefix /usr/local``
After installing the dotfiles, this config must have been wrong somehow, that no global installed node-based tool was working any more. With this setting everything was repaired around this.


Interpolation issue- minimum frame change

It seems that interpolation only works correctly across 4 or more frames. If I want to get the right annotation, I have to jump ahead by at least 3 frames. This makes frame by frame correction difficult / impossible. This is a bigger problem when on object comes into frame - if frame by frame correction is attempted, the outside of view attributed is incorrectly interpolated. If anyone else who is facing this problem / knows how to fix it/ knows where to look to fix it could let me know, I would greatly appreciate it. Thanks!

Did you find a catch yet? I have recently reduced the frames per second of my video. I made a sub-video out of main video taking only every 10 frames. When I annotate the resulting sub-video, interpolation doesnt work fine and the bounding boxes around the object is always moving.

for the "outside of view attributed is incorrectly interpolated". You may want to set the blow-radius=0 when "load" a task

^that's what I ended up doing finally
I fixed my outside attribute code by making it identical to the occluded code (removing the interpolation of that attribute using the estimate function), and set the blow-radius 1 so that interpolation of objects worked across one frame.


Add out-of-order blocks to bucket verify

Is your proposal related to a problem?
When a Compactor halts due to an out-of-order (OOO) block, there are normally several OOO blocks that need to be tidied up before Compactor can safely run again. At the moment, Compactor only tells me about the first OOO block that it finds - so I need to go through quite a long cycle of identifying a broken block, deleting the broken block, and restarting compactor, multiple times before the storage account is clean.
Describe the solution you'd like
I would like thanos tools bucket verify to check for OOO blocks, and to tell me about all of the ones that it finds.
Describe alternatives you've considered
n.a.
Additional context
n.a.

Are you looking for a tool to check OOO chunks or OOO blocks? If it is the latter one, the verify tool can already tell your all overalapped blocks for a group I think.

Just to be clear on terminology, what would you consider a chunk and what would you consider a block?
My experience last week was that thanos tools bucket verify gave me a list of overlapped blocks, all of which I deleted. When I restarted Thanos Compactor, it then halted on a block which hadn't been part of the output of verify. I don't have a note of the error message, but it was because the block contained a small number (1 or 2) of out-of-order time series, rather than the whole block being out of order, if this is what your question is referring to. Is the issue here that verify only verifies that the timestamps of the blocks themselves are in order, but doesn't verify the time series within them?

@AndrewNiven1 this describes the difference between chunks and blocks - https://thanos.io/tip/thanos/design.md/#metric-data-backup
Another question: When you ran tools bucket verify did you receive any warning about OOO series, along with overlapping blocks?
The index issues checked during mention any OOO series.

When I restarted Thanos Compactor, it then halted on a block which hadn't been part of the output of verify. I don't have a note of the error message, but it was because the block contained a small number (1 or 2) of out-of-order time series rather than the whole block being out of order, if this is what your question is referring to.

Yes, out of order time series and halting is related to OOO chunks and has nothing to do with OOO blocks.

Is the issue here that verify only verifies that the timestamps of the blocks themselves are in order, but doesn't verify the time series within them?

The verify tool already supports verifying all series by default. But this is another step after checking the overlapped blocks. So if you failed the previous check, the check for OOO chunks won't start.
Can you try the latest main branch? With https://github.com/thanos-io/thanos/pull/4727/files#diff-ff9912cc5d78d6a548e6ba9cc818cd48e67f7ee5e23a817107cc84ba55c68e02R331 and debug log level we are already able to show all out of order chunks.

Hi both, thanks for your answers. I was using v0.23.0-rc.1, so I don't have that last PR which would hopefully provide what I want. Unfortunately I already tidied up the ABS that was causing problems, so I can't reproduce the issue or do any testing on it. What I remember is:

I ran tools bucket verify, which gave me a list of overlapping blocks
I deleted these blocks
I ran tools bucket verify again, without the repair flag, which did not report any issues
I ran Thanos Compactor, which halted because of an OOO series

As you say, Thanos should already do what I want it to, so either there's a bug or I've missed something - in either case I don't think there's much more to be discussed here until I can reproduce the issue. I'll try and do this when I get time.
Thanks both

Hi again,
I'd like to reopen this issue, as I'm seeing the same behaviour again.
When compactor is running against a certain ABS, it fails with the following error message:
level=warn ts=2021-11-26T07:48:58.625467572Z caller=intrumentation.go:54 msg="changing probe status" status=not-ready reason="error executing compaction: compaction: group 0@17975502000459606275: blocks with out-of-order chunks are dropped from compaction:  /data/compact/0@17975502000459606275/01FKQ2QTPC73X07XKW7VS1E8JG: 1/438729 series have an average of 1.000 out-of-order chunks: 1.000 of these are exact duplicates (in terms of data and time range)"
There are several similar error message referring to the same block.
If I run thanos tools bucket verify over the ABS account, using --issues=index_known_issues, I would expect to see the out of order time series - as I understand it, the line you linked above (this one) that flags OOO series is run as part of the index_known_issues check. However, I see no error message:
Step 4/4 : RUN thanos tools bucket verify --log.level=debug --issues=index_known_issues --id=01FKQ2QTPC73X07XKW7VS1E8JG --objstore.config-file=/objstore.yml
level=debug ts=2021-11-29T14:25:29.069639483Z caller=azure.go:374 msg="check if blob exists" blob=01FKQ2QTPC73X07XKW7VS1E8JG/meta.json
level=debug ts=2021-11-29T14:25:29.461829594Z caller=azure.go:295 msg="getting blob" blob=01FKQ2QTPC73X07XKW7VS1E8JG/meta.json offset=0 length=0
level=debug ts=2021-11-29T14:25:29.461953931Z caller=azure.go:374 msg="check if blob exists" blob=01FKQ2QTPC73X07XKW7VS1E8JG/meta.json
level=debug ts=2021-11-29T14:25:34.977022191Z caller=azure.go:326 msg="set size to go to EOF" contentlength=983 size=983 length=0 offset=0 name=01FKQ2QTPC73X07XKW7VS1E8JG/meta.json

This is the same if I enable the --repair flag.
This is using the most up to date version of master as of this morning (main-2021-11-26-78391ded).
For what it's worth, I'm aware that one of our microservices is sometimes pushing out-of-order time series, and I'm trying to get that fixed, but in the meantime we need to be able to easily identify and repair these out-of-order series.
I'm curious about why the out-of-order series is picked up by the check in the Compaction routine, but not in the Verify routine - I'm going to try and compare the code and see what the difference is.
Any help (or pointing out that I've done something wrong) would be much appreciated.

I've run verify again - the first time I ran it I didn't get a summary at the end, but this time I did. The final output is as follows:
level=debug ts=2021-11-29T15:50:24.250768867Z caller=index_issue.go:64 verifiers=index_known_issues verifier=index_known_issues stats="{TotalSeries:49402 OutOfOrderSeries:0 OutOfOrderChunks:0 DuplicatedChunks:0 OutsideChunks:0 CompleteOutsideChunks:0 Issue347OutsideChunks:0 OutOfOrderLabels:0 SeriesMinLifeDuration:2m44.631s SeriesAvgLifeDuration:1h58m21.913s SeriesMaxLifeDuration:1h59m30.219s SeriesMinLifeDurationWithoutSingleSampleSeries:2m44.631s SeriesAvgLifeDurationWithoutSingleSampleSeries:1h58m21.913s SeriesMaxLifeDurationWithoutSingleSampleSeries:1h59m30.219s SeriesMinChunks:1 SeriesAvgChunks:3 SeriesMaxChunks:4 TotalChunks:187632 ChunkMinDuration:2m44.631s ChunkAvgDuration:31m9.876s ChunkMaxDuration:1h59m0s ChunkMinSize:54 ChunkAvgSize:147 ChunkMaxSize:1251 SingleSampleSeries:0 SingleSampleChunks:0 LabelNamesCount:212 MetricLabelValuesCount:1319}" id=01FN2SC2A7B4K022T6FBWPWTJP

It looks to me like this is only actually verifying a single block, so my issue here is really just the same as https://github.com/thanos-io/thanos/issues/4878. If you agree I'm happy to close this issue in favour of that one.

Close as #4878 was closed. Thanks @AndrewNiven1


Frontend Routes for Admin

Short PR for the admin panel's routes.
They're all set to a blank page (with a TODO div) at the moment.
Are these URLs okay?
They can be changed anything, I'm just wondering if they'll conflict with the server's API.
Will we be using /api/* for those?

Ideally, the api or app part should be the subdomain name, but we haven't settle this yet so you left them out for now.
The /users or /admins should return all paged users if not provided any parameters so we probably don't need /users/all etc.
The action should be reflected by the HTTP request method as much as possible instead of part of the path which is used to identify resource. So instead of /users/create, it should be a HTTP request: `POST /amins'
The Search API is prioritized with its own API category (following the style of facebook and github) so searching for a user would be /search/users instead of /users/search

These are URLs for pages, not requests.
They're handled by JavaScript.
Essentially, the flow goes like this:
User goes to base home page
-> JS on page determines which "virtual page" to redirect to based on url in address
-> JS loads components and parts to render that "virtual page" into an actual one.
So, for example, if the user goes to /app/users, the server will serve /app/index.htm instead.
The JS on the page then detects that it's supposed to be /app/users, redirects to /app/users/all, and renders the components for that page.
The JS in those components will then activate and send a request to /api/users/, reorganises the retrieved data, and renders them.
So, yeah, these URLs are meant for the web browser, not for API requests.

All right, sure. Since we use the subdomain to distinguish between the app server and the media server, not the api and the pages, we should have some prefix to avoid clashes with the api. How about something like /admins/pages/... for admin pages and '/views/pages/..` for pages to view stream from web browser?

I personally prefer something more generic like /admin or /app.
/admin/pages/ sounds okay. (admins sounds like a request)
It'll result in /admin/pages/admins for the admin CRUD pages in the admin web pages, though, lol.
root/view - WebView
root/admin - Admin Panel
root/api - REST API
^ Works?
I'll run with that for static file handler on the server side if that's okay.
I'll probably be leaving the static file handler for later, until we have a minimum REST API (able to connect to DB, return JSON).
I think I'll probably mess the files up if I try jamming it in somewhere now.

Ok sure I will reconfigure the REST routes with /api prefix then.


modified dialog system to work with the multi-connection changes

#133 modified dialog system to work with the multi-connection changes #74
Modified all the BaseDialogNode derived classes to use the new connection system and define their own static and dynamic Connection Knobs
Added a common method in BaseDialogNode for all classes to use to check if a specific connection points to another node and get that node
DialogNodeCanvas - I could not get the list of Dialog Start Nodes (_lstDialogStartNodes) to work, it kept getting "type mismatch" in unity, so I removed the list and dynamically get the list now.
Dialog1.asset - created a new example as the existing one would not load
tested with unity version 5.5.2f1 personal

Thanks very much for you effort, seems like a solid port! :)


paper issue

hello ,i have read the paper"Towards End-to-End Lane Detection: an Instance Segmentation Approach"
do you know what's the meaning of the "bounded inverse class weighting"(to solve the problem that the lane lines area is too small).  i can not find the detailed explanation about the "bounded inverse class weighting"
thanks so much!

As I understand, you just weight the classes anti proportional to their frequency and have some cutoff value. I think, I did the same but hardcoded the values

i just want to use the binary segmentation branch, how to change your code? the meanshift cluster is so slow.
thanks a lot!


Uncaught TypeError: Cannot read property 'tokens' of undefined

[Enter steps to reproduce below:]

just clicked and tried to drag on minimap as is possible with ST

Atom Version: 0.166.0
System: Mac OS X 10.10.1
Thrown From: minimap package, v3.5.2
Stack Trace
Uncaught TypeError: Cannot read property 'tokens' of undefined
At /opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app/src/display-buffer.js:958

TypeError: Cannot read property 'tokens' of undefined
  at DisplayBuffer.module.exports.DisplayBuffer.screenPositionForPixelPosition (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app/src/display-buffer.js:958:50)
  at MinimapView.module.exports.MinimapView.onMouseDown (/Users/Dan/Dropbox/Mackup/.atom/packages/minimap/lib/minimap-view.coffee:500:38)
  at space-pen-div.<anonymous> (/Users/Dan/Dropbox/Mackup/.atom/packages/minimap/lib/minimap-view.coffee:1:1)

Commands
     -0:00.0 open-recent:open-recent-path-2 (ul.list-inline.tab-bar.inset-panel)

Config
{
  "core": {
    "ignoredNames": [
      ".git",
      ".svn",
      ".DS_Store",
      "._*"
    ],
    "followSymlinks": true,
    "disabledPackages": [
      "sublime-tabs",
      "highlight-line",
      "language-objective-c",
      "language-perl",
      "language-php",
      "language-mustache",
      "language-java"
    ],
    "themes": [
      "atom-dark-ui",
      "monokai"
    ],
    "projectHome": "/Users/Dan/Code",
    "destroyEmptyPanes": false
  }
}

Installed Packages
# User
atom-color-highlight, v3.0.2
color-picker, v1.2.6
docblockr, v0.5.8
editorconfig, v0.2.3
file-icons, v1.4.4
language-jade, v0.3.0
linter, v0.9.1
linter-csslint, v0.0.11
linter-jscs, v1.4.9
linter-jshint, v0.1.0
linter-less, v0.3.1
linter-tidy, v0.0.1
local-history, v2.0.0
minimap, v3.5.2
monokai, v0.9.0
open-recent, v2.0.0

# Dev
No dev packages

/cc @atom/core

Thanks for the report, I'll fix that asap.

Hmm, I can't reproduce it, does it occurs repeatedly?
I also see that the last command comes from the open-recent package, is there a recent update of this package? Does this error occurs when opening a project the classical way?

Same error here. Just clicked on the minimap
Atom Version: 0.165.0
System: Ubuntu 14.10
Thrown From: minimap package, v3.5.3
Stack Trace
TypeError: Cannot read property 'tokens' of undefined
  at DisplayBuffer.module.exports.DisplayBuffer.screenPositionForPixelPosition (/opt/atom/resources/app/src/display-buffer.js:940:50)
  at MinimapView.module.exports.MinimapView.onMouseDown (/home/sdouche/.atom/packages/minimap/lib/minimap-view.coffee:500:38)
  at space-pen-div.<anonymous> (/home/sdouche/.atom/packages/minimap/lib/minimap-view.coffee:1:1)

Same error here. Happened when I have split the view and then destroyed the split.

Occurs pretty regularly - I opened a folder without using the 'open-recent' package and same thing but it took me a few attempts with different files to get it to happen.  Interestingly my package.json seems to work best.

The new click handler now use the same implementation as with v4 preview, meaning that it doesn't rely on screenPositionForPixelPosition to compute the row at position. I hope it'll fix the issue, if not I'll reopen this ticket.