Generic Switch goes offline after sometime in Homekit (CASE Session establishment failed: 54)

Hello there,
I'm working Matter Generic Switch (0x000F) device type and I started off with Nordic semiconductor template application and able to commission the deivce to the Apple fabric successfully.

The device stays online for about 5-6 Hours and goes offline.
Rebooting the device makes it online and the cycle repeats.
When the device goes offline, I get this in my terminal.
00> I: 729849 [SC]Received Sigma1 msg
00> D: 729849 [SC]Found MRP parameters in the message
00> D: 729849 [SC]Peer assigned session key ID 58240
00> I: 729854 [SC]CASE matched destination ID: fabricIndex 1, NodeID 0x000000001EE63FF2
00> D: 730081 [SC]Including MRP parameters
00> I: 730082 [EM]<<< [E:43689r M:134778314 (Ack:146813535)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:31 (SecureChannel:CASE_Sigma2)
00> I: 730083 [IN](U) Sending msg 134778314 to IP address 'UDP:[fda9:49eb:c24a:1:4f8:92e2:c038:4f08]:54215'
00> I: 730084 [SC]Sent Sigma2 msg
00> I: 730085 [EM]>>> [E:4450i M:108836740 (Ack:55569058)] (S) Msg RX from 1:6726C27A4F6B7C34 [51F1] --- Type 0001:01 (IM:StatusResponse)
00> D: 730086 [EM]Found matching exchange: 4450i, Delegate: 0x2000f32c
00> D: 730086 [EM]Rxd Ack; Removing MessageCounter:55569058 from Retrans Table on exchange 4450i
00> I: 730087 [IM]Received status response, status is 0x00
00> D: 730087 [DMG]<RE> OnReportConfirm: NumReports = 0
00> D: 730087 [DMG]IM RH moving to [GeneratingReports]
00> I: 730088 [EM]<<< [E:4450i M:55569059 (Ack:108836740)] (S) Msg TX to 1:6726C27A4F6B7C34 [51F1] --- Type 0000:10 (SecureChannel:StandaloneAck)
00> I: 730089 [IN](S) Sending msg 55569059 on secure session with LSID: 46710
00> D: 730090 [EM]Flushed pending ack for MessageCounter:108836740 on exchange 4450i
00> D: 730090 [DMG]All ReadHandler-s are clean, clear GlobalDirtySet
00> D: 730301 [IN]Received a duplicate message with MessageCounter:108836740 on exchange 4450i
00> I: 730302 [EM]>>> [E:4450i M:108836740 (Ack:55569058)] (S) Msg RX from 1:6726C27A4F6B7C34 [51F1] --- Type 0001:01 (IM:StatusResponse)
00> D: 730302 [EM]Generating StandaloneAck via exchange: 4450i
00> D: 730302 [EM]Forcing tx of solitary ack for duplicate MessageCounter:108836740 on exchange 4450i
00> I: 730304 [EM]<<< [E:4450i M:55569060 (Ack:108836740)] (S) Msg TX to 1:6726C27A4F6B7C34 [51F1] --- Type 0000:10 (SecureChannel:StandaloneAck)
00> I: 730304 [IN](S) Sending msg 55569060 on secure session with LSID: 46710
00> D: 730326 [IN]Received a duplicate message with MessageCounter:108836740 on exchange 4450i
00> I: 730327 [EM]>>> [E:4450i M:108836740 (Ack:55569058)] (S) Msg RX from 1:6726C27A4F6B7C34 [51F1] --- Type 0001:01 (IM:StatusResponse)
00> D: 730327 [EM]Generating StandaloneAck via exchange: 4450i
00> D: 730328 [EM]Forcing tx of solitary ack for duplicate MessageCounter:108836740 on exchange 4450i
00> I: 730329 [EM]<<< [E:4450i M:55569061 (Ack:108836740)] (S) Msg TX to 1:6726C27A4F6B7C34 [51F1] --- Type 0000:10 (SecureChannel:StandaloneAck)
00> I: 730329 [IN](S) Sending msg 55569061 on secure session with LSID: 46710
00> D: 730563 [EM]Retransmitting MessageCounter:134778314 on exchange 43689r Send Cnt 1
00> I: 730563 [IN](U) Sending msg 134778314 to IP address 'UDP:[fda9:49eb:c24a:1:4f8:92e2:c038:4f08]:54215'
00> I: 730600 [EM]>>> [E:43689r M:146813536 (Ack:134778314)] (U) Msg RX from 0:23AD9FCEEF2D72BC [0000] --- Type 0000:40 (SecureChannel:StatusReport)
00> D: 730601 [EM]Found matching exchange: 43689r, Delegate: 0x20004454
00> D: 730601 [EM]Rxd Ack; Removing MessageCounter:134778314 from Retrans Table on exchange 43689r
00> E: 730602 [SC]Received error (protocol code 2) during pairing process: 54
00> E: 730603 [IN]CASE Session establishment failed: 54

Once the CASE Session establishment failed, no activity regarding the network in the terminal.
Setup:
Hardware: nRF52840
SDK: nRF Connect SDK v2.2.0
Fabric Setup:
BR: Homepod Mini -> tvOS 16.3.2
Controller: iPhone 13 -> iOS 16.3.1

@bzbarsky-apple - f4a75a5
Started with the template from here.
Further logs here:
case-session-failing.txt

SRP timeout is the root for all of this? If yes, the attached log provides the reason for SRP timeout?

I'm getting the same thing:
<dbg> chip: LogV: [DL]SRP update succeeded
<dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
<dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
<dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
<dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
<dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
<dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
<dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
<dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
<dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
<dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
<dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
<dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
<dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
<dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
<dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
<dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
<dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
<dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
<dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
<dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
<dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
<inf> chip: [EM]>>> [E:56959r S:0 M:138206359] (U) Msg RX from 0:93427D31E0321BE5 [0000] --- Type 0000:30 (SecureChannel:CASE_Sigma1)
<inf> chip: [IN]CASE Server received Sigma1 message . Starting handshake. EC 0x20004878
<inf> chip: [IN]CASE Server disabling CASE session setups
<inf> chip: [EM]<<< [E:56959r S:0 M:134838261 (Ack:138206359)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
<inf> chip: [IN](U) Sending msg 134838261 to IP address 'UDP:[2001:bb6:54cc:9100:3d95:8c2c:fc97:6495]:53945'
<inf> chip: [SC]Received Sigma1 msg
<inf> chip: [SC]CASE matched destination ID: fabricIndex 1, NodeID 0x00000000142A910F
<inf> chip: [EM]<<< [E:56959r S:0 M:134838262 (Ack:138206359)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:31 (SecureChannel:CASE_Sigma2)
<inf> chip: [IN](U) Sending msg 134838262 to IP address 'UDP:[2001:bb6:54cc:9100:3d95:8c2c:fc97:6495]:53945'
<inf> chip: [SC]Sent Sigma2 msg
<inf> chip: [EM]>>> [E:56959r S:0 M:138206360 (Ack:134838262)] (U) Msg RX from 0:93427D31E0321BE5 [0000] --- Type 0000:40 (SecureChannel:StatusReport)
<err> chip: [SC]Received error (protocol code 2) during pairing process: 54
<err> chip: [IN]CASE Session establishment failed: 54
<inf> chip: [IN]CASE Server enabling CASE session setups
<dbg> chip: LogV: [IN]SecureSession[0x20002f88]: Released - Type:2 LSID:49755
<dbg> chip: LogV: [IN]SecureSession[0x20002f88]: Allocated Type:2 LSID:49756
<inf> chip: [EM]<<< [E:56959r S:0 M:134838263 (Ack:138206360)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
<inf> chip: [IN](U) Sending msg 134838263 to IP address 'UDP:[2001:bb6:54cc:9100:3d95:8c2c:fc97:6495]:53945'
<inf> chip: [EM]>>> [E:56960r S:0 M:138206361] (U) Msg RX from 0:2B79512F975BCE75 [0000] --- Type 0000:30 (SecureChannel:CASE_Sigma1)
<inf> chip: [IN]CASE Server received Sigma1 message . Starting handshake. EC 0x20004878
<inf> chip: [IN]CASE Server disabling CASE session setups
<inf> chip: [EM]<<< [E:56960r S:0 M:134838264 (Ack:138206361)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
<inf> chip: [IN](U) Sending msg 134838264 to IP address 'UDP:[2001:bb6:54cc:9100:3d95:8c2c:fc97:6495]:53945'
<inf> chip: [SC]Received Sigma1 msg
<inf> chip: [SC]CASE matched destination ID: fabricIndex 1, NodeID 0x00000000142A910F
<inf> chip: [EM]<<< [E:56960r S:0 M:134838265 (Ack:138206361)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:31 (SecureChannel:CASE_Sigma2)
<inf> chip: [IN](U) Sending msg 134838265 to IP address 'UDP:[2001:bb6:54cc:9100:3d95:8c2c:fc97:6495]:53945'
<inf> chip: [SC]Sent Sigma2 msg
<dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
<inf> chip: [EM]>>> [E:56960r S:0 M:138206362 (Ack:134838265)] (U) Msg RX from 0:2B79512F975BCE75 [0000] --- Type 0000:40 (SecureChannel:StatusReport)
<err> chip: [SC]Received error (protocol code 2) during pairing process: 54
<err> chip: [IN]CASE Session establishment failed: 54
<inf> chip: [IN]CASE Server enabling CASE session setups
<dbg> chip: LogV: [IN]SecureSession[0x20002f88]: Released - Type:2 LSID:49756
<dbg> chip: LogV: [IN]SecureSession[0x20002f88]: Allocated Type:2 LSID:49757
<inf> chip: [EM]<<< [E:56960r S:0 M:134838266 (Ack:138206362)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
<inf> chip: [IN](U) Sending msg 134838266 to IP address 'UDP:[2001:bb6:54cc:9100:3d95:8c2c:fc97:6495]:53945'
<dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
<dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
<dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
<dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
<dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
<dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
<dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
<dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
<dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
<dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
<dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
<inf> chip: [FS]Fail-safe timer expired
<err> chip: [SVR]Failsafe timer expired
<dbg> chip: LogV: [IN]SecureSession[0x20002ed0]: MarkForEviction Type:1 LSID:49754
<inf> chip: [SC]SecureSession[0x20002ed0]: Moving from state 'kActive' --> 'kPendingEviction'
<dbg> chip: LogV: [IN]SecureSession[0x20002ed0]: Released - Type:1 LSID:49754
<err> chip: [SVR]Commissioning failed (attempt 1): 32
<dbg> chip: LogV: [IN]Clearing BLE pending packets.
<inf> chip: [BLE]Releasing end point's BLE connection back to application.
<inf> chip: [DL]Closing BLE GATT connection (ConnId 00)
<dbg> chip: LogV: [IN]SecureSession[0x20002ed0]: Allocated Type:1 LSID:49758
<dbg> chip: LogV: [DL]CHIPoBLE advertising set to on
<inf> chip: [DIS]Updating services using commissioning mode 1
<dbg> chip: LogV: [DL]Using Thread extended MAC for hostname.
<inf> chip: [DIS]Advertise operational node 3DBC3C9EC277FD5C-00000000142A910F
<dbg> chip: LogV: [DL]Using Thread extended MAC for hostname.
<inf> chip: [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=1
<inf> chip: [DL]advertising srp service: 8A24DE0E184A6D83._matterc._udp
<err> chip: [ZCL]OpCreds: Got FailSafeTimerExpired
<err> chip: [ZCL]OpCreds: Proceeding to FailSafeCleanup on fail-safe expiry!
<dbg> chip: LogV: [IN]Expiring all sessions for fabric 0x1!!
<err> chip: [FP]Reverting pending fabric data for fabric 0x1
<err> chip: [FP]Warning: metadata not found during delete of fabric 0x1
<inf> chip: [FP]Fabric (0x1) deleted.
<inf> chip: [ZCL]UserLabel: Last Fabric index 0x1 was removed
<inf> chip: [ZCL]OpCreds: Fabric index 0x1 was removed
<inf> chip: [DIS]Updating services using commissioning mode 1
<dbg> chip: LogV: [DL]Using Thread extended MAC for hostname.
<inf> chip: [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=1
<inf> chip: [DL]advertising srp service: 8A24DE0E184A6D83._matterc._udp
<inf> chip: [DL]removing srp service: 3DBC3C9EC277FD5C-00000000142A910F._matter._tcp
<inf> chip: [TS]Pending Last Known Good Time: 2023-04-08T09:07:00
<inf> chip: [TS]Previous Last Known Good Time: 2023-04-08T09:07:00
<inf> chip: [TS]Reverted Last Known Good Time to previous value
<err> chip: [FP]Warning: metadata not found during delete of fabric 0x1
<err> chip: [ZCL]OpCreds: failed to delete fabric at index 1: d8
<inf> chip: [NP]Reverting Thread operational dataset
<err> chip: [DL]Long dispatch time: 181 ms, for event type 32782
<inf> chip: [FS]Fail-safe cleanly disarmed

@adminy Are you getting this randomly, or every time?  Would you be able to log the payloads involved to see what's going on, exactly?

This issue persists almost always.
Steps to reproduce:

Build window covering example (I built for nRF)
Commission to Homekit.

Sometimes it goes offline like in 15-20 minutes and the only way to recover is to factory reset it and re-commission and the cycle continues.
Just to understand, is that something to do with CSL (Coordinated Sample Listening)?

This issue persists almost always.

@absoluteabutaj OK, in that case can you do what I asked and log the payloads so we can tell what data is actually going across?

Just to understand, is that something to do with CSL (Coordinated Sample Listening)?

I really doubt it.

Every time ...
Last login: Fri May 12 12:42:02 on ttys002
18:30:36 ~ λ minicom -D /dev/tty.usbmodem1101

Welcome to minicom 2.8

OPTIONS:
Compiled on Oct 24 2022, 11:16:41.
Port /dev/tty.usbmodem1101, 18:30:37

Press Meta-Z for help on special keys

chip: [IN]SO_REUSEPORT failed: 109
chip: [ZCL]Trying to write invalid Calendar Type
chip: [ZCL]Failed to write calendar type with error: 0x87
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
bt_l2cap: Ignoring data for unknown channel ID 0x003a
chip: [DL]Long dispatch time: 1886 ms, for event type 16388
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise extended commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [DL]Long dispatch time: 223 ms, for event type 16388
chip: [SVR]Server initialization complete
chip: [SVR]Failsafe timer expired
chip: [SVR]Commissioning failed (attempt 1): 32
chip: [ZCL]OpCreds: Got FailSafeTimerExpired
chip: [ZCL]OpCreds: Proceeding to FailSafeCleanup on fail-safe expiry!
chip: [FP]Reverting pending fabric data for fabric 0x1
chip: [FP]Warning: metadata not found during delete of fabric 0x1
chip: [FP]Warning: metadata not found during delete of fabric 0x1
chip: [ZCL]OpCreds: failed to delete fabric at index 1: d8
chip: [DL]Long dispatch time: 165 ms, for event type 32782
chip: [IN]SO_REUSEPORT failed: 109
chip: [ZCL]Trying to write invalid Calendar Type
chip: [ZCL]Failed to write calendar type with error: 0x87
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [IN]SO_REUSEPORT failed: 109
chip: [ZCL]Trying to write invalid Calendar Type
chip: [ZCL]Failed to write calendar type with error: 0x87
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [IN]SO_REUSEPORT failed: 109
chip: [ZCL]Trying to write invalid Calendar Type
chip: [ZCL]Failed to write calendar type with error: 0x87
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [IN]SO_REUSEPORT failed: 109
chip: [ZCL]Trying to write invalid Calendar Type
chip: [ZCL]Failed to write calendar type with error: 0x87
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [DIS]Failed to remove advertised services: 3
chip: [IN]SO_REUSEPORT failed: 109
chip: [IN]SO_REUSEPORT failed: 109
chip: [ZCL]Trying to write invalid Calendar Type
chip: [ZCL]Failed to write calendar type with error: 0x87
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [IN]SO_REUSEPORT failed: 109
chip: [IN]SO_REUSEPORT failed: 109
chip: [ZCL]Trying to write invalid Calendar Type
chip: [ZCL]Failed to write calendar type with error: 0x87
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [IN]SO_REUSEPORT failed: 109
chip: [ZCL]Trying to write invalid Calendar Type
chip: [ZCL]Failed to write calendar type with error: 0x87
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [IN]SO_REUSEPORT failed: 109
chip: [ZCL]Trying to write invalid Calendar Type
chip: [ZCL]Failed to write calendar type with error: 0x87
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [IN]SO_REUSEPORT failed: 109
chip: [ZCL]Trying to write invalid Calendar Type
chip: [ZCL]Failed to write calendar type with error: 0x87
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [IN]SO_REUSEPORT failed: 109
chip: [ZCL]Trying to write invalid Calendar Type
chip: [ZCL]Failed to write calendar type with error: 0x87
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [IN]SO_REUSEPORT failed: 109
chip: [ZCL]Trying to write invalid Calendar Type
chip: [ZCL]Failed to write calendar type with error: 0x87
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 1c
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 1c
chip: [SVR]Server initialization complete
chip: [IN]SO_REUSEPORT failed: 109
chip: [ZCL]Trying to write invalid Calendar Type
chip: [ZCL]Failed to write calendar type with error: 0x87
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [SVR]Server initialization complete
bt_l2cap: Ignoring data for unknown channel ID 0x003a
chip: [DL]Long dispatch time: 1915 ms, for event type 16388
chip: [DL]Long dispatch time: 223 ms, for event type 16388
chip: [DL]Long dispatch time: 224 ms, for event type 16388
app: Should be resetting .... or updating ...
chip: [FP]Reverting pending fabric data for fabric 0x3
chip: [FP]Warning: metadata not found during delete of fabric 0x3
chip: [IN]SO_REUSEPORT failed: 109
chip: [ZCL]Trying to write invalid Calendar Type
chip: [ZCL]Failed to write calendar type with error: 0x87
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
bt_l2cap: Ignoring data for unknown channel ID 0x003a
chip: [DL]Long dispatch time: 1882 ms, for event type 16388
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise extended commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [DL]Long dispatch time: 223 ms, for event type 16388
chip: [SVR]Server initialization complete
chip: [SVR]Failsafe timer expired
chip: [SVR]Commissioning failed (attempt 1): 32
chip: [ZCL]OpCreds: Got FailSafeTimerExpired
chip: [ZCL]OpCreds: Proceeding to FailSafeCleanup on fail-safe expiry!
chip: [FP]Reverting pending fabric data for fabric 0x1
chip: [FP]Warning: metadata not found during delete of fabric 0x1
chip: [FP]Warning: metadata not found during delete of fabric 0x1
chip: [ZCL]OpCreds: failed to delete fabric at index 1: d8
chip: [DL]Long dispatch time: 243 ms, for event type 32782
chip: [BLE]ack recv timeout, closing ep 0x2000c3f8
chip: [SVR]Failsafe timer expired
chip: [SVR]Commissioning failed (attempt 2): 32
chip: [ZCL]OpCreds: Got FailSafeTimerExpired
chip: [ZCL]OpCreds: Proceeding to FailSafeCleanup on fail-safe expiry!
chip: [FP]Reverting pending fabric data for fabric 0x1
chip: [FP]Warning: metadata not found during delete of fabric 0x1
chip: [FP]Warning: metadata not found during delete of fabric 0x1
chip: [ZCL]OpCreds: failed to delete fabric at index 1: d8
chip: [DL]Long dispatch time: 264 ms, for event type 32782
chip: [IN]SO_REUSEPORT failed: 109
chip: [ZCL]Trying to write invalid Calendar Type
chip: [ZCL]Failed to write calendar type with error: 0x87
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [IN]SO_REUSEPORT failed: 109
chip: [ZCL]Trying to write invalid Calendar Type
chip: [ZCL]Failed to write calendar type with error: 0x87
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
bt_l2cap: Ignoring data for unknown channel ID 0x003a
chip: [DL]Long dispatch time: 1886 ms, for event type 16388
chip: [DIS]Failed to remove advertised services: 3
chip: [DIS]Failed to advertise extended commissionable node: 3
chip: [DIS]Failed to finalize service update: 3
chip: [DL]Long dispatch time: 222 ms, for event type 16388
chip: [SVR]Server initialization complete
chip: [SVR]Failsafe timer expired
chip: [SVR]Commissioning failed (attempt 1): 32
chip: [ZCL]OpCreds: Got FailSafeTimerExpired
chip: [ZCL]OpCreds: Proceeding to FailSafeCleanup on fail-safe expiry!
chip: [FP]Reverting pending fabric data for fabric 0x1
chip: [FP]Warning: metadata not found during delete of fabric 0x1
chip: [FP]Warning: metadata not found during delete of fabric 0x1
chip: [ZCL]OpCreds: failed to delete fabric at index 1: d8
chip: [DL]Long dispatch time: 198 ms, for event type 32782

These are consistent errors
app: Init CHIP stack
[DL]BLE address: D9:FC:87:41:7F:5F
[DL]OpenThread started: OK
[DL]Setting OpenThread device type to ROUTER
[SVR]Subscription persistence not supported
[SVR]Server initializing...
[TS]Last Known Good Time: 2023-05-12T19:43:16
[DMG]AccessControl: initializing
[DMG]Examples::AccessControlDelegate::Init
[DMG]AccessControl: setting
[DMG]DefaultAclStorage: initializing
[DMG]DefaultAclStorage: 0 entries loaded
LogV: [IN]UDP::Init bind&listen port=5540
[IN]SO_REUSEPORT failed: 109
LogV: [IN]UDP::Init bound to port=5540
LogV: [IN]BLEBase::Init - setting/overriding transport
LogV: [IN]TransportMgr initialized
LogV: [DL]Using Thread extended MAC for hostname.
[ZCL]Using ZAP configuration...
[DMG]AccessControlCluster: initializing
[ZCL]Initiating Admin Commissioning cluster.
LogV: [DL]Boot reason: 6
[ZCL]DeviceInfoProvider is not registered
[ZCL]Trying to write invalid Calendar Type
[ZCL]Failed to write calendar type with error: 0x87
[ZCL]Endpoint 1 On/off already set to new value
[ZCL]Cluster LevelControl: attribute CurrentLevel set to 254
LogV: [IN]SecureSession[0x20002ed0]: Allocated Type:1 LSID:24923
LogV: [DL]CHIPoBLE advertising set to on
[DIS]Updating services using commissioning mode 1
[DIS]Failed to remove advertised services: 3
LogV: [DL]Using Thread extended MAC for hostname.
[DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=1
[DIS]Failed to advertise commissionable node: 3
[DIS]Failed to finalize service update: 3
[DIS]Updating services using commissioning mode 1
[DIS]Failed to remove advertised services: 3
LogV: [DL]Using Thread extended MAC for hostname.
[DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=1
[DIS]Failed to advertise commissionable node: 3
[DIS]Failed to finalize service update: 3
[DIS]Delaying proxy of operational discovery: missing delegate
[IN]CASE Server enabling CASE session setups
LogV: [IN]SecureSession[0x20002f88]: Allocated Type:2 LSID:24924
[SVR]Joining Multicast groups
[SVR]Server Listening...
[DL]Device Configuration:
[DL]  Serial Number:<PHONE_NUMBER>6677889900
[DL]  Vendor Id: 65521 (0xFFF1)
[DL]  Product Id: 32773 (0x8005)
[DL]  Product Name: not-specified
[DL]  Hardware Version: 0
[DL]  Setup Pin Code (0 for UNKNOWN/ERROR): 20202021
[DL]  Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00)
[DL]  Manufacturing Date: (not set)
[DL]  Device Type: 65535 (0xFFFF)
[SVR]SetupQRCode: [MT:6FCJ142C00KA0648G00]
[SVR]Copy/paste the below URL in a browser to see the QR Code:
[SVR]https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A6FCJ142C00KA0648G00
[SVR]Manual pairing code: [34970112332]
LE advertising is already enabled
LogV: [IN]SecureSession[0x20002ed0]: Released - Type:1 LSID:24923
LogV: [IN]SecureSession[0x20002ed0]: Allocated Type:1 LSID:24925
[DIS]Updating services using commissioning mode 1
[DIS]Failed to remove advertised services: 3
LogV: [DL]Using Thread extended MAC for hostname.
[DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=1
[DIS]Failed to advertise commissionable node: 3
[DIS]Failed to finalize service update: 3
[DL]CHIP task running
[DL]CHIPoBLE advertising started

@adminy That log you pasted seems unrelated to this issue and is not showing any particularly unexpected errors: it just shows a BLE-enabled device that is not connected to any IP network coming up.

Hi there, are you still seeing this issue? If so please file a feedback ticket like so:

File a feedback assistant ticket.
https://developer.apple.com/bug-reporting/#feedback-assistant
Click on the link below using your account:
https://feedbackassistant.apple.com/new-form-response
Choose iOS/iPadOS to file an issue
Choose the area as Home App and fill in the details of the type of issue and the description

Technical Information
Please provide the following
a) Sysdiagnose logs for iPhone / iPad with the timestamp / timeframe of the issue
b) Sysdiagnose logs for all the Home Hubs (HomePod mini / HomePod / Apple TV) with the timestamp / timeframe of the issue
c) Accessory logs with the timestamp / timeframe of the issue
d) mDNS network logs with timestamp / timeframe of the issue
e) Video or screenshot describing the issue (optional but beneficial)
Please make sure you download and install the profiles for iOS and tvOS as provided here. The instructions are also in these links.
iOS:

https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=ios&name=homekit
https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=ios&name=network
https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=ios&name=mdns

tvOS:

https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=tvos&name=homekit
https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=tvos&name=network
https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=tvos&name=mdns
For installation instructions, refer to https://developer.apple.com/bug-reporting/profiles-and-logs.
Note: Once you have the profile on the iPhone, it will ask you if you want to install it on other devices. Follow the prompts to install on the HomePod, Apple TV, etc., where you have the described issue and reproduce it.

Matter Commission  demo video ： https://www.bilibili.com/video/BV1Nx421y7sa/


Add OP_OF_FOUND_AT.

Add support for "any of them at 0" constructs to the language. This allows users to avoid using long or chains like "$a at 0 or $b at 0" and also is a nicer way
to write "for any of them: ($ at 0)".

This is mostly a syntactic sugar PR because someone at work asked if there was a nicer way than long or chains like $a at 0 or $b at 0....
If this is a good idea I'll update the docs before merging.

I think this is good idea, also for completeness and coherency, because we have $a in (0..100), $a at 0 and any of them in (0..100), the missing piece is any of them at 0.

I was looking for this.
So, if I understood correctly we'll be able to do this
$a1 = "MZ"
$a2 = "PE"

condition would be
any of ($a*) at 0x80
Thanks!

I wanted to ask one more question about this.
$a1 = "MZ" $a2 = "PE"
this condition doesn't work
($a1 or $a2) at 0x80
this does work
$a1 at 0x80 or $a2 at 0x80
Apologies if this was covered in some other topic.

You want to use any of ($a1, $a2) at 0x80 or the shorter form any of ($a*) at 0x80 which will be true if at least one of the $a* strings are found at that offset.
The idea of string sets is covered here: https://yara.readthedocs.io/en/stable/writingrules.html#sets-of-strings-1 (though the at portion of it is not in a released version yet).

Thank you @wxsBSD. Yes, I went through the documentation many times.
If I understand correctly this is a correct way but that is not released yet?

You want to use any of ($a1, $a2) at 0x80 or the shorter form any of ($a*) at 0x80 which will be true if at least one of the $a* strings are found at that offset.

Thank you @wxsBSD. Yes, I went through the documentation many times. If I understand correctly this is a correct way but that is not released yet?

Correct. any of ($a*) at 0x80 is coming in 4.3.0. For now, you can use $a1 at 0x80 or $a2 at 0x80.
If you have a lot of strings you want to check at a specific offset you can do it with a loop: for any of ($a*): ($ at 0x80)
4.3.0 adds the shorter syntax version than the loop.


Demokit / Documentation broken since 1.72.0

OpenUI5 version: 1.72.x
Browser/version (+device/version): Chrome 78.0.3904.97 on Windows10
Any other tested browsers/devices(OK/FAIL):
URL (minimal example if possible): https://openui5.hana.ondemand.com/#/topic
User/password (if required and possible - do not post any confidential information here):
Steps to reproduce the problem:

Just open the URL

What is the expected result?
What happens instead?
No content is shown at all, no content tree, no page content.
Any other information? (attach screenshot if possible)
It worked until the latest 1.71.x release and was broken with 1.72.0

Duplicate of https://github.com/SAP/openui5/issues/2716 (or at least of the lastest update of that issue).
A fix is already on its way (internal release process takes a while + deployment).
As other URLs are affected than initially described in #2716, I keep this one open for tracking purposes. Internal incident is<PHONE_NUMBER> .

You can use the fixed demokit at https://openui5.hana.ondemand.com/1.72.1/ now, the URL without version will beupdated soon.

Now also fixed for the URL without version (https://openui5.hana.ondemand.com/#/topic)


Compress plugin should send always Vary: accept-encoding if content-type matches

When a request comes to a remap that has the compress plugin, but does not have an Accept-encoding: header that indicates the plugin should compress, but, the object would otherwise be compressible we should still add a Vary: accept-encoding.
Say an ATS close to the origin in a cache hierarchy (a parent) receives a request that does not ask for compression on a compressible object. It responds, and, because the response does not have Vary: accept-encoding, an ATS closer to the client (child) think that it is the only possible variant. For the next request that does ask for compression, that 1st ATS in the path will have a cache hit for the uncompressed object and send it uncompressed.
If however the parent originally sends Vary: accept-encoding, the child can still ask the parent for the compressed version.

@mlibbey Can you please clarify whether this is still an issue? Looking at the plugin code, it looks like it tries to handle Vary intelligently. If possible, can you add an AuTest for this? If you don't have time, can you describe an example request and response which causes this issue.

Assigning to @vmamidi .


Onboarding widget - No way to leave the OTP screen

Describe the bug
If you are activating an atsign using the onboarding widget, when you go to the verification screen there is no way to leave this screen and go back to the previous one. Someone might want to do this if the verification code didn't get sent or if they change their mind on which atsign to use.
To Reproduce
Steps to reproduce the behavior:

Activate an atsign
Open the onboarding widget and enter the atsign
When the verification code screen displayed, there is no way to leave unless you enter the code to proceed.

Expected behavior
It would be good if we had a back or cancel button, somewhere on this screen, which takes us back tot he previous screen.
Screenshots

Smartphone (please complete the following information):

Device: Android and iOS devices

Were you using an @application when the bug was found?

atmosphere

Fixed and tested, it's working fine. will release it in pub dev with new version.
Below attached recorded video.
https://user-images.githubusercontent.com/60208690/130217651-b76bd814-cc40-477f-80c1-2f4f56cbf90e.mp4


feat: add beta-5 network to supported networks

Description
closes #5458.
Adds beta-5 as a possible target for forc-client.

blocked by #5457


keyboard-interactive authentication for nodejs

Hi I first had problem with my authentications method.
But I checked the ssh2 config and was able to authenticate with the help of  'keyboard-interactive'.
I have right now problems to implement this the same way here.
I tried:
await Client({
         host: 'my_ip',
         port: 22,
         username: 'my_user',
         password: 'my_password',
         tryKeyboard: true,
        type: 'keyboard-interactive',
        prompt: (name, instructions, instructionsLang, prompts, finish) => {
                console.log('keyboard auth')
                if (prompts.length > 0 && prompts[0].prompt.toLowerCase().includes('password')) {
                        console.log('finish with my password')
                        finish(['my_password']);
                    } else {
                      finish([]);
                    }
                }
    })

but just end in handshake timeouts.
For ssh2 I got this hint:

you have to use the standard node.js EventEmitter interface for attaching an event handler (.on()),

How do I have to use the keyboard authentication here correctly?
Maybe you have a small example for me?
Thank you very much.
Best

I got your issue, will get back to you with example on this

Please upgrade to latest version (0.0.23), now you can listen for any event which is provided by SSH2, for example:
async function test() {
  try {
    const client = await Client({
      host: "server_ip",
      port: 22,
      username: "username",
      tryKeyboard: true,
      events: {
        "keyboard-interactive": (
          name,
          instructions,
          instructionsLang,
          prompts,
          finish
        ) => {
          finish(['my_password'])
        },
      },
    });

    client.close(); // remember to close connection after you finish
  } catch (e) {
    console.log(e);
  }
}

Sorry for the delay, but that worked for me. Thank you :)


Added testing redis binary path for  Mac OS

I faced a pah problem testing the [org.redisson.RedissonAtomicLongReactiveTest.java].
When I checked this problem, only Windows OS Path was set in RedissonRuntimeEnvironment. So I sent a PR by adding the Mac OS Path.
[problem]

[solved]

Thank you for contribution!


How to translate?

Hello, I would like to help with the translation of the tutorial into Spanish but would like an explanation on how to do it in the same way it can be useful for anyone who also intends to help translate.
Greetings,
Carlos

Great question Carlos. The translation initiative is new so we're building a process out right now. Here's what I'm thinking:
For contributors

Fork
Add a new directory in content with language (e.g., /content/spanish).
Copy the existing docs to the new directory
Translate markdown content including what's in the "frontmatter" (title, tocTitle, description), but leave the code, commit, and filename
Run the project using yarn develop to confirm that everything looks OK. For now, you can preview changes by going to a url that looks like this http://localhost:8000/spanish/composite-component
Make a pull request

Todo from a development perspective (me or @tmeasday)
Contributors can start translating now by doing the above. But the sidebar and links won't work till we sort out the following features:

Support languages in the /content directory (e.g., /content/spanish, /content/english).
Add a language picker
Ensure the sidebar works with new languages

Updated #3 to reflect the steps to get started.

Going to close this and open up a Spanish translation issue where we can chat further


Lambda to ECS Ingestion Migration

Asana Task: https://app.asana.com/0/0/1203049724800739/f
Asana Task: https://app.asana.com/0/0/1203049724800740/f
After numerous issues, we've decided to move our ingestion process from
lambda to an ECS service. This should make it easier to connect to our
RDS and keep our springboard filecount down, as well as model when
running everything in docker locally.

Create dockerfile to describe the ingestion image.
remove batch_files dot py
Completely change ingest dot py to do both the batching and the
ingestion, using the (newly added) schedule module to schedule the
task to run five minutes past the hour.
Simplify batcher.py, removing compress_filenames,
unpack_filenames, create_event, trigger_lambda and
event_size_over_limit functions.
Add in (unimplimented) LIGHT_RAIL Config Type.
Cleanup tests that no longer make sense.
Update Docker File Structure so it makes sense with one RDS and two Docker Files.

With this new approach, it seems like we have to implement a new batching strategy. Previously we were limited by processing time and message size of sending file lists between the lambdas. Without that limitation, and using batch_files(file_list, 1_000_000_000) we could conceivable create a parquet file in memory consisting of hundreds of thousands gzip files, which I think would crash the ECS.
Ideally these files would be batched by the header``timestamp value from inside of the gzip file. This would align the batches with the pyarrow partitioning and hopefully guarantee that the ECS is never holding more than 1 hours with of a parquet file in memory and that each partition folder on S3 only has one file.
Might want to discuss this over a quick all today.

Only major comment is if the work flow relies on file_list_from_s3 providing all s3 paths in chronological order. I know there is no way to sort the files you're getting from s3 with any of the boto3 file list functionality, so I think this could be a dangerous assumption.
I believe all of the paths we are dealing with have a timestamp in the filename (created by delta), so we could perform our own sort, after the file_list_from_s3 operation based on filename, and then that would include the assumption that the data in the files is the same chronologically as the filename being created by delta. I'm not totally sure how solid that assumption is.


Strange justification error

MusicXML test score MozaVeilSample is rendered with a justification error in last system. The problem has been isolated and test score 00253-justification-error has been created. This is the error:

Fixed by https://github.com/lenmus/lomse/commit/099c795ed14648e53e52dab72f623bc1e8540b8f


How to verify the integrity of notary components during install

I'm trying out notary but I'm not sure what steps I would have to take when setting up a notary instance for production.
Simply cloning a Git repo from GitHub and running a docker-compuse up does not seem very secure.
What would be the easiest while secure method to verify the integrity of all components during setup?

Are you running containers in production (Kubernetes, ECS, pure Docker, etc.)? If so, you can deploy it using the official images. The images are obviously Notary-signed and you can verify them with notary list docker.io/library/notary.
If you're trying things out locally first, you can run the docker-compose instructions in this repo, or if you're more familiar with Kubernetes/Helm, I'm working on a chart in a fork as well.

But to run a trusted Kubernetes environment on-prem, wouldn't I need to run trusted docker images first which I would need notary for? Seems like a chicken and egg problem.

If you were to run on ECS (the Fargate flavor, not EC2), you can run your Notary containers without having to bootstrap other components first. Other clouds have similar services (I'm just not sure of the names right now). But it sounds like that's not your situation right now.
If you run Kubernetes, whether managed (EKS, GKE, AKS, etc.) or hosted (on-prem or on-cloud), there are some components that will have to be bootstrapped first (kubelet, kube-proxy, etc.), and the trust of those depends on the distribution channel, but in general that's outside of the trust model of Notary. They're not necessarily the root of trust, but they are one of the "turtles" towards the bottom. After all, you're already trusting the underlying hardware, whether you're running directly on top of it, or if there are several layers of virtualization on top of it.
When you spin up a cluster from scratch, you have to inherently trust the components you're installing, and the definition of trust is up to you, e.g. if downloading the binaries from https://github.com/kubernetes/kubernetes/releases and matching the sha512 is good enough for you then good, but if you want each individual binary signed with the Kubernetes' organization GPG key and you have a way to get it, then that's your starting point.
Now, if the adoption of Notary (or any implementation of TUF) gets more widespread traction, then we can start talking about verifying these components via Notary ;)
I hope I answered your question, and open to hear other people's opinions.

Thanks, that explained a lot for me.

What does the phrase "they are one of the "turtles" towards the bottom" mean?
Which other implementations of TUF are you aware about?

Kubernetes is out of scope for the PoC I want to build. I just want to set up some standalone Linux machines and a private registry where only signed images can be started by the Docker daemon.

Ah, the turtle comment comes from the expression of "Turtles all the way down", which in turn comes from the mythology that the world is supported by a turtle, but then that turtle is supported by a larger turtle, and that one supported by another turtle, and so on. The analogy being that each turtle is a layer of trust, e.g. your software is the world, and the first turtle is your platform, then the next turtle the distribution channel for that platform, then the hardware, etc. Does that make sense?
I'm not aware of other implementations of TUF, what I meant to say is that with TUF being a spec, and Notary being the first (or reference) implementation, it's feasible that some other implementation can come along and get more adoption. Keep in mind that Notary is an "opinionated" implementation and other alternatives might address the goals in a different way. I didn't mean to imply that Notary is bad, if it stays as the only implementation and that works forever, that would be great. I just wanted to generalize my comment.
That said, I recently heard about vcn, which is not a TUF implementation, but operates in the same space as Notary. I haven't used it yet, so I can't comment on how it compares to Notary.
And yeah, it was my impression that Kubernetes was outside of your scope, I was just using it to illustrate where the boundaries of trust and Notary's scope were. You should be able to deploy Notary on VMs or on-prem hardware, without requiring Kubernetes.


[BUG]The name 'FindObjectsSortMode' does not exist in the current context

Describe the bug
Follow the official documents.create a new Unity project with Unity 2021.3.4f1 and import required dependencies and MRTK3 packages with Mixed Reality Feature Tool.An error was reported after reopening the project.
**Yes, it sounds ridiculous.**I checked google, stackoverflow, official FAQ and ISSUS, and didn't see anyone having related questions.
The software Mixed Reality Feature Toolcan be used normally half a year ago,but now importing mrtk3 will be returned and did not import MRTK3 into my project.
To reproduce
Steps to reproduce the behavior:

Import required dependencies and MRTK3 packages with Mixed Reality Feature Tool.
An error was reported after reopening the project.

Expected behavior
Under normal circumstances, no errors should be reported
Screenshots

Your setup (please complete the following information)

Unity Version 2021.3.4f1 URP
MRTK Version  v3.0

Target platform (please complete the following information)

HoloLens 2

Additional context

After commenting the relevant functions, the project can be used normally for the time being (not sure what will happen later)

@marlenaklein-msft can you take a look at this?  I think you've already addressed this with the follow PR:

https://github.com/MixedRealityToolkit/MixedRealityToolkit-Unity/pull/515

@xxx-x-x  this fix has been shipped, please update to latest packages and try again.

(This issue should be addressed with https://github.com/MixedRealityToolkit/MixedRealityToolkit-Unity/pull/484 and the [core v3.0.1] patch release).


The output result of the MUL operator is different between EdgeTPU and CPU.

Dear coral support team,
if any of the users have similar experiences, I would like to get help, so I post an issue.
I made a simple model that takes an input of 1x3x3 and a mul operator with 3 weight parameters. (The parameter value is learned by quantization-aware training.)
When running this model with the cpu backend, the result is the same as calculated by hand.
However, the result of the edgetpu path is different except when the input is -20.
It looks as if the scale value for each weight is different.
The calculation formula was referred to the paper "Quantization and Training of Neural Networks for Efficient Integer-Arithmetic-Only Inference".
I'm really wondering why this result happens.
Edge TPU Compiler version 14.1.317412892 (though, I checked from version 2.0 and the same problem occurred.)
libedgetpu version : Frogfish
Attached models : mul_issue.tflite, mul_issue_edgetpu.tflite
Regards,
nadongguri.

models.zip

@nadongguri thank for submitting, this looks like a compiler issue, do you mind submitting your inference script for both model also?

Dear @Namburger ,
here's the script file and the simple usage. :-)

$python inf_and_cmp_two_models.py --model mul_issue.tflite  --model2 mul_issue_edgetpu.tflite
--model mul_issue.tflite
--model2 mul_issue_edgetpu.tflite
diff[0] : -31 vs -71
diff[1] : -17 vs -43
diff[2] : 14 vs -59
diff[3] : -31 vs -62
diff[4] : -43 vs -20
diff[5] : 4 vs -53
diff[6] : -31 vs 8
diff[7] : -55 vs -10
diff[8] : -33 vs -30
$python inf_and_cmp_two_models.py --model mul_issue.tflite  --model2 mul_issue.tflite
--model mul_issue.tflite
--model2 mul_issue.tflite
the results are the same

script.zip

@nadongguri Were you able to fix this ?

Feel free to reopen if this issue still persists.


#4631 remove shadow

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Context

[x] Closes #4631
[ ] Requires deployment <>

Before submitting pull request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[ ] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </bsx/collection>
[ ] I've tested PR on mobile
[ ] I've written unit tests 🧪
[ ] I've found edge cases

Had issue bounty label?

[x] Fill up your KSM address:
Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot 📸

[ ] My fix has changed something on UI; a screenshot is best to understand changes for others.

pay 10 usd

😍 Perfect, I’ve sent the payout
💵 $10 @ 26.61 USD/KSM ~ 0.376 $KSM
🧗 EzGc4s9PgCPx1YnF3fqzhLzVHpHMTL4LWPScwpDrR8JKgSU
🔗 0x55c9649143983182f7209fa536eaf1253bfc411722cd9372317197cc83d082f2
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


python311Packages.blinkpy: 0.22.4 -> 0.22.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.blinkpy is: Python library for the Blink Camera system
meta.homepage for python311Packages.blinkpy is: https://github.com/fronzbot/blinkpy
meta.changelog for python311Packages.blinkpy is: https://github.com/fronzbot/blinkpy/blob/refs/tags/v0.22.5/CHANGES.rst
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.22.5 with grep in /nix/store/p3hkhfb1wiv4isgsl4w6g985skiy61gf-python3.11-blinkpy-0.22.5
found 0.22.5 in filename of file in /nix/store/p3hkhfb1wiv4isgsl4w6g985skiy61gf-python3.11-blinkpy-0.22.5

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.blink
python310Packages.blinkpy
python311Packages.blinkpy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/p3hkhfb1wiv4isgsl4w6g985skiy61gf-python3.11-blinkpy-0.22.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.blinkpy https://github.com/r-ryantm/nixpkgs/archive/bf97e3c7ffbb932b96735bc82e7c28d56a57a42d.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/bf97e3c7ffbb932b96735bc82e7c28d56a57a42d#python311Packages.blinkpy

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/p3hkhfb1wiv4isgsl4w6g985skiy61gf-python3.11-blinkpy-0.22.5
ls -la /nix/store/p3hkhfb1wiv4isgsl4w6g985skiy61gf-python3.11-blinkpy-0.22.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

python310Packages.blinkpy
python311Packages.blinkpy

Maintainer pings
cc @dotlambda for testing.

Already on master.


Dead letter unit test failed occasionally

In what area(s)?

/area runtime

/area operator

/area placement

/area docs

/area test-and-release

Expected Behavior
Unit tests always pass.
Actual Behavior
The dead letter unit test failed occasionally. For example https://github.com/dapr/dapr/runs/6284493034?check_suite_focus=true
Reason
The test resiliency has a single inbound policy with a 100ms timeout, sometimes the timeout limit is exceeded and causes a retry to publish.

Hi @Taction thanks for fixing this :) It seems that we're having some issues with the e2e tests that were added in #4399 too. Could you please take a look and see if those can be fixed too? See: https://github.com/dapr/dapr/actions/workflows/dapr-test.yml

@ItalyPaleAle Sure, I'll look into the e2e tests, sorry for not noticing this before.

@ItalyPaleAle I found the reason why e2e failed. The e2e triggered by https://github.com/dapr/dapr/actions/workflows/dapr-test.yml is using pubsub.azure.servicebus with config https://github.com/dapr/dapr/blob/master/tests/config/dapr_servicebus_pubsub.yaml. This component config sets disableEntityManagement to true, which disables automatically creating topics and subscriptions according to the doc. This causes failed to publish to dead-letter topic. I don't have the context of why it is set to true(maybe prevent from abuse), I think there are two ways to solve this issue:

The administrator of this component adds two topics: pubsub-dead-topic-http、pubsub-deadletter-topic-http and its subscriptions if needed.
Edit servicebus config change disableEntityManagement to false.

/cc @yaron2

Wow great find.
I don't have full context either. But because this is a component, I'm adding @berndverst too

@berndverst Any update on this?

@Taction Lets go for the 2nd option to resolve the issue.

@Taction @amulyavarote we don't know if this will work yet, but agree on opening this PR to test out the hypothesis.

@Taction I created this PR based on the above discussion. This is failing on Linux and is passing on Windows. Can you please take a look?
https://github.com/dapr/dapr/pull/4595

@amulyavarote different tests are failing than the ones that failed before.

@yaron2 I see the same tests failing here.
https://github.com/dapr/dapr/runs/6359195699?check_suite_focus=true#step:18:846

@amulyavarote different tests are failing than the ones that failed before.

@yaron2 I see the same tests failing here. https://github.com/dapr/dapr/runs/6359195699?check_suite_focus=true#step:18:846

Prior to this change, 100% of tests were failing for both Windows and Linux
The mentioned failing tests had different failure reasons than what's observed now
Several test runs on that PR failed due to completely different issues like bindings and actor reminders

The best way to tell if the change to the pub/sub component YAML resolved the reported issues is to run the e2e tests manually on a standalone cluster with only the relevant dead letter e2e tests.

I checked the container log for https://github.com/dapr/dapr/runs/6359195699?check_suite_focus=true#step:18:854, publishing to topic pubsub-dead-topic-http is succeed from message-http-005 to message-http-057, but seems stucked to publish message-http-058, resulting in the publish timeout exceed.
Here is related publisher app container log.
2022/05/09 20:56:15 performPublish() called
2022/05/09 20:56:15     commandBody.ContentType=application/json
2022/05/09 20:56:15     commandBody.Topic=pubsub-dead-topic-http
2022/05/09 20:56:15     commandBody.Data=message-http-057
2022/05/09 20:56:15     commandBody.Protocol=http
2022/05/09 20:56:15     commandBody.Metadata=map[]
2022/05/09 20:56:15 Publishing using url http://localhost:3500/v1.0/publish/messagebus/pubsub-dead-topic-http and body '"message-http-057"'
2022/05/09 20:56:15 Publish succeeded
2022/05/09 20:56:15 performPublish() called
2022/05/09 20:56:15     commandBody.ContentType=application/json
2022/05/09 20:56:15     commandBody.Topic=pubsub-dead-topic-http
2022/05/09 20:56:15     commandBody.Data=message-http-058
2022/05/09 20:56:15     commandBody.Protocol=http
2022/05/09 20:56:15     commandBody.Metadata=map[]
2022/05/09 20:56:15 Publishing using url http://localhost:3500/v1.0/publish/messagebus/pubsub-dead-topic-http and body '"message-http-058"'
2022/05/09 20:56:30 callSubscriberMethod: Call initialize on pubsub-subscriber
2022/05/09 20:56:30 callSubscriberMethod: Call set-respond-invalid-status on pubsub-subscriber
2022/05/09 20:56:30 performPublish() called
2022/05/09 20:56:30     commandBody.ContentType=application/json
2022/05/09 20:56:30     commandBody.Topic=pubsub-a-topic-http
2022/05/09 20:56:30     commandBody.Data=message-http-074
2022/05/09 20:56:30     commandBody.Protocol=http
2022/05/09 20:56:30     commandBody.Metadata=map[]
2022/05/09 20:56:30 Publishing using url http://localhost:3500/v1.0/publish/messagebus/pubsub-a-topic-http and body '"message-http-074"'
2022/05/09 20:56:30 Publish succeeded


Support cached_ids for all collection associations

Hey @KevinBongart, thanks for creating this gem! Not sure if this Gem is still being maintained, but if yes, thoughts on adding support for cached result from scopes?
And does cached_association_name fallback to using the actual association if no cache exists?

Hi @oyeanuj, I haven't used this gem in 4 years and we should probably consider it abandoned. The implementation is pretty bad but should be fairly easy to either recreate better or fix to adapt it to today's ActiveRecord.
It's actually still in use in an old application that I run, but I don't really plan on fixing it. Feel free to fork and fix, I'll be happy to help!

Got it, thanks for the update! I don't feel confident enough to be able to play with it at the moment, but I'll keep this as a reference to understand caching better.
Curious, since you don't like the implementation, how would you do it today?


Nearby places icons localization bug fix

Title (Nearby places icons localization bug fix)
Fixes #{Icons in Nearby list showing up when phone is set to English but not when set to Czech #1852 }
Description (required)
Fixes #{Icons in Nearby list showing up when phone is set to English but not when set to Czech #1852}
Place.java: Enum Label was changed from using English word identifiers to QID identifiers. These are obtained from link sent within the query in NearbyPlaces.java. Few identifiers were added to the enum but still there are plenty of them missing and showing as unknown but they are actually set. New issue should be opened to add more identifiers to the enum in the future.
Tests performed (required)
Tested on Samsung Galaxy J5, API 25
Screenshots showing what changed (optional)
Nearby places for English locales:

Nearby places for Slovak locales before fix:

Nearby places for Slovak locales after fix:

Can somebody review this request?

Hi @Rulino , sorry about the wait. @neslihanturan usually does PR testing, and I think she is away at the Netherlands techstorm at the moment. :) Will check in again with you soon...

Thanks for testing, @domdomegg . :)
Happy to merge after the requested changes are made.

Test results: all tests passed
Tested home, nearby, in en-GB
Tested home, nearby, in cs-CZ
2.8.5-debug-pr-1947~492ea591 on Samsung Galaxy S6 with API level 25.
Ready to merge.


Use updated related_applications manifest key (DONT MERGE)

R: all

Is this still valid? I mean, can we merge it or close?

I'll update it with 44s changes
On Sun, May 31, 2015, 4:27 PM alex<EMAIL_ADDRESS>wrote:

Is this still valid? I mean, can we merge it or close?
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleChrome/ioweb2015/pull/859#issuecomment-107285337
.


Use np.ma.is_masked() instead of isinstance(MaskedArray) in tests

Due to some changes in Numpy 1.12, some aggregator functions in np.ma return a MaskedArray instance with no mask rather than an ndarray. This causes some of our tests to fail which do an instance check for a MaskedArray.
I've modified the checking code to use np.ma.is_masked(), but this causes other tests to fail where the array being checked has always been a MaskedArray instance with no mask (thus, the reference file claims it is masked when it isn't). Commit dfa75a3 demonstrates this - see the Travis test failures. Note that because some tests contain multiple checks, not all of the checks which would fail are listed in the output.

thank you @djkirkham
this is a better test pattern, I think, asking whether the data is masked, rather than checking if it's type is 'maskedarray'
the only changes here are test results which were not masked, but were of masked array type, so this is a testing pattern change only


wizard creates incomplete snapshot.json file

I have just been trying this with two new fans ..
python -m tinytuya wizard -nocolor creates a snapshot.json file .. when running in tinytuya2mqtt errors are raised about incomplete data in the file.
running python -m tinytuya scan -nocolor fixed up the file ..
Not sure if others have seen the same?  Maybe update the docos?

Hi,
You need to install pip3 install getmac when you python3 -m tinytuya wizard -nocolor -force it will detect the mac addresses.


Create Readme for RT-2.15

This PR is to create a Readme for IS-IS Extensions for Segment Routing

Pull Request Functional Test Report for #3503 / e7ab691bff062c504f453d29a1b32b3b7eae3dc8
No tests identified for validation.
Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

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 55.268%

Totals

Change from base Build<PHONE_NUMBER>7:
0.0%

Covered Lines:
1983

Relevant Lines:
3588

💛  - Coveralls


Update options.py

[ ] Closes #xxxx
[ ] Tests added
[ ] User visible changes (including notable bug fixes) are documented in whats-new.rst
[ ] New functions/methods are listed in api.rst

@dcherian I've modified the parameters for get_options() as per changes suggested. Could you review these once, so that I can do the same for other functions as well? Thanks!

I interpreted the previous change suggested as a suggestion to include all possible keyword arguments for get_options() function, as would be ideal in its documentation, and modified accordingly. Did you mean to suggest something else? I'm sorry if i interpreted it wrongly. Could you explain it again?
Really sorry for the inconvenience!


Make provisioning more resilient

What this PR does / why we need it:

Use kubernetes repos
Statically define pgp keys for repos
Add retry logic to scripts

Fixes #269

Not force pushing has btw the nice advantage that you can pin CI failures onto specific changes ;)


Migrate to version 0.6.0 of the fastly crate

Upgrades the default Compute@Edge starter kit for rust to version 0.6.0 of the fastly crate, along with:

a more descriptive version of the rust-toolchain file
minor copyedits for consistency with Developer Hub and other starter kits
linting
adding Rust SME team as codeowners

Edit: This is a duplication of https://github.com/fastly/compute-starter-kit-rust-default/pull/28, which I hadn't realised existed.

The changes to main.rs in #28 should be what we use going forward.

The changes to main.rs in #28 should be what we use going forward.

Cross-posting this comment from #28:

I rolled the rest of the changes that @/doramatadora thoughtfully added in #29 into this branch, including copy edits, rust-toolchain modifcations, and the addition of code owners. With that, I'll close #29 and hopefully this should be ready to merge!
Thank you to both @/jeddenlea and @/doramatadora for your work updating this template, and apologies about the confusion. I think together, we made a much more thorough diff slightly_smiling_face

With these changes all rolled up together, I'm going to close this in favor of #28. :door: :sparkles:

Cross-posting this comment from #28:

I rolled the rest of the changes that @/doramatadora thoughtfully added in #29 into this branch, including copy edits, rust-toolchain modifcations, and the addition of code owners. With that, I'll close #29 and hopefully this should be ready to merge!
Thank you to both @/jeddenlea and @/doramatadora for your work updating this template, and apologies about the confusion. I think together, we made a much more thorough diff slightly_smiling_face

With these changes all rolled up together, I'm going to close this in favor of #28. :door: :sparkles:


[Docs]: Performance best practices

Is there an existing issue for this?

[X] I have searched the existing issues

Engineering Ticket Link
N/A
Release Date
N/A
Release Number
N/A
First Draft
No response
Loom video
No response
Discord/slack/intercom Link if needed
No response
PRD
No response
Test plan/cases
No response
Use cases or user requests
Each framework or product has best practices in order to eke performance from that framework. Like our security docs, we should publish a document around best practices to improve the performance of Appsmith apps.
This includes:

Paginating queries
Performing aggregation on the server instead of pulling a lot of data to the browser.
Design multiple pages instead of loading a single page with many widgets.
Following best practices of JS code to avoid infinite loop or intensive computations.

Should be part of core concepts cc: @jnikhila @Pranay105


add focus and blur event

When the user Click on Image Focus Event will work
When the user Click on outside of Image Blur Event will work

This isn't necessarily nor does it capture all the focus and blur possibilities. The DOM events are fine here.
See my comment here

@msalsbery thank you for reviewing this. I think it's looking good now... Do you concur? If not, what needs changing?

Aside from the two doc comment changes I requested, it looks good to me!
I like your recommended doc comments phrasing, thank you!

@btzr-io, I know it was years ago that you suggested this, so it's probably not relevant for you anymore, but I'm just curious if this patch looks like it would do what you were hoping for. :)

Yes, this expected behavior:

When the user Click on Image Focus Event will work
When the user Click on outside of Image Blur Event will work


AZ support

Doc says VMs in Availability Zones are not supported.
But according to this thread, they are: https://www.yammer.com/azureadvisors/threads/1147323515

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

ID: 0e2dde49-662d-fc39-a03f-c67f7f86df67
Version Independent ID: a4545bdc-298b-b440-203e-4f6f66882655
Content: Azure Backup support matrix for Azure VM backup
Content Source: articles/backup/backup-support-matrix-iaas.md
Service: backup
GitHub Login: @rayne-wiselman
Microsoft Alias: raynew

@jtuliani Thank you for your feedback . We will investigate and update this thread.

@jtuliani AFAIK, VM's in Availability Zones are not supported. I am not sure of the link you have provided.
@rayne-wiselman can you please provide your insights on this?

Assigning @rayne-wiselman  for visibility

@SwathiDhanwada-MSFT  Please assign to me.

@Sogup @GeethalakshmiG Can you help with this issue?

@SwathiDhanwada-MSFT  Please assign to @GeethalakshmiG

@SwathiDhanwada-MSFT  Please have @GeethalakshmiG  be the only assignee on this issue. Thanks.

https://docs.microsoft.com/en-us/azure/backup/backup-support-matrix-iaas#vm-compute-support
I have updated the support matrix for availability zones.

#please-close


[Bug]: TypeScript 5.6 has a new behavior when handling ES6

Version
29.2.5
Steps to reproduce
The issue has been opened in jest but it seems to be a ts-jest issue:
https://github.com/jestjs/jest/issues/15312
When using TypeScript and ES6 modules, it is common to transform these with ts-jest:
transform: {
    '\\.[tj]sx?$': [
        'ts-jest',
        {
            tsconfig: {
                outDir: './.ts-jest'
            }
        }
    ],
},
transformIgnorePatterns: [
    '/node_modules/(?!(ol|txml|geotiff|quick-lru|color-|rbush|earcut|pbf|quickselect))'
],

This for example will transform OpenLayers which is shipped as ES6 modules.
Since TypeScript 5.6 this does not work anymore, because TypeScript will interpret the type: module in OpenLayers itself and it will produce ES6 which jest won't parse.
Expected behavior
Someone should investigate this change of behavior and see what is to be done when TypeScript transpiler is used through its API.
Actual behavior
TypeScript produces ES6 code
Debug log
    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /home/mmom/src/rlayers/node_modules/ol/proj/proj4.js:40
    import Projection from './Projection.js';
    ^^^^^^

Additional context
The TypeScript changelog with a summary of the change:
https://devblogs.microsoft.com/typescript/announcing-typescript-5-6/
An issue which discusses the change:
https://github.com/microsoft/TypeScript/issues/59991
Environment
Does not depend on anything but TypeScript 5.6

Related to https://github.com/kulshekhar/ts-jest/pull/4542#issuecomment-2358998886


Feature Request: Add grouping just like on File Explorer

What's the Problem?
Feature Request: Add grouping just like on File Explorer
Solution/Idea
Feature request to add grouping of files and folders like what the File Explorer already with Group By menu. This feature gives user to visually separate the files based on selected filters, like file type, name, date, etc.
For me I find this feature especially useful when using File Explorer. Without this, any other file manager that does not have it makes it feel less efficient to use.
I really hope that Files will have this feature which is great.
Alternatives
For now there is no alternative way for this feature. I can simply sort files by not group, so visually when browsing files, it is just flat and no seperation.
Priorities

Capability
Priority

This proposal will allow developers to accomplish W
Must

This proposal will allow end users to accomplish X
Should

This proposal will allow developers to accomplish Y
Could

This proposal will allow end users to accomplish Z
Won't

Files Version
v<IP_ADDRESS>
Windows Version
Windows 11 21H2
Additional comment
No response

This has been implemented in Files V2 💪 (now in preview)


Install the latest version whl of tensorflow from Jenkins daily build system, but can not find a part of the directory。

hello, i have a question:
Operating System:
ubuntu 14.04
question：
Install the latest version whl of tensorflow from Jenkins daily build system, but can not find a part of the directory。
If installed from binary pip package, provide:

Which pip package you installed.

first download the latest stable package:
http://ci.tensorflow.org/view/Nightly/job/nightly-matrix-cpu/TF_BUILD_CONTAINER_TYPE=CPU,TF_BUILD_IS_OPT=OPT,TF_BUILD_IS_PIP=PIP,TF_BUILD_PYTHON_VERSION=PYTHON2,label=cpu-slave/lastStableBuild/

The output from python -c "import tensorflow; print(tensorflow.version)".

import tensorflow; print(tensorflow.version)
0.8.0

Steps to reproduce

pip uninstall tensorflow
pip install  --upgrade  tensorflow-0.8.0-cp27-none-linux_x86_64.whl

What have you tried?

in  the  path anaconda2\envs\tensorflow\lib\python2.7\site-packages\tensorflow\models\image dictionary，can not find the alexnet and imagenet dictionary, but can find them from the github path https://github.com/tensorflow/tensorflow/tree/master/tensorflow/models/image.

how can i update to get alexnet and imagenet dictionary?

I am fixing this for the future. For now, you can simply clone the tensorflow repository (the r0.8 branch if you want to be consistent with your binaries), and copy the alexnet and imagenet directories from the cloned directory into the anaconda2/envs/tensorflow/lib/python2.7/site-packages/tensorflow/models directory.


Session Leak

I've investigated my code so many times and I cannot understand why I'm still getting this leak log:
org.neo4j.driver.internal.logging.JULogger error
SEVERE: Neo4j Session object leaked, please ensure that your application calls the `close` method on Sessions before disposing of the objects.

My application uses neo4j-ogm only and my sessions life time are always cleaned after a work unit.
Also, there is no close operation in Session object.
Is there anything I can do in order to figure out why exactly I'm getting this error?
What's the proper way to clean/close db session?
Also, if my unit of work is simple a session.load(...), do I still have to close anything?
I'm using ogm 2.0.5 with those libs:
        compile 'org.neo4j:neo4j-ogm-core:2.0.5'
        compile 'org.neo4j:neo4j-ogm-bolt-driver:2.0.5'
        compile 'org.neo4j:neo4j-ogm-http-driver:2.0.5'

We have backported several fixes to the OGM from the new 2.1.0. Please try 2.0.6 and see if this issue continues.
Note that 2.1.0 introduces some new concepts while 2.0.6 is a patch release.

@mangrish thank you, I'll try it asap.

@jdorleans: Did you make any progress with this?

There was indeed a specific point in my code I was not closing the Session. I was creating several threads and executing concurrent operations with my Repositories which had a Session obj each. At one particular point, I was dealing with the transaction manually and I didn't close the session. So I believe that was the leak.
For the record I've also done an improvement that might be interesting for some. Since my Repositories are stateless, I've decided to use ThreadLocal<Session> (one session per thread) as opposed to creating a new Session for each Repository. That way we can have singleton repos and just a few reusable Sessions open at once. I've gained a lot more with that approach. Solved the leak, less memory usage, simplified my code, easier to test etc.


Database#prepareSet(object, cb) - prepare a set of statements

Would you accept a patch for a Database.prototype.prepareSet() method which takes an object containing strings of SQL and creates a Statement object for each, replacing the original string with the new object? Written in JS for the original sqlite binding, it looks like:
sqlite.Database.prototype.prepareSet = function(ioSet, iCallback, _async) {
  var that = this;
  for (var a in ioSet) {
    if (typeof ioSet[a] !== 'string')
      continue;
    that.prepare(ioSet[a], function(err, stmt) {
      if (err) return iCallback(err);
      ioSet[a] = stmt;
      that.prepareSet(ioSet, iCallback, 1);
    });
    return;
  }
  if (!_async)
    process.nextTick(iCallback);
  else
    iCallback();
};

Can you explain a bit further what this function does and why it might be useful?

How 'bout it? :-)


Unable to upgrade to 0.8.9

I'm trying to upgrade from MetroLog 0.8.6 to the latest version 0.8.9. However, the MetroLog targets seem to have changed and that is creating a problem for me on a couple of my own PCL's. I get this error:

Could not install package 'MetroLog 0.8.9'. You are trying to install this package into a project that targets '.NETPortable,Version=v4.5,Profile=Profile111', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.

Here's what 0.8.6 reports as targets:

.NET 4.5, .NET Core 4.5 (Windows Store apps), Windows Phone 8, WinPhone 8.1 and WinJS

Here's what 0.8.9 reports as targets:

.NET 4.5, Windows 8.1 (Windows Store apps), Windows Phone 8, WinPhone 8.1 WinJS, Xamarin.iOS, Xamarin.Android.

My own project targets:

'portable45-net45+win8+wpa81'

I've tried to update the build targets for my own project, but it seems like it's already up-to-date. Is it possible 0.8.9 went backwards? Any ideas how I can get my project onto the latest MetroLog version?
Thanks,
Paul

So Win8 support was dropped as VS 2015 forces that. Can you try changing your supported frameworks in your PCL to Win8.1+?

Closing for now. Please reopen if this is still an issue.


Update changes from review

Updated  as suggested
/assign @darshan-nagaraj

/assign @josefkarasek
/assign @sherine-k
/assign @ayesha54
I have made changes for the README (darshan has already reviewed). This should have been a separate commit but I mistakenly included it.
The changes really were to enable the goimports local-prefixes: github.com/openshift/node-observability-operator and ensure all imports would then pass the golangci-lint run.


Add friend by peer ID

They may not be online or visible

Added in https://github.com/alanshaw/chatterbox-webext/commit/e97981ac0435bde9a746f21ee3ac94faabc9ee09


[Speculative decoding] [Help wanted] [Performance] Optimize draft-model speculative decoding

Proposal to improve performance
With the end-to-end correctness tests merged in https://github.com/vllm-project/vllm/pull/3951, now we will optimize the implementation to get ~50% speedup on 70B model with temperature 1.0.
Work required:
P0/P1 -- priority
(Small/Medium/Large) -- relative size estimate

Optimizing proposal time

[x] P0 (Large) Reduce draft model control-plane communication from O(num_steps) to O(1)
[x] P0 (Medium) Support draft model on different tensor-parallel-size than target model https://github.com/vllm-project/vllm/issues/4632

Optimizations for scoring time

[x] P0 (Medium) Re-enable bonus tokens to increase % accepted tokens https://github.com/vllm-project/vllm/issues/4212
[ ] P1 (Large) Replace CPU-based batch expansion with multi-query attention kernel call
[ ] P1 (Medium) Automate speculative decoding https://github.com/vllm-project/vllm/issues/4565

Optimizations for both proposal and scoring time https://github.com/vllm-project/vllm/issues/5561

[x] P0 (Medium) Decouple sampling serialization from sampling
[x] P1 (Large) Amortize prepare_inputs over multiple forward passes

Optimizations for scheduling time

[x] P0 (Medium) Profile & optimize block manager V2 https://github.com/vllm-project/vllm/issues/4536

FAQ
What should the target configuration be for 50% speedup?
In the Anyscale fork we saw a 50% speedup on bs=8 with a 68m-sized draft model on TP1/70B target model on TP8 and a 7B draft model on TP(1|8)/70B target model on TP8. This was with the optimizations listed above as "P0".
Note we can do much better than this, with multi-query scoring (P1), GQA for target model scoring, and a dynamic speculation policy. This is just the starting point!
Why not implement Medusa / tree-attention?
We should implement this! The work here will lay the foundation for future improvements in speculative decoding. For example, Eagle uses the Medusa approach (fine-tuned heads plus tree attention) and even claims to beat Medusa. But for Eagle to work well in vLLM we need to optimize the sampler as listed above.
The north star should be: configurable tree size (top-k .. top-1), which uses multi-query attention for scoring (no batch expansion). This issue is about optimizing vLLM in the top-1 speculation case to get 50% speedup with draft models.

Support draft model on different tensor-parallel-size than target model

This should be doable. Just need to figure out the UX change of how users use it.

See the code linked here @youkaichao : https://github.com/vllm-project/vllm/issues/4632. The spec worker and non-spec workers share the same process.

In the Anyscale fork we saw a 50% speedup on bs=8 with a 68m-sized draft model on TP1/70B target model on TP8 and a 7B draft model on TP(1|8)/70B target model on TP8. This was with the optimizations listed above as "P0".

Hi @cadedaniel, I have tried current main branch to evaluate the acceleration of speculative decoding, but encountered the following assertion error:
https://github.com/vllm-project/vllm/blob/190bc838e17196733526896bf2861f8d05bd3f43/vllm/executor/ray_gpu_executor.py#L28-L32
I'm wondering how the 50% speedup is measured, is there still further pending PRs? And, as the draft-model looks so small (64m-sized), may I know if the 50% speedup is measured with greedy sampling or random sampling?
Thanks!

About the tree-attention/Medusa/Eagle, one of the core implementation will be tree attention mask in flash attention, which is currently not ready. I'd like to bring your attention to it https://github.com/Dao-AILab/flash-attention/issues/924. If anyone would like to contribute to it, it would be great.

@LiuXiaoxuanPKU has more on this

@sighingnow this issue is for getting the 50% speedup. once the P0s are done we will get it with temperature 1.0.

@sighingnow this issue is for getting the 50% speedup. once the P0s are done we will get it with temperature 1.0.

May I know more about the accept rate when we get the 50% speedup? Thanks!

May I know more about the accept rate when we get the 50% speedup? Thanks!

On llama2 7b / llama2 70b, the acceptance rate was like 80%. we trained a 68m draft model at anyscale that gets ~50% acceptance rate.

I have met the same problem. Is there a solution? By the way, is there any documentation on how to evaluate the acceleration of speculative decoding? Thanks!

Thanks @ChuanhongLi -- FYI there is no acceleration yet. we'll share documentation once there is a useful speedup.

On llama2 7b / llama2 70b, the acceptance rate was like 80% (no fine tuning). we trained a 68m draft model at anyscale that gets ~50% acceptance rate. btw you can run acceptance rate experiments today (I will push a PR tomorrow for TP>1 support)

Thanks for the information! Looking forward to the complete speculative decoding support!

Thanks for the information! Looking forward to the complete speculative decoding support!

Thanks for your reply!

I noticed there's a feature request related to Medusa/Eagle at https://github.com/vllm-project/vllm/issues/4669

On llama2 7b / llama2 70b, the acceptance rate was like 80% (no fine tuning). we trained a 68m draft model at anyscale that gets ~50% acceptance rate. btw you can run acceptance rate experiments today (I will push a PR tomorrow for TP>1 support)
@cadedaniel May I know how you calculated the acceptance rate？On llama2 7b / llama2 70b, this acceptance rate seems a little high but just 50% speedup.

P1 (Large) Replace CPU-based batch expansion with multi-query attention kernel call

Hi @cadedaniel @LiuXiaoxuanPKU, I have pushed a multi-query scorer implementation in #6185. Could you please take a look at it and let me know how do you think about it?
Thanks!

Thanks everyone for the help! We hit a 45% latency reduction. Big thanks to @sroy745 @alexm-neuralmagic @comaniac @wooyeonlee0 @zifeitong @LiuXiaoxuanPKU @rkooo567 @ruisearch42 and everyone else who has helped reduced vLLM overheads!

I expect there to be more performance gains once we move the API server outside of the worker, we can re-run evals then.

@cadedaniel thanks for leading this project!

@cadedaniel Thanks for leading this effort.

Is speculative decoding optimized on vLLM now? The doc on speculative decoding mentions that it is not currently optimized and links this PR to track progress while this PR was closed as complete on Aug 5

[ ]  P1 (Large) Replace CPU-based batch expansion with multi-query attention kernel call

I believe the ongoing optimisation work is the checklist in the PR description @ishan-scribe

Is speculative decoding optimized on vLLM now? The doc on speculative decoding mentions that it is not currently optimized and links this PR to track progress while this PR was closed as complete on Aug 5 Doc: https://docs.vllm.ai/en/latest/models/spec_decode.html

I believe the ongoing optimisation work is the checklist in the PR description @ishan-scribe

Is speculative decoding optimized on vLLM now? The doc on speculative decoding mentions that it is not currently optimized and links this PR to track progress while this PR was closed as complete on Aug 5 Doc: https://docs.vllm.ai/en/latest/models/spec_decode.html

I believe the ongoing optimisation work is the checklist in the PR description @ishan-scribe

Is speculative decoding optimized on vLLM now? The doc on speculative decoding mentions that it is not currently optimized and links this PR to track progress while this PR was closed as complete on Aug 5 Doc: https://docs.vllm.ai/en/latest/models/spec_decode.html

I believe the ongoing optimisation work is the checklist in the PR description @ishan-scribe

Lot of the tasks mentioned in the PR description have been addressed and the improvements from these changes have been reported by Cade here https://github.com/vllm-project/vllm/issues/4630#issuecomment-2269618262.
There are still ongoing improvements to sd e.g. enabling chunked_prefill with speculative-decoding, MQA support for speculative decoding etc.

I've tested with llama3.1 70B with 3.1 8B draft model, it turn out that TTFT latency somehow also got improved a bit (~12%), is this unexpected? anyone knows why?

I've tested with llama3.1 70B with 3.1 8B draft model, it turn out that TTFT latency somehow also got improved a bit (~12%), is this unexpected? anyone knows why?

How much performance improvement has THPT achieved?

I've tested with llama3.1 70B with 3.1 8B draft model, it turn out that TTFT latency somehow also got improved a bit (~12%), is this unexpected? anyone knows why?

How much performance improvement has THPT achieved?

what is THPT?

Hi @cadedaniel I've tested with llama3.1 70B with 3.1 8B draft model, it turn out that TTFT latency somehow also got improved a bit (~12%), is this unexpected? anyone knows why?

Could you check chunked prefill is disabled in your baseline? For llama3.1 70B, chunked prefill might be turned on by default because the context length is long. You could disable chunked prefill and compare TTFT again. Spec decode should not help with TTFT. It will actually slow down TTFT because you need to run draft model's prefill.

Hi @cadedaniel I've tested with llama3.1 70B with 3.1 8B draft model, it turn out that TTFT latency somehow also got improved a bit (~12%), is this unexpected? anyone knows why?

Could you check chunked prefill is disabled in your baseline? For llama3.1 70B, chunked prefill might be turned on by default because the context length is long. You could disable chunked prefill and compare TTFT again. Spec decode should not help with TTFT. It will actually slow down TTFT because you need to run draft model's prefill.

Hi @LiuXiaoxuanPKU
Thanks for your reply, after disabled chunked prefill, the TTFT latency is slower for draft model speculative decoding (~4%).
Besides, I also test ngram as well, and i notice the TTFT is less for speculation with "ngram=3", 172ms -> 144ms, is that expected?


lazy loading/bindPromise

Sorry @davedawkins, haven't checked the whole API but, is there something to bind promise/transform promises into SutilElements? I assume it shouldn't be very difficult as SutilElements are asynchronous by default. Binding promises would enable lazy loading and deferred elements (for fetching data, etc).
The helper should have 3 arguments:

The promise: element is automatically updated when the promise is resolved
Fallback (optional?): What to show while the promise hasn't resolved
OnError (optional?): What to show if the promise fails

Here's how I do it

[<AutoOpen>]
module SutilExtensions =
    open Sutil
    type JS.Promise<'T> with
        member self.ToObservable() : ObservablePromise<'T> =
            let op = ObservablePromise<'T>()
            op.Run(self)
            op

let view (server : Server) dispatchExternal (setlistId : string) =

    Bind.el(
         (findCreateSetlist server setlistId).ToObservable(),
         fun x ->
            match x with
            | Waiting ->
                Html.div "Loading..."
            | State.Error x ->
                Html.div (x.Message)
            | Result (setlist,songs) ->
                viewSetlist server dispatchExternal setlist songs
    )

We can make an overload in Bind.el that accepts a Promise, and does the .ToObservable() part internally

This works, thank you @davedawkins!


Starting Bash results in Error: 0x80070005

Your Windows build number:  (Type ver at a Windows Command Prompt)

Microsoft Windows [Version 10.0.15063]

What you're doing and what's happening:  (Copy&paste specific commands and their output, or include screen shots)

Starting Bash

What's wrong / what should be happening instead:

Bash should start without issues

Strace of the failing command, if applicable:  (If <cmd> is failing, then run strace -o strace.txt -ff <cmd>, and post the strace.txt output here)

Strace not available.
Per the instructions on Issue #473 I'm submitting the traces as requested.
wsl-traces.zip
I did perform an lxrun /uninstall /full /y today to eliminate my 14.04 system and upgrade to 16.04
Once I had a successful lxrun /install I was able to run bash once.
I then unpacked my home directory backup.
My home directory backup has replacements for ...
.ssh/    -> (symlink to /mnt/c/Users/joakim/.ssh)
.vim/    -> (symlink to /mnt/c/Users/joakim/vimfiles)
.m2/     -> (symlink to /mnt/c/Users/joakim/.m2)
.bashrc
.bash_aliases
.bash_logout
.gitconfig
.gvimrc
.profile
.vim
.vimrc
java/    -> (symlink to /mnt/c/Users/joakim/java/wsl)

After the unpack (in bash on the first run) i exited bash and attempted to restart, when this error occurred.

I suspect something I did in my home directory caused this, is there a way to start bash in a different home directory?

@joakime - In windows PowerShell, "lxrun /setdefaultuser root".

Once I had a successful lxrun /install I was able to run bash once.

This means you had installed WSL successfully and maden default user, might be joakim?, I think. When you "lxrun /install /y", lxrun does not make default user, but only make root user. If you "lxrun /install", lxrun makes root user and normal user like joakim. The command "lxrun /setdefaultuser root" switch default user to root; of course, you can switch to anoter user like "lxrun /setdefaultuser joakim".

After the unpack (in bash on the first run) i exited bash and attempted to restart, when this error occurred.

After launching bash with root user, you could check why this happens, I think.

After looking at the trace I'm fairly certain this is a duplicate of #651.


Usability issue with exported node types when a scene is Duplicated in the editor

Godot version
v4.1.1.stable.mono.official [bd6af8e0e]
System information
Windows 11
Issue description
It's great to be able to directly export nodes instead of having to export them as NodePaths, or to use get_node even with a unique scene name.
This works as expected when a scene with an exported node is instantiated in the editor. But, if I use the Control+D shortcut (or select this command from the popup menu), the node refence breaks, and the duplicated scenes will refer to the original node, instead of the nodes in their own hierarchy.
I think I understand why this might work like this, but I doubt the current behavior would be useful in any case. An exported node is hardly some outer resource which could act as a "static" member. I'd rather expect that when I lazily duplicate a node, then all its inner node references also updated, as it happens when using a NodePath.
Steps to reproduce
Please check out the attached minimal reproduction project, and/or take a look at the code repository and the screenshot:
https://github.com/sszigeti/Godot_Exported_node_duplication_behavior

Minimal reproduction project
Godot_Exported_node_duplication_behavior-1.zip

https://github.com/godotengine/godot/issues/82670 sounds related to this

Thanks for the report! Consolidating in https://github.com/godotengine/godot/issues/82670.


Use a common SuspendableServerInterceptor for AKID-to-principal mapping.

This change is

This is related to #708


Explicitly name some parameters in callback methods

This improves readability of the callbacks and also significantly
improves the naming of the synthesized UnionType classes that the
parameters represent

LGTM


Changed age_sqrt and age_floor functions volatililty categories

Changed function volatility categories of age_srt() and age_floor() from STABLE to IMMUTABLE
Why age_srt() and age_floor() are Immutable?

Given the same input, the result will never gonna change no matter what.
Both are pure functions & the results only depends on their input values.
Are mathematical functions that will always return the same constant value given the same arguments.

Why age_srt() and age_floor() are not stable?

For a STABLE function “given the same arguments result could change across SQL statements”. But in this case, the result will never gonna change for the same arguments even across multiple SQL statements.

@imranzaheer612 Please fix your commit log entry for the PR to be descriptive of the change - what was changed and why. Once this is corrected, let us know so that we can review the PR for merging.

@imranzaheer612 Please fix your commit log entry for the PR to be descriptive of the change - what was changed and why. Once this is corrected, let us know so that we can review the PR for merging.

Commit log updated. Let me know if still need to change.

@imranzaheer612 I probably should have shown you what I meant -

Please make sure the first part is a reasonable, but short, title. Then add in the details in the extended description. Remember that we don't want the line length going beyond 80 characters. This is due to legacy terminals.

@jrgemignani I updated that. You can take a look now.


Victor VosMottor: Watch pampit.ru

Victor VosMottor requests the watch of the watch_keyword pampit\.ru. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

pampit\.ru has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by cigien in Charcoal HQ