chip-tool command failed with "Timeout" error

Problem
After commissioning end device over Thread, subsequent chip-tool commands returned "Timeout" error.
<13:48:33.542> Thread.run:[<IP_ADDRESS>:23:O]pi@raspi-04:~$ ~/connectedhomeip/out/chip-tool/chip-tool colorcontrol read cluster-revision 5244 1
<13:48:33.544> MatterCli.sendCmd:DEBUG: expect found after 1 attempt(s)
<13:48:33.545> MatterCli.sendCmd:Node<<IP_ADDRESS>> issuing cmd<

expecting<(.+@.+)(.)$> timeout<120000> attempt <0
<13:48:33.545> MatterCli.sendCmd:Sent <
, to <<IP_ADDRESS>:23>, regex <(.+@.+)(.)$>, timeout <120000>
<13:48:33.545> MatterCli.sendCmd:[<IP_ADDRESS>:23:I]
<13:48:33.553> Thread.run:[<IP_ADDRESS>:23:O]
<13:48:33.553> Thread.run:[<IP_ADDRESS>:23:O]
<13:48:33.658> Thread.run:[<IP_ADDRESS>:23:O][1649958513.646960][2620:2620] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
<13:48:33.659> Thread.run:[<IP_ADDRESS>:23:O][1649958513.647183][2620:2620] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_device_info.ini
<13:48:33.659> Thread.run:[<IP_ADDRESS>:23:O][1649958513.647513][2620:2620] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_factory.ini
<13:48:33.660> Thread.run:[<IP_ADDRESS>:23:O][1649958513.647658][2620:2620] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_config.ini
<13:48:33.661> Thread.run:[<IP_ADDRESS>:23:O][1649958513.647758][2620:2620] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_counters.ini
<13:48:33.661> Thread.run:[<IP_ADDRESS>:23:O][1649958513.648034][2620:2620] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-R9Phbl)
<13:48:33.662> Thread.run:[<IP_ADDRESS>:23:O][1649958513.648657][2620:2620] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
<13:48:33.662> Thread.run:[<IP_ADDRESS>:23:O][1649958513.648703][2620:2620] CHIP:DL: NVS set: chip-counters/reboot-count = 2 (0x2)
<13:48:33.662> Thread.run:[<IP_ADDRESS>:23:O][1649958513.649209][2620:2620] CHIP:DL: Got Ethernet interface: eth0
<13:48:33.663> Thread.run:[<IP_ADDRESS>:23:O][1649958513.649518][2620:2620] CHIP:DL: Found the primary Ethernet interface:eth0
<13:48:33.663> Thread.run:[<IP_ADDRESS>:23:O][1649958513.649842][2620:2620] CHIP:DL: Got WiFi interface: wlan0
<13:48:33.663> Thread.run:[<IP_ADDRESS>:23:O][1649958513.651614][2620:2620] CHIP:DL: Found the primary WiFi interface:wlan0
<13:48:33.663> Thread.run:[<IP_ADDRESS>:23:O][1649958513.651719][2620:2620] CHIP:IN: UDP::Init bind&listen port=0
<13:48:33.663> Thread.run:[<IP_ADDRESS>:23:O][1649958513.651843][2620:2620] CHIP:IN: UDP::Init bound to port=55859
<13:48:33.663> Thread.run:[<IP_ADDRESS>:23:O][1649958513.651872][2620:2620] CHIP:IN: UDP::Init bind&listen port=0
<13:48:33.664> Thread.run:[<IP_ADDRESS>:23:O][1649958513.651969][2620:2620] CHIP:IN: UDP::Init bound to port=41133
<13:48:33.664> Thread.run:[<IP_ADDRESS>:23:O][1649958513.651994][2620:2620] CHIP:IN: BLEBase::Init - setting/overriding transport
<13:48:33.664> Thread.run:[<IP_ADDRESS>:23:O][1649958513.652017][2620:2620] CHIP:IN: TransportMgr initialized
<13:48:33.664> Thread.run:[<IP_ADDRESS>:23:O][1649958513.652054][2620:2620] CHIP:DIS: Init fabric pairing table with server storage
<13:48:33.664> Thread.run:[<IP_ADDRESS>:23:O][1649958513.652193][2620:2620] CHIP:IN: Loading from storage for fabric index 1
<13:48:33.665> Thread.run:[<IP_ADDRESS>:23:O][1649958513.654928][2620:2620] CHIP:IN: Loading from storage for fabric index 2
<13:48:33.665> Thread.run:[<IP_ADDRESS>:23:O][1649958513.655570][2620:2620] CHIP:IN: Loading from storage for fabric index 3
<13:48:33.665> Thread.run:[<IP_ADDRESS>:23:O][1649958513.656160][2620:2620] CHIP:DIS: Add fabric pairing table delegate
<13:48:33.665> Thread.run:[<IP_ADDRESS>:23:O][1649958513.656454][2620:2620] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-7Zxpqi)
<13:48:33.665> Thread.run:[<IP_ADDRESS>:23:O][1649958513.657053][2620:2620] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
<13:48:33.665> Thread.run:[<IP_ADDRESS>:23:O][1649958513.657105][2620:2620] CHIP:DL: NVS set: chip-counters/GlobalMCTR = 2000 (0x7D0)
<13:48:33.666> Thread.run:[<IP_ADDRESS>:23:O][1649958513.660495][2620:2620] CHIP:ZCL: Using ZAP configuration...
<13:48:33.666> Thread.run:[<IP_ADDRESS>:23:O][1649958513.663864][2620:2620] CHIP:DL: MDNS failed to join multicast group on wpan0 for address type IPv4: ../../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:772: Inet Error 0x00000110: Address not found
<13:48:33.666> Thread.run:[<IP_ADDRESS>:23:O][1649958513.664177][2620:2620] CHIP:CTL: System State Initialized...
<13:48:33.666> Thread.run:[<IP_ADDRESS>:23:O][1649958513.664243][2620:2620] CHIP:CTL: Setting attestation nonce to random value
<13:48:33.666> Thread.run:[<IP_ADDRESS>:23:O][1649958513.664309][2620:2620] CHIP:CTL: Setting CSR nonce to random value
<13:48:33.667> Thread.run:[<IP_ADDRESS>:23:O][1649958513.664390][2620:2620] CHIP:IN: UDP::Init bind&listen port=5550
<13:48:33.667> Thread.run:[<IP_ADDRESS>:23:O][1649958513.664478][2620:2620] CHIP:IN: UDP::Init bound to port=5550
<13:48:33.667> Thread.run:[<IP_ADDRESS>:23:O][1649958513.664507][2620:2620] CHIP:IN: UDP::Init bind&listen port=5550
<13:48:33.667> Thread.run:[<IP_ADDRESS>:23:O][1649958513.664589][2620:2620] CHIP:IN: UDP::Init bound to port=5550
<13:48:33.667> Thread.run:[<IP_ADDRESS>:23:O][1649958513.664614][2620:2620] CHIP:IN: TransportMgr initialized
<13:48:33.668> Thread.run:[<IP_ADDRESS>:23:O][1649958513.664686][2620:2620] CHIP:CTL: Setting attestation nonce to random value
<13:48:33.668> Thread.run:[<IP_ADDRESS>:23:O][1649958513.664738][2620:2620] CHIP:CTL: Setting CSR nonce to random value
<13:48:33.668> Thread.run:[<IP_ADDRESS>:23:O][1649958513.665732][2620:2620] CHIP:CTL: Generating NOC
<13:48:33.668> Thread.run:[<IP_ADDRESS>:23:O][1649958513.666748][2620:2620] CHIP:DIS: Verifying the received credentials
<13:48:33.668> Thread.run:[<IP_ADDRESS>:23:O][1649958513.668711][2620:2620] CHIP:DIS: Added new fabric at index: 1, Initialized: 1
<13:48:33.669> Thread.run:[<IP_ADDRESS>:23:O][1649958513.668850][2620:2620] CHIP:DIS: Assigned compressed fabric ID: 0x9CBA16EBFF456F49, node ID: 0x000000000001B669
<13:48:33.669> Thread.run:[<IP_ADDRESS>:23:O][1649958513.668880][2620:2620] CHIP:CTL: Joined the fabric at index 1. Compressed fabric ID is: 0x9CBA16EBFF456F49
<13:48:33.669> Thread.run:[<IP_ADDRESS>:23:O][1649958513.668925][2620:2620] CHIP:IN: UDP::Init bind&listen port=5550
<13:48:33.669> Thread.run:[<IP_ADDRESS>:23:O][1649958513.669049][2620:2620] CHIP:IN: UDP::Init bound to port=5550
<13:48:33.669> Thread.run:[<IP_ADDRESS>:23:O][1649958513.669076][2620:2620] CHIP:IN: UDP::Init bind&listen port=5550
<13:48:33.670> Thread.run:[<IP_ADDRESS>:23:O][1649958513.669162][2620:2620] CHIP:IN: UDP::Init bound to port=5550
<13:48:33.670> Thread.run:[<IP_ADDRESS>:23:O][1649958513.669187][2620:2620] CHIP:IN: TransportMgr initialized
<13:48:33.670> Thread.run:[<IP_ADDRESS>:23:O][1649958513.669284][2620:2620] CHIP:CTL: Setting attestation nonce to random value
<13:48:33.670> Thread.run:[<IP_ADDRESS>:23:O][1649958513.669345][2620:2620] CHIP:CTL: Setting CSR nonce to random value
<13:48:33.670> Thread.run:[<IP_ADDRESS>:23:O][1649958513.670293][2620:2620] CHIP:CTL: Generating NOC
<13:48:33.671> Thread.run:[<IP_ADDRESS>:23:O][1649958513.671258][2620:2620] CHIP:DIS: Verifying the received credentials
<13:48:33.671> Thread.run:[<IP_ADDRESS>:23:O][1649958513.673047][2620:2620] CHIP:DIS: Added new fabric at index: 2, Initialized: 1
<13:48:33.671> Thread.run:[<IP_ADDRESS>:23:O][1649958513.673077][2620:2620] CHIP:DIS: Assigned compressed fabric ID: 0x17BBDE630F5825AD, node ID: 0x000000000001B669
<13:48:33.671> Thread.run:[<IP_ADDRESS>:23:O][1649958513.673101][2620:2620] CHIP:CTL: Joined the fabric at index 2. Compressed fabric ID is: 0x17BBDE630F5825AD
<13:48:33.672> Thread.run:[<IP_ADDRESS>:23:O][1649958513.673139][2620:2620] CHIP:IN: UDP::Init bind&listen port=5550
<13:48:33.672> Thread.run:[<IP_ADDRESS>:23:O][1649958513.673249][2620:2620] CHIP:IN: UDP::Init bound to port=5550
<13:48:33.672> Thread.run:[<IP_ADDRESS>:23:O][1649958513.673275][2620:2620] CHIP:IN: UDP::Init bind&listen port=5550
<13:48:33.672> Thread.run:[<IP_ADDRESS>:23:O][1649958513.673354][2620:2620] CHIP:IN: UDP::Init bound to port=5550
<13:48:33.673> Thread.run:[<IP_ADDRESS>:23:O][1649958513.673379][2620:2620] CHIP:IN: TransportMgr initialized
<13:48:33.673> Thread.run:[<IP_ADDRESS>:23:O][1649958513.673467][2620:2620] CHIP:CTL: Setting attestation nonce to random value
<13:48:33.673> Thread.run:[<IP_ADDRESS>:23:O][1649958513.673523][2620:2620] CHIP:CTL: Setting CSR nonce to random value
<13:48:33.724> Thread.run:[<IP_ADDRESS>:23:O][1649958513.674637][2620:2620] CHIP:CTL: Generating NOC
<13:48:33.724> Thread.run:[<IP_ADDRESS>:23:O][1649958513.675758][2620:2620] CHIP:DIS: Verifying the received credentials
<13:48:33.724> Thread.run:[<IP_ADDRESS>:23:O][1649958513.677609][2620:2620] CHIP:DIS: Added new fabric at index: 3, Initialized: 1
<13:48:33.725> Thread.run:[<IP_ADDRESS>:23:O][1649958513.677643][2620:2620] CHIP:DIS: Assigned compressed fabric ID: 0x45A28E6E1DE42FBF, node ID: 0x000000000001B669
<13:48:33.725> Thread.run:[<IP_ADDRESS>:23:O][1649958513.677666][2620:2620] CHIP:CTL: Joined the fabric at index 3. Compressed fabric ID is: 0x45A28E6E1DE42FBF
<13:48:33.725> Thread.run:[<IP_ADDRESS>:23:O][1649958513.677710][2620:2620] CHIP:IN: UDP::Init bind&listen port=5550
<13:48:33.725> Thread.run:[<IP_ADDRESS>:23:O][1649958513.677830][2620:2620] CHIP:IN: UDP::Init bound to port=5550
<13:48:33.725> Thread.run:[<IP_ADDRESS>:23:O][1649958513.677856][2620:2620] CHIP:IN: UDP::Init bind&listen port=5550
<13:48:33.726> Thread.run:[<IP_ADDRESS>:23:O][1649958513.678016][2620:2620] CHIP:IN: UDP::Init bound to port=5550
<13:48:33.726> Thread.run:[<IP_ADDRESS>:23:O][1649958513.678041][2620:2620] CHIP:IN: TransportMgr initialized
<13:48:33.726> Thread.run:[<IP_ADDRESS>:23:O][1649958513.714273][2620:2625] CHIP:DL: CHIP task running
<13:48:33.726> Thread.run:[<IP_ADDRESS>:23:O][1649958513.714412][2620:2625] CHIP:TOO: Sending command to node 0x147c
<13:48:33.727> Thread.run:[<IP_ADDRESS>:23:O][1649958513.714446][2620:2625] CHIP:CSM: FindOrEstablishSession: PeerId = 9CBA16EBFF456F49:000000000000147C
<13:48:33.727> Thread.run:[<IP_ADDRESS>:23:O][1649958513.714471][2620:2625] CHIP:CSM: FindOrEstablishSession: No existing session found
<13:48:33.727> Thread.run:[<IP_ADDRESS>:23:O][1649958513.715704][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:33.727> Thread.run:[<IP_ADDRESS>:23:O][1649958513.715889][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:33.728> Thread.run:[<IP_ADDRESS>:23:O][1649958513.716372][2620:2625] CHIP:DIS: Lookup clearing interface for non LL address
<13:48:33.728> Thread.run:[<IP_ADDRESS>:23:O][1649958513.716406][2620:2625] CHIP:DIS: UDP:[fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72%eth0]:5540: new best score: 6
<13:48:33.728> Thread.run:[<IP_ADDRESS>:23:O][1649958513.716427][2620:2625] CHIP:DIS: Checking node lookup status after 2 ms
<13:48:33.728> Thread.run:[<IP_ADDRESS>:23:O][1649958513.716448][2620:2625] CHIP:DIS: Keeping DNSSD lookup active
<13:48:33.728> Thread.run:[<IP_ADDRESS>:23:O][1649958513.716604][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:33.729> Thread.run:[<IP_ADDRESS>:23:O][1649958513.716628][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:33.729> Thread.run:[<IP_ADDRESS>:23:O][1649958513.716657][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:33.729> Thread.run:[<IP_ADDRESS>:23:O][1649958513.716980][2620:2625] CHIP:DIS: UDP:[fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72%eth0]:5540: score has not improved: 6
<13:48:33.729> Thread.run:[<IP_ADDRESS>:23:O][1649958513.717007][2620:2625] CHIP:DIS: Checking node lookup status after 3 ms
<13:48:33.730> Thread.run:[<IP_ADDRESS>:23:O][1649958513.717033][2620:2625] CHIP:DIS: Keeping DNSSD lookup active
<13:48:33.730> Thread.run:[<IP_ADDRESS>:23:O][1649958513.717146][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:33.730> Thread.run:[<IP_ADDRESS>:23:O][1649958513.717169][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:33.730> Thread.run:[<IP_ADDRESS>:23:O][1649958513.717191][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:33.740> Thread.run:[<IP_ADDRESS>:23:O][1649958513.717479][2620:2625] CHIP:DIS: UDP:[fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72%wlan0]:5540: score has not improved: 6
<13:48:33.740> Thread.run:[<IP_ADDRESS>:23:O][1649958513.717504][2620:2625] CHIP:DIS: Checking node lookup status after 3 ms
<13:48:33.741> Thread.run:[<IP_ADDRESS>:23:O][1649958513.717521][2620:2625] CHIP:DIS: Keeping DNSSD lookup active
<13:48:33.741> Thread.run:[<IP_ADDRESS>:23:O][1649958513.717646][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:33.741> Thread.run:[<IP_ADDRESS>:23:O][1649958513.717670][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:33.741> Thread.run:[<IP_ADDRESS>:23:O][1649958513.717697][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:33.742> Thread.run:[<IP_ADDRESS>:23:O][1649958513.718033][2620:2625] CHIP:DIS: UDP:[fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72%wlan0]:5540: score has not improved: 6
<13:48:33.742> Thread.run:[<IP_ADDRESS>:23:O][1649958513.718061][2620:2625] CHIP:DIS: Checking node lookup status after 4 ms
<13:48:33.742> Thread.run:[<IP_ADDRESS>:23:O][1649958513.718088][2620:2625] CHIP:DIS: Keeping DNSSD lookup active
<13:48:33.752> Thread.run:[<IP_ADDRESS>:23:O][1649958513.749533][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:33.753> Thread.run:[<IP_ADDRESS>:23:O][1649958513.749617][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:33.754> Thread.run:[<IP_ADDRESS>:23:O][1649958513.749677][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:33.754> Thread.run:[<IP_ADDRESS>:23:O][1649958513.750638][2620:2625] CHIP:DIS: UDP:[fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72%eth0]:5540: score has not improved: 6
<13:48:33.755> Thread.run:[<IP_ADDRESS>:23:O][1649958513.751180][2620:2625] CHIP:DIS: Checking node lookup status after 37 ms
<13:48:33.756> Thread.run:[<IP_ADDRESS>:23:O][1649958513.751465][2620:2625] CHIP:DIS: Keeping DNSSD lookup active
<13:48:33.756> Thread.run:[<IP_ADDRESS>:23:O][1649958513.751743][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:33.757> Thread.run:[<IP_ADDRESS>:23:O][1649958513.751806][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:33.757> Thread.run:[<IP_ADDRESS>:23:O][1649958513.751935][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:33.757> Thread.run:[<IP_ADDRESS>:23:O][1649958513.752820][2620:2625] CHIP:DIS: UDP:[fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72%eth0]:5540: score has not improved: 6
<13:48:33.757> Thread.run:[<IP_ADDRESS>:23:O][1649958513.752895][2620:2625] CHIP:DIS: Checking node lookup status after 39 ms
<13:48:33.758> Thread.run:[<IP_ADDRESS>:23:O][1649958513.752948][2620:2625] CHIP:DIS: Keeping DNSSD lookup active
<13:48:33.758> Thread.run:[<IP_ADDRESS>:23:O][1649958513.753192][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:33.758> Thread.run:[<IP_ADDRESS>:23:O][1649958513.753251][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:33.758> Thread.run:[<IP_ADDRESS>:23:O][1649958513.753313][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:33.759> Thread.run:[<IP_ADDRESS>:23:O][1649958513.754119][2620:2625] CHIP:DIS: UDP:[fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72%eth0]:5540: score has not improved: 6
<13:48:33.759> Thread.run:[<IP_ADDRESS>:23:O][1649958513.754183][2620:2625] CHIP:DIS: Checking node lookup status after 40 ms
<13:48:33.759> Thread.run:[<IP_ADDRESS>:23:O][1649958513.754230][2620:2625] CHIP:DIS: Keeping DNSSD lookup active
<13:48:33.760> Thread.run:[<IP_ADDRESS>:23:O][1649958513.754615][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:33.760> Thread.run:[<IP_ADDRESS>:23:O][1649958513.754676][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:33.760> Thread.run:[<IP_ADDRESS>:23:O][1649958513.754735][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:33.760> Thread.run:[<IP_ADDRESS>:23:O][1649958513.755453][2620:2625] CHIP:DIS: UDP:[fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72%wlan0]:5540: score has not improved: 6
<13:48:33.761> Thread.run:[<IP_ADDRESS>:23:O][1649958513.755514][2620:2625] CHIP:DIS: Checking node lookup status after 41 ms
<13:48:33.761> Thread.run:[<IP_ADDRESS>:23:O][1649958513.755561][2620:2625] CHIP:DIS: Keeping DNSSD lookup active
<13:48:33.761> Thread.run:[<IP_ADDRESS>:23:O][1649958513.755766][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:33.761> Thread.run:[<IP_ADDRESS>:23:O][1649958513.755824][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:33.762> Thread.run:[<IP_ADDRESS>:23:O][1649958513.755883][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:33.764> Thread.run:[<IP_ADDRESS>:23:O][1649958513.756572][2620:2625] CHIP:DIS: UDP:[fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72%eth0]:5540: score has not improved: 6
<13:48:33.764> Thread.run:[<IP_ADDRESS>:23:O][1649958513.756632][2620:2625] CHIP:DIS: Checking node lookup status after 42 ms
<13:48:33.764> Thread.run:[<IP_ADDRESS>:23:O][1649958513.756679][2620:2625] CHIP:DIS: Keeping DNSSD lookup active
<13:48:33.765> Thread.run:[<IP_ADDRESS>:23:O][1649958513.756877][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:33.765> Thread.run:[<IP_ADDRESS>:23:O][1649958513.756936][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:33.765> Thread.run:[<IP_ADDRESS>:23:O][1649958513.756994][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:33.765> Thread.run:[<IP_ADDRESS>:23:O][1649958513.757711][2620:2625] CHIP:DIS: UDP:[fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72%wlan0]:5540: score has not improved: 6
<13:48:33.766> Thread.run:[<IP_ADDRESS>:23:O][1649958513.757771][2620:2625] CHIP:DIS: Checking node lookup status after 43 ms
<13:48:33.766> Thread.run:[<IP_ADDRESS>:23:O][1649958513.757819][2620:2625] CHIP:DIS: Keeping DNSSD lookup active
<13:48:33.766> Thread.run:[<IP_ADDRESS>:23:O][1649958513.758075][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:33.767> Thread.run:[<IP_ADDRESS>:23:O][1649958513.758133][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:33.767> Thread.run:[<IP_ADDRESS>:23:O][1649958513.758190][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:33.768> Thread.run:[<IP_ADDRESS>:23:O][1649958513.758880][2620:2625] CHIP:DIS: UDP:[fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72%eth0]:5540: score has not improved: 6
<13:48:33.769> Thread.run:[<IP_ADDRESS>:23:O][1649958513.759110][2620:2625] CHIP:DIS: Checking node lookup status after 45 ms
<13:48:33.770> Thread.run:[<IP_ADDRESS>:23:O][1649958513.759163][2620:2625] CHIP:DIS: Keeping DNSSD lookup active
<13:48:33.770> Thread.run:[<IP_ADDRESS>:23:O][1649958513.759367][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:33.770> Thread.run:[<IP_ADDRESS>:23:O][1649958513.759423][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:33.771> Thread.run:[<IP_ADDRESS>:23:O][1649958513.759481][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:33.771> Thread.run:[<IP_ADDRESS>:23:O][1649958513.760178][2620:2625] CHIP:DIS: UDP:[fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72%wlan0]:5540: score has not improved: 6
<13:48:33.771> Thread.run:[<IP_ADDRESS>:23:O][1649958513.760267][2620:2625] CHIP:DIS: Checking node lookup status after 46 ms
<13:48:33.772> Thread.run:[<IP_ADDRESS>:23:O][1649958513.760316][2620:2625] CHIP:DIS: Keeping DNSSD lookup active
<13:48:33.772> Thread.run:[<IP_ADDRESS>:23:O][1649958513.760519][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:33.772> Thread.run:[<IP_ADDRESS>:23:O][1649958513.760575][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:33.773> Thread.run:[<IP_ADDRESS>:23:O][1649958513.760633][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:33.773> Thread.run:[<IP_ADDRESS>:23:O][1649958513.761081][2620:2625] CHIP:DIS: UDP:[fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72%eth0]:5540: score has not improved: 6
<13:48:33.773> Thread.run:[<IP_ADDRESS>:23:O][1649958513.761107][2620:2625] CHIP:DIS: Checking node lookup status after 47 ms
<13:48:33.773> Thread.run:[<IP_ADDRESS>:23:O][1649958513.761126][2620:2625] CHIP:DIS: Keeping DNSSD lookup active
<13:48:33.774> Thread.run:[<IP_ADDRESS>:23:O][1649958513.761210][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:33.774> Thread.run:[<IP_ADDRESS>:23:O][1649958513.761233][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:33.774> Thread.run:[<IP_ADDRESS>:23:O][1649958513.761256][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:33.775> Thread.run:[<IP_ADDRESS>:23:O][1649958513.761538][2620:2625] CHIP:DIS: UDP:[fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72%eth0]:5540: score has not improved: 6
<13:48:33.775> Thread.run:[<IP_ADDRESS>:23:O][1649958513.761562][2620:2625] CHIP:DIS: Checking node lookup status after 47 ms
<13:48:33.775> Thread.run:[<IP_ADDRESS>:23:O][1649958513.761581][2620:2625] CHIP:DIS: Keeping DNSSD lookup active
<13:48:33.776> Thread.run:[<IP_ADDRESS>:23:O][1649958513.761720][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:33.776> Thread.run:[<IP_ADDRESS>:23:O][1649958513.761744][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:33.776> Thread.run:[<IP_ADDRESS>:23:O][1649958513.761766][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:33.777> Thread.run:[<IP_ADDRESS>:23:O][1649958513.762069][2620:2625] CHIP:DIS: UDP:[fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72%wlan0]:5540: score has not improved: 6
<13:48:33.777> Thread.run:[<IP_ADDRESS>:23:O][1649958513.762095][2620:2625] CHIP:DIS: Checking node lookup status after 48 ms
<13:48:33.777> Thread.run:[<IP_ADDRESS>:23:O][1649958513.762114][2620:2625] CHIP:DIS: Keeping DNSSD lookup active
<13:48:33.778> Thread.run:[<IP_ADDRESS>:23:O][1649958513.762197][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:33.778> Thread.run:[<IP_ADDRESS>:23:O][1649958513.762231][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:33.778> Thread.run:[<IP_ADDRESS>:23:O][1649958513.762254][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:33.779> Thread.run:[<IP_ADDRESS>:23:O][1649958513.762533][2620:2625] CHIP:DIS: UDP:[fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72%wlan0]:5540: score has not improved: 6
<13:48:33.779> Thread.run:[<IP_ADDRESS>:23:O][1649958513.762557][2620:2625] CHIP:DIS: Checking node lookup status after 48 ms
<13:48:33.779> Thread.run:[<IP_ADDRESS>:23:O][1649958513.762576][2620:2625] CHIP:DIS: Keeping DNSSD lookup active
<13:48:33.780> Thread.run:[<IP_ADDRESS>:23:O][1649958513.762656][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:33.780> Thread.run:[<IP_ADDRESS>:23:O][1649958513.762678][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:33.780> Thread.run:[<IP_ADDRESS>:23:O][1649958513.762701][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:33.800> Thread.run:[<IP_ADDRESS>:23:O][1649958513.762994][2620:2625] CHIP:DIS: UDP:[fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72%wlan0]:5540: score has not improved: 6
<13:48:33.800> Thread.run:[<IP_ADDRESS>:23:O][1649958513.763020][2620:2625] CHIP:DIS: Checking node lookup status after 49 ms
<13:48:33.801> Thread.run:[<IP_ADDRESS>:23:O][1649958513.763038][2620:2625] CHIP:DIS: Keeping DNSSD lookup active
<13:48:33.801> Thread.run:[<IP_ADDRESS>:23:O][1649958513.763122][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:33.801> Thread.run:[<IP_ADDRESS>:23:O][1649958513.763145][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:33.802> Thread.run:[<IP_ADDRESS>:23:O][1649958513.763168][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:33.802> Thread.run:[<IP_ADDRESS>:23:O][1649958513.763448][2620:2625] CHIP:DIS: UDP:[fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72%wlan0]:5540: score has not improved: 6
<13:48:33.802> Thread.run:[<IP_ADDRESS>:23:O][1649958513.763472][2620:2625] CHIP:DIS: Checking node lookup status after 49 ms
<13:48:33.803> Thread.run:[<IP_ADDRESS>:23:O][1649958513.763490][2620:2625] CHIP:DIS: Keeping DNSSD lookup active
<13:48:33.909> Thread.run:[<IP_ADDRESS>:23:O][1649958513.914884][2620:2625] CHIP:DIS: Checking node lookup status after 201 ms
<13:48:33.909> Thread.run:[<IP_ADDRESS>:23:O][1649958513.914990][2620:2625] CHIP:CTL: Updating device address to UDP:[fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540 while in state 1
<13:48:33.962> Thread.run:[<IP_ADDRESS>:23:O][1649958513.915045][2620:2625] CHIP:CTL: OperationalDeviceProxy[9CBA16EBFF456F49:000000000000147C]: State change 1 --> 2
<13:48:33.962> Thread.run:[<IP_ADDRESS>:23:O][1649958513.915387][2620:2625] CHIP:SC: Establishing CASE session to UDP:[fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:33.962> Thread.run:[<IP_ADDRESS>:23:O][1649958513.916644][2620:2625] CHIP:SC: RecoverInitiatorIpk: GroupDataProvider 0xaaaaf56aeff0, Got IPK for FabricIndex 1
<13:48:33.962> Thread.run:[<IP_ADDRESS>:23:O][1649958513.916725][2620:2625] CHIP:SC: 0x1e, 0xc8, 0xce, 0x2e, 0x59, 0x46, 0xa8, 0x6f,
<13:48:33.963> Thread.run:[<IP_ADDRESS>:23:O][1649958513.916784][2620:2625] CHIP:SC: 0x4c, 0x87, 0xd5, 0x3d, 0x51, 0x51, 0x09, 0x69,
<13:48:33.963> Thread.run:[<IP_ADDRESS>:23:O][1649958513.917017][2620:2625] CHIP:SC: Including MRP parameters
<13:48:33.963> Thread.run:[<IP_ADDRESS>:23:O][1649958513.917149][2620:2625] CHIP:IN: Prepared unauthenticated message 0xaaaaf5ac86a8 to 0x0000000000000000 (0)  of type 0x30 and protocolId (0, 0) on exchange 60012i with MessageCounter:1712433032.
<13:48:33.964> Thread.run:[<IP_ADDRESS>:23:O][1649958513.917272][2620:2625] CHIP:IN: Sending unauthenticated msg 0xaaaaf5ac86a8 with MessageCounter:1712433032 to 0x0000000000000000 at monotonic time:<PHONE_NUMBER>083F8B msec
<13:48:33.964> Thread.run:[<IP_ADDRESS>:23:O][1649958513.917607][2620:2625] CHIP:SC: Sent Sigma1 msg
<13:48:33.965> Thread.run:[<IP_ADDRESS>:23:O][1649958513.917673][2620:2625] CHIP:CTL: OperationalDeviceProxy[9CBA16EBFF456F49:000000000000147C]: State change 2 --> 3
<13:48:33.965> Thread.run:[<IP_ADDRESS>:23:O][1649958513.917738][2620:2625] CHIP:DIS: Discovery does not require any more timeouts
[<IP_ADDRESS>:4902] [WSTK> WSTK> ]
<13:48:37.451> Thread.run:[<IP_ADDRESS>:4902:O]WSTK> WSTK>
<13:48:37.455> Thread.run:[<IP_ADDRESS>:4901:O]
<13:48:37.752> Thread.run:[<IP_ADDRESS>:23:O][1649958517.753097][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:37.753> Thread.run:[<IP_ADDRESS>:23:O][1649958517.753292][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:37.754> Thread.run:[<IP_ADDRESS>:23:O][1649958517.753419][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:37.754> Thread.run:[<IP_ADDRESS>:23:O][1649958517.753538][2620:2625] CHIP:DIS: Discovery does not require any more timeouts
<13:48:37.755> Thread.run:[<IP_ADDRESS>:23:O][1649958517.753803][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:37.756> Thread.run:[<IP_ADDRESS>:23:O][1649958517.753963][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:37.757> Thread.run:[<IP_ADDRESS>:23:O][1649958517.754109][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:37.758> Thread.run:[<IP_ADDRESS>:23:O][1649958517.754220][2620:2625] CHIP:DIS: Discovery does not require any more timeouts
<13:48:37.758> Thread.run:[<IP_ADDRESS>:23:O][1649958517.754474][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:37.759> Thread.run:[<IP_ADDRESS>:23:O][1649958517.754534][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:37.760> Thread.run:[<IP_ADDRESS>:23:O][1649958517.754655][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:37.761> Thread.run:[<IP_ADDRESS>:23:O][1649958517.754766][2620:2625] CHIP:DIS: Discovery does not require any more timeouts
<13:48:37.761> Thread.run:[<IP_ADDRESS>:23:O][1649958517.755144][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:37.762> Thread.run:[<IP_ADDRESS>:23:O][1649958517.755203][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:37.763> Thread.run:[<IP_ADDRESS>:23:O][1649958517.755323][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:37.763> Thread.run:[<IP_ADDRESS>:23:O][1649958517.755431][2620:2625] CHIP:DIS: Discovery does not require any more timeouts
<13:48:37.764> Thread.run:[<IP_ADDRESS>:23:O][1649958517.755678][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:37.765> Thread.run:[<IP_ADDRESS>:23:O][1649958517.755736][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:37.766> Thread.run:[<IP_ADDRESS>:23:O][1649958517.755855][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:37.767> Thread.run:[<IP_ADDRESS>:23:O][1649958517.755964][2620:2625] CHIP:DIS: Discovery does not require any more timeouts
<13:48:37.768> Thread.run:[<IP_ADDRESS>:23:O][1649958517.756260][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:37.768> Thread.run:[<IP_ADDRESS>:23:O][1649958517.756320][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:37.769> Thread.run:[<IP_ADDRESS>:23:O][1649958517.756439][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:37.770> Thread.run:[<IP_ADDRESS>:23:O][1649958517.756547][2620:2625] CHIP:DIS: Discovery does not require any more timeouts
<13:48:37.770> Thread.run:[<IP_ADDRESS>:23:O][1649958517.756792][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:37.771> Thread.run:[<IP_ADDRESS>:23:O][1649958517.756852][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:37.772> Thread.run:[<IP_ADDRESS>:23:O][1649958517.756913][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:37.772> Thread.run:[<IP_ADDRESS>:23:O][1649958517.756993][2620:2625] CHIP:DIS: Discovery does not require any more timeouts
<13:48:37.773> Thread.run:[<IP_ADDRESS>:23:O][1649958517.757189][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:37.774> Thread.run:[<IP_ADDRESS>:23:O][1649958517.757247][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:37.774> Thread.run:[<IP_ADDRESS>:23:O][1649958517.757307][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:37.775> Thread.run:[<IP_ADDRESS>:23:O][1649958517.757364][2620:2625] CHIP:DIS: Discovery does not require any more timeouts
<13:48:37.775> Thread.run:[<IP_ADDRESS>:23:O][1649958517.757550][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:37.776> Thread.run:[<IP_ADDRESS>:23:O][1649958517.757607][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:37.776> Thread.run:[<IP_ADDRESS>:23:O][1649958517.757664][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:37.777> Thread.run:[<IP_ADDRESS>:23:O][1649958517.757716][2620:2625] CHIP:DIS: Discovery does not require any more timeouts
<13:48:37.778> Thread.run:[<IP_ADDRESS>:23:O][1649958517.757947][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:37.778> Thread.run:[<IP_ADDRESS>:23:O][1649958517.758005][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:37.779> Thread.run:[<IP_ADDRESS>:23:O][1649958517.758061][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:37.779> Thread.run:[<IP_ADDRESS>:23:O][1649958517.758112][2620:2625] CHIP:DIS: Discovery does not require any more timeouts
<13:48:37.780> Thread.run:[<IP_ADDRESS>:23:O][1649958517.758440][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:37.780> Thread.run:[<IP_ADDRESS>:23:O][1649958517.758499][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:37.781> Thread.run:[<IP_ADDRESS>:23:O][1649958517.758556][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:37.782> Thread.run:[<IP_ADDRESS>:23:O][1649958517.758608][2620:2625] CHIP:DIS: Discovery does not require any more timeouts
<13:48:37.782> Thread.run:[<IP_ADDRESS>:23:O][1649958517.758792][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:37.783> Thread.run:[<IP_ADDRESS>:23:O][1649958517.758848][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:37.783> Thread.run:[<IP_ADDRESS>:23:O][1649958517.758903][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:37.784> Thread.run:[<IP_ADDRESS>:23:O][1649958517.758955][2620:2625] CHIP:DIS: Discovery does not require any more timeouts
<13:48:37.805> Thread.run:[<IP_ADDRESS>:23:O][1649958517.759139][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:37.806> Thread.run:[<IP_ADDRESS>:23:O][1649958517.759197][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:37.806> Thread.run:[<IP_ADDRESS>:23:O][1649958517.759276][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:37.807> Thread.run:[<IP_ADDRESS>:23:O][1649958517.759331][2620:2625] CHIP:DIS: Discovery does not require any more timeouts
<13:48:37.807> Thread.run:[<IP_ADDRESS>:23:O][1649958517.759515][2620:2625] CHIP:DIS: Discovered node without a pending query
<13:48:37.808> Thread.run:[<IP_ADDRESS>:23:O][1649958517.759572][2620:2625] CHIP:DIS: Node ID resolved for 9CBA16EBFF456F49:000000000000147C
<13:48:37.808> Thread.run:[<IP_ADDRESS>:23:O][1649958517.759628][2620:2625] CHIP:DIS:     Addr 0: [fdbb:ac76:3599:5f42:cd25:b7d7:90b8:cd72]:5540
<13:48:37.809> Thread.run:[<IP_ADDRESS>:23:O][1649958517.759679][2620:2625] CHIP:DIS: Discovery does not require any more timeouts
<13:48:39.518> Thread.run:[<IP_ADDRESS>:23:O][1649958519.523271][2620:2625] CHIP:EM: Retransmitting MessageCounter:1712433032 on exchange 60012i Send Cnt 0
<13:48:39.573> Thread.run:[<IP_ADDRESS>:23:O][1649958519.523466][2620:2625] CHIP:IN: Sending unauthenticated msg 0xaaaaf5ac86a8 with MessageCounter:1712433032 to 0x0000000000000000 at monotonic time:<PHONE_NUMBER>085571 msec
<13:48:39.576> Thread.run:[<IP_ADDRESS>:23:O][1649958519.523702][2620:2625] CHIP:EM: Crit-err ../../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000065: Network is unreachable when sending CHIP MessageCounter:1712433032 on exchange 60012i, send tries: 0
<13:49:03.709> Thread.run:[<IP_ADDRESS>:23:O][1649958543.714793][2620:2620] CHIP:CTL: Shutting down the commissioner
<13:49:03.722> Thread.run:[<IP_ADDRESS>:23:O][1649958543.715028][2620:2620] CHIP:CTL: Shutting down the controller
<13:49:03.725> Thread.run:[<IP_ADDRESS>:23:O][1649958543.715100][2620:2620] CHIP:CTL: Shutting down the commissioner
<13:49:03.727> Thread.run:[<IP_ADDRESS>:23:O][1649958543.715263][2620:2620] CHIP:CTL: Shutting down the controller
<13:49:03.729> Thread.run:[<IP_ADDRESS>:23:O][1649958543.715392][2620:2620] CHIP:IN: Expiring all connections for fabric 1!!
<13:49:03.731> Thread.run:[<IP_ADDRESS>:23:O][1649958543.715481][2620:2620] CHIP:CTL: Shutting down the commissioner
<13:49:03.732> Thread.run:[<IP_ADDRESS>:23:O][1649958543.715644][2620:2620] CHIP:CTL: Shutting down the controller
<13:49:03.734> Thread.run:[<IP_ADDRESS>:23:O][1649958543.715699][2620:2620] CHIP:IN: Expiring all connections for fabric 2!!
<13:49:03.735> Thread.run:[<IP_ADDRESS>:23:O][1649958543.715776][2620:2620] CHIP:CTL: Shutting down the commissioner
<13:49:03.736> Thread.run:[<IP_ADDRESS>:23:O][1649958543.715938][2620:2620] CHIP:CTL: Shutting down the controller
<13:49:03.737> Thread.run:[<IP_ADDRESS>:23:O][1649958543.715991][2620:2620] CHIP:IN: Expiring all connections for fabric 3!!
<13:49:03.738> Thread.run:[<IP_ADDRESS>:23:O][1649958543.716058][2620:2620] CHIP:CTL: Shutting down the System State, this will teardown the CHIP Stack
<13:49:03.739> Thread.run:[<IP_ADDRESS>:23:O][1649958543.716913][2620:2620] CHIP:DMG: IM WH moving to [Uninitialized]
<13:49:03.740> Thread.run:[<IP_ADDRESS>:23:O][1649958543.716996][2620:2620] CHIP:DMG: IM WH moving to [Uninitialized]
<13:49:03.741> Thread.run:[<IP_ADDRESS>:23:O][1649958543.717047][2620:2620] CHIP:DMG: IM WH moving to [Uninitialized]
<13:49:03.742> Thread.run:[<IP_ADDRESS>:23:O][1649958543.717093][2620:2620] CHIP:DMG: IM WH moving to [Uninitialized]
<13:49:03.743> Thread.run:[<IP_ADDRESS>:23:O][1649958543.717142][2620:2620] CHIP:DMG: All ReadHandler-s are clean, clear GlobalDirtySet
<13:49:03.744> Thread.run:[<IP_ADDRESS>:23:O][1649958543.717303][2620:2620] CHIP:BLE: BleConnectionDelegate::CancelConnection is not implemented.
<13:49:03.745> Thread.run:[<IP_ADDRESS>:23:O][1649958543.717741][2620:2620] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-2zZi9i)
<13:49:03.746> Thread.run:[<IP_ADDRESS>:23:O][1649958543.718998][2620:2620] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
<13:49:03.747> Thread.run:[<IP_ADDRESS>:23:O][1649958543.719102][2620:2620] CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0)
<13:49:03.747> Thread.run:[<IP_ADDRESS>:23:O][1649958543.719161][2620:2620] CHIP:DL: Inet Layer shutdown
<13:49:03.748> Thread.run:[<IP_ADDRESS>:23:O][1649958543.719209][2620:2620] CHIP:DL: BLE shutdown
<13:49:03.749> Thread.run:[<IP_ADDRESS>:23:O][1649958543.719259][2620:2620] CHIP:DL: System Layer shutdown
<13:49:03.750> Thread.run:[<IP_ADDRESS>:23:O][1649958543.719471][2620:2620] CHIP:TOO: Run command failure: ../../examples/chip-tool/commands/common/CHIPCommand.cpp:391: CHIP Error 0x00000032: Timeout

Proposed Solution
<suggested fix, suggested enhancement>

@yinyihu-silabs Please attach the full log of the command that was used to commission the device.

Here is the log for both commissioning and chip-tool read command when it get timeout error
timeout commision.log

this timeout does not always happen right after commissioning.
at commit 077e44eadf46f349916b3f4f358da6126be2ed48, it happens after every 5-10 chip-tool commands (read/write attributes or functional commands)

It looks like the Sigma1 message never got a response, even though it's the same IP as what was discovered at the end of commissioning and the Sigma handshake there worked fine.  Is it possible to attach both chip-tool and device logs from the same run (complete logs for both)?  Would be good to know what the device thinks it's doing.

we noticed these two issues seen on all-cluster-app could be similar to what I'm seeing here on EFR32. https://github.com/project-chip/connectedhomeip/issues/17698
https://github.com/project-chip/connectedhomeip/issues/17568

So the logs from https://github.com/project-chip/connectedhomeip/issues/17406#issuecomment-1110087952 show that client sent Sigma1, server received Sigma1 and responded with a standalone ack, but never sent Sigma2.  In particular, CASEServer::InitCASEHandshake failed on the server:
<info  > [IN] CASE Server received Sigma1 message. Starting handshake. EC 0x2001bcf0
<info  > [IN] CASE Server enabling CASE session setups

Compare to a working case, which looks more like this:
<info  > [IN] CASE Server received Sigma1 message. Starting handshake. EC 0x2001bcf0
<detail> [SC] Waiting for Sigma1 msg
<info  > [IN] CASE Server disabling CASE session setups
<info  > [SC] Received Sigma1 msg
...etc

we're not logging detailed error info on this device, looks like, but if this is in a build where #17698 could happen, that would have these symptoms.  And looking at the client log, it's the 16th read that fails, which definitely starts to look like #17698.

issue hasn't been seen for a while. close for now.


Infinite loop false alarm in unit test (easy fix) - static analysis warning

Is your feature request related to a problem? Please describe.
Static analysis warning on i being int8.  Can be avoided if defined as size_t.
https://github.com/nasa/cFE/blob/c708d64bf2b25500cd0308a700aa4ee0b3fd5909/fsw/cfe-core/unit-test/ut_support.c#L82-L90
Based on logic strlen(UT_subsys) will never be bigger than int8 (unless someone redefines UT_subsys as something unreasonable) so this is a false alarm but easy to fix and better pattern to follow.
Describe the solution you'd like
Change to size_t
Describe alternatives you've considered
None
Additional context
Please wait until #972 is resolved.
Requester Info
Jacob Hageman - NASA/GSFC

I would like to work on this issue.

@skliper Hi, as #972 is closed, so i assume it is resolved. So should i go for a PR for this issue?

@himanshu007-creator Yes please!  You'll need to follow the PR template instructions to fill out and deliver a CLA before the PR can be merged.  Thanks!


Join: ensure inflight status is cleared when in auto mode

Fixes #4080

Coverage: 68.583% (+0.07%) from 68.51% when pulling 9e6d5010094e35ef54594f6ccfb7ad594e36c51f on fix-join-memory into 910f6134f6a93612967cc908c45dfb8c885b395f on dev.


docs: s/Tables/Variables/

Found another place that refers to the name change from "Tables" to "Variables"

Also: #1805 & #1809

Thanks!


Skeletal Hands

Tracked hands -> SteamVR skeletal hands (not controller emulation)

Apoarently this is required for vrchat's new pinch gesture input to function which may allow vrchat to be useable on vision pro without controllers.


[Bug]: userChrome.theme-default doesn't apply the older userChrome.default-theme-colors settings

What happened?
Since commit d8392e989f32d68abd517e05fe844af0bc909773, I no longer see the "default colors" in Firefox Nightly 129.0a1 (2024-06-18) (64-bit), MacOS.
I've also set userChrome.theme-default to true, the slightly darker topbar was :100:, is there a way to return the old look?
Previously, it would look like this:

Now it looks like this (note the top bar shading change):

Would this now be handled via a custom CSS file, if so I could contribute that back :+1:
Steps to reproduce the problem

Open Firefox
about:config -> userChrome.theme-default to true
Reload Firefox

Additional info (Optional)
Firefox version:
Operating system:

There is no need for a custom CSS file because I wrap all color rules in a media query. When userChrome.theme-default is true, these rules won't be loaded, and Firefox will use the default colors. I think the issue is with the title bar active/inactive color. I'll fix it later.

Awesome, thanks! Been really loving this theme for quite a while :).
Thanks for maintaining it!

Would this now be handled via a custom CSS file

As I checked, the latest version fully matches the native Firefox color scheme, so I won't override it.
You can restore the old title bar color, as shown in your screenshot, by simply placing the following code in the custom.css file:
@media (prefers-color-scheme: light) {
  :root:not(:-moz-window-inactive) #navigator-toolbox {
    background-color: #c7c9c9 !important;
    background-image: none !important;

    #toolbar-menubar,
    #TabsToolbar,
    #titlebar {
      background-color: #c7c9c9 !important;
      background-image: none !important;
    }
  }
}


[CT-3265] The docs generated for exposures should display owner

Describe the feature
Because 'owner' is a required property of an exposure, I would expect this to be displayed in the documentation generated. In fact, all of the properties of an exposure should be displayed. Maturity is also missing.
Describe alternatives you've considered
Using the meta parameters to add additional owner information that does get displayed in the header of the docs, but this is not DRY.
Additional context
Basic functionality for exposures
Who will this benefit?
Anyone who ever defines an exposure
Are you interested in contributing this feature?
Sure

Hello, this seems to still be an issue.

Would be super nice to have this section of the docs site be restored! 🙏 🙏

I agree, I feel like this is a big miss from the documentation site.


Duplicate field names in JSON of az postgres server list

Describe the bug
There are duplicate fields with names that differ only by case appearing in the storageProfile node of the JSON output.
Command Name
az postgres server list
Errors:
There are duplicate fields appearing under the storageProfile node:
"storageProfile": {
  "backupRetentionDays": 7,
  "geoRedundantBackup": "Disabled",
  "storageAutoGrow": "Disabled",
  "storageAutogrow": null,
  "storageMb": 10240
},

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

az postgres server list --resource-group {}

Expected Behavior
Only a single entry would be reported.
Environment Summary
Windows-10-10.0.17763-SP0
Python 3.6.6
Shell: cmd.exe

azure-cli 2.0.73

Extensions:
db-up 0.1.13
interactive 0.4.2

Additional Context

@danielbecroft Thank you for your feedback. We are aware of the issue and working to fix it. We expect the fix to be available by end of November.
(523139)

Work on this is in progress. Still expected to be available November end.

@danielbecroft Unfortunately, our deployment train for this has experienced delays. This, combined with our no-fly zones for the Christmas/New Year season, means that this fix will be delayed to January. We apologize for the delay.

This has been fixed. Thank you for your patience.
  "sslEnforcement": "Enabled", "storageProfile": {     "backupRetentionDays": 7,     "geoRedundantBackup": "Disabled",     "storageAutogrow": "Enabled",     "storageMb": 5120


build: add nix support

This is a very simple PR to make your project easily available to nix users.
I made it so the builds for nix will automatically pick up the right versions so there is no need for any changes in the future from you.

Lovely, thanks a lot! Sorry for my lack of understanding of how Nix works 🙂
I have a few questions:
•	Should we add documentation to the README file, or is this installation/build method self-explanatory for Nix users?
•	Also, should I generate and upload Nix builds for every release using a GitHub Action? Do those differ from standard Linux binary executables?

No worries, I enjoy nixifying repos!

The installation is self-explanatory for Nix users because this is just a simple package. As long as the user knows how flakes work, they're fine. Explaining how flakes work is definitely out of the scope of this repo.

Nix binaries do differ from standard Linux ones. There is a way to automate a cache binary but this package is pretty small so it won't be necessary. I could add a github action that checks if the nix build works in a separate PR if you'd like.

Got it, thanks for the explanation. Merging the PR now.
re 2.: I think that Github Action will not be necessary for now. Thanks anyway!


Changed kernel modules/firmware directories from /usr/lib/ to /lib/; also tidied Arch packaging scripts in the process

In the Linux kernel, the default modules directory is /lib/modules rather than /usr/lib/modules. The reason the current code works on many distros, such as Arch Linux, Fedora and Debian, is because these distribution have merged the members of the /usr directory with their root equivalents (Arch merge; Fedora merge; Debian merge). However, not all distros have performed this merge (like Gentoo), and the FHS still regards them as separate.
This proposed commit will preserve current behaviours on systems with a usrmerge hierarchy (as the symlink will just be followed); will now act correctly on systems without a usrmerge and where usr does not sit on a separate partition; and will open up the possibility of extending support to those systems without a usrmerge and with separate usr partitions. All tests remain passing on my Arch Linux system, and have gone from none of them passing to (almost) all of them passing on my Gentoo system.
Further reading if interested: 1, 2, 3.

hi @thomasfsteeples I would like to move forward with these changes. Do you still work on it?

Hi @anatol --- sorry, been busy with work lately, but I'll try and have a crack with splitting into separate commits in the next few days, and then I'll resubmit. Does that work for you?

@thomasfsteeples yes it works for me

also cc @nmeum

Pushed to wip branch as b040e83b9bf4c28082589ccee538cbec3cfe82a3

It turns out this PR beaks integration tests. CPIO compressor does not like to have 'lib as a symlink' together with /lib/modules/... files.
Image.Append*() needs to perform path sanitization and handle symlinks.
Or another way to fix the issue is to modify generator/image.go. Instead of implementing own streaming cpio/zstd compressor it is possible handle in a more traditional way - write all the files to a temp dir first and then use command line tools to do cpio/zstd compression. This way the code avoids dealing path sanitizing.


Add an identifier for unmanaged AWS security group rules

Description
For unmanaged security group rules, the json output currently shows only a hash generated based on the security group rule properties (such as from/to ports, protocol, sg ID). As far as I can tell, this makes it impossible to identify which rule is listed using the json report, and we have to run the "raw text" report to do so.
Example
Here is an example of the json output for an unmanaged security group rule:
{
    "id": "sgrule-123456789",
    "type": "aws_security_group_rule"
}

Here is an example of a raw report for the same rule:
- sgrule-123456789
    Ports: 442, Protocol: tcp, SecurityGroup: sg-1fsdf2345dsfsdf2s, Source: <IP_ADDRESS>/16, Type: ingress

Using the json one, it is not possible to identify on AWS which rule is actually behind the sgrule-123456789, making the json report hard to leverage here.
Proposition
Would it be possible to print the real security group rule ID instead for example?

I flagged this one as a good first issue, if someone from the community want to take it, it shouldn't be too hard to handle.
Here is a few hints:
In pkg/resource/resource.go:
You can add new field to SerializableResource, something like identityAttributes or humanReadableAttributes.
Then you need to set this field in NewSerializableResource based on res.Schema().HumanReadableAttributesFunc(res).
An example of what is done on the console side can be found here : https://github.com/snyk/driftctl/blob/0a1ed7d01e2370fd3fed45e0120d813bdf14e7d8/pkg/cmd/scan/output/console.go#L279-L301
We may work on this on our side if nobody from the community has taken it in a couple of week since we'll need this for internal needs at some point.
Please go to discord #support channel if you need more help on this one

👋 @eliecharra I created a PR for this issue

Ok I see this is the usecase for the opened PR then. Sorry I missed that.

This issue has been referenced in the latest release v0.21.0.


Add default projections to Views in ContactsPal

It's well known that some devices fail when trying to get all columns by passing null as the projection. ContactsPal should provide defaults for normal apps and sync-adapters.

Projections are no longer a property of Views, so this has become obsolete.


Add Polkadot Coretime to known chains

The chain hasn't been registered and onboarded yet, but just making this for some advance notice.
The chain spec has been added here and the referendum is ongoing. RPCs will be spinning up over the coming week.

Thanks for the notice Dónal! We'll definitely add it in the next minor release.


More in-depth documentation, in general

Problem:
So, I used to write my own dialogue system for my games, but after finding dialogic I've started using it instead. My issue comes with the documentation. When it comes to the documentation of dialogic, as great of an addon as it is, I cannot for the life of me find any clear documentation on it. Some things I'd love clarified would be text tags, things like [wave] and [color] aren't even documented on the text events page which makes me wonder what else they haven't documented. Not only this, but other features like custom choice buttons, is there a way to detect if it's being hovered? currently selected? maybe a way to check the widest option so you can set the width to be the same for all of the options? no idea. or maybe nicknames? how do you set multiple nicknames? is there a way to change the display name to one of the nicknames? I have no idea because it's not at all documented, not only that but hovering over 90% of the options tells me nothing as to what it actually does which leads me to have to test it out myself rather than work on what I wanted to get done. The only downside so far to this addon from what I've experienced so far is the fact there is no real documentation.
Solution:
Flesh out the documentation. Obviously with this being on Github, I'll try and contribute what I can and I'm sure others will too, but I find the lack of documentation to be rather annoying as it means I have to dig through the addon and posts on forums for hours to find how to do something with 0 idea if there's already a function or easier solution.
P.S.
Love the addon so far, when it works. The dialogue timeline editor is exactly what I've been looking for, keep up the good work!

Docuemntation will be improved 100% 👍🏻

How exactly will we decide when this is finished ;). I mean the docs aren't finished but with the builtin documentation and new stuff being written all around I'm not sure when this should be closed?

I would close this one whenall the help pages are somewhat reasonable for a release, but I have to review it a few times 😅  hopefully it can be done this week!

Could we collect a list of what should definitely be documented (at all or better) before 1.3? Of course there should be proof-reading of (at best) everything. But I'm thinking about what new articles are missing. These are the things that I can think of:
General

[ ] A page explainging the use of the glossary
[ ] A page explaining the use of values
[ ] A page explainging saving and loading (already in the works on my saving system branch)
[ ] A better explenation of the functions of the DialogicClass (also probably better be made after the saving system)
[ ] A page about the Voice Line Support
[ ] Maybe a page about the TimelineEditor? Where some not so well known functionality is explained?

Missing Event pages:

[ ] Set Glossary
[ ] Change Timeline
[ ] Set Background
[ ] Close Dialog
[ ] Wait Seconds
[ ] Set Theme

Please feel free to give feedback if something is unnecessary or missing!

I don't think that we really need a documentation page for everything, you already wrote the most important stuff and we can keep updating it when necessary. I'll remove the milestone tag on this issue to keep tracking for the future but I'm pretty happy with the state of the docs at the moment :)

I agree with you, we can add more documentation later on.
The only docs that are on the main branch and not complete/up to date and thus can be super misleading is the "Beginners Guide Tutorial". I think it would be very cool if you could have a look at that again @coppolaemilio!

One more note: the FAQ articles have way to long names! Make them shorter

Closing because it is too broad


Release testnet 55: Io

Testnet Release
Testnet name: Io
Release date: June 26, 2023
Testnet release manager: @redshiftzero
Testnet Release Manager Checklist
Preceding Friday (sprint planning day):

[x] Create GitHub project column, work with team to populate the milestone with tickets targeted for the release.

Tuesday (or after release of previous testnet):

[x] Construct the genesis data for the release:

[x] Create new testnet directory with initial genesis allocations for this testnet by running cd testnets && ./new-testnet.sh

This genesis data will be used for testnet-preview with a randomized version of the future testnet's chain ID.

Thursday:

[ ] Check in with team again in a release meeting and update the GitHub milestone to ensure it represents what will make it into the testnet.
[ ] Draft an announcement for peer review to ensure major changes included are comprehensive.

Following Monday (release day):

[ ] Verify that testnet-preview.penumbra.zone is operational; it is redeployed on every push to main, and is an exact preview of what is about to be deployed.
[ ] Bump the version number and push its tag, via cargo-release.

[ ] Run cargo release minor for a new testnet, or cargo release patch for a bugfix. For the latter, make sure you're on a dedicated release branch.
[ ] Push the commit and newly generated tag, e.g. v0.51.0, to the remote.

[ ] Wait for the "Release" workflow to complete: it'll take ~90m, most of which is the macOS builds.
[ ] Edit the newly created (and published) release object, then click "Generate release notes." Cut and paste the generated text from the bottom to the top of the post, then save it.
[ ] You must manually review the Waiting deployment in the GitHub Action UI before the deployment will begin. Monitor the GitHub action to ensure it completes after it is approved.
[ ] Delegate to the Penumbra Labs CI validators; use amounts of ~200k penumbra per validator.
[ ] Update the User Guide to mention the newly created git tag.
[ ] Update Galileo deployment, following docs.
[ ] Make GitHub release object and include the announcement
[ ] Make the announcement to Discord! 🎉🎉🎉

Upon discussion in the weekly recap on June 15, 2023, we decided to release Io on June 26, 2023.


update project dependenices

update to Spring boot 2.2.5
various miscellaneous to keep up to date with bug fixes and features

complete


Integrate an option for TrustServerCertificate on MsSql options

Is your feature request related to a problem? Please describe.
As of SqlClient v4, there is a breaking change to have encrypt set to true by default. Currently, the connection string output by the TestcontainerDatabase does not have this option enabled or an ability to toggle it on.
Describe the solution you'd like
Given that these dbs are for testing only, i would think adding TrustServerCertificate=true; on all sql server connection strings would be reasonable, but at least adding a toggle for it somehow would be helpful.
Describe alternatives you've considered
Currently, i need to do something like this:
    private readonly  TestcontainerDatabase _dbContainer = IsRunningOnMacOsArm64()
        ? new TestcontainersBuilder<MsSqlTestcontainer>()
            .WithDatabase(new MsSqlTestcontainerConfiguration()
            {
                Password = "#testingDockerPassword#",
            })
            .WithName($"IntegrationTesting_RecipeManagement_{Guid.NewGuid()}")
            .Build()
        : new TestcontainersBuilder<MsSqlTestcontainer>()
            .WithDatabase(new MsSqlTestcontainerConfiguration()
            {
                Password = "#testingDockerPassword#",
            })
            .WithName($"IntegrationTesting_RecipeManagement_{Guid.NewGuid()}")
            .WithImage("mcr.microsoft.com/azure-sql-edge:latest")
            .Build();

    public async Task InitializeAsync()
    {
        await _dbContainer.StartAsync();
        Environment.SetEnvironmentVariable("DB_CONNECTION_STRING", $"{_dbContainer.ConnectionString}TrustServerCertificate=true;");

Open to submitting a PR for this if you're low on bandwidth. Thanks!

What do you think about removing the sealed modifier from the HostedServiceContainer implementations like MsSqlTestcontainer? This allows to override MsSqlTestcontainer. Then you can do something like:
  private const string MsSqlX86DockerImage = "";

  private const string MsSqlArmDockerImage = "";

  private readonly IDockerContainer container;

  public GitHubIssue474()
  {
    var dockerImage = IsRunningOnM1() ? MsSqlArmDockerImage : MsSqlX86DockerImage;
    this.container = new TestcontainersBuilder<MsSqlRecipeManagement>()
      .WithName($"integration-test-recipe-management-{Guid.NewGuid():D}")
      .WithDatabase(new MsSqlTestcontainerConfiguration(dockerImage))
      .Build();
  }

  public Task InitializeAsync()
  {
    return this.container.StartAsync();
  }

  public Task DisposeAsync()
  {
    return this.container.DisposeAsync().AsTask();
  }

  private static bool IsRunningOnM1()
  {
    return true;
  }
}

public sealed class MsSqlRecipeManagement : MsSqlTestcontainer
{
  public MsSqlRecipeManagement(ITestcontainersConfiguration configuration, ILogger logger)
    : base(configuration, logger)
  {
  }

  public override string ConnectionString { get; }
    = string.Empty; // TODO: Set your connection string.
}

diff --git a/src/DotNet.Testcontainers/Containers/Modules/Databases/MsSqlTestcontainer.cs b/src/DotNet.Testcontainers/Containers/Modules/Databases/MsSqlTestcontainer.cs
index 0779950..5b7a361 100644
--- a/src/DotNet.Testcontainers/Containers/Modules/Databases/MsSqlTestcontainer.cs
+++ b/src/DotNet.Testcontainers/Containers/Modules/Databases/MsSqlTestcontainer.cs
@@ -9,14 +9,14 @@ namespace DotNet.Testcontainers.Containers

   /// <inheritdoc cref="TestcontainerDatabase" />
   [PublicAPI]
-  public sealed class MsSqlTestcontainer : TestcontainerDatabase
+  public class MsSqlTestcontainer : TestcontainerDatabase
   {
     /// <summary>
     /// Initializes a new instance of the <see cref="MsSqlTestcontainer" /> class.
     /// </summary>
     /// <param name="configuration">The Testcontainers configuration.</param>
     /// <param name="logger">The logger.</param>
-    internal MsSqlTestcontainer(ITestcontainersConfiguration configuration, ILogger logger)
+    protected MsSqlTestcontainer(ITestcontainersConfiguration configuration, ILogger logger)
       : base(configuration, logger)
     {
     }

hmmm, yeah i can buy that in my use case given the extra stuff i'm doing to use edge to account for M1 chips, but some might not care and just want to have the connection string work by default when using sql client v4+.
so i'd personally lean having TrustServerCertificate=true; included by default for those that only need that much to get it working, but also having this overriding capability for customization's like the edge override for M1s

Yes, we can do both, but just adding TrustServerCertificate is not enough IMO. If you need any other option in the future, you'll have the same issue again 😀.

yup, agreed :-)

I used this workaround:
SqlConnectionStringBuilder sqlConnectionStringBuilder =
                new SqlConnectionStringBuilder(Testcontainers.ConnectionString);

sqlConnectionStringBuilder.TrustServerCertificate = true;
sqlConnectionStringBuilder.InitialCatalog = "my stuff";
//etc
string connectionString = sqlConnectionStringBuilder.ConnectionString;

then use the new connectionString in my tests.
Wondered if it would be an option for the Testcontainers to have properties for eg host, port, etc in addition to a 'generic' connection string.

Wondered if it would be an option for the Testcontainers to have properties for eg host, port, etc in addition to a 'generic' connection string.

What do you mean by that? There is a Hostname, Port, etc. property.

Wondered if it would be an option for the Testcontainers to have properties for eg host, port, etc in addition to a 'generic' connection string.

What do you mean by that? There is a Hostname, Port, etc. property.

Good point - think I saw that originally and forgot when I replied - I was thinking more generically - any property that forms part of the connection string should be available such that the dev can create their own custom connection string if the auto-generated one doesn't quite meet the requirements (eg for adding additional options)
In my example I was able to use the SqlConnectionStringBuilder to parse the autogenerated one and add additional properties, other containers might need more meta-data to re-create a connection string. I can't think of any concrete examples mind!

In case of MsSqlTestcontainerConfiguration some config options, e.g. Database,  throw NotImplementedException.

In case of MsSqlTestcontainerConfiguration some config options, e.g. Database, throw NotImplementedException.

This is a limitation of the MSSQL Docker image. Not all images support all kinds of configuration. Although we support it now with the upcoming 2.2.0.

I was thinking more generically - any property that forms part of the connection string should be available such that the dev can create their own custom connection string if the auto-generated one doesn't quite meet the requirements

I agree. The new module structure offers more and convention ways to configure containers. I am done by the builder. Right now, I am looking into ways to pass the configurations along the builders. Immutability makes it a bit difficult and cumbersome... I hope I am done with the proposal in the next days.

Any updates here? I came across the same problem (MySql and OldGuids=true) and I know that @paule96 also has it.
We thought the best option would be to refactor the Testcontainer to use SqlConnectionStringBuilder under the hood (instead of the custom string concatenation currently e.g: ).
https://github.com/testcontainers/testcontainers-dotnet/blob/a5d45f88fbe78c2b831bd5b4c5bdc2ca5a1d56cc/src/Testcontainers/Containers/Modules/Databases/MySqlTestcontainer.cs#L25-L26
This way we could build and modify the ConnectionString as needed.
This would hopefully enable an Extension Method for TestcontainersBuilder like:
_container = new TestcontainersBuilder<MySqlTestcontainer>()
            .WithDatabase(new MySqlTestcontainerConfiguration { Database = "db", Username = "root", Password = "example" })
            .WithImage("mysql:8.0.29")
            // Should only be called after "WithDatabase"
            .ModifyConnectionString(connectionStringBuilder => { // supply current SqlConnectionStringBuilder
                // Modify as needed
                builder["Connect Timeout"] = 1000;
                builder["Trusted_Connection"] = true;
            })
            .Build();
// Modifications are saved and can be retrieved later via the existing interface
connectionString = _container.ConnectionString

@HofmeisterAn maybe it's better to implement an simple builder by yourself. It's basically only a key value list divided by ';'. The only hard thing todo, is always escaping inside the key values.
That should be doable by the current structure of the project.

If someone would like to work on that, we can certainly add it. Please create an issue if you like. I would favor an implementation that covers multiple database provides.

Okay I looked now a bit to the code, and now I know what @HofmeisterAn mean by different database providers. Providers that use as a connection string an URI schema and not an Connectionstring schema. I will think a bit more about it, the rest of the week.
For everyone who is interested to find a solution too interesting connection strings are the following:

normal ADO Connectionstring, Key/Value devided by = and each pair by ;

MySql for example: Server={this.Hostname};Port={this.Port};Database={this.Database};Uid={this.Username};Pwd={this.Password};

URI based Connectionstrings are using the schema known by SSH or FTP. Wher the user and the password can be part of the URI. Usally divived by @

CouchDb for example: http://{this.Username}:{this.Password}@{this.Hostname}:{this.Port}

I don't even know how additional connection options will work with the URI based connection schema. So I will see what I can find out at the next weekend.

@HofmeisterAn would it be possible to split the Database Classes in classes wich support ADO.NET connectionstrings and the others? That would simplify the feature request?

would it be possible to split the Database Classes in classes wich support ADO.NET connectionstrings and the others?

Do you mean connection strings that are key value pairs and delimited by ;?

@HofmeisterAn yes you are right. I mean more the Syntax of semicolon delimited connection strings.
So at the end to provide two implementations. One for URI based connection strings and one for the semicolon delimited.
And if this is not enough the current fallback to manipulate the builded connection string is still possible.

OC, if it makes the development experience better and more convenient lets add it. We do not need to support both types immediately (URIs usually do not have any options anyway). For those we can probably use the UriBuilder. I just want to point out, that we are more flexible with the dedicated modules in the future. E.g. we can just add System.Data.SqlClient and use SqlConnectionStringBuilder.

Okay finally after some weeks I was able to catch a bit of my free time to implement a first version of it. It would be nice if @HofmeisterAn could review my commit a bit. Just to know if I'm on the right path.
https://github.com/paule96/testcontainers-dotnet-issues-474/commit/7fd7cf045accad02506970be765d5c02ca0b60e7
If this is good I will try to extend the configuation interface with the new options.

With the latest release (3.0.0), we set the mentioned property for the MsSql and SqlEdge module. If you require additional capabilities to configure the connection string more conveniently, please consider creating a follow-up issue or participating in the following discussion. I will close this issue since, as mentioned, the property is now set.


Add scala version 2.12.13

Please add a new tag after merging it so I can send a PR for a new homebrew formula.

@mazgi take a look at this when you can :)

@mazgi take a look at this when you can :)

@mazgi can you please add a new tag? Or provide me permissions to push tags and I can do it next time.

@mazgi can you please add a new tag? Or provide me permissions to push tags and I can do it next time.

@MihaiBogdanEugen Thank you for the comment ✨
I've just invited you.

@MihaiBogdanEugen Thank you for the comment ✨
I've just invited you.

Thank you, I will not let you down!

Thank you, I will not let you down!

@mazgi you've just invited me to sbtenv, which is fine, I plan to keep that one up to date as well. Can I get you invite me to scalaenv as well (the current one)? The tag I want to add is for scalaenv right now.

@mazgi you've just invited me to sbtenv, which is fine, I plan to keep that one up to date as well. Can I get you invite me to scalaenv as well (the current one)? The tag I want to add is for scalaenv right now.

@MihaiBogdanEugen oops... I've just invited you scalaenv 🙏🏻

@MihaiBogdanEugen oops... I've just invited you scalaenv 🙏🏻

@MihaiBogdanEugen Thank you for your comment https://github.com/scalaenv/scalaenv/pull/101#issuecomment-765487587 again ❤
Please mention to @3tty0n before you tag.
Because he is the most active maintainer, I'm respecting him.

@MihaiBogdanEugen Thank you for your comment https://github.com/scalaenv/scalaenv/pull/101#issuecomment-765487587 again ❤
Please mention to @3tty0n before you tag.
Because he is the most active maintainer, I'm respecting him.

@MihaiBogdanEugen Thank you for your continuous commitments. Recently, I could not actively commit to this project since I'm pursuing my doctoral course, so I welcome your spontaneous development.  It's not mandatory to mention me when you add a new version tag. If you have any questions, please feel free to ask us.

@MihaiBogdanEugen Thank you for your continuous commitments. Recently, I could not actively commit to this project since I'm pursuing my doctoral course, so I welcome your spontaneous development.  It's not mandatory to mention me when you add a new version tag. If you have any questions, please feel free to ask us.

@3tty0n not a problem, I know how hard getting a PHd is, my wife has one. Good luck with your endeavours. I'll try to keep both scalaenv and sbtenv up to date with the latest releases. Thank you all for your work so far.

@3tty0n not a problem, I know how hard getting a PHd is, my wife has one. Good luck with your endeavours. I'll try to keep both scalaenv and sbtenv up to date with the latest releases. Thank you all for your work so far.


[glfw3] Update to 3.3.1

Patch removed because problem was fixed in this version (https://github.com/glfw/glfw/commit/2e3b4cf8984e8bf983e1647a85aced8f6e6754f0)

/azp run


Fixing ChessPlay.java for 1.18 --> 1.20

Errors found:

[x] error: level has private access in Entity
[x] error: incompatible types: possible lossy conversion from double to int

changed .level to .level() which might return null

Casted in to the Double variable, I didnt want to change the data types of the variables in case it misses something up


Cannot style selected ToggleGroup.Item inside Tooltip

Bug report
Current Behavior
Cannot style the selected state of ToggleGroup.Item when it's wrapped in a Tooltip.
Expected behavior
Can style the selected state of ToggleGroup.Item even when it's wrapped in a Tooltip.
Reproducible example
CodeSandbox
Suggested solution
--
Additional context
Tooltip's data-state attribute overrides ToggleGroup.Item's data-state attribute (due to using asChild in Tooltip).
ToggleGroup.Item's data-state="on" enables styling the selected state.
Related to https://github.com/radix-ui/primitives/issues/602.
A workaround is to wrap the tooltip trigger in a <span> but this causes the tooltip's aria-describedby to be added to the span instead of the button.
Your environment
"@radix-ui/react-toggle-group": "^1.0.3",
"@radix-ui/react-tooltip": "^1.0.5",

Hey @emlai yes that's a known issue (as you pointed out to in #602).
There are a few workarounds you can use as suggested in that issue by controlling the state and styling accordingly based on other attributes/classes you'd put in.
Alternatively here in this case, if you don't need the tooltip state, you can simply swap around Tooltip.Trigger and Toggle.Item: https://codesandbox.io/s/confident-napier-iglr6e?file=/src/App.tsx
Ultimately until we find a fix for this, the most flexible solution will be to control the state.
I will close the issue as it's a duplicate of #602 ultimately.


can routes be added dynamically?

can routes be added dynamically?

Thank you for your attention and feedback to arpc!
arpc.Handler is a interface{}, the default implementation(arpc.handler) doesn't support concurrent add operations.
But you can implement a Handler yourself and set it: arpc.Client/Server.Handler = yourHandler. The easiest way to implement it is copy the arpc/handler.go and add mutex operations in the handle/HandleStream/OnMessage funcs:
https://github.com/lesismal/arpc/blob/master/handler.go#L572
https://github.com/lesismal/arpc/blob/master/handler.go#L701

Welcome to try arpc!
Here's aother easier way:
newHandler := server.Handler.Clone()
newHandler.Handle(...) // or other logic you want
server.handler = newHandler


Fail to install on Windows due to undefined syscalls

I'm using godo for some products on Linux and Windows. Godo works fine on Linux, but on Windows, fails to install due to undefined syscalls.
> go get -u gopkg.in/godo.v2/cmd/godo
# gopkg.in/godo.v2/cmd/godo
src\gopkg.in\godo.v2\cmd\godo\main.go:202: undefined: syscall.Getpgid
src\gopkg.in\godo.v2\cmd\godo\main.go:206: undefined: syscall.Kill

Environment: Godo v2.0.7 (maybe), Go 1.5.3, Windows 7

I also get the same errors on both Cmder, and Cygwin.
C:\Users\predatorian
λ go get github.com/go-godo/godo
# github.com/go-godo/godo
Documents\GitHub\GO\src\github.com\go-godo\godo\exec.go:243: multiple-value gopass.GetPasswd() in single-value context

+1

+1

+1

+1

Is there any status update on this? Otherwise then maybe just update README that Godo is not usable with Windows?

The issues is Go is not very good at process handling. See questions like this on stackoverflow. If somebody can provide a solution to that on Windows, I'd be happy to merge it in.

It should be noted that this tool is way useful for cross platform development, since I can have my entire build expressed in golang and thus dispense with writing bash scripts for Linux builds and powershell scripts on windows. This issue blocks this use case.

@djhaskin987 Now there are other task runners supporting your use case, what makes godo a requirement for your project?
Here's a few, (google "golang task runner" for more)

https://github.com/go-task/task
https://github.com/rliebz/tusk
https://github.com/tockins/realize (some windows support seems in place https://github.com/tockins/realize/issues/19)
https://github.com/markbates/grift

@martinlindhe Thanks for that, I appreciate it :) I actually found mage, I'm looking into using it https://github.com/magefile/mage

Mage looks cool too! Glad you can move forward


Register now adds record to users table

Closed as its requesting to master. Will be moving the request to develop branch


MSVC19 - Spaceship Operator triggers "C2338	static_assert failed: 'NTTP functionality only works when rep is built-in integral type'

Hello Chip,
I noticed, that as soon as I export a class using the spaceship operator, I receive the error as mentioned in the title.
Minimal example:
#define DLL_API __declspec(dllexport)

	struct DLL_API TestClass
	{
		auto operator<=>(const TestClass&) const = default;

		au::Quantity<au::Meters, double> thickness;
	};

It would be great, if you could take a look at it.

Thanks for raising this.  Very timely, as we are on the verge of cutting the next release!
I was extremely confused, but I finally figured out what is happening.  It turns out that operator<=> can't be automatically defined for Quantity, because its data member is private.  Normally, we would have defined it ourselves as a hidden friend, but we maintain C++14 compatibility, and we literally can't express operator<=> in C++14.  However, Quantity can now be implicitly converted to the enum class Quantity::NTTP, which presumably does support <=>.  Of course, since Quantity<Meters, double> is of floating point type, we (correctly and safely) produce a hard compiler error when we trigger this conversion.
You can immediately unblock yourself by adding this function somewhere after you include "au/quantity.hh" (directly, or indirectly via "au/au.hh"), and before you define TestClass:
template <typename U1, typename R1, typename U2, typename R2>
constexpr auto operator<=>(const Quantity<U1, R1> &lhs, const Quantity<U2, R2> &rhs) {
    using U = CommonUnitT<U1, U2>;
    return lhs.in(U{}) <=> rhs.in(U{});
}

On the Au side, I think we can make a kind of "au/au_cpp20.hh" file, with appropriate CI testing.  Users on newer standards can include it to get library-supported fixes to handle features in newer standards.  Users on older standards won't be affected at all.

A colleague, @andrey-petr, pointed out that you could also change your return type from auto to std::strong_ordering in this case.  That would have the benefit of being a very simple change.  However, I think that auto better expresses author intent in this case, and probably would also scale better to structs with multiple members.

Thank you for your quick response! The workaround you suggested works perfectly.
Rather than placing the responsibility on the client to select the appropriate include, how about using a conditional approach like this?
#if __cplusplus >= 202002L
    // Code for C++20 or newer
#else
    // Code for older standards
#endif

Of course, this approach must be validated for the supported compilers.

A colleague, @andrey-petr, pointed out that you could also change your return type from auto to std::strong_ordering in this case. That would have the benefit of being a very simple change. However, I think that auto better expresses author intent in this case, and probably would also scale better to structs with multiple members.

I would rather not have a library in my code base which forces me to make changes...

Thank you for your quick response! The workaround you suggested works perfectly. Rather than placing the responsibility on the client to select the appropriate include, how about using a conditional approach like this?
#if __cplusplus >= 202002L
    // Code for C++20 or newer
#else
    // Code for older standards
#endif

Of course, this approach must be validated for the supported compilers.

This would be quite a watershed moment for Au: I have always striven to avoid all macros in the library.  The bar for going from 0 to 1 macros would be very high.  However, I can't deny your compelling point, that it would be better if the library would simply continue to work out of the box.
We have always said we implicitly support not just C++14, but C++17, C++20, and all newer versions.  We've founded this claim mainly on backwards compatibility.  Here's a concrete example where that's not enough.  If we really support C++20, then we'll need to support straightforward use cases such as the one in your initial post.
I think I probably need to get over myself and give up on absolute purity on macros, when the technical tradeoffs are heavily lopsided.  :sweat_smile:  I still want to keep the bar very high, and not open the floodgates to a codebase littered with test macros.
However, this particular instance does seem like it meets that bar.

I’m not particularly fond of macros either, but I believe prioritizing client convenience is more important in this case. At the moment, I can't think of a better alternative, so this approach seems like the most practical solution for now.

@MatthiasJeuthe, does #354 remove the need for you to add the manual implementation of operator<=>(Quantity, Quantity)?


Incorrect Paper Link in Multi-Modal Section

Hi,
First of all, I want to express my appreciation for the work you've done with the Awesome-Mixup repository.
While browsing through the Multi-Modal section, I noticed an issue with one of the paper links. The link for the paper "Enhance image classification via inter-class image mixup with diffusion model" currently points to "PowMix: A Versatile Regularizer for Multimodal Sentiment Analysis," which appears to be incorrect.
Here is the correct link for "Enhance image classification via inter-class image mixup with diffusion model":
[paper]

Hi, @huzhaozhe00
Thank you for pointing this out, we've modified it to the correct link.


Configure the code coverage

Ignore

*.container
index.js
*.test.js

ajouter le threshold à 100%

Wow, you want to ignore the containers? Why?


fix: fix rule deprecation support

By removing categories from the .defaultsForValidator.js, the deprecated rule logic
is prevented from finding the old rules to map to new ones. This commit adds the
categories back in so that users have an easier time converting their configurations
to the new format.
I also removed the init and migrate commands because they are largely irrelevant
at this point and we don't want anyone using them.

:tada: This PR is included in version 0.72.1 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 0.22.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


Subject page 404 handler

If subject is not found, have page fire 404 event

I am reopening this issue for Kimmy to review. It looks fine to me.


fix: querry response anthropic MCP

/attempt #1007
/claim #1007
claude app screeshort

mcp inspector screenshot

currently I handled OCR and audio working on other

nice!
actually i thought it would be better to do this is JS using our SDK, but i know it's a bit late to say that, you can keep python if you want

nice!
actually i thought it would be better to do this is JS using our SDK, but i know it's a bit late to say that, you can keep python if you want

ok I'm keeping in python
you can merge it now
https://github.com/user-attachments/assets/66fe1c57-7c7c-46a5-a705-b60aa3f80d40

i don't see any meaningful code change, so it was already working? how do you install it?

i don't see any meaningful code change, so it was already working? how do you install it?

no, it was not passing any context into AI, and previously your query was not working,I also fixed the result is not parsing correctly That's why it is not passing any context in Claude desktop now it is working fine
i  installed on the Claude desktop by following the readme point one
https://github.com/mediar-ai/screenpipe/blob/main/screenpipe-integrations/screenpipe-mcp/README.md#1-configure-claude-desktop

does not work for me @kumarvivek1752
https://github.com/user-attachments/assets/6c42edc1-c031-4e9a-b9f8-96485f2297fc

you have uv downloaded?

okay had to restart, it works
can you make the instructions better in the readme to install? mention to restart ...
also can you make it easier to use/more likely to work? for example to ask clarification for the query or make the AI show the query its going to use before sending for confirmation, like here
https://github.com/mediar-ai/screenpipe/tree/main/pipes/archive/perplexity-alike-asking-confirmation-rag-agent

sure

i think you are referring to  a feature that is not yet supported by Claude's desktop app

https://modelcontextprotocol.io/clients
https://modelcontextprotocol.io/docs/concepts/sampling
I'm trying different techniques to implement this.

i just used tools
https://github.com/mediar-ai/screenpipe/blob/6209eecdb6ae6bff4ac591a949235565f30252be/pipes/archive/perplexity-alike-asking-confirmation-rag-agent/screenpipe.ts#L164

I tried your above method, but with no success, it feels like we can easily handle with standard input and standard output but Claude desktop app does not give support to users direct access to the mcp server
I even studied some MCP servers codes but this feature is not implemented there
eg: in Filesystem MCP Server is doing CRUD operations on files but it does not ask for any confirmations  like "are you sure to delete this file?"

/approve
@kumarvivek1752 thanks! so u mean claude cannot create interactive UI buttons in the chat or something else like kind of input?

yes

/approve
@kumarvivek1752 thanks! so u mean claude cannot create interactive UI buttons in the chat or something else like kind of input?

yes Claude desktop not implemented this feature yet due to security reasons


Add a packages.md file to root of each repo as part of documentation scanning

packages.md should be of the following format, and contain a listing of every package within the repo.
| Service Name | Package Name as a link to the package | current version | link to source folder |
The "package name as a link to the package" should be a link out to the appropriate package manager. (maven, nuget, pypi, npm, etc)

@JonathanGiles as well.
I was wondering if we should actually have the build produce some of this information like the package name and version as part of an svg image and the table could just link to that. This would prevent the need to have it updated with the version all the time. The only time this would need to be updated would be if a service is added or removed.

Thinking about it more. The same image could be used on the readme specific to the library as well. I set up build processes before that basically update the svg with the latest build number and upload that to a known location for everything to reference as a "Status badge".

I really like the concept of the SVG keeping the version up to date, etc.
Pulling this work in, instead of pulling in the release notes, we will place a link (with SHA of the build artifacts) to this packages.md file. We will link directly to an anchor tag for the deploying package id. Then, from there, we'll look at the readme content to get the relative url.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

Codecov Report

Merging #97 (ee93320) into main (e988e10) will decrease coverage by 5.86%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #97      +/-   ##
==========================================
- Coverage   73.96%   68.09%   -5.87%
==========================================
  Files           4        3       -1
  Lines         457      351     -106
  Branches       28        0      -28
==========================================
- Hits          338      239      -99
+ Misses         85       78       -7
  Partials       34       34

Flag
Coverage Δ

cdk
?

go-lambda
68.09% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/index.ts

Continue to review full report at Codecov.

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


[release/v1.28.x] Cache maven local

Remake of #488 but push to main repo instead of fork.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/v1.28.x@844a3d1). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head df388cd differs from pull request most recent head 4077a4b. Consider uploading reports for the commit 4077a4b to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@                Coverage Diff                 @@
##             release/v1.28.x     #489   +/-   ##
==================================================
  Coverage                   ?   85.71%
  Complexity                 ?       19
==================================================
  Files                      ?        3
  Lines                      ?       49
  Branches                   ?        5
==================================================
  Hits                       ?       42
  Misses                     ?        3
  Partials                   ?        4

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Travis makes releases into bintray

For releases, use maven release from your local dev box.  Travis will
pick up the tag on it's run, and make the right pushes into bintray.

@areese we need to test this once it's in.  I've done some amount of testing on my user account's bintray, but this is now yahoo-org.

CLA is valid!

:+1:


HAL API to retrieve connected client information via Netlink and iw #28

Signed-off-by: Rajakumaran1106<EMAIL_ADDRESS>

https://jenkins.code.rdkcentral.com/job/github-triggered/127/ started

https://jenkins.code.rdkcentral.com/job/build-component-rdk-next/8566/ started.

Looks okay to me.


Print tree

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 66.66667% with 7 lines in your changes missing coverage. Please review.

Files with missing lines
Patch %
Lines

src/DecisionFunction.jl
70.00%
6 Missing :warning:

src/Tree.jl
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files with missing lines
Coverage Δ

src/OneTwoTree.jl
100.00% <ø> (ø)

src/Tree.jl
68.61% <0.00%> (-4.83%)
:arrow_down:

src/DecisionFunction.jl
70.00% <70.00%> (ø)

... and 1 file with indirect coverage changes


Logging

Closes #15 --
Nothing too exciting here. Just logging some error and startup messages so that ACI can pull the logs if we need to debug.

@zsusswein  They get piped to the UI: https://learn.microsoft.com/en-us/azure/container-instances/viewing-logs-in-portal
Or you can view via azure cli: https://learn.microsoft.com/en-us/azure/container-instances/container-instances-get-logs


Add examples from Noir libs

[ ] BigNum examples from here
[ ] Base64 examples from here
[ ] RSA example from here
[ ] String search examples for here
[ ] Regex examples part of zkEmail?

Related - https://github.com/AztecProtocol/dev-rel/issues/132

For these examples, is the intention to use pinned version numbers?
Or should we set up some testing that checks if a newer version of Noir is going to break these examples and notify us that we should update them?

Let's use pinned version numbers, and add to noir-examples repo.


Screenshot must be taken after wait_for condition is met

screenshot=True, takes screenshot before wait_for finishes, so on webpages where data loads later it take screenshot of empty pages.

@studio-anurag Great catch! You're absolutely right, and I’m on it. I'll update it soon, along with a few other things I got from the community. I’ll update everything and release it, and this time, I’ll definitely take the screenshot after waiting. I also made adjustments with the wait_for, it not only supports JavaScript expressions butΩ also waits for the presence of elements if you pass a CSS selector. This is crucial for taking more detailed screenshots. Plus, I plan to add more parameters for screenshots; right now, it’s the whole page, but soon you’ll be able to control location, size, and even specify which part of the page you want. All that is coming soon. Thanks for the very detailed feedback, much appreciated!

Great to hear back from you. I appreciate your efforts. Will be exploring more aspects.
This Library is really helpful and with further enhancements is going to be even more helpful.
Thanks


Format Lambda Response for API Gateway

It needs a special format: https://docs.aws.amazon.com/apigateway/latest/developerguide/set-up-lambda-proxy-integrations.html#api-gateway-simple-proxy-for-lambda-output-format

Closing because it looks like the accept function is already sending responses correctly.


Scope orders to impersonated user

Context
Support users should be able to view the correct subset of orders whilst impersonating
Changes proposed in this pull request
Add the impersonated user to the scope in the Orders controller
Guidance to review
Impersonate a user and visit /orders

 Add impersonation for the orders view


Beta 8

@Ralkage I noticed that you created fork for upgrade to beta 8. Are you planning to finish it? If not, maybe you could make a pull request, and Luceos would merge it to some devel branch? I could try to finish it.

Greetings @saleksin,
This extension has been updated for Beta 9, enjoy :)


Test validity of highlight ranges

Hi guys. Following on #52 that had an issue with vimls providing -1 as start/end of highlight range, I had a similar bug on pyls.
I'm working on a codebase I didn't write of a somewhat beginner python developer, and I had a sample similar to the following:
if True:
    '''
    some text
    '''
    print("hello_world")

On this sample of code (that shouldn't happen), pyls sends:
{
    code = "W0105",
    message = "[pointless-string-statement] String statement has no effect",
    range = {
      end = {
        character = 8,
        line = 3
      },
      start = {
        character = -1,
        line = 3
      }
    },
    severity = 2,
    source = "pylint"
  }

The problematic line here is start.character = -1. This value goes to the function responsible for highlighting, that throws:
Error executing vim.schedule lua callback: ...are/nvim/plugged/diagnostic-nvim/lua/diagnostic/util.lua:17: Column value outside range

Please note that this function is a copy from nvim's runtime, so without the plugin, it's neovim's identical function that throws that error:
Error executing vim.schedule lua callback: /usr/local/share/nvim/runtime/lua/vim/lsp/util.lua:628: Column value outside range

So #52 was solved by a server-side issue (that was extremely quickly fixed on vimls side), I guess this should be the preferred way to solve this issue as well (I will forward it to pyls).
However, as other cases like this one might appear, could it be interesting to find a non-intrusive way to log this error, as it was actually spamming my messages and made coding quite difficult.
P.S: I'm posting the issue here and not in diagnostic-nvim as it follows #52.

I push my fix in diagnostic-nvim, not sure how neovim and pyls deal with this problem though. Close this on my side.


Possibility to export Voronoi visualisations?

Is there a planned function to allow exporting Voronoi visualisation images as well? :)

Hi - I'll leave this open for now... It is pure front, no API.


feat(contracts): Use immutable variables for storage

We only initialize storage variables once per implementation deployment. As such, we can use immutable variables to save on storage loads.

For now, we've decided to table this feature, as the gas cost savings for a proposeL2Output call are at maximum ~4-5% and the immutable pattern is not recommended by OZ: https://docs.openzeppelin.com/upgrades-plugins/1.x/faq#why-cant-i-use-immutable-variables


Can't find instructions for installation on Linux

Problem description
I am looking for installation instructions on OpenSUSE.  Following the link led me to a 404.
Problem location

Other:
Link from https://blog.docker.com/2013/11/docker-0-7-docker-now-runs-on-any-linux-distribution/

"On Linux systems, first install the [Docker] for your OS as described on the Get Docker page, then come back here for instructions on installing Compose on Linux systems."
leads me to ...
https://docs.docker.com/install/index.md#server
Project version(s) affected

Suggestions for a fix

@simchuck For current images by the openSUSE Project, see opensuse/leap and opensuse/tumbleweed   images provided and maintained by the openSUSE Project release team at https://www.opensuse.org/. Thank you!

@simchuck have you tried some of these https://en.opensuse.org/SDB:Docker ?

The blog is no longer available. You can access the Get Docker page at https://docs.docker.com/get-docker/


[FEATURE]

Annotation Get /set method for Date class involving deep clone and shallow clone
like this ：
public Date getCreateDate() {
return (Date) createDate.clone();
}
public void setCreateDate(Date createDate) {
this.createDate = (Date) createDate.clone();
}
May expose internal representation by incorporating reference to mutable object

Solution: use LocalDate, is immutable.
https://github.com/rzwitserloot/lombok/wiki/ISSUES:-Why-we-close-issues-without-a-lot-of-explanation.