eq3bt - error on start, no notification again

I'm running fhem on raspberry pi without bluetooth so I've used a bluetooth dongle.  This was a small one and I've now got a bigger one with aerials.  With the small one, initially I had the no notifications issue I reported before.  This was fixed with the update although I see the log still reports errors at the start:
This is "small" dongle log:
==========
2024-02-10 18:50:26,379 - INFO     - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.719...
2024-02-10 18:50:26,400 - INFO     - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2024-02-10 18:50:26,947 - INFO     - websockets.server: server listening on <IP_ADDRESS>:15733
2024-02-10 18:50:35,425 - INFO     - websockets.server: connection open
2024-02-10 18:50:35,433 - INFO     - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: <IP_ADDRESS>
/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/fhempy/lib/core/bluetoothle.py:225: FutureWarning: BLEDevice.rssi is deprecated and will be removed in a future version of Bleak, use AdvertisementData.rssi instead
  self._dev_hash, "rssi", self._device.rssi, 1
2024-02-10 18:51:03,034 - ERROR    - asyncio: Task exception was never retrieved
future: <Task finished name='Task-286' coro=<eq3bt.notification_received() done, defined at /opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/fhempy/lib/eq3bt/eq3bt.py:197> exception=RuntimeError('dictionary changed size during iteration')>
Traceback (most recent call last):
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/fhempy/lib/eq3bt/eq3bt.py", line 200, in notification_received
    await self.update_all_readings()
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/fhempy/lib/eq3bt/eq3bt.py", line 211, in update_all_readings
    await self.update_schedule_readings()
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/fhempy/lib/eq3bt/eq3bt.py", line 311, in update_schedule_readings
    for day in self.thermostat.schedule.keys():
RuntimeError: dictionary changed size during iteration
2024-02-10 18:51:16,187 - ERROR    - Eq3bt1: Timeout on update, retry in 60s
/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/fhempy/lib/core/bluetoothle.py:225: FutureWarning: BLEDevice.rssi is deprecated and will be removed in a future version of Bleak, use AdvertisementData.rssi instead
  self._dev_hash, "rssi", self._device.rssi, 1
2024-02-10 18:52:24,863 - ERROR    - asyncio: Task exception was never retrieved
future: <Task finished name='Task-743' coro=<eq3bt.notification_received() done, defined at /opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/fhempy/lib/eq3bt/eq3bt.py:197> exception=RuntimeError('dictionary changed size during iteration')>
Traceback (most recent call last):
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/fhempy/lib/eq3bt/eq3bt.py", line 200, in notification_received
    await self.update_all_readings()
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/fhempy/lib/eq3bt/eq3bt.py", line 211, in update_all_readings
    await self.update_schedule_readings()
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/fhempy/lib/eq3bt/eq3bt.py", line 311, in update_schedule_readings
    for day in self.thermostat.schedule.keys():
RuntimeError: dictionary changed size during iteration
2024-02-10 18:53:03,140 - ERROR    - root: Eq3bt2: readingsBeginUpdate couldn't acquire lock, caused by readingsBeginUpdate without End or Single update inbetween
2024-02-10 18:54:24,968 - ERROR    - root: Eq3bt1: readingsBeginUpdate couldn't acquire lock, caused by readingsBeginUpdate without End or Single update inbetween
2024-02-10 18:57:49,013 - ERROR    - Eq3bt1: Device disconnected, reconnect now
2024-02-10 18:57:49,133 - ERROR    - Eq3bt2: Device disconnected, reconnect now
==========

With aerial dongle I always have "connected (no notifications)" no matter how long I wait.  I've gone through the bluetoothctl steps as in the eq3bt page.  That all works and shows no errors.  Both dongles report as Realtek but different mac addresses.  I have 2 eq3bt thermostats, Wq3bt1 and Eq3bt2.  The log for aerial dongle is:
==========
Activating virtual environment...OK
2024-02-14 12:48:58,038 - INFO     - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.719...
2024-02-14 12:48:58,059 - INFO     - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2024-02-14 12:48:58,522 - INFO     - websockets.server: server listening on <IP_ADDRESS>:15733
2024-02-14 12:49:07,854 - INFO     - websockets.server: connection open
2024-02-14 12:49:07,862 - INFO     - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: <IP_ADDRESS>
2024-02-14 12:50:07,527 - ERROR    - Eq3bt2: Timeout on update, retry in 60s
2024-02-14 12:51:37,574 - ERROR    - Eq3bt2: Timeout on update, retry in 60s
/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/fhempy/lib/core/bluetoothle.py:225: FutureWarning: BLEDevice.rssi is deprecated and will be removed in a future version of Bleak, use AdvertisementData.rssi instead
  self._dev_hash, "rssi", self._device.rssi, 1
/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/fhempy/lib/core/bluetoothle.py:225: FutureWarning: BLEDevice.rssi is deprecated and will be removed in a future version of Bleak, use AdvertisementData.rssi instead
  self._dev_hash, "rssi", self._device.rssi, 1
2024-02-14 12:52:44,786 - ERROR    - Eq3bt2: Failed to subscribe to notifications
Traceback (most recent call last):
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/fhempy/lib/core/bluetoothle.py", line 243, in connect_once
    await self._subscribe_notifies()
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/fhempy/lib/core/bluetoothle.py", line 276, in _subscribe_notifies
    await self._client.start_notify(
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/bleak/__init__.py", line 717, in start_notify
    await self._backend.start_notify(characteristic, wrapped_callback, **kwargs)
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/bleak/backends/bluezdbus/client.py", line 1003, in start_notify
    assert_reply(reply)
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/bleak/backends/bluezdbus/utils.py", line 22, in assert_reply
    raise BleakDBusError(reply.error_name, reply.body)
bleak.exc.BleakDBusError: [org.bluez.Error.NotPermitted] Not paired
2024-02-14 12:52:46,774 - ERROR    - Eq3bt1: Failed to subscribe to notifications
Traceback (most recent call last):
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/fhempy/lib/core/bluetoothle.py", line 243, in connect_once
    await self._subscribe_notifies()
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/fhempy/lib/core/bluetoothle.py", line 276, in _subscribe_notifies
    await self._client.start_notify(
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/bleak/__init__.py", line 717, in start_notify
    await self._backend.start_notify(characteristic, wrapped_callback, **kwargs)
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/bleak/backends/bluezdbus/client.py", line 1003, in start_notify
    assert_reply(reply)
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/bleak/backends/bluezdbus/utils.py", line 22, in assert_reply
    raise BleakDBusError(reply.error_name, reply.body)
bleak.exc.BleakDBusError: [org.bluez.Error.NotPermitted] Not paired
=========

What should I try to fix this?  When I swap back to small dongle (power off first of course) the notifications work again.

Can you please provide the output of
bluetoothctl
paired-devices
devices Paired
list
info MAC

SSH'ed in to pi and started bluetoothctl and I get

[CC-RT-BLE]# devices
Device 00:1A:22:1B:D1:DA CC-RT-BLE
Device 00:1A:22:1B:D3:05 CC-RT-BLE

[CC-RT-BLE]# list
Controller 8C:88:4B:07:12:97 pi [default]

[CC-RT-BLE]# info 00:1A:22:1B:D1:DA
Device 00:1A:22:1B:D1:DA (public)
        Name: CC-RT-BLE
        Alias: CC-RT-BLE
        Paired: no
        Trusted: yes
        Blocked: no
        Connected: yes
        LegacyPairing: no
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (3e135142-654f-9090-134a-a6ff5bb77046)
        UUID: Vendor specific           (9e5d1e47-5c13-43a0-8635-82ad38a1386f)
        ManufacturerData Key: 0x0000
        ManufacturerData Value:
  00 00 00 00 00 00 00 00 00                       .........
[CC-RT-BLE]# info 00:1A:22:1B:D3:05
Device 00:1A:22:1B:D3:05 (public)
        Name: CC-RT-BLE
        Alias: CC-RT-BLE
        Paired: no
        Trusted: yes
        Blocked: no
        Connected: yes
        LegacyPairing: no
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (3e135142-654f-9090-134a-a6ff5bb77046)
        UUID: Vendor specific           (9e5d1e47-5c13-43a0-8635-82ad38a1386f)
        ManufacturerData Key: 0x0000
        ManufacturerData Value:
  00 00 00 00 00 00 00 00 00

So neither thermostats are paired (paired-devices returns nothing).  I now pair these in bluetoothctl.
[CC-RT-BLE]# pair 00:1A:22:1B:D1:DA
Attempting to pair with 00:1A:22:1B:D1:DA
[CHG] Device 00:1A:22:1B:D1:DA Paired: yes
Pairing successful
[CC-RT-BLE]# paired-devices
Device 00:1A:22:1B:D1:DA CC-RT-BLE
[CC-RT-BLE]# pair 00:1A:22:1B:D3:05
Attempting to pair with 00:1A:22:1B:D3:05
[CHG] Device 00:1A:22:1B:D3:05 Paired: yes
Pairing successful
[CC-RT-BLE]# paired-devices
Device 00:1A:22:1B:D1:DA CC-RT-BLE
Device 00:1A:22:1B:D3:05 CC-RT-BLE
[CC-RT-BLE]#

[CC-RT-BLE]# info 00:1A:22:1B:D3:05
Device 00:1A:22:1B:D3:05 (public)
        Name: CC-RT-BLE
        Alias: CC-RT-BLE
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: yes
        LegacyPairing: no
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (3e135142-654f-9090-134a-a6ff5bb77046)
        UUID: Vendor specific           (9e5d1e47-5c13-43a0-8635-82ad38a1386f)
        ManufacturerData Key: 0x0000
        ManufacturerData Value:
  00 00 00 00 00 00 00 00 00                       .........
[CC-RT-BLE]# info 00:1A:22:1B:D1:DA
Device 00:1A:22:1B:D1:DA (public)
        Name: CC-RT-BLE
        Alias: CC-RT-BLE
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: yes
        LegacyPairing: no
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (3e135142-654f-9090-134a-a6ff5bb77046)
        UUID: Vendor specific           (9e5d1e47-5c13-43a0-8635-82ad38a1386f)
        ManufacturerData Key: 0x0000
        ManufacturerData Value:
  00 00 00 00 00 00 00 00 00                       .........
[CC-RT-BLE]#

So it all seems to work in bluetoothctl.  I have not uninstalled/reinstalled bluetooth.  Swapping the dongles seems to work without doing that.

BTW tried the update to 0.1.720.  No difference.  I did notice after the update that 1 thermostat connects and I can change the setting.  The second is still connecting.  After a wait that one is also connected and I can change that setting.  Both are not getting notification though.  Tried a fhem restart and no difference.

I can see that you have successfully paired both devices. Can you please check if the paired-devices are still there after a fhempy restart?

No.  Here is the output of bluetoothctl.  pi is just powered on and booted.  fhem is booting.
root@pi:~# bluetoothctl
Agent registered
[CC-RT-BLE]# list
Controller 8C:88:4B:07:12:97 pi [default]
[CHG] Device 00:1A:22:1B:D3:05 ServicesResolved: no
[CHG] Device 00:1A:22:1B:D3:05 Connected: no
[CHG] Controller 8C:88:4B:07:12:97 Discovering: yes
[CHG] Controller 8C:88:4B:07:12:97 Discovering: no
[CHG] Device 00:1A:22:1B:D3:05 Connected: yes
[CHG] Device 00:1A:22:1B:D3:05 ServicesResolved: yes
[CC-RT-BLE]# pair  00:1A:22:1B:D3:05
Attempting to pair with 00:1A:22:1B:D3:05
Failed to pair: org.bluez.Error.InProgress
[CC-RT-BLE]# info  00:1A:22:1B:D3:05
Device 00:1A:22:1B:D3:05 (public)
        Name: CC-RT-BLE
        Alias: CC-RT-BLE
        Paired: no
        Trusted: yes
        Blocked: no
        Connected: yes
        LegacyPairing: no
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (3e135142-654f-9090-134a-a6ff5bb77046)
        UUID: Vendor specific           (9e5d1e47-5c13-43a0-8635-82ad38a1386f)
        ManufacturerData Key: 0x0000
        ManufacturerData Value:
  00 00 00 00 00 00 00 00 00                       .........
[CC-RT-BLE]# pair  00:1A:22:1B:D3:05
Attempting to pair with 00:1A:22:1B:D3:05
Failed to pair: org.bluez.Error.InProgress
[CHG] Device 00:1A:22:1B:D3:05 ServicesResolved: no
[CHG] Device 00:1A:22:1B:D3:05 Connected: no
[CHG] Controller 8C:88:4B:07:12:97 Discovering: yes
[CHG] Device 00:1A:22:1B:D1:DA RSSI: -68
[CHG] Device 00:1A:22:1B:D1:DA RSSI is nil
[CHG] Controller 8C:88:4B:07:12:97 Discovering: no
[CHG] Controller 8C:88:4B:07:12:97 Discovering: yes
[CHG] Device 00:1A:22:1B:D3:05 RSSI: -66
[CHG] Device 00:1A:22:1B:D3:05 RSSI is nil
[CHG] Controller 8C:88:4B:07:12:97 Discovering: no
[CHG] Device 00:1A:22:1B:D1:DA Connected: yes
[CHG] Device 00:1A:22:1B:D1:DA ServicesResolved: yes
[CHG] Device 00:1A:22:1B:D3:05 Connected: yes
[CHG] Device 00:1A:22:1B:D3:05 ServicesResolved: yes
[CC-RT-BLE]# info  00:1A:22:1B:D3:05
Device 00:1A:22:1B:D3:05 (public)
        Name: CC-RT-BLE
        Alias: CC-RT-BLE
        Paired: no
        Trusted: yes
        Blocked: no
        Connected: yes
        LegacyPairing: no
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (3e135142-654f-9090-134a-a6ff5bb77046)
        UUID: Vendor specific           (9e5d1e47-5c13-43a0-8635-82ad38a1386f)
        ManufacturerData Key: 0x0000
        ManufacturerData Value:
  00 00 00 00 00 00 00 00 00                       .........
[CC-RT-BLE]# pair  00:1A:22:1B:D3:05
Attempting to pair with 00:1A:22:1B:D3:05
[CHG] Device 00:1A:22:1B:D3:05 Paired: yes
Pairing successful
[CC-RT-BLE]# info 00:1A:22:1B:D1:DA
Device 00:1A:22:1B:D1:DA (public)
        Name: CC-RT-BLE
        Alias: CC-RT-BLE
        Paired: no
        Trusted: yes
        Blocked: no
        Connected: yes
        LegacyPairing: no
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (3e135142-654f-9090-134a-a6ff5bb77046)
        UUID: Vendor specific           (9e5d1e47-5c13-43a0-8635-82ad38a1386f)
        ManufacturerData Key: 0x0000
        ManufacturerData Value:
  00 00 00 00 00 00 00 00 00                       .........
[CC-RT-BLE]# pair 00:1A:22:1B:D1:DA
Attempting to pair with 00:1A:22:1B:D1:DA
[CHG] Device 00:1A:22:1B:D1:DA Paired: yes
Pairing successful
[CC-RT-BLE]# info 00:1A:22:1B:D1:DA
Device 00:1A:22:1B:D1:DA (public)
        Name: CC-RT-BLE
        Alias: CC-RT-BLE
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: yes
        LegacyPairing: no
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (3e135142-654f-9090-134a-a6ff5bb77046)
        UUID: Vendor specific           (9e5d1e47-5c13-43a0-8635-82ad38a1386f)
        ManufacturerData Key: 0x0000
        ManufacturerData Value:
  00 00 00 00 00 00 00 00 00                       .........
[CC-RT-BLE]#

maybe this is useful?
[CC-RT-BLE]# export
SHELL=0xd73858
HISTORY=0x4a1f8
DBUS_CONNECTION=0xd92ae8
/org/bluez/hci0=0xd979c8
/org/bluez/hci0/dev_00_1A_22_1B_D1_DA=0xd998e8
/org/bluez/hci0/dev_00_1A_22_1B_D3_05=0xda4a88
[CC-RT-BLE]# paired-devices
Device 00:1A:22:1B:D1:DA CC-RT-BLE
Device 00:1A:22:1B:D3:05 CC-RT-BLE
[CC-RT-BLE]#

update to 0.1.721, restart fhempy, ~10min wait, still connected (no notifications)
[CC-RT-BLE]# paired-devices
[CC-RT-BLE]# pair 00:1A:22:1B:D1:DA
Attempting to pair with 00:1A:22:1B:D1:DA
[CHG] Device 00:1A:22:1B:D1:DA Paired: yes
Pairing successful
[CC-RT-BLE]# pair  00:1A:22:1B:D3:05
Attempting to pair with 00:1A:22:1B:D3:05
[CHG] Device 00:1A:22:1B:D3:05 Paired: yes
Pairing successful
[CC-RT-BLE]# paired-devices
Device 00:1A:22:1B:D1:DA CC-RT-BLE
Device 00:1A:22:1B:D3:05 CC-RT-BLE
[CC-RT-BLE]#

reboot fhem
[CC-RT-BLE]# paired-devices
Device 00:1A:22:1B:D1:DA CC-RT-BLE
Device 00:1A:22:1B:D3:05 CC-RT-BLE
[CC-RT-BLE]# paired-devices
Device 00:1A:22:1B:D1:DA CC-RT-BLE
Device 00:1A:22:1B:D3:05 CC-RT-BLE
[CHG] Device 00:1A:22:1B:D1:DA ServicesResolved: no
[CHG] Device 00:1A:22:1B:D1:DA Paired: no
[CHG] Device 00:1A:22:1B:D1:DA Connected: no
[CHG] Device 00:1A:22:1B:D3:05 ServicesResolved: no
[CHG] Device 00:1A:22:1B:D3:05 Paired: no
[CHG] Device 00:1A:22:1B:D3:05 Connected: no
[bluetooth]# paired-devices
[CHG] Controller 8C:88:4B:07:12:97 Discovering: yes
[CHG] Device 00:1A:22:1B:D1:DA RSSI: -72
[CHG] Device 00:1A:22:1B:D3:05 RSSI: -66
[NEW] Device 55:F3:28:8F:61:C1 55-F3-28-8F-61-C1
[CHG] Device 55:F3:28:8F:61:C1 TxPower is nil
[CHG] Device 55:F3:28:8F:61:C1 RSSI is nil
[CHG] Device 00:1A:22:1B:D3:05 RSSI is nil
[CHG] Device 00:1A:22:1B:D1:DA RSSI is nil
[CHG] Controller 8C:88:4B:07:12:97 Discovering: no
[CHG] Device 00:1A:22:1B:D3:05 Connected: yes
[CHG] Device 00:1A:22:1B:D3:05 ServicesResolved: yes
[DEL] Device 55:F3:28:8F:61:C1 55-F3-28-8F-61-C1
[CHG] Device 00:1A:22:1B:D3:05 ServicesResolved: no
[CHG] Device 00:1A:22:1B:D3:05 Connected: no
[CHG] Controller 8C:88:4B:07:12:97 Discovering: yes
[CHG] Device 00:1A:22:1B:D1:DA RSSI: -66
[CHG] Device 00:1A:22:1B:D1:DA RSSI is nil
[CHG] Controller 8C:88:4B:07:12:97 Discovering: no
[CHG] Device 00:1A:22:1B:D3:05 Connected: yes
[CHG] Device 00:1A:22:1B:D3:05 ServicesResolved: yes
[CHG] Device 00:1A:22:1B:D3:05 ServicesResolved: no
[CHG] Device 00:1A:22:1B:D3:05 Connected: no
[CHG] Controller 8C:88:4B:07:12:97 Discovering: yes
[CHG] Device 00:1A:22:1B:D3:05 RSSI: -66
[CHG] Device 00:1A:22:1B:D1:DA RSSI: -60
[CHG] Device 00:1A:22:1B:D1:DA RSSI is nil
[CHG] Device 00:1A:22:1B:D3:05 RSSI is nil
[CHG] Controller 8C:88:4B:07:12:97 Discovering: no
[CHG] Device 00:1A:22:1B:D1:DA Connected: yes
[CHG] Device 00:1A:22:1B:D1:DA ServicesResolved: yes
[CHG] Device 00:1A:22:1B:D1:DA ServicesResolved: no
[CHG] Device 00:1A:22:1B:D1:DA Connected: no
[CHG] Controller 8C:88:4B:07:12:97 Discovering: yes
[CHG] Controller 8C:88:4B:07:12:97 Discovering: no
[CHG] Device 00:1A:22:1B:D1:DA Connected: yes
[CHG] Device 00:1A:22:1B:D1:DA ServicesResolved: yes
[CHG] Device 00:1A:22:1B:D1:DA ServicesResolved: no
[CHG] Device 00:1A:22:1B:D1:DA Connected: no
[CHG] Controller 8C:88:4B:07:12:97 Discovering: yes
[NEW] Device 55:F3:28:8F:61:C1 55-F3-28-8F-61-C1
[NEW] Device 5F:9D:18:CD:FF:79 5F-9D-18-CD-FF-79
[CHG] Device 00:1A:22:1B:D3:05 RSSI: -68
[CHG] Device 00:1A:22:1B:D3:05 RSSI is nil
[CHG] Device 5F:9D:18:CD:FF:79 RSSI is nil
[CHG] Device 55:F3:28:8F:61:C1 TxPower is nil
[CHG] Device 55:F3:28:8F:61:C1 RSSI is nil
[CHG] Controller 8C:88:4B:07:12:97 Discovering: no
[CHG] Controller 8C:88:4B:07:12:97 Discovering: yes
[CHG] Device 55:F3:28:8F:61:C1 RSSI: -100
[CHG] Device 55:F3:28:8F:61:C1 TxPower: 11
[NEW] Device 45:21:CA:18:EF:4B 45-21-CA-18-EF-4B
[CHG] Device 00:1A:22:1B:D3:05 RSSI: -68
[CHG] Device 00:1A:22:1B:D3:05 Connected: yes
[CHG] Device 00:1A:22:1B:D3:05 ServicesResolved: yes
[DEL] Device 5F:9D:18:CD:FF:79 5F-9D-18-CD-FF-79
[CHG] Device 00:1A:22:1B:D3:05 RSSI is nil
[CHG] Device 45:21:CA:18:EF:4B TxPower is nil
[CHG] Device 45:21:CA:18:EF:4B RSSI is nil
[CHG] Device 55:F3:28:8F:61:C1 TxPower is nil
[CHG] Device 55:F3:28:8F:61:C1 RSSI is nil
[CHG] Controller 8C:88:4B:07:12:97 Discovering: no
[DEL] Device 55:F3:28:8F:61:C1 55-F3-28-8F-61-C1
[DEL] Device 45:21:CA:18:EF:4B 45-21-CA-18-EF-4B
[CHG] Controller 8C:88:4B:07:12:97 Discovering: yes
[NEW] Device 55:F3:28:8F:61:C1 55-F3-28-8F-61-C1
[NEW] Device 4C:02:A7:CF:0D:48 4C-02-A7-CF-0D-48
[CHG] Device 00:1A:22:1B:D1:DA RSSI: -72
[CHG] Device 00:1A:22:1B:D1:DA RSSI is nil
[CHG] Device 4C:02:A7:CF:0D:48 TxPower is nil
[CHG] Device 4C:02:A7:CF:0D:48 RSSI is nil
[CHG] Device 55:F3:28:8F:61:C1 TxPower is nil
[CHG] Device 55:F3:28:8F:61:C1 RSSI is nil
[CHG] Controller 8C:88:4B:07:12:97 Discovering: no
[CHG] Device 00:1A:22:1B:D1:DA Connected: yes
[CHG] Device 00:1A:22:1B:D1:DA ServicesResolved: yes
[CC-RT-BLE]#

checked if still paired,  they are not, so pair and recheck.
[CC-RT-BLE]# paired-devices
[CC-RT-BLE]# pair 00:1A:22:1B:D1:DA
Attempting to pair with 00:1A:22:1B:D1:DA
[CHG] Device 00:1A:22:1B:D1:DA Paired: yes
Pairing successful
[CC-RT-BLE]# pair  00:1A:22:1B:D3:05
Attempting to pair with 00:1A:22:1B:D3:05
[CHG] Device 00:1A:22:1B:D3:05 Paired: yes
Pairing successful
[CC-RT-BLE]# paired-devices
Device 00:1A:22:1B:D1:DA CC-RT-BLE
Device 00:1A:22:1B:D3:05 CC-RT-BLE
[CC-RT-BLE]#

So for some reason fhempy drops the pairing and then fails to pair.  Not I don't have the keep_connected attribute so that will be at whatever is the default, "no" I assume.

Please try
bluetoothctl
remove 00:1A:22:1B:D1:DA
remove 00:1A:22:1B:D3:05

After that restart fhempy, wait a few minutes and check in bluetoothctl if the devices are paired.

That might have helped but it not cured the problem.  Eventually one thermostat has connected but one hasn't.  I wonder if the problem is that the large dongle is more sensitive than the small one and it is picking up bluetooth kit from next door (or maybe mine in another room, but I don't recognise it as mine).  With bluetoothctl running I see a lot of instances like this:
[CHG] Controller 8C:88:4B:07:12:97 Discovering: yes
[CHG] Device 00:1A:22:1B:D3:05 RSSI: -42
[NEW] Device 7A:7F:50:31:DB:61 7A-7F-50-31-DB-61
[CHG] Device 7A:7F:50:31:DB:61 TxPower is nil
[CHG] Device 7A:7F:50:31:DB:61 RSSI is nil
[CHG] Device 00:1A:22:1B:D3:05 RSSI is nil
[CHG] Controller 8C:88:4B:07:12:97 Discovering: no
[CHG] Device 00:1A:22:1B:D3:05 Connected: yes
[CHG] Device 00:1A:22:1B:D3:05 ServicesResolved: yes
[CHG] Device 00:1A:22:1B:D3:05 ServicesResolved: no
[CHG] Device 00:1A:22:1B:D3:05 Connected: no
[DEL] Device 7A:7F:50:31:DB:61 7A-7F-50-31-DB-61

The new/del pair mac address varies.  I've also caught this
[CHG] Device 00:1A:22:1B:D3:05 Connected: yes
Request passkey
[agent] Enter passkey (number in 0-999999): [CHG] Device 00:1A:22:1B:D3:05 ServicesResolved: yes
[agent] Enter passkey (number in 0-999999): [CHG] Device 00:1A:22:1B:D1:DA Connected: yes
[agent] Enter passkey (number in 0-999999): [CHG] Device 00:1A:22:1B:D1:DA ServicesResolved: yes
[agent] Enter passkey (number in 0-999999): [DEL] Device 44:C2:AC:A7:83:9B 44-C2-AC-A7-83-9B
[agent] Enter passkey (number in 0-999999): [CHG] Device 00:1A:22:1B:D3:05 ServicesResolved: no
[bluetooth]# [CHG] Device 00:1A:22:1B:D3:05 Connected: no
[bluetooth]# Request canceled

At this time ...DA is fully connected, ...05 is "connecting" and have been for a long time.
I've tried remove on both parts again but the end results in DA becomes fully connected again and 05 is still connecting.

Here is fhempy log after a a fhem shutdown restart
Activating virtual environment...OK
2024-02-16 14:11:23,170 - INFO     - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.721...
2024-02-16 14:11:23,190 - INFO     - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2024-02-16 14:11:23,658 - INFO     - websockets.server: server listening on <IP_ADDRESS>:15733
2024-02-16 14:11:33,081 - INFO     - websockets.server: connection open
2024-02-16 14:11:33,089 - INFO     - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: <IP_ADDRESS>
2024-02-16 14:12:10,660 - ERROR    - Eq3bt2: Timeout on update, retry in 60s
2024-02-16 14:12:29,561 - ERROR    - Eq3bt1: Timeout exceeded.
<pexpect.pty_spawn.spawn object at 0xb32588e0>
command: /usr/bin/bluetoothctl
args: [b'/usr/bin/bluetoothctl']
buffer (last 100 chars): 'ndor specific\r\nPairing successful\r\n[\x01\x1b[0;91m\x02DEL\x01\x1b[0m\x02] Device 76:F8:69:2E:2F:E6 76-F8-69-2E-2F-E6\r\n'
before (last 100 chars): 'ndor specific\r\nPairing successful\r\n[\x01\x1b[0;91m\x02DEL\x01\x1b[0m\x02] Device 76:F8:69:2E:2F:E6 76-F8-69-2E-2F-E6\r\n'
after: <class 'pexpect.exceptions.TIMEOUT'>
match: None
match_index: None
exitstatus: None
flag_eof: False
pid: 1714
child_fd: 14
closed: False
timeout: 30
delimiter: <class 'pexpect.exceptions.EOF'>
logfile: None
logfile_read: None
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
searcher: searcher_re:
    0: re.compile('#')
    1: EOF
2024-02-16 14:13:04,667 - ERROR    - Eq3bt1: Timeout exceeded.
<pexpect.pty_spawn.spawn object at 0xb32588e0>
command: /usr/bin/bluetoothctl
args: [b'/usr/bin/bluetoothctl']
buffer (last 100 chars): 'F8-69-2E-2F-E6\r\n\x1b[1;39m[agent] Enter passkey (number in 0-999999): \x1b[0mChanging power on succeeded\r\n'
before (last 100 chars): 'F8-69-2E-2F-E6\r\n\x1b[1;39m[agent] Enter passkey (number in 0-999999): \x1b[0mChanging power on succeeded\r\n'
after: <class 'pexpect.exceptions.TIMEOUT'>
match: None
match_index: None
exitstatus: None
flag_eof: False
pid: 1714
child_fd: 14
closed: False
timeout: 30
delimiter: <class 'pexpect.exceptions.EOF'>
logfile: None
logfile_read: None
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
searcher: searcher_re:
    0: re.compile('#')
    1: EOF
2024-02-16 14:13:34,738 - ERROR    - Eq3bt1: Timeout exceeded.
<pexpect.pty_spawn.spawn object at 0xb32588e0>
command: /usr/bin/bluetoothctl
args: [b'/usr/bin/bluetoothctl']
buffer (last 100 chars): '0:1A:22:1B:D3:05 ServicesResolved: no\r\n[\x01\x1b[0;93m\x02CHG\x01\x1b[0m\x02] Device 00:1A:22:1B:D3:05 Connected: no\r\n'
before (last 100 chars): '0:1A:22:1B:D3:05 ServicesResolved: no\r\n[\x01\x1b[0;93m\x02CHG\x01\x1b[0m\x02] Device 00:1A:22:1B:D3:05 Connected: no\r\n'
after: <class 'pexpect.exceptions.TIMEOUT'>
match: None
match_index: None
exitstatus: None
flag_eof: False
pid: 1714
child_fd: 14
closed: False
timeout: 30
delimiter: <class 'pexpect.exceptions.EOF'>
logfile: None
logfile_read: None
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
searcher: searcher_re:
    0: re.compile('#')
    1: EOF
2024-02-16 14:13:40,709 - ERROR    - Eq3bt2: Timeout on update, retry in 60s
2024-02-16 14:14:04,839 - ERROR    - Eq3bt1: Timeout exceeded.
<pexpect.pty_spawn.spawn object at 0xb32588e0>
command: /usr/bin/bluetoothctl
args: [b'/usr/bin/bluetoothctl']
buffer (last 100 chars): 'ected: no\r\n\x1b[1;39m[agent] Enter passkey (number in 0-999999): \x1b[0mDefault agent request successful\r\n'
before (last 100 chars): 'ected: no\r\n\x1b[1;39m[agent] Enter passkey (number in 0-999999): \x1b[0mDefault agent request successful\r\n'
after: <class 'pexpect.exceptions.TIMEOUT'>
match: None
match_index: None
exitstatus: None
flag_eof: False
pid: 1714
child_fd: 14
closed: False
timeout: 30
delimiter: <class 'pexpect.exceptions.EOF'>
logfile: None
logfile_read: None
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
searcher: searcher_re:
    0: re.compile('#')
    1: EOF
2024-02-16 14:14:34,929 - ERROR    - Eq3bt1: Timeout exceeded.
<pexpect.pty_spawn.spawn object at 0xb32588e0>
command: /usr/bin/bluetoothctl
args: [b'/usr/bin/bluetoothctl']
buffer (last 100 chars): 'evice 00:1A:22:1B:D3:05 RSSI: -66\r\n[\x01\x1b[0;92m\x02NEW\x01\x1b[0m\x02] Device 73:10:B0:7A:A8:30 73-10-B0-7A-A8-30\r\n'
before (last 100 chars): 'evice 00:1A:22:1B:D3:05 RSSI: -66\r\n[\x01\x1b[0;92m\x02NEW\x01\x1b[0m\x02] Device 73:10:B0:7A:A8:30 73-10-B0-7A-A8-30\r\n'
after: <class 'pexpect.exceptions.TIMEOUT'>
match: None
match_index: None
exitstatus: None
flag_eof: False
pid: 1714
child_fd: 14
closed: False
timeout: 30
delimiter: <class 'pexpect.exceptions.EOF'>
logfile: None
logfile_read: None
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
searcher: searcher_re:
    0: re.compile('#')
    1: EOF
2024-02-16 14:15:10,760 - ERROR    - Eq3bt2: Timeout on update, retry in 60s
2024-02-16 14:15:15,016 - ERROR    - Eq3bt1: Timeout exceeded.
<pexpect.pty_spawn.spawn object at 0xb32588e0>
command: /usr/bin/bluetoothctl
args: [b'/usr/bin/bluetoothctl']
buffer (last 100 chars): ':10:B0:7A:A8:30 73-10-B0-7A-A8-30\r\n[\x01\x1b[0;91m\x02DEL\x01\x1b[0m\x02] Device 76:F8:69:2E:2F:E6 76-F8-69-2E-2F-E6\r\n'
before (last 100 chars): ':10:B0:7A:A8:30 73-10-B0-7A-A8-30\r\n[\x01\x1b[0;91m\x02DEL\x01\x1b[0m\x02] Device 76:F8:69:2E:2F:E6 76-F8-69-2E-2F-E6\r\n'
after: <class 'pexpect.exceptions.TIMEOUT'>
match: None
match_index: None
exitstatus: None
flag_eof: False
pid: 1714
child_fd: 14
closed: False
timeout: 30
delimiter: <class 'pexpect.exceptions.EOF'>
logfile: None
logfile_read: None
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
searcher: searcher_re:
    0: re.compile('#')
    1: EOF
2024-02-16 14:15:49,114 - ERROR    - Eq3bt1: Timeout exceeded.
<pexpect.pty_spawn.spawn object at 0xb32588e0>
command: /usr/bin/bluetoothctl
args: [b'/usr/bin/bluetoothctl']
buffer (last 100 chars): '-43a0-8635-82ad38a1386f\r\n\tVendor specific\r\n[\x01\x1b[0;91m\x02DEL\x01\x1b[0m\x02] Device 00:1A:22:1B:D3:05 CC-RT-BLE\r\n'
before (last 100 chars): '-43a0-8635-82ad38a1386f\r\n\tVendor specific\r\n[\x01\x1b[0;91m\x02DEL\x01\x1b[0m\x02] Device 00:1A:22:1B:D3:05 CC-RT-BLE\r\n'
after: <class 'pexpect.exceptions.TIMEOUT'>
match: None
match_index: None
exitstatus: None
flag_eof: False
pid: 1714
child_fd: 14
closed: False
timeout: 30
delimiter: <class 'pexpect.exceptions.EOF'>
logfile: None
logfile_read: None
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
searcher: searcher_re:
    0: re.compile('#')
    1: EOF

Why is fhempy trying to connect to 76:F8:69:2E:2F:E6 76-F8-69-2E-2F-E6 ?  Neither part is connected currently, both just say connecting.  I can't even change the set temperature so I'm going to reboot the pi.

I've rebooted and I also check the number displayed when the pair button is pushed and that had changed for one.  Why I don't know.  It's not a typo because it was working on the other dongle and the number is way different.  I've changed that def statement (it was the one that would not connect before).  Both are now "connected" and seem to working.  There are some line in the log I'm not sure about.  I'll see what appears in the log at next boot tomorrow and report that, but for now it is working again although not 100% sure why.  Perhaps a combination of the remove and finding the change in key.

As far as I know the pairing key changes when you change the battery, but if the pairing was successfully done once, it keeps the paired connection active.
I'll try to add a reading which informs about the wrong pairing pin.

Please open a new issue if the error occurs again.


One question regarding the linear projection of AST.

Dear Minister Gong,
I wanted to express my gratitude for your work on AST; it has truly been an inspiration to me. I can confidently say that AST has served as my enlightenment teacher. However, I do have a question regarding the linear projection aspect of AST.
In the traditional methods like ViT and DeiT, the image is divided into patches (typically 16x16), and each patch is then passed through a linear projection, often implemented as a fully connected layer (torch.nn.Linear). However, upon examining the AST's code in ast_models.py, line 29, I noticed that a CNN layer (torch.nn.Conv2d) is used for the linear projection. It appears that all three models (ViT, DeiT, and AST) refer to this as the linear projection.
My question is: Does this imply that the linear projection can be either a CNN or a fully connected layer?
Please correct me if I have misunderstood anything.

hi there,
This is not just linear projection, it is splitting the spectrogram into patches and then do linear projection (which is implemented using a CNN layer).
-Yuan


Dice roller fixes

I think the visuals are in a place I'm comfortable with. Please let me know if anything's missing or wonky so this can go into main for bug testing.

Two notes on things that may or may not be intended behavior. If they are intended, you can ignore these.

Despite the cursor being hidden while the dice are rolling, button inputs can still change the number and size of dice mid-roll.
If you continuously tap the roll button, the dice will continue to roll. You have to stop tapping to get a result

If you're not using these assets, please remove them from the folder

goldCornerDR.png
woodTexture1.png

Did you mean to edit test-level.aseprite? Seems unrelated.

Allowing reroll during animation was intentional but now that you mention it it's probably better to block button input during a roll.

Okay, I think that addresses all comments.


CTI Holograms can show negative reinforcements

The actual reinforcement is correct, it's just the CTI hologram that is incorrect

I'm closing this issue as won't fix because there aren't consistent reproduction steps, and this is very rarely seen in practice.


Flag for checking visibility

Is it possible to check if an object is visible programmatically? I am using clipping planes and can change their position by scrolling with the mouse. It would be nice if shape objects such as spheres have flags indicating when they are visible or invisible.

There's no flag - it would need to be recalculated every frame as panning/moving can also make certain things invisible. The problem is visibility is calculated on the GPU (in the shader code) so you have to figure out how to get that information back out of the shader. You could do something a bit like it by using the picking mechanism, but it would involve a lot of rooting around in the internals, see:
https://github.com/arose/ngl/blob/d35e0135eea6d603e3375b65a2a209fd8c9b47b1/src/viewer/viewer.ts#L942
Steps would be something like:

Use renderer.readRenderTargetPixels to copy the entire picking image to a buffer (rather than a small square as in the code linked)
For each pixel in the buffer get the objectID (see line ~970)
Keep a list of which objects were visible and, therefore, work out which ones weren't...

Performance might well be an issue! (You'd either be executing a reasonable amount of javascript per-frame, or you'd do the update on a slower interval, in which case it would lag the view).

That's what I suspected. Thanks for enlightening me.

Ahh but now I found that this should be possible with frustum as in https://stackoverflow.com/questions/17624021/determine-if-a-mesh-is-visible-on-the-viewport-according-to-current-camera
Would anyone know if this is possible in NGL too? I don't seem to find a way to create a frustum object in NGL as in the  THREE.js example


Store Open Beauty Facts logos and icons within the app

It would simplify the task of updating the derived version of the app currently on the store

https://github.com/teolemon/OpenFoodFacts-androidApp/commit/d79611f8432483cbd92d9975ae0ce5dc6a14ff29

Above is the changes I made at the time.

Fixed by @itchix


Bug: A function transformed by JAX had a side effect ...

train.py terminates with the following error message:
jax._src.errors.UnexpectedTracerError: Encountered an unexpected tracer. A function transformed by JAX had a side effect, allowing for a reference to an intermediate value with shape (400,) and dtype float32 to escape.
JAX transformations require that functions explicitly return their outputs, and disallow saving intermediate values to global state.
The function being traced when the value leaked was update at /dreamax/dreamer/dreamer.py:140 traced for jit.
------------------------------
The leaked intermediate value was created on line /usr/local/lib/python3.8/dist-packages/jmp/_src/loss_scale.py:185 (select_tree).

Full stack trace:
Traceback (most recent call last):
  File "train.py", line 336, in <module>
    main()
  File "train.py", line 316, in main
    master_params = jax.tree_map(lambda x: jax.device_put(x, device=jax.devices('cpu')[0]), train_agent.params)
  File "/usr/local/lib/python3.8/dist-packages/jax/_src/tree_util.py", line 184, in tree_map
    return treedef.unflatten(f(*xs) for xs in zip(*all_leaves))
  File "/usr/local/lib/python3.8/dist-packages/jax/_src/tree_util.py", line 184, in <genexpr>
    return treedef.unflatten(f(*xs) for xs in zip(*all_leaves))
  File "train.py", line 316, in <lambda>
    master_params = jax.tree_map(lambda x: jax.device_put(x, device=jax.devices('cpu')[0]), train_agent.params)
  File "/usr/local/lib/python3.8/dist-packages/jax/_src/api.py", line 2667, in device_put
    return tree_map(lambda y: dispatch.device_put_p.bind(y, device=device), x)
  File "/usr/local/lib/python3.8/dist-packages/jax/_src/tree_util.py", line 184, in tree_map
    return treedef.unflatten(f(*xs) for xs in zip(*all_leaves))
  File "/usr/local/lib/python3.8/dist-packages/jax/_src/tree_util.py", line 184, in <genexpr>
    return treedef.unflatten(f(*xs) for xs in zip(*all_leaves))
  File "/usr/local/lib/python3.8/dist-packages/jax/_src/api.py", line 2667, in <lambda>
    return tree_map(lambda y: dispatch.device_put_p.bind(y, device=device), x)
  File "/usr/local/lib/python3.8/dist-packages/jax/core.py", line 323, in bind
    return self.bind_with_trace(find_top_trace(args), args, params)
  File "/usr/local/lib/python3.8/dist-packages/jax/core.py", line 981, in find_top_trace
    top_tracer._assert_live()
  File "/usr/local/lib/python3.8/dist-packages/jax/interpreters/partial_eval.py", line 1302, in _assert_live
    raise core.escaped_tracer_error(self, None)
jax._src.errors.UnexpectedTracerError: Encountered an unexpected tracer. A function transformed by JAX had a side effect, allowing for a reference to an intermediate value with shape (400,) and dtype float32 to escape.
JAX transformations require that functions explicitly return their outputs, and disallow saving intermediate values to global state.
The function being traced when the value leaked was update at /dreamax/dreamer/dreamer.py:140 traced for jit.
------------------------------
The leaked intermediate value was created on line /usr/local/lib/python3.8/dist-packages/jmp/_src/loss_scale.py:185 (select_tree).
------------------------------
When the value was created, the final 5 stack frames (most recent last) excluding JAX-internal frames were:
------------------------------
train.py:310 (main)
/dreamax/dreamer/dreamer.py:153 (update)
/dreamax/dreamer/dreamer.py:242 (update_actor)
/dreamax/dreamer/dreamer.py:288 (grad_step)
/usr/local/lib/python3.8/dist-packages/jmp/_src/loss_scale.py:185 (select_tree)
------------------------------

To catch the leak earlier, try setting the environment variable JAX_CHECK_TRACER_LEAKS or using the `jax.checking_leaks` context manager.
See https://jax.readthedocs.io/en/latest/errors.html#jax.errors.UnexpectedTracerError

see https://jax.readthedocs.io/en/latest/errors.html#jax.errors.UnexpectedTracerError

I could reproduce the error on two independent Unbuntu 20.04 machines with nvidia-driver Version: 510.60.02 / CUDA: 11.6 and jax version 0.3.7.

close with 1ff8933662a414dce6e42d2d1267e98b0f0f92ec / https://github.com/world-modelz/dreamax/commit/40c3966f90fc749a7b0ca0b94458905530997f83


Client side request are not cached

Hi, sorry for the disturb.
I'm using the data cache api and I was wondering if it was the normal functioning of the plugin that the client side returns undefined as the cached value.
Is there a way to make this work on the client side too?

The module is specifically only made for SSR caching. Especially the unstorage dependency would have to be included in the client bundle for a seamless experience, which would not be that great. And it would then also only be compatible with the memory driver. Of course it would be possible to hardcode a memory cache into the client side code of the composable.
On the client side you already have Nuxt's own utilities such as useState or useAsyncData available to implement your own caching. For a seamless experience, useDataCache would have to pass the cached data back to the client as a payload so it's available on hydration. However, when used together with useState or useAsyncData, the same data would then be passed as payload twice.
However, I do see the value of having a single useDataCache composable that handles both server and client caching. I will keep this open to explore possible solutions.

Thank you for your quick response. The problem with useState and useAsyncData is that at the moment it should do at least one time a graphql call on client side. If the data already persist in the cache i'd like to avoid that graphql call.
I don't know if my thought is right but I hope it can be useful

Yeah I know exactly what you mean! Just using useAsyncData out of the box will only return a cached value on hydration. You'd have to define your own getCachedData method in useAsyncData to make it work. That would give you the possibility to return cached data from payload. And when using transform you could also cache subsequent GraphQL calls done inside useAsyncData.

Thank you and sorry again. I know that this question can riuslt annoying.
What do you mean when you say "define my own getCachedData" method?
Do you think that a server endpoint that handle this for me can be a good solution? Or do you have an alternative idea?
🙏

You can pass a getCachedData method to the useAsyncData options: https://nuxt.com/docs/api/composables/use-async-data#params
By default, the getCachedData method is this:
key => nuxt.isHydrating ? nuxt.payload.data[key] : nuxt.static.data[key].
This will only load the cached data during hydration. But you can implement it as
key => nuxt.payload.data[key] || nuxt.static.data[key]
instead, which should also work after hydration.
Note that this only works on the client side. On the server these methods are not called, if I'm not mistaken.

Wow, simpler than i thought. It works fine with subsequent calls but in the client at the first access between one page and another it is always a new graphql when I am sure that the data has already been stored with the addToCache function.
`export async function useGqlData({ key, query, variables }, args) {
const transform = args?.transform
const options = {
...args,
cacheKey: key,
transform: undefined,
}
const nuxt = useNuxtApp()
const { $graphqlApi } = nuxt
return useAsyncData(
	key,
	async () => {
		const { value, addToCache } = await useDataCache(key)

		if (value) {
			return value
		} else {
			const res = await $graphqlApi({ query, variables })
			if (res.error || res.errors || !res.data) {
				console.error(res.error || res.errors || "No data found.")
				throw new Error("Error in fetching data")
			}

			const result = transform ? transform(res.data) : res.data

			if (key) {
				addToCache(result, options.cacheTags, options.cacheExpires)
			}
			return result
		}
	},
	{
		...options,
		getCachedData: (key) => {
			return nuxt.payload.data[key] || nuxt.static.data[key]
		},
	}
)

}
`
This is my custom useAsyncData

https://github.com/dulnan/nuxt-multi-cache/assets/32842043/b46bc3b2-7f08-40f4-b7b0-5f74a67b56e9

I would try to move const { value, addToCache } = await useDataCache(key) outside of useAsyncData into your composable. You might also need to enable the experimental asyncContext feature of Nuxt for this to work properly. Also keep in mind you should await addToCache, because it's possible that it never stores in cache if execution continues.

@plcdnl In #58 a new composable called useCachedAsyncData was implemented that now also implements a client-side cache. The plan is to also add this functionality to useDataCache in #59.
I hope to release the new composable some time next week.

Wow! Incredible work. Thank you ! 🙏

As this has already been released in the last release, I'm going to close this issue.


makefile: add target to create a new deps bundle

Signed-off-by: Nitin Goyal<EMAIL_ADDRESS>

/test odf-operator-e2e-aws

will you be removing the clubbing of other operators info in another PR?

Can you pls describe this?

will you be removing the clubbing of other operators info in another PR?

Can you pls describe this?

after this PR we'll only be interested in dependent operator channels and CSV isn't it and asked if other operator info, ie, name, namespace, catalog etc will still be required?

will you be removing the clubbing of other operators info in another PR?

Can you pls describe this?

after this PR we'll only be interested in dependent operator channels and CSV isn't it and asked if other operator info, ie, name, namespace, catalog etc will still be required?

Yes it will be required, We will still have to change the channel of the other operators.

This PR was never LGTM. GitHub shows it as merged because #499 (which was merged) included all its commits with identical hashes.


Proposal: add messages for HTML  tags

...a nice  message would have helped me right now.

Thanks for the proposal! Added some here: https://copybook.me/tags/noscript/


Feature: Site Notice

I'd like to display a site-wide notice at the top of each page. (like Sitenotice of Anonnotice in MediaWiki)
This feature is very useful to announce about maintenance and etc.

@shield-9 Thank you for your post.
I can't imagine that feature because I don't have enough experience to use MediaWiki.
Would you describe more details or post rough screen mock?

Japanese Wikipedia is currently using this feature (MediaWiki):

And this is rough mock for GROWI:

@shield-9 Thank you. Now I understand what you would like to.
We'll consider it.


Module 4 exercise[YAKUBU HUZIEMATA]

WS2_M4E1_ YAKUBU HUZIEMATA.docx

Well done, Huziemata. You clearly grasped the material outlined in Module 4 and successfully applied it to these exercises. Thank you for your participation! Please be sure to fill out the post-Module survey before you begin the next Module.


Return Result instead of stdout.

Currently, if the process has terminated with a non-zero return code, the exec method throws an exception.  Instead, the exec can return a Result structure storing the return code, stdout and stderr

@levBagryansky thanks!


Hello World in "Haskell" Programming Language

I wanna create a hello world program on 'Haskell' programming language

Sure, I will assign this issue to you!

Issue has been assigned to you under Hacktoberfest! @Arshad-ashuu

Happy contribution!


drivers: Fix asserts in i.MX UART Driver

After running some tests which enable assert macro I found some issues with the i.MX UART configuration.
This patch configures the Tx Fifo Watermark and Modem Mode accordingly.
Signed-off-by: Diego Sueiro<EMAIL_ADDRESS>

Codecov Report

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

@@          Coverage Diff           @@
##           master   #8938   +/-   ##
======================================
  Coverage    52.3%   52.3%
======================================
  Files         196     196
  Lines       24778   24778
  Branches     5152    5152
======================================
  Hits        12959   12959
  Misses       9740    9740
  Partials     2079    2079

Continue to review full report at Codecov.

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


Acquire FOV from ARCore

I am trying to fit some 3D menu items to fill the screen and it would be very helpful to be able to query the horizontal or vertical field of view when using ARCore.
I tried looking at the projection matrix calculation but the implementation for ArCamera_getProjectionMatrix seems to be in another library. If I could see how this matrix is constructed, I could work backward.

Check out the ComputerVision sample. It calculated the camera FOV based on the camera intrinsics there.

Thanks, I did find it tucked away in one of those BP's. If it helps anyone, here is the C++ equivalent using the image intrinsics:
const float FOVHor = 2.f * FMath::RadiansToDegrees(FMath::Atan2(ImageSizeX, 2.f * FocalLengthX));
const float FOVVer = 2.f * FMath::RadiansToDegrees(FMath::Atan2(ImageSizeY, 2.f * FocalLengthY));


Legend dash and dashdot

dash and dashdot lines have same legend style.
A bug here.
lines!(ax2,x,Va2,linestyle=:dash,linewidth =3,label="Objective")
lines!(ax2,x,Vmat1*EVa2_raw,linestyle=:dashdot,linewidth =3,label="Result")

I think the patchsize of the legend is just not wide enough to see the difference in pattern, it cuts off right at the dot. You can set it to something wider than the default.

f = Figure()
ax = Axis(f[1, 1])
lines!(ax, 1..10, cos, linestyle=:dash,linewidth =3,label="Objective")
lines!(ax, 1..10, sin, linestyle=:dashdot,linewidth =3,label="Result")
axislegend(ax, patchsize = (60, 30))
f


PoseC3D configuration about SlowFast network

Hi, it's really an amazing job! I really like it. But I didn't find the config about using SlowFast network (there is only SlowOnly network configuration). So could you offer a script about that? Thank you so much!

That's so great! Thank you very much!

I also wang to know how to integrate the classification results of video and pose. Is it just a simple weighted average of their scores？

are there any updates?

I am also interested, and I will try to make changes in the config file to make it like resnetslowfast. If I get lucky I will also share my config here.

@taliegemen Hi I am just wondering have you been able to implement the fusion of pose and rgb?

Hello,
Instead of implementing it i am now trying to maybe improve the backbone for recognition, or changing it with ResnetSlowFast. I think it should be easy to change it to ResnetSlowFast after looking at the code a little bit.
I think even if we use pose and rgb together we can not get much improvement, thats why i did not try to do it.

Finally, I have implemented RGBPoseConv3D in PYSKL 🤣 . The implementation is in PR #116 and has been merged to the main branch.


WGS84 Reference model?

Does this use an ellipsoid or spheroid reference model for WGS84? Are calculations done using geodesic (spatially accurate on globe) or planer geometry calculations (visually accurate on Mercator map)?

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

ID: 9c72695a-0bef-6a4b-0210-e02e4145f652
Version Independent ID: e29b6abf-a242-98c9-94e4-bfdc0885022e
Content: Working with geospatial data in Azure Cosmos DB SQL API account
Content Source: articles/cosmos-db/geospatial.md
Service: cosmos-db
GitHub Login: @SnehaGunda
Microsoft Alias: sngun

@rbrundritt , Thank you for your feedback. We will investigate and get back to you shortly.

@rbrundritt The GeoJSON is bases on RFC [7946] (https://tools.ietf.org/html/rfc7946). Please check the link if it helps you further. We are assigning this to author for further clarity.
@SnehaGunda Please check this further and help.

The GeoJSON spec doesn't specify how calculations should be done or which ellipsoid to use. Note, I'm on the Azure Maps team and we make heavy use of GeoJSON. Its just a data format, not a calculation method. Either reference model or calculation method could be used, but the results will differ. Trying to make sure we not the details as this makes a difference to many customers.

@rbrundritt I don't have any context about this issue. I sent an email to few folks on the Cosmos DB team who work on this area and CC'ed you. Let's track this issue via email.
I will close it here and track any doc updates with that email thread.
#please-close


Code intelligence will not be available for this file.

This issue is similar to https://github.com/BowlerHatLLC/vscode-as3mxml/issues/265 except I'm using older Adobe Flex AS3  libraries.

If I include Flex SDK sources into "source-path" I get like 100 compiler errors for Flex SDK .as files because (my guess) Apache royale cannot handle older libraries
If I don't include Flex SDK sources I get "Code intelligence will not be available for this file" errors for every .as file from Flex SDK

Is there a way to suppress this message for older Flex SDKs? Thank you.

I get like 100 compiler errors for Flex SDK .as files because (my guess) Apache royale cannot handle older libraries

It should be able to handle any ActionScript code. What kind of errors are you seeing? Most SDKs have source files separated across multiple projects (one for each SWC file), so could it be that you have not added everything?

I get "Code intelligence will not be available for this file" errors for every .as file from Flex SDK

Yeah, this is behaving as-designed. It happens when you open a source  file from inside any SDK, including Royale. Only your project's source files will have code intelligence. You can open a file from the SDK to read the code, but code intelligence features are purposefully disabled.
I'd like to improve this, but I haven't figured out how to do it right. As I mentioned, source files from an SDK are not located in a single convenient location, so there's a good chance of missing some dependencies that will result in false-positive errors that are not relevant to your project. That would be very confusing, so disabling code intelligence for files in the SDK is preferable.

Thank you for the clarification!

It should be able to handle any ActionScript code. What kind of errors are you seeing? Most SDKs have source files separated across multiple projects (one for each SWC file), so could it be that you have not added everything?

For one of the projects I'm using Flex SDK 3.6, here are the errors I'm receiving:
BoxLayout.as: Call to isVertical is not a function
(The isVertical is a private function defined in the same file)
CrossDomainRSLItem.as: Call to hasFailover is not a function.
(Same, defined in the same file)
ListRowInfo.as: Call to a possibly undefined method pop through a reference with static type ListRowInfo.
and etc etc etc
Those are original Adobe sources and the errors look weird like compiler doesn't understand the source.

Yeah, this is behaving as-designed. It happens when you open a source file from inside any SDK, including Royale. Only your project's source files will have code intelligence. You can open a file from the SDK to read the code, but code intelligence features are purposefully disabled.

Yes I understand that, the problem is I get these errors in the Problems of VS Code so every time the code is edited a check needed if those are actual code errors or just warning messages about code intelligence.

in the Problems of VS Code so every time the code is edited a check needed if those are actual code errors or just warning messages about code intelligence.

Hmm... I can't say that has ever bothered me. Maybe I tend to look in the status bar where each category of "Problem" has its own separate count rather than looking at the total sum. In the status bar, VSCode usually displays 2 or 3 icons, for ❌ errors, ⚠ warnings, and ℹ info.

It turns out that some of my recent refactoring made it much easier to add code intelligence to SDK files. You won't need to worry about this message anymore, starting in v0.21.

Thank you!


Enable pandas-style rounding of cftime.datetime objects

[x] Tests added
[x] Passes isort -rc . && black . && mypy . && flake8
[x] Fully documented, including whats-new.rst for all changes and api.rst for new API

This is particularly useful for removing microsecond noise that can sometimes be added from decoding times via cftime.num2date, though also applies more generally.  The methods used here for rounding dates in the integer domain are copied from pandas.
On a somewhat more internal note, this adds an asi8 property to CFTimeIndex, which encodes the dates as integer values representing microseconds since 1970-01-01; this encoding is made exact via the exact_cftime_datetime_difference function.  It's possible this could be useful in other contexts.
Some examples:
In [1]: import xarray as xr

In [2]: times = xr.cftime_range("2000", periods=5, freq="17D")

In [3]: time = xr.DataArray(times, dims=["time"], name="time")

In [4]: time.dt.floor("11D")
Out[4]:
<xarray.DataArray 'floor' (time: 5)>
array([cftime.DatetimeGregorian(1999-12-31 00:00:00),
       cftime.DatetimeGregorian(2000-01-11 00:00:00),
       cftime.DatetimeGregorian(2000-02-02 00:00:00),
       cftime.DatetimeGregorian(2000-02-13 00:00:00),
       cftime.DatetimeGregorian(2000-03-06 00:00:00)], dtype=object)
Coordinates:
  * time     (time) object 2000-01-01 00:00:00 ... 2000-03-09 00:00:00

In [5]: time.dt.ceil("11D")
Out[5]:
<xarray.DataArray 'ceil' (time: 5)>
array([cftime.DatetimeGregorian(2000-01-11 00:00:00),
       cftime.DatetimeGregorian(2000-01-22 00:00:00),
       cftime.DatetimeGregorian(2000-02-13 00:00:00),
       cftime.DatetimeGregorian(2000-02-24 00:00:00),
       cftime.DatetimeGregorian(2000-03-17 00:00:00)], dtype=object)
Coordinates:
  * time     (time) object 2000-01-01 00:00:00 ... 2000-03-09 00:00:00

In [6]: time.dt.round("11D")
Out[6]:
<xarray.DataArray 'round' (time: 5)>
array([cftime.DatetimeGregorian(1999-12-31 00:00:00),
       cftime.DatetimeGregorian(2000-01-22 00:00:00),
       cftime.DatetimeGregorian(2000-02-02 00:00:00),
       cftime.DatetimeGregorian(2000-02-24 00:00:00),
       cftime.DatetimeGregorian(2000-03-06 00:00:00)], dtype=object)
Coordinates:
  * time     (time) object 2000-01-01 00:00:00 ... 2000-03-09 00:00:00

Thanks @spencerkclark


Not Working, PLEASE FIX!!!!!

Undiscord Version
5.2.3
Browser
Firefox Latest
Extension
Violent Monkey
Reproduction steps
Clicked all the fields for deleting me, error pops up
Actual results
Error searching messages, API responded with status 401!
{"message":"401: Unauthorized","code":0}
CoreException	{}
Expected results
Wiping the messages
Bug affects

[X] DMs
[X] DMs (group)
[X] Channels
[X] Channel (NSFW)

Additional information & file uploads
Error searching messages, API responded with status 401!
{"message":"401: Unauthorized","code":0}
CoreException	{}

Problem with discord API, they put some weird rate limit which breaks this.

Problem with discord API, they put some weird rate limit which breaks this.

Well, hope the Dev can hurry up to review the new changes & fix things up. I use this to take care of some annoying people who join our discords.

Any update?

https://github.com/victornpb/undiscord/discussions/589#discussioncomment-8376052


[BEAM-12206] Update BigQuery IO documentation with quota and sharding information

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @chamikaramj @pabloem

Can you fix the whitespace precommit? It checks for trailing whitespaces on files
Everything else LGTM

Can you fix the whitespace precommit? It checks for trailing whitespaces on files
Everything else LGTM

Thanks! Removed the trailing whitespaces. I made some small adjustments as commented above. Let me know if the new changes make sense to you :)

@pabloem Hey Pablo, any more comments?

thanks @nehsyc !


chore: upgrade dependencies

Summary
The dependencies left to upgrade either require node 8, is micromatch or are covered by #8370

Test plan
Green CI

Not sure what's up with the error messages for jasmine or the onlyChanged test...


Change master branch to main

Rename the master branch to main to follow the new guidelines for GitHub

@hrwakeford this seems very easy to do, I have found example instructions here:
https://www.r-bloggers.com/2020/07/5-steps-to-change-github-default-branch-from-master-to-main/
Step 4 requires admin permissions though, as the new main branch will need to be assigned to be the default branch. Would you like me to do the first three steps, and then to reach out to you to finalize this?

Yeah that sounds good to me if you have time to do the first steps I will get it all finished off.

All right I'll get to it asap then, it doesn't seem to take much time. Will ping you when done.

@hrwakeford I am done with the first three steps from the above link. I also remembered that we will have to reset the branch protection rule from master to main, could I ask you do to the following?

On the repo, go to "Settings", and on the left to the menu button "Branches"
on the right you will find the part "Branch protection rules: find the entry for master and click edit
make a screenshot of those settings so that we can make sure we set up the same thing for main
close without changing anything

Then, as it turns out, we do not have to do Step number 4 in the above link, since the default branch on this repository is develop anyway.
So please just take a note of the current branch protection rules for master, let me know when you're done and I will proceed by deleting the master branch from the remote.
Let me know if I can be of any assistance.

I have screen shotted the settings we currently have. I assume you need to push the main branch and then remove the master branch. And then I go in and make sure the main branch has the same permissions and settings as before.
Correct?

That's exactly it. main is already pushed, I just need to delete master now. Do I have green lights from you to do that?
I have a full backup of the repo locally in case something goes wrong.

yes please do that now :)

Woops, we also need to un-protect the master branch first. Could you delete the branch protection rule for master?

did that work?

or if it is easier I can just press delete then you can push the main branch

The main is already pushed, but I still can't delete the master branch for some reason.

I believe I have now deleted master, left main, and updated the branch settings for main to mimic what we had for master.
This issue is now closed


Autocomplete suggestions not working

I haven't been able to get the unocss vscode extension to work. I'm using Svelte (vite).

My extensions

vite.config.ts

package.json

I've already tried the same configuration in a vue project and didn't work either. I also created a separate file unocss.config.js but same result.

A workaround is downgrading the version to v0.31.10. Closing this because it's better explained here #860


Bluetooth: Add API to iterate through existing bonds

So far the stack hasn't provided any way for the application to access
the existing bonds. This patch adds such an API.
Fixes #10122
Signed-off-by: Johan Hedberg<EMAIL_ADDRESS>

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@1c16cfc). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master   #10128   +/-   ##
=========================================
  Coverage          ?    52.5%
=========================================
  Files             ?      213
  Lines             ?    26140
  Branches          ?     5634
=========================================
  Hits              ?    13726
  Misses            ?    10159
  Partials          ?     2255

Impacted Files
Coverage Δ

include/bluetooth/bluetooth.h
0% <ø> (ø)

Continue to review full report at Codecov.

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

Discussing this with @carlescufi on IRC, we reached the consensus that starting off with a struct bt_bond_info from the start will afford us some flexibility in potentially extending this API in the future. So instead of being passed a bt_addr_le_t the callback will get a pointer to a struct bt_bond_info whose sole member (for now) is a bt_addr_le_t.


Automated cherry pick of #9345: fix(region): gpu server change config use reserved resources

Cherry pick of #9345 on release/3.6.
#9345: fix(region): gpu server change config use reserved resources

Codecov Report

Merging #9346 (b07387b) into release/3.6 (b9d30c0) will increase coverage by 1.38%.
The diff coverage is 1.04%.

@@              Coverage Diff               @@
##           release/3.6   #9346      +/-   ##
==============================================
+ Coverage         5.86%   7.24%   +1.38%
==============================================
  Files              828     354     -474
  Lines           129133   43828   -85305
==============================================
- Hits              7577    3177    -4400
+ Misses          120876   40318   -80558
+ Partials           680     333     -347

Flag
Coverage Δ

aFlag
7.24% <1.04%> (+1.38%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/apis/input.go
0.00% <ø> (ø)

pkg/apis/list.go
0.00% <ø> (ø)

pkg/cloudcommon/db/apply_manager_method.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/archs.go
0.00% <ø> (ø)

pkg/cloudcommon/db/db_dispatcher.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/modelbase.go
4.49% <0.00%> (-0.03%)
:arrow_down:

pkg/cloudcommon/db/models.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/quotas/errors.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/quotas/handler.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/quotas/register.go
11.11% <0.00%> (-2.41%)
:arrow_down:

... and 465 more

Continue to review full report at Codecov.

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


feat: Allow for overriding user-specified provisioning params with default values

This optional feature can be used to prevent users from specifying harmful provisioning parameters like the number of replicas where needed.

/assign f0rmiga

@aduffeck I rebased with master and pushed some commits to fix the feature. I could not get it to work as it was, especially because of the YAML lib that was being used. It would be great to have some integration tests before we merge it. Let me know if there're any issues with any of my commits.

/assign aduffeck

We will also need a good README explaining the process for figuring out the parameters that an operator may be interested in overriding.

/lgtm
/approve
There will be 2 separate PRs for more tests and documentation.


Document API appears to return success with incorrect auth token

Steps to reproduce:

Create a namespace

curl --request POST \
--url http://localhost:8082/v2/schemas/namespaces \
--header 'accept: application/json' \
--header "x-cassandra-token: c9be3193-4ee9-4d1a-8f19-3b07d635ad7b" \
--data '{"name": "library","replicas": "1"}'

Try to add a document (and be foolish by not adding your auth token!)

curl --request POST \
 --url http://localhost:8082/v2/namespaces/library/collections/books \
 --header "accept: application/json" \
 --header "content-type: application/json" \
 --header "x-cassandra-token: {your-auth-token-here}" \
 --data '{"title": "Dune",
          "author": "Frank Herbert",
          "genre": "Sci-Fi",
          "year": 1965 }'

Response:
{"documentId":"93c4951c-db5a-44bb-874e-abc12208f783"}

Mistakenly think it worked correctly so try to read back that document

curl --request GET \
--url http://localhost:8082/v2/namespaces/library/collections/books/93c4951c-db5a-44bb-874e-abc12208f783 \
--header 'accept: application/json' \
--header "x-cassandra-token: c9be3193-4ee9-4d1a-8f19-3b07d635ad7b"

Response
Unknown table 'library.books'

Be confused by "Unknown table" (I thought I was using documents?) and then realize you that there's a bug in the code but that you also messed up during Step 2!

Resolved by: https://github.com/stargate/stargate/pull/282


Minor README fixes - slack link and Dockerfile.Debian filename

Updated the link to the kafka-delta-ingest channel in Delta Users slack page and fixed the reference to the file Dockerfile.Debian (was called Dockerfile-Debian).  Closes #143

Clippy errors unrelated to change, merging anyways


docs: Add more Gateway deploy examples

Adds fontawesome icons to the portal and integrates them into the existing icon component. Use just like the heroicons except prefixed fa-. Edit: removed these because I don't think it's worth the increased bundle size. Just going to inline the icons we need instead.
Fixes #3041
Fixes #5072

bump @bmanifold


Use Template Parameters For Project GUIDs

As recommended by @hoensr in issue #119, template parameters are now used to ensure GUID uniqueness. This allows for creating and maintaining multiple test projects within a single solution.
Reference: https://msdn.microsoft.com/en-us/library/eehb4faa(v=vs.110).aspx
Closes #119

:+1:


In the Securing your GraphQL API documentation, the introductory sentence is difficult to read

Describe the bug
In the Securing your GraphQL API documentation the introductory sentence is difficult to read:

Building a secure GraphQL API is hard by design of to the because "Graph" part withing GraphQL.

To Reproduce
Steps to reproduce the behavior:

Visit: https://www.envelop.dev/docs/guides/securing-your-graphql-api
Read intro paragraph

Expected behavior
Perhaps reword this to:
Building a secure GraphQL API is hard by design because of the "Graph" nature of GraphQL.

Thank you 🙏


Doc Feedback: Image not rendered in Step5

Location : https://apim.docs.wso2.com/en/latest/learn/design-api/endpoints/endpoint-security/oauth-2.0/

we need to send this change to the master branch,


Implement extensions functions to make use of AL_EXT_float32 enums

Summary of the PR
Currently you have to explicitly cast FloatBufferFormat to BufferFormat to use the AL::BufferFormat function. alBufferFormat takes in two new enums provided by AL_EXT_float32  to provide the ability to load floating point data into openal buffer objects.
Related issues, Discord discussions, or proposals
Issue Ref: #1149
Spec Ref
Further Comments
There may be a possibility that the Capture feature of OpenAL supports floating point audio. I have no mind to include this because it adds more research that isn't easily presented in google. Silk.NET doesn't compile too well either. So, to keep it simple I won't add anything to do with anything other than what the spec AL_EXT_float32 says.

Want to get another maintainer's opinion before merging, as i dont think theres precedent for this kind of overload on extensions, and it only really applies to the manually generated bindings (like OpenAL)

I want to add a forethought, it appears that OpenAL-soft doesn't provide functionality for AL_EXT_vorbis and AL_EXT_mp3.
https://github.com/kcat/openal-soft/blob/master/al/buffer.cpp
https://github.com/kcat/openal-soft/blob/master/include/AL/alext.h
So by all means only AL_EXT_float32, AL_EXT_IMA4, AL_EXT_double, AL_EXT_MULAW, AL_EXT_ALAW would ideally need toyed with in the future for alBufferData
THAT IS,
if there was some friggin documentation on what to pass INTO alBufferData. Do I give it the whole mp3 file?! We will never know.

I want to add a forethought, it appears that OpenAL-soft doesn't provide functionality for AL_EXT_vorbis and AL_EXT_mp3.
https://github.com/kcat/openal-soft/blob/master/al/buffer.cpp https://github.com/kcat/openal-soft/blob/master/include/AL/alext.h
So by all means only AL_EXT_float32, AL_EXT_IMA4, AL_EXT_double, AL_EXT_MULAW, AL_EXT_ALAW would ideally need toyed with in the future for alBufferData
THAT IS,
if there was some friggin documentation on what to pass INTO alBufferData. Do I give it the whole [insert file format here] file?! We will never know.

@ohtrobinson you may be able to provide explination here on what alBufferData wants, i believe i know, but you may be able to explain better than i can, given you have more familiarity than i do

I'm not too sure myself, I've not experimented with it before. I can't find where I heard it, but I believe that (taking vorbis as an example) it specifically wants vorbis sound data, and you need to parse the headers yourself. All it can do is process the given data into a PCM stream, and doesn't do any actual loading.
There really isn't that much about these extensions anywhere online, and as such I would recommend avoiding them, instead opting to use StbVorbis and an MP3 loader. At least then you can guarantee that it will work, as well as working on machines that don't support the extension.
I'm surprised OpenAL soft doesn't appear to support vorbis, but I sorta understand, it's a royal pain to work with, especially in the way OpenAL works.

SoLoud is implemented with loading as well as playing audio. I would trial it to be a useful addition to sit alongside OpenAL, being that it has the zlib (basically MIT) license. They sure as hell did a good job keeping it free software in that regard too.
SoLoud: zlib/libpng
OGG: public domain
MP3: Unlicense
Wav: Unlicense
Speech Synth: Public domain (including author changes)
Vizsn (speech synth): Public domain
FFT: public domain
Sfxr: zlib/libpng
RPGMaker Wrapper Generator: BSDL (never claimed to be part of Ruby) but actually public domain
TED/SID soundchip emulation: public domain
Vic soundchip emulation: zlib/libpng
Openmpt (completely optional): BSD-3 https://opensource.org/licenses/BSD-3-Clause
FreeVerb: public domain
http://solhsa.com/soloud/legal.html
Would this be an interesting proposal?

We generally try to stick to well-known, industry-standard APIs specified by authoritative bodies for silk-provided bindings, with the exception of the HLU which binds to whatever library necessary to deliver its managed abstractions.
The audio space is very fragmented, heck to be honest it’s questionable why we even have OpenAL bindings given it’s not nearly as recognised or operated in the same way as their graphics counterparts. As such, I do not believe Silk.NET would have SoLoud bindings given this seems like we’re “picking” a preferred technology, and making our selection of bindings more opinionated.
However, the SilkCommunity has no such rules. If someone made SoLoud bindings/wrappers/utilities using our tech (be that our generator tech and/or Silk.NET.OpenAL itself to “tie” those libraries together) I’m sure the SilkCommunity would love to see it.
https://GitHub.com/SilkCommunity/SilkCommunity

We generally try to stick to well-known, industry-standard APIs specified by authoritative bodies for silk-provided bindings, with the exception of the HLU which binds to whatever library necessary to deliver its managed abstractions.
The audio space is very fragmented, heck to be honest it’s questionable why we even have OpenAL bindings given it’s not nearly as recognised or operated in the same way as their graphics counterparts. As such, I do not believe Silk.NET would have SoLoud bindings given this seems like we’re “picking” a preferred technology, and making our selection of bindings more opinionated.
However, the SilkCommunity has no such rules. If someone made SoLoud bindings/wrappers/utilities using our tech (be that our generator tech and/or Silk.NET.OpenAL itself to “tie” those libraries together) I’m sure the SilkCommunity would love to see it.
https://GitHub.com/SilkCommunity/SilkCommunity

To add to this, the generator is 95% of the way there to be able to generate SoLoud bindings (i believe there were a few random problems, but it mostly worked), so if someone wants to make them, @ me on discord, and ill help out best i can


[ENHANCEMENT] Allow search based on description

Is your feature request related to a problem? Please describe.
When a user currently searches without any terms, we search based on a feature's ID or name. However, both of those may not be obvious to the user. See https://github.com/GoogleChrome/webstatus.dev/issues/617
Describe the solution you'd like
To allow searching based on contents of the description may help with this.
Performance analysis should be done to see if we can add this to the existing no term query. Or should we require users to add a description term e.g. desc:@property
Also, in either case, we should consider expanding our allowed characters for certain characters. Like the @ sign.

Another approach is to keep the name: term specific to searching for features by name.
And for any search without a term, extend the search to include searching in the description as well.


Burnt message in toast

Can we burn the message into the toast?  like it was printed into the toast itself? (perhaps via a mask of some sort)

This is a great suggestion, it's actually what I was going for with the font and drop-shadow to make the text look a bit burnt into the toast. I didn't spend a lot of time on it though and it didn't end up really looking that way too much.
Maybe adding some transparency to the text to make the toast texture come through the lettering would help.


[BUG]The result of SyncCopyFromUriAsync may be corrupted

Library name and version
Azure.Storage.Blobs 12.14.0
Describe the bug
We use SyncCopyFromUriAsync to copy head images from Wechat to our own azure blob.
Sometimes the copied images are corrupted, losing some bytes at the end of file.
Expected behavior
Copied image should be integrated and same as the original ones.
Actual behavior
Sometimes,the copied images are corrupted,losing some bytes at the end of file.
For example,jpeg files lose EOI marker.

Reproduction Steps
public async Task<Uri> SyncCopyFromUriAsync(string containerName, string blobPath, Uri srcUri, string contentDisposition = "")
       {
            var blobClient = await this.GetBlobClientAsync(containerName, blobPath);
            await blobClient.SyncCopyFromUriAsync(srcUri);
            if (!string.IsNullOrWhiteSpace(contentDisposition))
            {
                var httpHeaders = new BlobHttpHeaders()
                {
                    ContentDisposition = contentDisposition
                };

                await blobClient.SetHttpHeadersAsync(httpHeaders).ConfigureAwait(false);
            }

            return blobClient.Uri;
        }

Environment
Docker in k8s with
.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.12 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.12 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
IDE:VS2022 17.4.3

@hitsjt Thanks for reaching out to us and reporting this issue. We are looking into this issue and we will provide an update.

Issue is being discussed internally with the Storage .Net Devs.

@hitsjt As discussed internally over email, please file an ICM and this issue would be looked further on that.


Fixed Spellings

Reading the documentation on docs.rs I noticed that this line seems to have some weird spellings.
This PR should fix them.

Thanks!


Update status of Concept Exercises

This issue is part of the migration to v3. You can read full details about the various changes here.
Concept Exercises can have a status specified in their "status" field in their config.json entry, as specified in the spec. This status can be one of four values:

"wip": A work-in-progress exercise not ready for public consumption. Exercises with this tag will not be shown to students on the UI or be used for unlocking logic. They may appear for maintainers.
"beta": This signifies active exercises that are new and which we would like feedback on. We show a beta label on the site for these exercise, with a Call To Action of "Please give us feedback."
"active": The normal state of active exercises
"deprecated": Exercises that are no longer shown to students who have not started them (not usable at this stage).

The "status" key can also be omitted, which is the equivalent of setting it to "active".
Goal
The "status" field of Concept Exercises in the config.json file should be updated to reflect the status of the Concept Exercises. See the spec for more information.
If your track doesn't have any Concept Exercises, this issue can be closed.
Example: removed wip status
{
  "exercises": {
    "concept": [
      {
        "uuid": "93fbc7cf-3a7e-4450-ad22-e30129c36bb9",
        "slug": "cars-assemble",
        "name": "Cars, Assemble!",
        "concepts": ["if-statements", "numbers"],
        "prerequisites": ["basics"]
      },
      ...
    ]
  }
}

Example: replaced wip status with active
{
  "exercises": {
    "concept": [
      {
        "uuid": "93fbc7cf-3a7e-4450-ad22-e30129c36bb9",
        "slug": "cars-assemble",
        "name": "Cars, Assemble!",
        "concepts": ["if-statements", "numbers"],
        "prerequisites": ["basics"],
        "status": "active"
      },
      ...
    ]
  }
}

Tracking
https://github.com/exercism/v3-launch/issues/14

Closing this as this track has no (active) Concept Exercises


Not getting remote stream on different networks, different wifi

I've tried different networks on android mobile to utilize easyrtc but its work fine for same wifi but not working in
different wifi
3g/4g to wifi
wifi to 3g/4g

@hafizImran need to use turn and stun service to make stable connection

Thank you @rtarta
@hafizImran see this doc:
https://github.com/open-easyrtc/open-easyrtc/blob/master/docs/easyrtc_server_ice.md
Note: this project is not maintain anymore we recommend to use Open-easyrtc instead. https://github.com/open-easyrtc/open-easyrtc


inner product distance support?

inner product distance support?

It seems there is support only for cosine distance？
what's the differences between cosine distance and normalized cosine distance?

I do think the FAISS lib supports only inner product rather than cosine distance is reasonable.
Because if inner product distance is supported, then vectors to be indexed can be handled offline, people can handwrite a process to standardize the indexed vectors and the query vector to get cosine distance.
But, if only cosine distance supported, you can never get a inner product distance.

NGT does not support inner product below which is not a distance function,

because NGT is a metric-based indexing method. Isn't the inner product distance you wrote this one above?
Although NGT supports cosine similarity which is also not a distance function, correctly NGT  supports pseudo cosine similarity below instead of exact cosine similarity.

When you specify normalized cosine similarity, stored vectors are normalized for each magnitude to be 1 before indexing. It means that the actual stored vectors are different from your specified vectors.
Supported distances

NGT does not support inner product below which is not a distance function,

because NGT is a metric-based indexing method. Isn't the inner product distance you wrote this one above?
Although NGT supports cosine similarity which is also not a distance function, correctly NGT supports pseudo cosine similarity below instead of exact cosine similarity.

When you specify normalized cosine similarity, stored vectors are normalized for each magnitude to be 1 before indexing. It means that the actual stored vectors are different from your specified vectors.
Supported distances

Well, actually, "inner product"(also known as "dot product")  is a distance function。 google Similarity Measures
We think it contains more information than cosine distance. We are using this kind of distance in our recommendation system, and it works well.
I'm a engineer rather than an algorithm expert.
And I wonder if any basic theory in this algorithm prevents it from being applied to dot product distance?
Or this algorithm  can be applied to any kind of distance if you want ?  I mean after a lot of coding job.

According to the definition of a distance function, inner product is not a distance function but a similarity measure. NGT is based on 1 - 4. Although 4 is not indispensable, functions that doesn't meet 4 reduce the accuracy. "inner product distance" you described looks like "maximum inner product search". If so, It is not nearest neighbor search NGT provides.
While consine similaity just represents angle of vectors, L1 or L2 represents more information than cosine similarity. However, I am not sure it works well.

According to the definition of a distance function, inner product is not a distance function but a similarity measure. NGT is based on 1 - 4. Although 4 is not indispensable, functions that doesn't meet 4 reduce the accuracy. "inner product distance" you described looks like "maximum inner product search". If so, It is not nearest neighbor search NGT provides.
While consine similaity just represents angle of vectors, L1 or L2 represents more information than cosine similarity. However, I am not sure it works well.

THANK YOU A LOT

Since the maximum inner product search can be transformed to the nearest neighbor search according to https://www.microsoft.com/en-us/research/wp-content/uploads/2016/02/XboxInnerProduct.pdf, I will consider implementing this. But I think it is not easy.

Since the maximum inner product search can be transformed to the nearest neighbor search according to https://www.microsoft.com/en-us/research/wp-content/uploads/2016/02/XboxInnerProduct.pdf, I will consider implementing this. But I think it is not easy.

We used another method.   We ensure all the vector , to be indexed, has the same lenght.   Cos(x,y)  = xy/|x||y|, where x is the query, y is the vectors to be searched, and |x|*|y| is a const number。The comparison between Inner products can be represented by cos distance.
However, the performance  deteriorated severely.

Thank you for the helpful advice.


Exclude _ from TypeScript key enum rendering

Reason/Context
Given an enum key such as something_something the enum renderer creates the following key SOMETHING_UNDERSCORE_SOMETHING even when TS fully supports SOMETHING_SOMETHING
Description
We need to add _ to the exclusion list here: https://github.com/asyncapi/modelina/blob/71ac65a5aafd44731f7d421aec88c2ccfbfc2cad/src/generators/typescript/renderers/EnumRenderer.ts#L53

we have to add exclude[ ' _ ' ] ???

we have to add exclude[ ' _ ' ] ???

Yes, excluding that we don't have to replace _ with underscore, as it is perfectly fine to have among the key for an enum 🙂

I'd like to work on this!

@all-contributors please add @Ishan-Saini for code and test


Step 9: Create comprehensive step-wise process checklist on README

Please see: https://spark.apache.org/release-process.html
for what we should be aiming for once all other steps are well understood (and documented individually).  They eventually all need to be brought together in some manner to create a top-to-bottom step-wise checklist.

@mrutkows
I think the tutorial can play the same role so far: https://github.com/apache/incubator-openwhisk-release#instruction-to-use-openwhisk-release


[Event Hubs Client] Idempotent Publishing Live Tests

Summary
The focus of these changes is to introduce the Live tests for the idempotent publishing feature, fix an error in AMQP metadata names, and address some delayed feedback from the previous set of changes.  The Live tests are currently disabled as the feature is not yet available across the public cloud and requires a special private resource to test against.
Note: These API changes are part of a preview feature. The design and API surface were informally reviewed with the language architect but have not yet undergone formal review with the architecture board. I expect some changes, particularly around naming.
Last Upstream Rebase
Thursday, September 24, 2:28pm (EDT)
References and Related Issues

Idempotent Publishing Design
Idempotent Publishing Requirements with Usage
Idempotent Publishing Support (#13941)

/azp run - eventhub - tests

/azp run net - eventhub - tests


update uglify-js package

I have an error as 'JS_Parse_Error' on uglify-js, so update it

Thanks for giving this a go.
This seems to be failing some tests on uglify.parse. If you'd be interested in fixing these cases further that would be a great help.

https://github.com/systemjs/builder/pull/815 is the proposed upgrade path here for full ES support.


feat: Add missing order getter to get item price

Related Issues

closes #5231
Short Description and Why It's Useful

Screenshots of Visual Changes before/after (if There Are Any)
no visual changes
Which Environment This Relates To
Check your case. In case of any doubts please read about Release Cycle

[ ] Test version (https://test.storefrontcloud.io) - this is a new feature or improvement for Vue Storefront. I've created branch from develop branch and want to merge it back to develop
[ ] RC version (https://next.storefrontcloud.io) - this is a stabilisation fix for Release Candidate of Vue Storefront. I've created branch from release branch and want to merge it back to release
[ ] Stable version (https://demo.storefrontcloud.io) - this is an important fix for current stable version. I've created branch from hotfix or master branch and want to merge it back to hotfix

Upgrade Notes and Changelog

[x] No upgrade steps required (100% backward compatibility and no breaking changes)
[ ] I've updated the Upgrade notes and Changelog on how to port existing Vue Storefront sites with this new feature

IMPORTANT NOTICE - Remember to update CHANGELOG.md with description of your change
Contribution and Currently Important Rules Acceptance

[ ] I read and followed contribution rules

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: justyna-13:x: JustynaJustyna seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


fix statement with non-compound name

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Fixed issues
PHP Warning - The use statement with non-compound name 'Yii' has no effect

$ composer run test
> phpunit
PHPUnit 10.5.8 by Sebastian Bergmann and contributors.

Runtime:       PHP 8.2.14
Configuration: /home/biladina/git/gii/phpunit.xml.dist

..................SSSSSSSSS..........................             53 / 53 (100%)

Time: 00:00.131, Memory: 6.00 MB

OK, but some tests were skipped!
Tests: 53, Assertions: 177, Skipped: 9.

👍


[QUESTION] seq2seq animated image creation process?

Does anyone know how the image in the README was created? i.e. what tools, environment, etc. I'd like to recreate it (which different sequence types of course) but I think its a great, teaching/learning tool. Thanks for any tips!!
https://camo.githubusercontent.com/a3c087bfca2eb44553f284ac13b19ccc27a333ed/68747470733a2f2f332e62702e626c6f6773706f742e636f6d2f2d3350626a5f64767430566f2f562d71652d4e6c365035492f41414141414141414251632f7a305f365774565774764152744d6b3069395f41744c6579794779563641493477434c63422f73313630302f6e6d742d6d6f64656c2d666173742e676966

Not 100% sure but it's probably d3.js. https://github.com/d3/d3/wiki/Gallery


Fixed filter form, now can submit filters either by attribute name, o…

…r by field name

@dahfool


Pascal Triangle code for c++

Issue:  Added a new pattern Pascal Triangle
Changes propsosed: In c++ -> pattern -> added new file
Errors: no error works very well
Mentions:

this file is empty!!


point to the new pkg.go.dev website for api docs

Proposed Changes

Use an image badge for godoc ref.
Update readme to be more like eventing.

Release Note

NONE

/lgtm


Add linting

I think prettier would be a good fit. It would save beginners having to worry excessively about linting. With prettier all the formatting is handled for you.
Open to discussion/suggestions on this!

I can take care of this.

 Any sort of specific rules that you would like for me to apply?

Aside from "tabWidth": 2, it's totally up to you! Whatever you feel makes sense. We can always update the linting rules at a later date

closed by #51


2022.2: Detected blocking call inside the event loop.

Heads up: here's a warning being logged after hte 2022.2 update:
2022-02-02 13:21:40 WARNING (MainThread) [homeassistant.util.async_] Detected blocking call inside the event loop. This is causing stability issues. Please report issue to the custom component author for ssh doing blocking calls at custom_components/ssh/sensor.py, line 136: self._ssh.login(self._host, self._username,
System Health

version
core-2022.2.0

installation_type
Home Assistant Container

dev
false

hassio
false

docker
true

user
root

virtualenv
false

python_version
3.9.7

os_name
Linux

os_version
5.10.28-Unraid

arch
x86_64

timezone
America/Los_Angeles

Home Assistant Community Store

GitHub API
ok

Github API Calls Remaining
4821

Installed Version
1.21.0

Stage
running

Available Repositories
978

Downloaded Repositories
30

@jchasey ?

I have the same issue:
`Logger: homeassistant.util.async_
Source: util/async_.py:180
First occurred: 5:40:40 PM (13 occurrences)
Last logged: 5:40:41 PM
Detected blocking call to sleep inside the event loop. This is causing stability issues. Please report issue to the custom integration author for ssh doing blocking calls at custom_components/ssh/sensor.py, line 136: self._ssh.login(self._host, self._username,`

Same issue in 2022.12.6

This went from WARNING to ERROR with the latest update... worked really nice until now
Detected blocking call to sleep inside the event loop by custom integration 'ssh' at custom_components/ssh/sensor.py, line 136: self._ssh.login(self._host, self._username, (offender: /usr/local/lib/python3.12/site-packages/pexpect/expect.py, line 113: time.sleep(self.spawn.delayafterread)), please report it to the author of the 'ssh' custom integration Traceback (most recent call last): File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module> sys.exit(main()) File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2064, in _async_forward_entry_setup result = await async_setup_component( File "/usr/src/homeassistant/homeassistant/setup.py", line 165, in async_setup_component result = await _async_setup_component(hass, domain, config) File "/usr/src/homeassistant/homeassistant/setup.py", line 402, in _async_setup_component result = await task File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 127, in async_setup await component.async_setup(config) File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 149, in async_setup self.hass.async_create_task_internal( File "/usr/src/homeassistant/homeassistant/core.py", line 828, in async_create_task_internal task = create_eager_task(target, name=name, loop=self.loop) File "/usr/src/homeassistant/homeassistant/util/async_.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 319, in async_setup_platform await self._platforms[key].async_setup(platform_config, discovery_info) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 303, in async_setup await self._async_setup_platform(async_create_setup_awaitable) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 363, in _async_setup_platform awaitable = create_eager_task(awaitable, loop=hass.loop) File "/usr/src/homeassistant/homeassistant/util/async_.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/config/custom_components/ssh/sensor.py", line 48, in async_setup_platform dev.append(SSHSensor(hass, config)) File "/config/custom_components/ssh/sensor.py", line 66, in __init__ self._connect() File "/config/custom_components/ssh/sensor.py", line 136, in _connect self._ssh.login(self._host, self._username,


PSAP support with regular updates

Benefit
Ensure PSAP centers have a low dispatch error rate; fulfill the contract responsibilities where applicable; and maintain the 911 fund income for UGRC.
Acceptance Criteria

[ ] Successfully updated all GIS data for each scheduled entity.
[ ] Begin editing on St. George and Beaver.
[ ] Establish a relationship with Logan, Tooele, and Summit Counties.

Sprint 1

[x] Weber

Sprint 2

[x] Weber

Sprint 3

[x] Weber

Sprint 4

Focused on geovalidation upgrades

Sprint 5

[ ] Beaver
[x] Weber
[ ] St George

Notes
No response
Risks
No response
Issue Reference
refs #202

hey, hank.  i can't remember, what psaps are getting updates for q3 sprint 1?
what do you think about creating a tentative list for each sprint with checkboxes?  it could probably be done in the main section above.

@mhchou i'll let you make the needed comments and close this feature out when it's time.