Can't mount a disk that doesn't have any partitions. Fails to mount with error code: 22

Version
10.0.22000.593
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps

GET-CimInstance -query "SELECT * from Win32_DiskDrive"
DeviceID           Caption                    Partitions Size          Model

\.\PHYSICALDRIVE0 Samsung SSD 980 PRO 2TB    3<PHONE_NUMBER>280 Samsung SSD 980 PRO 2TB
\.\PHYSICALDRIVE2 SAMSUNG MZPLJ6T4HALA-00007 1<PHONE_NUMBER>480 SAMSUNG MZPLJ6T4HALA-00007
\.\PHYSICALDRIVE1 SAMSUNG MZ1L21T9HCLS-00A07 0<PHONE_NUMBER>440 SAMSUNG MZ1L21T9HCLS-00A07

wsl --mount \.\PHYSICALDRIVE1 -t ext4
Expected Behavior
Disk should mount
Actual Behavior
The disk \.\PHYSICALDRIVE1 was attached from WSL2, but failed to mount (error code: -22). For more details, run 'dmesg' inside WSL2.
Diagnostic Logs
root@DESKTOP-C0D284N:/home/ubuntu# dmesg
[    0.000000] Linux version <IP_ADDRESS>-microsoft-standard-WSL2 (oe-user@oe-host) (x86_64-msft-linux-gcc (GCC) 9.3.0, GNU ld (GNU Binutils) <IP_ADDRESS>00220) #1 SMP Wed Mar 2 00:30:59 UTC 2022
[    0.000000] Command line: initrd=\initrd.img panic=-1 nr_cpus=24 swiotlb=force pty.legacy_count=0
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000e0fff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000001fffff] ACPI data
[    0.000000] BIOS-e820: [mem 0x0000000000200000-0x00000000f7ffffff] usable
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000008013fffff] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] DMI not present or invalid.
[    0.000000] Hypervisor detected: Microsoft Hyper-V
[    0.000000] Hyper-V: privilege flags low 0xae7f, high 0x3b8030, hints 0xa4e24, misc 0xe0bed7b2
[    0.000000] Hyper-V Host Build:22000-10.0-0-0.593
[    0.000000] Hyper-V: LAPIC Timer Frequency: 0x1e8480
[    0.000000] Hyper-V: Using hypercall for remote TLB flush
[    0.000000] clocksource: hyperv_clocksource_tsc_page: mask: 0xffffffffffffffff max_cycles: 0x24e6a1710, max_idle_ns:<PHONE_NUMBER>20 ns
[    0.000001] tsc: Detected 3187.197 MHz processor
[    0.000006] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.000008] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.000009] last_pfn = 0x801400 max_arch_pfn = 0x400000000
[    0.000021] MTRR default type: uncachable
[    0.000022] MTRR fixed ranges enabled:
[    0.000022]   00000-3FFFF write-back
[    0.000022]   40000-7FFFF uncachable
[    0.000023]   80000-8FFFF write-back
[    0.000023]   90000-FFFFF uncachable
[    0.000023] MTRR variable ranges enabled:
[    0.000024]   0 base<PHONE_NUMBER>00 mask 3FFF00000000 write-back
[    0.000024]   1 base<PHONE_NUMBER>00 mask 3FF000000000 write-back
[    0.000025]   2 disabled
[    0.000025]   3 disabled
[    0.000025]   4 disabled
[    0.000025]   5 disabled
[    0.000025]   6 disabled
[    0.000026]   7 disabled
[    0.000029] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT
[    0.000036] last_pfn = 0xf8000 max_arch_pfn = 0x400000000
[    0.000044] Using GB pages for direct mapping
[    0.000282] RAMDISK: [mem 0x03835000-0x03843fff]
[    0.000283] ACPI: Early table checksum verification disabled
[    0.000292] ACPI: RSDP 0x00000000000E0000 000024 (v02 VRTUAL)
[    0.000294] ACPI: XSDT 0x0000000000100000 000044 (v01 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000297] ACPI: FACP 0x0000000000101000 000114 (v06 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000300] ACPI: DSDT 0x00000000001011B8 01E184 (v02 MSFTVM DSDT01   00000001 MSFT 05000000)
[    0.000302] ACPI: FACS 0x0000000000101114 000040
[    0.000303] ACPI: OEM0 0x0000000000101154 000064 (v01 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000305] ACPI: SRAT 0x000000000011F33C 000430 (v02 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000307] ACPI: APIC 0x000000000011F76C 000108 (v04 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000308] ACPI: Reserving FACP table memory at [mem 0x101000-0x101113]
[    0.000309] ACPI: Reserving DSDT table memory at [mem 0x1011b8-0x11f33b]
[    0.000309] ACPI: Reserving FACS table memory at [mem 0x101114-0x101153]
[    0.000309] ACPI: Reserving OEM0 table memory at [mem 0x101154-0x1011b7]
[    0.000310] ACPI: Reserving SRAT table memory at [mem 0x11f33c-0x11f76b]
[    0.000310] ACPI: Reserving APIC table memory at [mem 0x11f76c-0x11f873]
[    0.000315] ACPI: Local APIC address 0xfee00000
[    0.000435] Zone ranges:
[    0.000436]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.000437]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
[    0.000437]   Normal   [mem 0x0000000100000000-0x00000008013fffff]
[    0.000438]   Device   empty
[    0.000438] Movable zone start for each node
[    0.000439] Early memory node ranges
[    0.000439]   node   0: [mem 0x0000000000001000-0x000000000009ffff]
[    0.000440]   node   0: [mem 0x0000000000200000-0x00000000f7ffffff]
[    0.000440]   node   0: [mem 0x0000000100000000-0x00000008013fffff]
[    0.000441] Initmem setup node 0 [mem 0x0000000000001000-0x00000008013fffff]
[    0.000442] On node 0 totalpages: 8360607
[    0.000443]   DMA zone: 59 pages used for memmap
[    0.000443]   DMA zone: 22 pages reserved
[    0.000444]   DMA zone: 3743 pages, LIFO batch:0
[    0.000444]   DMA32 zone: 16320 pages used for memmap
[    0.000444]   DMA32 zone: 1011712 pages, LIFO batch:63
[    0.000445]   Normal zone: 114768 pages used for memmap
[    0.000445]   Normal zone: 7345152 pages, LIFO batch:63
[    0.000551] On node 0, zone DMA: 1 pages in unavailable ranges
[    0.000567] On node 0, zone DMA: 352 pages in unavailable ranges
[    0.008833] On node 0, zone Normal: 27648 pages in unavailable ranges
[    0.008854] ACPI: Local APIC address 0xfee00000
[    0.008866] ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
[    0.008977] IOAPIC[0]: apic_id 24, version 17, address 0xfec00000, GSI 0-23
[    0.008979] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.008980] ACPI: IRQ9 used by override.
[    0.008981] Using ACPI (MADT) for SMP configuration information
[    0.008982] TSC deadline timer available
[    0.008983] smpboot: Allowing 24 CPUs, 0 hotplug CPUs
[    0.008988] [mem 0xf8000000-0xffffffff] available for PCI devices
[    0.008988] Booting paravirtualized kernel on Hyper-V
[    0.008989] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>2750000 ns
[    0.012252] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:24 nr_node_ids:1
[    0.013096] percpu: Embedded 56 pages/cpu s190040 r8192 d31144 u262144
[    0.013101] pcpu-alloc: s190040 r8192 d31144 u262144 alloc=1*2097152
[    0.013101] pcpu-alloc: [0] 00 01 02 03 04 05 06 07 [0] 08 09 10 11 12 13 14 15
[    0.013105] pcpu-alloc: [0] 16 17 18 19 20 21 22 23
[    0.013114] Hyper-V: PV spinlocks enabled
[    0.013115] PV qspinlock hash table entries: 256 (order: 0, 4096 bytes, linear)
[    0.013117] Built 1 zonelists, mobility grouping on.  Total pages: 8229438
[    0.013118] Kernel command line: initrd=\initrd.img panic=-1 nr_cpus=24 swiotlb=force pty.legacy_count=0
[    0.013555] printk: log_buf_len individual max cpu contribution: 4096 bytes
[    0.013556] printk: log_buf_len total cpu_extra contributions: 94208 bytes
[    0.013556] printk: log_buf_len min size: 131072 bytes
[    0.013631] printk: log_buf_len: 262144 bytes
[    0.013632] printk: early log buf free: 124464(94%)
[    0.016950] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes, linear)
[    0.018578] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)
[    0.018753] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.030722] Memory: 4085932K/33442428K available (16404K kernel code, 2544K rwdata, 9048K rodata, 1580K init, 2772K bss, 687124K reserved, 0K cma-reserved)
[    0.030755] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=24, Nodes=1
[    0.030760] ftrace: allocating 51665 entries in 202 pages
[    0.039042] ftrace: allocated 202 pages with 4 groups
[    0.039215] rcu: Hierarchical RCU implementation.
[    0.039216] rcu:     RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=24.
[    0.039217]  Rude variant of Tasks RCU enabled.
[    0.039217]  Tracing variant of Tasks RCU enabled.
[    0.039218] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.039218] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=24
[    0.041033] Using NULL legacy PIC
[    0.041034] NR_IRQS: 16640, nr_irqs: 616, preallocated irqs: 0
[    0.041231] random: crng done (trusting CPU's manufacturer)
[    0.041245] Console: colour dummy device 80x25
[    0.041249] printk: console [tty0] enabled
[    0.041260] ACPI: Core revision 20200925
[    0.041310] Failed to register legacy timer interrupt
[    0.041311] APIC: Switch to symmetric I/O mode setup
[    0.041997] x2apic: IRQ remapping doesn't support X2APIC mode
[    0.042674] Switched APIC routing to physical flat.
[    0.042686] Hyper-V: Using IPI hypercalls
[    0.042715] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x2df10b5eda2, max_idle_ns:<PHONE_NUMBER>85 ns
[    0.042717] Calibrating delay loop (skipped), value calculated using timer frequency.. 6374.39 BogoMIPS (lpj=31871970)
[    0.042718] pid_max: default: 32768 minimum: 301
[    0.042733] LSM: Security Framework initializing
[    0.042766] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
[    0.042791] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
[    0.042988] x86/cpu: User Mode Instruction Prevention (UMIP) activated
[    0.043001] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
[    0.043001] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0
[    0.043003] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[    0.043004] Spectre V2 : Mitigation: Enhanced IBRS
[    0.043004] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[    0.043005] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
[    0.043006] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp
[    0.043085] Freeing SMP alternatives memory: 56K
[    0.043806] smpboot: CPU0: 12th Gen Intel(R) Core(TM) i9-12900K (family: 0x6, model: 0x97, stepping: 0x2)
[    0.043852] Performance Events: unsupported p6 CPU model 151 no PMU driver, software events only.
[    0.043865] rcu: Hierarchical SRCU implementation.
[    0.044411] smp: Bringing up secondary CPUs ...
[    0.044446] x86: Booting SMP configuration:
[    0.044446] .... node  #0, CPUs:        #1  #2  #3  #4  #5  #6  #7  #8  #9 #10 #11 #12 #13 #14 #15 #16 #17 #18 #19 #20 #21 #22 #23
[    0.044737] smp: Brought up 1 node, 24 CPUs
[    0.044737] smpboot: Max logical packages: 1
[    0.044737] smpboot: Total of 24 processors activated (152985.45 BogoMIPS)
[    0.074046] node 0 deferred pages initialised in 30ms
[    0.074046] devtmpfs: initialized
[    0.074046] x86/mm: Memory block size: 128MB
[    0.074046] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>2750000 ns
[    0.074046] futex hash table entries: 8192 (order: 7, 524288 bytes, linear)
[    0.074046] NET: Registered protocol family 16
[    0.074046] thermal_sys: Registered thermal governor 'step_wise'
[    0.074046] cpuidle: using governor menu
[    0.074046] ACPI: bus type PCI registered
[    0.074046] PCI: Fatal: No config space access function found
[    0.074046] Kprobes globally optimized
[    0.074046] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.074046] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.074046] raid6: skip pq benchmark and using algorithm avx2x4
[    0.074046] raid6: using avx2x2 recovery algorithm
[    0.074046] ACPI: Added _OSI(Module Device)
[    0.074046] ACPI: Added _OSI(Processor Device)
[    0.074046] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.074046] ACPI: Added _OSI(Processor Aggregator Device)
[    0.074046] ACPI: Added _OSI(Linux-Dell-Video)
[    0.074046] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    0.074046] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[    0.074992] ACPI: 1 ACPI AML tables successfully acquired and loaded
[    0.075392] ACPI: Interpreter enabled
[    0.075394] ACPI: (supports S0 S5)
[    0.075394] ACPI: Using IOAPIC for interrupt routing
[    0.075398] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.075481] ACPI: Enabled 1 GPEs in block 00 to 0F
[    0.083242] iommu: Default domain type: Translated
[    0.083291] SCSI subsystem initialized
[    0.083293] ACPI: bus type USB registered
[    0.083297] usbcore: registered new interface driver usbfs
[    0.083299] usbcore: registered new interface driver hub
[    0.083304] usbcore: registered new device driver usb
[    0.083323] hv_vmbus: Vmbus version:5.2
[    0.083323] PCI: Using ACPI for IRQ routing
[    0.083323] PCI: System does not support PCI
[    0.083323] hv_vmbus: Unknown GUID: c376c1c3-d276-48d2-90a9-c04748072c60
[    0.083323] clocksource: Switched to clocksource tsc-early
[    0.083323] hv_vmbus: Unknown GUID: 6e382d18-3336-4f4b-acc4-2b7703d4df4a
[    0.083323] hv_vmbus: Unknown GUID: dde9cbc0-5060-4436-9448-ea1254a5d177
[    0.083323] hv_vmbus: Unknown GUID: 6e382d18-3336-4f4b-acc4-2b7703d4df4a
[    0.164244] VFS: Disk quotas dquot_6.6.0
[    0.164252] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.164263] FS-Cache: Loaded
[    0.164309] pnp: PnP ACPI init
[    0.164341] pnp 00:00: Plug and Play ACPI device, IDs PNP0b00 (active)
[    0.164380] pnp: PnP ACPI: found 1 devices
[    0.166364] NET: Registered protocol family 2
[    0.166628] IP idents hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.167480] tcp_listen_portaddr_hash hash table entries: 16384 (order: 6, 262144 bytes, linear)
[    0.167499] TCP established hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.167745] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear)
[    0.167918] TCP: Hash tables configured (established 262144 bind 65536)
[    0.167941] UDP hash table entries: 16384 (order: 7, 524288 bytes, linear)
[    0.167973] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes, linear)
[    0.168021] NET: Registered protocol family 1
[    0.168331] RPC: Registered named UNIX socket transport module.
[    0.168332] RPC: Registered udp transport module.
[    0.168332] RPC: Registered tcp transport module.
[    0.168333] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.168335] PCI: CLS 0 bytes, default 64
[    0.168364] Trying to unpack rootfs image as initramfs...
[    0.168504] Freeing initrd memory: 60K
[    0.168506] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    0.168507] software IO TLB: mapped [mem 0x00000000f4000000-0x00000000f8000000] (64MB)
[    0.168520] KVM: vmx: using Hyper-V Enlightened VMCS
[    0.170791] kvm: already loaded the other module
[    0.173151] Initialise system trusted keyrings
[    0.173207] workingset: timestamp_bits=46 max_order=23 bucket_order=0
[    0.173600] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.173695] NFS: Registering the id_resolver key type
[    0.173698] Key type id_resolver registered
[    0.173699] Key type id_legacy registered
[    0.173706] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.173707] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[    0.173707] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    0.173981] Key type cifs.idmap registered
[    0.174013] fuse: init (API version 7.32)
[    0.174094] SGI XFS with ACLs, security attributes, realtime, scrub, repair, quota, no debug enabled
[    0.174418] 9p: Installing v9fs 9p2000 file system support
[    0.174422] FS-Cache: Netfs '9p' registered for caching
[    0.174443] FS-Cache: Netfs 'ceph' registered for caching
[    0.174444] ceph: loaded (mds proto 32)
[    0.179310] NET: Registered protocol family 38
[    0.179311] xor: automatically using best checksumming function   avx
[    0.179312] Key type asymmetric registered
[    0.179313] Asymmetric key parser 'x509' registered
[    0.179317] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[    0.179828] hv_vmbus: registering driver hv_pci
[    0.180001] hv_pci 765d6d72-8772-490f-ad8d-952f91ac2a67: PCI VMBus probing: Using version 0x10003
[    0.180344] hv_pci 765d6d72-8772-490f-ad8d-952f91ac2a67: PCI host bridge to bus 8772:00
[    0.180471] pci 8772:00:00.0: [1414:008e] type 00 class 0x030200
[    0.182122] hv_pci d09c5ddd-11bf-4d9c-a85b-99d9d4fb67a3: PCI VMBus probing: Using version 0x10003
[    0.182448] hv_pci d09c5ddd-11bf-4d9c-a85b-99d9d4fb67a3: PCI host bridge to bus 11bf:00
[    0.182568] pci 11bf:00:00.0: [1414:008e] type 00 class 0x030200
[    0.184407] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    0.184707] Non-volatile memory driver v1.3
[    0.186489] brd: module loaded
[    0.186954] loop: module loaded
[    0.186978] hv_vmbus: registering driver hv_storvsc
[    0.187191] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[    0.187191] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld<EMAIL_ADDRESS>All Rights Reserved.
[    0.187198] tun: Universal TUN/TAP device driver, 1.6
[    0.187233] PPP generic driver version 2.4.2
[    0.187392] PPP BSD Compression module registered
[    0.187393] PPP Deflate Compression module registered
[    0.187395] PPP MPPE Compression module registered
[    0.187395] NET: Registered protocol family 24
[    0.187405] usbcore: registered new interface driver cdc_ether
[    0.187410] usbcore: registered new interface driver cdc_ncm
[    0.187410] hv_vmbus: registering driver hv_netvsc
[    0.187454] VFIO - User Level meta-driver version: 0.3
[    0.187528] usbcore: registered new interface driver cdc_acm
[    0.187528] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    0.187539] usbcore: registered new interface driver ch341
[    0.187540] usbserial: USB Serial support registered for ch341-uart
[    0.187541] usbcore: registered new interface driver cp210x
[    0.187543] usbserial: USB Serial support registered for cp210x
[    0.187544] usbcore: registered new interface driver ftdi_sio
[    0.187545] usbserial: USB Serial support registered for FTDI USB Serial Device
[    0.187616] vhci_hcd vhci_hcd.0: USB/IP Virtual Host Controller
[    0.187618] vhci_hcd vhci_hcd.0: new USB bus registered, assigned bus number 1
[    0.187621] vhci_hcd: created sysfs vhci_hcd.0
[    0.187717] scsi host0: storvsc_host_t
[    0.187720] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[    0.187721] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.187721] usb usb1: Product: USB/IP Virtual Host Controller
[    0.187722] usb usb1: Manufacturer: Linux <IP_ADDRESS>-microsoft-standard-WSL2 vhci_hcd
[    0.187722] usb usb1: SerialNumber: vhci_hcd.0
[    0.187783] hub 1-0:1.0: USB hub found
[    0.187797] hub 1-0:1.0: 8 ports detected
[    0.187930] vhci_hcd vhci_hcd.0: USB/IP Virtual Host Controller
[    0.187931] vhci_hcd vhci_hcd.0: new USB bus registered, assigned bus number 2
[    0.187971] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    0.188046] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10
[    0.188046] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.188047] usb usb2: Product: USB/IP Virtual Host Controller
[    0.188047] usb usb2: Manufacturer: Linux <IP_ADDRESS>-microsoft-standard-WSL2 vhci_hcd
[    0.188048] usb usb2: SerialNumber: vhci_hcd.0
[    0.188111] hub 2-0:1.0: USB hub found
[    0.188125] hub 2-0:1.0: 8 ports detected
[    0.188265] hv_vmbus: registering driver hyperv_keyboard
[    0.188337] rtc_cmos 00:00: RTC can wake from S4
[    0.188860] rtc_cmos 00:00: registered as rtc0
[    0.189071] rtc_cmos 00:00: setting system clock to 2022-03-31T11:40:31 UTC<PHONE_NUMBER>)
[    0.189075] rtc_cmos 00:00: alarms up to one month, 114 bytes nvram
[    0.189167] device-mapper: ioctl: 4.43.0-ioctl (2020-10-01) initialised<EMAIL_ADDRESS>[    0.189227] device-mapper: raid: Loading target version 1.15.1
[    0.189240] usbcore: registered new interface driver usbhid
[    0.189240] usbhid: USB HID core driver
[    0.189274] hv_utils: Registering HyperV Utility Driver
[    0.189275] hv_vmbus: registering driver hv_utils
[    0.189287] hv_vmbus: registering driver hv_balloon
[    0.189292] hv_vmbus: registering driver dxgkrnl
[    0.189299] hv_utils: cannot register PTP clock: 0
[    0.189299] (NULL device *): dxgk: dxg_drv_init  Version: 2216
[    0.189453] hv_utils: TimeSync IC version 4.0
[    0.189488] hv_balloon: Using Dynamic Memory protocol version 2.0
[    0.189770] (NULL device *): dxgk: mmio allocated 9ffe00000  200000000 9ffe00000 bffdfffff
[    0.189924] Free page reporting enabled
[    0.189924] hv_balloon: Cold memory discard hint enabled
[    0.190587] drop_monitor: Initializing network drop monitor service
[    0.190594] Mirror/redirect action on
[    0.191014] IPVS: Registered protocols (TCP, UDP)
[    0.191021] IPVS: Connection hash table configured (size=4096, memory=64Kbytes)
[    0.191152] IPVS: ipvs loaded.
[    0.191153] IPVS: [rr] scheduler registered.
[    0.191153] IPVS: [wrr] scheduler registered.
[    0.191153] IPVS: [sh] scheduler registered.
[    0.191173] ipip: IPv4 and MPLS over IPv4 tunneling driver
[    0.192476] ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
[    0.192918] Initializing XFRM netlink socket
[    0.192944] NET: Registered protocol family 10
[    0.193194] Segment Routing with IPv6
[    0.194221] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    0.194264] NET: Registered protocol family 17
[    0.194281] Bridge firewalling registered
[    0.194286] 8021q: 802.1Q VLAN Support v1.8
[    0.194441] sctp: Hash tables configured (bind 512/512)
[    0.194466] 9pnet: Installing 9P2000 support
[    0.194474] Key type dns_resolver registered
[    0.194477] Key type ceph registered
[    0.194680] libceph: loaded (mon/osd proto 15/24)
[    0.194723] NET: Registered protocol family 40
[    0.194724] hv_vmbus: registering driver hv_sock
[    0.194738] IPI shorthand broadcast: enabled
[    0.194743] sched_clock: Marking stable (193172612, 1537100)->(198529700, -3819988)
[    0.195014] registered taskstats version 1
[    0.195018] Loading compiled-in X.509 certificates
[    0.195233] Btrfs loaded, crc32c=crc32c-generic
[    0.206998] Freeing unused kernel image (initmem) memory: 1580K
[    0.262855] Write protecting the kernel read-only data: 28672k
[    0.263695] Freeing unused kernel image (text/rodata gap) memory: 2024K
[    0.264127] Freeing unused kernel image (rodata/data gap) memory: 1192K
[    0.264130] Run /init as init process
[    0.264130]   with arguments:
[    0.264130]     /init
[    0.264130]   with environment:
[    0.264131]     HOME=/
[    0.264131]     TERM=linux
[    0.374642] scsi 0:0:0:0: Direct-Access     Msft     Virtual Disk     1.0  PQ: 0 ANSI: 5
[    0.374914] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    0.375401] sd 0:0:0:0: [sda] 536870912 512-byte logical blocks: (275 GB/256 GiB)
[    0.375402] sd 0:0:0:0: [sda] 4096-byte physical blocks
[    0.375448] sd 0:0:0:0: [sda] Write Protect is off
[    0.375449] sd 0:0:0:0: [sda] Mode Sense: 0f 00 00 00
[    0.375543] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    0.381235] hv_pci 96ab15b2-c3f3-4173-b848-f7ae6247ecef: PCI VMBus probing: Using version 0x10003
[    0.382192] hv_pci 96ab15b2-c3f3-4173-b848-f7ae6247ecef: PCI host bridge to bus c3f3:00
[    0.382193] pci_bus c3f3:00: root bus resource [mem 0xc00000000-0xe00001fff window]
[    0.382541] pci c3f3:00:00.0: [1af4:105a] type 00 class 0x088000
[    0.383636] pci c3f3:00:00.0: reg 0x10: [mem 0xe00000000-0xe00000fff 64bit]
[    0.384552] pci c3f3:00:00.0: reg 0x18: [mem 0xe00001000-0xe00001fff 64bit]
[    0.385431] pci c3f3:00:00.0: reg 0x20: [mem 0xc00000000-0xdffffffff 64bit]
[    0.387356] pci c3f3:00:00.0: BAR 4: assigned [mem 0xc00000000-0xdffffffff 64bit]
[    0.388150] pci c3f3:00:00.0: BAR 0: assigned [mem 0xe00000000-0xe00000fff 64bit]
[    0.389090] pci c3f3:00:00.0: BAR 2: assigned [mem 0xe00001000-0xe00001fff 64bit]
[    0.396184] virtiofs virtio0: Cache len: 0x200000000 @ 0xc00000000
[    0.450035] memmap_init_zone_device initialised 2097152 pages in 10ms
[    0.472932] sd 0:0:0:0: [sda] Attached SCSI disk
[    0.613842] EXT4-fs (sda): mounted filesystem with ordered data mode. Opts: (null)
[    1.182741] Adding 8388608k swap on /swap/file.  Priority:-2 extents:4 across:8413184k
[    1.232749] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2df10b5eda2, max_idle_ns:<PHONE_NUMBER>85 ns
[    1.232975] clocksource: Switched to clocksource tsc
[    1.232982] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    2.742842] scsi 0:0:0:1: Direct-Access     Msft     Virtual Disk     1.0  PQ: 0 ANSI: 5
[    2.743022] sd 0:0:0:1: Attached scsi generic sg1 type 0
[    2.743132] scsi 0:0:0:2: Direct-Access     Msft     Virtual Disk     1.0  PQ: 0 ANSI: 5
[    2.743359] sd 0:0:0:2: Attached scsi generic sg2 type 0
[    2.743372] sd 0:0:0:1: [sdb] 695784 512-byte logical blocks: (356 MB/340 MiB)
[    2.743408] sd 0:0:0:1: [sdb] Write Protect is on
[    2.743409] sd 0:0:0:1: [sdb] Mode Sense: 0f 00 80 00
[    2.743517] sd 0:0:0:1: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    2.743565] sd 0:0:0:2: [sdc] 536870912 512-byte logical blocks: (275 GB/256 GiB)
[    2.743565] sd 0:0:0:2: [sdc] 4096-byte physical blocks
[    2.743604] sd 0:0:0:2: [sdc] Write Protect is off
[    2.743605] sd 0:0:0:2: [sdc] Mode Sense: 0f 00 00 00
[    2.743665] sd 0:0:0:2: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.744702] sd 0:0:0:1: [sdb] Attached SCSI disk
[    2.744762] sd 0:0:0:2: [sdc] Attached SCSI disk
[    2.750191] EXT4-fs (sdb): mounted filesystem without journal. Opts: (null)
[    2.775484] EXT4-fs (sdc): recovery complete
[    2.778963] EXT4-fs (sdc): mounted filesystem with ordered data mode. Opts: discard,errors=remount-ro,data=ordered
[    2.785568] hv_pci 6ae6a2f9-e762-4814-97c9-cebd5c348592: PCI VMBus probing: Using version 0x10003
[    2.813924] hv_pci 6ae6a2f9-e762-4814-97c9-cebd5c348592: PCI host bridge to bus e762:00
[    2.813926] pci_bus e762:00: root bus resource [mem 0xbffe00000-0xbffe02fff window]
[    2.814266] pci e762:00:00.0: [1af4:1049] type 00 class 0x010000
[    2.814607] pci e762:00:00.0: reg 0x10: [mem 0xbffe00000-0xbffe00fff 64bit]
[    2.814837] pci e762:00:00.0: reg 0x18: [mem 0xbffe01000-0xbffe01fff 64bit]
[    2.815067] pci e762:00:00.0: reg 0x20: [mem 0xbffe02000-0xbffe02fff 64bit]
[    2.816393] pci e762:00:00.0: BAR 0: assigned [mem 0xbffe00000-0xbffe00fff 64bit]
[    2.816559] pci e762:00:00.0: BAR 2: assigned [mem 0xbffe01000-0xbffe01fff 64bit]
[    2.816721] pci e762:00:00.0: BAR 4: assigned [mem 0xbffe02000-0xbffe02fff 64bit]
[    2.835499] FS-Cache: Duplicate cookie detected
[    2.835501] FS-Cache: O-cookie c=0000000010cbdb90 [p=00000000aad763ec fl=222 nc=0 na=1]
[    2.835501] FS-Cache: O-cookie d=0000000099f01593 n=0000000025d88a1d
[    2.835501] FS-Cache: O-key=[10] '34323934393337353736'
[    2.835504] FS-Cache: N-cookie c=000000007202c3e0 [p=00000000aad763ec fl=2 nc=0 na=1]
[    2.835505] FS-Cache: N-cookie d=0000000099f01593 n=00000000eb712e91
[    2.835505] FS-Cache: N-key=[10] '34323934393337353736'
[    2.975386] hv_pci a13ad158-1c39-4466-b3eb-2e508faafc49: PCI VMBus probing: Using version 0x10003
[    2.975990] 9pnet_virtio: no channels available for device drvfs
[    2.975992] WARNING: mount: waiting for virtio device...
[    3.004199] hv_pci a13ad158-1c39-4466-b3eb-2e508faafc49: PCI host bridge to bus 1c39:00
[    3.004200] pci_bus 1c39:00: root bus resource [mem 0xbffe04000-0xbffe06fff window]
[    3.004559] pci 1c39:00:00.0: [1af4:1049] type 00 class 0x010000
[    3.004893] pci 1c39:00:00.0: reg 0x10: [mem 0xbffe04000-0xbffe04fff 64bit]
[    3.005121] pci 1c39:00:00.0: reg 0x18: [mem 0xbffe05000-0xbffe05fff 64bit]
[    3.005384] pci 1c39:00:00.0: reg 0x20: [mem 0xbffe06000-0xbffe06fff 64bit]
[    3.006712] pci 1c39:00:00.0: BAR 0: assigned [mem 0xbffe04000-0xbffe04fff 64bit]
[    3.006933] pci 1c39:00:00.0: BAR 2: assigned [mem 0xbffe05000-0xbffe05fff 64bit]
[    3.007128] pci 1c39:00:00.0: BAR 4: assigned [mem 0xbffe06000-0xbffe06fff 64bit]
[    3.078653] hv_pci 6f2c37da-9c66-40dc-addd-726227ea6694: PCI VMBus probing: Using version 0x10003
[    3.081345] init: (1) ERROR: MountPlan9WithRetry:285: mount drvfs on /mnt/d (cache=mmap,noatime,msize=262144,trans=virtio,aname=drvfs;path=D:;uid=0;gid=0;symlinkroot=/mnt/
[    3.081347] ) failed: 22
[    3.107145] hv_pci 6f2c37da-9c66-40dc-addd-726227ea6694: PCI host bridge to bus 9c66:00
[    3.107147] pci_bus 9c66:00: root bus resource [mem 0xbffe08000-0xbffe0afff window]
[    3.107483] pci 9c66:00:00.0: [1af4:1049] type 00 class 0x010000
[    3.107848] pci 9c66:00:00.0: reg 0x10: [mem 0xbffe08000-0xbffe08fff 64bit]
[    3.108084] pci 9c66:00:00.0: reg 0x18: [mem 0xbffe09000-0xbffe09fff 64bit]
[    3.108333] pci 9c66:00:00.0: reg 0x20: [mem 0xbffe0a000-0xbffe0afff 64bit]
[    3.109617] pci 9c66:00:00.0: BAR 0: assigned [mem 0xbffe08000-0xbffe08fff 64bit]
[    3.109780] pci 9c66:00:00.0: BAR 2: assigned [mem 0xbffe09000-0xbffe09fff 64bit]
[    3.109946] pci 9c66:00:00.0: BAR 4: assigned [mem 0xbffe0a000-0xbffe0afff 64bit]
[    3.120562] FS-Cache: Duplicate cookie detected
[    3.120564] FS-Cache: O-cookie c=0000000093109fb4 [p=00000000aad763ec fl=222 nc=0 na=1]
[    3.120564] FS-Cache: O-cookie d=0000000099f01593 n=00000000d0b5b05b
[    3.120565] FS-Cache: O-key=[10] '34323934393337363034'
[    3.120568] FS-Cache: N-cookie c=00000000fcc67271 [p=00000000aad763ec fl=2 nc=0 na=1]
[    3.120568] FS-Cache: N-cookie d=0000000099f01593 n=000000008a7fbad6
[    3.120568] FS-Cache: N-key=[10] '34323934393337363034'
[    3.244304] hv_pci f92b4629-64a0-4ca6-9bf4-1321836da137: PCI VMBus probing: Using version 0x10003
[    3.245182] 9pnet_virtio: no channels available for device drvfs
[    3.245184] WARNING: mount: waiting for virtio device...
[    3.272905] hv_pci f92b4629-64a0-4ca6-9bf4-1321836da137: PCI host bridge to bus 64a0:00
[    3.272906] pci_bus 64a0:00: root bus resource [mem 0xbffe0c000-0xbffe0efff window]
[    3.273266] pci 64a0:00:00.0: [1af4:1049] type 00 class 0x010000
[    3.273680] pci 64a0:00:00.0: reg 0x10: [mem 0xbffe0c000-0xbffe0cfff 64bit]
[    3.273939] pci 64a0:00:00.0: reg 0x18: [mem 0xbffe0d000-0xbffe0dfff 64bit]
[    3.274172] pci 64a0:00:00.0: reg 0x20: [mem 0xbffe0e000-0xbffe0efff 64bit]
[    3.275491] pci 64a0:00:00.0: BAR 0: assigned [mem 0xbffe0c000-0xbffe0cfff 64bit]
[    3.275691] pci 64a0:00:00.0: BAR 2: assigned [mem 0xbffe0d000-0xbffe0dfff 64bit]
[    3.275874] pci 64a0:00:00.0: BAR 4: assigned [mem 0xbffe0e000-0xbffe0efff 64bit]
[    3.347982] hv_pci 46bb18e8-5b1d-4a0c-a58a-5111aa4d7a1e: PCI VMBus probing: Using version 0x10003
[    3.350399] init: (1) ERROR: MountPlan9WithRetry:285: mount drvfs on /mnt/d (cache=mmap,noatime,msize=262144,trans=virtio,aname=drvfs;path=D:;uid=1000;gid=1000;symlinkroot=/mnt/
[    3.350400] ) failed: 22
[    3.376512] hv_pci 46bb18e8-5b1d-4a0c-a58a-5111aa4d7a1e: PCI host bridge to bus 5b1d:00
[    3.376513] pci_bus 5b1d:00: root bus resource [mem 0xbffe10000-0xbffe12fff window]
[    3.376878] pci 5b1d:00:00.0: [1af4:1049] type 00 class 0x010000
[    3.377261] pci 5b1d:00:00.0: reg 0x10: [mem 0xbffe10000-0xbffe10fff 64bit]
[    3.377491] pci 5b1d:00:00.0: reg 0x18: [mem 0xbffe11000-0xbffe11fff 64bit]
[    3.377717] pci 5b1d:00:00.0: reg 0x20: [mem 0xbffe12000-0xbffe12fff 64bit]
[    3.379043] pci 5b1d:00:00.0: BAR 0: assigned [mem 0xbffe10000-0xbffe10fff 64bit]
[    3.379222] pci 5b1d:00:00.0: BAR 2: assigned [mem 0xbffe11000-0xbffe11fff 64bit]
[    3.379386] pci 5b1d:00:00.0: BAR 4: assigned [mem 0xbffe12000-0xbffe12fff 64bit]
[    3.616123] scsi 0:0:0:3: Direct-Access     Msft     Virtual Disk     1.0  PQ: 0 ANSI: 5
[    3.616323] sd 0:0:0:3: Attached scsi generic sg3 type 0
[    3.616621] sd 0:0:0:3: [sdd] 536870912 512-byte logical blocks: (275 GB/256 GiB)
[    3.616622] sd 0:0:0:3: [sdd] 4096-byte physical blocks
[    3.616658] sd 0:0:0:3: [sdd] Write Protect is off
[    3.616659] sd 0:0:0:3: [sdd] Mode Sense: 0f 00 00 00
[    3.616741] sd 0:0:0:3: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.617838] sd 0:0:0:3: [sdd] Attached SCSI disk
[    3.640945] EXT4-fs (sdd): recovery complete
[    3.642887] EXT4-fs (sdd): mounted filesystem with ordered data mode. Opts: discard,errors=remount-ro,data=ordered
[    3.645116] FS-Cache: Duplicate cookie detected
[    3.645118] FS-Cache: O-cookie c=00000000e4d0ccca [p=00000000aad763ec fl=222 nc=0 na=1]
[    3.645119] FS-Cache: O-cookie d=0000000099f01593 n=00000000c7bb2098
[    3.645119] FS-Cache: O-key=[10] '34323934393337363537'
[    3.645122] FS-Cache: N-cookie c=00000000ddd6cd04 [p=00000000aad763ec fl=2 nc=0 na=1]
[    3.645122] FS-Cache: N-cookie d=0000000099f01593 n=00000000950f6465
[    3.645123] FS-Cache: N-key=[10] '34323934393337363537'
[    3.724446] hv_pci 482f4381-1c15-4681-89e2-49106d6adb33: PCI VMBus probing: Using version 0x10003
[    3.725616] 9pnet_virtio: no channels available for device drvfs
[    3.725619] WARNING: mount: waiting for virtio device...
[    3.753006] hv_pci 482f4381-1c15-4681-89e2-49106d6adb33: PCI host bridge to bus 1c15:00
[    3.753007] pci_bus 1c15:00: root bus resource [mem 0xbffe14000-0xbffe16fff window]
[    3.753350] pci 1c15:00:00.0: [1af4:1049] type 00 class 0x010000
[    3.753723] pci 1c15:00:00.0: reg 0x10: [mem 0xbffe14000-0xbffe14fff 64bit]
[    3.753963] pci 1c15:00:00.0: reg 0x18: [mem 0xbffe15000-0xbffe15fff 64bit]
[    3.754189] pci 1c15:00:00.0: reg 0x20: [mem 0xbffe16000-0xbffe16fff 64bit]
[    3.755497] pci 1c15:00:00.0: BAR 0: assigned [mem 0xbffe14000-0xbffe14fff 64bit]
[    3.755663] pci 1c15:00:00.0: BAR 2: assigned [mem 0xbffe15000-0xbffe15fff 64bit]
[    3.755827] pci 1c15:00:00.0: BAR 4: assigned [mem 0xbffe16000-0xbffe16fff 64bit]
[    3.828403] hv_pci 5c05e87b-9370-44e9-bd1a-d28e99e78b66: PCI VMBus probing: Using version 0x10003
[    3.831613] init: (1) ERROR: MountPlan9WithRetry:285: mount drvfs on /mnt/d (cache=mmap,noatime,msize=262144,trans=virtio,aname=drvfs;path=D:;uid=0;gid=0;symlinkroot=/mnt/
[    3.831614] ) failed: 22
[    3.857196] hv_pci 5c05e87b-9370-44e9-bd1a-d28e99e78b66: PCI host bridge to bus 9370:00
[    3.857197] pci_bus 9370:00: root bus resource [mem 0xbffe18000-0xbffe1afff window]
[    3.857526] pci 9370:00:00.0: [1af4:1049] type 00 class 0x010000
[    3.857856] pci 9370:00:00.0: reg 0x10: [mem 0xbffe18000-0xbffe18fff 64bit]
[    3.858079] pci 9370:00:00.0: reg 0x18: [mem 0xbffe19000-0xbffe19fff 64bit]
[    3.858303] pci 9370:00:00.0: reg 0x20: [mem 0xbffe1a000-0xbffe1afff 64bit]
[    3.859615] pci 9370:00:00.0: BAR 0: assigned [mem 0xbffe18000-0xbffe18fff 64bit]
[    3.859796] pci 9370:00:00.0: BAR 2: assigned [mem 0xbffe19000-0xbffe19fff 64bit]
[    3.859961] pci 9370:00:00.0: BAR 4: assigned [mem 0xbffe1a000-0xbffe1afff 64bit]
[    3.869755] FS-Cache: Duplicate cookie detected
[    3.869757] FS-Cache: O-cookie c=00000000284bd572 [p=00000000aad763ec fl=222 nc=0 na=1]
[    3.869757] FS-Cache: O-cookie d=0000000099f01593 n=00000000d437ad3f
[    3.869758] FS-Cache: O-key=[10] '34323934393337363739'
[    3.869761] FS-Cache: N-cookie c=000000004c10032f [p=00000000aad763ec fl=2 nc=0 na=1]
[    3.869761] FS-Cache: N-cookie d=0000000099f01593 n=000000002cf7042e
[    3.869761] FS-Cache: N-key=[10] '34323934393337363739'
[    3.869893] init: (1) ERROR: ConfigApplyWindowsLibPath:2474: open /etc/ld.so.conf.d/ld.wsl.conf
[    3.869894]  failed 2
[    3.877975] hv_pci 9c10f538-18e0-4c8e-aa47-e085d738a0a8: PCI VMBus probing: Using version 0x10003
[    3.878656] 9pnet_virtio: no channels available for device drvfs
[    3.878659] WARNING: mount: waiting for virtio device...
[    3.906761] hv_pci 9c10f538-18e0-4c8e-aa47-e085d738a0a8: PCI host bridge to bus 18e0:00
[    3.906763] pci_bus 18e0:00: root bus resource [mem 0xbffe1c000-0xbffe1efff window]
[    3.907416] pci 18e0:00:00.0: [1af4:1049] type 00 class 0x010000
[    3.907771] pci 18e0:00:00.0: reg 0x10: [mem 0xbffe1c000-0xbffe1cfff 64bit]
[    3.908003] pci 18e0:00:00.0: reg 0x18: [mem 0xbffe1d000-0xbffe1dfff 64bit]
[    3.908237] pci 18e0:00:00.0: reg 0x20: [mem 0xbffe1e000-0xbffe1efff 64bit]
[    3.909585] pci 18e0:00:00.0: BAR 0: assigned [mem 0xbffe1c000-0xbffe1cfff 64bit]
[    3.909770] pci 18e0:00:00.0: BAR 2: assigned [mem 0xbffe1d000-0xbffe1dfff 64bit]
[    3.909937] pci 18e0:00:00.0: BAR 4: assigned [mem 0xbffe1e000-0xbffe1efff 64bit]
[    3.982080] hv_pci 56189f56-1ad9-4063-affb-d078a3d16ad8: PCI VMBus probing: Using version 0x10003
[    3.985416] init: (1) ERROR: MountPlan9WithRetry:285: mount drvfs on /mnt/host/d (cache=mmap,noatime,msize=262144,trans=virtio,aname=drvfs;path=D:;uid=0;gid=0;metadata;symlinkroot=/mnt/host/
[    3.985418] ) failed: 22
[    3.992810] WARNING: /usr/share/zoneinfo/Asia/Shanghai not found. Is the tzdata package installed?
[    4.010614] hv_pci 56189f56-1ad9-4063-affb-d078a3d16ad8: PCI host bridge to bus 1ad9:00
[    4.010616] pci_bus 1ad9:00: root bus resource [mem 0xbffe20000-0xbffe22fff window]
[    4.010943] pci 1ad9:00:00.0: [1af4:1049] type 00 class 0x010000
[    4.011322] pci 1ad9:00:00.0: reg 0x10: [mem 0xbffe20000-0xbffe20fff 64bit]
[    4.011601] pci 1ad9:00:00.0: reg 0x18: [mem 0xbffe21000-0xbffe21fff 64bit]
[    4.011835] pci 1ad9:00:00.0: reg 0x20: [mem 0xbffe22000-0xbffe22fff 64bit]
[    4.013173] pci 1ad9:00:00.0: BAR 0: assigned [mem 0xbffe20000-0xbffe20fff 64bit]
[    4.013446] pci 1ad9:00:00.0: BAR 2: assigned [mem 0xbffe21000-0xbffe21fff 64bit]
[    4.013661] pci 1ad9:00:00.0: BAR 4: assigned [mem 0xbffe22000-0xbffe22fff 64bit]
[    8.817017] scsi 0:0:0:4: Direct-Access     NVMe     SAMSUNG MZ1L21T9 102Q PQ: 0 ANSI: 6
[    8.817250] sd 0:0:0:4: Attached scsi generic sg4 type 0
[    8.819098] sd 0:0:0:4: [sde]<PHONE_NUMBER> 512-byte logical blocks: (1.92 TB/1.75 TiB)
[    8.819099] sd 0:0:0:4: [sde] 262144-byte physical blocks
[    8.823956] sd 0:0:0:4: [sde] Write Protect is off
[    8.823957] sd 0:0:0:4: [sde] Mode Sense: 0f 00 10 00
[    8.831939] sd 0:0:0:4: [sde] Write cache: disabled, read cache: enabled, supports DPO and FUA
[    8.831941] sd 0:0:0:4: [sde] Optimal transfer size 131072 bytes not a multiple of physical block size (262144 bytes)
[    8.844960]  sde: sde1
[    8.845190] EXT4-fs (sde): VFS: Can't find ext4 filesystem
[    8.845206] ERROR: Mount:2528: mount(/dev/sde, /share/PHYSICALDRIVE1, ext4, 0x0, ) failed
[    8.845207] 22
[    8.856940] sd 0:0:0:4: [sde] Attached SCSI disk
[   16.023963] EXT4-fs (sdd): mounted filesystem with ordered data mode. Opts: discard,errors=remount-ro,data=ordered
[   16.026593] FS-Cache: Duplicate cookie detected
[   16.026595] FS-Cache: O-cookie c=00000000f222f85f [p=00000000aad763ec fl=222 nc=0 na=1]
[   16.026595] FS-Cache: O-cookie d=0000000099f01593 n=000000002205160b
[   16.026595] FS-Cache: O-key=[10] '34323934393338383935'
[   16.026598] FS-Cache: N-cookie c=000000004cc5ec86 [p=00000000aad763ec fl=2 nc=0 na=1]
[   16.026599] FS-Cache: N-cookie d=0000000099f01593 n=00000000adc11ae7
[   16.026599] FS-Cache: N-key=[10] '34323934393338383935'
[   16.102400] FS-Cache: Duplicate cookie detected
[   16.102402] FS-Cache: O-cookie c=000000003f43e640 [p=00000000aad763ec fl=222 nc=0 na=1]
[   16.102403] FS-Cache: O-cookie d=0000000099f01593 n=00000000f453d57b
[   16.102403] FS-Cache: O-key=[10] '34323934393338393032'
[   16.102406] FS-Cache: N-cookie c=00000000b7add828 [p=00000000aad763ec fl=2 nc=0 na=1]
[   16.102406] FS-Cache: N-cookie d=0000000099f01593 n=0000000001f743f2
[   16.102406] FS-Cache: N-key=[10] '34323934393338393032'
[   16.107327] FS-Cache: Duplicate cookie detected
[   16.107329] FS-Cache: O-cookie c=0000000052439707 [p=00000000aad763ec fl=222 nc=0 na=1]
[   16.107329] FS-Cache: O-cookie d=0000000099f01593 n=00000000f12859f9
[   16.107330] FS-Cache: O-key=[10] '34323934393338393033'
[   16.107333] FS-Cache: N-cookie c=000000003d7643e4 [p=00000000aad763ec fl=2 nc=0 na=1]
[   16.107333] FS-Cache: N-cookie d=0000000099f01593 n=0000000047a4efed
[   16.107333] FS-Cache: N-key=[10] '34323934393338393033'
[   16.107473] init: (1) ERROR: ConfigApplyWindowsLibPath:2474: open /etc/ld.so.conf.d/ld.wsl.conf
[   16.107474]  failed 2
[   16.114245] FS-Cache: Duplicate cookie detected
[   16.114247] FS-Cache: O-cookie c=000000003d7643e4 [p=00000000aad763ec fl=222 nc=0 na=1]
[   16.114247] FS-Cache: O-cookie d=0000000099f01593 n=0000000027868243
[   16.114248] FS-Cache: O-key=[10] '34323934393338393034'
[   16.114251] FS-Cache: N-cookie c=00000000478f889a [p=00000000aad763ec fl=2 nc=0 na=1]
[   16.114251] FS-Cache: N-cookie d=0000000099f01593 n=0000000056b6d82f
[   16.114251] FS-Cache: N-key=[10] '34323934393338393034'
[   16.123159] WARNING: /usr/share/zoneinfo/Asia/Shanghai not found. Is the tzdata package installed?
[   16.170797] EXT4-fs (sdd): mounted filesystem with ordered data mode. Opts: discard,errors=remount-ro,data=ordered
[   16.234212] FS-Cache: Duplicate cookie detected
[   16.234214] FS-Cache: O-cookie c=000000005f183200 [p=00000000aad763ec fl=222 nc=0 na=1]
[   16.234215] FS-Cache: O-cookie d=0000000099f01593 n=00000000e5439aae
[   16.234215] FS-Cache: O-key=[10] '34323934393338393136'
[   16.234218] FS-Cache: N-cookie c=0000000054108e67 [p=00000000aad763ec fl=2 nc=0 na=1]
[   16.234218] FS-Cache: N-cookie d=0000000099f01593 n=00000000e872777d
[   16.234219] FS-Cache: N-key=[10] '34323934393338393136'
[   16.237802] FS-Cache: Duplicate cookie detected
[   16.237809] FS-Cache: O-cookie c=000000005f183200 [p=00000000aad763ec fl=222 nc=0 na=1]
[   16.237809] FS-Cache: O-cookie d=0000000099f01593 n=00000000e5439aae
[   16.237810] FS-Cache: O-key=[10] '34323934393338393136'
[   16.237813] FS-Cache: N-cookie c=00000000b7add828 [p=00000000aad763ec fl=2 nc=0 na=1]
[   16.237813] FS-Cache: N-cookie d=0000000099f01593 n=00000000c9be1363
[   16.237813] FS-Cache: N-key=[10] '34323934393338393136'
[   16.238481] FS-Cache: Duplicate cookie detected
[   16.238482] FS-Cache: O-cookie c=000000005f183200 [p=00000000aad763ec fl=222 nc=0 na=1]
[   16.238483] FS-Cache: O-cookie d=0000000099f01593 n=00000000e5439aae
[   16.238483] FS-Cache: O-key=[10] '34323934393338393136'
[   16.238486] FS-Cache: N-cookie c=00000000b7add828 [p=00000000aad763ec fl=2 nc=0 na=1]
[   16.238486] FS-Cache: N-cookie d=0000000099f01593 n=000000003d9320d5
[   16.238487] FS-Cache: N-key=[10] '34323934393338393136'
[   16.238581] init: (1) ERROR: ConfigApplyWindowsLibPath:2474: open /etc/ld.so.conf.d/ld.wsl.conf
[   16.238582]  failed 2
[   16.244796] FS-Cache: Duplicate cookie detected
[   16.244798] FS-Cache: O-cookie c=00000000b7add828 [p=00000000aad763ec fl=222 nc=0 na=1]
[   16.244799] FS-Cache: O-cookie d=0000000099f01593 n=00000000628237d7
[   16.244799] FS-Cache: O-key=[10] '34323934393338393137'
[   16.244807] FS-Cache: N-cookie c=00000000bc44e5d2 [p=00000000aad763ec fl=2 nc=0 na=1]
[   16.244807] FS-Cache: N-cookie d=0000000099f01593 n=0000000014d9cc3d
[   16.244808] FS-Cache: N-key=[10] '34323934393338393137'
[   16.262881] WARNING: /usr/share/zoneinfo/Asia/Shanghai not found. Is the tzdata package installed?
[   16.325358] scsi 0:0:0:5: Direct-Access     Msft     Virtual Disk     1.0  PQ: 0 ANSI: 5
[   16.325648] sd 0:0:0:5: Attached scsi generic sg5 type 0
[   16.326053] sd 0:0:0:5: [sdf] 536870912 512-byte logical blocks: (275 GB/256 GiB)
[   16.326054] sd 0:0:0:5: [sdf] 4096-byte physical blocks
[   16.326129] sd 0:0:0:5: [sdf] Write Protect is off
[   16.326131] sd 0:0:0:5: [sdf] Mode Sense: 0f 00 00 00
[   16.326237] sd 0:0:0:5: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   16.327829] sd 0:0:0:5: [sdf] Attached SCSI disk
[   16.475608] EXT4-fs (sdf): recovery complete
[   16.478498] EXT4-fs (sdf): mounted filesystem with ordered data mode. Opts: discard,errors=remount-ro,data=ordered
[   16.480958] FS-Cache: Duplicate cookie detected
[   16.480959] FS-Cache: O-cookie c=000000004d6f011e [p=00000000aad763ec fl=222 nc=0 na=1]
[   16.480960] FS-Cache: O-cookie d=0000000099f01593 n=00000000679193a5
[   16.480960] FS-Cache: O-key=[10] '34323934393338393430'
[   16.480963] FS-Cache: N-cookie c=000000007fd8a848 [p=00000000aad763ec fl=2 nc=0 na=1]
[   16.480963] FS-Cache: N-cookie d=0000000099f01593 n=00000000eb91c9bc
[   16.480963] FS-Cache: N-key=[10] '34323934393338393430'
[   16.556506] hv_pci 3c584ab5-a4c4-45e0-911e-70126f26dce6: PCI VMBus probing: Using version 0x10003
[   16.557332] 9pnet_virtio: no channels available for device drvfs
[   16.557335] WARNING: mount: waiting for virtio device...
[   16.584909] hv_pci 3c584ab5-a4c4-45e0-911e-70126f26dce6: PCI host bridge to bus a4c4:00
[   16.584911] pci_bus a4c4:00: root bus resource [mem 0xbffe24000-0xbffe26fff window]
[   16.585255] pci a4c4:00:00.0: [1af4:1049] type 00 class 0x010000
[   16.585605] pci a4c4:00:00.0: reg 0x10: [mem 0xbffe24000-0xbffe24fff 64bit]
[   16.585856] pci a4c4:00:00.0: reg 0x18: [mem 0xbffe25000-0xbffe25fff 64bit]
[   16.586109] pci a4c4:00:00.0: reg 0x20: [mem 0xbffe26000-0xbffe26fff 64bit]
[   16.587430] pci a4c4:00:00.0: BAR 0: assigned [mem 0xbffe24000-0xbffe24fff 64bit]
[   16.587599] pci a4c4:00:00.0: BAR 2: assigned [mem 0xbffe25000-0xbffe25fff 64bit]
[   16.587766] pci a4c4:00:00.0: BAR 4: assigned [mem 0xbffe26000-0xbffe26fff 64bit]
[   16.660126] hv_pci ae1e48cb-de75-46d7-97c6-682b7e9a7812: PCI VMBus probing: Using version 0x10003
[   16.688986] hv_pci ae1e48cb-de75-46d7-97c6-682b7e9a7812: PCI host bridge to bus de75:00
[   16.688987] pci_bus de75:00: root bus resource [mem 0xbffe28000-0xbffe2afff window]
[   16.689320] pci de75:00:00.0: [1af4:1049] type 00 class 0x010000
[   16.689729] pci de75:00:00.0: reg 0x10: [mem 0xbffe28000-0xbffe28fff 64bit]
[   16.689978] pci de75:00:00.0: reg 0x18: [mem 0xbffe29000-0xbffe29fff 64bit]
[   16.690230] pci de75:00:00.0: reg 0x20: [mem 0xbffe2a000-0xbffe2afff 64bit]
[   16.691609] pci de75:00:00.0: BAR 0: assigned [mem 0xbffe28000-0xbffe28fff 64bit]
[   16.691798] pci de75:00:00.0: BAR 2: assigned [mem 0xbffe29000-0xbffe29fff 64bit]
[   16.691969] pci de75:00:00.0: BAR 4: assigned [mem 0xbffe2a000-0xbffe2afff 64bit]
[   16.705362] FS-Cache: Duplicate cookie detected
[   16.705364] FS-Cache: O-cookie c=0000000054108e67 [p=00000000aad763ec fl=222 nc=0 na=1]
[   16.705365] FS-Cache: O-cookie d=0000000099f01593 n=00000000b5102ee3
[   16.705366] FS-Cache: O-key=[10] '34323934393338393633'
[   16.705370] FS-Cache: N-cookie c=00000000d05866b5 [p=00000000aad763ec fl=2 nc=0 na=1]
[   16.705370] FS-Cache: N-cookie d=0000000099f01593 n=0000000068600e55
[   16.705371] FS-Cache: N-key=[10] '34323934393338393633'
[   16.705544] init: (1) ERROR: ConfigApplyWindowsLibPath:2474: open /etc/ld.so.conf.d/ld.wsl.conf
[   16.705546]  failed 2
[   16.706219] init: (2) ERROR: UtilCreateProcessAndWait:653: /bin/mount failed with 2
[   16.706278] init: (1) ERROR: UtilCreateProcessAndWait:673: /bin/mount failed with status 0x
[   16.706279] ff00
[   16.706283] init: (1) ERROR: ConfigMountFsTab:2529: Processing fstab with mount -a failed.
[   16.710645] hv_pci 1e197e17-3d12-4900-a869-da55fa05be87: PCI VMBus probing: Using version 0x10003
[   16.711415] FS-Cache: Duplicate cookie detected
[   16.711416] FS-Cache: O-cookie c=0000000054108e67 [p=00000000aad763ec fl=222 nc=0 na=1]
[   16.711416] FS-Cache: O-cookie d=0000000099f01593 n=00000000b5102ee3
[   16.711417] FS-Cache: O-key=[10] '34323934393338393633'
[   16.711420] FS-Cache: N-cookie c=00000000d05866b5 [p=00000000aad763ec fl=2 nc=0 na=1]
[   16.711420] FS-Cache: N-cookie d=0000000099f01593 n=00000000fa908e55
[   16.711420] FS-Cache: N-key=[10] '34323934393338393633'
[   16.711733] 9pnet_virtio: no channels available for device drvfs
[   16.711735] WARNING: mount: waiting for virtio device...
[   16.739160] hv_pci 1e197e17-3d12-4900-a869-da55fa05be87: PCI host bridge to bus 3d12:00
[   16.739162] pci_bus 3d12:00: root bus resource [mem 0xbffe2c000-0xbffe2efff window]
[   16.739511] pci 3d12:00:00.0: [1af4:1049] type 00 class 0x010000
[   16.739876] pci 3d12:00:00.0: reg 0x10: [mem 0xbffe2c000-0xbffe2cfff 64bit]
[   16.740612] pci 3d12:00:00.0: reg 0x18: [mem 0xbffe2d000-0xbffe2dfff 64bit]
[   16.741367] pci 3d12:00:00.0: reg 0x20: [mem 0xbffe2e000-0xbffe2efff 64bit]
[   16.744296] pci 3d12:00:00.0: BAR 0: assigned [mem 0xbffe2c000-0xbffe2cfff 64bit]
[   16.744493] pci 3d12:00:00.0: BAR 2: assigned [mem 0xbffe2d000-0xbffe2dfff 64bit]
[   16.744669] pci 3d12:00:00.0: BAR 4: assigned [mem 0xbffe2e000-0xbffe2efff 64bit]
[   16.816775] hv_pci 5a76dbf1-1315-403e-91ac-88591e5dad39: PCI VMBus probing: Using version 0x10003
[   16.822834] WARNING: /usr/share/zoneinfo/Asia/Shanghai not found. Is the tzdata package installed?
[   16.845507] hv_pci 5a76dbf1-1315-403e-91ac-88591e5dad39: PCI host bridge to bus 1315:00
[   16.845509] pci_bus 1315:00: root bus resource [mem 0xbffe30000-0xbffe32fff window]
[   16.845888] pci 1315:00:00.0: [1af4:1049] type 00 class 0x010000
[   16.846232] pci 1315:00:00.0: reg 0x10: [mem 0xbffe30000-0xbffe30fff 64bit]
[   16.846464] pci 1315:00:00.0: reg 0x18: [mem 0xbffe31000-0xbffe31fff 64bit]
[   16.846776] pci 1315:00:00.0: reg 0x20: [mem 0xbffe32000-0xbffe32fff 64bit]
[   16.850078] pci 1315:00:00.0: BAR 0: assigned [mem 0xbffe30000-0xbffe30fff 64bit]
[   16.850263] pci 1315:00:00.0: BAR 2: assigned [mem 0xbffe31000-0xbffe31fff 64bit]
[   16.850443] pci 1315:00:00.0: BAR 4: assigned [mem 0xbffe32000-0xbffe32fff 64bit]
[   16.866165] init: (8) ERROR: CreateProcessEntryCommon:440: getpwuid(0) failed 2
[   16.866168] init: (8) ERROR: CreateProcessEntryCommon:443: getpwuid(0) failed 2
[   17.029027] ISO 9660 Extensions: Microsoft Joliet Level 3
[   17.029099] ISO 9660 Extensions: RRIP_1991A
[   17.107564] ISO 9660 Extensions: Microsoft Joliet Level 3
[   17.107712] ISO 9660 Extensions: RRIP_1991A
[   19.544338] cgroup: cgroup: disabling cgroup2 socket matching due to net_prio or net_cls activation
[   19.727987] IPv6: ADDRCONF(NETDEV_CHANGE): services1: link becomes ready
[   19.728029] IPv6: ADDRCONF(NETDEV_CHANGE): services0: link becomes ready
[   20.145897] cgroup: runc (1265) created nested cgroup for controller "memory" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
[   20.145898] cgroup: "memory" requires setting use_hierarchy to 1 on the root
[   45.843280] IPv6: ADDRCONF(NETDEV_CHANGE): veth1d74c0a2: link becomes ready
[   45.843582] cni0: port 1(veth1d74c0a2) entered blocking state
[   45.843583] cni0: port 1(veth1d74c0a2) entered disabled state
[   45.843605] device veth1d74c0a2 entered promiscuous mode
[   45.843618] cni0: port 1(veth1d74c0a2) entered blocking state
[   45.843619] cni0: port 1(veth1d74c0a2) entered forwarding state
[   46.243645] cni0: port 2(veth32637da7) entered blocking state
[   46.243647] cni0: port 2(veth32637da7) entered disabled state
[   46.243673] device veth32637da7 entered promiscuous mode
[   46.243681] cni0: port 2(veth32637da7) entered blocking state
[   46.243681] cni0: port 2(veth32637da7) entered forwarding state
[   46.353356] cni0: port 3(veth731c62bd) entered blocking state
[   46.353358] cni0: port 3(veth731c62bd) entered disabled state
[   46.353387] device veth731c62bd entered promiscuous mode
[   46.353394] cni0: port 3(veth731c62bd) entered blocking state
[   46.353395] cni0: port 3(veth731c62bd) entered forwarding state
[   46.513533] cni0: port 4(vethcca23b71) entered blocking state
[   46.513534] cni0: port 4(vethcca23b71) entered disabled state
[   46.513569] device vethcca23b71 entered promiscuous mode
[   46.513577] cni0: port 4(vethcca23b71) entered blocking state
[   46.513578] cni0: port 4(vethcca23b71) entered forwarding state
[   49.037349] hv_balloon: Max. dynamic memory size: 32660 MB
[  193.291546] scsi 0:0:0:4: Direct-Access     NVMe     SAMSUNG MZ1L21T9 102Q PQ: 0 ANSI: 6
[  193.291783] sd 0:0:0:4: Attached scsi generic sg4 type 0
[  193.292003] sd 0:0:0:4: [sde]<PHONE_NUMBER> 512-byte logical blocks: (1.92 TB/1.75 TiB)
[  193.292004] sd 0:0:0:4: [sde] 262144-byte physical blocks
[  193.296490] sd 0:0:0:4: [sde] Write Protect is off
[  193.296491] sd 0:0:0:4: [sde] Mode Sense: 0f 00 10 00
[  193.304487] sd 0:0:0:4: [sde] Write cache: disabled, read cache: enabled, supports DPO and FUA
[  193.304489] sd 0:0:0:4: [sde] Optimal transfer size 131072 bytes not a multiple of physical block size (262144 bytes)
[  193.317299]  sde:
[  193.317515] EXT4-fs (sde): VFS: Can't find ext4 filesystem
[  193.317537] ERROR: Mount:2528: mount(/dev/sde, /share/PHYSICALDRIVE1, ext4, 0x0, ) failed
[  193.317538] 22
[  193.329510] sd 0:0:0:4: [sde] Attached SCSI disk
[  471.307404] scsi 0:0:0:4: Direct-Access     NVMe     SAMSUNG MZ1L21T9 102Q PQ: 0 ANSI: 6
[  471.307636] sd 0:0:0:4: Attached scsi generic sg4 type 0
[  471.307812] sd 0:0:0:4: [sde]<PHONE_NUMBER> 512-byte logical blocks: (1.92 TB/1.75 TiB)
[  471.307813] sd 0:0:0:4: [sde] 262144-byte physical blocks
[  471.312352] sd 0:0:0:4: [sde] Write Protect is off
[  471.312353] sd 0:0:0:4: [sde] Mode Sense: 0f 00 10 00
[  471.320355] sd 0:0:0:4: [sde] Write cache: disabled, read cache: enabled, supports DPO and FUA
[  471.320357] sd 0:0:0:4: [sde] Optimal transfer size 131072 bytes not a multiple of physical block size (262144 bytes)
[  471.333202]  sde:
[  471.333447] EXT4-fs (sde): VFS: Can't find ext4 filesystem
[  471.333467] ERROR: Mount:2528: mount(/dev/sde, /share/PHYSICALDRIVE1, ext4, 0x0, ) failed
[  471.333468] 22
[  471.345348] sd 0:0:0:4: [sde] Attached SCSI disk
[  707.275676] scsi 0:0:0:4: Direct-Access     NVMe     SAMSUNG MZ1L21T9 102Q PQ: 0 ANSI: 6
[  707.275896] sd 0:0:0:4: Attached scsi generic sg4 type 0
[  707.276100] sd 0:0:0:4: [sde]<PHONE_NUMBER> 512-byte logical blocks: (1.92 TB/1.75 TiB)
[  707.276101] sd 0:0:0:4: [sde] 262144-byte physical blocks
[  707.280609] sd 0:0:0:4: [sde] Write Protect is off
[  707.280610] sd 0:0:0:4: [sde] Mode Sense: 0f 00 10 00
[  707.288607] sd 0:0:0:4: [sde] Write cache: disabled, read cache: enabled, supports DPO and FUA
[  707.288609] sd 0:0:0:4: [sde] Optimal transfer size 131072 bytes not a multiple of physical block size (262144 bytes)
[  707.301410]  sde:
[  707.301622] EXT4-fs (sde): VFS: Can't find ext4 filesystem
[  707.301640] ERROR: Mount:2528: mount(/dev/sde, /share/PHYSICALDRIVE1, ext4, 0x0, ) failed
[  707.301641] 22
[  707.313624] sd 0:0:0:4: [sde] Attached SCSI disk
[13476.151722] cni0: port 1(veth1d74c0a2) entered disabled state
[13476.151875] cni0: port 4(vethcca23b71) entered disabled state
[13476.151922] cni0: port 2(veth32637da7) entered disabled state
[13476.152002] device veth1d74c0a2 left promiscuous mode
[13476.152002] cni0: port 1(veth1d74c0a2) entered disabled state
[13476.211812] device vethcca23b71 left promiscuous mode
[13476.211814] cni0: port 4(vethcca23b71) entered disabled state
[13476.271856] device veth32637da7 left promiscuous mode
[13476.271857] cni0: port 2(veth32637da7) entered disabled state
[13476.921576] device veth731c62bd left promiscuous mode
[13476.921589] cni0: port 3(veth731c62bd) entered disabled state
[16757.506957] scsi 0:0:0:4: Direct-Access     NVMe     SAMSUNG MZ1L21T9 102Q PQ: 0 ANSI: 6
[16757.507202] sd 0:0:0:4: Attached scsi generic sg4 type 0
[16757.507441] sd 0:0:0:4: [sde]<PHONE_NUMBER> 512-byte logical blocks: (1.92 TB/1.75 TiB)
[16757.507442] sd 0:0:0:4: [sde] 262144-byte physical blocks
[16757.511882] sd 0:0:0:4: [sde] Write Protect is off
[16757.511883] sd 0:0:0:4: [sde] Mode Sense: 0f 00 10 00
[16757.519900] sd 0:0:0:4: [sde] Write cache: disabled, read cache: enabled, supports DPO and FUA
[16757.519902] sd 0:0:0:4: [sde] Optimal transfer size 131072 bytes not a multiple of physical block size (262144 bytes)
[16757.532759]  sde:
[16757.532901] EXT4-fs (sde): VFS: Can't find ext4 filesystem
[16757.532919] ERROR: Mount:2528: mount(/dev/sde, /share/PHYSICALDRIVE1, ext4, 0x0, ) failed
[16757.532921] 22
[16757.544902] sd 0:0:0:4: [sde] Attached SCSI disk

@zouherenjie in step nr. 2 you're trying to mount a disk that's supposed to have an ext4 filesystem. Did you create the filesystem previously? If not, attach the disk and create an ext4 filesystem then mount it. Otherwise mount fails.

@zouherenjie in step nr. 2 you're trying to mount a disk that's supposed to have an ext4 filesystem. Did you create the filesystem previously? If not, attach the disk and create an ext4 filesystem then mount it. Otherwise mount fails.

However， no matter I create the ext4 filesystem previously or not, it both fails with return code 22 and have the same ERROR in dmesg

hello, zouherenjie
Same problem happens when I am trying to mount the ext4.vhdx  image of my previous WSL. Would you please tell me how to manually mount the disk? I have really tried to find some way to deal with it. But none of them effective. Sorry for my poor English :)

hello, zouherenjie Same problem happens when I am trying to mount the ext4.vhdx image of my previous WSL. Would you please tell me how to manually mount the disk? I have really tried to find some way to deal with it. But none of them effective. Sorry for my poor English :)

@huiyeruzhou , unfortunately, my disk disappeared after one failed boot of WSL2. I hope my experience can help you.

delete all partitions of the disk you want to mount

mount the disk barely  in powershell wsl --mount <DiskPath> --bare

find you disk in WSL2 by blkid or lsblk or fdisk -l

build a new partition with ext4 filesystem in WSL2
mkfs.ext4 /dev/sdf1

unmount the disk wsl --unmount <DiskPath>

mount the disk barely again in powershell wsl --mount <DiskPath> --bare
Now you should see the disk with ext4 filesystem by blkid

Finally you can mount the disk manually in WSL2 such as mount  /dev/sdf  /app


fix(package): update uti to version 6.3.1

Codecov Report

Merging #752 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #752   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           2      2
  Lines          51     51
  Branches        9      9
=====================================
  Hits           51     51

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 d49b9c1...dee06cd. Read the comment docs.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Proxy request method, headers and body with  sendProxy()

I would expect sendProxy to copy method, headers and body from the original request.
// Copy request method
const method = event.req.method

// Copy request headers
const ignoredHeaders = [
	// https://github.com/nodejs/undici/blob/cd78eb57203ce85a26312290c1bef4017e30cf74/lib/core/request.js#L196-L220
	'transfer-encoding',
	'connection',
	'keep-alive',
	'upgrade',
	'expect',
]
const headers: HeadersInit = {}
for (const [header, value] of Object.entries(getRequestHeaders(event))) {
	if (value === undefined || ignoredHeaders.includes(header)) continue
	headers[header] = value
}
// TODO: Set x-forwarder-* headers?

// Copy request body
const payloadMethods = ['PATCH', 'POST', 'PUT', 'DELETE']
const body = payloadMethods.includes(method)
	? await (readRawBody(event, false) as unknown as Promise<Buffer>) // https://github.com/unjs/h3/issues/223
	: undefined

sendProxy(event, target.toString(), {
	fetchOptions: { method, headers, body },
})

Normally sendProxy is an explicit method to send response as proxy. We can create few options like passHeaders: true or proxyHeaders: true (same for body and method) to extend functionality.

https://github.com/unjs/h3/pull/226


Option to skip refresh on login

This PR adds an option on the login window to enable/disable forcing refreshing an account's stash tabs.  If the option is disabled, only missing tabs are downloaded while logging in.  This can help particularly in two cases.  First, if the user wants to close and reopen Procurement and not have to reload all tabs, which could be up to date anyway.  Second, if the user has Procurement keep track of multiple leagues, but the user is only going to reference one of those during a play session, he can have Procurement skip refreshing the tabs from all of those leagues, and manually refresh the tabs for the relevant league, after the login process is completed.
However, since the refresh process that can happen during login deletes and rebuilds the entire folder of bin files, if the user skips refreshing tabs at login, Procurement will never pick up changes to tab names/colors and tab ordering. (This is more a bug in how tabs are refreshed after logging in.)
I've also added in this PR some more error checking in places, and cleaned up how we determine we need to save the user's settings after modifying the login window's fields.
I'm not that adept with WPF/XAML, so please let me know particularly if I've done anything wrong or silly regarding the UI.

Fixed a misleading typo in a comment, and a momentary lapse of "when in Rome" mentality for variable naming.

About the variable naming, I'm not sure what style of variable naming you were using, but I have been thinking for some time that Procurement is long overdue to have the naming brought inline with modern .NET naming conventions.
Namely things like,
private int _someInt;
private void SomeMethod();
public const string SomeString = "foo";

Yeah, I had initially named forceRefresh as `_forceRefresh', as that's the style I'm used to (similar to the excerpt you wrote).
I've wanted to introduce StyleCop to this project because the style is a little all-over-the-place, but a) the StyleCop I used in the past has been deprecated, and I need to figure out how to tweak this one, b) I'm not sure of the best way to introduce a style-checker where there are a lot of issues already, c) it's still not a high priority, and d) I don't want to make it like I'm imposing a coding style (it's not my project).
Since you're of a similar mind, though, it seems, I think I should at least file an issue about it and get the ball rolling.

I've wanted to consolidate the style for some time, but it's always been that time spent on Procurement has always gone to features or fixes.
One approach could be to boyscout naming when making changes or adding new functionality making the trade-off of time spent on naming for consistency across the whole app.
Either way you have my blessing on this, I'd consider throwing up a naming PR but don't want to cause conflicts with all the good work you've been doing recently unnecessarily.


Update Composer dependencies (2023-05-15-00-12)

Visual regression test passed!
View the visual regression test report


After a factory reset, and before the first successful GUI pipette calibration, pipettes are way too low

Overview
Without having already established good pipette calibrations through the pipette calibration GUI, pipettes will be positioned too low. They will be so low that they will crash into the z switch of the tip probe box during tip probing, preventing a successful calibration unless the tip is taken off and tip probing is faked by hitting the switches manually.
This occurs after CLI calibration on fresh SD cards. It also occurs after doing a tip length factory reset through the GUI.
We've seen this issue across multiple OT-2s.
Reproducing

Feed an OT-2 a fresh SD card. We've seen this on a few different system versions, but the  VERSION.json corresponding to the sdcard.img I used is: {"buildroot_version": "v1.0.3-1-gc4bf505b1", "buildroot_sha": "c4bf505b1562e9d9a7a3544a19cd16151a3b23f6", "buildroot_branch": "opentrons-develop", "buildroot_buildid": "opentrons-buildroot:61c73d8b-97f6-4bc9-a3b6-6ef4b482b286", "build_type": "dev", "opentrons_api_version": "3.11.3", "opentrons_api_sha": "b88c73ba9a79758cf130d2c24d8700aa5c13bcc8", "opentrons_api_branch": "edge", "update_server_version": "3.11.3", "update_server_sha": "b88c73ba9a79758cf130d2c24d8700aa5c13bcc8", "update_server_branch": "edge"}
Do CLI calibration. The tip probe stage (p) may fail initially, but after multiple p+spacebar iterations with manual "helping," it will stabilize and succeed. See also #3985.
Reboot and upload a protocol through the GUI. I used one with two P300s. When you do pipette calibration, the pipettes will be too low, despite having done a successful tip probe in CLI calibration.
After many iterations with manual intervention, pipette calibration will eventually stabilize and succeed.
Do a Reset > Tip Length. Observe you're now back at step 3.

Reading Material
I've attached a .zip with a history of JSON files.

robot_settings_0_after_cli_calibration.json and deck_calibration_0_after_cli_calibration.json are from immediately after step 2, above.
robot_settings_1_after_much_pipette_calibration_finagling.json is immediately after step 4, above.
robot_settings_2_after_factory_reset.json is immediately after step 5, above.

3986.zip

In some cases, this can result in the z-switch on the tip probe being triggered too early during tip length calibration, which results in the error message below

Ran into a strange scenario using a workaround to resolve this issue.
Right now, when users run into this issue, we manually change the tip length data in robot_settings.json, adding 10-15mm to provide a margin of safety so that the next time the robot does tip length calibration, it will be able to do so successfully and independently.
Today when I did this with a user, the robot was able to successfully complete tip length calibration after making the change to tip length, but ran into the issue again on a subsequent run with the same pipette and same tips.
The first time we changed robot_settings.json, there was only one key/value pair for the p1000:
"p1000_single_v1.4": xx.xxxxx
(I don't remember the original value, apologies)
When the user ran into the issue again, when we opened robot_settings.json, there were two separate key/value pairs:
"p1000_single_v1": xx.xxxxx
"p1000_single_v1.4": xx.xxxxx
The v1 had a corrupt data point that was causing the issue. We manually changed the value for v1 and resolved the issue.
Hope this info helps!


[scope]: annotate std.random

Update to work with -dip1000

The inference is rather simplistic, in particular, it doesn't work so well when the value is copied about.

Will override DAutoTest cc @CyberShadow for follow-up


Add filter mechanism

We can use a larger package like Semantic UI.
Or find individual features that we want, like this multiple select React component.

[ ] Filter popup
[ ] Dropdown options
[ ] Population slider


Added 404 page not found

Signed-off-by: afzal442<EMAIL_ADDRESS>
Description
Fix #170

Additional context

What is the purpose of this pull request?

[ ] Bug fix
[x] New feature
[ ] Other

Plz, have a look at the screenshot;

Thanks @afzal442!
Let me run the deploy preview!

@afzal442 Looks like we have some linting issues here
https://github.com/pytorch-ignite/code-generator/pull/178/checks?check_run_id=3781076007#step:9:13
Please take a look at our CONTRIBUTING how to run formatters.

Thanks @afzal442 ! It works!
https://deploy-preview-178--code-generator.netlify.app/foo
But let's try to add header and a footer, to get smth like this:

Inspired by pytorch 404 page

@trsvchn I am done. 🪧 Plz also add  hacktoberfest label as well. 😵💫

Thanks @afzal442 ! This looks much better :)
Let's split the page content into several lines, to fit into the following template:
Error Code

Error Short Description

Error Long Description

How to solve

navbar

404
Page Not Found
Oops we couldn't find that page.
Try going home

footer


How to use options API along with Composition API in vue3?

Version
3.2.31
Reproduction link
sfc.vuejs.org/
Steps to reproduce
click the button,  reactive msg variable doesn't  change as expected.
What is expected?
when click button, console log ref msg variable, and change it to  'ok!'
What is actually happening?
console log msg is undefined(in my local workstation)
click doesn't seem to work

when development(vite), everything works as expected.
after build(vite build) and deploy,  it doesn't work!

As pointed out in other issues: you don't use both apis on the same component. You can use both apis in the same project thought.


[docs] Add TypeScript guide on the polymorphic components

Related to https://github.com/mui/material-ui/issues/31314, https://github.com/mui/material-ui/issues/31976
Looks like this applies for the base components too, maybe would be worth adding it there too cc @michaldudak
Here is a codendbox describing the issue and the suggested solution:
https://codesandbox.io/s/amazing-lucy-rs38sz?file=/src/App.tsx

@mnajdova The codesandbox you linked here has an issue - in lines 9 and 10 a Button is wrapped in styled, not ButtonUnstyled. Correcting it makes it work without errors.
This is likely because ButtonUnstyled does not inherit from OverridableComponent. Because of this, it's not really polymorphic, but it prevents this problem (and hopefully is faster, but I haven't measured it).

@mnajdova The codesandbox you linked here has an issue - in lines 9 and 10 a Button is wrapped in styled, not ButtonUnstyled. Correcting it makes it work without errors.
This is likely because ButtonUnstyled does not inherit from OverridableComponent. Because of this, it's not really polymorphic, but it prevents this problem (and hopefully is faster, but I haven't measured it). Any additional props can be placed on a componentsProps.root object.
But in principle, yes, it does apply to generic components. There is a note in Select docs describing the need to cast because of this problem.

Right, I've updated the sandboxed. Let's leave it as is for know then and if necessary we can add similar section on one of the guides for the base components.


add pulp ostree import commit

Description
Add method to use import-commit for importing a commit to an existing repo with one or more existing commits
OstreeImportCommits includes the OSTree ref for updating a tree that has at least one commit
Use OstreeImportAll via RepositoriesImport for the initial commit
(see https://pulpproject.org/pulp_ostree/docs/user/guides/import-commit/)
FIXES: HMS-4121
Type of change
What is it?

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[ ] Refactor

How is this different from RepositoriesImport ? could we add a brief comment for it? It might confuse future readers as much as I'm confused now xD

How is this different from RepositoriesImport ?

This is for subsequent updates to an existing repo.
Comments added to both code and PR.


[Bug]:When insert/delete table with multiple blocks, and only one segment, errors occur.

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Branch name
main
Commit ID
1ca85c2e
Other environment information
No response
Actual behavior
When inserting or deleting a table with multiple blocks, but only one segment, some errors occur.

Expected behavior
No response
Steps to reproduce
Function test code can be found in python/test/test_delete.py `test_delete_table_with_one_segment`

Additional information
No response

Fixed by #614

It looks fixed.


Invalid HTTP upgrade when try to connect

When I try to connect, I am always thrown into onDisconnect. I looked into the connect() and there I came across an error 308 and message "Invalid HTTP upgrade". Do u have any solutions ?

AFAIK, a websocket connection is established via http UPGRADE command. Check if your webserver allows WS connections.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Protocol_upgrade_mechanism


private & protected

Hey,
I do not know if you'd interested but I've released recently this https://github.com/wojtkowiak/private-decorator.
It works only without strict because it is based on function.caller therefore you can use them only with es2015-without-strict.
If you want you can include it in your library. Of course you do not have to explain if you do not want to :smile: Just wanted you to know.
Greets

Very neat solution.
I don't think it belongs here because of the caveats you mentioned. Especially because ES2015 code is supposed to always be in strict mode implicitly which is why babel includes it by default.

Module code is always strict mode code.
All parts of a ClassDeclaration or a ClassExpression are strict mode code.

https://tc39.github.io/ecma262/#sec-strict-mode-code
This is important to note because not including it means you'll never be able to stop transpiling.


Update Image

So I think this will work. The worst case scenario is someone commits their compose.yaml but it will get overwritten anytime you run the container.
Other problem is it will run the get a new image tag every time... Let me know what you think

Works for me if CI is happy; let's ship it and refine later if we need to


Document VertexAI authentication

Yes, good idea to add some details about authentication.
As you need a GCP project to use Gemini and PaLM, when running locally you can just configure the gcloud SDK with your project that has those LLM APIs enabled. The Vertex AI libraries will automatically figure out how to authenticate to the APIs, without the need to export an JSON service account key, as long as you're logged in with the default application credentials, or with your own user account.
It's better to avoid generating such a key, as we run the risk of committing that key by mistake 😄
For deployment, when running on GCP, same thing, authentication will be handled transparently.
I think it's only when deploying elsewhere that you need to have the JSON service account key.

@glaforge do oyu mean it is better to swith options a) and b) ? Or remove option a (service account/json file) completely?

Switching a) and b) would be good.
I think I wouldn't remove the json file mention because not all developers necessarily use gcloud, so they would need that approach if they don't use it.

@glaforge just did the change you suggested, could you please double-check?

Yup, I think it's better that way 👍


Pin tools in https://github.com/serlo/cloudflare-worker

Done in https://github.com/serlo/cloudflare-worker/pull/425


Update of climate/lock is taking over 10 seconds is flooding log

The updates of the device are flooding the logs with warnings Update of xxx is taking over 10 seconds. For some reason the ‘climate’ update is every 5 minutes but the ‘lock’ update is every 2 minutes (sometimes every minute).
2023-05-01 10:20:10.251 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.spare_bedroom_wall_heater is taking over 10 seconds
2023-05-01 10:21:10.713 WARNING (MainThread) [homeassistant.helpers.entity] Update of lock.spare_bedroom_wall_heater is taking over 10 seconds

Enabling the debug log shows it is having an issue with ‘protocol 3.1’ but then tries again with 3.3 and succeeds every time.
2023-05-01 10:38:00.735 DEBUG (SyncWorker_3) [custom_components.goldair_climate.device] Refreshing device state for Spare Bedroom Wall Heater.
2023-05-01 10:38:00.781 DEBUG (SyncWorker_3) [custom_components.goldair_climate.device] Retrying after exception [Errno 104] Connection reset by peer
2023-05-01 10:38:00.781 INFO (SyncWorker_3) [custom_components.goldair_climate.device] Setting protocol version for Spare Bedroom Wall Heater to 3.1.
2023-05-01 10:38:10.735 WARNING (MainThread) [homeassistant.helpers.entity] Update of lock.spare_bedroom_wall_heater is taking over 10 seconds
2023-05-01 10:38:10.800 DEBUG (SyncWorker_3) [custom_components.goldair_climate.device] Retrying after exception timed out
2023-05-01 10:38:10.800 INFO (SyncWorker_3) [custom_components.goldair_climate.device] Setting protocol version for Spare Bedroom Wall Heater to 3.3.
2023-05-01 10:38:10.860 INFO (SyncWorker_3) [custom_components.goldair_climate.device] refreshed device state: {"devId": "84403378c45bbeee506b", "dps": {"1": false, "2": false, "3": 23, "4": 22, "5": 0, "6": 0, "updated_at":<PHONE_NUMBER>.860798}}
2023-05-01 10:38:10.860 DEBUG (SyncWorker_3) [custom_components.goldair_climate.device] new cache state (including pending properties): {"1": false, "2": false, "3": 23, "4": 22, "5": 0, "6": 0, "updated_at":<PHONE_NUMBER>.860798}
2023-05-01 10:39:00.736 DEBUG (SyncWorker_3) [custom_components.goldair_climate.device] Refreshing device state for Spare Bedroom Wall Heater.
2023-05-01 10:39:00.868 INFO (SyncWorker_3) [custom_components.goldair_climate.device] refreshed device state: {"devId": "84403378c45bbeee506b", "dps": {"1": false, "2": false, "3": 23, "4": 22, "5": 0, "6": 0, "updated_at":<PHONE_NUMBER>.8680916}}
2023-05-01 10:39:00.868 DEBUG (SyncWorker_3) [custom_components.goldair_climate.device] new cache state (including pending properties): {"1": false, "2": false, "3": 23, "4": 22, "5": 0, "6": 0, "updated_at":<PHONE_NUMBER>.8680916}

Updating line 18 of ‘const.py’ to remove protocol 3.1 and restarting HA seems to resolve the issue.
Changed from:
API_PROTOCOL_VERSIONS = [3.3, 3.1]
to:
API_PROTOCOL_VERSIONS = [3.3]
Note this is for a GECO heater. Limiting the protocol to 3.3 may cause issues with other devices

You must be using an old version to only have two versions in that list.  Try updating.


I have been unable to get it to work on Joomla

Hey!
I've been unable to get it to work on Joomla.
I'm getting lots of different errors and I was unable to find anything in the documentation or google.
I have put the script in the index.php file of the entire website, I made sure it runs, it is, it appears in the source code.
However when I try to call it in a html document I always get "jsPDF is not defined".
So I added a statement to import it. Now it just says that I can only import javascript if they are set as modules. Tried adding that tag, but it goes back to the first error. So I'm stuck there.
Any help?

Seems more like a general question how to import JS libraries in Joomla.

I am having the same issue. I would like to know if someone could add the script on joomla.
I used:  before the head tag, but everytime is returning Uncaught ReferenceError: jsPDF is not defined

Haven't found a way to make it work yet

The global variable has changed to jspdf (all lowercase). The jsPDF constructor is available under window.jspdf.jsPDF.

Thanks for the Help!


Checkpooint Callback not called when training GAN from documentation

I tried to add a model checkpoint callback to the GAN example from the documentation (https://github.com/PyTorchLightning/pytorch-lightning/blob/master/pl_examples/domain_templates/gan.py), but it is failing silently; no checkpoints are being written.  I can't find anything in the checkpoint docs that indicate why it is not working.
What's your environment?

OS: Linux
Packaging: Conda
Version : 1.0, pytorch 1.4

@PasqualeZingo could you reproduce the error in a Colab notebook and share the link?

Sure thing, here it is: https://colab.research.google.com/drive/1wvZXP3WYxolfa4oA0mVnawtCXDr19eLd
Thanks @jeremyjordan !

Ah ok I think I know what's going on here.
If you look at the checkpointing callback, it's invoked with on_validation_end.
However, because you don't have a validation_step defined, the trainer is skipping validation. As a result, the callback to save the model checkpoints is never actually called.

should we enable the checkpoint callback to use any metric across training or validation step?

That would be ideal, in the mean time I can fool the validation loop into running for my use.  Would it be worth updating the docs in the mean time to clarify about the checkpoint callback?

Yes, we should be running this on_epoch_end after both training and validation are complete.

merged #1043


Is there an agreed upon pattern for re-useable reducers?

In my app I've got several different entities that are tracked in the store (E.G. users, admins, etc) each kept under their own subdomain in the state like this:
{
  users: {
    "users/1": {
      loaded: true,
      loading: false,
      data: { ... }
    }
  },
  admins: {
    "admins/1": {
      loaded: true,
      loading: false,
      data: { ... }
    }
  }
}

Ideally, I'd like to only have a single entity module that handles all of these, but need a good way to reuse the LOAD, UNLOAD, etc actions as well as a reducer that only reacts to actions for that specific subdomain. multireducer doesn't quite work because the load actions are dispatched in the @asyncConnect decorator, which is before multireducer binds the actions to the specific reducers.
My question is whether or not there is an agreed upon best practice for this situation? Surely I can't be the only one who wants to try to reuse reducers and actions in this way.
One approach I had considered was an entities.js module that exports reducer and action factories that would take an entity name or something and produce a reducer that only modifies the state if the action contains { meta: { entity: "users" } } or something like that. The action factories could produce actions that automatically contain the proper meta data.
Anyone have any suggestions?

It can't be the case that no one has figured out a good solution to this


Why does only Course.cs have [DatabaseGenerated(DatabaseGeneratedOption.None)]?

Why does Student.cs and Enrollment.cs not have this data annotation? I think the point for having this can either be clarified better or explained since Enrollment.cs has a primary key for EnrollmentID but it doesn't require this annotation.

The article explains that in this case we want to select the PK, not the DB.

Thanks for contacting us. We believe that the question you've raised have been answered. If you still feel a need to continue the discussion, feel free to reopen it and add your comments.


error: ‘::readv’ has not been declared

Tars/cpp/servant/libservant/Transceiver.cpp:493:18: error: ‘::readv’ has not been declared
     int iRet = ::readv(_fd, vecs, vcnt);
                  ^~~~~

missing header sys/uio.h?

Reproduced on Ubuntu 18.04
add #include <sys/uio.h>  in Tars/cpp/servant/libservant/Transceiver.cpp fixed this.


System.IO.IOException: Error -104 ECONNRESET connection reset by peer

I am getting this excpetion in my code
System.IO.IOException: Error -104 ECONNRESET connection reset by peer ---> Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.UvException: Error -104 ECONNRESET connection reset by peer
at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.LibuvOutputConsumer.d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.LibuvConnection.d__26.MoveNext()
--- End of inner exception stack trace ---
at Microsoft.AspNetCore.Server.Kestrel.Internal.System.IO.Pipelines.PipeCompletion.ThrowFailed()
at Microsoft.AspNetCore.Server.Kestrel.Internal.System.IO.Pipelines.Pipe.GetResult(ReadResult& result)
at Microsoft.AspNetCore.Server.Kestrel.Internal.System.IO.Pipelines.Pipe.Microsoft.AspNetCore.Server.Kestrel.Internal.System.IO.Pipelines.IReadableBufferAwaiter.GetResult()
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.Frame`1.d__2.MoveNext()

@radheshchamarti Do you see this on every request? This exception should only occur when the client closes the underlying connection mid-request which is generally pretty rare.

Same here, ref: https://github.com/aspnet/KestrelHttpServer/issues/2536. I spent over an hour skyping a MS Network Engineer going over a network trace to try and figure out why we are getting ECONNRESET exceptions in our logs. We are running a number of Docker containers on an Azure VM which together comprise a small microservice system. The Docker base image is microsoft/aspnetcore:2.0.6.
The Azure application gateway sends a default health probe request to the web server every 30 seconds. Mostly this works but maybe 20 times a day it fails. Stack trace logged:
22:33:19 [Information] () "Request starting HTTP/1.1 GET http://<IP_ADDRESS>/  "

22:33:19 [Information] () {"Connection":["Keep-Alive"],"Host":["<IP_ADDRESS>"],"Max-Forwards":["10"]}

22:33:19 [Information] () Executing action method "HonestyBoxWeb.Controllers.HomeController.Index (HonestyBoxWeb)" with arguments (null) - ModelState is Valid

22:33:19 [Information] () Executing ViewResult, running view at path "/Views/Home/Index.cshtml".

22:33:19 [Information] () Executed action "HonestyBoxWeb.Controllers.HomeController.Index (HonestyBoxWeb)" in 6.6907ms

22:33:19 [Information] () "Request finished in 13.7646ms 200 text/html; charset=utf-8"

22:33:19 [Information] () Connection id ""0HLD3PUA8AP49"" request processing ended abnormally.
System.IO.IOException: Error -104 ECONNRESET connection reset by peer ---> Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.UvException: Error -104 ECONNRESET connection reset by peer
   at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.LibuvOutputConsumer.<WriteOutputAsync>d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.LibuvConnection.<Start>d__26.MoveNext()
   --- End of inner exception stack trace ---
   at Microsoft.AspNetCore.Server.Kestrel.Internal.System.IO.Pipelines.PipeCompletion.ThrowFailed()
   at Microsoft.AspNetCore.Server.Kestrel.Internal.System.IO.Pipelines.Pipe.GetResult(ReadResult& result)
   at Microsoft.AspNetCore.Server.Kestrel.Internal.System.IO.Pipelines.Pipe.Microsoft.AspNetCore.Server.Kestrel.Internal.System.IO.Pipelines.IReadableBufferAwaiter.GetResult()
   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.Frame`1.<ProcessRequestsAsync>d__2.MoveNext()

The network trace does show the health probe sending RST, but it does that each time. The website is not being hit by any other requests when this occurs. It would be helpful to have this resolved - at the moment we're getting these reported effectively as false positives that make it less likely we will identify actual issues when they occur. I have an open ticket with Azure Infrastructure Support REG:118032617886670 but their feedback is basically that it isn't their issue:

I have had an internal discussion with my Technical advisory of the health probe behavior of Application gateway and we confirmed that it will not use graceful TCP closure to close the session with backend server. It will only use the ACK Reset to close the existing health probe session in a much efficiency way.
To conclude, the Application gateway will use ACK Reset to close the health probe session and no graceful TCP session close phase will be used by Application gateway. In the latest network trace file you provide on 05/02, we can see totally of 12 Reset packets have been sent to backend server to finish the TCP connection between health probe and server.
For the ECONNRESET log in your webserver, we do consider it was generated by Kestrel itself instead of Azure Application gateway. Because according to the packet analysis, it should record more logs of ECONNRESET instead of only 1 time in the log file around issue time.

@daveclarke are you saying that you get an RST in Kestrel without the client disconnecting? Do you have a repro for that? Sounds like maybe it could be a deeper issue as we're not doing anything special here. If you have something reproducible then we can take a look.

@davidfowl no, the Azure application gateway is sending a health probe request every 30 seconds but is just doing a Reset to close the connection. This happens for every request but Kestrel doesn't log an exception every time, only a couple of dozen are logged per day. Obviously we're not the only ones using Kestrel in Azure but we are generating an email notification when an exception is logged so we're effectively getting false positives. Our clients don't appear to be impacted by this as far as I'm aware. Certainly the 30 second health probes are currently the most active client we have but we hope that will change as our client base grows :-)

Yes, @halter73 and I had a discussion about making it so that all errors due to the connection going away are logged as trace/debug.

Sounds good to me. When might we see it resolved? @halter73 indicated it "didn't hit the escrow bar for 2.1.0".

2.1.0 is pretty much done.

#2547 should address the noisy logs. I tried to get the change approved for 2.1 a few days before opening that PR, but it didn't meet the bar.

Fixed by #2547


run active file in terminal should add backslashes for windows

fixes #36897
Run Active File In Active Terminal command needs to add backslashes on windows in order to fully qualify the file path to the terminal being used. This change checks for the platform and adds the extra backslashes if the platform is windows.

This won't fix the linked issue as / are meant to be used, in addition to resolving the wslpath when under wsl and nativeSep will be '`?


chore(RingTheory/OreLocalization): split into GroupTheory.OreLocalization

The files Mathlib/GroupTheory/OreLocalization/OreSet.lean and Mathlib/GroupTheory/OreLocalization/Basic.lean contain the results of Mathlib/RingTheory/OreLocalization/OreSet.lean and Mathlib/RingTheory/OreLocalization/Basic.lean that don't involve rings or monoids with zero.

[ ] depends on: #17729

bors d+

bors merge

bors merge


Remove engine::util

What have you changed?
This PR gets rid of engine::util in favor of engine_traits as part of https://github.com/tikv/tikv/issues/6402
We're getting to the long tail of hard-to-categorize stuff that lives in the engine. Instead of trying to come up with a nice factoring for some of the things I'm moving into engine_traits, I've instead just created a MiscExt to hold some methods that aren't entirely sorted out yet.
Eventually I will expect KvEngine to not have any methods or associated types of its own. It is essentially just a name to refer to a big bundle of other traits. It may become a typedef if Rust ever supports it.
What is the type of the changes?

Engineering (engineering change which doesn't change any feature or fix any issue)

How is the PR tested?
cargo test --all --no-run
Does this PR affect documentation (docs) or should it be mentioned in the release notes?
no
Does this PR affect tidb-ansible?
no
Refer to a related PR or issue link (optional)
https://github.com/tikv/tikv/issues/6402
Benchmark result if necessary (optional)
Any examples? (optional)

/merge


Add RTLCSS support for resource pipelines

With support for RTLCSS in the pipelines we can have support for multilingual websites a lot more easily. The script is written in JavaScript but I think if the feature is implementable, we can either convert it to Go or think of something so it can be run using NodeJS, that way Babel (#5039) would be implementable as well.

If that is something, worthwhile for Hugo, there might be engineering resources we can put behind it. Don't want to start anything without a first discussion.

Why not make this as a postcss plugin?

This is available as a PostCSS plugin:
https://github.com/elchininet/postcss-rtlcss
Try it:
git clone --single-branch -b hugo-github-issue-5079 https://github.com/jmooring/hugo-testing hugo-github-issue-5079
cd hugo-github-issue-5079
npm ci
hugo server


Added border curve style prop ("Squircle" effect - iOS only)

Summary

Since iOS 13+, it is possible to change the corner curve property on iOS in order to smoothen border radius and make it more "rounded" (also called "squircle")
Here's an article explaining in details what it is.
This property is also built in figma, but currently there is no way to implement this directly with react-native despite it being available natively on iOS.
Many open source react-native libraries were created in order to simulate this behaviour:
react-native-super-ellipse-mask
react-native-squircle-view
react-native-figma-squircle
But they rely on creating an SVG shape with the smoothed corners and masking the view behind. This makes it not very performant (flickering on mounting was a common side-effect)
This PR aims at implementing the property natively.
PR for the docs update: https://github.com/facebook/react-native-website/pull/2785
Changelog

[iOS] [Added] - Added cornerCurve style prop to smoothen the border radius (squircle effect)
Test Plan
We used the RNTester app and added an example with cornerCurve  set to 'continuous' (only on iOS).
As the difference is quite subtle, we also made some more tests to better illustrate the difference (these are not in the showcase app):

We overlapped two views with position: absolute, the one in the background has a red background and has cornerRadius set to false, and the one in the foreground is set to true. We can clearly see where the borders differs on the corners.

What about naming it borderCurve (borderRadiusCurve? cornerCurve? borderRadiusStyle?) with value 'circular' | 'continuous'.

Sounds good to me.
borderCurve: ?('circular' | 'continuous'),

@janicduplessis is it normal that the CI fails here ? Thanks

I think its fine, failures don't seem related to your changes.
LGTM thanks for the PR!!
@yungsters Can you import this?

@philIip Could you have a look at this again? seems like all feedback have been addressed.

@janicduplessis @philIip  quick bump on this one, looks like the ReactNativeViewViewConfig.js doesn't exist anymore + merging with main fails locally with
error: add_cacheinfo failed to refresh for path 'packages/react-native-gradle-plugin/gradlew.bat'; merge aborting.

Any help on what should I do next to get this feature merged? Thanks!

I think this commit can help, https://github.com/facebook/react-native/commit/7b9490b4b122183c34bd6228836ffb1d2f394f0a Just move the change to Libraries/NativeComponent/PlatformBaseViewConfig.js

thanks @giautm
@janicduplessis I kept running into merge issues mentioned above so I just opened a fresh PR here: https://github.com/facebook/react-native/pull/33783 if you don't mind. This one can safely be closed


As a user, I want to have the Edit Account button point to the standard Salesforce edit and have a Manage Household button shown for Household Accounts

Included in beta release version 3.40 (Beta 1) and higher

Included in production release version 3.40


home.miot-spec.com is down.

Is it intentional, is there any hope to get it back soon? Btw, thank you very much for all your efforts!

This website is currently hosted on my Raspberry Pi. Recently, my home network suffered a failure. It should be restored today. Later, I will host the website on a cloud server.
Thank you for your support !

@al-one 500 Server Error :(


Fix unittests

Fixes errors in unit tests caused by #11201.
CC: @abose

Fixed, merging.

@abose Did all of them pass this time?

Yes all tests passed.
If you noticed that live Preview tests failed, that intermittently happens, usually some timeout issues, but will pass eventually on rerums.

@abose Only 1 live preview test passed for me at first run.

yes i too get that at times, but reruns usually does the trick. Might be some timing issue.


{Service Connector}: add error message for invalid source resource id

Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Service Connector


Fix hot reload support for typical usage of CupertinoTabView.

Description
CupertinoTabView does not currently handle hot reload as well as it could.
This CL fixes a common case triggered by Cupertino apps that breaks hot reload unless users know the common workaround to fix closures that don't update on hot-reload.
Related Issues
This PR fixes
https://github.com/flutter/flutter/issues/43574
Tests
I added the following tests:
I've added a test that simulates a hot reload of the CupertinoTabView. Without this CL the test fails.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I signed the [CLA].
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (Please read [Handling breaking changes]). Replace this with a link to the e-mail where you asked for input on this proposed change.
[x] No, this is not a breaking change.

This CL fixes the builder case but creating a CupertinoPageRoute directly can still leave you in a state where hot reload does not work as expected. I'm not clear what the right fix would be for that case.

@xster Are you available to review this PR?

This should not affect state restoration.


BSD trained checkpoints

Dear authors,
Thank you for sharing your code and paper. Where can I find the checkpoints of the VDTR trained on a real blur dataset (BSD)? I only noticed GoPro and DVD checkpoints.
Sincerely,
Magauiya

I will update the model pretrained on BSD.

Hello, the checkpoints are available now.