error on launch: TCP Socket Disconnected

Hello @vanackej ,
First of all, thanks for your work.
So, to begin, i've found the installer password through Risco Configuration Sofware and i disabled the cloud part.
 Does i have to configure the ip of the machine wich contains your app instead of the risco cloud url?
Any clue?
Thanks for your return.

Hey, make sure you have the latest update of this project, there were some improvemenst
but the socket destroyed  issue, i have it too sometimes, just restart it, it should work on second or third attempt....
see also here : https://github.com/vanackej/risco-mqtt-local/issues/9

Well that's strange, I never encounter this error. Your panel is returning a N05 error code (invalid parameter) to the CUSTLST command, did not expect it to happen.
panelID is supposed to be an integer, not a string. Can you try to change panelId from "0001" to just 1 please ?

Well that's strange, I never encounter this error. Your panel is returning a N05 error code (invalid parameter) to the CUSTLST command, did not expect it to happen.

Thanks for your return.
here is the result with the "panel_id": 1 parameter
Loading config from: /root/risco/config.json
2022-2-8 13:35:21 [debug] User config:
{
"log": "debug",
"panel": {
"panelIp": "<IP_ADDRESS>",
"panelPort": 1000,
"panelPassword": "5678",
"panelId": 1,
"watchDogInterval": 10000
},
"mqtt": {
"url": "mqtt://<IP_ADDRESS>:1883"
},
"zones": {
"default": {
"off_delay": 30,
"name_prefix": "Sensor - "
}
}
}
2022-2-8 13:35:21 [debug] Merged config:
{
"log": "debug",
"logColorize": false,
"ha_discovery_prefix_topic": "homeassistant",
"ha_discovery_include_nodeId": false,
"panel": {
"panelIp": "<IP_ADDRESS>",
"panelPort": 1000,
"panelPassword": "5678",
"panelId": 1,
"watchDogInterval": 10000
},
"zones": {
"default": {
"off_delay": 30,
"device_class": "motion",
"name_prefix": "Sensor - "
}
},
"mqtt": {
"url": "mqtt://<IP_ADDRESS>:1883",
"reconnectPeriod": 5000,
"clientId": "risco-mqtt-8aa247",
"will": {
"topic": "riscopanel/alarm/status",
"payload": "offline",
"qos": 1,
"retain": true,
"properties": {
"willDelayInterval": 30
}
}
}
}
2022-2-8 13:35:21 [debug] Pseudo Buffer Created for Panel Id(1):
[2,5,11,23,47,94,189,122,244,232,208,161,66,133,11,22,45,90,181,107,214,173,90,180,104,208,161,67,135,15,31,63,126,253,251,247,239,223,191,127,255,255,254,252,249,242,229,202,149,43,86,172,8
8,176,96,193,131,6,12,25,50,100,200,144,32,65,130,5,11,23,47,95,190,125,250,245,234,213,170,85,170,84,168,81,162,68,136,17,35,70,140,24,49,98,197,138,21,42,85,171,87,175,94,188,121,243,230,2
04,152,49,98,197,138,21,43,86,172,88,177,99,198,141,27,54,109,218,180,105,210,165,74,149,42,85,171,86,173,90,181,106,212,168,80,160,64,129,2,4,9,19,39,78,157,58,117,234,213,170,85,170,85,171
,87,175,95,190,124,248,240,225,195,135,15,30,60,120,240,224,193,131,6,12,25,51,102,205,154,53,107,215,175,94,189,122,245,235,215,175,95,190,125,251,246,236,216,176,96,192,129,2,4,8,17,34,68,
137,19,39,78,156,56,113,227,199,143,30,61,122,245,234,213,171,86,172,89,179,102,205,154,53,107,215,174,92,185,115,231,207,158,61,123,247,239,223,191]
2022-2-8 13:35:21 [debug] Local GMT Timezone is : +01:00
2022-2-8 13:35:21 [info] autoConnect enabled, starting communication
2022-2-8 13:35:21 [verbose] Start Connection to Panel
2022-2-8 13:35:21 [debug] TCP Socket is not already created, Create It
2022-2-8 13:35:21 [debug] TCP Socket must be created now
2022-2-8 13:35:21 [info] Connecting to mqtt server: mqtt://<IP_ADDRESS>:1883
2022-2-8 13:35:21 [info] Connected on mqtt server: mqtt://<IP_ADDRESS>:1883
2022-2-8 13:35:21 [info] Panel is not connected, waiting
2022-2-8 13:35:21 [verbose] Socket Connected, log in to panel
2022-2-8 13:35:21 [verbose] Authenticating to the panel
2022-2-8 13:35:21 [verbose] Command[1] Sending Command: RMT=5678
2022-2-8 13:35:21 [debug] Command[1] Writing command buffer to socket: [2,48,49,82,77,84,61,53,54,55,56,23,66,48,70,56,3]
2022-2-8 13:35:21 [debug] Command[1] Data Sent : RMT=5678
2022-2-8 13:35:26 [warn] Command[1] 'RMT=5678' Timeout
2022-2-8 13:35:26 [debug] Command[1] retrying with a new command Id
2022-2-8 13:35:26 [verbose] Command[1] Sending Command: RMT=5678
2022-2-8 13:35:26 [debug] Command[1] Writing command buffer to socket: [2,48,49,82,77,84,61,53,54,55,56,23,66,48,70,56,3]
2022-2-8 13:35:26 [debug] Command[1] Data Sent : RMT=5678
2022-2-8 13:35:27 [debug] Received data Buffer : [2,48,49,65,67,75,23,51,57,69,66,3]
2022-2-8 13:35:27 [debug] Command[1] CRC Value : 39EB
2022-2-8 13:35:27 [debug] Command[1] CRC Ok
2022-2-8 13:35:27 [debug] Command[1] Command response from Panel
2022-2-8 13:35:27 [debug] Command[1] Emitting expected command response
2022-2-8 13:35:27 [verbose] Command[1] Received data from panel: ACK
2022-2-8 13:35:27 [debug] Command[1] SendCommand receive this response : ACK
2022-2-8 13:35:27 [verbose] Command[2] Sending Command: LCL
2022-2-8 13:35:27 [debug] Command[2] Writing command buffer to socket: [2,48,50,76,67,76,23,65,53,65,70,3]
2022-2-8 13:35:27 [debug] Command[2] Data Sent : LCL
2022-2-8 13:35:27 [debug] Received data Buffer : [2,48,50,65,67,75,23,51,57,65,70,3]
2022-2-8 13:35:27 [debug] Command[2] CRC Value : 39AF
2022-2-8 13:35:27 [debug] Command[2] CRC Ok
2022-2-8 13:35:27 [debug] Command[2] Command response from Panel
2022-2-8 13:35:27 [debug] Command[2] Emitting expected command response
2022-2-8 13:35:27 [verbose] Command[2] Received data from panel: ACK
2022-2-8 13:35:27 [debug] Command[2] SendCommand receive this response : ACK
2022-2-8 13:35:27 [debug] LCL command result OK
2022-2-8 13:35:27 [verbose] Setting up encryption using Panel Id
2022-2-8 13:35:27 [verbose] Command[3] Sending Command: CUSTLST?
2022-2-8 13:35:27 [debug] Command[3] Writing command buffer to socket: [2,17,50,54,72,66,124,10,241,41,160,215,199,148,115,188,60,3]
2022-2-8 13:35:27 [debug] Command[3] Data Sent : CUSTLST?
2022-2-8 13:35:27 [debug] Received data Buffer : [2,17,50,54,69,39,26,73,132,76,192,217,3]
2022-2-8 13:35:27 [debug] Command[3] CRC Value : 9641
2022-2-8 13:35:27 [debug] Command[3] CRC Ok
2022-2-8 13:35:27 [verbose] Command[3] inCryptTest enabled, emitting response without checks
2022-2-8 13:35:27 [debug] Command[3] SendCommand receive this response : N05
2022-2-8 13:35:27 [debug] cryptTableTester response: N05
2022-2-8 13:35:27 [verbose] Command[4] Sending Command: CUSTLST?
2022-2-8 13:35:27 [debug] Command[4] Writing command buffer to socket: [2,17,50,49,72,66,124,10,241,41,160,215,199,153,0,183,61,3]
2022-2-8 13:35:27 [debug] Command[4] Data Sent : CUSTLST?
2022-2-8 13:35:27 [debug] Received data Buffer : [2,17,50,49,69,39,26,73,136,76,178,220,3]
2022-2-8 13:35:27 [debug] Command[4] CRC Value : 56F4
2022-2-8 13:35:27 [debug] Command[4] CRC Ok
2022-2-8 13:35:27 [verbose] Command[4] inCryptTest enabled, emitting response without checks
2022-2-8 13:35:27 [debug] Command[4] SendCommand receive this response : N05
2022-2-8 13:35:27 [debug] cryptTableTester response: N05
2022-2-8 13:35:27 [verbose] Command[5] Sending Command: CUSTLST?
2022-2-8 13:35:27 [debug] Command[5] Writing command buffer to socket: [2,17,50,48,72,66,124,10,241,41,160,215,199,149,7,178,60,3]
2022-2-8 13:35:27 [debug] Command[5] Data Sent : CUSTLST?
2022-2-8 13:35:27 [debug] Received data Buffer : [2,17,50,48,69,39,26,73,132,76,183,209,3]
2022-2-8 13:35:27 [debug] Command[5] CRC Value : 96C9
2022-2-8 13:35:27 [debug] Command[5] CRC Ok
2022-2-8 13:35:27 [verbose] Command[5] inCryptTest enabled, emitting response without checks
2022-2-8 13:35:27 [debug] Command[5] SendCommand receive this response : N05
2022-2-8 13:35:27 [debug] cryptTableTester response: N05
2022-2-8 13:35:27 [error] Unable to connect to the control panel.
2022-2-8 13:35:27 [verbose] Command[6] Sending Command: DCN
2022-2-8 13:35:27 [debug] Command[6] Writing command buffer to socket: [2,17,50,51,79,84,97,73,139,79,193,172,3]
2022-2-8 13:35:27 [debug] Command[6] Data Sent : DCN
2022-2-8 13:35:28 [debug] Received data Buffer : [2,17,50,51,74,84,100,73,251,67,193,173,3]
2022-2-8 13:35:28 [debug] Command[6] CRC Value : F95E
2022-2-8 13:35:28 [debug] Command[6] CRC Ok
2022-2-8 13:35:28 [debug] Command[6] Command response from Panel
2022-2-8 13:35:28 [debug] Command[6] Emitting expected command response
2022-2-8 13:35:28 [verbose] Command[6] Received data from panel: ACK
2022-2-8 13:35:28 [debug] Command[6] SendCommand receive this response : ACK
2022-2-8 13:35:28 [debug] Socket Destroyed.
2022-2-8 13:35:28 [info] TCP Socket Disconnected
2022-2-8 13:35:28 [debug] Socket Disconnected.

sorry , disregard, you disabled the cloud, i still have cloud enabled, and i use the proxy method

hello @pergolafabio ,
i'm using this version; i think its the latest:
npm list | grep -i risco
/root/risco
├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>does the proxy mode mean i have to change the default cloud url with the ip of my server with the risco-mqtt-local code? and enable the cloud parameter?
The alarm is a Agility4.

yes, you have 2 ways:
on your risco panel, the www.riscocloud.be 33000  => should be changed to IP of your docker + 33333
OR , f you have an advanced router, you can make an IPTABLES rule, to forward OUTGOING traffic back to internal traffic, tahts what i did, thn i dont have to configure anything on the risco panel... (not the same as portforward = INCOMING)
make sure also to enable proxy in the json of this project, mine looks like below; the IP config is irrelevant
{
  "log": "info",
  "logColorize": true,
  "panel": {
    "panelIp": "<IP_ADDRESS>",
    "panelPort": 1000,
    "panelPassword": 1234,
    "panelId": "0001",
    "watchDogInterval": 10000,
	"guessPasswordAndPanelId": false,
	"Disable_RiscoCloud":  true,
	"Enable_RiscoCloud":  true,
	"autoDiscover":  false,
	"socketMode": "proxy",
	"listeningPort": 33000,
	"cloudPort": 33000,
	"cloudUrl": "www.riscocloud.com"
  },
  "mqtt": {
    "url": "mqtt://homeassistant:1883",
    "username": "hassio",
    "password": "Duj0ur--"
  },
  "zones": {
    "default": {
      "off_delay": 0,
      "name_prefix": ""
    },
    "GARAGE": {
      "off_delay": 0,
      "device_class": "garage_door",
      "name": "Garage Door",
      "name_prefix": ""
    }
  }
}

yes, you have 2 ways:
on your risco panel, the www.riscocloud.be 33000 => should be changed to IP of your docker + 33333
OR , f you have an advanced router, you can make an IPTABLES rule, to forward OUTGOING traffic back to internal traffic, tahts what i did, thn i dont have to configure anything on the risco panel... (not the same as portforward = INCOMING)
make sure also to enable proxy in the json of this project, mine looks like below; the IP config is irrelevant
{
  "log": "info",
  "logColorize": true,
  "panel": {
    "panelIp": "<IP_ADDRESS>",
    "panelPort": 1000,
    "panelPassword": 1234,
    "panelId": "0001",
    "watchDogInterval": 10000,
	"guessPasswordAndPanelId": false,
	"Disable_RiscoCloud":  true,
	"Enable_RiscoCloud":  true,
	"autoDiscover":  false,
	"socketMode": "proxy",
	"listeningPort": 33000,
	"cloudPort": 33000,
	"cloudUrl": "www.riscocloud.com"
  },
  "mqtt": {
    "url": "mqtt://homeassistant:1883",
    "username": "hassio",
    "password": "hassio"
  },
  "zones": {
    "default": {
      "off_delay": 0,
      "name_prefix": ""
    },
    "GARAGE": {
      "off_delay": 0,
      "device_class": "garage_door",
      "name": "Garage Door",
      "name_prefix": ""
    }
  }
}

Why ip of my docker + 33333, and not ip of my docker and 33000  for the cs configuration?
Thanks

sorry, type error , its 33000, below is important:
"socketMode": "proxy",
"listeningPort": 33000,
"cloudPort": 33000,
"cloudUrl": "www.riscocloud.com"

sorry, type error , its 33000, below is important:
"socketMode": "proxy",
"listeningPort": 33000,
"cloudPort": 33000,
"cloudUrl": "www.riscocloud.com"

i will try this end of afternoon , no kids at home ^^
i 'll keep you informed.
Thanks again @pergolafabio
Another question, does someone have the upgrade password for a firmware update? (i sent an email to risco, but no response for the moment)
Cheers

try :<PHONE_NUMBER>7

re,
so I was able to test right now.
Indeed, it is better.
However, I encountered the following error:
Loading config from: /root/risco/config.json
2022-2-8 18:41:22 [debug] User config:
{
  "log": "debug",
  "logColorize": true,
  "panel": {
    "panelIp": "<IP_ADDRESS>",
    "panelPort": 1000,
    "panelPassword": 5678,
    "panelId": "0001",
    "watchDogInterval": 10000,
    "guessPasswordAndPanelId": false,
    "Disable_RiscoCloud": true,
    "Enable_RiscoCloud": true,
    "autoDiscover": true,
    "socketMode": "proxy",
    "listeningPort": 33000,
    "cloudPort": 33000,
    "cloudUrl": "www.riscocloud.com"
  },
  "mqtt": {
    "url": "mqtt://homeassistant:1883"
  },
  "zones": {
    "default": {
      "off_delay": 0,
      "name_prefix": ""
    },
    "GARAGE": {
      "off_delay": 0,
      "device_class": "garage_door",
      "name": "Garage Door",
      "name_prefix": ""
    }
  }
}
2022-2-8 18:41:22 [debug] Merged config:
{
  "log": "debug",
  "logColorize": true,
  "ha_discovery_prefix_topic": "homeassistant",
  "ha_discovery_include_nodeId": false,
  "panel": {
    "panelIp": "<IP_ADDRESS>",
    "panelPort": 1000,
    "panelPassword": 5678,
    "panelId": "0001",
    "watchDogInterval": 10000,
    "guessPasswordAndPanelId": false,
    "Disable_RiscoCloud": true,
    "Enable_RiscoCloud": true,
    "autoDiscover": true,
    "socketMode": "proxy",
    "listeningPort": 33000,
    "cloudPort": 33000,
    "cloudUrl": "www.riscocloud.com"
  },
  "zones": {
    "default": {
      "off_delay": 0,
      "device_class": "motion",
      "name_prefix": ""
    },
    "GARAGE": {
      "off_delay": 0,
      "device_class": "garage_door",
      "name": "Garage Door",
      "name_prefix": ""
    }
  },
  "mqtt": {
    "url": "mqtt://homeassistant:1883",
    "reconnectPeriod": 5000,
    "clientId": "risco-mqtt-47ebe2",
    "will": {
      "topic": "riscopanel/alarm/status",
      "payload": "offline",
      "qos": 1,
      "retain": true,
      "properties": {
        "willDelayInterval": 30
      }
    }
  }
}
2022-2-8 18:41:22 [debug] Pseudo Buffer Created for Panel Id(0001):
[2,5,11,23,47,94,189,122,244,232,208,161,66,133,11,22,45,90,181,107,214,173,90,180,104,208,161,67,135,15,31,63,126,253,251,247,239,223,191,127,255,255,254,252,249,242,229,202,149,43,86,172,88,176,96,193,131,6,12,25,50,100,200,144,32,65,130,5,11,23,47,95,190,125,250,245,234,213,170,85,170,84,168,81,162,68,136,17,35,70,140,24,49,98,197,138,21,42,85,171,87,175,94,188,121,243,230,204,152,49,98,197,138,21,43,86,172,88,177,99,198,141,27,54,109,218,180,105,210,165,74,149,42,85,171,86,173,90,181,106,212,168,80,160,64,129,2,4,9,19,39,78,157,58,117,234,213,170,85,170,85,171,87,175,95,190,124,248,240,225,195,135,15,30,60,120,240,224,193,131,6,12,25,51,102,205,154,53,107,215,175,94,189,122,245,235,215,175,95,190,125,251,246,236,216,176,96,192,129,2,4,8,17,34,68,137,19,39,78,156,56,113,227,199,143,30,61,122,245,234,213,171,86,172,89,179,102,205,154,53,107,215,174,92,185,115,231,207,158,61,123,247,239,223,191]
2022-2-8 18:41:22 [debug] Local GMT Timezone is : +01:00
2022-2-8 18:41:22 [info] autoConnect enabled, starting communication
2022-2-8 18:41:22 [verbose] Start Connection to Panel
2022-2-8 18:41:22 [debug] TCP Socket is not already created, Create It
2022-2-8 18:41:22 [debug] TCP Socket must be created now
2022-2-8 18:41:22 [info] Connecting to mqtt server: mqtt://homeassistant:1883
2022-2-8 18:41:22 [info] Listening on IP :: and Port 33000
2022-2-8 18:41:22 [info] Waiting for panel incoming connection... This can take up to 1 or 2 minutes
2022-2-8 18:41:22 [info] MQTT close
2022-2-8 18:41:27 [info] MQTT reconnect
2022-2-8 18:41:27 [info] MQTT close
2022-2-8 18:41:32 [info] MQTT reconnect
2022-2-8 18:41:32 [info] MQTT close
2022-2-8 18:41:37 [info] MQTT reconnect
2022-2-8 18:41:37 [info] MQTT close
2022-2-8 18:41:42 [info] MQTT reconnect
2022-2-8 18:41:42 [info] MQTT close
2022-2-8 18:41:47 [info] MQTT reconnect
2022-2-8 18:41:47 [info] MQTT close
2022-2-8 18:41:52 [info] MQTT reconnect
2022-2-8 18:41:52 [info] MQTT close
2022-2-8 18:41:57 [info] MQTT reconnect
2022-2-8 18:41:57 [info] MQTT close
2022-2-8 18:42:02 [info] MQTT reconnect
2022-2-8 18:42:02 [info] MQTT close
2022-2-8 18:42:07 [info] MQTT reconnect
2022-2-8 18:42:07 [info] MQTT close
2022-2-8 18:42:12 [info] MQTT reconnect
2022-2-8 18:42:12 [info] MQTT close
2022-2-8 18:42:15 [info] Incoming connection from panel received
2022-2-8 18:42:15 [debug] RiscoCloud Socket: connect
2022-2-8 18:42:15 [info] RiscoCloud Socket: ready
2022-2-8 18:42:15 [info] Setting a timer for panel connection in 30000 ms
2022-2-8 18:42:17 [debug] [Panel => Cloud] Forwarding panel packet to cloud: [2,19,55,54,4,81,0,16,3,0,50,50,52,48,48,52,49,49,57,55,48,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,0,0,23,23,69,76,5,20,1,255,255,255,255,255,255,48,16,2,1,0,0,0,0,5,55,43,41,66,0,0,16,2,15,49,57,50,46,49,54,56,46,49,48,48,46,49,56,50,1,23,49,52,69,50,3]
2022-2-8 18:42:17 [info] MQTT reconnect
2022-2-8 18:42:17 [info] MQTT close
2022-2-8 18:42:19 [debug] [Cloud => Panel] Forwarding Cloud data Buffer to panel: [2,19,55,54,0,9,0,16,3,248,23,66,23,34,16,2,8,16,3,23,48,50,57,55,3]
2022-2-8 18:42:22 [info] MQTT reconnect
2022-2-8 18:42:22 [info] MQTT close
2022-2-8 18:42:27 [info] MQTT reconnect
2022-2-8 18:42:27 [info] MQTT close
2022-2-8 18:42:32 [info] MQTT reconnect
2022-2-8 18:42:32 [info] MQTT close
2022-2-8 18:42:37 [info] MQTT reconnect
2022-2-8 18:42:37 [info] MQTT close
2022-2-8 18:42:42 [info] MQTT reconnect
2022-2-8 18:42:42 [info] MQTT close
2022-2-8 18:42:45 [verbose] Authenticating to the panel
2022-2-8 18:42:45 [verbose] Command[1] Sending Command: RMT=5678
2022-2-8 18:42:45 [debug] Command[1] Writing command buffer to socket: [2,48,49,82,77,84,61,53,54,55,56,23,66,48,70,56,3]
2022-2-8 18:42:45 [debug] Command[1] Data Sent : RMT=5678
2022-2-8 18:42:45 [debug] [Panel => Bridge] Received unencrypted data Buffer from Panel : [2,48,49,65,67,75,23,51,57,69,66,3]
2022-2-8 18:42:45 [debug] Received data Buffer : [2,48,49,65,67,75,23,51,57,69,66,3]
2022-2-8 18:42:45 [debug] Command[1] CRC Value : 39EB
2022-2-8 18:42:45 [debug] Command[1] CRC Ok
2022-2-8 18:42:45 [debug] Command[1] Command response from Panel
2022-2-8 18:42:45 [debug] Command[1] Emitting expected command response
2022-2-8 18:42:45 [verbose] Command[1] Received data from panel: ACK
2022-2-8 18:42:45 [debug] Command[1] SendCommand receive this response : ACK
2022-2-8 18:42:45 [verbose] Command[2] Sending Command: LCL
2022-2-8 18:42:45 [debug] Command[2] Writing command buffer to socket: [2,48,50,76,67,76,23,65,53,65,70,3]
2022-2-8 18:42:45 [debug] Command[2] Data Sent : LCL
2022-2-8 18:42:45 [debug] [Panel => Bridge] Received unencrypted data Buffer from Panel : [2,48,50,65,67,75,23,51,57,65,70,3]
2022-2-8 18:42:45 [debug] Received data Buffer : [2,48,50,65,67,75,23,51,57,65,70,3]
2022-2-8 18:42:45 [debug] Command[2] CRC Value : 39AF
2022-2-8 18:42:45 [debug] Command[2] CRC Ok
2022-2-8 18:42:45 [debug] Command[2] Command response from Panel
2022-2-8 18:42:45 [debug] Command[2] Emitting expected command response
2022-2-8 18:42:45 [verbose] Command[2] Received data from panel: ACK
2022-2-8 18:42:45 [debug] Command[2] SendCommand receive this response : ACK
2022-2-8 18:42:45 [debug] LCL command result OK
2022-2-8 18:42:45 [verbose] Setting up encryption using Panel Id
2022-2-8 18:42:45 [verbose] Command[3] Sending Command: CUSTLST?
2022-2-8 18:42:45 [debug] Command[3] Writing command buffer to socket: [2,17,50,54,72,66,124,10,241,41,160,215,199,148,115,188,60,3]
2022-2-8 18:42:45 [debug] Command[3] Data Sent : CUSTLST?
2022-2-8 18:42:46 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,50,54,69,39,26,73,132,76,192,217,3]
2022-2-8 18:42:46 [debug] Received data Buffer : [2,17,50,54,69,39,26,73,132,76,192,217,3]
2022-2-8 18:42:46 [debug] Command[3] CRC Value : 9641
2022-2-8 18:42:46 [debug] Command[3] CRC Ok
2022-2-8 18:42:46 [verbose] Command[3] inCryptTest enabled, emitting response without checks
2022-2-8 18:42:46 [debug] Command[3] SendCommand receive this response : N05
2022-2-8 18:42:46 [debug] cryptTableTester response: N05
2022-2-8 18:42:46 [verbose] Command[4] Sending Command: CUSTLST?
2022-2-8 18:42:46 [debug] Command[4] Writing command buffer to socket: [2,17,50,49,72,66,124,10,241,41,160,215,199,153,0,183,61,3]
2022-2-8 18:42:46 [debug] Command[4] Data Sent : CUSTLST?
2022-2-8 18:42:46 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,55,53,88,68,123,10,128,87,217,197,253,140,111,168,38,59,0,119,152,70,251,128,77,128,44,228,224,3]
2022-2-8 18:42:46 [debug] Received data Buffer : [2,17,55,53,88,68,123,10,128,87,217,197,253,140,111,168,38,59,0,119,152,70,251,128,77,128,44,228,224,3]
2022-2-8 18:42:46 [debug] Command[50] CRC Value : 4D4A
2022-2-8 18:42:46 [debug] Command[50] CRC Ok
2022-2-8 18:42:46 [verbose] Command[50] inCryptTest enabled, emitting response without checks
2022-2-8 18:42:46 [debug] Command[4] SendCommand receive this response : SSTT=---------------
2022-2-8 18:42:46 [debug] cryptTableTester response: SSTT=---------------
2022-2-8 18:42:46 [verbose] Connection to the control panel successfully established.
2022-2-8 18:42:46 [debug] Risco Panel Connected.
2022-2-8 18:42:46 [verbose] Command[5] Sending Command: PNLCNF
2022-2-8 18:42:46 [debug] Command[5] Writing command buffer to socket: [2,17,50,48,91,89,99,29,243,60,227,216,226,229,118,3]
2022-2-8 18:42:46 [debug] Command[5] Data Sent : PNLCNF
2022-2-8 18:42:46 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,50,49,69,39,26,73,136,76,178,220,3]
2022-2-8 18:42:46 [debug] Received data Buffer : [2,17,50,49,69,39,26,73,136,76,178,220,3]
2022-2-8 18:42:46 [debug] Command[4] CRC Value : 56F4
2022-2-8 18:42:46 [debug] Command[4] CRC Ok
2022-2-8 18:42:46 [debug] Command[4] Command response from Panel
2022-2-8 18:42:46 [warn] Command[4] Command response was unexpected, ignoring. Data[N05]. sequenceId[5]
2022-2-8 18:42:46 [verbose] Command[4] Received data from panel: N05
2022-2-8 18:42:46 [warn] Command[4] Receipt of an error code: Invalid parameter
2022-2-8 18:42:46 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,50,48,91,89,99,29,243,60,201,186,135,145,113,183,49,32,28,98,227,44,155,228,77,241,80,147,151,3]
2022-2-8 18:42:46 [debug] Received data Buffer : [2,17,50,48,91,89,99,29,243,60,201,186,135,145,113,183,49,32,28,98,227,44,155,228,77,241,80,147,151,3]
2022-2-8 18:42:46 [debug] Command[5] CRC Value : E8C6
2022-2-8 18:42:46 [debug] Command[5] CRC Ok
2022-2-8 18:42:46 [debug] Command[5] Command response from Panel
2022-2-8 18:42:46 [debug] Command[5] Emitting expected command response
2022-2-8 18:42:46 [verbose] Command[5] Received data from panel: PNLCNF=RW032:618VGMI
2022-2-8 18:42:46 [debug] Command[5] SendCommand receive this response : PNLCNF=RW032:618VGMI
(node:20806) UnhandledPromiseRejectionWarning: Error: Unsupported panel type : RW032:618VGMI
    at RiscoComm.<anonymous> (/root/risco/node_modules/@vanackej/risco-lan-bridge/dist/RiscoComm.js:354:27)
    at Generator.next (<anonymous>)
    at fulfilled (/root/risco/node_modules/tslib/tslib.js:114:62)
(node:20806) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:20806) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
2022-2-8 18:42:47 [info] MQTT reconnect
2022-2-8 18:42:47 [info] MQTT close
2022-2-8 18:42:48 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,55,52,91,68,123,10,140,71,217,197,253,140,111,168,38,59,127,119,240,70,251,186,30,240,90,147,3]
2022-2-8 18:42:48 [debug] Received data Buffer : [2,17,55,52,91,68,123,10,140,71,217,197,253,140,111,168,38,59,127,119,240,70,251,186,30,240,90,147,3]
2022-2-8 18:42:48 [debug] Command[51] CRC Value : DD2C
2022-2-8 18:42:48 [debug] Command[51] CRC Ok
2022-2-8 18:42:48 [debug] Command[51] Data from Panel, need to send an ACK.
2022-2-8 18:42:48 [debug] Command[51] Sending Ack.
2022-2-8 18:42:48 [verbose] Command[51] Received data from panel: PSTT1=--------R-E--
2022-2-8 18:42:48 [debug] Command[51] Data type: Partition Status
2022-2-8 18:42:49 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,55,55,91,68,123,10,143,71,217,197,253,140,111,168,38,59,0,119,152,70,251,186,24,132,92,232,3]
2022-2-8 18:42:49 [debug] Received data Buffer : [2,17,55,55,91,68,123,10,143,71,217,197,253,140,111,168,38,59,0,119,152,70,251,186,24,132,92,232,3]
2022-2-8 18:42:49 [debug] Command[52] CRC Value : B048
2022-2-8 18:42:49 [debug] Command[52] CRC Ok
2022-2-8 18:42:49 [debug] Command[52] Data from Panel, need to send an ACK.
2022-2-8 18:42:49 [debug] Command[52] Sending Ack.
2022-2-8 18:42:49 [verbose] Command[52] Received data from panel: PSTT2=-------------
2022-2-8 18:42:49 [debug] Command[52] Data type: Partition Status
2022-2-8 18:42:49 [error] Panel Socket Closed.
2022-2-8 18:42:49 [debug] RiscoCloud Socket Destroyed.
2022-2-8 18:42:49 [error] TCP Socket Disconnected
2022-2-8 18:42:52 [info] MQTT reconnect
2022-2-8 18:42:52 [info] MQTT close
2022-2-8 18:42:57 [info] MQTT reconnect
2022-2-8 18:42:57 [info] MQTT close
2022-2-8 18:42:59 [verbose] Start Connection to Panel
2022-2-8 18:42:59 [debug] TCP Socket is already created, Connect It
2022-2-8 18:42:59 [debug] TCP Socket must be created now
2022-2-8 18:42:59 [info] Listening on IP :: and Port 33000
2022-2-8 18:42:59 [info] Waiting for panel incoming connection... This can take up to 1 or 2 minutes
2022-2-8 18:43:02 [info] MQTT reconnect
2022-2-8 18:43:02 [info] MQTT close
2022-2-8 18:43:04 [info] Incoming connection from panel received
2022-2-8 18:43:04 [debug] RiscoCloud Socket: connect
2022-2-8 18:43:04 [info] RiscoCloud Socket: ready
2022-2-8 18:43:04 [info] Setting a timer for panel connection in 30000 ms
2022-2-8 18:43:04 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,55,54,91,68,123,10,142,71,217,197,253,140,111,168,38,59,0,119,152,70,251,186,28,133,81,233,3]
2022-2-8 18:43:04 [debug] Received data Buffer : [2,17,55,54,91,68,123,10,142,71,217,197,253,140,111,168,38,59,0,119,152,70,251,186,28,133,81,233,3]
2022-2-8 18:43:04 [debug] Command[53] CRC Value : F199
2022-2-8 18:43:04 [debug] Command[53] CRC Ok
2022-2-8 18:43:04 [debug] Command[53] Data from Panel, need to send an ACK.
2022-2-8 18:43:04 [debug] Command[53] Sending Ack.
2022-2-8 18:43:04 [verbose] Command[53] Received data from panel: PSTT3=-------------
2022-2-8 18:43:04 [debug] Command[53] Data type: Partition Status
2022-2-8 18:43:06 [debug] [Panel => Cloud] Forwarding panel packet to cloud: [2,19,55,55,4,81,0,16,3,0,50,50,52,48,48,52,49,49,57,55,48,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,0,0,23,23,69,76,5,20,1,255,255,255,255,255,255,48,16,2,1,0,0,0,0,5,55,43,41,66,0,0,16,2,15,49,57,50,46,49,54,56,46,49,48,48,46,49,56,50,1,23,55,66,49,65,3]
2022-2-8 18:43:07 [info] MQTT reconnect
2022-2-8 18:43:07 [info] MQTT close
2022-2-8 18:43:12 [info] MQTT reconnect
2022-2-8 18:43:12 [info] MQTT close
2022-2-8 18:43:17 [info] MQTT reconnect
2022-2-8 18:43:17 [info] MQTT close
2022-2-8 18:43:22 [info] MQTT reconnect
2022-2-8 18:43:22 [info] MQTT close
2022-2-8 18:43:27 [info] MQTT reconnect
2022-2-8 18:43:27 [info] MQTT close
2022-2-8 18:43:32 [info] MQTT reconnect
2022-2-8 18:43:32 [info] MQTT close
2022-2-8 18:43:34 [verbose] Authenticating to the panel
2022-2-8 18:43:34 [verbose] Command[6] Sending Command: RMT=5678
2022-2-8 18:43:34 [debug] Command[6] Writing command buffer to socket: [2,17,50,51,89,90,123,99,136,76,195,208,199,151,16,3,177,50,3]
2022-2-8 18:43:34 [debug] Command[6] Data Sent : RMT=5678
2022-2-8 18:43:34 [debug] [Panel => Bridge] Received unencrypted data Buffer from Panel : [2,48,54,65,67,75,23,70,57,53,69,3]
2022-2-8 18:43:34 [debug] Received data Buffer : [2,48,54,65,67,75,23,70,57,53,69,3]
2022-2-8 18:43:34 [debug] Command[6] CRC Value : F95E
2022-2-8 18:43:34 [debug] Command[6] CRC Ok
2022-2-8 18:43:34 [debug] Command[6] Command response from Panel
2022-2-8 18:43:34 [debug] Command[6] Emitting expected command response
2022-2-8 18:43:34 [verbose] Command[6] Received data from panel: ACK
2022-2-8 18:43:34 [debug] Command[6] SendCommand receive this response : ACK
2022-2-8 18:43:34 [verbose] Command[7] Sending Command: LCL
2022-2-8 18:43:34 [debug] Command[7] Writing command buffer to socket: [2,48,55,76,67,76,23,65,53,54,51,3]
2022-2-8 18:43:34 [debug] Command[7] Data Sent : LCL
2022-2-8 18:43:34 [debug] [Panel => Bridge] Received unencrypted data Buffer from Panel : [2,48,55,65,67,75,23,51,57,54,51,3]
2022-2-8 18:43:34 [debug] Received data Buffer : [2,48,55,65,67,75,23,51,57,54,51,3]
2022-2-8 18:43:34 [debug] Command[7] CRC Value : 3963
2022-2-8 18:43:34 [debug] Command[7] CRC Ok
2022-2-8 18:43:34 [debug] Command[7] Command response from Panel
2022-2-8 18:43:34 [debug] Command[7] Emitting expected command response
2022-2-8 18:43:34 [verbose] Command[7] Received data from panel: ACK
2022-2-8 18:43:34 [debug] Command[7] SendCommand receive this response : ACK
2022-2-8 18:43:34 [debug] LCL command result OK
2022-2-8 18:43:34 [verbose] Setting up encryption using Panel Id
2022-2-8 18:43:34 [verbose] Command[8] Sending Command: CUSTLST?
2022-2-8 18:43:34 [debug] Command[8] Writing command buffer to socket: [2,17,50,61,72,66,124,10,241,41,160,215,199,227,118,192,61,3]
2022-2-8 18:43:34 [debug] Command[8] Data Sent : CUSTLST?
2022-2-8 18:43:35 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,50,61,69,39,26,73,136,77,177,220,3]
2022-2-8 18:43:35 [debug] Received data Buffer : [2,17,50,61,69,39,26,73,136,77,177,220,3]
2022-2-8 18:43:35 [debug] Command[8] CRC Value : 57E4
2022-2-8 18:43:35 [debug] Command[8] CRC Ok
2022-2-8 18:43:35 [verbose] Command[8] inCryptTest enabled, emitting response without checks
2022-2-8 18:43:35 [debug] Command[8] SendCommand receive this response : N05
2022-2-8 18:43:35 [debug] cryptTableTester response: N05
2022-2-8 18:43:35 [verbose] Command[9] Sending Command: CUSTLST?
2022-2-8 18:43:35 [debug] Command[9] Writing command buffer to socket: [2,17,50,60,72,66,124,10,241,41,160,215,199,150,115,199,60,3]
2022-2-8 18:43:35 [debug] Command[9] Data Sent : CUSTLST?
2022-2-8 18:43:35 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,55,49,81,68,123,10,140,71,217,197,253,140,111,168,38,59,0,119,162,83,148,235,107,3]
2022-2-8 18:43:35 [debug] Received data Buffer : [2,17,55,49,81,68,123,10,140,71,217,197,253,140,111,168,38,59,0,119,162,83,148,235,107,3]
2022-2-8 18:43:35 [debug] Command[54] CRC Value : 8BF1
2022-2-8 18:43:35 [debug] Command[54] CRC Ok
2022-2-8 18:43:35 [verbose] Command[54] inCryptTest enabled, emitting response without checks
2022-2-8 18:43:35 [debug] Command[9] SendCommand receive this response : ZSTT1=----------
2022-2-8 18:43:35 [debug] cryptTableTester response: ZSTT1=----------
2022-2-8 18:43:35 [verbose] Connection to the control panel successfully established.
2022-2-8 18:43:35 [debug] Risco Panel Connected.
2022-2-8 18:43:35 [verbose] Command[10] Sending Command: PNLCNF
2022-2-8 18:43:35 [debug] Command[10] Writing command buffer to socket: [2,17,51,53,91,89,99,29,243,60,227,169,148,144,123,3]
2022-2-8 18:43:35 [debug] Command[10] Data Sent : PNLCNF
2022-2-8 18:43:35 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,50,60,69,39,26,73,132,77,176,209,3]
2022-2-8 18:43:35 [debug] Received data Buffer : [2,17,50,60,69,39,26,73,132,77,176,209,3]
2022-2-8 18:43:35 [debug] Command[9] CRC Value : 97D9
2022-2-8 18:43:35 [debug] Command[9] CRC Ok
2022-2-8 18:43:35 [debug] Command[9] Command response from Panel
2022-2-8 18:43:35 [warn] Command[9] Command response was unexpected, ignoring. Data[N05]. sequenceId[10]
2022-2-8 18:43:35 [verbose] Command[9] Received data from panel: N05
2022-2-8 18:43:35 [warn] Command[9] Receipt of an error code: Invalid parameter
2022-2-8 18:43:35 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,51,53,91,89,99,29,243,60,201,186,135,145,113,183,49,32,28,98,227,44,155,228,77,128,42,233,228,3]
2022-2-8 18:43:35 [debug] Received data Buffer : [2,17,51,53,91,89,99,29,243,60,201,186,135,145,113,183,49,32,28,98,227,44,155,228,77,128,42,233,228,3]
2022-2-8 18:43:35 [debug] Command[10] CRC Value : 4B9E
2022-2-8 18:43:35 [debug] Command[10] CRC Ok
2022-2-8 18:43:35 [debug] Command[10] Command response from Panel
2022-2-8 18:43:35 [debug] Command[10] Emitting expected command response
2022-2-8 18:43:35 [verbose] Command[10] Received data from panel: PNLCNF=RW032:618VGMI
2022-2-8 18:43:35 [debug] Command[10] SendCommand receive this response : PNLCNF=RW032:618VGMI
(node:20806) UnhandledPromiseRejectionWarning: Error: Unsupported panel type : RW032:618VGMI
    at RiscoComm.<anonymous> (/root/risco/node_modules/@vanackej/risco-lan-bridge/dist/RiscoComm.js:354:27)
    at Generator.next (<anonymous>)
    at fulfilled (/root/risco/node_modules/tslib/tslib.js:114:62)
(node:20806) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
2022-2-8 18:43:36 [error] Panel Socket Closed.
2022-2-8 18:43:36 [debug] RiscoCloud Socket Destroyed.
2022-2-8 18:43:36 [error] TCP Socket Disconnected
2022-2-8 18:43:37 [info] MQTT reconnect
2022-2-8 18:43:37 [info] MQTT close
2022-2-8 18:43:42 [info] MQTT reconnect
2022-2-8 18:43:42 [info] MQTT close
2022-2-8 18:43:46 [verbose] Start Connection to Panel
2022-2-8 18:43:46 [debug] TCP Socket is already created, Connect It
2022-2-8 18:43:46 [debug] TCP Socket must be created now
2022-2-8 18:43:46 [info] Listening on IP :: and Port 33000
2022-2-8 18:43:46 [info] Waiting for panel incoming connection... This can take up to 1 or 2 minutes
2022-2-8 18:43:47 [info] MQTT reconnect
2022-2-8 18:43:47 [info] MQTT close
2022-2-8 18:43:51 [info] Incoming connection from panel received
2022-2-8 18:43:51 [debug] RiscoCloud Socket: connect
2022-2-8 18:43:51 [info] RiscoCloud Socket: ready
2022-2-8 18:43:51 [info] Setting a timer for panel connection in 30000 ms
2022-2-8 18:43:52 [info] MQTT reconnect
2022-2-8 18:43:52 [info] MQTT close
2022-2-8 18:43:57 [info] MQTT reconnect
2022-2-8 18:43:57 [info] MQTT close
2022-2-8 18:43:58 [debug] [Panel => Cloud] Forwarding panel packet to cloud: [2,19,55,55,4,81,0,16,3,0,50,50,52,48,48,52,49,49,57,55,48,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,0,0,23,23,69,76,5,20,1,255,255,255,255,255,255,48,16,2,1,0,0,0,0,5,55,43,41,66,0,0,16,2,15,49,57,50,46,49,54,56,46,49,48,48,46,49,56,50,1,23,55,66,49,65,3]
2022-2-8 18:44:02 [info] MQTT reconnect
2022-2-8 18:44:02 [info] MQTT close
2022-2-8 18:44:07 [info] MQTT reconnect
2022-2-8 18:44:07 [info] MQTT close
2022-2-8 18:44:12 [info] MQTT reconnect
2022-2-8 18:44:12 [info] MQTT close
2022-2-8 18:44:17 [info] MQTT reconnect
2022-2-8 18:44:17 [info] MQTT close
2022-2-8 18:44:21 [verbose] Authenticating to the panel
2022-2-8 18:44:21 [verbose] Command[11] Sending Command: RMT=5678
2022-2-8 18:44:21 [debug] Command[11] Writing command buffer to socket: [2,17,51,52,89,90,123,99,136,76,195,208,199,149,1,195,72,3]
2022-2-8 18:44:21 [debug] Command[11] Data Sent : RMT=5678
2022-2-8 18:44:21 [debug] [Panel => Bridge] Received unencrypted data Buffer from Panel : [2,49,49,65,67,75,23,69,56,69,65,3]
2022-2-8 18:44:21 [debug] Received data Buffer : [2,49,49,65,67,75,23,69,56,69,65,3]
2022-2-8 18:44:21 [debug] Command[11] CRC Value : E8EA
2022-2-8 18:44:21 [debug] Command[11] CRC Ok
2022-2-8 18:44:21 [debug] Command[11] Command response from Panel
2022-2-8 18:44:21 [debug] Command[11] Emitting expected command response
2022-2-8 18:44:21 [verbose] Command[11] Received data from panel: ACK
2022-2-8 18:44:21 [debug] Command[11] SendCommand receive this response : ACK
2022-2-8 18:44:21 [verbose] Command[12] Sending Command: LCL
2022-2-8 18:44:21 [debug] Command[12] Writing command buffer to socket: [2,49,50,76,67,76,23,55,52,65,69,3]
2022-2-8 18:44:21 [debug] Command[12] Data Sent : LCL
2022-2-8 18:44:22 [debug] [Panel => Bridge] Received unencrypted data Buffer from Panel : [2,49,50,65,67,75,23,69,56,65,69,3]
2022-2-8 18:44:22 [debug] Received data Buffer : [2,49,50,65,67,75,23,69,56,65,69,3]
2022-2-8 18:44:22 [debug] Command[12] CRC Value : E8AE
2022-2-8 18:44:22 [debug] Command[12] CRC Ok
2022-2-8 18:44:22 [debug] Command[12] Command response from Panel
2022-2-8 18:44:22 [debug] Command[12] Emitting expected command response
2022-2-8 18:44:22 [verbose] Command[12] Received data from panel: ACK
2022-2-8 18:44:22 [debug] Command[12] SendCommand receive this response : ACK
2022-2-8 18:44:22 [debug] LCL command result OK
2022-2-8 18:44:22 [verbose] Setting up encryption using Panel Id
2022-2-8 18:44:22 [verbose] Command[13] Sending Command: CUSTLST?
2022-2-8 18:44:22 [debug] Command[13] Writing command buffer to socket: [2,17,51,54,72,66,124,10,241,41,160,215,199,224,6,188,56,3]
2022-2-8 18:44:22 [debug] Command[13] Data Sent : CUSTLST?
2022-2-8 18:44:22 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,55,49,81,68,123,10,140,71,217,197,253,140,111,168,38,59,0,119,162,83,148,235,107,3]
2022-2-8 18:44:22 [debug] Received data Buffer : [2,17,55,49,81,68,123,10,140,71,217,197,253,140,111,168,38,59,0,119,162,83,148,235,107,3]
2022-2-8 18:44:22 [debug] Command[54] CRC Value : 8BF1
2022-2-8 18:44:22 [debug] Command[54] CRC Ok
2022-2-8 18:44:22 [verbose] Command[54] inCryptTest enabled, emitting response without checks
2022-2-8 18:44:22 [debug] Command[13] SendCommand receive this response : ZSTT1=----------
2022-2-8 18:44:22 [debug] cryptTableTester response: ZSTT1=----------
2022-2-8 18:44:22 [verbose] Connection to the control panel successfully established.
2022-2-8 18:44:22 [debug] Risco Panel Connected.
2022-2-8 18:44:22 [verbose] Command[14] Sending Command: PNLCNF
2022-2-8 18:44:22 [debug] Command[14] Writing command buffer to socket: [2,17,51,49,91,89,99,29,243,60,227,221,149,144,122,3]
2022-2-8 18:44:22 [debug] Command[14] Data Sent : PNLCNF
2022-2-8 18:44:22 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,51,54,69,39,26,73,137,77,192,216,3]
2022-2-8 18:44:22 [debug] Received data Buffer : [2,17,51,54,69,39,26,73,137,77,192,216,3]
2022-2-8 18:44:22 [debug] Command[13] CRC Value : 4740
2022-2-8 18:44:22 [debug] Command[13] CRC Ok
2022-2-8 18:44:22 [debug] Command[13] Command response from Panel
2022-2-8 18:44:22 [warn] Command[13] Command response was unexpected, ignoring. Data[N05]. sequenceId[14]
2022-2-8 18:44:22 [verbose] Command[13] Received data from panel: N05
2022-2-8 18:44:22 [warn] Command[13] Receipt of an error code: Invalid parameter
2022-2-8 18:44:22 [info] MQTT reconnect
2022-2-8 18:44:22 [info] MQTT close
2022-2-8 18:44:22 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,51,49,91,89,99,29,243,60,201,186,135,145,113,183,49,32,28,98,227,44,155,228,77,246,80,148,227,3]
2022-2-8 18:44:22 [debug] Received data Buffer : [2,17,51,49,91,89,99,29,243,60,201,186,135,145,113,183,49,32,28,98,227,44,155,228,77,246,80,148,227,3]
2022-2-8 18:44:22 [debug] Command[14] CRC Value : B8DB
2022-2-8 18:44:22 [debug] Command[14] CRC Ok
2022-2-8 18:44:22 [debug] Command[14] Command response from Panel
2022-2-8 18:44:22 [debug] Command[14] Emitting expected command response
2022-2-8 18:44:22 [verbose] Command[14] Received data from panel: PNLCNF=RW032:618VGMI
2022-2-8 18:44:22 [debug] Command[14] SendCommand receive this response : PNLCNF=RW032:618VGMI
(node:20806) UnhandledPromiseRejectionWarning: Error: Unsupported panel type : RW032:618VGMI
    at RiscoComm.<anonymous> (/root/risco/node_modules/@vanackej/risco-lan-bridge/dist/RiscoComm.js:354:27)
    at Generator.next (<anonymous>)
    at fulfilled (/root/risco/node_modules/tslib/tslib.js:114:62)
(node:20806) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
2022-2-8 18:44:24 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,55,49,81,68,123,10,140,71,217,197,253,140,111,168,38,59,0,119,162,83,148,235,107,3]
2022-2-8 18:44:24 [debug] Received data Buffer : [2,17,55,49,81,68,123,10,140,71,217,197,253,140,111,168,38,59,0,119,162,83,148,235,107,3]
2022-2-8 18:44:24 [debug] Command[54] CRC Value : 8BF1
2022-2-8 18:44:24 [debug] Command[54] CRC Ok
2022-2-8 18:44:24 [debug] Command[54] Data from Panel, need to send an ACK.
2022-2-8 18:44:24 [debug] Command[54] Sending Ack.
2022-2-8 18:44:24 [verbose] Command[54] Received data from panel: ZSTT1=----------
2022-2-8 18:44:24 [debug] Command[54] Data type: Zone Status
2022-2-8 18:44:25 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,55,48,81,68,123,10,143,71,217,197,253,140,111,168,38,59,0,119,162,41,226,236,111,3]
2022-2-8 18:44:25 [debug] Received data Buffer : [2,17,55,48,81,68,123,10,143,71,217,197,253,140,111,168,38,59,0,119,162,41,226,236,111,3]
2022-2-8 18:44:25 [debug] Command[55] CRC Value : B4A5
2022-2-8 18:44:25 [debug] Command[55] CRC Ok
2022-2-8 18:44:25 [debug] Command[55] Data from Panel, need to send an ACK.
2022-2-8 18:44:25 [debug] Command[55] Sending Ack.
2022-2-8 18:44:25 [verbose] Command[55] Received data from panel: ZSTT2=----------
2022-2-8 18:44:25 [debug] Command[55] Data type: Zone Status
2022-2-8 18:44:25 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,55,51,81,68,123,10,142,71,217,197,253,140,111,168,38,59,0,119,162,92,231,152,109,3]
2022-2-8 18:44:25 [debug] Received data Buffer : [2,17,55,51,81,68,123,10,142,71,217,197,253,140,111,168,38,59,0,119,162,92,231,152,109,3]
2022-2-8 18:44:25 [debug] Command[56] CRC Value : 7157
2022-2-8 18:44:25 [debug] Command[56] CRC Ok
2022-2-8 18:44:25 [debug] Command[56] Data from Panel, need to send an ACK.
2022-2-8 18:44:25 [debug] Command[56] Sending Ack.
2022-2-8 18:44:25 [verbose] Command[56] Received data from panel: ZSTT3=----------
2022-2-8 18:44:25 [debug] Command[56] Data type: Zone Status
2022-2-8 18:44:25 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,55,50,81,68,123,10,137,71,217,197,253,140,111,168,38,59,0,119,162,40,151,157,30,3]
2022-2-8 18:44:25 [debug] Received data Buffer : [2,17,55,50,81,68,123,10,137,71,217,197,253,140,111,168,38,59,0,119,162,40,151,157,30,3]
2022-2-8 18:44:25 [debug] Command[57] CRC Value : CA0D
2022-2-8 18:44:25 [debug] Command[57] CRC Ok
2022-2-8 18:44:25 [debug] Command[57] Data from Panel, need to send an ACK.
2022-2-8 18:44:25 [debug] Command[57] Sending Ack.
2022-2-8 18:44:25 [verbose] Command[57] Received data from panel: ZSTT4=----------
2022-2-8 18:44:25 [debug] Command[57] Data type: Zone Status
2022-2-8 18:44:25 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,55,61,81,68,123,10,136,71,217,197,253,140,111,168,38,59,0,119,162,94,149,158,25,3]
2022-2-8 18:44:25 [debug] Received data Buffer : [2,17,55,61,81,68,123,10,136,71,217,197,253,140,111,168,38,59,0,119,162,94,149,158,25,3]
2022-2-8 18:44:25 [debug] Command[58] CRC Value : 5C3C
2022-2-8 18:44:25 [debug] Command[58] CRC Ok
2022-2-8 18:44:25 [debug] Command[58] Data from Panel, need to send an ACK.
2022-2-8 18:44:25 [debug] Command[58] Sending Ack.
2022-2-8 18:44:25 [verbose] Command[58] Received data from panel: ZSTT5=----------
2022-2-8 18:44:25 [debug] Command[58] Data type: Zone Status
2022-2-8 18:44:26 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,55,60,81,68,123,10,139,71,217,197,253,140,111,168,38,59,0,119,162,93,229,155,98,3]
2022-2-8 18:44:26 [debug] Received data Buffer : [2,17,55,60,81,68,123,10,139,71,217,197,253,140,111,168,38,59,0,119,162,93,229,155,98,3]
2022-2-8 18:44:26 [debug] Command[59] CRC Value : 6368
2022-2-8 18:44:26 [debug] Command[59] CRC Ok
2022-2-8 18:44:26 [debug] Command[59] Data from Panel, need to send an ACK.
2022-2-8 18:44:26 [debug] Command[59] Sending Ack.
2022-2-8 18:44:26 [verbose] Command[59] Received data from panel: ZSTT6=----------
2022-2-8 18:44:26 [debug] Command[59] Data type: Zone Status
2022-2-8 18:44:26 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,52,53,81,68,123,10,138,71,217,197,253,140,111,168,38,59,0,119,162,88,238,235,30,3]
2022-2-8 18:44:26 [debug] Received data Buffer : [2,17,52,53,81,68,123,10,138,71,217,197,253,140,111,168,38,59,0,119,162,88,238,235,30,3]
2022-2-8 18:44:26 [debug] Command[60] CRC Value : 38FD
2022-2-8 18:44:26 [debug] Command[60] CRC Ok
2022-2-8 18:44:26 [debug] Command[60] Data from Panel, need to send an ACK.
2022-2-8 18:44:26 [debug] Command[60] Sending Ack.
2022-2-8 18:44:26 [verbose] Command[60] Received data from panel: ZSTT7=----------
2022-2-8 18:44:26 [debug] Command[60] Data type: Zone Status
2022-2-8 18:44:26 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,52,52,81,68,123,10,133,71,217,197,253,140,111,168,38,59,0,119,162,40,148,239,98,3]
2022-2-8 18:44:26 [debug] Received data Buffer : [2,17,52,52,81,68,123,10,133,71,217,197,253,140,111,168,38,59,0,119,162,40,148,239,98,3]
2022-2-8 18:44:26 [debug] Command[61] CRC Value : CBB8
2022-2-8 18:44:26 [debug] Command[61] CRC Ok
2022-2-8 18:44:26 [debug] Command[61] Data from Panel, need to send an ACK.
2022-2-8 18:44:26 [debug] Command[61] Sending Ack.
2022-2-8 18:44:26 [verbose] Command[61] Received data from panel: ZSTT8=----------
2022-2-8 18:44:26 [debug] Command[61] Data type: Zone Status
2022-2-8 18:44:26 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,52,55,81,68,123,10,132,71,217,197,253,140,111,168,38,59,0,119,162,91,147,153,27,3]
2022-2-8 18:44:26 [debug] Received data Buffer : [2,17,52,55,81,68,123,10,132,71,217,197,253,140,111,168,38,59,0,119,162,91,147,153,27,3]
2022-2-8 18:44:26 [debug] Command[62] CRC Value : 0E4A
2022-2-8 18:44:26 [debug] Command[62] CRC Ok
2022-2-8 18:44:26 [debug] Command[62] Data from Panel, need to send an ACK.
2022-2-8 18:44:26 [debug] Command[62] Sending Ack.
2022-2-8 18:44:26 [verbose] Command[62] Received data from panel: ZSTT9=----------
2022-2-8 18:44:26 [debug] Command[62] Data type: Zone Status
2022-2-8 18:44:27 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,52,54,81,68,123,10,140,74,201,197,253,140,111,168,38,59,0,119,152,124,146,235,105,246,3]
2022-2-8 18:44:27 [debug] Received data Buffer : [2,17,52,54,81,68,123,10,140,74,201,197,253,140,111,168,38,59,0,119,152,124,146,235,105,246,3]
2022-2-8 18:44:27 [debug] Command[63] CRC Value : DF3B
2022-2-8 18:44:27 [debug] Command[63] CRC Ok
2022-2-8 18:44:27 [debug] Command[63] Data from Panel, need to send an ACK.
2022-2-8 18:44:27 [debug] Command[63] Sending Ack.
2022-2-8 18:44:27 [verbose] Command[63] Received data from panel: ZSTT10=----------
2022-2-8 18:44:27 [debug] Command[63] Data type: Zone Status
2022-2-8 18:44:27 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,52,49,81,68,123,10,140,75,201,197,253,140,111,168,38,59,0,119,152,124,228,236,98,247,3]
2022-2-8 18:44:27 [debug] Received data Buffer : [2,17,52,49,81,68,123,10,140,75,201,197,253,140,111,168,38,59,0,119,152,124,228,236,98,247,3]
2022-2-8 18:44:27 [debug] Command[64] CRC Value : 2A8C
2022-2-8 18:44:27 [debug] Command[64] CRC Ok
2022-2-8 18:44:27 [debug] Command[64] Data from Panel, need to send an ACK.
2022-2-8 18:44:27 [debug] Command[64] Sending Ack.
2022-2-8 18:44:27 [verbose] Command[64] Received data from panel: ZSTT11=----------
2022-2-8 18:44:27 [debug] Command[64] Data type: Zone Status
2022-2-8 18:44:27 [info] MQTT reconnect
2022-2-8 18:44:27 [info] MQTT close
2022-2-8 18:44:27 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,52,48,81,68,123,10,140,72,201,197,253,140,111,168,38,59,0,119,152,124,231,152,24,128,3]
2022-2-8 18:44:27 [debug] Received data Buffer : [2,17,52,48,81,68,123,10,140,72,201,197,253,140,111,168,38,59,0,119,152,124,231,152,24,128,3]
2022-2-8 18:44:27 [debug] Command[65] CRC Value : 15B4
2022-2-8 18:44:27 [debug] Command[65] CRC Ok
2022-2-8 18:44:27 [debug] Command[65] Data from Panel, need to send an ACK.
2022-2-8 18:44:27 [debug] Command[65] Sending Ack.
2022-2-8 18:44:27 [verbose] Command[65] Received data from panel: ZSTT12=----------
2022-2-8 18:44:27 [debug] Command[65] Data type: Zone Status
2022-2-8 18:44:27 [debug] [Panel => Bridge] Received encrypted data Buffer from Panel : [2,17,52,51,81,68,123,10,140,73,201,197,253,140,111,168,38,59,0,119,152,124,146,157,28,134,3]
2022-2-8 18:44:27 [debug] Received data Buffer : [2,17,52,51,81,68,123,10,140,73,201,197,253,140,111,168,38,59,0,119,152,124,146,157,28,134,3]
2022-2-8 18:44:27 [debug] Command[66] CRC Value : D0F2
2022-2-8 18:44:27 [debug] Command[66] CRC Ok
2022-2-8 18:44:27 [debug] Command[66] Data from Panel, need to send an ACK.
2022-2-8 18:44:27 [debug] Command[66] Sending Ack.
2022-2-8 18:44:27 [verbose] Command[66] Received data from panel: ZSTT13=----------
2022-2-8 18:44:27 [debug] Command[66] Data type: Zone Status
2022-2-8 18:44:28 [error] Panel Socket Closed.
2022-2-8 18:44:28 [debug] RiscoCloud Socket Destroyed.
2022-2-8 18:44:28 [error] TCP Socket Disconnected
2022-2-8 18:44:32 [info] MQTT reconnect
2022-2-8 18:44:32 [info] MQTT close
2022-2-8 18:44:37 [info] MQTT reconnect
2022-2-8 18:44:37 [info] MQTT close
2022-2-8 18:44:38 [verbose] Start Connection to Panel
2022-2-8 18:44:38 [debug] TCP Socket is already created, Connect It
2022-2-8 18:44:38 [debug] TCP Socket must be created now
2022-2-8 18:44:38 [info] Listening on IP :: and Port 33000
2022-2-8 18:44:38 [info] Waiting for panel incoming connection... This can take up to 1 or 2 minutes
2022-2-8 18:44:42 [info] MQTT reconnect

The panel does not appear to be supported...
Error: Unsupported panel type : RW032:618VGMI
Thanks for your return,
Cheers

try :<PHONE_NUMBER>7

For information, the support tells me the same password.
I will try the update soon.
Thanks @pergolafabio

dont think an software update will help :-)
worth a try

Salutations,
it also gives me the same error:
/usr/src/app/node_modules/@vanackej/risco-lan-bridge/dist/RiscoComm.js:344
throw new Error(Unsupported panel type : ${panelType});
^
Error: Unsupported panel type : RW032:618V-MI
The alarm is a Agility4.
Thanks

I don't know if the issue is similar to yours @teruggim but I see a disconnect here too..
2/16/2022, 9:26:54 PM [debug] Local GMT Timezone is : +00:00
2/16/2022, 9:26:54 PM [info] autoConnect enabled, starting communication
2/16/2022, 9:26:54 PM [verbose] Start Connection to Panel
2/16/2022, 9:26:54 PM [debug] TCP Socket is not already created, Create It
2/16/2022, 9:26:54 PM [debug] TCP Socket must be created now
2/16/2022, 9:26:54 PM [info] Connecting to mqtt server: mqtt://<IP_ADDRESS>:1883
2/16/2022, 9:26:54 PM [info] Connected on mqtt server: mqtt://<IP_ADDRESS>:1883
2/16/2022, 9:26:54 PM [info] Panel is not connected, waiting
2/16/2022, 9:27:24 PM [error] Socket Timeout.
2/16/2022, 9:27:24 PM [debug] Socket Destroyed.
2/16/2022, 9:27:24 PM [error] TCP Socket Disconnected
2/16/2022, 9:27:24 PM [debug] Socket Disconnected.
2/16/2022, 9:27:34 PM [verbose] Start Connection to Panel
2/16/2022, 9:27:34 PM [debug] TCP Socket is already created, Connect It
2/16/2022, 9:27:34 PM [debug] TCP Socket must be created now
2/16/2022, 9:28:04 PM [error] Socket Timeout.
2/16/2022, 9:28:04 PM [debug] Socket Destroyed.
2/16/2022, 9:28:04 PM [error] TCP Socket Disconnected
2/16/2022, 9:28:04 PM [debug] Socket Disconnected.

As you can see it seems to not even get a connection to the panel. Currently my configuration looks the following:
    "log": "debug",
    "panel": {
      "panelIp": "<IP_ADDRESS>",
      "panelPort": 1000,
      "panelPassword": 1234,
      "panelId": 1,
      "watchDogInterval": 10000
    }

Am I missing something? (I've got a Lightsys 2 alarm but I didn't check which network card is being used atm)

Check your firmware, if you are on 2.73 or below, then you have the single socket module..
You need to disable cloud or use the proxy then

Check your firmware, if you are on 2.73 or below, then you have the single socket module.. You need to disable cloud or use the proxy then

Is there a way that I can check this firmware version myself or do I need my installer to check this? (My system is closed by the installer).

Maybe on the panel, maybe some about tab?
You can also check if the port is open

Also just ask the installer code, you bought it, it's your system.... What if that company quits or something happens with that person?  They need to give it to you, so you can at least change something..
You can also call Risco and ask to detach the panel from your installer, so you can manage yourself, or just ask your installer that you want to manage it on your own...
They need todo that, I also did it

Check your firmware, if you are on 2.73 or below, then you have the single socket module.. You need to disable cloud or use the proxy then

Is there a way that I can check this firmware version myself or do I need my installer to check this? (My system is closed by the installer).

Hello
You can found the information through Risco Configuration Sofware. ;-)

Good morning @pergolafabio ,
Is there any way to make Agility4 RW032: 618V-MI panel compatible?
Thanks

No idea

Check your firmware, if you are on 2.73 or below, then you have the single socket module.. You need to disable cloud or use the proxy then

Confirmed by installer that I've got the single socket module. So I either need to check the proxy approach or disable the cloud features indeed. Is there an elaborate documentation on how to configure the proxy stuff with this plugin? I only so the notice that I have to find some way to route the traffic to the MQTT module so far. :)
Thanks for the help so far!

Good morning @pergolafabio , Is there any way to make Agility4 RW032: 618V-MI panel compatible?
Thanks

Maybe @vanackej or @TJForc can help us?
Thanks again

Check your firmware, if you are on 2.73 or below, then you have the single socket module.. You need to disable cloud or use the proxy then

Confirmed by installer that I've got the single socket module. So I either need to check the proxy approach or disable the cloud features indeed. Is there an elaborate documentation on how to configure the proxy stuff with this plugin? I only so the notice that I have to find some way to route the traffic to the MQTT module so far. :)
Thanks for the help so far!

Yes, it's in the readme, just enable the proxy in the config JSON file... And then indeed disable cloud OR make a forward rule on your router by using Iptables if your router supports that.. I have an Asus router with custom firmware, I can make iptables

Check your firmware, if you are on 2.73 or below, then you have the single socket module.. You need to disable cloud or use the proxy then

Confirmed by installer that I've got the single socket module. So I either need to check the proxy approach or disable the cloud features indeed. Is there an elaborate documentation on how to configure the proxy stuff with this plugin? I only so the notice that I have to find some way to route the traffic to the MQTT module so far. :)
Thanks for the help so far!

Yes, it's in the readme, just enable the proxy in the config JSON file... And then indeed disable cloud OR make a forward rule on your router by using Iptables if your router supports that.. I have an Asus router with custom firmware, I can make iptables

@pergolafabio could you share your iptable route? :) I'm looking to see on which ports your targettting here..
set service nat rule 6700 description risco-alarm
set service nat rule 6700 destination port 33000
set service nat rule 6700 source address <IP_ADDRESS>
set service nat rule 6700 inbound-interface eth1
set service nat rule 6700 inside-address address <IP_ADDRESS>
set service nat rule 6700 inside-address port 8000
set service nat rule 6700 protocol tcp
set service nat rule 6700 type destination

As this is a nodeJs based application I think the port needs to be 8000? Or something else?

Hi, see below, .26 is the riscopanel, .17 is the risco addon
iptables -t nat -I PREROUTING -s <IP_ADDRESS> -d www.riscocloud.com -p tcp --dport 33000 -j DNAT --to-destination <IP_ADDRESS>:33000

RW032:618V-MI

Hi.
Can you open a new issue about this please ?
Can't track different requests in a single issue.
For generic discussion, I'll activate the github discussion tab in order to not spam issues with unrelated comments.
Thx

Hi @nonameboy007
I'm doing some cleanup in github issues.
Can you reopen an issue and provide all informations asked in the new issue template please ?
Thx


[Master] Fixing grant types disable issue

Purpose
When we disable a grant type from deploymnet.toml file and update an existing application from the devportal, the request payload will include the client credential as a supported grant type. This PR will fix this issue.
Goals
Fixes https://github.com/wso2/product-apim/issues/9469 for Master
User stories
Disable Grant types
Documentation
No doc changes required.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Improve localization logic

Gimme assignee

Now there is critical bug due to invalid for-each indexed :see_no_evil:


Incorrectly generated parent data class

part 'database.g.dart';

@DriftDatabase(
  tables: [
    Companies,
  ],
)
class Database extends _$Database {
  Database(super.e);

  @override
  int get schemaVersion => 1;
}

abstract class BaseDataClass extends DataClass {
  abstract String id;
}

@DataClassName('Company', extending: BaseDataClass)
class Companies extends Table with BaseDriftTable {
  TextColumn get name => text().named('name')();
}

mixin BaseDriftTable on Table {
  TextColumn get id => text().clientDefault(() => const Uuid().v1())();
}

//---------Generated class------------

class Company extends Companies implements Insertable<Company> {
  final String id;
  final String name;
  const Company({required this.id, required this.name});

//...
}

When specifying the extending parameter, the generated class is inherited from the table class, and not from the specified class

Thanks for the report and the helpful snippet to reproduce this, I think this regression comes from drift_dev version 2.3.
This problem is fixed in c3cd2f2eeb01060e5607bb0d8027d0d1bc3194f4.


doc: add a more complete prometheus.yaml example

This is great! Very helpful!
This should be possible to do also with Juju using the prometheus2 charm https://charmhub.io/prometheus2 down the road.

This is how a config is setup with "no ssl":
https://discuss.linuxcontainers.org/t/official-grafana-dashboard-for-lxd/13438/33?u=erik_lonroth


RTD Documentation setup outdated

In the usage section in Start to finish for Read the Docs
In step 6 It tells you to check the option :
install your project inside a virtualenv using setup.py install
This is no more required to build the doc on RTD

Sorry for the confusion about that, thanks for reaching out!


Explicit non-reentrancy invariant

There is a non-reentrancy requirement stated in Evaluate() as:
1. [Assert](https://tc39.es/ecma262/#assert): This call to Evaluate is not happening at the same time as another call to Evaluate within the [surrounding agent](https://tc39.es/ecma262/#surrounding-agent).

It is possible to violate this invariant with the current specification as written, by importing and evaluating a deferred module within the top-level evaluation of another module's execution.
For example:
main.mjs
import './dep.mjs';
console.log('main');

dep.mjs
import defer * as lazy from './lazy.mjs';
lazy.breakInvariant;
console.log('dep');

lazy.mjs
console.log('lazy');

The evaluation of main.mjs will result in lazy being executed between dep.mjs and main.mjs via a new top-level execution interleaved during the top-level execution of main, breaking the invariant of main being the only top-level execution.
We could:

Relax the invariant to allow for disjoint graph evaluations to more carefully distinguish partial evaluating graphs, then only throwing specifically for the case where we hit modules already in the evaluating phase/
Harden this invariant more explicitly by treating it as an explicit check with a real value.

I can try to work on a PR for a more relaxed invariant here if it would be useful.

Fixed by https://github.com/tc39/proposal-defer-import-eval/pull/39, by doing (1).


Add an option to downgrade errors to warnings

In Charon we want to extract a crate even when there are errors. To achieve that, we use catch_unwind when translating any item. Except sometimes this isn't enough, because hax's use of struct_fatal and struct_err informs rustc that there was an error, which causes Charon to fail. This PR adds an option to avoid that.

I found another solution: I can just ignore rustc's errors in Charon. So unless you have a use for this too, this is no longer useful.


Added Engine label for Prometheus Metrics | Minor Refactoring of Types

Signed-off-by: Oum Kale<EMAIL_ADDRESS>Adding the chaosengine label inside the label filters { chaosengine_label="litmuschaos.io/engine-context=<value>"}
Without Labels logs of exporter-service: Exam Network-Loss Experiment
litmuschaos_passed_experiments{chaosengine_label="",chaosengine_name="pod-network-loss-chaos-1616141807",chaosresult_name="pod-network-loss-chaos-1616141807-pod-network-loss",chaosresult_namespace="litmus"} 1

With Labels logs of exporter-service: Exam Pod-Delete Experiment
example :
labels:
    litmuschaos.io/engine-context: lab

litmuschaos_passed_experiments{chaosengine_label="litmuschaos.io/engine-context=lab",chaosengine_name="catalogue-pod-delete-chaos-1616141807",chaosresult_name="catalogue-pod-delete-chaos-1616141807-pod-delete",chaosresult_namespace="litmus"} 1

@ispeakc0de  Requested changes has been done. PTAL again and let me know any more change?

Can we ensure that the label keys for Kubernetes label (on the chaosengine) as well as metric label are in sync/same? This will help the user relate better


Add appsetreport for argo pull model

Related Issue:  stolostron/backlog#: ACM-1301
Description of Changes:
In ACM 2.8, for the new argoCD pull model feature, we introduced a new CRD: multiclusterapplicationsetreports.apps.open-cluster-management.io. We need to gather these resources from the hub.
What resource is being added: multiclusterapplicationsetreports.apps.open-cluster-management.io
Is this a Hub or Managed cluster change?:
Hub Cluster
Notes:

/assign @JakobGray


Fluids Not Rendering

Attempted to render a waterlogged stair and it simply did not show the water. The only work around for this I have found is to do an Area Render instead.
Using v0.4.7 on 1.20.4.

This isn't really a bug or a missing feature as much as it is a consequence of how waterlogged blocks work. The fluid is indeed not actually part of the block and drawn in an entirely separate stage of terrain rendering - which is why it doesn't show when rendering just the block.
Given how trivial this is to work around by doing single-block area render I also don't see any reason to invest effort into "fixing" it. I will however add a small snippet to the documentation to let users know that they should do that instead
Cheers


Error when supportsCompletionsRequest is not supported

After playing with this plugin and diving into the source I've finally figured out why this did not work for me. I'm using PHP and the PHP debug adapter (https://github.com/xdebug/vscode-php-debug/) does not support supportsCompletionsRequest.
When it does not support the completions request I assume the plugin should just do nothing but it gives the following error:
Error executing vim.schedule lua callback: ...e/pack/packer/start/cmp-buffer/lua/cmp_buffer/buffer.lua:356: bad argument #1 to 'ipairs' (table expected, got userdata)
stack traceback:
        [C]: in function 'ipairs'
        ...e/pack/packer/start/cmp-buffer/lua/cmp_buffer/buffer.lua:356: in function 'rebuild_unique_words'
        ...e/pack/packer/start/cmp-buffer/lua/cmp_buffer/buffer.lua:341: in function 'get_words'
        ...e/pack/packer/start/cmp-buffer/lua/cmp_buffer/source.lua:66: in function ''
        vim/_editor.lua: in function ''
        vim/_editor.lua: in function <vim/_editor.lua:0>

It happens sometimes when I type in the REPL window. When I disable the plugin, the error is gone.

Oh that's strange, there is a check for the capability https://github.com/rcarriga/cmp-dap/blob/master/lua/cmp_dap/init.lua#L56. Can you check the DAP log to see what the initialize response looks like? See :h *dap.set_log_level() to get a log if you're not sure how.

This is not an error for cmp-dap, it does check that the capability is there.
This is cmp-buffer throwing the error cmp-buffer/lua/cmp_buffer/buffer.lua.
My guess is that it assumes you're not using prompt buffers and there's an issue with having completion enabled in them

[...] the debug adapter [...] does not support supportsCompletionsRequest

Hey @rcarriga, is there another way to get completion if the adapter doesn't support this request?

Hey @rcarriga, is there another way to get completion if the adapter doesn't support this request?

Theoretically you could use the variables DAP request to build a list of sources that would probably be valid. This would be a large enough task though. You'd have to handle caching so to not spam the adapter, handle invalidating that cache etc. I'm not using an adapter that doesn't provide completions so I don't have much interest in developing this but if someone wanted to submit a PR I'd be happy to help.

Closing this as it's an issue with another plugin


Add Elasticsearch sniffer class name and use it by default

Because elasticasearch plugin should use elasticsearch-ruby client's sniffering cluster feature which is called every 10000 requests by default and its sniffering feature replaces elasticsearch instances service names with their pod ip addresses.
But, in k8s environment, we should use service name instead of raw ip addresses.
So, in k8s, we should recommend to use SimpleSniffer class for elasticsearch plugin.
WDYT?
Signed-off-by: Hiroshi Hatake<EMAIL_ADDRESS>

Let's :shipit:!

I triggers es6 and es7 image builds.
They will be published with the new tags.


Cannot edit connection - Error running command sqltools.openEditConnectionScreen

Describe the bug
After upgrading to 0.22.2 right click connection/edit connection gives the following error:
Error running command sqltools.openEditConnectionScreen: Cannot read property '_lower' of undefined. This is likely caused by the extension that contributes sqltools.openEditConnectionScreen.
To Reproduce

Create a connection
Upgrade
Right click an existing connection and click edit
The error appears

Expected behavior
Edit connection dialog should appear.
Desktop (please complete the following information):

SQLTools Version v0.22.2
VSCode Version: 1.45.1
Driver Used/Version: MariaDB
OS: Windows 10

Additional context
May be related with https://github.com/mtxr/vscode-sqltools/issues/590

It is fixed after installing SQLTools MySQL/MariaDB. So probably a similar error message context issue similar to #590.

@guneyozsan yeah, we had this bug

FIxed on recent releases.


changed methods for woocommerce v3.0 methods for process payment

+1 .. was making exactly the same changes and found this

If you are going to add the notify url check it would have to be more like:
if ( ( 'yes' == $this->debug) && ($this->notify_url) && ($this->notify_url !=='') )

as the equality test alone would error if the property is undefined..


Use ubuntu-22.04 in github runner

It's a fairly trivial point, but people running ros2 (and rosdoc2) are more likely to be on ubuntu-22.04 rather than ubuntu-20.04, so update the action runner to support this. Also add python3.10 since that is now the default version.

This is a good point that most people will be on 22.04 and soon 24.04. There's a bit of a question of whether we are worried about breaking our oldest platform or testing our newest platform. But I think that our general policy has been to keep this as close to what's happening on the buildfarm so make sure that keeps working. @clalancette @nuclearsandwich have we moved the buildfarm forward?
Optimally we'd actually switch this to support a matrix test of all our supported platforms 20.04 (for the next year), 22.04 and soon 24.04. If we did that we could potentially switch this to use the built in versions of the tools instead of pip which would also increase reproducibility for users.

@clalancette @nuclearsandwich have we moved the buildfarm forward?

Yes; all Rdoc jobs are now using 24.04.
However, the Idoc jobs are still using 22.04, so we should test both.  Which brings me to...

Optimally we'd actually switch this to support a matrix test of all our supported platforms 20.04 (for the next year), 22.04 and soon 24.04.

We only need to test 22.04 and 24.04.  We never had working documentation on any 20.04-based distribution, and all 20.04-based distributions are now end-of-life anyway.

I tried adding a github runner matrix with ubuntu-24.04 but the job is hanging. I don't see any evidence from github resources that 24.04 is an available os. Do you know how to use that?

Yeah, github hasn't updated to make the prebuilds of 24.04 available yet. For most of our builds we use the Ubuntu ones or our own base images instead of the GitHub ones that gives us more flexibilty. Such as just running it on ros:rolling or ros:iron which is actually closer to what we expect our users to run on anyway.

So where are we at with this? Is there some way to use ubuntu24 on github actions that I don't know about? If not, then this PR as-is seems to be the best option.
Really though this is not critical to anything I am doing, so I'd be happy to drop it if that is what you want. To me, a much more interesting change would be to add a Windows runner, which is more likely to find regressions or new issues. But one way or another, it would good to get this either landed or rejected.

To me, a much more interesting change would be to add a Windows runner, which is more likely to find regressions or new issues.

To be honest, I don't think a Windows runner adds much value, and adds more work.  The point of this tool is, in the end, to generate HTML.  Realistically, we only need a single platform where that works, and since it already works on Linux, we may as well stay there.  I guess it might be nice for people to be able to do it natively on Windows, but with WSL nowadays, they can do it there.

"Realistically, we only need a single platform where that works" You are looking at this from the perspective of someone who is maintaining the rosdoc2 website. To me, another important audience for rosdoc2 is the individual package developer, who we would like to run rosdoc2 when they are developing the documentation for their package. rosdoc2 should work cleanly in all environments where we expect developers to live. I thought Windows was supposed to be a first-class environment in ros2. Has that changed?

I thought Windows was supposed to be a first-class environment in ros2. Has that changed?

No, but I'm trying to be realistic about what work we are going to do here.  We've never tested this tool on Windows, and I suspect that it is going to be quite a lot of work to make it work there.

Back when the big patch adding python support was being worked on, we tested rosdoc2 with Windows, and added where needed calls to a function to make it it work. I have not tested if for a couple of years, and without unit tests I doubt if it still works, but I suspect the changes are not major.

I think we can integrate what I tested in #74 here to have specific coverage of images. I think that we can also remove some of the installation boilerplate too such as setup python which should already be in the image.

I'm still tweaking on this, the python setup and pip cache is not being done correctly yet.

There is one remaining issue with this, and that is that the pip caching does not work in a docker image, but that is a pretty trivial issue. If you look at previous runs, even with the pip cache "working", the github runner cache does not seem to prevent the re-download of all of the various pip dependencies. I've already put much more effort into this than I intended, that was supposed to be trivial.
The last patch incorporates using the ros:iron and ros:rolling images as suggested by @tfoote, and eliminates the unneeded python setup as well as the (not working) cache setup.
The only remaining change that might be interesting would be to add an additional image using ubuntu:24.04 like the build farm. But otherwise I don't think this is worth any more effort.

Back when the big patch adding python support was being worked on, we tested rosdoc2 with Windows, and added where needed calls to a function to make it it work. I have not tested if for a couple of years, and without unit tests I doubt if it still works, but I suspect the changes are not major.

OK, I didn't know that.  Thanks for the info.

This pull request has been mentioned on ROS Discourse. There might be relevant details there:
https://discourse.ros.org/t/rosdoc2-undergoing-significant-change/36905/2


Add Inversion to SingleAxis, DualAxis, and VirtualDPad

Fixes #247.
Adds inverted, inverted_x, and inverted_y builder-style functions for SingleAxis, DualAxis, and VirtualDPad, where appropriate. The SingleAxis implementation uses an inverted field, the DualAxis implementation just inverts its internal axes, and the VirtualDPad implementation swaps the relevant inputs.
Current tests pass, but I haven't written any yet to test inversion.
Todo

[ ] Write tests
[ ] Better documentation?

Solid :) Changelog entry and a couple tests and this looks good to me.

Cool, thanks. CONTRIBUTING.md says to put changes into CHANGELOG.md, which doesn't exist -- I assume it should be RELEASES.md?

That's correct. Thanks for pointing that out; I'll update it!


Package compiled aar in NPM lib

I noticed a lot of time Android Studio will fail the build if this library is included.
After a bit of investigation, I noticed that happens because it fails to find the compiled aar while syncing the project, this because it fails to find the source code in time, creates an empty module to fill the gaps and then won't have anything to compile.
React native main package solves this providing pre-compiled aars in their NPM package, instead of having the developers have to add the lib as a module to their project. This is quite easy to achieve with something on the lines of:
apply plugin: 'maven'

task generateReactArchive(type: Upload) {
    configuration = configurations.archives
    repositories.mavenDeployer {
        repository url: "file://${rootDir}/android-repository"
        pom.project {
            groupId 'react-native-community'
            artifactId 'react-native-linear-gradient'
            version '1.2.3'
        }
    }
}

Apart from Android Studio related problems, this would solve a whole set of issues that right now a dev might have, for example the fact the build tools might be different from the ones in the android project this lib is included in (which will, again, make Android Studio fail the sync).
At that point, instead of having to include the project as a module, the dev would include the aar folder as react native does here http://facebook.github.io/react-native/docs/integration-with-existing-apps.html#configuring-maven (select Android, go to "Configuring maven", second code block)

this looks like a nice solution
do you wanna provide a PR for this?

Can do! I'm currently without a computer but will do as soon as I'm back from holidays

Hey, thanks for raising this issue. I am trying to understand:

this because it fails to find the source code in time

how is this condition possible given that the Android source code is shipped onto the npm? I think it could be worth investigating an alternative solution given that proposed PR adds some complexity for quite a popular/standard library.

Everything is fine if you run npm/yarn install before opening Android studio, otherwise the node_modules dir is empty and the ide fails to find it.
To be honest, I think shipping the source code of a library to add to an Android project is the problem here, cause there are many variables that come into play (i.e. the fact the SDK tools version might be different and fail the compilation).
Android libs are usually distributed through Maven in the form of pre-compiled artifacts for that (also, that shaves off a good 10s of build time for the lib) and the whole system isn't supposed to have libraries as source modules.
Imho the ideal solution would be to have them on Maven as any other Android lib, then synchronising the version reading the package.json and do something like this:
static def reactNativeVersion() {
    def contents = new File('package.json').text
    def jsonSlurper = new JsonSlurper()
    def json = jsonSlurper.parseText(contents)
    json.dependencies['react-native']
}

Now, this is imho the ideal solution, but for now it would really be helpful to have one way of getting the artifact instead of the source code, thus the PR

Everything is fine if you run npm/yarn install before opening Android studio, otherwise, the node_modules dir is empty and the ide fails to find it.

Don't you have to run it anyway to install the package, like this: yarn add react-native-linear-gradient?
I generally feel that we are missing guidelines on how to create native modules and that's the area that we should improve.
Don't get me wrong - I support any issue that has the goal of making the dependency management a bit saner, but on the other hand, I do think this might end up being a bit too complex for the community. Not only is the link not yet ready for this, but also the unlink will fail to remove the maven entry pointing to node_modules. That means we will get a compilation error after removing that dependency.
I was planning on rewriting link to support new ways of linking on ios and a couple of other requirements that popped up recently - this might be an interesting thing to factor in.

I think supporting aar could be a good thing, so we can make building time faster on android

@grabbou you do, but in a team other devs might just clone your repo, and will have to run yarn install somehow.
In my specific case (since not everyone is working on the JS bits), we automated it as part of the gradle build step, so that the lib is always present. What I found out is that pre-built AAR (i.e. the react native AAR) won't fail if done while the IDE is open, while building from sources will.
I agree on the fact we need to improve link/unlink to support that kind of automation and avoid problems, have you any reference on that? I struggled a bit to find any docs on the matter.

@fourlastor you can check here
https://github.com/facebook/react-native/blob/master/local-cli/link/link.js#L102

I unified the dicussion in #255, let's continue there :)


recurrence experiment

Can you public your dataset or dataset formate?
Thanks.

I'm also interested in your article . but i can run it without the dataset.  would you like to public your test dataset  or dataset formate？

Since this tool is trained using bert-pytorch implementation by codertimo, i think the data format is similar to the dataset format from that repo. Is this correct @SidekickLx? If its correct, maybe the code to prepare such dataset using binary ninja might be helpful for others. Would gladly contribute to prepare the dataset using other reverse engineering tools as well if needed be.

Yes I have prepared those code but cannot get access to it right now. Will
release code for cfg and dfg generation later.
On Sun, Jan 9, 2022 at 17:32 bobbyhaliwela @.***> wrote:

Since this tool is trained using bert-pytorch implementation by codertimo,
i think the data format is similar to the dataset format from that repo. Is
this correct @SidekickLx https://github.com/SidekickLx? If its correct,
maybe the code to prepare such dataset using binary ninja might be helpful
for others. Would gladly contribute to prepare the dataset using other
reverse engineering tools as well if needed be.
—
Reply to this email directly, view it on GitHub
https://github.com/palmtreemodel/PalmTree/issues/4#issuecomment-1008517196,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADGXP2ONJ3V323D43MSNR6TUVJHN7ANCNFSM5I42Q2IA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

@SidekickLx Wonderful! Looking forward to it!

We have updated the code for CFG, DFG generation as well as intrinsic and extrinsic evaluation. So, this issue will be closed


[Community Skin] Media time formatting doesn't pad minutes

v0.6.4

Similar to https://github.com/vidstack/player/issues/852

Strange, just tested and it works...?

Hm i have the same issue 🤔 . I am on 0.6.10.
For me it is only on the time slider hover using the Community Skin:

Same here.
Does pad-minutes help?

This issue is outdated now and should be resolved since our new 1.0@next release. If the issue persits after upgrading, feel free to let me know here and we can reopen. If the issue has changed then please open a new one.


Error building RTL

Trying to build RTL (https://github.com/isaacvando/rtl)  it throws this error:
roc build rtl.roc --optimize
Downloading https://github.com/roc-lang/basic-cli/releases/download/0.17.0/lZFLstMUCUvd5bjnnpYromZJXkQUrdhbva4xdBInicE.tar.br
into /home/arkaitz/.cache/roc/packages
[8.7 / 8.7 MB]
An internal compiler expectation was broken.
This is definitely a compiler bug.
Please file an issue here: https://github.com/roc-lang/roc/issues/new/choose
Undefined Symbol in relocation, (+13297, Relocation { kind: PltRelative, encoding: Generic, size: +20, target: Symbol(SymbolIndex(+a2)), addend: +fffffffffffffffc, implicit_addend: false }): Ok(Symbol { name: "memmove", address: +0, size: +0, kind: Unknown, section: Undefined, scope: Unknown, weak: false, flags: Elf { st_info: +10, st_other: +0 } }) try compiling with --linker legacy
Location: crates/linker/src/elf.rs:1452:25
roc --version
roc nightly pre-release, built from commit 2e2be45 on Sa 28 Dez 2024 09:01:40 UTC

Can you try adding the --linker legacy flag?

Related issue: #3609


Fixed radio button conflicts, issue #114 fix

Moved and modified the logic from pr #85 to resolve a merge conflict with that pull request.
Pr #85 had changes in the GUI3.py, but now the brainwave prediction tab has its own class. Now the changes are in the new class.

@chavue91

Please, also make the complete submission on D2L, including video demo. When you do that, also add the link and make a quick note that is was merged into the main repo - which will grant your team the extra bounty. Congrats!

good job! no apparent conflict.


Can i request something? Sub

Hi, maybe an option for exclude files like (*.psd files).
And if the folder only have a txt file delete that folder?
i hope this is the correct place for a request
thanks

Sounds good, yeah you can request it here. I will have it done in the next version sometime soon with some quality of life upgrades. Updates will  be less frequent since I'm job hunting and stuff but I'll make sure to continue adding stuff if you request it.

Thanks


Fix current npm broken. Remove babel-polyfill import

Hi @dennybritz
Current npm 0.2.4 is broken. This PR fix that.
I changed Object.assign to jQuery.extend. Now is more IE9 and mobile compliant without babel-polyfill dependencies.

I don't understand, why is it broken? I'd really not rely on jQuery.

Cause this line: https://github.com/dennybritz/neal-react/blob/master/js/app.js#L1 it broke if babel-polyfill npm is unmet. Adding the whole polyfill only for Object.assign IMO is not adecuate.
This package already use jQuery: https://github.com/dennybritz/neal-react/blob/master/js/components/vendor/stripe.jsx#L14. jQuery is needed for Bootstrap 4 module.

Hi @dennybritz do you already see the problem?

I decided to keep babel-polyfill in. It's true that it's currently not used beyond Object.assign but I think it may be useful in the future when adding new features. I moved it back into the dependencies.
I'd love to get rid of the jQuery dependency someday. Not everyone needs the Bootstrap Javascript.


Add Portfolio updates for v1.2

Description
Portfolio update.
Fixes #101
Testing
NIL
Remarks
Add any additional remarks for others to take note of.

Looking good.

Codecov Report

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

@@            Coverage Diff            @@
##             master     #158   +/-   ##
=========================================
  Coverage     71.41%   71.41%
  Complexity      523      523
=========================================
  Files            90       90
  Lines          1665     1665
  Branches        171      171
=========================================
  Hits           1189     1189
  Misses          418      418
  Partials         58       58

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/seedu/address/ui/HelpWindow.java
0.00% <ø> (ø)
0.00 <0.00> (ø)

Continue to review full report at Codecov.

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


add more build/installation instructions

Depends on https://github.com/Homebrew/homebrew/pull/42506

Homebrew accepted dfix, so we're good to go here


Etcd in operator

Enable launching etcd in operator. This is the first step in which alluxio cluster and etcd cluster is one-to-one.
The second step would be launching only one etcd cluster regardless of how many alluxio cluster exists.

@JiamingMai Could you help take a look? Thanks!


Failed to send file: failed to stat source file Error

Hello,
When I'm trying to send this command:
fleex scan -n pwn -i list.txt -o scan-results.txt -c "findomain -f {{INPUT}} -o {{OUTPUT}}"
The contents of list.txt contains a list of domains.
I get this error:
FATA[0004] Failed to send file: failed to stat source file: err=stat /tmp/XXXXXX/input/chunk-pwn-2: no such file or directory
May I know what can be the issue?

Seems like the list.txt should contain more than one domains otherwise it won't work.
But I'm getting this error now:
error: Found argument '/tmp/fleex-1626253782507772000-chunk-out-pwn-1' which wasn't expected, or isn't valid in this context

USAGE:
    findomain --file <files>... --output

FATA[0013] Failed to get file: failed to read scp message header: err=failed to write scp replyOK reply: err=EOF

Hi there, thanks for sending this issue.
I'm checking it now, will update you shortly

So it looks like you can't just use the -o flag in findomain the way you using it.
That flag doesn't support a path as it just puts all subdomains in a file named .txt.
The flag you want to use is -u.
Let me know if this works :)

My bad, it works as expected. Great tool btw!

Thank you, appreciate your words :)
By the way, you're right about the more than 1 domain error, we'll add better error handling for it in the next release.
Closing this now!


☂ Translate the website into Turkish (tr)

Description
If you would like to contribute to a specific page, please leave a comment indicating the page you would like to translate and create a PR.
If there is any error, please notify us here in the comments.

[x] Translate sidebar @ImBIOS
[x] Translate README.md @ImBIOS
[ ] Translate the files inside src/content/docs

[x] index.md @ImBIOS
[ ] 404.md
[ ] analyzer/index.mdx
[ ] formatter/index.mdx
[ ] formatter/option-philosophy.md
[ ] formatter/differences-with-prettier.md
[ ] linter/index.mdx
[ ] guides/big-projects.mdx
[ ] guides/getting-started.mdx
[ ] guides/how-biome-works.mdx
[ ] guides/integrate-in-editor.mdx
[ ] guides/manual-installation.mdx
[ ] internals/architecture.mdx
[ ] internals/credits.mdx
[ ] internals/language-support.mdx
[ ] internals/philosophy.mdx
[ ] internals/versioning.mdx
[ ] recipes/continuous-integration.mdx
[ ] reference/vscode.mdx

The following files don't need to be translated, since they are auto-generated

internals/changelog.mdx
linter/rules/*.mdx
reference/configuration.mdx (will be auto-generated in https://github.com/biomejs/biome/issues/825 )
reference/cli.mdx
blog/*.mdx (low priority)

I'll be more than happy to review Turkish translations @ematipico

Thank you @ImBIOS , but we are going to wait for translating pages to this language until we have more contributors/maintainers that speak this language.


[BUG] Eurotronic Spirit Zigbee (SPZB0001) does not reconnect after HAss restart

Describe the bug
Controlled by a ConBee II over USB.
After restarting always neither battery nor heating functionality available. The device does not display the symbol for an active connection. Removing and reinserting the device's battery, displays the symbol, but it is still not connected in HAss, neither battery not heating.
Other devices controlled by the ConBee II reconnect fine.
To Reproduce
Steps to reproduce the behavior:

Restart Home Assistant
Look at the device status

Expected behavior
After a restart, the device should be able to get a temperature set and reports the currently measured temperature and battery level.

Do you have some routers around that it can connecting 2 and is not leaving the network if the coordinator is not online ?

Can't HAss' ZHA resolve the problem? (To be honest, this is why I opened the bug report here ;-) ) Since I am not the only one to have the problem it might be worth to develop a device specific behavior or so.
Unfortunately the only other device I have is an IKEA Tradfri gateway. Unsuccessfully tried to connect to the device.

Is there anything else I can do to help sort this out? A log file, an action, a test, ...?

It is not ZHA's problem. It is ConBee non Zigbee compliant behavior (not enough information based on the logs) where it does not keep the track of it's children.
Easiest way to fix/confirm, add another Zigbee router and pair the thermostat throu it.
Alternatively:

Update ConBees firmware
2 remove device from zha
Power cycle conbee
Factory reset thermostat -- it is important, because it has to request the network key
Pair it again
Don't restart HA -- important for the next three hours.
Check visualization map and confirm that thermostat has a link to the parent device

Honestly I think this is more likely an issue of the thermostat itself. I had 8 of them until two weeks ago and I am happy I moved away since EUROTRONIC doesn't seem to work on these issues known to them since the beginning of this year.
This reconnection issue is really the most annoying part but not the only "unlucky behaviour".


chore(patients): split patient address field into subfields

Fix #2141
Relevant files changed:
GeneralInformation.tsx
Patient.ts
index.ts
patient-slice.ts

Hi @thelderop. Before we can review this, can you please make sure all of the PR checks are passing! thanks!


Remove print 'got name' to stdout

Remove un-necessary (and ugly) 'got name' print when reading ASCII stl's.

Coverage remained the same at 100.0% when pulling 11cd92f90c76d8ab167ee0ebe17e436ed6b443df on hakostra:bugfix/remove-print into f9767ce869c6ed5661fb7c8ffbbc1d6974bdcb9f on WoLpH:develop.

Thanks for the fix. I forgot about that one :P


all work revised

Is there anything in this PR that's not part of your other PRs (https://github.com/abdul-moize/learn-python/pull/1 & https://github.com/abdul-moize/learn-python/pull/2)?
If not, we can remove this PR and we'll go ahead with merging/rebasing the PRs with the master. e.g We'll merge https://github.com/abdul-moize/learn-python/pull/1 after getting approval and then rebase & merge https://github.com/abdul-moize/learn-python/pull/2.

Is there anything in this PR that's not part of your other PRs (#1 & #2)?
If not, we can remove this PR and we'll go ahead with merging/rebasing the PRs with the master. e.g We'll merge #1 after getting approval and then rebase & merge #2.

this PR has the combined work of both the PRs. we can remove this as i have updated the other PRs


fix: disable ACL in dev-mode

References https://github.com/lightbend/kalix/issues/7783

Seems the integration tests is testing ACLs so need a change in one way or the other.

@johanandren, test is passing now. My bad, I changed something in the integration tests that should have been left untouched.

This needs an extra note in announcement of release since it might break user tests.

yes, it's on my list. I also need to add it to the main docs.


[Enhancement] Optimize the partition prune for hive table

Fixes #issue
When there are a lot of partitions in the hive/hudi table. there could cost lots of times, eg.

it will costs 3845ms to partition prune, after optimize,

Main change:
use parallel stream to compute the columnToPartitionValuesMap
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.1
[x] 3.0
[x] 2.5
[ ] 2.4

[FE PR Coverage Check]
:heart_eyes: pass : 21 / 21 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/optimizer/rewrite/OptExternalPartitionPruner.java
12
12
100.00%
[]

:large_blue_circle:
com/starrocks/sql/optimizer/rule/transformation/ListPartitionPruner.java
5
5
100.00%
[]

:large_blue_circle:
com/starrocks/connector/PartitionUtil.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/sql/optimizer/rewrite/OptOlapPartitionPruner.java
3
3
100.00%
[]

nit: maybe you need to test whether the performance under high concurrency is as efficient as TreeMap.

@Mergifyio backport branch-3.1

@Mergifyio backport branch-3.0

@Mergifyio backport branch-2.5


.vscode directory shouldnt be part of code

Ideally, the .vscode dir should be excluded from github through the .gitignore file

@ShashankaNataraj , I would disagree. The workspace .vscode settings file is actually a suggested way, by the VSCode team, to share common workspace settings (see: https://code.visualstudio.com/docs/getstarted/settings)

Workspace settings are useful for sharing project specific settings across a team.

Because of the way our project is setup, the primary directory where all of our package code, packages/node_modules, is ignored by search and file watcher. The settings we provide are a way to get around that.
One thing you can do, if there are settings that you don't like is to create another .json settings file in the .vscode directory. That should get picked up by VSCode and used.


Avoid lots of messages for training with single line images

Signed-off-by: Stefan Weil<EMAIL_ADDRESS>

I hope that nobody will miss those messages.

In theory such messages should be in trace verbosity.
One log level is definitely not enogh.

@stweil I see that the Loaded messages are no longer there. Thanks, it will certainly make the log files smaller.
If possible, as suggested by @egorpugin they can be kept for trace verbosity. It will be helpful when trying to track an error.
Loaded 1/1 lines (1-1) of document data/San-ground-truth/bugfix/san.Segoe_UI_Semi-Light.0000002.exp0_0.lstmf
Loaded 1/1 lines (1-1) of document data/San-ground-truth/bugfix/san.Mandala_Italic.0000080.exp0_0.lstmf
Loaded 1/1 lines (1-1) of document data/San-ground-truth/bugfix/san.Segoe_UI_Semi-Light_Italic.0000040.exp0_0

All warning and error messages report the filename. Example:
Compute CTC targets failed for data/gt/AustrianNewspapers/train/ONB_ibn_19110701_010/ONB_ibn_19110701_010.tif_line_1547100903812_34.lstmf!

So the removed message should not be needed for error tracking.


fix(ui): restore gradients on Android

Description
Please include a summary of changes and which issues are fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Linked Issues/Tasks
Add any links to GitHub issues or Asana tasks that are relevant to this pull request.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Refactoring (improving code without creating new functionality)

Tests

[ ] Detox test
[ ] Unit test
[ ] No test

Screenshot / Video
Insert relevant screenshot / recording
QA Notes
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce during the Bitkit testing session. You can also leave a video of the PR in action.

Please, check e2e tests

Staging servers offline currently so slashtags and restore are broken in CI.