chip-tool unable to commission chip-app1 and all clusters app

Problem
chip-tool cannot commission all clusters app or chip-app on RaspberryPi+Linux with ToT
Configuration:
OS: Ubuntu 21.10
Platform: RaspberryPi
CommitSHA: a08613bed0a7ed48efc96571d7a799590a2f3ed5
Setup: chip-tool and chip-app1/chip-all-clusters-app running on the same raspberry pi

Chip Tool Logs
ubuntu@ubuntu:~/chip-certification-tool/backend/third_party/connectedhomeip/repo/examples/chip-tool/out/debug$ ./chip-tool pairing onnetwork-long 0x654321 20202021 3840
[1644531046.749763][92866:92866] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-uBVhf5)
[1644531046.750478][92866:92866] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1644531046.750537][92866:92866] CHIP:DL: NVS set: chip-counters/reboot-count = 4 (0x4)
[1644531046.751401][92866:92866] CHIP:DL: Got Ethernet interface: eth0
[1644531046.751960][92866:92866] CHIP:DL: Found the primary Ethernet interface:eth0
[1644531046.752546][92866:92866] CHIP:DL: Got WiFi interface: wlan0
[1644531046.752618][92866:92866] CHIP:DL: Failed to reset WiFi statistic counts
[1644531046.752682][92866:92866] CHIP:IN: UDP::Init bind&listen port=5542
[1644531046.752790][92866:92866] CHIP:IN: UDP::Init bound to port=5542
[1644531046.752816][92866:92866] CHIP:IN: UDP::Init bind&listen port=5542
[1644531046.752903][92866:92866] CHIP:IN: UDP::Init bound to port=5542
[1644531046.752928][92866:92866] CHIP:IN: TransportMgr initialized
[1644531046.752963][92866:92866] CHIP:DIS: Init fabric pairing table with server storage
[1644531046.755051][92866:92866] CHIP:IN: Loading certs from storage
[1644531046.755181][92866:92866] CHIP:IN: Generating compressed fabric ID using uncompressed fabric ID 0x0000000000000001 and root pubkey
[1644531046.755213][92866:92866] CHIP:IN: 0x04, 0x7e, 0x67, 0x39, 0x26, 0x44, 0x23, 0xa3,
[1644531046.755237][92866:92866] CHIP:IN: 0x85, 0xb8, 0x19, 0xb5, 0xfd, 0xb8, 0x45, 0x60,
[1644531046.755260][92866:92866] CHIP:IN: 0xef, 0x61, 0x7b, 0x06, 0xf3, 0x4c, 0x2c, 0x21,
[1644531046.755282][92866:92866] CHIP:IN: 0xe7, 0x73, 0x20, 0x7a, 0x28, 0x04, 0xdf, 0xe4,
[1644531046.755304][92866:92866] CHIP:IN: 0xab, 0xcf, 0xfc, 0xfe, 0x2e, 0x08, 0x9d, 0xa0,
[1644531046.755327][92866:92866] CHIP:IN: 0x10, 0x2a, 0x0c, 0x4f, 0x1b, 0xcd, 0xdd, 0x8a,
[1644531046.755350][92866:92866] CHIP:IN: 0x62, 0x0f, 0xf3, 0x4a, 0xd5, 0x42, 0x03, 0xc2,
[1644531046.755372][92866:92866] CHIP:IN: 0x69, 0x78, 0xca, 0xbd, 0x29, 0x31, 0x70, 0x33,
[1644531046.755391][92866:92866] CHIP:IN: 0x9a,
[1644531046.755452][92866:92866] CHIP:IN: Generated compressed fabric ID
[1644531046.755478][92866:92866] CHIP:IN: 0x37, 0x49, 0x22, 0xd7, 0xb8, 0x89, 0x72, 0x88,
[1644531046.755752][92866:92866] CHIP:IN: Loading certs from storage
[1644531046.755830][92866:92866] CHIP:IN: Generating compressed fabric ID using uncompressed fabric ID 0x0000000000000002 and root pubkey
[1644531046.755859][92866:92866] CHIP:IN: 0x04, 0x7e, 0x67, 0x39, 0x26, 0x44, 0x23, 0xa3,
[1644531046.755883][92866:92866] CHIP:IN: 0x85, 0xb8, 0x19, 0xb5, 0xfd, 0xb8, 0x45, 0x60,
[1644531046.755906][92866:92866] CHIP:IN: 0xef, 0x61, 0x7b, 0x06, 0xf3, 0x4c, 0x2c, 0x21,
[1644531046.755928][92866:92866] CHIP:IN: 0xe7, 0x73, 0x20, 0x7a, 0x28, 0x04, 0xdf, 0xe4,
[1644531046.755950][92866:92866] CHIP:IN: 0xab, 0xcf, 0xfc, 0xfe, 0x2e, 0x08, 0x9d, 0xa0,
[1644531046.755972][92866:92866] CHIP:IN: 0x10, 0x2a, 0x0c, 0x4f, 0x1b, 0xcd, 0xdd, 0x8a,
[1644531046.755995][92866:92866] CHIP:IN: 0x62, 0x0f, 0xf3, 0x4a, 0xd5, 0x42, 0x03, 0xc2,
[1644531046.756017][92866:92866] CHIP:IN: 0x69, 0x78, 0xca, 0xbd, 0x29, 0x31, 0x70, 0x33,
[1644531046.756036][92866:92866] CHIP:IN: 0x9a,
[1644531046.756077][92866:92866] CHIP:IN: Generated compressed fabric ID
[1644531046.756103][92866:92866] CHIP:IN: 0xae, 0x15, 0x97, 0x2c, 0x47, 0x66, 0xa3, 0xb7,
[1644531046.756321][92866:92866] CHIP:IN: Loading certs from storage
[1644531046.756392][92866:92866] CHIP:IN: Generating compressed fabric ID using uncompressed fabric ID 0x0000000000000003 and root pubkey
[1644531046.756422][92866:92866] CHIP:IN: 0x04, 0x7e, 0x67, 0x39, 0x26, 0x44, 0x23, 0xa3,
[1644531046.756445][92866:92866] CHIP:IN: 0x85, 0xb8, 0x19, 0xb5, 0xfd, 0xb8, 0x45, 0x60,
[1644531046.756468][92866:92866] CHIP:IN: 0xef, 0x61, 0x7b, 0x06, 0xf3, 0x4c, 0x2c, 0x21,
[1644531046.756490][92866:92866] CHIP:IN: 0xe7, 0x73, 0x20, 0x7a, 0x28, 0x04, 0xdf, 0xe4,
[1644531046.756512][92866:92866] CHIP:IN: 0xab, 0xcf, 0xfc, 0xfe, 0x2e, 0x08, 0x9d, 0xa0,
[1644531046.756534][92866:92866] CHIP:IN: 0x10, 0x2a, 0x0c, 0x4f, 0x1b, 0xcd, 0xdd, 0x8a,
[1644531046.756557][92866:92866] CHIP:IN: 0x62, 0x0f, 0xf3, 0x4a, 0xd5, 0x42, 0x03, 0xc2,
[1644531046.756579][92866:92866] CHIP:IN: 0x69, 0x78, 0xca, 0xbd, 0x29, 0x31, 0x70, 0x33,
[1644531046.756598][92866:92866] CHIP:IN: 0x9a,
[1644531046.756637][92866:92866] CHIP:IN: Generated compressed fabric ID
[1644531046.756662][92866:92866] CHIP:IN: 0xa4, 0xf8, 0x62, 0xe1, 0x81, 0xa3, 0xf6, 0xd7,
[1644531046.756984][92866:92866] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-L4lIwY)
[1644531046.771065][92866:92866] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1644531046.771135][92866:92866] CHIP:DL: NVS set: chip-counters/GlobalMCTR = 4000 (0xFA0)
[1644531046.771287][92866:92866] CHIP:ZCL: Using ZAP configuration...
[1644531046.778058][92866:92866] CHIP:DL: MDNS failed to join multicast group on wlan0 for address type IPv4: ../../third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:772: Inet Error 0x00000110: Address not found
[1644531046.785808][92866:92866] CHIP:DL: MDNS failed to join multicast group on veth51ecf59 for address type IPv4: ../../third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:772: Inet Error 0x00000110: Address not found
[1644531046.787549][92866:92866] CHIP:DL: MDNS failed to join multicast group on vethb8796c7 for address type IPv4: ../../third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:772: Inet Error 0x00000110: Address not found
[1644531046.789217][92866:92866] CHIP:DL: MDNS failed to join multicast group on veth9568210 for address type IPv4: ../../third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:772: Inet Error 0x00000110: Address not found
[1644531046.790986][92866:92866] CHIP:DL: MDNS failed to join multicast group on veth16faf8f for address type IPv4: ../../third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:772: Inet Error 0x00000110: Address not found
[1644531046.792679][92866:92866] CHIP:DL: MDNS failed to join multicast group on veth72a3920 for address type IPv4: ../../third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:772: Inet Error 0x00000110: Address not found
[1644531046.793083][92866:92866] CHIP:CTL: System State Initialized...
[1644531046.793216][92866:92866] CHIP:IN: UDP::Init bind&listen port=5550
[1644531046.793314][92866:92866] CHIP:IN: UDP::Init bound to port=5550
[1644531046.793342][92866:92866] CHIP:IN: UDP::Init bind&listen port=5550
[1644531046.793429][92866:92866] CHIP:IN: UDP::Init bound to port=5550
[1644531046.793454][92866:92866] CHIP:IN: TransportMgr initialized
[1644531046.794431][92866:92866] CHIP:CTL: Generating NOC
[1644531046.795386][92866:92866] CHIP:DIS: Verifying the received credentials
[1644531046.797076][92866:92866] CHIP:IN: Generating compressed fabric ID using uncompressed fabric ID 0x0000000000000001 and root pubkey
[1644531046.797113][92866:92866] CHIP:IN: 0x04, 0x7e, 0x67, 0x39, 0x26, 0x44, 0x23, 0xa3,
[1644531046.797137][92866:92866] CHIP:IN: 0x85, 0xb8, 0x19, 0xb5, 0xfd, 0xb8, 0x45, 0x60,
[1644531046.797160][92866:92866] CHIP:IN: 0xef, 0x61, 0x7b, 0x06, 0xf3, 0x4c, 0x2c, 0x21,
[1644531046.797182][92866:92866] CHIP:IN: 0xe7, 0x73, 0x20, 0x7a, 0x28, 0x04, 0xdf, 0xe4,
[1644531046.797205][92866:92866] CHIP:IN: 0xab, 0xcf, 0xfc, 0xfe, 0x2e, 0x08, 0x9d, 0xa0,
[1644531046.797228][92866:92866] CHIP:IN: 0x10, 0x2a, 0x0c, 0x4f, 0x1b, 0xcd, 0xdd, 0x8a,
[1644531046.797250][92866:92866] CHIP:IN: 0x62, 0x0f, 0xf3, 0x4a, 0xd5, 0x42, 0x03, 0xc2,
[1644531046.797272][92866:92866] CHIP:IN: 0x69, 0x78, 0xca, 0xbd, 0x29, 0x31, 0x70, 0x33,
[1644531046.797291][92866:92866] CHIP:IN: 0x9a,
[1644531046.797345][92866:92866] CHIP:IN: Generated compressed fabric ID
[1644531046.797372][92866:92866] CHIP:IN: 0x37, 0x49, 0x22, 0xd7, 0xb8, 0x89, 0x72, 0x88,
[1644531046.797395][92866:92866] CHIP:DIS: Added new fabric at index: 1, Initialized: 1
[1644531046.797416][92866:92866] CHIP:DIS: Assigned compressed fabric ID: 0x374922D7B8897288, node ID: 0x000000000001B669
[1644531046.797438][92866:92866] CHIP:CTL: Joined the fabric at index 1. Compressed fabric ID is: 0x374922D7B8897288
[1644531046.797483][92866:92866] CHIP:IN: UDP::Init bind&listen port=5550
[1644531046.797606][92866:92866] CHIP:IN: UDP::Init bound to port=5550
[1644531046.797631][92866:92866] CHIP:IN: UDP::Init bind&listen port=5550
[1644531046.797720][92866:92866] CHIP:IN: UDP::Init bound to port=5550
[1644531046.797743][92866:92866] CHIP:IN: TransportMgr initialized
[1644531046.798690][92866:92866] CHIP:CTL: Generating NOC
[1644531046.799612][92866:92866] CHIP:DIS: Verifying the received credentials
[1644531046.801285][92866:92866] CHIP:IN: Generating compressed fabric ID using uncompressed fabric ID 0x0000000000000002 and root pubkey
[1644531046.801320][92866:92866] CHIP:IN: 0x04, 0x7e, 0x67, 0x39, 0x26, 0x44, 0x23, 0xa3,
[1644531046.801344][92866:92866] CHIP:IN: 0x85, 0xb8, 0x19, 0xb5, 0xfd, 0xb8, 0x45, 0x60,
[1644531046.801367][92866:92866] CHIP:IN: 0xef, 0x61, 0x7b, 0x06, 0xf3, 0x4c, 0x2c, 0x21,
[1644531046.801389][92866:92866] CHIP:IN: 0xe7, 0x73, 0x20, 0x7a, 0x28, 0x04, 0xdf, 0xe4,
[1644531046.801412][92866:92866] CHIP:IN: 0xab, 0xcf, 0xfc, 0xfe, 0x2e, 0x08, 0x9d, 0xa0,
[1644531046.801434][92866:92866] CHIP:IN: 0x10, 0x2a, 0x0c, 0x4f, 0x1b, 0xcd, 0xdd, 0x8a,
[1644531046.801456][92866:92866] CHIP:IN: 0x62, 0x0f, 0xf3, 0x4a, 0xd5, 0x42, 0x03, 0xc2,
[1644531046.801478][92866:92866] CHIP:IN: 0x69, 0x78, 0xca, 0xbd, 0x29, 0x31, 0x70, 0x33,
[1644531046.801497][92866:92866] CHIP:IN: 0x9a,
[1644531046.801548][92866:92866] CHIP:IN: Generated compressed fabric ID
[1644531046.801574][92866:92866] CHIP:IN: 0xae, 0x15, 0x97, 0x2c, 0x47, 0x66, 0xa3, 0xb7,
[1644531046.801600][92866:92866] CHIP:DIS: Added new fabric at index: 2, Initialized: 1
[1644531046.801621][92866:92866] CHIP:DIS: Assigned compressed fabric ID: 0xAE15972C4766A3B7, node ID: 0x000000000001B669
[1644531046.801643][92866:92866] CHIP:CTL: Joined the fabric at index 2. Compressed fabric ID is: 0xAE15972C4766A3B7
[1644531046.801687][92866:92866] CHIP:IN: UDP::Init bind&listen port=5550
[1644531046.801810][92866:92866] CHIP:IN: UDP::Init bound to port=5550
[1644531046.801836][92866:92866] CHIP:IN: UDP::Init bind&listen port=5550
[1644531046.801952][92866:92866] CHIP:IN: UDP::Init bound to port=5550
[1644531046.801978][92866:92866] CHIP:IN: TransportMgr initialized
[1644531046.802804][92866:92866] CHIP:CTL: Generating NOC
[1644531046.803783][92866:92866] CHIP:DIS: Verifying the received credentials
[1644531046.805439][92866:92866] CHIP:IN: Generating compressed fabric ID using uncompressed fabric ID 0x0000000000000003 and root pubkey
[1644531046.805477][92866:92866] CHIP:IN: 0x04, 0x7e, 0x67, 0x39, 0x26, 0x44, 0x23, 0xa3,
[1644531046.805501][92866:92866] CHIP:IN: 0x85, 0xb8, 0x19, 0xb5, 0xfd, 0xb8, 0x45, 0x60,
[1644531046.805524][92866:92866] CHIP:IN: 0xef, 0x61, 0x7b, 0x06, 0xf3, 0x4c, 0x2c, 0x21,
[1644531046.805546][92866:92866] CHIP:IN: 0xe7, 0x73, 0x20, 0x7a, 0x28, 0x04, 0xdf, 0xe4,
[1644531046.805569][92866:92866] CHIP:IN: 0xab, 0xcf, 0xfc, 0xfe, 0x2e, 0x08, 0x9d, 0xa0,
[1644531046.805591][92866:92866] CHIP:IN: 0x10, 0x2a, 0x0c, 0x4f, 0x1b, 0xcd, 0xdd, 0x8a,
[1644531046.805613][92866:92866] CHIP:IN: 0x62, 0x0f, 0xf3, 0x4a, 0xd5, 0x42, 0x03, 0xc2,
[1644531046.805635][92866:92866] CHIP:IN: 0x69, 0x78, 0xca, 0xbd, 0x29, 0x31, 0x70, 0x33,
[1644531046.805655][92866:92866] CHIP:IN: 0x9a,
[1644531046.805707][92866:92866] CHIP:IN: Generated compressed fabric ID
[1644531046.805733][92866:92866] CHIP:IN: 0xa4, 0xf8, 0x62, 0xe1, 0x81, 0xa3, 0xf6, 0xd7,
[1644531046.805759][92866:92866] CHIP:DIS: Added new fabric at index: 3, Initialized: 1
[1644531046.805780][92866:92866] CHIP:DIS: Assigned compressed fabric ID: 0xA4F862E181A3F6D7, node ID: 0x000000000001B669
[1644531046.805802][92866:92866] CHIP:CTL: Joined the fabric at index 3. Compressed fabric ID is: 0xA4F862E181A3F6D7
[1644531046.805846][92866:92866] CHIP:IN: UDP::Init bind&listen port=5550
[1644531046.806601][92866:92866] CHIP:IN: UDP::Init bound to port=5550
[1644531046.806635][92866:92866] CHIP:IN: UDP::Init bind&listen port=5550
[1644531046.806724][92866:92866] CHIP:IN: UDP::Init bound to port=5550
[1644531046.806747][92866:92866] CHIP:IN: TransportMgr initialized
[1644531046.807053][92866:92871] CHIP:DL: CHIP task running
[1644531046.808230][92866:92871] CHIP:DIS: Attempt to mDNS broadcast failed:  ../../third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000065: Network is unreachable
[1644531046.808784][92866:92871] CHIP:DIS: Attempt to mDNS broadcast failed:  ../../third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000065: Network is unreachable
[1644531046.812256][92866:92871] CHIP:TOO: Discovered Device: fd1d:8168:485b:5:dea6:32ff:febe:8d58:5540
[1644531046.812528][92866:92871] CHIP:SC: Assigned local session key ID 1
[1644531046.812604][92866:92871] CHIP:SC: Including MRP parameters in PBKDF param request
[1644531046.812732][92866:92871] CHIP:IN: Prepared unauthenticated message 0xaaaadd49e6d8 to 0x0000000000000000 (0)  of type 0x20 and protocolId (0, 0) on exchange 33192i with MessageCounter:2723366131.
[1644531046.812781][92866:92871] CHIP:IN: Sending unauthenticated msg 0xaaaadd49e6d8 with MessageCounter:2723366131 to 0x0000000000000000 at monotonic time: 9237454 msec
[1644531046.814816][92866:92871] CHIP:SC: Sent PBKDF param request
[1644531046.814879][92866:92871] CHIP:CTL: Commission called for node ID 0x0000000000654321
[1644531046.814915][92866:92871] CHIP:CTL: Setting attestation nonce to random value
[1644531046.814982][92866:92871] CHIP:CTL: Setting CSR nonce to random value
[1644531046.815853][92866:92871] CHIP:IN: Received malformed unsecure packet with source 0x0000000000000000 destination 0x0000000000000000

Chip All Clusters App Logs
ubuntu@ubuntu:~/chip-certification-tool/backend/third_party/connectedhomeip/repo/examples/all-clusters-app/linux/out/debug$ ./chip-all-clusters-app
[1644531020.904719][92061:92061] CHIP:DL: writing settings to file (/tmp/chip_kvs-0lvQNy)
[1644531020.905073][92061:92061] CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
[1644531020.911095][92061:92061] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-facqUX)
[1644531020.911761][92061:92061] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1644531020.911815][92061:92061] CHIP:DL: NVS set: chip-counters/reboot-count = 2 (0x2)
[1644531020.912729][92061:92061] CHIP:DL: Got Ethernet interface: eth0
[1644531020.913309][92061:92061] CHIP:DL: Found the primary Ethernet interface:eth0
[1644531020.913954][92061:92061] CHIP:DL: Got WiFi interface: wlan0
[1644531020.914032][92061:92061] CHIP:DL: Failed to reset WiFi statistic counts
[1644531020.914100][92061:92061] CHIP:DL: Device Configuration:
[1644531020.914127][92061:92061] CHIP:DL:   Serial Number: TEST_SN
[1644531020.914161][92061:92061] CHIP:DL:   Vendor Id: 65521 (0xFFF1)
[1644531020.914181][92061:92061] CHIP:DL:   Product Id: 32769 (0x8001)
[1644531020.914212][92061:92061] CHIP:DL:   Hardware Version: 0
[1644531020.914235][92061:92061] CHIP:DL:   Setup Pin Code: 20202021
[1644531020.914257][92061:92061] CHIP:DL:   Setup Discriminator: 3840 (0xF00)
[1644531020.914291][92061:92061] CHIP:DL:   Manufacturing Date: (not set)
[1644531020.914312][92061:92061] CHIP:DL:   Device Type: 65535 (0xFFFF)
[1644531020.914376][92061:92061] CHIP:SVR: SetupQRCode: [MT:-24J042C00KA0648G00]
[1644531020.914415][92061:92061] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code:
[1644531020.914436][92061:92061] CHIP:SVR: https://dhrishi.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J042C00KA0648G00
[1644531020.914466][92061:92061] CHIP:SVR: Manual pairing code: [34970112332]
[1644531020.914491][92061:92061] CHIP:SVR: Long manual pairing code: [34970112332]
[1644531020.914528][92061:92061] CHIP:DL: wpa_supplicant: Start WiFi management
[1644531020.919374][92061:92064] CHIP:DL: wpa_supplicant: connected to wpa_supplicant proxy
[1644531020.920862][92061:92064] CHIP:DL: wpa_supplicant: WiFi interface: /fi/w1/wpa_supplicant1/Interfaces/0
[1644531020.930660][92061:92064] CHIP:DL: wpa_supplicant: connected to wpa_supplicant interface proxy
[1644531020.930966][92061:92064] CHIP:DL: wpa_supplicant: connected to wpa_supplicant bss proxy
[1644531021.015206][92061:92061] CHIP:DIS: Add fabric pairing table delegate
[1644531021.015309][92061:92061] CHIP:ZCL: Using ZAP configuration...
[1644531021.015677][92061:92061] CHIP:DMG: Failed to read stored attribute (0, 0x0000_0028, 0x0000_0005: ../../third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
[1644531021.015823][92061:92061] CHIP:DMG: Failed to read stored attribute (0, 0x0000_0028, 0x0000_0010: ../../third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
[1644531021.015921][92061:92061] CHIP:DMG: Failed to read stored attribute (0, 0x0000_002B, 0x0000_0001: ../../third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
[1644531021.016005][92061:92061] CHIP:DMG: Failed to read stored attribute (0, 0x0000_002C, 0x0000_0000: ../../third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
[1644531021.016081][92061:92061] CHIP:DMG: Failed to read stored attribute (0, 0x0000_002C, 0x0000_0001: ../../third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
[1644531021.016187][92061:92061] CHIP:DMG: Failed to read stored attribute (0, 0x0000_002D, 0x0000_0000: ../../third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
[1644531021.016592][92061:92061] CHIP:DMG: Failed to read stored attribute (1, 0x0000_0008, 0x0000_0000: ../../third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
[1644531021.016705][92061:92061] CHIP:DMG: Failed to read stored attribute (1, 0x0000_0008, 0x0000_4000: ../../third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
[1644531021.017010][92061:92061] CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_0003: ../../third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
[1644531021.017088][92061:92061] CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_0004: ../../third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
[1644531021.017162][92061:92061] CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_0007: ../../third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
[1644531021.017237][92061:92061] CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_0008: ../../third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
[1644531021.017311][92061:92061] CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_0009: ../../third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
[1644531021.017413][92061:92061] CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_000E: ../../third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
[1644531021.017490][92061:92061] CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_000F: ../../third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
[1644531021.017615][92061:92061] CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_0010: ../../third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
[1644531021.017696][92061:92061] CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_0011: ../../third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
[1644531021.017794][92061:92061] CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_0012: ../../third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
[1644531021.017870][92061:92061] CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_0013: ../../third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
[1644531021.018022][92061:92061] CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_0017: ../../third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
[1644531021.018900][92061:92061] CHIP:ZCL: Initiating Admin Commissioning cluster.
[1644531021.018961][92061:92061] CHIP:ZCL: Door Lock server initialized
[1644531021.019023][92061:92061] CHIP:ZCL: OpCreds: Initiating OpCreds cluster by writing fabrics list from fabric table.
[1644531021.019075][92061:92061] CHIP:DIS: Add fabric pairing table delegate
[1644531021.019152][92061:92061] CHIP:DMG: Endpoint 0, Cluster 0x0000_0003 update version to 8ad63700
[1644531021.019241][92061:92061] CHIP:DMG: Endpoint 0, Cluster 0x0000_0004 update version to 1dc760a
[1644531021.019700][92061:92061] CHIP:DL: writing settings to file (/tmp/chip_kvs-AnvTCY)
[1644531021.020708][92061:92061] CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
[1644531021.020823][92061:92061] CHIP:DMG: Endpoint 0, Cluster 0x0000_002B update version to 4556b0f3
[1644531021.020916][92061:92061] CHIP:DMG: Endpoint 1, Cluster 0x0000_0003 update version to 8efe8929
[1644531021.020983][92061:92061] CHIP:DMG: Endpoint 1, Cluster 0x0000_0004 update version to ea9625f
[1644531021.021071][92061:92061] CHIP:DMG: Endpoint 1, Cluster 0x0000_0005 update version to 2d35acf5
[1644531021.021425][92061:92061] CHIP:DL: writing settings to file (/tmp/chip_kvs-dGXqDL)
[1644531021.022412][92061:92061] CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
[1644531021.022522][92061:92061] CHIP:DMG: Endpoint 1, Cluster 0x0000_0008 update version to ae7ae5a4
[1644531021.022600][92061:92061] CHIP:ZCL: Window Covering Cluster init
[1644531021.022655][92061:92061] CHIP:ZCL: Initialize PCC Server Cluster [EP:1]
[1644531021.022740][92061:92061] CHIP:DMG: Endpoint 1, Cluster 0x0000_0300 update version to 369de2e9
[1644531021.022832][92061:92061] CHIP:DMG: Endpoint 1, Cluster 0x0000_0300 update version to 369de2ea
[1644531021.022904][92061:92061] CHIP:DMG: Endpoint 1, Cluster 0x0000_0300 update version to 369de2eb
[1644531021.022973][92061:92061] CHIP:DMG: Endpoint 1, Cluster 0x0000_0406 update version to f7d1a725
[1644531021.023071][92061:92061] CHIP:DMG: Endpoint 1, Cluster 0x0000_0406 update version to f7d1a726
[1644531021.023133][92061:92061] CHIP:ZCL: WARNING: ATTRIBUTES ARE NOT BEING STORED IN FLASH!
[1644531021.023205][92061:92061] CHIP:ZCL: DEVICE WILL NOT FUNCTION PROPERLY AFTER REBOOTING!!
[1644531021.023264][92061:92061] CHIP:DMG: Endpoint 1, Cluster 0x0000_0500 update version to 2e71a43
[1644531021.023351][92061:92061] CHIP:DMG: Endpoint 1, Cluster 0x0000_0500 update version to 2e71a44
[1644531021.023413][92061:92061] CHIP:ZCL: Failed to send IAS Zone update. Err 0x70
[1644531021.023485][92061:92061] CHIP:ZCL: TV Linux App: LowPower::SetDefaultDelegate
[1644531021.023550][92061:92061] CHIP:DMG: Endpoint 2, Cluster 0x0000_0004 update version to ebfcf3d0
[1644531021.023616][92061:92061] CHIP:DMG: Endpoint 2, Cluster 0x0000_0406 update version to e06aff6c
[1644531021.023698][92061:92061] CHIP:DMG: Endpoint 2, Cluster 0x0000_0406 update version to e06aff6d
[1644531021.023756][92061:92061] CHIP:DIS: Init fabric pairing table with server storage
[1644531021.024072][92061:92061] CHIP:DMG: AccessControl: initializing
[1644531021.024149][92061:92061] CHIP:DMG: Examples::AccessControlDelegate::Init
[1644531021.024213][92061:92061] CHIP:DMG: AccessControl: unable to load stored ACL entries; using empty list instead
[1644531021.024305][92061:92061] CHIP:IN: UDP::Init bind&listen port=5540
[1644531021.024575][92061:92061] CHIP:IN: UDP::Init bound to port=5540
[1644531021.024642][92061:92061] CHIP:IN: UDP::Init bind&listen port=5540
[1644531021.024878][92061:92061] CHIP:IN: UDP::Init bound to port=5540
[1644531021.024964][92061:92061] CHIP:IN: TransportMgr initialized
[1644531021.025315][92061:92061] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-qi2GxH)
[1644531021.026177][92061:92061] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1644531021.026229][92061:92061] CHIP:DL: NVS set: chip-counters/GlobalMCTR = 2000 (0x7D0)
[1644531021.026513][92061:92061] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-JhAfRF)
[1644531021.026998][92061:92061] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1644531021.027048][92061:92061] CHIP:DL: NVS set: chip-counters/global-eidc = 65536 (0x10000)
[1644531021.027105][92061:92061] CHIP:DIS: Fabric 1 is not yet configured
[1644531021.027143][92061:92061] CHIP:DIS: Fabric 2 is not yet configured
[1644531021.027190][92061:92061] CHIP:DIS: Fabric 3 is not yet configured
[1644531021.027225][92061:92061] CHIP:DIS: Fabric 4 is not yet configured
[1644531021.027259][92061:92061] CHIP:DIS: Fabric 5 is not yet configured
[1644531021.027308][92061:92061] CHIP:DIS: Fabric 6 is not yet configured
[1644531021.027343][92061:92061] CHIP:DIS: Fabric 7 is not yet configured
[1644531021.027387][92061:92061] CHIP:DIS: Fabric 8 is not yet configured
[1644531021.027432][92061:92061] CHIP:DIS: Fabric 9 is not yet configured
[1644531021.027466][92061:92061] CHIP:DIS: Fabric 10 is not yet configured
[1644531021.027510][92061:92061] CHIP:DIS: Fabric 11 is not yet configured
[1644531021.027556][92061:92061] CHIP:DIS: Fabric 12 is not yet configured
[1644531021.027593][92061:92061] CHIP:DIS: Fabric 13 is not yet configured
[1644531021.027639][92061:92061] CHIP:DIS: Fabric 14 is not yet configured
[1644531021.027673][92061:92061] CHIP:DIS: Fabric 15 is not yet configured
[1644531021.027717][92061:92061] CHIP:DIS: Fabric 16 is not yet configured
[1644531021.027770][92061:92061] CHIP:SC: Assigned local session key ID 1
[1644531021.027798][92061:92061] CHIP:SC: Waiting for PBKDF param request
[1644531021.027847][92061:92061] CHIP:DIS: DNS-SD StartServer modeHasValue=1 modeValue=1
[1644531021.030989][92061:92061] CHIP:DL: MDNS failed to join multicast group on wlan0 for address type IPv4: ../../third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:772: Inet Error 0x00000110: Address not found
[1644531021.035560][92061:92061] CHIP:DL: MDNS failed to join multicast group on veth51ecf59 for address type IPv4: ../../third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:772: Inet Error 0x00000110: Address not found
[1644531021.037251][92061:92061] CHIP:DL: MDNS failed to join multicast group on vethb8796c7 for address type IPv4: ../../third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:772: Inet Error 0x00000110: Address not found
[1644531021.038880][92061:92061] CHIP:DL: MDNS failed to join multicast group on veth9568210 for address type IPv4: ../../third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:772: Inet Error 0x00000110: Address not found
[1644531021.040494][92061:92061] CHIP:DL: MDNS failed to join multicast group on veth16faf8f for address type IPv4: ../../third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:772: Inet Error 0x00000110: Address not found
[1644531021.042091][92061:92061] CHIP:DL: MDNS failed to join multicast group on veth72a3920 for address type IPv4: ../../third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:772: Inet Error 0x00000110: Address not found
[1644531021.042393][92061:92061] CHIP:DIS: CHIP minimal mDNS started advertising.
[1644531021.044534][92061:92061] CHIP:DIS: Failed to find a valid admin pairing. Node ID unknown
[1644531021.044608][92061:92061] CHIP:DIS: Start dns-sd server - no current nodeId
[1644531021.044640][92061:92061] CHIP:DL: MAC is not known, using a default.
[1644531021.044683][92061:92061] CHIP:DIS: Advertise commission parameter vendorID=65521 productID=32769 discriminator=3840/15
[1644531021.044780][92061:92061] CHIP:DIS: CHIP minimal mDNS configured as 'Commissionable node device'.
[1644531021.048248][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from <IP_ADDRESS>
[1644531021.051256][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from <IP_ADDRESS>
[1644531021.054703][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from <IP_ADDRESS>
[1644531021.057848][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from <IP_ADDRESS>
[1644531021.061143][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fd1d:8168:485b:5:dea6:32ff:febe:8d58
[1644531021.064375][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fd3f:6f80:c617:7:dea6:32ff:febe:8d58
[1644531021.067537][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from 2601:647:4100:b59:dea6:32ff:febe:8d58
[1644531021.070702][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fd56:4c87:932d:1:dea6:32ff:febe:8d58
[1644531021.073846][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::dea6:32ff:febe:8d58
[1644531021.077653][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::42:4fff:fe24:3368
[1644531021.080706][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fd00:6d61:7474:6572::1
[1644531021.083816][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::42:b0ff:fe74:1239
[1644531021.086915][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::1
[1644531021.089871][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::f81f:b3ff:febf:672c
[1644531021.093091][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::e88e:4cff:fe6c:10aa
[1644531021.095986][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::781a:3cff:fe77:3e48
[1644531021.100271][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::e88f:69ff:fe8a:df53
[1644531021.103318][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::d80b:10ff:fe11:35d9
[1644531021.103550][92061:92061] CHIP:DIS: Scheduling Discovery timeout in secs=900
[1644531021.103600][92061:92061] CHIP:DIS: DNS-SD StartServer modeHasValue=0 modeValue=0
[1644531021.108174][92061:92061] CHIP:DL: MDNS failed to join multicast group on wlan0 for address type IPv4: ../../third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:772: Inet Error 0x00000110: Address not found
[1644531021.112411][92061:92061] CHIP:DL: MDNS failed to join multicast group on veth51ecf59 for address type IPv4: ../../third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:772: Inet Error 0x00000110: Address not found
[1644531021.114523][92061:92061] CHIP:DL: MDNS failed to join multicast group on vethb8796c7 for address type IPv4: ../../third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:772: Inet Error 0x00000110: Address not found
[1644531021.116117][92061:92061] CHIP:DL: MDNS failed to join multicast group on veth9568210 for address type IPv4: ../../third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:772: Inet Error 0x00000110: Address not found
[1644531021.117737][92061:92061] CHIP:DL: MDNS failed to join multicast group on veth16faf8f for address type IPv4: ../../third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:772: Inet Error 0x00000110: Address not found
[1644531021.119333][92061:92061] CHIP:DL: MDNS failed to join multicast group on veth72a3920 for address type IPv4: ../../third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:772: Inet Error 0x00000110: Address not found
[1644531021.119635][92061:92061] CHIP:DIS: CHIP minimal mDNS started advertising.
[1644531021.122980][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from <IP_ADDRESS>
[1644531021.125926][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from <IP_ADDRESS>
[1644531021.128813][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from <IP_ADDRESS>
[1644531021.132678][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from <IP_ADDRESS>
[1644531021.135952][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fd1d:8168:485b:5:dea6:32ff:febe:8d58
[1644531021.139569][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fd3f:6f80:c617:7:dea6:32ff:febe:8d58
[1644531021.142685][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from 2601:647:4100:b59:dea6:32ff:febe:8d58
[1644531021.145803][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fd56:4c87:932d:1:dea6:32ff:febe:8d58
[1644531021.150073][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::dea6:32ff:febe:8d58
[1644531021.153000][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::42:4fff:fe24:3368
[1644531021.156595][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fd00:6d61:7474:6572::1
[1644531021.159757][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::42:b0ff:fe74:1239
[1644531021.162892][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::1
[1644531021.165801][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::f81f:b3ff:febf:672c
[1644531021.168747][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::e88e:4cff:fe6c:10aa
[1644531021.172221][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::781a:3cff:fe77:3e48
[1644531021.175100][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::e88f:69ff:fe8a:df53
[1644531021.178418][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::d80b:10ff:fe11:35d9
[1644531021.178690][92061:92061] CHIP:DIS: Failed to find a valid admin pairing. Node ID unknown
[1644531021.178725][92061:92061] CHIP:DIS: Start dns-sd server - no current nodeId
[1644531021.178753][92061:92061] CHIP:DL: MAC is not known, using a default.
[1644531021.178798][92061:92061] CHIP:DIS: Advertise commission parameter vendorID=65521 productID=32769 discriminator=3840/15
[1644531021.178869][92061:92061] CHIP:DIS: CHIP minimal mDNS configured as 'Commissionable node device'.
[1644531021.182323][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from <IP_ADDRESS>
[1644531021.185204][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from <IP_ADDRESS>
[1644531021.189184][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from <IP_ADDRESS>
[1644531021.192306][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from <IP_ADDRESS>
[1644531021.195469][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fd1d:8168:485b:5:dea6:32ff:febe:8d58
[1644531021.198624][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fd3f:6f80:c617:7:dea6:32ff:febe:8d58
[1644531021.201753][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from 2601:647:4100:b59:dea6:32ff:febe:8d58
[1644531021.204953][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fd56:4c87:932d:1:dea6:32ff:febe:8d58
[1644531021.208645][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::dea6:32ff:febe:8d58
[1644531021.211576][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::42:4fff:fe24:3368
[1644531021.215103][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fd00:6d61:7474:6572::1
[1644531021.218216][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::42:b0ff:fe74:1239
[1644531021.221272][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::1
[1644531021.225568][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::f81f:b3ff:febf:672c
[1644531021.228517][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::e88e:4cff:fe6c:10aa
[1644531021.231427][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::781a:3cff:fe77:3e48
[1644531021.234402][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::e88f:69ff:fe8a:df53
[1644531021.237335][92061:92061] CHIP:DIS: Broadcasting mDns reply for query from fe80::d80b:10ff:fe11:35d9
[1644531021.237577][92061:92061] CHIP:DIS: Scheduling Discovery timeout in secs=900
[1644531021.237643][92061:92061] CHIP:IN: CASE Server enabling CASE session setups
[1644531021.237678][92061:92061] CHIP:SVR: Server Listening...
[1644531021.237701][92061:92061] CHIP:DL: Device Configuration:
[1644531021.237734][92061:92061] CHIP:DL:   Serial Number: TEST_SN
[1644531021.237756][92061:92061] CHIP:DL:   Vendor Id: 65521 (0xFFF1)
[1644531021.237777][92061:92061] CHIP:DL:   Product Id: 32769 (0x8001)
[1644531021.237812][92061:92061] CHIP:DL:   Hardware Version: 0
[1644531021.237836][92061:92061] CHIP:DL:   Setup Pin Code: 20202021
[1644531021.237860][92061:92061] CHIP:DL:   Setup Discriminator: 3840 (0xF00)
[1644531021.238459][92061:92061] CHIP:DL:   Manufacturing Date: (not set)
[1644531021.238485][92061:92061] CHIP:DL:   Device Type: 65535 (0xFFFF)
[1644531021.238543][92061:92061] CHIP:SVR: SetupQRCode: [MT:-24J042C00KA0648G00]
[1644531021.238574][92061:92061] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code:
[1644531021.238604][92061:92061] CHIP:SVR: https://dhrishi.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J042C00KA0648G00
[1644531021.238635][92061:92061] CHIP:SVR: Manual pairing code: [34970112332]
[1644531021.238660][92061:92061] CHIP:SVR: Long manual pairing code: [34970112332]
[1644531021.239222][92061:92061] CHIP:ZCL: GeneralDiagnosticsDelegate: OnDeviceRebooted
[1644531021.239255][92061:92061] CHIP:DMG: Endpoint 0, Cluster 0x0000_0033 update version to 4efa9f9f
[1644531021.239300][92061:92061] CHIP:ZCL: PlatformMgrDelegate: OnStartUp
[1644531021.239414][92061:92061] CHIP:EVL: LogEvent event number: 0x0000000000000000 priority: 2, endpoint id:  0x0 cluster id: 0x0000_0028 event id: 0x0 Sys timestamp: 0x00000000008C8FE9
[1644531021.239698][92061:92067] CHIP:DL: TRACE: Bluez mainloop starting Thread
[1644531021.239807][92061:92064] CHIP:DL: TRACE: Bus acquired for name MATTER-3840
[1644531021.240046][92061:92064] CHIP:DL: CREATE service object at /chipoble/679d/service
[1644531021.240819][92061:92064] CHIP:DL: Create characteristic object at /chipoble/679d/service/c1
[1644531021.241342][92061:92064] CHIP:DL: Create characteristic object at /chipoble/679d/service/c2
[1644531021.241664][92061:92064] CHIP:DL: CHIP BTP C1 /chipoble/679d/service
[1644531021.241692][92061:92064] CHIP:DL: CHIP BTP C2 /chipoble/679d/service
[1644531021.241711][92061:92064] CHIP:DL: CHIP_ENABLE_ADDITIONAL_DATA_ADVERTISING is FALSE
[1644531021.248522][92061:92061] CHIP:DL: PlatformBlueZInit init success
[1644531021.248613][92061:92061] CHIP:DL: Disabling auto scan
[1644531021.255397][92061:92064] CHIP:DL: BluezPeripheralRegisterAppDone done
[1644531021.255530][92061:92061] CHIP:DL: HandlePlatformSpecificBLEEvent 16392
[1644531021.255615][92061:92064] CHIP:DL: Create adv object at /chipoble/679d/advertising
[1644531021.258988][92061:92064] CHIP:DL: SET service data to {'0xFFF6': <[byte 0x00, 0x00, 0x0f, 0xf1, 0xff, 0x01, 0x80, 0x00]>}
[1644531021.259965][92061:92061] CHIP:DL: HandlePlatformSpecificBLEEvent 16393
[1644531021.260012][92061:92061] CHIP:DL: CHIPoBLE advertising config complete
[1644531021.270594][92061:92064] CHIP:DL: RegisterAdvertisement complete
[1644531021.270794][92061:92061] CHIP:DL: HandlePlatformSpecificBLEEvent 16394
[1644531046.810761][92061:92061] CHIP:DIS: Directly sending mDns reply to peer <IP_ADDRESS> on port 54060
[1644531046.813983][92061:92061] CHIP:DIS: Directly sending mDns reply to peer <IP_ADDRESS> on port 54060
[1644531046.817417][92061:92061] CHIP:DIS: Directly sending mDns reply to peer <IP_ADDRESS> on port 54060
[1644531046.820818][92061:92061] CHIP:DIS: Directly sending mDns reply to peer <IP_ADDRESS> on port 54060
[1644531046.824257][92061:92061] CHIP:DIS: Directly sending mDns reply to peer <IP_ADDRESS> on port 57746
[1644531046.827905][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::dea6:32ff:febe:8d58 on port 33450
[1644531046.831670][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::dea6:32ff:febe:8d58 on port 33450
[1644531046.835268][92061:92061] CHIP:DIS: Directly sending mDns reply to peer <IP_ADDRESS> on port 57746
[1644531046.838916][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::dea6:32ff:febe:8d58 on port 33450
[1644531046.842218][92061:92061] CHIP:DIS: Directly sending mDns reply to peer <IP_ADDRESS> on port 57746
[1644531046.845705][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::dea6:32ff:febe:8d58 on port 33450
[1644531046.849410][92061:92061] CHIP:DIS: Directly sending mDns reply to peer <IP_ADDRESS> on port 57746
[1644531046.852962][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::dea6:32ff:febe:8d58 on port 33450
[1644531046.858147][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::dea6:32ff:febe:8d58 on port 33450
[1644531046.862168][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::dea6:32ff:febe:8d58 on port 33450
[1644531046.867125][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::dea6:32ff:febe:8d58 on port 33450
[1644531046.871055][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::dea6:32ff:febe:8d58 on port 33450
[1644531046.875108][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::dea6:32ff:febe:8d58 on port 33450
[1644531046.878981][92061:92061] CHIP:DIS: Directly sending mDns reply to peer <IP_ADDRESS> on port 42726
[1644531046.883108][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::42:4fff:fe24:3368 on port 44300
[1644531046.887010][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::42:4fff:fe24:3368 on port 44300
[1644531046.890909][92061:92061] CHIP:DIS: Directly sending mDns reply to peer <IP_ADDRESS> on port 42726
[1644531046.895836][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::42:4fff:fe24:3368 on port 44300
[1644531046.899738][92061:92061] CHIP:DIS: Directly sending mDns reply to peer <IP_ADDRESS> on port 42726
[1644531046.903571][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::42:4fff:fe24:3368 on port 44300
[1644531046.907952][92061:92061] CHIP:DIS: Directly sending mDns reply to peer <IP_ADDRESS> on port 42726
[1644531046.911782][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::42:4fff:fe24:3368 on port 44300
[1644531046.915650][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::42:4fff:fe24:3368 on port 44300
[1644531046.920027][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::42:4fff:fe24:3368 on port 44300
[1644531046.923856][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::42:4fff:fe24:3368 on port 44300
[1644531046.927722][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::42:4fff:fe24:3368 on port 44300
[1644531046.932171][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::42:4fff:fe24:3368 on port 44300
[1644531046.936167][92061:92061] CHIP:DIS: Directly sending mDns reply to peer <IP_ADDRESS> on port 60432
[1644531046.940021][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::42:b0ff:fe74:1239 on port 50535
[1644531046.944480][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::42:b0ff:fe74:1239 on port 50535
[1644531046.947805][92061:92061] CHIP:DIS: Directly sending mDns reply to peer <IP_ADDRESS> on port 60432
[1644531046.951783][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::42:b0ff:fe74:1239 on port 50535
[1644531046.956261][92061:92061] CHIP:DIS: Directly sending mDns reply to peer <IP_ADDRESS> on port 60432
[1644531046.959795][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::42:b0ff:fe74:1239 on port 50535
[1644531046.964246][92061:92061] CHIP:DIS: Directly sending mDns reply to peer <IP_ADDRESS> on port 60432
[1644531046.968313][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::42:b0ff:fe74:1239 on port 50535
[1644531046.972968][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::42:b0ff:fe74:1239 on port 50535
[1644531046.976383][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::42:b0ff:fe74:1239 on port 50535
[1644531046.980227][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::42:b0ff:fe74:1239 on port 50535
[1644531046.984198][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::42:b0ff:fe74:1239 on port 50535
[1644531046.988109][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::42:b0ff:fe74:1239 on port 50535
[1644531046.991980][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::f81f:b3ff:febf:672c on port 46622
[1644531046.995741][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::f81f:b3ff:febf:672c on port 46622
[1644531047.000077][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::f81f:b3ff:febf:672c on port 46622
[1644531047.003796][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::f81f:b3ff:febf:672c on port 46622
[1644531047.007601][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::f81f:b3ff:febf:672c on port 46622
[1644531047.011569][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::f81f:b3ff:febf:672c on port 46622
[1644531047.015291][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::f81f:b3ff:febf:672c on port 46622
[1644531047.018642][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::f81f:b3ff:febf:672c on port 46622
[1644531047.022734][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::f81f:b3ff:febf:672c on port 46622
[1644531047.026147][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::f81f:b3ff:febf:672c on port 46622
[1644531047.029492][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::e88e:4cff:fe6c:10aa on port 54927
[1644531047.034131][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::e88e:4cff:fe6c:10aa on port 54927
[1644531047.037481][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::e88e:4cff:fe6c:10aa on port 54927
[1644531047.040736][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::e88e:4cff:fe6c:10aa on port 54927
[1644531047.044135][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::e88e:4cff:fe6c:10aa on port 54927
[1644531047.049799][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::e88e:4cff:fe6c:10aa on port 54927
[1644531047.053138][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::e88e:4cff:fe6c:10aa on port 54927
[1644531047.056437][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::e88e:4cff:fe6c:10aa on port 54927
[1644531047.061458][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::e88e:4cff:fe6c:10aa on port 54927
[1644531047.064868][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::e88e:4cff:fe6c:10aa on port 54927
[1644531047.068279][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::781a:3cff:fe77:3e48 on port 52033
[1644531047.071756][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::781a:3cff:fe77:3e48 on port 52033
[1644531047.075092][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::781a:3cff:fe77:3e48 on port 52033
[1644531047.078434][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::781a:3cff:fe77:3e48 on port 52033
[1644531047.081674][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::781a:3cff:fe77:3e48 on port 52033
[1644531047.084842][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::781a:3cff:fe77:3e48 on port 52033
[1644531047.088231][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::781a:3cff:fe77:3e48 on port 52033
[1644531047.093420][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::781a:3cff:fe77:3e48 on port 52033
[1644531047.096777][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::781a:3cff:fe77:3e48 on port 52033
[1644531047.100077][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::781a:3cff:fe77:3e48 on port 52033
[1644531047.103519][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::e88f:69ff:fe8a:df53 on port 45506
[1644531047.107269][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::e88f:69ff:fe8a:df53 on port 45506
[1644531047.110478][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::e88f:69ff:fe8a:df53 on port 45506
[1644531047.113797][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::e88f:69ff:fe8a:df53 on port 45506
[1644531047.117348][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::e88f:69ff:fe8a:df53 on port 45506
[1644531047.121459][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::e88f:69ff:fe8a:df53 on port 45506
[1644531047.125664][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::e88f:69ff:fe8a:df53 on port 45506
[1644531047.128874][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::e88f:69ff:fe8a:df53 on port 45506
[1644531047.132788][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::e88f:69ff:fe8a:df53 on port 45506
[1644531047.135857][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::e88f:69ff:fe8a:df53 on port 45506
[1644531047.139280][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::d80b:10ff:fe11:35d9 on port 43077
[1644531047.142456][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::d80b:10ff:fe11:35d9 on port 43077
[1644531047.145584][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::d80b:10ff:fe11:35d9 on port 43077
[1644531047.148864][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::d80b:10ff:fe11:35d9 on port 43077
[1644531047.152224][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::d80b:10ff:fe11:35d9 on port 43077
[1644531047.155766][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::d80b:10ff:fe11:35d9 on port 43077
[1644531047.158972][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::d80b:10ff:fe11:35d9 on port 43077
[1644531047.162149][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::d80b:10ff:fe11:35d9 on port 43077
[1644531047.165505][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::d80b:10ff:fe11:35d9 on port 43077
[1644531047.168733][92061:92061] CHIP:DIS: Directly sending mDns reply to peer fe80::d80b:10ff:fe11:35d9 on port 43077

@wahajsyed can you bisect to figure out what commit introduced the problem?  In general onnetwork commissioning on Linux works (it's tested in CI all the time), so presumably there is some difference between your setup and what CI is doing.

I also encounter this issue. Below is device's log
chip[IN] BLE EndPoint 0x410b98 Connection Complete
chip[DL] _OnPlatformEvent kCHIPoBLEIndicateConfirm
chip[DL] _OnPlatformEvent default:  event->Type = 32778
chip[ZCL] DeviceEventCallback, event->Type:32778
chip[ZCL] CHIPoBLE connection established
chip[DL] write_cb:conn_idx:0, prf_id:0, add_id:2, len:75, data[0]:0d
chip[DL] _OnPlatformEvent kCHIPoBLEWriteReceived
chip[IN] Received malformed unsecure packet with source 0x0000000000000000 destination 0x0000000000000000

@jamesluo11 Again, can you bisect?

@bzbarsky-apple yeah,  i just upgrade the android chip-tool, the issue was gone. So the root cause is there was a mismatch between node and controller.

@bzbarsky-apple - I think mine was a version mismatch too, chip-app inside docker was on the older version. Clearing out the build directories, env and rebuilding binaries and docker containers fixed it.


[RTM] New pun

This change is

Thank you 🙏 for this amazing contribution.
I can't wait to see the see the ones from @lsechoir @anaisfarr


Builder :: Custom Module :: Multiple control fields not supported in display conditions

Problem Description
I'd like to create display condition depending on two or more affecting fields, but current logic doesn't allow that.
And I can't even set multiple values in depends_show_if in affected field - it must be string (unlike depends_show_if_not which can be array of values (comma separated string))
Steps To Reproduce

Add select field my_select_field_1

'my_select_field_1' => [
	'type'        => 'select',
	'label'       => 'My Select 1',
	'options'     => [
		'option_1'  => 'Option 1',
		'option_2'  => 'Option 2',
	],
	'affects'     => [
		'my_text_field'
	]
]

Add another select field my_select_field_2

'my_select_field_2' => [
	'type'        => 'select',
	'label'       => 'My Select 2',
	'options'     => [
		'option_x'  => 'Option X',
		'option_y'  => 'Option Y',
	],
	'affects'     => [
		'my_text_field'
	]
]

Add my_text_field

'my_text_field' => [
	'type'              => 'text',
	'label'             => 'My text',
	'depends_show_if'   => '?????'
]

Which I'd like to display only when e.g.
my_select_field_1 == option_1 AND my_select_field_2 == option_y
And would be really great if OR conditions were also supported e.g.
my_select_field_1 == option_1 OR my_select_field_2 == option_x
How I would do that with standard Builder methods (without modifying/hardcoding anything in Divi)?
It's impossible, right? And would you accept it as a feature request please?
Thanks!
Update:
I see it's told here that multiple conditions are supported:
https://www.elegantthemes.com/documentation/developers/divi-module/settings-field-visibility/
But I just checked the latest version of Divi (it's 3.12.2, right?), and in Divi/includes/builder/scripts/builder.js there's still only single value supported for show_if condition:

Am I looking at the wrong direction?

QA Checklist
Reporter

[ ] Helpful title used

Helpful title format: Scope(s) :: One Sentence To Describe The Issue
Example: VB :: Floating Toolbar :: Jumps To Top Of Page

[x] Detailed description
[x] Steps to reproduce included
[ ] Support Ticket URL included
[ ] Image and/or gif

Developer

[ ] Steps to reproduce proven solved
[ ] Test included and coverage acceptable and all Tests passing?
[ ] PR description has layman's description of problem and solution and "Areas Affected" listed/explained?
[ ] PR branch includes latest commits from master branch (at the time of checking)?
[ ] Estimated points on issue
[ ] Proper code documentation and conventions?
[ ] Proper RTL appearance
[ ] i18n used if applicable
[ ] Ajax/Form used? Nonce used? Perms checked? All user input sanitized and validated? Intentional unsanitized/unescaped functions used?
[ ] Database saved/updated? Data sanitized and validated?
[ ] Variable output properly escaped and validated?

Peer Review

[ ] PR branch includes latest commits from master branch (at the time of checking)?
[ ] Steps to reproduce proven solved
[ ] Affected areas are tested and ok
[ ] Proper code documentation and conventions
[ ] Proper RTL appearance
[ ] i18n used if applicable
[ ] Test(s) included and coverage acceptable
[ ] Ajax/Form used? Nonce used? Perms checked? All user input sanitized and validated? Intentional unsanitized/unescaped functions used?
[ ] Database saved/updated? Data sanitized and validated?
[ ] Variable output properly escaped and validated?

Quality Assurance

[ ] All tests passed on CircleCI.
[ ] Steps to reproduce passed, the fix works.
[ ] No errors in console or output
[ ] Affected areas are tested and ok
[ ] The fix does not change a customer's website in any surprising or unintended way

[ ] If Divi's design is adjusted, settings are migrated gracefully and invisibly

Design Review

[ ] UI is to spec
[ ] UX is to spec
[ ] Design is to spec
[ ] No surprising visual changes to a customer's website will be experienced after updating

[ ] Any/all visual changes are migrated gracefully

Dev Review

[ ] Test(s) included and coverage acceptable
[ ] Ajax/Form used? Nonce used? Perms checked? All user input sanitized and validated? Intentional unsanitized/unescaped functions used?
[ ] Database saved/updated? Data sanitized and validated?
[ ] Variable output properly escaped and validated?
[ ] i18n used if applicable
[ ] Implementation acceptable, DRY, Scaleable, future safe
[ ] Best practices used, cleverness and grokage, ES6 use, etc.

@ulkoalex How do you set debug point and watching all those source files? can you please help me to work with debugger like that?


feat: add opensearch client;

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 195 (0.51%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-33.3%) to 0.015%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main.rs
1
195
0.51%

Files with Coverage Reduction
New Missed Lines
%

src/main.rs
1
0.51%

Totals

Change from base Build<PHONE_NUMBER>:
-33.3%

Covered Lines:
1

Relevant Lines:
6521

💛  - Coveralls


Improve notifications page

Notifications page need a UI revamp to align with the rest of the Circuitverse pages.

Fix title and headers
Remove big browser notifications test button
Other ux improvements

I would like to work on this, Please assign this to me

what changes would you like to see in this title and headers  and also what are you expecting in "Other ux improvements"

is this still runnning???

What is the current design? Can you attach a screenshot @tachyons?

Hi,
Is anyone working on this issue?
If not, please assign me this issue, and please help me out with some references from where I can start digging into it.

@tachyons it should align with the other pages of circuitverse

@Vasuvj24 , have you improved the UX design ? Cause I want to contribute in it.

If someone is currently not working on this issue can I work on it, please? There is an open notification button which on click does nothing currently as the contents of the notification are already visible by default. It seems to me that it was made so that the notification content would be visible once it is clicked but I think that the open notification option is not needed. Even without it the notifications are looking pretty minimalistic and are visible directly. So, I suggest removing the open notification option. Moreover, currently, the profile picture of the user is not visible in the notifications, so I can help fix that too.

@nitin10s it would be great to hear about your views regarding the above?


Where can I download the trained model parameters?

I want to do some work with the trained NN of character-level language model. Your work is a good example. However, I can not find the trained model in public, such as Huggingface Transformer. Could you please give me some advice?

I'm afraid I didn't save any of the models I trained with repository (it's been over 3 years now).
The package has training code. So training one yourslef shouldn't be a problem.
I'm sure you can also find other repositories with newer algorithms with pre-trained models.


Farm client similar to Vite's. For backend integration.

What problem does this feature solve?
Currently I can't use Farm as I require Vite-like client functionality. I am working on backend integration and there are no plugins for my framework.
https://vitejs.dev/guide/backend-integration.html#backend-integration
With Vite I would:

Programmatically add @vite/client script to the HTML page when in dev mode.
Programmatically add TS/SCSS/other assets into the HTML page when in dev mode. In production, this would be JS/CSS/etc.
Start my app/Vite's dev server
Have HMR working

Example HTML:

What does the proposed API look like?
This does not currently exist in Farm, but does in Vite. See https://vitejs.dev/guide/backend-integration.html#backend-integration.
Proposed:

Template repos with some modern backend framework like Hono, Fastify or Elisya could be really helpful.


Pass kwargs to encoder

Feature request
Models like https://huggingface.co/BAAI/bge-m3 and https://huggingface.co/jinaai/jina-embeddings-v3 can take extras kwargs as input of the encode function such as task=... for Jina v3 or return_dense=False/True for bge-m3
It would be great if we could pass these kwargs either when using the async engine via the Python API
engine.embed(sentences=[...], additional_args=**kwargs)
or when we are sending requests to an endpoint create using your docker image
r = requests.post("http://<IP_ADDRESS>:7997/embeddings", json={"model":"test_model","input":["Two cute cats."], "task": "text-matching"})
Motivation
This would could also be used to handle truncate_dim for Matryoshka embeddings.
might be linked to:  #476
Your contribution
I could try to implement it on my free time but I do not have much currently plus I'm still navigating the code. Any pointers at where to start are welcome.

Ok my bad, thanks for the explanations. I was under the impression that similarly to what has been done in vLLM we could pass custom args to the encode method for each request.
So this means that if I want to use model like jinja on specific task such as retrieval.query like the example on the model card:
model = SentenceTransformer("jinaai/jina-embeddings-v3", trust_remote_code=True, model_kwargs={'default_task': 'retrieval.query'})

I need to find a way to pass it through the EngineArgs to the AsyncEmbeddingEngine?
Thanks for the hard work on this lib!


Support transfer with twin Id

![Screenshot from 2023-07-17 12-03-15](https://github.com/threefoldtech/tfgrid-sdk-ts/assets/5494449

1/97b75340-5844-426e-8b61-8bbd3a1e0aeb)

the validation sometimes works and sometimes not
https://github.com/threefoldtech/tfgrid-sdk-ts/assets/41957921/584e1a06-7c91-42f4-be09-d67e8c87a4b0


Column mapping not working

Column mapping is not working in the system, I get "TypeError: unsupported operand type(s) for -: 'float' and 'NoneType'" or Zero Division Error when I try to use.
OS : Windows
Python 3.7
Even I tried in Google Colab, still its not working

Hey @raajeshlr ,
Thanks for letting us know! It definitely should not be like this, let's figure out what has happened.
Could you please share a screenshot with the full error output?
And there are a couple of questions, which also will help to solve the case faster:

what report you are building?
how the column_mapping dict looks like (if you prefer not to share feature names - that’s completely OK)?
what is the evidently package version (print(evidently.__version__)) ?

Hi @emeli-dral
Thanks for the response, let me share the details.

I am using Boston dataset only and trying to generate Data Drift and Num Target Drift.

Evidently package version is 0.1.23.dev0

Error is unsupported operand type(s) for -: 'float' and 'NoneType' when I use column mapping, attached the screenshot.

My Column mapping is
column_mapping = {}
column_mapping['target'] = 'target'
column_mapping['prediction'] = None
column_mapping['datetime'] = None
column_mapping['numerical_features'] = ['CRIM','ZN','INDUS','NOX','RM','AGE','DIS','TAX',
'PTRATIO','B','LSTAT']
column_mapping['categorical_features'] = ['CHAS','RAD']

Please connect with me at https://www.linkedin.com/in/raajeshlr/

I am eager to discuss about this.

Hi @raajeshlr ,
Got it, this is the problem we recently fixed in the latest version.
Could you please try to update the package and run the example again?
```pip install evidently --upgrade``
And than run two following commands in the terminal from the evidently directory:
jupyter nbextension install --sys-prefix --symlink --overwrite --py evidently
jupyter nbextension enable evidently --py --sys-prefix


Is it correct path for symbol

just now added symbol  path like this , i run below commands on cmd
md C:\Windows\Symbol
set _NT_SYMBOL_PATH=srvC:\Windows\Symbolhttps://msdl.microsoft.com/download/symbols
Is above commnds are correct , should i add further   symbol cache folder ?
if needed means , pleave tell me the command  to add symbol cache .
Thanking you sir

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d7231888-3d4f-3a7c-cae3-2038f34f31bb
Version Independent ID: 9f100c05-e2f9-f3d2-c818-e9d977a25ef6
Content: Microsoft public symbol server - Windows drivers
Content Source: windows-driver-docs-pr/debugger/microsoft-public-symbols.md
Product: windows-hardware
GitHub Login: @DOMARS
Microsoft Alias: domars

@RAJU2529 - Working with symbols can be a challenge. These topics can help you get started:
Symbol Problems While Debugging
Introduction to Symbols
Beyond that guidance, unfortunately we don’t have the resources to offer individual technical advice to the broad array of customers who use the driver documentation.
You may have success posting your question in the following forums, where other driver developers and Microsoft engineers can be found. The community there is quite responsive.
Windows Hardware WDK and Driver Development


Make bin/wct work with new and old versions of wct

Looks good. Need to do the same in wct-st

LGTM


fix(compiler-ssr): transition group should inject props

fix #5141

Can it be merged? It's really essential problem with SSR

we are also encountering this issue

See aed10c50 - the idea is correct, but it's safer to build the props during the actual transform phase.


Non-JSX examples

Add examples not using JSX in docs

+1 on that. How can I use react-globalize to label a button for example (where button is another existing component which gets the label as prop). Do I need to fall back to straight up globalize or is there some convenience method in this library?

JSX has become widely accepted in the React community for a while now so this is probably unnecessary at this point.


Allow force replacing of fcm token

Allow force replacing of fcm token by adding a forceFcmToken query param to the user endpoints

Maybe also add a test for this case (when the arg is true), and check that the fcmtoken has been updated for the previous user? But can be extracted to an issue to be dealt with later if bandwidth is limited.

Maybe also add a test for this case (when the arg is true), and check that the fcmtoken has been updated for the previous user? But can be extracted to an issue to be dealt with later if bandwidth is limited.

Yes I can add in another PR. https://github.com/RADAR-base/RADAR-Appserver/pull/265


Bump Node module version to be compatible with Node 10

It looks like Node 10 will actually launch with module version 64:
https://github.com/nodejs/node/blob/master/src/node_version.h
https://github.com/sass/node-sass/blob/master/lib/extensions.js -> still defines it as 63.

Sigh, yes I noticed this. Thanks, we'll release a 4.9.0 shortly with this change.

Fixed in #2343

@xzyfer When can we expect an updated version published?

Hopefully before Node 10 goes stable.
On Tue., 24 Apr. 2018, 8:13 pm Igor Savin<EMAIL_ADDRESS>wrote:

@xzyfer https://github.com/xzyfer When can we expect an updated version
published?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2341#issuecomment-383879353,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWNzi42YO-kuaMr-5wlNdvvXWaWlNks5trvrMgaJpZM4TffMq
.


Fix subscription flow for Event ID integrity

This PR addresses a security issue by ensuring event IDs are verified, preventing a scenario where attackers could spoof event IDs to inject malicious events. It includes a fix and unit tests (TestEventIDIntegrity) for validation.

This thing duplicates the hash calculation, so I'm trying to think of a way to not duplicate that. Maybe create a new method, but I don't know.


pre-configured cost profile not working

[Enter feedback here]
The link you create is not working:
https://azure.com/e/a8c4809dab444c1ca4870c489fbb196b

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e5dbc36d-1197-0b73-d0fe-2c9dd5f1d17d
Version Independent ID: b2285023-1f19-d037-e1c5-18b0b65009df
Content: Scalable and secure WordPress on Azure - Azure Example Scenarios
Content Source: docs/example-scenario/infrastructure/wordpress.yml
Service: architecture-center
Sub-service: example-scenario
GitHub Login: @david-stanford
Microsoft Alias: pnp

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 513731

@xjohnyknox Thanks for the feedback. Could you please let us know what is not working as expected?
I'm able to load the pre-configured cost profile and see respective estimates. When you open the link, you have the option to login with a Microsoft account that has access to the licensing program, or view the estimate with Microsoft Customer Agreement retail pricing. I've verified that it does work either way.

@xjohnyknox Any further update on this?

@xjohnyknox We will now proceed to close this thread, but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


ViewModelWidget does not get re-rendered in headerSliverBuilder?

Context
I have a page where I use ScrollController object to determine the app bar title opacity. There is _appBarTitleOpacity non-final variable which is then passed to Opacity widget to set the opacity of the app bar title.  I added a listener to scroll controller which updates the value of _appBarTitleOpacity.
And I have a PrimaryAppBar which extends ViewModelWidget and set reactive parameter with value true. PrimaryAppBar has one required parameter titleOpacity.
My code is something like this
@override
  void initState() {
    super.initState();
    _appBarTitleOpacity = 0;
    _scrollController = ScrollController()
      ..addListener(() {
        setState(() {
          _appBarTitleOpacity =
              min<double>(_flexibleSpaceHeight, _scrollController.offset) /
                  _flexibleSpaceHeight;
        });
      });
  }

@override
  Widget build(BuildContext context) {
    return ViewModelBuilder<ProfileViewModel>.reactive(
      builder: (context, viewModel, child) {
        return Scaffold(
          backgroundColor: Colors.white,
          body: SafeArea(
            child: DefaultTabController(
              length: 2,
              child: NestedScrollView(
                controller: _scrollController,
                headerSliverBuilder: (context, innerBoxIsScrolled) {
                  return [
                    PrimaryAppBar(appBarTitleOpacity: _appBarTitleOpacity),
                    BottomTabBar(showShadow: innerBoxIsScrolled),
                  ];
                },
                body: _scrollViewBody(),
              ),
            ),
          ),
        );
      },
      viewModelBuilder: () => ProfileViewModel(),
    );
  }

Problem
PrimaryAppBar does not re-renders when scroll view is scrolled and as a result app bar title opacity does not get changed.
Edit
I tried to refactor the code and used viewModel.notifyListener() in scroll controller listener instead of setState it's working fine now.
@override
  void initState() {
    super.initState();
    _appBarTitleOpacity = 0;
    _scrollController = ScrollController();
  }

void _addScrollViewListener(ProfileViewModel viewModel) {
    _scrollController
      ..addListener(() {
        _appBarTitleOpacity =
            min<double>(_flexibleSpaceHeight, _scrollController.offset) /
                _flexibleSpaceHeight;
        viewModel.notifyListeners();
      });
  }

@override
  Widget build(BuildContext context) {
    return ViewModelBuilder<ProfileViewModel>.reactive(
      onModelReady: (viewModel) => _addScrollViewListener(viewModel),
      builder: (context, viewModel, child) {
        return Scaffold(
          backgroundColor: Colors.white,
          body: SafeArea(
            child: DefaultTabController(
              length: 2,
              child: NestedScrollView(
                controller: _scrollController,
                headerSliverBuilder: (context, innerBoxIsScrolled) {
                  return [
                    PrimaryAppBar(appBarTitleOpacity: _appBarTitleOpacity),
                    BottomTabBar(showShadow: innerBoxIsScrolled),
                  ];
                },
                body: _scrollViewBody(),
              ),
            ),
          ),
        );
      },
      viewModelBuilder: () => ProfileViewModel(),
    );
  }

But I still don't think it's the right way to c all notifyListener in the view itself. I think maybe it can degrade the performance, I am very confuse about it right now. Help me with this.

The value's you're using is not coming from the ViewModel . I don't see why you're using the ViewModel's builder for that. I'd use the normal stateful widget for what you're doing in a separate widget that manages that state internally. then in the view you have no controllers set or anything like that.

Actually PrimaryAppBar extends ViewModelWidget does use the view model. It has image and username which comes from the view model.
Are you suggesting that I should create a new StatefulWidget for the primary app bar that takes image and username from outside something like this
@override
  Widget build(BuildContext context) {
    return ViewModelBuilder<ProfileViewModel>.reactive(
      onModelReady: (viewModel) => _addScrollViewListener(viewModel),
      builder: (context, viewModel, child) {
        return Scaffold(
          backgroundColor: Colors.white,
          body: SafeArea(
            child: DefaultTabController(
              length: 2,
              child: NestedScrollView(
                controller: _scrollController,
                headerSliverBuilder: (context, innerBoxIsScrolled) {
                  return [
                    PrimaryAppBar(appBarTitleOpacity: _appBarTitleOpacity, imageUrl: viewModel.user.imageUrl, username: viewModel.user.username),
                    BottomTabBar(showShadow: innerBoxIsScrolled),
                  ];
                },
                body: _scrollViewBody(),
              ),
            ),
          ),
        );
      },
      viewModelBuilder: () => ProfileViewModel(),
    );
  }

Here's PrimaryAppBar is a StatefulWidget.

That could work. The other way would also be fine. As a tip, I would always trust flutters built in setState over calling our notifyListeners that same amount of times.

I thought this too but I wanted to ask you first. BTW great architecture man, keep up the good work.


lib{std,}c++: Fix setup hooks for cross

Motivation for this change
This was causing trouble with iOS cross compilation and C++. libstdc++ is prebuilt, but CC_FOR_BUILD wrapper's libcxx was adding a -stdlib=libc+.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

CC @kmicklas @ElvishJerricco

@dtzWill Yes indeed! I already want to factor out common bits in *-wrapper so I can write a pkgconfig-wrapper without hating myself. [Then we can use that from the other two *-wrappers and get rid of NIX_CXXSTDLIB* altogether. Yay!]


using Roaring64Bitmap in Spark

hi,I encountered a problem when using Roaring64Bitmap in Spark, the details are as follows,
spark  version 2.4.5,
Scala version 2.11.12
first
./spark-shell
scala> import org.roaringbitmap.longlong.Roaring64Bitmap
<console>:23: error: object Roaring64Bitmap is not a member of package org.roaringbitmap.longlong
       import org.roaringbitmap.longlong.Roaring64Bitmap
              ^

then
./spark-shell --jars ./RoaringBitmap-0.9.8.jar
scala> import org.roaringbitmap.longlong.Roaring64Bitmap
import org.roaringbitmap.longlong.Roaring64Bitmap

scala> val res1 = new Roaring64Bitmap()
res1: org.roaringbitmap.longlong.Roaring64Bitmap = {}
scala> res1.add(16L)
java.lang.NoSuchMethodError: org.roaringbitmap.ArrayContainer.add(C)Lorg/roaringbitmap/Container;
  at org.roaringbitmap.longlong.Roaring64Bitmap.addLong(Roaring64Bitmap.java:62)
  at org.roaringbitmap.longlong.Roaring64Bitmap.add(Roaring64Bitmap.java:599)
  ... 49 elided

I find that spark-2.4.5 dependents  Roaring64Bitmap-0.7.45,  so how can I using Roaring64Bitmap-0.9.8 in spark-2.4.5

It seems that you want to use a class that was introduced in later version of the RoaringBitmap library, within a setup where you have the earlier version of the library. We cannot retroactively add features to a previous version of the library. By design, these versions are immutable. I removed the bug label, I do not think that this can be qualified as a bug.
Have you considered updating the RoaringBitmap library you are using? If you would like spark to use a more recent version of RoaringBitmap, shouldn't you take this with them? We do not control which version spark uses.
If there is something else you think we should do, please be specific.


Video Optimization: Improve default ffmpeg configuration

Feature Description
Let's try to optimize the default ffmpeg configuration to get the best speed/quality/size combo.
Alternatives Considered

Additional Context

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

[ ] See how the ffmpeg configuration could be optimized, and do that

@pbakaus IIRC you are a bit of an ffmpeg expert by now. Any pointers how to get the best out of ffmpeg for within the editor?
Currently we use:
ffmpeg -i inputfile.mp4 -vcodec libx264 -vf "scale='min(1080,iw)':'min(1920,ih)'" -preset fast outputfile.mp4

I've also tried -preset veryfast before but that seems to crash in the browser.

mhh the basics here seem correct to me. Weird that veryfast/ultrafast would crash.. See https://trac.ffmpeg.org/wiki/Encode/H.264 for more, I would also try:

I don't see any quality setting - try -crf
try zerolatency and -movflags +faststart
I'm guessing OpenCL / HW accel won't work in webasm ;)
try a dumber color profile: -vf format=yuv420p
try a simpler codec profile: -profile:v baseline or -profile:v main. This will will disable a bunch of advanced optimization strategies that make encoding/decoding slower.

@swissspidy Do you want to put the file as a webm instead of mp4?

This table is interesting from support.

@swissspidy Do you want to put the file as a webm instead of mp4?

No, the format recommendation is to use MP4 for best compatibility. So we stick to MP4.

drive-by: did folks try HLS or are the costs of implementing both HLS and MP4 (for desktop fallback) prohibitive (CPU/Storage)?

drive-by: did folks try HLS or are the costs of implementing both HLS and MP4 (for desktop fallback) prohibitive (CPU/Storage)?

Storage costs are one factor, limited browser support and complexity of storing multiple formats within WordPress are others. It's something we might explore in the future if the benefits outweigh the drawbacks.

@swissspidy can't wait to start using the hotlink feature, could you let me know what the current ffmpeg configuration is the plugin is using?
I want to keep your coding pattern.

@campiotto The current configuration can be found at https://github.com/google/web-stories-wp/blob/eaf67db8d83482b2ca027eda019aa79c0df72bb3/packages/story-editor/src/app/media/utils/useFFmpeg.js, with some explanation available at https://pascalbirchler.com/client-side-video-optimization/. This of course is irrelevant for hotlinking as we can't run hotlinked videos through FFmpeg.

@swissspidy I think there is some problem with using hotlink. The test I took was as follows:
I used 4 media videos that had been generated by the plugin, moved them to my CDN, then added them back to webstories via hotlink.
I didn't change anything in the encoding of these videos, the plugin who did everything I just moved to the CDN.
In the plugin settings I always had google cache enabled, however the image quality was poor using hotlink and with this the view rate dropped a lot.

If you have any issues with media in stories, please open a new ticket in the support forums or at the very least a new issue on GitHub, instead of commenting on some old issud that is unrelated.


Appstudio update test-component-pac-gmqm

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-gmqm-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
20 seconds
clone-repository

✅ Succeeded
31 seconds
build-container

✅ Succeeded
12 seconds
deprecated-base-image-check

✅ Succeeded
12 seconds
inspect-image

✅ Succeeded
16 seconds
clair-scan

✅ Succeeded
33 seconds
clamav-scan

✅ Succeeded
10 seconds
sbom-json-check

✅ Succeeded
16 seconds
label-check

✅ Succeeded
16 seconds
optional-label-check

✅ Succeeded
8 seconds
show-sbom

✅ Succeeded
9 seconds
show-summary

Pipelines as Code CI/test-component-pac-gmqm-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
20 seconds
clone-repository

✅ Succeeded
31 seconds
build-container

✅ Succeeded
12 seconds
inspect-image

✅ Succeeded
12 seconds
deprecated-base-image-check

✅ Succeeded
33 seconds
clamav-scan

✅ Succeeded
16 seconds
clair-scan

✅ Succeeded
10 seconds
sbom-json-check

✅ Succeeded
16 seconds
optional-label-check

✅ Succeeded
16 seconds
label-check

✅ Succeeded
8 seconds
show-sbom

✅ Succeeded
9 seconds
show-summary

Pipelines as Code CI/test-component-pac-gmqm-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
20 seconds
clone-repository

✅ Succeeded
31 seconds
build-container

✅ Succeeded
12 seconds
inspect-image

✅ Succeeded
12 seconds
deprecated-base-image-check

✅ Succeeded
16 seconds
clair-scan

✅ Succeeded
33 seconds
clamav-scan

✅ Succeeded
10 seconds
sbom-json-check

✅ Succeeded
16 seconds
label-check

✅ Succeeded
16 seconds
optional-label-check

✅ Succeeded
9 seconds
show-summary

✅ Succeeded
8 seconds
show-sbom


[ENH] - Simplify Docker images

Feature description
Right now there is a lot of configuration login embedded within our Docker images. This has many downsides with really the only upside I can see at the moment is it has reduced the complexity of our qhub pod image deployments.

The qhub version is tightly coupled with the docker image version
End users have a harder time to add their own custom images
harder for qhub to make custom modifications

Value and/or benefit
Easier development and allowing end users to use their own custom docker images
Anything else?
No response

Closed by #1174

currently there is jupyter specific information cooked into the docker images. this means that adding/removing features requires a new docker image and is costlier than it needs to be to create.
it could be practical to place the entire qhub-jlab environment in a meta-package/package that carries our jupyter opinions. with a separate package, extensions and tools can be added and tested outside of qhub. the changes then can propogate to qhub by referring the qhub-jlab rather than qhub managing the UX entropy.

currently there is jupyter specific information cooked into the docker images.

@tonyfast this is no longer true as of about 1 month ago. https://github.com/Quansight/qhub/blob/main/qhub/template/image/Dockerfile.jupyterlab.
The docker images for everything are all just a collection of installed packages via apt/conda now. But I do agree that it needs to be documented explained how users can create their own images.


About the version of NuScenes-devkit

The latest version of Nuscenes-devkit doesnot support python 3.5.

I have same question.

@cassiemxtt @Dysonsun  We did downgrade the nuscenes repository. Check this out
https://github.com/Fellfalla/nuscenes-devkit


Assertion failed in Realm 0.95.0

0x1072617cf <+79>:  leaq   0x372f4(%rip), %rax       ; "[realm-core-0.88.0] Assertion failed: col_ndx < m_columns.size()"
0x1072617d6 <+86>:  leaq   0x369fc(%rip), %rcx       ; "table.cpp"
0x1072617dd <+93>:  movl   $0x9b9, %edx
0x1072617e2 <+98>:  jmp    0x10726180c               ; <+140>
0x1072617e4 <+100>: leaq   0x34ab1(%rip), %rax       ; "[realm-core-0.88.0] Assertion failed: ndx < m_size"
0x1072617eb <+107>: leaq   0x369e7(%rip), %rcx       ; "table.cpp"
0x1072617f2 <+114>: movl   $0x9ba, %edx
0x1072617f7 <+119>: jmp    0x10726180c               ; <+140>
0x1072617f9 <+121>: leaq   0x36104(%rip), %rax       ; "[realm-core-0.88.0] Assertion failed: typeid(Col) == typeid(col)"
0x107261800 <+128>: leaq   0x34906(%rip), %rcx       ; "../tightdb/table.hpp"
0x107261807 <+135>: movl   $0x5cf, %edx
0x10726180c <+140>: movq   %rax, %rdi
0x10726180f <+143>: movq   %rcx, %rsi
0x107261812 <+146>: callq  0x107146060               ; tightdb::util::terminate(char const*, char const*, long)

->  0x107261817 <+151>: nopw   (%rax,%rax)

@ikeyboard can you try updating to Realm 0.95 and seeing if we've fixed the issue already? Thanks!

Thanks! This issue happen in Realm Objective-C latest 0.95.0(static) in Xcode 6.4 - iOS8.4 simulator.
I happy rarely, and not happy now. I just worry sometime happy in real app.

Can you share the assertion failure when using 0.95.0, and if possible, a project that demonstrates the issue (either here or privately at help@realm.io)? Thanks!

@ikeyboard I'm sure you're under the impression that you're actually using Realm Objective-C 0.95.0, but your stack trace indicates that you're running a version between 0.90.0 and 0.90.4, so please double check your Realm version.

Thanks for your reply! I can only copy the failed log, it's in my project. The assertion not happen again now. I recheck again and again, Surely the version is 0.95.0 but log message warning me to update.
//Version 0.95.0 of Realm is now available: http://static.realm.io/downloads/cocoa/latest
Waning message when I access real only realm
RLMRealm *realm = [RLMRealm realmWithPath:SWIPEREALMPATH readOnly:YES error:&error];
Anyway, it work OK now. Thank you!


'utf-8' codec can't decode byte (in tutorial)

I'm getting an error "'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte" error when I try to run the MNIST tutorial (specifically, the dataset import).
Environment info
Operating System: Ubuntu 15.04
Python: 3.4.3
Tensorflow from source, commit: 03bff43
Steps to reproduce

Install fresh python3 venv (pyvenv venv)
Activate venv
uninstall and re-install protobuf 3.0.0a3 to fix 487
pip install "built whl file"
In a python terminal, run:

from tensorflow.examples.tutorials.mnist import input_data
mnist = input_data.read_data_sets('MNIST_data', one_hot=True)
Full Error Output
UnicodeDecodeError                        Traceback (most recent call last)
 in ()
1 import tensorflow
2 from tensorflow.examples.tutorials.mnist import input_data
----> 3 mnist = input_data.read_data_sets('MNIST_data', one_hot=True)
/home/ubuntu/venv/standard/lib/python3.4/site-packages/tensorflow/examples/tutorials/mnist/input_data.py in read_data_sets(train_dir, fake_data, one_hot, dtype)
197
198   local_file = maybe_download(TRAIN_IMAGES, train_dir)
--> 199   train_images = extract_images(local_file)
200
201   local_file = maybe_download(TRAIN_LABELS, train_dir)
/home/ubuntu/venv/standard/lib/python3.4/site-packages/tensorflow/examples/tutorials/mnist/input_data.py in extract_images(filename)
56   print('Extracting', filename)
57   with tf.gfile.Open(filename) as f, gzip.GzipFile(fileobj=f) as bytestream:
---> 58     magic = _read32(bytestream)
59     if magic != 2051:
60       raise ValueError(
/home/ubuntu/venv/standard/lib/python3.4/site-packages/tensorflow/examples/tutorials/mnist/input_data.py in _read32(bytestream)
49 def _read32(bytestream):
50   dt = numpy.dtype(numpy.uint32).newbyteorder('>')
---> 51   return numpy.frombuffer(bytestream.read(4), dtype=dt)[0]
52
53
/usr/lib/python3.4/gzip.py in read(self, size)
363         else:               # just get some more of it
364             while size > self.extrasize:
--> 365                 if not self._read(readsize):
366                     if size > self.extrasize:
367                         size = self.extrasize
/usr/lib/python3.4/gzip.py in _read(self, size)
431             # jump to the next member, if there is one.
432             self._init_read()
--> 433             if not self._read_gzip_header():
434                 return False
435             self.decompress = zlib.decompressobj(-zlib.MAX_WBITS)
/usr/lib/python3.4/gzip.py in _read_gzip_header(self)
290
291     def _read_gzip_header(self):
--> 292         magic = self.fileobj.read(2)
293         if magic == b'':
294             return False
/usr/lib/python3.4/gzip.py in read(self, size)
88             self._read = None
89             return self._buffer[read:] +
---> 90                    self.file.read(size-self._length+read)
91
92     def prepend(self, prepend=b'', readprevious=False):
/home/ubuntu/venv/standard/lib/python3.4/site-packages/tensorflow/python/platform/default/_gfile.py in sync(self, *args, **kwargs)
43       if hasattr(self, '_locker'): self._locker.lock()
44       try:
---> 45         return fn(self, *args, **kwargs)
46       finally:
47         if hasattr(self, '_locker'): self._locker.unlock()
/home/ubuntu/venv/standard/lib/python3.4/site-packages/tensorflow/python/platform/default/_gfile.py in read(self, n)
197       A string of the bytes read, up to the end of file.
198     """
--> 199     return self._fp.read(n)
200
201   @_synchronized
/usr/lib/python3.4/codecs.py in decode(self, input, final)
317         # decode input (taking the buffer into account)
318         data = self.buffer + input
--> 319         (result, consumed) = self._buffer_decode(data, self.errors, final)
320         # keep undecoded input until the next call
321         self.buffer = data[consumed:]
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte

very same problem. I had to build from source to have cuda 7.5 since the current binaries are for 7.0 even for the new release 0.7
The build was fine and even some basic ops seem to work but opening the internal MNIST examples breaks exactly like above

Thanks for the report, this was fixed yesterday, so either build from source at current HEAD or wait for our next patch release (soon)


Measure width dynamically

Issue #64

Pull Request Test Coverage Report for Build 166

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 91.683%

Totals

Change from base Build 165:
0.0%

Covered Lines:
342

Relevant Lines:
361

💛  - Coveralls


have host control the text

Currently the text is managed for each client. The host should be able to enforce the text from their config
probably need to hook into LC API

Given that the plugin is mostly used for localization this will not be implemented


Make HSM pin an optional argument to allow setting it via the BANK_VAULTS_HSM_PIN env var

Overview
Previously, the pin had to be provided by the user in their Vault yaml. If you want to keep the pin secret in
source code, then this isn't desirable. Viper defaults to the command line version of the pin, so even if you
set a dummy pin in the yaml and override it via envsConfig, bank-vaults won't use the right pin.
Notes for reviewer
This is my first PR here so please check if I missed things that need to be updated.

Hi @mark64, thanks for raising this! I will look into this one once I am back from PTO, apologies for taking a bit longer. I just need to verify how this specific config flag is passed downstream.


[python-package] fix mypy error about missing type hint in dask.py

Contributes to #3867.
This PR fixes one mypy error in dask.py.

python-package/lightgbm/dask.py:933: error: Need type annotation for "out"

Confirmed that this suppresses these warnings by running the following.
mypy \
    --exclude='python-package/compile/|python-package/build' \
    --ignore-missing-imports \
    python-package/

I think the first time out is populated in https://github.com/microsoft/LightGBM/blob/b94577d05cd08a6a9147bff16395d442866cb511/python-package/lightgbm/dask.py#L945 it's actually List[List[dask_Array]], where each entry has as many items as there are partitions. Then the contents get overwritten in https://github.com/microsoft/LightGBM/blob/b94577d05cd08a6a9147bff16395d442866cb511/python-package/lightgbm/dask.py#L959 where the partitions get concatenated and the elements become List[dask_Array].
I think variables changing types is a big no-no for mypy so maybe we could define two variables here?

it's actuallyList[List[dask_Array]]

ooooooo you're right! I missed that .append(). Fixed in https://github.com/microsoft/LightGBM/pull/4840/commits/006a271fe8b4d4352b751b385b0b8319a6357684.

where the partitions get concatenated and the elements become List[dask_Array].
I think variables changing types is a big no-no for mypy so maybe we could define two variables here?

You're generally right about mypy not liking it when code overwrites a variable with a value of a different type than it was initialized with. Fixed in https://github.com/microsoft/LightGBM/pull/4840/commits/32f40dec3dc7813ca5649459598bcac3c2150f7c.

just re-ran the R-package jobs, let's see if the MiKTeX issue (https://github.com/microsoft/LightGBM/issues/4005#issuecomment-983235895) was fixed overnight

🎉 CI seems happy again!
e.g. from this Windows build

The downloaded binary packages are in
C:\Users\runneradmin\AppData\Local\Temp\RtmpwpHjaj\downloaded_packages
Downloading https://github.com/microsoft/LightGBM/releases/download/v2.0.12/miktexsetup-4.0-x64.zip
Setting up MiKTeX
Installing MiKTeX
Done installing MiKTeX


added license headers

added license headers

Looks good. One optimization is that you could add the short form of the Apache license to files having 50 lines or fewer.

How is this different from PR#25 raised by Nidhi? If this is an old PR, pls close it.


[WIP] /billing/: Change to not reload page, better copy.

This removes the unecessary alerts about how many cards are on file
along with changing the page to not refresh on successful card input.
This is WIP because I'm not sure the copy and mechanics are just right yet, but I think it's a definite improvement over existing infrastructure.

@brockwhittaker what's the status on this?

Closing, since this has gotten pretty stale.


Ensure output metadata is complete

While working on CITE-seq post-processing, I wondered if we want to expand the output metadata with more ADT info.
https://github.com/AlexsLemonade/scpca-nf/blob/19722f43c8b5dd8ebacd0b3202ebee0b0a18ce90/bin/sce_qc_report.R#L163-L207
Specifically:

I see we have normalization information in there, but not scpca filter. Should scpca_filter_method be added?

Similarly, adt filtering (if citeseq)?

Since we have normalization for RNA, perhaps it's worth mentioning normalization for adt if citeseq (https://github.com/AlexsLemonade/scpca-nf/pull/343#discussion_r1245384759)

@allyhawkins @jashapiro

I think that would all be appropriate to add. I don't think we expose everything in those outputs on the front end, but having extra things in the json should not cause any trouble.

It is not part of the download directly, but it is compiled into a table for the download, which we could expand.

From what I see, the values are not all exposed in the portal, but they are all in the TSV download. For example for SCPCS000018 (chosen b/c it is small!) -
single_cell_metadata.tsv.txt

I see we have normalization information in there, but not scpca filter.

I did not read this carefully enough! We do have scpca_filter_method, but it's called cell_filtering_method. Therefore...

This should probably be renamed rna_filtering_method. But, I'm wary of making that kind of a change (in part because of pending cite-seq-only portal updates..)
We can still have an adt_filtering_method in there even though that one isn't called rna!

I see we have normalization information in there, but not scpca filter.

I did not read this carefully enough! We do have scpca_filter_method, but it's called cell_filtering_method. Therefore...

This should probably be renamed rna_filtering_method. But, I'm wary of making that kind of a change (in part because of pending cite-seq-only portal updates..)
We can still have an adt_filtering_method in there even though that one isn't called rna!

I think this is fine, since the fell filtering we actually do is based on the RNA, so the name still fits.


Parametrize the JDK used for testing

This depends on https://github.com/pantsbuild/pants/pull/14421, but works when run from sources. The first commit is https://github.com/pantsbuild/example-jvm/pull/9.
I used jdk="adopt:<IP_ADDRESS>" because anything greater than 12 fails due to https://github.com/pantsbuild/pants/issues/14445.