Detect devices as well, if not native integration but mqtt device

Checklist

[X] I have filled out the template to the best of my ability.
[X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
[X] This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.
I'm using zigbee2mqtt and zwave2mqtt and hence my devices are all in HA but not using ZHA for example. I have enabled the "discovery" but somehow its not detecting any of the devices, even the integration is adding all the device details also with the mqtt in between
Describe the solution you'd like
Detect devices as you do in ZHA
Describe alternatives you've considered
manually entering all the values, but yeah, thats kind of sad
Additional context
not much more to add

zigbee communicates different model id's generally which could not be known to powercalc yet.
You can enable debug logging for powercalc, and then you should get some lines saying Auto discovered model.
Look at the manufacturer and model there and share the models which should be discovered (because of supported models list) and are currently not.

New beta release https://github.com/bramstroker/homeassistant-powercalc/releases/tag/v1.5.0-beta.1.
Please let me know if this fixes the problem with disappearing entities for you.

I think I see the issue, it works all great for the Ikea stuff I have, but the Philips hue seems not to work, though they seem to be in the list with a different brand (signify). The numbers are ver similar though for some reason<PHONE_NUMBER>01 vs<PHONE_NUMBER>00)

signify is not an issue, that is aliased to Philips inside powercalc library.
929003099101 just needs to be added as an alias to 3216331P6 to make things work, as noted above. When you are not able to make a PR for this code change I will do, but I first need to know which other models are not detected but should, so I can do them all at once.
You'll need to enable debug logging for powercalc and share the lines saying someting like this.
light.ambient_muur: Auto discovered model (manufacturer=Signify Netherlands B.V., model=Hue Play<PHONE_NUMBER>41))
For the models which are not working.

thats the final one that does not work, another hue lamp
(signify | 1742930P7 | Hue Impress Outdoor Wall Light Small |   | 0.170 | hs,color_temp
-- | -- | -- | -- | -- | --)
All others seem to work indeed now :) thanks

What did you do to make the other lights work? As you mentioned a lot of devices were not detected. How are they magically working all of a sudden?
Regarding this light which give an error. Looking at the error the model is<PHONE_NUMBER>01.
Which is "Hue White Ambiance Milliskin" light, which is a completely other light than "Hue Impress Outdoor Wall Light Small" only allows to control color temperature and no hs (color mode). That's why you get this error.
Searching on Google for https://www.google.com/search?q=929003045001 also returns only Milliskin spot light.
Did you set this model manually yourself? Cannot impossibly be the Hue bridge mis identifiying the bulb I would assume.

@stefanschaedeli did you see my remarks / questions above?

@bramstroker sorry, got interupted by the birth of my daughter and forgot about this one :D the ID gets filled by the zigbee2mqtt application and passed over by the mqtt integration into home assistant. the ids are
It would be this lamp:
https://www.amazon.de/Philips-Hue-Wandleuchte-Aussenbereich-kompatibel/dp/B07KMPCHBV

@stefanschaedeli Congratz on the birth of your daughter.
I don't have Zigbee myself, so also don't use Zigbee2Mqtt.
But this looks like a bug in that integration to me when it returns an id for a completely other model.
Could you have a look into device info of the eg_eingang_lampe_hue, and see what manufacturer and model is exposed there for your light?
For example screenshot here for one of my Hue lights:

interstingly here it shows another ID... its only in the error log it shows the other id

Please enable debug logging https://homeassistant-powercalc.readthedocs.io/en/latest/troubleshooting/debug-logging.html.
Restart and have a look into the debug logs, that should give insight. Or share the logs in this issue if you can't find the culprit.

its the same as before:

This are not the debug logs, but only the log which resulted in an error. HA will only log error level logs by default.
When you enable debug logging for powercalc you'll get hundreds of logs lines after restarting.
That should hopefully give some more clues.

And one more question. You did setup all the sensors with the GUI/discovery, right? Or did you use YAML?
When using GUI you can click the three dots at the powercalc integration panel and click "Download diagnostics".

This are not the debug logs, but only the log which resulted in an error. HA will only log error level logs by default. When you enable debug logging for powercalc you'll get hundreds of logs lines after restarting. That should hopefully give some more clues.

2023-04-22 20:32:36.183 INFO (MainThread) [homeassistant.setup] Setting up powercalc 2023-04-22 20:32:36.184 INFO (MainThread) [homeassistant.setup] Setup of domain powercalc took 0.0 seconds 2023-04-22 20:32:36.559 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.powercalc 2023-04-22 20:32:36.578 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.powercalc 2023-04-22 20:32:36.579 DEBUG (MainThread) [custom_components.powercalc.sensors.daily_energy] Creating daily_fixed_energy energy sensor (name=Heizungssteuerung_kwh, entity_id=sensor.heizungssteuerung_kwh, unique_id=Heizungssteuerung) 2023-04-22 20:32:36.579 DEBUG (MainThread) [custom_components.powercalc.sensors.daily_energy] Creating daily_fixed_energy power sensor (base_name=Heizungssteuerung unique_id=Heizungssteuerung) 2023-04-22 20:32:36.579 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=sensor.dummy entity_category=None, sensor_name=Heizungssteuerung_pwr strategy=FixedStrategy manufacturer= model= standby_power=0.00 unique_id=Heizungssteuerung_power) 2023-04-22 20:32:36.586 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.powercalc 2023-04-22 20:32:36.586 DEBUG (MainThread) [custom_components.powercalc.sensors.daily_energy] Creating daily_fixed_energy energy sensor (name=musiccast Standby_kwh, entity_id=sensor.musiccast_standby_kwh, unique_id=musiccast Standby) 2023-04-22 20:32:36.586 DEBUG (MainThread) [custom_components.powercalc.sensors.daily_energy] Creating daily_fixed_energy power sensor (base_name=musiccast Standby unique_id=musiccast Standby) 2023-04-22 20:32:36.586 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=sensor.dummy entity_category=None, sensor_name=musiccast Standby_pwr strategy=FixedStrategy manufacturer= model= standby_power=0.00 unique_id=musiccast Standby_power) 2023-04-22 20:32:36.592 DEBUG (MainThread) [custom_components.powercalc.discovery] light.eg_eingang_lampe_hue: Auto discovered model (manufacturer=Signify Netherlands B.V., model=Hue outdoor Impress wall lamp (1743030P7)) 2023-04-22 20:32:36.612 DEBUG (MainThread) [custom_components.powercalc.strategy.lut] Loading LUT data file: /config/custom_components/powercalc/power_profile/../data/signify/929003045001/color_temp.csv.gz 2023-04-22 20:32:36.616 DEBUG (MainThread) [custom_components.powercalc.strategy.lut] LUT file loaded: 1664 lines 2023-04-22 20:32:36.617 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=light.eg_eingang_lampe_hue entity_category=None, sensor_name=eg_eingang_lampe_hue_pwr strategy=LutStrategy manufacturer=signify model=929003045001 standby_power=0.30 unique_id=pc_0x00178801067f11b6_light_zigbee2mqtt) 2023-04-22 20:32:36.617 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: eg_eingang_lampe_hue_kwh 2023-04-22 20:32:36.623 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.eg_eingang_lampe_hue_pwr to device a327327c26509f028f203231e2dbf11a 2023-04-22 20:32:36.627 DEBUG (MainThread) [custom_components.powercalc.sensors.daily_energy] sensor.heizungssteuerung_kwh: Restoring state: 89.9529 2023-04-22 20:32:36.627 DEBUG (MainThread) [custom_components.powercalc.sensors.daily_energy] sensor.musiccast_standby_kwh: Restoring state: 93.3425 2023-04-22 20:32:36.630 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.eg_eingang_lampe_hue_kwh to device a327327c26509f028f203231e2dbf11a 2023-04-22 20:32:36.643 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.powercalc 2023-04-22 20:32:36.643 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.powercalc 2023-04-22 20:32:36.643 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.powercalc 2023-04-22 20:32:36.643 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.powercalc 2023-04-22 20:32:36.643 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.powercalc 2023-04-22 20:32:36.643 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.powercalc 2023-04-22 20:32:36.644 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.powercalc 2023-04-22 20:32:36.644 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.powercalc 2023-04-22 20:32:36.645 DEBUG (MainThread) [custom_components.powercalc.discovery] light.alu_q: Auto discovered model (manufacturer=IKEA of Sweden, model=TRADFRI driver for wireless control (10 watt) (ICPSHC24-10EU-IL-1)) 2023-04-22 20:32:36.654 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=light.alu_q entity_category=None, sensor_name=Alu Q_pwr strategy=LinearStrategy manufacturer= model= standby_power=0.00 unique_id=0x000d6ffffefce3cb_light_zigbee2mqtt) 2023-04-22 20:32:36.655 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: Alu Q_kwh 2023-04-22 20:32:36.655 DEBUG (MainThread) [custom_components.powercalc.discovery] light.eg_buro_bambus: Auto discovered model (manufacturer=IKEA of Sweden, model=TRADFRI driver for wireless control (10 watt) (ICPSHC24-10EU-IL-1)) 2023-04-22 20:32:36.655 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=light.eg_buro_bambus entity_category=None, sensor_name=Bambus_pwr strategy=LinearStrategy manufacturer= model= standby_power=0.00 unique_id=0x086bd7fffe076348_light_zigbee2mqtt) 2023-04-22 20:32:36.655 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: Bambus_kwh 2023-04-22 20:32:36.655 DEBUG (MainThread) [custom_components.powercalc.discovery] light.alu_rund: Auto discovered model (manufacturer=IKEA of Sweden, model=TRADFRI driver for wireless control (30 watt) (ICPSHC24-30EU-IL-1)) 2023-04-22 20:32:36.655 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=light.alu_rund entity_category=None, sensor_name=Alu Rund_pwr strategy=LinearStrategy manufacturer= model= standby_power=0.00 unique_id=0x000b57fffee363e3_light_zigbee2mqtt) 2023-04-22 20:32:36.656 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: Alu Rund_kwh 2023-04-22 20:32:36.656 DEBUG (MainThread) [custom_components.powercalc.discovery] light.alu_l: Auto discovered model (manufacturer=IKEA of Sweden, model=TRADFRI driver for wireless control (30 watt) (ICPSHC24-30EU-IL-1)) 2023-04-22 20:32:36.656 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=light.alu_l entity_category=None, sensor_name=Alu L_pwr strategy=LinearStrategy manufacturer= model= standby_power=0.00 unique_id=0x90fd9ffffe18418f_light_zigbee2mqtt) 2023-04-22 20:32:36.656 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: Alu L_kwh 2023-04-22 20:32:36.656 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=light.eg_schlafzimmer_stilllicht entity_category=None, sensor_name=eg schlafzimmer stilllicht_pwr strategy=LinearStrategy manufacturer= model= standby_power=0.00 unique_id=None) 2023-04-22 20:32:36.656 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: eg schlafzimmer stilllicht_kwh 2023-04-22 20:32:36.657 DEBUG (MainThread) [custom_components.powercalc.discovery] switch.ug_buro_heizung: Auto discovered model (manufacturer=IKEA of Sweden, model=TRADFRI control outlet (E1603#slash#E1702#slash#E1708)) 2023-04-22 20:32:36.657 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=switch.ug_buro_heizung entity_category=None, sensor_name=Heizung_pwr strategy=FixedStrategy manufacturer= model= standby_power=0.00 unique_id=0x086bd7fffe3714a8_switch_zigbee2mqtt) 2023-04-22 20:32:36.657 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: Heizung_kwh 2023-04-22 20:32:36.658 DEBUG (MainThread) [custom_components.powercalc.discovery] climate.ir_heizung_ug_buro: Auto discovered model (manufacturer=Tuya, model=Wonderwall Air Art Smart (aemgen54nfdktfej)) 2023-04-22 20:32:36.660 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=climate.ir_heizung_ug_buro entity_category=None, sensor_name=ir_heizung_ug_buro_pwr strategy=FixedStrategy manufacturer= model= standby_power=0.00 unique_id=tuya.22000752a4e57c9a91b7) 2023-04-22 20:32:36.660 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: ir_heizung_ug_buro_kwh 2023-04-22 20:32:36.661 DEBUG (MainThread) [custom_components.powercalc.discovery] switch.eg_wohnzimmer_kugel: Auto discovered model (manufacturer=IKEA of Sweden, model=TRADFRI control outlet (E1603#slash#E1702#slash#E1708)) 2023-04-22 20:32:36.661 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=switch.eg_wohnzimmer_kugel entity_category=None, sensor_name=Kugel_pwr strategy=FixedStrategy manufacturer= model= standby_power=0.00 unique_id=0x086bd7fffe2b99e5_switch_zigbee2mqtt) 2023-04-22 20:32:36.661 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: Kugel_kwh 2023-04-22 20:32:36.663 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.alu_q_pwr to device 186b8e08addbe7a51b4322cbf6db48ea 2023-04-22 20:32:36.664 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.eg_buro_bambus_pwr to device c7a21d590b7bb9cad503c09d1fc4e266 2023-04-22 20:32:36.665 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.alu_rund_pwr to device 5717e19d9affedcd5fde8c60b956e2c3 2023-04-22 20:32:36.666 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.alu_l_pwr to device 72aaa61b04b60bd55e7bc5de5577606d 2023-04-22 20:32:36.668 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.ug_buro_heizung_pwr to device 948aada5706699a207c68f8dfeccea32 2023-04-22 20:32:36.669 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.ir_heizung_ug_buro_pwr to device 2aae1236e63f5177ca6c58051390c045 2023-04-22 20:32:36.670 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.eg_wohnzimmer_kugel_pwr to device c1306ef319343f0c03265de619f2ef79 2023-04-22 20:32:36.702 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.alu_q_kwh to device 186b8e08addbe7a51b4322cbf6db48ea 2023-04-22 20:32:36.703 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.eg_buro_bambus_kwh to device c7a21d590b7bb9cad503c09d1fc4e266 2023-04-22 20:32:36.704 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.alu_rund_kwh to device 5717e19d9affedcd5fde8c60b956e2c3 2023-04-22 20:32:36.705 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.alu_l_kwh to device 72aaa61b04b60bd55e7bc5de5577606d 2023-04-22 20:32:36.705 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.ug_buro_heizung_kwh to device 948aada5706699a207c68f8dfeccea32 2023-04-22 20:32:36.706 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.ir_heizung_ug_buro_kwh to device 2aae1236e63f5177ca6c58051390c045 2023-04-22 20:32:36.707 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.eg_wohnzimmer_kugel_kwh to device c1306ef319343f0c03265de619f2ef79 2023-04-22 20:33:07.201 DEBUG (MainThread) [custom_components.powercalc.sensors.power] switch.ug_buro_heizung: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:07.235 DEBUG (MainThread) [custom_components.powercalc.sensors.power] switch.eg_wohnzimmer_kugel: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:07.656 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.eg_buro_bambus: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:07.657 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.alu_rund: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:07.657 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.alu_q: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:07.658 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.alu_l: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:07.723 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.eg_eingang_lampe_hue: State changed to "unavailable". Power:0.00 2023-04-22 20:33:08.927 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.eg_eingang_lampe_hue: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:08.928 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.alu_l: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:08.929 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.alu_q: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:08.929 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.alu_rund: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:08.929 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.eg_buro_bambus: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:08.933 DEBUG (MainThread) [custom_components.powercalc.sensors.power] switch.eg_wohnzimmer_kugel: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:08.933 DEBUG (MainThread) [custom_components.powercalc.sensors.power] switch.ug_buro_heizung: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:13.832 DEBUG (MainThread) [custom_components.powercalc.sensors.power] climate.ir_heizung_ug_buro: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:22.819 DEBUG (MainThread) [custom_components.powercalc.sensors.power] sensor.dummy: State changed to "on". Power:0.00 2023-04-22 20:33:22.819 DEBUG (MainThread) [custom_components.powercalc.sensors.power] sensor.dummy: State changed to "on". Power:21.00 2023-04-22 20:33:22.820 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.eg_eingang_lampe_hue: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:22.820 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.alu_q: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:22.821 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.eg_buro_bambus: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:22.821 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.alu_rund: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:22.822 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.alu_l: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:22.822 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.eg_schlafzimmer_stilllicht: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:22.823 DEBUG (MainThread) [custom_components.powercalc.sensors.power] switch.ug_buro_heizung: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:22.823 DEBUG (MainThread) [custom_components.powercalc.sensors.power] climate.ir_heizung_ug_buro: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:22.824 DEBUG (MainThread) [custom_components.powercalc.sensors.power] switch.eg_wohnzimmer_kugel: Source entity has an invalid state, setting power sensor to unavailable 2023-04-22 20:33:57.506 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.eg_buro_bambus: State changed to "off". Power:0.00 2023-04-22 20:33:57.658 DEBUG (MainThread) [custom_components.powercalc.sensors.power] switch.ug_buro_heizung: State changed to "off". Power:0.00 2023-04-22 20:33:57.930 DEBUG (MainThread) [custom_components.powercalc.strategy.linear] light.alu_rund: Linear mode state value: 18 range(1-127) 2023-04-22 20:33:57.931 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.alu_rund: State changed to "on". Power:2.54 2023-04-22 20:33:57.933 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.alu_q: State changed to "off". Power:0.00 2023-04-22 20:33:57.934 DEBUG (MainThread) [custom_components.powercalc.strategy.linear] light.alu_l: Linear mode state value: 18 range(1-63) 2023-04-22 20:33:57.934 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.alu_l: State changed to "on". Power:2.41 2023-04-22 20:33:58.203 DEBUG (MainThread) [custom_components.powercalc.sensors.power] switch.eg_wohnzimmer_kugel: State changed to "off". Power:0.00 2023-04-22 20:33:58.269 ERROR (MainThread) [custom_components.powercalc.strategy.lut] light.eg_eingang_lampe_hue: Lookup table not found (model:<PHONE_NUMBER>01, color_mode: hs) 2023-04-22 20:33:58.272 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.eg_eingang_lampe_hue: State changed to "on". Power:None 2023-04-22 20:38:00.634 DEBUG (MainThread) [custom_components.powercalc.strategy.linear] light.alu_l: Linear mode state value: 125 range(63-127) 2023-04-22 20:38:00.635 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.alu_l: State changed to "on". Power:6.89 2023-04-22 20:38:00.649 DEBUG (MainThread) [custom_components.powercalc.strategy.linear] light.alu_rund: Linear mode state value: 125 range(1-127) 2023-04-22 20:38:00.650 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.alu_rund: State changed to "on". Power:5.94 2023-04-22 20:38:36.646 DEBUG (MainThread) [custom_components.powercalc.sensors.daily_energy] sensor.musiccast_standby_kwh: Updating daily_fixed_energy sensor: 93.3457 2023-04-22 20:44:36.654 DEBUG (MainThread) [custom_components.powercalc.sensors.daily_energy] sensor.musiccast_standby_kwh: Updating daily_fixed_energy sensor: 93.3478

And one more question. You did setup all the sensors with the GUI/discovery, right? Or did you use YAML? When using GUI you can click the three dots at the powercalc integration panel and click "Download diagnostics".

I have a mix due to historical reasons... the manual ones work though (yaml and gui) the automatic once are the "strange behaving"

Relevant log lines are these. I have omitted the date etc, to make it a bit more readable.
light.eg_eingang_lampe_hue: Auto discovered model (manufacturer=Signify Netherlands B.V., model=Hue outdoor Impress wall lamp (1743030P7))
Loading LUT data file: /config/custom_components/powercalc/power_profile/../data/signify/929003045001/color_temp.csv.gz
LUT file loaded: 1664 lines
Creating power sensor (entity_id=light.eg_eingang_lampe_hue entity_category=None, sensor_name=eg_eingang_lampe_hue_pwr strategy=LutStrategy manufacturer=signify model=929003045001 standby_power=0.30 unique_id=pc_0x00178801067f11b6_light_zigbee2mqtt)

The correct model id is autodiscovered 1743030P7, but next line the model id is forced to<PHONE_NUMBER>01 and also that LUT file is selected.
Only way I can see this happening is you manually selected the model when setting up the sensor.
So please share the diagnostics for this powercalc configuration as requested in comment above.

Sorry, tired to do this but there was no manual entry... I did reinstall the plugin from hacs and the issue is gone... I think it must have been somehow a previos attemd of a manual entry that failed to delete somehow...
so the error is gone. its still does not yet detect the lamp, but thats expected as its not yet on the supported list...

Very strange issue still, but glad you got it resolved and error is gone.
Yes you are correct, it shouldn't detect the light because it is not supported (yet).


Error when load best_stg2.pth

Hello,
something wrong with my model when I try to load weights
I get:
RuntimeError: Error(s) in loading state_dict for DFINE:
Missing key(s) in state_dict: "encoder.lateral_convs.0.conv_bn_fused.weight", ...
Before I successfully load trained in google colab model with same  configuration.
Training was successfully finished, but something wrong with model state_dict when I try to load it for inference test:

Found error in my config, case closed.


ocioview image and PySide6 updates

This PR makes the following changes to ocioview:

Image viewer operates on RGB instead of RGBA, with an assumed opaque alpha
Image viewer pan and zoom regression fixed following change from imath to NumPy for transform implementation
Image read implementations moved to utility module
NumPy array used for image data messages instead of oiio ImageBuf
UI size adjustments to account for Qt6 style changes
Pyide6 compatibility fixes

@michdolan , should we go ahead and merge this?

@remia thoughts on the CI failure I'm getting since updating the base? It's related to CMake, but this work only changed Python files internal to ocioview. Safe to ignore?

@remia thoughts on the CI failure I'm getting since updating the base? It's related to CMake, but this work only changed Python files internal to ocioview. Safe to ignore?

I haven't time to investigate properly this week but it seems like the issue we have in https://github.com/AcademySoftwareFoundation/OpenColorIO/issues/1964 ? I didn't see the error as the job was in canceled state today, I relaunched it and it now passes so this might have been fixed with a CMake update.


Is this working with beta versions of angular?

I'm using angular2 2.0.0-beta.0 either I'm missing something or I'm really not seeing how to include the new libraries into the components.ts

no, it is doesn't right now

Thanks for letting me know. I'm trying ag-grid now. Still too early to make any comments on it.

you can try ng2-table

Does it allow the cells to be editable? I'm currently struggling with ag-grid as it's not giving out any errors and yet the data isn't loading.


Allow custom websocket implementations

By adding WS_PORT and WS_IP to the HostInfo as defined in the OSCQuery required attributes, we can implement the bi-directional websocket support outside of this library.

@joreg - thanks for submitting this PR. The OSCQuery spec is a little vague about how to specify that a server support Websockets or not. My best understanding is that a server that does not support them should not provide them as fields when returning a HOST_INFO request, but this implementation provides them by default now. What do you think about only including them if they are passed to the fluent constructor?

sounds good to me!


Register jQuery plugin

It's very hard to maintain use without a version number. It would also be nice if it was listed on the jQuery plugin site (http://plugins.jquery.com/) with the proper metadata.
Thanks!!

jQuery plugins have been moved to npm. I'd dig it if you could create a PR with the proper package.json details.


simplified example in docs

Thanks, but this changes the results from a single null value to an empty array. null actually has some value here, indicating that we haven't produced any todos at all, not just that they are none left. It may not matter in this example, but we want to establish that null is a good pattern to use.


Operation could destabilize the runtime

Environment
TFS 16.131.27701.1
Issue Description
https://github.com/nunit/nunit3-vs-adapter/issues/519

Fixed with https://github.com/Microsoft/vstest/pull/1997, we have also released latest nuget package (16.0.2 preview) of test platform with above change, please upgrade to it.


Action hanging forever after error

I get the following logs, and the action just hangs:
Built HTML file: final.html
Built PDF file: final.pdf
Gracefully shut down image server.
(node:1) UnhandledPromiseRejectionWarning: TimeoutError: Navigation Timeout Exceeded: 30000ms exceeded
    at /node_modules/puppeteer/lib/LifecycleWatcher.js:142:21
  -- ASYNC --
    at Frame.<anonymous> (/node_modules/puppeteer/lib/helper.js:110:27)
    at Page.goto (/node_modules/puppeteer/lib/Page.js:629:49)
    at Page.<anonymous> (/node_modules/puppeteer/lib/helper.js:111:23)
    at /markdown-to-pdf.js:159:14
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:1) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Thank you, I will look into this shortly. Are you able to email me the final.md file for testing?

This should be fixed by https://github.com/BaileyJM02/markdown-to-pdf/pull/22
by adding https://github.com/BaileyJM02/markdown-to-pdf/pull/22/commits/3ff190b5f2bada1818c62359bd3f0658ad31d826
and https://github.com/BaileyJM02/markdown-to-pdf/pull/22/commits/d743c4256a9a979b2ca1b5fb89c266c92dfe0f23

Thank you, I will look into this shortly. Are you able to email me the final.md file for testing?

It's from here
https://github.com/sszczep/BD2021/tree/main/content
If you merge these MDs with cat *.md > final.md, just like in the gh action (we used pandoc instead)

Closing as this was fixed in #22.


Users should be able to modify requests at a high level

There is a common set of user-reported issues that could be solved by making high-level requests easier to modify.
This change would support these use cases and more:

Sending unsigned requests to S3.
Adding custom headers
Augmenting the user agent sent with requests

Implementers adding a new method to an operation should take care to avoid namespace issues with the new method name(s).
A possible implementation would involve users passing a closer that took a request as input and then returned a request.
Related Issue(s):

https://github.com/awslabs/aws-sdk-rust/issues/389

This was completed in #1647.


[BUG]Clusters deployed using IPV6 do not support the DiscoverNodes method.

What is the bug?
When using the opensearch-go library to access an opensearch cluster deployed with IPV6, an access error will occur when calling other APIs after calling the DiscoverNodes method.
How can one reproduce the bug?

Construct a client using NewClient
Call client.DiscoverNodes method
Calling another API
For example: opensearchapi.CatMasterRequest{}.Do(context.Background(), client)

What is the expected behavior?
Able to use the opensearch-go library to normally access the OpenSearch cluster deployed with IPV6
What is your host/environment?
go1.17.1 Windows/amd64
Do you have any screenshots?

Do you have any additional context?

Failure

+Success

Looks legit. Want to try to add a test and implement a fix for this?


Skipping used options

Hello,
I am using the editable table.  In the example there are two columns (status and group) that retrieve their options from some scope list.  Is there a way to add new rows that will not display the options used in the rows above?  So for example, since status1 and status2 have been used, then the add row would provide only status3 and status4.  If you edit set the status to status3, then adding a new row would give you only the status4 option.
Thanks
Dino

You could probably setup a function that loops through any existing values that are used and removes them from the available list.
Or, create an AJAX call and have your backend query filter out the values already saved to the db (if items are being saved).

@eugef There has been no follow up, I think this can be closed.


ci(snap): Add snap go mod to dependabot

Adding the snap's hooks package to dependabot in order to get automated PRs for the dependency upgrades.
Signed-off-by: Farshid Tavakolizadeh<EMAIL_ADDRESS>

If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?)
[ ] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

New Dependency Instructions (If applicable)

Codecov Report

Merging #3995 (7d0cc4e) into main (375f1d8) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #3995   +/-   ##
=======================================
  Coverage   47.19%   47.19%
=======================================
  Files         114      114
  Lines        9831     9831
=======================================
  Hits         4640     4640
  Misses       4804     4804
  Partials      387      387

Continue to review full report at Codecov.

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


Differences between VCF and consensus sequence

Hi,
I am testing how accurately I can correct reads from nanopore Minion by sequencing a plasmid.
I generated a VCF file by following all the steps given in this site.  For the nanopolish variant I run the following code:
~/nanopolish/nanopolish variants -r fastq_runid_d22b8e7fd196418c6c106e08c22cdb0696c0264e_0.fastq -g ~/pGUS1.fa -b reads.sorted.bam --ploidy=1 -o pGUS1.vcf --min-candidate-frequency=0.65
This gave me a VCF with 2 variants (great!)
Then I wanted to generate a consensus fasta file.  I run the following code:
~/nanopolish/nanopolish variants -r fastq_runid_d22b8e7fd196418c6c106e08c22cdb0696c0264e_0.fastq -g ~/pGUS1.fa -b reads.sorted.bam --ploidy=1 --consensus polished.pGUS1.fa  --min-candidate-frequency=0.65
This generated a consensus fa file that has 39 mismatches compared to the original reference.  I was expecting to get a consensus with the two variants reported in the VCF file.  Why the difference? How can I correct it?
Thanks in advanced for your help.
-MariaI

Hi Marial,
In consensus mode, nanopolish will test all possible single base edits to the input genome. In variant calling mode, it will only test variants that have a high level support in the basecalled reads. In the former case it is trying many more candidate variants, so more of them end up being called as "improvements" and are written to the VCF file.
Jared


dynamic resources

Hi, I need to define dynamic resources, such as:
x = luigi.Parameter()
if x==1:
resources = {"x1": 1}
elif x==2:
resources = {"x2": 1}
what is the solution?
I have to change the init function?
I think the way of resources definition should be the same as requires, in a function not in a member variable.

The answer that @erikbern gave at https://github.com/spotify/luigi/issues/1362#issuecomment-152177510 maybe is the right choice. e.g.
➜  python
Python 2.7.9 (default, Jul 27 2015, 11:02:06)
[GCC 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import luigi
>>> class FoobarTask(luigi.Task):
...   x = luigi.IntParameter()
...   @property
...   def resources(self):
...     return {"x{}".format(self.x): 1}
...
>>> f1 = FoobarTask(x=2)
>>> f1.x
2
>>> f1.resources
{'x2': 1}
>>>

we could change the default interface so that it's a method, might make more sense
let me know if the property decorator works though

@mvj3 @erikbern , the property decorator works !
Thanks very much. This problem could be closed.


Cucumber Pretty 1.6.0 no longer works with Cucumber 5.1.0

Cucumber Pretty 1.6.0 no longer works with Cucumber 5.1.0
Can we have the backward compatibility with Cucumber Pretty? As we are using Protractor-cucumber-framework which is still not pdated.
Getting the below error message.
E/launcher - Error: TypeError: options.eventDataCollector.getTestCaseAttempt is not a function
11-Oct-2019 12:47:43 | at EventEmitter.PrettyFormatter.options.eventBroadcaster.on (D:\Atlassian\Data\BambooRemoteAgentHome\xml-data\build-dir\ADV-APU0-SC\node_modules\cucumber-pretty\index.js:52:70)
11-Oct-2019 12:47:43 | at emitOne (events.js:116:13)
11-Oct-2019 12:47:43 | at EventEmitter.emit (events.js:211:7)

For Cucumber.js versions 3 to 5 please use cucumber-pretty 1.5.
For Cucumber.js version 6 (latest) please use cucumber-pretty 1.6 (latest).
You can either update Cucumber.js to the latest version or install specific version of cucumber-pretty with cucumber-pretty@<version> --save-exact command.
npm install<EMAIL_ADDRESS>--save-exact

You should get a warning when trying to install<EMAIL_ADDRESS>without cucumber@6 because it declares "peerDependencies": { "cucumber": ">=6.0.0" }.

I've unpublished 1.6.0 and published it as 6.0.0 so any existing installs with default ^1.5.2 version range will continue to work as before. If you ever update to cucumber@6 then you need to install cucumber-pretty@6 as well as since ^ version range does not automatically update major versions.

Thank you very much for a swift reply, I have now downgraded the Cucumber
Pretty and made sure that ^ is removed. As we are using
Protracotor-Cucumber-Framework which is still not supporting Cucumber
6.0.2.
Appreciate your prompt response.
On Fri, Oct 11, 2019 at 3:29 PM Ilya Kozhevnikov<EMAIL_ADDRESS>wrote:

I've unpublished 1.6.0 and published it as 6.0.0 so any existing installs
with default ^1.5.2 version range will continue to work as before. If you
ever update to cucumber@6 then you need to install cucumber-pretty@6 as
well as since ^ version range does not automatically update major
versions.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kozhevnikov/cucumber-pretty/issues/11?email_source=notifications&email_token=ANOO2XG23RBI5XRO2OEEYFTQOAB33A5CNFSM4I7UPPGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEA6ZCFY#issuecomment-540905751,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANOO2XCJLLWGORNLNYAV26TQOAB33ANCNFSM4I7UPPGA
.


[CI] Fix code coverage display in README

The README's coverage icon currently displays "unknown" for the code coverage report, although everything seems to be running fine on the CI, see below:

It's a relatively low-priority issue though.

@sebastiendan Just noticed with latest commits that now the CI job for code coverage fails with the latest error,
[2023-05-01T11:34:44.580Z] ['error'] There was an error running the uploader: Error uploading to [https://codecov.io:](https://codecov.io/) Error: There was an error fetching the storage URL during POST: 400 - [ErrorDetail(string='This repository has been deactivated. To resume uploading to it, please activate the repository in the codecov UI: https://app.codecov.io/github/topos-network/ice-frost/settings', code='invalid')]

Did you do something related?

The repo was deactivated on Codecov. It's been re-activated and the original problem was fixed by #2 (for code coverage fix) and #3 (for badge update).


Connect Deutsche Telekom sign-in page to appcenter

Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Maybe this is the same as https://github.com/microsoft/appcenter/issues/674 which is closed but what I want still does not work.
As a Deutsche Telekom Employee I want to be able to chose the "Corporate and school" option at appcenter login, enter my<EMAIL_ADDRESS>email address, login at DT's sign-in page and be redirected back to appcenter as a DT user.
The last step currently does not work, I guess because the redirct_url for appcenter is not registered.


Allow filter pipelinerun by event title

Let filter events by title, using CEL
add event_title which support push and pull request
Fixes #768
need to go after #751

Changes

Submitter Checklist

[ ] ♽  Run make test lint before submitting a PR (ie: with pre-commit, no need to waste CPU cycle on CI
[ ] 📖 If you are adding a user facing feature or make a change of the behavior, please verify that you have documented it
[ ] 🧪 100% coverage is not a target but most of the time we would rather have a unit test if you make a code change.
[ ] 🎁 If that's something that is possible to do please ensure to check if we can add a e2e test.
[ ] 🔎 If there is a flakiness in the CI tests then don't necessary ignore it, better get the flakyness fixed before merging or if that's not possible there is a good reason to bypass it. (token rate limitation may be a good reason to skip).

Codecov Report

Merging #769 (a90e2dc) into main (1814723) will decrease coverage by 0.03%.
The diff coverage is 61.90%.

@@            Coverage Diff             @@
##             main     #769      +/-   ##
==========================================
- Coverage   65.40%   65.36%   -0.04%
==========================================
  Files          75       75
  Lines        4500     4545      +45
==========================================
+ Hits         2943     2971      +28
- Misses       1277     1294      +17
  Partials      280      280

Impacted Files
Coverage Δ

pkg/params/clients/clients.go
11.11% <ø> (+0.26%)
:arrow_up:

pkg/pipelineascode/match.go
49.15% <0.00%> (ø)

pkg/provider/bitbucketcloud/bitbucket.go
76.77% <0.00%> (-1.01%)
:arrow_down:

pkg/provider/bitbucketserver/bitbucketserver.go
83.56% <0.00%> (-1.17%)
:arrow_down:

pkg/provider/github/github.go
65.51% <10.00%> (-2.88%)
:arrow_down:

pkg/provider/gitlab/gitlab.go
79.76% <11.11%> (-2.55%)
:arrow_down:

pkg/matcher/cel.go
82.75% <94.11%> (+14.75%)
:arrow_up:

pkg/matcher/annotation_matcher.go
93.85% <100.00%> (+2.63%)
:arrow_up:

pkg/matcher/annotation_tasks_install.go
84.37% <100.00%> (+0.24%)
:arrow_up:

pkg/provider/bitbucketcloud/events.go
76.55% <100.00%> (+0.16%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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

e2e tests should work now, aside of the annoying token expiration limit


Debug one specific case in a rspec file

Including the possibility to debug one specific case in one specific rspec test

LGTM thanks!


how to develop coding skills for the best programming results

###proposed title of the article:
how to develop coding skills for the best programming results
####proposed article introduction:
Nowadays, programming skills are in high demand. A programmer is a computer and web program development specialist who is in charge of creating the program architecture, implementing it, optimizing it, and testing it. To be successful at coding, you must enjoy what you do. Even if you already engage in professional growth, you should learn to keep up with emerging technologies. This entails learning new languages, libraries, or frameworks.
There are numerous reasons why coding is vital, as well as numerous motivations to learn how coding works is a fundamental component of today's most fascinating and rewarding occupations. Furthermore, code is completely everywhere! Languages like Java and Python hold the keys to the capabilities.
The following are suggestions for improving your coding expertise: Participate in programming contests, Everyday practice since leads to perfection, Do not be afraid to enquire Look into a new programming language, write a clean code free from errors. Besides learning how to obtain information from google to save time.
#####key takeaways
There are numerous strategies to increase your coding abilities
Learning one or more programming languages is an important aspect of developing coding skills.
Learners can search, use, and apply information outside the confines of what a professor or teacher may demand.

Besides, my article is educational as well as professional. unlimited revisions are made.
Quick turnaround time is involved and a conversational tone for easy understanding of the article.
####References
N/A

Thank you for your response and we thank you for submitting your topic. After some careful consideration it struck us that this topic may be a bit over saturated throughout other blog sites and official documentations as previously mentioned on your topic form by our content moderator.
We typically refrain from publishing content that is covered widely on the net or other blogs. As we're more interested in original, practitioner-focused content that takes a deeper dive into programming-centric concepts.
We believe this is the best way for students to build a great portfolio (for potential employers) is by building what does not exist and what can provide the most value.
You are more than welcome to pursue another more in depth topic


Use GM_info.namespace as homepage URL

Fixes an issue with Tampermonkey where the edit note contains undefined instead of the hompage URL, see the report in the forum and my reply.
The namespace property has the widest support among userscript engines, while homepageURL and homepage are only available in Violentmonkey and Tampermonkey respectively.

Thanks!


Remove all the old .sh scripts for build and deploy as the mvn docker plugin is what we use

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/fabric8-quickstarts-master-pullreq/453/
Test PASSed.


Chore/docs fix

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


ListTile Leading Height Constraint Issue

The current implementation of the ListTile in Flutter constrains the height of the leading widget to a maximum of 56px.
This constraint does not align with the Material Design spec and guidelines, which permit a height of up to 64px for video and for image thumbnails.

Current implementation of the ListTile leading height constraint can be found here.
Material Design guidelines for list components can be found here.

This looks similar to https://github.com/flutter/flutter/issues/98178 for which you can follow-up in it for further updates.
Closing this as a duplicate. If you disagree, write in comments and I'll reopen it.


Port over OpenCLIP models

I assigned myself but could use help

Most is ported over; just need to figure out why the tolerance is not matching on the test

Tolerence not matching here
https://github.com/soniajoseph/ViT-Prisma/blob/sonia-open-clip-acc-baseline/tests/test_loading_open_clip.py


Add endpoint to retrieve random entry

At the moment only the entire document can be fetched, but retrieving a random entry would be way more interesting.
I'm leaving this issue open on purpose because it it quite simple and a beginner might try and have a go at it.

Hi, how it is going? I'll be glad to contribute, please assign this issue to me.

Go ahead @enzomzaocv , let me know if you need help. I'll try and development instructions tomorrow


Render module refactor

gathered the render-related functions into nmmo/render
removed config.RENDER, and made the renderer external to the env/realm
fixed some packets so that the client can work
config.SAVE_REPLAY stays in the env. Replay class was renamed to PacketManager and combined with replay_helper
created test scripts for showing how the online and replay rendering works

Some issues

The market mechanism has been changed but the packet structure remains the same. I guess this is ok because it's just for visualization
Team/color-related issues were handled by a hacky "patch_patcket" function. Hopefully, this can go away soon or would need some work to integrate with team env.
I guess Wilderness overlay can be removed. Checking with Joseph.

@daveey Merged in the updated dev branch. It all works.
One issue is that a unit test related to item/inventory failed when merging your PR, but I think it happens rarely. The unit tests done after it were ok.


Shared launch intervals STILL don't work

This probably has something to do with the key-value pair stuff but I'm going to sleep right now, too tired.

This was an engage task timing issue


NSG for subnet with private endpoint - typo?

Currently, you can't configure Network Security Group (NSG) rules and user-defined routes for private endpoints. NSG rules applied to the subnet hosting the private endpoint are applied to the private endpoint. A limited workaround for this issue is to implement your access rules for private endpoints on the source subnets, though this approach may require a higher management overhead.
"NSG rules applied to the subnet hosting the private endpoint are applied to the private endpoint"
do you mean are not applied to private endpoint?
Also is this by design or feature enhancement is on the way? Want to know in the future whether it will change and NSG rule will be applied to the subnet of the private endpoint.

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

ID: 1d6cc016-6c8f-81d7-3b5b-edce932294cf
Version Independent ID: 619d6b5e-ea75-61dd-5ef4-f653f9822cb8
Content: Use private endpoints - Azure Storage
Content Source: articles/storage/common/storage-private-endpoints.md
Service: storage
Sub-service: common
GitHub Login: @santoshc
Microsoft Alias: santoshc

@RonnieQuan Thanks for the feedback. We are investigating the issue and will update you shortly.

@RonnieQuan Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@SumanthMarigowda-MSFT - Hi, do you have any update on this? NSG rules for private endpoints are supported or not?

https://docs.microsoft.com/en-us/azure/private-link/private-endpoint-overview
"NSG is not supported on private endpoints. While subnets containing the private endpoint can have NSG associated with it, the rules will not be effective on traffic processed by the private endpoint."
A bit useless without NSGs

#reassign: @tamram

@RonnieQuan - It appears that the error in the documentation has been addressed .

#reassign: @santoshc1


yet another solution: overlaid git repositories

Here's another solution to the problem of managing your dotfiles in multiple, separate git repositories: https://github.com/capr/multigit  -- It's a more general solution, it's actually used as a package manager for a Lua module distribution called luapower.

This project is really cool, I'll have to see how it stacks up against mr and vcsh (my guess is very well). Thanks for sharing!

Just to share my solution for this: Bower. For example: https://github.com/rxrc/dotfiles/blob/master/bower.json

Related issue: #135 (basically the same idea, but without an external script)


gh-1538 - added removeGroup method to ViewUtil

Codecov Report

Merging #1539 into develop will increase coverage by 2.72%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #1539      +/-   ##
=============================================
+ Coverage      66.13%   68.85%   +2.72%
+ Complexity      1613      598    -1015
=============================================
  Files            695      405     -290
  Lines          24054    13365   -10689
  Branches        3141     1689    -1452
=============================================
- Hits           15907     9202    -6705
+ Misses          6893     3494    -3399
+ Partials        1254      669     -585

Impacted Files
Coverage Δ
Complexity Δ

...affer/cache/exception/CacheOperationException.java

...main/java/uk/gov/gchq/gaffer/data/GroupCounts.java

...fer/commonutil/exception/OverwritingException.java

...plementation/ordered/OrderedIntegerSerialiser.java

...mplementation/ordered/OrderedDoubleSerialiser.java

...nutil/elementvisibilityutil/ArrayByteSequence.java

.../store/operation/util/TransformStreamSupplier.java

.../uk/gov/gchq/gaffer/data/element/ElementTuple.java

...java/uk/gov/gchq/gaffer/store/StoreProperties.java

...v/gchq/gaffer/commonutil/ByteArrayEscapeUtils.java

... and 377 more

Continue to review full report at Codecov.

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


Update api_spec, fix for Exports API

Pulls in the latest updates to the api_spec repo to fix the Exports API. Bumps version to 1.3.6.
@kaip @sethtrain @gavindeschutter

:+1:

:+1:


NIFI 4774: Provide alternate implementation of Write-Ahead Log

Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

+1 LGTM, ran full suite of tests and numerous flows in a running NiFi instance. I did not do performance testing (Joe W did quite a few) but did verify the stability.  Thanks for the improvement! Merging to master

So, I was under the impression this was still a WIP.  I am a HUGE -1 on this change.  As @markap14 stated above, this is a critical section of code.  And while the previous version has serious flaws, they are at least somewhat know based on a long period of use.  In other words, we know there are problems, but they only bite us every so often.
This major rewrite of a critical piece being essentially forced on users, likely without their knowledge unless they are paying close attention, seems less than ideal.  This new implementation will need SIGNIFICANT testing before it can be trusted to the same degree as the previous, even with its issues.
I would have greatly preferred, and will still advocate for, making this a new implementation vs. a change to the WriteAheadFlowFileRepository (e.g. SequentialWriteAheadFlowFileRepository).  Again, there are other issues, but avoiding repo corruption in the previous WriteAheadFlowFileRepository would have been a reasonably simple fix, not requiring this rewrite.  While the rewrite may have other benefits, making it a new implementation (even if you were to make it the default...) would give users the opportunity to evaluate and decide for themselves when they are ready to move to the new repo, without forcing them to postpone an upgrade to 1.6.0 which has other worthwhile changes.
I know critical sections are change all the time, and that users won't always be aware of the changes.  However, the criticality of this section combined with it's history means I think we should tread a little more lightly.

It definitely requires considerable testing.  Burgess clearly did testing during his code review and he had favorable findings.  Mark obviously did.  I personally spent multiple weeks in long running protracted tests on a couple of systems one of which ran uninterrupted at a rate of 120,000 events per second (so WALI update rate was far higher) for 11 days with zero full gcs, perfectly stable performance, and in testing before after with a series of hard stops/restarts all behaviors were favorable.  Do you have tests underway with problematic findings? I'll state that based on my experience with this project I am very comfortable with this change and my own personally verified observations and evaluation.
It is critical code so it does help that the author that wrote the previous implementation also authored this one and that the problems of the previous one were well stated and the path to write it was clear.  That the changes were significant in nature in terms of total lines/files impacted I dont think reflects the improved simplicity this brings and as noted it was reusing much of the core logic of the previous more complicated approach.
The claim of a simple fix being available to close the previous gaps doesn't appear to be backed with a suggested implementation though it does look like you received a good response to why that wasn't feasible.
You raised some good points and got a really detailed reply from mark a month ago after which others such as myself and Burgess stayed active on this important item.  So, in that sense this all seems fine.
Now, having said all of this I do share your view that I would have preferred to see this be something users could opt-out since the old implementation even with the known potential issue has been extremely stable for a very long time and is relied upon heavily. I think using this new implementation as the default which closes the gap and which handles automatically reading old repository formatted partitions is correct and letting users that are on the old one stay on it as they wish is perfectly valid.
I dont think it is right to revert this change.  But I do think it is fair to reopen the JIRA and move toward a model allowing opt-out and leveraging this as a default.  @markap14 do you agree?  @mattyb149  do you?
Thanks

+1 to @joewitt 's comments on allowing opt-out or selection of the implementation. I'm good with this being the default going forward, but I think the other impl(s) should be available to the users.

I'm glad there's support for making this opt in.  One point on @joewitt 's comment : "The claim of a simple fix being available to close the previous gaps doesn't appear to be backed with a suggested implementation though it does look like you received a good response to why that wasn't feasible." ... the reasons given were reasons why @markap14 's original proposed solution wouldn't work, not why another solution might not.  For example (as suggested previously in email):

the immediate fix that I see needing is that when building the transaction map[1], we need to keep track of the lowest encountered corrupt transaction. Then, when iterating over the transaction map to rebuild the repo, we need to stop when that transaction is reached...  after that we can't trust that there are no missing transactions which could lead to repo corruption or incorrect state.

This is the relatively simple fix that I believe would be more appropriate to the WhriteAheadFlowFileRepository, as it would only prevent a known bug from causing corruption, as opposed to a major rewrite.  I never got any response suggesting this wouldn't work, rather simply that another solution was preferred... which turned out not to be feasible.  At that point, instead of circling back and trying to fix the bug, it appears as though the rewrite began.
If there's a reason the author of the original implementation doesn't believe my suggestion would work to prevent the observed corruption, I'd be happy to take another look.
[1] https://github.com/apache/nifi/blob/0f2ac39f69c1a744f151f0d924c9978f6790b7f7/nifi-commons/nifi-write-ahead-log/src/main/java/org/wali/MinimalLockingWriteAheadLog.java#L444

I am not opposed to providing a mechanism for opting out. I can look into creating a new PR that will provide that.

@devriesb I believe the issue with this proposed solution is that if we have 256 partitions (the default), for instance, then if one partition is not flushed to disk during a power failure, we would end up losing all data written to the other 255 partitions. Even if we were to use an fsync() for each CREATE event, that data would be lost with the proposed solution. So this could lead to quite a bit of data loss even with fsync enabled.

@markap14 yes... under this somewhat unusual circumstance, my proposed solution would sacrifice data for consistency.  However, if alwaysSync is set false, there isn't a guarantee of no loss anyway.
Also, I fully agree that an implementation that DOES guarantee no loss of CREATEs would be for the best.  My proposal above doesn't address that in any way.  It lives inside the "all or nothing" guarantee of the current (/previous?) WriteAheadFFR.

I would not consider that circumstance to be unusual, but rather a common scenario if power is lost, after NIFI-4775 has been implemented. Given that NIFI-4775 was created and that there were no objections, I considered that verification that it is intended to be implemented in the future. Once this is done, it will guarantee no loss of data (though it would allow loss of processing). The proposed solution, however, still results in data loss if power is lost, but also prevents us from implementing NIFI-4775 effectively because once it is implemented it would provide us no real benefit with such a solution, as it would still throw out those fsync'ed CREATE events if another partition was not also fsync'ed.

I'll grant NIFI-4775 may raise issues with my proposed solution. However, there is a problem right now.  My proposed solution addresses the problem right now.  Future modification may require adjustments to previous assumptions.  That, however, is a problem for the future.
In any case, after doing some experimentation, I'm not sure the current version of NIFI-4775 is the correct approach.  And whatever the eventual approach is, it may more appropriately be a new implementation (as discussed above).  I don't think we should put off correcting current bugs because they may complicate potential future features.

The proposed solution does address the issue that was raised in NIFI-4774, but in doing so introduces a new issue of data loss. This is why I provided the solution that I did in the PR, as I believe that it addresses both of these issues.
Again, I do not have a problem with making this new solution one that the user is able to opt out of, though. If you want to submit a PR that also incorporates your proposed solution into the MinimalLockingWirteAheadLog that is okay too and we can also review and incorporate that change as well.

Again, I would submit that it isn't violating the data loss guarantees of the original implementation.  Yes, some data could potentially be lost, but none that it guaranteed to keep, and in doing so it prevents corruption... in a handful of easily understandable lines, that don't fundamentally alter the implementation.
I want to be clear... I'm in no way opposed to improvements.  However, for operational data flows there is going to be some trepidation about large changes to such a key component... especially one that we've had previous issues with.  The smaller / more incremental the changes, and the more time allowed for evaluation under load, the more comfortable I would imagine people would be.


Pin Helm versions to docs version

Description
We should ensure that the helm installation instructions also specify the correct version of the chart that corresponds to the currently browsed version of the docs (like we do for kumactl install commands).

I found old kuma website deployment and the helm instructions did not have a version pinned - https://deploy-preview-1013--kuma.netlify.app/docs/1.6.x/installation/helm/#run-kuma. We did pinning in 1.4 - https://kuma.io/docs/1.4.x/installation/helm/.  So I guess we just stopped after 1.4, nothing to do with the docs migration.

Triage: still relevant. For example here https://kuma.io/docs/2.5.x/production/cp-deployment/stand-alone/ we should add --version to pick proper helm chart version (that is equal to kuma version)


Getting lots of non useful messages

Just installed it, quite nice! I'm trying it coupled with vim-android and YCM.
One thing that's annoying me a bit is that it's generating non-useful messages like creating socket and Cannot open file "/Users/francisco/.vim/plugged/vim-javacomplete2/libs/javavi/target/classes/*.java", even though the completion is being functional these messages keep getting showing up. What about providing a silence mode or removing them?

Agreed. Will work on it.

Please, can you pull last commits and try again. Is there anything unnecessary?

Thanks! I'll check asap when I get back home late night.

Thanks!


Fixed handling of Motion and Key events in GVRActivity

Forward un handled events from the GVRInputManager to the
VRActivity.
GearVRf-DCO-1.0-Signed-off-by: Rahul Rudradevan
<EMAIL_ADDRESS>

Works as expected


Executed dart2native report error error: import of dart:mirrors is not supported in the current Dart runtime

import 'package:mustache/mustache.dart' as mustache;
import 'file_system.dart';

void renderTemplate(String absoluteSourcePath, String finalDestinationPath,
    Map<String, dynamic> context) {
  final sourceFile = fs.file(absoluteSourcePath);
  final templateContents = sourceFile.readAsStringSync();
  final renderedContents =
      mustache.Template(templateContents).renderString(context);

  final finalDestinationFile = fs.file(finalDestinationPath);
  finalDestinationFile.writeAsStringSync(renderedContents);
}

remove mustache import , dart2native can output the bin

The library has a hard dependency on dart:mirrors at the moment. This means it's not possible to use with dart2native.
Should be pretty easy for someone to implement a patch.
See:
https://github.com/xxgreg/mustache/issues/19#issuecomment-562525727

I ran into exactly the same thing trying to do dart2native on dart-sitegen which had a dependency on this package and can confirm that changing over to reflected-mustache fork allows dart2native to compile.


Responsive Image Gallery

I've been working on a responsive (mobile friendly) layout for Stacey and the image gallery has me totally stumped. I don't know JavaScript very well. I have managed to figure out that the problem I am having is related to the divs image-wrapper and image-holder. Single images work perfectly with what I currently have but multiple images in a project folder that invoke the image gallery just run off of the page when re-sizing.
Thanks

@pbatts could you elaborate please?

For a single image I can use CSS to resize the image with the size of the window with:
    img {
        max-width: 100%;
        height: auto;
    }

But no matter how I apply that same style to #image-wrapper and #image-holder it doesn't work on a project with more than one image. When the window is resized (smaller) the image overflows off of the page.

could you show an example of this?

try this, if i understant you correctly:

	<meta charset="utf-8">
	<title>Title</title>

		Header

			Main

		Footer

oh, are you using id's on more than one element?
"...But no matter how I apply that same style to #image-wrapper and #image-holder it doesn't work...".
If this is the case, use classes not id's.

Thanks for the input @o-l-e. I appreciate you taking a look at this.
I apologize for not explaining myself better.
The problem I am having is specific to the Stacey core. Whenever a project directory contains more than one image the js gallery is automatically invoked. If there is only one image in the project directory, no gallery.
Responsive scaling of the images works perfectly for a project with a single image but does not work for a project with multiple images.
I hope that makes better sense.
Here is an example of a page with a single image. http://guitdev.com/Stacey Image Test/
Here is an example of a page with the image gallery. http://guitdev.com/Stacey Image Test/project-name-3/
Thanks again.

I think i know what you are saying now. But (and with all respect to the default gallery in stacey), i would use a different slider plugin if where you. The default gallery in stacey is not really made for responsive images i think, so maybe you should try some other?
A few good sliders would be:
http://dimsemenov.com/plugins/royal-slider/ (not free, but very robust)
http://kenwheeler.github.io/slick/ (have not tried this yet, but looks good)
http://responsiveslides.com (very simple and light, have tried it)
http://flickity.metafizzy.co (have not tried this yet, but looks brilliant)
There are many others out there, but if you are simply looking to make the stacey gallery responsive(and no swiping or video etc) i would try the ResponsiveSlides plugin. It would do the job.

Yeah, my first thought, after not being able to get it to work, was to go with a different slider/gallery plugin. I really wanted to make this one work. Thanks for the links. I will give them a look.

Let me know how it goes, i would be happy to help, if/when i find the time :)
As i said, if you just want to keep it simple, go for the third one.


zwave are turning off when home-assistant restarts

For example: when the porch light is on and home-assistant restarts, they turn off.
This is likely related to the way home assistant works with zwave2mqtt.

Perhaps there is an 'initial state' that somehow needs to be set
Perhaps there needs to be something set to preserve the last setting (I think this is something you can configure in zwave2mqtt)

This was a simple fix:


Option to use in nodejs environment (without window)

highlight.js can be used on server side to change code tags
line-numbers plugin depends on window
https://stackoverflow.com/questions/48843806/how-to-use-npm-marked-with-highlightjs

For those who are looking for the functionality of adding lines on the Node.js side can look at the plugin for rehype in my repository, it splits into lines and wraps the content created by rehype-highlight in span.line which in the future you can use to create numbered lines.


sweep: cleanup

Introduce OTHER_VARIANTS, variants that are not part
of the sweep, but used for other testing purposes or
from SWEEP variants.
BoomTile has pathological resource usage when not flattened
regardless of MAX_UNGROUP_SIZE(we have done a sweep to drive
a wooden stake through the heart of the idea that some magic
value of MAX_UNGROUP_SIZE will 'fix' hiearchical synthesis for
megaboom), so non-flattened synthesis is not interesting
to examine in megaboom. Upcoming work in OpenROAD will probably
restore the usefulness of studying hierarchical synthesis
results in OpenROAD since eliminating unused logic after
hierarchical synthesis is known (from naja) to reduce
instances in megaboom by 50%.

@jeffng-or @vvbandeira FYI, some sort of intermittent(?) artifact problem.
[2024-11-17T14:00:58.362Z] [230 / 236] Action results/asap7/BoomTile/base/2_floorplan.odb; 1168s remote-cache, linux-sandbox
[2024-11-17T14:00:58.925Z] WARNING: Remote Cache: 9 errors during bulk transfer:
[2024-11-17T14:00:58.925Z] com.google.devtools.build.lib.remote.http.HttpException: 401 Unauthorized
[2024-11-17T14:00:58.925Z] <?xml version='1.0' encoding='UTF-8'?><Error>AuthenticationRequired<Message>Authentication required.</Message></Error>

@jeffng-or FYI global route still fails, even with flattened synthesis. Because of the (intermittent?) artifact problems, I can't see the global route result.

@maliberty @jeffng-or FYI, with this change, where megaboom is flattened and macro placement is from hierarchical synthesis, I get very little global route congestion, a few hundred instead of 10s of thousands.
I'll try a sweep of layer adjustments to see what that does tomorrow.


Enable squash merging for this repo

Hej @h5bp/html5please,
could someone with admin privileges enable squash merging as described over here:
https://github.com/blog/2141-squash-your-commits
Thanks,
Michael

wasn't me, but it appears to be on:

Thanks to whoever it was :sparkling_heart:


[FEATURE] Disable save button until changes are made to the profile through forms

Description

Can be done to save hits to the api till changes are made to the profile
Screenshots
No response
Additional information
Other forms should also have this feature

profile form
link form
milestone form
event form

I wanna work on it please assign it to me...

Hi there, I'd really love to work on this issue. Please assign it to me so that I can start working on it as soon as possible.

I wanna work on it please assign it to me...

@akash19coder thank you for your enthusiasm, but as you recently had a PR merged it would be good to give someone else the opportunity to contribute.

Hi there, I'd really love to work on this issue. Please assign it to me so that I can start working on it as soon as possible.

@mianakbarjan I have assigned this to you

Hi Sara! Before I create a PR, I wanted to ask if I should make this change to the other forms too as mentioned in the issue (link, milestone, and event) or just the profile form?

Closing due to accessibility concerns


App upgrade - addition of metric dashboard to Tomcat app. Fix for Memcached OTel doc.

Purpose of this pull request
This pull request adds metric dashboard to Tomcat app. Fix for Memcached OTel doc.
Select the type of change

[ ] Minor Changes - Typos, formatting, slight revisions
[X] Update Content - Revisions, updating sections
[ ] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Ticket (if applicable)

@kimsauce - could you please review.

@sumoanema, can this PR be merged now, or does it need to wait for a feature release?


Make Date conform to MultipartConvertible

This brings parity between JSON and Form encoding and decoding of dates by using ISO8601 for multipart instead of epoch time and doubles

Should we make a way to opt out of this? I think ISO 8601 is the right default and what should have been happening here in the first place, but this could be a breaking change for people.

(IIRC, ISO8601DateFormatter wasn't available in swift-corelibs-foundation until after Multipart 2.0 was released)

@grundoon the tests pass on the Linux Swift 4.1 image so we should be good (since that's the lowest version Vapor 3 supports) right?

@tanner0101 We could do, though not sure how. There's no way to pass in any kind of configuration to the MultipartPartConvertible functions - any ideas?

@0xTim Oh yeah, I think that's all fine – really just an observation as to why it probably wasn't done that way from the start. I recall it being one of the very first lack-of-parity annoyances I ran into when first delving into SSS/Vapor

We could do, though not sure how. There's no way to pass in any kind of configuration to the MultipartPartConvertible functions - any ideas?

I was imagining a static config var. Something like:
import Multipart

Multipart.useISO8601ForDates = true

@tanner0101 Added the config var to Date since that's the only place I could put it for now (can't add it to the module directly and can't add it to MultipartConvertible since that's a protocol)


[BUG]WAF is no longer linked to the user pool

Describe the bug
When I deployed it to Oregon using CDK, the waf was not linked to the user pool, so it did not work.
No manual changes are made.
A clear and concise description of what the bug is.

Please do not ignore issue template. If still the problem exists, please create another PR.


How to use data tracker in third-party ui node

Hi guys,
Perhaps a stupid question, but I am not sure how I can use the data tracker in a third-party ui node vue file.
Because the standard ui nodes do it like this:
import { useDataTracker } from '../data-tracker.mjs'

setup (props) {
   useDataTracker(props.id)
}

Not sure whether I should include somehow the data-tracker.mjs into my own Vite build.
Or can I use the one that is already available in the dashboard somehow?
Thanks!
Bart

Unfortunately, it's not possible currently. Hence we have to build the trackers, etc. manually in a third-party node.
@cstns may have some ideas on how we could do this though?

From the top of my head we could expose the composable. I'd need to give it a go and play with this idea but it might work

Hey guys,
Thanks for considering to add it!!
It would be nice if all the nodes would have a bit of similar implementation, to allow developers to find their way more easily...

Can someone point me to where I can find out what the datatracker is, in case I might want to use it?

https://dashboard.flowfuse.com/contributing/widgets/core-widgets.html#data-tracker


Openpilot not working with carla, no response when keys are pressed

OS: Ubuntu 18.04
Followed the procedure given at tools/sim/README.md
Carla is getting started with no error.
After running manager.py i get following error but it continues running.
loggerd and modeld are shown in red whereas rest are in green.
./_modeld: error while loading shared libraries: libSNPE.so: cannot open shared object file: No such file or directory
loggerd: selfdrive/loggerd/loggerd.cc:631: int main(int, char **): Assertion `err == 0' failed.

After running bridge.py from sim, when i press 1, in manager.py terminal i get
{"event": "alert_add", "alert_type": "commIssueNoEntry", "enabled": false, "ctx": {"dongle_id": "e8c37a13d6b5c170", "version": "0.7.5", "dirty": true, "is_eon": true}}

Looks like the model is still running with the SNPE API (should use the tensorflow runner on PC) which throws an error and prevents op from engaging. Have you tried rebuliding openpilot?

Closing this issue. Feel free to open a new issue if you still have issues.

i have tried rebuilding open pilot and it is still giving me the above error


P100 Failed to verify server hash

Describe The Bug
I connected using the P100 product and the corresponding plug-in, but 2 out of 3 are not connected.
deviceInfo Error: Failed to verify server hash
at KlapAPI.firstHandshake (/volume2/homebridge/node_modules/homebridge-tp-link-tapo/src/api/KlapAPI.ts:196:11)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at /volume2/homebridge/node_modules/homebridge-tp-link-tapo/src/api/KlapAPI.ts:109:51
Expected behavior
Must be properly connected to homebridge
Logs
[6/1/2024, 9:50:36 PM] [TPLink Tapo] Error sending command: deviceInfo Error: Failed to verify server hash
at KlapAPI.firstHandshake (/volume2/homebridge/node_modules/homebridge-tp-link-tapo/src/api/KlapAPI.ts:196:11)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at /volume2/homebridge/node_modules/homebridge-tp-link-tapo/src/api/KlapAPI.ts:109:51
[6/1/2024, 9:50:36 PM] [TPLink Tapo] Failed to get info about: <IP_ADDRESS>
[6/1/2024, 9:50:36 PM] [TPLink Tapo] Retry to connect in 10s : <IP_ADDRESS>
[6/1/2024, 9:50:36 PM] [TPLink Tapo] Error sending command: deviceInfo Error: Failed to verify server hash
at KlapAPI.firstHandshake (/volume2/homebridge/node_modules/homebridge-tp-link-tapo/src/api/KlapAPI.ts:196:11)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at /volume2/homebridge/node_modules/homebridge-tp-link-tapo/src/api/KlapAPI.ts:109:51
[6/1/2024, 9:50:36 PM] [TPLink Tapo] Failed to get info about: <IP_ADDRESS>
[6/1/2024, 9:50:36 PM] [TPLink Tapo] Retry to connect in 10s : <IP_ADDRESS>
[6/1/2024, 9:50:36 PM] [TPLink Tapo] Adding new accessory: 휴대등충전기
[휴대등충전기@@Contact Sensor State] Characteristic not in required or optional characteristic section for service Outlet. Adding anyway.
[6/1/2024, 9:50:36 PM] [TPLink Tapo] Command error: getCurrentPower > -1002
Plugin Config
{
"addresses": [
"<IP_ADDRESS>",
"<IP_ADDRESS>",
"<IP_ADDRESS>"
],
"name": "TPLink Tapo",
"email": "-",
"password": "-",
"platform": "HomebridgeTPLinkTapo"
}
Plugin Version
4.1.0
Homebridge Version
3.1.1 (homebridge: 1.8.2, homebridge ui: 4.56.2)
Node.js Version
20.9.0
NPM Version
10.2.3
Operating System
Synology DSM

I am having the same issue on a Raspberry Pi under Docker: one P100 out of my five devices (3 P100s and 2 bulbs) is connecting, the other four are giving the same error as in the original.
This also confirms behaviour I’ve been experiencing in Home Assistant: the exact same P100 is working while the others are not.

Same Problem here with the P110. Two devices are working and the other two not.

Same issue here. Tried resetting Tapo password, resetting and re-adding devices, etc, to no avail.

Same issue here. Tried resetting Tapo password, resetting and re-adding devices to no avail. I was previosly running HomeBridge on it's own Raspberry Pi and it was working fine. I moved HomeBridge into Docker so I could run both HomeBridge and HomeAssistant on the same Pi and it hasn't worked since then. Seems to be something related to communicating out of the Docker environment?

@nzscoff I am running HomeBridge on a Rasperry Pi without Docker. So I don't think that this is the problem.

I can confirm this issue. I am trying to run it on a Rasperry Pi with Ubuntu 24.04 inside Docker.

Exact same issue running homebridge on Raspberry Pi. Please help us.

+1 here
both for P100 and the Light Strip L900


Update to Svelte 4

svelte-vega seems to work with Svelte 4. This PR is to make npm happy.
#858

The CI errors with Cannot find module 'prettier-plugin-svelte'

There was a linting error.

Whoops - forgot to commit them.


Slow compilation of RQSpline flow operations

Currently the training and sampling phases takes around 3.5 minutes on a A100 node with icelake CPU for RQSpline model with 10 layers, [128,128] conditioners.
See whether swapping make_flow with a scan can solve this compilation problem. This could very well be issue associated with how distrax form the bijector, in that case, there won't be much I can do.

Distrax is now deprecated, solved in #123


Accessing sub schema members

Hi, I'm using SimpleSchema with Autoform and can't quite figure out what I'm doing wrong in relation to using a subschema
I basically have
Address = new SimpleSchema()
X = new SimpleSchema()
XWithAddress = new SimpleSchema([X,{address:{type:Address}}]);
in a quickForm using XWithAddress as its schema the following doesn't work
{{> afQuickField name="address.line1" }}
nor does
{{> afObjectField name="address"}}

Please shared a github repo or meteorpad.

To help me catch up, I'm closing some old issues. If you still need help, post a comment asking to reopen.


resynchronization process fails with determined values of SQN

Some values of SQN from UE does not synchronize in UDM and this results in authentication of failure. For example, test set 4, test set 18 and test set 19 based on 3GPP TS 35.208 version 15.0.0 Release 15.

Thanks for the PR!


[BUG] Simple Calendar no longer will allow settings to be saved or calendar modified in latest v10 update

Modifications to calendar settings no longer can be saved. Clicking the 'save' button does nothing. The import function is also broken; it gives an error message that a properly exported json file is not a Simple Calendar json.
I tried this in a new world with no mods using the PF2e system and the issue continued. I'm on the most recent v10 build of Foundry as of posting, v10 build 288.

Which version of simple calendar are you running?
I don't think you are on the latest version of simple calendar.
The version should be 2.1.27
If you are on 1.3.75 you will have to uninstall and reinstall the module. Uninstalling a module doesn't delete any data so it's safe to do that.


Not able to run "autoreconf"

Per tutorial, got the following errors to run "autoreconf" to prep for build.
autoreconf -i -v
autoreconf: Entering directory .' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal -I m4 ${ACLOCAL_FLAGS} autoreconf: configure.ac: tracing autoreconf: configure.ac: not using Libtool autoreconf: running: /usr/bin/autoconf autoreconf: running: /usr/bin/autoheader autoreconf: running: automake --add-missing --copy --no-force Makefile.am:38: Libtool library used but LIBTOOL' is undefined
Makefile.am:38:   The usual way to define LIBTOOL' is to add AC_PROG_LIBTOOL'
Makefile.am:38:   to configure.ac' and run aclocal' and autoconf' again. Makefile.am:38:   If AC_PROG_LIBTOOL' is in `configure.ac', make sure
Makefile.am:38:   its definition is in aclocal's search path.
autoreconf: automake failed with exit status: 1
Please advise what can be missing.
By the way, build tools autoconf, automake, and libtool have the following versions on debian.
autoconf, 2.67-2, 	automatic configure script builder
automake, 1:1.11.1-1,  A tool for generating GNU Standards-compliant Makefiles
libltdl7, 2.2.6b-2,	A system independent dlopen wrapper for GNU libtool
It looks like that on my debian, I have libltdl7 instead of "libtool". Does it have to be exact?

My first instinct would be to say that the "libtool" package is not installed.  On my Debian box, the package can be installed with:
aptitude install libtool

If you're building everything from scratch, the following line should get you the packages you need:
aptitude install libbsd-dev libgoogle-glog-dev pkg-config autotools-dev python-dev automake autoconf libtool make g++

You'll have to manually install CityHash (or use libcityhash-dev from our Debian repo).
If this does not work, can you please attach config.log?

Thanks Robert for more detail instruction to install dev and build tools. It seems that libtool is in place. I also installed CityHash by hand. "autoreconf -i" works for me now.
However, I had a problem to prep for make when running "configure". By the way, I obtained source from github directly. How to fix this problem?
./configure --prefix=/home/nokia/src/repo/tng/branches/dev/annie/hyperdex/HyperDex
...
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for PO6... no
configure: error: Package requirements (libpo6 >= 0.2) were not met:
No package 'libpo6' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables PO6_CFLAGS
and PO6_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

Also see some errors related to HyperDex in config.log.
196 conftest.c:11:28: error: ac_nonexistent.h: No such file or directory
197 configure:7270: $? = 1
198 configure: failed program was:
199 | /* confdefs.h /
200 | #define PACKAGE_NAME "HyperDex"
201 | #define PACKAGE_TARNAME "hyperdex"
202 | #define PACKAGE_VERSION "0.1.dev"
203 | #define PACKAGE_STRING "HyperDex 0.1.dev"
204 | #define PACKAGE_BUGREPORT<EMAIL_ADDRESS>205 | #define PACKAGE_URL ""
206 | #define PACKAGE "hyperdex"
207 | #define VERSION "0.1.dev"
208 | / end confdefs.h.  */
209 | #include <ac_nonexistent.h>
210 configure:7295: result: gcc -E
211 configure:7315: gcc -E  conftest.c
212 configure:7315: $? = 0
213 configure:7329: gcc -E  conftest.c
214 conftest.c:11:28: error: ac_nonexistent.h: No such file or directory
215 configure:7329: $? = 1

Errors about "libpo6" in config.log:
511 configure:16097: checking pkg-config is at least version 0.9.0
512 configure:16100: result: yes
513 configure:16110: checking for PO6
514 configure:16117: $PKG_CONFIG --exists --print-errors "libpo6 >= 0.2"
515 Package libpo6 was not found in the pkg-config search path.
516 Perhaps you should add the directory containing libpo6.pc' 517 to the PKG_CONFIG_PATH environment variable 518 No package 'libpo6' found 519 configure:16120: $? = 1 520 configure:16133: $PKG_CONFIG --exists --print-errors "libpo6 >= 0.2" 521 Package libpo6 was not found in the pkg-config search path. 522 Perhaps you should add the directory containing libpo6.pc'
523 to the PKG_CONFIG_PATH environment variable
524 No package 'libpo6' found
525 configure:16136: $? = 1
526 configure:16149: result: no
527 No package 'libpo6' found
528 configure:16165: error: Package requirements (libpo6 >= 0.2) were not met:
529
530 No package 'libpo6' found
531
532 Consider adjusting the PKG_CONFIG_PATH environment variable if you
533 installed software in a non-standard prefix.
534
535 Alternatively, you may set the environment variables PO6_CFLAGS
536 and PO6_LIBS to avoid the need to call pkg-config.
537 See the pkg-config man page for more details.

You'll need to install "po6" and "e" from the other repos I have on GitHub before configure will complete successfully.
It is safe to ignore "ac_nonexistent.h" as it is intentionally non-existent.  Autoconf uses this to check what warning or error is issued by the compiler for non-existent headers.

I noted 4 dependencies for HyperDex. Two from Google for "CityHash" and "Glog", and two from cornell for "po06" and "e". I followed instructions and had all 4 pieces of software in place in addition to "HyperDex" code base.
But I still got the above configuration err. Would u pls help?
Details:
A) Downloaded from github repo.
$ git clone git://git.hyperdex.org/po6.git
$ git clone git://git.hyperdex.org/e.git
B) po6 and e are in place
nokia@vm01:~/src/repo/tng/branches/dev/annie/hyperdex/HyperDex$ ls po6
config.h.in configure.ac  include  libpo6-0.2.dev.pc.in libpo6.pc.in  LICENSE  m4  Makefile.am  README  test

I looked to help for "configure". The following flags seem to be related to "po6" and "e".
How to use these flags?
By the way, why does not "autogen.sh" in HyperDex work? How to validate 4 dependencies are installed correctly to pursue for configuration, then make ...
PO6_CFLAGS  C compiler flags for PO6, overriding pkg-config
PO6_LIBS    linker flags for PO6, overriding pkg-config
E_CFLAGS    C compiler flags for E, overriding pkg-config
E_LIBS      linker flags for E, overriding pkg-config

You'll need to run:
./configure
make
sudo make install

for each of po6 and e (in that order).  It looks like you've only cloned the repos and not fully installed them.

Thanks for response.
But there is no "configure" for "po6" or "e" from repo.

Able to create "configure" for "po6" and "e". But, the result for "make install" looks as following.
What else can be missing?
../po6# make install
Making install in include
make[1]: Entering directory /scratchbox/users/nokia/home/nokia/src/repo/tng/branches/dev/annie/hyperdex/po6/include' make[2]: Entering directory /scratchbox/users/nokia/home/nokia/src/repo/tng/branches/dev/annie/hyperdex/po6/include'
make[2]: Nothing to be done for install-exec-am'. test -z "/usr/local/include" || /bin/mkdir -p "/usr/local/include" /bin/mkdir -p '/usr/local/include/po6'  /usr/bin/install -c -m 644  po6/error.h po6/noncopyable.h po6/pathname.h '/usr/local/include/po6' /bin/mkdir -p '/usr/local/include/po6/net'  /usr/bin/install -c -m 644  po6/net/ipaddr.h po6/net/location.h po6/net/socket.h '/usr/local/include/po6/net' /bin/mkdir -p '/usr/local/include/po6/io'  /usr/bin/install -c -m 644  po6/io/fd.h '/usr/local/include/po6/io' /bin/mkdir -p '/usr/local/include/po6/threads'  /usr/bin/install -c -m 644  po6/threads/rwlock.h po6/threads/cond.h po6/threads/spinlock.h po6/threads/thread.h po6/threads/mutex.h po6/threads/barrier.h '/usr/local/include/po6/threads' make[2]: Leaving directory /scratchbox/users/nokia/home/nokia/src/repo/tng/branches/dev/annie/hyperdex/po6/include'
make[1]: Leaving directory /scratchbox/users/nokia/home/nokia/src/repo/tng/branches/dev/annie/hyperdex/po6/include' Making install in test make[1]: Entering directory /scratchbox/users/nokia/home/nokia/src/repo/tng/branches/dev/annie/hyperdex/po6/test'
make[2]: Entering directory /scratchbox/users/nokia/home/nokia/src/repo/tng/branches/dev/annie/hyperdex/po6/test' make[2]: Nothing to be done for install-exec-am'.
make[2]: Nothing to be done for install-data-am'. make[2]: Leaving directory /scratchbox/users/nokia/home/nokia/src/repo/tng/branches/dev/annie/hyperdex/po6/test'
make[1]: Leaving directory /scratchbox/users/nokia/home/nokia/src/repo/tng/branches/dev/annie/hyperdex/po6/test' make[1]: Entering directory /scratchbox/users/nokia/home/nokia/src/repo/tng/branches/dev/annie/hyperdex/po6'
make[2]: Entering directory /scratchbox/users/nokia/home/nokia/src/repo/tng/branches/dev/annie/hyperdex/po6' make[2]: Nothing to be done for install-exec-am'.
test -z "/usr/local/lib/pkgconfig" || /bin/mkdir -p "/usr/local/lib/pkgconfig"
/usr/bin/install -c -m 644 libpo6-0.2.dev.pc '/usr/local/lib/pkgconfig'
make[2]: Leaving directory /scratchbox/users/nokia/home/nokia/src/repo/tng/branches/dev/annie/hyperdex/po6' make[1]: Leaving directory /scratchbox/users/nokia/home/nokia/src/repo/tng/branches/dev/annie/hyperdex/po6'

able to install "po6" and "e".
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for PO6... yes
checking for E... yes
But got err when running "configure" to generate "make" file ..
./configure: line 16855: syntax error near unexpected token >' ./configure: line 16855:     AC_PYTHON_DEVEL(>= 2.6)'

mark as a dup for #10.


localconfig connector support for gemfire

hello,
i recently experimented with working with gemfire on pivotal cloud foundry, so this project was useful.  this pull request enables local development with the same code via the spring cloud localconfig connector.  that connector does not explicitly support gemfire.  this pull request adds it.
thanks,
/ eitan

@mkenyon @awmartin

@pulkitpivotal ?

Thanks Eitan for the pull request. I will review.

@eitansuez Looks pretty good, would you mind please adding a sample configuration in the README. E.g. if you can paste example properties which define the gemfire://<IP>.

check out the updated readme.  let me know if that works for you.  worse case, you can merge the pull request and edit the readme afterwards.  thanks! / eitan

clarification:  the readme i'm referring to is the one in the subfolder spring-cloud-gemfire-localconfig-connector


bug: Wasm32 compilation issues on 1.0.0

Description & observations
Issue has appeared when we switched from cw-storage-plus 0.16.0 to cw-storage-plus 1.0.0.
Main difference in dependencies that I have spotted is the addition of k256 which depends on rand_core, thus getrandom.
Building with cw-storage-plus 0.16.0 continues to work flawlessly, so in case anyone else encounters this, just revert back.
Reproduction
Prerequisites

Cargo.toml

[package]
name = "bug"
version = "0.1.0"
edition = "2021"

[dependencies]
cw-storage-plus = "1.0.0"

src/lib.rs

/* Empty */

Steps to reproduce
Build command: cargo build --target wasm32-unknown-unknown
Error
   Compiling getrandom v0.2.8
error: the wasm32-unknown-unknown target is not supported by default, you may need to enable the "js" feature. For more information see: https://docs.rs/getrandom/#webassembly-support
   --> /home/kiril/.cargo/registry/src/github.com-1ecc6299db9ec823/getrandom-0.2.8/src/lib.rs:263:9
    |
263 | /         compile_error!("the wasm32-unknown-unknown target is not supported by \
264 | |                         default, you may need to enable the \"js\" feature. \
265 | |                         For more information see: \
266 | |                         https://docs.rs/getrandom/#webassembly-support");
    | |________________________________________________________________________^

error[E0433]: failed to resolve: use of undeclared crate or module `imp`
   --> /home/kiril/.cargo/registry/src/github.com-1ecc6299db9ec823/getrandom-0.2.8/src/lib.rs:290:5
    |
290 |     imp::getrandom_inner(dest)
    |     ^^^ use of undeclared crate or module `imp`

For more information about this error, try `rustc --explain E0433`.
error: could not compile `getrandom` due to 2 previous errors

Apologies.
Duplicate of #19.

Reopening as solution from #19 to add "resolver = 2" doesn't solve problem.
I'd like to stress on the fact that, even with #20 removing it explicitly from this crate, it gets pulled by k256.