Battery Powered devices marked as DEAD

Some battery powered devices like ZW100 MultiSensor 6 (AEON Labs) are detected as DEAD after stratup and do not have the type/product fields loaded. (zwcfg has the device with all the info)
Under settings -> zwave I have Assume Awake toggled disabled.
The only way for the device to show online is by manually waking it (physically) and sending a NIF request to the device. After that it will be correctly marked as sleeping

(I managed to get most things working aside from battery level and the very annoying issues with switches, linking these to homekit using node-red is causing mayham due to the multiple conflicting state changes, I backed this config so I can quickly go back to the state I am at now. But I did revert to OpenHAB for my current flow as now so I have a working setup)

Did you try to set the Assume Awake option enabled? Battery powered devices usually need that to be awaken on init

I thank you for your feedbacks and I will try to fix them all but some bugs related with the protocols most times are related to node-openzwave and Openzwave library, maybe you can find your issues there too

Well thats the thing, the device is not awake at startup because it sleeps for ~20min and then sends an update. (Unless there is movement, then it sends it imediatly)
Wouldn't assume awake make it worse? I think the table should alteast load the type/product info from the zcfg.zml file in that case. I can see this getting very confusing if there are multiple battery devices.
Also the type/product does not get update once the devices checks it, the node state is properly set to 'Sleep' after the first update though.
--- that was a bit confusing, let me try in a few bullets

Wouldn't setting Assume Awake make it worse? As the battery devices are sleeping.
It would be nice to load the type/product info form the zcfg.xml if a device is not responding on startup.
The type/product info does not get update once the device wakes up and sends data
The state of the node is OK after the first wakeup and set to sleeping.

I can try to fetch the type/product from zwcfg_...xml file on init but I don't know how to detect devices as sleeping on start, try to send testNode on a device, does the state is correctly updated to sleeping then?

Does send a NIF request to the sleeping nodes on init would fix the problem?

Try with this fix ed6acb0929dde014d821fbcca32916e1677ae384 and let me know @sjorge

That didn't help, as the node deos not respond to a NIF command while it is sleeping.
Here is the log from the startup
2019-03-11T12:33:32.478Z z2m:Store scenes.json not found
2019-03-11T12:33:32.913Z z2m:App Application path:/opt/zwave2mqtt
Initialising OpenZWave 1.4.3365 binary addon for Node.JS.
        OpenZWave Security API is ENABLED
        ZWave device db    : /opt/local/etc/openzwave
        User settings path : /opt/zwave2mqtt
        Option Overrides : --Logging false --ConsoleOutput false --QueueLogLevel 6 --DriverMaxAttempts 9999 --SaveConfiguration true --PollInterval 15000 --NetworkKey 0x58,0x50,0x3A,0x1C,0x0A,0xD7,0x66,0x6D,0x27,0x78,0x67,0x4C,0x1E,0xCB,0xC4,0x61
2019-03-11T12:33:33.030Z z2m:Zwave Connecting to /dev/cua/0
2019-03-11T12:33:33.129Z z2m:App Listening on port 8091
2019-03-11T12:33:33.203Z z2m:Mqtt MQTT client connected
2019-03-11T12:33:33.217Z z2m:Zwave Scanning network with homeid: 0xfc20d090
2019-03-11T12:33:33.218Z z2m:Zwave Node added 1
2019-03-11T12:33:33.220Z z2m:Zwave ValueAdded: 1-32-1-0 Basic
2019-03-11T12:33:33.220Z z2m:Zwave Node added 2
2019-03-11T12:33:33.223Z z2m:Zwave ValueAdded: 2-48-1-0 Sensor
2019-03-11T12:33:33.223Z z2m:Zwave ValueAdded: 2-49-1-1 Temperature
2019-03-11T12:33:33.224Z z2m:Zwave ValueAdded: 2-49-1-3 Luminance
2019-03-11T12:33:33.224Z z2m:Zwave ValueAdded: 2-49-1-5 Relative Humidity
2019-03-11T12:33:33.224Z z2m:Zwave ValueAdded: 2-49-1-27 Ultraviolet
2019-03-11T12:33:33.224Z z2m:Zwave ValueAdded: 2-94-1-0 ZWave+ Version
2019-03-11T12:33:33.224Z z2m:Zwave ValueAdded: 2-94-1-1 InstallerIcon
2019-03-11T12:33:33.225Z z2m:Zwave ValueAdded: 2-94-1-2 UserIcon
2019-03-11T12:33:33.225Z z2m:Zwave ValueAdded: 2-112-1-2 Wake up 10 minutes on Power On
2019-03-11T12:33:33.225Z z2m:Zwave ValueAdded: 2-112-1-3 On time
2019-03-11T12:33:33.225Z z2m:Zwave ValueAdded: 2-112-1-4 Enable Motion Sensor
2019-03-11T12:33:33.225Z z2m:Zwave ValueAdded: 2-112-1-5 Command Options
2019-03-11T12:33:33.226Z z2m:Zwave ValueAdded: 2-112-1-8 Awake timeout
2019-03-11T12:33:33.226Z z2m:Zwave ValueAdded: 2-112-1-9 Current power mode
2019-03-11T12:33:33.226Z z2m:Zwave ValueAdded: 2-112-1-39 Low Battery
2019-03-11T12:33:33.226Z z2m:Zwave ValueAdded: 2-112-1-40 Report Only On Thresholds
2019-03-11T12:33:33.226Z z2m:Zwave ValueAdded: 2-112-1-41 Temperature Reporting Threshold
2019-03-11T12:33:33.227Z z2m:Zwave ValueAdded: 2-112-1-42 Humidity Reporting Threshold
2019-03-11T12:33:33.227Z z2m:Zwave ValueAdded: 2-112-1-43 Luminance Reporting Threshold
2019-03-11T12:33:33.227Z z2m:Zwave ValueAdded: 2-112-1-44 Battery Reporting Threshold
2019-03-11T12:33:33.227Z z2m:Zwave ValueAdded: 2-112-1-45 UV Reporting Threshold
2019-03-11T12:33:33.227Z z2m:Zwave ValueAdded: 2-112-1-46 Low Temp Alarm
2019-03-11T12:33:33.228Z z2m:Zwave ValueAdded: 2-112-1-48 Enable/disable to send a report on Threshold
2019-03-11T12:33:33.228Z z2m:Zwave ValueAdded: 2-112-1-49 Set the upper limit value of temperature sensor
2019-03-11T12:33:33.228Z z2m:Zwave ValueAdded: 2-112-1-50 Set the lower limit value of temperature sensor
2019-03-11T12:33:33.228Z z2m:Zwave ValueAdded: 2-112-1-51 Set the upper limit value of humidity sensor
2019-03-11T12:33:33.228Z z2m:Zwave ValueAdded: 2-112-1-52 Set the lower limit value of humidity sensor
2019-03-11T12:33:33.229Z z2m:Zwave ValueAdded: 2-112-1-53 Set the upper limit value of Lighting sensor
2019-03-11T12:33:33.229Z z2m:Zwave ValueAdded: 2-112-1-54 Set the lower limit value of Lighting sensor
2019-03-11T12:33:33.229Z z2m:Zwave ValueAdded: 2-112-1-55 Set the upper limit value of ultraviolet sensor
2019-03-11T12:33:33.229Z z2m:Zwave ValueAdded: 2-112-1-56 Set the lower limit value of ultraviolet sensor
2019-03-11T12:33:33.230Z z2m:Zwave ValueAdded: 2-112-1-57 Set the recover limit value of temperature sensor
2019-03-11T12:33:33.230Z z2m:Zwave ValueAdded: 2-112-1-58 Set the recover limit value of humidity sensor
2019-03-11T12:33:33.230Z z2m:Zwave ValueAdded: 2-112-1-59 Set the recover limit value of Lighting sensor
2019-03-11T12:33:33.230Z z2m:Zwave ValueAdded: 2-112-1-60 Set the recover limit value of Ultraviolet sensor
2019-03-11T12:33:33.231Z z2m:Zwave ValueAdded: 2-112-1-61 Get the out-of-limit state of the Sensors
2019-03-11T12:33:33.231Z z2m:Zwave ValueAdded: 2-112-1-64 Temperature scale
2019-03-11T12:33:33.231Z z2m:Zwave ValueAdded: 2-112-1-81 LED blinking report
2019-03-11T12:33:33.231Z z2m:Zwave ValueAdded: 2-112-1-100 Reset Params 101-103 to Default
2019-03-11T12:33:33.232Z z2m:Zwave ValueAdded: 2-112-1-101 Group 1 Reports
2019-03-11T12:33:33.232Z z2m:Zwave ValueAdded: 2-112-1-102 Group 2 Reports
2019-03-11T12:33:33.232Z z2m:Zwave ValueAdded: 2-112-1-103 Group 3 Reports
2019-03-11T12:33:33.232Z z2m:Zwave ValueAdded: 2-112-1-110 Reset Params 111-113 to Default
2019-03-11T12:33:33.232Z z2m:Zwave ValueAdded: 2-112-1-111 Group 1 Interval
2019-03-11T12:33:33.232Z z2m:Zwave ValueAdded: 2-112-1-112 Group 2 Interval
2019-03-11T12:33:33.233Z z2m:Zwave ValueAdded: 2-112-1-113 Group 3 Interval
2019-03-11T12:33:33.233Z z2m:Zwave ValueAdded: 2-112-1-201 Temperature Calibration
2019-03-11T12:33:33.233Z z2m:Zwave ValueAdded: 2-112-1-202 Humidity Calibration
2019-03-11T12:33:33.233Z z2m:Zwave ValueAdded: 2-112-1-203 Luminance Calibration
2019-03-11T12:33:33.233Z z2m:Zwave ValueAdded: 2-112-1-204 Ultraviolet Calibration
2019-03-11T12:33:33.234Z z2m:Zwave ValueAdded: 2-112-1-252 Enable/disable Lock Configuration
2019-03-11T12:33:33.234Z z2m:Zwave ValueAdded: 2-112-1-255 Reset To Factory Defaults
2019-03-11T12:33:33.234Z z2m:Zwave ValueAdded: 2-113-1-0 Alarm Type
2019-03-11T12:33:33.234Z z2m:Zwave ValueAdded: 2-113-1-1 Alarm Level
2019-03-11T12:33:33.234Z z2m:Zwave ValueAdded: 2-113-1-2 SourceNodeId
2019-03-11T12:33:33.235Z z2m:Zwave ValueAdded: 2-113-1-10 Burglar
2019-03-11T12:33:33.235Z z2m:Zwave ValueAdded: 2-115-1-0 Powerlevel
2019-03-11T12:33:33.235Z z2m:Zwave ValueAdded: 2-115-1-1 Timeout
2019-03-11T12:33:33.235Z z2m:Zwave ValueAdded: 2-115-1-2 Set Powerlevel
2019-03-11T12:33:33.235Z z2m:Zwave ValueAdded: 2-115-1-3 Test Node
2019-03-11T12:33:33.235Z z2m:Zwave ValueAdded: 2-115-1-4 Test Powerlevel
2019-03-11T12:33:33.236Z z2m:Zwave ValueAdded: 2-115-1-5 Frame Count
2019-03-11T12:33:33.236Z z2m:Zwave ValueAdded: 2-115-1-6 Test
2019-03-11T12:33:33.236Z z2m:Zwave ValueAdded: 2-115-1-7 Report
2019-03-11T12:33:33.236Z z2m:Zwave ValueAdded: 2-115-1-8 Test Status
2019-03-11T12:33:33.236Z z2m:Zwave ValueAdded: 2-115-1-9 Acked Frames
2019-03-11T12:33:33.237Z z2m:Zwave ValueAdded: 2-128-1-0 Battery Level
2019-03-11T12:33:33.237Z z2m:Zwave ValueAdded: 2-132-1-1 Minimum Wake-up Interval
2019-03-11T12:33:33.237Z z2m:Zwave ValueAdded: 2-132-1-2 Maximum Wake-up Interval
2019-03-11T12:33:33.237Z z2m:Zwave ValueAdded: 2-132-1-3 Default Wake-up Interval
2019-03-11T12:33:33.237Z z2m:Zwave ValueAdded: 2-132-1-4 Wake-up Interval Step
2019-03-11T12:33:33.237Z z2m:Zwave ValueAdded: 2-132-1-0 Wake-up Interval
2019-03-11T12:33:33.238Z z2m:Zwave ValueAdded: 2-134-1-0 Library Version
2019-03-11T12:33:33.238Z z2m:Zwave ValueAdded: 2-134-1-1 Protocol Version
2019-03-11T12:33:33.238Z z2m:Zwave ValueAdded: 2-134-1-2 Application Version
2019-03-11T12:33:33.238Z z2m:Zwave Node added 4
2019-03-11T12:33:33.238Z z2m:Zwave ValueAdded: 4-37-1-0 Switch
2019-03-11T12:33:33.239Z z2m:Zwave ValueAdded: 4-39-1-0 Switch All
2019-03-11T12:33:33.239Z z2m:Zwave ValueAdded: 4-50-1-0 Energy
2019-03-11T12:33:33.239Z z2m:Zwave ValueAdded: 4-50-1-1 Previous Reading
2019-03-11T12:33:33.239Z z2m:Zwave ValueAdded: 4-50-1-2 Interval
2019-03-11T12:33:33.239Z z2m:Zwave ValueAdded: 4-50-1-8 Power
2019-03-11T12:33:33.240Z z2m:Zwave ValueAdded: 4-50-1-16 Voltage
2019-03-11T12:33:33.240Z z2m:Zwave ValueAdded: 4-50-1-20 Current
2019-03-11T12:33:33.240Z z2m:Zwave ValueAdded: 4-50-1-32 Exporting
2019-03-11T12:33:33.240Z z2m:Zwave ValueAdded: 4-50-1-33 Reset
2019-03-11T12:33:33.240Z z2m:Zwave ValueAdded: 4-94-1-0 ZWave+ Version
2019-03-11T12:33:33.241Z z2m:Zwave ValueAdded: 4-94-1-1 InstallerIcon
2019-03-11T12:33:33.241Z z2m:Zwave ValueAdded: 4-94-1-2 UserIcon
2019-03-11T12:33:33.241Z z2m:Zwave ValueAdded: 4-112-1-3 Over current protection
2019-03-11T12:33:33.241Z z2m:Zwave ValueAdded: 4-112-1-4 Over heat protection
2019-03-11T12:33:33.241Z z2m:Zwave ValueAdded: 4-112-1-20 Status re-power on
2019-03-11T12:33:33.241Z z2m:Zwave ValueAdded: 4-112-1-21 WallSwipe IR sensor
2019-03-11T12:33:33.242Z z2m:Zwave ValueAdded: 4-112-1-64 WallSwipe button color
2019-03-11T12:33:33.242Z z2m:Zwave ValueAdded: 4-112-1-65 WallSwipe LED Up gesture action
2019-03-11T12:33:33.242Z z2m:Zwave ValueAdded: 4-112-1-66 WallSwipe LED Down gesture action
2019-03-11T12:33:33.242Z z2m:Zwave ValueAdded: 4-112-1-67 WallSwipe LED Left gesture action
2019-03-11T12:33:33.243Z z2m:Zwave ValueAdded: 4-112-1-68 WallSwipe LED Right gesture action
2019-03-11T12:33:33.243Z z2m:Zwave ValueAdded: 4-112-1-69 WallSwipe Night light
2019-03-11T12:33:33.243Z z2m:Zwave ValueAdded: 4-112-1-71 WallSwipe sensitivity
2019-03-11T12:33:33.243Z z2m:Zwave ValueAdded: 4-112-1-80 Notification report association group 1
2019-03-11T12:33:33.243Z z2m:Zwave ValueAdded: 4-112-1-81 Notification report using the external switch 1
2019-03-11T12:33:33.244Z z2m:Zwave ValueAdded: 4-112-1-82 Notification report using the external switch 2
2019-03-11T12:33:33.244Z z2m:Zwave ValueAdded: 4-112-1-83 LED status
2019-03-11T12:33:33.244Z z2m:Zwave ValueAdded: 4-112-1-84 Time set for Night light mode
2019-03-11T12:33:33.244Z z2m:Zwave ValueAdded: 4-112-1-86 Set the ON time of output load
2019-03-11T12:33:33.244Z z2m:Zwave ValueAdded: 4-112-1-87 Set the OFF time of output load
2019-03-11T12:33:33.245Z z2m:Zwave ValueAdded: 4-112-1-90 Enable/disable the parameter 91 and 92
2019-03-11T12:33:33.245Z z2m:Zwave ValueAdded: 4-112-1-91 Minimum Change to send Report (Watt)
2019-03-11T12:33:33.245Z z2m:Zwave ValueAdded: 4-112-1-92 Minimum Change to send Report (%)
2019-03-11T12:33:33.245Z z2m:Zwave ValueAdded: 4-112-1-100 Default Group Reports
2019-03-11T12:33:33.245Z z2m:Zwave ValueAdded: 4-112-1-101 Report type sent in Reporting Group 1
2019-03-11T12:33:33.245Z z2m:Zwave ValueAdded: 4-112-1-102 Report type sent in Reporting Group 2
2019-03-11T12:33:33.246Z z2m:Zwave ValueAdded: 4-112-1-103 Report type sent in Reporting Group 3
2019-03-11T12:33:33.246Z z2m:Zwave ValueAdded: 4-112-1-110 Set 111-113 to default
2019-03-11T12:33:33.246Z z2m:Zwave ValueAdded: 4-112-1-111 Send Interval for Reporting Group 1
2019-03-11T12:33:33.246Z z2m:Zwave ValueAdded: 4-112-1-112 Send Interval for Reporting Group 2
2019-03-11T12:33:33.246Z z2m:Zwave ValueAdded: 4-112-1-113 Send Interval for Reporting Group 3
2019-03-11T12:33:33.247Z z2m:Zwave ValueAdded: 4-112-1-120 Set the external S1 mode
2019-03-11T12:33:33.247Z z2m:Zwave ValueAdded: 4-112-1-121 Set the external S2 mode
2019-03-11T12:33:33.247Z z2m:Zwave ValueAdded: 4-112-1-122 Control destination for S1
2019-03-11T12:33:33.247Z z2m:Zwave ValueAdded: 4-112-1-123 Control destination for S2
2019-03-11T12:33:33.247Z z2m:Zwave ValueAdded: 4-112-1-144 WallSwipe
2019-03-11T12:33:33.248Z z2m:Zwave ValueAdded: 4-112-1-247 S1/S2 when the Switch mode is 3-way switch
2019-03-11T12:33:33.248Z z2m:Zwave ValueAdded: 4-112-1-248 Function of S1/S2
2019-03-11T12:33:33.248Z z2m:Zwave ValueAdded: 4-112-1-251 Configuration factory reset function
2019-03-11T12:33:33.248Z z2m:Zwave ValueAdded: 4-112-1-252 Configuration Locked
2019-03-11T12:33:33.248Z z2m:Zwave ValueAdded: 4-112-1-255 Reset To Factory Defaults
2019-03-11T12:33:33.248Z z2m:Zwave ValueAdded: 4-113-1-0 Alarm Type
2019-03-11T12:33:33.249Z z2m:Zwave ValueAdded: 4-113-1-1 Alarm Level
2019-03-11T12:33:33.249Z z2m:Zwave ValueAdded: 4-113-1-2 SourceNodeId
2019-03-11T12:33:33.249Z z2m:Zwave ValueAdded: 4-113-1-7 Heat
2019-03-11T12:33:33.249Z z2m:Zwave ValueAdded: 4-113-1-11 Power Management
2019-03-11T12:33:33.249Z z2m:Zwave ValueAdded: 4-115-1-0 Powerlevel
2019-03-11T12:33:33.250Z z2m:Zwave ValueAdded: 4-115-1-1 Timeout
2019-03-11T12:33:33.250Z z2m:Zwave ValueAdded: 4-115-1-2 Set Powerlevel
2019-03-11T12:33:33.250Z z2m:Zwave ValueAdded: 4-115-1-3 Test Node
2019-03-11T12:33:33.250Z z2m:Zwave ValueAdded: 4-115-1-4 Test Powerlevel
2019-03-11T12:33:33.250Z z2m:Zwave ValueAdded: 4-115-1-5 Frame Count
2019-03-11T12:33:33.250Z z2m:Zwave ValueAdded: 4-115-1-6 Test
2019-03-11T12:33:33.251Z z2m:Zwave ValueAdded: 4-115-1-7 Report
2019-03-11T12:33:33.251Z z2m:Zwave ValueAdded: 4-115-1-8 Test Status
2019-03-11T12:33:33.251Z z2m:Zwave ValueAdded: 4-115-1-9 Acked Frames
2019-03-11T12:33:33.251Z z2m:Zwave ValueAdded: 4-129-1-0 Day
2019-03-11T12:33:33.251Z z2m:Zwave ValueAdded: 4-129-1-1 Hour
2019-03-11T12:33:33.252Z z2m:Zwave ValueAdded: 4-129-1-2 Minute
2019-03-11T12:33:33.252Z z2m:Zwave ValueAdded: 4-134-1-0 Library Version
2019-03-11T12:33:33.252Z z2m:Zwave ValueAdded: 4-134-1-1 Protocol Version
2019-03-11T12:33:33.252Z z2m:Zwave ValueAdded: 4-134-1-2 Application Version
2019-03-11T12:33:37.379Z z2m:App New connection P95jcp1Jpi1H6IPXAAAA
2019-03-11T12:33:37.630Z z2m:Zwave Notification from node 2: Notification - NoOperation (2)
2019-03-11T12:33:37.658Z z2m:Zwave Notification from node 4: Notification - NoOperation (2)
2019-03-11T12:33:37.658Z z2m:Zwave controller command { nodeid: 0, state: 1, errcode: 0, help: 'Starting' }
2019-03-11T12:33:37.665Z z2m:Zwave controller command { nodeid: 0, state: 6, errcode: 0, help: 'InProgress' }
2019-03-11T12:33:37.777Z z2m:Zwave controller command { nodeid: 0, state: 7, errcode: 0, help: 'Completed' }
2019-03-11T12:33:37.777Z z2m:Zwave controller command { nodeid: 0, state: 1, errcode: 0, help: 'Starting' }
2019-03-11T12:33:37.789Z z2m:Zwave controller command { nodeid: 0, state: 6, errcode: 0, help: 'InProgress' }
2019-03-11T12:33:38.078Z z2m:Zwave controller command { nodeid: 0, state: 7, errcode: 0, help: 'Completed' }
2019-03-11T12:33:38.082Z z2m:Zwave node 1 ready: Z-Wave.Me - ZME_UZB1 USB Stick (Static PC Controller)
2019-03-11T12:33:42.536Z z2m:Zwave Notification from node 2: Notification - NoOperation (2)
2019-03-11T12:33:47.154Z z2m:App User disconnected P95jcp1Jpi1H6IPXAAAA
2019-03-11T12:33:47.200Z z2m:Zwave Notification from node 2: Notification - NoOperation (2)
2019-03-11T12:33:47.203Z z2m:Zwave Notification from node 2: Notification - Node Dead (5)
2019-03-11T12:33:47.642Z z2m:Zwave node 4 ready: AEON Labs - ZW116 Nano Switch (On/Off Power Switch)
2019-03-11T12:33:47.644Z z2m:Zwave Network scan complete. Found: 3 nodes
2019-03-11T12:33:47.644Z z2m:Zwave controller command { nodeid: 0, state: 1, errcode: 0, help: 'Starting' }
2019-03-11T12:33:47.644Z z2m:Zwave controller command { nodeid: 0, state: 3, errcode: 10, help: 'Error - Failed' }
2019-03-11T12:33:47.977Z z2m:App New connection o6OAxznl529W-8WRAAAB
2019-03-11T12:33:57.868Z z2m:Zwave zwave node 4: changed: 50-1-32:Exporting:false -> false
2019-03-11T12:33:57.869Z z2m:Zwave zwave node 4: changed: 50-1-0:Energy:3.175 -> 3.175
2019-03-11T12:33:57.870Z z2m:Zwave zwave node 4: changed: 50-1-1:Previous Reading:3.175 -> 3.175
2019-03-11T12:33:57.870Z z2m:Zwave zwave node 4: changed: 50-1-2:Interval:4 -> 11
2019-03-11T12:33:57.968Z z2m:Zwave zwave node 4: changed: 50-1-32:Exporting:false -> false
2019-03-11T12:33:57.968Z z2m:Zwave zwave node 4: changed: 50-1-8:Power:6.4 -> 6.404
2019-03-11T12:33:58.068Z z2m:Zwave zwave node 4: changed: 50-1-32:Exporting:false -> false
2019-03-11T12:33:58.069Z z2m:Zwave zwave node 4: changed: 50-1-16:Voltage:227.575 -> 227.341
2019-03-11T12:33:58.167Z z2m:Zwave zwave node 4: changed: 50-1-32:Exporting:false -> false
2019-03-11T12:33:58.168Z z2m:Zwave zwave node 4: changed: 50-1-20:Current:0.087 -> 0.092

I tried with both Assume Awake enabled and disabled.

Node 2 being the battery powered node that is asleep

I could fetch the type/product on init but I would prefer a way to detect battery powered devices, can you find something in openzwave docs about this?
Maybe by sending a wakeup command if your device supports it?
I think that mark a node as dead if it doesn't respond to the initial scan is correct here and If I change this I could create errors in the case the node is really missing in my network. SO I think the best fix to this is to manually weak someway the node on init

They seem to have the following command class:
                        <CommandClass id="128" name="COMMAND_CLASS_BATTERY" version="1" request_flags="4" innif="true">
                                <Instance index="1" />
                                <Value type="byte" genre="user" instance="1" index="0" label="Battery Level" units="%" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="0" />
                        </CommandClass>

If is this one is present in the cached configuration, one can make a safe assumption that it is a battery powered device?

So in brief: I should check if a 'dead' device has COMMAND_CLASS_WAKE_UP after scan is done, set it to asleep, wait for Wake-up Interval seconds to check if it checks in than assume it 'dead' ?
Are you sure there is no way that openzwave can send a request to this node to manually trigger that 'check in' ? I think this would be lot easier and more correct

I have found this issue: https://github.com/OpenZWave/node-openzwave-shared/issues/249 check it

So in brief: I should check if a 'dead' device has COMMAND_CLASS_WAKE_UP after scan is done, set it to asleep, wait for Wake-up Interval seconds to check if it checks in than assume it 'dead' ?

Sounds about right

Are you sure there is no way that openzwave can send a request to this node to manually trigger that 'check in' ? I think this would be lot easier and more correct

Not on the once I have atleast, testNode, Send NIF, all the commands just fail.
The only way to force and early checkin is getting on a ladder and opening the battery compartment to push the little wake up switch needed for inclusion.

I have found this issue: OpenZWave/node-openzwave-shared#249 check it

Sounds different, after the first wake up of the node the table gets type/product update and all values start to come through.

2019-03-12T12:28:07.523Z z2m:Store scenes.json not found
2019-03-12T12:28:07.970Z z2m:App Application path:/opt/zwave2mqtt
Initialising OpenZWave 1.4.3365 binary addon for Node.JS.
        OpenZWave Security API is ENABLED
        ZWave device db    : /opt/local/etc/openzwave
        User settings path : /opt/zwave2mqtt
        Option Overrides : --Logging false --ConsoleOutput false --QueueLogLevel 6 --DriverMaxAttempts 9999 --SaveConfiguration true --PollInterval 15000 --NetworkKey XXX
2019-03-12T12:28:08.095Z z2m:Zwave Connecting to /dev/cua/0
2019-03-12T12:28:08.192Z z2m:App Listening on port 8091
2019-03-12T12:28:08.264Z z2m:Mqtt MQTT client connected
2019-03-12T12:28:08.279Z z2m:Zwave Scanning network with homeid: 0xfc20d090
2019-03-12T12:28:08.280Z z2m:Zwave Node added 1
2019-03-12T12:28:08.281Z z2m:Zwave Node ID 1 is available { manufacturer: 'Z-Wave.Me',
  manufacturerid: '0x0115',
  product: 'ZME_UZB1 USB Stick',
  producttype: '0x0400',
  productid: '0x0001',
  type: 'Static PC Controller',
  name: 'controller',
  loc: 'serverroom' }
2019-03-12T12:28:08.289Z z2m:Zwave ValueAdded: 1-32-1-0 Basic
2019-03-12T12:28:08.289Z z2m:Zwave Node added 2
2019-03-12T12:28:08.291Z z2m:Zwave Node ID 2 is available { manufacturer: 'AEON Labs',
  manufacturerid: '0x0086',
  product: 'ZW100 MultiSensor 6',
  producttype: '0x0002',
  productid: '0x0064',
  type: 'Home Security Sensor',
  name: 'multisensor',
  loc: 'bedroom' }
2019-03-12T12:28:08.291Z z2m:Zwave ValueAdded: 2-48-1-0 Sensor
2019-03-12T12:28:08.292Z z2m:Zwave ValueAdded: 2-49-1-1 Temperature
2019-03-12T12:28:08.292Z z2m:Zwave ValueAdded: 2-49-1-3 Luminance
2019-03-12T12:28:08.292Z z2m:Zwave ValueAdded: 2-49-1-5 Relative Humidity
2019-03-12T12:28:08.292Z z2m:Zwave ValueAdded: 2-49-1-27 Ultraviolet
2019-03-12T12:28:08.292Z z2m:Zwave ValueAdded: 2-94-1-0 ZWave+ Version
2019-03-12T12:28:08.293Z z2m:Zwave ValueAdded: 2-94-1-1 InstallerIcon
2019-03-12T12:28:08.293Z z2m:Zwave ValueAdded: 2-94-1-2 UserIcon
2019-03-12T12:28:08.293Z z2m:Zwave ValueAdded: 2-112-1-2 Wake up 10 minutes on Power On
2019-03-12T12:28:08.293Z z2m:Zwave ValueAdded: 2-112-1-3 On time
2019-03-12T12:28:08.293Z z2m:Zwave ValueAdded: 2-112-1-4 Enable Motion Sensor
2019-03-12T12:28:08.293Z z2m:Zwave ValueAdded: 2-112-1-5 Command Options
2019-03-12T12:28:08.294Z z2m:Zwave ValueAdded: 2-112-1-7 Parameter #7
2019-03-12T12:28:08.294Z z2m:Zwave ValueAdded: 2-112-1-8 Awake timeout
2019-03-12T12:28:08.294Z z2m:Zwave ValueAdded: 2-112-1-9 Current power mode
2019-03-12T12:28:08.294Z z2m:Zwave ValueAdded: 2-112-1-39 Low Battery
2019-03-12T12:28:08.294Z z2m:Zwave ValueAdded: 2-112-1-40 Report Only On Thresholds
2019-03-12T12:28:08.295Z z2m:Zwave ValueAdded: 2-112-1-41 Temperature Reporting Threshold
2019-03-12T12:28:08.295Z z2m:Zwave ValueAdded: 2-112-1-42 Humidity Reporting Threshold
2019-03-12T12:28:08.295Z z2m:Zwave ValueAdded: 2-112-1-43 Luminance Reporting Threshold
2019-03-12T12:28:08.295Z z2m:Zwave ValueAdded: 2-112-1-44 Battery Reporting Threshold
2019-03-12T12:28:08.295Z z2m:Zwave ValueAdded: 2-112-1-45 UV Reporting Threshold
2019-03-12T12:28:08.295Z z2m:Zwave ValueAdded: 2-112-1-46 Low Temp Alarm
2019-03-12T12:28:08.296Z z2m:Zwave ValueAdded: 2-112-1-48 Enable/disable to send a report on Threshold
2019-03-12T12:28:08.296Z z2m:Zwave ValueAdded: 2-112-1-49 Set the upper limit value of temperature sensor
2019-03-12T12:28:08.296Z z2m:Zwave ValueAdded: 2-112-1-50 Set the lower limit value of temperature sensor
2019-03-12T12:28:08.296Z z2m:Zwave ValueAdded: 2-112-1-51 Set the upper limit value of humidity sensor
2019-03-12T12:28:08.296Z z2m:Zwave ValueAdded: 2-112-1-52 Set the lower limit value of humidity sensor
2019-03-12T12:28:08.296Z z2m:Zwave ValueAdded: 2-112-1-53 Set the upper limit value of Lighting sensor
2019-03-12T12:28:08.296Z z2m:Zwave ValueAdded: 2-112-1-54 Set the lower limit value of Lighting sensor
2019-03-12T12:28:08.297Z z2m:Zwave ValueAdded: 2-112-1-55 Set the upper limit value of ultraviolet sensor
2019-03-12T12:28:08.297Z z2m:Zwave ValueAdded: 2-112-1-56 Set the lower limit value of ultraviolet sensor
2019-03-12T12:28:08.297Z z2m:Zwave ValueAdded: 2-112-1-57 Set the recover limit value of temperature sensor
2019-03-12T12:28:08.297Z z2m:Zwave ValueAdded: 2-112-1-58 Set the recover limit value of humidity sensor
2019-03-12T12:28:08.297Z z2m:Zwave ValueAdded: 2-112-1-59 Set the recover limit value of Lighting sensor
2019-03-12T12:28:08.297Z z2m:Zwave ValueAdded: 2-112-1-60 Set the recover limit value of Ultraviolet sensor
2019-03-12T12:28:08.298Z z2m:Zwave ValueAdded: 2-112-1-61 Get the out-of-limit state of the Sensors
2019-03-12T12:28:08.298Z z2m:Zwave ValueAdded: 2-112-1-64 Temperature scale
2019-03-12T12:28:08.298Z z2m:Zwave ValueAdded: 2-112-1-81 LED blinking report
2019-03-12T12:28:08.298Z z2m:Zwave ValueAdded: 2-112-1-100 Reset Params 101-103 to Default
2019-03-12T12:28:08.298Z z2m:Zwave ValueAdded: 2-112-1-101 Group 1 Reports
2019-03-12T12:28:08.298Z z2m:Zwave ValueAdded: 2-112-1-102 Group 2 Reports
2019-03-12T12:28:08.299Z z2m:Zwave ValueAdded: 2-112-1-103 Group 3 Reports
2019-03-12T12:28:08.299Z z2m:Zwave ValueAdded: 2-112-1-110 Reset Params 111-113 to Default
2019-03-12T12:28:08.299Z z2m:Zwave ValueAdded: 2-112-1-111 Group 1 Interval
2019-03-12T12:28:08.299Z z2m:Zwave ValueAdded: 2-112-1-112 Group 2 Interval
2019-03-12T12:28:08.299Z z2m:Zwave ValueAdded: 2-112-1-113 Group 3 Interval
2019-03-12T12:28:08.299Z z2m:Zwave ValueAdded: 2-112-1-201 Temperature Calibration
2019-03-12T12:28:08.300Z z2m:Zwave ValueAdded: 2-112-1-202 Humidity Calibration
2019-03-12T12:28:08.300Z z2m:Zwave ValueAdded: 2-112-1-203 Luminance Calibration
2019-03-12T12:28:08.300Z z2m:Zwave ValueAdded: 2-112-1-204 Ultraviolet Calibration
2019-03-12T12:28:08.300Z z2m:Zwave ValueAdded: 2-112-1-252 Enable/disable Lock Configuration
2019-03-12T12:28:08.300Z z2m:Zwave ValueAdded: 2-112-1-255 Reset To Factory Defaults
2019-03-12T12:28:08.300Z z2m:Zwave ValueAdded: 2-113-1-0 Alarm Type
2019-03-12T12:28:08.301Z z2m:Zwave ValueAdded: 2-113-1-1 Alarm Level
2019-03-12T12:28:08.301Z z2m:Zwave ValueAdded: 2-113-1-2 SourceNodeId
2019-03-12T12:28:08.301Z z2m:Zwave ValueAdded: 2-113-1-10 Burglar
2019-03-12T12:28:08.301Z z2m:Zwave ValueAdded: 2-115-1-0 Powerlevel
2019-03-12T12:28:08.301Z z2m:Zwave ValueAdded: 2-115-1-1 Timeout
2019-03-12T12:28:08.301Z z2m:Zwave ValueAdded: 2-115-1-2 Set Powerlevel
2019-03-12T12:28:08.302Z z2m:Zwave ValueAdded: 2-115-1-3 Test Node
2019-03-12T12:28:08.302Z z2m:Zwave ValueAdded: 2-115-1-4 Test Powerlevel
2019-03-12T12:28:08.302Z z2m:Zwave ValueAdded: 2-115-1-5 Frame Count
2019-03-12T12:28:08.302Z z2m:Zwave ValueAdded: 2-115-1-6 Test
2019-03-12T12:28:08.302Z z2m:Zwave ValueAdded: 2-115-1-7 Report
2019-03-12T12:28:08.302Z z2m:Zwave ValueAdded: 2-115-1-8 Test Status
2019-03-12T12:28:08.303Z z2m:Zwave ValueAdded: 2-115-1-9 Acked Frames
2019-03-12T12:28:08.303Z z2m:Zwave ValueAdded: 2-128-1-0 Battery Level
2019-03-12T12:28:08.303Z z2m:Zwave ValueAdded: 2-132-1-1 Minimum Wake-up Interval
2019-03-12T12:28:08.303Z z2m:Zwave ValueAdded: 2-132-1-2 Maximum Wake-up Interval
2019-03-12T12:28:08.303Z z2m:Zwave ValueAdded: 2-132-1-3 Default Wake-up Interval
2019-03-12T12:28:08.303Z z2m:Zwave ValueAdded: 2-132-1-4 Wake-up Interval Step
2019-03-12T12:28:08.303Z z2m:Zwave ValueAdded: 2-132-1-0 Wake-up Interval
2019-03-12T12:28:08.304Z z2m:Zwave ValueAdded: 2-134-1-0 Library Version
2019-03-12T12:28:08.304Z z2m:Zwave ValueAdded: 2-134-1-1 Protocol Version
2019-03-12T12:28:08.304Z z2m:Zwave ValueAdded: 2-134-1-2 Application Version
2019-03-12T12:28:08.304Z z2m:Zwave Node added 4
2019-03-12T12:28:08.304Z z2m:Zwave Node ID 4 is available { manufacturer: 'AEON Labs',
  manufacturerid: '0x0086',
  product: 'ZW116 Nano Switch',
  producttype: '0x0003',
  productid: '0x0074',
  type: 'On/Off Power Switch',
  name: 'socket_desk',
  loc: 'bedroom' }
2019-03-12T12:28:08.304Z z2m:Zwave ValueAdded: 4-37-1-0 Switch
2019-03-12T12:28:08.305Z z2m:Zwave ValueAdded: 4-39-1-0 Switch All
2019-03-12T12:28:08.305Z z2m:Zwave ValueAdded: 4-50-1-0 Energy
2019-03-12T12:28:08.305Z z2m:Zwave ValueAdded: 4-50-1-1 Previous Reading
2019-03-12T12:28:08.305Z z2m:Zwave ValueAdded: 4-50-1-2 Interval
2019-03-12T12:28:08.305Z z2m:Zwave ValueAdded: 4-50-1-8 Power
2019-03-12T12:28:08.305Z z2m:Zwave ValueAdded: 4-50-1-16 Voltage
2019-03-12T12:28:08.306Z z2m:Zwave ValueAdded: 4-50-1-20 Current
2019-03-12T12:28:08.306Z z2m:Zwave ValueAdded: 4-50-1-32 Exporting
2019-03-12T12:28:08.306Z z2m:Zwave ValueAdded: 4-50-1-33 Reset
2019-03-12T12:28:08.306Z z2m:Zwave ValueAdded: 4-94-1-0 ZWave+ Version
2019-03-12T12:28:08.306Z z2m:Zwave ValueAdded: 4-94-1-1 InstallerIcon
2019-03-12T12:28:08.306Z z2m:Zwave ValueAdded: 4-94-1-2 UserIcon
2019-03-12T12:28:08.307Z z2m:Zwave ValueAdded: 4-112-1-3 Over current protection
2019-03-12T12:28:08.307Z z2m:Zwave ValueAdded: 4-112-1-4 Over heat protection
2019-03-12T12:28:08.307Z z2m:Zwave ValueAdded: 4-112-1-20 Status re-power on
2019-03-12T12:28:08.307Z z2m:Zwave ValueAdded: 4-112-1-21 WallSwipe IR sensor
2019-03-12T12:28:08.307Z z2m:Zwave ValueAdded: 4-112-1-64 WallSwipe button color
2019-03-12T12:28:08.307Z z2m:Zwave ValueAdded: 4-112-1-65 WallSwipe LED Up gesture action
2019-03-12T12:28:08.308Z z2m:Zwave ValueAdded: 4-112-1-66 WallSwipe LED Down gesture action
2019-03-12T12:28:08.308Z z2m:Zwave ValueAdded: 4-112-1-67 WallSwipe LED Left gesture action
2019-03-12T12:28:08.308Z z2m:Zwave ValueAdded: 4-112-1-68 WallSwipe LED Right gesture action
2019-03-12T12:28:08.308Z z2m:Zwave ValueAdded: 4-112-1-69 WallSwipe Night light
2019-03-12T12:28:08.308Z z2m:Zwave ValueAdded: 4-112-1-71 WallSwipe sensitivity
2019-03-12T12:28:08.308Z z2m:Zwave ValueAdded: 4-112-1-80 Notification report association group 1
2019-03-12T12:28:08.309Z z2m:Zwave ValueAdded: 4-112-1-81 Notification report using the external switch 1
2019-03-12T12:28:08.309Z z2m:Zwave ValueAdded: 4-112-1-82 Notification report using the external switch 2
2019-03-12T12:28:08.309Z z2m:Zwave ValueAdded: 4-112-1-83 LED status
2019-03-12T12:28:08.309Z z2m:Zwave ValueAdded: 4-112-1-84 Time set for Night light mode
2019-03-12T12:28:08.309Z z2m:Zwave ValueAdded: 4-112-1-86 Set the ON time of output load
2019-03-12T12:28:08.309Z z2m:Zwave ValueAdded: 4-112-1-87 Set the OFF time of output load
2019-03-12T12:28:08.310Z z2m:Zwave ValueAdded: 4-112-1-90 Enable/disable the parameter 91 and 92
2019-03-12T12:28:08.310Z z2m:Zwave ValueAdded: 4-112-1-91 Minimum Change to send Report (Watt)
2019-03-12T12:28:08.310Z z2m:Zwave ValueAdded: 4-112-1-92 Minimum Change to send Report (%)
2019-03-12T12:28:08.310Z z2m:Zwave ValueAdded: 4-112-1-100 Default Group Reports
2019-03-12T12:28:08.310Z z2m:Zwave ValueAdded: 4-112-1-101 Report type sent in Reporting Group 1
2019-03-12T12:28:08.310Z z2m:Zwave ValueAdded: 4-112-1-102 Report type sent in Reporting Group 2
2019-03-12T12:28:08.311Z z2m:Zwave ValueAdded: 4-112-1-103 Report type sent in Reporting Group 3
2019-03-12T12:28:08.311Z z2m:Zwave ValueAdded: 4-112-1-110 Set 111-113 to default
2019-03-12T12:28:08.311Z z2m:Zwave ValueAdded: 4-112-1-111 Send Interval for Reporting Group 1
2019-03-12T12:28:08.311Z z2m:Zwave ValueAdded: 4-112-1-112 Send Interval for Reporting Group 2
2019-03-12T12:28:08.311Z z2m:Zwave ValueAdded: 4-112-1-113 Send Interval for Reporting Group 3
2019-03-12T12:28:08.311Z z2m:Zwave ValueAdded: 4-112-1-120 Set the external S1 mode
2019-03-12T12:28:08.311Z z2m:Zwave ValueAdded: 4-112-1-121 Set the external S2 mode
2019-03-12T12:28:08.312Z z2m:Zwave ValueAdded: 4-112-1-122 Control destination for S1
2019-03-12T12:28:08.312Z z2m:Zwave ValueAdded: 4-112-1-123 Control destination for S2
2019-03-12T12:28:08.312Z z2m:Zwave ValueAdded: 4-112-1-144 WallSwipe
2019-03-12T12:28:08.312Z z2m:Zwave ValueAdded: 4-112-1-247 S1/S2 when the Switch mode is 3-way switch
2019-03-12T12:28:08.312Z z2m:Zwave ValueAdded: 4-112-1-248 Function of S1/S2
2019-03-12T12:28:08.312Z z2m:Zwave ValueAdded: 4-112-1-251 Configuration factory reset function
2019-03-12T12:28:08.313Z z2m:Zwave ValueAdded: 4-112-1-252 Configuration Locked
2019-03-12T12:28:08.313Z z2m:Zwave ValueAdded: 4-112-1-255 Reset To Factory Defaults
2019-03-12T12:28:08.313Z z2m:Zwave ValueAdded: 4-113-1-0 Alarm Type
2019-03-12T12:28:08.313Z z2m:Zwave ValueAdded: 4-113-1-1 Alarm Level
2019-03-12T12:28:08.313Z z2m:Zwave ValueAdded: 4-113-1-2 SourceNodeId
2019-03-12T12:28:08.313Z z2m:Zwave ValueAdded: 4-113-1-7 Heat
2019-03-12T12:28:08.314Z z2m:Zwave ValueAdded: 4-113-1-11 Power Management
2019-03-12T12:28:08.314Z z2m:Zwave ValueAdded: 4-115-1-0 Powerlevel
2019-03-12T12:28:08.314Z z2m:Zwave ValueAdded: 4-115-1-1 Timeout
2019-03-12T12:28:08.314Z z2m:Zwave ValueAdded: 4-115-1-2 Set Powerlevel
2019-03-12T12:28:08.314Z z2m:Zwave ValueAdded: 4-115-1-3 Test Node
2019-03-12T12:28:08.314Z z2m:Zwave ValueAdded: 4-115-1-4 Test Powerlevel
2019-03-12T12:28:08.315Z z2m:Zwave ValueAdded: 4-115-1-5 Frame Count
2019-03-12T12:28:08.315Z z2m:Zwave ValueAdded: 4-115-1-6 Test
2019-03-12T12:28:08.315Z z2m:Zwave ValueAdded: 4-115-1-7 Report
2019-03-12T12:28:08.315Z z2m:Zwave ValueAdded: 4-115-1-8 Test Status
2019-03-12T12:28:08.315Z z2m:Zwave ValueAdded: 4-115-1-9 Acked Frames
2019-03-12T12:28:08.315Z z2m:Zwave ValueAdded: 4-129-1-0 Day
2019-03-12T12:28:08.315Z z2m:Zwave ValueAdded: 4-129-1-1 Hour
2019-03-12T12:28:08.316Z z2m:Zwave ValueAdded: 4-129-1-2 Minute
2019-03-12T12:28:08.316Z z2m:Zwave ValueAdded: 4-134-1-0 Library Version
2019-03-12T12:28:08.316Z z2m:Zwave ValueAdded: 4-134-1-1 Protocol Version
2019-03-12T12:28:08.316Z z2m:Zwave ValueAdded: 4-134-1-2 Application Version
2019-03-12T12:28:12.909Z z2m:Zwave Notification from node 2: Notification - NoOperation (2)
2019-03-12T12:28:12.936Z z2m:Zwave Notification from node 4: Notification - NoOperation (2)
2019-03-12T12:28:12.937Z z2m:Zwave controller command { nodeid: 0, state: 1, errcode: 0, help: 'Starting' }
2019-03-12T12:28:12.943Z z2m:Zwave controller command { nodeid: 0, state: 6, errcode: 0, help: 'InProgress' }
2019-03-12T12:28:13.073Z z2m:Zwave controller command { nodeid: 0, state: 7, errcode: 0, help: 'Completed' }
2019-03-12T12:28:13.073Z z2m:Zwave controller command { nodeid: 0, state: 1, errcode: 0, help: 'Starting' }
2019-03-12T12:28:13.086Z z2m:Zwave controller command { nodeid: 0, state: 6, errcode: 0, help: 'InProgress' }
2019-03-12T12:28:13.426Z z2m:Zwave controller command { nodeid: 0, state: 7, errcode: 0, help: 'Completed' }
2019-03-12T12:28:13.432Z z2m:Zwave node 1 ready: Z-Wave.Me - ZME_UZB1 USB Stick (Static PC Controller)
2019-03-12T12:28:18.037Z z2m:Zwave Notification from node 2: Notification - NoOperation (2)
2019-03-12T12:28:22.676Z z2m:Zwave Notification from node 2: Notification - NoOperation (2)
2019-03-12T12:28:22.687Z z2m:Zwave Notification from node 2: Notification - Node Dead (5)
2019-03-12T12:28:23.116Z z2m:Zwave node 4 ready: AEON Labs - ZW116 Nano Switch (On/Off Power Switch)
2019-03-12T12:28:23.117Z z2m:Zwave Network scan complete. Found: 3 nodes

@sjorge Check my last commit and tell me if everything works now

Works fine now!

Let me know if you find other bugs. Thank you @sjorge

Hi @robertsLando is there any chance of getting the docker image pushed up to 3.03 that includes this. Have same issue. I can only see ARM3.03 in there. I am very new to zwave2mqtt so apologies if i have missed something

@jamesarbrown I don't understand what you mean

At the time the docker did not seem to have 3.03 x64, so i cleaned and docker pull again and now its running on 3.03
But, it did not fix this issue for me on a Trisensor zwa005. My device still says dead immediately after restarting zwave2mqtt and even after waiting 2 days
https://github.com/OpenZWave/open-zwave/blob/master/config/aeotec/zwa005.xml
In the device table earlier today, also confirmed comms were active, by having an last active time of 5 hours ago.
Then I looked at the logs by creating a motion event and I can see the controller communicating with it... but still shows dead
2020-04-27 19:59:55.946 Detail, Node012, Decrypted Packet: 0x00, 0x30, 0x03, 0x00, 0x0c                                                      2020-04-27 19:59:55.947 Detail,                                                                                2020-04-27 19:59:55.947 Info, Node012, ApplicationCommandHandler - Unhandled Command Class 0x30
Are there any logs / tests I can provide?
The only way I can get it to fix is to press the internal button for 5 sec until the little red LED comes, at which point the tables update and I get a "Sleep" status.

@robertsLando would it be possible to re-open this issue? or do you think its something different and I can open a new issue?

@jamesarbrown If you have refreshNodeInfo option enabled in Zwave settings please disable it

I have tried the refreshnodeinfo and still the device is marked as dead after some days. I am not sure about the operating details of zwave what it needs to get out of a dead state, but as you can see from this screenshot it has woken up in the past hours and connected in.
Is there anything that can be done to force a full wake up on check in, whilst the device has its zwave radio active?

@jamesarbrown Did you try to enable the option in zwave settings called assume awake?
Also let's see what @Fishwaldo says about this. Please @jamesarbrown add your OZW log file here

OZWLog Startup
OZWLogStartup.txt
settings.zip
Ill try to remember to pull a later log at some point tomorrow

Assume Awake was off.... as I thought it should assume they are asleep
Then I turned it on and currently see no difference.
OZWLogStartup.txt
settings.zip
Will try to remember to do another log post after a considerable uptime

Node 16 seems to be busy but still flagged as dead

1526 Log
1526 Node 16 Logs.txt
Full Log
OZW_Log.txt

@Fishwaldo COuld you check the logs please?

@robertsLando @Fishwaldo
I set the wakeup time as low as possible and then waited on the logs
So, please find attached a node that is "DEAD" and wakes up, but sadly remains dead. Ozw2mqtt 3.2.1
deadnodewakeup.log

I was trying to investigate and i found this
https://github.com/OpenZWave/Zwave2Mqtt/issues/284#issuecomment-594002439
It fixed my issue

Looks like that option was removed https://github.com/OpenZWave/Zwave2Mqtt/pull/603
I wonder what the fix is now to make battery devices alive again.

@onedr0p Just send refreshNodeInfo command as broadcast :) To send it as broadcast select that from controller actions and press ok on the popup

@robertsLando so by default refreshnodeinfo is OFF and does not occur on start?
@onedr0p as far as I was concerned the refreshnodeinfo was a startup thing and was breaking system due to sleeping devices. Looks to me like it's gone altogether which would have suggested it should just work as is?

so by default refreshnodeinfo is OFF and does not occur on start?

Yes. It was making too much confusion and there was peoples that was leaving that on and that is not good.

I tried running all the commands last night and it would not come back alive. Not I woke up and I see it's working. Time heals all wounds 😅

@onedr0p Patience is the key :laughing:

I just restarted zwave2mqtt again and the device is dead. I am trying to run refreshnodeinfo but the device does not wake up. I know in time it will heal itself somehow but it's not ideal to wait :/

Unfortunately I have no idea how to help you with this, sorry

Daniel

On 14 Jul 2020, at 21:49, Devin Buhl<EMAIL_ADDRESS>wrote:

I just restarted zwave2mqtt again and the device is dead. I am trying to run refreshnodeinfo but the device does not wake up. I know in time it will heal itself somehow but it's not ideal to wait :/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

No worries, here are the logs and if anyone is curious the device that is problematic is the Ecolink Zwave Plus Door & Window Sensor (DWZWAVE2.5-ECO)
The device is Node008.
OZW.log


Language and Classifier Agnostic Usage

We use mostly Java with various ML algorithms. Let say I have a vectorized dataset with both labels along with predictions of some classifier A. Is there a way to use lime just with this kind of tabular data?

No, we need access to the classifier. When generating explanations for an example, we perturb that example in various ways and use the predictions of the classifier on the perturbed examples.

No, we need access to the classifier. When generating explanations for an example, we perturb that example in various ways and use the predictions of the classifier on the perturbed examples.

Hi, I recently ran into a similar problem. I'm working on text classification. My model is implemented in Java. I wrote a py4j wrapper and defined a python method that takes the input text, calls the Java service and returns the result as a numpy array. The method works and returns the array representing the probability. However, when I passed the method to LIME, it seems to be accessing a built-in method of the model. (Sorry I don't have the stack trace at hand. I'll be happy to add it later on).
So I wonder is it only the example (text in this case) that's perturbed? If so, why do we care about which language is the model implemented as long as we can write a Python wrapper for it?

The explainer is just calling your wrapper,  it does not access anything else. Make sure your wrapper takes as input a list of strings, rather than a single string.

Thanks! It helped. I messed up with the dimensions since the input to explainer.explain_instance is a string but lime will batch the perturbed sentences and call the wrapper. It's working now.


Force encoding of Qcow magic.

Account for new default string encoding in Ruby 2, by
forcing the encoding of the qcow magic string.
https://bugzilla.redhat.com/show_bug.cgi?id=1198814
https://bugzilla.redhat.com/show_bug.cgi?id=1199224

@jrafanie , @Fryguy please review.

@roliveri Does it make sense to go through ALL the magic numbers in the fleecing code base and do the same?

@chessbyte, @jrafanie did this in PR #804 .  I had given him a regex to scan the files, but it seems the regex only checked with base-ten-digits, and should have been hex-digits.  We should run that check again with an adjusted regex: `\[xu]?[0-9a-fA-F][0-9a-fA-F]?[0-9a-fA-F]?[0-9a-fA-F]?
In that PR, @jrafanie used the magic encoding comment...should we do that instead of this change?

@chessbyte , the only other probe files that have magic numbers are VMWareDiskProbe.rb and MSVSDiskProbe.rb. VMWareDiskProbe.rb already has a # encoding: US-ASCII comment.
So the question is, should we address this in a consistent way?

I'll switch to the comment and add the comment to MSVSDiskProbe.rb,

:+1: @roliveri


[FORMATTING] Spaces are added when fields begin with numbers

Input data
Which SQL and options did you provide as input?
SELECT
total_pay,
7d_pay,
offline_days,
15d_pay,
30d_pay,
FROM
role
Expected Output
SELECT
total_pay,
7 d_pay,
offline_days,
15 d_pay,
30 d_pay,
FROM
role
-- ADD SQL HERE

Actual Output
-- ADD SQL HERE

Usage

How are you calling / using the library?
What SQL language(s) does this apply to?
Which SQL Formatter version are you using?

What language is this, that allows for identifiers that start with numbers ?

There are some SQL dialects (like MariaDB and MySQL) which allow identifiers to begin with numbers. Most likely you aren't using the correct language option when formatting.
Hard to diagnose unless you tell us which SQL dialect you're using.

the output result is not the same between the version 6.1.5 and the version 7.0.4
I stay with the version 6
I close the issue

I'm closing this, as there's not enough info to properly understand the issue.

Fix for this is now released in 9.0.0-beta.6


Add CxNOT gate

This is a CZ gate conjugated by Hadamards. It's a native gate for ion traps.

Fixed by https://github.com/quantumlib/Cirq/pull/1102 (which implements the correct gate, not this one)


Fitting chart to mins and maxes of input data

Should be able to handle variable times ranges and lengths and fit chart to the input data. Ideally this can be handled modularly in one place.

Also should be able to dynamically handle the number of lines to plot. May need to re-format when a certain number of lines is exceeded in order to give a more condensed view.


python312Packages.borb: fix build failure on darwin

Fixes the build failures on x86_64/aarch64-darwin that appeared in:
https://hydra.nixos.org/build/276817930
https://hydra.nixos.org/build/276701789
ZHF #352882

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 355819

x86_64-darwin

:white_check_mark: 4 packages built:

python311Packages.borb
python311Packages.borb.dist
python312Packages.borb
python312Packages.borb.dist

aarch64-darwin

:white_check_mark: 4 packages built:

python311Packages.borb
python311Packages.borb.dist
python312Packages.borb
python312Packages.borb.dist

Weird that it only breaks on darwin


corrected spacing to pass ansible-lint

released to the galaxy as andrewrothstein.epel v1.0.5. thanks for the contribution!


Cannot delete charts

As the title says. I have several charts that just won't delete. kubectl hangs after saying a chart was deleted (but it is not).
No job is started to delete the chart.

I'm working around the problem by deleting the entire cluster and starting over. :laughing:

That's exactly what I had to do. Now I'm just templating out of cluster. I'm not sure why the finalizer doesn't run.

In my case, I manage to overcome this by editing the HelmChart and setting metadata.finalizers to an empty list (rke2).

Anyone looking at this?

@rasmusson no

Here a HelmChart example which does not get cleaned up properly:
apiVersion: helm.cattle.io/v1
kind: HelmChart
metadata:
  name: csi-s3
  namespace: kube-system
spec:
  repo: https://yandex-cloud.github.io/k8s-csi-s3/charts
  chart: csi-s3
  version: 0.41.1
  targetNamespace: kube-system
  valuesContent: |-
    # we create the secret using kustomize
    secret:
      create: false

Hi!
Here is a link to the solution description for RKE2
Delete frozen resource

Disable helmchart for managed helm-controller (select you variants )

kubectl -n $MY_NS_NAME patch helmchart.helm.cattle.io $MY_HELMCHART_NAME-p '{"metadata":{"annotations":{"helmcharts.helm.cattle.io/unmanaged":"true"}}}' --type=merge
# OR
kubectl annotate --overwrite -f helm.yaml helmcharts.helm.cattle.io/unmanaged='true'

Delete finalizers(select you variants )

kubectl -n $MY_NS_NAME patch helmchart.helm.cattle.io $MY_HELMCHART_NAME  -p '{"metadata":{"finalizers":null}}' --type=merge
# OR
kubectl patch -f helm.yaml -p '{"metadata":{"finalizers":null}}' --type=merge

Delete helmchart(select you variants )

kubectl -n $MY_NS_NAME delete --force=true helmchart.helm.cattle.io $MY_HELMCHART_NAME
#OR
kubectl -n $MY_NS_NAME delete --force=true  -f helm.yaml


Issue with mobile view on new UI

Follow-up of #19
Content in mobile view is not fully centered, also the UI might look better if there is a small padding around the boxes (at least it's worth a try, I guess)

This also gets addressed in #23 🙂

Looking awesome, thanks!


⚠ Bofrost.nl has degraded performance

In d1f5643, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 1078 ms

Resolved: Bofrost.nl performance has improved in 9fbbf75 after 9 minutes.


[Question] How to pass a list of raw args to fzf_exec ?

I am trying to remove nvim-bqf 's dependence on fzf#run to fzf_exec. The following is the code I want to change:
nvim-bqf code that uses fzf#run
At the very end, I want to pass the opts.options flags list to fzf_exec I tried going through various docs and methods but I don't think it's working.
Here is my current version:
function M.run()
    local qwinid = api.nvim_get_current_win()
    local qlist = qfs:get(qwinid):list()
    local prompt = qlist.type == 'loc' and ' Location> ' or ' Quickfix> '
    local size = qlist:getQfList({size = 0}).size
    if size < 2 then
        return
    end
    -- greater than 1000 items is worth using headless as stream to improve user experience
    local source = size > 1000 and sourceCmd or sourceList

    local baseOpt = {'--color', 'gutter:-1'}
    if compareVersion(version, '0.27.4') >= 0 then
        table.insert(baseOpt, '--scroll-off')
        table.insert(baseOpt, utils.scrolloff(qwinid))
    end
    if compareVersion(version, '0.35.0') >= 0 then
        table.insert(baseOpt, '--no-separator')
    end

    -- TODO
    -- ctx.fzf_extra_opts and ctx.fzf_action_for are used by myself, I'm not sure who wants them.
    local ctx = qlist:context().bqf or {}
    ctxActionFor = nil
    if type(ctx.fzf_action_for) == 'table' then
        ctxActionFor = vim.tbl_extend('keep', ctx.fzf_action_for, actionFor)
        filterActions(ctxActionFor)
    end
    local expectKeys = table.concat(vim.tbl_keys(ctxActionFor or actionFor), ',')
    vim.list_extend(baseOpt, {
        '--multi', '--ansi', '--delimiter', [[\|]], '--with-nth', '2..', '--nth', '3..,1,2',
        '--header-lines', 0, '--tiebreak', 'index', '--info', 'inline', '--prompt', prompt,
        '--no-border', '--layout', 'reverse-list', '--expect', expectKeys
    })
    local options = vim.list_extend(baseOpt, ctx.fzf_extra_opts or extraOpts)
    local delimiter = parseDelimiter(options)
    local bind = parseBind(options)
    local opts = {
        options = options,
        source = source(qwinid, qlist:sign():list(), delimiter),
        ['sink*'] = function(lines)
            return handler(qwinid, lines)
        end,
        window = {
            width = api.nvim_win_get_width(qwinid),
            height = api.nvim_win_get_height(qwinid) + 1,
            xoffset = 0,
            yoffset = 0,
            border = 'none'
        }
    }

    local tmpfile = fn.tempname()
    vim.list_extend(opts.options, {'--preview-window', 0, '--preview', 'echo {1} >> ' .. tmpfile})
    local releaseCallback = watchFile(qwinid, tmpfile)
    M.postHandle = function()
        releaseCallback()
        M.postHandle = nil
    end
    phandler.keepPreview()

    cmd(('au BqfFilterFzf FileType fzf ++once %s'):format(
        ([[lua require('bqf.filter.fzf').preHandle(%d, %d, %q)]]):format(qwinid, size, bind)))

    if ok_fzf_lua then
      fzf_lua.fzf_exec(opts.source,
      {
	-- fzf_args = opts.options,
	-- fzf_args = table.concat(opts.options,' '),
	fzf_raw_args = opts.options ,
	actions = {
	  ['default'] = function(lines)
	      return handler(qwinid, lines)
	  end
	}
      })
    else
      fn.BqfFzfWrapper(opts)
    end
end

You can pass fzf flags in two different ways:

As a table with fzf_opts
As raw args with fzf_cli_args, I.e. fzf_exec{ … }, { 'fzf_cli_args’ = … })(the entire argument will be encapsulated withvim.fun.shellescape` automatically)

Actually, I see you already used fzf_raw_args which is the same argument, the issue is you’re sensing it as a table which isn’t proxied directly to termopen, it wasn’t possible due to stream redirection limitations so I had to use a plain string for arguments with sh -c.
What you need to do is convertopts.options to a string with shell escaping for complex values so it will probably be a bit more nuanced than table.concat.
I can also try and revisit the issue of passing the arguments as a table directly to termopen but can’t make any promises as for the result.

I can also try and revisit the issue of passing the arguments as a table directly to termopen but can’t make any promises as for the result.

It's okay if this isn't implemented. The main reason I'm trying to do this nvim-bqf PR myself is to take burden off you.
You guys can focus on other more important stuff. Let us(or just me :P) focus on the relatively simpler stuff.

I can also try and revisit the issue of passing the arguments as a table directly to termopen but can’t make any promises as for the result.

It's okay if this isn't implemented. The main reason I'm trying to do this nvim-bqf PR myself is to take burden off you.

Tysm!
I’ll give it a go again, if I can get rid of the output redirection at the shell level that would be a good first step for supporting windows, I even forgot what was the hurdle last time I tried.

You guys can focus on other more important stuff. Let us(or just me :P) focus on the relatively simpler stuff.

There’s just me for now :) and it’s been relatively stable for a while now, only questions and feature requests and barely any bugs.

I just revisited this and tried to convert the termopen (esssentially jobstart) to no-shell to be able to supply a table or raw arguments with no shell ecaping requirements, I'm again stuck at the lack of shell redirection.
To be able to "act" upon selection we need to redirect the fzf output into a file (maybe there's a better way?) and redirection ( >) requires the use of a shell, I tried removing the shell requirement by using jobstart's on_stdout parameter but it gets called for each line and each screen modification and I can't seem to find a way to discrern betweem the fzf draw output and the "post-selection" output.
TBH I would just convert baseOpt to the below and then pass it as fzf_opts:
local baseOpt = {
  ['--multi']        = "",
  ['--ansi']         = "",
  ['--delimiter']    = vim.fn.shellescape([[\|]]),
  ['--with-nth']     = '2..',
  ['--nth']          = '3..,1,2',
  ['--header-lines'] = "0",
  ['--tiebreak']     = 'index',
  ['--info']         = 'inline',
  ['--prompt']       = vim.fn.shellescape(prompt),
  ['--no-border']    = "",
  ['--layout']       = 'reverse-list',
  ['--expect']       = vim.fn.shellescape(expectKeys),
}

Reading the code again I would also avoid the --expect, use the actions keybind table instead and let fzf-lua build the --expect argument by itself.


DTP/DUP: Deleting a study or data object does not remove it from associated study/object

Where deleting a study or data object, if it appears as an associated study or associated data object in a DTP/DUP, it should automatically be removed there as well. Currently there are ghost associated DOs (not tested with studies).

Hallucinated an issue


Reconcile RetrySettings & Clock

Reconcile RetrySettings in GAX with RetryParams in google-cloud-java
https://github.com/GoogleCloudPlatform/google-cloud-java/issues/1574
Reconcile NanoClock in GAX with Clock in google-cloud-java
https://github.com/GoogleCloudPlatform/google-cloud-java/issues/1575

Codecov Report

Merging #235 into master will decrease coverage by 0.35%.
The diff coverage is 85.52%.

@@             Coverage Diff              @@
##             master     #235      +/-   ##
============================================
- Coverage     70.54%   70.19%   -0.36%
- Complexity      492      520      +28
============================================
  Files            69       75       +6
  Lines          2550     2416     -134
  Branches        269      257      -12
============================================
- Hits           1799     1696     -103
+ Misses          652      621      -31
  Partials         99       99

Impacted Files
Coverage Δ
Complexity Δ

...main/java/com/google/api/gax/core/SystemClock.java
0% <0%> (ø)
0 <0> (?)

...in/java/com/google/api/gax/grpc/UnaryCallable.java
76.66% <100%> (-13.34%)
17 <1> (ø)

.../google/api/gax/retrying/RetryAttemptSettings.java
100% <100%> (ø)
7 <7> (?)

.../google/api/gax/retrying/AbstractRetryHandler.java
100% <100%> (ø)
8 <8> (?)

...google/api/gax/retrying/ScheduledRetryHandler.java
100% <100%> (ø)
2 <2> (?)

...in/java/com/google/api/gax/core/RetrySettings.java
41.02% <60%> (-0.65%)
3 <2> (ø)

...java/com/google/api/gax/core/DefaultNanoClock.java
66.66% <66.66%> (ø)
4 <4> (?)

...om/google/api/gax/retrying/DirectRetryHandler.java
70% <70%> (ø)
3 <3> (?)

...a/com/google/api/gax/retrying/RetryFutureImpl.java
86.2% <86.2%> (ø)
13 <13> (?)

...java/com/google/api/gax/grpc/RetryingCallable.java
94.87% <95.83%> (+5.18%)
6 <1> (-4)
:x:

... and 42 more

Continue to review full report at Codecov.

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

Addressed review comments, PTAL.

PTAL
Addressed the review comments, plus some other smaller changes:

Split RetryHandler on 3 different components: 1) scheduling logic, 2) time-specific and 3) exception-specific retry logics.
Removed abstract classes.
Renamed NanoClock to ApiClock, as it has System.currentTimeMillis() implementation, and NanoClock name is misleading now.

Adressed PR comments, PTAL.

PTAL

Offline agreements:

Rename SystemClock to CurrentMillisClock
Have ExceptionAlgorithm.createNextAttempt return null if it is not overriding the settings

LGTM after these are done - Shin should probably also approve.

PTAL

Done

LGTM


Update SAW Functional Verification Tests for compatibility with s2n_hash dual implementation

Following PR #529, where an EVP s2n_hash implementation was added, the SAW tests require updates to test the HMAC using s2n_hash low_level implementations (the existing implementations - used when outside of FIPS mode).

@atomb It appears that the SAW tests for this PR have failed. Is it a Travis cache issue? They passed in my repo: https://travis-ci.org/bpdavidson/s2n/builds/258320108

I suspect it's a caching issue. The updated scripts require the latest SAW, and I think the cache includes the SAW binaries. Clearing the cache and re-running it should fix the problem.

SAW Tests Pass, merging to FIPS Feature branch. ct-verif test fails because this branch doesn't have fix from https://github.com/awslabs/s2n/pull/552


benchmarks

We haven't run the benchmarks in a while. On controlled, properly set up hardware we should run the benchmarks for every Boost release of JSON and keep track of any regressions or improvements. We should also investigate how the per-commit benchmarks work, what kind of hardware they are running on, and make a determination if they are providing us value. There is the possibility that they are not accurate.

how do the per-commit benchmarks work

The jenkins server has a job to monitor pull requests on boostorg/json. When a pull request is submitted it checks out the code and runs this script:
https://github.com/CPPAlliance/Infrastructure-Docs/blob/master/benchmarks/json/runbenchmarks.py
Parameters of runbenchmarks.py are configurable. The command it runs is overridden:
benchcommand = "sudo cset shield --exec -- nice -n -20 sudo -u nodejenkins ./bench -i:b *.json"

cset isolates the process on a separate CPU core.
The overall job takes approximately 1 hour to run benchmarks on the develop branch and the PR branch and compare them.

how about the accuracy of benchmarks

The benchmark servers are set up using techniques to minimize interference from other programs. Many services are disabled and stopped. IRQ interrupts are moved to another cpu. Hyperthreading and turbo boost are disabled.  cpu frequency is set to not vary.  These techniques are discussed at https://github.com/CPPAlliance/Infrastructure-Docs/blob/master/benchmarks/json/README.md

prepare-hardware.sh adjusts cpu settings and interrupts.
prepare-server.sh cleans up services and cronjobs.
prepare-json.sh installs boost, git, and other prerequisites.

There is "invisible" evidence, hiding in plain sight, about how accurate the benchmarks are, which is the following. Consider that in the early iterations of the benchmarks, before many optimizations were added, the results might show bright red or green, with variation of 1%, 2%, 3%, even though nothing had changed in the codebase. If a benchmark varied by 2% for no reason, that was the test environment's fault.  Each run of the tests was unpredictable, due to random variations on the benchmark server, caused by interference from other processes using memory, cpu, shared busses on the hardware, and other random factors.   However, the current benchmarks display a remarkable number of 0.0% results.  Not 0.1% , 0.2%, 0.3%.  A 0.0% might seem unimportant but in fact it verifies the consistency between multiple test runs.
One might harbor a suspicion though, "Are the benchmarks really working?  To investigate that, there is also a cronjob which runs benchmarks once per day, comparing recent git commits with selected older commits from 2020. Here is an example output https://benchmark.cppalliance.org/jsonbenchmarks-intel/merged-results-across-commits/charts/2022-05-28-05-00-02.html   Notice at the top of the page under "Parse apache_builds.json", how the times from 2020 are worse than recent 2022 results. These results are computed from ./runbenchmarks.py and are recomputed each time, not relying on cached values.  They vary by 10% or more.

what kind of hardware they are running on

Server hosting at knownhost.com. The specs:
CPU Dual Intel Xeon E5620 @ 2.4GHz (8 Cores + HT)
Memory (RAM) 32GB DDR3 ECC
RAID None
Drive 1 240GB Enterprise SSD

Wow


Crashes when directories becomes empty after applying exceptions in config

How to recreate:

Add "" as exception making all files to be ignored by the directory list.

The directoryfilter is complicating the code, and fixing this issue will complicate the code even further. My proposal is to remove this option altogether, as it is not very, if at all, important.

Yes I tried to fix it, but the issue together with caching of the directory structure made it very hard.


[WIP] Introduction of MemoryPool based CharTextWriter

An experimental PR that changes CharArrayTextWriter pooling behavior from the custom one to one based on MemoryPool<char> from System.Memory package

I tried to follow this comment from travis https://github.com/travis-ci/travis-ci/issues/8990#issuecomment-385357592 to make the build green. I don't know travis much and if somebody could help me in enabling C# 7.2 for this PR I'd be grateful.

@jeremydmiller could you please rerun the travis ci test for this PR?

Hey @jeremydmiller , did you get a green build of it? I can't see the status and this was marked as WIP 😅

Yep.


RHIDP-2236: Update GS guide abstract

Version(s):
1.2.2
Issue:
https://issues.redhat.com/browse/RHIDP-2236
Reviews:

[ ] Docs: TBD

/cherrypick 1.2.x


Add type for log_output param

This fixes a problem where the parameter is a boolean, but not specified as such, so it picks up the default parameter type which is string. If one actually tries to use this, you get an error when you try to pass in the default parameter type or the boolean type.
As it is being used as a boolean later on, I changed the type to boolean.

Thanks for contributing to fastlane! Before you submit your pull request, please make sure to check the following boxes:

[ ] Run rspec for all tools you modified
[ ] Run rubocop -a to ensure the code style is valid
[ ] We currently don't accept new actions, please publish a plugin instead, more information in Plugins.md

Before submitting a pull request, we appreciate if you create an issue first to discuss the change :+1:

I have yet to run rspec and rubocop

@TKBurner reminder

@TKBurner poke

Looks good, thanks. This will be in the next release 👍


Converting a string containing "

When I paste this code in the converter :
test1 = "Simple\"Test";
If the  "colorize source" option is active, the code is transformed into :
test1 = "Simple\"Test"\"Test";
Regardless of the option "colorize source" is active or not, the generated VB code is incorrect.
test1 = "Simple""Test"""Test"

@lorcQc I saw that when the colorizer is on. There is """ and some extra text. This is coming from the colorizer and I have not yet figured out why. The version I just posted I turn off the colorizer for many scenarios which helps. But I need to figure would what is happening, the colorize code is something I have will the original repo and I haven't changed it but maybe on the the Roslyn libraries has changed. I will look at this today.
With the colorizer off it looks to me to be generating the correct result
test1 = "Simple""Test"

@lorcQc I saw that when the colorizer is on. There is """ and some extra text. This is coming from the colorizer and I have not yet figured out why. The version I just posted I turn off the colorizer for many scenarios which helps. But I need to figure would what is happening, the colorize code is something I have will the original repo and I haven't changed it but maybe on the the Roslyn libraries has changed. I will look at this today.
With the colorizer off it looks to me to be generating the correct result
test1 = "Simple""Test"

I confirm that when "Colorize Result" and "Colorize Source" are off, it works.
Thank you!

I confirm that when "Colorize Result" and "Colorize Source" are off, it works.
Thank you!

I believe this was a new feature added to Roslyn Colorization that I did not support, I am looking to work around it, until I understand it. It is "fixed" in  New in <IP_ADDRESS>/<IP_ADDRESS>. @DualBrain this also addresses your issue.

I believe this was a new feature added to Roslyn Colorization that I did not support, I am looking to work around it, until I understand it. It is "fixed" in  New in <IP_ADDRESS>/<IP_ADDRESS>. @DualBrain this also addresses your issue.


x/vgo: import path is resolved to the wrong version

What version of Go are you using (go version)?
» vgo version
go version go1.10.1 linux/amd64 vgo:2018-02-20.1

Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/u/.cache/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/u/go"
GORACE=""
GOROOT="/usr/lib/go"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build277438090=/tmp/go-build -gno-record-gcc-switches"

What did you do?
I've imported a package using versioned syntax: import _ "github.com/gomodule/redigo/v2/redis"
What did you expect to see?
Version 2.0.0 of redigo imported;
» vgo list -t github.com/gomodule/redigo/v2                2018-04-23 12:55:36
github.com/gomodule/redigo/v2
        v2.0.0

What did you see instead?
Path is resolved to version 1.6 with v2 subdir -
CGO_ENABLED=0 CC=gcc vgo build -a -tags netgo -o /home/u/gtl/bx/listing_api/bin/listing_api ./cmd/listing_api
vgo: resolving import "github.com/gomodule/redigo/v2/redis"
vgo: finding github.com/gomodule/redigo (latest)
vgo: adding github.com/gomodule/redigo v1.6.0
vgo: import "myrepo/listing_api/cmd/listing_api" ->
        import "github.com/gomodule/redigo/v2/redis"<EMAIL_ADDRESS>open<EMAIL_ADDRESS>no such file or directory
make: *** [Makefile:10: build] Error 1

Import path with a /v2/ is only available for packages directly supporting vgo and has a go.mod file, redigo does not.
In addition to that, #24585 is about vgo incorrectly generating the go.mod file for legacy packages with versions >= v2.0.0

Yes, if github.com/gomodule/redigo does not opt into semantic import versioning by creating a go.mod that says 'module github.com/gomodule/redigo/v2', then you cannot import it using that path.
However, you can still import the old name under a pseudo-version. If you run
vgo get<EMAIL_ADDRESS>
then vgo will add to go.mod not v2.0.0 (that doesn't match the module path) but instead
github.com/gomodule/redigo v0.0.0-20180314223443-9c11da706d9b

which is the same code.


[PlayCode] -> [others]

Link : https://playcode.io/
description : build your html, css, javascript online

@studmuffin30  please check #514.

will be checked


TimeSeries always iterates over all the data

Hi I've been experimenting with ta4j and would like to create a TimeSeries using a memory map backed list. The only issue is that the creating a TimeSeries always iterates over the entire dataset to calculate the timePeriod.
I already know the timePeriod so would it be possible to add the ability to specify this manually?

Hi,
What if the period of the time series does not match the period of the tick?
I understand the problem but I think it would need a deeper thinking before roughly accepting your PR.
Marc

Could this be something that is calculated on demand rather than in the constructor? It could even cache the value for subsequent calls.

Of course! I will try to address the problem as the same time as #81.

Finally I just removed the time period. I realized that I don't know any relevant use case of it since it's an approximation.


Feature request: Interrogate CLIP and Interrogate DeepBooru for koishi-novelai-bot and SD-Webui users

Feature request: Add a interrogate function based on API of Interrogate CLIP and Interrogate DeepBooru in Stable Diffusion WebUI
Name suggestion: sd-interroage
Function name suggestion: interrogate, intrg
Console inputs suggestion: endpoint, headers, max words return, default method(DeepBooru or CLIP)
Just do it. :-)

已完成，插件市场搜索 sd-interroage


Custom tree right click broken

Expected (Stable):

Bug (Insiders):

Version: 1.38.0-insider
Commit: 8985ff7c9d38bd2ce7d1e6b58e40d27c5bbdb67b
Date: 2019-08-15T07:34:22.748Z
Electron: 4.2.9
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Darwin x64 18.6.0

Strange.
This works fine for me on Windows with GitHub Pull Request Nightly Build (2019.8.19623) on the same VS Code Insiders build.

VS Code version: Code - Insiders 1.38.0-insider (8985ff7c9d38bd2ce7d1e6b58e40d27c5bbdb67b, 2019-08-15T07:37:38.653Z)
OS version: Windows_NT x64 10.0.18362

I'm on 0.10.0 on GH PR extension. Also wondering if it's only on macOS as it might be related to native context menus.

Now it feels like OS specific. Works as expected with 0.10.0 on Windows  for me.

VS Code version: Code - Insiders 1.38.0-insider (8985ff7c9d38bd2ce7d1e6b58e40d27c5bbdb67b, 2019-08-15T07:37:38.653Z)
OS version: Windows_NT x64 10.0.18956

Extension
Author (truncated)
Version

vscode-pull-request-github
Git
0.10.0

Bringing this to your attention @alexr00, as it affects all custom tree's right click:

Tested on Windows and it works there. Looks like it could be mac specific then. @sbatten are native context menus under your purview?

@alexr00 yes, but using native context menus on windows doesn't seem to reproduce the issue.

This is caused by the Sass extension contributing actions to the menu without filtering to their view in the when clause. I think it is strange that an extension can accidentally bleed everywhere as I would expect by default that my command only shows up in my view.

Thank you for investigating!


Docs; ATO-1063 Rasa Pro install doc update

Proposed changes:

...

Status (please check what you already did):

[ ] added some tests for the functionality
[x] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

@andreaklmn Can you please review this?

@rgstephens I added a missing changelog fragment (please include it next time 🙏🏻 ), changed the base branch to 3.6.x (add to cherry-pick commits and force push) instead of main, so that your changes are released sooner. And I've enabled auto-merge


The link to pixi.min.js is dead in the Learning Pixi doc.

Might want to update that link because as of now it takes you to this 404: https://github.com/pixijs/pixi.js/tree/master/bin

Hey @chrispwns, I assume you are talking about: https://github.com/kittykatattack/learningPixi?
You should file an issue with that repository, the Pixi team does not maintain it.

You were right, I went ahead and submitted a pull request over there to hopefully fix the link.

Thanks @chrispwns


Question about preloading, create session and loading of a plug in endpoint.ex

I have a User that belongs_to an Employee (belonging_to an Organization). The SessionController.create/2 is like:
defmodule MyAppWeb.SessionController do
  use MyAppWeb, :controller
  alias MyApp.Repo

  def create(conn, %{"user" => user_params}) do
    conn
    |> Pow.Plug.authenticate_user(user_params)
    |> case do
      {:ok, conn} ->
        user = Pow.Plug.current_user(conn) |> Repo.preload(employee: :organization)

        conn
        |> put_flash(:info, "Welcome back #{user.employee.name}!")
        |> redirect(to: Routes.organization_path(conn, :show, user.employee.organization))

      {:error, conn} ->
        changeset = Pow.Plug.change_user(conn, conn.params["user"])

        conn
        |> put_flash(:info, "Password and Email don't match")
        |> render("new.html", changeset: changeset)
    end
  end
end

I also have a LoadEmployeePlug (which is added to the Endpoint) like:
defmodule MyApp.LoadEmployeePlug do
  @doc false

  @spec init(any()) :: any()
  def init(opts), do: opts

  @doc false
  @spec call(Conn.t(), atom()) :: Conn.t()
  def call(conn, _opts) do
    config = Pow.Plug.fetch_config(conn)

    case Pow.Plug.current_user(conn, config) do
      nil ->
        conn

      user ->
        employee = MyApp.Repo.preload(user, employee: :organization)

        Pow.Plug.assign_current_user(conn, employee, config)
    end
  end
end

I would expect I shouldn't have to preload employee: :organization in the SessionController, because of the LoadEmployeePlug,  but that doesn't seem to work. Also see https://github.com/danschultzer/pow/issues/331.

The plug runs before the Pow.Plug.authenticate_user/2 call, so the association won't be preloaded. One way to refactor this would be to call the plug after:
defmodule MyAppWeb.SessionController do
  use MyAppWeb, :controller
  alias MyApp.Repo

  def create(conn, %{"user" => user_params}) do
    conn
    |> Pow.Plug.authenticate_user(user_params)
    |> case do
      {:ok, conn} ->
        user =
          conn
          |> MyApp.LoadEmployeePlug.call([])
          |> Pow.Plug.current_user(conn)

        conn
        |> put_flash(:info, "Welcome back #{user.employee.name}!")
        |> redirect(to: Routes.organization_path(conn, :show, user.employee.organization))

      {:error, conn} ->
        changeset = Pow.Plug.change_user(conn, conn.params["user"])

        conn
        |> put_flash(:info, "Password and Email don't match")
        |> render("new.html", changeset: changeset)
    end
  end
end

It's preferred to load straight from DB, but the sync guide also details an alternative where you update what's in the cache.

Is there a way to load the associations like we regularly do? Like in the Context schema?
def get_user!(id) do
    User
    |> Repo.get!(id)
    |> Repo.preload(:credential)
end

Mind that Credential in the Phoenix examples are like Pows User.

That would store the association in the cache too. To do that you can either use the example in the sync guide, or you can do as described in https://github.com/danschultzer/pow/issues/308#issuecomment-545475332, using a custom context:
defmodule MyApp.Users do
  use Pow.Ecto.Context,
    repo: MyApp.Repo,
    user: MyApp.Users.User

  @impl true
  def get_by(clauses) do
    clauses
    |> pow_get_by()
    |> preload_credential()
  end

  defp preload_profile(nil), do: nil
  defp preload_profile(user) do
    MyApp.Repo.preload(user, :credential)
  end
end

Ok, thanks!


Accounts Aging reports UI and API integration

Notion card
https://www.notion.so/saeloun/Create-the-frontend-designs-for-Accounts-Aging-report-09c39ab08a7244edbb5503aad9a30c10
Summary

Accounts aging report section added.
Table with alphabetical order, Filter with search, table row with total and summary dashboard  added.

Preview

https://www.loom.com/share/967df4701ddf4a518e0458b47ce4bc4b
Type of change

[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to
not work as expected)

How Has This Been Tested?

Checked Filtering of the reports.
Checked empty states.
Pagination is not implemented.

Checklist:

[x] I have manually tested all workflows
[x] I have performed a self-review of my own code
[x] I have annotated changes in the PR that are relevant to the reviewer

@Shruti-Apte App is breaking. Please fix

@Shruti-Apte Lets close the review comments from Apoorv and Prasanth on this PR today.

@Shruti-Apte Something is wrong with the aging reports. Not able to see clients and their data.

Fixed!


🐛 Bug Report: pick scaffolder filter doesn't work as expected

📜 Description
The pick scaffolder filter introduced in v1.13.0 doesn't work as expected when used for instance on entities retrieved from the catalog.
👍 Expected behavior
When using the following steps:
steps:
    - id: catalogFetch
      name: Fetch Context
      action: catalog:fetch
      input:
        entityRef: ${{ parameters.api }}
    - name: Debug definition
      action: debug:log
      input:
        message: ${{ steps.catalogFetch.output | pick('spec') | pick('definition') }}

It is expected for the debug:log action to be given the spec.definition attribute of the (in this case) API definition.
👎 Actual Behavior with Screenshots
The snippet isn't interpreted that the debug:log outputs ${{ steps.catalogFetch.output | pick('spec') | pick('definition') }} instead of the contents of the definition attribute.

Check the Reproduction steps for more context.

👟 Reproduction steps
Create a template similar to the following
apiVersion: scaffolder.backstage.io/v1beta3
kind: Template
metadata:
  name: test-api-template
  title: Test pick filter
  tags: []
  links: []
spec:
  type: configuration
  parameters:
    - title: Initial configuration
      required:
        - api
      properties:
        api:
          title: API
          type: string
          description: The API you want to test
          ui:field: EntityPicker
          ui:options:
            defaultKind: API
            catalogFilter:
              - kind:
                  - API
                spec.type: openapi
            allowArbitraryValues: false
  steps:
    - id: catalogFetch
      name: Fetch Context
      action: catalog:fetch
      input:
        entityRef: ${{ parameters.api }}
    - name: Debug definition
      action: debug:log
      input:
        message: ${{ steps.catalogFetch.output | pick('spec') | pick('definition') }}
    - name: Debug spec
      action: debug:log
      input:
        message: ${{ steps.catalogFetch.output | pick('spec') }}
    - name: Debug output
      action: debug:log
      input:
        message: ${{ steps.catalogFetch.output }}

And register an API resource on the catalog for testing purposes:
apiVersion: backstage.io/v1alpha1
kind: API
metadata:
  name: test-openapi-api
spec:
  type: openapi
  lifecycle: test
  definition:
    $text: the path to some openapi spec

When the scaffolder runs the test-api-template it will output each step something like:
Fetch Content
[1](http://localhost:3000/create/tasks/90954478-b868-4a9c-b4e4-135c7bfbff94#line-1)2023-06-13T10:13:58.000Z Beginning step Fetch Context
[2](http://localhost:3000/create/tasks/90954478-b868-4a9c-b4e4-135c7bfbff94#line-2)2023-06-13T10:13:58.000Z Finished step Fetch Context

Debug definition
[1](http://localhost:3000/create/tasks/90954478-b868-4a9c-b4e4-135c7bfbff94#line-1)2023-06-13T10:13:58.000Z Beginning step Debug definition
[2](http://localhost:3000/create/tasks/90954478-b868-4a9c-b4e4-135c7bfbff94#line-2)2023-06-13T10:13:58.000Z info: {
[3](http://localhost:3000/create/tasks/90954478-b868-4a9c-b4e4-135c7bfbff94#line-3)  "message": "${{ steps.catalogFetch.output | pick('spec') | pick('definition') }}"
[4](http://localhost:3000/create/tasks/90954478-b868-4a9c-b4e4-135c7bfbff94#line-4)}
[5](http://localhost:3000/create/tasks/90954478-b868-4a9c-b4e4-135c7bfbff94#line-5)2023-06-13T10:13:58.000Z ${{ steps.catalogFetch.output | pick('spec') | pick('definition') }}
[6](http://localhost:3000/create/tasks/90954478-b868-4a9c-b4e4-135c7bfbff94#line-6)2023-06-13T10:13:58.000Z Finished step Debug definition

Debug spec
[1](http://localhost:3000/create/tasks/90954478-b868-4a9c-b4e4-135c7bfbff94#line-1)2023-06-13T10:13:58.000Z Beginning step Debug spec
[2](http://localhost:3000/create/tasks/90954478-b868-4a9c-b4e4-135c7bfbff94#line-2)2023-06-13T10:13:58.000Z info: {
[3](http://localhost:3000/create/tasks/90954478-b868-4a9c-b4e4-135c7bfbff94#line-3)  "message": "${{ steps.catalogFetch.output | pick('spec') }}"
[4](http://localhost:3000/create/tasks/90954478-b868-4a9c-b4e4-135c7bfbff94#line-4)}
[5](http://localhost:3000/create/tasks/90954478-b868-4a9c-b4e4-135c7bfbff94#line-5)2023-06-13T10:13:58.000Z ${{ steps.catalogFetch.output | pick('spec') }}
[6](http://localhost:3000/create/tasks/90954478-b868-4a9c-b4e4-135c7bfbff94#line-6)2023-06-13T10:13:58.000Z Finished step Debug spec

Debug output 🟥
[1](http://localhost:3000/create/tasks/90954478-b868-4a9c-b4e4-135c7bfbff94#line-1)2023-06-13T10:13:58.000Z Beginning step Debug output
[2](http://localhost:3000/create/tasks/90954478-b868-4a9c-b4e4-135c7bfbff94#line-2)2023-06-13T10:13:58.000Z InputError: Invalid input passed to action debug:log, instance.message is not of a type(s) string
...

The Debug output step fails because the input provided isn't a string. If the pick filter worked as expected then the Debug spec step should have failed as well because it should have also been given an object.
📃 Provide the context for the Bug.
No response
🖥 Your Environment
OS:   Darwin 22.5.0 - darwin/arm64
node: v16.14.0
yarn: 1.22.17
cli:  0.22.7 (installed)
backstage:  1.14.1

Dependencies:
  @backstage/app-defaults                               1.3.1
  @backstage/backend-app-api                            0.4.3
  @backstage/backend-common                             0.18.5
  @backstage/backend-dev-utils                          0.1.1
  @backstage/backend-plugin-api                         0.5.2
  @backstage/backend-tasks                              0.5.2
  @backstage/catalog-client                             1.4.1
  @backstage/catalog-model                              1.3.0
  @backstage/cli-common                                 0.1.12
  @backstage/cli-node                                   0.1.0
  @backstage/cli                                        0.22.7
  @backstage/config-loader                              1.3.0
  @backstage/config                                     1.0.7
  @backstage/core-app-api                               1.8.0
  @backstage/core-components                            0.13.1
  @backstage/core-plugin-api                            1.5.1
  @backstage/dev-utils                                  1.0.15
  @backstage/errors                                     1.1.5
  @backstage/eslint-plugin                              0.1.3
  @backstage/integration-aws-node                       0.1.3
  @backstage/integration-react                          1.1.13
  @backstage/integration                                1.4.5
  @backstage/plugin-api-docs                            0.9.3
  @backstage/plugin-app-backend                         0.3.45
  @backstage/plugin-auth-backend                        0.18.3
  @backstage/plugin-auth-node                           0.2.14
  @backstage/plugin-catalog-backend-module-github       0.3.0
  @backstage/plugin-catalog-backend                     1.9.1
  @backstage/plugin-catalog-common                      1.0.13
  @backstage/plugin-catalog-graph                       0.2.30
  @backstage/plugin-catalog-import                      0.9.8
  @backstage/plugin-catalog-node                        1.3.6
  @backstage/plugin-catalog-react                       1.6.0
  @backstage/plugin-catalog                             1.11.0
  @backstage/plugin-events-node                         0.2.6
  @backstage/plugin-github-actions                      0.5.18
  @backstage/plugin-graphiql                            0.2.50
  @backstage/plugin-org                                 0.6.8
  @backstage/plugin-permission-backend                  0.5.20
  @backstage/plugin-permission-common                   0.7.5
  @backstage/plugin-permission-node                     0.7.8
  @backstage/plugin-permission-react                    0.4.12
  @backstage/plugin-proxy-backend                       0.2.39
  @backstage/plugin-scaffolder-backend                  1.14.0
  @backstage/plugin-scaffolder-common                   1.3.0
  @backstage/plugin-scaffolder-node                     0.1.3
  @backstage/plugin-scaffolder-react                    1.4.0
  @backstage/plugin-scaffolder                          1.13.1
  @backstage/plugin-search-backend-module-catalog       0.1.1
  @backstage/plugin-search-backend-module-pg            0.5.6
  @backstage/plugin-search-backend-module-techdocs      0.1.1
  @backstage/plugin-search-backend-node                 1.2.1
  @backstage/plugin-search-backend                      1.3.1
  @backstage/plugin-search-common                       1.2.3
  @backstage/plugin-search-react                        1.6.0
  @backstage/plugin-search                              1.3.0
  @backstage/plugin-tech-insights-backend-module-jsonfc 0.1.29
  @backstage/plugin-tech-insights-backend               0.5.11
  @backstage/plugin-tech-insights-common                0.2.10
  @backstage/plugin-tech-insights-node                  0.4.3
  @backstage/plugin-tech-insights                       0.3.10
  @backstage/plugin-techdocs-backend                    1.6.2
  @backstage/plugin-techdocs-module-addons-contrib      1.0.13
  @backstage/plugin-techdocs-node                       1.7.1
  @backstage/plugin-techdocs-react                      1.1.6
  @backstage/plugin-techdocs                            1.6.2
  @backstage/plugin-user-settings                       0.7.3
  @backstage/release-manifests                          0.0.9
  @backstage/test-utils                                 1.3.1
  @backstage/theme                                      0.2.19, 0.3.0
  @backstage/types                                      1.0.2
  @backstage/version-bridge                             1.0.4

👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else

The problem turns out is not on the pick filter but rather on the provided parameters.
The snippet ${{ steps.catalogFetch.output | pick('spec') | pick('definition') }} should be ${{ steps.catalogFetch.output.entity | pick('spec') | pick('definition') }}.


Initial Discord bot implementation

Still very rough around the edges, but seems to work. Currently supports
sending a command starting with !puzzles. By default, the command
lists unsolved puzzles, but you can supply a subcommand like !puzzles stuck to view all puzzles with STUCK status. Current commands:
- !puzzles
- !puzzles unsolved
- !puzzles solved
- !puzzles stuck
Still need to implement:

[x] Links to puzzles in response
[x] Status for puzzles (since "stuck" includes STUCK and EXTRACTION)
[x] Answers for solved puzzles (maybe?)

For #214

It works :) and runs on heroku :+1: see the #discord-bot-spam channel in our server.

It works :) and runs on heroku :+1: see the #discord-bot-spam channel in our server.

One limitation we'll need to resolve: Discord embeds (used by this bot) currently limit field values to 1024 characters. If there are lots of puzzles to list, we might need more characters. One simple solution might be to use regular text instead of embeds...but embeds look so nice :joy:

One limitation we'll need to resolve: Discord embeds (used by this bot) currently limit field values to 1024 characters. If there are lots of puzzles to list, we might need more characters. One simple solution might be to use regular text instead of embeds...but embeds look so nice :joy:


RenderingSystem with SortedIteratingSystem in wiki is wrong

This is an issue in a part of the wiki that is misleading and plain wrong.
The following code does not work and it does not provide a good alternative/implementation of the Comparator to be used with the SortedIteratingSystem:
`public class RenderingSystem extends SortedIteratingSystem {
private ComponentMapper rm;
private ComponentMapper pm;
public RenderingSystem() {
    super(Family.all(RenderableComponent.class, PositionComponent.class).get(), new ZComparator());

    rm = ComponentMapper.getFor(RenderableComponent.class);
    pm = ComponentMapper.getFor(PositionComponent.class);
}

protected void processEntity(Entity entity, float deltaTime) {
    // Render the entity
}

private class ZComparator implements Comparator<Entity> {
    @Override
    public int compare(Entity e1, Entity e2) {
        return (int)Math.signum(pm.get(e1).z - pm.get(e2).z);
    }
}

}`
That code does not compile as the call to the super constructor should be the first thing called inside the RenderingSystem constructor, but this rule is broken when you are instantiating the ZComparator());
Now the ZComparator must be an inner class as it needs to access pm. Not sure how to solve that but the way it is right now its wrong.

The ZComparator just needed to be static, that's all. Fixed.

Sorry, Its not my intention to bother, bot setting the ZComparator to static makes the RenderingSystem.pm unaccessible from within the ZComparator

Did this ever get resolved?

I think it should be OK now.


Fix slow imports to speed up paster

Would be better with a comment, to guard against people moving them back or adding others at the top.


triton.language.where return float32 always even if input is float16

triton.language.where return float32 always even if input is float16.
var = triton.language.zeros([vec_bs], dtype=triton.language.float16)

for off in range(0, vec_sz, vec_bs):
    # Do somthing
    x = triton.language.where(msk, x - mean, 0)
    var += language.pow2(x)

Error message is AssertionError('Loop-carried variable var has initial type <[32768], fp16> but is re-assigned to <[32768], fp32> in loop! Please make sure that the type stays consistent.').

@Jokeren I tried x = triton.language.where(msk, x - mean, triton.language.zeros([1], dtype)) but I got a same error.

Can you provide a full script?

Hi,
@Jokeren
im glad you brought up the cast function! im having problem with data type in triton, mainly
triton.language.semantic.IncompatibleTypeErrorImpl: invalid operands of type pointer<int64> and triton.language.int32
i understand i need to cast my data to triton.language.int32, but cant find a way to do it. tl.cast does not exist anymore.
any recommendations?
Thanks

There isn't a cast function. Please use <tensor>.to(<data_type>)

ah, i see. thank you
i was able to use data = data.to(tl.int32) to fix this. but how come the to method did not show up in dir(triton.language)?
not essential, but very curious.

@Jokeren Sorry for late response.

git clone https://github.com/kakaobrain/trident.git
cd trident
git checkout triton/issue_1891
export PYTHONPATH=${PYTHONPATH}:${pwd}
pytest -k test_instance_norm

Thanks!


How achieve multiple files upload with pause resume.

For single file upload , it's works well . so now i need to know , how to use this package for folder upload i.e multiple files upload with pause resume functionality.
do i need to combine the streams in  to single stream ?? how to achieve multiple file upload ??

can you try zipping the folder and the upload by unzipping the same in streams


texlive: accept gracefully packages without pname or version

Description of changes
Quick fix for the issue reported in https://github.com/NixOS/nixpkgs/issues/213632#issuecomment-1506579997: in the new combinePkgs, I inadvertently forced packages to have a version, breaking some people setups.
This PR makes combinePkgs more lenient in the absence of version and even pname (falling back to name in that case).
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[X] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[X] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Great! I'll be able to remove the version attribute from my custom LaTeX packages!

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/903


chore: remove useless compiler_flag and copy .exe on windows

v install should not be concerned with compilation flags.
And the actual compiler is determined by build.vsh:

PS C:\Users\***\.config\v-analyzer> $Env:CC = 'clang'
PS C:\Users\***\.config\v-analyzer> v .\install.vsh up --nightly
Installing latest nightly version...
Updating v-analyzer sources...
✓ Successfully updated v-analyzer sources
Building v-analyzer...
✓ Dependencies for v-analyzer installed successfully
Building v-analyzer at commit: 7e11a6f, build time: 2024-06-15 01:17:19 ...
✓ Prepared output directory
Building v-analyzer in debug mode, using: "E:\Programs\v\v.exe" "C:\Users\***\.config\v-analyzer\sources" -o "./bin/v-analyzer.exe" -no-parallel -cc clang  -g
To build in release mode, run v build.vsh release
Release mode is recommended for production use. At runtime, it is about 30-40% faster than debug mode.
✓ Successfully built v-analyzer!
Binary is located at C:\Users\***\.config\v-analyzer\sources\bin\v-analyzer.exe

Moving v-analyzer binary to the standard location...
Failed to copy v-analyzer binary to C:\Users\***\.config\v-analyzer\bin: Failed to remove "C:\Users\***\.config\v-analyzer\bin\v-analyzer.exe": Permission denied; code: 13
✓ v-analyzer successfully updated to nightly (7e11a6f8f369df935664fadd2f0c99d90fe3226f)
Path to the binary: C:\Users\***\.config\v-analyzer\bin\v-analyzer

Also, the executable has .exe extension on Windows, thus v-analyzer.exe should be copied on Windows

The analyzer test failure is unrelated, and due to a change in string.is_upper() that happened in https://github.com/vlang/v/pull/21358 , while v-analyzer's CI was not ran after that (we only test that v-analyzer itself builds on the main V CI, and not that v-analyzer's CI passes).

I am not sure whether to fix pascal_case_to_snake_case or its tests, but I am more inclined to change pascal_case_to_snake_case to preserve its old behavior. @ttytm what do you think?

https://github.com/vlang/v-analyzer/blob/7e11a6f8f369df935664fadd2f0c99d90fe3226f/src/utils/text_utils.v#L6
- if c.ascii_str().is_upper() {
+ if c.ascii_str().is_upper() || c.is_digit() {

https://github.com/vlang/v-analyzer/blob/7e11a6f8f369df935664fadd2f0c99d90fe3226f/src/utils/text_utils.v#L6
- if c.ascii_str().is_upper() {
+ if c.ascii_str().is_upper() || c.is_digit() {

Applied in 2584e86 .

(rebased over current main)


no built in library for typescript

npm install @types/process-list
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@types%2fprocess-list - Not found
npm ERR! 404
npm ERR! 404  '@types/process-list@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/leonardo/.npm/_logs/2020-08-18T13_51_07_663Z-debug.log

I don't known how to do that, PR welcome. or just use plain js.

@LeonardoRick I've created a simple example for typescript.
Please check out https://github.com/yeoupooh/node-process-list-ts-example
Hope this helps.

@LeonardoRick I've created a simple example for typescript.
Please check out https://github.com/yeoupooh/node-process-list-ts-example
Hope this helps.