Pi 4B not working with Hifiberry DAC2 HD

I had everything working beautifully before plugging in the DAC.

Raspberry Pi 4 Model B
Hifiberry DAC2 HD
balenaOS 2.60.1+rev5

I tried some things from #296 to no avail. The aux output isn't working either anymore.
Here are the logs from the audio container:
23.11.20 22:47:57 (-0500)  audio
23.11.20 22:47:57 (-0500)  audio  --- Audio ---
23.11.20 22:47:57 (-0500)  audio  Starting audio service with settings:
23.11.20 22:47:57 (-0500)  audio  - Pulse log level: NOTICE
23.11.20 22:47:57 (-0500)  audio  - Default output: DAC
23.11.20 22:47:57 (-0500)  audio
23.11.20 22:47:57 (-0500)  audio  Detected audio cards:
23.11.20 22:47:57 (-0500)  audio  0 Headphones bcm2835_headphonbcm2835Headphones-bcm2835Headphones
23.11.20 22:47:57 (-0500)  audio  1 sndrpihifiberry HifiberryDacplu-snd_rpi_hifiberry_dacplushd
23.11.20 22:47:57 (-0500)  audio
23.11.20 22:47:57 (-0500)  audio
23.11.20 22:48:26 (-0500)  audio  Setting audio routing rules. Note that this can be changed after startup.
23.11.20 22:48:26 (-0500)  audio  Routing 'balena-sound.input' to 'balena-sound.output'.
23.11.20 22:48:26 (-0500)  audio  Routing 'balena-sound.output' to 'alsa_output.dac.stereo-fallback'.
23.11.20 22:48:26 (-0500)  audio  W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified).
23.11.20 22:48:27 (-0500)  audio  E: [pulseaudio] module-loopback.c: No such sink.
23.11.20 22:48:27 (-0500)  audio  E: [pulseaudio] module.c: Failed to load module "module-loopback" (argument: "source="balena-sound.output.monitor" sink="alsa_output.dac.stereo-fallback""): initialization failed.
23.11.20 22:48:27 (-0500)  audio  E: [pulseaudio] main.c: Sink alsa_output.dac.stereo-fallback does not exist.
23.11.20 22:48:27 (-0500)  audio  W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
23.11.20 22:48:27 (-0500)  audio  W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

The audio jack doesn't seem to work either.
The output from running pactl list sinks in the audio container is as follows:
root@bec19b8c0a64:/usr/src# pactl list sinks
Sink #0
        State: SUSPENDED
        Name: alsa_output.bcm2835.stereo-fallback
        Description: Built-in Audio Stereo
        Driver: module-alsa-card.c
        Sample Specification: s16le 2ch 44100Hz
        Channel Map: front-left,front-right
        Owner Module: 6
        Mute: no
        Volume: front-left: 56210 /  86% / -4.00 dB,   front-right: 56210 /  86% / -4.00 dB
                balance 0.00
        Base Volume: 56210 /  86% / -4.00 dB
        Monitor Source: alsa_output.bcm2835.stereo-fallback.monitor
        Latency: 0 usec, configured 0 usec
        Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY
        Properties:
                alsa.resolution_bits = "16"
                device.api = "alsa"
                device.class = "sound"
                alsa.class = "generic"
                alsa.subclass = "generic-mix"
                alsa.name = "bcm2835 Headphones"
                alsa.id = "bcm2835 Headphones"
                alsa.subdevice = "0"
                alsa.subdevice_name = "subdevice #0"
                alsa.device = "0"
                alsa.card = "0"
                alsa.card_name = "bcm2835 Headphones"
                alsa.long_card_name = "bcm2835 Headphones"
                alsa.driver_name = "snd_bcm2835"
                device.bus_path = "/devices/platform/soc/fe00b840.mailbox/bcm2835_audio/sound/card0"
                sysfs.path = "/devices/platform/soc/fe00b840.mailbox/bcm2835_audio/sound/card0"
                device.form_factor = "internal"
                device.string = "hw:0"
                device.buffering.buffer_size = "131072"
                device.buffering.fragment_size = "131072"
                device.access_mode = "mmap+timer"
                device.profile.name = "stereo-fallback"
                device.profile.description = "Stereo"
                device.description = "Built-in Audio Stereo"
                alsa.mixer_name = "Broadcom Mixer"
                module-udev-detect.discovered = "1"
                device.icon_name = "audio-card"
        Ports:
                analog-output-headphones: Headphones (priority: 9900)
        Active Port: analog-output-headphones
        Formats:
                pcm

Sink #1
        State: SUSPENDED
        Name: alsa_output.1.stereo-fallback
        Description: Built-in Audio Stereo
        Driver: module-alsa-card.c
        Sample Specification: s16le 2ch 44100Hz
        Channel Map: front-left,front-right
        Owner Module: 7
        Mute: no
        Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% / 0.00 dB
                balance 0.00
        Base Volume: 65536 / 100% / 0.00 dB
        Monitor Source: alsa_output.1.stereo-fallback.monitor
        Latency: 0 usec, configured 0 usec
        Flags: HARDWARE DECIBEL_VOLUME LATENCY
        Properties:
                alsa.resolution_bits = "16"
                device.api = "alsa"
                device.class = "sound"
                alsa.class = "generic"
                alsa.subclass = "generic-mix"
                alsa.name = "HiFiBerry DAC+ HD HiFi pcm179x-hifi-0"
                alsa.id = "HiFiBerry DAC+ HD HiFi pcm179x-hifi-0"
                alsa.subdevice = "0"
                alsa.subdevice_name = "subdevice #0"
                alsa.device = "0"
                alsa.card = "1"
                alsa.card_name = "snd_rpi_hifiberry_dacplushd"
                alsa.long_card_name = "snd_rpi_hifiberry_dacplushd"
                alsa.driver_name = "snd_soc_hifiberry_dacplushd"
                device.bus_path = "/devices/platform/soc/soc:sound/sound/card1"
                sysfs.path = "/devices/platform/soc/soc:sound/sound/card1"
                device.form_factor = "internal"
                device.string = "hw:1"
                device.buffering.buffer_size = "352800"
                device.buffering.fragment_size = "176400"
                device.access_mode = "mmap+timer"
                device.profile.name = "stereo-fallback"
                device.profile.description = "Stereo"
                device.description = "Built-in Audio Stereo"
                module-udev-detect.discovered = "1"
                device.icon_name = "audio-card"
        Ports:
                analog-output: Analog Output (priority: 9900)
        Active Port: analog-output
        Formats:
                pcm

Sink #2
        State: IDLE
        Name: balena-sound.input
        Description: Null Output
        Driver: module-null-sink.c
        Sample Specification: s16le 2ch 44100Hz
        Channel Map: front-left,front-right
        Owner Module: 23
        Mute: no
        Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% / 0.00 dB
                balance 0.00
        Base Volume: 65536 / 100% / 0.00 dB
        Monitor Source: balena-sound.input.monitor
        Latency: 58704 usec, configured 66666 usec
        Flags: DECIBEL_VOLUME LATENCY
        Properties:
                device.description = "Null Output"
                device.class = "abstract"
                device.icon_name = "audio-card"
        Formats:
                pcm

Sink #3
        State: RUNNING
        Name: balena-sound.output
        Description: Null Output
        Driver: module-null-sink.c
        Sample Specification: s16le 2ch 44100Hz
        Channel Map: front-left,front-right
        Owner Module: 24
        Mute: no
        Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% / 0.00 dB
                balance 0.00
        Base Volume: 65536 / 100% / 0.00 dB
        Monitor Source: balena-sound.output.monitor
        Latency: 58788 usec, configured 66666 usec
        Flags: DECIBEL_VOLUME LATENCY
        Properties:
                device.description = "Null Output"
                device.class = "abstract"
                device.icon_name = "audio-card"
        Formats:
                pcm

Sink #4
        State: SUSPENDED
        Name: snapcast
        Description: Unix FIFO sink /var/cache/snapcast/snapfifo
        Driver: module-pipe-sink.c
        Sample Specification: s16le 2ch 44100Hz
        Channel Map: front-left,front-right
        Owner Module: 25
        Mute: no
        Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% / 0.00 dB
                balance 0.00
        Base Volume: 65536 / 100% / 0.00 dB
        Monitor Source: snapcast.monitor
        Latency: 0 usec, configured 0 usec
        Flags: DECIBEL_VOLUME LATENCY
        Properties:
                device.string = "/var/cache/snapcast/snapfifo"
                device.description = "Unix FIFO sink /var/cache/snapcast/snapfifo"
                device.icon_name = "audio-card"
        Formats:
                pcm

... so the device is there as Sink #1 (which is different than in #296 where it was Sink #0). So it's being detected at alsa_output.1.stereo-fallback.monitor instead of alsa_output.dac.stereo-fallback.monitor.
Output from http://<device_ip>:3000/support
{
   "config" : {
      "device" : {
         "type" : "raspberrypi4-64",
         "ip" : "<IP_ADDRESS>"
      },
      "audioBlock" : {
         "_events" : {},
         "name" : "BalenaAudio",
         "connected" : true,
         "address" : "tcp:<IP_ADDRESS>:4317",
         "chunks" : [],
         "requests" : [],
         "lastRequestId" : 26,
         "socket" : {
            "_pendingEncoding" : "",
            "connecting" : false,
            "_host" : null,
            "_server" : null,
            "_writableState" : {
               "highWaterMark" : 16384,
               "writing" : false,
               "bufferedRequestCount" : 0,
               "errorEmitted" : false,
               "sync" : false,
               "autoDestroy" : false,
               "needDrain" : false,
               "emitClose" : false,
               "lastBufferedRequest" : null,
               "ended" : false,
               "pendingcb" : 0,
               "writecb" : null,
               "objectMode" : false,
               "finalCalled" : false,
               "destroyed" : false,
               "bufferProcessing" : false,
               "corked" : 0,
               "bufferedRequest" : null,
               "writelen" : 0,
               "length" : 0,
               "corkedRequestsFree" : {
                  "entry" : null,
                  "next" : null
               },
               "decodeStrings" : false,
               "defaultEncoding" : "utf8",
               "finished" : false,
               "ending" : false,
               "prefinished" : false,
               "afterWriteTickInfo" : null
            },
            "allowHalfOpen" : false,
            "writable" : true,
            "_hadError" : false,
            "_pendingData" : null,
            "_readableState" : {
               "multiAwaitDrain" : false,
               "awaitDrainWriters" : null,
               "buffer" : {
                  "tail" : null,
                  "length" : 0,
                  "head" : null
               },
               "length" : 0,
               "encoding" : null,
               "resumeScheduled" : false,
               "readableListening" : true,
               "defaultEncoding" : "utf8",
               "needReadable" : true,
               "highWaterMark" : 16384,
               "readingMore" : false,
               "sync" : false,
               "reading" : true,
               "autoDestroy" : false,
               "emitClose" : false,
               "endEmitted" : false,
               "emittedReadable" : false,
               "flowing" : false,
               "pipesCount" : 0,
               "decoder" : null,
               "ended" : false,
               "objectMode" : false,
               "destroyed" : false,
               "pipes" : null
            },
            "_parent" : null,
            "_eventsCount" : 4,
            "server" : null,
            "readable" : true,
            "_events" : {},
            "_sockname" : null
         },
         "subToEvents" : true,
         "_eventsCount" : 2,
         "pulseAddress" : {
            "port" : 4317,
            "host" : "<IP_ADDRESS>"
         },
         "defaultSink" : "balena-sound.input",
         "pulseCookie" : {
            "data" : [
               152,
               121,
               162,
               165,
               85,
               0,
               0,
               0,
               255,
               255,
               255,
               255,
               255,
               255,
               255,
               255,
               1,
               16,
               162,
               165,
               85,
               0,
               0,
               0,
               255,
               255,
               255,
               255,
               54,
               9,
               0,
               0,
               152,
               121,
               162,
               165,
               85,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               255,
               255,
               255,
               255,
               0,
               0,
               0,
               0,
               152,
               121,
               162,
               165,
               85,
               0,
               0,
               0,
               0,
               122,
               162,
               165,
               85,
               0,
               0,
               0,
               72,
               119,
               162,
               165,
               85,
               0,
               0,
               0,
               120,
               118,
               162,
               165,
               85,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               24,
               122,
               162,
               165,
               85,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               146,
               24,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               104,
               121,
               162,
               165,
               85,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               255,
               255,
               255,
               255,
               72,
               122,
               162,
               165,
               85,
               0,
               0,
               0,
               255,
               255,
               255,
               255,
               54,
               9,
               0,
               0,
               24,
               122,
               162,
               165,
               85,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               255,
               255,
               255,
               255,
               0,
               0,
               0,
               0,
               24,
               122,
               162,
               165,
               85,
               0,
               0,
               0,
               128,
               122,
               162,
               165,
               85,
               0,
               0,
               0,
               72,
               119,
               162,
               165,
               85,
               0,
               0,
               0,
               160,
               118,
               162,
               165,
               85,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               152,
               122,
               162,
               165,
               85,
               0,
               0,
               0,
               1,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               146,
               24,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0,
               0
            ],
            "type" : "Buffer"
         }
      },
      "mode" : "STANDALONE",
      "multiroom" : {
         "master" : "<IP_ADDRESS>",
         "forced" : false
      }
   },
   "volume" : 100,
   "sinks" : [
      {
         "formats" : "Headphones",
         "monitorSourceIndex" : 0,
         "cardIndex" : 0,
         "baseVolume" : 56210,
         "moduleIndex" : 6,
         "name" : "alsa_output.bcm2835.stereo-fallback",
         "sampleSpec" : {
            "rate" : 44100,
            "format" : 3,
            "channels" : 2
         },
         "channelVolumes" : {
            "channels" : 2,
            "volumes" : [
               56210,
               56210
            ]
         },
         "activePortName" : "analog-output-headphones",
         "index" : 0,
         "description" : "Built-in Audio Stereo",
         "driverName" : "module-alsa-card.c",
         "latency" : "0n",
         "monitorSourceName" : "alsa_output.bcm2835.stereo-fallback.monitor",
         "properties" : [
            [
               "alsa.resolution_bits",
               "16"
            ],
            [
               "device.api",
               "alsa"
            ],
            [
               "device.class",
               "sound"
            ],
            [
               "alsa.class",
               "generic"
            ],
            [
               "alsa.subclass",
               "generic-mix"
            ],
            [
               "alsa.name",
               "bcm2835 Headphones"
            ],
            [
               "alsa.id",
               "bcm2835 Headphones"
            ],
            [
               "alsa.subdevice",
               "0"
            ],
            [
               "alsa.subdevice_name",
               "subdevice #0"
            ],
            [
               "alsa.device",
               "0"
            ],
            [
               "alsa.card",
               "0"
            ],
            [
               "alsa.card_name",
               "bcm2835 Headphones"
            ],
            [
               "alsa.long_card_name",
               "bcm2835 Headphones"
            ],
            [
               "alsa.driver_name",
               "snd_bcm2835"
            ],
            [
               "device.bus_path",
               "/devices/platform/soc/fe00b840.mailbox/bcm2835_audio/sound/card0"
            ],
            [
               "sysfs.path",
               "/devices/platform/soc/fe00b840.mailbox/bcm2835_audio/sound/card0"
            ],
            [
               "device.form_factor",
               "internal"
            ],
            [
               "device.string",
               "hw:0"
            ],
            [
               "device.buffering.buffer_size",
               "131072"
            ],
            [
               "device.buffering.fragment_size",
               "131072"
            ],
            [
               "device.access_mode",
               "mmap+timer"
            ],
            [
               "device.profile.name",
               "stereo-fallback"
            ],
            [
               "device.profile.description",
               "Stereo"
            ],
            [
               "device.description",
               "Built-in Audio Stereo"
            ],
            [
               "alsa.mixer_name",
               "Broadcom Mixer"
            ],
            [
               "module-udev-detect.discovered",
               "1"
            ],
            [
               "device.icon_name",
               "audio-card"
            ]
         ],
         "ports" : 1,
         "state" : 2,
         "channelMap" : {
            "types" : [
               1,
               2
            ],
            "channels" : 2
         },
         "volumeSteps" : 65537,
         "flagsRaw" : 183,
         "isMuted" : false,
         "configLatency" : "0n"
      },
      {
         "sampleSpec" : [
            {
               "properties" : [],
               "encoding" : 1
            }
         ],
         "channelVolumes" : "Built-in Audio Stereo",
         "description" : "analog-output-headphones",
         "activePortName" : 2,
         "index" : 9900,
         "latency" : {
            "channels" : 2,
            "volumes" : [
               65536,
               65536
            ]
         },
         "driverName" : false,
         "properties" : "alsa_output.1.stereo-fallback.monitor",
         "monitorSourceName" : 7,
         "state" : 166,
         "ports" : 65536,
         "configLatency" : "0n",
         "volumeSteps" : [
            [
               "alsa.resolution_bits",
               "16"
            ],
            [
               "device.api",
               "alsa"
            ],
            [
               "device.class",
               "sound"
            ],
            [
               "alsa.class",
               "generic"
            ],
            [
               "alsa.subclass",
               "generic-mix"
            ],
            [
               "alsa.name",
               "HiFiBerry DAC+ HD HiFi pcm179x-hifi-0"
            ],
            [
               "alsa.id",
               "HiFiBerry DAC+ HD HiFi pcm179x-hifi-0"
            ],
            [
               "alsa.subdevice",
               "0"
            ],
            [
               "alsa.subdevice_name",
               "subdevice #0"
            ],
            [
               "alsa.device",
               "0"
            ],
            [
               "alsa.card",
               "1"
            ],
            [
               "alsa.card_name",
               "snd_rpi_hifiberry_dacplushd"
            ],
            [
               "alsa.long_card_name",
               "snd_rpi_hifiberry_dacplushd"
            ],
            [
               "alsa.driver_name",
               "snd_soc_hifiberry_dacplushd"
            ],
            [
               "device.bus_path",
               "/devices/platform/soc/soc:sound/sound/card1"
            ],
            [
               "sysfs.path",
               "/devices/platform/soc/soc:sound/sound/card1"
            ],
            [
               "device.form_factor",
               "internal"
            ],
            [
               "device.string",
               "hw:1"
            ],
            [
               "device.buffering.buffer_size",
               "352800"
            ],
            [
               "device.buffering.fragment_size",
               "176400"
            ],
            [
               "device.access_mode",
               "mmap+timer"
            ],
            [
               "device.profile.name",
               "stereo-fallback"
            ],
            [
               "device.profile.description",
               "Stereo"
            ],
            [
               "device.description",
               "Built-in Audio Stereo"
            ],
            [
               "module-udev-detect.discovered",
               "1"
            ],
            [
               "device.icon_name",
               "audio-card"
            ]
         ],
         "isMuted" : {
            "channels" : 2,
            "format" : 3,
            "rate" : 44100
         },
         "flagsRaw" : 1,
         "channelMap" : 1,
         "baseVolume" : "module-alsa-card.c",
         "moduleIndex" : "alsa_output.1.stereo-fallback",
         "monitorSourceIndex" : {
            "channels" : 2,
            "types" : [
               1,
               2
            ]
         },
         "formats" : 65537,
         "cardIndex" : "0n",
         "name" : 0
      },
      {
         "name" : 1,
         "monitorSourceIndex" : 2,
         "formats" : [
            [
               "device.description",
               "Null Output"
            ],
            [
               "device.class",
               "abstract"
            ],
            [
               "device.icon_name",
               "audio-card"
            ]
         ],
         "cardIndex" : "12406n",
         "baseVolume" : false,
         "moduleIndex" : 0,
         "monitorSourceName" : "balena-sound.input",
         "properties" : 23,
         "flagsRaw" : {
            "types" : [
               1,
               2
            ],
            "channels" : 2
         },
         "volumeSteps" : "balena-sound.input.monitor",
         "channelMap" : 9900,
         "isMuted" : [
            {
               "encoding" : 1,
               "properties" : []
            }
         ],
         "configLatency" : {
            "volumes" : [
               65536,
               65536
            ],
            "channels" : 2
         },
         "ports" : "module-null-sink.c",
         "state" : 2,
         "sampleSpec" : "Analog Output",
         "channelVolumes" : "analog-output",
         "driverName" : {
            "rate" : 44100,
            "format" : 3,
            "channels" : 2
         },
         "latency" : "Null Output",
         "index" : 1,
         "activePortName" : 162,
         "description" : "analog-output"
      },
      {
         "name" : 65536,
         "baseVolume" : false,
         "moduleIndex" : 0,
         "monitorSourceIndex" : 3,
         "formats" : [
            [
               "device.description",
               "Null Output"
            ],
            [
               "device.class",
               "abstract"
            ],
            [
               "device.icon_name",
               "audio-card"
            ]
         ],
         "cardIndex" : "12382n",
         "configLatency" : {
            "channels" : 2,
            "volumes" : [
               65536,
               65536
            ]
         },
         "volumeSteps" : "balena-sound.output.monitor",
         "channelMap" :<PHONE_NUMBER>,
         "flagsRaw" : {
            "types" : [
               1,
               2
            ],
            "channels" : 2
         },
         "isMuted" : [
            {
               "encoding" : 1,
               "properties" : []
            }
         ],
         "state" : 3,
         "ports" : "module-null-sink.c",
         "properties" : 24,
         "monitorSourceName" : "balena-sound.output",
         "latency" : "Null Output",
         "driverName" : {
            "format" : 3,
            "rate" : 44100,
            "channels" : 2
         },
         "description" : 1,
         "index" : "66666n",
         "activePortName" : 162,
         "channelVolumes" : "",
         "sampleSpec" : 65537
      },
      {
         "monitorSourceName" : "snapcast",
         "properties" : 25,
         "ports" : "module-pipe-sink.c",
         "state" : 4,
         "channelMap" :<PHONE_NUMBER>,
         "volumeSteps" : "snapcast.monitor",
         "flagsRaw" : {
            "types" : [
               1,
               2
            ],
            "channels" : 2
         },
         "isMuted" : [
            {
               "encoding" : 1,
               "properties" : []
            }
         ],
         "configLatency" : {
            "channels" : 2,
            "volumes" : [
               65536,
               65536
            ]
         },
         "channelVolumes" : "",
         "sampleSpec" : 65537,
         "index" : "66666n",
         "activePortName" : 34,
         "description" : 0,
         "driverName" : {
            "format" : 3,
            "rate" : 44100,
            "channels" : 2
         },
         "latency" : "Unix FIFO sink /var/cache/snapcast/snapfifo",
         "name" : 65536,
         "formats" : [
            [
               "device.string",
               "/var/cache/snapcast/snapfifo"
            ],
            [
               "device.description",
               "Unix FIFO sink /var/cache/snapcast/snapfifo"
            ],
            [
               "device.icon_name",
               "audio-card"
            ]
         ],
         "cardIndex" : "0n",
         "monitorSourceIndex" : 4,
         "baseVolume" : false,
         "moduleIndex" : 0
      }
   ],
   "constants" : {
      "port" : 3000,
      "mode" : "STANDALONE",
      "multiroom" : {
         "forced" : false
      },
      "coteDelay" : 5000,
      "debug" : false,
      "balenaDeviceType" : "raspberrypi4-64",
      "volume" : 100
   },
   "audio" : {
      "hostname" : "bec19b8c0a64",
      "user" : "root",
      "name" : "pulseaudio",
      "channelMap" : {
         "types" : [
            1,
            2
         ],
         "channels" : 2
      },
      "defaultSource" : "balena-sound.input.monitor",
      "version" : "13.0",
      "sampleSpec" : {
         "format" : 3,
         "rate" : 44100,
         "channels" : 2
      },
      "cookie" :<PHONE_NUMBER>,
      "defaultSink" : "balena-sound.input"
   }
}

And running dmesg | grep hifi
root@bec19b8c0a64:/usr/src# dmesg | grep hifi
[    8.980998] snd-rpi-hifiberry-dacplushd soc:sound: pcm179x-hifi <-> fe203000.i2s mapping ok
[    8.989655] snd-rpi-hifiberry-dacplushd soc:sound: ASoC: no DMI vendor name!

and finally dmesg | grep snd
root@bec19b8c0a64:/usr/src# dmesg | grep snd
[    0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 bcm2708_fb.fbwidth=0 bcm2708_fb.fbheight=0 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:3A:4C:B2 vc_mem.mem_base=0x3f000000 vc_mem.mem_size=0x3f600000  dwc_otg.lpm_enable=0 console=tty1 console=ttyS0,115200 rootfstype=ext4 rootwait root=UUID=ba1eadef-f68c-4f2e-a845-a0ee01c229a1 rootwait
[    8.808429] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[    8.980998] snd-rpi-hifiberry-dacplushd soc:sound: pcm179x-hifi <-> fe203000.i2s mapping ok
[    8.989655] snd-rpi-hifiberry-dacplushd soc:sound: ASoC: no DMI vendor name!

(I have two Pis and two DACs so I don't think any of the hardware is faulty)

To update: when I hardcode alsa_output.1.stereo-fallback in the start.sh script, everything works perfectly (although I still get one of those 24.11.20 13:39:49 (-0500)  audio  E: [pulseaudio] main.c: Sink alsa_output.dac.stereo-fallback does not exist. instead of two).
I'm actually not quite sure what happens when I use the one-click-deploy with Balena-cloud. Before manually pushing edits, would Balena-Cloud have picked up new versions from this repo? Or would I have had to upgrade manually anyway?

And another question (feel free to get me to write this in a forum somewhere)... are there more configuration options?
I see from this
Sink #1
        State: SUSPENDED
        Name: alsa_output.1.stereo-fallback
        Description: Built-in Audio Stereo
        Driver: module-alsa-card.c
        Sample Specification: s16le 2ch 44100Hz
        Channel Map: front-left,front-right
        Owner Module: 7
        Mute: no
        Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% / 0.00 dB
                balance 0.00
        Base Volume: 65536 / 100% / 0.00 dB
        Monitor Source: alsa_output.1.stereo-fallback.monitor
        Latency: 0 usec, configured 0 usec
        Flags: HARDWARE DECIBEL_VOLUME LATENCY
        Properties:
                alsa.resolution_bits = "16"
                device.api = "alsa"
                device.class = "sound"
                alsa.class = "generic"
                alsa.subclass = "generic-mix"
                alsa.name = "HiFiBerry DAC+ HD HiFi pcm179x-hifi-0"
                alsa.id = "HiFiBerry DAC+ HD HiFi pcm179x-hifi-0"
                alsa.subdevice = "0"
                alsa.subdevice_name = "subdevice #0"
                alsa.device = "0"
                alsa.card = "1"
                alsa.card_name = "snd_rpi_hifiberry_dacplushd"
                alsa.long_card_name = "snd_rpi_hifiberry_dacplushd"
                alsa.driver_name = "snd_soc_hifiberry_dacplushd"
                device.bus_path = "/devices/platform/soc/soc:sound/sound/card1"
                sysfs.path = "/devices/platform/soc/soc:sound/sound/card1"
                device.form_factor = "internal"
                device.string = "hw:1"
                device.buffering.buffer_size = "352800"
                device.buffering.fragment_size = "176400"
                device.access_mode = "mmap+timer"
                device.profile.name = "stereo-fallback"
                device.profile.description = "Stereo"
                device.description = "Built-in Audio Stereo"
                module-udev-detect.discovered = "1"
                device.icon_name = "audio-card"
        Ports:
                analog-output: Analog Output (priority: 9900)
        Active Port: analog-output
        Formats:
                pcm

that the resolution is 16bits and the sample rate is configured to 44.1kHz. From the datasheet, it looks like this board can handle a resolution of 24bits and a sample rate all the way up to 192kHz, is it possible to change these values?

@richardpringle did you change the dtparams to say audio=off instead of audio=on ?

i bet it's the latest pulseaudio update causing the problem. you can try to downgrade pulseaudio and restart:
sudo apt install pulseaudio=12.2-4+deb10u1 libpulse0=12.2-4+deb10u1 pulseaudio-utils=12.2-4+deb10u1 libpulsedsp=12.2-4+deb10u1

@shawaj, tried, didn't help
@aandroide, I could downgrade, but I that's just as much effort as hardcoding the name of the Sink

@richardpringle with the audio=off set is it still sink 1 not sink 0?

Aha I've spotted the issue I think.
The udev rules don't currently have an entry for snd-rpi-hifiberry-dacplushd
https://github.com/balenablocks/audio/blob/master/udev/95-balena-audio.rules
Relates to #296
Will submit a PR to fix this later.

PR is here https://github.com/balenablocks/audio/pull/48

@richardpringle until the PR is merged, you should be able to get this working by following the instructions here https://github.com/balenalabs/balena-sound/issues/377#issuecomment-752152387

Duplicate of #377

Duplicate of #377

Closing this issue now in favour of #377
Necessary changes were pulled to the audio block in https://github.com/balenablocks/audio/pull/49
You can update by using git pull and balena push -c to rebuild if using balena CLI to build again without using cached images.

Closing this issue now in favour of #377
Necessary changes were pulled to the audio block in https://github.com/balenablocks/audio/pull/49
You can update by using git pull and balena push -c to rebuild if using balena CLI to build again without using cached images.


BoardCopier, PlayerCopier, PieceCopier and associated test classes

This pull request has been redone in Pull #46


GamePadALT doesn't seem to work for Sega Genesis

BlueRetro firmware version
1.8.3
BlueRetro firmware specification
HW1
BlueRetro firmware variant
Universal
BlueRetro hardware type
External adapter with detachable cord
Manufacturer
Myself
System used
SEGA MegaDrive Genesis
Bluetooth controller brand & name
8BitDo Arcade Stick / 8BitDo DIY Kit for Sega Genesis
What is problem? (only list ONE problem per report)
Selecting GamePadAlt and power cycling the Esp32 doesn't change to 6 buttons gamepad for Sega Genesis.
Firmware 1.7.3 didn't have this issue. I noticed it since I've updated to 1.8.3. I went from 173 to 183 directly.
What did you expect to happen?
Enabling X, Y, Z and Mode button.
Attach files like logs or Bluetooth traces here
I don't know how to do that, but am willing to learn!

1.8.3 works for Sony official DS4 controllers in ALT mode 6 button and a 8bitDo M30 i tried.  Make sure the setting in the web GUI is saved and a hard power cycle (not via button hold) is done.

I am using v1.8.3 HW1 with 8BitDo M30. GamePad and GamePadAlt have only Start button working, I am using the BlueRetro Core from AliExpress with the MD adapter. Using DS4 is working as expected.

Please try in v1.9
https://github.com/darthcloud/BlueRetro/releases/tag/v1.9
Tested in MK1 two player gamepadalt myself today.

Different behavior on 1.9.  X, Y and Z are ok, but Start and Mode are weird:
BlueRetro firmware version
1.9
BlueRetro firmware specification
HW1
BlueRetro firmware variant
Universal
BlueRetro hardware type
External adapter with detachable cord
Manufacturer
Aliexpress
System used
SEGA Mega Drive II
Bluetooth controller brand & name
2x 8BitDo M30
What is problem? (only list ONE problem per report)
On both Player 1 and 2:
Pressing Start gives Start + Mode
Pressing Select gives nothing.
What did you expect to happen?
Pressing Start giving Start
Pressing Select giving Mode.

I also experienced the symptom of mixed START and MODE. (v1.9.2)
I am just guessing from looking at the source, as I think the cause is that START and MODE are in the same place in the mapping table of "genesis_btns_mask" in "main/adapter/wired/genesis.c".
    /* TH LOW */
    {
        0, 0, 0, 0,
        0, 0, 0, 0,
        0, 0, BIT(P1_LD_DOWN), BIT(P1_LD_UP),
        0, 0, 0, 0,
        BIT(P1_A), 0, 0, 0,
        BIT(P1_START), 0, 0, 0,
        0, 0, 0, 0,
        0, 0, 0, 0,
    },
    /* 6BTNS */
    {
        0, 0, 0, 0,
        0, 0, 0, 0,
        0, 0, 0, 0,
        0, 0, 0, 0,
        0, 0, 0, BIT(P1_Y),
        BIT(P1_MODE), 0, 0, 0,
        BIT(P1_X), BIT(P1_X), 0, 0,
        BIT(P1_Z), BIT(P1_Z), 0, 0,
    },

The BIT(P1_START) for TH LOW and the BIT(P1_MODE) for 6BTNS are both located in row 6, column 1.
I believe that the BIT(P1_MODE) for 6BTNS is probably correct in row 2.
            0, BIT(P1_MODE), 0, 0,

Very good catch @scrap-a
Feel free to send a PR or I can fix it later today.

Unfortunately, I have not the build environment, so I cannot verify this right away.
If you need a PR, please wait a few days.

That beta should fix the overlap between start and mode:
https://github.com/darthcloud/BlueRetro/actions/runs/8760755824

Excellent!
The OVERLAP symptom has been completely fixed about both 1P and 2P.


Merge Dev ke UAT 26 Feb 2017 - fix date time monitoring event

Coverage increased (+0.05%) to 59.173% when pulling 1305cdddb3f3b25c6aab05372654189f26ceae8d on dev into 670a09076ba7299a40d0bb67dcfa8a0f411edcf2 on uat.


Misspelling: "sensitive" is printed as "senstive"

Describe the bug
"sensitive" is printed as "senstive" in the output file.
To Reproduce
Steps to reproduce the behavior:

create html output file
click the + sign next to the section called Sensitive Data
the next to the last item on the list reads "Senstive secret"

Expected behavior
The next to the last item on the list should read "Sensitive secret"
Screenshots

Desktop (please complete the following information):

OS: MacOS 11.2.3
Browser : Chrome
Version: 89.0.4389.90

Additional context
N/A

I'll include a fix for this with some additional fixes next week.


Can't Flash Aoycocr X5P Plug

Purchased from Amazon 12/2020. Previously known to work per the Wiki.
The plug requests the token but never requests the firmware. This looks like the 02 issue, the LED stops blinking quickly, but the ID starts with 01 and there's no PSK error. I've tried the master and development branches.
The hardware could have changed, there's no nondestructive way to open the plugs, but the MAC address is right for an ESP8266 and the user agent reports SP8266SDK.
Any thoughts on what to try?
smarthack-wifi.log
smarthack-web.log
smarthack-udp.log
smarthack-psk.log
smarthack-mqtt.log

I can confirm this issue exactly as described by OP.  I received a four pack of these switches from Amazon today (12/20).  I am using the same hardware that was used in December 2019 to flash these same plugs, also from Amazon.

I was unable to flash the same device purchased from Amazon this month.  Log files from a fresh attempt via docker-compose: https://gist.github.com/colinodell/1578307a6fb67390bd230f7e3384cc5b

Although I was not able to get it working via docker-compose on my laptop, I was able to flash it successfully using a Raspberry Pi 4.  It's entirely possible the issue was something with my laptop's configuration.

@colinodell this was your issue:
https://gist.github.com/colinodell/1578307a6fb67390bd230f7e3384cc5b#file-smarthack-web-log
Could not start server on port 80
Close the process on this port and try again


WIP: Add externalTrafficPolicy=Local CI tests

/cc @gandro

This change is

test-me-please

test-me-please

Coverage decreased (-0.02%) to 45.948% when pulling 4c6bcbed20736006689f01770512717227a82d9a on pr/brb/ci-externaltrafficpolicy into c82ea8ff5cdd075e0a3ba942aa646af802579e53 on master.

test-me-please

test-me-please

test-me-please

test-me-please

The CI tests are failing because of the 80 -> 8080 port change of the zgroup=testDS pods.

test-me-please

test-me-please

test-me-please

This test will be hard to run on eks, but it's good to have it.

Waiting for 1.7.0

@Antiarchitect with or without kube-proxy?

@Antiarchitect with or without kube-proxy?

@brb Currently with kube-proxy. (K8s provisioning is via Puppet module, so I can't easily turn off kube-proxy)


App performance is degraded when react native version updated to 0.71.2 from 0.68.0 on android

New Version
0.71.2
Old Version
0.68.0
Build Target(s)
Android 8 to Android 13
Output of react-native info
System:
OS: macOS 12.6.1
CPU: (8) arm64 Apple M1
Memory: 147.81 MB / 16.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 18.0.0 - ~/.nvm/versions/node/v18.0.0/bin/node
Yarn: 1.22.19 - /opt/homebrew/bin/yarn
npm: 8.6.0 - ~/.nvm/versions/node/v18.0.0/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.11.3 - /Users/vaibhavandhare/.rbenv/shims/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.1, iOS 16.1, macOS 13.0, tvOS 16.1, watchOS 9.1
Android SDK: Not Found
IDEs:
Android Studio: 2022.1 AI-221.6008.13.2211.9514443
Xcode: 14.1/14B47b - /usr/bin/xcodebuild
Languages:
Java: 11.0.17 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.2.0 => 18.2.0
react-native: 0.71.2 => 0.71.2
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Description
Few days ago we upgraded our react-native app from version 0.68.0 to 0.70.6 using the React Native Upgrade Helper and have notice some performance issues in navigation as well as UI interactions in release mode also. So, recently we upgraded to 0.71.2 but still the application performance is not same which as at 0.68.0. We tried by enabling & disabling the hermes by results are same.

Addtional:
For version 0.68.0
"dependencies": {
"@react-native-async-storage/async-storage": "^1.17.3",
"@react-navigation/drawer": "^6.4.1",
"@react-navigation/native": "^6.0.10",
"@react-navigation/native-stack": "^6.6.1",
"react": "18.2.0",
"react-native": "0.68.0",
"react-native-job-queue": "^0.5.0",
"react-native-reanimated": "^2.6.0",
"react-native-safe-area-context": "^4.2.4",
"react-native-screens": "^3.13.1",
"react-native-vision-camera": "^2.15.2",
"react-native-webview": "^11.18.1",
"react-redux": "^7.2.8",
"realm": "^11.0.0-rc.0",
"redux": "^4.2.0",
"redux-persist": "^6.0.0",
"redux-thunk": "^2.4.2",
},
For 0.70.6
"dependencies": {
"@react-native-async-storage/async-storage": "^1.17.3",
"@react-navigation/drawer": "^6.4.1",
"@react-navigation/native": "^6.0.10",
"@react-navigation/native-stack": "^6.6.1",
"react": "18.1.0",
"react-native": "0.70.6",
"react-native-job-queue": "^0.5.0",
"react-native-reanimated": "^2.6.0",
"react-native-safe-area-context": "^4.2.4",
"react-native-screens": "^3.13.1",
"react-native-vision-camera": "^2.15.2",
"react-native-webview": "^11.18.1",
"react-redux": "^8.0.5",
"realm": "^11.3.1",
"redux": "^4.2.0",
"redux-persist": "^6.0.0",
"redux-thunk": "^2.4.2",
},
For 0.71.2
"dependencies": {
"@react-native-async-storage/async-storage": "^1.17.11",
"@react-navigation/drawer": "^6.5.8",
"@react-navigation/native": "^6.1.3",
"@react-navigation/native-stack": "^6.9.9",
"react": "18.2.0",
"react-native": "0.71.2",
"react-native-job-queue": "^0.5.0",
"react-native-reanimated": "2.14.2",
"react-native-safe-area-context": "^4.5.0",
"react-native-screens": "^3.19.0",
"react-native-vision-camera": "^2.15.4",
"react-native-webview": "^11.26.1",
"react-redux": "^8.0.5",
"realm": "^11.4.0",
"redux": "^4.2.1",
"redux-persist": "^6.0.0",
"redux-thunk": "^2.4.2",
},

Few days ago we upgraded our react-native app from version 0.68.0 to 0.70.6 using the React Native Upgrade Helper and have notice some performance issues in navigation as well as UI interactions in release mode also. So, recently we upgraded to 0.71.2 but still the application performance is not same which as at 0.68.0. We tried by enabling & disabling the hermes by results are same.

I'm unsure what is actionable for us on this issue. You're mentioning generic "performance issue". Which kind of issues are you referring to?

Também tive problemas com a versão 0.71.2.
Quando navego em meu app, ao tentar voltar para a tela anterior recebo o seguinte log:
Fatal Exception: com.facebook.react.common.JavascriptException
TypeError: undefined is not a function This error is located at: in CountDown in RCTView in Unknown in RCTView in Unknown in RCTView in Unknown in RCTView in Unknown in QuizDirecaoDefensiva in StaticContainer in EnsureSingleNavigator in SceneView in RCTView in Unknown in MaybeNestedStack in RCTView in Unknown in RNSScreen in AnimatedComponent in AnimatedComponentWrapper in Suspender in Suspense in Freeze in DelayedFreeze in InnerScreen in Screen in SceneView in Suspender in Suspense in Freeze in DelayedFreeze in RNSScreenStack in ScreenStack in NativeStackViewInner in RNCSafeAreaProvider in SafeAreaProvider in SafeAreaProviderCompat in NativeStackView in PreventRemoveProvider in NavigationContent in Unknown in NativeStackNavigator in EnsureSingleNavigator in BaseNavigationContainer in ThemeProvider in NavigationContainerInner in App in RCTView in Unknown in RCTView in Unknown in AppContainer, js engine: hermes, stack: componentWillUnmount@1:731758 commitDeletionEffectsOnFiber@1:286834 recursivelyTraverseDeletionEffects@1:286598 commitDeletionEffectsOnFiber@1:287154 recursivelyTraverseDeletionEffects@1:286598 commitDeletionEffectsOnFiber@1:287393 recursivelyTraverseDeletionEffects@1:286598 commitDeletionEffectsOnFiber@1:287004 recursivelyTraverseDeletionEffects@1:286598 commitDeletionEffectsOnFiber@1:287154 recursivelyTraverseDeletionEffects@1:286598 commitDeletionEffectsOnFiber@1:287393 recursivelyTraverseDeletionEffects@1:286598 commitDeletionEffectsOnFiber@1:287004 recursivelyTraverseDeletionEffects@1:286598 commitDeletionEffectsOnFiber@1:287154 recursivelyTraverseDeletionEffects@1:286598 commitDeletionEffectsOnFiber@1:287393 recursivelyTraverseDeletionEffects@1:286598 commitDeletionEffectsOnFiber@1:287004 recursivelyTraverseDeletionEffects@1:286598 commitDeletionEffectsOnFiber@1:287154 recursivelyTrav<truncated: 2955 chars>
Sendo que na versão 0.68 eu não tinha esses problemas

@cortinico Application works smoother in v0.68.0 than in v0.70.6 & 0.71.2 in terms of navigation, button clicks, etc. We keep the same versions of other dependencies.

@cortinico Application works smoother in v0.68.0 than in v0.70.6 & 0.71.2 in terms of navigation, button clicks, etc. We keep the same versions of other dependencies.

Could you provide evidence in the form of a reproducer or gifs that shows your problem side by side?

I have the same issue when using debug mode. But when I tried release mode it run smoothly.
It's very slow in debug mode. I'm using flipper.
// 0.71.0

i have same issue its very slow and i have a lot of frames drops after update from 0.69.2 to 0.71.3

same issue

Experiencing this starting from 0.70.5. In low-power mode on iOS, everything is much worse. Cannot share a repo unfortunately.

This seems like it could be related to #36296 and #35778.
In our case, in a repo where the only change was switching react-native from 0.69.7 to 0.70.7, startup time almost doubled, we experienced double average memory consumption and a huge spike in 'slow renders' as tracked by our remote logging tool, and various misc complaints from users about freezing / lag.
@cortinico #35778 Contains some reproductions and video demos. I understand this is a vague and complex issue, so thank you for following this thread, and if there is anything you need in terms of extra info or more reproductions, please let me know and I'll get on it. This is probably the number 1 issue facing our RN app as it prevents us upgrading, so eager to help in whatever way possible 😄

Not stale. Repro in #35778.

@tj-mc @cortinico not a reproduction but possibly valuable information, or might be a separate issue
We use react-native-performance v4 from @oblador to measure onstart performance. I have to confess I wrote it in a bit of a hurry without fully understanding the markers.
We released an upgrade from 0.69 to 0.70 at the start of february and have seen the amount of time between runJsBundleStart and runJsBundleEnd on iOS explode:

We use Hermes across Android/iOS, could this be a performance regression in Hermes?
We use Hermes.

@henrymoulton thank you that's interesting. Do you have control groups on that release (0.69/0.71 being the only change)?
The general picture isn't good for perf, just trying to account for variables.

not sure if this helps but this issue might be related and has a narrowed down cause with reproductions:

https://github.com/facebook/react-native/issues/35778

These are two identical builds of our app, except the left is RN 0.69.7, and right is RN 0.70.7.
0.70.7 experiences:

Drastically increased startup time
Almost double memory usage (only on iOS in our case)
Animation / navigation freezing + stuttering
JS engine freezes completely
https://user-images.githubusercontent.com/46665295/231018682-6c1719b0-7983-4a0e-9a29-61743899c443.mp4

This graph shows our memory usage after the rollout, which helped us initially identify the problem.

@tj-mc Hi there! We are looking into the issue, trying to understand what's going on.
To rule out problems with hermes, could you make these tests for us?
In version 0.71.x

Try to install the pods with PRODUCTION=1 bundle exec pod install. This should force React Native to download a version of Hermes for production that could contain some optimization. This can help us to rule out that we are building the wrong version of Hermes for Debug.

Hi @cipolleschi 😄
I attempted to upgrade to to 0.71.x, but it is quite a complex diff for our app and I didn't have the time to get it working.
However I did these tests comparing 0.69.8 and 0.70.1, which I hope may still be useful for ruling things out.
I built the app with PRODUCTION=1 bundle exec pod install but did not notice an improvement in startup time or memory usage. I was only able to test on simulator, but It seems to behave the same as hardware.

LEFT: 0.69.8 bundle exec pod install
RIGHT: 0.70.1 PRODUCTION=1 bundle exec pod install
https://user-images.githubusercontent.com/46665295/231908485-a5054b53-9499-4685-8ccd-5a028b0a277d.mp4

One clarification is I used jsc for the 0.71.3 video I added to https://github.com/facebook/react-native/issues/36296:
0.68.2 (snappy): https://www.loom.com/share/d0f9dac183f849e2ac6c6909b26a24c3
0.71.3 (significant lag on the learn tab): https://www.loom.com/share/2b73dae94d324b999d7ed31832565779
Hermes for 0.71.3 is unfortunately even worse. So there may be two separate issues between hermes accidentally being compiled without optimizations and whatever overall architecture changes have also impacted jsc.

Hey everyone - a quick update on this performance issue: we've just released:

https://github.com/facebook/react-native/releases/tag/v0.71.7
https://github.com/facebook/react-native/releases/tag/v0.70.9

Both contain a fix for how we build Hermes' artifacts that should help address this problem. Please upgrade to those versions and let us know if they help!

@kelset seems like someone opened a new issue #37335 for 0.71.7

Hey folks - we released a couple more RCs for 0.72 and in them there are a few commits which should help address the perf regression: can you try RC5 and let us know if it helps?

@vaandhare please create a repro.

We are facing the same issue with 0.71.3. There is delay in navigation for nested routes, especially when they are re-rendering. However, this is mainly happening in Android for us.

@kelset can you point us to the fixes so we can patch on older versions? In my case, I'm on v0.70.10 and experiencing app start time degradation on iOS but I can't upgrade to 0.72 to test your fixes without a significant effort.

Unfortunately, the fixes are not easily backported: we have to update the JS scheduler and reroute the rendering to a native implementation of the RuntimeScheduler.
For example, for iOS:

https://github.com/facebook/react-native/commit/dd9a5ab8a938f9f9ae0b3c117d8f432d7793bbc5
https://github.com/facebook/react-native/commit/ee177cab7583fa305d43c66342fb9b3693a4769a
https://github.com/facebook/react-native/commit/dc6a2c384db8acf59eba87bf75e435e51780204d
https://github.com/facebook/react-native/commit/c43bd7a73a210ce9514ddf1fe8af33d9347f5d16

For Android:

https://github.com/facebook/react-native/commit/47b45df65c104411339090d2b9c307402a8eb679

As you can see, these are not trivial changes to backport as the state of the repo evolved significantly after almost ~2k commits. :(

I'm on v0.70.10 and experiencing app start time degradation on iOS but I can't upgrade to 0.72 to test your fixes without a significant effort.

As @cipolleschi mentioned, the useEffect bug we fixed in 0.72 can't be easily backported. The reason is that this is a fundamental change in the internals of React and we can't ship this change as a patch release for a stable release.

I couldn't try 0.72 on our app because Expo didn't support it (at least it didn't 3 weeks ago), but this comment says it's not completely fixed #36296 (comment)

@diegolmello Nope that comments mentions generic performance regression with a calendar libray. The problem is that we receive 'generic performance regressions' issues over and over, and it's hard to pinpoint where the issue is, especially if the issue is in a 3rd party library.
So far, we isolated a bug with useEffect which we fixed and we released in 0.72. Expo will come up with SDK 49 soon which will include this fix.

@cortinico I saw the fix is still back and forth and waiting to be re-landed https://github.com/facebook/react-native/pull/37634 Can you clarify the bug is truly sorted out for both platforms in 0.72 or in main or still in investigation? Thank you

I have created new application with 0.72.0 version, I can see performance improvement as compared to 0.71.
But with navigations in v0.68 is still better.

Anecdotal, but this is our experience with the issue:

On 0.68.X no major performance issues.
After upgrading to 0.71.X in our app (no other updates that are probable to affect performance), massive spike of Android users reporting major performance issues. The app has hundreds of thousands of users on Android, so it is not just reports from a handful of users.
We updated to React Native 0.72 late release candidates, then the proper release. However, users are still reporting major performance issues and saw no change between 0.71 and 0.72.

In our case, the issue seems to only affect Android, unlike for some of the other developers in this thread. Perhaps it is because we are using Hermes engine only on Android and JSC on iOS.
Additionally, this performance issue has been extremely hard to reproduce and profile. We have seen no significant memory or CPU usage increase when comparing 0.68 and 0.71 or 0.72 on multiple generations of Android devices. Yet, it is undeniable that the performance took a big hit after upgrading React Native, on non-insignificant portion of Android devices in the real world (but not all of them).

Hey everyone - I talked with @cortinico and we have decided to deduplicate this "performance regression post 0.70" conversation in this issue to try and keep the comments meaningfully relevant all in the same spot and avoid having to literally post the same comments in the both.
Please head over to #36296 and check out the status update on the maintainers end on this problem.


added targets for data to display, added header to login page(wip)

added a few generic targets, added generic header to login page


logged_duration: wrap get_disk_space_status, give default condition a "slow call threshold"

The first of these I don't expect to be controversial, because we already similarly wrap all the "additional checks" for the status view.
The second adds a SLOW_DEFAULT_CALL_THRESHOLD of 0.5s to the default logged_duration condition. This will have a small effect on existing uses of it, but I don't think it's significant enough to warrant a major bump. The commit message explains more:

the thinking here is that any routine we consider measurable spending more than half a second doing what it's doing is probably something we want to know about and the maximum rate it can hypothetically churn our unwanted logs is 2 per second (per thread I guess). longer than SLOW_EXTERNAL_CALL_THRESHOLD because we already try and limit the number of external calls we do, whereas we may not have the same attitude to whatever block of code this is wrapped around.

a logged_duration user wanting to use the default condition but a shorter threshold can always add that to the default condition with an "or" clause

How much (roughly) do you expect the number of logged calls to increase by? Doubled? 10x?

I'd expect it only to make a difference in weird cases.


Updated pom and dependencies

Same questions as draggable about artifactIds

Yep, it works. I was using the snapshot and gwt 2.7 with navigo


Is it time to merge weak announcement support to the main branch?

Weak support was added nine months ago -- I've been using it pretty much ever since. Is there any work to be done before merging it to the main branch for the upcoming alpha?

It seems the merge occurred and the topic branch changes were in development and main. I removed the topic branch.


Add front end validation for phone numbers

Since we've added the backend validation for phone numbers, we should add the same validation for the front end.

@jpaidoussi Ready for review.
@rowanseymour Ready for you to have a look at too.

👍 Looks good to me

Django tests are failing, but this PR doesn't touch anything django, so I'll have to look into it


class \CssMin not found

Class 'CssMin' not found in module\AsseticBundle\vendor\assetic\src\Assetic\Filter\CssMinFilter.php on line 72

To use the CssMinFilter, you need to get the CssMin library and include it in your code [...]

I just want to clarify: Do you mean this library as a valid candidate for the task? If yes, there's also a packagist item for that. It goes by the name natxet/CssMin. It worked for me but I had a little trouble finding a matching package because there's quiet a number of CSS minifiers out there. What do you think about an entry in the "suggest" config within Assetic's composer.json?

@netbrothers-tr yes, this is the name of the package which has been created by someone to expose this library on Packagist. It is a fork of the original codebase (which was not on github and not on composer), and this fork was not yet there in 2012

@stof Thank you for answering and clarifying! What about adding it as a "suggest" package in Assetic's composer.json?


which policies to add - is not authorized to perform: amplify:CreateApp on resource

Describe the bug
I am following the tutorial here and my goal is to get AWS Transcribe in ios app.
https://aws-amplify.github.io/docs/sdk/ios/start#step-1-configure-your-app
I'm at the Step 2 - Initialize the project
I typed amplify init and got the error -
init failed, and is not authorized to perform: amplify:CreateApp on resource.
There is no instructions mentioning how to add policies to my IAM role on this page for amplify.
I went to the stackflow and it says that I need to add the policies (pretty lot of policies here). Not sure if it's outdated or not.
https://stackoverflow.com/questions/59734709/amplify-createapp-permission
I went to the IAM page and started to see what roles I can find by that answer -
"appsync:*",
and I see the
AWSAppSyncAdministrator
AWSAppSyncInvokeFullAccess
AWSAppSyncPushToCloudWatchLogs
AWSAppSyncSchemaAuthor
Not sure what policies to add to get it working.
To Reproduce
Steps to reproduce the behavior:
I typed amplify init and got the error -
init failed, and is not authorized to perform: amplify:CreateApp on resource.
There is no instructions mentioning how to add policies to my IAM role on this page.
I went to the stackflow and it says that I need to add the roles
https://stackoverflow.com/questions/59734709/amplify-createapp-permission
I went to the IAM page and started to see what roles I can find by that answer -
"appsync:*",
and I see the
AWSAppSyncAdministrator
AWSAppSyncInvokeFullAccess
AWSAppSyncPushToCloudWatchLogs
AWSAppSyncSchemaAuthor
Not sure what policies to add to get it working.
Expected behavior
I expect to see amplify working and start coding to get transcribe working as well.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment(please complete the following information):

Amplify Framework Version: 4.13.1
Dependency Manager: Pods
Swift Version : 5.0

Device Information (please complete the following information):

Device: Iphone 6s plus
iOS Version: [e.g. iOS 11]
Specific to simulators:

Additional context
Add any other context about the problem here.

Could you please guide me how to use "amplify init" without AdministratorAccess (full admin access role)?
What policies should I add to my IAM user without the full admin access role?


CTLR+enter doesn't send the request after selecting the request from the left menu.

Expected Behavior
When I select a request, I want to CTRL+enter to send the request.
Actual Behavior
I need to click in the middle column (request details) to make the CTRL+enter to work.
Reproduction Steps

create a request
create another request
on the request list (left menu) click on the first request created
now CTRL+enter
that doesn't fire the request
now click on the request details (middle column)
now CTRL+enter
that fires the request

Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Which sync method do you use?

[ ] Git sync.
[ ] Insomnia Cloud sync.
[X] Local only

Additional Information
I use Linux Mint which is based on Ubuntu.
Insomnia Version
2023.5.8
What operating system are you using?
Other Linux
Operating System Version
Linux Mint 21.3
Installation method
mint software manager, I guess it uses apt internally
Last Known Working Insomnia version
No response

Thanks for reporting this issue, @ppazos! I think we can track this on #8163 as it's the same underlying issue, and both symptoms will be addressed by the same fix. Closing this issue to avoid tracking duplicates.


Selecting on one component of a composite index

Discussed in https://github.com/isar/isar/discussions/371

Originally posted by bigbenchrob May  7, 2022
The documentation led me to believe that, using a two-element compound index, ids in the index would be organized by the first component of the index, then sorted within that by the second component of the index. Selecting on the first component would give me the second sort 'for free'. Instead, I don't seem to be able to select based on the first component of the index at all, with or without adding a selection on the second component  My test class looks like this:
part 'isar_test.g.dart';

@Collection(accessor: 'test')
class IsarTest {
  IsarTest( this.id, this.sequence, this.citySingle,  this.cityComposite, this.name,);

  @Id()
  final int id;

  final int sequence;

  @Index(type: IndexType.hash)
  final String citySingle;

  @Index(composite: [CompositeIndex('sequence')])
  final String cityComposite;

  final String name;
  }
}

I populate the database with a series of records, the id incrementing as each record is added and the "sequence" field decrementing (so I can distinguish sorting based on this field from the natural order of records in the db, or the id field).
If I select on the citySingle index, it works as expected (the correct selection is made, with the objects returned either in the order in which they were added to the database or by the primary id index field (I can't tell which):
final result = await isarTest
        .where()
        .citySingleEqualTo('Toronto')
        .findAll();

    for (final item in result) {
      print(item.toString());
    }

flutter:
    id:            3
    sequence:      107
    citySingle:    Toronto
    cityComposite: Toronto
    name:          Ruth
flutter:
    id:            6
    sequence:      104
    citySingle:    Toronto
    cityComposite: Toronto
    name:          Helen
flutter:
    id:            9
    sequence:      101
    citySingle:    Toronto
    cityComposite: Toronto
    name:          Emma

I thought that if I used the compound index, the records would be returned selected for city (cityComposite == 'Toronto') and sorted by the sequence field. There is no reason to specify a particular sequence value or range -- I just want to take advantage of the sorting. Isar allows me to write a query like this:
final result =
        await isarTest.where().cityCompositeEqualTo('Toronto').findAll();

...but the result set is empty. Querying:
    final result = await isarTest
        .where()
        .cityCompositeEqualToSequenceGreaterThan('Toronto', 1)
        .findAll();

...returns all the records in the database, in the order I would expect the index to be structured: sorted alphabetically by city, and within each city category, numerically by sequence.
I can accomplish what I need to do using a query like:
    final result = await isarTest
        .where()
        .citySingleEqualTo('Toronto')
        .sortBySequence()
        .findAll();

...but I'd like to know what it is I'm not understanding from the documentation.
Thanks in advance!

Fixed in 3.0.0-dev.2


Disable linking delegated harvest button when the importance is 0

It seems to me that linking delegated harvest fails until the importance is calculated.
I think it would be better to control the button to link when the importance value is 0 so that it cannot be pressed.

If the button is disabled, there should be a message explaining why. Something like "Your importance score (link to the docs) is too low, harvesting will not be effective. Please increase your balance and wait for the importance score to be recalculated."
Ideally, it could also include a countdown to the next importance recalculation (it happens every multiple of 720 chain height).
Doc link: https://docs.symbolplatform.com/concepts/consensus-algorithm.html#importance-calculation


[BugFix] Fix the failure of querying extenal table that contains struc columns

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #9020
Problem Summary(Required) ：

For map or struct columns, parquet reader parses the column meta to a flat vector,
each column meta should be located by physical_column_index rather than col_idx_in_parquet.
The current code uses col_idx_in_parquet when setting io ranges, while uses physical_column_index when reading column data, resulting in incorrect column meta information and mismatched data offset.

run starrocks_admit_test

run starrocks_admit_test

run starrocks_admit_test

run starrocks_admit_test

run starrocks_admit_test

run starrocks_admit_test

run starrocks_admit_test


Restore the old repo

@robin-swift
I've had a thousand nightmares let alone users trying to build what Jon had created.
Essentially you destroyed all of that and all your endeavors with any code that existed. Including all the good ideas.
The worst thing you could do is delete someones history with no repercussions.
I am a developer too. I hate to make this hard, but what I have stated is what happened.
You need to restore the code that cannot be accessed by the people(the last commit before your actions as of taking over(over-writing the repo) ), or we have no other option than to fork Jon's last commit(and if if happens it will be set)(I'm sorry that you deleted someones college education, let alone 15+ years of it you just don't understand.)
The reason for this issue is that whoever was let into the organization(namely you) did not account for who was behind them nor who proceeded.
This is not a business and never will be. I can still fly a missile into your dot at any time.
I'd prefer to like a life where people came to me and offered something other than my own AI back....
If you put the old repo back somewhere(by the same name), there probably wont be too many breaks.
"We just need you to restore what you destroyed"
Politely
,sincerely don't erase your history
Edward Greig

@JoshVarga can you tell me what's going on here?

Fine, the history is as it was to (2013-2018) inclusive, I just grafted on my current work. You can disarm your missiles now.

That's a seperate issue, if you want to get into that can you open a new one.

Well GitHub apparently issued a robin broke the tree structure type of
message when you probably started changing thing. It didn't have a
timestamp. Maybe that is a new warning thing for those who have a fork and
someone at the trunk level actually deletes the repo. Git is unforgiving at
times, but back in the day all you really had was to blame whoever did it.
It was actually quite common thing, so when it spit out that message it
basically lead me back to an empty repo. It also is worded like a someone
might have done it intentionally. Apologies. But yes you need to treat the
repo code as if it was an actual dangerous machine. That is how gits tone
is when it pops out an error or such action or trigger.
On Wed, Jan 18, 2023, 3:03 PM Robin Swift @.***> wrote:

That's a seperate issue, if you want to get into that can you open a new
one.
—
Reply to this email directly, view it on GitHub
https://github.com/Embroidermodder/Embroidermodder/issues/295#issuecomment-1396084540,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDTXRCMCPDSZ44N2YUDEALWTBLCJANCNFSM6AAAAAAT7IRRHM
.
You are receiving this because you authored the thread.Message ID:
@.***>

@robin-swift I'd appreciate it if you made a link to the ol structure in the new documentation. Thank you. I do not have a lot of time to do things but it would be appreciated, especially by those 1000+ people I talked to in person. Disregard what negativity I meantioned about the website if you are mature enough,; just don't repeat it please. dot keys don't come cheep. If github falls tommorrow, then so be it....
If I had time, it would be like greased lightning. I appreciate all you are doing for the people. Keep up the bad work.
Thanks again.
-- Edward Greig

Sorry, I just saw this.

I'd appreciate it if you made a link to the ol structure in the new documentation.

I'm not sure what the "ol structure" is, can you give me some references to what you mean? The website is actively changing because it's an output of Doxygen and I'm sorting out how that's generated at the moment.

This isn't the easiest thing to explain, but if you notice the organization
contains only 2 human beings. This was part of the design. So if you
theoretically link all of the members of the organization together, in a
sense you have successfully demonstrated that all machines work the same
way. When you compressed the code base, you sent the whole idea to another
address(which is possible for someone or something such as an AI to
modify). Anyone who has for example a git fetch/pull script will draw from
what you are doing now in this delta time. These folks are probably
interested in the c/c++ version because there is a problem with the memory
somewhere whether that be a human or a machine, and need to analyze which
one needs to do what. For example I see that you are interested in art...
You would want to use for example python/pascal/swift/etc... With the c/c++
bindings to be safe to generate the software on any operating system in the
world. You probably noticed a few empty CI repos and didn't realize that is
where the built exes end up somewhere down the line on some users machine
or computer or server. Basically add the link to the (now looks to be 5
archives) instead of source code in the open that could be compiled by a 10
year old with a simple I just want this to work script. Folks that are savy
enough to modify their script to fetch the code will now have to extract it
and check crcs ect...
On the other hand you also have to realize @Tatarize had ported the library
to python and it is now available on pypi which may not have been the best
idea. He is the type that is using it on a machine that is destructive and
realizes it doesn't have a "way back machine"(when you execute it the
material will be used). On the plus side he is correcting small hiccups
with the formats which would need ported back and also documenting the
machine at same time. On the negative side, I would never recommend anyone
use the python library with a program such as Krita(art), they would want
to use python scripting with compiled bindings. Krita is one of the few
programs that has an honest format that is open, so therefore common sense
should tell you that when function A goes to dot, it won't cut off some
poor kids arm. JavaScript is the type of script that will say I think this
is what you want, which is not always the case, hence why the bindings
existed. In this case JavaScript implementation is a command language and
not a script per say. Python is more powerful and if I tell JavaScript to
do it my way and it doesn't do it... Guess who the boss is.
Sorry again if some of this might seem a bit negative, but I could probably
put on a 3 hour talk and some folks still wouldn't understand the many
different ways to use a curve. Basically just a link to where the archives
are would be enough for now. Most people can copy paste a link from the
documentation into a fetch script on their own without much confusion.
Thanks
On Tue, Apr 11, 2023, 2:37 AM Robin Swift @.***> wrote:

Sorry, I just saw this.
I'd appreciate it if you made a link to the ol structure in the new
documentation.
I'm not sure what the "ol structure" is, can you give me some references
to what you mean? The website is actively changing because it's an output
of Doxygen and I'm sorting out how that's generated at the moment.
—
Reply to this email directly, view it on GitHub
https://github.com/Embroidermodder/Embroidermodder/issues/295#issuecomment-1502838469,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDTXRGAOIRHZ33P343PABDXAUCZZANCNFSM6AAAAAAT7IRRHM
.
You are receiving this because you authored the thread.Message ID:
@.***>

I feel like you're trying to cover a lot of issues in one message here. Can you seperate out and clearly state what you want me to do with respect to the documentation, please? It would also help if you supply a specific link like this: https://www.libembroidery.org/todo.html so I know where to fix it.

Well... As far as I can tell, the server or link is housed on GitHub
originally. So if a user executed a script that fetched the code, would end
up with your code, which would not be the right code. OK, let's say I have
a script that fetched your code and trys to compile it. You are the problem
in-between. A machine or musician knows that they CANNOT hit the same note
twice. Unless you are Robin or I need a detour. Try to click on what you
think will download the source code and then write a script. The only
difference will be the curve(link). I hope this makes sense. This is your
curve.
On Wed, Apr 12, 2023, 12:35 AM Robin Swift @.***> wrote:

I feel like you're trying to cover a lot of issues in one message here.
Can you seperate out and clearly state what you want me to do with respect
to the documentation, please? It would also help if you supply a specific
link like this: https://www.libembroidery.org/todo.html so I know where
to fix it.
—
Reply to this email directly, view it on GitHub
https://github.com/Embroidermodder/Embroidermodder/issues/295#issuecomment-1504675236,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDTXREW4XYEFH4WIKX4FQ3XAY5KVANCNFSM6AAAAAAT7IRRHM
.
You are receiving this because you authored the thread.Message ID:
@.***>

I will git on GitHub soon and post a link so you know. It is impossible to
do this from a phone.
On Wed, Apr 12, 2023, 2:21 AM Metalio Bovinus @.***>
wrote:

Well... As far as I can tell, the server or link is housed on GitHub
originally. So if a user executed a script that fetched the code, would end
up with your code, which would not be the right code. OK, let's say I have
a script that fetched your code and trys to compile it. You are the problem
in-between. A machine or musician knows that they CANNOT hit the same note
twice. Unless you are Robin or I need a detour. Try to click on what you
think will download the source code and then write a script. The only
difference will be the curve(link). I hope this makes sense. This is your
curve.
On Wed, Apr 12, 2023, 12:35 AM Robin Swift @.***>
wrote:

I feel like you're trying to cover a lot of issues in one message here.
Can you seperate out and clearly state what you want me to do with respect
to the documentation, please? It would also help if you supply a specific
link like this: https://www.libembroidery.org/todo.html so I know where
to fix it.
—
Reply to this email directly, view it on GitHub
https://github.com/Embroidermodder/Embroidermodder/issues/295#issuecomment-1504675236,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDTXREW4XYEFH4WIKX4FQ3XAY5KVANCNFSM6AAAAAAT7IRRHM
.
You are receiving this because you authored the thread.Message ID:
@.***>

@robin-swift

It appears that it isn't here. Plus your "2.0 alpha" build for windows doesn't work out of the box.
Basically what we are needing is the "1.5 version" code(as some call it) from the organization timeline archived. The portion where the 'Experimental' directory was still there.
Here was my last merge on the timeline to give you a better idea of what the repo looked like before it got cut off. The c/c++ valgrind linux/windows/mac/rasperrypi version.
https://github.com/Metallicow/Embroidermodder
I have the actual working machines and the software Jon worked on and built and works and even other unreleased code, but what we just need is all that archived from the organization git history.
Basically the point right before you started modifying things(or more accurately before you became member #2/3). We need the archive we know will build on all platforms.
And of course after you create a backup(release page so its called now), there should be a link at like the end of the main readme file that states if folks are looking for that c/c++ version to direct them there to download the sourcecode archive from that point in time.
I am reluctant to do anything with the stuff I have forked at this time(such as push/pull/etc).  And I do NOT want to log into Jons github account after he is passed and upload it myself to his account handle, do you understand...?

In the immortal words of Jon "They will be more serious next time."
In the immortal words of Eddie "There will not be a next time."
Do you understand how delta time works? There is no way back machine.

Ok, I understand. You want the working build from about 190 commits ago to be available as a downloadable version and this experiment to not override it. Particularly that the release version should be available for "1.5".
What I'll do is create a branch with the current work on it as imgui, the master will be the only lightly modified Qt version to keep it working as new versions of Qt come out etc.
Thanks for making this clear for me: I'll work on this today.

Ok, so now master branch is the code as of 2018. The imgui development version is in the branch imgui.
I'll try and get CI to build the Qt version.

I think you understand, but this is not about QT or WX. This has to be wrong around our ways of thinking. x = x probably doesnt mean much to you. KABOOOM is what it means to me. We have to work together with curves to make them all work out.... 3 curves is PROBABLY a dangerous thing. or so say 12million

Well, in that case, I'll close this issue and make a new one about getting the releases to build for the master branch.
I do want to work with you on this, even if it's difficult for me to tell what you're saying. Please follow that new issue (#314).

Meh, so long as the git hasn't be reverted or whatever, you should be able to create a tag or branch and leave it there.

it is hard to say python is 3 and c is 4 and parrot. pair it which what machine.....?


chore: optimize code

Coverage increased (+0.007%) to 87.25% when pulling 239cdaec588b92ce7cb36e99266c827d1810d67f on wuare:chore/optimize-code into 260dba8d4cffe68311393fdff0264fac8a3c71da on mybatis:master.

Coverage increased (+0.007%) to 87.25% when pulling 239cdaec588b92ce7cb36e99266c827d1810d67f on wuare:chore/optimize-code into 260dba8d4cffe68311393fdff0264fac8a3c71da on mybatis:master.

@wuare Thanks for the cleanup.

@wuare Thanks for the cleanup.


CLI Docs Should indicate the "tools" CLI is legacy

The page has links to both the BF CLI and the older "-tools" CLI repo.
The "-tools" repo is legacy, and that message should be clearly communicated here. Consider even deleting the link.

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

ID: 342edda6-ca59-cafd-ef8f-68586acd7703
Version Independent ID: ad1d9e0d-9252-4abd-d23c-c06d2ce6e826
Content: Azure Bot Framework Command-Line Interface (CLI) tool - Bot Service
Content Source: articles/v4sdk/bf-cli-overview.md
Service: bot-service
GitHub Login: @JonathanFingold
Microsoft Alias: kamrani

Verified with @cleemullins - need to update the link text (no longer "new", etc.). The link target is good.

@cleemullins - I'm finally getting around to fixing the copy in the SDK docs. Someone should update the copy in the repo's README file.


C++ Desktop Build Linking Fails

Describe the bug
When building a 2024 wpilib C++ codebase that has pathplannerlib 2024.2.5 installed, if desktop/simulation support is enabled, linking fails. (worked fine on 2024.2.3).
To Reproduce
Steps to reproduce the behavior:

Install pathplannerlib 2024.2.5 as vendor library
Enable desktop support
Build or run simulation
See error

Expected behavior
No error?
Screenshots

Versions: (please complete the following information):

OS: Windows 10
GUI Version: N/A
PPLib Version: 2024.2.5
PPLib Language: C++

Downloading and copying pathplannerlib into the project seems to work without issue. Unsure if this means the solution is related to using it as a vendor library or it was fixed in an update that hasn't been uploaded yet.

Is your WPILib version updated? It is built against the latest wpilib

Have you tried updating your Visual Studio Build Tools? Our team was facing the same issue but that resolved it.


Once pubic, avoid using code style and leverage precommit.ci

Whenever we make a repo public, we typically remove the "code-style" action in favor of using pre-commit.ci

@gmalinve assigned this to you as it could be a good entry point to maintaining the repo's apps usage. Feel free to contact me if you need help !


Jbaker/date range support

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Resolves: #106, #112
Summary:
Please summarize the scope of the changes you have submitted, what the intent of the work is and anything that describes the before/after state of the project.
Type of change:
Please delete options that are not relevant.

[x] New capability
[x] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

The commits early in the history using BREAKING CHANGE as the type will not create a MAJOR release. Please see the rules here https://www.conventionalcommits.org/en/v1.0.0/#specification
According to conventional commits, you can use a ! to designate a breaking change, but this example I am not finding in the semantic-release docs. https://semantic-release.gitbook.io/semantic-release/
The following example is known to work.
feat: move feature from Node 6 to Node 8 support

BREAKING CHANGE: This feature requires a major update to Node support due to deprecated Node features

I am seeing an issue in the log where the bundled CDN version is not being produced correctly.
./src/auro-datepicker.js → dist/...
(!) Unresolved dependencies
https://rollupjs.org/guide/en/#warning-treating-module-as-external-dependency
lit-html/is-server.js (imported by node_modules/lit/index.js)
(!) Unused external imports
LitElement,html,css imported from external module "lit-html/is-server.js" but never used in "node_modules/lit/index.js"
created dist/ in 6.1s

Has the CDN version been tested and verified it's working?
I'd consider the updates we made to the Generator https://github.com/AlaskaAirlines/WC-Generator/blob/master/template/rollup.config.mjs

What are you doing to run into this issue? I am unable to find/reproduce this error.

I am seeing an issue in the log where the bundled CDN version is not being produced correctly.
./src/auro-datepicker.js → dist/...
(!) Unresolved dependencies
https://rollupjs.org/guide/en/#warning-treating-module-as-external-dependency
lit-html/is-server.js (imported by node_modules/lit/index.js)
(!) Unused external imports
LitElement,html,css imported from external module "lit-html/is-server.js" but never used in "node_modules/lit/index.js"
created dist/ in 6.1s

Has the CDN version been tested and verified it's working?
I'd consider the updates we made to the Generator https://github.com/AlaskaAirlines/WC-Generator/blob/master/template/rollup.config.mjs

@blackfalcon I have updated the rollup config to match the latest from our generator. I rebuilt, bundled and tested the localhost with that bundle and it all appears to work correctly for me now.

@blackfalcon The token value can be replaced to elevation-200

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


chore: gpu base docker image

Related issue
# followed by the number of the issue
Summary
Notes
Please check if the PR fulfills these requirements

[ ] If the feature has an impact on the user experience, the changelog has been updated
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] The commit message follows the conventional commit specification

/e2e --tests camelyon

End to end tests: :hourglass_flowing_sand: STARTING

/e2e tests=substrafl,mnist,camelyon,docs

End to end tests: :hourglass_flowing_sand: STARTING

/e2e --tests=substrafl,mnist,camelyon,docs

End to end tests: :hourglass_flowing_sand: STARTING

Running MNIST on dev "worked" (there is an execution error RuntimeError: Expected either a CPUGeneratorImplStateLegacy of size 5048 or a CPUGeneratorImplState of size 5056 but found the input RNG state size to be 16 that was already noted before, but building and running non torch code is working).

/e2e --tests=substrafl,mnist,camelyon,docs

/e2e --tests=docs

End to end tests: :hourglass_flowing_sand: STARTING

/e2e --tests substrafl,camelyon

/e2e --tests docs

End to end tests: :hourglass_flowing_sand: STARTING

/e2e --tests docs

End to end tests: :hourglass_flowing_sand: STARTING


How to Access LassoNet Model Wieghts

I'm trying to pull the model weights selected in the final optimized regularization path for LassoNet. Is there anyway to show the weights for each of the features used in that path? I know you can print out the most complex path using path[-1] but how do I access the weights there? I've tried using path[-1].state_dict() but that didn't work. Is there a special way to call the weights in the path?  I know you can use model.feature_importance_ to show the feature importance but that doesn't serve as the weight in the model. Correct? The model.coef_ attribute doesn't work just to print out the weight. Could you please provide some guidance on how to obtain the weights or coefficients of the LassoNet model? Thanks for your help.

Can you provide the full code? The answer is not the same depending on the method you called. For a CV model, you do model.path_[-1].state_dict.

I was using the LassoNetRegressorCV. Thank you for the suggestion it worked that way. My goal is to create a scatter plot with all the individual features and show the final optimal path taken by connecting them. I want to annotate the top 10 features on this line. I want to shade the area underneath the line to show the selected features region. This area would represent the selection of features most likely used in the model but not the top 10. The points above the line weren't included in the final path taken by the model. One axis would be weights and I can't figure out what the other one would be. I think accuracy would be with respect to the output of the model. I want to give it weight  I'm confused about what my axis should be can it be accuracy and coefficients? When I use lambda for x and coefficients and y it would be a vertical line because the best features all have the same lambda value.  What should my axis be and is this possible? I will use coefficients = model.path_[-1].state_dict()['linear.weight'].numpy() to get the weights of each of the features. Is this possible?

You should be able to access it with just
model.path_[-1].state_dict['linear.weight'].numpy()

That method gave me an error message. The correct statement is model.path_[-1].state_dict. 'linear.wieght' is not a key for the state_dict. The keys are ['layers.0.weight', 'layers.0.bias', 'layers.1.weight', 'layers.1.bias', 'skip.weight']. So I will use 'layers.0.weight' to get it. Thank you for your help.


[fix] Do not allow null key or null value to be added to cache fixes #152

fixes #152
caffeine will throw null pointer exception so do not add null types

coverage: 93.75% (+0.4%) from 93.333%
when pulling 42a18d4bcc788b0b87b7f64f77fe3c3198c0837c on hazendaz:master
into 58279e36dd9adc3c58b8228caa1af8497dccd774 on mybatis:master.


Added json file

Issue
What is changed
added Json files with an id

Hey @OjashKush
I am so sorry but this repo has been excluded from Hacktoberfest, yet, I'll take your Pull Request for the sake of Contribution
Thank you so much!


[Storage] ErrorCode: AuthorizationPermissionMismatch when access azure queue with aad auth

Hello, we are trying to use aad auth of a service principal to connect an azure queue.
I am following the sample code using QueueServiceClient.
            // Create a client that can authenticate using our token credential
            QueueServiceClient service = new QueueServiceClient(new Uri("https://speaker0reco0westus0dev2.queue.core.windows.net"), credential);

            // Make a service request to verify we've successfully authenticated
            var response = service.GetProperties();

            var queueClient = service.CreateQueue("testqueue2").Value;
            queueClient.SendMessage("abc");

service.GetProperties() returns 200 and CreateQueue() call succeeded, I can see the queue was created in the storage account. but the SendMessage() call failed with 403. "'This request is not authorized to perform this operation using this permission."
I have added the Azure Storage API permission in the service principal and also added the service principal as an owner in the storage account owner list.
Could anyone let me know what I am missing here?
Thanks
Hua

Thank you for your feedback.  Tagging and routing to the team best able to assist.

Do you know what your role is assigned to your aad identity that you are using to access your storage queues?
https://docs.microsoft.com/en-us/azure/storage/common/storage-auth-aad#azure-built-in-roles-for-blobs-and-queues

@amnguye @jsquire
Hello, I'm having the same issue but with blobs. I left a comment on a similar issue in the python repository here:
https://github.com/Azure/azure-sdk-for-python/issues/24282#issuecomment-1533605256
Part of my comment will be copied from there with some additional C# code and version details.
Note: Some values such as the storage account name and other information have a placeholder value (e.g. "mystaccount")

My user account has the "Storage Blob Data Contributor" role assigned to it.
When I run the following command via Azure CLI (logged in with az login):
az storage blob list --blob-endpoint "https://mystaccount.blob.core.windows.net/" -c "mycontainer" --auth-mode login

It returns no errors. I also tested without the role assignment and it gives me an error.
Using DefaultAzureCredential in my .NET code, it recognizes the AzureCliCredential and selects it.
Then, I attempt the following request to the storage account (via the SDK):
AzureCliCredential.GetToken invoked. Scopes: [ https://storage.azure.com/.default ] ParentRequestId: REDACTED
AzureCliCredential.GetToken succeeded. Scopes: [ https://storage.azure.com/.default ] ParentRequestId: REDACTED ExpiresOn: 2023-05-03T20:39:00.0000000+00:00
DefaultAzureCredential credential selected: Azure.Identity.AzureCliCredential

GET https://mystaccount.blob.core.windows.net/mycontainer?restype=container&comp=list&prefix=MyPrefix&include=Tags

Which returns "Status: 403 (This request is not authorized to perform this operation using this permission.)"
Even after adding the "Storage Blob Data Reader" role it still does NOT work.
Program.cs
services.AddAzureClients(builder =>
{
     builder.AddBlobServiceClient(new Uri("https://mystaccount.blob.core.windows.net/"));

     builder.UseCredential(new DefaultAzureCredential());
});

MyBlobService.cs
private readonly BlobContainerClient _blobContainerClient;

public MyBlobService(BlobServiceClient blobServiceClient)
{
   _blobContainerClient = blobServiceClient.GetBlobContainerClient("mycontainer");
}

public AsyncPageable<BlobItem> GetBlobsByPrefix(string prefix)
{
    var blobs = _blobContainerClient.GetBlobsAsync(BlobTraits.Tags, BlobStates.None, prefix);
    return blobs;
}

When trying to await foreach over the AsyncPageable is when the error occurs.
.NET version: 6.0
App type: Azure Function App
Installed packages:
Azure.Storage.Blobs - 12.16.0
Microsoft.Extensions.Azure - 1.6.3
Implicitly installed packages:
Azure.Core - 1.31.0
Azure.Identity - 1.7.0
There are more packages in each list and I can provide them if needed.

I am experiencing the same error from the await foreach as @rgrace-puck.
I am running  the dotnet cli inside WSL2 and logged in to Azure via the az cli.
Oddly enough, the code runs without errors when invoked from VSCode.

UPDATE: I believe this problem is specific to the function apps but I'm still looking into it.
I created a standalone console app using Azure.Storage.Blobs and Azure.Identity with the Storage Blob Data Contributor role assigned to my account:
using Azure.Identity;
using Azure.Storage.Blobs;

var serviceClient = new BlobServiceClient(new Uri("https://mystaccount.blob.core.windows.net/"), new DefaultAzureCredential());
var containerClient = serviceClient.GetBlobContainerClient("mycontainer");

await foreach (var blob in containerClient.GetBlobsAsync())
{
    Console.WriteLine(blob.Name);
}

...which worked without any errors. Apologies for any confusion caused by this.

Issue not caused by the storage SDK. Also the OP did not respond to my first response. Closing issue.

For posterity, the 403 error was happening because I'm trying to access tags on the blobs.
This operation requires the "Storage Blob Data Owner" role for some reason. After assigning the role, everything works fine.
https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blob-index-how-to?tabs=azure-portal#get-set-and-update-blob-index-tags


Made a single button

Pull Request
Title
Merged Sign in and Sign up
Description
merged two seperate button as one and made it easier for users to understand where they can access the log in and sign up page.
Related Issues
Fixes #523
Changes Made
Made changes in the navbar.tsx and deleted one button and made changes to the other.
Checklist

[X] I have tested the changes locally
[X] Documentation has been updated (if necessary)
[X] Changes are backward-compatible

Screenshots (if applicable)

Additional Notes

Footer

@VaibhavArora314 do check if this looks better


.mid: Add messages system, parse T1 GEMS and PART DRUMS_REAL_PS, add legacy SP fixup, rewrite SysEx parsing/writing, exclude VENUE track

Summary:

Implement system for .mid parsing actions that require user intervention
Add legacy SP fixups, prompted by a message
Add handling and message for duplicate tracks
Allow T1 GEMS to be parsed as a guitar track
Parse PART DRUMS_REAL_PS as a drums track
Add VENUE to exclusion map
Rewrite SysEx event parsing to be much more robust and defined
Rewrite SysEx event writing to utilize common code and constants

Going to be splitting this so the changes are easier to go through, the SysEx and legacy SP fixups are overlapping there.


loader bar

git pull for updated code

Do not push secrets and other environment variables.
st.loader takes more time to give a response. I've added st.spinner instead.