Lifx Beam Issues

Describe The Bug:
Lifx Beam is not working with Homebridge. I think This could be one of two things 1: the beam sends out non-standard manufacture and model info and this is normal or two there is an issue with my specific model. If I use the app "controller" I have, it shows as a manufacturer as Default-Manufacturer and Model as Default-Model I oddly see it listed twice in the app, the second time I see it as Lifx and Lifx Lightstrip
I did try to completely remove the light and then reset it via the button, but I'm still having issues. I am wondering if you were to just add those manufacturers and models to support it will just work. I don't code very much so idk if something that simple would work.
To Reproduce:
Try to add Lifx Beam to homebridge.
Expected behavior:
Normal operation
Logs:
[8/19/2023, 6:46:13 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:13 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:13 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:13 PM] Homebridge v1.6.1 (HAP v0.11.1) (Lifx Plugin) is running on port 53015.
[8/19/2023, 6:46:13 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Manufacturer': characteristic value expected string and received undefined. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:13 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Model': characteristic value expected string and received undefined. See https://homebridge.io/w/JtMGR for more info.
TypeError: Cannot read properties of undefined (reading 'temperature_range')
at Bulb.hasKelvin (/homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:64:47)
at LifxPlatformAccessory.bindFunctions (/homebridge/node_modules/homebridge-lifx-plugin/src/platformAccessory.ts:56:19)
at /homebridge/node_modules/homebridge-lifx-plugin/src/platformAccessory.ts:25:12
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:29:11
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:90:7
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:125:7
at Client. (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/light.js:236:5)
at Client. (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/client.js:451:26)
at Array.forEach ()
at Client.processMessageHandlers (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/client.js:438:24)
[8/19/2023, 6:46:13 PM] [Lifx Plugin] Child bridge process ended
[8/19/2023, 6:46:13 PM] [Lifx Plugin] Process Ended. Code: 1, Signal: null
[8/19/2023, 6:46:20 PM] [Lifx Plugin] Restarting Process...
[8/19/2023, 6:46:20 PM] [Lifx Plugin] Launched child bridge with PID 5491
[8/19/2023, 6:46:20 PM] Registering platform 'homebridge-lifx-plugin.LifxPlugin'
[8/19/2023, 6:46:20 PM] [Lifx Plugin] Loaded homebridge-lifx-plugin v0.2.4 child bridge successfully
[8/19/2023, 6:46:20 PM] Loaded 8 cached accessories from cachedAccessories.0EFBA205xxxx.
[8/19/2023, 6:46:20 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:20 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:20 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:20 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:20 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:20 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:20 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:20 PM] Homebridge v1.6.1 (HAP v0.11.1) (Lifx Plugin) is running on port 53015.
[8/19/2023, 6:46:21 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Manufacturer': characteristic value expected string and received undefined. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:21 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Model': characteristic value expected string and received undefined. See https://homebridge.io/w/JtMGR for more info.
TypeError: Cannot read properties of undefined (reading 'temperature_range')
at Bulb.hasKelvin (/homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:64:47)
at LifxPlatformAccessory.bindFunctions (/homebridge/node_modules/homebridge-lifx-plugin/src/platformAccessory.ts:56:19)
at /homebridge/node_modules/homebridge-lifx-plugin/src/platformAccessory.ts:25:12
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:29:11
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:90:7
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:125:7
at Client. (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/light.js:236:5)
at Client. (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/client.js:451:26)
at Array.forEach ()
at Client.processMessageHandlers (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/client.js:438:24)
[8/19/2023, 6:46:21 PM] [Lifx Plugin] Child bridge process ended
[8/19/2023, 6:46:21 PM] [Lifx Plugin] Process Ended. Code: 1, Signal: null
[8/19/2023, 6:46:28 PM] [Lifx Plugin] Restarting Process...
[8/19/2023, 6:46:28 PM] [Lifx Plugin] Launched child bridge with PID 5503
[8/19/2023, 6:46:28 PM] Registering platform 'homebridge-lifx-plugin.LifxPlugin'
[8/19/2023, 6:46:28 PM] [Lifx Plugin] Loaded homebridge-lifx-plugin v0.2.4 child bridge successfully
[8/19/2023, 6:46:28 PM] Loaded 8 cached accessories from cachedAccessories.0EFBA205xxxx.
[8/19/2023, 6:46:28 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:28 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:28 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:28 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:28 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:28 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:28 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:28 PM] Homebridge v1.6.1 (HAP v0.11.1) (Lifx Plugin) is running on port 53015.
[8/19/2023, 6:46:29 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Manufacturer': characteristic value expected string and received undefined. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:29 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Model': characteristic value expected string and received undefined. See https://homebridge.io/w/JtMGR for more info.
TypeError: Cannot read properties of undefined (reading 'temperature_range')
at Bulb.hasKelvin (/homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:64:47)
at LifxPlatformAccessory.bindFunctions (/homebridge/node_modules/homebridge-lifx-plugin/src/platformAccessory.ts:56:19)
at /homebridge/node_modules/homebridge-lifx-plugin/src/platformAccessory.ts:25:12
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:29:11
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:90:7
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:125:7
at Client. (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/light.js:236:5)
at Client. (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/client.js:451:26)
at Array.forEach ()
at Client.processMessageHandlers (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/client.js:438:24)
[8/19/2023, 6:46:29 PM] [Lifx Plugin] Child bridge process ended
[8/19/2023, 6:46:29 PM] [Lifx Plugin] Process Ended. Code: 1, Signal: null
[8/19/2023, 6:46:36 PM] [Lifx Plugin] Restarting Process...
[8/19/2023, 6:46:36 PM] [Lifx Plugin] Launched child bridge with PID 5517
[8/19/2023, 6:46:36 PM] Registering platform 'homebridge-lifx-plugin.LifxPlugin'
[8/19/2023, 6:46:36 PM] [Lifx Plugin] Loaded homebridge-lifx-plugin v0.2.4 child bridge successfully
[8/19/2023, 6:46:36 PM] Loaded 8 cached accessories from cachedAccessories.0EFBA205xxxx.
[8/19/2023, 6:46:36 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:36 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:36 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:36 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:36 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:36 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:36 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:36 PM] Homebridge v1.6.1 (HAP v0.11.1) (Lifx Plugin) is running on port 53015.
[8/19/2023, 6:46:36 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Manufacturer': characteristic value expected string and received undefined. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:36 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Model': characteristic value expected string and received undefined. See https://homebridge.io/w/JtMGR for more info.
TypeError: Cannot read properties of undefined (reading 'temperature_range')
at Bulb.hasKelvin (/homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:64:47)
at LifxPlatformAccessory.bindFunctions (/homebridge/node_modules/homebridge-lifx-plugin/src/platformAccessory.ts:56:19)
at /homebridge/node_modules/homebridge-lifx-plugin/src/platformAccessory.ts:25:12
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:29:11
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:90:7
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:125:7
at Client. (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/light.js:236:5)
at Client. (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/client.js:451:26)
at Array.forEach ()
at Client.processMessageHandlers (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/client.js:438:24)
[8/19/2023, 6:46:36 PM] [Lifx Plugin] Child bridge process ended
[8/19/2023, 6:46:36 PM] [Lifx Plugin] Process Ended. Code: 1, Signal: null
[8/19/2023, 6:46:43 PM] [Lifx Plugin] Restarting Process...
[8/19/2023, 6:46:43 PM] [Lifx Plugin] Launched child bridge with PID 5529
[8/19/2023, 6:46:43 PM] Registering platform 'homebridge-lifx-plugin.LifxPlugin'
[8/19/2023, 6:46:43 PM] [Lifx Plugin] Loaded homebridge-lifx-plugin v0.2.4 child bridge successfully
[8/19/2023, 6:46:43 PM] Loaded 8 cached accessories from cachedAccessories.0EFBA205xxxx.
[8/19/2023, 6:46:44 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:44 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:44 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:44 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:44 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:44 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:44 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:44 PM] Homebridge v1.6.1 (HAP v0.11.1) (Lifx Plugin) is running on port 53015.
[8/19/2023, 6:46:44 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Manufacturer': characteristic value expected string and received undefined. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:44 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Model': characteristic value expected string and received undefined. See https://homebridge.io/w/JtMGR for more info.
TypeError: Cannot read properties of undefined (reading 'temperature_range')
at Bulb.hasKelvin (/homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:64:47)
at LifxPlatformAccessory.bindFunctions (/homebridge/node_modules/homebridge-lifx-plugin/src/platformAccessory.ts:56:19)
at /homebridge/node_modules/homebridge-lifx-plugin/src/platformAccessory.ts:25:12
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:29:11
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:90:7
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:125:7
at Client. (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/light.js:236:5)
at Client. (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/client.js:451:26)
at Array.forEach ()
at Client.processMessageHandlers (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/client.js:438:24)
[8/19/2023, 6:46:44 PM] [Lifx Plugin] Child bridge process ended
[8/19/2023, 6:46:44 PM] [Lifx Plugin] Process Ended. Code: 1, Signal: null
[8/19/2023, 6:46:51 PM] [Lifx Plugin] Restarting Process...
[8/19/2023, 6:46:51 PM] [Lifx Plugin] Launched child bridge with PID 5543
[8/19/2023, 6:46:51 PM] Registering platform 'homebridge-lifx-plugin.LifxPlugin'
[8/19/2023, 6:46:51 PM] [Lifx Plugin] Loaded homebridge-lifx-plugin v0.2.4 child bridge successfully
[8/19/2023, 6:46:51 PM] Loaded 8 cached accessories from cachedAccessories.0EFBA205xxxx.
[8/19/2023, 6:46:51 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:51 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:51 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:51 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:51 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:51 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:51 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:51 PM] Homebridge v1.6.1 (HAP v0.11.1) (Lifx Plugin) is running on port 53015.
[8/19/2023, 6:46:52 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Manufacturer': characteristic value expected string and received undefined. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:52 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Model': characteristic value expected string and received undefined. See https://homebridge.io/w/JtMGR for more info.
TypeError: Cannot read properties of undefined (reading 'temperature_range')
at Bulb.hasKelvin (/homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:64:47)
at LifxPlatformAccessory.bindFunctions (/homebridge/node_modules/homebridge-lifx-plugin/src/platformAccessory.ts:56:19)
at /homebridge/node_modules/homebridge-lifx-plugin/src/platformAccessory.ts:25:12
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:29:11
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:90:7
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:125:7
at Client. (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/light.js:236:5)
at Client. (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/client.js:451:26)
at Array.forEach ()
at Client.processMessageHandlers (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/client.js:438:24)
[8/19/2023, 6:46:52 PM] [Lifx Plugin] Child bridge process ended
[8/19/2023, 6:46:52 PM] [Lifx Plugin] Process Ended. Code: 1, Signal: null
[8/19/2023, 6:46:59 PM] [Lifx Plugin] Restarting Process...
[8/19/2023, 6:46:59 PM] [Lifx Plugin] Launched child bridge with PID 5555
[8/19/2023, 6:46:59 PM] Registering platform 'homebridge-lifx-plugin.LifxPlugin'
[8/19/2023, 6:46:59 PM] [Lifx Plugin] Loaded homebridge-lifx-plugin v0.2.4 child bridge successfully
[8/19/2023, 6:46:59 PM] Loaded 8 cached accessories from cachedAccessories.0EFBA205xxxx.
[8/19/2023, 6:46:59 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:59 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:59 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:59 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:59 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:59 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:59 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:46:59 PM] Homebridge v1.6.1 (HAP v0.11.1) (Lifx Plugin) is running on port 53015.
[8/19/2023, 6:47:44 PM] [Lifx Plugin] Bulb  throughs error setFirmwareVersionError: No LIFX response in time
Error: A Controller with the type/id 'characteristic-transition-00000043-0000-1000-8000-0026BB765291' was already added to the accessory xxx
at Accessory.configureController (/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:847:13)
at PlatformAccessory.configureController (/homebridge/node_modules/homebridge/src/platformAccessory.ts:148:34)
at LifxPlatformAccessory.bindFunctions (/homebridge/node_modules/homebridge-lifx-plugin/src/platformAccessory.ts:63:24)
at /homebridge/node_modules/homebridge-lifx-plugin/src/platformAccessory.ts:25:12
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:29:11
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:90:7
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:125:7
at Client. (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/light.js:226:14)
at Client. (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/client.js:466:24)
at Array.forEach ()
[8/19/2023, 6:47:44 PM] [Lifx Plugin] Child bridge process ended
[8/19/2023, 6:47:44 PM] [Lifx Plugin] Process Ended. Code: 1, Signal: null
[8/19/2023, 6:47:51 PM] [Lifx Plugin] Restarting Process...
[8/19/2023, 6:47:52 PM] [Lifx Plugin] Launched child bridge with PID 5578
[8/19/2023, 6:47:52 PM] Registering platform 'homebridge-lifx-plugin.LifxPlugin'
[8/19/2023, 6:47:52 PM] [Lifx Plugin] Loaded homebridge-lifx-plugin v0.2.4 child bridge successfully
[8/19/2023, 6:47:52 PM] Loaded 8 cached accessories from cachedAccessories.0EFBA2051xxxx.
[8/19/2023, 6:47:52 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:47:52 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:47:52 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:47:52 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:47:52 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:47:52 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:47:52 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:47:52 PM] Homebridge v1.6.1 (HAP v0.11.1) (Lifx Plugin) is running on port 53015.
[8/19/2023, 6:47:52 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Manufacturer': characteristic value expected string and received undefined. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:47:52 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Model': characteristic value expected string and received undefined. See https://homebridge.io/w/JtMGR for more info.
TypeError: Cannot read properties of undefined (reading 'temperature_range')
at Bulb.hasKelvin (/homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:64:47)
at LifxPlatformAccessory.bindFunctions (/homebridge/node_modules/homebridge-lifx-plugin/src/platformAccessory.ts:56:19)
at /homebridge/node_modules/homebridge-lifx-plugin/src/platformAccessory.ts:25:12
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:29:11
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:90:7
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:125:7
at Client. (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/light.js:236:5)
at Client. (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/client.js:451:26)
at Array.forEach ()
at Client.processMessageHandlers (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/client.js:438:24)
[8/19/2023, 6:47:52 PM] [Lifx Plugin] Child bridge process ended
[8/19/2023, 6:47:52 PM] [Lifx Plugin] Process Ended. Code: 1, Signal: null
[8/19/2023, 6:47:59 PM] [Lifx Plugin] Restarting Process...
[8/19/2023, 6:47:59 PM] [Lifx Plugin] Launched child bridge with PID 5590
[8/19/2023, 6:47:59 PM] Registering platform 'homebridge-lifx-plugin.LifxPlugin'
[8/19/2023, 6:47:59 PM] [Lifx Plugin] Loaded homebridge-lifx-plugin v0.2.4 child bridge successfully
[8/19/2023, 6:47:59 PM] Loaded 8 cached accessories from cachedAccessories.0EFBA205xxxx.
[8/19/2023, 6:47:59 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:47:59 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:47:59 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:47:59 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:47:59 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:47:59 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:47:59 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:47:59 PM] Homebridge v1.6.1 (HAP v0.11.1) (Lifx Plugin) is running on port 53015.
[8/19/2023, 6:48:00 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Manufacturer': characteristic value expected string and received undefined. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:48:00 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Model': characteristic value expected string and received undefined. See https://homebridge.io/w/JtMGR for more info.
TypeError: Cannot read properties of undefined (reading 'temperature_range')
at Bulb.hasKelvin (/homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:64:47)
at LifxPlatformAccessory.bindFunctions (/homebridge/node_modules/homebridge-lifx-plugin/src/platformAccessory.ts:56:19)
at /homebridge/node_modules/homebridge-lifx-plugin/src/platformAccessory.ts:25:12
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:29:11
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:90:7
at /homebridge/node_modules/homebridge-lifx-plugin/src/bulb.ts:125:7
at Client. (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/light.js:236:5)
at Client. (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/client.js:451:26)
at Array.forEach ()
at Client.processMessageHandlers (/homebridge/node_modules/homebridge-lifx-plugin/node_modules/lifx-lan-client/lib/lifx/client.js:438:24)
[8/19/2023, 6:48:00 PM] [Lifx Plugin] Child bridge process ended
[8/19/2023, 6:48:00 PM] [Lifx Plugin] Process Ended. Code: 1, Signal: null
[8/19/2023, 6:48:07 PM] [Lifx Plugin] Restarting Process...
[8/19/2023, 6:48:07 PM] [Lifx Plugin] Launched child bridge with PID 5604
[8/19/2023, 6:48:07 PM] Registering platform 'homebridge-lifx-plugin.LifxPlugin'
[8/19/2023, 6:48:07 PM] [Lifx Plugin] Loaded homebridge-lifx-plugin v0.2.4 child bridge successfully
[8/19/2023, 6:48:07 PM] Loaded 8 cached accessories from cachedAccessories.0EFBA205xxxx.
[8/19/2023, 6:48:07 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:48:07 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:48:07 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:48:07 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:48:07 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:48:07 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:48:07 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service AccessoryInformation. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:48:07 PM] Homebridge v1.6.1 (HAP v0.11.1) (Lifx Plugin) is running on port 53015.
[8/19/2023, 6:48:52 PM] [Lifx Plugin] Bulb  throughs error setHardwareInformationError: No LIFX response in time
[8/19/2023, 6:48:52 PM] [Lifx Plugin] Bulb  throughs error setHardwareInformationError: No LIFX response in time
[8/19/2023, 6:48:53 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Manufacturer': characteristic value expected string and received undefined. See https://homebridge.io/w/JtMGR for more info.
[8/19/2023, 6:48:53 PM] [homebridge-lifx-plugin] This plugin generated a warning from the characteristic 'Model': characteristic value expected string and received undefined. See https://homebridge.io/w/JtMGR for more info.
Show the Homebridge logs here, remove any sensitive information.

Plugin Config:
{
    "bridge": {
        "name": "Homebridge 3CxXD",
        "username": "0E:XX:81:CX:3C:XX",
        "port": 51037,
        "pin": "xxx-xxx-xxx",
        "advertiser": "ciao"
    },
    "accessories": [],
    "platforms": [
        {
            "name": "Config",
            "port": 8581,
            "auth": "form",
            "theme": "dark-mode-cyan",
            "tempUnits": "c",
            "lang": "auto",
            "platform": "config"
        },
        {
            "name": "Govee",
            "username": "xxx",
            "password": "XXX",
            "platform": "Govee",
            "_bridge": {
                "username": "XXX",
                "port": 53062
            }
        },
        {
            "name": "IFTTT",
            "platform": "IFTTT"
        },
        {
            "name": "Lifx Plugin",
            "duration": 0,
            "brightnessDuration": 300,
            "colorDuration": 300,
            "default": "<IP_ADDRESS>",
            "broadcast": "<IP_ADDRESS>",
            "lightOfflineTolerance": 3,
            "messageHandlerTimeout": 45000,
            "resendPacketDelay": 150,
            "resendMaxTimes": 3,
            "updates": true,
            "debug": false,
            "autoDiscover": true,
            "platform": "LifxPlugin",
            "_bridge": {
                "username": "0E:FB:A2:XX:1C:XX",
                "port": 53015
            }
        }
    ],
    "disabledPlugins": [
        "homebridge-lg-thinq",
        "homebridge-messenger",
        "homebridge-webos-tv",
        "homebridge-alexa",
        "homebridge-ifttt",
        "homebridge-linak"
    ]
}```

**Screenshots:**
<!-- If applicable, add screenshots to help explain your problem. -->

**Environment:**

All Up to date running on windows vm.

Note: Things seem to be wonky with adaptive lighting since adding the beam, I also can't change the temp of the color lights via home kit. I had to remove my grouping and re-group them to get the group to work after adding the beam to that group. Simply removing the beam didn't fix the issue.
Looking at the beam in home kit, its showing manufacture and model as default as I laid it out above.


Slash on S3 credentials causes problems

Hello,
this will fail if a S3 secret key has any "/" on it, which can happen quite often.
The problem seems to be in __parseUrl().
Perhaps checking for the length of username and password in the s3 case could help?
Thanks!
Regards,
Robert

Thanks quiuquio. I will check it and fix the issue detected.
Regards!

Hi @quiuquio,
Now you can use any credential containing / before @ (not only s3).
Hope this helps.
Regards and enjoy,


Add blank link at end of file in config

Description
Adding blank line at the end of the file in config.

Hi there,
Please create a single PR for adding the blank line at the end of the file of all packages.


Conjunction removal in English isn't working

It seems it was already fixed by the time I first opened the issue


How to use it as a simple react redux boilerplate?

I love this boilerplate but I'm not really interested in the whole node server setup with the serverside rendering and all. How easy is it to remove all of the proxying api calls and removing the whole serverside part of it to make it a simple react redux boilerplate?
If that's too difficult, is there a way to at the least not proxy those api calls?

The whole webpack hot-reloading magic is a bit tied to the server stuff, because webpack outputs a webstats.json that is read by the server to use the proper js and css files, but we already have a way to disable server-side rendering and only do react and redux stuff on the client. It should just be a matter of trimming the fat little by little, and, when things break, figuring out why.

@erikras Since we don't need the hot reloading magic in production and if I don't want the server side rendering from node, are we able to simply serve the static files (.js, .css) in production? This is why I'm wondering if we can easily disable the proxying of the api calls through node.

The answer is, "Yes, it should be pretty easy."

@erikras Close this.


Put the init code

Where do you recomend initialize the owlCarousel? i try on the rendered function but just getting plain/text witouth effects

If the slider is only for some of you pages. Maybe initial them in onRendered(or onCreated) is a better.
Something like
Template.xxxx.onRendered ->
  this.$(".owl-carousel").owlCarousel()

This works for me...
Template.main.onRendered(function(){
	initSlider();
})

initSlider = function() {
	$(document).ready(function() {

		$("#home-slider").owlCarousel({

			autoPlay: 3000, //Set AutoPlay to 3 seconds

			items : 1,
			itemsDesktop : [1199,3],
			itemsDesktopSmall : [979,3]

		});

	});
}

Hello guys.
The best way to initialize the owlCarousel in the meteor is from the helper function.

In html/template FIle.
Add Template handler like in our case {{initializeCarousel}} in html file. This is to be added where your html snippets ends.

In helper File.
Template.carousle.helpers({
initializeCarousel: function(){
Deps.autorun(function() {
var owl = $('#owl-demo').length;
Tracker.afterFlush(function(){
$(owl).owlCarousel({
autoPlay: 3000, //Set AutoPlay to 3 seconds
items : 1,
itemsDesktop : [1199,3],
itemsDesktopSmall : [979,3]});
});
});
});
}
});

This is the way when the required html loads in the DOM and on the calling of the helper handler initiates carousel when required the owl instance.
This snippet works well as per our requirement and listed here with minimal changes for the purpose of example.
If stuck anywhere feel free to ask.
Thanks,
Mohinder Thakur.

@mahiagit Thanks a lot! You saved my day!


Farming house activity is not normal. Only between them 17 devices

Hotspot b58 Addresses

Wallet;
1: https://explorer.helium.com/hotspots/11WTVK9QHCfjt4h1fLhQcWJpUs9Cc97pNhKULEPLuTrgJJuahvu

2: https://explorer.helium.com/hotspots/112NKx5zR7gqT7eiKfYhJa7pL6zgvBKq9yzrg2YTTQDvjcnrrrQs
3: https://explorer.helium.com/hotspots/112SEVeQnKXNRFsifpgxxFLax58TehPbSaH6fFXxBWM1d3a3j8Fd
4: https://explorer.helium.com/hotspots/11YG5PKUEZAyma7xXBxWMnEvgSz3k6nRHwMQXfRrAq5WA3nBFYj
5: https://explorer.helium.com/hotspots/11h39LsvJA8NtDtYzYTNdUd3oCsFDid5gcV6WdEFByJ1cMADHyY
6: https://explorer.helium.com/hotspots/112TyyH5bk3ueN4qwhZxtMFXWerY995oLs2LJTG86a1gW97JUoJh
7: https://explorer.helium.com/hotspots/112A14NGwQzNWEn9cvK1Rjos5L7JMFNNSu4WhXopsHTL1bWbqwxF

Wallet;
1: https://explorer.helium.com/hotspots/112CTmj6tHTwfFEqkTgMKgAGabSTJXQsfRww91CWMDZmdhmWZWth

2: https://explorer.helium.com/hotspots/112H68GKxfdD9F84U47X7o4EMFVE6XgTaYJQCGUXCzAQoJ5TcgM2
3: https://explorer.helium.com/hotspots/112XVVgA972Pe8VquSYz4HTYbq3Boc5qj9wT3AM7GMDps2AHdTF8
4: https://explorer.helium.com/hotspots/11D8USrcrS7ba5pBP7m3U7HPLXyPoZEuw9WAmQXy6FoqftSCGSW
5: https://explorer.helium.com/hotspots/11ZxwfZAm3BgP7WfzTvuVSgkexuybXosrXnAuKn5qAaJ7d3LMpv
6: https://explorer.helium.com/hotspots/112AQ1pYUH9DAn6msGP4Zq9cSrYRP9LPYspPkoWNQ9RqzQyr6tf3
7: https://explorer.helium.com/hotspots/11tTNoV1yQagBnyDyq8beVNDvsD5nz7WSrnsXczrkaUVtwVkt49
8: https://explorer.helium.com/hotspots/112E9h35WFe7vt4GqaY7i62szoyo7K23GYSt4bxsW7oUyfRuDLQk
9: https://explorer.helium.com/hotspots/11S7RGi144GjpbXifY41ywmkLURUaRxiFajJjK6B8UzqJZy2EUd
10: https://explorer.helium.com/hotspots/112SPXNyn284xH22KbWtSxmoUDPU3T28dyasqJ9HcHwNRhy8AEJf
Discord Handle
MercaN ' 30
Reason(s)
Yes, it happened to me at times. But where there are more than 40 devices, 17 devices belonging to only 1 person are constantly active and it is not normal every day. The owner clearly states that they tried the rx module and the devices are in the room.only own auspicious in these 2 bags belonging to one person. These beacon devices contain only their own equipment. Also watch the technical specifications from time to time. and for active login. The telegram, which is shown in writing on the back of the device owner from a validator, was stated in writing in Helium Aydın. and told us to keep quiet 20 days later, all the equipment in Aydın will gain a lot.The recordings of the conversations are available as pictures.

[ ] I reject the complaint.  Unfortunately, in our region, there have been many untrue complaints without evidence.  Let the complainant find valid evidence.  Let these devices present the current beacon, witness, Rssi, snr tables as evidence.  As far as I have examined, these devices communicate quite normally with all devices in the area.  Now, when I examine the devices, I present to you a non-false proof.  In a balloon flying event held in the region 2 months ago, data packets passed from these devices.

You're talking about an old ballooning event. What if rx tx devices are new? And the problem is, only his own devices can hear this guy's devices. Devices around him do not hear. I confirmed from the owner that these devices are in a room. 10 devices one antenna. In addition, the antenna increases dbi and decreases the signal output power, and other devices do not receive activity from these 17 devices. And again, the owner of the device will bring many more rx devices in the picture I added.

Him said in picture :
Sir, we spend money so that everyone can win, we are in a project that is not harmful in terms of helium and will provide more profit to the region. Unfortunately, you see the group, Tx devices come, we will contact you at the end, we will contact you there to expand the network.


Native copy and recursive directories creation

@paillechat Hi, wouldn't this always be the better way to copy a file? Or are there webdav implementations that don't support this?

@frankdejonge Hi! Native webdav copy is faster because we don't need to download target file and upload it by the new way. We just copy file on server without download. But default for the backward compatibility library is working as it was working before via download&upload.

@paillechat the benefit is quite obvious so I'm all for just having this patch in, I just wondered why we'd even keep the old behavior.

@frankdejonge cool :)

is this one ready to be merged? Looking forward to the recursive path creation..

@frankdejonge Hi. Also waiting for this PR. Can you merge it?

Hi! We are also waiting for this to be merged.

Tagged as 1.0.5


Wrap original hrnet as library

I'm sorry for being confused. Wrong target repository of pull-request.


make travis check that directories match git branch names (except on master & gh-pages)

so that they won't merge into master by accident

that there is only a single directory in src/ with the name of the branch


[chore] Fix double the typos

Changes
This fixes a couple typos, which were reported in https://github.com/open-telemetry/opentelemetry-go/pull/5048.
Merge requirement checklist

[x] CONTRIBUTING.md guidelines followed.
[x] Change log entry added, according to the guidelines in When to add a changelog entry.

If your PR does not need a change log, start the PR title with [chore]

[x] schema-next.yaml updated with changes to existing conventions.

The markdown failure seems unrelated to my changes (though somehow it doesn't fail on the CI main branch).


Tokenizer: Add support for tokenisation via llama-cpp-python

For pure llama.cpp operation of LMQL, we should support the tokenizer that ships with llama.cpp, avoiding the need to install 'transformers' just for tokenisation.

Hi Luca, Is there someone allotted to this? If not, I would like to take this up.
I am utilizing this repo in a project of ours, I would like to contribute.

I likely won't get to this in the next few weeks, so any help would be greatly appreciated. For reference, the implementation should end up being very similar to https://github.com/eth-sri/lmql/blob/main/src/lmql/runtime/tokenizers/hf_tokenizer.py.
Let me know if you need any other pointers.

@lbeurerkellner Thanks for the starter information! I will go through those and reply here if I need any help.

Wanted to give an update. Took me quite some time but I successfully understood the issue. The fix will come shortly.

Awesome, looking forward to it. Feel free to reach out with any questions :)

Hi Luca,
I ran into an issue while developing the new tokenizer class.
The VocabularyMatcher class tries to get the encoding for " ". Llama tokenizers are based on sentencepiece, " " is not tokenized in this method.
Currently investigating what VocabularyMatcher does and possibly extending it to make it compatible with sentencepiece
It would be helpful to have some context around VocabularyMatcher.

Great to hear about progress. You can have a look at https://github.com/eth-sri/lmql/blob/main/src/lmql/runtime/tokenizers/hf_tokenizer.py#L122.
In short, VocabularyMatcher needs space and newline to dissect the vocabulary for partial matches. The implementation above is for the HF Llama tokenizer, so I expect hard-coding values for space and NL like there, should do the trick.

Your fix seems to work. Thanks!
I will complete the implementation and run some local instances.

Updated the PR - https://github.com/eth-sri/lmql/pull/208.
It introduces a new tokenizer class - LlamaCPPTokenizer which uses sentencepiece.
Tested it with open_llama_3b local tokenizer model and hugging face tokenizer danielhanchen/open_llama_3b, outputs match.


Custom aggregation filter box totals differ from graph

Hi Nicolas,
I have created a custom aggregator:
        var countRate = function(){
            return function(){
                return {
                    counter: 0,
                    push: function(record){
                        if (!isNaN(parseFloat(record.count))) {
                            this.counter += parseFloat(record.count);
                        }
                    },
                    value: function() { return this.counter; },
                    format: function(x) { return x; },
                    label: "Count"
                };
            };
        };

which will sum a specific column from my query. For example the data returned from the query is: select some-data, count(data-id) as count from some-table INNER JOIN another-table where xxx is True GROUP BY some-group-stuff; which returns values the count is the number of matching
some-data   ,   count
xxx         ,         1
yyy         ,        6
(2 rows)
Now the graph is reporting back correct values so the aggregator is pulling out a total of '7' however the pivot filter box is showing
xxx 1
yyy 1
totalling 2 (I believe the number of rows it returned.) Graph is correct but the filter box should be:
xxx 1
yyy 6
Any suggestions?

An example of what I get...

The filter box is not meant to be linked to the aggregator i.e. it is not meant to show a 'total'. Indeed it is meant to always just show the number of records in the input which have the given value of the given attribute.


chore: suppress issues

Issue #, if available:
GALI-1866
Description of changes:
Suppress CFN nag errors and warnings.
Checklist:

[x] Have you successfully deployed to an AWS account with your changes?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Approving this as I was notified the findings will be addressed in another PR. The changes in this code just ignores the cfn nag findings and hence, when cfn nag pipeline workflow is activated it will not fail

Changing base branch to develop-pipeline to unblock solutions pipeline integration work. Fixes to the TODO comments/ignored CFN nag warnings will be fixed before merging with develop.


choose a record from the master_patient_ids to ensure the patient wil…

…l be in the IPP

@okeefm if you have a chance, can you take a look at this one...its somewhat related to the feature we worked on in the last release to limit the number of patients in a test deck.

This ticket address the feature requested in https://jira.mitre.org/browse/CYPRESS-44.
The previous code chooses a patient (from which the filter criteria is selected) from the test's record list.  A test's record list include pateints that do not meet IPP criteria.
This updated code chooses a patient from a test's "master_patient_ids."  "Master_patient_ids" is originally used by Patient Clone Job for the pateints that meet IPP criteria.  The patient clone job then randomly adds other patients that do not meet the criteria.  This is why I am reusing this method.
A note on "keep_if { |id| id[8] == '-' }"  All "Master Patients" has medical records numbers that are UUIDs following this pattern "007f5da0-4d3a-0135-867f-20999b0ed66f".  These medical record numbers are set in the bundle.  When patients are created for a test, they have a medical record number like this "757442430658921".  All patients will have an "original_medical_record_number" for a master patient.  This is why we want to make sure that the random 'medical_record_number' is a master patient identifier.
Submitter:

[x] This pull request describes why these changes were made.
[x] Internal ticket for this PR: https://jira.mitre.org/browse/CYPRESS-44
[x] Internal ticket links to this PR
[x] Code diff has been done and been reviewed
[NA] Tests are included and test edge cases - rationale explained
[x] Tests have been run locally and pass

Reviewer 1:
Name: Dave Czulada

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code


feat(ui): Sign-post IDE set-up. Closes #3720

Checklist:

[x] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
[x] The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
[x] I've signed the CLA.
[ ] I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged. N/A
[ ] My builds are green. Try syncing with master if they are not.
[x] My organization is added to USERS.md.

Closes #3720

Re-run jobs.


Correct iteration number on IRONMAN 6 month reminders.

Fix for https://jira.movember.com/browse/TN-500

Hello @pbugni! Thanks for submitting the PR.

In the file portal/migrations/versions/cea9fbdd98f9_.py, following are the PEP8 issues :

Line 41:1: E302 expected 2 blank lines, found 1


Git Fatal on Danger Branches

Report
What did you do?
Run danger on a pull request using Github/Jenkins.
What did you expect to happen?
Running Dangerfile without seeing git fatals.
What happened instead?
Every build that runs prints
fatal: Couldn't find remote ref refs/heads/danger_base and
fatal: Couldn't find remote ref refs/heads/danger_base
three times each, corresponding to the calls to git_fetch_branch_to_depth.  This seems to be tied to the manually assigned refspec, which makes git look for refs/heads/danger_head & refs/heads/danger_base as remote branches, throwing fatals if those branches do not exist.
I've manually set refspecs for the job, +refs/pull/*:refs/remotes/origin/pr/* refs/heads/${ghprbTargetBranch}:refs/heads/danger_base refs/pull/${ghprbPullId}/head:refs/heads/danger_head, in my case using the ghprb plugin in Jenkins to provide refs/heads/danger_head & refs/heads/danger_base, but the manual refspec assigned to the fetch command seems to override this anyway.
Why would a remote danger_base or danger_head branch be expected?  If it is not expected, do we need the refspec in the fetch?  The refspec isn't included in the call to git_in_depth_fetch which makes me think we don't need it.
This isn't a hard error as Danger gets past it each time, but would rather not see fatals unless there is something actually wrong.
Your Environment

Which CI are you running on?
Jenkins
Are you running the latest version of Danger?
5.5.3
What is your Dangerfile?# please paste here, with 2-space identation, thank you!
xcov.report(
   scheme: ENV["FL_XCOV_SCHEME"],
   workspace: ENV["FL_XCOV_WORKSPACE"],
   skip_slack: ENV["FL_XCOV_SKIP_SLACK"],
   derived_data_path: ENV["FL_XCOV_DERIVED_DATA"],
   only_project_targets: true
)
xcode_summary.ignored_files="Pods/**"
xcode_summary.report(ENV["FL_XCS_REPORT"])

:+1:

Danger uses those branches to simplify some internal logic around generating the diffs and keeping track of where master vs PR head is. They should be generated at runtime, which is why they're not in documentation anywhere. It seems strange that Danger cannot make those branches, is there some weird permissions thing?

I'm not sure - the issue only seems to pop up when using a shallow clone with a very specific refspec (it's a huge repo that can't be reasonably fully cloned very often).  It seems like if the refspec doesn't include whatever commit Danger is looking for, it falls back to git_fetch_branch_to_depth as expected but in the process ignores removes anything besides what it's looking for along the way which results in this output.
I did start seeing failures pop up sporadically around this - my best guess for when/how it happened at the time was that a new commit was added to the base branch at the same time (or thereabouts) that Danger gets the commit from the API.  The Github API, at least the Enterprise version that I'm running on, appears to report the new commit before it's actually available to fetch which means Danger doesn't start out with the commit.   Because the commit isn't available for Danger, it starts trying to perform incremental fetches and ends up removing the danger_head and danger_base branches along the way because of the --prune in the refspec.

You can "work around" this problem by switching to Danger JS which only relies on the GitHub API to generate all this metadata (so no need to have a local git setup with the same infra as the PR ) - I don't think it uses modern APIs in GitHub, so you should be fine with any enterprise build.

I'm actually using danger from fastlane, so I'm a little hesitant to make that switch

We are seeing this issue as well running on VSTS. Same Dangerfile, same problem. The log looks like:
fatal: Couldn't find remote ref refs/heads/danger_base
fatal: Couldn't find remote ref refs/heads/danger_head
fatal: Couldn't find remote ref refs/heads/danger_base
fatal: Couldn't find remote ref refs/heads/danger_head
fatal: Couldn't find remote ref refs/heads/danger_base
fatal: Couldn't find remote ref refs/heads/danger_head
fatal: Couldn't find remote ref refs/heads/danger_base
fatal: Couldn't find remote ref refs/heads/danger_head
From https://[redacted].visualstudio.com/[redacted]/_git/[redacted]
   1cc96ae9b7..9e854a4b96 [redacted] -> origin/[redacted]
bundler: failed to load command: danger (/usr/local/bin/danger)
RuntimeError: Cannot find a merge base between danger_base and danger_head.
  /usr/local/lib/ruby/gems/2.5.0/gems/danger-5.5.11/lib/danger/scm_source/git_repo.rb:128:in `find_merge_base'
  /usr/local/lib/ruby/gems/2.5.0/gems/danger-5.5.11/lib/danger/scm_source/git_repo.rb:16:in `diff_for_folder'
  /usr/local/lib/ruby/gems/2.5.0/gems/danger-5.5.11/lib/danger/danger_core/dangerfile.rb:261:in `setup_for_running'
  /usr/local/lib/ruby/gems/2.5.0/gems/danger-5.5.11/lib/danger/danger_core/dangerfile.rb:271:in `run'
  /usr/local/lib/ruby/gems/2.5.0/gems/danger-5.5.11/lib/danger/danger_core/executor.rb:28:in `run'
  /usr/local/lib/ruby/gems/2.5.0/gems/danger-5.5.11/lib/danger/commands/runner.rb:68:in `run'
  /usr/local/lib/ruby/gems/2.5.0/gems/claide-1.0.2/lib/claide/command.rb:334:in `run'
  /usr/local/lib/ruby/gems/2.5.0/gems/danger-5.5.11/bin/danger:5:in `<top (required)>'
  /usr/local/bin/danger:23:in `load'
  /usr/local/bin/danger:23:in `<top (required)>'

The branches that it refers to are totally random however. They have nothing to do with the build being run. I think it was just the latest push to the repo.

This is still an issue today. I'm lucky I discovered this by perusing the PR and seeing this comment:
https://github.com/danger/danger/issues/768#issuecomment-398893158

For the folks who end up stumbling on this issue because they use Github Actions, changing the depth of the check-out fixed the issue for us. Here's our full danger action, which may help some folks:
name: Run Danger

on: [pull_request]

jobs:
  build:
    name: Run Danger
    runs-on: ubuntu-latest

    steps:
      - name: Checkout Code
        uses: actions/checkout@v2
        with:
          fetch-depth: 100

      # Setup ruby
      - name: Set up Ruby 2.6
        uses: actions/setup-ruby@v1
        with:
          ruby-version: 2.6

      # Install the right bundler version
      - name: Install bundler
        run: gem install bundler

      # Cache dependencies
      - name: Cache ruby dependencies
        id: cache-ruby
        uses: actions/cache@v2
        with:
          path: vendor/bundle
          key: union-gems-${{ hashFiles('**/Gemfile.lock') }}
          restore-keys: |
            union-gems-

      # Install dependencies on cache miss
      - name: Install ruby dependencies
        if: steps.cache-ruby.outputs.cache-hit != 'true'
        run: |
          bundle config path vendor/bundle
          bundle install --jobs 4 --retry 3 --without=documentation

      # Run danger
      - name: Run danger
        env:
          DANGER_GITHUB_API_TOKEN: ${{ secrets.DANGER_GITHUB_API_TOKEN }}
        run: |
          bundle config path vendor/bundle
          bundle exec danger

For the folks who end up stumbling on this issue because they use Github Actions, changing the depth of the check-out fixed the issue for us. Here's our full danger action, which may help some folks:
name: Run Danger

on: [pull_request]

jobs:
  build:
    name: Run Danger
    runs-on: ubuntu-latest

    steps:
      - name: Checkout Code
        uses: actions/checkout@v2
        with:
          fetch-depth: 100

      # Setup ruby
      - name: Set up Ruby 2.6
        uses: actions/setup-ruby@v1
        with:
          ruby-version: 2.6

      # Install the right bundler version
      - name: Install bundler
        run: gem install bundler

      # Cache dependencies
      - name: Cache ruby dependencies
        id: cache-ruby
        uses: actions/cache@v2
        with:
          path: vendor/bundle
          key: union-gems-${{ hashFiles('**/Gemfile.lock') }}
          restore-keys: |
            union-gems-

      # Install dependencies on cache miss
      - name: Install ruby dependencies
        if: steps.cache-ruby.outputs.cache-hit != 'true'
        run: |
          bundle config path vendor/bundle
          bundle install --jobs 4 --retry 3 --without=documentation

      # Run danger
      - name: Run danger
        env:
          DANGER_GITHUB_API_TOKEN: ${{ secrets.DANGER_GITHUB_API_TOKEN }}
        run: |
          bundle config path vendor/bundle
          bundle exec danger

I can confirm this worked for us! Thanks @fredoliveira

thanks @fredoliveira :bow:

Appreciate it @fredoliveira 🙇♂

@fredoliveira Why does adding fetch-depth: 100 fixes the issue? 🤔

@fredoliveira Why does adding fetch-depth: 100 fix the issue? 🤔

I would also like to know this lol

Danger gets the difference between the base of your PR and the head by looking at the commit history between them, if they are not available then Danger fails


Does this make a website work on mobile?

I'm trying to make this website player cast from mobile phone to chromecast.
www.tamandua.tv.br
But I can't see the cast button on iOS or android? Is it possible?
Thanks,

Sorry @dogmydog but we don't have the resources to provide user support. This plugin adds a Chromecast button to the VideoJS interface when you have it configured properly and are using it on devices and browsers that support Chromecast.


Rename Accessor methods after DataTable removal

Rename accessor  read_csv
rename accessor load_retail

Update statistical insights documentation to use this instead of load_retail_accessor

rename Accessor indexers to _ilocIndexer and _locIndexer
rename serialization files/relevant functions to just serialize and deserialize

Closed by #723


[Wishlist] non-terrain based plane lock for adding new objects.

I'm currently working on building modular levels, and there's a growing list of things that could be done to make this type of building easier.
The current and slightly awkward method for this is to use a terrain and use the snap to terrain feature, add and move your objects, without this method you have to manually move every added object to the correct 'height' this is even more tedious and sometimes needs to be done by directly adding numbers for precision. All in all a plane locking system would allow for the much faster development of modularly based levels.

Not sure how you do your level, but I used https://github.com/GarageGames/Torque3D/pull/2024 and some of the tool that t3d already have, and I not have to use the correct "height" just snap with the object I want. Is possible that you can do a short video to understand the workflow? I'm sure this will help to give a fix.

https://github.com/GarageGames/Torque3D/pull/1961 added https://imgur.com/a/m9b7j
flipping use group center off will kill the averaging for multiple objects so jiggling the assets in a group will settle them into thier gridpoints, while atgizmo lets you spawn objects at the selectionpoint.

oh I see :rofl:


[SPARK-17263][SQL] Add hexadecimal literal parsing

What changes were proposed in this pull request?
This PR adds the ability to parse SQL (hexadecimal) binary literals (AKA bit strings). It follows the following syntax X'[Hexadecimal Characters]+', for example: X'01AB' would create a binary the following binary array 0x01AB.
If an uneven number of hexadecimal characters is passed, then the upper 4 bits of the initial byte are kept empty, and the lower 4 bits are filled using the first character. For example X'1C7' would create the following binary array 0x01C7.
Binary data (Array[Byte]) does not have a proper hashCode and equals functions. This meant that comparing Literals containing binary data was a pain. I have updated Literal.hashCode and Literal.equals to deal properly with binary data.
How was this patch tested?
Added tests to the ExpressionParserSuite, SQLQueryTestSuite and ExpressionSQLBuilderSuite.

cc @JoshRosen

Test build #64485 has started for PR 14832 at commit 1853785.

Test build #64485 has finished for PR 14832 at commit 1853785.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64485/
Test PASSed.

Test build #64507 has started for PR 14832 at commit 4f2b272.

Test build #64507 has finished for PR 14832 at commit 4f2b272.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64507/
Test PASSed.

LGTM!

Merging to master.


chore(dev-deps): update dependency @semantic-release/github to v9.2.4

This PR contains the following updates:

Package
Type
Update
Change

@semantic-release/github
devDependencies
patch
9.2.3 -> 9.2.4

Release Notes

semantic-release/github (@semantic-release/github)
v9.2.4
Compare Source
Bug Fixes

deps: update dependency mime to v4 (#745) (342a2f2)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 1.2.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


XRTBackend Implementation of AirBackend is Confusing

I was trying to use the compile() and load() methods of XRTBackend when I was doing some debugging recently. I realized the load() method takes a module: air.ir.Module as an argument which is then never used.
This is confusing.
The abstract base class (AirBackend) is flexible, because we can specify a unique CompiledArtifact for XRTBackend. I think this confusion would be fixed if the CompiledArgument for the XRTBackend were something like (in pseudo code):
class XRTArtifact:
  xclbin: File(),
  insts: File(),

e.g., the compiled artifacts are a pair of files (or file paths) pointing to the xclbin and instruction file.
I'm happy to make a PR for this, if others think this is a reasonable change. If there is some history behind the current format that needs to be taken into account, I'm happy to hear it!

I'm happy to make a PR for this, if others think this is a reasonable change. If there is some history behind the current format that needs to be taken into account, I'm happy to hear it!

There is no history other than the simplest thing was implemented. Any improvements are welcome!

Great! Closing because I've created a PR for consideration: https://github.com/Xilinx/mlir-air/pull/634


feat(storage): git-based storage Backend, Committer interface

I'm going to add an integration tests in a follow-up since there's already enough code in this PR. Will also follow up with configurable storage.
Signed-off-by: Eric Stroczynski<EMAIL_ADDRESS>

See #36 for follow-up on storage configuration and integration tests.


RGB Light on Keypress

This adds a feature that allows you to change the default light of the keyboard and also turn on light on keypress. I have a few more ideas on patterns that I will look into implementing soon. Let me know what you think of the implementation. I think we should figure out a good place to move this code so that its easy to separate from the action of the keypress. Maybe out to its own function. But this is a good proof of concept

Along with the example I put in the code.py, here is a more advanced macro (here its MACRO(0) that lets you set up a cycle for the current RGB options of off, solid color, or light on keypress with this in the code.py:
keyboard.set_default_color(r=0xFF, g=0, b=0xFF)
keyboard.light_on_press = True

def macro_handler(dev, n, is_down):
    if is_down and n == 0:
        if keyboard.light_on_press:
            keyboard.light_on_press = False
            keyboard.backlight.on(*keyboard.default_color)
        elif keyboard.backlight.dev.any():
            keyboard.backlight.off()
        else:
            keyboard.light_on_press = True

I cleaned up the implementation a little bit and separated out the RGB updating. This allows for the higher latency when the lights on keypress is enabled, but when it is set to false, the latency drops back down to 1/2 nanoseconds. Neither set ups has a noticeable lag tho even when typing at high speeds 120/130wpm which is good.

I was thinking to add some new action codes to control the backlight. With backlight action codes, we could just modify the keymap without the macro handler.

Ah yeah I like that solution a lot better

Just added some keycodes to control RGB backlight. We can use  RGB_MOD to change backlight modes.

Awesome! That is amazing! Thank you so much! I'll play around with this code a bit and look into what I can add. I'm really enjoying this keeb, thanks for all your hard work!


[Doc] Softdeprecate C style array declaration

Is your feature request related to a problem? Please describe.
Cython currently supports two ways how to declare an array:
cdef int arr1[4]   # C style array declaration
cdef int[4] arr1   # Java style array declaration

it seems that both of them generate same C code but the Java style (cdef int[4] arr1) is more consistent because:

Memoryviews are defined in the same way: cdef int [:, :, :] narr_view = narr [1]
As mentioned in the bug report Cython currently supports cdef int[4] arr2 = [1, 2, 3, 4] but not cdef int arr[4] = [1, 2, 3, 4] #5179
Defining fused types uses syntax of TYPE[n] [2]:ctypedef fused my_fused_type:
    int[3]
    float[2]

[1] https://cython.readthedocs.io/en/latest/src/userguide/memoryviews.html
Describe the solution you'd like.
Soft-deprecate C style definition - use only Java style array definition (cdef int[4] arr1) in Cython Documentation in all places but still support the C style (to keep backward compatibility).
Describe alternatives you've considered.
No response
Additional context
See https://github.com/cython/cython/issues/5179#issuecomment-1409259055

Seems right to me, we should migrate the documentation to Java style.

This syntax change does not appear to apply to pointers, correct? For example, the following code works fine.
cdef char[4] char_array

But this does not work (produces "Syntax error in C variable declaration"),
cdef char*[4] char_ptr_array

Changing it to the c-declaration style does work.
cdef char* char_ptr_array[4]

The documentation states that "C-style array declarations (cdef int a[4]) are now (silently) deprecated in favour of the Java-style cdef int[4] a form. Will cdef char*[4] char_ptr_array be allowed in the future. More importantly, will a hard deprecation block cdef char* char_ptr_array[4] soon?
Running Cython 3.0.4

@jrenaud90 I don't think the plan here is to do more than update the documentation to use the java style. So don't worry about using the other style for pointer arrays.

This syntax change does not appear to apply to pointers, correct?

No it does supports it:

cdef char[4] *char_ptr_array is equivalent to cdef char (*char_ptr_array)[4] and translates to C char (*__pyx_v_6delete_char_ptr_array)[4]
cdef (char *)[4] char_ptr_array is equivalent to cdef char *char_ptr_array[4] and translates to C char *__pyx_v_6delete_char_ptr_array[4]

For difference between them see https://www.geeksforgeeks.org/difference-between-pointer-to-an-array-and-array-of-pointers/


ctrl-p opens fuzzy finder instead of moving up

os: ubuntu 15.04
related plugins installed:

clipboard-plus
disable-keybindings
emacs-plus

Please disable the fuzzy-finder keybindings.


Handle correctly merge commits.

In the case of pull request #3, there was a merge commit in the pull
request (https://api.github.com/repos/apache/incubator-distributedlog/commits/2197d49261785a370f22c026cc9fe02f55b7e77c)
which has no login key for the actor, and the script was unable to
handle this situation. Now we check for the presence of the key.

@franckcuny you are faster than me. I was planning to send a change out :D

The change looks good to me. +1


Fix root/path kwargs for Stream Resource documents generated by HDFWriter

Previously, root was hardcoded to '/'. This removes that, and instead ensures the root and resource_path are accurate.

Tests failing?

This change is good, I will finish it


[prettier-plugin-sh] sh extension not resolving

Since I updated to<EMAIL_ADDRESS>and<EMAIL_ADDRESS>this command no longer reports .sh files that need formatting:
prettier --check .
With<EMAIL_ADDRESS>and<EMAIL_ADDRESS>the above command would find .sh files that need formatting.
Please note with the aforementioned newer versions this wildcard pattern does work:
prettier --check ./*.sh
Here is my .prettierrc.json:
{
  "plugins": ["prettier-plugin-sh"]
}

Any useful error message?

No errors. Just acts as if there were no sh files needing a format when in
fact there are. Other file types recognized by prettier and need formatting
are listed.
On Fri, Jul 7, 2023 at 21:27 JounQin @.***> wrote:

Any useful error message?
—
Reply to this email directly, view it on GitHub
https://github.com/un-ts/prettier/issues/273#issuecomment-1626407178,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKQGNDEBAU4WBJ5OXW3CCSTXPCZPRANCNFSM6AAAAAA2CLAIQA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Can you please provide a runnable reproduction?

Here you go. Both repos have the same files that need to be formatted.
Repo for old
$ npm run format

><EMAIL_ADDRESS>format
> prettier --check .

Checking formatting...
[warn] level-0/go.sh
[warn] level-0/hello.sh
[warn] level-0/level-1/another.sh
[warn] level-0/level-1/library.js
[warn] level-0/level-1/runme.sh
[warn] level-0/program.js
[warn] Code style issues found in 6 files. Forgot to run Prettier?

Repo for new
$ npm run format

><EMAIL_ADDRESS>format
> prettier --check .

Checking formatting...
[warn] level-0/level-1/library.js
[warn] level-0/program.js
[warn] Code style issues found in 2 files. Run Prettier to fix.

close in favor of https://github.com/prettier/prettier/issues/15079


Serializer for class 'DirectionImpl' is not found in v2

crash log:
kotlinx.serialization.SerializationException: Serializer for class 'DirectionImpl' is not found.
                                                                                Please ensure that class is marked as '@Serializable' and that the serialization compiler plugin is applied

when i navigate to some screen, it will crashed
my screen is like:
data class ProfileNavArgs(val account: Account)

@Destination<RootGraph>(navArgs = ProfileNavArgs::class)
@Composable
fun Profile(
  navigator: DestinationsNavigator,
  viewModel: ProfileViewModel = hiltViewModel(),
  resultRecipient: ResultRecipient<StatusDetailDestination, StatusBackResult>
)

and my StatusBackResult is
@Parcelize
data class StatusBackResult(
  val id: String,
  val favorited: Boolean,
  val favouritesCount: Int,
  val reblogged: Boolean,
  val reblogsCount: Int,
  val repliesCount: Int,
  val bookmarked: Boolean,
  val poll: Poll?
) : Parcelable

@Serializable
@Parcelize
data class Poll(
  val id: String,
  @SerialName("expires_at") val expiresAt: String?,
  val expired: Boolean,
  val multiple: Boolean,
  @SerialName("votes_count") val votesCount: Int,
  @SerialName("voters_count") val votersCount: Int?, // nullable for compatibility with other fediverse
  val options: List<PollOption>,
  val emojis: List<Emoji> = emptyList(),
  val voted: Boolean,
  @SerialName("own_votes") val ownVotes: List<Int>?
) : Parcelable {

  @Serializable
  @Parcelize
  data class PollOption(
    val title: String,
    @SerialName("votes_count") val votesCount: Int
  ) : Parcelable
}

btw, Can Compose Destination support Kotlin Serialization's navigation parameters? Because it seems that the latest version of androidx navigation compose just supports 🤔

but it goes well in v1, so I'm not sure what's causing it

What version are you using? Are you also importing compose navigation dependency or just Compose Destinations?
(for the record, you should ONLY depend on Compose Destinations)

I know what it is, but I would like to understand how you got to this point.
Check these breaking changes:
https://github.com/raamcosta/compose-destinations/releases/tag/2.1.0-beta02
Because new versions of official jetpack compose navigation, navigate method can receive anything as its parameter, you are calling that function rather than calling Compose Destinations functions.
As explained in the release notes, you need to use a DestinationsNavigator to be able to use Compose Destinations navigate APIs. So make sure to do what it says there.
And do let me know how you ended up calling their functions.. because I specifically removed all previous functions so that you must have gotten some "red imports". The expectation is that when you found those imports, you would try to understand what's happening and figure you needed to do some changes, but I guess if you just delete the import, the app will compile.. but obviously you'd be calling official APIs passing in Direction which doesn't work!

Added a big WARNING section on README to make this more visible!
https://github.com/raamcosta/compose-destinations

After I looked at the warnings on the README and I replaced all navControllers with navigators, this issue was solved! 😄👍
But the overall code makes me wonder a bit:
val engine = rememberNavHostEngine()
val navController = engine.rememberNavController()
val navigator = navController.rememberDestinationsNavigator()

DestinationNavHost(
  engine = engine,
  navController = navController
)

DestinationNavHost still need a navController, But our navigational behavior doesn't need it anymore 👀💦.
BTW, I have two more questions that are not related to this issue, but I'd love to hear from you, and it would be great if you could answer them or give me some suggestions! 😍
1. Specify animations for specific screens
I have a custom default animations for DestinationNavHost
object DefaultAppTransitions : NavHostAnimatedDestinationStyle() {
  override val enterTransition: AnimatedContentTransitionScope<NavBackStackEntry>.() -> EnterTransition
     = { defaultSlideIntoContainer() }
  override val exitTransition: AnimatedContentTransitionScope<NavBackStackEntry>.() -> ExitTransition
    = { defaultSlideOutContainer() }
  override val popEnterTransition: AnimatedContentTransitionScope<NavBackStackEntry>.() -> EnterTransition
    = {  defaultSlideIntoContainer(forward = false) }
  override val popExitTransition: AnimatedContentTransitionScope<NavBackStackEntry>.() -> ExitTransition
    = { defaultSlideOutContainer(forward = false) }
}

fun <T> AnimatedContentTransitionScope <T>.defaultSlideIntoContainer(
  forward: Boolean = true
): EnterTransition {
  return when (forward) {
    true -> slideIntoContainer(Start, tween(slideAnimationTween, easing = FastOutSlowInEasing))
    false -> scaleIn(initialScale = scaleSize, animationSpec = tween(300, easing = EaseOutCubic)) +
      fadeIn(animationSpec = tween(300, delayMillis = 80), initialAlpha = 0.15f)
  }
}

fun <T> AnimatedContentTransitionScope<T>.defaultSlideOutContainer(
  forward: Boolean = true
): ExitTransition = when (forward) {
  true -> scaleOut(targetScale = scaleSize, animationSpec = tween(400, easing = EaseInOutCubic)) +
    fadeOut(targetAlpha = 0.15f)
  false -> slideOutOfContainer(End, tween(slideAnimationTween))
}

DestinationsNavHost(
  engine = engine,
  navController = navController,
  defaultTransitions = DefaultAppTransitions,
  navGraph = NavGraphs.root,
  startRoute = startRoute,
  dependenciesContainerBuilder = {
    navGraph(NavGraphs.app) {
      dependency(drawerState)
      dependency(appState)
    }
    dependency(this@SharedTransitionLayout)
  }
)

The effect of this navigation is overall very similar to Twitter in that it's a slide-in/slide-out animation.
https://github.com/raamcosta/compose-destinations/assets/31311826/8a6ea57f-66c5-4aa4-acd2-c1e053fdcdad
But since the advent of the shared element animation, I need to use the fadeIn/fadeOut animation instead of this animation between the post and image detail screens, what is the best practice in this case? 👀👀
If I understand correctly, it seems like it's possible to write a separate object that inherits DestinationStyle.Animated() and then use it on the specified @Destination
object StatusMediaScreen: DestinationStyle.Animated() {
  ...
}

@Destination<RootGraph>(style = ...)

2. NavigationDrawer display conditions
This question doesn't have much to do with Compose Destination, but I don't have any good ideas.
SharedTransitionLayout {
  ModalNavigationDrawer(
    drawerState = drawerState,
    drawerContent = {
      if (destination.shouldShowScaffoldElements() && activeAccount != null) {
       AppDrawer(
          drawerState = drawerState,
          activeAccount = activeAccount!!,
          accounts = accounts.toImmutableList(),
          changeAccount = {
            scope.launch { drawerState.close() }
            viewModel.changeActiveAccount(it)
          },
          navigateToLogin = {...},
          navigateToProfile = {...}
          },
          navigateToSettings = {...}
        )
      }
    },
    gesturesEnabled = destination.shouldShowScaffoldElements()
  ) {
    Scaffold(
      bottomBar = {
        if (destination.shouldShowScaffoldElements() && !appState.hideBottomBar) {
          BottomBar(
            appState = appState,
            navigator = navigator,
            destination = destination,
            scrollToTop = {
              scope.launch { appState.scrollToTop() }
            }
          )
        }
      }
    ) {
      DestinationsNavHost(...) { ... }
  }
}

val DestinationSpec.isBottomBarScreen: Boolean
  get() = this == HomeDestination  this == ExploreDestination  this == NotificationDestination ||
    this == DirectMessageDestination

fun DestinationSpec.shouldShowScaffoldElements(): Boolean {
  if (NavGraphs.login.destinations.contains(this)) return false
  else {
    BottomBarItem.entries.forEach {
      if (this == it.direction) return true
    }
  }
  return false
}

My current method is to determine if it belongs to a Screen in the bottomBar and then decide if it will show/enable the side swipe expand gesture. This method worked fine before, but after I migrated to v2, every time I start the App or jump back to the homepage from a non-bottomBar screen, it automatically pops up the NavigationDrawer, so I wonder if there is a better solution for this scenario. I don't know if there is a better solution for this scenario 🤔

@raamcosta Can you check the second issue I mentioned, in the v2 version, if I add some if conditions to control the show/hide of the Drawer, then going back from some screen popBack will result in not completing the navigation behavior correctly (it'll be very strange, refer to the video like that)

This is the log of the normal popBack navigation to Home (navController.currentDestinationAsState().value)
From launching the App -> click on the Status detail screen -> go back to the home page
destination HomeDestination
destination HomeDestination
destination StatusDetailDestination
destination HomeDestination

but, if i add if condition (if(destination.shouldShowScaffoldElements() && activeAccount != null)) in drawer.
it will be:
destination HomeDestination
destination HomeDestination
destination StatusDetailDestination
destination HomeDestination
destination HomeDestination

https://private-user-images.githubusercontent.com/31311826/328021988-6b8b9bdc-ba3c-4d4b-b010-89890929a28d.mp4?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTU0NDgwMjUsIm5iZiI6MTcxNTQ0NzcyNSwicGF0aCI6Ii8zMTMxMTgyNi8zMjgwMjE5ODgtNmI4YjliZGMtYmEzYy00ZDRiLWIwMTAtODk4OTA5MjlhMjhkLm1wND9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA1MTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNTExVDE3MTUyNVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQ4ZWUxOTZjZTI0MjJkMWM3NTA5MmQ1Mjc0ZWExYzU5ZWViMTE1YmUxNTY2MmY4OTkzOWY4MzkxNGFhMjQ2MjQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.dTkBH8QKL6n-ZMHY_47W7SUfCxbWLneB2mfmlc8bXhY

After some research, I found that if log have two times about "HomeDestinatino", it will trigger this incorrect navigation behavitor (perhaps it performed twice navigation?)
But in reality I really didn't change much of the code, I followed the documentation and migrated most of the API names, this is my previous v1 code and it's works very well
https://github.com/whitescent/Mastify/blob/main/app/src/main/java/com/github/whitescent/mastify/ui/component/AppScaffold.kt#L104-L111


Two problems with ex. 58

Unfortunately, the algorithm shown in the exercise is wrong: it doesn't work e.g. for
A -----------10-------------> B --1--> F
|                             |
\--1-- C --1-- D --1-- E --1--/

because it visits each node not more than once (and doesn't update neighbors of the nodes updated with new information).
It can easily be fixed e.g. by returning an ?u8 from getEntry instead of a ?*NotebookEntry and updating the notebook next_entry field with it in checkNote (choosing the minimum of the current value and the updated entry index).
The second problem is much less severe: the figure with the notebook lists wrong distance for the B->D entry. The distance must be greater than distance for the A->B entry.

Ha, go figure. Thanks the attention to detail! If anybody is able to verify and PR a fix for this, that'd be great. It might be a while before I can.
...Or replace this exercise with something else entirely - see #198 and #125.

@arbrk1 can you provide output that is incorrect?
The example you provided works fine and produces the output:
Archer's Point--1->Cottage--1->Dogwood Grove--1->East Pond--1->Bridge--1->Fox Pond

Additionally, the algorithm is correct exhaustively, for all start and end points, for the hermits map.
It also updates as appropriate; in the main function, the while loop will visit every node and the inner for loop will update each of the nodes neighbours.
This may help, the following is a digraph of the hermits map:
digraph hermit_map {
  a [label = "Archer's Point"];
  b [label = "Bridge"];
  c [label = "Cottage"];
  d [label = "Dogwood Grove"];
  e [label = "East Pond"];
  f [label = "Fox Pond"];

  a -> b [label = "2"];

  b -> a [label = "2"];
  b -> d [label = "1"];

  c -> d [label = "3"];
  c -> e [label = "2"];

  d -> b [label = "1"];
  d -> c [label = "3"];
  d -> f [label = "7"];

  e -> c [label = "2"];
  e -> f [label = "1"];

  f -> d [label = "7"];
}

Save the map as hermit_map.dot and generate the map with dot by running the following command on the command-line:
cat hermit_map.dot | dot -Tpng -o hermit_map.png

You can run the exercise and compare.
@ratfactor I really like this example! It is fun and a great refresher to graph algorithms.

Update: Unfortunately, the algorithm is incorrect. After my last update, I kept having a nagging feeling; I remembered I thought it was really neat that you could use the hermit's notebook both to hold the locations and as the queue for the algorithm. This is actually the problem.
While the neighbours get updated correctly, they are supposed to go back into the queue after that; otherwise, their neighbours and neighbours' neighbours etc.. won't get updated.
@arbrk1's suggested fix is also incorrect as the notebook's next_entry field can be overwritten before it is even used in that case.
The only efficient way is to have a data structure hold nodes we need to check; queue for breath-first search, stack for depth-first search, or something else.
If you want to just get this algorithm to work then we can wrap the while loop in main with another while loop with a condition like a was_updated variable which is set to true depending on the return value from checkNote (when it updates a distance or adds a new entry). I've tested and this works:
var was_updated = true;
while (was_updated) {
    notebook.next_entry = 0;
    was_updated = false;
    while (notebook.hasNextEntry()) {
        ...
        for (place_entry.place.paths) |*path| {
        ...
            if (notebook.checkNote(working_note)) {
                was_updated = true;
            }
        }
    }
}

@ratfactor If you want to do this, I could do a pull request in a couple days; but it may be better for you to do it and integrate it with the rest of the comments/story [maybe something about the hermit updating his notebook so that when he goes on future trips the path will be better :-) ]. Or you could modify it after I do a pull request.
Failure Example of Current Algorithm
It is pretty difficult to get it to fail on a small graph, especially because it is sensitive to how you order the paths, but I finally got an example of it failing after adding two new locations. The following graph will still give the original answer when there is  shorter path available.
digraph hermit_map {
  a [label = "Archer's Point"];
  b [label = "Bridge"];
  c [label = "Cottage"];
  d [label = "Dogwood Grove"];
  e [label = "East Pond"];
  f [label = "Fox Pond"];
  g [label = "Gorge"];
  h [label = "Haunted Forest"];

  a -> b [label = "2"];

  b -> g [label = "10"];
  b -> a [label = "2"];
  b -> d [label = "1"];

  c -> d [label = "3"];
  c -> e [label = "2"];

  d -> b [label = "1"];
  d -> c [label = "3"];
  d -> f [label = "7"];
  d -> g [label = "2"];

  e -> c [label = "2"];
  e -> f [label = "1"];

  f -> d [label = "7"];

  g -> b [label = "10"];
  g -> d [label = "2"];
  g -> h [label = "1"];

  h -> f [label = "1"];
}


Check out single-sentence summaries for RougeNAligner

The following snippet produces unexpected results, which should be investigated, and ideally also integrated as a test case:
from summaries.aligners import RougeNAligner
aligner = RougeNAligner()
aligner.extract_source_sentences("This is a short test. Another sentence is here.", "This is a test.")

Expected output:
A single output sentence ("This is a short test.")
Actual observed output:
Two sentences (twice the same) in the output. ("This is a short test.", "This is a short test.")
A potential reason could be that it does not correctly split the sentences of the "summary", but will have to check.

Turns out that this is due to spacy incorrectly splitting sentences in the above example. For this reason, we cannot do much at the current time, other than recommend the usage of custom splitters that improve upon such cases.


Disable a test that seems to time out on Android.

Will investigate and re-enable the test when the cause is found.

For the record, here's the link to a failing run: https://github.com/firebase/firebase-cpp-sdk/runs/2516720057

Closing this in favor of https://github.com/firebase/firebase-cpp-sdk/pull/417


Web view error mangalib

Source information
Mangalib 1.4.102
Source language
Russian
Steps to reproduce

Most likely this is due to an incorrect link.
Expected behavior
Should be open: 1) for the case when you opened a manga: The main page of the title. 2) if the page is open, then open the same one in web view mode
Actual behavior

Mihon/Tachiyomi version
App version: 1.10.5 (standard, 31f967235, 68, 2024-06-01T22:29:05Z) Preview build: 561 Android version: 9 (SDK 28; build Flyme <IP_ADDRESS>G) Device brand: meizu Device manufacturer: meizu Device name: 16s (meizu_16s) Device model: 16s WebView: Chrome 126.0.6478.122
Android version
Android 9
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Change domain to test-front.mangalib.me . The mangalib.me site has not yet been updated to the new version


New Contribution

Contributor: Jonnie-Dev
SSH Public key:ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIFBMIYkP00+Ldhf29UvhdJmHcQKWLRII127Vc1JeGvj3
Attestation: [any form of attestation for contribution (e.g., signature) - Optional]

edited

Contribution started

@zvorcuit Can I go ahead with the contribution?