Container hangs on Apple logo after crashing once

Operating system
Debian 11
Description
When starting the container for the first time the MacOS installer crashes with this error message. After rebooting it gets stuck at an apple logo with a loading bar at the bottom that never progresses any further.
Docker compose
services:
  macos:
    image: dockurr/macos
    container_name: macos
    environment:
      VERSION: "sonoma"
    devices:
      - /dev/kvm
    cap_add:
      - NET_ADMIN
    ports:
      - 8006:8006
      - 5900:5900/tcp
      - 5900:5900/udp
    stop_grace_period: 2m

Docker log

❯ Starting macOS for Docker v1.04...
❯ For support visit https://github.com/dockur/macos
❯ CPU: AMD Ryzen 5 2600 Six Core Processor | RAM: 9/32 GB | DISK: 289 GB (ext4) | HOST: 6.1.0-0.deb11.18-amd64...
❯ Downloading macOS Sonoma recovery image...
Downloading 694-88583...
Saving http://oscdn.apple.com/content/downloads/17/05/052-32968/ncxjjpfvl0w3kfzu3du0hqp06rqqic1c7u/RecoveryImage/BaseSystem.chunklist to /storage/tmp/BaseSystem.chunklist...
0.002887725830078125 MBs downloaded...
Download complete!

Download complete!
Verifying image with chunklist...

❯ Creating a 32G growable disk image in raw format...
❯ Extracting boot image...
❯ Booting macOS 1920x1080 using QEMU v8.2.4...
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
3h3h3hBdsDxe: failed to load Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0xA,0x0): Not Found
BdsDxe: loading Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
#[EB|LOG:EXITBS:END] _
#[EB.BST.FBS|-]
#[EB|B:BOOT]
#[EB|LOG:HANDOFF TO XNU] _
======== End of efiboot serial output. ========
3h3h3hBdsDxe: failed to load Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0xA,0x0): Not Found
BdsDxe: loading Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
#[EB|LOG:EXITBS:END] _
#[EB.BST.FBS|-]
#[EB|B:BOOT]
#[EB|LOG:HANDOFF TO XNU] _
======== End of efiboot serial output. ========

Screenshots (optional)

That command did seemed to make some progress as the bar did start moving now though it eventually ended up just boot looping with the same error message again. I've attached the logs of a clean container with debug logs enabled below:

        Logs:

❯ Starting macOS for Docker v1.04...
❯ For support visit https://github.com/dockur/macos
❯ CPU: AMD Ryzen 5 2600 Six Core Processor | RAM: 9/32 GB | DISK: 287 GB (ext4) | HOST: 6.1.0-0.deb11.18-amd64...
❯ Downloading macOS Sonoma recovery image...
Downloading 694-88583...
Saving http://oscdn.apple.com/content/downloads/17/05/052-32968/ncxjjpfvl0w3kfzu3du0hqp06rqqic1c7u/RecoveryImage/BaseSystem.chunklist to /storage/tmp/BaseSystem.chunklist...
0.002887725830078125 MBs downloaded...
Download complete!

Download complete!
Verifying image with chunklist...

❯ Creating a 32G growable disk image in raw format...
❯ Host: 629ef3f0a207  IP: <IP_ADDRESS>  Gateway: <IP_ADDRESS>  Interface: eth0  MAC: 02:E2:D1:9B:AD:48
nameserver <IP_ADDRESS>
++ /usr/sbin/dnsmasq --dhcp-range=<IP_ADDRESS>,<IP_ADDRESS> --dhcp-host=02:E2:D1:9B:AD:48,,<IP_ADDRESS>,QEMU,infinite --dhcp-option=option:netmask,<IP_ADDRESS> --dhcp-option=option:dns-server,<IP_ADDRESS> --dhcp-option=option:router,<IP_ADDRESS> --address=/host.lan/<IP_ADDRESS>
❯ Extracting boot image...
Arguments:
-nodefaults
-cpu Haswell-noTSX,kvm=on,l3-cache=on,+hypervisor,+invtsc,vendor=GenuineIntel,vmware-cpuid-freq=on,-pdpe1gb
-smp 2,sockets=1,dies=1,cores=2,threads=1
-m 3G
-machine type=q35,smm=off,graphics=off,vmport=off,dump-guest-core=off,hpet=off,accel=kvm
-enable-kvm
-global kvm-pit.lost_tick_policy=discard
-display vnc=:0,websocket=5700
-vga vmware
-monitor telnet:localhost:7100,server,nowait,nodelay
-name macos,process=macos,debug-threads=on
-serial mon:stdio
-device nec-usb-xhci,id=xhci
-device usb-kbd,bus=xhci.0
-global nec-usb-xhci.msi=off
-device usb-tablet
-netdev tap,ifname=qemu,script=no,downscript=no,id=hostnet0
-device virtio-net-pci,romfile=,netdev=hostnet0,mac=02:E2:D1:9B:AD:48,id=net0
-device virtio-blk-pci,drive=InstallMedia,scsi=off,bus=pcie.0,addr=0x6,iothread=io2
-drive file=/storage/base.dmg,id=InstallMedia,format=dmg,cache=unsafe,readonly=on,if=none
-drive file=/storage/data.img,id=data3,format=raw,cache=none,aio=native,discard=on,detect-zeroes=on,if=none
-device virtio-blk-pci,drive=data3,scsi=off,bus=pcie.0,addr=0xa,iothread=io2,bootindex=3
-object iothread,id=io2
-device virtio-blk-pci,drive=OpenCore,scsi=off,bus=pcie.0,addr=0x5,iothread=io2,bootindex=10
-drive file=/storage/boot.img,id=OpenCore,format=raw,cache=none,aio=native,readonly=on,if=none
-smbios type=2
-rtc base=utc,base=localtime
-global ICH9-LPC.disable_s3=1
-global ICH9-LPC.disable_s4=1
-global ICH9-LPC.acpi-pci-hotplug-with-bridge-support=off
-device isa-applesmc,osk=ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc
-drive if=pflash,format=raw,readonly=on,file=/storage/macos.rom
-drive if=pflash,format=raw,file=/storage/macos.vars
-object rng-random,id=objrng0,filename=/dev/urandom
-device virtio-rng-pci,rng=objrng0,id=rng0,bus=pcie.0,addr=0x1c
-device virtio-balloon-pci,id=balloon0,bus=pcie.0,addr=0x4
❯ Booting macOS 1920x1080 using QEMU v8.2.4...
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
3h3h3hBdsDxe: failed to load Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0xA,0x0): Not Found
BdsDxe: loading Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
#[EB|LOG:EXITBS:END] _
#[EB.BST.FBS|-]
#[EB|B:BOOT]
#[EB|LOG:HANDOFF TO XNU] _
======== End of efiboot serial output. ========
3h3h3hBdsDxe: failed to load Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0xA,0x0): Not Found
BdsDxe: loading Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
#[EB|LOG:EXITBS:END] _
#[EB.BST.FBS|-]
#[EB|B:BOOT]
#[EB|LOG:HANDOFF TO XNU] _
======== End of efiboot serial output. ========
3h3h3hBdsDxe: failed to load Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0xA,0x0): Not Found
BdsDxe: loading Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
#[EB|LOG:EXITBS:END] _
#[EB.BST.FBS|-]
#[EB|B:BOOT]
#[EB|LOG:HANDOFF TO XNU] _
======== End of efiboot serial output. ========
qemu-system-x86_64: terminating on signal 15 from pid 1 (/usr/bin/tini)

Big sur worked, Monterey started doing the same thing instantly. Also I'd enable that option in my BIOS but for that I'd need to hook up a monitor to the PC and I'm too lazy to do that right now, will get on that tomorrow though.

That's weird as its an AMD Ryzen 2600. It should be relatively new I assume. I"ll try limiting the cores tomorrow and seeing if that works.

which suggest you need to enable the AMD CBS option in your BIOS.

I've tried searching for an option with the name "AMD CBS" but was only able to find an entire category with a lot of options that I didn't understand so I left those alone. I have also updated my BIOS in case that fixed anything but nothing good came out of that.
Moreover, running Big Sur with anything but the default core / ram amount triggers the same issue as with the other MacOS versions. The VM boots but hangs at an apple logo.

        Logs from the Somona container after upgrading BIOS:

❯ Starting macOS for Docker v1.05...
❯ For support visit https://github.com/dockur/macos
❯ CPU: AMD Ryzen 5 2600 Six Core Processor | RAM: 26/32 GB | DISK: 283 GB (ext4) | HOST: 6.1.0-0.deb11.18-amd64...
❯ Downloading macOS Sonoma recovery image...
Downloading 694-88583...
Saving http://oscdn.apple.com/content/downloads/17/05/052-32968/ncxjjpfvl0w3kfzu3du0hqp06rqqic1c7u/RecoveryImage/BaseSystem.chunklist to /storage/tmp/BaseSystem.chunklist...
0.002887725830078125 MBs downloaded...
Download complete!

Download complete!
Verifying image with chunklist...

❯ Creating a 64G growable disk image in raw format...
❯ Extracting boot image...
❯ Warning: unexpected clocksource: hpet
❯ Booting macOS 1920x1080 using QEMU v8.2.4...
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
3h3h3hBdsDxe: failed to load Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0xA,0x0): Not Found
BdsDxe: loading Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
#[EB|LOG:EXITBS:END] _
#[EB.BST.FBS|-]
#[EB|B:BOOT]
#[EB|LOG:HANDOFF TO XNU] _
======== End of efiboot serial output. ========
3h3h3hBdsDxe: failed to load Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0xA,0x0): Not Found
BdsDxe: loading Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
#[EB|LOG:EXITBS:END] _
#[EB.BST.FBS|-]
#[EB|B:BOOT]
#[EB|LOG:HANDOFF TO XNU] _
======== End of efiboot serial output. ========
3h3h3hBdsDxe: failed to load Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0xA,0x0): Not Found
BdsDxe: loading Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
qemu-system-x86_64: terminating on signal 15 from pid 1 (/usr/bin/tini)

        Logs from Big Sur container with changed CPU / RAM values:

❯ Starting macOS for Docker v1.05...
❯ For support visit https://github.com/dockur/macos
❯ CPU: AMD Ryzen 5 2600 Six Core Processor | RAM: 26/32 GB | DISK: 282 GB (ext4) | HOST: 6.1.0-0.deb11.18-amd64...
❯ Downloading macOS Big-sur recovery image...
Downloading 694-35959...
Saving http://oscdn.apple.com/content/downloads/41/28/071-71279/5djpevqmc2w0ti2c4n1m8mkz7fm791t1ic/RecoveryImage/BaseSystem.chunklist to /storage/tmp/BaseSystem.chunklist...
0.002475738525390625 MBs downloaded...
Download complete!

Download complete!
Verifying image with chunklist...

❯ Creating a 64G growable disk image in raw format...
❯ Extracting boot image...
❯ Warning: unexpected clocksource: hpet
❯ Booting macOS 1920x1080 using QEMU v8.2.4...
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
3h3h3hBdsDxe: failed to load Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0xA,0x0): Not Found
BdsDxe: loading Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
#[EB|LOG:EXITBS:END] _
#[EB.BST.FBS|-]
#[EB|B:BOOT]
#[EB|LOG:HANDOFF TO XNU] _
======== End of efiboot serial output. ========
qemu-system-x86_64: terminating on signal 15 from pid 1 (/usr/bin/tini)

I copy and pasted the example docker-compose text and then changed the values to my liking
    environment:
      VERSION: "big-sur"
      RAM_SIZE: "6G"
      CPU_CORES: "6"

Yes, setting it to 1 core did work for sonoma.

I pulled the latest version of the container and modified my docker-compose file a bit so that the storage is actually persistent but it still fails to boot on sonoma. Here's my docker-compose file and container logs
services:
  macos:
    image: dockurr/macos
    container_name: macos-sonoma
    environment:
      VERSION: "sonoma"
      RAM_SIZE: "6G"
      CPU_CORES: "8"
      DEBUG: "yes"
    devices:
      - /dev/kvm
    volumes:
      - /srv/dev-disk-by-uuid-6f21d0e1-eec4-44f3-a95d-b36aa9e60448/MacOS/sonoma:/storage
    cap_add:
      - NET_ADMIN
    ports:
      - 8006:8006
      - 5900:5900/tcp
      - 5900:5900/udp
    stop_grace_period: 2m

        Container logs:

  ❯ Starting macOS for Docker v1.06...
❯ For support visit https://github.com/dockur/macos
❯ CPU: AMD Ryzen 5 2600 Six Core Processor | RAM: 9/32 GB | DISK: 67 GB (ext4) | HOST: 6.1.0-0.deb11.18-amd64...
❯ Host: 5a31004e6f3f  IP: <IP_ADDRESS>  Gateway: <IP_ADDRESS>  Interface: eth0  MAC: 02:69:8A:B7:91:C6
nameserver <IP_ADDRESS>
❯ Warning: unexpected clocksource: hpet
Arguments:
-nodefaults
-cpu Haswell-noTSX,kvm=on,l3-cache=on,+hypervisor,+invtsc,vendor=GenuineIntel,vmware-cpuid-freq=on,-pdpe1gb,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+avx2,+aes,+fma,+bmi1,+bmi2,+smep,+xsave,+xsavec,+xsaveopt,+xgetbv1,+movbe,+rdrand,check
-smp 8,sockets=8,dies=1,cores=1,threads=1
-m 6G
-machine type=q35,smm=off,graphics=off,vmport=off,dump-guest-core=off,hpet=off,accel=kvm
-enable-kvm
-global kvm-pit.lost_tick_policy=discard
-display vnc=:0,websocket=5700
-vga vmware
-monitor telnet:localhost:7100,server,nowait,nodelay
-name macos,process=macos,debug-threads=on
-serial mon:stdio
-device nec-usb-xhci,id=xhci
-device usb-kbd,bus=xhci.0
-global nec-usb-xhci.msi=off
-device usb-tablet
-netdev tap,id=hostnet0,ifname=qemu,script=no,downscript=no
-device virtio-net-pci,romfile=,netdev=hostnet0,mac=02:69:8A:B7:91:C6,id=net0
-device virtio-blk-pci,drive=InstallMedia,scsi=off,bus=pcie.0,addr=0x6
-drive file=/storage/base.dmg,id=InstallMedia,format=dmg,cache=unsafe,readonly=on,if=none
-drive file=/storage/data.img,id=data3,format=raw,cache=none,aio=native,discard=on,detect-zeroes=on,if=none
-device virtio-blk-pci,drive=data3,scsi=off,bus=pcie.0,addr=0xa,iothread=io2,bootindex=3
-object iothread,id=io2
-device virtio-blk-pci,drive=OpenCore,scsi=off,bus=pcie.0,addr=0x5,bootindex=10
-drive file=/storage/boot.img,id=OpenCore,format=raw,cache=unsafe,readonly=on,if=none
-smbios type=2
-rtc base=utc,base=localtime
-global ICH9-LPC.disable_s3=1
-global ICH9-LPC.disable_s4=1
-global ICH9-LPC.acpi-pci-hotplug-with-bridge-support=off
-device isa-applesmc,osk=ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc
-drive if=pflash,format=raw,readonly=on,file=/storage/macos.rom
-drive if=pflash,format=raw,file=/storage/macos.vars
-object rng-random,id=objrng0,filename=/dev/urandom
-device virtio-rng-pci,rng=objrng0,id=rng0,bus=pcie.0,addr=0x1c
-device virtio-balloon-pci,id=balloon0,bus=pcie.0,addr=0x4
❯ Booting macOS 1920x1080 using QEMU v8.2.4...
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
3h3h3hBdsDxe: failed to load Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0xA,0x0): Not Found
BdsDxe: loading Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
#[EB|LOG:EXITBS:END] _
#[EB.BST.FBS|-]
#[EB|B:BOOT]
#[EB|LOG:HANDOFF TO XNU] _
======== End of efiboot serial output. ========
qemu-system-x86_64: terminating on signal 15 from pid 1 (/usr/bin/tini)
❯ Starting macOS for Docker v1.06...
❯ For support visit https://github.com/dockur/macos
❯ CPU: AMD Ryzen 5 2600 Six Core Processor | RAM: 9/32 GB | DISK: 67 GB (ext4) | HOST: 6.1.0-0.deb11.18-amd64...
❯ Host: 5a31004e6f3f  IP: <IP_ADDRESS>  Gateway: <IP_ADDRESS>  Interface: eth0  MAC: 02:69:8A:B7:91:C6
nameserver <IP_ADDRESS>
❯ Warning: unexpected clocksource: hpet
Arguments:
-nodefaults
-cpu Haswell-noTSX,kvm=on,l3-cache=on,+hypervisor,+invtsc,vendor=GenuineIntel,vmware-cpuid-freq=on,-pdpe1gb,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+avx2,+aes,+fma,+bmi1,+bmi2,+smep,+xsave,+xsavec,+xsaveopt,+xgetbv1,+movbe,+rdrand,check
-smp 8,sockets=8,dies=1,cores=1,threads=1
-m 6G
-machine type=q35,smm=off,graphics=off,vmport=off,dump-guest-core=off,hpet=off,accel=kvm
-enable-kvm
-global kvm-pit.lost_tick_policy=discard
-display vnc=:0,websocket=5700
-vga vmware
-monitor telnet:localhost:7100,server,nowait,nodelay
-name macos,process=macos,debug-threads=on
-serial mon:stdio
-device nec-usb-xhci,id=xhci
-device usb-kbd,bus=xhci.0
-global nec-usb-xhci.msi=off
-device usb-tablet
-netdev tap,id=hostnet0,ifname=qemu,script=no,downscript=no
-device virtio-net-pci,romfile=,netdev=hostnet0,mac=02:69:8A:B7:91:C6,id=net0
-device virtio-blk-pci,drive=InstallMedia,scsi=off,bus=pcie.0,addr=0x6
-drive file=/storage/base.dmg,id=InstallMedia,format=dmg,cache=unsafe,readonly=on,if=none
-drive file=/storage/data.img,id=data3,format=raw,cache=none,aio=native,discard=on,detect-zeroes=on,if=none
-device virtio-blk-pci,drive=data3,scsi=off,bus=pcie.0,addr=0xa,iothread=io2,bootindex=3
-object iothread,id=io2
-device virtio-blk-pci,drive=OpenCore,scsi=off,bus=pcie.0,addr=0x5,bootindex=10
-drive file=/storage/boot.img,id=OpenCore,format=raw,cache=unsafe,readonly=on,if=none
-smbios type=2
-rtc base=utc,base=localtime
-global ICH9-LPC.disable_s3=1
-global ICH9-LPC.disable_s4=1
-global ICH9-LPC.acpi-pci-hotplug-with-bridge-support=off
-device isa-applesmc,osk=ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc
-drive if=pflash,format=raw,readonly=on,file=/storage/macos.rom
-drive if=pflash,format=raw,file=/storage/macos.vars
-object rng-random,id=objrng0,filename=/dev/urandom
-device virtio-rng-pci,rng=objrng0,id=rng0,bus=pcie.0,addr=0x1c
-device virtio-balloon-pci,id=balloon0,bus=pcie.0,addr=0x4
❯ Booting macOS 1920x1080 using QEMU v8.2.4...
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
3h3h3hBdsDxe: failed to load Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0xA,0x0): Not Found
BdsDxe: loading Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
#[EB|LOG:EXITBS:END] _
#[EB.BST.FBS|-]
#[EB|B:BOOT]
#[EB|LOG:HANDOFF TO XNU] _
======== End of efiboot serial output. ========
3h3h3hBdsDxe: failed to load Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0xA,0x0): Not Found
BdsDxe: loading Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
#[EB|LOG:EXITBS:END] _
#[EB.BST.FBS|-]
#[EB|B:BOOT]
#[EB|LOG:HANDOFF TO XNU] _
======== End of efiboot serial output. ========
3h3h3hBdsDxe: failed to load Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0xA,0x0): Not Found
BdsDxe: loading Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0002 "UEFI Misc Device 2" from PciRoot(0x0)/Pci(0x5,0x0)
qemu-system-x86_64: terminating on signal 15 from pid 1 (/usr/bin/tini)

Nice it works now! Thank you so much for helping / making this. I ended up reinstalling the OS that's on my server so that the clocksource would be set to TSC as I managed to break it even further while trying to fix it.


Update F-Droid Descriptions

I updated the translations in the full_description.txt files using translations provided via Google Translate.

Fixes #275

Closes #275

Closes #275


fix: Correct typo in GoTrueClient warning message

What kind of change does this PR introduce?
This PR corrects the spelling of clock in a warning message in GoTrueClient.ts.
What is the current behavior?
@supabase_supabase-js.js?v=12ace510:5329 @supabase/gotrue-js: Session as retrieved from URL was issued in the future? Check the device clok for skew

What is the new behavior?
@supabase_supabase-js.js?v=12ace510:5329 @supabase/gotrue-js: Session as retrieved from URL was issued in the future? Check the device clock for skew

Additional context

Thanks for the contribution! And sorry for the trouble  - we use latest and the CI break is caused by the removal of Docker Compose v1 from the Ubuntu latest image I think

All updated @J0

Thanks for the contribution


MRTK3's Record Eye Gaze Sample is not working

Describe the bug
MRTK3's Record Eye Gaze Sample is not working
To reproduce
Steps to reproduce the behavior:

Go to 'EyeTrackingVisualizerExample.scene'
Click on 'Record Eye Gaze'
Look and heat map target on the left and on the right
Click on 'Stop recording'
Click 'Play recording'
Nothing plays

Expected behavior
The heat map recording to play

Fixed with

https://github.com/microsoft/MixedRealityToolkit-Unity/pull/11744


App crash with open drawer (version 1.0)

When I try open Drawer, application crashed.
<Drawer open={true}>Test</Drawer>

Cannot read property 'call' of undefined
TypeError: Cannot read property 'call' of undefined
    at ProxyComponent.hotComponentRender (node_modules/react-hot-loader/dist/react-hot-loader.development.js:579:0)
    at ProxyComponent.proxiedRender (node_modules/react-hot-loader/dist/react-hot-loader.development.js:587:0)
    at finishClassComponent (node_modules/react-dom/cjs/react-dom.development.js:8389:0)
    at updateClassComponent (node_modules/react-dom/cjs/react-dom.development.js:8357:0)
    at beginWork (node_modules/react-dom/cjs/react-dom.development.js:8982:0)
    at performUnitOfWork (node_modules/react-dom/cjs/react-dom.development.js:11814:0)
    at workLoop (node_modules/react-dom/cjs/react-dom.development.js:11843:0)
    at renderRoot (node_modules/react-dom/cjs/react-dom.development.js:11874:0)
    at performWorkOnRoot (node_modules/react-dom/cjs/react-dom.development.js:12449:0)
    at performWork (node_modules/react-dom/cjs/react-dom.development.js:12370:0)

    in EventListener (created by Slide)
    in Slide (created by WithTheme(Slide))
    in WithTheme(Slide) (created by Drawer)
    in RootRef (created by Modal)
    in div (created by Modal)
    in Portal (created by Modal)
    in Modal (created by WithStyles(Modal))
    in WithStyles(Modal) (created by Drawer)
    in Drawer (created by WithStyles(Drawer))
    in WithStyles(Drawer) (at HomePageContainer.tsx:29)
    in div (created by Grid)
    in Grid (created by GridWrapper)
    in GridWrapper (created by WithStyles(GridWrapper))
    in WithStyles(GridWrapper) (at HomePageContainer.tsx:28)
    in div (created by Grid)
    in Grid (created by GridWrapper)
    in GridWrapper (created by WithStyles(GridWrapper))
    in WithStyles(GridWrapper) (at HomePageContainer.tsx:27)
    in Container (at index.tsx:5)
    in Component (at app.tsx:29)
    in div (at Content.tsx:12)
    in Component (created by WithStyles(Component))
    in WithStyles(Component) (at PageContainer.tsx:55)
    in Container (created by Connect(Container))
    in Connect(Container) (at app.tsx:28)
    in Component (at withMaterialUi.tsx:95)
    in Component (created by WithStyles(Component))
    in WithStyles(Component) (at withMaterialUi.tsx:94)
    in MuiThemeProvider (created by Component)
    in JssProvider (at withMaterialUi.tsx:91)
    in Component (created by Connect(Component))
    in Connect(Component) (created by InjectIntl(Connect(Component)))
    in InjectIntl(Connect(Component)) (created by PageWithIntl)
    in IntlProvider (at withIntl.tsx:37)
    in PageWithIntl (at withApolloProvider.tsx:52)
    in ApolloProvider (at withApolloProvider.tsx:51)
    in PageWithApollo (created by Connect(PageWithApollo))
    in Connect(PageWithApollo) (created by Connect(Connect(PageWithApollo)))
    in Connect(Connect(PageWithApollo)) (created by WrappedCmp)
    in Provider (created by WrappedCmp)
    in WrappedCmp (created by App)
    in Container (created by App)
    in App
    in AppContainer

Dependencies
  "dependencies": {
    "@material-ui/core": "1.0.0",
    "@material-ui/icons": "1.0.0",
    "accepts": "1.3.5",
    "apollo-boost": "0.1.6",
    "apollo-server-express": "1.3.6",
    "autoprefixer": "8.5.0",
    "body-parser": "1.18.3",
    "dotenv": "5.0.1",
    "express": "4.16.3",
    "glob": "7.1.2",
    "graphql": "0.13.2",
    "graphql-import": "0.5.2",
    "graphql-tag": "2.9.2",
    "graphql-tools": "3.0.1",
    "intl": "1.2.5",
    "isomorphic-fetch": "2.2.1",
    "next": "6.0.3",
    "next-redux-wrapper": "1.3.5",
    "nprogress": "0.2.0",
    "postcss": "6.0.22",
    "react": "16.3.2",
    "react-apollo": "2.1.4",
    "react-dom": "16.3.2",
    "react-intl": "2.4.0",
    "react-redux": "5.0.7",
    "redux": "4.0.0",
    "redux-actions": "2.3.2",
    "redux-form": "7.3.0",
    "redux-thunk": "2.2.0",
    "reselect": "3.0.1"
  },
  "devDependencies": {
    "@types/accepts": "1.3.5",
    "@types/express": "4.11.1",
    "@types/glob": "5.0.35",
    "@types/intl": "1.2.0",
    "@types/isomorphic-fetch": "0.0.34",
    "@types/jest": "22.2.3",
    "@types/next": "2.4.10",
    "@types/next-redux-wrapper": "1.4.1",
    "@types/node": "10.1.0",
    "@types/nprogress": "0.0.29",
    "@types/react": "16.3.14",
    "@types/react-intl": "2.3.8",
    "@types/redux-actions": "2.3.0",
    "@types/redux-form": "7.2.5",
    "@zeit/next-typescript": "1.0.0",
    "apollo-codegen": "0.19.1",
    "babel-plugin-react-intl": "2.4.0",
    "coveralls": "3.0.1",
    "graphql-code-generator": "0.9.1",
    "graphql-codegen-typescript-template": "0.9.1",
    "husky": "0.14.3",
    "jest": "22.4.4",
    "nodemon": "1.17.4",
    "prettier": "1.12.1",
    "pretty-quick": "1.4.1",
    "rimraf": "2.6.2",
    "ts-jest": "22.4.6",
    "ts-node": "6.0.3",
    "tslint": "5.10.0",
    "tslint-config-prettier": "1.12.0",
    "tslint-react": "3.6.0",
    "typescript": "2.8.3"
  }

I found problem.
'react-event-listener'
When I downgrade to "0.5.3", application is correct.

How can I reproduce the problem?

It's very hard :)
I have open repository: https://github.com/ApiTreeCZ/alda (dev branch)
When I remove dependency: "react-event-listener", clear package-lock.json and run: npm i && npm run dev
In app is left menu in top corner (open Drawer)

A create branch with this issue: https://github.com/ApiTreeCZ/alda/tree/issue-11528
For reproduce:
npm i && npm run dev

In browser: localhost:8080

I'm not sure what to think about it. The error seems to be coming from react-hot-loader.

It's working fine with<EMAIL_ADDRESS>

So, the issue was introduced with one of:

https://github.com/oliviertassinari/react-event-listener/pull/73/files
https://github.com/oliviertassinari/react-event-listener/pull/74/files (unlikely)
https://github.com/oliviertassinari/react-event-listener/pull/76/files

cc @TrySound

@oliviertassinari Well... next.js just replaces babel helpers (47) with own (42) and they behave differently. inherits helper from 42 just resets prototype after methods assigning.
Blame next.js!

Here's the structure. How do you think runtime should be resolved? But they are resolved to 42
-react-event-listener
-@babel
-- runtime (47)
-next
--node_modules
----@babel
-----runtime (42)

I have released<EMAIL_ADDRESS>following @TrySound advice. Can anyone confirm the problem is fixed?

@oliviertassinari This won't fix next js behaviour. They just forces us to stick with babel runtime 42. Why they do this?

I try versiom 0.5.7 but no success :(

@oliviertassinari Thanks for providing a version that fixes this issue. How can I use it now with next and @material-ui/core?
If you install my sample repo that demonstrates this problem, and yarn install, you get the latest versions of each package at the present time. react-event-listener is not a direct dependency listed in package.json, and the packages that use react-event-listener use older versions of it --
├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>
├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>
├─<EMAIL_ADDRESS>
I'm assuming the critical dependency for this issue is from<EMAIL_ADDRESS>Will I have to wait for the next version of @material-ui/core, etc. to get 0.5.8 of react-event-listener?

@TrySound That works. Thank you.

Just a note to say this is still broken for me with<EMAIL_ADDRESS>I have to manually specify "react-event-listener": "0.5.5" in my package.json to fix

#12407

Confirmed fixed in 0.20.2.

Sounds related to my issue with @babel/runtime conflicting versions from @material-ui/core 1.5.1 (7.0.0-rc.1) and react-event-listener 0.6.2 (7.0.0-beta.42).
https://github.com/mui-org/material-ui/issues/12587

@Fandekasp see if you have other @material-ui packages that contradict, I had an older @material-ui/icons which caused the contradiction with @material-ui/core 1.51

@eyalap  I only have one instance of material-ui
$ find node_modules -name '*material-ui'
node_modules/material-ui
node_modules/@material-ui

But the packages inside indeed have different versions:
$ for dir in node_modules/@material-ui/*; do echo $dir; cat $dir/package.json|grep version; done
node_modules/@material-ui/core
  "version": "1.5.1",
node_modules/@material-ui/icons
  "version": "2.0.3",

But these versions match yours.
As described in https://github.com/mui-org/material-ui/issues/12587#issuecomment-414217894, the problem seems to be that material-ui is searching for files in the wrong babel/runtime directory. No idea why, how to fix this issue, and building a full reproduction test case might take a lot of time, so I won't be able to do it soon.


autocomplete problem with type command

So my problem is that when inserting some text using type command, autocomplete seems active and destroy my flow.
For exemple: the output of this macros is "something()" i don't want the closing parentheses.
"macros" : {
    "doStuff": [{
        "command": "type", "args": { "text" : "something("}
     }]
}

If it can helps someone, I found this trick to avoid my autocomplete problems :
"mymacro" : [
{"command": "type",
"args": {
"text": "' . some_function()" //write the 2 parentheses
}
},
{"command": "deleteLeft"} //delete the second one
]

@rthoreau nice trick, i like it 👍


Corrected terminology and other things

There is no such thing as a WSFC cluster. It's a WSFC - Windows Server Failover Cluster. I've fixed this elsewhere. I know I wrote this right when I wrote it for docs so somethign happened.
Added a reference to Pacemaker since it's applicable there, too.

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

Also, it looks like you pulled the note which needs to come back - Never use DAG for a distributed AG. Why was that section deleted? That is a recent deletion.


Fix typo in output of install_autocomplete()

The output of install_autocomplete() says "restart you bash session". This just changes it to read "your session".

Thanks :)


[Feature Request] Direct activation hotkey

Great work with this plugin!

Currently I have to open PowerToys Run and then type the activation command every time I want to see the list.  A direct hotkey would be more convenient.  Is this possible?
I'd like the option to just copy the selected option to my clipboard.  Currently, the plugin pastes the result after I select it.  Can you make the direct paste behavior toggleable?

Hey @R-Bower, Thanks!

This is a cool idea but as far as I know not something that is supported by PowerToys Run, to make usage easier you have a couple options, firstly you can enable Clipboard Manager to show in global results so you can immediately search without having to enter the activation command (though this wont give you the list of history as entering the activation command would). Secondly, you can change the activation shortcut to something different (maybe try just 'c') so that pressing Alt+Space (or whatever shortcut you use) then 'c' opens the history which may be a bit more convenient than 'c:'. The other option I can think of would be setting up a custom mapping if you have a keyboard that supports it or using something like AutoHotKey to perform the actions when you click a certain key combination could work too.
This is a great idea too and definitely something I can do, I'll update you once this is added and a release is available :)

Hi @R-Bower,
Just wanted to let you know your second point is now available in the latest release!


Trying to implement Docz on a project with native-base

Question
Hey, guys. I'm trying to document my React-Native project using Docz. Thing is my project is using Native-Base.
Description
When I try to build, I keep getting this error:
./node_modules/native-base-shoutem-theme/src/StyleProvider.js 10:19
Module parse failed: Unexpected token (10:19)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|  */
| export default class StyleProvider extends React.Component {
>   static propTypes = {
|     children: PropTypes.element.isRequired,
|     style: PropTypes.object,

This is my doczrc.js file:
import { reactNative } from 'docz-plugin-react-native';

export default {
  title: 'Recarga Styleguide',
  plugins: [reactNative()],
  native: true,
  src: './app/components/ui/' // <== where the components are located inside the project
};

I've been researching and it seems to be quite a common error with Native-Base.
I found this solution in stackoverflow:
[https://stackoverflow.com/questions/56586865/expo-for-web-failed-to-compile-because-of-native-base-module](Expo for Web failed to compile because of native base module)
I suspect this solution might work for me, thing is: I don't think my project is using expo. I think I would like to try some setting on my babel.config or metro.config file, but I'm not sure how it would work.
Could you help me?
Thanks!

Hey @ecalvi
Unfortunately my experience with native-base is very limited.
Any chance you can provide an example repo that I ( or someone ) could look into ?

Also, which docz version are you using ?

@ecalvi docz no longer uses that plugin for native. It was moved to a default config option like:
// doczrc.js

import pkg from "./package.json";
export default {
  title: pkg.name,
  native: true,
  ...
};

Even with this setting, I had some issues with the v2 rc branches which I fixed by adding an alias the gatsby webpack hook docz kindly exposes, like this:
// gatsby-node.js
const path = require("path");

const ROOT = "../";

exports.onCreateWebpackConfig = ({ actions }) => {
  actions.setWebpackConfig({
    resolve: {
      alias: {
        "react-native": path.resolve(ROOT, "node_modules/react-native-web"),
        ...
      },
      ...
    }
  });
};

Hope that helps!

Hey, guys! Thank you all for your help. I can't share the code because it's a company project.
But I will try to share more code than I did.
Regarding version, @rakannimer (thanks for the btw): I tried v2 but it forced me to install yarn and for what I've read it didn't seem to be too stable yet, so I got back to v1.
But I keep getting that same error:
./node_modules/native-base-shoutem-theme/src/StyleProvider.js 10:19
Module parse failed: Unexpected token (10:19)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|  */
| export default class StyleProvider extends React.Component {
>   static propTypes = {
|     children: PropTypes.element.isRequired,
|     style: PropTypes.object,

I always end up there. No matter which path I travel.
Again, I think its Native Base related. I'm starting to hate Native Base but it's in the project nonetheless, so I'll have to cope for now. :-p
I had to freeze the documentation task for the moment, but I will get back to this in the next few days because I would really like to use Docz in my project, I think it's a very cool tool.
Thanks for all the help!

I keep hitting that same wall no matter what I do. :___(
I'm adding here my webpack config file:
module.exports = {
  presets: ['module:metro-react-native-babel-preset', 'module:react-native-dotenv'],
  plugins: [
    [
      'transform-rename-import',
      {
        replacements: [
          { original: 'react-native-vector-icons/Ionicons', replacement: '../../../../../app/components/icon' }
        ]
      }
    ],
    [
      'jsx-property-alias',
      {
        properties: {
          testID: 'accessibilityLabel'
        }
      }
    ],
    ['transform-inline-environment-variables']
  ],
  env: {
    production: {
      plugins: ['transform-remove-console']
    }
  }
};

I tried adding 'module:native-base-shoutem-theme' into presets to try the solution mentioned here Expo for Web failed to compile because of native base module and I got a different crash:
Error: Cannot find module 'react-docgen/dist/babylon'
That, I'm seeing, seems to be related to Docs (727, 822) but it is an earlier crash, so I'm assuming it's not a good idea to go that way.
The crash appears after I run= the docz dev, the original crash appears later during the compilation.
I'm not sure what to try next, because I don't have a clue of what could be causing this error.


Team update - Aug 24, 2022

This is a @Quansight-Labs/czi-a11y-grant team sync 🎉🎉🎉! This is a way for the Team Members to provide status reports on what they've been up to this week and request help and attention for things they are working on. This issue will be closed at the end of the day.
Copy and paste the template below, and answer questions as you wish!

Response Template
**Thanks I'd like to give 🙌**
- So-and-so helped me out a lot with foo...

**Updates from last week :heavy_check_mark:**
- I worked towards deliverable: <link-to-deliverable>

**Challenges I faced and things I'd like assistance with 🙏**
- I had a hard time figuring out ...

**My availability for next week**
- I'll be off on foo day...

**Important items for discussion 💬**
- I have a question about goal <link-to-goal>
- Can @foo give a comment on issue #NN ?
- I opened #NN for discussion, please chime in
- I need to discuss foo

:mag: Needs Triage
The Needs Triage issues require an initial assessment and labeling.

Rendered notebook user testing - Round 1

:dart: Project boards
Please make sure the boards reflect the current status of the project.
Jupyter a11y grant project

Thanks I'd like to give 🙌

@isabela-pf for letting me work with her on an interesting blog post
@steff456 for agreeing to help @kulsoomzahra navigate the zoom-related issues in JupyterLab
@trallard for keeping eyes and ears open for new opportunities to bring more support to this team's work (Berkeley)

Updates from last week :heavy_check_mark:

https://github.com/jupyterlab/lumino/pull/373. There are still other tab traps that need fixing in JupyterLab, but the one in the Lumino menu bar was probably the worst offender. I'm not sure when this will get rolled out to end users, though — need to check with Darian or Frederic.
https://github.com/Quansight-Labs/jupyter-a11y-testing/issues/13. I've branched locally and started writing (refactoring) code, but I won't be able to finish this until next week. I will get in touch with @tonyfast next week if I have any questions or hit any walls.
Had Q&A with Tania, Isabela, and Berkeley's dev team about the state of accessibility in JupyterLab
Had chat with Kulsoom about which accessibility issues she wants to work on. She will let you know in her update.

My availability for next week

I'm off Thursday-Monday, August 25-29.
I will be working from plane (flying to the USA) on Wednesday, August 31.

Thanks I'd like to give 🙌

@isabela-pf for always being super helpful

Updates from last week :heavy_check_mark:

I worked in the blurry python 3 icon present in the Launcher

Challenges I faced and things I'd like assistance with 🙏

I'm having a hard time finding the actual asset for the icon, I decided to create an issue to seek for some guidance: https://github.com/jupyterlab/jupyterlab/issues/12997.
Start organizing future tasks for fixing Zoom issues

My availability for next week

I'll be here!

Important items for discussion 💬

Future zoom related tasks

Thanks I'd like to give 🙌
Updates from last week :heavy_check_mark:

#146. User tests are happening! I don't have any documented updates while we're in the middle of it, but I am excited to report back when we get there.
#132. Made some changes to the draft event content based on feedback, but it's still in draft. I still need to make some slides before we can really test it, but I'd like to schedule something so I have a deadline.
#133. Has been on the back burner between testing time needed and some napari deadlines. This is going to be my main focus directly after this meeting. I did throw out one scoped solution for tabs on Slack that I'm willing to discuss in more detail if it's timely for anyone.

Challenges I faced and things I'd like assistance with 🙏

I have nothing to talk about.

My availability for next week

I'll be out of office September 1–September 5.

Important items for discussion 💬

Schedule event test run so that I have a deadline? Because I operate on deadlines? Maybe? 😅

Thanks I'd like to give 🙌

@tonyfast for demonstrating an overview of the many kind of issues on the project board
@gabalafou for helping me explore the areas where I could potentially work
@trallard @steff456 @isabela-pf for sharing resources and their thoughts

Updates from last week :heavy_check_mark:

Spent some time figuring out what I could work on and ended up with the Zoom issue
Tried understanding the Reflow criterion (1.4.10) of WCAG 2.1 and also Understanding Success Criterion

Challenges I faced and things I'd like assistance with 🙏

Nothing at the moment, thanks

My availability for next week

I'll be here

Items for discussion 💬

Something that quickly came up to my mind when we were thinking of solutions to items of the menu bar was:

Add a button that says Menu,  expanding on which gives all the menu items
Second Menu bar like two rows so that all items of the menu bar are visible (I'm not sure if this aligns with the guidelines, so I'll need to read about it)

@kulsoomzahra

Feels like colour contrast and zoom issues are something she could tackle -> sync with @steff456

@isabela-pf

Has been working on user tests (STScI): two left (this and the upcoming week)
Will try and make some progress on the reflow mocks: will work on her own sketches

there are still plenty of unknowns
@trallard  was reading this https://stephaniewalter.design/blog/a-designers-guide-to-documenting-accessibility-user-interactions/
12th September - team's rundown of the event

@steff456

Make a PR to ipykernel
Right now, and apparently only supports png (i.e. 64x64)
Will sync with Matthias on how to submit this change
Started organizing future tasks for fixing Zoom issues

@isabela-pf  mentioned TABS-related fixes could be well scoped for Kulsoom
skiplink stuff: there are notes and should also be well scoped

📓 Misc notes:

Related to zoom: how is the experience related to code wrapping in 400% zoom


Prevent third-party libraries from repeatedly importing vue

一些第三方库在引入vue.js到时候，使用如下配置
Some third-party libraries use this configuration when use vue.js
...
externals:  {
    vue: {
      commonjs: 'vue',
      commonjs2: 'vue',
      amd: 'vue',
      root: 'Vue',
      var: 'Vue'
    }
  }
...

这使得本地项目在引入第三方库并且打包的时候重新引入vue
此时，打包第三方库时如（vue-material）,第三方库会引入（vue-material/node_modules/vue/dist/vue.esm.js）
It wiil import vue into packaged duplicate

因此，修改此处别名
Therefore, change the 'vue' of alias to 'path.resolve(__dirname, '../node_modules/vue/dist/vue.esm.js'),'
// build/webpack.base.conf.js
resolve: {
    extensions: ['.js', '.vue', '.json'],
    alias: {
       'vue$': path.resolve(__dirname, '../node_modules/vue/dist/vue.esm.js'),
      '@': resolve('src')
    }
  },

使得webpack打包的时候，始终是打包到同一个vuejs
Then, it will import vue once time

Wow, good find!
Will check this out this weekend.

@chrisvfritz This would probably also be relevant for the docs.

I don't think this is actually a good idea. The real problem is that vue-material has listed Vue as a dependency, which means they specifically want to package their own version of Vue into the library. This is most likely a mistake and what they really want is to list Vue as a peer dependency. That's the correct way to avoid bundling the same package twice.

@chrisvfritz get! I think you are right! Thanks for your check out this pr.


CORE-6580 use error code 409 for WrongConfigVersionException

This PR changes error response code to be 409 when a config is updated with an incorrect version.
This also moves two exceptions from components/configuration/configuration-write-service to libs/configuration/configuration-core/exception to make them visable to components/configuration/configuration-rpcops-service-impl
I have tested this manually against the combined worker by trying to update an existing version with an incorrect version number as in the task description.
https://r3-cev.atlassian.net/browse/CORE-6580

Actually not sure I agree with moving ConfigWriteServiceException exception in configuration-core as it doesn't have to do with the module at all, i.e. is not part of its API as it cannot be thrown by any api of the module. To fair it shouldn't even be in configuration-write-service api module as it also cannot be thrown by any of configuration-write-service (public) apis, (although more relevant there) but rather defined internally in configuration-write-service-impl, but then we need to reference it somehow in configuration-rpcops-service-impl module.

Actually not sure I agree with moving ConfigWriteServiceException exception in configuration-core as it doesn't have to do with the module at all, i.e. is not part of its API as it cannot be thrown by any api of the module. To be fair it shouldn't even be in configuration-write-service api module as it also cannot be thrown by any of configuration-write-service (public) apis, (although more relevant there) but rather defined internally in configuration-write-service-impl, but then we need to reference it somehow in configuration-rpcops-service-impl module.

I don't think we have ConfigWriteServiceException now. It's just ConfigException and ConfigVersionConflictException, which seem both generic enough that I think they can live in the core module. Do you not agree, @kyriathar ?

Had a chat with Dries and moved ConfigWriteServiceException back to configuration-write-service. But left the WrongConfigVersionException in libs/configuration/configuration-core as it's fairly generic. This way we still have access to it in both configuration-rpcops-service-impl and configuration-write-service.


feat: add img_tag_options to ix_picture_tag

Description
As suggested in #40 and #101, this PR adds an img_tag_options argument for ix_picture_tag. This can be used to futher customize the generated tags. It also updates the specs and README for documentation.
You can check the spec changes to see how this can be used.
Since this only adds an additional optional parameter, I don't expect any incompatibilities and therefore would not consider this a breaking change.
Checklist

[x] Read the contributing guidelines.
[x] Each commit follows the Conventional Commit spec format.
[x] Update the readme (if applicable).
[x] Update or add any necessary API documentation (if applicable)
[x] All existing unit tests are still passing (if applicable).

[ ] Add some steps so we can test your bug fix or feature (if applicable).
[x] Add new passing unit tests to cover the code introduced by your PR (if applicable).
[x] Any breaking changes are specified on the commit on which they are introduced with BREAKING CHANGE in the body of the commit.
[x] If this is a big feature with breaking changes, consider opening an issue to discuss first. This is completely up to you, but please keep in mind that your PR might not be accepted.

Hi @sherwinski
Thanks for reviewing the PR and considering the changes.

I got some feedback from the team regarding the naming of this attribute. If it's not too much trouble, do you think you can rename it to html_attributes instead? This will help us remain consistent with our naming elsewhere throughout our kit.

Thanks for checking in with the team. Consistency matters a lot in an API and changing the name is obviously and easy fix. But I'm not sure html_attributes is the best solution. I don't know how much discussion you already had. So please forgive me if I'm adding my 2 cents. If you still want to have it changed, I'll happily oblige.
The helper generates two HTML elements: a picture and an img. With your suggestion, the helper would have two options: tag_options and html_attributes. For once this introduces inconsistences - why use _attributes and _options. And then: How would the user know which is which? Both HTML and Tag suggest that it's going to be additional options for the generated HTML tag. But since we're generating two of those (a picture and a nested img), you wouldn't know which is which.
Since the ix_image_tag also has tag_options, and those affect the main generated element, it makes sense to have tag_options for ix_picture_tag as well. And consequentily they should affect the picture tag. In this way, tag_options is very similar to the html_attributes you have in React.
In order to give the library user a hint at what the parameter does, I think img_tag_options is both in line with the other convertions (using the _tag_option suffix) and tell the user which element is affected.
When you generally want to rename or alias tag_options to html_attributes to match the react naming, that's probably a different discussion/PR.

Hey @schmidt
I think you made some great points and mentioned some drawbacks to the proposed change that we missed. Given that, we are happy to move forward with your PR as-is and revisit renaming this in the future.


live preview was cancelled because developer tools were opened

Prerequisites

[ ] Can you reproduce the problem with Debug -> Reload Without Extensions?
[ ] Did you perform a cursory search to see if your bug or enhancement is already reported?
[ ] Did you read the Troubleshooting guide?

For more information on how to write a good bug report read here
For more information on how to contribute read here
Description
[Description of the bug or feature]
Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Expected behavior: [What you expected to happen]
Actual behavior: [What actually happened]
Versions
Please include the OS and what version of the OS you're running.
Please include the version of Brackets. You can find it under Help -> About Brackets (Windows and Linux) or Brackets -> About Brackets (macOS)

Hi @hamish100,
Sadly it's currently not possible to use the developer tools while live previewing.

Hi Peter
Thanks I won’t die wondering :)

On 17 Oct 2017, at 5:01 pm, Pete Nykänen<EMAIL_ADDRESS>wrote:
Hi @hamish100 https://github.com/hamish100,
Sadly it's currently not possible to use the developer tools while live previewing.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/adobe/brackets/issues/13772#issuecomment-337136950, or mute the thread https://github.com/notifications/unsubscribe-auth/AJtYnxGVlRKsHh38RpTuAzeFdG5EFLAEks5stFDQgaJpZM4P58mu.

Chrome 63 adds support for a multi-client Remote Debugging, so this bug should no longer be an issue once it goes live


Support dynamically reloading custom file .csscomb.json file changes

Instead of using require which caches the result, check if file exists and then use it if it does, otherwise fall back to bundled config.

Fails, but due to formatting issues involving other modules.

Thanks!


fix(textfield): Disable pointer events for JS Component labels

Fixes issue where the label positioned on top of the text field
intercepts the click event the textfield needs to gain focused. This was
originally uncaught because textfield labels were always given a for
attribute pointing back to a uniquely ID'd textfield. We cannot,
however, assume this will always be the case.
[ci skip]

LGTM. Recommend rewording the commit to avoid confusion between pointer-events and Pointer Events, though. E.g. something like "fix(textfield): Disable default touch actions for JS Component labels".