Motion sensor connected via USB power stops detecting motion

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within Z-Wave JS UI (formerly ZwaveJS2MQTT)?
NO, my problem is NOT within Z-Wave JS UI
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
What causes the bug?
What do you observe?
After restarting the host system, some the Aeotec multisensor 7 sensors stop sending motion events.
What did you expect to happen?
Never
Steps to reproduce the behavior:

Restart the ZwaveJS
Trigger motion event in a multisensor 7 device.

Log is filled with:
2023-04-22T02:45:04.494Z DRIVER « [Node 020] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -73 dBm
                                  └─[Security2CCMessageEncapsulation] [INVALID]
                                      error: Security2CC_NoSPAN
2023-04-22T02:45:04.498Z CNTRLR » [Node 020] No SPAN is established yet, cannot decode command. Requesting a non
                                  ce...
2023-04-22T02:45:04.510Z SERIAL » 0x012000a90114149f027f01d6ce365a83c881a8168e0b874c6c55ba05000000009 (34 bytes)
                                  ec2
2023-04-22T02:45:04.512Z DRIVER » [Node 020] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x05
                                  │ callback id:      158
                                  └─[Security2CCNonceReport]
                                      sequence number:  127
                                      SOS:              true
                                      MOS:              false
                                      receiver entropy: 0xd6ce365a83c881a8168e0b874c6c55ba
2023-04-22T02:45:04.519Z SERIAL « [ACK]                                                                   (0x06)
2023-04-22T02:45:04.522Z SERIAL « 0x010401a90152                                                       (6 bytes)
2023-04-22T02:45:04.524Z SERIAL » [ACK]                                                                   (0x06)
2023-04-22T02:45:04.526Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2023-04-22T02:45:04.534Z SERIAL « 0x011d00a99e00000100b77f7f7f7f00000300000000030100007f7f7f7f7f1d    (31 bytes)
2023-04-22T02:45:04.535Z SERIAL » [ACK]                                                                   (0x06)
2023-04-22T02:45:04.538Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            158
                                    transmit status:        OK, took 10 ms
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 100 kbit/s
                                    ACK RSSI:               -73 dBm
                                    ACK channel no.:        0
                                    TX channel no.:         0
2023-04-22T02:45:04.547Z SERIAL « 0x012a00a8000114219f0367011241badc6634d40626ed61ea8238361db49db6900 (44 bytes)
                                  bf276a24eac39ded800b890
2023-04-22T02:45:04.551Z SERIAL » [ACK]                                                                   (0x06)
2023-04-22T02:45:04.554Z CNTRLR   [Node 020] [~] [Battery] level: 100 => 100                        [Endpoint 0]
2023-04-22T02:45:04.556Z CNTRLR   [Node 020] [~] [Battery] isLow: false => false                    [Endpoint 0]
2023-04-22T02:45:04.559Z DRIVER « [Node 020] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -72 dBm
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 103
                                    │ extensions:
                                    │ · type: SPAN
                                    │   sender EI: 0xbadc6634d40626ed61ea8238361db49d
                                    └─[BatteryCCReport]
                                        level:  100
                                        is low: false

Device information
Manufacturer: Aeotec
Model name: Multisensor 7
Node ID in your network: 20
How are you using node-zwave-js?

[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker image (latest)
[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker image (dev)
[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[ ] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?
version:
node-zwave-js branch:
zwave-js-ui branch:
Did you change anything?
yes (please describe)
If yes, what did you change?
No response
Did this work before?
Don't know, this is a new device
If yes, where did it work?
No response
Attach Driver Logfile
zwave_js.log

I don't see anything obviously wrong with that log. That error you mention happens when the node sends it first report where the shared encryption state between Z-Wave JS and the node is out of sync. This is then re-synchronized and the node re-transmits its command, which is a battery report:
2023-04-22T02:45:04.494Z DRIVER « [Node 020] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -73 dBm
                                  └─[Security2CCMessageEncapsulation] [INVALID]
                                      error: Security2CC_NoSPAN
2023-04-22T02:45:04.512Z DRIVER » [Node 020] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x05
                                  │ callback id:      158
                                  └─[Security2CCNonceReport]
                                      sequence number:  127
                                      SOS:              true
                                      MOS:              false
                                      receiver entropy: 0xd6ce365a83c881a8168e0b874c6c55ba
2023-04-22T02:45:04.559Z DRIVER « [Node 020] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -72 dBm
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 103
                                    │ extensions:
                                    │ · type: SPAN
                                    │   sender EI: 0xbadc6634d40626ed61ea8238361db49d
                                    └─[BatteryCCReport]
                                        level:  100
                                        is low: false

The other occurences are on other S2-capable nodes, so I guess you recently restarted?

I suppose you're running into this bug in the sensor:

Try a firmware update: https://aeotec.freshdesk.com/support/solutions/articles/6000255731-update-multisensor-7-v1-4-2

I attempted the firmware update.  However, after the update the device was not able to be interviewed.
This sensor is in the ceiling, it will be very hard for me to try to reset the device.
2023-05-03T00:19:16.552Z CNTRLR « [Node 020] received information for parameter #1:
                                  parameter name:      Beaming Enable/Disable
                                  value format:        Enumerated
                                  value size:          1 bytes
                                  min value:           0
                                  max value:           1
                                  default value:       0
                                  is read-only:        false
                                  is advanced (UI):    false
                                  has bulk support:    false
                                  alters capabilities: false
2023-05-03T00:19:16.557Z CNTRLR » [Node 020] querying parameter #2 information...
2023-05-03T00:19:16.716Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:19:17.658Z CNTRLR   [Node 020] failed to decode the message, retrying with SPAN extension...
2023-05-03T00:19:17.679Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2023-05-03T00:19:17.918Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:19:18.470Z CNTRLR « [Node 020] received information for parameter #2:
                                  parameter name:      Motion Retrigger Time
                                  value format:        UnsignedInteger
                                  value size:          2 bytes
                                  min value:           0
                                  max value:           3600
                                  default value:       30
                                  is read-only:        false
                                  is advanced (UI):    false
                                  has bulk support:    false
                                  alters capabilities: false
2023-05-03T00:19:18.472Z CNTRLR » [Node 020] querying parameter #3 information...
2023-05-03T00:19:18.651Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:19:19.668Z CNTRLR   [Node 020] Timed out while waiting for a response from the node (ZW0201)
2023-05-03T00:19:19.670Z CNTRLR « [Node 020] received information for parameter #3:
                                  parameter name:      Motion Untrigger Time
                                  value format:        UnsignedInteger
                                  value size:          2 bytes
                                  min value:           30
                                  max value:           3600
                                  default value:       240
                                  is read-only:        false
                                  is advanced (UI):    false
                                  has bulk support:    false
                                  alters capabilities: false
2023-05-03T00:19:19.676Z CNTRLR » [Node 020] querying parameter #4 information...
2023-05-03T00:19:19.738Z CNTRLR   [Node 020] failed to decode the message, retrying with SPAN extension...
2023-05-03T00:19:20.320Z CNTRLR   [Node 020] failed to decode the message, retrying with SPAN extension...
2023-05-03T00:19:20.342Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2023-05-03T00:19:20.525Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:19:21.055Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:19:21.592Z CNTRLR « [Node 020] received information for parameter #4:
                                  parameter name:      Motion Sensitivity
                                  value format:        UnsignedInteger
                                  value size:          1 bytes
                                  min value:           0
                                  max value:           11
                                  default value:       11
                                  is read-only:        false
                                  is advanced (UI):    false
                                  has bulk support:    false
                                  alters capabilities: false
2023-05-03T00:19:21.597Z CNTRLR » [Node 020] querying parameter #5 information...
2023-05-03T00:19:21.760Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:19:22.782Z CNTRLR   [Node 020] Timed out while waiting for a response from the node (ZW0201)
2023-05-03T00:19:22.785Z CNTRLR « [Node 020] received information for parameter #5:
                                  parameter name:      Motion Report Type
                                  value format:        Enumerated
                                  value size:          1 bytes
                                  min value:           0
                                  max value:           2
                                  default value:       2
                                  is read-only:        false
                                  is advanced (UI):    false
                                  has bulk support:    false
                                  alters capabilities: false
2023-05-03T00:19:22.789Z CNTRLR » [Node 020] querying parameter #6 information...
2023-05-03T00:19:22.845Z CNTRLR   [Node 020] failed to decode the message, retrying with SPAN extension...
2023-05-03T00:19:23.361Z CNTRLR   [Node 020] failed to decode the message, retrying with SPAN extension...
2023-05-03T00:19:25.371Z CNTRLR   [Node 020] Timed out while waiting for a response from the node (ZW0201)
2023-05-03T00:19:25.417Z CNTRLR   [Node 020] failed to decode the message, retrying with SPAN extension...
2023-05-03T00:19:25.885Z CNTRLR   [Node 020] failed to decode the message after re-transmission with SPAN extens
                                  ion, dropping the message.
2023-05-03T00:19:25.888Z CNTRLR   [Node 020] Interview attempt 3/5 failed, retrying in 15000 ms...
2023-05-03T00:19:25.953Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:19:40.893Z CNTRLR   [Node 020] Beginning interview - last completed stage: NodeInfo
2023-05-03T00:19:40.959Z CNTRLR   [Node 020] Embedded device config loaded
2023-05-03T00:19:40.965Z CNTRLR   [Node 020] Interviewing Configuration...
2023-05-03T00:19:40.966Z CNTRLR   [Node 020] ConfigurationCC: Loading configuration parameters from device confi
                                  g
2023-05-03T00:19:41.033Z CNTRLR » [Node 020] finding first configuration parameter...
2023-05-03T00:19:41.089Z CNTRLR » [Node 020] querying parameter #1 information...
2023-05-03T00:19:41.685Z CNTRLR   [Node 020] failed to decode the message, retrying with SPAN extension...
2023-05-03T00:19:41.717Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2023-05-03T00:19:41.902Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:19:42.433Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:19:42.976Z CNTRLR « [Node 020] received information for parameter #1:
                                  parameter name:      Beaming Enable/Disable
                                  value format:        Enumerated
                                  value size:          1 bytes
                                  min value:           0
                                  max value:           1
                                  default value:       0
                                  is read-only:        false
                                  is advanced (UI):    false
                                  has bulk support:    false
                                  alters capabilities: false
2023-05-03T00:19:42.978Z CNTRLR » [Node 020] querying parameter #2 information...
2023-05-03T00:19:43.191Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:19:44.115Z CNTRLR   [Node 020] failed to decode the message, retrying with SPAN extension...
2023-05-03T00:19:44.136Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2023-05-03T00:19:44.370Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:19:44.919Z CNTRLR « [Node 020] received information for parameter #2:
                                  parameter name:      Motion Retrigger Time
                                  value format:        UnsignedInteger
                                  value size:          2 bytes
                                  min value:           0
                                  max value:           3600
                                  default value:       30
                                  is read-only:        false
                                  is advanced (UI):    false
                                  has bulk support:    false
                                  alters capabilities: false
2023-05-03T00:19:44.921Z CNTRLR » [Node 020] querying parameter #3 information...
2023-05-03T00:19:44.999Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2023-05-03T00:19:45.197Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:19:46.215Z CNTRLR   [Node 020] Timed out while waiting for a response from the node (ZW0201)
2023-05-03T00:19:46.216Z CNTRLR « [Node 020] received information for parameter #3:
                                  parameter name:      Motion Untrigger Time
                                  value format:        UnsignedInteger
                                  value size:          2 bytes
                                  min value:           30
                                  max value:           3600
                                  default value:       240
                                  is read-only:        false
                                  is advanced (UI):    false
                                  has bulk support:    false
                                  alters capabilities: false
2023-05-03T00:19:46.218Z CNTRLR » [Node 020] querying parameter #4 information...
2023-05-03T00:19:46.269Z CNTRLR   [Node 020] failed to decode the message, retrying with SPAN extension...
2023-05-03T00:19:46.837Z CNTRLR   [Node 020] failed to decode the message, retrying with SPAN extension...
2023-05-03T00:19:46.862Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2023-05-03T00:19:47.044Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:19:47.573Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:19:48.114Z CNTRLR « [Node 020] received information for parameter #4:
                                  parameter name:      Motion Sensitivity
                                  value format:        UnsignedInteger
                                  value size:          1 bytes
                                  min value:           0
                                  max value:           11
                                  default value:       11
                                  is read-only:        false
                                  is advanced (UI):    false
                                  has bulk support:    false
                                  alters capabilities: false
2023-05-03T00:19:48.117Z CNTRLR » [Node 020] querying parameter #5 information...
2023-05-03T00:19:48.297Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:19:49.250Z CNTRLR   [Node 020] failed to decode the message, retrying with SPAN extension...
2023-05-03T00:19:49.323Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:19:51.260Z CNTRLR   [Node 020] Timed out while waiting for a response from the node (ZW0201)
2023-05-03T00:19:51.261Z CNTRLR « [Node 020] received information for parameter #5:
                                  parameter name:      Motion Report Type
                                  value format:        Enumerated
                                  value size:          1 bytes
                                  min value:           0
                                  max value:           2
                                  default value:       2
                                  is read-only:        false
                                  is advanced (UI):    false
                                  has bulk support:    false
                                  alters capabilities: false
2023-05-03T00:19:51.264Z CNTRLR » [Node 020] querying parameter #6 information...
2023-05-03T00:19:51.314Z CNTRLR   [Node 020] failed to decode the message, retrying with SPAN extension...
2023-05-03T00:19:51.827Z CNTRLR   [Node 020] failed to decode the message, retrying with SPAN extension...
2023-05-03T00:19:53.832Z CNTRLR   [Node 020] Timed out while waiting for a response from the node (ZW0201)
2023-05-03T00:19:53.879Z CNTRLR   [Node 020] failed to decode the message, retrying with SPAN extension...
2023-05-03T00:19:54.349Z CNTRLR   [Node 020] failed to decode the message after re-transmission with SPAN extens
                                  ion, dropping the message.
2023-05-03T00:19:54.354Z CNTRLR   [Node 020] Interview attempt 4/5 failed, retrying in 20000 ms...
2023-05-03T00:19:54.415Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:20:14.358Z CNTRLR   [Node 020] Beginning interview - last completed stage: NodeInfo
2023-05-03T00:20:14.422Z CNTRLR   [Node 020] Embedded device config loaded
2023-05-03T00:20:14.433Z CNTRLR   [Node 020] Interviewing Configuration...
2023-05-03T00:20:14.435Z CNTRLR   [Node 020] ConfigurationCC: Loading configuration parameters from device confi
                                  g
2023-05-03T00:20:14.519Z CNTRLR » [Node 020] finding first configuration parameter...
2023-05-03T00:20:14.582Z CNTRLR » [Node 020] querying parameter #1 information...
2023-05-03T00:20:15.171Z CNTRLR   [Node 020] failed to decode the message, retrying with SPAN extension...
2023-05-03T00:20:15.198Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2023-05-03T00:20:15.381Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:20:15.910Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:20:16.454Z CNTRLR « [Node 020] received information for parameter #1:
                                  parameter name:      Beaming Enable/Disable
                                  value format:        Enumerated
                                  value size:          1 bytes
                                  min value:           0
                                  max value:           1
                                  default value:       0
                                  is read-only:        false
                                  is advanced (UI):    false
                                  has bulk support:    false
                                  alters capabilities: false
2023-05-03T00:20:16.455Z CNTRLR » [Node 020] querying parameter #2 information...
2023-05-03T00:20:16.616Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:20:17.577Z CNTRLR   [Node 020] failed to decode the message, retrying with SPAN extension...
2023-05-03T00:20:17.633Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:20:19.581Z CNTRLR   [Node 020] Timed out while waiting for a response from the node (ZW0201)
2023-05-03T00:20:19.589Z CNTRLR   [Node 020] Timed out while waiting for a response from the node (ZW0201)
2023-05-03T00:20:19.591Z CNTRLR « [Node 020] received information for parameter #2:
                                  parameter name:      Motion Retrigger Time
                                  value format:        UnsignedInteger
                                  value size:          2 bytes
                                  min value:           0
                                  max value:           3600
                                  default value:       30
                                  is read-only:        false
                                  is advanced (UI):    false
                                  has bulk support:    false
                                  alters capabilities: false
2023-05-03T00:20:19.594Z CNTRLR » [Node 020] querying parameter #3 information...
2023-05-03T00:20:20.234Z CNTRLR   [Node 020] failed to decode the message, retrying with SPAN extension...
2023-05-03T00:20:20.254Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2023-05-03T00:20:20.434Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:20:20.968Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:20:21.772Z CNTRLR   [Node 146] in the process of replying to a NonceGet, won't send another NonceR
                                  eport
2023-05-03T00:20:22.244Z CNTRLR   [Node 020] Timed out while waiting for a response from the node (ZW0201)
2023-05-03T00:20:22.246Z CNTRLR « [Node 020] received information for parameter #3:
                                  parameter name:      Motion Untrigger Time
                                  value format:        UnsignedInteger
                                  value size:          2 bytes
                                  min value:           30
                                  max value:           3600
                                  default value:       240
                                  is read-only:        false
                                  is advanced (UI):    false
                                  has bulk support:    false
                                  alters capabilities: false
2023-05-03T00:20:22.249Z CNTRLR » [Node 020] querying parameter #4 information...
2023-05-03T00:20:22.521Z CNTRLR   [Node 020] failed to decode the message, retrying with SPAN extension...
2023-05-03T00:20:23.091Z CNTRLR   [Node 020] failed to decode the message, retrying with SPAN extension...
2023-05-03T00:20:23.113Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2023-05-03T00:20:23.295Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:20:23.827Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:20:24.365Z CNTRLR « [Node 020] received information for parameter #4:
                                  parameter name:      Motion Sensitivity
                                  value format:        UnsignedInteger
                                  value size:          1 bytes
                                  min value:           0
                                  max value:           11
                                  default value:       11
                                  is read-only:        false
                                  is advanced (UI):    false
                                  has bulk support:    false
                                  alters capabilities: false
2023-05-03T00:20:24.369Z CNTRLR » [Node 020] querying parameter #5 information...
2023-05-03T00:20:24.528Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)
2023-05-03T00:20:25.546Z CNTRLR   [Node 020] Timed out while waiting for a response from the node (ZW0201)
2023-05-03T00:20:25.549Z CNTRLR « [Node 020] received information for parameter #5:
                                  parameter name:      Motion Report Type
                                  value format:        Enumerated
                                  value size:          1 bytes
                                  min value:           0
                                  max value:           2
                                  default value:       2
                                  is read-only:        false
                                  is advanced (UI):    false
                                  has bulk support:    false
                                  alters capabilities: false
2023-05-03T00:20:25.553Z CNTRLR » [Node 020] querying parameter #6 information...
2023-05-03T00:20:25.602Z CNTRLR   [Node 020] failed to decode the message, retrying with SPAN extension...
2023-05-03T00:20:26.122Z CNTRLR   [Node 020] failed to decode the message, retrying with SPAN extension...
2023-05-03T00:20:28.129Z CNTRLR   [Node 020] Timed out while waiting for a response from the node (ZW0201)
2023-05-03T00:20:28.182Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2023-05-03T00:20:28.322Z CNTRLR   [Node 020] failed to decode the message, retrying with SPAN extension...
2023-05-03T00:20:28.787Z CNTRLR   [Node 020] failed to decode the message after re-transmission with SPAN extens
                                  ion, dropping the message.
2023-05-03T00:20:28.791Z CNTRLR   [Node 020] Failed all interview attempts, giving up.
2023-05-03T00:20:28.851Z DRIVER   Dropping message because it could not be deserialized: The command class Appli
                                  cation Status is not implemented (ZW0303)

Should I restart the Zwave addon?
What should be the next step other than remove the device and readd ?

Ok looks like you're now running into an issue I fixed yesterday. Will make sure to get a new release out soon.

After forcing interview multiple times I recovered the device.
However, the lock up issue is still happening, even with firmware 1.4.2

After forcing interview multiple times I recovered the device.

That does sound like you have some connectivity issues and the reports just get lost.

After forcing interview multiple times I recovered the device.

That does sound like you have some connectivity issues and the reports just get lost.

Aeotec support reply with a beta version of a new firmware: 1.5.3 beta.
I will update to this version and report back here.

Unfortunately, even in version 1.5.3 of the firmware the issue still repro.

You may want to temporarily switch to Z-Wave JS UI and look into the connection strength with a health check.
Although if the firmware update went through, this can't be that bad - or did you move it for the update?

You may want to temporarily switch to Z-Wave JS UI and look into the connection strength with a health check.
Although if the firmware update went through, this can't be that bad - or did you move it for the update?

How do I switch to zwave js UI without loosing all the settings?
I there instructions somewhere?

https://www.home-assistant.io/integrations/zwave_js/#how-do-i-switch-between-the-official-z-wave-js-add-on-and-the-z-wave-js-ui-add-on
Minus step 5, do not uninstall if you plan to switch back. Switching back works similarly, but you check the "use the supervisor addon" box.

I failed to perform the migration to ZwaveJS-UI.
Problems:

The new addon does not allow me to edit the security config:

The add-on fails to start correcty:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
 Add-on: Z-Wave JS UI
 Fully configurable Z-Wave JS gateway and control panel
-----------------------------------------------------------
 Add-on version: 1.12.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 10.1  (aarch64 / yellow)
 Home Assistant Core: 2023.5.2
 Home Assistant Supervisor: 2023.04.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
Log level is set to INFO
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-zwave-js-ui: starting
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-nginx successfully started
s6-rc: info: service init-zwave-js-ui successfully started
s6-rc: info: service zwave-js-ui: starting
s6-rc: info: service zwave-js-ui successfully started
s6-rc: info: service discovery: starting
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
[08:48:06] INFO: Starting the Z-Wave JS UI...
2023-05-12 08:48:13.660 INFO APP: Version: 8.15.0
2023-05-12 08:48:13.672 INFO APP: Application path:/opt
  ______  __          __                      _  _____     _    _ _____
 |___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
    / /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |
   / /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |
  / /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_
 /_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|
2023-05-12 08:48:13.722 WARN STORE: scenes.json not found
2023-05-12 08:48:13.725 WARN STORE: nodes.json not found
2023-05-12 08:48:13.728 WARN STORE: users.json not found
2023-05-12 08:48:13.759 INFO APP: Listening on port 44920 host <IP_ADDRESS> protocol HTTP
[08:48:13] INFO: Starting NGinx...
2023-05-12 08:48:14.116 INFO MQTT: MQTT is disabled
2023-05-12 08:48:14.135 WARN BACKUP: Store backup is disabled
2023-05-12 08:48:14.140 WARN BACKUP: Nvm backup is disabled
2023-05-12 08:48:14.147 WARN Z-WAVE: Z-Wave driver not inited, no port configured
2023-05-12 08:48:21.313 INFO APP: GET /health/zwave 200 62.203 ms - 2140
2023-05-12 08:48:48.684 INFO APP: GET / 200 6.196 ms - 2140
2023-05-12 08:48:48.787 INFO APP: GET /static/js/126.6652f99f93c7eece9082.js 200 16.170 ms - 44168
2023-05-12 08:48:48.815 INFO APP: GET /static/css/app.6e9a0e56f46532006ef8.css 200 23.402 ms - 696282
2023-05-12 08:48:48.871 INFO APP: GET /static/js/app.7c25fc4ced5cca9e71dc.js 200 15.903 ms - 2204086
2023-05-12 08:48:51.632 INFO APP: GET /api/auth-enabled 200 28.710 ms - 29
2023-05-12 08:48:51.869 INFO APP: GET //static/fonts/MaterialIcons-Regular.2d80174.woff2 200 4.432 ms - 125116
2023-05-12 08:48:51.965 INFO APP: GET /static/logo.png 200 67.860 ms - 26171
2023-05-12 08:48:52.224 INFO APP: GET /api/settings 200 318.541 ms - 12910
2023-05-12 08:48:52.289 INFO APP: GET /api/auth-enabled 304 7.448 ms - -
2023-05-12 08:49:00.370 WARN Z-WAVE: Zwavejs driver is not ready yet, statistics will be enabled on driver initialization
2023-05-12 08:49:00.377 INFO APP: POST /api/statistics 200 53.394 ms - 89
2023-05-12 08:49:10.613 INFO Z-WAVE: Calling api getProvisioningEntries with args: [ [length]: 0 ]
2023-05-12 08:49:10.621 ERROR APP: Unhandled Rejection, reason: TypeError: Cannot read properties of undefined (reading 'isInBootloader')
2023-05-12 08:49:11.964 INFO APP: GET /api/settings 200 161.288 ms - 12956
2023-05-12 08:49:12.031 INFO APP: GET /api/auth-enabled 304 6.957 ms - -
2023-05-12 08:49:15.092 INFO Z-WAVE: Calling api _getScenes with args: [ [length]: 0 ]
2023-05-12 08:49:15.096 ERROR APP: Unhandled Rejection, reason: TypeError: Cannot read properties of undefined (reading 'isInBootloader')
2023-05-12 08:49:17.412 INFO APP: GET /api/store 200 12.376 ms - 584
2023-05-12 08:49:19.731 INFO Z-WAVE: Calling api refreshNeighbors with args: [ [length]: 0 ]
2023-05-12 08:49:19.734 ERROR APP: Unhandled Rejection, reason: TypeError: Cannot read properties of undefined (reading 'isInBootloader')
2023-05-12 08:50:21.327 INFO APP: GET /health/zwave 200 4.868 ms - 2140

These are the stats for Node 20 (the motion sensor). After this I am trying to recover the network:

I went back to the old ZwaveJS. I dont have the stomach to have the network going down.

You need to configure the same path and security keys in the addon's web ui under settings that  you have in the core addon config.
Then it should just be a matter of waiting until all devices are interviewed.

I have completed the fast migration to ZwaveJS-UI, however initially the network was running super slow. Turning off/on a light takes up to 30 seconds.
It seems that after 10 minutes, it recover itself, I hope this is normal.
What do you need me todo in the ZwaveUI control panel for node 20?

Go to the network map, reload graph, click Node 20 there, click "check health" in the popup panel, keep the controller (node 1) as the target, start a health check, wake up the node so it actually starts.

Node 20:

Check result:
(Running)

Interestingly enough, after I did the check health test, the sensor stopped sending motion events.

The first few attempts aren't looking too reliable, the last few (I assume that's after the route change) are much better.
Not sure if the node is also using that route now, or if it still has a different one.
But if it still drops commands, it might not be using that route for unsolicited reports. You can try healing just that node now, hoping that the controller will assign it that good route.
Unfortunately we don't know if it doesn't send the commands or if they get lost. You'd have to use a Zniffer to figure that out.

Also side question: Is your Z-Wave stick on a USB extension?

I have an usb extension and the dongle is in middle air:

I will try to restart zwave addon next time that the issue happens.
I do have an additional zwave dongle, will install the sniffer to learn how to detect events coming from the sensor.

Aeotec Z-Stick 7 I see. EU or US? The EU version has connectivity issues.
Could be worth a try switching to the other stick (which one specifically?) temporarily - you can do that relatively easy using Z-Wave JS UI:

Do an NVM backup of the current stick
switch sticks, make sure the path is correct
restore the NVM backup onto the other stick

If that doesn't help, you can just switch sticks again and everything should be back to the previous state.

Thanks, I am only using US radios.

After modifing the motion retirgger timeout from 30 seconds to 240 seconds the sensor has been working better, so far the issue has not repro.
However, after migration to ZWaveJS-UI I started to see another issue where ZwaveJS fails completely in home-assistant


enh: Add SPMD interfaces for Covariance

Description
Please include a summary of the change. For large or complex changes please include enough information to introduce your change and explain motivation for it.
Changes proposed in this pull request:

/intelci: run

/intelci: run


Return Asset Growth since last request

I don't really see the value in this one. Daily growth is the norm. And this FR would require per-source tracking of asset requests.

I don't really see the value in this one. Daily growth is the norm. And this FR would require per-source tracking of asset requests.


Cycles not detected

Hi Jonas,
many thanks for the new version. I've had a quick play.
Issue 41 is marked as fixed/closed. I can't re-open it, but it appears not to be fixed. Here's my simple example...
G1:
text: This is a Goal
supportedBy: [S1]
S1:
text: This is a Strategy.
supportedBy: [G2.1]
G2.1:
text: subgoal
# circular reference!!
supportedBy: [G1]
This contains a cycle but no error message is generated by gsn2x.
Many thanks...
gary

Thanks, @DoctorGM. That is interesting, since I have exactly that test case implemented.
I will check that today.

Hi @DoctorGM, I found the root cause.
The program expects that there is at least one unreferenced element.
Your example does not have that. I extended the check for unreferenced elements and the documentation in the #49 MR.
I will release it later today.
Thanks again.


COCO (obj det) Submission Error: Execution time limit exceeded!

the scoring error log as follows:
WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
/opt/conda/lib/python2.7/site-packages/matplotlib/font_manager.py:273: UserWarning: Matplotlib is building the font cache using fc-list. This may take a moment.
warnings.warn('Matplotlib is building the font cache using fc-list. This may take a moment.')
Execution time limit exceeded!
but my submission of the mvd dataset was finished successfully.
the det result format:
[{
"image_id": str,
"category_id": int,
"bbox": [x,y,width,height],
"score": float,
}]
any advices? thanks

Hi, COCO evaluation server is still being rebuild. Please see this issue for updates:
https://github.com/ozendelait/rvc_devkit/issues/64
Please proceed to submit to OID in the meantime.

Hi, COCO evaluation server is still being rebuild. Please see this issue for updates: #56 Please proceed to submit to OID in the meantime.

ok
btw, will the ddl be postponed？


[WIP] PCM-1540 PCM-1559 PCM-1552

bump streaming-client v13.2.2 and use http client from sc for better error outputs. remove PII from sdk logs

The retry logic in streaming-client needs to be touched up. Right now it doesn't cancel any "retrying" requests when you make another one. There needs to be a way to cancel those (which there is, I just didn't expose it).


Nav bar on password update page styled differently from elsewhere

The navigation bar on the "change password" page is narrow than the bar on all the other pages. Inside the wrong div, maybe?

There are other pages where nav bar is narrow. I don't see any rule. @pbanaszkiewicz, when base_nav_fixed.html and base_nav_fluid.html should be used? Could we stick one with them and get rid of the another?

The rule was "if the page is wide, a wide navbar should be used", e.g. all pages with filters are wide and (probably) all object-details pages use narrow navbar.

I'd dismiss this issue because there are other pages with navbar styled in the same way as on the "change password" page -- @gvwilson ?


glx2 does not always replace SE when opening a script

example:
I just did a find for a function name (in the card editor), and double-clicked on one of the entries.
the SE opened, instead of glx2

Again, what's a 'card editor'?

For lack of a better word, it's when I am not in the script editor.  What did we used to call it in HC?

Ah. I don't remember what HC called that thing. You're referring to the "Find and Replace" palette? If so, that seems to be stack "revSearch". And double-clicking an entry brings up glx2 for me. I'm assuming you've grabbed the latest version here. I realize saying "it works for me" isn't much help. Is there some other plugin that's getting in the way? What should be happening is that the "editScript" message is intercepted by the glx2 script editor frontscript. If something else is getting it first then that might explain things.

No, that's not what I meant. I meant whatever it was called when you had either the button tool or the field tool selected, and therefore you were editing buttons or fields. Now, we have the, uh, pointer and the pointer with the compass. I think of that as the "card editor", because you're not in the script editor, you're editing cards (or backgrounds, etc.)

OK - I'm really confused now. So I select an object with the cursor in... er... pointer and compass mode... and I press control-F to find things. And that brings up the Find and Replace palette. If I search for a handler I get an entry, and then double-clicking it brings up the proper script editor.
Seth could well be a conflict if it's trying to do similar things in a frontscript. I'll keep my fingers crossed that it's the issue because I'm not sure where else to look.

Just checked... yep... Seth also grabs the editScript message in a frontscript before glx2 has a chance to see it. But it does pass the message on when it's done colorizing, so I'm not sure why glx2 as a second frontscript isn't getting the message for you.

So far, so good. I just disabled seth and both of the issues I reported stopped. I'm going to close this unless it comes back.

Reopening to keep this flagged so I can see if there's a way to avoid the conflict.

OK - give it a try with the new build and see if the conflict is gone.


dep(concerto) Add Concerto tools to dependencies for Ergo compiler

Signed-off-by: Jerome Simeon<EMAIL_ADDRESS>

Coverage remained the same at 99.584% when pulling da9333e8b0d8acd1f72077085efcceaef287fc55 on js-fix-concerto-tools into dd4ef533d4ee11d44e9ac5a4298dbb9688609430 on master.


Don't do operations on a closed ZipFile

When zip file was opened inside the loop and it did not contain the lib
inside of it, the zipFile stayed non-null for all next iterations. This
can cause next iterations that fail to open zip file to access
previously already closed zipFile because zipFile == null will never
be true.
Fixed by moving the zipFile declaration inside of the loop.

When zip file was opened inside the loop and it did not contain the lib
inside of it, the zipFile stayed non-null for all next iterations. This
can cause next iterations that fail to open zip file to access
previously already closed zipFile because zipFile == null will never
be true.

This doesn't make sense to me.  As is, the variable is fresh on each loop iteration - subsequent iterations cannot see values assigned in previous iterations, because it's effectively a new variable.
With your proposed fix, it will definitely become possible for values to "bleed through" between iterations, which seems logically incorrect.
Finally, I'm not sure what actual problem is being solved here.  Is it possible to provide some concrete problem, like a crash report or a reproduction?

Currently the variable bleeds through iterations and my patch fixes this, not the other way around. But let me try to describe the problem more precisely.
This is the crash that we get (relinker 1.3.1):
java.lang.IllegalStateException: zip file closed at java.util.zip.ZipFile.ensureOpen(ZipFile.java:706) at java.util.zip.ZipFile.getEntry(ZipFile.java:335) at
com.getkeepsafe.relinker.ApkLibraryInstaller.findAPKWithLibrary(ApkLibraryInstaller.java:92) at
com.getkeepsafe.relinker.ApkLibraryInstaller.installLibrary(ApkLibraryInstaller.java:125) at
com.getkeepsafe.relinker.ReLinkerInstance.loadLibraryInternal(ReLinkerInstance.java:180) at
com.getkeepsafe.relinker.ReLinkerInstance.loadLibrary(ReLinkerInstance.java:136) at
org.libsdl.app.SDL.loadLibrary(SDL.java:58) at
org.libsdl.app.SDLActivity.loadLibraries(SDLActivity.java:328) at
org.libsdl.app.SDLActivity.onCreate(SDLActivity.java:379) at
com.outfit7.bridge.EngineActivity.onCreate(EngineActivity.java:21) at
com.outfit7.engine.EngineHelper.onCreate(EngineHelper.java:245) at
com.outfit7.mytalkingtom2.MyTalkingTom2NativeActivity.onCreate(MyTalkingTom2NativeActivity.java:40) at android.app.Activity.performCreate(Activity.java:7032) at
android.app.Activity.performCreate(Activity.java:7023) at
android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1236) at
android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2836) at
android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2965) at
android.app.ActivityThread.-wrap11(Unknown Source:0) at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:1645) at
android.os.Handler.dispatchMessage(Handler.java:106) at
android.os.Looper.loop(Looper.java:164) at
android.app.ActivityThread.main(ActivityThread.java:6648) at
java.lang.reflect.Method.invoke(Native Method) at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438) at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:811)

We don't have a repro but I believe the problem is triggered this way:

One of the iterations of the loop for (String sourceDir : sourceDirectories(context) opens the zip file with zipFile = new ZipFile(new File(sourceDir), ZipFile.OPEN_READ);
If we don't find the lib in that iteration, the zipFile is closed at end of the iteration with zipFile.close();. But it is not nulled!
On next iteration zipFile = new ZipFile(new File(sourceDir), ZipFile.OPEN_READ); can fail, resulting in zipFile keeping the value from previous iteration.
if (zipFile == null) check does not skip this iteration, because zipFile is not null.
We crash at libraryEntry = zipFile.getEntry(jniNameInApk); because we are doing operations on an already closed zipFile from previous iteration.

My proposed fix moves the zipFile inside the loop because I don't see a need to keep the value of it over multiple iterations. I could be missing something though.

I don't know how I managed to misread this simple PR, but I did - of course, you're correct.  Moving the variable into the loop fixes that problem.  I must have mixed up the red and green lines in the diff.
This now looks fine to me.  Thanks!

I though something was off with you first comment, it took me a while to see that you probably mixed up the diff :)
Thanks for the review!

@emarc-m would you please review/merge this as well?  It's a legit bugfix.

@benjamin-bader Thanks for alerting me. I'll review as well.

@blaztinn Thanks for fixing. I'll include this on the next release and update once I do.


Fix Codecov

Short Description
Since codecov seems to fail, this pr will attempt to fix it.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@bf20e30). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #48   +/-   ##
=========================================
  Coverage          ?   40.80%
  Complexity        ?      192
=========================================
  Files             ?       77
  Lines             ?      919
  Branches          ?       29
=========================================
  Hits              ?      375
  Misses            ?      529
  Partials          ?       15


Very fast scrolling inside the webview

Hi all, I'm rendering html code of a book in webview but there is a problem, too fast scrolling inside webView, when trying to specify declarationRate nothing changes, I've tried almost everything but didn't find a solution.
https://github.com/react-native-webview/react-native-webview/assets/112204520/c623ec78-a0a8-4294-b3fa-77fee49528ff

any issues?


add while node

you know like the "if" node? yeah why isnt there a "while" node

unfeasiable due to difference in implementation on luastg-x and explus, plus it isnt that meaningful to the editor user in general from my perspective


Remove the snapshot dependency on MP 1.1-SNAPSHOT

Tests run: 44, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.891 s - in TestSuite

@asoldano I get no errors with this change. Please let me know if you still face problems


Test packages are visible on search results when filtering by last uploaded

Describe the bug
See twitter thread: https://twitter.com/buhakmeh/status/1299115494973341696
To Reproduce
Steps to reproduce the behavior:

Run Functional tests / E2E tests
Sort search results by "Recently updated"

Expected behavior
User packages only are shown
Screenshots

Additional context
We need to unlist/delete those packages after test completion

Previously tracked by https://github.com/NuGet/Engineering/issues/497.


Integrate pa11y as a check in push and pull request workflows

https://github.com/pa11y/pa11y
Pa11y is your automated accessibility testing pal. It runs accessibility tests on your pages via the command line or Node.js, so you can automate your testing process.

pa11y is catching and stopping issues.


Check EntityRenderer

net/minecraft/client/render/entity/EntityRenderer might not be the correct name for this.

Can you or someone else elaborate?

In older mapping projects, EntityRenderer was the name used for a rendering class that did a lot more than just rendering entities. We should make sure that our EntityRenderer mapping is actually for a class that is dedicated to rendering entities.

Our EntityRenderer is the name of the base class which other EntityRenderers inherit from and is dedicated to that purpose, much like BlockEntityRenderer. As such, solved!


Invalid line protocol format crashes influxdb <IP_ADDRESS>

This write is coming from graphios (which needs to be fixed to escape backslashes). This shouldn't crash influxd, though.
[http] 2016/01/20 14:52:15 <IP_ADDRESS> - graphios [20/Jan/2016:14:52:15 -0500] POST /write?p=%5BREDACTED%5D&u=graphios HTTP/1.1 204 0 - Python-urllib/2.6 4e5de0a5-bfaf-11e5-b736-000000000000 3.140773ms
[cluster] 2016/01/20 14:52:16 close remote connection from <IP_ADDRESS>:34321
panic: failed to parse point: `Disk,check=C:\,host=lp-admin-t01.lionpath.psu.edu,nagios_location=Shields value=52.45<PHONE_NUMBER>802451556`: unable to parse 'Disk,check=C:\,host=lp-admin-t01.lionpath.psu.edu,nagios_location=Shields value=52.45<PHONE_NUMBER>802451556': invalid tag format

Reading the documentation, I shouldn't have to escape the backslash. The problem is likely because the backslash is the last character in the tag value, immediately proceeded by a comma.

#5382 looks like it should prevent the panic, but it's still not parseable.  Looks like \ needs to be escapable as well because it's escaping the , and causing the tag format to become invalid.

As @jwilder mentions, this won't panic as of master, but it's not currently possible to have a tag value ending in a literal slash if there are tags after it (#5231).
Unfortunately the only workaround at the moment is to add another character to the tag value (which could be an escaped space, say), e.g., like this:  Disk,check=C:\\ ,host=..... Of course this means querying on that tag value would involve having to specify the space too, so it's not really a good alternative I'm afraid.

Hmm, agreed. How easy would it be possible to either allow backslash to be escaped? Or would it be preferable to handle the backslash-as-last-character case?
Should I file a new issue or just re-purpose this one?

@e-dard @phalenor I think the line protocol would need to handle \\ to make this work.  You would need to write in Disk,check=C:\\,host=lp-admin-t01.lionpath.psu.edu,nagios_location=Shields value=52.45<PHONE_NUMBER>802451556

Yep, makes sense. I would be happy to look at this, if you like.

On 21 Jan 2016, at 00:18, Jason Wilder<EMAIL_ADDRESS>wrote:
@e-dard @phalenor I think the line protocol would need to handle \ to make this work. You would need to write in Disk,check=C:\,host=lp-admin-t01.lionpath.psu.edu,nagios_location=Shields value=52.45<PHONE_NUMBER>802451556
—
Reply to this email directly or view it on GitHub.

@e-dard If you have time to look at it that would great.  Thanks!


Go directly into RNN layers without using Embeddings and preprocessing methods.

Hello,
We are currently working on an NLP research project.
We have already obtained our way of preprocessing, such as give a long document a specified vector representer. So, what the training set now is a fixed length decimal vector, and the output should be different labels.
However, as far as I know, Passage has its own preprocessing methods, and is kind of "required" for a training input.
Could I have any way to reduce Passage's own preprocessing procedures?
such as tokenizer and Embedding layer.
For example the layers looks like this
layers = [
            Embedding(size=256, n_features=tokenizer.n_features),
            GatedRecurrent(size=256, seq_output=True),
            GatedRecurrent(size=256, seq_output=False), # activation='t_rectify',
            Dense(size=1, activation='sigmoid')
        ]

So, is there any way to remove the first layer, so that the training inputs can directly go to RNN layers.
layers = [
            # Embedding(size=256, n_features=tokenizer.n_features),
            GatedRecurrent(size=256, seq_output=True),
            GatedRecurrent(size=256, seq_output=False), # activation='t_rectify',
            Dense(size=1, activation='sigmoid')
        ]

Well, if I do so, it will, of course, give error msg:
line 41, in __init__
    self.params = flatten([l.params for l in layers])
AttributeError: 'GatedRecurrent' object has no attribute 'params'

Thank you.

This can be done with the generic layer. For an example,  check the mnist demo https://github.com/IndicoDataSolutions/Passage/blob/master/examples/mnist.py


Display missing components.css during loading

Hi，Thank you for you code.
When I try to start this project. system report a error: ENOENT: no such file or directory, open '\src\data\categories\components.css.mdx'
The Component page, It really didn't work.
Can you please provide this file to solve this problem?
Thank you again!

Hi, please try running this command:
npm run css:components

npx tailwindcss -i src/styles/components.css -o public/components.css -m

Consult the CONTRIBUTING guide for more details about this. Let me know if this fixes the issue.

Closing issue due to inactivity. Feel free to open a new one.


[#1052] fix: position name should support upper-case when add a column

What changes were proposed in this pull request?
Position name supports upper-case when add a column for FIRST and DEFAULT.
Why are the changes needed?
Position name should support upper-case when add a column. For example, the correct value of position is first NOT FIRST currently.
curl -X PUT -H "Accept: application/vnd.gravitino.v1+json" -H "Content-Type: application/json" -d '{
  "updates": [
    {
      "@type": "removeProperty",
      "property": "key2"
    }, {
      "@type": "setProperty",
      "property": "key3",
      "value": "value3"
    },
    {
    "@type": "addColumn",
    "fieldName": [
      "position"
      ],
    "type": "varchar(20)",
    "comment": "Position of user",
    "position": "FIRST"
    }
  ]
}' http://localhost:8090/api/metalakes/metalake/catalogs/catalog/schemas/schema/tables/table

Unknown json column position: "FIRST" (through reference chain: com.datastrato.gravitino.dto.requests.TableUpdatesRequest["updates"]->java.util.ArrayList[2])%

Fix: #1052
Does this PR introduce any user-facing change?
No.
How was this patch tested?
TestTableUpdatesRequest#testAddTableColumnRequest

Could you please add unit tests for uppercase?

@SteNicholas
Ignoring case is too broad, I think it's better to have all upper case or all lower case.

@yuqi1129, from a user perspective, ignoring case is better than have all upper case or all lower case. The position name could have cases like FiRst etc, which could not limit users.

@yuqi1129, from a user perspective, ignoring case is better than have all upper case or all lower case. The position name could have cases like FiRst etc, which could not limit users.

It's okay from SQL syntax to ignore case directly, but from the user's point of view, it's better to use all uppercase or all lowercase. I rarely see a mix of case and case in SQL keywords

@SteNicholas
Please rebase the main branch and update your PR


4.3.1 regression / Restore ability for DBField to return dynamic field assigment

Affected Version
Pretty much every version ever created
Description
To patch CVE-2019-5715, we disallowed DBField::prepValueForDB() from returning dynamic assignments (field assignment that relies on the execution of some DB function). The assumption was that what ever value one could want to compute on the DB Server, could just as easily be computed in the application in PHP.
However, there's some specialised application that require geographic or geometric function to be computed where this is required. e.g.:
    public function prepValueForDB($value)
    {
        if (!$value) {
            return null;
        }

        list($wkt, $srid) = GIS::split_ewkt($value);

        return ['ST_GeomFromText(?, ?)' => [$wkt, $srid]];
    }

Example from smindel/silverstripe-gis
Pull Requests

[x] #8815
[x] #8821 (SS3)

There's two solutions I could think off:

Add a allowDynamicAssigment method on DBField that would whitelist the field to have dynamic assigment. DataObject::writeManipulation() would have to check this method for the field to before throwing an exception.
Update DB::manipulate() to accept an SQLAssignmentRow object (or some similar entity). DBField::prepValueForDB() could build this object and add it to the manipulation array.

@chillu This issue is a regression and a semver break. However, I don't think there's an obvious way to fix it that resolve the semver breakage and doesn't weaken security.

Please have a look at my approach suggested in 25bba49

I've spent limited time on this but can't spend any more right now. Here's my patch:
diff --git a/src/ORM/DataObject.php b/src/ORM/DataObject.php
index 85ad5d8f1..6957e2f83 100644
--- a/src/ORM/DataObject.php
+++ b/src/ORM/DataObject.php
@@ -1474,11 +1474,14 @@ class DataObject extends ViewableData implements DataObjectInterface, i18nEntity
             if (!isset($tableManipulation['fields'])) {
                 continue;
             }
-            foreach ($tableManipulation['fields'] as $fieldValue) {
+            foreach ($tableManipulation['fields'] as $fieldName => $fieldValue) {
                 if (is_array($fieldValue)) {
-                    throw new InvalidArgumentException(
-                        'DataObject::writeManipulation: parameterised field assignments are disallowed'
-                    );
+                    $dbObject = $this->dbObject($fieldName);
+                    if ($dbObject && $dbObject->scalarValueOnly()) {
+                        throw new InvalidArgumentException(
+                            'DataObject::writeManipulation: parameterised field assignments are disallowed'
+                        );
+                    }
                 }
             }
         }

We should also do this for ManyManyList::add(), and write tests for both.
I have a test for prepValueForDB() accepting arrays when scalarValueOnly is false (this doesn't test the change above at all though):
# Class: DBFieldTest
    public function testPrepValueForDBArrayValueWithNonScalarValuesAllowed()
    {
        /** @var DBField|PHPUnit_Framework_MockObject_MockObject $fieldAllowingNonScalars */
        $fieldAllowingNonScalars = $this->getMockBuilder(DBField::class)
            ->setMethods(['scalarValueOnly'])
            ->getMockForAbstractClass();
        $fieldAllowingNonScalars->expects($this->exactly(2))->method('scalarValueOnly')
            ->willReturnOnConsecutiveCalls(true, false);

        $input = ['GREATEST(0,?)' => [2]];

        $preparedValue = $fieldAllowingNonScalars->prepValueForDB($input);
        $this->assertNull($preparedValue, 'Should return null when scalars are enforced');

        $preparedValue = $fieldAllowingNonScalars->prepValueForDB($input);
        $this->assertSame($input, $preparedValue, 'Should return manipulation with non-scalars allowed');
    }

Awesome, thanks a lot!

I've implemented Robbie's suggestion for 4.0 and 3.6.

I can see the one for 3.6, can't find the 4.0 one though

Sorry ... copy-paste fail.
Here's the SS4 PR https://github.com/silverstripe/silverstripe-framework/pull/8815

Both PRs merged


operators [N] [CI] security-profiles-operator (0.4.2)

Adds the currently latest version of the Security Profiles Operator:
https://github.com/kubernetes-sigs/security-profiles-operator
Signed-off-by: Jakub Hrozek<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[x] Are you familiar with our contribution guidelines?
[x] Have you packaged and deployed your Operator for Operator Framework?

[x] Is your submission signed?
[-] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[-] Example templates for all Custom Resource Definitions intended to be used
[-] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

Thank you for working on this @jhrozek! :pray:

/merge possible

/merge possible

/merge possible


Webhook delete method

Hello,
I'm currently relying on this sdk for python, and I've come across one question. Knowing the add_webhook method, could I use delete_webhook?
Apparently I wasn't able to find anything regarding this method:
base.delete_webhook(webhook.id)

Where can I find it?
Thanks

Thanks


Cannot compile on Linux Fedora 40

here is the error log:
g++ -Os -Wall -pedantic -std=c++11   -c -o src/URIParse.o src/URIParse.cpp
In file included from src/URIParse.cpp:9:
src/../include/rtmfp/Hex.hpp:15:62: error: ‘uint8_t’ was not declared in this scope
15 |         static void print(const char *msg, const std::vector<uint8_t> &bytes);
|                                                              ^~~~~~~
src/../include/rtmfp/Hex.hpp:8:1: note: ‘uint8_t’ is defined in header ‘’; this is probably fixable by adding ‘#include ’
7 | #include
+++ |+#include
8 |
src/../include/rtmfp/Hex.hpp:15:69: error: template argument 1 is invalid
15 |         static void print(const char *msg, const std::vector<uint8_t> &bytes);
|                                                                     ^
src/../include/rtmfp/Hex.hpp:15:69: error: template argument 2 is invalid
src/../include/rtmfp/Hex.hpp:22:53: error: ‘uint8_t’ was not declared in this scope
22 |         static std::string encode(const std::vector<uint8_t> &bytes);
|                                                     ^~~~~~~
src/../include/rtmfp/Hex.hpp:22:53: note: ‘uint8_t’ is defined in header ‘’; this is probably fixable by adding ‘#include ’
src/../include/rtmfp/Hex.hpp:22:60: error: template argument 1 is invalid
22 |         static std::string encode(const std::vector<uint8_t> &bytes);
|                                                            ^
src/../include/rtmfp/Hex.hpp:22:60: error: template argument 2 is invalid
src/../include/rtmfp/Hex.hpp:24:57: error: ‘uint8_t’ was not declared in this scope
24 |         static bool decode(const char *hex, std::vector<uint8_t> &dst);
|                                                         ^~~~~~~
src/../include/rtmfp/Hex.hpp:24:57: note: ‘uint8_t’ is defined in header ‘’; this is probably fixable by adding ‘#include ’
src/../include/rtmfp/Hex.hpp:24:64: error: template argument 1 is invalid
24 |         static bool decode(const char *hex, std::vector<uint8_t> &dst);
|                                                                ^
src/../include/rtmfp/Hex.hpp:24:64: error: template argument 2 is invalid
src/URIParse.cpp: In static member function ‘static std::string com::zenomt::URIParse::percentDecode(const std::string&)’:
src/URIParse.cpp:226:38: error: ‘uint8_t’ was not declared in this scope
226 |                         rv.push_back(uint8_t(b));
|                                      ^~~~~~~
src/URIParse.cpp:11:1: note: ‘uint8_t’ is defined in header ‘’; this is probably fixable by adding ‘#include ’
10 | #include "../include/rtmfp/URIParse.hpp"
+++ |+#include
11 |
make: *** [: src/URIParse.o] Error
gcc 14.1.1
Thanks

thanks. i'll look at this tonight.

i don't have ready access to a Fedora 40 system (nor a desire to install a VM). rather than playing whack-a-mole, can you tell me if you get any other compile errors after adding an
#include <cstdint>

to include/rtmfp/Hex.hpp, just above the include for <string>? i'd like to fix all the problems at once. :)

in installed a Fedora 40 VM and replicated your build error with g++ 14.1.1. the only error was a missing #include <cstdint> in Hex.hpp. https://github.com/zenomt/rtmfp-cpp/commit/9c53bde974e6463537a4e5573a548e59eb45786c should fix that.
please confirm the problem is fixed for you, and i'll close this issue.

I confirm it compiles perfectly now. man thanks!


Login error resolution / simplification

This PR endeavors to resolve some nagging errors and broken functionality while removing, improving, or simplifying some parts of the application.

Eliminate onAuthSuccess() method from SignInPage and SignUpPage
Implement "find one or create" logic for user profile queries on server
Generally rely on Firebase-provided UID to interact with users on the database, rather than Mongo ObjectId
Correct property access on decoded Firebase auth token
Remove references to email and remove DB index on email
Add Skeleton to user name in SideNav
Various updates to import statements, variable names, typos, small syntax errors, etc.
Pass trace string to useFetchUserProfile() hook to track calls from various components
Consistent implementation of timestamps across DB models
Delete obsolete files: genAiController.ts and typeChecker.ts

Fixes #356
Type of change

[x]  🐛 Bug fix (non-breaking change which fixes an issue)

How Can this be tested? Testing Plan to review this PR

What are the steps to test this change?
Generally interact with the app as a user. Delete your accounts on Firebase Auth and Mongo, create new accounts, submit queries, interact with Flows, etc.
Expect reliable operation without errors.
Checklist:

[x] I have performed a self-review of my own code.
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] My changes generate no new warnings.

I deleted accounts in firebase and mongoDB and created users with google, github and with password. I'm still getting the 'failed to fetch user profile' error with a 404 user not found on v1/users' This also prevents me from creating any Linkta flows. @kinskiwu are you able to create flows on this branch?

@colinvandergraaf Can I mark this one resolved?

I deleted accounts in firebase and mongoDB and created users with google, github and with password. I'm still getting the 'failed to fetch user profile' error with a 404 user not found on v1/users' This also prevents me from creating any Linkta flows. @kinskiwu are you able to create flows on this branch?

@colinvandergraaf Can I mark this one resolved?

@relandboyle I think we can mark it as resolved since we discussed it at standup yesterday and clarified that it was an issue with the .env file on Colin's local machine. I didn't get this error following the same steps.


reversal content

I think this contents are reversal, maybe.

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

We have moved the Hugo site source to its own repository, so we would appreciate if you could open this PR directly in hugoDocs:  https://github.com/gohugoio/hugoDocs/pulls


Update provider-linux.md

just changed the order of the options on the tar command.  In the previous order, it didn't work as the "f" option expects the filename next.

@MightySuz
(second request) Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.

#sign-off


CWE integer parsing problem on Acunetix

Hi there,
There is a parsing problem on Acunetix codes. There are PRs according to the issue like below.
https://github.com/DefectDojo/django-DefectDojo/pull/6100
https://github.com/DefectDojo/django-DefectDojo/pull/5970
For Netsparker, this issue is fixed with this commit.
https://github.com/DefectDojo/django-DefectDojo/commit/63cdba42233d879b8c21b84e743cf17e3c0a8bc9
Could you implement the fix please?

merged for release 2.11


Added create_log4j_2_config to product logging

Description

Added method to create log4j2 config properties

Review Checklist

[x] Code contains useful comments
[x] (Integration-)Test cases added (or not applicable)
[x] Documentation added (or not applicable)
[x] Changelog updated (or not applicable)
[x] Cargo.toml only contains references to git tags (not specific commits or branches)

Once the review is done, comment bors r+ (or bors merge) to merge. Further information

bors merge


Start tracking Referer urls for page views

This will allow apps owners to understand the sources of incoming traffic to their pages. Value in this field is similar to the ones in HTTP referer header.

This could be really helpful. Would this be a new schema field? Or an automatically populated custom property when we autocollect PageViewData?

I would expect it to be a new auto-collected field in the page views schema.
For other types like requests,  it would be nice to have optional (opt-in) support to collect this info as a custom property. This part is lower priority.

Added in 2.0.0-rc1


DBeaver - Maximum statements that can be executed in the SQL Explorer?

Hi,
So I have tried to import and execute a few hundreds SQL statements and DBeaver gives me an error message when I get somewhere near 1000 statements.  Is that normal?  Can we make it show there is no limit or/and at least, read and execute directly from a .sql file?  This is the error message:
(conn:86) You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'ALTER TABLE languages ENABLE KEYS */;

There are no any limitations in DBeaver itself.
Perhaps it is just an error in SQL file or something. You can check Query Manager view to see what actual query caused the error.

I will check that Query Manager and see.  But if I copy and paste the first part and execute them, it works.  Then I copy and paste the last portion, and they work too.  So I can say the entire statements have no errors.

The maybe something is wrong with query delimiters.
Anyhow I can't say what is it without actual query example.
Just open query manager (main menu Window->Show View->Query Manager or click on Log item under SQL editor) and check what happens.

Found the issue.  The SQL export from HeidiSQL was not understood by DBeaver.  HeidiSQL exported the single quote character ' of a value using ', which may not work in DBeaver.


Query should fail after iteration

It is easily overlooked that Query is a throw-away one-time-use object.
Had the case of query re-use and zero iterations several times when updating the benchmarks in Arche.
This should at least be documented.
in Arche, I took the route of panicing when iterating after the end of the iterator.

Hmm indeed its easy to overlook, but I would not panic in such situation...
Honestly, I added in the project the QueryCursor.Restart() function to reuse the query, but I don't know if it makes sense in a game.
For example, in Overwatch they did the updates in a way that all intermediate generated data was kept in an singleton component, and processed at the end of the pipeline (think about physics, where you collect all contacts in the frame and proccess them at the end to update the ecs state, maybe in the start of the next frame iteration).
I can't think in an use for the Restart function, but I can see that a variable that's reused for a new query can lead to this type of errors. I'll add some alert to the documentation, that's a nice addition.


Add etl (embedded template library)

Corresponding PR https://github.com/mattgodbolt/compiler-explorer-image/pull/308

How do you envision profile selection working?
I noticed etl recently added automatic compiler detection, but it doesn't look like we have a way to enable this easily from CE because the user can't drop a custom_profile.h anywhere in the include path, and auto.h doesn't appear in the elif chain in etl_profile.h

Currently you need to specify something like -DPROFILE_CLANG_GENERIC depending on the selected compiler. I haven't found any way to configure those kind of flags automatically for the compilers in the c++.*.properties files.
I hope to convince the etl maintainers to either add something like -DPROFILE_AUTO or even make the auto detection a default fallback.

PROFILE_AUTO would be great
PROFILE_NONE would also be useful, allowing to basically short circuit the logic in etl_profile.h. It would require that any profile options be defined in the source code before including any etl headers, but that is perfect for our use case. It would allow the creation of snippets with specific combinations of etl options not covered by any built in profiles.


Youtube-DL is not working for Downloading Videos from PluralSight

Checklist

[ ] I'm reporting a broken site support issue
[x] I've verified that I'm running youtube-dl version 2019.11.28
[ ] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar bug reports including closed ones
[ ] I've read bugs section in FAQ

Verbose log

PASTE VERBOSE LOG HERE

Description

WRITE DESCRIPTION HERE

i am using latest youtube-dl also , still it is not working, Please share  procedure for how to do this .


Disable auto-addition of pip & setuptools

otherwise you end up with an error about pip not being able to depend on itself.

Thanks


The Classes Discovery hook should support the same OrderBy and Shuffle API as the Methods hook

To give better control over test execution order, Discovery conventions should be allowed to specify OrderBy and Shuffle for both test classes and test methods.

This was better resolved by other discovery phase fixes in the version 3 API.


⚠ Bofrost.fr has degraded performance

In c09f01c, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 846 ms

Resolved: Bofrost.fr performance has improved in a066a8a after 6 minutes.


[ Suggestion ] Better work with interaction entities

Basically like marker googles but for interaction entities (I do know you can just use f3 + B)
Also this may be not exactly for us (datapack devs) but it would be useful to have such options:

hi-light sphere of given radius around given marker.
make markers have 0.1 block ^ 3 select box (to select the by doing TAB and pointing, this is useful)
move interaction entities & markers ( like you can move schematics in litematicka mod for example, or make punching them with stick move them 0.1 blocks forward and right-clicking 0.1 blocks backwards )
show command in command block by looking at it (like floating text). (this is not directly of data packs but when you are testing simple things in flat world, its useful to see what command block does)
creating world already with blank test datapack

Thank you for the suggestions!

hi-light sphere of given radius around given marker.
This could be a configuration toggle to customize how marker goggles work.

make markers have 0.1 block ^ 3 select box (to select the by doing TAB and pointing, this is useful)
I'm assuming so it can automatically target the marker you are looking at? I'd like to hear more

move interaction entities & markers ( like you can move schematics in litematicka mod for example, or make punching them with stick move them 0.1 blocks forward and right-clicking 0.1 blocks backwards )
Planned sometime for the future

show command in command block by looking at it (like floating text). (this is not directly of data packs but when you are testing simple things in flat world, its useful to see what command block does)
Could definitely be a feature. I'm all for this.

creating world already with blank test datapack
Potentially - this can be done once Datamancer introduces configuration features


Need to add the navbar to manageAccount

We need to add the navbar to the manageAccount component.

I fixed it in c5abfaf


update document for namespaced federation

note: DELETE_CLUSTER_RESOURCE=y should be used for the last namespaced
deployment
limitedScope is changed to global variable

@gyliu513

/lgtm
/approve


Add context support

In react-opal, you can use the React context feature, like this. I can probably do a PR for this.
class ParentComponent
  include React::Component

  # Simply supply the Ruby/Opal type that :foo will be and react-opal will map that to a React PropType automatically
  provide_context(:foo, Fixnum) { params[:foo_value] }

  def render
    present ChildComponent
  end
end

class ChildComponent
  include React::Component

  consume_context(:foo, Fixnum)

  def render
    # will render the :foo_value prop passed into ParentComponent
    div { "foo is #{self.context[:foo]}" }
  end
end

@wied03 Please do!

I would request that we keep the syntax consistent with params and state:
params.foo
state.foo
context.foo
Also I am not clear on what the type is for, does it have the same purpose as the optional typing of params?  If so again I would want to see consistent syntax.

You are required to give React a proptype for context. My code converts the Ruby type into a proptype. You could just give it an Object type for everything but I figured I would try and play nice.

@catmando - As to context.foo vs. context[:foo], I guess you guys changed react.rb after my fork to return a method missing type class instead of a Hash for params to allow params.foo ?

It looks like PropsWrapper is being used for that. Why do the cache? To avoid camel_casing, etc. again? How are you marking the cache dirty when a re-render happens?

context.foo vs. context[:foo] is just syntax sugar right?  it can do the same thing under the hood.
Interesting that React requires a proptype.  So do we want to be consistent and make it optional (and if not provided we will just use Object as you suggest.)
So syntax would be consistent with params
provide_context :foo, type: Bar  or provide_context :foo # equivilent to adding, type: Object

I realized I don't have the initializer in the above, but again would like to make it all consistent with param for ease of learning.

What about the caching question?

I'm leaving that to @ajjahn.   I'm just going from the standpoint that there is no reason why we can't make context.foo work the same as context[:foo].  In fact it should be easier if we wanted to work on it to make context.foo slightly faster than context[:foo].

@catmando - I agree there, my mind moved on to the internal of PropsWrapper

right... so we want to redo the PropsWrapper (and validation too) so that it works for props, and context, plus it work for class level props, and special param types (like observables) without adding burden to the base function if you don't use those features...

And I'm cool with doing a PR for this since I already wrote it in react-opal. I'm mainly curious about the cache question now.

@wied03 That cache was added to address #124 and #125.
@catmando You implemented a fix for the 0.7.x branch (in a different way). When I pulled it into master things had changed, so I brought the spec you wrote along and made it pass.
Those issues are only issues because of the _react_params_conversion, which I feel is a code smell anyway, and not a responsibility of react.
@wied03 We've had discussions on the state and props wrappers. I believe they both could use some TLC. Especially the implementation of state and observables. Too many objects know too much about each other.

@ajjahn - I'm not really as curious about why the cache is there as much as how you know when to clean it out. If you have a re-render of a component, doesn't the cache as is stick around?

okay so if part of the confusion is being caused by _react_params_conversion, then lets wrap up that discussion. ( #96 )

@wied03 The cache for a prop busts if the underlying component's prop has changed. There isn't a need to mark the entire cache as dirty. When the prop is accessed (regardless of renders), the current value of the prop is examined.
Really, the argument could be made that this caching is a concern of the object that responds to _react_params_conversion. It should memoize it's converted value, and return it on subsequent calls. If a new prop arrives that responds to _react_params_conversion, it's value will not yet have been memoized, and the conversion will take place.

I'm guessing that the complexity of the cache is worth it? Was it really that expensive to do the camel case/native conversions on demand?

@wied03 I don't believe camel case/native conversion was the primary reason. The problem here is react.rb has some reactive-record feature envy. Reactive record is counting on react components to deserialize it's models that is is passing as props. I'd like to see serialization/deserialization removed. It belongs elsewhere. So as @catmando suggested, it would be helpful to converge on a consensues in #96.

This issue was moved to reactrb/reactrb#134


movement controls not working in multiple different ways. valve index controllers

Game Version:
OWML Version:
NomaiVR Version:
VR hardware:

every time i try to walk with the index controllers i end up walking in circles, and it seems like all of a sudden i just start jumping randomly. what button is this? none of the buttons im pressing do anything of the sort to make me jump. Not to mention the stuttering. I've tried all the different refresh rates to no avail and it seems practically unplayable with how much stuttering is happening and the lack of being able to move. It's not a grip problem either because I've tried moving just the analog stick and the same running in circle problem happens. I'm on the latest version of everything as of 12/20/20 :)
thanks :)

Closing this as it's a duplicate of #307
Try making a new profile. If that doesn't help, I can't do anything else to help you.


Check the bundle entry resourceType matches requested type in the Retrieve operation results

Open Epic FHIR server returns Operation Outcome with message "Resource request returns no results", rather than empty bundle, when query has 0 results. Causes errors in Query operations due to type mismatch, unless resource type is always explicitly checked.
Suggest enhancement to check the Bundle entry resourceType and only include those that match the requested type in the Retrieve operation results.

Fixed here:
https://github.com/DBCG/cql_engine/commit/7666186b16139eec0b84d08dd0811aba55dc8ab1


Importing to models and WithMappedCells  only first row

Prerequisites
Versions

PHP version:  7.1.7
Laravel version: 5.5
Package version: 3.1

Description

import file use ToModel and WithMappedCells  ,only first row can insert table
Additional Information
I try import  file  use Importing to models and WithMappedCells ,  only first row can insert the table
I dont know how to solve it

Could you please add the code you're using and an example of how your import file is structured? Thanks

I think my usage is wrong.  I had resolve it.   Thanks

Hi all,
What if I want to change the WithHeadingRow names cuz currently, the row['name'] will depend on the text inside of the cell.


Whitelists use of cnp modules for em-hrs-api

https://tools.hmcts.net/jira/browse/EM-3318

Thank you @adusumillipraveen . Seems the PR build failure was complaining about this wrongly. Resolved the issue with the PR build now


PR for addition of SurveyMonkey to the engagement tool

PR for addition of SurveyMonkey to the engagement tool

I see some changes in the Federal Climate Tools and then a reversion. Are the three edits here: Dash, Survey Monkey, and Enscape then?

Thanks David! Yes I intended to add these three edits, but overlooked and had the survey monkey and escape commits pushed under one single PR. I also had another commit for the CEJST tool (https://toolkit.climate.gov/tool/climate-and-economic-justice-screening-tool) but reverted due to my mishandling of the single PR requirement.


Fix CI

I think this should fix the CI matrix and get the modules building.

I think the reason the push CI isn't working is related to this: https://github.com/zmkfirmware/zmk/pull/2262, as this does work for build-use-config yml usage, but this is a good fix in the meantime, thanks again!

Yeah the upstream bug is still present and push builds are still failing unfortunately :/

Ah, that's a shame. At least I believe CI for pulls is actually working now too.


On Events

Hey,
I'd like to know if there's a way to trigger an event when the user reached the bottom of the scroll.
Thanks!

I agree with this feature request, furthermor it should be nice if there is an event for the bottom and for the top.


lolfire

Hello, World!
I would like to see a bonfire colorized terminal output like the one with a rainbow.
What keywords should I use to google it? =)

Color schemes might be an interesting feature to add.
PRs welcome 🍭


C:\Users\oddkj\MyMicroservice>docker push mattisvollen2021/mymicroservice The push refers to repository [docker.io/mattisvollen2021/mymicroservice] 56abcb8bf8e4: Preparing df2baa174a8d: Preparing 7dc39ee34889: Preparing 96282ef47aa7: Preparing 82099e0891ed: Preparing 3cf53a68ca2f: Waiting 7e718b9c0c8c: Waiting denied: requested access to the resource is denied

Problem encountered on https://dotnet.microsoft.com/learn/aspnet/deploy-microservice-tutorial/docker-hub
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

Regards,
Odd K.


Update WebJobs DI configuration

Use RegistrationContext from AddBus to configure WebJob' receivers

You're going to have to explain this, I don't understand what you're trying to change at all.

Just trying to omit using old methods (based on IServiceProvider), and prevent injecting IRegistration explicitly.
Replaced them with Configure method inside receiver

tbh, realized it doesn't make sense, so probably I'll just replace IServiceProvider with IRegistration

Merged


Wrong Point Cost for C-3PO (Republic) Crew

C-3PO (Republic) is listed as 7 points instead of 6.

Fixed in #514


Package setup

Boilerplate package setup, much of it copied directly from pangeo-forge-recipes.
Splitting this into a separate PR from #6 so that the content of #6 is more clearly separated from package boilerplate.

Merging this so the package boilerplate is not mixed in with content of #6.
This should be largely uncontroversial as most of this is copied directly from pangeo-forge-recipes.
If there is anything we need to change, we can do that in subsequent commits.


Gradle build fails when Jenkins passes in non-ASCII env vars.

Description
Gradle build fails when Jenkins passes in non-ASCII env vars to gradle daemon.
Steps to Reproduce (Bug)

Create a PR with a non-ASCII char in the title, or have a non-ASCII char in your git author name.
Allow Jenkins to build the PR.

Expected behavior:
Gradle build is kicked off and runs as expected.
Actual behavior:
Gradle build never starts. Fails 4-5s in due to "gradle daemon disappeared".
Frequency:
100%
Workaround
When indicating a PR is in a Work In Progress status, prepend [WIP] to the title instead of 🚧. You can still continue to use 🚧 in the PR description, as that is not sent to gradle in the env vars.
Additional Information
See https://github.com/gradle/gradle/issues/3117

@schroedingerscode, has this been completed or is it still an open issue?

closing this bc i don't think it is worth fixing


fix for ThunderSoft description

this is CTO & SVP of ThunderSoft, would like to request the following change to "Thunder Software"
please use "ThunderSoft" as the name of the company, not "Thunder Software".
Thundersoft Company offers mobile internet terminal products and operating systems through integrated mobile and IoT terminal solutions.
Website
thundersoft.com
Crunchbase
crunchbase.com/organization/thundersoft-company-limited
LinkedIn
linkedin.com/company/thundersoft
Twitter
@ThunderSoft_Ltd
Headquarters
Beijing, China
Headcount
5000-10,000
Market Cap
$3.59B

Thanks @pczou  - just merged the update.


Change dataURI method to support setting resolution on PNG export

New Pull Request
Change the dataURI method to optionally pass the options object as argument, through which it is now possible to set either a scale or a width in order to scale the exported PNG file.
Fixes #1591
Type of change

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Thanks for creating a PR.
Can you please remove the dist files. Those files should only be updated on a new release.

Hi @junedchhipa, thanks for your reply - I've just removed the dist files as you suggested.

@junedchhipa thanks for merging! Do you plan to release a new version soon?

in a couple of days

When will this be added to the vue component?

Looking forward for the implementation in the vue component as well

@vaspadi @cmfc31
I had the same question and found a way to do it: use exec
this.$apexcharts.exec('chart-id', 'dataURI', { width: 1000 })).imgURI

Hi, is this supported for reactjs library, where I can set the resolution in options ?


Navbar as well as Hero section UI enhancement

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Hey @Anushkabh
The Navbar is overlapping the Hero section and it is very clumsy . I will make sure to change these and make the Hero section more attractive  and even there's icon missing in the buy me I will also add it and make the whole home page responsive for every dimensions.

I will also add some carousels to make it more user friendly. It will make the Hero section more attractive.
Please assign me this , I am GSSoC'24 contributor.
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Fixes #292


[Enhancement]: Validator Client Only Preset

Describe the enhancement
Preset to only install a validator client and set up the node connection (execution & consensus) in the installation.
Also should include the option to remove monitoring.
Dependencies
--
Additional Context
--
Acknowledgment

[X] I have reviewed the existing enhancements and confirm that this suggestion is unique.


Upgrading multilingual site from <IP_ADDRESS> to 8.1.0 - Global Areas is not created

I tried to upgrade a site with multilingual on (2 languages). This does not work! It seem that because the default language is not "www.testsite.dk" but "www.testsite.dk/da/home", the Clobal Areas under C5 8.1.0 does not get created.
Example:
Old site:
http://www.testsite.dk/da/home (danish)
http://www.testsite.dk/en/home (english)
Expected way:
http://www.testsite.dk/ (danish)
http://www.testsite.dk/en/ (english)
Because of the new way it is expected to be, it does not seem to be able to generate the default stack (Global Areas). This way it simply says that "No global areas have been added." and there is no way to create them.

It is also getting in a never ending loop while setting "Redirect home page to default locale.". It seem not to understand that the default home page is on the second level.
I'm not going to roll back - I will rather wait for a fix.

I had the same issues today.

Reported my issues in bugtracker. It seems that there are several related problems with the changing of the base language and global areas :
https://www.concrete5.org/developers/bugs/8-1-0/changing-site-default-locale-in-multilingual-settings-breaks-glo/

Let's see what @aembler has to say about this. It might be a minor issue (but of cause it could be a big one).
I will still wait rolling back the site for a few days if any one would like to have a look.
Site is: http://addons.concrete5.dk

@aembler  Great... Thanks...
I have rolled back the site to <IP_ADDRESS> for the time being. I can't let it stand there not working.
But if you want me to try upgrade again, just give me a message!