Home App - Fails to Pair Accessory -  Received error (protocol code 2) during pairing process

Hi,
1. I am an Admin, and my fiancee is the Owner of the Apple HomeKit Home.
I used my phone to add the Matter device, but as I am Admin of the house and not the Owner (my fiancee is), I get the following display.

If I click OK and try and add a new accessory, the Matter accessory is visible on my phone.
If I try and add the device on my fiancee's phone, it isn't visible.
On my phone, I click the Matter device, and the above warning appears, and I notice it sends a command to open commissioning window. It is only at that time that the device becomes visible on my finacee's phone. Very cool. I can now proceed with adding the device.

However, when I select the Matter device on her phone, it just hangs up

In the logs, I see errors
I (19024) ROUTE_HOOK: Received RIO
I (19034) ROUTE_HOOK: prefix FD46:BA6D:CE9D:: lifetime 1800

I (19324) ROUTE_HOOK: Received RIO
I (19324) ROUTE_HOOK: prefix FD99:7AEE:449A:: lifetime 1800

I (19844) ROUTE_HOOK: Received RIO
I (19844) ROUTE_HOOK: prefix FD99:7AEE:449A:: lifetime 1800

E (30074) chip[IN]: Data received on an unknown session (LSID=10196). Dropping it!
E (34784) chip[IN]: Data received on an unknown session (LSID=10196). Dropping it!
E (39294) chip[IN]: Data received on an unknown session (LSID=10196). Dropping it!
I (44414) ROUTE_HOOK: Received RIO
I (44414) ROUTE_HOOK: prefix FD99:7AEE:449A:: lifetime 1800

E (46664) chip[IN]: Data received on an unknown session (LSID=10196). Dropping it!
I (52604) chip[EM]: >>> [E:51149r M:178417320] (U) Msg RX from 0:33450209EADD6E45 [0000] --- Type 0000:30 (SecureChannel:CASE_Sigma1)
I (52604) chip[IN]: CASE Server received Sigma1 message. Starting handshake. EC 0x3fc98cf8
I (52614) chip[IN]: CASE Server disabling CASE session setups
I (52634) chip[EM]: <<< [E:51149r M:46017097 (Ack:178417320)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (52644) chip[IN]: (U) Sending msg 46017097 to IP address 'UDP:[FE80::1037:4BB5:7FBC:4569%st1]:59734'
I (52654) chip[SC]: Received Sigma1 msg
I (52664) chip[EM]: <<< [E:51149r M:46017098 (Ack:178417320)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:33 (SecureChannel:CASE_Sigma2Resume)
I (52674) chip[IN]: (U) Sending msg 46017098 to IP address 'UDP:[FE80::1037:4BB5:7FBC:4569%st1]:59734'
I (53014) chip[EM]: >>> [E:51149r M:178417321 (Ack:46017098)] (U) Msg RX from 0:33450209EADD6E45 [0000] --- Type 0000:40 (SecureChannel:StatusReport)
I (53024) chip[SC]: Success status report received. Session was established
I (53044) chip[SC]: SecureSession[0x3fc974d0]: Moving from state 'kEstablishing' --> 'kActive'
I (53044) chip[IN]: CASE Session established to peer: <61A31AE3257E956B, 2>
I (53054) chip[IN]: CASE Server enabling CASE session setups
I (53054) chip[EM]: <<< [E:51149r M:46017099 (Ack:178417321)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (53074) chip[IN]: (U) Sending msg 46017099 to IP address 'UDP:[FE80::1037:4BB5:7FBC:4569%st1]:59734'
I (53084) chip[EM]: >>> [E:51150r M:127948830] (S) Msg RX from 2:61A31AE3257E956B [4A5F] --- Type 0001:0a (IM:TimedRequest)
I (53104) chip[EM]: <<< [E:51150r M:86783068 (Ack:127948830)] (S) Msg TX to 2:61A31AE3257E956B [4A5F] --- Type 0001:01 (IM:StatusResponse)
I (53114) chip[IN]: (S) Sending msg 86783068 on secure session with LSID: 5441
I (53124) chip[EM]: >>> [E:51150r M:127948831 (Ack:86783068)] (S) Msg RX from 2:61A31AE3257E956B [4A5F] --- Type 0001:08 (IM:InvokeCommandRequest)
I (53134) esp_matter_command: Received command 0x0000 for enpoint 0x0000's cluster 0x0000003C
I (53144) chip[ZCL]: Received command to open commissioning window
I (53154) chip[DIS]: Updating services using commissioning mode 2
I (53154) chip[DIS]: CHIP minimal mDNS started advertising.
I (53184) chip[DIS]: Advertise operational node 62276A0E3AA35B0D-0000000063E40CB5
I (53184) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: 62276A0E3AA35B0D-0000000063E40CB5.
I (53204) chip[DIS]: mDNS service published: _matter._tcp
I (53204) chip[DIS]: Advertise operational node 99403E686FAB4A5F-000000001D300FA0
I (53224) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: 99403E686FAB4A5F-000000001D300FA0.
I (53244) chip[DIS]: mDNS service published: _matter._tcp
I (53244) chip[DIS]: Advertise commission parameter vendorID=65521 productID=32768 discriminator=3600/14 cm=2
I (53254) chip[DIS]: CHIP minimal mDNS configured as 'Commissionable node device'; instance name: 05A551279FB9BA75.
I (53294) chip[DIS]: mDNS service published: _matterc._udp
I (53294) chip[ZCL]: Commissioning window is now open
I (53304) chip[EM]: <<< [E:51150r M:86783069 (Ack:127948831)] (S) Msg TX to 2:61A31AE3257E956B [4A5F] --- Type 0001:09 (IM:InvokeCommandResponse)
I (53314) chip[IN]: (S) Sending msg 86783069 on secure session with LSID: 5441
E (53324) chip[DL]: Long dispatch time: 203 ms, for event type 3
I (53324) app_main: Commissioning window opened
I (53344) chip[EM]: >>> [E:51150r M:127948832 (Ack:86783069)] (S) Msg RX from 2:61A31AE3257E956B [4A5F] --- Type 0000:10 (SecureChannel:StandaloneAck)
E (58444) chip[IN]: Data received on an unknown session (LSID=10196). Dropping it!
I (73184) chip[EM]: >>> [E:62910r M:190106792] (U) Msg RX from 0:5456093A6581D1E7 [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)
I (73204) chip[EM]: <<< [E:62910r M:46017100 (Ack:190106792)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (73214) chip[IN]: (U) Sending msg 46017100 to IP address 'UDP:[FE80::10E2:B381:1767:85A8%st1]:50181'
I (73214) chip[EM]: <<< [E:62910r M:46017101 (Ack:190106792)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:21 (SecureChannel:PBKDFParamResponse)
I (73224) chip[IN]: (U) Sending msg 46017101 to IP address 'UDP:[FE80::10E2:B381:1767:85A8%st1]:50181'
I (73584) chip[IN]: (U) Sending msg 46017101 to IP address 'UDP:[FE80::10E2:B381:1767:85A8%st1]:50181'
E (73584) chip[EM]: Ignoring transient send error: 3000001 on exchange 62910r
I (73934) chip[IN]: (U) Sending msg 46017101 to IP address 'UDP:[FE80::10E2:B381:1767:85A8%st1]:50181'
E (73934) chip[EM]: Ignoring transient send error: 3000001 on exchange 62910r
I (74524) chip[IN]: (U) Sending msg 46017101 to IP address 'UDP:[FE80::10E2:B381:1767:85A8%st1]:50181'
E (74524) chip[EM]: Ignoring transient send error: 3000001 on exchange 62910r
I (74934) chip[EM]: >>> [E:62910r M:190106793 (Ack:46017101)] (U) Msg RX from 0:5456093A6581D1E7 [0000] --- Type 0000:22 (SecureChannel:PASE_Pake1)
I (74944) chip[EM]: <<< [E:62910r M:46017102 (Ack:190106793)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (74954) chip[IN]: (U) Sending msg 46017102 to IP address 'UDP:[FE80::10E2:B381:1767:85A8%st1]:50181'
I (75794) chip[EM]: <<< [E:62910r M:46017103 (Ack:190106793)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:23 (SecureChannel:PASE_Pake2)
I (75804) chip[IN]: (U) Sending msg 46017103 to IP address 'UDP:[FE80::10E2:B381:1767:85A8%st1]:50181'
E (75804) chip[DL]: Long dispatch time: 876 ms, for event type 3
I (75854) chip[EM]: >>> [E:62910r M:190106794 (Ack:46017103)] (U) Msg RX from 0:5456093A6581D1E7 [0000] --- Type 0000:40 (SecureChannel:StatusReport)
E (75864) chip[SC]: Received error (protocol code 2) during PASE process: 38
E (75864) chip[SC]: Failed during PASE session setup: 38
E (75874) chip[SVR]: Commissioning failed (attempt 1): 38
I (75874) chip[DIS]: Updating services using commissioning mode 2
I (75894) chip[DIS]: CHIP minimal mDNS started advertising.
I (75944) chip[DIS]: Advertise operational node 62276A0E3AA35B0D-0000000063E40CB5
I (75944) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: 62276A0E3AA35B0D-0000000063E40CB5.
I (75964) chip[DIS]: mDNS service published: _matter._tcp
I (75964) chip[DIS]: Advertise operational node 99403E686FAB4A5F-000000001D300FA0
I (75984) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: 99403E686FAB4A5F-000000001D300FA0.
I (76004) chip[DIS]: mDNS service published: _matter._tcp
I (76004) chip[DIS]: Advertise commission parameter vendorID=65521 productID=32768 discriminator=3600/14 cm=2
I (76014) chip[DIS]: CHIP minimal mDNS configured as 'Commissionable node device'; instance name: 05A551279FB9BA75.
I (76054) chip[DIS]: mDNS service published: _matterc._udp
I (76054) chip[EM]: <<< [E:62910r M:46017104 (Ack:190106794)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (76074) chip[IN]: (U) Sending msg 46017104 to IP address 'UDP:[FE80::10E2:B381:1767:85A8%st1]:50181'
E (76084) chip[DL]: Long dispatch time: 235 ms, for event type 3
I (76084) app_main: Commissioning window opened
I (86494) chip[EM]: >>> [E:62911r M:190106795] (U) Msg RX from 0:A5D5704103397946 [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)
I (86514) chip[EM]: <<< [E:62911r M:46017105 (Ack:190106795)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (86524) chip[IN]: (U) Sending msg 46017105 to IP address 'UDP:[FE80::10E2:B381:1767:85A8%st1]:50181'
I (86524) chip[EM]: <<< [E:62911r M:46017106 (Ack:190106795)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:21 (SecureChannel:PBKDFParamResponse)
I (86544) chip[IN]: (U) Sending msg 46017106 to IP address 'UDP:[FE80::10E2:B381:1767:85A8%st1]:50181'
I (86614) chip[EM]: >>> [E:62911r M:190106796 (Ack:46017106)] (U) Msg RX from 0:A5D5704103397946 [0000] --- Type 0000:22 (SecureChannel:PASE_Pake1)
I (86624) chip[EM]: <<< [E:62911r M:46017107 (Ack:190106796)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (86634) chip[IN]: (U) Sending msg 46017107 to IP address 'UDP:[FE80::10E2:B381:1767:85A8%st1]:50181'
I (87474) chip[EM]: <<< [E:62911r M:46017108 (Ack:190106796)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:23 (SecureChannel:PASE_Pake2)
I (87484) chip[IN]: (U) Sending msg 46017108 to IP address 'UDP:[FE80::10E2:B381:1767:85A8%st1]:50181'
E (87494) chip[DL]: Long dispatch time: 877 ms, for event type 3
I (87544) chip[EM]: >>> [E:62911r M:190106797 (Ack:46017108)] (U) Msg RX from 0:A5D5704103397946 [0000] --- Type 0000:40 (SecureChannel:StatusReport)
E (87554) chip[SC]: Received error (protocol code 2) during PASE process: 38
E (87554) chip[SC]: Failed during PASE session setup: 38
E (87564) chip[SVR]: Commissioning failed (attempt 2): 38
I (87564) chip[DIS]: Updating services using commissioning mode 2
I (87574) chip[DIS]: CHIP minimal mDNS started advertising.
I (87634) chip[DIS]: Advertise operational node 62276A0E3AA35B0D-0000000063E40CB5
I (87634) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: 62276A0E3AA35B0D-0000000063E40CB5.
I (87654) chip[DIS]: mDNS service published: _matter._tcp
I (87654) chip[DIS]: Advertise operational node 99403E686FAB4A5F-000000001D300FA0
I (87674) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: 99403E686FAB4A5F-000000001D300FA0.
I (87694) chip[DIS]: mDNS service published: _matter._tcp
I (87694) chip[DIS]: Advertise commission parameter vendorID=65521 productID=32768 discriminator=3600/14 cm=2
I (87704) chip[DIS]: CHIP minimal mDNS configured as 'Commissionable node device'; instance name: 05A551279FB9BA75.
I (87744) chip[DIS]: mDNS service published: _matterc._udp
I (87744) chip[EM]: <<< [E:62911r M:46017109 (Ack:190106797)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (87764) chip[IN]: (U) Sending msg 46017109 to IP address 'UDP:[FE80::10E2:B381:1767:85A8%st1]:50181'
E (87774) chip[DL]: Long dispatch time: 234 ms, for event type 3
I (87774) app_main: Commissioning window opened
I (97244) ROUTE_HOOK: Received RIO
I (97244) ROUTE_HOOK: prefix FD99:7AEE:449A:: lifetime 1800

I (109124) ROUTE_HOOK: Received RIO
I (109124) ROUTE_HOOK: prefix FD46:BA6D:CE9D:: lifetime 1800

I (289454) ROUTE_HOOK: Received RIO
I (289454) ROUTE_HOOK: prefix FD46:BA6D:CE9D:: lifetime 1800

I (301534) ROUTE_HOOK: Received RIO
I (301534) ROUTE_HOOK: prefix FD99:7AEE:449A:: lifetime 1800

I (313824) ROUTE_HOOK: Received RIO
I (313834) ROUTE_HOOK: prefix FD46:BA6D:CE9D:: lifetime 1800

I (353154) chip[SVR]: Closing pairing window
I (353154) chip[DIS]: Updating services using commissioning mode 0
I (353154) chip[DIS]: CHIP minimal mDNS started advertising.
I (353224) chip[DIS]: Advertise operational node 62276A0E3AA35B0D-0000000063E40CB5
I (353224) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: 62276A0E3AA35B0D-0000000063E40CB5.
I (353244) chip[DIS]: mDNS service published: _matter._tcp
I (353244) chip[DIS]: Advertise operational node 99403E686FAB4A5F-000000001D300FA0
I (353254) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: 99403E686FAB4A5F-000000001D300FA0.
I (353274) chip[DIS]: mDNS service published: _matter._tcp
I (353274) app_main: Commissioning window closed
I (405784) ROUTE_HOOK: Received RIO
I (405784) ROUTE_HOOK: prefix FD99:7AEE:449A:: lifetime 1800

I (470084) ROUTE_HOOK: Received RIO
I (470084) ROUTE_HOOK: prefix FD46:BA6D:CE9D:: lifetime 1800

2. I try to setup from my fiancee's phone
I did a idf.py erase_flash to try again from my finacee's phone. It still doesn't work. I get the following error.

I (1738) app_main: Commissioning window opened
> I (31388) chip[DL]: Configuring CHIPoBLE advertising (interval 500 ms, connectable)
I (31388) chip[DL]: Device already advertising, stop active advertisement and restart
I (31398) NimBLE: GAP procedure initiated: stop advertising.

I (31398) NimBLE: GAP procedure initiated: advertise;
I (31408) NimBLE: disc_mode=2
I (31408) NimBLE:  adv_channel_map=0 own_addr_type=1 adv_filter_policy=0 adv_itvl_min=800 adv_itvl_max=800
I (31418) NimBLE:

I (33438) chip[DL]: BLE GAP connection established (con 1)
I (33448) chip[DL]: CHIPoBLE advertising stopped
I (34358) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (34368) chip[BLE]: local and remote recv window sizes = 5
I (34378) chip[BLE]: selected BTP version 4
I (34378) chip[BLE]: using BTP fragment sizes rx 244 / tx 244.
I (34538) chip[DL]: Write request/command received for CHIPoBLE TX CCCD characteristic (con 1 ) indicate = 1
I (34548) chip[DL]: CHIPoBLE subscribe received
I (34548) NimBLE: GATT procedure initiated: indicate;
I (34558) NimBLE: att_handle=14

I (34598) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (34628) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (34638) chip[EM]: >>> [E:62914r M:190106806] (U) Msg RX from 0:D1CDE13CAE038B11 [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)
I (34648) chip[EM]: <<< [E:62914r M:138783540] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:21 (SecureChannel:PBKDFParamResponse)
I (34658) chip[IN]: (U) Sending msg 138783540 to IP address 'BLE'
I (34668) NimBLE: GATT procedure initiated: indicate;
I (34678) NimBLE: att_handle=14

I (34748) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (34778) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (34788) chip[EM]: >>> [E:62914r M:190106807] (U) Msg RX from 0:D1CDE13CAE038B11 [0000] --- Type 0000:22 (SecureChannel:PASE_Pake1)
I (35628) chip[EM]: <<< [E:62914r M:138783541] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:23 (SecureChannel:PASE_Pake2)
I (35628) chip[IN]: (U) Sending msg 138783541 to IP address 'BLE'
I (35638) NimBLE: GATT procedure initiated: indicate;
I (35648) NimBLE: att_handle=14

E (35648) chip[DL]: Long dispatch time: 867 ms, for event type 7
I (35678) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (35708) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (35718) chip[EM]: >>> [E:62914r M:190106808] (U) Msg RX from 0:D1CDE13CAE038B11 [0000] --- Type 0000:24 (SecureChannel:PASE_Pake3)
I (35728) chip[EM]: <<< [E:62914r M:138783542] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:40 (SecureChannel:StatusReport)
I (35738) chip[IN]: (U) Sending msg 138783542 to IP address 'BLE'
I (35738) NimBLE: GATT procedure initiated: indicate;
I (35758) NimBLE: att_handle=14

I (35758) chip[SC]: SecureSession[0x3fc96eb0]: Moving from state 'kEstablishing' --> 'kActive'
I (35768) chip[SVR]: Commissioning completed session establishment step
I (35768) chip[DIS]: Updating services using commissioning mode 0
I (35778) chip[DIS]: CHIP minimal mDNS started advertising.
I (35778) chip[SVR]: Device completed Rendezvous process
I (35788) app_main: Commissioning session started
I (35798) app_main: Commissioning window closed
I (35828) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (35838) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (35848) chip[EM]: >>> [E:62915r M:252623395] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (35868) chip[EM]: <<< [E:62915r M:113733880] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
I (35868) chip[IN]: (S) Sending msg 113733880 on secure session with LSID: 19243
I (35878) NimBLE: GATT procedure initiated: indicate;
I (35888) NimBLE: att_handle=14

I (35918) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (35928) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (35938) chip[EM]: >>> [E:62916r M:252623396] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (35958) chip[EM]: <<< [E:62916r M:113733881] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
I (35958) chip[IN]: (S) Sending msg 113733881 on secure session with LSID: 19243
I (35968) NimBLE: GATT procedure initiated: indicate;
I (35978) NimBLE: att_handle=14

I (36008) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (36018) NimBLE: GATT procedure initiated: indicate;
I (36028) NimBLE: att_handle=14

I (36068) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (36078) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (36088) chip[EM]: >>> [E:62917r M:252623397] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (36108) chip[EM]: <<< [E:62917r M:113733882] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
I (36108) chip[IN]: (S) Sending msg 113733882 on secure session with LSID: 19243
I (36118) NimBLE: GATT procedure initiated: indicate;
I (36128) NimBLE: att_handle=14

I (36158) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (36168) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (36178) chip[EM]: >>> [E:62918r M:252623398] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (36198) chip[EM]: <<< [E:62918r M:113733883] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
I (36198) chip[IN]: (S) Sending msg 113733883 on secure session with LSID: 19243
I (36208) NimBLE: GATT procedure initiated: indicate;
I (36218) NimBLE: att_handle=14

I (36248) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (36258) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (36268) chip[EM]: >>> [E:62919r M:252623399] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (36288) chip[EM]: <<< [E:62919r M:113733884] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
I (36288) chip[IN]: (S) Sending msg 113733884 on secure session with LSID: 19243
I (36298) NimBLE: GATT procedure initiated: indicate;
I (36308) NimBLE: att_handle=14

I (36338) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (36348) NimBLE: GATT procedure initiated: indicate;
I (36358) NimBLE: att_handle=14

I (36428) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (36438) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (36448) chip[EM]: >>> [E:62920r M:252623400] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (36468) chip[EM]: <<< [E:62920r M:113733885] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
I (36468) chip[IN]: (S) Sending msg 113733885 on secure session with LSID: 19243
I (36478) NimBLE: GATT procedure initiated: indicate;
I (36488) NimBLE: att_handle=14

I (36518) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (36578) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (36588) chip[EM]: >>> [E:62921r M:252623401] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (36598) chip[DL]: NVS set: chip-config/reg-location = 0 (0x0)
I (36608) esp_matter_attribute: ********** Endpoint 0x0000's Cluster 0x0030's Attribute 0x0000 is 0 **********
I (36618) chip[EM]: <<< [E:62921r M:113733886] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
I (36618) chip[IN]: (S) Sending msg 113733886 on secure session with LSID: 19243
I (36628) NimBLE: GATT procedure initiated: indicate;
I (36648) NimBLE: att_handle=14

I (36698) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (36708) NimBLE: GATT procedure initiated: indicate;
I (36718) NimBLE: att_handle=14

I (36758) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (36768) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (36778) chip[EM]: >>> [E:62922r M:252623402] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (36788) esp_matter_command: Received command 0x0000 for enpoint 0x0000's cluster 0x00000030
I (36788) chip[FS]: GeneralCommissioning: Received ArmFailSafe (60s)
I (36808) esp_matter_attribute: ********** Endpoint 0x0000's Cluster 0x0030's Attribute 0x0000 is 3 **********
I (36818) chip[EM]: <<< [E:62922r M:113733887] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (36828) chip[IN]: (S) Sending msg 113733887 on secure session with LSID: 19243
I (36828) NimBLE: GATT procedure initiated: indicate;
I (36838) NimBLE: att_handle=14

I (36878) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (36888) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (36898) chip[EM]: >>> [E:62923r M:252623403] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (36908) esp_matter_command: Received command 0x0002 for enpoint 0x0000's cluster 0x00000030
I (36908) chip[DL]: NVS set: chip-config/reg-location = 0 (0x0)
I (36928) chip[DL]: NVS set: chip-config/country-code = "XX"
I (36928) esp_matter_attribute: ********** Endpoint 0x0000's Cluster 0x0030's Attribute 0x0000 is 4 **********
I (36938) chip[EM]: <<< [E:62923r M:113733888] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (36948) chip[IN]: (S) Sending msg 113733888 on secure session with LSID: 19243
I (36968) NimBLE: GATT procedure initiated: indicate;
I (36968) NimBLE: att_handle=14

I (36998) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (37008) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (37018) chip[EM]: >>> [E:62924r M:252623404] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (37028) esp_matter_command: Received command 0x0002 for enpoint 0x0000's cluster 0x0000003E
I (37028) chip[ZCL]: OpCreds: Certificate Chain request received for PAI
I (37048) chip[EM]: <<< [E:62924r M:113733889] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (37058) chip[IN]: (S) Sending msg 113733889 on secure session with LSID: 19243
I (37058) NimBLE: GATT procedure initiated: indicate;
I (37068) NimBLE: att_handle=14

I (37118) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (37128) NimBLE: GATT procedure initiated: indicate;
I (37138) NimBLE: att_handle=14

I (37178) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (37188) NimBLE: GATT procedure initiated: indicate;
I (37198) NimBLE: att_handle=14

I (37238) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (37268) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (37278) chip[EM]: >>> [E:62925r M:252623405] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (37288) esp_matter_command: Received command 0x0002 for enpoint 0x0000's cluster 0x0000003E
I (37298) chip[ZCL]: OpCreds: Certificate Chain request received for DAC
I (37308) chip[EM]: <<< [E:62925r M:113733890] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (37318) chip[IN]: (S) Sending msg 113733890 on secure session with LSID: 19243
I (37328) NimBLE: GATT procedure initiated: indicate;
I (37328) NimBLE: att_handle=14

I (37388) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (37398) NimBLE: GATT procedure initiated: indicate;
I (37408) NimBLE: att_handle=14

I (37448) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (37458) NimBLE: GATT procedure initiated: indicate;
I (37468) NimBLE: att_handle=14

I (37538) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (37548) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (37558) chip[EM]: >>> [E:62926r M:252623406] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (37568) esp_matter_command: Received command 0x0000 for enpoint 0x0000's cluster 0x0000003E
I (37568) chip[ZCL]: OpCreds: Received an AttestationRequest command
I (37748) chip[ZCL]: OpCreds: AttestationRequest successful.
I (37758) chip[EM]: <<< [E:62926r M:113733891] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (37768) chip[IN]: (S) Sending msg 113733891 on secure session with LSID: 19243
I (37768) NimBLE: GATT procedure initiated: indicate;
I (37778) NimBLE: att_handle=14

E (37788) chip[DL]: Long dispatch time: 228 ms, for event type 7
I (37868) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (37878) NimBLE: GATT procedure initiated: indicate;
I (37888) NimBLE: att_handle=14

I (37928) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (37938) NimBLE: GATT procedure initiated: indicate;
I (37948) NimBLE: att_handle=14

I (37988) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (38018) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (38028) chip[EM]: >>> [E:62927r M:252623407] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (38038) esp_matter_command: Received command 0x0000 for enpoint 0x0000's cluster 0x00000030
I (38048) chip[FS]: GeneralCommissioning: Received ArmFailSafe (60s)
I (38048) esp_matter_attribute: ********** Endpoint 0x0000's Cluster 0x0030's Attribute 0x0000 is 8 **********
I (38068) chip[EM]: <<< [E:62927r M:113733892] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (38078) chip[IN]: (S) Sending msg 113733892 on secure session with LSID: 19243
I (38088) NimBLE: GATT procedure initiated: indicate;
I (38088) NimBLE: att_handle=14

I (38198) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (40208) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (40218) chip[EM]: >>> [E:62928r M:252623408] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (40228) esp_matter_command: Received command 0x0004 for enpoint 0x0000's cluster 0x0000003E
I (40238) chip[ZCL]: OpCreds: Received a CSRRequest command
I (40578) chip[ZCL]: OpCreds: AllocatePendingOperationalKey succeeded
I (40748) chip[ZCL]: OpCreds: CSRRequest successful.
I (40748) chip[EM]: <<< [E:62928r M:113733893] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (40768) chip[IN]: (S) Sending msg 113733893 on secure session with LSID: 19243
I (40768) NimBLE: GATT procedure initiated: indicate;
I (40778) NimBLE: att_handle=14

E (40778) chip[DL]: Long dispatch time: 564 ms, for event type 7
I (40808) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (40818) NimBLE: GATT procedure initiated: indicate;
I (40828) NimBLE: att_handle=14

I (40868) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (40898) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (40988) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (40998) chip[EM]: >>> [E:62929r M:252623409] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (41008) esp_matter_command: Received command 0x000B for enpoint 0x0000's cluster 0x0000003E
I (41018) chip[ZCL]: OpCreds: Received an AddTrustedRootCertificate command
I (41368) chip[ZCL]: OpCreds: AddTrustedRootCertificate successful.
I (41378) chip[EM]: <<< [E:62929r M:113733894] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (41388) chip[IN]: (S) Sending msg 113733894 on secure session with LSID: 19243
I (41398) NimBLE: GATT procedure initiated: indicate;
I (41398) NimBLE: att_handle=14

E (41398) chip[DL]: Long dispatch time: 406 ms, for event type 7
I (41468) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (41478) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (41528) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (41538) chip[EM]: >>> [E:62930r M:252623410] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (41548) esp_matter_command: Received command 0x0006 for enpoint 0x0000's cluster 0x0000003E
I (41558) chip[ZCL]: OpCreds: Received an AddNOC command
I (41568) chip[FP]: Validating NOC chain
I (41918) chip[FP]: NOC chain validation successful
I (41918) chip[FP]: Added new fabric at index: 0x1
I (41918) chip[FP]: Assigned compressed fabric ID: 0xD43208B99A92B1A7, node ID: 0x0000000048563B89
I (41928) chip[TS]: Last Known Good Time: 2022-12-29T13:30:36
I (41938) chip[TS]: New proposed Last Known Good Time: 2022-12-29T13:35:53
I (41938) chip[TS]: Updating pending Last Known Good Time to 2022-12-29T13:35:53
I (41958) chip[ZCL]: OpCreds: ACL entry created for Fabric index 0x1 CASE Admin Subject 0x28D715BA9569913C
I (41958) chip[DIS]: Advertise operational node D43208B99A92B1A7-0000000048563B89
I (41968) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: D43208B99A92B1A7-0000000048563B89.
I (41988) chip[DIS]: mDNS service published: _matter._tcp
I (41988) chip[ZCL]: OpCreds: successfully created fabric index 0x1 via AddNOC
I (41998) chip[EM]: <<< [E:62930r M:113733895] (S) Msg TX to 1:FFFFFFFB00000000 [B1A7] --- Type 0001:09 (IM:InvokeCommandResponse)
I (42008) chip[IN]: (S) Sending msg 113733895 on secure session with LSID: 19243
I (42018) NimBLE: GATT procedure initiated: indicate;
I (42028) NimBLE: att_handle=14

E (42028) chip[DL]: Long dispatch time: 491 ms, for event type 7
I (42098) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (42108) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (42118) chip[EM]: >>> [E:62931r M:252623411] (S) Msg RX from 1:FFFFFFFB00000000 [B1A7] --- Type 0001:08 (IM:InvokeCommandRequest)
I (42128) esp_matter_attribute: ********** Endpoint 0x0000's Cluster 0x0030's Attribute 0x0000 is 14 **********
I (42138) chip[EM]: <<< [E:62931r M:113733896] (S) Msg TX to 1:FFFFFFFB00000000 [B1A7] --- Type 0001:09 (IM:InvokeCommandResponse)
I (42148) chip[IN]: (S) Sending msg 113733896 on secure session with LSID: 19243
I (42158) NimBLE: GATT procedure initiated: indicate;
I (42158) NimBLE: att_handle=14

I (42218) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (42228) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (42238) chip[EM]: >>> [E:62932r M:252623412] (S) Msg RX from 1:FFFFFFFB00000000 [B1A7] --- Type 0001:08 (IM:InvokeCommandRequest)
I (42248) chip[NP]: ESP NetworkCommissioningDelegate: SSID: Palisades
W (42248) wifi:Haven't to connect to a suitable AP now!
I (42268) chip[DL]: WiFi station mode change: Enabled -> Disabled
I (42268) chip[DL]: WiFi station mode change: Disabled -> Enabled
I (42278) phy: chan:1,max_power:80
I (42278) phy: chan:2,max_power:80
I (42288) phy: chan:3,max_power:80
I (42288) phy: chan:4,max_power:80
I (42288) phy: chan:5,max_power:80
I (42298) phy: chan:6,max_power:80
I (42298) phy: chan:7,max_power:80
I (42298) phy: chan:8,max_power:80
I (42308) phy: chan:9,max_power:80
I (42308) phy: chan:10,max_power:80
I (42308) phy: chan:11,max_power:80
I (42318) phy: chan:12,max_power:80
I (42318) phy: chan:13,max_power:80
I (42318) phy: chan:14,max_power:80
W (42328) wifi:Haven't to connect to a suitable AP now!
I (42338) chip[DL]: Attempting to connect WiFi station interface
I (42348) chip[DL]: WiFi station state change: NotConnected -> Connecting
I (42348) chip[DL]: Done driving station state, nothing else to do...
I (42358) phy: chan:1,max_power:80
I (42358) phy: chan:2,max_power:80
I (42368) phy: chan:3,max_power:80
I (42368) phy: chan:4,max_power:80
I (42368) phy: chan:5,max_power:80
I (42378) phy: chan:6,max_power:80
I (42378) phy: chan:7,max_power:80
I (42378) phy: chan:8,max_power:80
I (42398) phy: chan:9,max_power:80
I (42398) phy: chan:10,max_power:80
I (42398) phy: chan:11,max_power:80
I (42408) phy: chan:12,max_power:80
I (42408) phy: chan:13,max_power:80
I (42408) phy: chan:14,max_power:80
W (42418) wifi:Haven't to connect to a suitable AP now!
I (42418) chip[DL]: Attempting to connect WiFi station interface
E (42428) wifi:sta is connecting, return error
E (42428) chip[DL]: esp_wifi_connect() failed: ESP_ERR_WIFI_CONN
I (42438) phy: chan:1,max_power:80
I (42438) phy: chan:2,max_power:80
I (42438) phy: chan:3,max_power:80
I (42458) phy: chan:4,max_power:80
I (42458) phy: chan:5,max_power:80
I (42458) phy: chan:6,max_power:80
I (42468) phy: chan:7,max_power:80
I (42468) phy: chan:8,max_power:80
I (42468) phy: chan:9,max_power:80
I (42478) phy: chan:10,max_power:80
I (42478) phy: chan:11,max_power:80
I (42478) phy: chan:12,max_power:80
I (42488) phy: chan:13,max_power:80
I (42488) phy: chan:14,max_power:80
W (42488) wifi:Haven't to connect to a suitable AP now!
I (42498) chip[DL]: Attempting to connect WiFi station interface
E (42498) wifi:sta is connecting, return error
E (42518) chip[DL]: esp_wifi_connect() failed: ESP_ERR_WIFI_CONN
W (42518) wifi:Haven't to connect to a suitable AP now!
E (42528) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
I (43798) wifi:new:<7,1>, old:<1,0>, ap:<255,255>, sta:<7,1>, prof:1
I (44408) wifi:state: init -> auth (b0)
I (44408) wifi:state: auth -> assoc (0)
I (44418) wifi:state: assoc -> run (10)
I (44438) wifi:connected with Palisades, aid = 6, channel 7, 40U, bssid = b4:20:46:d3:1a:06
I (44438) wifi:security: WPA2-PSK, phy: bgn, rssi: -34
I (44458) wifi:pm start, type: 1

I (44458) wifi:set rx beacon pti, rx_bcn_pti: 14, bcn_timeout: 14, mt_pti: 25000, mt_time: 10000
I (44458) chip[DL]: WIFI_EVENT_STA_CONNECTED
I (44468) chip[DL]: WiFi station state change: Connecting -> Connecting_Succeeded
I (44468) phy: chan:1,max_power:80
I (44488) phy: chan:2,max_power:80
I (44488) phy: chan:3,max_power:80
I (44488) phy: chan:4,max_power:80
I (44498) phy: chan:5,max_power:80
I (44498) phy: chan:6,max_power:80
I (44498) phy: chan:7,max_power:80
I (44508) phy: chan:8,max_power:80
I (44508) phy: chan:9,max_power:80
I (44508) phy: chan:10,max_power:80
I (44518) phy: chan:11,max_power:80
I (44518) phy: chan:12,max_power:80
I (44518) phy: chan:13,max_power:80
I (44528) phy: chan:14,max_power:80
W (44468) wifi:<ba-add>idx:0 (ifx:0, b4:20:46:d3:1a:06), tid:0, ssn:0, winSize:64
I (44548) chip[DL]: WiFi station state change: Connecting_Succeeded -> Connected
I (44548) chip[DL]: WiFi station interface connected
I (44558) esp_matter_attribute: ********** Endpoint 0x0000's Cluster 0x0030's Attribute 0x0000 is 16 **********
I (44568) chip[EM]: <<< [E:62932r M:113733897] (S) Msg TX to 1:FFFFFFFB00000000 [B1A7] --- Type 0001:09 (IM:InvokeCommandResponse)
I (44568) chip[IN]: (S) Sending msg 113733897 on secure session with LSID: 19243
I (44588) NimBLE: GATT procedure initiated: indicate;
I (44598) NimBLE: att_handle=14

I (44598) chip[ZCL]: WiFiDiagnosticsDelegate: OnConnectionStatusChanged
I (44598) chip[DL]: Done driving station state, nothing else to do...
E (44608) chip[DL]: Long dispatch time: 151 ms, for event type 49152
I (44608) chip[DIS]: Advertise operational node D43208B99A92B1A7-0000000048563B89
I (44628) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: D43208B99A92B1A7-0000000048563B89.
I (44638) chip[DIS]: mDNS service published: _matter._tcp
I (44638) chip[SVR]: Operational advertising enabled
I (44648) chip[DL]: Updating advertising data
I (44638) wifi:BcnInt:102400, DTIM:2
I (44678) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (46488) chip[DL]: IP_EVENT_GOT_IP6
I (46488) chip[DL]: IPv6 addr available. Ready on WIFI_STA_DEF interface: fe80:0000:0000:0000:86f7:03ff:fe3a:7c2c
I (46498) app_main: Interface IP Address changed
I (46498) chip[DIS]: Updating services using commissioning mode 0
I (46508) chip[DIS]: CHIP minimal mDNS started advertising.
I (46518) chip[DIS]: Advertise operational node D43208B99A92B1A7-0000000048563B89
I (46518) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: D43208B99A92B1A7-0000000048563B89.
I (46528) chip[DIS]: mDNS service published: _matter._tcp
I (47138) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (48488) esp_netif_handlers: sta ip: <IP_ADDRESS>, mask: <IP_ADDRESS>, gw: <IP_ADDRESS>
I (48488) chip[DL]: IP_EVENT_STA_GOT_IP
I (48498) chip[DL]: IPv4 address changed on WiFi station interface: <IP_ADDRESS>/<IP_ADDRESS> gateway <IP_ADDRESS>
I (48498) chip[DL]: IPv4 Internet connectivity ESTABLISHED
I (48508) app_main: Interface IP Address changed
I (48508) chip[DIS]: Updating services using commissioning mode 0
I (48518) chip[DIS]: CHIP minimal mDNS started advertising.
I (48528) chip[DIS]: Advertise operational node D43208B99A92B1A7-0000000048563B89
I (48538) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: D43208B99A92B1A7-0000000048563B89.
I (48548) chip[DIS]: mDNS service published: _matter._tcp
I (48548) ROUTE_HOOK: Hook already installed on netif, skip...
I (49548) ROUTE_HOOK: Received RIO
I (49548) ROUTE_HOOK: prefix FD46:BA6D:CE9D:: lifetime 1800

I (49588) ROUTE_HOOK: Received RIO
I (49588) ROUTE_HOOK: prefix FD99:7AEE:449A:: lifetime 1800

I (49638) NimBLE: GATT procedure initiated: indicate;
I (49638) NimBLE: att_handle=14

I (49658) ROUTE_HOOK: Received RIO
I (49668) ROUTE_HOOK: prefix FD99:7AEE:449A:: lifetime 1800

I (49668) ROUTE_HOOK: Received RIO
I (49678) ROUTE_HOOK: prefix FD99:7AEE:449A:: lifetime 1800

I (49718) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (51488) chip[DL]: IP_EVENT_GOT_IP6
I (51488) chip[DL]: IPv6 addr available. Ready on WIFI_STA_DEF interface: fd83:85af:31eb:451b:86f7:03ff:fe3a:7c2c
I (51498) app_main: Interface IP Address changed
I (51498) chip[DIS]: Updating services using commissioning mode 0
I (51508) chip[DIS]: CHIP minimal mDNS started advertising.
I (51528) chip[DIS]: Advertise operational node D43208B99A92B1A7-0000000048563B89
I (51528) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: D43208B99A92B1A7-0000000048563B89.
I (51548) chip[DIS]: mDNS service published: _matter._tcp
I (51548) ROUTE_HOOK: Hook already installed on netif, skip...
I (52208) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (52218) chip[EM]: >>> [E:62933r M:190106809] (U) Msg RX from 0:59D60279EF09AB29 [0000] --- Type 0000:30 (SecureChannel:CASE_Sigma1)
I (52238) chip[IN]: CASE Server received Sigma1 message. Starting handshake. EC 0x3fc986d8
I (52238) chip[IN]: CASE Server disabling CASE session setups
I (52248) chip[EM]: <<< [E:62933r M:138783543 (Ack:190106809)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (52258) chip[IN]: (U) Sending msg 138783543 to IP address 'UDP:[FE80::10E2:B381:1767:85A8%st1]:50181'
I (52278) chip[SC]: Received Sigma1 msg
I (52278) chip[SC]: CASE matched destination ID: fabricIndex 1, NodeID 0x0000000048563B89
I (52788) chip[EM]: <<< [E:62933r M:138783544 (Ack:190106809)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:31 (SecureChannel:CASE_Sigma2)
I (52798) chip[IN]: (U) Sending msg 138783544 to IP address 'UDP:[FE80::10E2:B381:1767:85A8%st1]:50181'
I (52798) chip[SC]: Sent Sigma2 msg
E (52818) chip[DL]: Long dispatch time: 593 ms, for event type 3
I (52848) chip[EM]: >>> [E:62933r M:190106810 (Ack:138783544)] (U) Msg RX from 0:59D60279EF09AB29 [0000] --- Type 0000:40 (SecureChannel:StatusReport)
E (52858) chip[SC]: Received error (protocol code 2) during pairing process: 54
E (52868) chip[IN]: CASE Session establishment failed: 54
I (52878) chip[IN]: CASE Server enabling CASE session setups
I (52878) chip[EM]: <<< [E:62933r M:138783545 (Ack:190106810)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (52888) chip[IN]: (U) Sending msg 138783545 to IP address 'UDP:[FE80::10E2:B381:1767:85A8%st1]:50181'
I (53068) chip[EM]: >>> [E:62934r M:190106811] (U) Msg RX from 0:68C0843ED4E02427 [0000] --- Type 0000:30 (SecureChannel:CASE_Sigma1)
I (53078) chip[IN]: CASE Server received Sigma1 message. Starting handshake. EC 0x3fc986d8
I (53078) chip[IN]: CASE Server disabling CASE session setups
I (53088) chip[EM]: <<< [E:62934r M:138783546 (Ack:190106811)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (53098) chip[IN]: (U) Sending msg 138783546 to IP address 'UDP:[FE80::10E2:B381:1767:85A8%st1]:50181'
I (53118) chip[SC]: Received Sigma1 msg
I (53118) chip[SC]: CASE matched destination ID: fabricIndex 1, NodeID 0x0000000048563B89
I (53628) chip[EM]: <<< [E:62934r M:138783547 (Ack:190106811)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:31 (SecureChannel:CASE_Sigma2)
I (53638) chip[IN]: (U) Sending msg 138783547 to IP address 'UDP:[FE80::10E2:B381:1767:85A8%st1]:50181'
I (53638) chip[SC]: Sent Sigma2 msg
E (53648) chip[DL]: Long dispatch time: 589 ms, for event type 3
I (53678) chip[EM]: >>> [E:62934r M:190106812 (Ack:138783547)] (U) Msg RX from 0:68C0843ED4E02427 [0000] --- Type 0000:40 (SecureChannel:StatusReport)
E (53688) chip[SC]: Received error (protocol code 2) during pairing process: 54
E (53688) chip[IN]: CASE Session establishment failed: 54
I (53708) chip[IN]: CASE Server enabling CASE session setups
I (53708) chip[EM]: <<< [E:62934r M:138783548 (Ack:190106812)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (53718) chip[IN]: (U) Sending msg 138783548 to IP address 'UDP:[FE80::10E2:B381:1767:85A8%st1]:50181'
I (53748) ROUTE_HOOK: Received RIO
I (53748) ROUTE_HOOK: prefix FD99:7AEE:449A:: lifetime 1800

I (53758) ROUTE_HOOK: Received RIO
I (53758) ROUTE_HOOK: prefix FD99:7AEE:449A:: lifetime 1800

I (53968) ROUTE_HOOK: Received RIO
I (53968) ROUTE_HOOK: prefix FD99:7AEE:449A:: lifetime 1800

I (54068) ROUTE_HOOK: Received RIO
I (54068) ROUTE_HOOK: prefix FD46:BA6D:CE9D:: lifetime 1800

I (54708) NimBLE: GATT procedure initiated: indicate;
I (54708) NimBLE: att_handle=14

I (54788) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (57248) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (58468) ROUTE_HOOK: Received RIO
I (58468) ROUTE_HOOK: prefix FD46:BA6D:CE9D:: lifetime 1800

I (58778) ROUTE_HOOK: Received RIO
I (58778) ROUTE_HOOK: prefix FD99:7AEE:449A:: lifetime 1800

I (58778) ROUTE_HOOK: Received RIO
I (58788) ROUTE_HOOK: prefix FD99:7AEE:449A:: lifetime 1800

I (58868) ROUTE_HOOK: Received RIO
I (58868) ROUTE_HOOK: prefix FD99:7AEE:449A:: lifetime 1800

I (59748) NimBLE: GATT procedure initiated: indicate;
I (59748) NimBLE: att_handle=14

I (59828) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (60308) ROUTE_HOOK: Received RIO
I (60308) ROUTE_HOOK: prefix FD99:7AEE:449A:: lifetime 1800

I (62288) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (62768) ROUTE_HOOK: Received RIO
I (62768) ROUTE_HOOK: prefix FD46:BA6D:CE9D:: lifetime 1800

I (62868) ROUTE_HOOK: Received RIO
I (62868) ROUTE_HOOK: prefix FD99:7AEE:449A:: lifetime 1800

I (62868) ROUTE_HOOK: Received RIO
I (62878) ROUTE_HOOK: prefix FD99:7AEE:449A:: lifetime 1800

I (62878) ROUTE_HOOK: Received RIO
I (62878) ROUTE_HOOK: prefix FD99:7AEE:449A:: lifetime 1800

I (64788) NimBLE: GATT procedure initiated: indicate;
I (64788) NimBLE: att_handle=14

I (64838) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (67328) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (69828) NimBLE: GATT procedure initiated: indicate;
I (69828) NimBLE: att_handle=14

I (69878) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (72368) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (74238) ROUTE_HOOK: Received RIO
I (74238) ROUTE_HOOK: prefix FD46:BA6D:CE9D:: lifetime 1800

I (74868) NimBLE: GATT procedure initiated: indicate;
I (74868) NimBLE: att_handle=14

I (74918) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (77468) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (79968) NimBLE: GATT procedure initiated: indicate;
I (79968) NimBLE: att_handle=14

I (80018) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (82508) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (84268) ROUTE_HOOK: Received RIO
I (84278) ROUTE_HOOK: prefix FD99:7AEE:449A:: lifetime 1800

I (85008) NimBLE: GATT procedure initiated: indicate;
I (85008) NimBLE: att_handle=14

I (85058) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (87578) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (90078) NimBLE: GATT procedure initiated: indicate;
I (90078) NimBLE: att_handle=14

I (90128) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (92618) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (95118) NimBLE: GATT procedure initiated: indicate;
I (95118) NimBLE: att_handle=14

I (95198) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (97658) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (98048) chip[FS]: Fail-safe timer expired
E (98048) chip[SVR]: Failsafe timer expired
I (98058) chip[SC]: SecureSession[0x3fc96eb0]: Moving from state 'kActive' --> 'kPendingEviction'
E (98068) chip[SVR]: Commissioning failed (attempt 1): 32
I (98078) chip[BLE]: Releasing end point's BLE connection back to application.
I (98078) chip[DIS]: Updating services using commissioning mode 1
I (98088) chip[DIS]: CHIP minimal mDNS started advertising.
I (98108) chip[DIS]: Advertise operational node D43208B99A92B1A7-0000000048563B89
I (98108) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: D43208B99A92B1A7-0000000048563B89.
I (98128) chip[DIS]: mDNS service published: _matter._tcp
I (98128) chip[DIS]: Advertise commission parameter vendorID=65521 productID=32768 discriminator=3840/15 cm=1
I (98138) chip[DIS]: CHIP minimal mDNS configured as 'Commissionable node device'; instance name: E84A24ECA633C490.
I (98168) chip[DIS]: mDNS service published: _matterc._udp
E (98168) chip[ZCL]: OpCreds: Got FailSafeTimerExpired
E (98168) chip[ZCL]: OpCreds: Proceeding to FailSafeCleanup on fail-safe expiry!
E (98188) chip[FP]: Reverting pending fabric data for fabric 0x1
E (98198) chip[FP]: Warning: metadata not found during delete of fabric 0x1
I (98218) chip[FP]: Fabric (0x1) deleted.
I (98218) chip[ZCL]: OpCreds: Fabric index 0x1 was removed
I (98218) chip[DIS]: Updating services using commissioning mode 1
I (98228) chip[DIS]: CHIP minimal mDNS started advertising.
I (98268) chip[DIS]: Advertise commission parameter vendorID=65521 productID=32768 discriminator=3840/15 cm=1
I (98268) chip[DIS]: CHIP minimal mDNS configured as 'Commissionable node device'; instance name: E84A24ECA633C490.
I (98288) chip[DIS]: mDNS service published: _matterc._udp
I (98318) chip[TS]: Pending Last Known Good Time: 2022-12-29T13:35:53
I (98318) chip[TS]: Previous Last Known Good Time: 2022-12-29T13:30:36
I (98328) chip[TS]: Reverted Last Known Good Time to previous value
E (98328) chip[FP]: Warning: metadata not found during delete of fabric 0x1
E (98348) chip[ZCL]: OpCreds: failed to delete fabric at index 1: d8
I (98348) esp_matter_attribute: ********** Endpoint 0x0000's Cluster 0x0030's Attribute 0x0000 is 0 **********
I (98358) app_main: Commissioning failed, fail safe timer expired
E (98358) chip[DL]: Long dispatch time: 306 ms, for event type 32782
I (98368) chip[FS]: Fail-safe cleanly disarmed
I (98368) app_main: Commissioning window opened
I (99218) ROUTE_HOOK: Received RIO
I (99218) ROUTE_HOOK: prefix FD46:BA6D:CE9D:: lifetime 1800

I (112658) chip[DL]: Write request/command received for CHIPoBLE TX CCCD characteristic (con 1 ) indicate = 0
I (112658) chip[DL]: CHIPoBLE unsubscribe received
E (112658) chip[BLE]: no endpoint for unsub recvd
I (112668) chip[DL]: Configuring CHIPoBLE advertising (interval 25 ms, connectable)
I (112678) NimBLE: GAP procedure initiated: advertise;
I (112678) NimBLE: disc_mode=2
I (112688) NimBLE:  adv_channel_map=0 own_addr_type=1 adv_filter_policy=0 adv_itvl_min=40 adv_itvl_max=40
I (112708) NimBLE:

I (112708) chip[DL]: CHIPoBLE advertising started
I (112718) chip[DL]: BLE GAP connection terminated (con 1 reason 0x213)
I (112718) chip[DL]: Configuring CHIPoBLE advertising (interval 25 ms, connectable)
I (112728) chip[DL]: Device already advertising, stop active advertisement and restart
I (112728) NimBLE: GAP procedure initiated: stop advertising.

I (112738) NimBLE: GAP procedure initiated: advertise;
I (112738) NimBLE: disc_mode=2
I (112758) NimBLE:  adv_channel_map=0 own_addr_type=1 adv_filter_policy=0 adv_itvl_min=40 adv_itvl_max=40
I (112768) NimBLE:

I tried with the QR code and it worked.
Ugh. I tried with passcode 20202021 and it worked....
What is<PHONE_NUMBER>2 for!?

What is<PHONE_NUMBER>2 for!?

@mriksman It's the manual pairing code that can be used in certain situations next to or instead of QR code. An example could be commissioning through a voice assistant during which you can say (audio) the manual pairing code as the proof of possession.

@dhrishi Thanks. But. What is the difference between the 'manual code' 20202021 vs<PHONE_NUMBER>2. Why does the iOS Home App use 20202021, whilst the another app (Espressif Matter iOS App???) uses<PHONE_NUMBER>2? What different information does it convey?

20202021 is not the manual pairing code. It is the setup passcode, that serves as the proof of possession.
This setup passcode along with other parameters like discriminator, vid, pid etc. are embedded into QR code as well as the manual pairing code.


Add fetch_maven_artifacts plugin

Signed-off-by: Luiz Carvalho<EMAIL_ADDRESS>

Not sure whether we want to merge this into master yet.

Going over the design doc I realized the allowed_domains implementation was a little off. We want to be able to check the full URL prefix, not just the netloc. Updated accordingly, PTAL.

@twaugh docs updated. Let me know if that's sufficient.


Bump Operator-SDK base image to v0.16.0

This bumps the base image for Operator SDK to match the downstream image under v4.5.0.
Related: https://github.com/infrawatch/smart-gateway-operator/pull/63

/runtest

/runtest


Get-Service should return the user account the services are running under

Currently the #1 item on the PowerShell UserVoice: https://windowsserver.uservoice.com/forums/301869-powershell/suggestions/12336204-get-service-should-return-the-user-account-the-ser
Arnaud Petitjean:

The Get-Service cmdlet should return the service account associated to each service.

We can get this information easily from the Win32_Service WMI class, but to me, it should be returned by Get-Service.

Expected behavior
Get-Service Spooler | Format-List Name,LogOnAs

Name : Spooler
LogOnAs : Local System

Actual behavior
Get-Service Spooler | Format-List Name,LogOnAs

Name : Spooler

Environment data
All versions of PowerShell

please also return StartupType and ServicePath

@copdips StartType as been included in Get-Service output since 5.0:
C:\Users\jaiello> get-service sshd | fl *

Name                : sshd
RequiredServices    : {ssh-agent}
CanPauseAndContinue : False
CanShutdown         : False
CanStop             : False
DisplayName         : sshd
DependentServices   : {}
MachineName         : .
ServiceName         : sshd
ServicesDependedOn  : {ssh-agent}
ServiceHandle       :
Status              : Stopped
ServiceType         : Win32OwnProcess
StartType           : Manual
Site                :
Container           :

But yeah, we should probably have ServicePath too

@SteveL-MSFT , @lzybkr  @joeyaiello  : As mentioned, Service Account info as well service path is available from Win32_Service WMI class. Should I get started on this?

@charub you can always take up issues marked as Backlog, although it's preferred if you can prioritize issues you can fix marked for 6.0.0 milestone

Some food for thought: Don't forget the Description property, and consider device drivers as well.
Years ago when I used to work on PowerGUI (PowerShell v1 days, before StartType was added), we solved this problem like this:
$wmiServices = @{}
Get-WmiObject -Namespace root\cimv2 -Class Win32_Service | ForEach-Object {
	$wmiServices.Add($_.Name,$_)
}
Get-Service `
	| ForEach-Object {
		$_ | Add-Member -Name Win32_Service -MemberType NoteProperty -Value $(if ($wmiServices.ContainsKey($_.ServiceName)) {$wmiServices[$_.ServiceName]} else {$null}) -PassThru
	} `
	| Add-Member -Name Description -MemberType ScriptProperty -Value {if ($this.Win32_Service) { $this.Win32_Service.Description }} -PassThru `
  	| Add-Member -Name LogonAs -MemberType ScriptProperty -Value {if ($this.Win32_Service) { $this.Win32_Service.StartName }} -PassThru `
  	| Add-Member -Name StartupType -MemberType ScriptProperty -Value {if ($this.Win32_Service) { $this.Win32_Service.StartMode }} -PassThru

When digging into the details of how Get-Service works way back then, I discovered that you can also get device drivers from Get-Service. Device drivers can be discovered via WMI using the Win32_SystemDriver class. This led to the following proxy function (implemented using pspx) that supports retrieving the additional properties that were missing (although I didn't get the path) and that supports retrieving services, device drivers, or both:
# This script creates a proxy function for Get-Service. It adds support for retrieving both
# device drivers (which are services under the covers) and windows services, using wildcards
# or fullnames. It allows you to specify the type of service you are looking for as well with
# the -ServiceType parameter. And lastly, it retrieves the Description, the LogonAs and the
# StartupType properties of the services you enumerate (these properties are not visible with
# the built-in Get-Service cmdlet).

Fix-It Get-Service `
	-Synopsis 'Gets the Windows services and device driver services on a local or remote computer.' `
	-Description @'
The Get-Service command gets objects that represent the services on a local computer or on a remote computer, including running and stopped services.

You can direct Get-Service to get only particular services by specifying the service name or display name of the services, or you can pipe service objects to Get-Service.

Services returned from this command may be Windows services or device driver services. You can direct Get-Service to only return services of a particular type using the ServiceType parameter.
'@ `
	-Parameter @(
		@{
			Name = 'ServiceType'
			Alias = 'Type'
			Type = [System.String]
			ValidateSet = @('Service','DeviceDriver','All')
			Description = @'
Gets only services of the specified type. The default is All if you search by name without wildcards, or Service otherwise.

	The valid values for this parameter are:

	-- All: Gets all services on a computer.
	-- Service: Gets standard Windows Services on a computer.
	-- DeviceDriver: Gets device driver services on a computer.

'@
			DefaultValue = '''All'' if you search by name without wildcards, or ''Service'' otherwise.'
			Example = @(
				@{
					ScriptBlock={Get-Service -ServiceType DeviceDriver}
					Description='This command retrieves all device driver services on the local computer. This example shows that you can enumerate all device driver services.'
				}
				@{
					ScriptBlock={Get-Service -Name hvboot}
					Description='This command gets the hvboot device driver service on the local computer. This example shows that you can search for device driver services by name.'
				}
				@{
					ScriptBlock={Get-Service -ServiceType All}
					Description='This command gets both standard Windows Services and device driver services on the local computer.'
				}
			)
		}
	) `
	-DefaultParameterValue @{
		ServiceType = {if ($PSPassThruParameters.ContainsKey('Name') -and ($Name -notmatch '[\?\*]')) {'All'} else {'Service'}}
	} `
	-Begin {
		function ConvertTo-WmiFilter {
			[CmdletBinding()]
			[OutputType([System.String])]
			param(
				[Parameter(Mandatory=$true,Position=0)]
				[ValidateNotNullOrEmpty()]
				[System.String]
				$PropertyName,

				[Parameter()]
				[ValidateNotNullOrEmpty()]
				[System.String[]]
				$FilterValue,

				[Parameter()]
				[ValidateNotNullOrEmpty()]
				[System.String[]]
				$LiteralFilterValue
			)
			$wmiFilterSet = @()
			if ($FilterValue) {
				foreach ($item in $FilterValue) {
					if ([System.Management.Automation.WildcardPattern]::ContainsWildcardCharacters($item)) {
						$wmiEquivalentItem = $item -replace '``','¢' -replace '^\*','%' -replace '^\?','_' -replace '([^`]{1}?)\*','$1%' -replace '([^`]{1}?)\?','$1_' -replace '`\*','*' -replace '`\?','?' -replace '¢','`'
						$wmiFilterSet += "$PropertyName LIKE '$wmiEquivalentItem'"
					} else {
						$wmiEquivalentItem = [System.Management.Automation.WildcardPattern]::Unescape($item)
						$wmiFilterSet += "$PropertyName = '$item'"
					}
				}
			}
			if ($LiteralFilterValue) {
				foreach ($item in $LiteralFilterValue) {
					$wmiFilterSet += "$PropertyName = '$item'"
				}
			}
			$wmiFilterSet -join ' OR '
		}
		$wmiServices = @{}
		$getWmiObjectParameters = @{
			Namespace = 'root\cimv2'
			Class = $(if ($PSCmdlet.MyInvocation.BoundParameters.ContainsKey('Name')) {'Win32_BaseService'} else {'Win32_Service'})
		}
		if ($PSCmdlet.MyInvocation.BoundParameters.ContainsKey('ComputerName')) {
			$getWmiObjectParameters['ComputerName'] = $ComputerName
		}
		if ($PSCmdlet.MyInvocation.BoundParameters.ContainsKey('ServiceType')) {
			switch ($ServiceType) {
				'DeviceDriver' {
					$getWmiObjectParameters['Class'] = 'Win32_SystemDriver'
					break
				}
				'Service' {
					$getWmiObjectParameters['Class'] = 'Win32_Service'
					break
				}
				default {
					$getWmiObjectParameters['Class'] = 'Win32_BaseService'
					break
				}
			}
		}
		$filter = ''
		if ($PSCmdlet.MyInvocation.BoundParameters.ContainsKey('Name')) {
			$filter += '(' + (ConvertTo-WmiFilter -PropertyName Name -FilterValue $Name) + ')'
			$filter += ' OR '
			$filter += '(' + (ConvertTo-WmiFilter -PropertyName DisplayName -FilterValue $Name) + ')'
		} elseif ($PSCmdlet.MyInvocation.BoundParameters.ContainsKey('DisplayName')) {
			$filter += '(' + (ConvertTo-WmiFilter -PropertyName DisplayName -FilterValue $DisplayName) + ')'
		}
		if ($PSCmdlet.MyInvocation.BoundParameters.ContainsKey('Include')) {
			if ($filter) {
				$filter += ' AND '
			}
			$filter += '(' + (ConvertTo-WmiFilter -PropertyName Name -FilterValue $Include) + ')'
		}
		if ($PSCmdlet.MyInvocation.BoundParameters.ContainsKey('Exclude')) {
			if ($filter) {
				$filter += ' AND NOT '
			}
			$filter += '(' + (ConvertTo-WmiFilter -PropertyName Name -FilterValue $Exclude) + ')'
		}
		if ($filter) {
			$getWmiObjectParameters['Filter'] = $filter
		}
		$serviceNames = @()
		Get-WmiObject @getWmiObjectParameters | ForEach-Object {
			if (-not $wmiServices.ContainsKey($_.__SERVER)) {
				$wmiServices[$_.__SERVER] = @{}
			}
			if ($serviceNames -notcontains ($_.Name)) {
				$serviceNames += $_.Name
			}
			$wmiServices[$_.__SERVER][$_.Name] = $_
		}
		if ($serviceNames) {
			$PSPassThruParameters.Remove('Name') | Out-Null
			$PSPassThruParameters.Remove('Include') | Out-Null
			$PSPassThruParameters.Remove('Exclude') | Out-Null
			$PSPassThruParameters['Name'] = $serviceNames | Sort-Object
		}
	} `
	-Process {
		ForEach-Object {
			$serviceComputerName = $_.MachineName
			if (@('<IP_ADDRESS>','.','localhost',"${env:COMPUTERNAME}.${env:USERDNSDOMAIN}") -contains $serviceComputerName) {
				$serviceComputerName = $env:COMPUTERNAME
			}
			if ($wmiServices.ContainsKey($serviceComputerName) -and $wmiServices.$serviceComputerName.ContainsKey($_.ServiceName)) {
				$_ `
					| Add-Member -Name WmiService -MemberType NoteProperty -Value $wmiServices.$serviceComputerName[$_.ServiceName] -PassThru `
					| Add-Member -Name Description -MemberType ScriptProperty -Value {if ($this.WmiService) { $this.WmiService.Description }} -PassThru `
				  	| Add-Member -Name LogonAs -MemberType ScriptProperty -Value {if ($this.WmiService) { $this.WmiService.StartName }} -PassThru `
				  	| Add-Member -Name StartupType -MemberType ScriptProperty -Value {if ($this.WmiService) { $this.WmiService.StartMode }} -PassThru `
					| Add-Member -Force -Name ToString -MemberType ScriptMethod -Value {$this.Name} -PassThru
			}
		}
	} `
	-DefineNow

I just wanted to add this here because it made for easier use of Get-Service that gave back more data properties and that could be used to enumerate device drivers as well.

Whatever happened to this? It looks like it never made it out for public use.

Try:
Get-Service wuauserv | fl * -Force

other work around (like Get-WmiObject is deprecated):
(Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Microsoft SQL Server').InstalledInstances|%{Get-CimInstance  -ClassName win32_service -Filter "Name = '$_'" | ? {$_.state -eq "Running" -and ($_.name -ne 'MSSQLFDLauncher')} |Format-Table name,startname}


Add cada-prio backend service

Is your feature request related to a problem? Please describe.
We currently have viguno for phenotype access. cada-prio shows better performance.
Describe the solution you'd like
Add cada-prio to the reev-docker-compose and document how to get data in README.md.
Describe alternatives you've considered
N/A
Additional context
N/A

Fixed in bihealth/reev-docker-compose#23


Configure linter for VSCode extension code

While reviewing the PR https://github.com/bytecodealliance/wasm-micro-runtime/pull/1637/ I noticed there's a bit of inconsistency in our code for VS Code extension. I'm opening this issue to track setting up a linter that:

checks for style
detects common errors
drives overall best practices in the code

I'd like to also use this issue to track the fixes.

May I ask

Will it be a linter for js/ts only?
Will it be an offline linter(running on developer's computer) or online CI linter?

Hi @lum1n0us I think we can start with ts/js linter for now and only for the VSCode extension. Ideally the linter should run in the CI, but also we should let developers to run them locally with autofix (this could be e.g. a lint script in package.json so developers can simply execute it with npm run lint).

Many thanks for doing that!


Get Z coordinate from body joint x and y

After playing around a while with the pyKinect BodyGame example and doing some research i didn't figure  out how to receive the z value by using the x and y coordinate from the body joints.
In #31 you wrote:

You need to get z from depth frame using x and y you got from body_joints_to_depth_space

what makes sense but this function doesn't exist anymore ( in the PyKinectRuntime.py ).
I've managed to receive the depth frame and to get the x and y coordinates like
joint_points[PyKinectV2.JointType_Head].x
and respectively
joint_points[PyKinectV2.JointType_Head].y
but what's the meaning of this values? ( As an example x: 1529.32343242342 and y:<PHONE_NUMBER> )
They don't fit as index for a standard image matrix ( i could crop them but i'm not shure if this is the "good way" ).
Can u explain how i reach my goal to receive the z value and would it be possible to write an API documentation as mentioned in other Issues before?
At least a list of functions with a small explanation how to use them would be enormous useful.
Thanks for the reply

The solution for the z-Question is quite simple: The pip repository is out of date.
The question for a documentation still exists.
Thanks. Thread can be closed.

@TheSOMGuy
z = self._depth[ y * 424 + x ]    the depth frame is 512*424
But I have another question:  is   the x,y value  color_frame's pixel or  a point in coordinate system? and is x,y value's unit   consistent with z value's (all meter？)

@wxy656
It depends on the function call.
The call depth_points = self._kinect.body_joints_to_depth_space(joints) should always return values in the world coordinate system.
But if i need the z coordinate of an image pixel i would use joint_points = self._kinect.body_joints_to_color_space(joints) for x and y.
Otherwise i obviously can't access the position in the image matrix.
Yes, they should be consistent.

@TheSOMGuy  Hey, I been reading through your comments, and i figured i would have a better chance asking you since the repo seems to be abandoned.
I am interested in getting the depth images from a kinectv2.
What is the difference between self._kinect.body_joints_to_depth_space and frame = self._kinect.get_last_depth_frame()? Is there a need to use the former if the latter already returns the depth image?
Also, do you have any tips on how to extract only the hand depth image from the full image? Right now i am setting depth values > and < than a threshold. it looks like this
. Not very sure if this is the best method

@dhecloud If you know a point that definitely belongs to the hand you can start region growing from there, adding nearby pixels that aren't too far away. That way you wouldn't have the two other artefacts that happen to be within your distance-range. You could also configure region growing to have a maximum depth-distance of say

            if self._bodies is not None:
                if self._kinect.has_new_depth_frame:
                    for i in range(0, self._kinect.max_body_count):
                        body = self._bodies.bodies[i]
                        if not body.is_tracked:
                            continue

                        joints = body.joints
                        # convert joint coordinates to color space
                        joint_points = self._kinect.body_joints_to_color_space(joints)
                        self.draw_body(joints, joint_points, SKELETON_COLORS[i])
                        # get the skeleton joint x y z
                        depth_points = self._kinect.body_joints_to_depth_space(joints)
                        x = int(depth_points[PyKinectV2.JointType_ElbowLeft].x)
                        y = int(depth_points[PyKinectV2.JointType_ElbowLeft].y)
                        _depth = self._kinect.get_last_depth_frame()
                        z = int(_depth[y* 512 + x] )
                        array_x.append(x)
                        array_y.append(y)
                        array_z.append(z)

i want to get the z coordinate, but there is an error (TypeError: 'NoneType' object is not subscriptable ), can anyone helps me~ thanks~

@TheSOMGuy
z = self._depth[ y * 512 + x ] the depth frame is 512*424
But I have another question: is the x,y value color_frame's pixel or a point in coordinate system? and is x,y value's unit consistent with z value's (all meter？)

I do not understand the equation, may you explain me, please? Why 512?

The Kinect camera is taking three different kind of images. One of them is a colour image as you would get from your smartphone (with a resolution of 1920x1080 IIRC), an infrared image (can't remember the resolution) and a depth image with a resolution of 512x424 pixels.
The depth image is a single array of 512*424 numbers, one after another. The first pixel in that array is the pixel in the top left corner. The next pixel in the array is the pixel right next to it.
So if you wanted to iterate over the first row from the image, you'd do for index in range(0, 512): self._depth[index].
Now if you would like to get a specific pixel where you know the row(=y) and column(=x) number of, then you can calculate its index via index = row * 512 + column since you need to sum up the number of pixels in all the rows above and then add the number of pixels to the left of the pixel you want.


[cosmos] React Native support

Is your feature request related to a problem? Please describe.
This library doesn't seem to work with React Native CLI projects
Describe the solution you'd like
Some sort of polyfill / other solution for projects that want to use libraries that will work with react native
Describe alternatives you've considered
We have considered creating a fork with these updated changes.
Additional context
The error we're getting is
error: Error: Unable to resolve module isomorphic-webcrypto from C:\Users\x\OneDrive -<EMAIL_ADDRESS>isomorphic-webcrypto could not be found within the project or in these directories:
  node_modules
  4 | // doing so requires adding a bunch of react packages as peer dependencies. So,
  5 | // it is being loaded dynamically here to not cause compiler error.
> 6 | const globalCrypto = require("isomorphic-webcrypto"); // eslint-disable-line import/no-extraneous-dependencies, @typescript-eslint/no-require-imports
    |                               ^
  7 | export { globalCrypto };
  8 | //# sourceMappingURL=globalCrypto.native.js.map

maybe a duplicate of https://github.com/Azure/azure-sdk-for-js/issues/26574
also related https://github.com/Azure/azure-sdk-for-js/issues/22628


language can't be changed

Hi, Volkanceylan
I really appreciate your work, Serenity is the best framework I have seen ever.
I am going make a back-office system for my company and everything is fine except multi-language.
I am preparing two language set, Korean and English.
In my development environment, default language is Korean.
When I change to English at the general settings, it is not work.
Language setting is changed to Korean automatically.
Have you any experience like my case?
There are 3 files in my App_data/texts directory.
user.texts.en.json, user.texts.invariant.json and user.texts.ko.json
I hope you could give me some hint.

Check cookies and language key you set for Korean in languages page

It should be two letter ko lowercase

Thanks your answer.
I sought cookies and found the language preference is 'en'.
Meanwhile, general settings is set to 'Korean'  which I made as 'ko' / 'Korean'.
I think it is not cookies problem. I've checked 3 types of browser  chrome, firefox and MS edge.
In all of those browsers I can not change the language setting from Korean to English.
I'll reset my system and dig more.
If I found any clue of it, I'll report here.

It sets language in Application_BeginRequest method of global.asax.cs. It might not be working.

OMG!
I've touched that method to amend culture variable.
I forgot it.
Now Serenity is perfect framework :)
Thank you so much.


Does my data has only Chinese can few shot learning support both Chinese and English?

Does my data has only Chinese can few shot learning support both Chinese and English?
About 1min voice.

Yes you can have a try.
1min is enough, but 5min may be better

Does my data has only Chinese can few shot learning support both Chinese and English?
About 1min voice.

May I ask how you managed to achieve the mixed output of Chinese and English? I noticed that when I used English words the model would skip them.

@WinterStraw  You say not using English words?

I expect to be able to do mixed output of languages. That is, a sentence contains both English and Chinese.
While doing interface work, I found that the English part was automatically skipped, and only the Chinese part was read.
Thanks a lot.

@WinterStraw You say not using English words?

I expect to be able to do mixed output of languages. That is, a sentence contains both English and Chinese.
While doing interface work, I found that the English part was automatically skipped, and only the Chinese part was read.
Thanks a lot.

This is unexpected @RVC-Boss

难道我的数据只有中文，少数镜头学习可以同时支持中文和英文吗？
语音约1分钟。

请问你是如何实现中英文混合输出的？我注意到，当我使用英语单词时，模型会跳过它们。

Now it's supported now. Chinese mixing English inference.


Improve SEO for our content

We need to review our metadata (title, description, keywords), our topic title and first paragraph of each topic to make sure that our content is correctly tagged for search engines to find it.
Also need to ensure that our guidelines are complete in terms of SEO guidance.

This issue has been closed as part of the issue backlog grooming process outlined in #22351.
That automated process may have closed some issues that should be addressed. If you think this is one of them, reopen it with a comment explaining why. Tag the @dotnet/docs team for visibility.

This issue has been closed as part of the issue backlog grooming process outlined in #22351.
That automated process may have closed some issues that should be addressed. If you think this is one of them, reopen it with a comment explaining why. Tag the @dotnet/docs team for visibility.


Default to Windows Server version 1809 for Windows nodes.

Removes all references to 1803, including moving "win1803" directory to
just "windows". A single Windows directory suffices for now, if
necessary in the future we can shard it into directories for each
Windows version.
Also switches smoke-test.sh to use containers from
https://hub.docker.com/r/claudiubelu/nettest which have been updated for
1809. This is a temporary change and can be reverted once the official
e2eteam containers have been updated (and possible migrated to a more
official location).

@yujuhong this will update https://testgrid.k8s.io/google-windows#windows-prototype to use 1809. Are we ready to merge this?
cc @mtaufen @jingxu97

If everything looks ok after testing this in our private fork, I'll send a PR (https://github.com/pjh/kubernetes/commit/a8edec9b477ad5b81aac1e88013fe0968432a43e already prepared) upstream.

@yujuhong this will update https://testgrid.k8s.io/google-windows#windows-prototype to use 1809. Are we ready to merge this?

I think we can merge this to test the windows-up fork. I'm hoping the upstream test job will be running by EOD, so that we can get some good signal before switching there.

I've verified that smoke-test.sh passes with a ./hack/e2e.go  -- --up cluster and a kube-up.sh cluster. Will merge this now.


cMF separate density for alpha/beta

Use separate density for alpha and beta electrons for cMF. Also add option to use the relaxation of other clusters within a microiteration of cMF.

Fixed.


Code Splitting with 2.0.0-rc.2 results in "Error: Order in extracted chunk undefined"

I saw a bunch of issues related to code splitting with extract-text-plugin.

https://github.com/webpack-contrib/extract-text-webpack-plugin/issues/208
https://github.com/webpack-contrib/extract-text-webpack-plugin/issues/120
https://github.com/webpack-contrib/extract-text-webpack-plugin/issues/106

We were seeing the issue of using require.ensure and CSS was not extracted, but remained in the chunk bundle. I updated to 2.0.0-rc.2 and use the extract-text-plugin with allChunks: true option and it seemed to work in a minimal use case repo. When I migrated to a larger repo and used the same config I got
ERROR in ./src/containers/DeepDive/ContentBlocks/ContentBlocks.css
Order in extracted chunk undefined

ERROR in ./src/containers/ContactOptions/ActionBlock/ActionBlock.css
Order in extracted chunk undefined

ERROR in ./src/containers/DeepDive/ContentBlocks/ContentBlocks.css
Order in extracted chunk undefined

ERROR in ./src/containers/ContactOptions/ActionBlock/ActionBlock.css
Order in extracted chunk undefined

const plugins = new ExtractTextPlugin({
      filename: assetEntries.css[env],
      allChunks: true,
    }),
]

// loaders
[{
        test: /\.jsx?$/,
        enforce: 'pre',
        loader: 'eslint-loader'
    },
    {
        test: /\.jsx?$/,
        exclude: /node_modules/,
        loader: 'babel-loader',
        options: {
            presets: [Object],
            plugins: [Object],
            babelrc: false
        }
    },
    {
        test: /(components|containers|pages)\/.*\.css$/,
        loader: '/Users/davidfox-powell/dev/sleep-spa/node_modules/extract-text-webpack-plugin/loader.js?{"omit":1,"remove":true}!style-loader?singleton!css-loader?modules&importLoaders=1&localIdentName=[name]__[local]___[hash:base64:5]&-autoprefixer!postcss-loader'
    },
    {
        test: /assets\/css\/.*\.css$/,
        loader: '/Users/davidfox-powell/dev/sleep-spa/node_modules/extract-text-webpack-plugin/loader.js?{"omit":1,"remove":true}!style-loader?singleton!css-loader?importLoaders=1!postcss-loader'
    },
    {
        test: /\.svg$/,
        loader: 'file-loader'
    }
]

which seems potentially related https://github.com/webpack-contrib/extract-text-webpack-plugin/issues/80
I can make the minimal use case repo but it doesn't demonstrate this problem because it only happens in a larger code base
I can also confirm this was happening before I updated on 2.0.0-beta.4 if I add the allChunks: true option

I wonder if we should merge those three into this one. Am I correct to assume this didn't work earlier even?

@bebraw I made this repo for isomorphic rendering of react-router with code splitting
https://github.com/dtothefp/isomorphic-react-router-code-splitting
I'm using require.ensure in the router getComponent, and in the isomorphic build I use babel-plugin-remove-webpack to convert it to a synchronus require. In the webpack config setup I pass the allChunks: true option, which does end up extracting my asynchronously loaded/chunked component CSS module styles out into the CSS bundle. You can test this by running yarn prod:quick and inspecting the dist/main-xxx.css file.
So it looks like my CSS is being extracted from the chunk but I think some of those issues I listed are asking for extracted CSS to create a separate file for each chunk, which I'm not overly concerned with.
What I am concerned with is the error Order in extracted chunk undefined which is referenced in this issue https://github.com/webpack-contrib/extract-text-webpack-plugin/issues/80. I'm seeing this error in our larger application when applying the latest extract text plugin release candidate in combination with the allChunks: true option. Unfortunately I have no idea how to reproduce this in my small repo so if you have any suggestions on how to work with this issue that would be great.

There's ignoreOrder flag now. Please give it a go.

@bebraw thanks...this works for my use case!!

Ok, let's close then.


Behavioral difference with Pygments

When using Pygments 2.2.0 with IronPython 2.7.8 to format source code into syntax highlighted RTF or HTML, the first character of the source code is missing. The same code with the same version of Pygments on IPython 2.7.13 does not exhibit the same bug.
I've tried both the Rust and Python lexers and they have the same problem.
For example, in IronPython:
>>> import sys
>>> sys.path.append(r'C:\Users\gordon.tyler\dev\PygmentSyntaxHighlighter\Pygments-2.2.0-py2.py3-none-any.whl')
>>> import pygments
>>> import pygments.lexers
>>> import pygments.formatters
>>> language='rust'
>>> code=r'''fn factorial(i: u64) -> u64 {
...     let mut acc = 1;
...     for num in 2..i+1 {
...         acc *= num;
...     }
...     acc
... }
... '''
>>> lexer = pygments.lexers.get_lexer_by_name(language, stripnl=False)
>>> formatter = pygments.formatters.get_formatter_by_name('rtf', fontface='Consolas')
>>> pygments.highlight(code, lexer, formatter)
'{\\rtf1\\ansi\\uc0\\deff0{\\fonttbl{\\f0\\fmodern\\fprq1\\fcharset0 Consolas;}}{\\colortbl;\\red125\\green144\\blue41;\\red187\\green102\\blue136;\\red153\\green153\\blue153;\\red25\\green23\\blue124;\\red0\\green0\\blue128;\\red186\\green33\\blue33;\\red0\\green128\\blue0;\\red0\\green0\\blue255;\\red64\\green128\\blue128;\\red136\\green136\\blue136;\\red160\\green160\\blue0;\\red102\\green102\\blue102;\\red136\\green0\\blue0;\\red170\\green34\\blue255;\\red0\\green160\\blue0;\\red0\\green68\\blue221;\\red255\\green0\\blue0;\\red188\\green122\\blue0;\\red176\\green0\\blue64;\\red187\\green187\\blue187;\\red128\\green0\\blue128;\\red160\\green0\\blue0;\\red187\\green102\\blue34;\\red210\\green65\\blue58;}\\f0 n{\\cf20  }factorial(i: {\\cf19 u64}){\\cf20  }-> {\\cf19 u64} \\{{\\cf20 \\par\n}{\\cf20     }{\\cf7\\b let}{\\cf20  }{\\cf7\\b mut}{\\cf20  }acc{\\cf20  }{\\cf12 =}{\\cf20  }{\\cf12 1};{\\cf20 \\par\n}{\\cf20     }{\\cf7\\b for}{\\cf20  }num{\\cf20  }{\\cf7\\b in}{\\cf20  }{\\cf12 2}..i{\\cf12 +}{\\cf12 1}{\\cf20  }\\{{\\cf20 \\par\n}{\\cf20         }acc{\\cf20  }{\\cf12 *}{\\cf12 =}{\\cf20  }num;{\\cf20 \\par\n}{\\cf20     }\\}{\\cf20 \\par\n}{\\cf20     }acc{\\cf20 \\par\n}\\}{\\cf20 \\par\n}}'

Note that the f is missing from fn just after the color table.
The same code in IPython 2.7.13 produces:
u'{\\rtf1\\ansi\\uc0\\deff0{\\fonttbl{\\f0\\fmodern\\fprq1\\fcharset0 Consolas;}}{\\colortbl;\\red136\\green136\\blue136;\\red186\\green33\\blue33;\\red0\\green68\\blue221;\\red102\\green102\\blue102;\\red64\\green128\\blue128;\\red160\\green160\\blue0;\\red25\\green23\\blue124;\\red0\\green128\\blue0;\\red187\\green102\\blue136;\\red187\\green102\\blue34;\\red136\\green0\\blue0;\\red170\\green34\\blue255;\\red153\\green153\\blue153;\\red0\\green160\\blue0;\\red160\\green0\\blue0;\\red255\\green0\\blue0;\\red128\\green0\\blue128;\\red176\\green0\\blue64;\\red0\\green0\\blue255;\\red187\\green187\\blue187;\\red188\\green122\\blue0;\\red0\\green0\\blue128;\\red125\\green144\\blue41;\\red210\\green65\\blue58;}\\f0 {\\cf8\\b fn} {\\cf19 factorial}(i: {\\cf18 u64}){\\cf20  }-> {\\cf18 u64} \\{{\\cf20 \\par\n}{\\cf20     }{\\cf8\\b let}{\\cf20  }{\\cf8\\b mut}{\\cf20  }acc{\\cf20  }{\\cf4 =}{\\cf20  }{\\cf4 1};{\\cf20 \\par\n}{\\cf20     }{\\cf8\\b for}{\\cf20  }num{\\cf20  }{\\cf8\\b in}{\\cf20  }{\\cf4 2}..i{\\cf4 +}{\\cf4 1}{\\cf20  }\\{{\\cf20 \\par\n}{\\cf20         }acc{\\cf20  }{\\cf4 *}{\\cf4 =}{\\cf20  }num;{\\cf20 \\par\n}{\\cf20     }\\}{\\cf20 \\par\n}{\\cf20     }acc{\\cf20 \\par\n}\\}{\\cf20 \\par\n}}'

Looks like the underlying issue may be that the following assertion is not correct in IronPython
assert not u"".startswith(u"\ufeff")

AFAIK, strings in IronPython are always Unicode since that's the case for .NET as well. In C#, the following fails as well:
Assert.False("".StartsWith("\uffef"));

However, in C# this succeeds:
Assert.False("".Equals("\uffef"));

So the strings are considered difference, but StartsWith ignores the Byte Order Mark for some reason.

The backing code of startswith probably needs to use the Ordinal comparison instead
Assert.False("".StartsWith("\uffef", StringComparison.Ordinal));

I'm not sure what implications that has. The .NET string comparison uses locale sorting rules, etc. Does Python string comparison have the same thing or is simply ordinal comparison? It wasn't clear to me from the Python 2.7 docs.

Yes, it's unclear from the Python 2.7 documentation. Here's another example:
assert not u"\xdf".startswith(u"ss")

Yeah, then the CPython string comparison is definitely doing an ordinal / byte comparison, even for unicode strings.


Preview fonts while browsing selections with up/down arrow keys

Click to open dropdown
Use down arrow key to move selection several fonts down
For each selection change, I would like to see the previewed font load up immediately by firing loadedCallback or similar type of callback

This would make it a lot faster to preview the fonts on actual content than having to keep re-opening the dropdown and selecting a new font.
Thoughts?

The Idea was to load as less fonts as we can to make the Document  light weight. This can be an optional feature. I will work on it if I get time. Please let me know if you can do it and i will merge the change into the library.

I understand. I will let you know if I decide to take a stab at it, but currently it's not a high priority on my end. I just figured someone else might also find this useful, and hopefully implement it at some point.


Unable to run Project

Hi ,
Thanks for sharing this project.
I have downloaded, extract and then open the project in visual studio code.
When I run the project with command: ng serve
Below Error comes:
The serve command requires to be run in an Angular project, but a project definition could not be found.
I can create new angular project in separate VS Code solution and can build, run angular application and can see output in browser.
How to run and see login functionality in browser. Assist me
Thanks and Regards.

Hi,
Please run the below commands sequentially, Hope this will help you.
npm install
npm start
After running both the command, I can run project perfectly.

Hi,
Please run the below commands sequentially, Hope this will help you.
npm install
npm start
After running both the command, I can run project perfectly.


QA: Orin with Kairos 2.3.0

This is a card to track QA sanity checks with kairos 2.3.0 and the Nvidia Orin board.

what is tested so far:

[x] flashing
[x] upgrades
[x] upgrades with custom images (adding few packages to see that the default size is enough)

Note: seems build-essential is now in the image (probably pulled by the nvidia stack?). we should check next what are the minimum required packages needed to e.g. run the gpu with k8s.


Windows uninstaller should have option to also remove user data dir and extensions dir

I tried to uninstall / Reinstall Code Insider because of a recurring Error/Crash at "startup/reloaded" (Update / Reboot / proper exit), disabling extensions and remove all custom settings did not fixed it
Before re-installing i wanted to be sure i has no crap left that code have hurted Code Insiders .... surprise surprise ....

VSCode Version: Latest of Code and Code Insider
OS Version: Windows 10

Steps to Reproduce:

Install it
Add extensions
Change settings
Use it
Update it
Uninstall it
Be curious on what's left

On top of that, i uninstalled extensions long time ago and they were still on disk, here is what code-insiders --list-extensions output :
Angular.ng-template
bierner.markdown-preview-github-styles
eamodio.gitlens
EditorConfig.EditorConfig
eg2.tslint
formulahendry.dotnet-test-explorer
GitHub.vscode-pull-request-github
humao.rest-client
icsharpcode.ilspy-vscode
Ionide.Ionide-fsharp
mitchdenny.ecdc
ms-azuretools.vscode-azurefunctions
ms-vscode.azure-account
ms-vscode.cpptools
ms-vscode.csharp
ms-vscode.PowerShell
ms-vsts.team
msjsdiag.debugger-for-chrome
PeterJausovec.vscode-docker
ryanluker.vscode-coverage-gutters
Tyriar.sort-lines
VisualStudioExptTeam.vscodeintellicode

Support this. I think this can be considered after https://github.com/Microsoft/vscode/issues/3884.

Support this. I think this one can be considered after #3884.

i keep getting crash when i close vs code insiders
same when i update (because it is supposed to restart it)
i would gladly test it if shipped
also i
also is there a way to export preferences / extension / everything in a file so i can easily move on ?
as this option probably already existing using internet / cloud
in this context this is not an option when as the company block outgoing tons of http traffic (fear of leaking data)

thx for the link,
Was struck by a corrupted extension, would love to test these new feature to see if it helps resolving such scenario

As #76590 (part of #3884) has been on deck recently, I guess #3884 will be assigned as well. After that, this issue #66837 will be possible to fix. I hope these would happen ASAP because I have waited for near two years (actually #3884 has been opened for more than 3 years).

(ping back)

🦆
a ping from the past,
Should this issue still be tracked / opened / completed
I'm cleaning my backlog and found that one still being opened.
Can anyone confirm if VsCode now properly uninstall or if it needs to stay open ?


Add FuturesSettlemen and ACAT txn variants

Adds FuturesSettlement and ACAT variants to the ReceiveDeliverTransactionSubType enum.
Fixes #3.

Am I missing anything?

Thank you!


Chrony action: Update time

Wouldn't it be nice to be able to update/sync time by a chrony action? My issue is, system time difference is up to 1.5 seconds and when I restart chrony that is fixed. Faster would be to call a service when time is wrong.

call a service

This is not an integration; I think you are mixing up concepts.
../Frenck

Okay. Did not know that there can be no action exposed from add on.


Add new internal cmd package request struct to remove shimdiag package import

This PR was created to remove the shimdiag package import in internal/cmd. This allows us to use the internal/cmd package in more places without worry about import cycles or improper use of service types.
Signed-off-by: Kathryn Baldauf<EMAIL_ADDRESS>

I have no idea how this got closed lol


serve static error

the docs here seem to be a bit incomplete:
https://hono.dev/getting-started/nodejs#serve-static-files
app.use('/images/*', serveStatic({ root: './assets/images' }))

gives me this error:
✘ [ERROR] Error on remote worker: ParseError: A request to the Cloudflare API (/accounts/f9d6328dc3115e621758a741dda3d5c4/workers/scripts/graphql-yoga/edge-preview) failed.

      at throwFetchError
  (/Users/a/Dev/sonicjs-workers/yoga/node_modules/wrangler/wrangler-dist/cli.js:130684:17)
      at fetchResult
  (/Users/a/Dev/sonicjs-workers/yoga/node_modules/wrangler/wrangler-dist/cli.js:130651:5)
      at processTicksAndRejections (node:internal/process/task_queues:96:5)
      at async createPreviewToken
  (/Users/a/Dev/sonicjs-workers/yoga/node_modules/wrangler/wrangler-dist/cli.js:132627:29)
      at async createWorkerPreview
  (/Users/a/Dev/sonicjs-workers/yoga/node_modules/wrangler/wrangler-dist/cli.js:132648:17)
      at async start
  (/Users/a/Dev/sonicjs-workers/yoga/node_modules/wrangler/wrangler-dist/cli.js:151221:34) {
    text: 'A request to the Cloudflare API
  (/accounts/f9d6328dc3115e621758a741dda3d5c4/workers/scripts/graphql-yoga/edge-preview) failed.',
    notes: [
      {
        text: 'Uncaught Error: No such module "__STATIC_CONTENT_MANIFEST".\n' +
          '  imported from "index.js"\n' +
          ' [code: 10021]'
      }
    ],
    location: undefined,
    kind: 'error',
    code: 10021
  }

do I also need to add something like this to the wrangler.toml file?
[site]
bucket = "./assets"

Hi @lane711 !
Try a minimal code:
import { Hono } from 'hono'
import { serveStatic } from 'hono/cloudflare-workers'

const app = new Hono()

app.use('/images/*', serveStatic({ root: './assets/images' }))

export default app

ok got it working, but only after adding:
[site]
bucket = "./assets"

I'm assuming that is required?

@lane711
Yes. See: https://developers.cloudflare.com/workers/platform/sites/configuration/

@lane711
Is this issue fixed?

Yes it is fixed thanks. For anyone else trying to do this, Cloudflare pages is a better solution for my situation. Pages is the newer solution when trying to host static assets.

i have a little confusion here. i used the below code
app.use('/assets/', serveStatic({ root: './' }));
and then this
app.use('/assets/', serveStatic({ root: './assets' }));
and a lot of other variations but whenever i reference some static file in jsx like below image tag

OR

i always get 404 not found.
so how can i reference my static files in jsx? or should i change my serveStatic call or what?


Welcome: Invalid invite link to discord.

Describe the bug
The invite link to discord is invalid.
To Reproduce
Steps to reproduce the behavior:

Go to the welcome page.
Click on Discord chat
See error

Expected behavior
Entering a discord chat.
Screenshots
If applicable, add screenshots to help explain your problem.

+1 - would like to join!

@nikolasrieble @ckifer https://discord.gg/jSdp6TRu
And I'll fix where it is on the Storybook here in a minute.
When I originally launched this storybook. I made a discord, no one joined, so I took it down. It's good to finally see people wanting to use it!
@nikolasrieble let's move all communications onto there!

@nikolasrieble and @ckifer discord is back up


Update all NuGet references

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

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 28.458%

Totals

Change from base Build<PHONE_NUMBER>4:
0.01%

Covered Lines:
3381

Relevant Lines:
10138

💛  - Coveralls


frontend work with some bugs issues in padding property.

Help me out!

Hey @Aaditya-Singh78 , It is super advisable to first open an issue and inform the mentors about the issue, cause of the problem and also a brief summary of your solution. Your PR looks very good to me. It'll be merged. Nothing is perfect, we'll be resolving few bugs in days to come. Nevertheless, great job.
Happy Hacking and contributing! :)


Raidboss: O2N initial package

No enrage on this one, at least within the first 30 minutes. I don't care to try for an hour just to see.

Hmm, I'm sorry, I don't remember what the resolution for translation collisions was?

(?<! )Petrosphere and (?<! )Explosion

I suppose I should have figured that out from the translations I copyasta'd. Thanks for jogging my Sunday-nap brain.

No enrage on this one, at least within the first 30 minutes. I don't care to try for an hour just to see.

:sob: :sob: :sob:
That's some dedication.


Track unmanaged file descriptors

Port: https://github.com/HowProgrammingWorks/NodejsStarterKit/pull/171

Landed in https://github.com/metarhia/impress/commit/da86c3f93398018afcba290340a0eb1ccf5ad7d8


random crash when I try to play

the game loads up to the point when I press "start" and it gives me the loading screen with all the elements. when they all fill in signifying that the game is loaded, it takes me back to the launcher. I am not entirely sure what the whole "wine" thing is, but it is set to "gi-wine-1.0". Let me know if you need more information, Thank you.

macOS: version 11.6 Big Sur
Device: MacBook Air 13.3 Inch
CPU: Apple M1
RAM: 8G

try gi-wine-1.2

hmm it didn't work. I still crash after the loading screen. would another wine version work? should I try all of them?

you can try but I'm not sure any will work. it's not something definitely solvable (at least on my side).


Beta Frontend Setup

Setup beta frontend on https://treeckle.com/beta or https://beta.treeckle.com/

#5


Void recipes have a null output

In Minecraft, ItemStacks are meant to be non-null, however when deserializing a void recipe, you set the recipe result to null if it isn't a replicate:
https://github.com/acikek/void-crafting/blob/main/src/main/java/com/acikek/voidcrafting/recipe/VoidRecipeSerializer.java#L57C68-L57C68
This should most likely read as:
ItemStack result = !replicate ? buf.readItemStack() : ItemStack.EMPTY;

Similarly, this method:
https://github.com/acikek/void-crafting/blob/main/src/main/java/com/acikek/voidcrafting/recipe/VoidRecipe.java#L52
should probably return ItemStack.EMPTY as well.

Thanks for catching this. I'll fix it (and probably do a refactor in the process, tbh) and keep this in mind for future projects.