Zigbee2mqtt ui page keeps loading

Hello, I have a problem with loading the interface on domoticz.
My plugin is in version 3.0.0
My Domoticz version
Version: 2021.1 (build 13360)
Build Hash: eee333c30
Compile Date: 2021-07-04 11:58:11
dzVents Version: 3.1.8
Python Version: 3.8.6 (default, Sep 25 2020, 09:36:53) [GCC 10.2.0]
I get stuck on loading, is there a solution?

Hi,
I have the same issue. Plugin 3.0.0, Domoticz build 13482. Tried a lot of things:

disable/enable hardware
remove zigbee2mqtt folder and get latest from git
chmod +x of plugin.py

The devices are being created / can be used correctly, but the Custom | Zigbee2mqtt webpage stays on 'Loading'.
Enabled the debug logging, but no error messages of any kind.
Regards,
Marco

Same issue after updating z2m ...
Domoticz V2021.1 (c)2012-2021 GizMoCuz
Status: Build Hash: 8547c5b7e, Date: 2021-04-17 17:29:11
Status: Startup Path: /home/pi/domoticz/
Status: PluginSystem: Started, Python version '3.7.3'.
Plugin version V3.0.1 (recent git pull)
Zigbee2MQTT version : 1.21.0 commit: 70891ee
Coordinator type : zStack3x0
Coordinator revision :20210708
Frontend version : 0.5.18

Thanks for the info !
But instead of downgrading
i ordered a new Pi4 for testing.
(All possible testing is not yet done, but this is what i've done until now )
New Pi 4B :
Installed OS complete new.

Installed Docker and in docker :
- zigbee2mqtt recent version 1.21.0
- node-red (For testing)
- Mosquitto 2.0.11 (most recent)
Plugged in an CC2531   :
Zigbee2mqtt is OK and running.
Installed recent plugin within Domoticz, restarts domoticz
In Domoticz : i did make 2 hardware configuration for zigbee2mqtt :
1 for this new rasp. and 1 for connecting the existing rasp.
After restart domoticz :
Log from existing Pi :   'Received available devices list from bridge'  - OK
Log from new Pi :    'Received available devices list from bridge'  - OK
.
The 'Devices' are loaded up from both (from the existing Pi and from the new Pi) : OK for both!
.
But ....
On the screen   - custom - zigbee2mqtt - i have 2 screens. Nice !
The screen for the new Pi with CC2531 is loading up and working.
The screen for the existing Pi with Slaesh's CC2652RB stick keeps loading....
.
The difference between those 2 is the stick...
And version Mosquitto (New Pi is newer version)

Short next test :
Situation: 1 existing Pi with Slaesh stick (Say Pi1) and a new Pi with CC2531 stick (Say Pi2)
On boths Pi's (same) Domoticz with (same) Z2M plugin.
I've created on both Pi's 2 identical configurations for Z2M : 1 to itself and 1 to the other Pi.
.
Result on both Pi's are identical : !
On Pi1 ( with Slaesh-stick) : Screen from Slaesh keeps loading........ Screen from other Pi2 (CC2531) - OK!
On Pi2 ( with CC2531-stick) : Screen from Pi1 with Slaesh keeps loading..... Screen from Pi2 (CC2531) - OK!
.
(Keeps loading : also no headers or any borders...)
(Meanwhile i've made an temporary workaround with node-red for the important things. Maybe it is possible to compare the MQTT-messages)

Could you please try again with the latest plugin version, I did several improvements to communication protocol and hopefully it'll help with your issue

I still have the same problem.
I have Slaesh's stick.
when I click on zigbee2mqtt in domoticz, in the zigbee log I have "Debug Received MQTT message on 'zigbee2mqtt / bridge / config / permit_join' with data ''
and it stops there. I have nothing else displayed in the logs.

Hi all, same for me, also use Slaesh's stick, and also with latest git pull it still remains in Loading...

Could you please enable Debug mode for plugin and post here you Domoticz log after you open the plugin UI

2021-09-04 18:20:14.021 Zigbee2Mqtt_v3: (Zigbee2Mqtt_v3) [API] Request: [1] bridge_getstatus({}) 2021-09-04 18:20:14.021 Zigbee2Mqtt_v3: (Zigbee2Mqtt_v3) MqttClient::publish zigbee2mqtt/bridge/config/permit_join ()

I'm running clean install of 13491 and 3.1.0-beta. The api_transport device is not created. Could this be an issue? On my production enviroment 13491 with 3.1.0-beta is OK.

since the plugin update I have errors
2021-09-04 18:38:58.017 Error: EventSystem: TEMP_HUM_BARO missing values : ID=396, sValue=19.0;85.21;0 2021-09-04 18:38:58.018 Error: EventSystem: TEMP_HUM_BARO missing values : ID=369, sValue=23.8;67.38;0 2021-09-04 18:38:58.018 Error: EventSystem: TEMP_HUM_BARO missing values : ID=396, sValue=19.0;85.21;0 2021-09-04 18:38:58.020 Error: EventSystem: TEMP_HUM_BARO missing values : ID=369, sValue=23.8;67.38;0 2021-09-04 18:38:58.020 Error: EventSystem: TEMP_HUM_BARO missing values : ID=396, sValue=19.0;85.21;0

I'm afraid of having to do a new zigbee2mqtt install on domoticz

@Eucliwood090, looks like you haven't been using the recent version before, try to just remove these broken devices: 396 and 369
@dobber81, yes, that definitely could be an issue as api_transport device is required for UI to work

Weird, I even did a complete installation when I switched to 3.0

@stas-demydiuk #686 did the trick. After updating from git and restart, gui with devices are shown on my test-setup. Also the new Plugin Configuration.
Tnx!

Hello,
I did see you have made an update ! Great !
I' have run on my test-system   the well now  - git pull
But .... After restart Domoticz, no option    -Custom   -Zigbee2Mqtt -
anymore....
I have next errors in the log : (z2m points to the 'production' Pi with
Slaesh-stick  and z2m points to this test-Pi with CC2531)
2021-09-04 20:46:43.168 Error: z2m: (Zigbee2MQTT) failed to load
'plugin.py', Python Path used was
'/home/pi/domoticz/plugins/zigbee2mqtt/:/usr/lib/python37.zip:/usr/lib/python3.7:/usr/lib/python3.7/lib-dynload:/usr/local/lib/python3.7/dist-packages:/usr/lib/python3/dist-packages:/usr/lib/python3.7/dist-packages'.
2021-09-04 20:46:43.168 Error: z2m: (z2m) Module Import failed, exception:
'ModuleNotFoundError'
2021-09-04 20:46:43.168 Error: z2m: (z2m) Module Import failed: ' Name:
DomoticzEx'
2021-09-04 20:46:43.168 Error: z2m: (z2m) Error Line details not available.
2021-09-04 20:46:43.218 Error: z2m-zelf: (Zigbee2MQTT) failed to load
'plugin.py', Python Path used was
'/home/pi/domoticz/plugins/zigbee2mqtt/:/usr/lib/python37.zip:/usr/lib/python3.7:/usr/lib/python3.7/lib-dynload:/usr/local/lib/python3.7/dist-packages:/usr/lib/python3/dist-packages:/usr/lib/python3.7/dist-packages'.
2021-09-04 20:46:43.218 Error: z2m-zelf: (z2m-zelf) Module Import failed,
exception: 'ModuleNotFoundError'
2021-09-04 20:46:43.218 Error: z2m-zelf: (z2m-zelf) Module Import failed: '
Name: DomoticzEx'
2021-09-04 20:46:43.218 Error: z2m-zelf: (z2m-zelf) Error Line details not
available.
My screen BEFORE the update from z2m-zelf (Test Pi with CC2531)  This with
z2m keeps 'loading'
[image: image.png]
Screen after update with missing Custom :
[image: image.png]
Thanks, Dirk
Op za 4 sep. 2021 om 13:40 schreef Stanislav Demydiuk <
@.***>:

Could you please enable Debug mode for plugin and post here you Domoticz
log after you open the plugin UI
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/stas-demydiuk/domoticz-zigbee2mqtt-plugin/issues/686#issuecomment-912959560,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASF3KGABAD75EJCNLCHV4D3UAIAR5ANCNFSM5CZOFTVQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Groetjes, Dirk Janssens

@Verysimply, as you can see the error is
Module Import failed: ' Name: DomoticzEx'

which means that you are using a Domoticz version that doesn't support DomoticzEx, you need the latest beta to be able to run this version of the plugin

We deviate a bit from the subject but, I have just redone a complete installation and I still have the same concerns
2021-09-04 21:26:21.007 Error: EventSystem: TEMP_HUM_BARO missing values : ID=504, sValue=25.9;55.56;0 2021-09-04 21:26:21.007 Error: EventSystem: TEMP_HUM_BARO missing values : ID=515, sValue=24.6;71.29;0 2021-09-04 21:26:21.007 Error: EventSystem: TEMP_HUM_BARO missing values : ID=524, sValue=22.7;72.99;0 2021-09-04 21:26:21.007 Error: EventSystem: TEMP_HUM_BARO missing values : ID=533, sValue=19.0;85.21;0 2021-09-04 21:26:21.009 Error: EventSystem: TEMP_HUM_BARO missing values : ID=491, sValue=23.8;67.38;0 2021-09-04 21:26:21.010 Error: EventSystem: TEMP_HUM_BARO missing values : ID=504, sValue=25.9;55.56;0 2021-09-04 21:26:21.010 Error: EventSystem: TEMP_HUM_BARO missing values : ID=515, sValue=24.6;71.29;0 2021-09-04 21:26:21.010 Error: EventSystem: TEMP_HUM_BARO missing values : ID=524, sValue=22.7;72.99;0 2021-09-04 21:26:21.010 Error: EventSystem: TEMP_HUM_BARO missing values : ID=533, sValue=19.0;85.21;0 2021-09-04 21:26:21.066 Error: EventSystem: TEMP_HUM_BARO missing values : ID=491, sValue=23.8;67.38;0 2021-09-04 21:26:21.067 Error: EventSystem: TEMP_HUM_BARO missing values : ID=504, sValue=25.9;55.56;0 2021-09-04 21:26:21.067 Error: EventSystem: TEMP_HUM_BARO missing values : ID=515, sValue=24.6;71.29;0 2021-09-04 21:26:21.067 Error: EventSystem: TEMP_HUM_BARO missing values : ID=524, sValue=22.7;72.99;0

Hello,
i've updated domoticz to latest beta-version on my test Pi.
Screen to the plugged in cc2531 is now OK !
But to the Slaesh-stick (on production Pi ( z2m ))  i have the 'loading' screen....
My log :
2021-09-04 21:35:53.791 z2m hardware started.
2021-09-04 21:35:53.791 Status: z2m: (z2m) Started.
2021-09-04 21:35:53.791 Status: z2m: (z2m) Entering work loop.
2021-09-04 21:35:53.791 Status: NotificationSystem: thread started...
2021-09-04 21:35:53.792 Status: EventSystem: reset all events...
2021-09-04 21:35:53.793 Status: EventSystem: reset all device statuses...
2021-09-04 21:35:53.880 Status: Python EventSystem: Initializing event module.
2021-09-04 21:35:53.881 Status: EventSystem: Started
2021-09-04 21:35:53.881 Status: EventSystem: Queue thread started...
2021-09-04 21:35:54.086 z2m: (z2m) Installing plugin custom page...
2021-09-04 21:35:54.105 z2m: (z2m) Installing plugin custom page completed.
2021-09-04 21:35:54.256 z2m: (z2m) Connected to MQTT Server: <IP_ADDRESS>:1883
2021-09-04 21:35:54.357 z2m: (z2m) Zigbee2mqtt bridge is online
2021-09-04 21:35:54.357 z2m: (z2m) Joining new devices is disabled on the zigbee bridge
2021-09-04 21:35:54.361 z2m: (z2m) Received available devices list from bridge
2021-09-04 21:35:54.060 Status: z2m: (z2m) Initialized version 3.1.0-beta
2021-09-04 21:35:54.223 Status: PluginSystem: 1 plugins started.

Hi! I enabled the debug -> Verbose option in the Domotiz|Hardware|Zigbee2mqtt plugin. The starting point is when I press refresh, around 10:52:20.520. The other items are probably some kind of keep-alive-ping.
     Ю

What version of zigbee2mqtt do you have?

1.21.1 (from npm-shrinkwrap.json, hope that is the right way)

2021-09-05 14:00:25.895 Error: EventSystem: in /root/domoticz/dzVents/runtime/dzVents.lua: ...oticz/dzVents/runtime/device-adapters/generic_device.lua:67: attempt to index a nil value (field '')
2021-09-05 14:02:52.900 Error: Zigbee_3.1: (Zigbee_3.1) 'onMessage' failed 'KeyError':'('humidity',)'.
2021-09-05 14:02:52.900 Error: Zigbee_3.1: (Zigbee_3.1) Exception traceback:
2021-09-05 14:02:52.900 Error: Zigbee_3.1: (Zigbee_3.1) ----> Line 301 in '/root/domoticz/plugins/zigbee2mqtt/plugin.py'
2021-09-05 14:02:52.900 Error: Zigbee_3.1: (Zigbee_3.1) ----> Line 135 in '/root/domoticz/plugins/zigbee2mqtt/plugin.py'
2021-09-05 14:02:52.900 Error: Zigbee_3.1: (Zigbee_3.1) ----> Line 167 in '/root/domoticz/plugins/zigbee2mqtt/mqtt.py'
2021-09-05 14:02:52.900 Error: Zigbee_3.1: (Zigbee_3.1) ----> Line 215 in '/root/domoticz/plugins/zigbee2mqtt/plugin.py'
2021-09-05 14:02:52.900 Error: Zigbee_3.1: (Zigbee_3.1) ----> Line 61 in '/root/domoticz/plugins/zigbee2mqtt/devices_manager.py'
2021-09-05 14:02:52.900 Error: Zigbee_3.1: (Zigbee_3.1) ----> Line 64 in '/root/domoticz/plugins/zigbee2mqtt/adapters/base_adapter.py'
2021-09-05 14:02:52.900 Error: Zigbee_3.1: (Zigbee_3.1) ----> Line 179 in '/root/domoticz/plugins/zigbee2mqtt/devices/device.py'
2021-09-05 14:02:52.900 Error: Zigbee_3.1: (Zigbee_3.1) ----> Line 158 in '/root/domoticz/plugins/zigbee2mqtt/devices/device.py'
2021-09-05 14:02:52.900 Error: Zigbee_3.1: (Zigbee_3.1) ----> Line 48 in '/root/domoticz/plugins/zigbee2mqtt/devices/temperature_humidity_sensor.py'
2021-09-05 14:02:52.900 Error: Zigbee_3.1: (Zigbee_3.1) ----> Line 35 in '/root/domoticz/plugins/zigbee2mqtt/devices/temperature_humidity_sensor.py'
2021-09-05 14:02:52.916 Error: Zigbee_3.1: (Zigbee_3.1) 'onMessage' failed 'KeyError':'('pressure',)'.
2021-09-05 14:02:52.916 Error: Zigbee_3.1: (Zigbee_3.1) Exception traceback:
2021-09-05 14:02:52.916 Error: Zigbee_3.1: (Zigbee_3.1) ----> Line 301 in '/root/domoticz/plugins/zigbee2mqtt/plugin.py'
2021-09-05 14:02:52.916 Error: Zigbee_3.1: (Zigbee_3.1) ----> Line 135 in '/root/domoticz/plugins/zigbee2mqtt/plugin.py'
2021-09-05 14:02:52.916 Error: Zigbee_3.1: (Zigbee_3.1) ----> Line 167 in '/root/domoticz/plugins/zigbee2mqtt/mqtt.py'
2021-09-05 14:02:52.916 Error: Zigbee_3.1: (Zigbee_3.1) ----> Line 215 in '/root/domoticz/plugins/zigbee2mqtt/plugin.py'
2021-09-05 14:02:52.916 Error: Zigbee_3.1: (Zigbee_3.1) ----> Line 61 in '/root/domoticz/plugins/zigbee2mqtt/devices_manager.py'
2021-09-05 14:02:52.916 Error: Zigbee_3.1: (Zigbee_3.1) ----> Line 64 in '/root/domoticz/plugins/zigbee2mqtt/adapters/base_adapter.py'
2021-09-05 14:02:52.916 Error: Zigbee_3.1: (Zigbee_3.1) ----> Line 179 in '/root/domoticz/plugins/zigbee2mqtt/devices/device.py'
2021-09-05 14:02:52.916 Error: Zigbee_3.1: (Zigbee_3.1) ----> Line 158 in '/root/domoticz/plugins/zigbee2mqtt/devices/device.py'
2021-09-05 14:02:52.916 Error: Zigbee_3.1: (Zigbee_3.1) ----> Line 25 in '/root/domoticz/plugins/zigbee2mqtt/devices/temperature_humidity_barometer_sensor.py'
2021-09-05 14:02:52.916 Error: Zigbee_3.1: (Zigbee_3.1) ----> Line 18 in '/root/domoticz/plugins/zigbee2mqtt/devices/temperature_humidity_barometer_sensor.py'
2021-09-05 14:02:52.937 Error: EventSystem: in /root/domoticz/dzVents/runtime/dzVents.lua: ...oticz/dzVents/runtime/device-adapters/generic_device.lua:67: attempt to index a nil value (field '')
2021-09-05 14:02:52.995 Error: EventSystem: in /root/domoticz/dzVents/runtime/dzVents.lua: ...oticz/dzVents/runtime/device-adapters/generic_device.lua:67: attempt to index a nil value (field '')
2021-09-05 14:03:09.768 Error: EventSystem: in /root/domoticz/dzVents/runtime/dzVents.lua: ...oticz/dzVents/runtime/device-adapters/generic_device.lua:67: attempt to index a nil value (field '')
2021-09-05 14:11:08.848 Error: EventSystem: in /root/domoticz/dzVents/runtime/dzVents.lua: ...oticz/dzVents/runtime/device-adapters/generic_device.lua:67: attempt to index a nil value (field '')
2021-09-05 14:11:08.913 Error: EventSystem: in /root/domoticz/dzVents/runtime/dzVents.lua: ...oticz/dzVents/runtime/device-adapters/generic_device.lua:67: attempt to index a nil value (field '')
I did a new installation of the plugin

@Eucliwood090, how does it relate to the original issue, does error happen when you open a plugin UI?

unfortunately yes it still does not work ... I am still stuck on loading

Updated Pi1 to zigbee2mqtt version 1.21.0. Same results.
But i see on the loggings in z2m something different between the 2 Pi's :
On Pi1 opening UI-page local, i have this in the logging:
Debug Received MQTT message on 'zigbee2mqtt/bridge/config/permit_join' with data ''
On Pi1 opening UI external page  a lot more response :
Debug Received MQTT message on 'zigbee2mqtt/bridge/config/permit_join' with data ''
Info Zigbee: disabling joining new devices.
Info MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"commit":"eb5750d\n","coordinator":{"meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20190608,"transportrev":2},"type":"zStack12"},"log_level":"debug","network":{"channel":11,"extendedPanID":"0xdddddddddddddddd","panID":7896},"permit_join":false,"version":"1.21.1"}'
Debug Received MQTT message on 'zigbee2mqtt/bridge/config/devices' with data ''
Info MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":[{"dateCode":"20190608","friendly_name":"Coordinator","ieeeAddr":"0x00124b001949bf1b","lastSeen":1631382315822,"networkAddress":0,"softwareBuildID":"zStack12","type":"Coordinator"},{"dateCode":"20191205","description":"Aqara temperature, humidity and pressure sensor","friendly_name":"0x00158d000461fa54","hardwareVersion":30,"ieeeAddr":"0x00158d000461fa54","lastSeen":1630948047386,"manufacturerID":4151,"manufacturerName":"LUMI","model":"WSDCGQ11LM","modelID":"lumi.weather","networkAddress":59198,"powerSource":"Battery","softwareBuildID":"3000-0001","type":"EndDevice","vendor":"Xiaomi"}],"type":"devices"}'
Debug Received MQTT message on 'zigbee2mqtt/bridge/config/groups' with data ''
Info MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":[],"type":"groups"}'
Identical on Pi2
( Pi1 with Slaesh : no response )

Hi! Updated to latest version, but still see 1.21.1 (like my comment above) and still not working. Do I need to do something different to get above (possible) fix?

Found it, needed to do a git pull in domoticz/plugins/zigbee2mqtt too. But unfortunately, still not working.

Is now working ( on the 2 Pi's) !
I tried a lot, but i think, this did the trick:
On the Pi1 with Slaesh's stick :
Removed the zigbee2mqtt 1.21.1 from docker (docker-compose) complete and
installed Z2M 1.21.1 native (not in Docker).
UI in Domoticz on Pi1 and Pi2 is now OK. New ZB-devices are loaded and working in domoticz. (On both Pi's ! )
There must be an fault on my docker(-compose) configuration ...
But, if i start 'touchlink' on z2m, then it 'freezes' and UI's on both domoticz are gone and keeps 'loading'.
After restart z2m the UI's are back good.
I found it is an other known issue from TI .
(Config on both Pi's 4B : Z2M version 1.21.1 , Domoticz Z2M plugin version 0.2.1 (for V3.. is Domoticz BETA needed and on one Pi i'm running stable)),_

I'm using Domoticz 2021.1 build 13497 (BETA) with plugin version 3.1.0-Beta, only get the "loading.." screen.

Found a solution.
You have to enable the Legacy Api option.  Search for the Legacy API checkbox and enable. Restart Zigbee2MQTT.
Or edit the /opt/zigbee2mqtt/data/configuration.yaml and add the line: legacy_api: true

Wonder if someone could check if it gets better with the latest update

I get errors when trying to load devices tab now. Did not happen on my setup before this update.
2021-09-23 22:10:10.291 Error: SQL Query("UPDATE DeviceStatus SET Name='$Zigbee2MQTT API Transport', Description='', Used=1, Type=243, SubType=19, SwitchType=0, nValue=0, sValue='{"type": "response", "requestId": 2, "isError": false, "payload": {"commit": "b558bbdc", "config": {"advanced": {"adapter_concurrent": null, "adapter_delay": null, "availability_blacklist": [], "availability_blocklist": [], "availability_passlist": [], "availability_timeout": 0, "availability_whitelist": [], "cache_state": true, "cache_state_persistent": true, "cache_state_send_on_startup": true, "channel": 11, "elapsed": false, "ext_pan_id": [221, 221, 221, 221, 221, 221, 221, 221], "homeassistant_discovery_topic": "homeassistant", "homeassistant_legacy_entity_attributes": true, "homeassistant_legacy_triggers": false, "homeassistant_status_topic": "hass/status", "ikea_ota_use_test_url": true, "last_seen": "disable", "legacy_api": true, "log_directory": "/opt/zigbee2mqtt/data/log/%TIMESTAMP%", "log_file": "log.txt", "log_level": "info", "log_output": ["console"], "log_rotation": false, "log_symlink_current": false, "log_syslog": {"app_name": "Zigbee2MQTT", "eol": "/n", "host": "localhost", "localhost": "localhost", "path": "/dev/log", "pid": "process.pid", "port": 123, "protocol": "tcp4", "type": "5424"}, "pan_id": 6754, "report": true, "rtscts": false, "soft_reset_timeout": 0, "timestamp_format": "YYYY-MM-DD HH:mm:ss"}, "ban": [], "blocklist": [], "device_options": {}, "devices": {"0x000b57fffe8986bd": {"friendly_name": "Vardagsrum Fram"}, "0x000b57fffe93c9a3": {"friendly_name": "Vardagsrum Uppe"}, "0x000b57fffe952045": {"friendly_name": "Vardagsrum Bak"}, "0x000b57fffe984c19": {"friendly_name": "Trappa"}, "0x000b57fffea50fde": {"friendly_name": "Trappa Fj\u00e4rrkontroll"}, "0x000b57fffeb0c010": {"friendly_name": "Spotlight V\u00e4nster"}, "0x000b57fffeb8fb12": {"friendly_name": "Spotlight H\u00f6ger"}, "0x000b57fffebdc0bd": {"friendly_name": "Spotlight Mitten"}, "0x000d6ffffe21bd2e": {"friendly_name": "Hampus TV-rum"}, "0x000d6ffffec243cf": {"friendly_name": "Larmknapp"}, "0x00124b001ba70858": {"friendly_name": "Vitrinsk\u00e5p"}, "0x00158d000104201f": {"friendly_name": "Mi Cube"}, "0x00158d000184557b": {"friendly_name": "Trust Remote"}, "0x00158d0001a668da": {"friendly_name": "TV Uppe Fj\u00e4rrkontroll"}, "0x00158d000218b7ce": {"friendly_name": "Matrum"}, "0x00158d0003468c75": {"friendly_name": "Aqara Vibration"}, "0x00158d00034ff59d": {"friendly_name": "Vinden"}, "0x00158d000444b431": {"friendly_name": "Garage"}, "0x00158d000444b477": {"friendly_name": "Bottenv\u00e5ning"}, "0x00158d000444b505": {"friendly_name": "Sovrum"}, "0x00158d00045be000": {"friendly_name": "Ute", "temperature_calibration": -0.5}, "0x00158d00052d2cfb": {"friendly_name": "0x00158d00052d2cfb"}, "0x00158d000543c5c3": {"friendly_name": "MCS Ytterd\u00f6rr"}, "0x588e81fffe3e89a2": {"friendly_name": "PIR WC"}, "0x60a423fffe61cfd2": {"friendly_name": "Datarum"}, "0x680ae2fffe71c1ad": {"friendly_name": "\u00d6verv\u00e5ning"}, "0x7cb03eaa0a06a75f": {"friendly_name": "Osram Plug"}, "0x84182600000e4790": {"friendly_name": "Uteplats"}, "0x84182600000eb8f0": {"friendly_name": "TV Uppe"}, "0x84fd27fffecf31b7": {"friendly_name": "Ikea Repeater"}, "0x90fd9ffffe73cfa9": {"friendly_name": "Matbord"}, "0x90fd9ffffed7715a": {"friendly_name": "Matbord Fj\u00e4rrkontroll"}, "0xbc33acfffe1bfcfb": {"friendly_name": "F\u00f6nster \u00d6verv\u00e5ning"}, "0xbc33acfffed8529d": {"friendly_name": "Garagebrytare"}, "0xd0cf5efffee6e587": {"friendly_name": "Spotlights Fj\u00e4rrkontroll"}, "0xec1bbdfffee4dc13": {"friendly_name": "Hampus Sovrum"}}, "experimental": {"new_api": true, "output": "json"}, "external_converters": [], "frontend": {"port": 8880}, "groups": {"3": {"devices": ["0x000b57fffe984c19/1"], "friendly_name": "Trappa_dimmer"}, "321": {"devices": ["0x000b57fffeb8fb12/1", "0x000b57fffebdc0bd/1", "0x000b57fffeb0c010/1"], "friendly_name": "Spotlights_vardagsrum"}, "901": {"devices": ["0x90fd9ffffe73cfa9/1"], "friendly_name": "Matbord_dimmer"}}, "homeassistant": true, "map_options": {"graphviz": {"colors": {"fill": {"coordinator": "#e04e5d", "enddevice": "#fff8ce", "router": "#4ea3e0"}, "font": {"coordinator": "#ffffff", "enddevice": "#000000", "router": "#ffffff"}, "line": {"active": "#009900", "inactive": "#994444"}}}}, "mqtt": {"base_topic": "zigbee2mqtt", "force_disable_retain": false, "include_device_information": false, "server": "mqtt://localhost", "user": "mqtt"}, "ota": {"disable_automatic_update_check": false, "update_check_interval": 1440}, "passlist": [], "permit_join": false, "serial": {"disable_led": false, "port": "/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0"}, "whitelist": []}, "config_schema": {"definitions": {"device": {"properties": {"debounce": {"description": "Debounces messages of this device", "title": "Debounce", "type": "number"}, "debounce_ignore": {"description": "Protects unique payload values of specified payload properties from overriding within debounce time", "examples": ["action"], "items": {"type": "string"}, "title": "Ignore debounce", "type": "array"}, "filtered_attributes": {"description": "Filter attributes from publish payload.", "examples": ["temperature", "battery", "action"], "items": {"type": "string"}, "title": "Filtered publish attributes", "type": "array"}, "filtered_optimistic": {"description": "Filter attributes from optimistic publish payload when calling /set. (This has no effect if optimistic is set to false).", "examples": ["color_mode", "color_temp", "color"], "items": {"type": "string"}, "title": "Filtered optimistic attributes", "type": "array"}, "friendly_name": {"description": "Used in the MQTT topic of a device. By default this is the device ID", "readOnly": true, "title": "Friendly name", "type": "string"}, "icon": {"description": "The user-defined device icon for the frontend. It can be a link to an image (not a path to a file) or base64 encoded data URL like: image/svg+xml;base64,PHN2ZyB3aW....R0aD", "title": "Icon", "type": "string"}, "optimistic": {"default": true, "description": "Publish optimistic state after set", "title": "Optimistic", "type": "boolean"},

DataTables warning: table id=zigbee2mqtt-devices - Requested unknown parameter 'ieeeAddr' for row 0, column 4. For more information about this error, please see http://datatables.net/tn/4
after update ive got this

Looks like the old UI page has been cached, try to clear browser page

I cleared cache and also tried with incognito mode. Same result on 13530. If the "clear browser cache"-question was directed at me.

I got also DataTables warning: table id=zigbee2mqtt-devices - Requested unknown parameter 'ieeeAddr' for row 0, column 4. For more information about this error, please see http://datatables.net/tn/4 just after yesterday update. Legacy API was enabled in the zigbee2mqtt

how to switch back onto commit 1d5f12d ?

@pawol clearing browser cache should help with your issue.
But if you'd like to revert just checkout the required commit i.e.
git checkout 1d5f12d

Hi Stas,
After browse cleanup your the latest beta plugin works ok.
I would like to report bug. I have issue as below:
I have integrated 2 TRVs called TS0601 or Moes HY-368.
I use zigbee2mqtt plugin and Zigbee module CC2652P.
My TRVs supports only integers as setpoint value but In domoticz I can set floats also.
Because floats are not accepted by TRVs, the setpoint is always set to 0 value.
Integers works OK.
How could I modify setpoint in Domoticz to support integers only?
I use the latest Domoticz beta and the latest zigbee2mqtt (koenk) + your the latest zigbe2mqtt domoticz plugin
Rgds
Pawel

Go in your Domoticz to Setup --> Devices, search for the device "api_transport" and set it to used (click the green arrow pointing right). The custom plugin pages will load again.

Wow that's it! Thanks Sammyke!


any ideas in how to integrate with accelerator-core-js

Hi,
What should be your recommend approach to integrate this layout with https://github.com/opentok/accelerator-core-js
Thank you

I'm not very familiar with that project. Are you having issues using it? You should be able to just use it on whatever container you put your subscribers in.


Add support for all SPARQL query types

The rdfpub generator currently only supports SPARQL tuple (SELECT) queries. It should support all other SPARQL query types, including boolean (ASK) and RDF (CONSTRUCT, DESCRIBE) queries. This will require query type detection and appropriate outputs for each query type in the init process, and it will require changes to the render process to handle the new output types.

Closing as duplicate of #6.


Add action-shellcheck to lint shell scripts

Close #17

Shellcheck is a tool which can be executed like any other tool on your local machine or in a CI/CD pipeline.
Here is the Github repository: https://github.com/koalaman/shellcheck
You can run it on your machine or even paste the code into a webpage and get the result from the linter:
https://www.shellcheck.net/

Hey @mstruebing, Thanks for you help.
I ran shell-check locally and fixed lint issues. I have pushed the  changes.
please take a look.
Thanks

@vvkpd Thank you! 👍


Some minor suggestions for improving your README

[+] Replaced emojis with GitHub MarkDown emoji syntax — eg. “:partying_face:” instead of “🥳”
[+] Fixed some grammar/strange ways of saying things — eg. “Question for you”
[+] Fixed link to Food & Wine’s “7-octopus-recipes”
[+] Changed “what is” —> “what’s” (Line 4) — this is because the use of emojis in your README.md implies that you are being informal

Hello @KennyOliver thanks for showing interest
let me make this clear to you, I Built with ❤ on silicon valley(if you don't know watch this video)
I built this when I got bored in 3 hours in that time I didn't think about spellings, anyways I will look into your PRs
Good to see that 15 year old one is doing such a nice stuff

Thanks for your quick reply & time
I didn’t know about silicon valley; it’s actually quite funny!
Crazy that you built an app in 3hrs! I hope to have that skill some day :crossed_fingers:

Don't worry, if you understand the topics and practice daily without fail you can do that with no time :)


[DNM] drivers: i2c: changes to address i2c failure

This PR is not to be merged. This is more of an experimental branch to reduce the i2c errors and print some registers when the errors occur.
Signed-off-by: Rajavardhan Gundi<EMAIL_ADDRESS>

Have also followed Jay's suggestion (first part).

@pabigot Updated the commit as per your suggestion.


FallbackInputHandler executing thogh other GameObject consumes the event

Overview
A FallbackInputHandler's OnInputClicked() is executing thogh other focussed GameObject consumes the event.
Expected Behavior
Any input handlers on the game object are given input events when no modal or focused objects consume the event.
Actual Behavior
Event gets handled by focused object and fallbackInputStack.
Steps to reproduce
Create a scene with HololensCamera, DefaultCursor and InputManager. Add two cubes with scripts implementing IInputClickHandler. Push one of them to fallbackInputStack.
Unity Editor Version
Unity 2017.1.2f1 (64-bit)
Mixed Reality Toolkit Release Version
HoloToolkit-Unity-v1.2017.2.0

Did you use eventData.Use();?

Yes I do, but the somehow the one from fallbackstack gets triggert bevor the focused one. Updated to Unity 2017 2.1f1 and HoloToolkit-Unity-2<IP_ADDRESS>.

Ok. Just took a look into my test setup like described in "Steps to reproduce". Forgot to call eventData.Use(); and it does the trick! So I have to figure out where what's going wrong in my main project... Thanks!

For the record: I found the problem in my project. The GameObject with fallback handler script also uses HandDraggable.cs fom MRTK. I changed InputManager.Instance.PushModalInputHandler(gameObject); to InputManager.Instance.PushModalInputHandler(HostTransform.gameObject); in there what is ok for me because I have set HostTransform to another GameObject and enable/disable HandDraggable somewhere else.
Now everything is working like expected and this should be closed.


Fail softly on task status retrieval failure

Sometimes bad data gets written to zookeeper and the master
cannot deserialize the data. Fail softly by skipping bad
task statuses instead of failing the entire attempt.

@rculbertson

:+1:

Maybe also log stuff? I would also be interested to know how or when this happens. Bad data shouldn't just get written.

@rohansingh We log.debug here https://github.com/spotify/helios/pull/516/files#diff-8d500c531ffb1f7836e9d5b60585a002R850. Should we increase the log level?

Turns out the bad data was being written to disk by an agent, and it would put it back into ZK every time the agent restarted (or reconnected to ZK for some other reason). Still seems like a good PR though...better if 'helios hosts' doesn't break for an entire site because of one agent.

:+1:


Deployment of MulticallV3 to Harmony

Link to blockchain explorer: https://explorer.harmony.one/

Any chance you could send deployment funds to 0x05f32B3cC3888453ff71B01135B34FF8e41263F2? I have not used this chain, so it will take me some time to figure out how to get funds on it. I would guess that $10 of funds should be more than enough and I can refund the excess

Deployed! https://explorer.harmony.one/address/0xca11bde05977b3631167028862be2a173976ca11?activeTab=7

Hi, sorry for missing this update! Thank you very much for the deployment!


.env

Codecov Report

Merging #10 into master will increase coverage by 1.30%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #10      +/-   ##
==========================================
+ Coverage   72.50%   73.80%   +1.30%
==========================================
  Files           7        7
  Lines          40       42       +2
==========================================
+ Hits           29       31       +2
  Misses         11       11

Impacted Files
Coverage Δ

pypro/base/views.py
100.00% <100.00%> (ø)

pypro/settings.py
100.00% <100.00%> (ø)

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 d6d5917...2ec29d4. Read the comment docs.


Error can't locate file for: -lPods-Cargo

When I try to run Cargo Lib I have this error
error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: can't locate file for: -lPods-Cargo

Make sure that you have opened the file  Cargo.xcworkspace and not the project.
Cocoapods needs the workspace to work.


Improve performance of merge_percentiles

As discussed in https://github.com/dask/dask/pull/7162#discussion_r569784138, this PR adds an improvement to merge_percentiles - by using numpy operations rather than merge_sorted. This makes it significantly faster, especially for CuPy arrays:
merge_percentiles timings for NumPy arrays, before and after this PR:

merge_percentiles timings for CuPy arrays, before and after this PR:

Additional info:

This PR depends on #7162 and should not be merged before that one
The script I used to generate the timings:

from dask.array.percentile import merge_percentiles
import numpy as np
import cupy as cp
import timeit

def bench(nquantiles, ndatasets, lib):
    scale = 100
    calculated_quantiles = nquantiles//2

    finalq = lib.floor(lib.random.rand(nquantiles) * scale)
    qs = list(lib.floor(lib.random.rand(ndatasets, calculated_quantiles) * scale))
    vals = list(lib.random.rand(ndatasets, calculated_quantiles))
    Ns = lib.ones(ndatasets) *  100

    dt = 0.
    repeat = 10
    for i in range(repeat):
        t1 = timeit.default_timer()
        merge_percentiles(finalq, qs, vals, Ns=Ns)
        t2 = timeit.default_timer()
        dt += (t2 - t1)
    return (dt) / repeat

import pandas as pd

results = pd.DataFrame(columns=("nquantiles", "ndatasets", "time"))

for nquantiles in (2, 10, 100):
    for ndatasets in (2, 10, 100):
        results.loc[len(results)] = (nquantiles, ndatasets, bench(nquantiles, ndatasets, cp))

results

Apologies for the multitude of commits here - got myself in a bit of a git mess. Should be good now.

No worries we do squash merge here 🙂

It looks like the tests are passing other than the known mac one. There is a fix on master for that, so if you merge or rebase, the tests should all pass.

Looks like Ashwin merged in master. Were there other things we were waiting on here?

Taking silence here to mean no

Thanks Ashwin! 😄
If anything else comes up, please let us know and we can follow up in a new issue/PR as appropriate 🙂


How to make a 64bit build of some cmake project?

I have some cmake project using some 3rd party library (available as a vcpkg package), say zeromq.
I installed the x64 version of it (vcpkg install zeromq:x64-windows), and if I go to build my project, it complains about zeromq not available:
C:\Development\myproject\build> cmake -DCMAKE_TOOLCHAIN_FILE=C:\vcpkg\scripts\buildsystems\vcpkg.cmake ..
-- Building for: Visual Studio 15 2017
-- Selecting Windows SDK version 10.0.17763.0 to target Windows 10.0.14393.
-- The C compiler identification is MSVC 19.16.27024.1
-- The CXX compiler identification is MSVC 19.16.27024.1
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/Hostx86/x86/cl.exe
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/Hostx86/x86/cl.exe -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/Hostx86/x86/cl.exe
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/Hostx86/x86/cl.exe -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
...
CMake Error at C:/vcpkg/scripts/buildsystems/vcpkg.cmake:247 (_find_package):
  Could not find a configuration file for package "ZeroMQ" that is compatible
  with requested version "".

  The following configuration files were considered but not accepted:

    C:/vcpkg/installed/x64-windows/share/zeromq/ZeroMQConfig.cmake, version: 4.3.1 (64bit)

So I tryed to specify the VCPKG_TARGET_TRIPLET, but I get this result:
C:\Development\myproject\build> cmake -DVCPKG_TARGET_TRIPLET=x64-windows -DCMAKE_TOOLCHAIN_FILE=C:\vcpkg\scripts\buildsystems\vcpkg.cmake ..
-- Building for: Visual Studio 15 2017
-- Selecting Windows SDK version 10.0.17763.0 to target Windows 10.0.14393.
-- The C compiler identification is MSVC 19.16.27024.1
-- The CXX compiler identification is MSVC 19.16.27024.1
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/Hostx86/x86/cl.exe
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/Hostx86/x86/cl.exe -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/Hostx86/x86/cl.exe
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/Hostx86/x86/cl.exe -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
...
CMake Error at C:/vcpkg/scripts/buildsystems/vcpkg.cmake:247 (_find_package):
  Could not find a configuration file for package "ZeroMQ" that is compatible
  with requested version "".

  The following configuration files were considered but not accepted:

    C:/vcpkg/installed/x64-windows/share/zeromq/ZeroMQConfig.cmake, version: 4.3.1 (64bit)

What is the proper way to build a project in 64 bit mode via cmake?

Not a vcpkg issue and this is also not stackoverflow.
If you do not now how to use cmake correctly I urge you to read the manual/docs and simply pass the correct generator ( -G "Visual Studio 15 2017 Win64" ) or use the gui of cmake where a list of generators is displayed. Also a search in the web should have answered your question.
So please close this issue.


Changing theme at runtime

Is there a recommended pattern for allowing to change the theme of the dock panel at runtime, i.e. after panels have been created and docked? Currently an InvalidOperationException is thrown, but it seems like this should be allowed, given that VS does allow changing the theme without closing document windows.

The sample project illustrates that.


PointLight2D doesn't work on Tilemap that uses shader if you have an empty light function

Godot version
4.2 Beta 4
System information
Windows 11
Issue description
Hello! I ran into something that I thought was a bit confusing the other day. I wrote a shader for my tilemap and it stopped interacting with my PointLight2D Nodes. I spent quite a while trying to figure it out and then just by chance I noticed that my shader still had the empty light() function that the template creates. When I removed it it started working again.
It would be a nice QOL update to add a comment or something to that template function indicating to people that it is overriding ALL lighting behavior (as opposed to being additive or doing nothing if left empty). I'm sure this is obvious to more experienced developers, but since this is my first shader I only really found it by pure chance as I couldn't find this documented anywhere or in any videos.
Steps to reproduce
Make any shader, leave the light function empty. Observe that Nodes that use that shader no longer interact with light sources.
Minimal reproduction project
N/A

This will be fixed once we merge https://github.com/godotengine/godot/pull/84594

Nice, great to hear it is already taken care of :D


Compiling problems

I am very interested in using wxUiEditor, but as it stands I see that support for wxAui seems to be missing.
I have used both  wxCrafter & wxFormBuilder for some time and both have their strengths and missing features for my needs.
Currently, I need support for Python so I can use wxPython code for OS agnostic utilities.
Which is the best forum to sort out my compiling issues.
FWIW, I am running under Win 11, 64-bit using wxWidgets 3.2.2.
I have installed MSys64 and have installed ninja as well a cmake, but am unsure as to where I need to run the build process.
I am much more familiar with MSVC Visual Studio, but quite understand why you are using MSYS or mingw if you plan on making the app run under Linux or Mac OS.
Unfortunately, the build instructions are too sparse to get me going using either MSys or Mingw
Even the short discussion on the wxWidgets forum did not get me off the ground
https://forums.wxwidgets.org/viewtopic.php?f=10&t=48819&p=209840&hilit=wxuieditor#p209840

There is support for wxAuiNotebook and wxAuiToolbar, but wxUiEditor does not currently support the main AUI manager.
As far as building wxUiEditor, you can use any toolchain supported by CMake. The one requirement is that the C++ compiler must support C++20. You definitely do not need MSYS or Mingw. I haven't personally tried this, but current versions of Visual Studio are supposed to support CMake projects, so you should in theory be able to use the CMakeLists.txt file in the root of the repository and have Visual Studio create a solution from that. If you have cmake-gui.exe installed and in your path, an even faster way is to start a Visual Studio cmd shell, go to the root of the repository and type:
start cmake-gui.exe --preset=ninja-multi -S .

That will configure CMake for you. After that run
cmake --build build --config Release --target wxUiEditor

This will build the executable in build\stage\bin\Release
You might also find the action file .github/workflows/daily_build.yml helpful -- this is how the daily builds are created, which builds with Visual Studio 17 on Windows.
If none of these suggestions get you to the point where you can build, either ask further on this issue, or switch over to the Discussions and create a new topic there. It'll still be mostly me responding, but that will make it a bit easier to find if other people have similar problems getting it to build.

Glad to hear this got resolved for you. I'm going to leave this issue open because I want to look further into getting something in place that makes it possible to build directly in Visual Studio without needing to use a command line.


Dependabot: @adobe/css-tools Regular Expression Denial of Service (ReDOS) while Parsing CSS

Context
Moderate issue depedabot issue in the US-EPA-CAMD/easey-ecmps-ui and US-EPA-CAMD/easey-campd-ui repos
https://github.com/US-EPA-CAMD/easey-campd-ui/security/dependabot/52
Private Zenhub Image

Based on 9/19 Refinment discussion, DPC will work on this dependabot issue. Because this is not a high or severe issue, this is not a high priority item.

Need to debug this issue

This issue seems to be fixed - Justin will add screengrab and verify fix with Jason before closing ticket.

Private Zenhub Image

this has been addressed with dependabot PR being merged into develop for both campd and ecmps. If you look at security tab and go to Dependabot you will see that the issue is no longer listed. We should not be creating tickets for these unless Dependabot is not able to create the PR as this duplicates efforts.


Unescaped ampersand not allowed in HTML attribute

In the use cases document for Web Bluetooth there are anchor tags where the href attribute contains a URL including query parameters. When compiling Bikeshed complains about these with the following error:
LINE 60:81: Character reference '&Q' didn't end in ;.
 ✘  Did not generate, due to fatal errors

Markdown links in the TAG Design Principles are also generating this error, eg.

Character reference '&sort' didn't end in ;.

The Bluetooth use cases document is also failing with this error now.


Update the images to the latest tag in master branch

To have the latest changes in the master branch, tag is updated to latest

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.04%) to 35.455%

Files with Coverage Reduction
New Missed Lines
%

pkg/controller.v1/mpi/mpijob.go
1
91.06%

Totals

Change from base Build<PHONE_NUMBER>:
0.04%

Covered Lines:
4383

Relevant Lines:
12362

💛  - Coveralls


Update parameter validation to use OpenAPI display names

Currently, OpenAPI parameters which do not validate (i.e., have error messages) show the incorrect display name for the parameter:

This PR updates the logic to check if there is a schema associated with the parameter first and, if so, use that schema's title or summary fields to fill in the display name. Otherwise, fall back to the current logic.
Result:

One thing I want to check is how this logic compares to the logic used above the field as well, for consistency.


Switch to Angular

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
Use Angular as a rendering framework, this will allow you to make app.py much simpler, and will allow you to take advantage of the API that you are developing
Describe alternatives you've considered
Stay with how things are.
React 🤮
Additional context
Angular Documentation: https://angular.io/docs
Angular Tutorial: https://angular.io/tutorial
This is somewhat related to https://github.com/WhiteHatCP/thewhitehat.club/issues/22

This suggestion has been implemented with considerations described in the Design Considerations Wiki Page. As such, we will be staying with Flask, but working off of the API routes that have already been made generic in commit 87045e9, which allows for generic page rendering to occur and utilize the data from the API endpoints.
Closed by commit 4d4f55f.


docs(updating): fix typos/punctuation/grammar

I've improved the docs on updating a project by fixing typos, punctuation, grammar, etc.

Codecov Report

Merging #935 (c5144d8) into master (f8ae8d6) will decrease coverage by 0.63%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #935      +/-   ##
==========================================
- Coverage   96.45%   95.82%   -0.63%
==========================================
  Files          41       41
  Lines        3018     3018
==========================================
- Hits         2911     2892      -19
- Misses        107      126      +19

Flag
Coverage Δ

unittests
95.82% <ø> (-0.63%)
:arrow_down:

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

Impacted Files
Coverage Δ

tests/test_tools.py
47.36% <0.00%> (-15.79%)
:arrow_down:

copier/tools.py
86.74% <0.00%> (-6.03%)
:arrow_down:

tests/test_vcs.py
95.31% <0.00%> (-4.69%)
:arrow_down:

tests/conftest.py
90.90% <0.00%> (-4.55%)
:arrow_down:

copier/subproject.py
95.12% <0.00%> (-2.44%)
:arrow_down:

copier/types.py
83.33% <0.00%> (-2.09%)
:arrow_down:

copier/main.py
93.61% <0.00%> (-0.80%)
:arrow_down:

copier/template.py
95.79% <0.00%> (-0.47%)
:arrow_down:

copier/user_data.py
94.06% <0.00%> (-0.46%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Do not panic on private map properties

Good one. Just two questions:

CanInterface actullay panics if IsValid returns false. Shouldn't we use IsValid instead?
In case of CanInterface is actually better than IsValid for our use case, should we use it at the beginning of the method instead of IsValid?

Thanks!

Hi!, thanks for your feedback!
At the point where I inserted the call to CanInterface() we are sure that it's valid, because you check for it at line 45.
I tried to study and experiment with the code a little bit to better understand and address your questions, but I'm a bit worried about the fact that commenting out the checks at lines 19-21 and 45-47 doesn't break any test. Is it because those checks are really superfluous or because we need more tests?...

You are right, CanInterface() is right where you call it. I didn't remember the previous IsValid.
About the check at lines 19-21 and 45-47: I think Mergo should be defensive about its input because it must handle any possible scenario. As you found, I didn't think about private map properties.
So, your PR looks good to me. Don't worry about my questions as I missed the check at 45-47 and they don't make sense anymore.
Merging your PR in one minute.

Thanks!


ISPN-10977 AsciiDoctor/J 2.1.0

https://issues.jboss.org/browse/ISPN-10977
Also fixes the base.version (ISPN-10870)

merged, thanks


[BUG]: bicep.exe not found with AzureCLI@2 when using "az bicep "

Task name
AzureCLI
Task version
2.217.1
Environment type (Please select at least one enviroment where you face this issue)

[ ] Self-Hosted
[X] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
windows-latest
Task log
2023-03-14T07:32:25.2305422Z ##[section]Starting: Azure CLI ACR Push
2023-03-14T07:32:25.2423805Z ==============================================================================
2023-03-14T07:32:25.2424059Z Task         : Azure CLI
2023-03-14T07:32:25.2424178Z Description  : Run Azure CLI commands against an Azure subscription in a PowerShell Core/Shell script when running on Linux agent or PowerShell/PowerShell Core/Batch script when running on Windows agent.
2023-03-14T07:32:25.2424535Z Version      : 2.217.1
2023-03-14T07:32:25.2424667Z Author       : Microsoft Corporation
2023-03-14T07:32:25.2424813Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/deploy/azure-cli
2023-03-14T07:32:25.2425003Z ==============================================================================
2023-03-14T07:32:25.7013583Z [command]C:\Windows\system32\cmd.exe /D /S /C ""C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin\az.cmd" --version"
2023-03-14T07:32:26.6060915Z azure-cli                         2.46.0
2023-03-14T07:32:26.6061566Z
2023-03-14T07:32:26.6061930Z core                              2.46.0
2023-03-14T07:32:26.6062286Z telemetry                          1.0.8
2023-03-14T07:32:26.6062517Z
2023-03-14T07:32:26.6062795Z Extensions:
2023-03-14T07:32:26.6063130Z azure-devops                      0.26.0
2023-03-14T07:32:26.6063348Z
2023-03-14T07:32:26.6063625Z Dependencies:
2023-03-14T07:32:26.6063951Z msal                              1.20.0
2023-03-14T07:32:26.6064302Z azure-mgmt-resource             21.1.0b1
2023-03-14T07:32:26.6064524Z
2023-03-14T07:32:26.6065663Z Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
2023-03-14T07:32:26.6066170Z Extensions directory 'C:\Program Files\Common Files\AzureCliExtensionDirectory'
2023-03-14T07:32:26.6066480Z
2023-03-14T07:32:26.6066927Z Python (Windows) 3.10.10 (tags/v3.10.10:aad5f6a, Feb  7 2023, 17:05:00) [MSC v.1929 32 bit (Intel)]
2023-03-14T07:32:26.6067265Z
2023-03-14T07:32:26.6067615Z Legal docs and information: aka.ms/AzureCliLegal
2023-03-14T07:32:26.6067869Z
2023-03-14T07:32:26.6068059Z
2023-03-14T07:32:26.6068349Z Your CLI is up-to-date.
2023-03-14T07:32:26.6082824Z Setting AZURE_CONFIG_DIR env variable to: D:\a\_temp\.azclitask
2023-03-14T07:32:26.6089012Z Setting active cloud to: AzureCloud
2023-03-14T07:32:26.6284024Z [command]C:\Windows\system32\cmd.exe /D /S /C ""C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin\az.cmd" cloud set -n AzureCloud"
2023-03-14T07:32:27.1806996Z [command]C:\Windows\system32\cmd.exe /D /S /C ""C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin\az.cmd" login --service-principal -u *** "--password=***" --tenant *** --allow-no-subscriptions"
2023-03-14T07:32:28.2697740Z [
2023-03-14T07:32:28.2698294Z   {
2023-03-14T07:32:28.2698624Z     "cloudName": "AzureCloud",
2023-03-14T07:32:28.2699022Z     "homeTenantId": "***",
2023-03-14T07:32:28.2699459Z     "id": "***",
2023-03-14T07:32:28.2699846Z     "isDefault": true,
2023-03-14T07:32:28.2700171Z     "managedByTenants": [],
2023-03-14T07:32:28.2700498Z     "name": "***",
2023-03-14T07:32:28.2700798Z     "state": "Enabled",
2023-03-14T07:32:28.2701172Z     "tenantId": "***",
2023-03-14T07:32:28.2701515Z     "user": {
2023-03-14T07:32:28.2702248Z       "name": "***",
2023-03-14T07:32:28.2702580Z       "type": "servicePrincipal"
2023-03-14T07:32:28.2702875Z     }
2023-03-14T07:32:28.2703142Z   }
2023-03-14T07:32:28.2703391Z ]
2023-03-14T07:32:28.2971097Z [command]C:\Windows\system32\cmd.exe /D /S /C ""C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin\az.cmd" account set --subscription ***"
2023-03-14T07:32:28.8407351Z [command]C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". 'D:\a\_temp\azureclitaskscript1678779145655.ps1'"
2023-03-14T07:32:29.9486048Z ERROR: The command failed with an unexpected error. Here is the traceback:
2023-03-14T07:32:29.9492529Z ERROR: [WinError 2] The system cannot find the file specified
2023-03-14T07:32:29.9492859Z Traceback (most recent call last):
2023-03-14T07:32:29.9493243Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke
2023-03-14T07:32:29.9493759Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 663, in execute
2023-03-14T07:32:29.9494336Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
2023-03-14T07:32:29.9494917Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 697, in _run_job
2023-03-14T07:32:29.9495464Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 333, in __call__
2023-03-14T07:32:29.9496033Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
2023-03-14T07:32:29.9496624Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/resource/custom.py", line 3708, in publish_bicep_file
2023-03-14T07:32:29.9497261Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/resource/_bicep.py", line 193, in bicep_version_greater_than_or_equal_to
2023-03-14T07:32:29.9498065Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/resource/_bicep.py", line 264, in _get_bicep_installed_version
2023-03-14T07:32:29.9498678Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/resource/_bicep.py", line 302, in _run_command
2023-03-14T07:32:29.9499098Z   File "subprocess.py", line 503, in run
2023-03-14T07:32:29.9499388Z   File "subprocess.py", line 971, in __init__
2023-03-14T07:32:29.9499679Z   File "subprocess.py", line 1440, in _execute_child
2023-03-14T07:32:29.9500027Z FileNotFoundError: [WinError 2] The system cannot find the file specified
2023-03-14T07:32:29.9500409Z To check existing issues, please visit: https://github.com/Azure/azure-cli/issues
2023-03-14T07:32:29.9500748Z To open a new issue, please run `az feedback`

<error repeats many times because command is called in a for loop>

2023-03-14T07:33:10.8904309Z ##[error]Script failed with exit code: 1
2023-03-14T07:33:10.9054423Z [command]C:\Windows\system32\cmd.exe /D /S /C ""C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin\az.cmd" account clear"
2023-03-14T07:33:11.5753862Z ##[section]Finishing: Azure CLI ACR Push

Relevant log output
2023-03-14T07:32:28.8407351Z [command]C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". 'D:\a\_temp\azureclitaskscript1678779145655.ps1'"
2023-03-14T07:32:29.9486048Z ERROR: The command failed with an unexpected error. Here is the traceback:
2023-03-14T07:32:29.9492529Z ERROR: [WinError 2] The system cannot find the file specified
2023-03-14T07:32:29.9492859Z Traceback (most recent call last):
2023-03-14T07:32:29.9493243Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke
2023-03-14T07:32:29.9493759Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 663, in execute
2023-03-14T07:32:29.9494336Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
2023-03-14T07:32:29.9494917Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 697, in _run_job
2023-03-14T07:32:29.9495464Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 333, in __call__
2023-03-14T07:32:29.9496033Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
2023-03-14T07:32:29.9496624Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/resource/custom.py", line 3708, in publish_bicep_file
2023-03-14T07:32:29.9497261Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/resource/_bicep.py", line 193, in bicep_version_greater_than_or_equal_to
2023-03-14T07:32:29.9498065Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/resource/_bicep.py", line 264, in _get_bicep_installed_version
2023-03-14T07:32:29.9498678Z   File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/resource/_bicep.py", line 302, in _run_command
2023-03-14T07:32:29.9499098Z   File "subprocess.py", line 503, in run
2023-03-14T07:32:29.9499388Z   File "subprocess.py", line 971, in __init__
2023-03-14T07:32:29.9499679Z   File "subprocess.py", line 1440, in _execute_child
2023-03-14T07:32:29.9500027Z FileNotFoundError: [WinError 2] The system cannot find the file specified
2023-03-14T07:32:29.9500409Z To check existing issues, please visit: https://github.com/Azure/azure-cli/issues
2023-03-14T07:32:29.9500748Z To open a new issue, please run `az feedback`

Aditional info
The command that fails is "az bicep publish". I already looked at the source code of AzureCLI and the problem is that it expects bicep.exe in <AZURE_CONFIG_DIR>/bin/bicep.exe, but it's not there. The last run that worked is task version 2.216.0

Also experiencing this with ubuntu-latest

@mike-wood-dywidag solution that works for now is calling bicep publish directly instead of az bicep publish because bicep itself is in the environment path, but it would save a lot of headache with debugging if the az version also works as expected

The above did work. However a later stage failed on something else which was previously working.
I suspect this is due to a recent update to the AZ CLI in hosted agents. (v2.46.0)

@ochampet if you use the bicep publish directly, leave out the --file/-f completly. Just use the filename/path as the first parameter and it works.

To verify the above I went back to a branch that run successfully prior to ubuntu az cli upgrade
Per suggestion I modify the code
from
az bicep publish
--file ./bicep/privateAppService.bicep
--target 'br:acrm6txyynfkimr4.azurecr.io/bicep/modules/private-app-service:v2.8'
to
bicep publish
./bicep/privateAppService.bicep
'br:acrm6txyynfkimr4.azurecr.io/bicep/modules/private-app-service:v2.8'
The error is "The input file path cannot be specified multiple times."
It does not make sense the backward compatibility break.  There is no documentation on using bicep vs az bicep.
The command below is very simple

stage: Deploy
jobs:

deployment: DeployBicepToRegistry
displayName: Deploy bicep files to registry
environment: Infra
strategy:
runOnce:
deploy:
steps:
- checkout: self
- task: AzureCLI@2
name: 'DeployBicepFile'
displayName: 'Deploy Bicep file'
inputs:
azureSubscription: $(azureServiceConnection)
scriptType: 'bash'
scriptLocation: 'inlineScript'
inlineScript: |
bicep publish
./bicep/privateAppService.bicep
'br:acrm6txyynfkimr4.azurecr.io/bicep/modules/private-app-service:v2.8'

I'm curious whether the following would solve your problem.
bicep publish
'./bicep/privateAppService.bicep'
--target 'br:acrm6txyynfkimr4.azurecr.io/bicep/modules/private-app-service:v2.8'

Without --target I can see why it does think you are specifying 2 --file params

That worked for me. Thanks


Rework lv_conf_checker.py to ignore certain items

This allows certain items (namely LV_OBJ_FREE_NUM_TYPE) to be ignored when defining defaults. Currently commenting out this, as suggested in lv_conf.h, results in an uint32_t free num.
I also reworked the syntax a little bit to be more PEP8-compliant.

@averne
Actually LV_OBJ_FREE_NUM_TYPE is not in lv_conf_template.h anymore. It is replaxed with typedef void * lv_obj_user_data_t;
Is it really there for you?

Ah sorry, I didn't see it was deprecated in 6.0, sorry about that.

@averne
No problem!
The syntax fixes still would be nice update :)


ext/hal/st: Update stm32cube packages for 1.14 zephyr release

Update stm32cube packages in sight of Zephyr 1.14.
stm32f3: V1.9.0 > 1.10.0
stm32f7: V1.11 > 1.12.0
As a preamble, dos2unix and trailing white spaces removal has been applied on all stm32 packages on which it was not already the case.

Codecov Report

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

@@           Coverage Diff           @@
##           master   #10461   +/-   ##
=======================================
  Coverage   53.14%   53.14%
=======================================
  Files         210      210
  Lines       25747    25747
  Branches     5673     5673
=======================================
  Hits        13682    13682
  Misses       9755     9755
  Partials     2310     2310

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 8ce758a...3e909eb. Read the comment docs.

Should we open an issue to convert the CAN driver to the new API?

@galak

Should we open an issue to convert the CAN driver to the new API?

Indeed will do.


Docker

This is a PR to add Docker support to the repository.
Key Features:

Built on Alpine Linux (lightweight image)
Includes Golang 1.x (latest) - v1.9 at time of commit
Includes Git (used for go get commands)
docker-compose.yml file for easy image handling
Support for mounting a Prova configuration file

Note: I decided to use the COPY command instead of the git clone suggested in issue #32, because it allows the developer to build the image with the repository in its 'current state' rather than building from the latest commit to master.
For more details, see the comments in the files below.

utACK

I've done quite a bit of testing with this now and it seems to work consistently on Docker for Windows and Debian. I don't currently have the ability to test on OSX.
In order to enable the config file mounting, you will need to create /prova.conf and /provactl.conf in the root of the project with your configuration (I considered putting these in a /config folder, but saw the existing /chaincfg and didn't want to confuse things). You will then need to uncomment the volume mounts in the /docker-compose.yml file. This will load them into the correct location when the container is brought up. As they are mounted, changes on the host will mirror to the container in real-time.
Note: As this method requires users to create non-committed config files in the project root (which then make your workspace 'dirty'), I would suggest that we also add the config files to the .gitignore. Obviously the sample config is still needed, so perhaps something like:
# Config files
/prova.conf
/provactl.conf

Any thoughts on this are welcome. I'll continue to work with Oscar to make sure this works fully

One problem that we did find, is that we don't appear to be able to bind the RPC listener to an IPv6 port.
A warning is displayed during startup:
14:54:56 2017-11-30 [WRN] RPCS: Can't listen on [::1]:18334: listen tcp6 [::1]:18334: bind: cannot assign requested address
14:54:56 2017-11-30 [INF] RPCS: RPC server listening on <IP_ADDRESS>:18334

The connection via ipv4 seems to work fine. I suspect this might be an Alpine issue as it's such a stripped down version of Linux. It's possible that reverting to a debian-slim image or similar could fix the issue, but I'd prefer to get Alpine working if I can - purely for it's efficiency.

@pd93 did you have any joy with Alpine and IPv6?

@Duality-CDOO Haven't had the chance to test this any further unfortunately, so the IPv6 error is still there. However, we've been using it without issue over IPv4. I might have some time to pick this up again towards the end of the week - I'll see if I can get it working then.


500 Internal Server Error

Not sure if this is the right forum, but if I try to access https://cdn.jsdelivr.net/polyfills/polyfill.js I get a 500 return status. Now this could be some temporary issues, but if I search for polyfill on http://www.jsdelivr.com, I get nothing.
So I wonder if the docs are outdated, or any explanation for this?

The issue is with the origin server controlled by @polyfills
It looks down or missconfigured

Shouldn't the files be cached?

Yes, but sooner or later they need to expire. The system cant keep it cached for ever. The cache would have worked just fine for a small to medium downtime.

i'm indisposed at the moment. i can add you as collab both here on heroku until i have time to figure it out

ohhh.... it could be heroku. i'm using the free instance and i think they changed their pricing

@jonathanong http://powerful-woodland-4579.herokuapp.com/polyfill.js

Ok, so that's figured out.
However, I'm a little worried about this behavior from jsDelivr, and I'll admit I don't know enough about the CDN space to point any specific fingers, but it seems to me that it's a problem if a CDN, which is suppose to be HA, is sensitive to underlying non-HA resource problems.
Any thoughts on that?

The problem is not the CDN itself. We dont host the actual file, we proxy and cache it from @polyfills official server. That server went down and caused the issue. The CDN operates just fine and has lots of advanced techniques of load balancing

yup it's an issue with my server. haven't touched it in a while

Yeah, I understand that part. But I think we can agree that the observed behavior is sub-optimal. In this case, it would seem better to keep serving the cached file, if the server isn't reachable. Is that a configuration thing or what's the way to achieve that?

Our agreement was to proxy everything as is from the origin server. I now changed the config to prevent updating the cache if the server has issues. It should help but its not bulletproof, if the server will go down for days nothing will save it.

@jonathanong Any ETA on this?

seems that one of the polyfills changed their package structure

@jonathanong Your server is still down. Any ideas?

Yeah one of the libraries messed things up. Haven't updated it. Trying to get more collaborators...

I'm confused. Given that this service is down, which repositories do I need exactly in order to mirror & host it myself?

these are the relevant repos:
https://github.com/polyfills/db
https://github.com/polyfills/feature
https://github.com/polyfills/polyfill-ua
this is the actual server: https://github.com/polyfills/paas
let me know if you wanna help

When will https://cdn.jsdelivr.net/polyfills/polyfill.js be restored?

Man I got so excited when I saw this project in a google search, and then so disappointed when I eventually got the 500 error. I think it has some merit. Any update on the status of the project?

Still experiencing the 500 upon GET https://cdn.jsdelivr.net/polyfills/polyfill.js :(