This plugin generated a warning from the characteristic 'Security System Current State'

[1/17/2023, 3:28:51 PM] [homebridge-envisalink-ademco] This plugin generated a warning from the characteristic 'Security System Current State': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info. [1/17/2023, 3:28:51 PM] [homebridge-envisalink-ademco] This plugin generated a warning from the characteristic 'Security System Target State': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
This plugin is absolutely awesome, and rock solid. Minor niggle is this occasional error if the panel is used to disarm (versus the Envisalink device itself).
Is this a simple fix?

Thanks for the reply! FYI I’m running Homebridge on a QNAP NAS..

v2.0.3
Panel is always “ready”, module doesn’t connect
Here’s the log; I restarted Homebridge and attempted to arm the panel:

[1/18/2023, 8:15:35 AM] [Homebridge UI] Homebridge restart request received
[1/18/2023, 8:15:35 AM] [Homebridge UI] UI / Bridge settings have not changed; only restarting Homebridge process
[1/18/2023, 8:15:35 AM] [Homebridge UI] Sending SIGTERM to Homebridge
[1/18/2023, 8:15:35 AM] Got SIGTERM, shutting down Homebridge...
[1/18/2023, 8:15:40 AM] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[1/18/2023, 8:15:45 AM] [HB Supervisor] Restarting Homebridge...
[1/18/2023, 8:15:45 AM] [HB Supervisor] Starting Homebridge with extra flags: -I -P /var/lib/homebridge/node_modules -D --strict-plugin-resolution
[1/18/2023, 8:15:45 AM] [HB Supervisor] Started Homebridge v1.6.0 with PID: 9369
[1/18/2023, 8:15:46 AM] Loaded config.json with 0 accessories and 4 platforms.
[1/18/2023, 8:15:47 AM] Loaded 11 cached accessories from cachedAccessories.
[1/18/2023, 8:15:47 AM] ---
[1/18/2023, 8:15:47 AM] Disabled plugin: @.***
[1/18/2023, 8:15:47 AM] ---
[1/18/2023, 8:15:47 AM] Loaded plugin: @.***
[1/18/2023, 8:15:47 AM] Registering platform 'homebridge-envisalink-ademco.Envisalink-Ademco'
[1/18/2023, 8:15:47 AM] ---
[1/18/2023, 8:15:47 AM] Loaded plugin: @.***
[1/18/2023, 8:15:47 AM] Registering platform 'homebridge-myq.myQ'
[1/18/2023, 8:15:47 AM] ---
[1/18/2023, 8:15:47 AM] Loading 4 platforms...
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] Initializing Envisalink-Ademco platform...
[1/18/2023, 8:15:47 AM] Ignoring config for the platform "Envisalink" in your config.json as the plugin "homebridge-envisalink" has been disabled.
[1/18/2023, 8:15:47 AM] [myQ] Initializing myQ platform...
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] Loading accessory from cache: House
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] Loading accessory from cache: Carbon Monoxide
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] Loading accessory from cache: Smoke Detector
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] Loading accessory from cache: Entry / Exit
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] Loading accessory from cache: Kitchen Windows
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] Loading accessory from cache: Glass Break
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] Loading accessory from cache: Balcony Doors
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] Loading accessory from cache: Master Bedroom Windows
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] Loading accessory from cache: Office Windows
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] Loading accessory from cache: Chime
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] Configuring Honeywell VISTA-20P for Homekit...
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] refreshAccessories: Partition number -  1  configured.
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] refreshAccessories: Zone number -  1  configured.
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] refreshAccessories: Zone number -  2  configured.
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] refreshAccessories: Zone number -  3  configured.
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] refreshAccessories: Zone number -  4  configured.
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] refreshAccessories: Zone number -  5  configured.
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] refreshAccessories: Zone number -  6  configured.
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] refreshAccessories: Zone number -  7  configured.
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] refreshAccessories: Zone number -  8  configured.
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] Partition configured: 1
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] Zone accessories configured: 8
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] Chime toggle accessory configured.
[1/18/2023, 8:15:47 AM] [Envisalink-Ademco] Starting connection to envisalink module at: <IP_ADDRESS>, port: 4025
[1/18/2023, 8:15:47 AM] Publishing bridge accessory (name: Homebridge B3E4, publishInfo: {
username: '0E:E0:8D:1D:B3:E4',
port: 51982,
pincode: '--**',
category: 2,
bind: undefined,
mdns: undefined,
addIdentifyingMaterial: true,
advertiser: 'bonjour-hap'
}).
Setup Payload:
X-HM://0024YDID8UHBP
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ 897-63-900 │
└────────────┘

[1/18/2023, 8:15:47 AM] Homebridge v1.6.0 (HAP v0.11.0) (Homebridge B3E4) is running on port 51982.
[1/18/2023, 8:15:48 AM] [Envisalink-Ademco] getPanelStatusLowBattery: Return Low Battery Status -  0
[1/18/2023, 8:15:49 AM] [myQ] myQ API: Successfully connected to the myQ API.
[1/18/2023, 8:15:50 AM] [myQ] myQ API: Discovered device family garagedoor: Garage Door (serial number: CG086016802D, gateway: GW0F000C812B).
[1/18/2023, 8:15:50 AM] [myQ] myQ API: Discovered device family gateway: Hub [Liftmaster WiFi GDO AC 3/4 HP] (serial number: GW0F000C812B).
[1/18/2023, 8:16:19 AM] [Envisalink-Ademco] getPanelStatusLowBattery: Return Low Battery Status -  0
[1/18/2023, 8:16:20 AM] [Envisalink-Ademco] setTargetState: Homekit alarm requested set -  0
[1/18/2023, 8:16:20 AM] [Envisalink-Ademco] Arming alarm to Stay (Home). [Partition 1]
[1/18/2023, 8:16:20 AM] [Envisalink-Ademco] setAlarmState: Partition state command issued.
[1/18/2023, 8:16:20 AM] [Envisalink-Ademco] Command not successful. No TPI session establish.
[1/18/2023, 8:16:20 AM] [Envisalink-Ademco] setAlarmState: Command not sent returning home state  3
[1/18/2023, 8:16:20 AM] [homebridge-envisalink-ademco] Characteristic 'Security System Target State': SET handler returned write response value, though the characteristic doesn't support write response. See https://homebridge.io/w/JtMGR for more info.
[1/18/2023, 8:16:20 AM] [homebridge-envisalink-ademco] Error:
at SecuritySystemTargetState.Characteristic.characteristicWarning (/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:3011:105)
at /homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2627:22
at /homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:15:18
at EnvisalinkPartitionAccessory.setTargetState (/homebridge/node_modules/homebridge-envisalink-ademco/accessories/partitionAccessory.js:204:10)
at SecuritySystemTargetState. (/homebridge/node_modules/homebridge-envisalink-ademco/accessories/partitionAccessory.js:66:52)
at SecuritySystemTargetState.emit (node:events:513:28)
at /homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2596:16
at new Promise ()
at SecuritySystemTargetState. (/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2594:14)
at step (/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:144:27)
[1/18/2023, 8:16:21 AM] [Envisalink-Ademco] Setting Alarm state to READY

On Jan 18, 2023, at 7:50 AM, haywirecoder @.***> wrote:
Thanks...
Hmm... I haven't seen this error prior and not experience this personally.
Few questions:
What version of plug-in are your using?
What state is your panel in when your disarm? Is it "Ready" after you disarmed?
Can you put module in debug and post was results. I am looking for:
"systemUpdate: partition change " and "partitionUpdate: status change " event in the debug log.
The error is indicating the panel (and/ro virtual key) is sending a state that is not define within the plug-in. Should be able to capture it and hopefully remove the error.
—
Reply to this email directly, view it on GitHub https://github.com/haywirecoder/homebridge-envisalink-ademco/issues/36#issuecomment-1387105686, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5IPCGDZ7S7P7O6BV6GUMFTWS7YLLANCNFSM6AAAAAAT6N63XI.
You are receiving this because you are subscribed to this thread.

1: homebridge-envisalink-ademco v2.0.3
2.1: There's a motion sensor right next to the alarm, so it goes into that "Not Ready state", but would still allow for "Arming Stay"
2.2: I recently added the Envisalink unit, I also have a Tuxedo Wifi controller. Why would I add the Envisalink if I already have the Tuxedo? The Tuxedo webserver is ancient (expired SSL certs), buggy, and since I use everything behind a reverse proxy it requires me to disable client renegotiation checking - a security risk for my nginx instance I'm not prepared to take. I can run the Envisalink on a dedicated vlan and protect it. The Envisalik is also much. much faster at updating Homekit correctly, and displays "state" notifications properly - something the Tuxedo plugins never did.
3: Full debug log for the plugin during the issue:

[1/18/2023, 8:57:37 AM] [Envisalink-Ademco] Checking for Heartbeat...
[1/18/2023, 8:57:37 AM] [Envisalink-Ademco] Heartbeat successful. Last message time: Wed Jan 18 2023 08:57:34 GMT-0800 (Pacific Standard Time)
[1/18/2023, 8:57:39 AM] [Envisalink-Ademco] Command | %00,01,8C28,08,00,ARMED STAY                $,00,01,8C28,08,00,ARMED STAY                 | Acknowledged
[1/18/2023, 8:57:39 AM] [Envisalink-Ademco] Envisakit Operation: updatekeypad
[1/18/2023, 8:57:39 AM] [Envisalink-Ademco] systemUpdate: Status changed -  {
partition: '01',
code: {
icon: [ 3, 5, 10, 11, 15 ],
zone: '08',
beep: 'off',
txt: 'ARMED STAY                '
},
status: 'Virtual Keypad Update',
keypadledstatus: {
alarm: false,
alarm_in_memory: false,
armed_away: false,
ac_present: true,
bypass: false,
chime: true,
not_used1: false,
armed_zero_entry_delay: false,
alarm_fire_zone: false,
system_trouble: false,
not_used2: true,
not_used3: true,
ready: false,
fire: false,
low_battery: false,
armed_stay: true
},
mode: 'ARMED_STAY'
}
[1/18/2023, 8:57:41 AM] [Envisalink-Ademco] Partition Change | %02,0700000000000000$,02,0700000000000000 | has been detected.
[1/18/2023, 8:57:41 AM] [Envisalink-Ademco] Envisakit Operation: updatepartition
[1/18/2023, 8:57:41 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 1,
mode: 'EXIT_DELAY',
code: 7,
status: 'Partition State Change'
}
[1/18/2023, 8:57:41 AM] [Envisalink-Ademco] partitionUpdate: Partition data - House to EXIT_DELAY
[1/18/2023, 8:57:41 AM] [homebridge-envisalink-ademco] This plugin generated a warning from the characteristic 'Security System Current State': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
[1/18/2023, 8:57:41 AM] [homebridge-envisalink-ademco] Error:
at SecuritySystemCurrentState.Characteristic.characteristicWarning (/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:3011:105)
at SecuritySystemCurrentState.Characteristic.validateUserInput (/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2903:14)
at SecuritySystemCurrentState.Characteristic.updateValue (/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2328:20)
at SecuritySystem.Service.updateCharacteristic (/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Service.ts:795:35)
at EnvisalinkPlatform.partitionUpdate (/homebridge/node_modules/homebridge-envisalink-ademco/index.js:390:46)
at EnvisaLink.emit (node:events:513:28)
at updatePartition (/homebridge/node_modules/homebridge-envisalink-ademco/envisalink.js:309:14)
at Socket. (/homebridge/node_modules/homebridge-envisalink-ademco/envisalink.js:185:23)
at Socket.emit (node:events:513:28)
at addChunk (node:internal/streams/readable:324:12)
[1/18/2023, 8:57:41 AM] [homebridge-envisalink-ademco] This plugin generated a warning from the characteristic 'Security System Target State': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
[1/18/2023, 8:57:41 AM] [homebridge-envisalink-ademco] Error:
at SecuritySystemTargetState.Characteristic.characteristicWarning (/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:3011:105)
at SecuritySystemTargetState.Characteristic.validateUserInput (/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2903:14)
at SecuritySystemTargetState.Characteristic.updateValue (/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2328:20)
at SecuritySystem.Service.updateCharacteristic (/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Service.ts:795:35)
at EnvisalinkPlatform.partitionUpdate (/homebridge/node_modules/homebridge-envisalink-ademco/index.js:391:71)
at EnvisaLink.emit (node:events:513:28)
at updatePartition (/homebridge/node_modules/homebridge-envisalink-ademco/envisalink.js:309:14)
at Socket. (/homebridge/node_modules/homebridge-envisalink-ademco/envisalink.js:185:23)
at Socket.emit (node:events:513:28)
at addChunk (node:internal/streams/readable:324:12)
[1/18/2023, 8:57:41 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 2,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:41 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:41 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 3,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:41 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:41 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 4,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:41 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:41 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 5,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:41 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:41 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 6,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:41 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:41 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 7,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:41 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:41 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 8,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:41 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:41 AM] [Envisalink-Ademco] Command | %00,01,8C28,08,05,DISARM SYSTEM   or alarm occurs $,00,01,8C28,08,05,DISARM SYSTEM   or alarm occurs  | Acknowledged
[1/18/2023, 8:57:41 AM] [Envisalink-Ademco] Envisakit Operation: updatekeypad
[1/18/2023, 8:57:41 AM] [Envisalink-Ademco] systemUpdate: Status changed -  {
partition: '01',
code: {
icon: [ 3, 5, 10, 11, 15 ],
zone: '08',
beep: 'continuous slow beep',
txt: 'DISARM SYSTEM   or alarm occurs '
},
status: 'Virtual Keypad Update',
keypadledstatus: {
alarm: false,
alarm_in_memory: false,
armed_away: false,
ac_present: true,
bypass: false,
chime: true,
not_used1: false,
armed_zero_entry_delay: false,
alarm_fire_zone: false,
system_trouble: false,
not_used2: true,
not_used3: true,
ready: false,
fire: false,
low_battery: false,
armed_stay: true
},
mode: 'ARMED_STAY'
}
[1/18/2023, 8:57:41 AM] [Envisalink-Ademco] systemUpdate: partition change - House to ARMED_STAY
[1/18/2023, 8:57:46 AM] [Envisalink-Ademco] Partition Change | %02,0300000000000000$,02,0300000000000000 | has been detected.
[1/18/2023, 8:57:46 AM] [Envisalink-Ademco] Envisakit Operation: updatepartition
[1/18/2023, 8:57:46 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 1,
mode: 'NOT_READY',
code: 3,
status: 'Partition State Change'
}
[1/18/2023, 8:57:46 AM] [Envisalink-Ademco] partitionUpdate: Partition data - House to NOT_READY
[1/18/2023, 8:57:46 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 2,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:46 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:46 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 3,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:46 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:46 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 4,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:46 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:46 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 5,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:46 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:46 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 6,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:46 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:46 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 7,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:46 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:46 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 8,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:46 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:46 AM] [Envisalink-Ademco] Command | %00,01,0C28,08,01, DISARMED CHIME Hit * for faults$,00,01,0C28,08,01, DISARMED CHIME Hit * for faults | Acknowledged
[1/18/2023, 8:57:46 AM] [Envisalink-Ademco] Envisakit Operation: updatekeypad
[1/18/2023, 8:57:46 AM] [Envisalink-Ademco] systemUpdate: Status changed -  {
partition: '01',
code: {
icon: [ 3, 5, 10, 11 ],
zone: '08',
beep: 'beep 1 time',
txt: ' DISARMED CHIME Hit * for faults'
},
status: 'Virtual Keypad Update',
keypadledstatus: {
alarm: false,
alarm_in_memory: false,
armed_away: false,
ac_present: true,
bypass: false,
chime: true,
not_used1: false,
armed_zero_entry_delay: false,
alarm_fire_zone: false,
system_trouble: false,
not_used2: true,
not_used3: true,
ready: false,
fire: false,
low_battery: false,
armed_stay: false
},
mode: 'NOT_READY'
}
[1/18/2023, 8:57:47 AM] [Envisalink-Ademco] Zone Update | %01,01000000000000000000000000000000$,01,01000000000000000000000000000000 | has been detected.
[1/18/2023, 8:57:47 AM] [Envisalink-Ademco] Envisakit Operation: updatezone
[1/18/2023, 8:57:47 AM] [Envisalink-Ademco] Zone updated
[1/18/2023, 8:57:47 AM] [Envisalink-Ademco] Not Found zone -  1
[1/18/2023, 8:57:47 AM] [Envisalink-Ademco] Adding new zone -  1
[1/18/2023, 8:57:47 AM] [Envisalink-Ademco] Activating zone timer
[1/18/2023, 8:57:47 AM] [Envisalink-Ademco] zoneUpdate: Status change -  { zone: [ 1 ], mode: 'open', source: 'Zone Status Change' }
[1/18/2023, 8:57:47 AM] [Envisalink-Ademco] zoneUpdate: Accessory change - Front Door to open
[1/18/2023, 8:57:47 AM] [Envisalink-Ademco] Command | %00,01,0028,01,00,FAULT 01        FRONT DOOR      $,00,01,0028,01,00,FAULT 01        FRONT DOOR       | Acknowledged
[1/18/2023, 8:57:47 AM] [Envisalink-Ademco] Envisakit Operation: updatekeypad
[1/18/2023, 8:57:47 AM] [Envisalink-Ademco] Found zone -  01
[1/18/2023, 8:57:47 AM] [Envisalink-Ademco] Zone found in active zone list index -  0
[1/18/2023, 8:57:47 AM] [Envisalink-Ademco] systemUpdate: Status changed -  {
partition: '01',
code: {
icon: [ 3, 5 ],
zone: '01',
beep: 'off',
txt: 'FAULT 01        FRONT DOOR      '
},
status: 'Virtual Keypad Update',
keypadledstatus: {
alarm: false,
alarm_in_memory: false,
armed_away: false,
ac_present: true,
bypass: false,
chime: true,
not_used1: false,
armed_zero_entry_delay: false,
alarm_fire_zone: false,
system_trouble: false,
not_used2: false,
not_used3: false,
ready: false,
fire: false,
low_battery: false,
armed_stay: false
},
mode: 'NOT_READY'
}
[1/18/2023, 8:57:50 AM] [Envisalink-Ademco] Zone Update | %01,21000000000000000000000000000000$,01,21000000000000000000000000000000 | has been detected.
[1/18/2023, 8:57:50 AM] [Envisalink-Ademco] Envisakit Operation: updatezone
[1/18/2023, 8:57:50 AM] [Envisalink-Ademco] Zone updated
[1/18/2023, 8:57:50 AM] [Envisalink-Ademco] Found zone -  1
[1/18/2023, 8:57:50 AM] [Envisalink-Ademco] Zone found in active zone list index -  0
[1/18/2023, 8:57:50 AM] [Envisalink-Ademco] Not Found zone -  6
[1/18/2023, 8:57:50 AM] [Envisalink-Ademco] Adding new zone -  6
[1/18/2023, 8:57:50 AM] [Envisalink-Ademco] zoneUpdate: Status change -  { zone: [ 6 ], mode: 'open', source: 'Zone Status Change' }
[1/18/2023, 8:57:50 AM] [Envisalink-Ademco] zoneUpdate: Accessory change - Entry Motion to open
[1/18/2023, 8:57:50 AM] [Envisalink-Ademco] Command | %00,01,0028,06,00,FAULT 06 ENTRY  MOTION DETECTOR $,00,01,0028,06,00,FAULT 06 ENTRY  MOTION DETECTOR  | Acknowledged
[1/18/2023, 8:57:50 AM] [Envisalink-Ademco] Envisakit Operation: updatekeypad
[1/18/2023, 8:57:50 AM] [Envisalink-Ademco] Found zone -  06
[1/18/2023, 8:57:50 AM] [Envisalink-Ademco] Zone found in active zone list index -  1
[1/18/2023, 8:57:50 AM] [Envisalink-Ademco] systemUpdate: Status changed -  {
partition: '01',
code: {
icon: [ 3, 5 ],
zone: '06',
beep: 'off',
txt: 'FAULT 06 ENTRY  MOTION DETECTOR '
},
status: 'Virtual Keypad Update',
keypadledstatus: {
alarm: false,
alarm_in_memory: false,
armed_away: false,
ac_present: true,
bypass: false,
chime: true,
not_used1: false,
armed_zero_entry_delay: false,
alarm_fire_zone: false,
system_trouble: false,
not_used2: false,
not_used3: false,
ready: false,
fire: false,
low_battery: false,
armed_stay: false
},
mode: 'NOT_READY'
}
[1/18/2023, 8:57:51 AM] [Envisalink-Ademco] CID Event: | %03,1441010020$,03,1441010020 |
[1/18/2023, 8:57:51 AM] [Envisalink-Ademco] Envisakit Operation: cidEvent
[1/18/2023, 8:57:51 AM] [Envisalink-Ademco] cidUpdate: Status change -  {
partition: '01',
qualifier: '1',
qualifier_description: 'event',
code: '441',
type: 'user',
subject: 'STAY/INSTANT',
status: 'Realtime CID Event',
user: '002'
}
[1/18/2023, 8:57:52 AM] [Envisalink-Ademco] CID Event: | %03,1441010020$,03,1441010020 |
[1/18/2023, 8:57:52 AM] [Envisalink-Ademco] Envisakit Operation: cidEvent
[1/18/2023, 8:57:52 AM] [Envisalink-Ademco] cidUpdate: Status change -  {
partition: '01',
qualifier: '1',
qualifier_description: 'event',
code: '441',
type: 'user',
subject: 'STAY/INSTANT',
status: 'Realtime CID Event',
user: '002'
}
[1/18/2023, 8:57:52 AM] [Envisalink-Ademco] CID Event: | %03,1441010020$,03,1441010020 |
[1/18/2023, 8:57:52 AM] [Envisalink-Ademco] Envisakit Operation: cidEvent
[1/18/2023, 8:57:52 AM] [Envisalink-Ademco] cidUpdate: Status change -  {
partition: '01',
qualifier: '1',
qualifier_description: 'event',
code: '441',
type: 'user',
subject: 'STAY/INSTANT',
status: 'Realtime CID Event',
user: '002'
}
[1/18/2023, 8:57:52 AM] [Envisalink-Ademco] CID Event: | %03,1441010020$,03,1441010020 |
[1/18/2023, 8:57:52 AM] [Envisalink-Ademco] Envisakit Operation: cidEvent
[1/18/2023, 8:57:52 AM] [Envisalink-Ademco] cidUpdate: Status change -  {
partition: '01',
qualifier: '1',
qualifier_description: 'event',
code: '441',
type: 'user',
subject: 'STAY/INSTANT',
status: 'Realtime CID Event',
user: '002'
}
[1/18/2023, 8:57:53 AM] [Envisalink-Ademco] CID Event: | %03,1441010020$,03,1441010020 |
[1/18/2023, 8:57:53 AM] [Envisalink-Ademco] Envisakit Operation: cidEvent
[1/18/2023, 8:57:53 AM] [Envisalink-Ademco] cidUpdate: Status change -  {
partition: '01',
qualifier: '1',
qualifier_description: 'event',
code: '441',
type: 'user',
subject: 'STAY/INSTANT',
status: 'Realtime CID Event',
user: '002'
}
[1/18/2023, 8:57:53 AM] [Envisalink-Ademco] Command | %00,01,0028,06,00,FAULT 06 ENTRY  MOTION DETECTOR $,00,01,0028,06,00,FAULT 06 ENTRY  MOTION DETECTOR  | Acknowledged
[1/18/2023, 8:57:53 AM] [Envisalink-Ademco] Envisakit Operation: updatekeypad
[1/18/2023, 8:57:53 AM] [Envisalink-Ademco] Found zone -  06
[1/18/2023, 8:57:53 AM] [Envisalink-Ademco] Zone found in active zone list index -  1
[1/18/2023, 8:57:53 AM] [Envisalink-Ademco] systemUpdate: Status changed -  {
partition: '01',
code: {
icon: [ 3, 5 ],
zone: '06',
beep: 'off',
txt: 'FAULT 06 ENTRY  MOTION DETECTOR '
},
status: 'Virtual Keypad Update',
keypadledstatus: {
alarm: false,
alarm_in_memory: false,
armed_away: false,
ac_present: true,
bypass: false,
chime: true,
not_used1: false,
armed_zero_entry_delay: false,
alarm_fire_zone: false,
system_trouble: false,
not_used2: false,
not_used3: false,
ready: false,
fire: false,
low_battery: false,
armed_stay: false
},
mode: 'NOT_READY'
}
[1/18/2023, 8:57:56 AM] [Envisalink-Ademco] Partition Change | %02,0100000000000000$,02,0100000000000000 | has been detected.
[1/18/2023, 8:57:56 AM] [Envisalink-Ademco] Envisakit Operation: updatepartition
[1/18/2023, 8:57:56 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 1,
mode: 'READY',
code: 1,
status: 'Partition State Change'
}
[1/18/2023, 8:57:56 AM] [Envisalink-Ademco] partitionUpdate: Partition data - House to READY
[1/18/2023, 8:57:56 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 2,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:56 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:56 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 3,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:56 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:56 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 4,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:56 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:56 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 5,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:56 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:56 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 6,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:56 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:56 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 7,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:56 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:56 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 8,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:56 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:56 AM] [Envisalink-Ademco] Command | %00,01,1C28,08,00, DISARMED CHIME   Ready to Arm  $,00,01,1C28,08,00, DISARMED CHIME   Ready to Arm   | Acknowledged
[1/18/2023, 8:57:56 AM] [Envisalink-Ademco] Envisakit Operation: updatekeypad
[1/18/2023, 8:57:56 AM] [Envisalink-Ademco] systemUpdate: Status changed -  {
partition: '01',
code: {
icon: [ 3, 5, 10, 11, 12 ],
zone: '08',
beep: 'off',
txt: ' DISARMED CHIME   Ready to Arm  '
},
status: 'Virtual Keypad Update',
keypadledstatus: {
alarm: false,
alarm_in_memory: false,
armed_away: false,
ac_present: true,
bypass: false,
chime: true,
not_used1: false,
armed_zero_entry_delay: false,
alarm_fire_zone: false,
system_trouble: false,
not_used2: true,
not_used3: true,
ready: true,
fire: false,
low_battery: false,
armed_stay: false
},
mode: 'READY'
}
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] Partition Change | %02,0300000000000000$,02,0300000000000000 | has been detected.
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] Envisakit Operation: updatepartition
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 1,
mode: 'NOT_READY',
code: 3,
status: 'Partition State Change'
}
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] partitionUpdate: Partition data - House to NOT_READY
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 2,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 3,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 4,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 5,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 6,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 7,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 8,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] Zone Update | %01,61000000000000000000000000000000$,01,61000000000000000000000000000000 | has been detected.
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] Envisakit Operation: updatezone
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] Zone updated
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] Found zone -  1
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] Zone found in active zone list index -  0
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] Found zone -  6
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] Zone found in active zone list index -  1
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] Not Found zone -  7
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] Adding new zone -  7
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] zoneUpdate: Status change -  { zone: [ 7 ], mode: 'open', source: 'Zone Status Change' }
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] zoneUpdate: Accessory change - Sunroom Motion to open
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] Command | %00,01,0028,07,00,FAULT 07 MASTER BEDROOM MOTION  $,00,01,0028,07,00,FAULT 07 MASTER BEDROOM MOTION   | Acknowledged
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] Envisakit Operation: updatekeypad
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] Found zone -  07
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] Zone found in active zone list index -  2
[1/18/2023, 8:57:58 AM] [Envisalink-Ademco] systemUpdate: Status changed -  {
partition: '01',
code: {
icon: [ 3, 5 ],
zone: '07',
beep: 'off',
txt: 'FAULT 07 MASTER BEDROOM MOTION  '
},
status: 'Virtual Keypad Update',
keypadledstatus: {
alarm: false,
alarm_in_memory: false,
armed_away: false,
ac_present: true,
bypass: false,
chime: true,
not_used1: false,
armed_zero_entry_delay: false,
alarm_fire_zone: false,
system_trouble: false,
not_used2: false,
not_used3: false,
ready: false,
fire: false,
low_battery: false,
armed_stay: false
},
mode: 'NOT_READY'
}
[1/18/2023, 8:58:01 AM] [Envisalink-Ademco] Command | %00,01,0028,07,00,FAULT 07 MASTER BEDROOM MOTION  $,00,01,0028,07,00,FAULT 07 MASTER BEDROOM MOTION   | Acknowledged
[1/18/2023, 8:58:01 AM] [Envisalink-Ademco] Envisakit Operation: updatekeypad
[1/18/2023, 8:58:01 AM] [Envisalink-Ademco] Found zone -  07
[1/18/2023, 8:58:01 AM] [Envisalink-Ademco] Zone found in active zone list index -  2
[1/18/2023, 8:58:01 AM] [Envisalink-Ademco] systemUpdate: Status changed -  {
partition: '01',
code: {
icon: [ 3, 5 ],
zone: '07',
beep: 'off',
txt: 'FAULT 07 MASTER BEDROOM MOTION  '
},
status: 'Virtual Keypad Update',
keypadledstatus: {
alarm: false,
alarm_in_memory: false,
armed_away: false,
ac_present: true,
bypass: false,
chime: true,
not_used1: false,
armed_zero_entry_delay: false,
alarm_fire_zone: false,
system_trouble: false,
not_used2: false,
not_used3: false,
ready: false,
fire: false,
low_battery: false,
armed_stay: false
},
mode: 'NOT_READY'
}
[1/18/2023, 8:58:05 AM] [Envisalink-Ademco] Partition Change | %02,0100000000000000$,02,0100000000000000 | has been detected.
[1/18/2023, 8:58:05 AM] [Envisalink-Ademco] Envisakit Operation: updatepartition
[1/18/2023, 8:58:05 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 1,
mode: 'READY',
code: 1,
status: 'Partition State Change'
}
[1/18/2023, 8:58:05 AM] [Envisalink-Ademco] partitionUpdate: Partition data - House to READY
[1/18/2023, 8:58:05 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 2,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:58:05 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:58:05 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 3,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:58:05 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:58:05 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 4,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:58:05 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:58:05 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 5,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:58:05 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:58:05 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 6,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:58:05 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:58:05 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 7,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:58:05 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:58:05 AM] [Envisalink-Ademco] partitionUpdate: status change -  {
partition: 8,
mode: 'AWAY',
code: 0,
status: 'Partition State Change'
}
[1/18/2023, 8:58:05 AM] [Envisalink-Ademco] Partition status change: Partition not monitored dismissing partition update.
[1/18/2023, 8:58:05 AM] [Envisalink-Ademco] Command | %00,01,1C28,08,00, DISARMED CHIME   Ready to Arm  $,00,01,1C28,08,00, DISARMED CHIME   Ready to Arm   | Acknowledged
[1/18/2023, 8:58:05 AM] [Envisalink-Ademco] Envisakit Operation: updatekeypad
[1/18/2023, 8:58:05 AM] [Envisalink-Ademco] systemUpdate: Status changed -  {
partition: '01',
code: {
icon: [ 3, 5, 10, 11, 12 ],
zone: '08',
beep: 'off',
txt: ' DISARMED CHIME   Ready to Arm  '
},
status: 'Virtual Keypad Update',
keypadledstatus: {
alarm: false,
alarm_in_memory: false,
armed_away: false,
ac_present: true,
bypass: false,
chime: true,
not_used1: false,
armed_zero_entry_delay: false,
alarm_fire_zone: false,
system_trouble: false,
not_used2: true,
not_used3: true,
ready: true,
fire: false,
low_battery: false,
armed_stay: false
},
mode: 'READY'
}
[1/18/2023, 8:58:07 AM] [Envisalink-Ademco] Checking for Heartbeat...
[1/18/2023, 8:58:07 AM] [Envisalink-Ademco] Heartbeat successful. Last message time: Wed Jan 18 2023 08:58:05 GMT-0800 (Pacific Standard Time)
2023-01-18T16:58:08.224Z HAP-NodeJS:EventedHTTPServer Currently 1 hap connections open: ::ffff:<IP_ADDRESS>:52434
[1/18/2023, 8:58:08 AM] [Envisalink-Ademco] Command | %00,01,1C28,08,00, DISARMED CHIME   Ready to Arm  $,00,01,1C28,08,00, DISARMED CHIME   Ready to Arm   | Acknowledged
[1/18/2023, 8:58:08 AM] [Envisalink-Ademco] Envisakit Operation: updatekeypad
[1/18/2023, 8:58:08 AM] [Envisalink-Ademco] systemUpdate: Status changed -  {
partition: '01',
code: {
icon: [ 3, 5, 10, 11, 12 ],
zone: '08',
beep: 'off',
txt: ' DISARMED CHIME   Ready to Arm  '
},
status: 'Virtual Keypad Update',
keypadledstatus: {
alarm: false,
alarm_in_memory: false,
armed_away: false,
ac_present: true,
bypass: false,
chime: true,
not_used1: false,
armed_zero_entry_delay: false,
alarm_fire_zone: false,
system_trouble: false,
not_used2: true,
not_used3: true,
ready: true,
fire: false,
low_battery: false,
armed_stay: false
},
mode: 'READY'
}
[1/18/2023, 8:58:18 AM] [Envisalink-Ademco] Command | %00,01,1C28,08,00, DISARMED CHIME   Ready to Arm  $,00,01,1C28,08,00, DISARMED CHIME   Ready to Arm   | Acknowledged
[1/18/2023, 8:58:18 AM] [Envisalink-Ademco] Envisakit Operation: updatekeypad
[1/18/2023, 8:58:18 AM] [Envisalink-Ademco] systemUpdate: Status changed -  {
partition: '01',
code: {
icon: [ 3, 5, 10, 11, 12 ],
zone: '08',
beep: 'off',
txt: ' DISARMED CHIME   Ready to Arm  '
},
status: 'Virtual Keypad Update',
keypadledstatus: {
alarm: false,
alarm_in_memory: false,
armed_away: false,
ac_present: true,
bypass: false,
chime: true,
not_used1: false,
armed_zero_entry_delay: false,
alarm_fire_zone: false,
system_trouble: false,
not_used2: true,
not_used3: true,
ready: true,
fire: false,
low_battery: false,
armed_stay: false
},
mode: 'READY'
}

Thanks, the output helps a lot I see the issue. The panel is sending an  'EXIT_DELAY' message, which I didn't see prior. Have to see what other messages can be sent from the panel which is not trapped during partition change. Labeling it as bug and will let you know when I postfix that you can use the test but will incorporate the fix into the next

Hi,
The new index.js and envisakit.js have been post they should correct this issue. The package solution will be released after some additional testing.

I'm eagerly awaiting this package release! Any ETA?

The update is still running locally at my house to assure nothing broke. Assuming no issues will try to post the updated update package this weekend. If you wish you can replace following files with current ones in the repo. It includes the fix to your issue.

envisalink.js
index.js
accessories/partitionAccessory.js

Corrected as part v2.0.4

Works perfect! Thank you.


Add some commands in makefile to generate docs

Codecov Report

Merging #15 (f1f282a) into master (83f4418) will decrease coverage by 0.13%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master     #15      +/-   ##
=========================================
- Coverage    6.48%   6.34%   -0.14%
=========================================
  Files          17      16       -1
  Lines         694     693       -1
=========================================
- Hits           45      44       -1
  Misses        649     649

Impacted Files
Coverage Δ

src/problems/bitstrings.jl
73.07% <ø> (ø)

src/Pidoh.jl

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 83f4418...f1f282a. Read the comment docs.


Let users control what the layer generation script does

The script previously tried to generate all 4 layers every time you run it. I was manually commenting out things to work faster on a new layer. This PR adds more CLI flags, so you specify what layer(s) you want.
Also, organize all of the intermediate files that get downloaded / processed into "tmp_XYZ" directories and have a nice "output/" directory.

I've added wards as a new layer in this PR too. (I don't want to diffbase two PRs)

Alright, this now includes wards, CAs, and LADs -- latter two from Pete's branch

Merging to avoid growing this one even further or diffbasing the next. Async review very welcome


[DO NOT MERGE UNTIL SERVICE TEAM DECIDES] Adding preview version of Event Hubs Cluster to Azure REST API specs.

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

We're in contact with Gaurav and have identified some issues. We're working on updating the spec now.

This commit was treated and no generation was made for Azure/azure-sdk-for-python

Was unable to create SDK Azure/azure-sdk-for-python PR for this closed PR.

This commit was treated and no generation was made for Azure/azure-sdk-for-go

This commit was treated and no generation was made for Azure/azure-sdk-for-python

Swagger to SDK encountered an unknown error: (Azure/azure-sdk-for-go)
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/swaggertosdk/github_tools.py", line 29, in exception_to_github
    yield context
  File "/usr/local/lib/python3.6/dist-packages/swaggertosdk/restapi/github.py", line 180, in rest_handle_action
    return rest_pull_close(body, github_con, restapi_repo, sdk_pr_target_repo, sdkbase)
  File "/usr/local/lib/python3.6/dist-packages/swaggertosdk/restapi/github.py", line 311, in rest_pull_close
    rest_pr.create_issue_comment("Was unable to create SDK %s PR for this closed PR.", sdkid)
TypeError: create_issue_comment() takes 2 positional arguments but 3 were given

This commit was treated and no generation was made for Azure/azure-sdk-for-go

Automation for azure-sdk-for-go

Automation for azure-sdk-for-python

I have updated the PR. It is now ready for final review from ARM team.

Looks good overall. Just a couple of small notes. Signing off from ARM.

Per linter failure there is no API for listing operations.  Is this intentional?
Also there is still [DO NOT MERGE] in the title of the PR, is this still the case?

@biberli We still waiting to merge this one?

@biberli ping, we still waiting to merge this?

Automation for azure-libraries-for-java

We've just made some additional changes recommended by ARM, including moving our capacity property to the sku property bag, and we've added a couple additional properties as well. We're now ready to merge! Please do so at your earliest convenience.

@biberli Thanks I'll remove the "DO NOT MERGE" from the PR title and review today.
There is one linter error about missing the list operations API which is an ARM requirement.  Is this intentional?

@biberli Also you need to update the README file with this new API version else no SDKs will be generated for this.

Automation for azure-sdk-for-node


simplifies vue useAutoAnimate composable and adds docs

Per some guidance I wrote recently, I changed useAutoAnimate to return a normal template ref instead of a function ref. The function ref is not necessary in this use case, and is more likely to confuse other devs compared to the more familiar template ref approach.

Just adjusted the composable to use watchEffect inside onMounted, watching the template ref for changes. This ensures that autoAnimate works with elements that are conditionally rendered with v-if and might not be present in the DOM yet when the component is mounted.
Each time v-if re-renders the element, the template ref will update, and the effect will run again to connect autoAnimate.


ONTOP-597 createDBConcatOperator now calls createNullRejectingDBConcat

was throwing UnsupportedOperationException.
Fixes #597

Hi @thomasjtaylor , thanks for the PR but || operator is actually not a concat operator in MySQL, it is an OR: https://dev.mysql.com/doc/refman/8.0/en/logical-operators.html#operator_or .
If we want to implement this method, we should  call getDBOr().
Here is a live example.
Best,
Benjamin

@bcogrel I suppose this would be a case for when MySQL is running with sessionVariables=sql_mode=ANSI or sessionVariables=sql_mode=PIPES_AS_CONCAT

The case of session variables in MySQL is indeed an interesting point. They basically change the semantics of the dialect.
I think at the moment we are able detect some of the changes, at least when it comes to quoting (to be double-checked). However the DBFunctionSymbolFactory at the moment ignores them and focuses on the standard semantics of MySQL.
I am unsure how attractive these session variables are in practice for a system like Ontop that is expected to behave well with the standard semantics. In my view, it is important to give clear priority to the standard semantics (what most users would expect I suppose). In that regard || should be interpreted by default as an OR, not a concat.


FileChunk Int32 overflow

Description
File downloading is not work correctly for files larger than Int32.MaxValue<PHONE_NUMBER> bytes). You will get error message from client "Error reading file" when you try _fileStream.Seek(offset, SeekOrigin.Begin); in method ReadChunk(long offset).
Bug in class Quasar.Common.IO.FileSplit
public IEnumerator<FileChunk> GetEnumerator()
        {
            for (int currentChunk = 0; currentChunk <= _fileStream.Length / MaxChunkSize; currentChunk++)
            {
                yield return ReadChunk(currentChunk * MaxChunkSize);
            }
        }

When pass arg to ReadChunk method currentChunk * MaxChunkSize is casting to Int32. We must declare currentChunk as long.
Expected behavior
public IEnumerator<FileChunk> GetEnumerator()
        {
            for (long currentChunk = 0; currentChunk <= _fileStream.Length / MaxChunkSize; currentChunk++)
            {
                yield return ReadChunk(currentChunk * MaxChunkSize);
            }
        }

Nice catch and very detailed error report. Thanks a lot!


README: releases link might give 404

maybe depending on how you reach the README.md, but the releases link is giving a 404 when using the link on "https://github.com/timescale/tobs" page, so replace it with full link
Second part of the diff is caused by doing a 'github' edit I guess, I don't see the diff on that line...

 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.

Thanks for your contribution! @heyleke :)


Tensorflow in Mininet

Expected/Desired Behavior:
tensorflow to be available to use
Actual Behavior:
Tensorflow is installed but not available in mininet xterm
Detailed Steps to Reproduce the Behavior:
install ubuntu 20.04
install python3 and pip3
install tensorflow
start mininet
run xterm h1
run pip list or pip freeze
Additional Information:
All others libs are available, only tensorflow is not.

Tensorflow - or problems with your python configuration - have nothing to do with Mininet.
Also you seem to be confusing pip and pip3.


Multiple partials with same file name, in different directories

I'm trying to migrate a large project to assemble. I have two partials named header.hbs, placed in different directories like this:
../partials/foo/header.hbs
../partials/bar/header.hbs
I've tried {{> foo/header }} and {{> 'foo/header' }} but those fail with Warning: The partial foo/header could not be found.
I can see in the verbose output that two partials with name header are created. {{> header }} succeeds, but will always return the second file (probably since it was the last one registered).
How can I reference a specific header partial?

grunt-assemble will only use the basename of the partial's filepath.
There is a registerPartial option that can be a function that gets the engine (handlebars), filename, and content properties.
This won't really help you here because filename will always be header.
Since we moved the original assemble code into this library, I think we'll consider any PRs that can make this easier and we can use proper semver versioning. Eventually, we'll be using more of the new features in assemble (like renameKey) which takes the entire filepath and allows updating how the key is created.

I see.
Thank you for the prompt reply.


Add rlGetProcAddress function

Hello, i implimented the rlGetProcAddress this allow users with bindings to load extenstions of OpenGL and more!

@MrScautHD I'm afraid this change couples rlgl with platform libraries. A lot of effort was put to avoid that coupling so I prefer to avoid this change.


Fix tests with QEMU 9.0

-no-acpi was removed in QEMU 9.0, see https://www.qemu.org/docs/master/about/removed-features.html#no-acpi-removed-in-9-0.

How backwards compatible is this? From the link it sounds like -machine acpi=off might be a new thing in QEMU 9.0.

I don't think it is that new, I'm at least seeing -machine acpi=off in QEMU 6.0 (https://gitlab.com/qemu-project/qemu/-/blob/stable-6.0/softmmu/vl.c#L3311-3313).

Thanks!


Add 'altText' to all sample cards

Related Issues

Closes #6424
Closes #6421

Description
Ensures "altText" is defined for all sample cards located in the samples folder. This includes template and non-template cards.
Microsoft Reviewers: Open in CodeFlow

/azp run android-ci.yml


Add stage/migrate annotations to backup/restore

https://github.com/fusor/ocp-velero-plugin/blob/master/velero-plugins/common/types.go#L31
This annotation is required for the plugin to work properly.
Fixes #74

It looks like you're missing "openshift.io/migrate-type" -- if this isn't set, the imagestream plugin won't copy images.

In reference to Scott's comment, we discussed in slack and I am going to set migrate-type to swing for now just so that the plugin doesn't break. We need to revisit this in the plugin to operate on the proper annotations because these annotations have changed meaning over time.


Lot of difficulty running functional tests

Support Request

Your Environment

Vagrant 1.9.2
VirtualBox 5.1.16r113841
ansible <IP_ADDRESS>
  config file =
  configured module search path = Default w/o overrides

Your OS

macOS 10.12.5 (16F73)

Full console output
One run:
Drupal\Tests\netforum_auth\Functional\AuthenticationTest::testAdminUserUsesDrupalAuthentication
rmdir(sites/simpletest/52528722): Operation not permitted

Another run:
Drupal\Tests\netforum_auth\Functional\AuthenticationTest::testAdminUserUsesDrupalAuthentication
Exception: Warning: file_put_contents(sites/simpletest/61504822/files/php/twig/597a393cb6709_form-element.html.twig_dJcTIbdx1y7B0dbOtEyyZSSZ1/.htaccess): failed to open stream: Permission denied
Drupal\Component\PhpStorage\FileStorage->ensureDirectory()() (Line: 122)

Summary
I initially posted about this here but did not get too far. None of the suggestions worked, so I am turning to the server side gurus here.
Sometimes the test runs without producing any error, other times it produces errors like the ones above. I don't really know why. File/folder ownership looks correct and is being generated by Drupal and executed as the Apache user.
Is there something I have not done in regards to setting this up? The test extends BrowserTestBase and only has one stub for checking the current user, just to get started. Sometimes I can run it multiple times in a row without issue, other times I get multiple errors.
I am running it from PHPStorm using the remote interpreter, as written in the drupal.org docs. I even tried running from the command line with the same results.

Are you running a recent version of Drupal VM? There were some permissions changes that could help out with the default NFS mount.
Other than that, can you provide a reliable set of steps to reproduce, ideally starting from a completely fresh/empty Drupal VM installation? I have been able to successfully run and debug Honeypot's simpletests, as well as Drupal Core phpunit tests, both from the CLI and within Drupal's UI.
However, I've never tried doing this stuff through PHPStorm. And I'm wondering if that's where the weirdness lies—so many of these little IDE conveniences seem to take hours and/or days to get working correctly for one person... I don't use PHPStorm much/if at all, so I can't be of much help there.

Did you try it with a recent version of Drupal VM?

This happens to me as well when running PHPUnit on the command line. Doesn't matter whether I run tests as vagrant or www-data
www-data@www:/var/www/drupalvm$ XDEBUG_CONFIG="remote_host=<IP_ADDRESS> remote_enable=On" PHP_IDE_CONFIG="serverName=www.fillpdf-service.com" ./phpunit.sh web/modules/contrib/fillpdf/tests/src/Functional/PdfPopulationTest.php
PHPUnit 4.8.36 by Sebastian Bergmann and contributors.

E

Time: 1.08 minutes, Memory: 6.00MB

There was 1 error:

1) Drupal\Tests\fillpdf\Functional\PdfPopulationTest::testPdfPopulation
rmdir(sites/simpletest/24402401/files/php/twig): Directory not empty

/var/www/drupalvm/web/core/lib/Drupal/Core/File/FileSystem.php:256
/var/www/drupalvm/web/core/includes/file.inc:1196
/var/www/drupalvm/web/core/includes/file.inc:922
/var/www/drupalvm/web/core/includes/file.inc:918
/var/www/drupalvm/web/core/includes/file.inc:918
/var/www/drupalvm/web/core/includes/file.inc:918
/var/www/drupalvm/web/core/tests/Drupal/Tests/BrowserTestBase.php:508
/var/www/drupalvm/web/core/tests/Drupal/Tests/BrowserTestBase.php:519

Going to try updating my Drupal VM code and see if that helps.

Pulled from repo, re-provisioned, reloaded VM. Running tests as vagrant (because that has always worked anyway). No luck :(
vagrant@www:/var/www/drupalvm$ XDEBUG_CONFIG="remote_host=<IP_ADDRESS> remote_enable=On" PHP_IDE_CONFIG="serverName=www.fillpdf-service.com" ./phpunit.sh web/modules/contrib/fillpdf/tests/src/Functional/PdfPopulationTest.php
PHPUnit 4.8.36 by Sebastian Bergmann and contributors.

E

Time: 58.5 seconds, Memory: 6.00MB

There was 1 error:

1) Drupal\Tests\fillpdf\Functional\PdfPopulationTest::testPdfPopulation
rmdir(sites/simpletest/14743438/files/php/twig): Directory not empty

/var/www/drupalvm/web/core/lib/Drupal/Core/File/FileSystem.php:256
/var/www/drupalvm/web/core/includes/file.inc:1196
/var/www/drupalvm/web/core/includes/file.inc:922
/var/www/drupalvm/web/core/includes/file.inc:918
/var/www/drupalvm/web/core/includes/file.inc:918
/var/www/drupalvm/web/core/includes/file.inc:918
/var/www/drupalvm/web/core/tests/Drupal/Tests/BrowserTestBase.php:508
/var/www/drupalvm/web/core/tests/Drupal/Tests/BrowserTestBase.php:519

FAILURES!
Tests: 1, Assertions: 18, Errors: 1.

Strange. Does it work if you run it on your Mac/workstation directly (and not in the VM)? It definitely seems permissions-related to me.

It might have been permissions. I know I somehow got past it. It might have been a red herring for something else. I don't recall now :(

K, for now I'll close this issue—if this happens again for someone, please file a new issue, and make sure to include any step-by-step instructions for reproducing on a fresh instance of Drupal VM (sometimes I guess it can be hard with project-specific tests... but if you can reproduce it with a contrib module or core test, that would be ideal!).


NEProvider objects cannot be instantiated from non-extension processes

i want write a flutter plugin for openvpn.  i git clone  plugin flutter_vpn and modify it.
i  replce code let p = NEVPNProtocolIKEv2() to let p = PacketTunnelProvider() and

code sample
/// A packet tunnel provider object.
class PacketTunnelProvider: NEPacketTunnelProvider {

    // MARK: Properties

    var _vpnAdapter = OpenVPNAdapter.init()
    var _openVpnReach = OpenVPNReachability.init()

    // MARK: NEPacketTunnelProvider

    /// Begin the process of establishing the tunnel.
    override func startTunnel(options: [String : NSObject]? = nil, completionHandler: @escaping (Error?) -> Void) {
        let fileContent = """
                                 <openvpn config file  fileContent>
                                 """ as String
               let dic = [
                               "fileContent": fileContent
                               ] as [String : String]
        let openVpnConfiguration = OpenVPNConfiguration()
        openVpnConfiguration.fileContent = fileContent.data(using: .utf8)
        openVpnConfiguration.peerInfo = dic
        openVpnConfiguration.disableClientCert = true
        var properties : OpenVPNProperties?
        do{
            try properties = self._vpnAdapter.apply(configuration: openVpnConfiguration)
            print(properties as Any)
            if !properties!.autologin {
               let credentials = OpenVPNCredentials()
               credentials.username = "tester"
               credentials.password = "tester"
               try self._vpnAdapter.provide(credentials: credentials)
                self._openVpnReach.startTracking { (OpenVPNReachabilityStatus) in
                    print("@@@@",OpenVPNReachabilityStatus)
                }
               self._vpnAdapter.connect();
           }
        }catch let error as NSError{
            print(error)
        }
    }

    /// Begin the process of stopping the tunnel.
    override func stopTunnel(with reason: NEProviderStopReason, completionHandler: @escaping () -> Void) {
        if(self._openVpnReach.isTracking){
            self._openVpnReach.stopTracking()
        }
        self._vpnAdapter.disconnect()
    }

    /// Handle IPC messages from the app.
    override func handleAppMessage(_ messageData: Data, completionHandler: ((Data?) -> Void)? = nil) {
        guard let messageString = NSString(data: messageData, encoding: String.Encoding.utf8.rawValue) else {
            completionHandler?(nil)
            return
        }

        print("Got a message from the app: \(messageString)")

        let responseData = "Hello app".data(using: .utf8)
        print("responseData",responseData as Any)
        completionHandler?(responseData)
    }

}

debug it , and got a error:

2020-01-08 16:13:37.664056+0800 Runner[2603:880696] [] NEProvider objects cannot be instantiated from non-extension processes

The problem is:
I known the NetworkExtension must run extension processes , but i want write a NetworkExtension code in plugin not in project Runner
Target Platform: iOS
Target OS version/browser: 13.2
Devices:

flutter doctor -v
[✓] Flutter (Channel stable, v1.12.13+hotfix.5, on Mac OS X 10.15.2 19C57, locale en-CN)
    • Flutter version 1.12.13+hotfix.5 at /Users/qiantao/development/flutter
    • Framework revision 27321ebbad (4 weeks ago), 2019-12-10 18:15:01 -0800
    • Engine revision 2994f7e1e6
    • Dart version 2.7.0

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/qiantao/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • ANDROID_HOME = /Users/qiantao/Library/Android/sdk
    • Java binary at: /Applications/pm_auto_install/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.2, Build version 11B52
    • CocoaPods version 1.7.5

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/pm_auto_install/Android Studio.app/Contents
    • Flutter plugin version 31.3.1
    • Dart plugin version 181.5656
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] Android Studio (version 3.4)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 39.0.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[✓] IntelliJ IDEA Ultimate Edition (version 2019.3.1)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 42.1.4
    • Dart plugin version 193.5731

[✓] VS Code (version 1.36.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.4.1

[✓] Connected device (1 available)
    • iPhone-qt • 82f7ff7c8283bd44680643f7c3fe327046866847 • ios • iOS 13.2

• No issues found!

Hi @guhan121
flutter_vpn is a 3rd party plugin
you may want to open an issue in the dedicated github.
Also, this platform is not meant for assistance on personal code.
Please see https://flutter.dev/community for resources for asking questions like this,
you may also get some help if you post it on Stack Overflow.
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
Thank you

i mean :
if i write a plugin for others. the plugin use  ios Extension . in the example Runner, i must Create a new packectTunnel target for demo.
like this

and user use this plugin,He must build such a target as I did
Is there a better way to implement this plugin?


Update GetLatestVersionAsync for NuGetPackageActions to include pre-release versions

Update GetLatestVersionAsync for NuGetPackageActions to include pre-release versions by default to match how the other package managers get the latest version. NPM and PyPI at least don't check for latest version not-including pre-releases.
We were having issues with getting the metadata for: https://www.nuget.org/packages/SlipeServer.Scripting/0.1.0-CI-20220607-083949 as all of the versions are pre-release versions.

Hmm. This looks to me like the flag already existed so the bug is actually that the other managers are not respecting the flag in the default configuration - since they should not be returning prereleases with it set to false right?
This also seems to be to kind of be a semver change in that it modifies an existing public api. Is there a reason you can't for your cases pass true for the use prerelease flag instead of modifying the lib?

Hmm. This looks to me like the flag already existed so the bug is actually that the other managers are not respecting the flag in the default configuration - since they should not be returning prereleases with it set to false right?

So there is currently a disconnect between all project managers and the NuGet project manager, where the method I changed the default value of the flag is only implemented on the NuGet project manager. At the time it made sense to include that flag and default it to false, however, with all other project managers not having an equivalent flag, it made sense to change the default to match the functionality of the rest of the project managers.

This also seems to be to kind of be a semver change in that it modifies an existing public api. Is there a reason you can't for your cases pass true for the use prerelease flag instead of modifying the lib?

The use prerelease flag isn't available that high up the call stack to the metadata call, but that could be added instead.
An alternative solution I had come up with is as follows:
// If we don't want pre-releases but all versions are pre-releases, then we have to include pre-releases to get a latest version.
if (!includePrerelease && versionsAscending.All(v => v.IsPrerelease))
{
    includePrerelease = true;
}
return versionsAscending
    .Last(v => includePrerelease || !v.IsPrerelease) // The latest version is the last in ascending order.
    .ToString();

Where essentially, if there are no versions of the package being called on that aren't a pre-release version then it will return the last pre-release version.

One other thought I had on this - the package managers other than NuGet don't support false for this flag today, correct? As in, they don't change the result when the flag is false?
If that's true, should we remove the flag entirely? Or have the other package managers throw NotSupportedException when that flag is false?

Hmm. This looks to me like the flag already existed so the bug is actually that the other managers are not respecting the flag in the default configuration - since they should not be returning prereleases with it set to false right?

So there is currently a disconnect between all project managers and the NuGet project manager, where the method I changed the default value of the flag is only implemented on the NuGet project manager. At the time it made sense to include that flag and default it to false, however, with all other project managers not having an equivalent flag, it made sense to change the default to match the functionality of the rest of the project managers.

I think I agree with Paul. Changing the default value here doesn't fix the problem if no managers except NuGet respect this value - it just makes it harder to notice.

This also seems to be to kind of be a semver change in that it modifies an existing public api. Is there a reason you can't for your cases pass true for the use prerelease flag instead of modifying the lib?

The use prerelease flag isn't available that high up the call stack to the metadata call, but that could be added instead. An alternative solution I had come up with is as follows:
// If we don't want pre-releases but all versions are pre-releases, then we have to include pre-releases to get a latest version.
if (!includePrerelease && versionsAscending.All(v => v.IsPrerelease))
{
    includePrerelease = true;
}
return versionsAscending
    .Last(v => includePrerelease || !v.IsPrerelease) // The latest version is the last in ascending order.
    .ToString();

Where essentially, if there are no versions of the package being called on that aren't a pre-release version then it will return the last pre-release version.

I'm not really a fan of this hidden behavior. If a user asks for the latest version but no pre-releases the result of the API call shouldn't be a pre-release - that violates the API contract where they said they didn't want pre-releases.
I don't think this is good to merge. I think either we need to implement the pre-release flag for every manager, or remove it. I don't think it makes sense to change the deafult.

I'm cool with removing the pre-release flag for NuGet until we can implement it across all managers.

@jpinz one note, this is technically a semver change so we theoretically should update the version.json to 0.2 - however, ossgadget is also major version 0 which allows for breaking changes and this is minor so maybe its okay?

@jpinz as I think about this more, is this really needed? If removing the check works wouldn't passing "true" for pre-release on the existing API also fix the issue in the same way?

Yes it would, the issue is that for us it's failing as a part of getting metadata. Which doesn't expose the includePrerelease flag.

@jpinz which API call do you mean for get metadata? I am having trouble finding that in the changes.

After further discussion we are pursuing adding the pre-release flag to the GetMetadataAsync api instead.

@gfs just updated the PR. Found a bug related to a lack of "tags" in nuget metadata so made a quick fix for that as well.
Added a lot of unit test coverage for the changes as well.


Add support printing as an error stack trace of checkA11y method

Example of test fail console log with Cucumber JS:
   ✖ Then user performs accessibility check # step_defs/pages/slideroom/app/general.steps.ts:15
       Error: Violations detected on page https://test-automation.slideroom-auto.net/#/marketing
           at Function.<anonymous> (/home/newfire/Desktop/work/qa-ui/framework/accessibility/AXE.ts:29:19)
           at step (/home/newfire/Desktop/work/qa-ui/framework/accessibility/AXE.ts:44:23)
           at Object.throw (/home/newfire/Desktop/work/qa-ui/framework/accessibility/AXE.ts:25:53)
           at rejected (/home/newfire/Desktop/work/qa-ui/framework/accessibility/AXE.ts:17:65)
   ✔ After # step_defs/setup.steps.ts:20

try {
            await checkA11y(page, elementContext, defaultOptions)
        } catch (err) {
            console.log("Error:", err)
            console.log(`^^^ Violations detected on page ${pageUrl} ^^^`)
            throw new Error(`Violations detected on page ${pageUrl}`)
        }

Error: AssertionError [ERR_ASSERTION]: 2 accessibility violations were detected
    at testResultDependsOnViolations (/home/newfire/Desktop/work/qa-ui/node_modules/axe-playwright/dist/index.js:61:26)
    at /home/newfire/Desktop/work/qa-ui/node_modules/axe-playwright/dist/index.js:52:5
    at Generator.next (<anonymous>)
    at fulfilled (/home/newfire/Desktop/work/qa-ui/node_modules/axe-playwright/dist/index.js:24:58) {
  generatedMessage: false,
  code: 'ERR_ASSERTION',
  actual: 2,
  expected: 0,
  operator: 'strictEqual',
  [Symbol(originalCallSite)]: [Array],
  [Symbol(mutatedCallSite)]: [Array]
}```

Hi @NazarYermolenko Lets make the idea clear. Currently even if the accessibility violations got detected, it passes the test. Do you want to fail the test if any of the violations got detected? In that case we can introduce a configuration param to handle the same. Thoughts?

@abhinaba-ghosh actually, I couldn't remember the core of the issue, I resolved it in some way. Anyway, I'd like to get the ability to manipulate accessibility violations detailed report from the code. Could you extend the functionality of ax-playwright to get a detailed report in the code, for example, to convert a detailed report to CSV, or to parse it any other way?

I'd like to get the ability to manipulate accessibility violations detailed report from the code.

That would be a really useful thing to have @NazarYermolenko. I would totally love if we could decouple the accessibility evaluation, reporting and violation result assertion.
Something that satisfies this interface will work great for me. I can simply parse the result myself, assert and fail a test run as I see fit.
getViolations(page: Page, context?: ElementContext, options?: Options): Promise<Result[]>

Going further I see value in having the ability to inject our own, user-defined reporter.
export interface Reporter {
  report(results: AxeResults): Promise<void>
}

// the current reporting capabilities are used as the default
printViolations(page: Page, reporter: Reporter, context?: ElementContext, options?: Options): Promise<Result[]>

Considering the library has the vast majority of it already implemented in some, should not be too massive of an undertaking.  Do you think it is a worthwhile undertaking @abhinaba-ghosh? I'm happy to get started with a small PR.

@cipivanov Sounds exciting. Please go-ahead.

Can you create necessary tickets for the feature and start working on them? This ticket will be a implementation of that feature. Will link those okce merged.

Can you create necessary tickets for the feature and start working on them? This ticket will be a implementation of that feature. Will link those okce merged.

@abhinaba-ghosh not sure if I understand exactly what you mean by this, could you please clarify?
I've submitted a PR for what we discussed above. Let me know what do you think.

@cipivanov changes are available in v1.1.8
Many thanks for the contribution.


Support CPU path for date_format function with timezone

PR includes:

Support no-fallback for date_format using Spark existing implement (running in CPU) for non-UTC time zone.
Depends on and merged https://github.com/NVIDIA/spark-rapids/pull/9719

Signed-off-by: Chong Gao<EMAIL_ADDRESS>

build

build

build

Please review the last commit.

build

build

This one is depending on https://github.com/NVIDIA/spark-rapids/pull/9814
When #9814 is merged, I'll then update this one.

build

build

pre-merge failed due to https://github.com/NVIDIA/spark-rapids/issues/10026

build


qcloud elb sync

这个 PR 实现什么功能/修复什么问题:

腾讯云同步及操作fix

是否需要 backport 到之前的 release 分支:

release/2.11
release/2.12
release/2.13
release/2.14
release/3.0
release/3.1

/area region
/cc @swordqiu @ioito @yousong

Codecov Report

Merging #5145 into master will decrease coverage by 0.01%.
The diff coverage is 3.79%.

@@            Coverage Diff            @@
##           master   #5145      +/-   ##
=========================================
- Coverage    6.74%   6.73%   -0.02%
=========================================
  Files         546     548       +2
  Lines       95305   95758     +453
=========================================
+ Hits         6433    6451      +18
- Misses      88334   88769     +435
  Partials      538     538

Flag
Coverage Δ

#aFlag
6.73% <3.79%> (-0.02%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/compute/models/regiondrivers.go
20% <ø> (ø)
:arrow_up:

pkg/compute/models/loadbalancerlistenerrules.go
1.86% <0%> (-0.07%)
:arrow_down:

pkg/compute/models/loadbalancerbackendgroups.go
1.48% <0%> (-0.05%)
:arrow_down:

pkg/compute/models/loadbalancerlisteners.go
1.36% <0%> (-0.11%)
:arrow_down:

pkg/compute/models/cloudsyncelb.go
0% <0%> (ø)
:arrow_up:

pkg/compute/models/loadbalancerqcloudcachedlbbg.go
4.73% <4.73%> (ø)

pkg/compute/models/loadbalancerqcloudcachedlbb.go
5.8% <5.8%> (ø)

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 dfaadc0...18cad47. Read the comment docs.

/lgtm

/lgtm

/lgtm

/approve

/approve

/approve


Updating Ubuntu CI to build Botan from source

I noticed that the latest Ubuntu box on github actions is on 22.04 which the botan package is at 2.19 and it looks like in new releases of ubuntu it is still 2.19,  Since it was a little disheartening to see the linux ci fail, I updated it to pull down botan 3.2.0 from source, build it, and install it. this should fix a couple of the failing linux builds on the main-ci run. it looks like ghc 9.2.8 and ghc 9.0.2 are still failing for linux.

@ldillinger is it possible to get this merged?

Apologies, somehow I missed this for some time. I will find some time to update this project over the holidays.

No problem love the library


ManyToMany relation not saved inside a @transition method

I struggle with a strange problem... I use fsm with pleasure since few days, just to change a state field and use action buttons in admin to switch the state. On one transition I do some updates in the db, by calling a self.my_update() on the model inside the @transition method. No problem.
Today I added a ManyToMany field on that model. When I call the method from outside fsm world, it works well. The m2m relation is created/updated as expected. But when the same method is called inside the @transition, the model fields are saved but not the m2m relations. I tried a lot of workaround (saving intensively...) but nothing helped. Mayby something related to transaction.
Any idea what could be the problem? Thx
edit: it seems related to django-fsm-admin, because a call to the transition method works as expected. So I move there...

django-fsm 2,0 designed in assumption that .save method would be called outside of transition method
I've placed the next versino of django.fsm into the viewflow.fsm package. New approach separates models and fsm definitions, to allow explicit save(...) and other parameters changes.
https://docs-next.viewflow.io/fsm/models.html


docs: link to cem/a

What I did

Add a Custom Elements Manifest page under "Tools"
install rocket-preset-code-tabs
add code tabs for npm/yarn/pnpm in a few places
👉drop tests for node 12👈

one of the deps to rocket-preset-code-tabs needs node 14 or higher.
acc'd to https://nodejs.org/en/about/releases/ v12 has another year of maintenance to go. How should we proceed?

I fixed the incompatible node 12 tests in this pr by removing node 12 from the test matrix. 14 is lts, it's widely supported, and we've already dropped 12 in create, so this should be ok. cc @LarsDenBakker @daKmoR


Any Snippets about placing items like instancing?

Hi,
are there any minimal snippets that can place an element and eventually duplicate it's material and do modifications?
Thanks

Found a good reference actually from the examples:
https://github.com/20tab/UnrealEnginePython/blob/master/examples/editor_scripting001.py

If you have time, would you like to add a snippet about instancing in the repository ? Thanks


feat: 3332 - crop page title now reflects image field

Impacted files:

confirm_and_upload_picture.dart: minor refactoring
crop_helper.dart: added a pageTitle parameter
edit_ingredients_page.dart: minor refactoring
image_crop_page.dart: added imageField parameters, so that we can compute the correct label on crop page
image_upload_card.dart: now we explicitly use getProductImageButtonText as label
new_crop_page.dart: added a page title parameter
product_cards_helper.dart: new label method getImagePageTitle; minor refactoring
product_image_carousel.dart: minor refactoring
product_image_data.dart: removed label fields - now we have more flexibility, computing labels from imageField with product_cards_helper.dart methods
product_image_gallery_view.dart: minor refactoring
product_image_swipeable_view.dart: now we explicitly use getImagePageTitle as label
product_image_viewer.dart: minor refactoring
smooth_images_sliver_list.dart: now we explicitly use getProductImageTitle as label
smooth_product_image.dart: minor refactoring

What

Very first step of #3332: the crop page title now reflects the image field (instead of a mere "Edit image")
That was a good opportunity to refactor actually, by removing "labels" from ProductImageData that were not really useful

Screenshot

Part of

#3332

Possible variations:

"edit" before
"edit" after

Codecov Report

Merging #3366 (4e6e1c4) into develop (69968c2) will increase coverage by 0.00%.
The diff coverage is 0.00%.

:exclamation: Current head 4e6e1c4 differs from pull request most recent head 59ae41b.  Learn more

@omkarChend1kar ping

@omkarChend1kar ping

Hii @monsieurtanuki ,I didn't get you.

@omkarChend1kar ping

Hii @monsieurtanuki ,I didn't get you.

I think it's time you review this PR!!

Thank you @omkarChend1kar for your review!
Actually you're wrong, we still use it there: getImagePageTitle(appLocalizations, _imageDataList[index].imageField)
There would have been a warning if useless anyway.
@M123-dev @AshAman999 May you approve too? Not that I don't trust @omkarChend1kar, but for some reason I'm not able to merge even with one approval. Not enough seniority on this project maybe...

Thank you @omkarChend1kar for your review! Actually you're wrong, we still use it there: getImagePageTitle(appLocalizations, _imageDataList[index].imageField) There would have been a warning if useless anyway.
@M123-dev @AshAman999 May you approve too? Not that I don't trust @omkarChend1kar, but for some reason I'm not able to merge even with one approval. Not enough seniority on this project maybe...

Yeah, Right missed it completely.

The first option looks like a good improvement. Does it degrade gracefully if translated texts are longer ?

You mean "edit before", right?
I'll check with lorem ipsum.

Nothing special, 1 review needed to merge.

Nothing special, 1 review needed to merge.

There seems to be different review colors, and the concept of "reviewer with write access":

We cannot display more than 2 lines in the title, but the overflow can be handled "in fade mode":

Thank you @omkarChend1kar @teolemon @AshAman999 for your help!


(PUP-4342) add acceptance to call all parser functions

This change adds a test for all parser functions.
This test calls all the parser functions that ship with puppet. It
ensures sane output in most cases. The remainder of the coverage for
functions lies in the spec tests.

@er0ck is this still needed given https://github.com/puppetlabs/puppet/pull/3917 was merged to master? Or is this a backport?

it's a backport.  some folks (including @hlindberg, IIRC) thought it might be important to get into 3.x.
i guess we all forgot about the second PR on the ticket... :-\

@er0ck @hlindberg do you want to add a ticket to your sprint so this work gets backported?

what work needs to be done to merge?  as far as i can tell it's ready to go.

@er0ck just that someone needs to own reviewing and merging it, and updating it if there are any 3.x differences that shake out in CI. Also, since this PR is from May, were any other changes made to puppet#master since that time, and this PR for 3.x should be updated accordingly? I'd prefer someone from the language team do this, since you guys did the original work.

+1 on merging - @er0ck will there be merge problems (merging 3.x -> stable -> master) because of this?

i'll add a ticket to the sprint starting today, in the doing column so i can investigate any merge issues prior to forcing someone to review.  thanks josh

yeah, this will cause issues when merging up to stable/master. we should divide the test in two parts, 3.x only and 4.x only.  4.x only test-file won't live in 3.x branch.  this PR will be for merging to 3.x.  i'll create a separate PR for removing the 3.x portion from stable.  later merges from 3.x to stable will re-enable testing of the 3.x functions in 4+ branches.


Despector fails to parse certain signatures

Stack trace:
https://paste.wut.ee/obixajavat.rb
Kotlin class:
https://paste.wut.ee/mokayazonu.cpp
ASMifier dump of target class:
https://paste.wut.ee/oviyoxoyij.java

Yes https://github.com/Despector/Despector/blob/master/src/main/java/org/spongepowered/despector/util/SignatureParser.java#L185 :)

Oh, haven't peeked into source yet :smile: no wonder


Branch 2.1

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)
Please review http://spark.apache.org/contributing.html before opening a pull request.

Can one of the admins verify this patch?

Hi @bupt2012, it seems this PR is mistakenly open. Could you please close this?

Hi @bupt2012, could you just click the "Close pull request" button below?

@bupt2012 please close this PR.

mistakenly opened? close it please!


Create and populate the eLife Biochemistry and Chemical Biology list

Ran over all events. Failed to get subject area for three DOIs:

10.1101/2<IP_ADDRESS>84051
10.1101/2<IP_ADDRESS>65656
10.1101/2<IP_ADDRESS>81628

Tried adding this event into the backstop data, but atm the list count on the group card is incorrect with this data, so not changing that backstop test to use this event until the list count is also correct. The event code below is for reference so we don't have to invent it all over again!
0a485144-5015-402a-b41e-4cf4d82b1eee,ListCreated,2022-03-10 11:40:00,"{""listId"": ""2c369dbd-0174-45c2-aa88-b94184f7305a"", ""name"": ""Bogus list"", ""description"": ""Bogus description"", ""ownerId"": ""74fd66e9-3b90-4b5a-a4ab-5be83db4c5de""}"```


Remove broken goback logic when token expires (SCRD-5747)

The logic to "goBack" to the page that timed out isn't working and causes the user to have to login twice (only to be taken to the default landing page anyway). For now, removed the extra logic, which fixes the double login problem.

Note: if you want to try this out this code change, see the notes in the JIRA defect for getting things setup

It seems to fix the problem, but of course after logging in, we are not attempting to go back to the page that the user was on. Perhaps that can be addressed in another change, if that functionality is still desired.

Ideally that would be the behavior. I played around with the history goBack() and go() functions a bit without much success, but I think at this point its more important not to have the double login

@guglo were you running minimized or in dev mode? if you run via run_dist.sh you should see the different behavior... in dev mode the error is replaced by a CORS error that I didnt work on since customers wont see it

@jeremy-moffitt thanks, will try again.


DataManager checkError Method

Complete Error Checking as much as possible. There may be future additions to this method
{t:110}


Accuracy=0 ,Loss=0, Perplexity = 1 during evaluate

When I run the evaluate progress while training,  the eval result always staying at ''Accuracy=0 ,Loss=0, Perplexity = 1 " ,   who know what's wrong with this .
I use cuda9+cudnn7+tf1.11 .

which model?

@adarob   melody_rnn

observed the same thing with newly trained performance_rnn model (run eval once after the training).
there were other problems with that process though, possibly unrelated -  https://github.com/tensorflow/magenta/issues/1364

I'm facing the same issue. Has there been any solution found to this?

Is it possible your training set is empty? How many examples are you training on?

The training set wasn't empty. The training of the model was done successfully. Am using this MIDI dataset here: https://mega.nz/#!Elg1TA7T!MXEZPzq9s9YObiUcMCoNQJmCbawZqzAkHzY4Ym6Gs_Q. I converted these MIDI files in NodeSequences and then SequenceExamples as per the tutorial given for Melody RNN.


fix the order of the replacement example

I don't think this is correct, although it depends on the behavior you want. Note that the order in the csv files is opposite that in Python, or a line cache,cash in words_to_replace.csv correspond with a dictionary entry "cash": "cache" in Python.

I don't think this is correct, although it depends on the behavior you want. Note that the order in the csv files is opposite that in Python, meaning a line cache,cash in words_to_replace.csv correspond with a dictionary entry "cash": "cache" in Python.

Oh I had misunderstood that, thank you! I think it would be great if you noted that in the comment, for future viewers. Thanks!


Problem saving album.

Hello. If there is a colon in the release title, then I can't upload such an album due to an error - os error 267.

Yes. I have a windows system.

Try new version https://github.com/skarrok/zvuk-dl-rs/releases/tag/v0.2.1
Reserved characters such as : will be converted to _.

Да, теперь нормально всё качает. Спасибо тебе мил человек за такой полезный софт)

I'm glad you enjoy it.
Thanks!


Providing names explicitly for some objects may be redundant, why not assign them automatically ?

p1, p2 = config.ports.port(name='p1').port(name='p2')

c1 = config.capture.capture(name='c1')
c1.port_names = [p1.name]

vs
p1, p2 = config.ports.port().port()

c1 = config.capture.capture()
c1.port_names = [p1.name]

This needs more refinement and further discussion.

new issue in openapiart addresses this feature request https://github.com/open-traffic-generator/openapiart/issues/195


constant reboots with update --update-mods

I have have 4 servers with 2 sets of different mods. I have a crontab scheduled to check for mod updates every 15 minutes. The update script I am using is being called correctly. The servers are updating when needed but keep rebooting even though there is no update ready.
Ark Update Script:
arkmanager update --validate --update-mods --warn @Server1 @Server2 @Server3 @Server4
I have steamdataroot=/home/steam/steam in arkmanager.cfg
I have tried /home/steam, ~$HOME/.steam, /home/steam/.steam.
The directories exist but nothing is being written. Currently my servers are installed to the /home/steam folder. I can move them into a common folder if that helps. Not sure what else to try.
Thanks for an awesome tool. it has improved my life 200 fold.

--validate will force a re-download of the server and mod-files each time your script is run, you should remove it from any script and only use it when you actually need to validate game or re-download mod files (have had to do it a couple of times when Classic Flyers update didn't take)

Thank you!
I knew it had to be something I'm doing wrong. It appears to be working now!


Allow loading of password protected private keys

The current implementation has a method to load private keys without requiring their password.
  ISignatureContext = interface
// snip
    procedure LoadKey(AStream: TStream; AFormat: TKeyDataFormat; AOwnsStream: Boolean);
// snip

The implementation class makes a call to the underlying xmlsec API, assuming there is no password
procedure TSignatureContext.LoadKey(AStream: TStream; AFormat: TKeyDataFormat;
  AOwnsStream: Boolean);
//snip
    // load private key, assuming that there is not password */
    dsigCtx.signKey := xmlSecCryptoAppKeyLoadMemory(data, dataSize, xmlSecKeyDataFormat(AFormat), nil, nil, nil);
// snip

I am proposing to overload the method to allow for a password to be provided.

So the proposed change is to simply add an optional param to the method signature
  ISignatureContext = interface
// snip
    procedure LoadKey(AStream: TStream; AFormat: TKeyDataFormat; AOwnsStream: Boolean; APassword: string = '');

and to the concrete class
  TSignatureContext = class(TInterfacedObject, ISignatureContext)
//snip
    procedure LoadKey(AStream: TStream; AFormat: TKeyDataFormat; AOwnsStream: Boolean; APassword: string = '');
// snip

procedure TSignatureContext.LoadKey(AStream: TStream; AFormat: TKeyDataFormat; AOwnsStream: Boolean; APassword: string);
var
//snip
  Pass: PAnsiChar; // new var to hold password
begin
//snip
    Pass := PAnsiChar(Pointer(AnsiString(APassword)));  // convert password to xmlsec compatible type
    dsigCtx.signKey := xmlSecCryptoAppKeyLoadMemory(data, dataSize, xmlSecKeyDataFormat(AFormat), Pass, nil, nil);
//snip

This handles the case where the private key has not been protected with a password, also the case where there is a password.


Support Butler file objects

DESC Requirement
This depends on File object issues #9 and #38

[ ]  Explore butler file objects.
[ ]  How to determine if butler file objects were created.
[ ]  Identify when a butler output is a collection ?

This is still very vague and needs research into what is needed to support butler data objects in Parsl workflows. With all the unknowns this should be Parsl-0.5.0. Perhaps @annawoodard could help understand this space better.
Butler info: https://github.com/lsst/daf_butler

@yadudoc and @danielskatz to make some time next Tuesday to discuss Butler issues further

also see https://confluence.lsstcorp.org/display/DM/Data+Butler+Working+Group

Another design doc : https://confluence.lsstcorp.org/display/DM/Data+Butler+-+Current+Design