envisalink_new integration can't connect to DscServer.jar

I just tried moving from the old envisalink integration to envisalink_new and whatever I try, the integration always respond with a "Failed to connect" with the following in the log file when trying to connect to the DscServer.jar:
2024-02-27 11:40:56.014 ERROR (MainThread) [custom_components.envisalink_new.pyenvisalink.alarm_panel] Unable to validate connection: ClientConnectorError(ConnectionKey(host='<IP_ADDRESS>', port=80, is_ssl=False, ssl=True, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Connect call failed ('<IP_ADDRESS>', 80)"))
The following is what was entered in the basic configuration page

I don't really understand why the log is reporting port=80 ???? should'nt it report 4025 as configured on the configuration page ?
I know my DscServer environment is working and that this is not a firewall issue or anything since prior installing the new envisalink_new, my envisalink.yaml was configured to connect to the same unchanged DscServer.jar with no issues, also, my other system is still connecting to the DscServer with same credentials.
I then made sure nothing was wrong with the installation and tried connecting with success directly to the Envisalink 3 bord.
As I am connecting two Automation system to my alarm, I need to have a way to connect both system hence the reason why I installed DscServer.jar
I tried removing completely the integration (including all HACS files) but that did not change a thing
Info: the DscServer.jar is not running on the same machine/VLAN as my HA
I tried entering 4025 in the discovery port just for fun then I got the following error
2024-02-27 12:43:52.881 ERROR (MainThread) [custom_components.envisalink_new.pyenvisalink.alarm_panel] Unable to validate connection: ClientResponseError(RequestInfo(url=URL('http://<IP_ADDRESS>:4025/3'), method='GET', headers=<CIMultiDictProxy('Host': '<IP_ADDRESS>:4025', 'Accept': '/', 'Accept-Encoding': 'gzip, deflate, br', 'User-Agent': 'Python/3.12 aiohttp/3.9.3', 'Authorization': 'Basic dXNlcjoxMDY2')>, real_url=URL('http://<IP_ADDRESS>:4025/3')), (), status=400, message="Expected HTTP/:\n\n b'5053CD'\n ^")

Port 80 is used to query the EVL for MAC address (needed as a unique ID as required by HA config flow).
See #79.
If you are using a proxy like DscServer, you should be able to specify the EVL hostname:port for the discovery port in the config.  E.g. set "Discovery Port" to something like <IP_ADDRESS>:80 (using the IP address of your EVL device).

That is completely wonderfull, thanks for this fast resolution

I might have call for victory too fast, the integration does connect but unfortunatly, it keeps disconnecting with the following errors in the log:
2024-02-27 16:48:15.097 ERROR (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Command '001' failed due to timeout waiting for response from EVL
2024-02-27 16:48:45.106 ERROR (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Command '005' failed due to timeout waiting for response from EVL
2024-02-27 16:48:45.106 ERROR (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] The server closed the connection.
2024-02-27 16:48:45.109 ERROR (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Reconnection attempt in 30s

I suspect that may be due to DscServer not proxying the EVL's response to the 001 command back to this integration - similar to what is described in the second point in issue #19 (that's for AlarmServer but I think they both act as proxies to the EVLs).

FYI, in this case, it's the 001 rather than the 005 command which doesn't appear to be getting a response.

My mistake, Mike just wrote me back saying the 005 was handled on his side, I corrected my mistake,

The developper just confim me he was returning 500 back in response to the 001 followed by the system status message

I just found what you meant by 'disable mobile app' ...
I desactivated both my ipad and my iphone and re-did the tests
home-assistant.log
icloud3-0.log

Which firmware version you are using?  Some older versions did have issues with becoming unresponsive periodically - which could have been masked before since I don't believe the core envisalink integration checked the response to commands.
Assuming you're on a recent firmware version, could you enable debug logging:
logger:
  default: info
  logs:
    custom_components.envisalink_new: debug

And restart HA and post the pull log?
You might also try temporarily disabling DscServer and connecting HA directly to the EVL device to eliminate any possibility that it is a factor.

envisalink verion : Firmware Version: 01.12.205
Here is the log file result:
2024-02-28 10:57:21.065 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Starting read loop.
2024-02-28 10:57:21.065 INFO (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Started to connect to Envisalink... at <IP_ADDRESS>:4025
2024-02-28 10:57:21.067 INFO (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Connection Successful!
2024-02-28 10:57:21.067 INFO (MainThread) [custom_components.envisalink_new] Connected to the envisalink device
2024-02-28 10:57:21.067 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Waiting for data from EVL
2024-02-28 10:57:21.069 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] {---------------------------------------
2024-02-28 10:57:21.069 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] RX < 5053CD
2024-02-28 10:57:21.069 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] calling handler: handle_login for code: 505 with data: 3
2024-02-28 10:57:21.069 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Invoking state change callbacks
2024-02-28 10:57:21.069 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] }---------------------------------------
2024-02-28 10:57:21.069 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Waiting for data from EVL
2024-02-28 10:57:21.069 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Queueing command '005' data: '' ; calling_task=queue_login_response
2024-02-28 10:57:21.069 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Command processor woke up.
2024-02-28 10:57:21.069 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Checking command queue: len=1
2024-02-28 10:57:21.069 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] TX > b'00562'
2024-02-28 10:57:21.069 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Checking command queue: len=1
2024-02-28 10:57:21.070 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] {---------------------------------------
2024-02-28 10:57:21.070 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] RX < 5051CB
2024-02-28 10:57:21.070 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] calling handler: handle_login_success for code: 505 with data: 1
2024-02-28 10:57:21.070 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Password accepted, session created
2024-02-28 10:57:21.070 INFO (MainThread) [custom_components.envisalink_new] Established a connection and logged into the Envisalink
2024-02-28 10:57:21.070 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 AC Power'
2024-02-28 10:57:21.070 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Ready'
2024-02-28 10:57:21.070 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Panel Battery'
2024-02-28 10:57:21.070 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Panel Health'
2024-02-28 10:57:21.070 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Fire'
2024-02-28 10:57:21.070 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Alarm'
2024-02-28 10:57:21.070 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Keypad'
2024-02-28 10:57:21.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Panel Chime'
2024-02-28 10:57:21.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1'
2024-02-28 10:57:21.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 1'
2024-02-28 10:57:21.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 1 Fault'
2024-02-28 10:57:21.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 2'
2024-02-28 10:57:21.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 2 Fault'
2024-02-28 10:57:21.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 3'
2024-02-28 10:57:21.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 3 Fault'
2024-02-28 10:57:21.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 4'
2024-02-28 10:57:21.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 4 Fault'
2024-02-28 10:57:21.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 5'
2024-02-28 10:57:21.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 5 Fault'
2024-02-28 10:57:21.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 6'
2024-02-28 10:57:21.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 6 Fault'
2024-02-28 10:57:21.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 7'
2024-02-28 10:57:21.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 7 Fault'
2024-02-28 10:57:21.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 8'
2024-02-28 10:57:21.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 8 Fault'
2024-02-28 10:57:21.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 9'
2024-02-28 10:57:21.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 9 Fault'
2024-02-28 10:57:21.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 10'
2024-02-28 10:57:21.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 10 Fault'
2024-02-28 10:57:21.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 11'
2024-02-28 10:57:21.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 11 Fault'
2024-02-28 10:57:21.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 12'
2024-02-28 10:57:21.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 12 Fault'
2024-02-28 10:57:21.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 13'
2024-02-28 10:57:21.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 13 Fault'
2024-02-28 10:57:21.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 14'
2024-02-28 10:57:21.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 14 Fault'
2024-02-28 10:57:21.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 15'
2024-02-28 10:57:21.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 15 Fault'
2024-02-28 10:57:21.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 16'
2024-02-28 10:57:21.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 16 Fault'
2024-02-28 10:57:21.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 17'
2024-02-28 10:57:21.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 17 Fault'
2024-02-28 10:57:21.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 18'
2024-02-28 10:57:21.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 18 Fault'
2024-02-28 10:57:21.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 19'
2024-02-28 10:57:21.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 19 Fault'
2024-02-28 10:57:21.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 20'
2024-02-28 10:57:21.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 20 Fault'
2024-02-28 10:57:21.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 21'
2024-02-28 10:57:21.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 21 Fault'
2024-02-28 10:57:21.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 22'
2024-02-28 10:57:21.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 22 Fault'
2024-02-28 10:57:21.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 23'
2024-02-28 10:57:21.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 23 Fault'
2024-02-28 10:57:21.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 24'
2024-02-28 10:57:21.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 24 Fault'
2024-02-28 10:57:21.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 25'
2024-02-28 10:57:21.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 25 Fault'
2024-02-28 10:57:21.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 26'
2024-02-28 10:57:21.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 26 Fault'
2024-02-28 10:57:21.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 27'
2024-02-28 10:57:21.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 27 Fault'
2024-02-28 10:57:21.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 28'
2024-02-28 10:57:21.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 28 Fault'
2024-02-28 10:57:21.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 29'
2024-02-28 10:57:21.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 29 Fault'
2024-02-28 10:57:21.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 30'
2024-02-28 10:57:21.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 30 Fault'
2024-02-28 10:57:21.074 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Invoking state change callbacks
2024-02-28 10:57:21.074 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] }---------------------------------------
2024-02-28 10:57:21.074 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Waiting for data from EVL
2024-02-28 10:57:21.077 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Queueing command '010' data: '1057022824' ; calling_task=complete_login
2024-02-28 10:57:21.077 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Command processor woke up.
2024-02-28 10:57:21.077 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Checking command queue: len=2
2024-02-28 10:57:26.070 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Checking command queue: len=2
2024-02-28 10:57:26.070 ERROR (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Command '005' failed due to timeout waiting for response from EVL
2024-02-28 10:57:26.070 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Cleaning up from disconnection with server.
2024-02-28 10:57:26.070 ERROR (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] The server closed the connection.
2024-02-28 10:57:26.070 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Cleaning up from disconnection with server.
2024-02-28 10:57:26.070 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 AC Power'
2024-02-28 10:57:26.070 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Ready'
2024-02-28 10:57:26.070 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Panel Battery'
2024-02-28 10:57:26.070 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Panel Health'
2024-02-28 10:57:26.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Fire'
2024-02-28 10:57:26.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Alarm'
2024-02-28 10:57:26.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Keypad'
2024-02-28 10:57:26.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Panel Chime'
2024-02-28 10:57:26.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1'
2024-02-28 10:57:26.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 1'
2024-02-28 10:57:26.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 1 Fault'
2024-02-28 10:57:26.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 2'
2024-02-28 10:57:26.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 2 Fault'
2024-02-28 10:57:26.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 3'
2024-02-28 10:57:26.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 3 Fault'
2024-02-28 10:57:26.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 4'
2024-02-28 10:57:26.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 4 Fault'
2024-02-28 10:57:26.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 5'
2024-02-28 10:57:26.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 5 Fault'
2024-02-28 10:57:26.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 6'
2024-02-28 10:57:26.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 6 Fault'
2024-02-28 10:57:26.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 7'
2024-02-28 10:57:26.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 7 Fault'
2024-02-28 10:57:26.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 8'
2024-02-28 10:57:26.071 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 8 Fault'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 9'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 9 Fault'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 10'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 10 Fault'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 11'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 11 Fault'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 12'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 12 Fault'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 13'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 13 Fault'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 14'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 14 Fault'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 15'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 15 Fault'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 16'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 16 Fault'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 17'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 17 Fault'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 18'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 18 Fault'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 19'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 19 Fault'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 20'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 20 Fault'
2024-02-28 10:57:26.072 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 21'
2024-02-28 10:57:26.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 21 Fault'
2024-02-28 10:57:26.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 22'
2024-02-28 10:57:26.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 22 Fault'
2024-02-28 10:57:26.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 23'
2024-02-28 10:57:26.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 23 Fault'
2024-02-28 10:57:26.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 24'
2024-02-28 10:57:26.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 24 Fault'
2024-02-28 10:57:26.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 25'
2024-02-28 10:57:26.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 25 Fault'
2024-02-28 10:57:26.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 26'
2024-02-28 10:57:26.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 26 Fault'
2024-02-28 10:57:26.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 27'
2024-02-28 10:57:26.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 27 Fault'
2024-02-28 10:57:26.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 28'
2024-02-28 10:57:26.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 28 Fault'
2024-02-28 10:57:26.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 29'
2024-02-28 10:57:26.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 29 Fault'
2024-02-28 10:57:26.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 30'
2024-02-28 10:57:26.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 30 Fault'
2024-02-28 10:57:26.073 ERROR (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Reconnection attempt in 30s
2024-02-28 10:57:26.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 AC Power'
2024-02-28 10:57:26.073 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Ready'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Panel Battery'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Panel Health'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Fire'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Alarm'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Keypad'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Panel Chime'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 1'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 1 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 2'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 2 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 3'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 3 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 4'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 4 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 5'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 5 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 6'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 6 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 7'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 7 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 8'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 8 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 9'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 9 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 10'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 10 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 11'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 11 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 12'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 12 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 13'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 13 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 14'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 14 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 15'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 15 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 16'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 16 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 17'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 17 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 18'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 18 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 19'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 19 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 20'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 20 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 21'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 21 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 22'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 22 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 23'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 23 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 24'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 24 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 25'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 25 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 26'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 26 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 27'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 27 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 28'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 28 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 29'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 29 Fault'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 30'
2024-02-28 10:57:26.074 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 30 Fault'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Checking command queue: len=2
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Checking command queue: len=1
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Cleaning up from disconnection with server.
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 AC Power'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Ready'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Panel Battery'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Panel Health'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Fire'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Alarm'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Keypad'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Panel Chime'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 1'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 1 Fault'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 2'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 2 Fault'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 3'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 3 Fault'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 4'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 4 Fault'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 5'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 5 Fault'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 6'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 6 Fault'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 7'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 7 Fault'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 8'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 8 Fault'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 9'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 9 Fault'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 10'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 10 Fault'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 11'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 11 Fault'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 12'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 12 Fault'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 13'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 13 Fault'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 14'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 14 Fault'
2024-02-28 10:57:26.077 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 15'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 15 Fault'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 16'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 16 Fault'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 17'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 17 Fault'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 18'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 18 Fault'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 19'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 19 Fault'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 20'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 20 Fault'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 21'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 21 Fault'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 22'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 22 Fault'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 23'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 23 Fault'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 24'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 24 Fault'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 25'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 25 Fault'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 26'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 26 Fault'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 27'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 27 Fault'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 28'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 28 Fault'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 29'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 29 Fault'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 30'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 30 Fault'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Queueing command '001' data: '' ; calling_task=complete_login
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Command processor woke up.
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Checking command queue: len=1
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] TX > b'00191'
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Unable to send data; not connected.
2024-02-28 10:57:26.078 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Checking command queue: len=1
2024-02-28 10:57:31.079 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Checking command queue: len=1
2024-02-28 10:57:31.079 ERROR (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Command '001' failed due to timeout waiting for response from EVL
2024-02-28 10:57:31.079 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Cleaning up from disconnection with server.
2024-02-28 10:57:31.079 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 AC Power'
2024-02-28 10:57:31.079 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Ready'
2024-02-28 10:57:31.079 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Panel Battery'
2024-02-28 10:57:31.079 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Panel Health'
2024-02-28 10:57:31.079 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Fire'
2024-02-28 10:57:31.079 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Alarm'
2024-02-28 10:57:31.079 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1 Keypad'
2024-02-28 10:57:31.079 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Panel Chime'
2024-02-28 10:57:31.079 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Partition 1'
2024-02-28 10:57:31.079 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 1'
2024-02-28 10:57:31.079 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 1 Fault'
2024-02-28 10:57:31.079 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 2'
2024-02-28 10:57:31.079 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 2 Fault'
2024-02-28 10:57:31.079 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 3'
2024-02-28 10:57:31.079 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 3 Fault'
2024-02-28 10:57:31.079 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 4'
2024-02-28 10:57:31.079 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 4 Fault'
2024-02-28 10:57:31.079 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 5'
2024-02-28 10:57:31.079 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 5 Fault'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 6'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 6 Fault'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 7'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 7 Fault'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 8'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 8 Fault'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 9'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 9 Fault'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 10'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 10 Fault'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 11'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 11 Fault'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 12'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 12 Fault'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 13'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 13 Fault'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 14'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 14 Fault'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 15'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 15 Fault'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 16'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 16 Fault'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 17'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 17 Fault'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 18'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 18 Fault'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 19'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 19 Fault'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 20'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 20 Fault'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 21'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 21 Fault'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 22'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 22 Fault'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 23'
2024-02-28 10:57:31.080 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 23 Fault'
2024-02-28 10:57:31.081 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 24'
2024-02-28 10:57:31.081 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 24 Fault'
2024-02-28 10:57:31.081 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 25'
2024-02-28 10:57:31.081 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 25 Fault'
2024-02-28 10:57:31.081 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 26'
2024-02-28 10:57:31.081 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 26 Fault'
2024-02-28 10:57:31.081 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 27'
2024-02-28 10:57:31.081 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 27 Fault'
2024-02-28 10:57:31.081 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 28'
2024-02-28 10:57:31.081 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 28 Fault'
2024-02-28 10:57:31.081 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 29'
2024-02-28 10:57:31.081 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 29 Fault'
2024-02-28 10:57:31.081 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 30'
2024-02-28 10:57:31.081 DEBUG (MainThread) [custom_components.envisalink_new] state_updated for 'Zone 30 Fault'
2024-02-28 10:57:31.081 DEBUG (MainThread) [custom_components.envisalink_new.pyenvisalink.envisalink_base_client] Checking command queue: len=1
2024-02-28 10:57:41.364 INFO (MainThread) [custom_components.blueiris.api.blue_iris_api] Updating data from BI Server (goldriver)

if required, I can run traces with wireshark to help with debugging

From those logs it appears that the DscServer is sending a 505 back to indicate the login status but is not also sending a 500 in response to the 005 (login) command itself.  All commands issued to the EVL should respond with a 500 (ack), 501 (command error) or 502 (system error).  This is important because there are cases where commands can fail and envisalink_new will retry them based on these responses.
Given the firmware version you are running, I'm pretty sure your EVL is sending the 500 response to the 005 command.  I'd suggest trying to connect this integration directly to the EVL to help narrow down where the issue is.
A network capture showing traffic to and from all three hosts would definitely pinpoint the issue.

You are right, the intégration does connect and work correctly when configured to go directly to the EVL.
My problem is I need to be able to connect 2 hosts to the EVL, why I was using DscServer.
I will educate myself on using wireshark and try to extract traces between the 3 hosts and will post back as soon as i understand how it works
Thanks

Given that it works when connecting directly to the EVL, it seems most likely that DscServer is responding to the 005 (login) request with only a 505 when it should be sending a 505 and 500 to properly emulate to how the EVL devices respond.  All commands issued to the EVL should respond with a 500, 501 or 502 regardless of any additional updates they may send (such as a 505 in this example).
I don't know what your network setup is like but if you want to capture traffic from all three hosts, the simplest will likely be to run the capture from the host running DscServer since it will be able to see all the needed traffic.  It gets more complicated if you need to capture from a different host since you'd likely need to do something like setting up port mirroring on your switch so that your capture host can see the traffic from all three hosts.

Ok I installed wireshark on the machine were DscServer is installed, I setup a capture filter for the DscServer machine host <IP_ADDRESS>
The HA server runs on <IP_ADDRESS> and EVL on<IP_ADDRESS>
As I mentionned I have NO CLUE how to investigate traces as I know nothing about low level communications if I provide you the following wireshark trace are you able to track down the problem ?
thanks again for helping me ion this
envisalink.zip

Based on the capture file, I assume your HA server is <IP_ADDRESS> rather than .14?
I don't see any traffic between the DscServer and the EVL.  This could possibly be because you have multiple interfaces on your DscServer host and you only captured on one of them.
However, the trace does have the traffic between HA and DscServer and it shows that DscServer is not sending the 500 response to the 005 login command.  The fact that it works when you connect directly to the EVL means your EVL is sending this response but DscServer does not appear to be relaying it back to HA.
In the screenshot below, you can see HA getting the login request (5053CD) from DscServer in frame 1342 and HA sending the login response in frame 1345 and the DscServer responding with indicating a successful login and then there is a 5 second gap when it sends nothing else and then HA disconnects in frame 2256.

@ufodone Thank for the help evaluating the tracefile, i'll look into it and try understand it a bit and will contact Mike from DscServer to see if he can help with this.
oither than DscServer and AlarmServer do you know of any other EVL proxies that could work in the event we couldn't get DscServer to work ?

@ufodone Hi, I received the following from Mike, can you helpo us with this... I would like to be able to answer him directly but I know nothing about reading or interpretation of those traces this is completelky chinese $"%?$/%%?? for me.
thanks a lot
_**Hi Bruno – I don’t see a 001 status report request in this log.  Am I reading it wrong? Can you point me to the 001 request from the client at <IP_ADDRESS> (ideally by entry number)?
I see a 505 at #1342, A 005 response at 1345, a 505 confirmation from the DscServer at 1346, but no further communication from the client on port 4025 after that exchange.
In my code the first action to a valid incoming request is send a 500 response, but since I can’t find a 001 request I can’t point you to the response 😊.
If there’s a bug in my code I’ll fix it ASAP, there would not by any fee, you reporting a bug is enough.
Mike**_

Hi, I just realized that I'd originally thought it was the 001 command that was the issue and never explicitly corrected that when I realized it was the 005 command that was the issue.
I correct login  handshake should look something like this:
1 RX < 5053CD
2 TX > b'005**********3B'
3 RX < 5000052A
4 RX < 5051CB
5 TX > b'01008170301248B'
6 RX < 50001026
7 TX > b'00191'
8 RX < 50000126

The issue here is that DscServer does not appear to be sending the 500 response to the 005 command (line 3).
In the network trace you provided, there is the equivalent of lines 1, 2, and 4. but no line 3.
I originally thought it might  be an issue with the 001 command which you can see issued at line 6.  That was a red herring because the timeout on that command was due to it being queued too long due to it still waiting for the 500 response to the 005 command.

@ufodone Mike just released a new version 5.9.5 wich I installed and is currently running. It has only been running for about 1/2 an hour but sonnection seems stable, devices are updating (at least motion devices ) I can see that open doors are not showing open in the app but I doubt that this is related to DscServer, I will investigate a bit further but I suspect this is the same problem that was present in the previous envisalink integration wher if netkrok connection was lost, the integration did not reload all sensor states from EVL,
I'll report a bit later
Thanks to both of you for your help on this

few hours in and no connection lost, seems fixed


Also Data Service IRI needs to be preserved the same way Dataset and Distribution IRI is preserved

Related to #178 and https://github.com/opendata-mvcr/lkod/issues/6#issuecomment-756654533

This holds true only for import using POST data.

This holds true only for import using POST data.


Install python3-boto3

🗣 Description
This PR installs the python3-boto3 package.

💭 Motivation and context
As part of the work for https://github.com/cisagov/cool-assessment-terraform/issues/115, we need to run a cloud-init script to fetch a certificate from our S3 bucket.  In order for that script to work, boto3 must be installed.

🧪 Testing
I tested this by creating a new pre-release AMI in Staging with this change and verified that the install-certificates.py cloud-init script could be run successfully.

✅ Checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[x] All new and existing tests pass.

@dav3r, when you tested this did you have to modify the instance to allow IMDSv1?

@dav3r, when you tested this did you have to modify the instance to allow IMDSv1? This should make that unnecessary, although you have to install like so:
- name: Install python3-boto3
  ansible.builtin.apt:
    default_release: buster-backports
    name:
      - python3-boto3
      - python3-botocore

Ah, nevermind. I forgot that this one is already on Bullseye.

Yes, with Bullseye, this worked the way I currently have it.


Dead link to monerod-reference in interacting/overview

In the page at _https://getmonero.dev/docs/interacting/overview.html_
is a link to:
_https://getmonero.dev/docs/interacting/monerod-reference/_
It is a dead link.

fixed, thank you


HSEARCH-2908 Incorrect mapping for 'java.lang.Short and java.lang.Byte' fields with Elasticsearch.

https://hibernate.atlassian.net/browse/HSEARCH-2908
Based on top of https://github.com/hibernate/hibernate-search/pull/1889.
Thus we need to merge https://github.com/hibernate/hibernate-search/pull/1889 first.

Pull Request Test Coverage Report for Build 1

1026 of 1094 (93.78%)  changed or added relevant lines in 73 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.4%) to 88.464%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

backend/lucene/src/main/java/org/hibernate/search/backend/lucene/types/codec/impl/LuceneInstantFieldCodec.java
9
10
90.0%

mapper/pojo/src/main/java/org/hibernate/search/mapper/pojo/bridge/builtin/impl/DefaultCharacterValueBridge.java
10
11
90.91%

mapper/pojo/src/main/java/org/hibernate/search/mapper/pojo/bridge/builtin/impl/DefaultUUIDValueBridge.java
10
11
90.91%

mapper/pojo/src/main/java/org/hibernate/search/mapper/pojo/bridge/builtin/impl/DefaultZoneIdValueBridge.java
10
11
90.91%

mapper/pojo/src/main/java/org/hibernate/search/mapper/pojo/bridge/builtin/impl/DefaultZoneOffsetValueBridge.java
10
11
90.91%

backend/elasticsearch/src/main/java/org/hibernate/search/backend/elasticsearch/gson/impl/JsonElementTypes.java
4
6
66.67%

backend/elasticsearch/src/main/java/org/hibernate/search/backend/elasticsearch/types/codec/impl/ElasticsearchByteFieldCodec.java
6
8
75.0%

backend/elasticsearch/src/main/java/org/hibernate/search/backend/elasticsearch/types/codec/impl/ElasticsearchDoubleFieldCodec.java
6
8
75.0%

backend/elasticsearch/src/main/java/org/hibernate/search/backend/elasticsearch/types/codec/impl/ElasticsearchFloatFieldCodec.java
6
8
75.0%

backend/elasticsearch/src/main/java/org/hibernate/search/backend/elasticsearch/types/codec/impl/ElasticsearchShortFieldCodec.java
6
8
75.0%

Totals

Change from base Build 147:
0.4%

Covered Lines:
15551

Relevant Lines:
17579

💛  - Coveralls

Merged, thanks!

Thanks ;)


[SPARK-46036][SQL] Removing error-class from raise_error function

What changes were proposed in this pull request?

Reverting raise_error to single param variant that is enforced through ExpressionBuilder interface (vs. reflection based lookup).
Keeping internal RaiseError class untouched with ability to throw custom exception class. The only way to call it as of this change is from internal code. Open question is whether we want to clean up this code as well, given that currently no one is using it and this code seems too complex if we don't need to expose RaiseError in surface layer. Looking for feedback on this one.

Why are the changes needed?

This PR is a follow up of raise_error improvement PR. As described in jira ticket, raise_error with custom error-class parameter was deemed to be too powerful with concern that user might throw internal system errors which shouldn't be exposed to external layers.
With this change, from external perspective, we revert to the old behaviour, where raise_error only accepts single string argument which will represent message of USER_RAISED_EXCEPTION exception object.
Does this PR introduce any user-facing change?

Yes, we introduce change in raise_error signature. With this change it is no longer allowed to call:
SELECT raise_error('VIEW_NOT_FOUND', Map('relationName', '`v`'))

Instead, only allowed version will be:
SELECT raise_error('custom error message'))

Which will result in USER_RAISED_EXCEPTION being thrown with provided message.
How was this patch tested?

The change updates existing sql tests under misc-functions.sql and adds some new checks.
Was this patch authored or co-authored using generative AI tooling?

No.

cc @srielau

thanks, merging to master!


Give user ability to browse and select proxy for scraping requests

Give user list of free proxy IP/ports to choose from. The list here looks promising.
Do httr::set_config(httr::use_proxy(url, port)). This will set proxy in a way that all future calls to httr::GET will respect.
Save and restore these settings across user sessions (e.g., via the client filesystem).

Related files:
https://github.com/lanceupton/gs_scrape/blob/dev/R/proxy.R
https://github.com/lanceupton/gs_scrape/blob/dev/R/mod_settings.R

Are these files potential components of a shiny app or just functions for the overall library?

I'm keeping functions for business logic (scraping, I/O, etc) in proxy.R and keeping the shiny interface and backend connections to business logic in mod_settings.R.


Add Turkish Translation for developer dictionary

I did not see the term 'artificial intelligence', I guess it is missing. Other than that, I think we can use 'Site Güvenilirlik Mühendisliği' instead of 'Saha Güvenilirlik Mühendisliği' for SRE, what do you think?
Thank you, it was helpful for me.


[Bug]: Inline code has wrong font

Description
Inline code does not use monospace font in the render view.
Instead, it uses Roboto.
Reproduction

Use inline code in the editor.

Additional context
No response
Preferences

[X] I want to be assigned to and work on this issue myself

Links inside the render view are also missing proper styling.


Get key issue

#76

Coverage decreased (-0.1%) to 87.12% when pulling f70184f10cb15a034c064ca48916bf5a2753a9f3 on get-key-issue into e40308716092b80f1e5637f1cd80944a46464bbf on master.


further-pretraining

I got this error when doing further-pretraining
my environment
Ubuntu 18.04.4 LTS (GNU/Linux 5.4.0-74-generic x86_64)
GPU 2080ti
I use following command
python run_pretraining.py
--input_file=./tmp/tf_AGnews.tfrecord
--output_dir=./uncased_L-12_H-768_A-12_AGnews_pretrain
--do_train=True
--do_eval=True
--bert_config_file=./uncased_L-12_H-768_A-12/bert_config.json
--init_checkpoint=./uncased_L-12_H-768_A-12/bert_model.ckpt
--train_batch_size=8
--max_seq_length=128
--max_predictions_per_seq=20
--num_train_steps=100000
--num_warmup_steps=10000
--save_checkpoints_steps=10000
--learning_rate=5e-5
I got this message and further pretraining does not work
How can I fix this problem?
WARNING:tensorflow:It seems that global step (tf.train.get_global_step) has not been increased. Current value (could be stable): 62 vs previous value: 62. You could increase the global step by passing tf.train.get_global_step() to Optimizer.apply_gradients or Optimizer.minimize.
W0622 17:33:44.304897<PHONE_NUMBER>17888 basic_session_run_hooks.py:724] It seems that global step (tf.train.get_global_step) has not been increased. Current value (could be stable): 62 vs previous value: 62. You could increase the global step by passing tf.train.get_global_step() to Optimizer.apply_gradients or Optimizer.minimize.

hello~
thank you for your interest in our repo.
for this problem, do you satisfy the requirements mentioned in README.md? that is, tensorflow==1.1x. or you just used tensorflow 2.x?


Optimize executions endpoints - jpql - s3client

Is your feature request related to a problem? Please describe.
The executions endpoint validate a version exists by iterating through the workflow's versions in Java. This can be slow and resource intensive for certain workflows with hundreds of versions.
Describe the solution you'd like
WorkflowVersionDAO has a method to fetch a workflow version by name, using JPA/SQL. We should use that.
Describe alternatives you've considered
Additional context
Discovered during metrics testing
┆Issue is synchronized with this Jira Story
┆Issue Number: DOCK-2515
┆Sprint: Backlog
┆Issue Type: Story

Another optimization we could do is not create a new S3Client for every request. The S3Client is thread-safe, so we should be able to instantiate it just once.

Seems like the s3client part could be a hotfix

Took a look, it looks like setting @UnitOfWork(readOnly= true) should be worth a try.
I think you still need the db connection, but it does improve performance
https://github.com/dockstore/dockstore/issues/3525
https://github.com/dockstore/dockstore/issues/3582
https://thorben-janssen.com/read-only-query-hint/

➤ Kathy Tran commented:
There’s also a CRT-based S3 client that has enhanced performance https://aws.amazon.com/blogs/developer/introducing-crt-based-s3-client-and-the-s3-transfer-manager-in-the-aws-sdk-for-java-2-x/ ( https://aws.amazon.com/blogs/developer/introducing-crt-based-s3-client-and-the-s3-transfer-manager-in-the-aws-sdk-for-java-2-x/|smart-link )

Interesting, skimming it, I think it would make more of a difference for files larger than what we're dealing with, but definitely worth a shot.


Move TLSCAKey to v1alpha1 package

What this PR does / why we need it:
This key is essentially part of our API, and should be represented as such.
This is part of the effort to implement conversion webhooks (#1984)
Release note:
NONE

/retest

/lgtm


Abilityt to store only index and not original document source/fields

Hi,
Looking at the docs, seems like the fields are always stored. Is it possible to not store the original source (which will also disable update etc) ?

Vespa uses the documents in the store for elasticity, e.g. copy the document to new nodes as needed - so not possible to not store the document. What is the use case?
You can modify the document in Document Processing, like dropping fields, if the goal is to save space and the data is not needed to generate indices / used in summaries

The use case is for a lot of data with low query rate. And the original data can be queried from original-db.

Ok. The only option is to trim to the minimal field set needed to create the indices, then. Remember, the document store is compressed: https://docs.vespa.ai/documentation/document-summaries.html#document-store - so might not be a big issue, depends on the data ...

@kkraune I understand. Is it possible to at return only id so you don't incur a disk-read for the document-store ?

OK - then the key is to make all data needed for document summaries available in attributes. So

put the document ID (or whatever you need as a key to look up data elsewhere) in a field that is also defined as an attribute (= memory access)
define a summary class with only this field
specify this summary class in queries so only this field is returned

https://docs.vespa.ai/documentation/attributes.html
https://docs.vespa.ai/documentation/document-summaries.html
https://docs.vespa.ai/documentation/reference/search-api-reference.html#presentation.summary (you can use a query profile for this)
So, reading IDs from memory is supported - hope this helps

@kkraune that's perfect. Means I can use the custom id to also query for the exact document (like get) and getting in-memory read.


How to use OutputStreamObserver ?

Hello developers!
I read the source code of mediapipe and found a class called "OutputStreamObserver".
According to the comments in mediapipe/frameword/graph_output_stream.h :
OutputStreamObserver that observes the output stream and passes packets to the caller via packet_callback.

it seems that OutputStreamObserver has the same function with OutputStreamPoller.
However, I failed to find any document about OutputStreamObserver. Could you please tell me how to use it? It will be perfect if you can show me some example code: using OutputStreamObserver and callback function to get the output packet from graph
I am looking forward to your reply and thanks in advance!

Hi @Billccx ,
Please check this document for usage of calculators in MediaPipe

@sureshdagooglecom
Thanks for your reply! I have read the document about calculators, but what I want to know is how to use OutputStreamPoller.
Actually, my question comes from this issue https://github.com/google/mediapipe/issues/3188.
Could you please show me an example about how to use output stream observer ?

Hi @Billccx ,
Please check this closed issue for steps on how to use outpur stream https://github.com/google/mediapipe/issues/734


[v2] Add WHIP support

Add support for WHIP ingest

OBS added WHIP/WebRTC support in version 30. Since FTL support is soon removed, this might be a good replacement?


Lookup Boundary

Fixes https://github.com/flutter/flutter/issues/115381.
Design Discussion
This change introduces a stopAtLookUpBoundary parameter to the various lookup methods on BuildContext and offers a consistent API between all lookup methods, which I really like. However, it comes at the cost of adding a field (_lookUpBoundary) to every Element. This could probably be slightly optimized by replacing the _inheritedWidgets with an immutable data object that incorporates the hashmap of inherited elements and the lookUpBoundary field. That way, most Elements would just point to the same data object and not need storage for an extra field. Only Elements of InheritedWidgets and Elements who are actually lookup boundaries would have slightly increased memory needs because they will have to create a new data object with that extra field for the lookup boundary.
An alternative approach would forego a common API among all lookup methods. It would keep the stopAtLookUpBoundary parameter on the various find* lookup methods, but remove it from the dependOn* and get* lookup methods. Instead of deciding at lookup time whether to retrieve InheritedWidgets past the lookup boundary, the InheritedWidgets themselves would decide whether they want to be visible through the lookup boundary. This would be controlled via a constructor argument to InheritedWidget or an overridable getter. At a lookup boundary, we would filter the hashmap of inherited widgets to remove those who have specified that they don't want to be visible through the lookup boundary. This would make adding and moving lookup boundaries more expensive because it requires filtering a potentially long list of inherited widgets and the lookup APIs on BuildContext would be less consistent. But it would remove the extra check from the lookup implementation for inherited widgets.

Approach in PR
Alternative Approach

+ consistent API for all lookup methods
- find methods have different API from depend/get methods

- requires extra memory (1 field per element, can be optimized to one per InheritedWidget/LookupBoundary)
+ no extra memory

- requires extra check for lookup of inherited widgets
+ no extra check for inherited widget lookup

- each element needs to copy lookupboundary reference from parent in mount/activate
- adding/moving lookup boundaries is slower due to filtering

+ flexible (at lookup it is decided whether an InheritedWidget should be seen)
- less flexible (InheritedWidget decides wether it wants to be seen)

- requires extending the PersistentHashMap interface to allow for iteration for filtering

@gspencergoog @LongCatIsLooong @Hixie Curious to hear what you think of this approach. I am a little torn between the two alternatives discussed in the PR description. I am currently leaning towards having consistent APIs as implemented in this PR, though. Let me know if you have any other ideas that I might have missed.

One con of this approach is that it is more bug-prone in the sense that if there are multiple ways to look up a widget, some might set the flag and some not. Given that we usually wrap calls into .of methods etc, that's probably rare, though.

Adding the stopAtLookUpBoundary to getElementForInheritedWidgetOfExactType  is breaking package:provider, which is overriding that method in a custom element implementation: https://github.com/rrousselGit/provider/blob/bd938bdd7a32692c489a74ae2fd31fe57f59c6c8/lib/src/inherited_provider.dart#L381

@Piinks was saying the other day that there may be a way to add parameters using dart fix?

there may be a way to add parameters using dart fix?

We would still have to fix the logic inside the body to account for the parameter, which likely cannot be done automatically.
Unfortunately, package:provider is forwarding the call to a different Element inside the body, which means we can't fix them to be compatible with both master and stable...

Also, (sorry) dart fix does not apply to overridden subclass methods. It only applies to the specific class the fix has been defined for. There is a feature request for applying to subclasses though: https://github.com/dart-lang/sdk/issues/36027


New Rule: Alpha

Write Rule to validate data to contain only alphabetic characters (a-zA-z)
Description: "The field under validation must be entirely alphabetic characters"
Please see CONTRIBUTING.md for Contribution details :100:

I intend to work on this issue


Hello, how to use it?

If I know the gstreamer str?
Sent from PPHub

Hi,
Sorry, the project is still very new, just got it working a couple of days ago. I now added some documentation, which should help you get started.
To answer your question, you can pass the GStreamer pipeline string to the driver by adding the gst_pipeline parameter to the node in your launch file, like this:
<param name="gst_pipeline" value="your_pipeline_string_here"/>

Hi, Sorry, the project is still very new, just got it working a couple of days ago. I now added some documentation, which should help you get started.
To answer your question, you can pass the GStreamer pipeline string to the driver by adding the gst_pipeline parameter to the node in your launch file, like this: <param name="gst_pipeline" value="your_pipeline_string_here"/>

Thank you for your reply!But yesterday,I tried this and failed, is there something wrong?
"nvv4l2camerasrc device=/dev/video{camera_id} do-timestamp=true !
queue max-size-buffers=0 max-size-time=0 max-size-bytes=0 max-size-bytes=65536 !
video/x-raw(memory:NVMM), width=(int){capture_width}, height=(int){capture_height},
framerate=(fraction){framerate}/1 !
nvvidconv flip-method={flip_method} !
video/x-raw,  format=(string)NV12, width=(int){display_width}, height=(int){display_height} !
videoconvert !
appsink "

What is the error that you are getting?
I don't have access to a Jetson device with ROS installed currently to test your pipeline, but it seems way too complicated. Does it work when you just run it at terminal using gst-launch-1.0 at terminal?
Also, take a look at this file.
https://github.com/JetsonHacksNano/CSI-Camera/blob/master/simple_camera.py


[e2e]: go tag main config-ldflags-assets-prerelease-tag slsa3

Repo: https://github.com/slsa-framework/example-package/tree/v34.0.514
Run: https://github.com/slsa-framework/example-package/actions/runs/11510787747
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.tag.main.config-ldflags-assets-prerelease-tag.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.tag.main.config-ldflags-assets-prerelease-tag.slsa3.yml
Trigger: push
Branch: v34.0.514
Date: Fri Oct 25 02:35:32 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v34.0.515
Run: https://github.com/slsa-framework/example-package/actions/runs/11528148601
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.tag.main.config-ldflags-assets-prerelease-tag.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.tag.main.config-ldflags-assets-prerelease-tag.slsa3.yml
Trigger: push
Branch: v34.0.515
Date: Sat Oct 26 02:34:10 UTC 2024
Tests are passing now. Closing this issue.


Laravel 8.83.15 Shift

This pull request includes updates for the recent minor version release of Laravel as well as updates to your package dependencies. Feel free to commit any additional changes to the shift-ci-v8.83.15 branch.
Before merging, you need to:

Checkout the shift-ci-v8.83.15 branch
Review all pull request comments for additional changes
Run composer update
Thoroughly test your application (no tests?, no CI?)

:warning: You are running version 10.6.0 of graham-campbell/github. The latest version is 11.0.0. You should review this dependency to see if you may upgrade to the latest version.

:information_source: You are running an older version of Laravel. The latest version is 9.15.0. Run the Laravel 9.x Shift to upgrade to the latest version of Laravel.

:warning: The Shift build servers run PHP 8.1. If you are running an older version of PHP you should run composer update locally to ensure you have the proper versions of your dependencies to reflect your PHP environment.

:information_source: Shift detected your application only has the default tests. You may quickly start adding tests by using the Test Generator to automatically create the model factories, test classes, and sample tests cases for your Laravel application.


Checked behavior for NullPointerExceptions.

(currently based on #4750 ; only the last commit belongs to this PR)
We introduce a new checked behavior nullPointers, which covers NullPointerExceptions thrown by IR nodes when one of their arguments is null. The relevant nodes are:

Apply and ApplyStatically for the receiver,
Select for the qualifier,
ArrayLength and ArraySelect for the array,
GetClass, Clone and UnwrapFromException for their respective only arguments.

In the CoreJSLib, we define a new core function $n(x), which throws when x === null and otherwise returns x. We give it such a short name because it gets inserted a lot.
We insert a call to $n for all the expressions that must not be null in the nodes above. We avoid doing so when we can prove that the expression is never null. For some simple things, the emitter can locally decide that (New, This, LoadModule and literals are some examples).
The optimizer already had null tracking, notably to elide explicit null tests such as those inserted by the compiler for ==. In order to communicate the enhanced information to the emitter, we use a new transient node AssumeNotNull(x). The emitter can then avoid null checks for those.
We add another transient node CheckNotNull(x) for an explicit null check. This is inserted by the optimizer when it expands a node that would other need to perform a null check. The canonical example of that is inlining, which gets rid of the Apply node, but must preserve a null check for the receiver. CheckNotNull is also used internally by the emitter during its translation.

The compiler itself only generated an explicit NPE for the receiver of synchronized. We convert that to using a GetClass(x) in statement position as a semantics-dependent null check. In theory, this is a breaking change (and that surfaces in changed tests), as the NPE was previously reliable and is not anymore. However, it is very unlikely that anyone would rely on this particular NPE to be thrown.
In general, we use the x.getClass()-in-statement-position idiom as a user-space way to perform a semantics-dependent null check. This is semantically accurate, since getClass() is pure for all non-null receivers. We make sure that the optimizer can replace it with a CheckNotNull or remove it entirely.

Benchmarks suggest that the overhead of these new checks in the default fastLink configuration are anywhere from 0% to 17%, with an average of 7%. The code size overhead is of 1.8% in the reversi demo.
It is possible that smarter optimizations could reduce the overhead further. For example, after a successful x.isInstanceOf[T], we could know that x is non-null. In fact, we could also know that it is a T. Both pieces of knowledge would be relevant to code generated for pattern matches. However, our optimizer is currently not equipped to reason about evaluation-order-dependent knowledge.

Overhead of nullPointers == Fatal vs nullPointers == Unchecked, where the config is otherwise the default fastLink config (behaviors are Fatal except moduleInits, productionMode == false, optimizer is enabled, GCC is disabled, ES 2015):

Benchmark
Overhead (%)

tracer
9.9

richards
7.20

deltablue
16.50

kmeans
12.60

sha512
6.10

sha512Int
14.70

bounce
7.00

cd
16.70

gcbench
3.80

mandelbrot
1.40

permute
2.00

brainfuck
10.60

json
0.80

list
0.00

nbody
1.10

queens
3.90

Average overhead: 7.14%.

This is now ready for review. I leave it "draft" because it is based on #4750.

I decomposed the giant commit a little bit, trying to isolate changes that are not tightly integrated with the NPE checked behavior. Unfortunately, the big commit remains big.

I decomposed things a bit further, and even extracted two preparation PRs as #4754 and #4756.

Rebased.
@gzm0 Do you want to still have a look at this, or shall I create a Version commit off of main now?

or shall I create a Version commit off of main now?

Let's release. I'll have a look at this now, but it'll take a bit to finish :)

Sounds good. There we go: https://github.com/sjrd/scala-js/commit/e1ddd647edb9de2466705b2d8a3b3211132d6ca3

I have been thinking: Would it be completely outrageous to introduce nullability (and maybe even preciseness) into Scala.js core typesystem?

I have been thinking: Would it be completely outrageous to introduce nullability (and maybe even preciseness) into Scala.js core typesystem?

That would probably be at least somewhat outrageous. :-p
The problem I see with that is that it opens up the IR for all kinds of changes that we would like to do for the sake of the optimizer only. I don't think that's a good idea, as we make the very stable definition dependent on what basically amounts to implementation details.
To be fair, we already crossed that line when we introduced records in the IR structure. I'm not sure I can truly call that a mistake, as I'm not sure how else we could have reasonably passed them from the optimizer to the emitter otherwise. Nevertheless, it is a bit of a transgression of the principle of separate responsibilities.

I see the argument of not leaking implementation details. But it's not like nullability and/or null-safety is such an arcane concept (exact types feel different) or a concept never provided by compilers (IMO it is fair to open up this to compilers as well).

To truly open it up to compilers, we also need to provide TypeRefs for non-nullable classes, so that they can be used in MethodNames. That's quite some more effort.
If only we were going to use that in Scala 3 with strict nulls, that would be worth it. But the run-time semantics of strict nulls are still going to be erasure-based (like all other semantics in Scala), so realistically we will not be able to compile Scala-level non-nullable types to IR-level non-nullable types without putting portability at risk.

I think I addressed all the comments except checking whether more partest pass with nullPointers (I will do that tomorrow)
For the AssumeNotNull problem: it is a bit a brittle, yes. But I don't really see what else to do, except duplicating all the NPE-able nodes, as you mentioned, but IMO that would be more brittle because of the code duplication and the potential for mistakes. The AssumeNotNull should be safe as long as no one intercepts and modifies the IR between the optimizer and the emitter. But that is anyway something that we don't truly support.

Last question RE null tracking: Is there anything preventing is from introducing a TransientType analogous to the trees? We could then:

Use this to implement records (IIRC records cannot be transient ATM because they need their own type).
Use this for null tracking

We still need to insert AssumeNotNull nodes to actually cast trees into a something with NonNullableType.

Hmmm... If that's the case, then it's indeed pointless. My hope was that the trees we care about here have non-automatic types, so we could just re-type the trees. But indeed, now I realize that we'd need this in the receiver trees. And they are completely arbitrary :-/

Unless you object, I propose to go ahead with this and tackle the transient type issue if we see that AssumeNotNull is too brittle.

Sounds good. Let's do that.


Make layer private

Note: This PR is forked from PR #409 which should be merged first.
Context: Part of the templates refactor. Since Layer() functions are contained in Layers() by setting the number of layers to 1, we can discard them.
Description of the Change: Turns all Layer() templates into private functions.
Benefits: Less clutter, clearer signatures.
Possible Drawbacks: Feature breaking.
Related GitHub Issues: -

This relatively small PR would be very convenient to merge before later ones. It also contains doc improvements!


Introduce a 'put into play' method

Replaces usages of playCard(card, true) a.k.a force-play with a new putIntoPlay method.
I'll fix usages introduced in #515 once it's merged (force play will continue to work even with this change, putIntoPlay is just simpler / reads better)
putIntoPlay will ultimately be used by the forthcoming marshaling refactor

@ystros: #518 (Ghosts of Harrenhal) which I just submitted also uses playCard(card, true). Let me know if you want me to rebase it on top of this (#517) PR.

Would it be possible to have the onCardEntersPlay event raised by putIntoPlay pass the location the card came from? Useful for this for example: https://thronesdb.com/card/06011.

@zacchiro - Don't worry about it, it can be converted after merge.
@DukeTax  - Yeah, we'll probably have to add that, but I would wait until the PR that actually implements that card.


Fix for NumPy 1.23

Rel #6764.

For CuPy v11, I'd follow NumPy 1.23's behavior by removing these lines
https://github.com/cupy/cupy/blob/16b511fd3f24b8e174d7c61198a1b5f81c46425c/cupy/_core/_routines_indexing.pyx#L259-L270

Sure! (I completely had misunderstanding about that...)

/test mini

/test mini

/test mini

v10 fix will be @testing.with_requires('numpy<1.23').


MWPW-109800 Video rich results

Add video-rich-results for Video Structured Data

Supports all Google required and recommended properties
Supports mulitple Author-defined BroadcastEvents, Clips
Supports SeekToAction

Resolves: MWPW-109800
Test URLs:

Before: https://main--milo--hparra.hlx.page/drafts/hgpa/test/video-rich-results?martech=off
After: https://video-rich-results--milo--hparra.hlx.page/drafts/hgpa/test/video-rich-results?martech=off

Validation URL:

Schema.org: https://validator.schema.org/#url=https%3A%2F%2Fvideo-rich-results--milo--hparra.hlx.live%2Fdrafts%2Fhgpa%2Ftest%2Fvideo-rich-results%3Fmartech%3Doff

New PR incoming (different branch name)


emqtt postgres plug-in load error

when i try to load plugin "./bin/emqttd_ctl plugins load emq_auth_pgsql " , it gives error.
load plugin error: {emq_auth_pgsql,                 {bad_return,                  {{emq_auth_pgsql_app,start,[normal,[]]},                   {'EXIT',                    {{badmatch,                      {error,                       {shutdown,                        {failed_to_start_child,emq_auth_pgsql,                         {shutdown,                          {failed_to_start_child,worker_sup,                           {shutdown,                            {failed_to_start_child,                             {worker,1},                             invalid_password}}}}}}}},                     [{emq_auth_pgsql_app,start,2,                       [{file,"src/emq_auth_pgsql_app.erl"},{line,33}]},                      {application_master,start_it_old,4,                       [{file,"application_master.erl"},{line,273}]}]}}}}}
(sorry for the link, could not format file properly) :  https://pastebin.com/1VaRVHZP

@TallDeed Invalid password.

Hi, password was valid but auth.pgsql.server value was incorrect, instead of protocol it should directly start from hostname (i.e. auth.pgsql.server = somename.cppj8b9hmnpe.us-west-2.rds.amazonaws.com:5432)


[feat] Add (more) directions to access the UI from within HA

Follow-up to #205
A user asked for additional detail regarding the lovelace change.

@zwave-js-bot fix lint

@zwave-js-bot fix lint

Pull Request Test Coverage Report for Build 479172753

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 24.76%

Totals

Change from base Build 478099928:
0.0%

Covered Lines:
1938

Relevant Lines:
7996

💛  - Coveralls

Pull Request Test Coverage Report for Build 479172753

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 24.76%

Totals

Change from base Build 478099928:
0.0%

Covered Lines:
1938

Relevant Lines:
7996

💛  - Coveralls

You're my new best friend bot...lol.

You're my new best friend bot...lol.

This looks great, thanks @blhoward2

This looks great, thanks @blhoward2


flink: 1.4.2 -> 1.5.0

Release announcement: https://ci.apache.org/projects/flink/flink-docs-release-1.5/release-notes/flink-1.5.html
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build flink flink_1_3

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: flink, flink_1_3
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: flink, flink_1_3
Partial log (click to expand)
/nix/store/iy32l030p4qx149qr49ryl34blgnm761-flink-1.5.0/opt/flink/bin/start-zookeeper-quorum.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/8zkg9ac4s4alzyf4a8kfrig1j73z66dw-bash-4.4-p23/bin/bash"
/nix/store/iy32l030p4qx149qr49ryl34blgnm761-flink-1.5.0/opt/flink/bin/yarn-session.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/8zkg9ac4s4alzyf4a8kfrig1j73z66dw-bash-4.4-p23/bin/bash"
/nix/store/iy32l030p4qx149qr49ryl34blgnm761-flink-1.5.0/opt/flink/bin/flink-daemon.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/8zkg9ac4s4alzyf4a8kfrig1j73z66dw-bash-4.4-p23/bin/bash"
/nix/store/iy32l030p4qx149qr49ryl34blgnm761-flink-1.5.0/opt/flink/bin/pyflink-stream.sh: interpreter directive changed from "/bin/bash" to "/nix/store/8zkg9ac4s4alzyf4a8kfrig1j73z66dw-bash-4.4-p23/bin/bash"
/nix/store/iy32l030p4qx149qr49ryl34blgnm761-flink-1.5.0/opt/flink/bin/mesos-appmaster.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/8zkg9ac4s4alzyf4a8kfrig1j73z66dw-bash-4.4-p23/bin/bash"
/nix/store/iy32l030p4qx149qr49ryl34blgnm761-flink-1.5.0/opt/flink/bin/flink: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/8zkg9ac4s4alzyf4a8kfrig1j73z66dw-bash-4.4-p23/bin/bash"
/nix/store/iy32l030p4qx149qr49ryl34blgnm761-flink-1.5.0/opt/flink/bin/flink-console.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/8zkg9ac4s4alzyf4a8kfrig1j73z66dw-bash-4.4-p23/bin/bash"
checking for references to /build in /nix/store/iy32l030p4qx149qr49ryl34blgnm761-flink-1.5.0...
/nix/store/iy32l030p4qx149qr49ryl34blgnm761-flink-1.5.0
/nix/store/byr3vhini7axrlw6z8r3i10p9hp3r71z-flink-1.3.3

Success on x86_64-darwin (full log)
Attempted: flink, flink_1_3
Partial log (click to expand)
/nix/store/fb1rg0b9ac54ypgl6cmy8ngwy2gld41x-flink-1.5.0/opt/flink/bin/start-cluster.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/q2wqq1k20v8kc3vckapqf5nws30brnni-bash-4.4-p23/bin/bash"
/nix/store/fb1rg0b9ac54ypgl6cmy8ngwy2gld41x-flink-1.5.0/opt/flink/bin/start-scala-shell.sh: interpreter directive changed from "/bin/bash" to "/nix/store/q2wqq1k20v8kc3vckapqf5nws30brnni-bash-4.4-p23/bin/bash"
/nix/store/fb1rg0b9ac54ypgl6cmy8ngwy2gld41x-flink-1.5.0/opt/flink/bin/start-zookeeper-quorum.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/q2wqq1k20v8kc3vckapqf5nws30brnni-bash-4.4-p23/bin/bash"
/nix/store/fb1rg0b9ac54ypgl6cmy8ngwy2gld41x-flink-1.5.0/opt/flink/bin/stop-cluster.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/q2wqq1k20v8kc3vckapqf5nws30brnni-bash-4.4-p23/bin/bash"
/nix/store/fb1rg0b9ac54ypgl6cmy8ngwy2gld41x-flink-1.5.0/opt/flink/bin/stop-zookeeper-quorum.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/q2wqq1k20v8kc3vckapqf5nws30brnni-bash-4.4-p23/bin/bash"
/nix/store/fb1rg0b9ac54ypgl6cmy8ngwy2gld41x-flink-1.5.0/opt/flink/bin/taskmanager.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/q2wqq1k20v8kc3vckapqf5nws30brnni-bash-4.4-p23/bin/bash"
/nix/store/fb1rg0b9ac54ypgl6cmy8ngwy2gld41x-flink-1.5.0/opt/flink/bin/yarn-session.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/q2wqq1k20v8kc3vckapqf5nws30brnni-bash-4.4-p23/bin/bash"
/nix/store/fb1rg0b9ac54ypgl6cmy8ngwy2gld41x-flink-1.5.0/opt/flink/bin/zookeeper.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/q2wqq1k20v8kc3vckapqf5nws30brnni-bash-4.4-p23/bin/bash"
/nix/store/fb1rg0b9ac54ypgl6cmy8ngwy2gld41x-flink-1.5.0
/nix/store/qb56hl0mydsz2dd83szx9zbkck46i39d-flink-1.3.3


[BUGFIX] Funnel#files is meant to be a fully expanded list of files, …

…not a glob
Funnel#includes can be used for globs.
This is meant as a 1.3.x release, which means it will never apply cleanly to master. We should likely create 1.3.x-stable branch, to PR against.

https://github.com/yahoo/ember-intl/pull/195 created a 1.3.1 branch and submitted your fix against it.  Thanks :+1:

I'll also bring the changes to master

1.3.1 published


Various updates

Update npm publish command to include latest tag

Need to update the @sats-connect/core version to 0.0.3 before merging


Widevine extract issue

I am experimenting with a S905W TV box and reinstalling Kodi and/or this plugin frequently. Over the last 24 hours I'm facing a strange issue not happening before. It occurs at first play of a video, when Widevine needs to be installed. It fails. I am guessing it has something to do with the fact that there are profiles with Greek characters on Netflix. But this was not happening before, and I have not changed anything regarding the profiles.
Here is the error produced:
2020-05-01 07:46:04.420 T:3664741232   ERROR: [plugin.video.netflix (2)] Traceback (most recent call last):
File "/storage/.kodi/addons/plugin.video.netflix/resources/lib/run_addon.py", line 182, in run
route([part for part in g.PATH.split('/') if part])
File "/storage/.kodi/addons/plugin.video.netflix/resources/lib/run_addon.py", line 33, in lazy_login_wrapper
return func(*args, **kwargs)
File "/storage/.kodi/addons/plugin.video.netflix/resources/lib/run_addon.py", line 57, in route
play(videoid=pathitems[1:])
File "/storage/.kodi/addons/plugin.video.netflix/resources/lib/common/videoid.py", line 294, in wrapper
return func(*args, **kwargs)
File "/storage/.kodi/addons/plugin.video.netflix/resources/lib/common/logging.py", line 133, in timing_wrapper
return func(*args, **kwargs)
File "/storage/.kodi/addons/plugin.video.netflix/resources/lib/navigation/player.py", line 72, in play
list_item = get_inputstream_listitem(videoid)
File "/storage/.kodi/addons/plugin.video.netflix/resources/lib/navigation/player.py", line 144, in get_inputstream_listitem
if not is_helper.check_inputstream():
File "/storage/.kodi/addons/script.module.inputstreamhelper/lib/inputstreamhelper/init.py", line 407, in check_inputstream
return self._check_drm()
File "/storage/.kodi/addons/script.module.inputstreamhelper/lib/inputstreamhelper/init.py", line 362, in _check_drm
return self.install_widevine()
File "/storage/.kodi/addons/script.module.inputstreamhelper/lib/inputstreamhelper/init.py", line 33, in clean_before_after
result = func(self, *args, **kwargs)
File "/storage/.kodi/addons/script.module.inputstreamhelper/lib/inputstreamhelper/init.py", line 223, in install_widevine
result = install_widevine_arm(backup_path())
File "/storage/.kodi/addons/script.module.inputstreamhelper/lib/inputstreamhelper/widevine/arm.py", line 240, in install_widevine_arm
extract_widevine_from_img(os.path.join(backup_path, arm_device['version']))
File "/storage/.kodi/addons/script.module.inputstreamhelper/lib/inputstreamhelper/widevine/arm.py", line 253, in extract_widevine_from_img
for root, _, files in os.walk(mnt_path()):
File "/usr/lib/python2.7/os.py", line 296, in walk
File "/usr/lib/python2.7/os.py", line 296, in walk
File "/usr/lib/python2.7/os.py", line 296, in walk
File "/usr/lib/python2.7/os.py", line 286, in walk
File "/usr/lib/python2.7/posixpath.py", line 73, in join
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc5 in position 29: ordinal not in range(128)

"/storage/.kodi/addons/script.module.inputstreamhelper/lib/inputstreamhelper/widevine/arm.py"
it is clearly written that the error does not come from this add-on

Yes but the above addon was installed by yours. It is a dependency.

if the dependencies don't work, it's not a problem that needs to be solved here
Nothing i can do for you

I undestand. Thank you for your time.


Meteor multiple list in single collection

Hi there!
I have an item collection divided by categoryId param and sort those items separately.
So I want to know there is any reason selector in package build based on order field and not on _id field
selector[orderField] = {$lte: orderPrevItem, $gt: startOrder};

Because it kills an idea to store separate list in same collection.

Didn't find  selector option at first. Sorry