~20 minute delay when completing lock interview on server start

Describe the bug
When I restart the server, my 3 Kwikset 914 locks have a ~20min unexpected delay after retrieving usercodes and before transitioning from RestartFromCache to Complete.  These locks have all been added securely and allowed to complete their interview, but this delay is observed every time when the zwjs server restarts.
The logs below are with "INFO" enabled, but the pattern is also present with "DEBUG" and I've included the log with debug enabled below.
zwavejs2mqtt-debug.zip
Scan starts here:
2021-02-17 16:59:40.106 INFO MQTT: Connecting to mqtt://<IP_ADDRESS>:1883
2021-02-17 16:59:40.156 INFO ZWAVE: Connecting to /dev/ttyACM0
2021-02-17 16:59:40.178 INFO APP: Listening on port 8091 host <IP_ADDRESS> protocol HTTP
2021-02-17 16:59:40.225 INFO MQTT: MQTT client connected
2021-02-17 16:59:45.691 INFO ZWAVE: Zwave driver is ready
2021-02-17 16:59:45.692 INFO ZWAVE: Controller status: Driver ready
2021-02-17 16:59:45.706 INFO ZWAVE: Scanning network with homeid: 0xe92faa0a

The scan proceeds, setting most line-powered nodes "Complete", and retrieves all 30 usercodes from all 3 locks.  At ~17:06:xx, metadata for the 112-0-xx parameters is updated for all 3 locks (sample of last communication):
2021-02-17 17:06:30.155 INFO ZWAVE: Node 64: metadata updated: 112-0-31-4
2021-02-17 17:06:30.156 INFO ZWAVE: Node 64: metadata updated: 112-0-31-8
2021-02-17 17:06:32.127 INFO ZWAVE: Node 44: value updated: 112-0-1 1 => 1
2021-02-17 17:06:33.603 INFO ZWAVE: Node 45: value updated: 112-0-1 1 => 1

At this point, all 3 locks are marked RestartFromCache, and remain that way for exactly 20 minutes.  During this time, there is no activity to any of the three locks, but other nodes report in and work properly.  After 20mins, I finally see some activity with the locks that goes like this:
2021-02-17 17:26:24.938 INFO ZWAVE: Node 44: value updated: 112-0-33 960049460 => 960049460
2021-02-17 17:26:26.450 INFO ZWAVE: Node 45: value updated: 112-0-33 960049460 => 960049460
2021-02-17 17:26:28.394 INFO ZWAVE: Node 64: value updated: 112-0-33 960049460 => 960049460
2021-02-17 17:26:30.384 INFO ZWAVE: Node 44: value updated: 112-0-34 808464947 => 808464947
2021-02-17 17:26:31.839 INFO ZWAVE: Node 45: value updated: 112-0-34 808464947 => 808464947
2021-02-17 17:26:32.424 INFO ZWAVE: Node 64: value updated: 112-0-34 808464947 => 808464947
2021-02-17 17:26:33.083 INFO ZWAVE: Node 44: value updated: 112-0-31-1 1 => 1
2021-02-17 17:26:33.086 INFO ZWAVE: Node 44: value updated: 112-0-31-2 0 => 0
2021-02-17 17:26:33.088 INFO ZWAVE: Node 44: value updated: 112-0-31-4 1 => 1
2021-02-17 17:26:33.092 INFO ZWAVE: Node 44: value updated: 112-0-31-8 0 => 0
2021-02-17 17:26:33.325 INFO ZWAVE: Node 45: value updated: 112-0-31-1 1 => 1
2021-02-17 17:26:33.328 INFO ZWAVE: Node 45: value updated: 112-0-31-2 0 => 0
2021-02-17 17:26:33.330 INFO ZWAVE: Node 45: value updated: 112-0-31-4 1 => 1
2021-02-17 17:26:33.332 INFO ZWAVE: Node 45: value updated: 112-0-31-8 0 => 0
2021-02-17 17:26:33.756 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 17:26:33.758 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 17:26:33.933 INFO ZWAVE: Node 64: value updated: 112-0-31-1 1 => 1
2021-02-17 17:26:33.936 INFO ZWAVE: Node 64: value updated: 112-0-31-2 0 => 0
2021-02-17 17:26:33.938 INFO ZWAVE: Node 64: value updated: 112-0-31-4 1 => 1
2021-02-17 17:26:33.940 INFO ZWAVE: Node 64: value updated: 112-0-31-8 0 => 0
2021-02-17 17:26:36.311 INFO ZWAVE: Node 44: interview completed, all values are updated
2021-02-17 17:26:36.324 INFO ZWAVE: Node 45: interview completed, all values are updated
2021-02-17 17:26:36.919 INFO ZWAVE: Node 64: interview completed, all values are updated

When this happens, the locks are finally all marked Complete.  Other nodes work fine during this 20 minute delay, both battery and line-powered.  When these locks are finally marked complete, they work fine remotely and when manually actuated.  The locks are marked "Alive" during this whole time, as viewed from the ZWJS2MQTT web ui.
I started to notice this behavior when the change to ignore sleeping nodes when marking the scan complete, but it's possible that it's been this way for a while.
Device information
Which device(s) is/are affected (make/model)?  Kwikset 914 locks
What are the node IDs? 44, 45, 64
Last Known Working Configuration

[ ] New device

[x] Previously working device (node-zwave-js)

Which library version/docker image/adapter version?
Have you made any recent configuration changes to the device? Describe.

[ ] Previously working device (other platform)

Which platform?
Have you made any recent configuration changes to the device? Describe.

Installation information
How did you install node-zwave-js?

[ ] zwavejs2mqtt (latest) docker image
[ ] zwavejs2mqtt (dev) docker image
[ ] ioBroker.zwave2 adapter
[ ] Pkg
[x] Manual Docker build

node-zwave-js branch: master
zwavejs2mqtt branch: master

[ ] Manually built (as described in the docs)
[ ] Other:

To Reproduce
Steps to reproduce the behavior:

Restart the zwjs2mqtt server and monitor the zwjs2mqtt web ui and log
Observe 20 minute delay in communication with a Kwikset 914 lock between reading the usercodes and finally marking the device "Complete"

Additional context
Add any other context about the problem here.
Logfile:

Here's a log with "INFO" enabled: zwavejs2mqtt.log
Here's a log with "DEBUG" enabled with the same behavior (search for "Node 45" from the bottom until you see the 20 minute gap): zwavejs2mqtt-debug.zip

Are they battery powered? If so, are you on 6.3.1?

Yes, they're battery-powered Kwikset 914 locks.  I pulled from master of both zwjs and zwjs2mqtt this morning and rebuilt my container, but the behavior has been consistent for a while now.  This is the version info from zwjs2mqtt:
Home ID<PHONE_NUMBER>
Home Hex 0xe92faa0a
App Version 1.1.1+2ea9944.2ea9944
Zwavejs Version 6.4.0-ad7995f8

Okay, but that is expected (at least for now). Those are battery-powered nodes that have been previously interviewed completely, so the driver knows everything about them it needs to know.
It doesn't sound like there is another problem, or am I missing something?

I came across this when I was debugging another seemingly-related issue that I should have mentioned.  During that 20min period of time before the locks reflect "Complete", the Z-Wave network is very slow to respond.  It will often take several seconds, maybe even 10s, for devices to respond, and the delays are unpredictable in length.  Once the locks are marked Complete, device response across the network is instantaneous.  The behavior repeats reliably as soon as I restart the server.  I see the long delay in device response even from the zwjs2mqtt control panel, independent of HA.
My apologies for not getting more quickly to the actual problem - I hate it when folks jump to their own conclusions on the HA forum :).
Here's a log snippet of controlling a GE/Jasco plug-in switch during that time period:
2021-02-17 20:14:08.358 INFO ZWAVE: Node 64: metadata updated: 112-0-31-8
2021-02-17 20:14:08.957 INFO ZWAVE: Node 44: value updated: 112-0-1 1 => 1
2021-02-17 20:14:09.204 INFO ZWAVE: Node 45: value updated: 112-0-1 1 => 1
2021-02-17 20:14:09.788 INFO ZWAVE: Node 64: value updated: 112-0-1 1 => 1
2021-02-17 20:14:22.044 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 0
2021-02-17 20:14:22.103 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:14:22.105 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => false
2021-02-17 20:14:22.349 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 0 => 8
2021-02-17 20:14:22.410 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:14:22.413 INFO ZWAVE: Node 19: value updated: 48-0-Motion false => true
2021-02-17 20:14:33.786 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:14:33.788 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:14:48.369 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:14:48.430 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:14:48.433 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => true
2021-02-17 20:15:03.783 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:15:03.786 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:15:19.349 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 0
2021-02-17 20:15:19.411 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:15:19.413 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => false
2021-02-17 20:15:19.669 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 0 => 8
2021-02-17 20:15:19.730 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:15:19.732 INFO ZWAVE: Node 19: value updated: 48-0-Motion false => true
2021-02-17 20:15:33.784 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:15:33.785 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:15:50.503 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 0
2021-02-17 20:15:50.562 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:15:50.564 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => false
2021-02-17 20:16:03.786 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:16:03.788 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:16:33.782 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:16:33.784 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:16:57.469 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 0 => 8
2021-02-17 20:16:57.530 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:16:57.532 INFO ZWAVE: Node 19: value updated: 48-0-Motion false => true
2021-02-17 20:17:03.783 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:17:03.786 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:17:14.732 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:17:14.792 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:17:14.794 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => true
2021-02-17 20:17:23.972 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:17:24.033 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:17:24.034 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => true
2021-02-17 20:17:33.279 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:17:33.340 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:17:33.341 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => true
2021-02-17 20:17:33.783 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:17:33.784 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:17:46.662 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:17:46.723 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:17:46.725 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => true
2021-02-17 20:18:03.784 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:18:03.786 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:18:17.484 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 0
2021-02-17 20:18:17.545 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:18:17.547 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => false
2021-02-17 20:18:33.783 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:18:33.785 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:18:35.177 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:18:35.179 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:18:41.085 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 0 => 8
2021-02-17 20:18:41.212 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:18:41.227 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:18:41.229 INFO ZWAVE: Node 19: value updated: 48-0-Motion false => true
2021-02-17 20:19:03.789 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:19:03.792 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:19:11.947 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 0
2021-02-17 20:19:11.963 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:19:11.964 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => false
2021-02-17 20:19:21.811 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 0 => 8
2021-02-17 20:19:23.219 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:19:23.223 INFO ZWAVE: Node 19: value updated: 48-0-Motion false => true
2021-02-17 20:19:33.789 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:19:33.791 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:19:46.697 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:19:48.119 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:19:48.121 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => true
2021-02-17 20:19:57.327 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:19:57.480 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:19:57.482 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => true
2021-02-17 20:20:04.809 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:20:04.812 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:20:05.776 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:20:06.494 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:20:07.330 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:20:07.447 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:20:07.449 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => true
2021-02-17 20:20:07.718 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:20:07.786 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:20:15.537 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:20:17.344 INFO ZWAVE: Node 58: value updated: 37-0-currentValue true => false
2021-02-17 20:20:17.523 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:20:18.867 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:20:18.869 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => true
2021-02-17 20:20:28.865 INFO ZWAVE: Node 58: value updated: 37-0-currentValue false => false
2021-02-17 20:20:29.101 INFO ZWAVE: Node 58: value updated: 37-0-currentValue false => false
2021-02-17 20:20:30.977 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:20:31.036 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:20:31.038 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => true
2021-02-17 20:20:33.790 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:20:33.793 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:20:39.836 INFO ZWAVE: Node 58: value updated: 37-0-currentValue false => false
2021-02-17 20:20:40.017 INFO ZWAVE: Node 58: value updated: 37-0-currentValue false => false
2021-02-17 20:20:40.156 INFO ZWAVE: Node 58: value updated: 37-0-currentValue false => true
2021-02-17 20:20:51.984 INFO ZWAVE: Node 58: value updated: 37-0-currentValue true => true
2021-02-17 20:21:01.918 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 0
2021-02-17 20:21:03.374 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 0 => 0
2021-02-17 20:21:03.636 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:21:03.638 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => false
2021-02-17 20:21:04.956 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:21:04.958 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:21:14.113 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 0 => 8
2021-02-17 20:21:14.195 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:21:14.197 INFO ZWAVE: Node 19: value updated: 48-0-Motion false => true
2021-02-17 20:21:33.790 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:21:33.792 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:21:39.841 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:21:39.924 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:21:39.925 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => true
2021-02-17 20:22:03.792 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:22:03.796 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:22:12.001 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 0
2021-02-17 20:22:12.169 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:22:12.171 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => false
2021-02-17 20:22:22.470 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 0 => 8
2021-02-17 20:22:22.579 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:22:22.580 INFO ZWAVE: Node 19: value updated: 48-0-Motion false => true
2021-02-17 20:22:33.791 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:22:33.793 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:22:55.006 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 0
2021-02-17 20:22:55.034 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 0 => 0
2021-02-17 20:22:55.146 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:22:55.147 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => false
2021-02-17 20:22:55.227 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 0 => 0
2021-02-17 20:23:03.792 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:23:03.793 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:23:11.989 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 0 => 8
2021-02-17 20:23:13.346 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:23:13.456 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:23:13.458 INFO ZWAVE: Node 19: value updated: 48-0-Motion false => true
2021-02-17 20:23:33.856 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:23:33.857 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:23:35.640 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:23:35.642 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:23:36.465 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:23:36.550 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:23:36.551 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => true
2021-02-17 20:23:44.266 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:23:47.348 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:23:47.352 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => true
2021-02-17 20:23:53.953 INFO ZWAVE: Calling api writeValue with args: [
  {
    nodeId: 58,
    commandClass: 37,
    endpoint: 0,
    property: 'targetValue'
  },
  false,
  [length]: 2
]
2021-02-17 20:23:53.954 INFO ZWAVE: Writing false to 58-37-0-targetValue
2021-02-17 20:23:57.302 INFO ZWAVE: Node 58: value updated: 37-0-currentValue true => false
2021-02-17 20:23:57.304 INFO ZWAVE: Success zwave api call writeValue { success: true, message: 'Success zwave api call', result: undefined }
2021-02-17 20:23:58.101 INFO ZWAVE: Calling api writeValue with args: [
  {
    nodeId: 58,
    commandClass: 37,
    endpoint: 0,
    property: 'targetValue'
  },
  true,
  [length]: 2
]
2021-02-17 20:23:58.101 INFO ZWAVE: Writing true to 58-37-0-targetValue
2021-02-17 20:24:06.840 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:24:06.977 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:24:06.979 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => true
2021-02-17 20:24:08.795 INFO ZWAVE: Node 58: value updated: 37-0-currentValue false => false
2021-02-17 20:24:08.869 INFO ZWAVE: Node 58: value updated: 37-0-currentValue false => true
2021-02-17 20:24:08.871 INFO ZWAVE: Success zwave api call writeValue { success: true, message: 'Success zwave api call', result: undefined }
2021-02-17 20:24:09.011 INFO ZWAVE: Node 58: value updated: 37-0-currentValue true => true
2021-02-17 20:24:20.821 INFO ZWAVE: Node 58: value updated: 37-0-currentValue true => true
2021-02-17 20:24:34.169 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:24:34.172 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:24:37.802 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 0
2021-02-17 20:24:37.991 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:24:37.992 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => false
2021-02-17 20:24:38.239 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 0 => 8
2021-02-17 20:24:38.384 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:24:38.386 INFO ZWAVE: Node 19: value updated: 48-0-Motion false => true
2021-02-17 20:24:50.083 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:24:50.165 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:24:50.167 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => true
2021-02-17 20:25:04.069 INFO ZWAVE: Node 42: value updated: 50-0-value-66049 0 => 0
2021-02-17 20:25:04.070 INFO ZWAVE: Node 42: value updated: 50-0-deltaTime-66049 0 => 0
2021-02-17 20:25:04.225 INFO ZWAVE: Node 19: value updated: 113-0-Home Security-Motion sensor status 8 => 8
2021-02-17 20:25:04.353 INFO ZWAVE: Node 19: metadata updated: 48-0-Motion
2021-02-17 20:25:04.355 INFO ZWAVE: Node 19: value updated: 48-0-Motion true => true

I'm going through it to see if I can see a pattern, but I toggled the light off and one a few times in there, each time with a multi-second delay before it responded.

Another example with debug enabled:
The light was on, so I switched it off from the zwjs2mqtt control panel, waited for it to go off, switched it back on and waited for it to turn on.
Switched light off:
2021-02-17 20:59:14.796 DEBUG SOCKET: Event ZWAVE_API emitted to gb0zDhVFCthpqnF-AAAF
2021-02-17 20:59:14.798 INFO ZWAVE: Calling api writeValue with args: [
  {
    nodeId: 58,
    commandClass: 37,
    endpoint: 0,
    property: 'targetValue'
  },
  false,
  [length]: 2
]
2021-02-17 20:59:14.798 INFO ZWAVE: Writing false to 58-37-0-targetValue

11s delay
2021-02-17 20:59:25.582 INFO ZWAVE: Node 58: value updated: 37-0-currentValue true => false
2021-02-17 20:59:25.584 INFO ZWAVE: Success zwave api call writeValue { success: true, message: 'Success zwave api call', result: undefined }

Switched light on:
2021-02-17 20:59:33.097 DEBUG SOCKET: Event ZWAVE_API emitted to gb0zDhVFCthpqnF-AAAF
2021-02-17 20:59:33.097 INFO ZWAVE: Calling api writeValue with args: [
  {
    nodeId: 58,
    commandClass: 37,
    endpoint: 0,
    property: 'targetValue'
  },
  true,
  [length]: 2
]
2021-02-17 20:59:33.098 INFO ZWAVE: Writing true to 58-37-0-targetValue

4s delay
2021-02-17 20:59:37.340 INFO ZWAVE: Node 58: value updated: 37-0-currentValue false => false
2021-02-17 20:59:37.617 INFO ZWAVE: Node 58: value updated: 37-0-currentValue false => false
2021-02-17 20:59:37.918 INFO ZWAVE: Node 58: value updated: 37-0-currentValue false => true
2021-02-17 20:59:37.919 INFO ZWAVE: Success zwave api call writeValue { success: true, message: 'Success zwave api call', result: undefined }

Okay that does seem like the devices are still being queried and respond extremely slow. While waiting for the response, new commands cannot be sent out.
I suggest you keep an eye out for https://github.com/zwave-js/node-zwave-js/pull/1787, where I'll elimitate the query on restart completely.

I'm certainly looking forward to that.  it doesn't seem like there's any querying going on - just reports from my power monitor (Node 42) and various motion sensors (18 & 19), so it doesn't seem busy and those go through just fine  That's why it seems so curious.  Maybe there is an outstanding command in there somewhere.
In any case, eliminating the query will probably help.

It doesn't seem like there's any querying going on

I could say for sure if you made a zwave-js log instead of the zwavejs2mqtt log :)

I soften see something similar - typically when i pull a new container image it takes ~26 minutes; restarts caused by UI changes typically only take 8mins or so.
When it happens i find the locks are being queried and answering through the whole startup interview process, but certain values / command classes time out.
That after all the other nodes have been interviewed the locks will complete interview but have secure set to unknown.
That i then have to do a subsequent re-interview of the locks (takes like 2 mins for 4 locks) and then all is good.
However i have not yet tested a full reboot to see if the changes i just made https://github.com/zwave-js/node-zwave-js/issues/1764#issuecomment-780865266 fix this or not.
My assumption is that for some reason secure messages are not being passed until after everything else completes, unclear if that is a mesh comms  issues or software.  Digging out todays logs where i have the behavior OP describes.

11:26:59.388 DRIVER   Cache file for homeId 0xdef5ff7b found, attempting to restore the network from
                       cache...
11:26:59.411 DRIVER   Restoring the network from cache failed: SyntaxError: Unexpected end of JSON i
                      nput

Seems your cache breaks, that's why a new interview is performed. Which node IDs are affected by this?

That after all the other nodes have been interviewed the locks will complete interview but have secure set to unknown.

nodes 2,3,4 and 5 - but before you dig in, let me see if i can repro with the new stick firmware and gain and now that my network is healed.  I guess i can delete the cache to invalidate it (i only saw the lock issue when it was 26m+ interviews)

With the new FW and gain settings earlier a complete rebuild took 11 minutes compared to the previous ~26
(i deleted all files except settings and nodes.json to make it do full query).
Also the locks now work as expected and show secure straight off.
Of course this doesn't mean other folks are having same sort of comms issues.

@rccoleman when the locks are doing their 20 minute thing have you sat and watched the zwave js log using tail -f?  (doing nothing else and with log set to debug or silly) i found that super useful in correlating what i see in the UI with what scrolls past - it was how i spotted that for my locks some items would time out and some would not.  Just a suggestion.

Yes, I did.  All I saw were power reports from my Aeotec SmartSwitch 6 and motion sensor reports, appearing to be pretty darn quiet.  I'll try to enable zwjs logs to see if I can see any other traffic going on.

I finally got the zwave-js logs and it looks like it's repeatedly timing out when reading some of the parameters from each of the 3 locks.  This is after it successfully read lots of configuration info from them, so it would be surprising to me if it was a communication issue.  Here's a snippet from one of them, a request for parameter #2 from Node 44, with some other activity interspersed.  This is typical of all three locks for most of the parameters queried in this stage, but not all (some succeed).
02:33:43.002 DRIVER « [Node 044] [REQ] [ApplicationCommand]
                      └─[SecurityCCNonceReport]
                          nonce: 0x051d8a65e3d8eccd
02:33:43.005 SERIAL » 0x011e00132c17988143ac494344e297f2fd017d800536e3d0d95f4c749425e51d  (32 bytes)
02:33:43.006 DRIVER » [Node 044] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      229
                      └─[SecurityCCCommandEncapsulation]
                        │ nonce id: 5
                        └─[ConfigurationCCGet]
                            parameter #: 2
02:33:43.008 SERIAL « [ACK]                                                                   (0x06)
02:33:43.016 SERIAL « 0x0104011301e8                                                       (6 bytes)
02:33:43.016 SERIAL » [ACK]                                                                   (0x06)
02:33:43.016 DRIVER « [RES] [SendData]
                        was sent: true
02:33:43.142 SERIAL « 0x01070013e500000d03                                                 (9 bytes)
02:33:43.142 SERIAL » [ACK]                                                                   (0x06)
02:33:43.143 DRIVER « [REQ] [SendData]
                        callback id:     229
                        transmit status: OK
02:33:49.227 SERIAL « 0x010f00040013097105000000ff0708006a                                (17 bytes)
02:33:49.228 SERIAL » [ACK]                                                                   (0x06)
02:33:49.229 DRIVER « [Node 019] [REQ] [ApplicationCommand]
                      └─[NotificationCCReport]
                          notification type:   Home Security
                          notification status: 255
                          notification state:  Motion detection
02:33:49.230 CNTRLR   [Node 019] [~] [Notification] Home Security[Motion sensor status] [Endpoint 0]
                      : 8 => 8
02:33:49.554 SERIAL « 0x010a00040013043003ff0c26                                          (12 bytes)
02:33:49.555 CNTRLR   [Node 019] [Binary Sensor] Motion: metadata updated               [Endpoint 0]
02:33:49.557 CNTRLR   [Node 019] [~] [Binary Sensor] Motion: true => true               [Endpoint 0]
02:33:49.559 SERIAL » [ACK]                                                                   (0x06)
02:33:49.560 DRIVER « [Node 019] [REQ] [ApplicationCommand]
                      └─[BinarySensorCCReport]
                          type:  Motion
                          value: true
02:33:53.148 SERIAL » 0x010900132d02984025e6d1                                            (11 bytes)
02:33:53.149 DRIVER » [Node 045] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      230
                      └─[SecurityCCNonceGet]
02:33:53.149 CNTRLR   [Node 044] Timed out while waiting for a response from the node
02:33:53.150 CNTRLR « [Node 044] received no value for parameter #2

Sound exactly like I was seeing for last week until this morning. Upgrading controller firmware, increasing gain and doing heal seemed to eliminate the issue. Not saying we have same issue, just sharing,
Get Outlook for iOShttps://aka.ms/o0ukef

From: rccoleman<EMAIL_ADDRESS>Sent: Wednesday, February 17, 2021 6:46:11 PM
To: zwave-js/node-zwave-js<EMAIL_ADDRESS>Cc: scyto<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [zwave-js/node-zwave-js] ~20 minute delay when completing lock interview on server start (#1806)
I finally got the zwave-js logs and it looks like it's repeatedly timing out when reading some of the parameters from each of the 3 locks. This is after it successfully read lots of configuration info from them, so it would be surprising to me if it was a communication issue. Here's a snippet from one of them, a request for parameter #2https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fzwave-js%2Fnode-zwave-js%2Fpull%2F2&data=04|01||acdf0522d71545de4e7a08d8d3b759ed|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637492131728392731|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=5CQCHYS%2F0mD13%2FUdXyjRHnmpBQWn9d90IwMUW6QanM0%3D&reserved=0 from Node 44, with some other activity interspersed. This is typical of all three locks for most of the parameters queried in this stage, but not all (some succeed).
02:33:43.002 DRIVER « [Node 044] [REQ] [ApplicationCommand]
                  └─[SecurityCCNonceReport]

                      nonce: 0x051d8a65e3d8eccd

02:33:43.005 SERIAL » 0x011e00132c17988143ac494344e297f2fd017d800536e3d0d95f4c749425e51d  (32 bytes)
02:33:43.006 DRIVER » [Node 044] [REQ] [SendData]
                  │ transmit options: 0x25

                  │ callback id:      229

                  └─[SecurityCCCommandEncapsulation]

                    │ nonce id: 5

                    └─[ConfigurationCCGet]

                        parameter #: 2

02:33:43.008 SERIAL « [ACK]                                                                   (0x06)
02:33:43.016 SERIAL « 0x0104011301e8                                                       (6 bytes)
02:33:43.016 SERIAL » [ACK]                                                                   (0x06)
02:33:43.016 DRIVER « [RES] [SendData]
                    was sent: true

02:33:43.142 SERIAL « 0x01070013e500000d03                                                 (9 bytes)
02:33:43.142 SERIAL » [ACK]                                                                   (0x06)
02:33:43.143 DRIVER « [REQ] [SendData]
                    callback id:     229

                    transmit status: OK

02:33:49.227 SERIAL « 0x010f00040013097105000000ff0708006a                                (17 bytes)
02:33:49.228 SERIAL » [ACK]                                                                   (0x06)
02:33:49.229 DRIVER « [Node 019] [REQ] [ApplicationCommand]
                  └─[NotificationCCReport]

                      notification type:   Home Security

                      notification status: 255

                      notification state:  Motion detection

02:33:49.230 CNTRLR   [Node 019] [~] [Notification] Home Security[Motion sensor status] [Endpoint 0]
                  : 8 => 8

02:33:49.554 SERIAL « 0x010a00040013043003ff0c26                                          (12 bytes)
02:33:49.555 CNTRLR   [Node 019] [Binary Sensor] Motion: metadata updated               [Endpoint 0]
02:33:49.557 CNTRLR   [Node 019] [~] [Binary Sensor] Motion: true => true               [Endpoint 0]
02:33:49.559 SERIAL » [ACK]                                                                   (0x06)
02:33:49.560 DRIVER « [Node 019] [REQ] [ApplicationCommand]
                  └─[BinarySensorCCReport]

                      type:  Motion

                      value: true

02:33:53.148 SERIAL » 0x010900132d02984025e6d1                                            (11 bytes)
02:33:53.149 DRIVER » [Node 045] [REQ] [SendData]
                  │ transmit options: 0x25

                  │ callback id:      230

                  └─[SecurityCCNonceGet]

02:33:53.149 CNTRLR   [Node 044] Timed out while waiting for a response from the node
02:33:53.150 CNTRLR « [Node 044] received no value for parameter #2
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fzwave-js%2Fnode-zwave-js%2Fissues%2F1806%23issuecomment-781004290&data=04|01||acdf0522d71545de4e7a08d8d3b759ed|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637492131728402727|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=AMx27M84tr5cFZwg5Lx0deOG0dfSYVkaMcnF0ReWl74%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACWXVXD2VSH22UC4PASVP4TS7R5PHANCNFSM4XY3UBNQ&data=04|01||acdf0522d71545de4e7a08d8d3b759ed|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637492131728412720|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Gnsf%2FyqRVqeyr98QZb1xP4hdXP3Y2Uq3Dmzr7wpTCv4%3D&reserved=0.

I pulled the branch from https://github.com/zwave-js/node-zwave-js/pull/1787 and startup is quite speedy.  My three locks come up with blank info and an Unknown status, but all other nodes come up with proper info and show "Complete" almost immediately.  If I hit "Refresh Values" for each of the locks, they also populate and their entities show up in HA.  Once that's done, everything works instantly!

I finally got the zwave-js logs and it looks like it's repeatedly timing out when reading some of the parameters from each of the 3 locks. This is after it successfully read lots of configuration info from them, so it would be surprising to me if it was a communication issue.

That could very well be true. Could you coordinate with @blhoward2 to check which config parameters are defined and shouldn't be there?

I'm pretty sure that the problem is that usercode type (owner, guest, worker) parameters that aren't set time out during the query.  All 3 locks have the first type set to "owner" (1), and the rest of the 29 parameters for each lock time out because I haven't set them.  The curious bit is that one of my locks had usercode #2 set when I bought it and I've since blanked it out and set that slot to "available."  In the zwjs logs, it times out on the usercode type for that slot just like the the other locks, but the zwjs2mqtt UI displays that parameter as "Owner" (1).  I suspect that it's just displaying a cached value, but it was unexpected.
So, it seems like these parameters are all valid, but each timeout contributes ~30s of wasted time with associated retries.  Luckily, it queries all of the locks concurrently, but it still takes nearly 20mins of timed out parameter queries before it moves on to the associations (log is above, timestamps are between ~02:33:xx and ~02:51:55).
The only mitigation that I can see is that each slot is marked with "Available", "Enabled", or "Disabled" in the UserCodeCC entry, and entries that are marked "Available" could be assumed to have no associated "type" config param.
Example:
02:28:00.779 DRIVER « [Node 064] [REQ] [ApplicationCommand]
                      └─[SecurityCCCommandEncapsulation]
                        │ sequenced: false
                        └─[UserCodeCCReport]
                            user id:   3
                            id status: Available
                            user code:

02:34:40.585 DRIVER » [Node 064] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      239
                      └─[SecurityCCCommandEncapsulation]
                        │ nonce id: 58
                        └─[ConfigurationCCGet]
                            parameter #: 3

02:34:50.727 CNTRLR   [Node 064] Timed out while waiting for a response from the node
02:34:50.728 CNTRLR « [Node 064] received no value for parameter #3

If that's not a universal solution across all locks, maybe it's enough to just skip the initial query as in https://github.com/zwave-js/node-zwave-js/pull/1787.

If you set a user code for those slots, does it then work correctly on those slots while the code is set? If so I'm not sure what do about that...Thoughts @AlCalzone?

I'm testing that now.

Also, what do you mean by set them as Available? Do you not have an option drop-down that only has owner, guest, vacation?

The combination between configuration and user code CC is something specific to this device and no generic rule I can implement in the driver.
The next major version will stop requerying the codes on each reboot so ideally you only have to endure the delay once.

Also, what do you mean by set them as Available? Do you not have an option drop-down that only has owner, guest, vacation?

Here's an example of a usercode type parameter that's set and one that isn't:

And usercodes with "Enabled" and "Available":

In any case, it sounds like it's not a universal rule.

Ah, gotcha. That's under values not configuration.

Correct, it's a correlation between the UserCodeCC values and the config parameters.

as a note i moved back from current public dev container to one built on zwavejs branch master and zwavejs2mqtt branch rgbw_switch and my slow  28+ minute issue came back and is identical to one described here where it just time outs on user codes
what i don't understand is why it appears to not be present as an issue in the public dev container.


KeyError: 'away' on box scores

This may very well be pebkac but when I try to pull any box scores I get a KeyError. I can pull other league settings without issue but it seems to break at this point.
Something like the following will throw the following error:
box_scores = league.box_scores()
print (box_scores)
Traceback (most recent call last):   File "test.py", line 9, in <module>     box_scores = league.box_scores(week=3)   File "/Users/john.peterson/Documents/FF/venv/lib/python3.7/site-packages/ff_espn_api/league.py", line 313, in box_scores     box_data = [BoxScore(matchup) for matchup in schedule]   File "/Users/john.peterson/Documents/FF/venv/lib/python3.7/site-packages/ff_espn_api/league.py", line 313, in <listcomp>     box_data = [BoxScore(matchup) for matchup in schedule]   File "/Users/john.peterson/Documents/FF/venv/lib/python3.7/site-packages/ff_espn_api/box_score.py", line 8, in __init__     self.away_team = data['away']['teamId'] KeyError: 'away'
Is there a way to just pull the league data object to parse and see if it is being returned in a different structure? Fwiw its a private league.
Thank you for putting this together, its wonderful.

At the moment there is no way to see the box_score data without calling the ESPN API in your own browser. I think that I should add a feature to have a “logger mode” that would print out all of the json returned from API calls. This would make it really easy to debug.
For the error your running into that’s interesting that there isn’t a away team. Do you have bye weeks in your league? Also could you try passing box_scores(week=1) or week=2, to see if that gives you a error.

I forgot to mention that I had tried with week= as well, but it yields the same KeyError.
We do have a bye week because we ended up with an odd number of players.
Question: it shouldn't matter if I am the league owner or not to pull the data correct?

Okay that is good to know about the bye week! It’s hard knowing what ESPN API does with different league settings. I will also try to look at it later and see if I can come up with a solution.

I ran into a similar issue yesterday while trying to pull all team scores from the last 7 years of data in the league I participate in. I was iterating over years and weeks pulling scoreboard and box_score data. In my case it was requests for playoff weeks failing and as a result, the matchup object was failing to init the dict.
I independently went with a fail->log->continue solution similar to what @johnmikep did. I think it's a reasonable approach since you can go back and look at the gaps to figure out why the request may have come up with nothing.

Yeah the biggest help for debugging is the json that is returned from the ESPN API. The continue could get a little tricky as some of the calls rely on that data later down for processing.
Where did it fail for playoffs? I know playoffs can be a little tricky as matchup period and scoring period can differ with same matchup span multiple scoring periods.

Box score is fixed, but this issue still remains with scoreboard


x/sys/windows: missing process working size system calls

What version of Go are you using (go version)?

$ go version
go version go1.14.3 linux/amd64

Does this issue reproduce with the latest release?
Yes. The currently exposed system calls can be seen at https://pkg.go.dev/golang.org/x/sys/windows?tab=doc
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/awn/.cache/go-build"
GOENV="/home/awn/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/awn/projects/src/go"
GOPRIVATE=""
GOPROXY="direct"
GOROOT="/usr/lib/golang"
GOSUMDB="off"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/golang/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/awn/projects/src/sys/go.mod"
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-build786429694=/tmp/go-build -gno-record-gcc-switches"

What did you do?
When using VirtualLock (which is available in the standard library) on Windows sometimes this fails due to the process's limit being reached. See https://github.com/awnumar/memcall/issues/3 for an example.
The workaround for this in the docs is to call SetProcessWorkingSetSize.
What did you expect to see?
The SetProcessWorkingSetSize and related system calls exposed in the x/sys/windows API.
What did you see instead?
They are not defined.

/cc @alexbrainman @bradfitz per owners.

Thanks for sending a PR that'll fix this issue @awnumar.
It's expected that this issue will need to transition to the NeedsFix state before you should proceed with the change. There's more information here.


Do we need to remove the silence segments before training the speaker verification ECAPA-TDNN?

I am trying to fine tune the ECAPA-TDNN on my speaker recognition dataset, do I need to remove the silence segments (doing VAD) before training? Will it affects the final result?

Is there silence in your test dataset as well? If so, what is the percentage of silence? I have trained ECAPA-TDN before on the instrument recognition task. when I trained the data after VAD, the results were very different. For my task, there was a lot of silence, so VAD was not appropriate for me.

@vic4code, If there is a lot of silence, I think adding a VAD should be appropriate, no?
As for the ECAPA-TDNN recipe, I don't see any step where we remove silences. We basically train the system using chunks of 3 seconds randomly sampled within each sentence. The assumption here is that the signal will mainly contain speech. I think small portions of noise are anyway tolerated.

@mravanelli, perhaps the data we use is a little different from the common speech data. I conducted the ECAPA model on the Nsynth dataset containing instrument sounds with a duration of 4 seconds for all data. However, about 10-15 % of the files start with a transient pulse of sound of about 0.1 seconds (silent in the left 3.9 secs). They are the sounds you get when you play a stringed instrument with the Pizzico or palm muting playing technique. So if I do VAD before training, there is a big mismatch that the model mainly learns to recognize the instrument sound without silence resulting in a poor F1-score.


Open In Terminal does not work

VSCode Version: Code 1.15.1 (41abd21afdf7424c89319ee7cb0445cc6f376959, 2017-08-16T18:05:38.342Z)
OS Version: Windows_NT ia32 6.1.7601
Extensions:

Extension
Author (truncated)
Version

debugger-for-chrome
msj
3.1.8

Steps to Reproduce:

Reproduces without extensions: Yes/No

Please provide more information:

How are you opening the terminal?
What happens?
Are there errors in the devtools console? (Help > Toggle Developer Tools)


Scavenger can't locate token

When running the scavenger I get the following output
Beginning quick scavenge
Beginning run
Locating Discord token

Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
   at EmoteScavenger.Program.Main(String[] args) in C:\Users\Mateusz\Documents\Visual Studio 2017\Projects\EmoteScavenger\EmoteScavenger\Program.cs:line 26

I tried to delete the content of the "%appdata%\discord\Local Storage" folder and restart discord but it still didn't work.
Additional note: I have Discord Stable, PTB and Canary installed

If you delete local storage, you're deleting the token.

I deleted local storage, reinstalled Discord and logged back in. The folder reappeared with the token inside.
The token was there before I removed the folder and after it reappeared but the scavenger failed to recognize it. Both times I received the same error message.

What Windows version

Windows 10, x64, build 16299

And what's the scavenger version?

I used v1.0.2 from the release tab.

Strange, because the stack trace points to a line where no nullref can occur (static call). Are you absolutely sure it's 1.0.2?

I just tried redownloading the 1.0.2 build and got the same error message. Both commits to Program.cs have the exact same line 26 so I would likely get the same error for every build.

I have the same problem


Multiple POST from SagePay-Notifier and error 5006

Hi,
I keep having the error 5006 (Unable to redirect to Vendor's web site. The Vendor failed to provide a RedirectionURL.) while all the payments are actually working (my payment are confirmed and I get the following status message: 0000 : The Authorisation was Successful.)
My website is WordPress, I use (I tried returnUrl and/or both):
'notifyUrl' => site_url('/payment-confirm/')
The order complete page (simplified):
`$gateway = OmniPay::create('SagePay\Server');
$gateway->setVendor('myvendor');
$gateway->setTestMode(true);
$requestMessage = $gateway->completePurchase([
    'transactionReference' => $transaction_ref,
]);

try {
    $responseMessage = $requestMessage->send();
} catch(\Exception $e) {
    $requestMessage = $gateway->completePurchase([]);
    $responseMessage = new ServerCompleteAuthorizeResponse($requestMessage, []);
    $responseMessage->invalid(site_url('/order-completed/?error=true'), $e->getMessage());
}

if ($responseMessage->isSuccessful()) {
    // some stuff
}

$responseMessage->confirm(site_url('/order-completed/?pr=' . $payment_id));`

I can see as well that the SagePay-Notifier is doing multiple POST requests:

Thanks a lot!!
Kevin

Is this happening with the sage pay test server, or live?
I ask because we're seeing an issue with 3D Secure posting to our 3d secure callback URL twice in succession, resulting in the transaction completing successfully, in the background, but the user only seeing the 'failed transaction' message resulting from the second post. I believe this may be an issue with 3D Secure.

Edit: This is happening on the testing environment and 3D secure if OFF, should I turn it on?

Okay I found my error. Some HTML was printed in my "payment-confirm" page, my bad!

Errors in the confirm page is so hard to debug, because it is only SagePay that ever sees it. Glad you have a solution now.


Fix GLX glue trying to use NULL display

i.e. when a unix platform has a non-GLX context: usually EGL-Wayland, but also might be offscreen or maybe EGL-X11.
This patch fixes #401 (well, it doesn't introduce EGL glue, but people just want FreeCAD running on Wayland).

Err:6 http://azure.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libegl-mesa0 amd64 19.2.8-0ubuntu0~18.04.3 404  Not Found [IP: <IP_ADDRESS> 80]

hmm looks like your CI needs to apt-get update before upgrade/install

Thanks for notifying us about the issue and for providing the fix. It is very much appreciated.

It might be nice to have a release which includes this bugfix, say 4.0.1 if appropriate.


Video

Kyverno review

Thanks @vfarcic! Love the detailed review and feedback.
What's the best way to follow-up on some of the items you noted in the video? Are you in on the Kubernetes slack?

I am in the k8s Slack. My user is vfarcic.


Improve Profile(Instance)List documentation: bigger picture/examples

From the already available descriptions of the profileList and profileInstanceList it was kinda hard to grasp for me how the profiles are related to the other parts of the code. For the overall understanding it would be helpful if there would be at least a short explanation of the bigger picture in the Concept of Profile/ProfileInstanceList (or own page), even if detailed descriptions would be included later on in other documents.
E.g. in Creating a ProfileInstanceList under New Profiles section there is the sentence:

Be aware that you just need to describe the structuring of configuration information. Application data shall be encapsulated by the application.

For someone new to the concept I find it hard to really understand what this sentence means in terms of the specification.

As I did not understand where the profile information comes into play, I had a look at the OAS yaml and e.g. found the following code snippet (markdown breaks the fomattings):

/core-model-1-4:control-construct/profile-collection/profile={uuid}/integer-profile-1-0:integer-profile-pac/integer-profile-capability/integer-name:
parameters:
- in: path
name: uuid
required: true
schema:
type: string
pattern: '-\d+-\d+-\d+-integer-p-\d{4}$'
example: '*-0-0-1-integer-p-0000'

So as far as I understand it, I'm having the path/url which has the path parameter {uuid} and I would then need to define an integer profile instance inside the profileInstanceList. I still had the old profiles.yaml in my repo, where I found the following profileInstance:

profile-name: IntegerProfile
uuid: integer-p-0000
integer-name: maximumNumberOfEntries
unit: records
minimum: 0
maximum: 17
configured-value: 8

Which would then mean if I see the pattern above, that my integer-p-0000 matches and the uuid could be a number between 0 and 17.
Of course I could add additional IntegerProfiles, e.g. integer-p-0001 with min=20 and max=120; then the uuid could be either between 0-17 or 20-120.

Maybe something like that could be given as an example and also together with an example of the application data that's encapsulated and not related to the profiles.

Purpose of Profiles and Examples have been described in Concept of Profiles.
Did you find it?

Details on the OAS and the CONFIGfile will be described in separate documents.
Formulated a little more text in the Purpose section:
Purpose of Profiles
Profiles are for holding configuration information.
Most the configuration information is for documenting traffic relationships (e.g. HttpServer, OperationClient).
Profiles are for configuration information that is not directly related to an individual interface.
Contained information could relate e.g.

to all or a group of interfaces
or to a process or calculation that is executed inside the application.

Examples:

If there would be an application, which is documenting records about some type of events, it would probably make sense to make the number of events, which are to be recorded before deleting the eldest record, configurable.
If there would be an application for calculating some value from input from the network, there could be one or several static parameters in that formular. Potentially, it would make sense to make these parameters available for configuration during runtime of the application.

Configuration information is not to be mixed with application data.
While data is entering the application through body or response body of services, configuration information is read and set through GET and PUT requests in the OaM section of the REST API.
Moreover structuring and storing of application data is implementation specific (could be e.g. a database), while structuring of configuration information is subject to specification and storing is happening in the CONFIGfile.


Use of args.multi_frame_attention

Hi @timmeinhardt  , thanks so much for this great work!
While trying to reproduce the results for MOTS20, I noticed some differences between your DeformableDETR and the DETR implementations.
Could you explain the use of args.multi_frame_attention in the adjusted DeformableDETR? I'm wondering why it is not used in the DETR based model for mask tracking.
Is multi frame attention not necessary to utilise track queries in the model? I read section 4.2 in the paper, but I'm still a bit confused.

We provide the MOTS20 results for the old model cause the deformable attention seemed to perform worse for segmentation. Multi-frame and multi-scale trainings were not part of the old model. However, there is no reason why multi-frame could not work for segmentation.

The track_attention is a legacy parameter and was not used during any of the trainings.


apps under /examples don't seem to work

Hiya! I was trying to get the apps under /examples to run, but I suspect they've not been updated to the newer APIs? As an example, in /examples/automerge-repo-demo-counter, there's a type error here :

Indeed, there's no url property on the object being returned, so the app never loads data, and never renders.
(Additionally, packages/automerge-repo-storage-nodefs/package.json tries to install rimraf@5, but only works with rimraf@4)
Happy to help debug more if needed!

Ah -- I think this is an error caused by my local yarn workspace config. If it doesn't see the URL property it's probably resolving the wrong (old) version of Automerge-Repo. I'll see if I can recreate this bug by checking out the repo from scratch but I suspect you can fix it by bumping the dependencies forward to "^1.0.0" in the package.json (if nobody's done this already.)

I went down the rabbit hold and made a PR https://github.com/automerge/automerge-repo/pull/173 that should fix it!

Ah geez, I got up this morning and sat down to fix it without seeing your PR @threepointone.

It looks like there are some good improvements to the overall structure in your PR, so I'll try and pull some of those bits in. Thanks for your efforts!


Grafana cannot connect to datasource over servicename, only IP.

heapster-grafana version: 4.0.2
kube-dns version: 1.14.4
OS: Centos 7.3
Kubernetes version: 1.5.2

I am having an issue where my grafana pod can only connect to the influxdb pod when it is using the service IP.
It would be assumed that kube-dns is not working, but when opening a shell on the grafana pod (with docker exec) it is able to resolve the hostname:
/ # ping monitoring-influxdb.kube-system.svc.cluster.local
PING monitoring-influxdb.kube-system.svc.cluster.local (<IP_ADDRESS>): 56 data bytes

So IP resolving works (for some reason I need the entire FQDN but that's another issue...)
But when entering this hostname into the datasource configuration I simply get
"Unknown error: InfluxDB Error: undefined". When entering the IP, it works.
What's going on here? I would prefer not to set the IP in the influxdb service staticly.

I have same problem.
ENV:
heapster-grafana version: 4.4.1
kubeadm: 1.7.0
OS: CentOS 7.2.1511

@piosz have you seen anything like this before?

even worst, if one tries to define the grafana datasource to the prometheus service (under ...srv.cluster.local) (or even the ClusterIP), it fails.

This sounds very similar to what is talked about here: https://github.com/kubernetes/kubernetes/issues/45790. I'm seeing the same problem and a workaround is to configure Grafana to contact InfluxDB via '<IP_ADDRESS>' instead of the service hostname.
I have not been able to find a way to solve it properly for now.


Cleanup function for keeping X latest components

This is a rough implementation of a new clenaup function which will
look at AMIs with the name structure -
and only keep the X newest for each component.
Since this is a rough implementation, it might still need some
modifications to fit your needs better, but should definetly work.
It just needs to be added under the "mark-for-cleanup" case in the
main cloudsweeper package.
NOTE: This is safe to merge, as it isn't added to run, but you will probably want to develop this further to fit your needs. In particular, take a look at the // TODO: Time layout, as you will need to add a parsing layout that follows what you actually use in your AWS account.

atonderski will make further modifications after merge.  Thank you hsson!


Payment infrastructure (OCC-49)

Payment services provide a method to charge the customer, and a flag to switch to simulation mode.
Jira issue

Dropping here the link to the PaymentGateway module we made for good old Orchard:
https://github.com/LaserSrl/Laser.Orchard.Platform/tree/master/src/Modules/Laser.Orchard.PaymentGateway
In the same repo there are a few implementations. THe one that's more relevant here is probably Braintree. There are others for a couple services specific to Italian banks.
In the NwazetIntegration module there there should be stuff that allows implementations of the PaymentGateways to work with Nwazet. This was a thing we did to avoid rewrites in Nwazet that would make it dependent on our modules.

This is of interest both as an upcoming W3C standard to be aware of, but also as a design blueprint.
https://www.w3.org/TR/payment-request/

Isn't this done, @sarahelsaig?

Yeah. We have the dummy provider instead of the simulation mode, but it's close enough.


Add the endpoint for battery level of Nuimo

Implement the endpoint:
Example:
http://<IP_ADDRESS>:6543/-/nuimos/{nuimo MAC address}/battery

@kelada What would be the expected response for this call?

Response:
{battery_level: integer [-1 100] }

-1 represents that the device is off

This is related to:

https://github.com/getsenic/senic-hub/pull/327
https://github.com/getsenic/senic-hub/pull/311/commits/ca60d6df833050c6b921b164def8d46d3c2f7b8b

which resulted in a bug when tested with multiple Nuimos.
Trying anew

Starter implementation
https://github.com/TheMeaningfulEngineer/senic-hub/tree/nuimo-battery-endpoint
Still need to implement the checking if Nuimo is on when the request is recieved.

Implemented in PR #338 . Closing.


A flex column nested inside a flex row results in unexpected layout calculation

Bevy version
0.6.1
Operating system & version
Windows 11
What you did
I compiled and ran this code (when a valid font)
use bevy::prelude::*;

fn main() {
    App::new()
        .add_plugins(DefaultPlugins)
        .add_startup_system(setup_ui)
        .run();
}

fn setup_ui(mut c: Commands, assets: Res<AssetServer>) {
    c.spawn_bundle(UiCameraBundle::default());

    let style = TextStyle {
        font: assets.load("Karla-VariableFont_wght.ttf"),
        font_size: 50.0,
        ..Default::default()
    };

    let label = |s: &'static str| TextBundle {
        text: Text::with_section(s, style.clone(), Default::default()),
        ..Default::default()
    };

    fn row() -> NodeBundle {
        NodeBundle {
            style: Style {
                flex_direction: FlexDirection::Row,
                ..Default::default()
            },
            color: Color::NONE.into(),
            ..Default::default()
        }
    }

    fn column() -> NodeBundle {
        NodeBundle {
            style: Style {
                flex_direction: FlexDirection::Column,
                ..Default::default()
            },
            color: Color::NONE.into(),
            ..Default::default()
        }
    };

    c.spawn_bundle(row()).with_children(|c| {
        c.spawn_bundle(label("-"));

        c.spawn_bundle(column()).with_children(|c| {
            c.spawn_bundle(label("/"));
            c.spawn_bundle(label("\\"));
        });

        c.spawn_bundle(label("|"));
    });
}

What you expected to happen
I expected a vertically reversed version of this html

-

/

\

|

which looks like this

What actually happened
This is what bevy renders

The row flex was ignored, and the column goes off the screen. Elements after the column are also missing.
Additional information
If I remove the children of the column, but keep the column itself there the row works fine. It looks like the column having content seems to break the row calculation.

Do you reproduce that issue with ImageBundle nodes with a specified size instead of the TextBundle?

I added an example using ImageBundle, however I'm not quite sure how to specify the exact size, I think Node has that but I'm uncertain.
use bevy::prelude::*;

fn main() {
    App::new()
        .add_plugins(DefaultPlugins)
        .add_startup_system(setup_ui)
        .run();
}

fn setup_ui(mut c: Commands, assets: Res<AssetServer>) {
    c.spawn_bundle(UiCameraBundle::default());

    let image = |s: &'static str| ImageBundle {
        image: assets.load(s).into(),
        node: Node {
            size: Vec2::new(10.0, 10.0),
            ..Default::default()
        },
        ..Default::default()
    };

    fn row() -> NodeBundle {
        NodeBundle {
            style: Style {
                flex_direction: FlexDirection::Row,
                ..Default::default()
            },
            color: Color::NONE.into(),
            ..Default::default()
        }
    }

    fn column() -> NodeBundle {
        NodeBundle {
            style: Style {
                flex_direction: FlexDirection::Column,
                ..Default::default()
            },
            color: Color::NONE.into(),
            ..Default::default()
        }
    }

    c.spawn_bundle(row()).with_children(|c| {
        c.spawn_bundle(image("icons/outline_north_east_black_24dp.png"));

        c.spawn_bundle(column()).with_children(|c| {
            c.spawn_bundle(image("icons/outline_north_west_black_24dp.png"));
            c.spawn_bundle(image("icons/outline_south_east_black_24dp.png"));
        });

        c.spawn_bundle(image("icons/outline_south_west_black_24dp.png"));
    });
}

This does result in a different behavior though, it appears the row is now invisible.

I tried this with all of the children directly under the row,

    c.spawn_bundle(row()).with_children(|c| {
        c.spawn_bundle(image("icons/outline_north_east_black_24dp.png"));
        c.spawn_bundle(image("icons/outline_north_west_black_24dp.png"));
        c.spawn_bundle(image("icons/outline_south_east_black_24dp.png"));
        c.spawn_bundle(image("icons/outline_south_west_black_24dp.png"));

        c.spawn_bundle(column()).with_children(|c| {});

    });

and this result was squished, but did render all 4.

It appears this happens specifically when the inner text element has a height of Auto or Unknown.

I suspect the answer is yes, but are you able to reproduce the issue using current main?


feat: storage disaster recovery (#619)

Cherry-pick https://github.com/cdklabs/construct-hub/pull/619 to main.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

We've decided to abandon this at this point due to high risk.


Document features

add documents include screen captures (GIF animation) on each feature

I think We don't need it now. I will re-open when We will need it.


fix names of http-equiv and accept-charset attributes

Fixes #260

Yeah not many native attributes have dashes (outside of SVG) but those do and should reflect that. Thank you.


Automatically obtain ENDF files from the web

Fixes #1

It seems you forgot to commit a data/endf_sources.json file,

It should be there, at cstool/data/endf_sources.json:

If it doesn't work, maybe reinstalling the package (pip install -e -U .) fixes it?

The file is there, my bad. I was looking in the wrong data/ folder (not the one in cstool/.
When I try to run this branch, I get an error in the json module. Full stack trace is:
  File "examples/cs.py", line 154, in <module>
    shells = ionization_shells(s)
  File "/xxx/cstool/ionization.py", line 76, in ionization_shells
    data = _ionization_shells(element.Z)
  File "/xxx/cstool/ionization.py", line 67, in _ionization_shells
    sources = obtain_endf_files()
  File "/xxx/cstool/ionization.py", line 42, in obtain_endf_files
    sources = json.loads(resource_string(__name__, 'data/endf_sources.json'))
  File "/usr/lib/python3.5/json/__init__.py", line 312, in loads
    s.__class__.__name__))
TypeError: the JSON object must be str, not 'bytes'

When I could not find the file myself, I figured that must have been what caused it, but I was wrong -- after moving the file I get a FileNotFoundError. But something else is definitely still wrong.
I got this error after a completely clean installation, in a fresh virtual python environment.

Strange, I didn't have that. Maybe because I run a different Python version.
Does ce86720 fix it for you?

Yeah, that seems to fix it. Strange that this is necessary though.
The one further comment I have is that the obtain_endf_files() function does not check if the connection to the server succeeds when downloading. If the user has no active internet connection, or the server is down, file removed or whatever, the program will simply crash. A nice error message before crashing would be more user-friendly and easier to debug.
After that, I think it's OK to merge this.

Thanks for the feedback!


tracker.rs doesn't log the slow request if it exceeds the deadline

Bug Report
If a coprocessor task takes longer than 1 minute, it can't be logged by tracker slowlog.
https://github.com/tikv/tikv/blob/master/src/coprocessor/tracker.rs#L256
What did you expect?
We want to get more information from the slow log to see why it take more than 1 minute.

Good catch. We will improve it.

Good catch. We will improve it.

Can I try to fix it?

@JayiceZ Of course.

/type bug
/severity Moderate
/assign youjiali1995

Per https://github.com/tikv/tikv/pull/12154#issuecomment-1067610392, personally I think it not a good idea to simply log the request as long as the request exceeds the deadline. This may cause log explosion under heavy load.
Instead, I'm thinking about returning enough information to TiDB and let TiDB aggregate and log the slow query. For example, how many requests are dropped due to exceeding the deadline, how much cpu time and i/o is wasted on these aborted executions.

Agreed on the aggregated summary to avoid the log flooding. However, why not do the aggregation in-place on the current  TiKV node?  There are basically multiple advantages doing it on TiKV node 1) saving a networking communications between TiKV and TiDB 2) in case there is no TiDB, user just run TiKV  3) in case a single node is busy while the others are idle because of data skew/hotspot,  per TiKV node level aggregation should be more useful.

A node level aggregation can be done through the metrics. We will try improving the Grafana dashboards.
To aggregate query-level information, we have to return these statistics to TiDB, because a TiDB query consists of multiple coprocessor requests.
The tracker only works for the tidb_query coprocessor. It's not useful for KV users. Anyway, it is better to provide the similar statistics in KV interfaces.


NO-ISSUE: Create doc about async service tasks

Also fixed a bug that deleting a device should trigger the task that updates device ownership (important in case there are overlapping selectors, so the Fleet's Conditions can be updated if fixed).

I'd rather not invest in tests and code for this file because it will be deleted once we use a real task system.

maybe we should stop doing self-merges? :-)

I'd rather not invest in tests and code for this file because it will be deleted once we use a real task system.

makes sense


[Misdetection] Eicar.txt file misdetected as text/vbscript

Eicar.txt is misdetected as text/vbscript instead of text/plain when using python-v0.5.0 or python-v0.5.1 release. Using the demo on https://google.github.io/magika, the detection is correct as it is text/plain.
The content of the file can be reached on this link: https://secure.eicar.org/eicar.com.txt
Could you please help to fix this so the detection can be correct from a Python script?
Thank you in advance!

Hi @reyammer,
Are there any progress regarding this issue? Were you be able to reproduce it and investigate?
Thank you in advance!


Allow adjusting or removing redirect delay

It would be nice to have the option to skip the redirect delay.
It would likely be necessary to add a way to configure this setting from the main page to prevent users from locking in this setting and not being able to disable it anymore.
Additionally, when adding settings on the main page, that could be an opportunity to add configuring the home instance there.

It's done, when set to 0, it entirely skips rendering the HTML page and does a http redirect directly. I don't have much time, so the UX is suboptimal, but it's not something people will interact with often.


Refactor the LogToParquet class

The current class is quite bleh, we need to incorporate a better approach to reading the log data in and converting to a parquet format.

We have a much better solution with this PR: https://github.com/SuperCowPowers/bat/pull/101


Failed while training dataset

Model Builder Version: 3.0.0
Visual Studion Version: Visual Studio 2022
Bug description
resnet takes so much time to install so I installed it manually and now I get this:

Steps to Reproduce

Scenario - Image Classification
Environment - GPU

Data - Dataset from kaggle
Train

Expected Experience
Find best solution
Actual Experience
Failed with error: logs.txt
Additional Context

Solved.
Update ModelBuilder to the latest version and it should works fine


bee.yaml in Windows AMD64 Release has "bee-mainnet: false"

Summary
If you look inside the released bee-windows-amd64.zip from the link below you will find a bee.yaml file that contains the lines:

triggers connection to main network
bee-mainnet: false

This is incorrect as it should be:

mainnet: false

Steps to reproduce
Just download the .ZIP and look inside for the bee.yaml.  The last 2 lines of that file.
Expected behavior
It should not be "bee-mainnet:", but just "mainnet:"
Actual behavior
Bee node operators that start from this file and uncomment this line and change the value to true are unable to operate on the xDai/mainnet.
https://github.com/ethersphere/bee/releases
https://github.com/ethersphere/bee/releases/download/v1.0.0/bee-windows-amd64.zip

Looks like this might be fixed by #2186

Should be fixed, so I'm closing this one.


Uart API changes v3

Changes since v2

Added suggestions pointed by @barbieri

Note: I will add the common docs later.

#1910


fixed issue #23

The EZLoadingActivity will now show in the center of modally presented view controllers.

It seems like that the file in the master branch is a little bit different from the file I installed. But I think it doesn't affect this, though (not tested). And I have tested, with my version of this file, that it does not affect view controllers which are not presented modally.


use core::mem::MaybeUninit; drop min-const-fn and smaller-atomics features

closes #69
this contains breaking changes (see CHANGELOG) and bumps the crate version to 0.5.0. We'll make a pre-release (i.e. v0.5.0-alpha.1) after rust-lang/rust#60445 lands and a proper release when that PR makes into the stable channel.

bors r+

bors r+


Enhancements for terminal window

Issue on page: https://github.com/opentelekomcloud-docs/elastic-cloud-server/blob/main/umn/source/faqs/file_upload_data_transfer/how_can_i_use_sftp_to_transfer_files_between_a_local_linux_computer_and_a_linux_ecs.rst
Code comments seems to be default italic

Auto coloring works only sometimes good
Issue on page: https://github.com/opentelekomcloud-docs/elastic-cloud-server/blob/main/umn/source/faqs/disk_management/how_can_i_adjust_system_disk_partitions.rst

test.txt

this is default visualization of comments in any code editors. So from our POV not a problem but improvement/feature
We might try out changing pre-class="screen" to format type console


Inconsistent behavior between platforms when RedirectStandardOut is used and delayed data is received.

Steps to reproduce
This behavior was originally observed while doing batch copies of blob containers with the Az CLI, but a simple contrived example is below.  ReproduceIssue.ps1 is a minimal script that fires off a batch of tasks defined in DelayedStdOut.ps1 that do not receive data to standard out until after the parent process has exited.  If I run ReproduceIssue.ps1 in pwsh on Windows, there is no exception and the late output is not redirected to the text file.  When it is run on a Linux container, there is an unhandled exception.
ReproduceIssue.ps1
$StdOutDelaySeconds = 5,
$RequestBatch = 5
@(1 .. $RequestBatch) | % {
    $processParameters = @{
        FilePath = 'pwsh'
        ArgumentList = @( '-file', "DelayedStdOut.ps1 $StdOutDelaySeconds")
        PassThru = $true
        RedirectStandardOut = Join-Path -Path (Get-Location) -ChildPath "$([System.Guid]::NewGuid().Guid).out.log"
    }
    Start-Process @processParameters
}
Start-Sleep (2*$StdOutDelaySeconds)

DelayedStdOut.ps1
param(
    $StdOutDelaySeconds
)
Start-Process -FilePath pwsh -ArgumentList @('-c',"{Start-Sleep $StdOutDelaySeconds; Write-Output 'Test' }")
exit 0

Expected behavior
On Windows, there is no exception and the standard output that was received after the process exited is not redirected to the file.
Actual behavior
When executed on Unix (Linux Azure Container Instance), there is an unhandled exception because the object is disposed when the data is received.  Under less contrived circumstances, the issue only appears intermittently.  I saw this comment in the if Unix region indicating that the ExitHandler waits for a second on another thread in hopes of avoiding a race condition whereas the non-Unix region has more involved logic.
An error has occurred that was not properly handled. Additional information is shown below. The PowerShell process will exit.

Unhandled Exception: System.ObjectDisposedException: Cannot write to a closed TextWriter.
   at System.IO.StreamWriter.WriteLine(String value)
   at Microsoft.PowerShell.Commands.StartProcessCommand.StdOutputHandler(Object sendingProcess, DataReceivedEventArgs outLine)
   at System.Diagnostics.Process.OutputReadNotifyUser(String data)
   at System.Diagnostics.AsyncStreamReader.FlushMessageQueue(Boolean rethrowInNewThread)
--- End of stack trace from previous location where exception was thrown ---
   at System.Diagnostics.AsyncStreamReader.<>c.<FlushMessageQueue>b__17_0(Object edi)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

Environment data
Windows Environment
Name                           Value
----                           -----
PSVersion                      6.2.2
PSEdition                      Core
GitCommitId                    6.2.2
OS                             Microsoft Windows 10.0.17763
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Unix Environment
Name                           Value
----                           -----
PSVersion                      6.2.2
PSEdition                      Core
GitCommitId                    6.2.2
OS                             Linux 4.15.0-1052-azure #57-Ubuntu SMP Tue Jul 23 19:07:16 UTC 2019
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

@hpaul-osi Can you confirm the issue with latest 7.0 build?


[research] Pre-pay easier than post-pay?

It may be the case that pre-loading wallet with funds is significantly easier to engineer. If this is the case, we should go back to sales to discuss.

Assigning to you @Atmosfearful


Subtask 6: Implement the connection between the Timer Dropdown and Timer Icon - FE

Add a connection between the timer icon and the dropdown for the timer in the front end start recording page. #184

Build works succesfully


Hide own repositories

Describe the feature
Add a checkbox to hide own repositories from the list in /stats/{username}
It should be implemented because
No response
Did you think about any alternative?
No response
Additional context
No response
Extra fields

[X] I have used the search function to check if an issue already exists
[ ] I'd like to work on this issue

I can work on this!

Assigned, go for it! :D


Sth is wrong with the dates after 6 November 2017.

This is my calendar:

I arrange it like this:
func configureCalendar(_ calendar: JTAppleCalendarView) -> ConfigurationParameters {

    let startDate = DateFormatter(type: .date, utcTimeZone: true).date(from: "01.01.2017")!
    let endDate = DateFormatter(type: .date, utcTimeZone: true).date(from: "01.01.2025")!

    return ConfigurationParameters(startDate: startDate, endDate: endDate, calendar: Calendar.currentUTC, firstDayOfWeek: .monday)
}

When I tap on the day, I display controller and set a date I tapped like this:
This is for 1 November

for 3 November:

For 5 November:

For 6 November:

As you can see the SAME dates are displayed for 5th and 6th November. Why?
What is wrong with that date?
Assuming. Everything is fine for the dates before 6th November, and everything is off after 6th November. Why?
update:
That critical date is different for every time zone I use. For example:
Warsaw (+0200) the date is 30 October
Chicago (-0500) the date is 6th November

i guess you realized why?

yes, the problem was related to sth else...


Add tests for side effects

I started out by adding some side effect tests and then I ended up refactoring the Erlang code and changing how things are done on the JavaScript side.

I added the temporary and simplified packages as dev dependencies to better test side effects (writing to files) inside the cached method.
The Erlang code seemed more complex than it needed to be so I simplified it a bit. I'm not super familiar with Erlang so maybe I'm missing something.
I found out that the JavaScript code didn't handle functions that return Nil so I changed it so that works now (maybe not an ideal solution). It could also be that this is the intended behavior but I don't think there is any way to prevent people from doing that with the type system alone.

Feel free to take all/some/none of these ideas.

Can you also rebase to get the updated CI suite that runs the tests in JS as well?

I rebased this branch, removed the Erlang FFI changes and moved all of the side effect tests to a separate anti-pattern file.


Add go tests, add framework dockerfile

Closing as circle ci updates the config based on the config in the PR, hence changes added to https://github.com/creditkudos/auth-sample-implementations/pull/7


Users can log miles walked when they log trash bags

Closes #18

Also... the HTML validations require that each is greater than zero, not that at least one is greater than zero.


Test multiple backend types within unit tests

Currently, the unit tests use whichever backend is set in config.json. This is good enough if you manually execute the unit tests in both backends, but really the unit tests should do this for the developer. Only unit testing one backend might miss something failing in the other backend.
I'm not sure it's worth duplicating each test for each backend (the API should function the same no matter the backend?) so perhaps doing X iterations of the tests (X being the number of backends/number of times within the codebase that the abstract class Backend is implemented).

PR reviewed, approved and merged into another branch but not yet merged into master. Work complete so I'm closing the issue.

PR reviewed, approved and merged into another branch but not yet merged into master. Work complete so I'm closing the issue.


Pub/Sub SPI: Adding IAM methods and auto-generated unit tests

Note: grpc-google-pubsub-v1 depends on a new package grpc-google-iam-v1, which contains IAMPolicy and Policy.

A couple of questions on dependencies:

grpc-google-iam-v1 contains iam classes that will be used by all services, right?
Why does grpc-google-common-protos depend on protobuf-java 3.0.0-beta-3 instead of the latest protobuf-java 3.0.0?

yes, grpc-google-iam-v1 will be shared by multiple services.
I haven't updated the protobuf-java dependency in order to isolate changes. I will do a batch upgrade of grpc to 1.0.0 and protobuf to 3.0.0 in one go, without other changes at the same time.

Coverage increased (+0.2%) to 85.434% when pulling 96f22d36e0eaf55db2eb124dac99d2cb2f645b0a on garrettjonesgoogle:master into 7cd60df2f29f6e9e10729125b4023106bcf1ab1f on GoogleCloudPlatform:master.

@garrettjonesgoogle another general question: is there a real need for having a copy of setIamPolicy, setIamPolicy and testIamPermissions in both PublisherApi and SubscriberApi? It seems like a lot of duplicated code to me. Will other services use/require this approach as well? Did you consider putting the three methods in a dedicated PubSubIamApi class?

It's the general pattern for IAM. In services that follow the suggested pattern (see https://github.com/googleapis/googleapis/blob/master/google/genomics/v1/datasets.proto ), the methods are redeclared in each service declaration. This allows their documentation and http paths to be customized. Pub/Sub doesn't follow the suggested pattern in the proto declarations, although it shows up the correct way in the http view (see https://developers.google.com/apis-explorer/#p/pubsub/v1/ ).

Will setting the policy for a topic resource via the SubscriberApi (or for a subscription via the PublisherApi) fail? Or is this just for having specific docs and http endpoints?

The way it's set up currently, it will fail validation when the flattened methods are used, but the request-based methods would not fail. The http endpoints actually have zero impact on the gRPC call; we just use the http endpoint information to inform our codegen (we derive the validation from it).

I am closing this, rebased on top of master in #1229


tests: drivers: timer: Test drivers.timer.nrf_rtc_timer.stress fails on nrf52 platforms

Describe the bug
The test drivers.timer.nrf_rtc_timer.stress from /tests/drivers/timer/nrf_rtc_timer/ fails on nrf52dk_nrf52832 and nrf52840dk_nrf52840.
To Reproduce
Steps to reproduce the behavior:

have nrf52 platform connected
go to zephyr dir
run ./scripts/twister -p nrf52dk_nrf52832 --device-testing --device-serial /dev/ttyACM0 -v -v --inline-logs -T tests/drivers/timer/nrf_rtc_timer
See error

Expected behavior
The test passes
Impact
Not clear
Logs and console output
The script enters test_stress test case then hangs and is terminated by a timeout.
Environment (please complete the following information):

OS: Ubuntu 18.04
Toolchain ZEphyr SDK
Commit SHA or Version used: v2.5.0-rc1-173-g3f1d1f5773

With my nrf52dk and nrf52840dk I can't reproduce the failures: three runs on each board all passed.  Is this very intermittent?
Also look at https://github.com/zephyrproject-rtos/zephyr/issues/32072#issuecomment-775091078 and try running the clock skew program it references.  If LFCLK is slower than HFCLK on the test boards (negative skew) the test may be failing because of that.

I have now reproduced it at the reported commit 3f1d1f5773, but have not on current mainline a281d10cff8d after 10 runs on the same board that failed at the reported commit.
Interestingly it's the non-ZLI test variant that failed for me:
tests/drivers/timer/nrf_rtc_timer/drivers.timer.nrf_rtc_timer FAILED Timeout

It seems the issue was fixed in the meantime. I saw no fails in recent versions in any of my setups. Closing the issue.


Python script using the large model doesn't work

I am trying to run the following python script, which uses the large model:
import torchaudio
from audiocraft.models import MusicGen
from audiocraft.data.audio import audio_write

model = MusicGen.get_pretrained('large')
model.set_generation_params(duration=8)  # generate 8 seconds.

descriptions = ['happy rock', 'energetic EDM', 'sad jazz']

wav = model.generate(descriptions)  # generates 3 samples.

for idx, one_wav in enumerate(wav):
    # Will save under {idx}.wav, with loudness normalization at -14 db LUFS.
    audio_write(f'{idx}', one_wav.cpu(), model.sample_rate, strategy="loudness")

I got the following logs:
Downloading: "https://dl.fbaipublicfiles.com/audiocraft/musicgen/v0/9b6e835c-1f0cf17b5e.th" to /home/worker/.cache/torch/hub/checkpoints/9b6e835c-1f0cf17b5e.th
100%|██████████████████████████████████████| 6.07G/6.07G [03:57<00:00, 27.4MB/s]
Killed

It's worth mentioning that the computer freezes for a while before giving the Killed output.
Regarding my hardware, I have an AMD Ryzen 5 2500U processor with Radeon Vega Mobile Gfx and Nvidia GeForce GTX GPU (the appropriate drivers are already installed).
I'm on Ubuntu 20.04 OS.
Here is my output for nvidia-smi command:
Mon Jun 12 00:45:05 2023
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 520.61.05    Driver Version: 520.61.05    CUDA Version: 11.8     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ...  On   | 00000000:01:00.0 Off |                  N/A |
| N/A   38C    P8    N/A /  N/A |      9MiB /  2048MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      1056      G   /usr/lib/xorg/Xorg                  4MiB |
|    0   N/A  N/A      2033      G   /usr/lib/xorg/Xorg                  4MiB |
+-----------------------------------------------------------------------------+

Here is my output to lscpu:
Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   43 bits physical, 48 bits virtual
CPU(s):                          8
On-line CPU(s) list:             0-7
Thread(s) per core:              2
Core(s) per socket:              4
Socket(s):                       1
NUMA node(s):                    1
Vendor ID:                       AuthenticAMD
CPU family:                      23
Model:                           17
Model name:                      AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx
Stepping:                        0
Frequency boost:                 enabled
CPU MHz:                         1600.000
CPU max MHz:                     2000,0000
CPU min MHz:                     1600,0000
BogoMIPS:                        3992.30
Virtualization:                  AMD-V
L1d cache:                       128 KiB
L1i cache:                       256 KiB
L2 cache:                        2 MiB
L3 cache:                        4 MiB
NUMA node0 CPU(s):               0-7

Thanks in advance for any help

spent some time trying to figure out why i was getting Killed too. It's most likely an out of memory error. Right after you run you can tail your kern logs:
sudo tail /var/log/kern.log
#  Out of memory: Killed process 1004 ...


Request: Add git to support git+https://github.com/... package sources

I request adding the git package to support git+https://github.com/... package sources.

This is particularly relevant because of https://github.com/prefix-dev/pixi/issues/2588: even including git in dependencies doesn't allow to install packages from git.


Body no longer has ID/class when navigating via Turbolinks

When navigating via Turbolinks in the latest version of MS Edge, the body looses its classes and ID.  This does not happen in any other browser.
This is using the latest Turbolinks (5.2.0)

I've not been able to reproduce this using the following environment: http://mybrowser.fyi/report/5c0eb9a5a6b88e00146f374b (or on Edge 18.18262). Could you produce a live/minimal example to demonstrate this?

Creating a basic app doesn't seem to be enough. I will work on trying to find the exact conditions that make this happen.
Thanks!

Thanks @kthibodeaux. Often issues arise due to conflicts with third-party scripts, so that might be worth checking out.
Thanks again.

@domchristie I have managed to produce with a minimal app!
https://github.com/kthibodeaux/demo_app
It looks like when there is an audio tag above the rest of the layout (which there likely should not be) then on Edge the body tag loses its attributes.  It continues to work on other browsers.

Hi @kthibodeaux Thanks for digging into this further, and for creating a demo.
As it's quite an obscure browser-specific bug, I think the simplest solution is the one you suggested: avoid placing audio elements outside the body. It may also be worth raising this bug on https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/, too. Thanks again.


gpt-4-vision-preview: Validation error for Request body -> functions extra fields not permitted (type=value_error.extra)

Confirm this is a Node library issue and not an underlying OpenAI API issue

[X] This is an issue with the Node library

Describe the bug
Error during openai.createChatCompletion: Error: 400 1 validation error for Request body -> functions   extra fields not permitted (type=value_error.extra)     at APIError.generate (error.ts:66:14)     at OpenAI.makeStatusError (core.ts:358:21)     at OpenAI.makeRequest (core.ts:416:24)     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)     at async ChatCompletionStream._createChatCompletion (ChatCompletionStream.ts:96:20)     at async ChatCompletionStream._runChatCompletion (AbstractChatCompletionRunner.ts:426:12)
gpt-4-vision-preview doesn't work with streaming and functions.
To Reproduce
const callParams = {
model,
messages: api_messages,
top_p: 0.1,
stream: true,
};
const stream = await this.openai.beta.chat.completions.stream(callParams, {
signal: this.abortController.signal,
});
Code snippets
No response
OS
macOS
Node version
20.6
Library version
4.16.1

Sorry, this repo is for the TypeScript SDK - for help using the API, please try community.openai.com or the OpenAI Discord channel.

Sorry, this repo is for the TypeScript SDK - for help using the API, please try community.openai.com or the OpenAI Discord channel.

that was the point, SDK works well with 'gpt-4-1106-preview', but  'gpt-4-vision-preview' for simple query like "hello" fails when functions included with streaming. But works fine without streaming.

Can you share a full code example? What I see above doesn't include functions from what I can see...

In any case, the error you're seeing is coming from the API, not the SDK.

I'm getting the same error when using gpt-4-vision-preview. "BadRequestError: 400 1 validation error for Request"
Here is a full demo:
import OpenAI from "openai";

const openai = new OpenAI();

async function main() {
  const response = await openai.chat.completions.create({
    model: "gpt-4-vision-preview",
    response_format: "json",
    messages: [
      {
        role: "system",
        content: "Return answer in JSON format",
      },
      {
        role: "user",
        content: [
          { type: "text", text: "What’s in this image?" },
          {
            type: "image_url",
            image_url:
              "https://assets2.devourtours.com/wp-content/uploads/slice-of-tortilla-de-patatas-on-white-plate-Cropped-1.jpeg",
          },
        ],
      },
    ],
  });
  console.log(response.choices[0]);
}
main();

For anyone who finds this issue via google.
Official OpenAI response:
JSON mode is supported for gpt-4-1106-preview but not for gpt-4-vision-preview, as of Nov 7th.


ICompileModule: how to know that the build is fully done

PostSharp needs to perform its job in a separate process or AppDomain. The best option from a performance point of view is for PostSharp to use a single AppDomain to build all projects in the current application. Then, to save memory, the AppDomain must be unloaded.
How can I know that DNX is done building all assemblies and that the AppDomain can be unloaded?
Is there even a concept of "being done"? It seems that projects are built on demand when assemblies are loaded.

Unfortunately, that;s just not a scenario we support. AppDomains don't even work on CoreCLR so you might want to change your approach completely here.

We use this approach for the same reason that you're using the "preprocess" compilation step: the project contains code that can modify the compilation. The difference is that any code can run at build time. So we need to load the output of the compiler in a standalone process/AppDomain, execute transformations, compile back the assembly and unload the process/AppDomain.
At short term the only other option we have is to run PostSharp out-of-process, which is fine feature-wise but will be slower.
Note that we won't support CoreCLR for a while.


Custom proxy context path is missing from some URLs in user_profile/gadget.xml

When a custom proxy context path is added in the carbon.xml, below use case in IS Dashboard fails.

Select View Details from My Profile.
Check Enable TOTP option and Update.

This will display an "Error while updating Profile" error.
This is because some URLs configured in <IS_HOME>/repository/deployment/server/jaggeryapps/portal/gadgets/user_profile/gadget.xml are missing PROXY_CONTEXT_PATH prefix which will cause them to redirect to the default URL without the proxy context path. Since there's no session cookie previously created for that path, above error will occur.

Fixed with wso2/product-is#4434
When adding a custom proxy context path to the carbon.xml update following files as well.

<IS_HOME>repository/deployment/server/jaggeryapps/portal/conf/site.json

<IS_HOME>/repository/deployment/server/jaggeryapps/dashboard/conf/site.json

Resolving as the issue is addressed