Connect matter device to Google Home won't work (CON-1087)

Hello there,
I finally got my contact-sensor device generally working.
I also already connected it with apple home and it working out fine (except that the default state is open, not closed as i want it to be)
But when I tried to connect it with Google Home, following error occured:
E (45302) chip[DMG]: Error retrieving data from clusterId: 0x0000_0028, err = 201
maybe somebody can help
Thanks
Florian

Please enable debug log as follows Component config → Log output → Default log verbosity -> Debug
and retry same thing and attach complete device side logs file.

I enabled the debug mode and here is the complete output:
I (36161) chip[ZCL]: Received command to open commissioning window I (36161) chip[DIS]: Updating services using commissioning mode 2 I (36171) chip[DIS]: CHIP minimal mDNS started advertising. I (36181) chip[DIS]: Advertise operational node 5236AFA001B879D3-00000000B69FF720 I (36181) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: 5236AFA001B879D3-00000000B69FF720. I (36201) chip[DIS]: mDNS service published: _matter._tcp I (36201) chip[DIS]: Advertise commission parameter vendorID=65522 productID=32769 discriminator=4054/15 cm=2 cp=0 I (36211) chip[DIS]: CHIP minimal mDNS configured as 'Commissionable node device'; instance name: 7E0318A45F6ECB60. I (36231) chip[DIS]: mDNS service published: _matterc._udp I (36231) chip[ZCL]: Commissioning window is now open I (36241) chip[EM]: <<< [E:17196r S:58560 M:121875092 (Ack:140751351)] (S) Msg TX to 1:00000000C2053460 [79D3] [UDP:<IP_ADDRESS>%st1:57784] --- Type 0001:09 (IM:InvokeCommandResponse) I (36261) logger: [CSystem::matter_event_callback] Commissioning window opened [system.cpp:382] I (36261) chip[EM]: >>> [E:17196r S:58560 M:140751352 (Ack:121875092)] (S) Msg RX from 1:00000000C2053460 [79D3] --- Type 0000:10 (SecureChannel:StandaloneAck) I (36411) chip[EM]: >>> [E:53360r S:0 M:214017046] (U) Msg RX from 0:8E41A27935CD5049 [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest) I (36421) chip[EM]: <<< [E:53360r S:0 M:147602092 (Ack:214017046)] (U) Msg TX to 0:0000000000000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0000:10 (SecureChannel:StandaloneAck) I (36441) chip[EM]: <<< [E:53360r S:0 M:147602093 (Ack:214017046)] (U) Msg TX to 0:0000000000000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0000:21 (SecureChannel:PBKDFParamResponse) I (36451) chip[SVR]: Commissioning session establishment step started I (36481) chip[EM]: >>> [E:53360r S:0 M:214017047 (Ack:147602093)] (U) Msg RX from 0:8E41A27935CD5049 [0000] --- Type 0000:22 (SecureChannel:PASE_Pake1) I (36481) chip[EM]: <<< [E:53360r S:0 M:147602094 (Ack:214017047)] (U) Msg TX to 0:0000000000000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0000:10 (SecureChannel:StandaloneAck) I (37231) chip[EM]: <<< [E:53360r S:0 M:147602095 (Ack:214017047)] (U) Msg TX to 0:0000000000000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0000:23 (SecureChannel:PASE_Pake2) E (37241) chip[DL]: Long dispatch time: 763 ms, for event type 3 I (37271) chip[EM]: >>> [E:53360r S:0 M:214017048 (Ack:147602095)] (U) Msg RX from 0:8E41A27935CD5049 [0000] --- Type 0000:24 (SecureChannel:PASE_Pake3) I (37271) chip[EM]: <<< [E:53360r S:0 M:147602096 (Ack:214017048)] (U) Msg TX to 0:0000000000000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0000:10 (SecureChannel:StandaloneAck) I (37291) chip[EM]: <<< [E:53360r S:0 M:147602097 (Ack:214017048)] (U) Msg TX to 0:0000000000000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0000:40 (SecureChannel:StatusReport) I (37311) chip[SC]: SecureSession[0x3fc9fe78, LSID:58562]: State change 'kEstablishing' --> 'kActive' I (37321) chip[SVR]: Commissioning completed session establishment step I (37321) chip[DIS]: Updating services using commissioning mode 0 I (37331) chip[DIS]: CHIP minimal mDNS started advertising. I (37351) chip[DIS]: Advertise operational node 5236AFA001B879D3-00000000B69FF720 I (37361) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: 5236AFA001B879D3-00000000B69FF720. I (37371) chip[DIS]: mDNS service published: _matter._tcp I (37371) chip[SVR]: Device completed Rendezvous process I (37381) logger: [CSystem::matter_event_callback] Commissioning session started [system.cpp:374] I (37391) chip[EM]: >>> [E:53360r S:0 M:214017049 (Ack:147602097)] (U) Msg RX from 0:8E41A27935CD5049 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck) I (37401) chip[EM]: >>> [E:53361r S:58562 M:14345287] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest) I (37411) logger: [CSystem::matter_event_callback] Commissioning window closed [system.cpp:385] I (37421) chip[EM]: <<< [E:53361r S:58562 M:267819773 (Ack:14345287)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:05 (IM:ReportData) I (37481) chip[EM]: >>> [E:53361r S:58562 M:14345288 (Ack:267819773)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck) I (37481) chip[EM]: >>> [E:53362r S:58562 M:14345289] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest) I (37501) esp_matter_command: Received command 0x00000000 for endpoint 0x0000's cluster 0x00000030 I (37511) chip[FS]: GeneralCommissioning: Received ArmFailSafe (120s) I (37511) esp_matter_attribute: ********** W : Endpoint 0x0000's Cluster 0x00000030's Attribute 0x00000000 is 0 ********** I (37531) chip[EM]: <<< [E:53362r S:58562 M:267819774 (Ack:14345289)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:09 (IM:InvokeCommandResponse) I (37551) chip[EM]: >>> [E:53362r S:58562 M:14345290 (Ack:267819774)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck) I (38261) ROUTE_HOOK: Received RIO I (38261) ROUTE_HOOK: prefix FDD9:AD53:1ECD:: lifetime 1800 I (38561) chip[EM]: >>> [E:53363r S:58562 M:14345291] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest) I (38561) esp_matter_command: Received command 0x00000000 for endpoint 0x0000's cluster 0x0000003E I (38571) chip[ZCL]: OpCreds: Received an AttestationRequest command I (38581) chip[EM]: <<< [E:53363r S:58562 M:267819775 (Ack:14345291)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0000:10 (SecureChannel:StandaloneAck) I (38671) chip[ZCL]: OpCreds: AttestationRequest successful. I (38671) chip[EM]: <<< [E:53363r S:58562 M:267819776 (Ack:14345291)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:09 (IM:InvokeCommandResponse) I (38691) chip[EM]: >>> [E:53363r S:58562 M:14345292 (Ack:267819776)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck) I (38701) chip[EM]: >>> [E:53364r S:58562 M:14345293] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest) I (38711) esp_matter_command: Received command 0x00000002 for endpoint 0x0000's cluster 0x0000003E I (38721) chip[ZCL]: OpCreds: Certificate Chain request received for DAC I (38741) chip[EM]: <<< [E:53364r S:58562 M:267819777 (Ack:14345293)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:09 (IM:InvokeCommandResponse) I (38781) chip[EM]: >>> [E:53364r S:58562 M:14345294 (Ack:267819777)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck) I (38791) chip[EM]: >>> [E:53365r S:58562 M:14345295] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest) I (38801) esp_matter_command: Received command 0x00000002 for endpoint 0x0000's cluster 0x0000003E I (38811) chip[ZCL]: OpCreds: Certificate Chain request received for PAI I (38821) chip[EM]: <<< [E:53365r S:58562 M:267819778 (Ack:14345295)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:09 (IM:InvokeCommandResponse) I (38851) chip[EM]: >>> [E:53365r S:58562 M:14345296 (Ack:267819778)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck) I (38861) chip[EM]: >>> [E:53366r S:58562 M:14345297] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest) I (38881) chip[EM]: <<< [E:53366r S:58562 M:267819779 (Ack:14345297)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:05 (IM:ReportData) I (38911) chip[EM]: >>> [E:53366r S:58562 M:14345298 (Ack:267819779)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck) I (38921) chip[EM]: >>> [E:53367r S:58562 M:14345299] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest) I (38941) chip[EM]: <<< [E:53367r S:58562 M:267819780 (Ack:14345299)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:05 (IM:ReportData) I (38981) chip[EM]: >>> [E:53367r S:58562 M:14345300 (Ack:267819780)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck) I (38981) chip[EM]: >>> [E:53368r S:58562 M:14345301] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest) E (39001) chip[DMG]: Error retrieving data from clusterId: 0x0000_0028, err = 201 I (39001) chip[EM]: <<< [E:53368r S:58562 M:267819781 (Ack:14345301)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:05 (IM:ReportData) I (39041) chip[EM]: >>> [E:53368r S:58562 M:14345302 (Ack:267819781)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck) I (40201) chip[EM]: >>> [E:53369r S:58562 M:14345303] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest) I (40201) chip[EM]: <<< [E:53369r S:58562 M:267819782 (Ack:14345303)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:05 (IM:ReportData) I (40401) chip[EM]: >>> [E:53369r S:58562 M:14345304 (Ack:267819782)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck) I (40411) chip[EM]: >>> [E:53370r S:58562 M:14345305] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest) I (40421) chip[EM]: <<< [E:53370r S:58562 M:267819783 (Ack:14345305)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:05 (IM:ReportData) I (40451) chip[EM]: >>> [E:53370r S:58562 M:14345306 (Ack:267819783)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck) I (40451) chip[EM]: >>> [E:53371r S:58562 M:14345307] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest) E (40471) chip[DMG]: Error retrieving data from clusterId: 0x0000_0028, err = 201 I (40471) chip[EM]: <<< [E:53371r S:58562 M:267819784 (Ack:14345307)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:05 (IM:ReportData) I (40711) chip[EM]: >>> [E:53371r S:58562 M:14345308 (Ack:267819784)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck) I (41671) chip[EM]: >>> [E:53372r S:58562 M:14345309] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest) I (41681) chip[EM]: <<< [E:53372r S:58562 M:267819785 (Ack:14345309)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:05 (IM:ReportData) I (41701) chip[EM]: >>> [E:53372r S:58562 M:14345310 (Ack:267819785)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck) I (41711) chip[EM]: >>> [E:53373r S:58562 M:14345311] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest) I (41721) chip[EM]: <<< [E:53373r S:58562 M:267819786 (Ack:14345311)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:05 (IM:ReportData) I (41751) chip[EM]: >>> [E:53373r S:58562 M:14345312 (Ack:267819786)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck) I (41761) chip[EM]: >>> [E:53374r S:58562 M:14345313] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest) E (41771) chip[DMG]: Error retrieving data from clusterId: 0x0000_0028, err = 201 I (41781) chip[EM]: <<< [E:53374r S:58562 M:267819787 (Ack:14345313)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:05 (IM:ReportData) I (41821) chip[EM]: >>> [E:53374r S:58562 M:14345314 (Ack:267819787)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck) I (42751) ROUTE_HOOK: Received RIO I (42751) ROUTE_HOOK: prefix FDD9:AD53:1ECD:: lifetime 1800 I (46951) ROUTE_HOOK: Received RIO

I added some breaklines for readability, because I couldnt read this.
I (36161) chip[ZCL]: Received command to open commissioning window
I (36161) chip[DIS]: Updating services using commissioning mode 2
I (36171) chip[DIS]: CHIP minimal mDNS started advertising.
I (36181) chip[DIS]: Advertise operational node 5236AFA001B879D3-00000000B69FF720
I (36181) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: 5236AFA001B879D3-00000000B69FF720.
I (36201) chip[DIS]: mDNS service published: _matter._tcp
I (36201) chip[DIS]: Advertise commission parameter vendorID=65522 productID=32769 discriminator=4054/15 cm=2 cp=0
I (36211) chip[DIS]: CHIP minimal mDNS configured as 'Commissionable node device'; instance name: 7E0318A45F6ECB60.
I (36231) chip[DIS]: mDNS service published: _matterc._udp
I (36231) chip[ZCL]: Commissioning window is now open
I (36241) chip[EM]: <<< [E:17196r S:58560 M:121875092 (Ack:140751351)] (S) Msg TX to 1:00000000C2053460 [79D3] [UDP:<IP_ADDRESS>%st1:57784] --- Type 0001:09 (IM:InvokeCommandResponse)
I (36261) logger: [CSystem::matter_event_callback] Commissioning window opened [system.cpp:382]
I (36261) chip[EM]: >>> [E:17196r S:58560 M:140751352 (Ack:121875092)] (S) Msg RX from 1:00000000C2053460 [79D3] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (36411) chip[EM]: >>> [E:53360r S:0 M:214017046] (U) Msg RX from 0:8E41A27935CD5049 [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)
I (36421) chip[EM]: <<< [E:53360r S:0 M:147602092 (Ack:214017046)] (U) Msg TX to 0:0000000000000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (36441) chip[EM]: <<< [E:53360r S:0 M:147602093 (Ack:214017046)] (U) Msg TX to 0:0000000000000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0000:21 (SecureChannel:PBKDFParamResponse)
I (36451) chip[SVR]: Commissioning session establishment step started
I (36481) chip[EM]: >>> [E:53360r S:0 M:214017047 (Ack:147602093)] (U) Msg RX from 0:8E41A27935CD5049 [0000] --- Type 0000:22 (SecureChannel:PASE_Pake1)
I (36481) chip[EM]: <<< [E:53360r S:0 M:147602094 (Ack:214017047)] (U) Msg TX to 0:0000000000000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (37231) chip[EM]: <<< [E:53360r S:0 M:147602095 (Ack:214017047)] (U) Msg TX to 0:0000000000000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0000:23 (SecureChannel:PASE_Pake2)
E (37241) chip[DL]: Long dispatch time: 763 ms, for event type 3
I (37271) chip[EM]: >>> [E:53360r S:0 M:214017048 (Ack:147602095)] (U) Msg RX from 0:8E41A27935CD5049 [0000] --- Type 0000:24 (SecureChannel:PASE_Pake3)
I (37271) chip[EM]: <<< [E:53360r S:0 M:147602096 (Ack:214017048)] (U) Msg TX to 0:0000000000000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (37291) chip[EM]: <<< [E:53360r S:0 M:147602097 (Ack:214017048)] (U) Msg TX to 0:0000000000000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0000:40 (SecureChannel:StatusReport)
I (37311) chip[SC]: SecureSession[0x3fc9fe78, LSID:58562]: State change 'kEstablishing' --> 'kActive'
I (37321) chip[SVR]: Commissioning completed session establishment step
I (37321) chip[DIS]: Updating services using commissioning mode 0
I (37331) chip[DIS]: CHIP minimal mDNS started advertising.
I (37351) chip[DIS]: Advertise operational node 5236AFA001B879D3-00000000B69FF720
I (37361) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: 5236AFA001B879D3-00000000B69FF720.
I (37371) chip[DIS]: mDNS service published: _matter._tcp
I (37371) chip[SVR]: Device completed Rendezvous process
I (37381) logger: [CSystem::matter_event_callback] Commissioning session started [system.cpp:374]
I (37391) chip[EM]: >>> [E:53360r S:0 M:214017049 (Ack:147602097)] (U) Msg RX from 0:8E41A27935CD5049 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (37401) chip[EM]: >>> [E:53361r S:58562 M:14345287] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (37411) logger: [CSystem::matter_event_callback] Commissioning window closed [system.cpp:385]
I (37421) chip[EM]: <<< [E:53361r S:58562 M:267819773 (Ack:14345287)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:05 (IM:ReportData)
I (37481) chip[EM]: >>> [E:53361r S:58562 M:14345288 (Ack:267819773)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (37481) chip[EM]: >>> [E:53362r S:58562 M:14345289] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (37501) esp_matter_command: Received command 0x00000000 for endpoint 0x0000's cluster 0x00000030
I (37511) chip[FS]: GeneralCommissioning: Received ArmFailSaf
E (120s)
I (37511) esp_matter_attribute: ********** W : Endpoint 0x0000's Cluster 0x00000030's Attribute 0x00000000 is 0 **********
I (37531) chip[EM]: <<< [E:53362r S:58562 M:267819774 (Ack:14345289)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:09 (IM:InvokeCommandResponse)
I (37551) chip[EM]: >>> [E:53362r S:58562 M:14345290 (Ack:267819774)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (38261) ROUTE_HOOK: Received RIO
I (38261) ROUTE_HOOK: prefix FDD9:AD53:1ECD:: lifetime 1800
I (38561) chip[EM]: >>> [E:53363r S:58562 M:14345291] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (38561) esp_matter_command: Received command 0x00000000 for endpoint 0x0000's cluster 0x0000003E
I (38571) chip[ZCL]: OpCreds: Received an AttestationRequest command
I (38581) chip[EM]: <<< [E:53363r S:58562 M:267819775 (Ack:14345291)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (38671) chip[ZCL]: OpCreds: AttestationRequest successful.
I (38671) chip[EM]: <<< [E:53363r S:58562 M:267819776 (Ack:14345291)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:09 (IM:InvokeCommandResponse)
I (38691) chip[EM]: >>> [E:53363r S:58562 M:14345292 (Ack:267819776)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (38701) chip[EM]: >>> [E:53364r S:58562 M:14345293] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (38711) esp_matter_command: Received command 0x00000002 for endpoint 0x0000's cluster 0x0000003E
I (38721) chip[ZCL]: OpCreds: Certificate Chain request received for DAC
I (38741) chip[EM]: <<< [E:53364r S:58562 M:267819777 (Ack:14345293)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:09 (IM:InvokeCommandResponse)
I (38781) chip[EM]: >>> [E:53364r S:58562 M:14345294 (Ack:267819777)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (38791) chip[EM]: >>> [E:53365r S:58562 M:14345295] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (38801) esp_matter_command: Received command 0x00000002 for endpoint 0x0000's cluster 0x0000003E
I (38811) chip[ZCL]: OpCreds: Certificate Chain request received for PAI
I (38821) chip[EM]: <<< [E:53365r S:58562 M:267819778 (Ack:14345295)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:09 (IM:InvokeCommandResponse)
I (38851) chip[EM]: >>> [E:53365r S:58562 M:14345296 (Ack:267819778)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (38861) chip[EM]: >>> [E:53366r S:58562 M:14345297] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (38881) chip[EM]: <<< [E:53366r S:58562 M:267819779 (Ack:14345297)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:05 (IM:ReportData)
I (38911) chip[EM]: >>> [E:53366r S:58562 M:14345298 (Ack:267819779)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (38921) chip[EM]: >>> [E:53367r S:58562 M:14345299] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (38941) chip[EM]: <<< [E:53367r S:58562 M:267819780 (Ack:14345299)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:05 (IM:ReportData)
I (38981) chip[EM]: >>> [E:53367r S:58562 M:14345300 (Ack:267819780)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (38981) chip[EM]: >>> [E:53368r S:58562 M:14345301] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
E (39001) chip[DMG]: Error retrieving data from clusterId: 0x0000_0028, err = 201
I (39001) chip[EM]: <<< [E:53368r S:58562 M:267819781 (Ack:14345301)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:05 (IM:ReportData)
I (39041) chip[EM]: >>> [E:53368r S:58562 M:14345302 (Ack:267819781)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (40201) chip[EM]: >>> [E:53369r S:58562 M:14345303] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (40201) chip[EM]: <<< [E:53369r S:58562 M:267819782 (Ack:14345303)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:05 (IM:ReportData)
I (40401) chip[EM]: >>> [E:53369r S:58562 M:14345304 (Ack:267819782)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (40411) chip[EM]: >>> [E:53370r S:58562 M:14345305] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (40421) chip[EM]: <<< [E:53370r S:58562 M:267819783 (Ack:14345305)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:05 (IM:ReportData)
I (40451) chip[EM]: >>> [E:53370r S:58562 M:14345306 (Ack:267819783)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (40451) chip[EM]: >>> [E:53371r S:58562 M:14345307] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
E (40471) chip[DMG]: Error retrieving data from clusterId: 0x0000_0028, err = 201
I (40471) chip[EM]: <<< [E:53371r S:58562 M:267819784 (Ack:14345307)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:05 (IM:ReportData)
I (40711) chip[EM]: >>> [E:53371r S:58562 M:14345308 (Ack:267819784)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (41671) chip[EM]: >>> [E:53372r S:58562 M:14345309] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (41681) chip[EM]: <<< [E:53372r S:58562 M:267819785 (Ack:14345309)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:05 (IM:ReportData)
I (41701) chip[EM]: >>> [E:53372r S:58562 M:14345310 (Ack:267819785)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (41711) chip[EM]: >>> [E:53373r S:58562 M:14345311] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (41721) chip[EM]: <<< [E:53373r S:58562 M:267819786 (Ack:14345311)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:05 (IM:ReportData)
I (41751) chip[EM]: >>> [E:53373r S:58562 M:14345312 (Ack:267819786)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (41761) chip[EM]: >>> [E:53374r S:58562 M:14345313] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
E (41771) chip[DMG]: Error retrieving data from clusterId: 0x0000_0028, err = 201
I (41781) chip[EM]: <<< [E:53374r S:58562 M:267819787 (Ack:14345313)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:62859] --- Type 0001:05 (IM:ReportData)
I (41821) chip[EM]: >>> [E:53374r S:58562 M:14345314 (Ack:267819787)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (42751) ROUTE_HOOK: Received RIO
I (42751) ROUTE_HOOK: prefix FDD9:AD53:1ECD:: lifetime 1800
I (46951) ROUTE_HOOK: Received RIO

The above logs do not indicate that debug log configuration is enabled.
The error 201 stands for CHIP_DEVICE_ERROR_CONFIG_NOT_FOUND, indicating that the requested configuration value was not found. The error is encountered for cluster 0x0028, which is the basic information cluster. Please enable the debug log as mentioned above to get the attribute of the cluster for which the config value is not found.
Additionally, could you please let me know if you are trying to make any changes to the basic information cluster in your code?

@VaishaliAvhale
I tried to enable the debug log as mentioned, but I think it didn't work. I'm working with Visual Studio on Windows via WSL. I enabled the debug log in the VS Extension settings, but this dont effect my log output.
Is there another way to enable the log?
I don't think I'm trying to do any changes to the basic information cluster.

Add CONFIG_LOG_DEFAULT_LEVEL_DEBUG=y to your file sdkconfig.defaults
And build using idf.py -D SDKCONFIG_DEFAULTS="sdkconfig.defaults" clean build
You should see CONFIG_LOG_DEFAULT_LEVEL_DEBUG=y in the sdkconfig that was generated during the build.

Okay, I think that worked now, thank you @FHFS.
This is the part from the sdkconfig:
# Log output
#
# CONFIG_LOG_DEFAULT_LEVEL_NONE is not set
# CONFIG_LOG_DEFAULT_LEVEL_ERROR is not set
# CONFIG_LOG_DEFAULT_LEVEL_WARN is not set
# CONFIG_LOG_DEFAULT_LEVEL_INFO is not set
CONFIG_LOG_DEFAULT_LEVEL_DEBUG=y
# CONFIG_LOG_DEFAULT_LEVEL_VERBOSE is not set

Now the log is massive, I hope I copied everything that is necessary:
D (63516) chip[DMG]: All ReadHandler-s are clean, clear GlobalDirtySet
I (63526) chip[EM]: >>> [E:30269r S:55454 M:225728011 (Ack:190411351)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
D (63536) chip[EM]: Found matching exchange: 30269r, Delegate: 0x0
D (63546) chip[EM]: Rxd Ack; Removing MessageCounter:190411351 from Retrans Table on exchange 30269r
I (63556) chip[EM]: >>> [E:30270r S:55454 M:225728012] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
D (63566) chip[EM]: Handling via exchange: 30270r, Delegate: 0x3fca5054
D (63576) chip[IM]: Received Read request
D (63576) chip[DMG]: ReadRequestMessage =
D (63586) chip[DMG]: {
D (63586) chip[DMG]:    AttributePathIBs =
D (63586) chip[DMG]:    [
D (63596) chip[DMG]:            AttributePathIB =
D (63596) chip[DMG]:            {
D (63596) chip[DMG]:                    Endpoint = 0x0,
D (63606) chip[DMG]:                    Cluster = 0x28,
D (63606) chip[DMG]:                    Attribute = 0x0000_0003,
D (63606) chip[DMG]:            }
D (63616) chip[DMG]:
D (63616) chip[DMG]:    ],
D (63616) chip[DMG]:
D (63626) chip[DMG]:    isFabricFiltered = true,
D (63626) chip[DMG]:    InteractionModelRevision = 11
D (63626) chip[DMG]: },
D (63636) chip[DMG]: IM RH moving to [CanStartReporting]
D (63636) chip[DMG]: Building Reports for ReadHandler with LastReportGeneration = 0x0000000000000000 DirtyGeneration = 0x0000000000000000
D (63646) chip[DMG]: <RE:Run> Cluster 28, Attribute 3 is dirty
D (63656) chip[DMG]: Reading attribute: Cluster=0x0000_0028 Endpoint=0 AttributeId=0x0000_0003 (expanded=0)
D (63666) nvs: nvs_open_from_partition chip-factory 0
D (63676) nvs: nvs_get_str_or_blob product-name
D (63676) nvs: nvs_close 381
E (63676) chip[DMG]: Error retrieving data from clusterId: 0x0000_0028, err = 201
D (63686) chip[DMG]: <RE> Sending report (payload has 33 bytes)...
I (63696) chip[EM]: <<< [E:30270r S:55454 M:190411352 (Ack:225728012)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:59913] --- Type 0001:05 (IM:ReportData)
D (63716) chip[DMG]: <RE> OnReportConfirm: NumReports = 0
D (63716) chip[DMG]: <RE> ReportsInFlight = 0 with readHandler 0, RE has no more messages
D (63726) chip[DMG]: IM RH moving to [AwaitingDestruction]
D (63726) nvs: nvs_open_from_partition CHIP_KVS 0
D (63736) nvs: nvs_get_str_or_blob g/su/0
D (63736) nvs: nvs_close 382
D (63746) nvs: nvs_open_from_partition CHIP_KVS 0
D (63746) nvs: nvs_get_str_or_blob g/su/1
D (63746) nvs: nvs_close 383
D (63756) nvs: nvs_open_from_partition CHIP_KVS 0
D (63756) nvs: nvs_get_str_or_blob g/su/2
D (63766) nvs: nvs_close 384
D (63766) nvs: nvs_open_from_partition CHIP_KVS 0
D (63766) nvs: nvs_get_str_or_blob g/su/3
D (63776) nvs: nvs_close 385
D (63776) nvs: nvs_open_from_partition CHIP_KVS 0
D (63786) nvs: nvs_get_str_or_blob g/su/4
D (63786) nvs: nvs_close 386
D (63786) nvs: nvs_open_from_partition CHIP_KVS 0
D (63796) nvs: nvs_get_str_or_blob g/su/5
D (63796) nvs: nvs_close 387
D (63796) nvs: nvs_open_from_partition CHIP_KVS 0
D (63806) nvs: nvs_get_str_or_blob g/su/6
D (63806) nvs: nvs_close 388
D (63816) nvs: nvs_open_from_partition CHIP_KVS 0
D (63816) nvs: nvs_get_str_or_blob g/su/7
D (63826) nvs: nvs_close 389
D (63826) nvs: nvs_open_from_partition CHIP_KVS 0
D (63826) nvs: nvs_get_str_or_blob g/su/8
D (63836) nvs: nvs_close 390
D (63836) nvs: nvs_open_from_partition CHIP_KVS 0
D (63846) nvs: nvs_get_str_or_blob g/su/9
D (63846) nvs: nvs_close 391
D (63846) nvs: nvs_open_from_partition CHIP_KVS 0
D (63856) nvs: nvs_get_str_or_blob g/su/a
D (63856) nvs: nvs_close 392
D (63856) nvs: nvs_open_from_partition CHIP_KVS 0
D (63866) nvs: nvs_get_str_or_blob g/su/b
D (63866) nvs: nvs_close 393
D (63876) nvs: nvs_open_from_partition CHIP_KVS 0
D (63876) nvs: nvs_get_str_or_blob g/su/c
D (63876) nvs: nvs_close 394
D (63886) nvs: nvs_open_from_partition CHIP_KVS 0
D (63886) nvs: nvs_get_str_or_blob g/su/d
D (63896) nvs: nvs_close 395
D (63896) nvs: nvs_open_from_partition CHIP_KVS 0
D (63896) nvs: nvs_get_str_or_blob g/su/e
D (63906) nvs: nvs_close 396
D (63906) chip[DMG]: All ReadHandler-s are clean, clear GlobalDirtySet
I (63916) chip[EM]: >>> [E:30270r S:55454 M:225728013 (Ack:190411352)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
D (63926) chip[EM]: Found matching exchange: 30270r, Delegate: 0x0
D (63936) chip[EM]: Rxd Ack; Removing MessageCounter:190411352 from Retrans Table on exchange 30270r
I (64856) chip[EM]: >>> [E:30271r S:55454 M:225728014] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
D (64856) chip[EM]: Handling via exchange: 30271r, Delegate: 0x3fca5054
D (64866) chip[IM]: Received Read request
D (64866) chip[DMG]: ReadRequestMessage =
D (64876) chip[DMG]: {
D (64876) chip[DMG]:    AttributePathIBs =
D (64876) chip[DMG]:    [
D (64876) chip[DMG]:            AttributePathIB =
D (64886) chip[DMG]:            {
D (64886) chip[DMG]:                    Endpoint = 0x0,
D (64886) chip[DMG]:                    Cluster = 0x28,
D (64896) chip[DMG]:                    Attribute = 0x0000_0002,
D (64896) chip[DMG]:            }
D (64906) chip[DMG]:
D (64906) chip[DMG]:    ],
D (64906) chip[DMG]:
D (64906) chip[DMG]:    isFabricFiltered = true,
D (64916) chip[DMG]:    InteractionModelRevision = 11
D (64916) chip[DMG]: },
D (64926) chip[DMG]: IM RH moving to [CanStartReporting]
D (64926) chip[DMG]: Building Reports for ReadHandler with LastReportGeneration = 0x0000000000000000 DirtyGeneration = 0x0000000000000000
D (64936) chip[DMG]: <RE:Run> Cluster 28, Attribute 2 is dirty
D (64946) chip[DMG]: Reading attribute: Cluster=0x0000_0028 Endpoint=0 AttributeId=0x0000_0002 (expanded=0)
D (64956) nvs: nvs_open_from_partition chip-factory 0
D (64956) nvs: nvs_get vendor-id 4
D (64966) nvs: nvs_close 397
D (64966) chip[DMG]: <RE> Sending report (payload has 37 bytes)...
I (64976) chip[EM]: <<< [E:30271r S:55454 M:190411353 (Ack:225728014)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:59913] --- Type 0001:05 (IM:ReportData)
D (64996) chip[DMG]: <RE> OnReportConfirm: NumReports = 0
D (64996) chip[DMG]: <RE> ReportsInFlight = 0 with readHandler 0, RE has no more messages
D (65006) chip[DMG]: IM RH moving to [AwaitingDestruction]
D (65006) nvs: nvs_open_from_partition CHIP_KVS 0
D (65016) nvs: nvs_get_str_or_blob g/su/0
D (65016) nvs: nvs_close 398
D (65026) nvs: nvs_open_from_partition CHIP_KVS 0
D (65026) nvs: nvs_get_str_or_blob g/su/1
D (65026) nvs: nvs_close 399
D (65036) nvs: nvs_open_from_partition CHIP_KVS 0
D (65036) nvs: nvs_get_str_or_blob g/su/2
D (65046) nvs: nvs_close 400
D (65046) nvs: nvs_open_from_partition CHIP_KVS 0
D (65046) nvs: nvs_get_str_or_blob g/su/3
D (65056) nvs: nvs_close 401
D (65056) nvs: nvs_open_from_partition CHIP_KVS 0
D (65066) nvs: nvs_get_str_or_blob g/su/4
D (65066) nvs: nvs_close 402
D (65066) nvs: nvs_open_from_partition CHIP_KVS 0
D (65076) nvs: nvs_get_str_or_blob g/su/5
D (65076) nvs: nvs_close 403
D (65076) nvs: nvs_open_from_partition CHIP_KVS 0
D (65086) nvs: nvs_get_str_or_blob g/su/6
D (65086) nvs: nvs_close 404
D (65096) nvs: nvs_open_from_partition CHIP_KVS 0
D (65096) nvs: nvs_get_str_or_blob g/su/7
D (65106) nvs: nvs_close 405
D (65106) nvs: nvs_open_from_partition CHIP_KVS 0
D (65106) nvs: nvs_get_str_or_blob g/su/8
D (65116) nvs: nvs_close 406
D (65116) nvs: nvs_open_from_partition CHIP_KVS 0
D (65116) nvs: nvs_get_str_or_blob g/su/9
D (65126) nvs: nvs_close 407
D (65126) nvs: nvs_open_from_partition CHIP_KVS 0
D (65136) nvs: nvs_get_str_or_blob g/su/a
D (65136) nvs: nvs_close 408
D (65136) nvs: nvs_open_from_partition CHIP_KVS 0
D (65146) nvs: nvs_get_str_or_blob g/su/b
D (65146) nvs: nvs_close 409
D (65156) nvs: nvs_open_from_partition CHIP_KVS 0
D (65156) nvs: nvs_get_str_or_blob g/su/c
D (65156) nvs: nvs_close 410
D (65166) nvs: nvs_open_from_partition CHIP_KVS 0
D (65166) nvs: nvs_get_str_or_blob g/su/d
D (65176) nvs: nvs_close 411
D (65176) nvs: nvs_open_from_partition CHIP_KVS 0
D (65176) nvs: nvs_get_str_or_blob g/su/e
D (65186) nvs: nvs_close 412
D (65186) chip[DMG]: All ReadHandler-s are clean, clear GlobalDirtySet
I (65196) chip[EM]: >>> [E:30271r S:55454 M:225728015 (Ack:190411353)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
D (65206) chip[EM]: Found matching exchange: 30271r, Delegate: 0x0
D (65216) chip[EM]: Rxd Ack; Removing MessageCounter:190411353 from Retrans Table on exchange 30271r
I (65226) chip[EM]: >>> [E:30272r S:55454 M:225728016] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
D (65236) chip[EM]: Handling via exchange: 30272r, Delegate: 0x3fca5054
D (65246) chip[IM]: Received Read request
D (65246) chip[DMG]: ReadRequestMessage =
D (65246) chip[DMG]: {
D (65256) chip[DMG]:    AttributePathIBs =
D (65256) chip[DMG]:    [
D (65256) chip[DMG]:            AttributePathIB =
D (65266) chip[DMG]:            {
D (65266) chip[DMG]:                    Endpoint = 0x0,
D (65266) chip[DMG]:                    Cluster = 0x28,
D (65276) chip[DMG]:                    Attribute = 0x0000_0004,
D (65276) chip[DMG]:            }
D (65286) chip[DMG]:
D (65286) chip[DMG]:    ],
D (65286) chip[DMG]:
D (65286) chip[DMG]:    isFabricFiltered = true,
D (65296) chip[DMG]:    InteractionModelRevision = 11
D (65296) chip[DMG]: },
D (65306) chip[DMG]: IM RH moving to [CanStartReporting]
D (65306) chip[DMG]: Building Reports for ReadHandler with LastReportGeneration = 0x0000000000000000 DirtyGeneration = 0x0000000000000000
D (65316) chip[DMG]: <RE:Run> Cluster 28, Attribute 4 is dirty
D (65326) chip[DMG]: Reading attribute: Cluster=0x0000_0028 Endpoint=0 AttributeId=0x0000_0004 (expanded=0)
D (65336) nvs: nvs_open_from_partition chip-factory 0
D (65336) nvs: nvs_get product-id 4
D (65346) nvs: nvs_close 413
D (65346) chip[DMG]: <RE> Sending report (payload has 37 bytes)...
I (65356) chip[EM]: <<< [E:30272r S:55454 M:190411354 (Ack:225728016)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:59913] --- Type 0001:05 (IM:ReportData)
D (65376) chip[DMG]: <RE> OnReportConfirm: NumReports = 0
D (65376) chip[DMG]: <RE> ReportsInFlight = 0 with readHandler 0, RE has no more messages
D (65386) chip[DMG]: IM RH moving to [AwaitingDestruction]
D (65386) nvs: nvs_open_from_partition CHIP_KVS 0
D (65396) nvs: nvs_get_str_or_blob g/su/0
D (65396) nvs: nvs_close 414
D (65406) nvs: nvs_open_from_partition CHIP_KVS 0
D (65406) nvs: nvs_get_str_or_blob g/su/1
D (65406) nvs: nvs_close 415
D (65416) nvs: nvs_open_from_partition CHIP_KVS 0
D (65416) nvs: nvs_get_str_or_blob g/su/2
D (65426) nvs: nvs_close 416
D (65426) nvs: nvs_open_from_partition CHIP_KVS 0
D (65426) nvs: nvs_get_str_or_blob g/su/3
D (65436) nvs: nvs_close 417
D (65436) nvs: nvs_open_from_partition CHIP_KVS 0
D (65446) nvs: nvs_get_str_or_blob g/su/4
D (65446) nvs: nvs_close 418
D (65446) nvs: nvs_open_from_partition CHIP_KVS 0
D (65456) nvs: nvs_get_str_or_blob g/su/5
D (65456) nvs: nvs_close 419
D (65456) nvs: nvs_open_from_partition CHIP_KVS 0
D (65466) nvs: nvs_get_str_or_blob g/su/6
D (65466) nvs: nvs_close 420
D (65476) nvs: nvs_open_from_partition CHIP_KVS 0
D (65476) nvs: nvs_get_str_or_blob g/su/7
D (65476) nvs: nvs_close 421
D (65486) nvs: nvs_open_from_partition CHIP_KVS 0
D (65486) nvs: nvs_get_str_or_blob g/su/8
D (65496) nvs: nvs_close 422
D (65496) nvs: nvs_open_from_partition CHIP_KVS 0
D (65496) nvs: nvs_get_str_or_blob g/su/9
D (65506) nvs: nvs_close 423
D (65506) nvs: nvs_open_from_partition CHIP_KVS 0
D (65516) nvs: nvs_get_str_or_blob g/su/a
D (65516) nvs: nvs_close 424
D (65516) nvs: nvs_open_from_partition CHIP_KVS 0
D (65526) nvs: nvs_get_str_or_blob g/su/b
D (65526) nvs: nvs_close 425
D (65526) nvs: nvs_open_from_partition CHIP_KVS 0
D (65536) nvs: nvs_get_str_or_blob g/su/c
D (65536) nvs: nvs_close 426
D (65546) nvs: nvs_open_from_partition CHIP_KVS 0
D (65546) nvs: nvs_get_str_or_blob g/su/d
D (65556) nvs: nvs_close 427
D (65556) nvs: nvs_open_from_partition CHIP_KVS 0
D (65556) nvs: nvs_get_str_or_blob g/su/e
D (65566) nvs: nvs_close 428
D (65566) chip[DMG]: All ReadHandler-s are clean, clear GlobalDirtySet
I (65576) chip[EM]: >>> [E:30272r S:55454 M:225728017 (Ack:190411354)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
D (65586) chip[EM]: Found matching exchange: 30272r, Delegate: 0x0
D (65596) chip[EM]: Rxd Ack; Removing MessageCounter:190411354 from Retrans Table on exchange 30272r
I (65606) chip[EM]: >>> [E:30273r S:55454 M:225728018] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
D (65616) chip[EM]: Handling via exchange: 30273r, Delegate: 0x3fca5054
D (65626) chip[IM]: Received Read request
D (65626) chip[DMG]: ReadRequestMessage =
D (65626) chip[DMG]: {
D (65636) chip[DMG]:    AttributePathIBs =
D (65636) chip[DMG]:    [
D (65636) chip[DMG]:            AttributePathIB =
D (65646) chip[DMG]:            {
D (65646) chip[DMG]:                    Endpoint = 0x0,
D (65646) chip[DMG]:                    Cluster = 0x28,
D (65656) chip[DMG]:                    Attribute = 0x0000_0003,
D (65656) chip[DMG]:            }
D (65666) chip[DMG]:
D (65666) chip[DMG]:    ],
D (65666) chip[DMG]:
D (65666) chip[DMG]:    isFabricFiltered = true,
D (65676) chip[DMG]:    InteractionModelRevision = 11
D (65676) chip[DMG]: },
D (65686) chip[DMG]: IM RH moving to [CanStartReporting]
D (65686) chip[DMG]: Building Reports for ReadHandler with LastReportGeneration = 0x0000000000000000 DirtyGeneration = 0x0000000000000000
D (65696) chip[DMG]: <RE:Run> Cluster 28, Attribute 3 is dirty
D (65706) chip[DMG]: Reading attribute: Cluster=0x0000_0028 Endpoint=0 AttributeId=0x0000_0003 (expanded=0)
D (65716) nvs: nvs_open_from_partition chip-factory 0
D (65716) nvs: nvs_get_str_or_blob product-name
D (65726) nvs: nvs_close 429
E (65726) chip[DMG]: Error retrieving data from clusterId: 0x0000_0028, err = 201
D (65736) chip[DMG]: <RE> Sending report (payload has 33 bytes)...
I (65746) chip[EM]: <<< [E:30273r S:55454 M:190411355 (Ack:225728018)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:59913] --- Type 0001:05 (IM:ReportData)
D (65756) chip[DMG]: <RE> OnReportConfirm: NumReports = 0
D (65766) chip[DMG]: <RE> ReportsInFlight = 0 with readHandler 0, RE has no more messages
D (65776) chip[DMG]: IM RH moving to [AwaitingDestruction]
D (65776) nvs: nvs_open_from_partition CHIP_KVS 0
D (65786) nvs: nvs_get_str_or_blob g/su/0
D (65786) nvs: nvs_close 430
D (65786) nvs: nvs_open_from_partition CHIP_KVS 0
D (65796) nvs: nvs_get_str_or_blob g/su/1
D (65796) nvs: nvs_close 431
D (65806) nvs: nvs_open_from_partition CHIP_KVS 0
D (65806) nvs: nvs_get_str_or_blob g/su/2
D (65806) nvs: nvs_close 432
D (65816) nvs: nvs_open_from_partition CHIP_KVS 0
D (65816) nvs: nvs_get_str_or_blob g/su/3
D (65826) nvs: nvs_close 433
D (65826) nvs: nvs_open_from_partition CHIP_KVS 0
D (65826) nvs: nvs_get_str_or_blob g/su/4
D (65836) nvs: nvs_close 434
D (65836) nvs: nvs_open_from_partition CHIP_KVS 0
D (65846) nvs: nvs_get_str_or_blob g/su/5
D (65846) nvs: nvs_close 435
D (65846) nvs: nvs_open_from_partition CHIP_KVS 0
D (65856) nvs: nvs_get_str_or_blob g/su/6
D (65856) nvs: nvs_close 436
D (65856) nvs: nvs_open_from_partition CHIP_KVS 0
D (65866) nvs: nvs_get_str_or_blob g/su/7
D (65866) nvs: nvs_close 437
D (65876) nvs: nvs_open_from_partition CHIP_KVS 0
D (65876) nvs: nvs_get_str_or_blob g/su/8
D (65886) nvs: nvs_close 438
D (65886) nvs: nvs_open_from_partition CHIP_KVS 0
D (65886) nvs: nvs_get_str_or_blob g/su/9
D (65896) nvs: nvs_close 439
D (65896) nvs: nvs_open_from_partition CHIP_KVS 0
D (65896) nvs: nvs_get_str_or_blob g/su/a
D (65906) nvs: nvs_close 440
D (65906) nvs: nvs_open_from_partition CHIP_KVS 0
D (65916) nvs: nvs_get_str_or_blob g/su/b
D (65916) nvs: nvs_close 441
D (65916) nvs: nvs_open_from_partition CHIP_KVS 0
D (65926) nvs: nvs_get_str_or_blob g/su/c
D (65926) nvs: nvs_close 442
D (65936) nvs: nvs_open_from_partition CHIP_KVS 0
D (65936) nvs: nvs_get_str_or_blob g/su/d
D (65936) nvs: nvs_close 443
D (65946) nvs: nvs_open_from_partition CHIP_KVS 0
D (65946) nvs: nvs_get_str_or_blob g/su/e
D (65956) nvs: nvs_close 444
D (65956) chip[DMG]: All ReadHandler-s are clean, clear GlobalDirtySet
D (65966) chip[IN]: Received a duplicate message with MessageCounter:225728018 on exchange 30273r
I (65966) chip[EM]: >>> [E:30273r S:55454 M:225728018] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
D (65986) chip[EM]: Found matching exchange: 30273r, Delegate: 0x0
D (65986) chip[EM]: Forcing tx of solitary ack for duplicate MessageCounter:225728018 on exchange 30273r
I (65996) chip[EM]: <<< [E:30273r S:55454 M:190411356 (Ack:225728018)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [UDP:[FE80::A2:2C39:3B2C:AD67%st1]:59913] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (66016) chip[EM]: >>> [E:30273r S:55454 M:225728019 (Ack:190411355)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
D (66036) chip[EM]: Found matching exchange: 30273r, Delegate: 0x0
D (66036) chip[EM]: Rxd Ack; Removing MessageCounter:190411355 from Retrans Table on exchange 30273r
D (74896) wifi:obss scan is disabled
D (74896) wifi:start obss scan: obss scan is stopped
E (82256) chip[SWU]: No suitable OTA Provider candidate found
I (82256) chip[SWU]: No provider available

Nobody who can help me here?

You could check your partition. Your error shows it was trying to get the product name from the nvs partition chip-factory.
Check if there is a valid name there?
D (63666) nvs: nvs_open_from_partition chip-factory 0
D (63676) nvs: nvs_get_str_or_blob product-name
D (63676) nvs: nvs_close 381
E (63676) chip[DMG]: Error retrieving data from clusterId: 0x0000_0028, err = 201

I do know generic_switch example has some factory data you need to flash before running your application. See generic_switch

@FloBer431 Are you still facing the issue?

Closing this now. Please re-open if you still see this issue


Updated Section: Security - Source Generated Access Control Lists

Current docs did not reflect the state of the code. This change will bring it back in line with where the Permissions setting is.

good catch and appreciate the fix 🙏


Support external source dependencies

Can Gradle fetch and link library from external repository for c++ (e.g. github)?
As in Cargo (Rust), go, nodejs and etc?
Example:
gem "nokogiri", :git => "git://github.com/tenderlove/nokogiri.git", :branch => "1.4"

Is this something Gradle would consider supporting in the future (or does it already)?

dependencies {
compile git: "git://github.com/someproject/someproject.git", branch: "1.4"
}

Good timing. We're actively working on implementing a feature like this in Gradle. No promises on the exact delivery timeframe, but I expect it will make it into one of the next few minor versions of gradle.

Great. What should I look for? Is there name of feature or version?

We're probably calling it Source Dependencies or External Source Dependencies
The work is being tracked in this epic on the gradle-native board, but we haven't got all the work chopped up and added to that epic yet.  That issue is best viewed with the ZenHub browser extension installed.

Duplicate of gradle/gradle-native#42


fix server-client interaction broken since <IP_ADDRESS>

v<IP_ADDRESS> (#221) broke the communication between old (before <IP_ADDRESS>) versions of poseidon-http-server and new versions of trident. This was foreseeable, yet unforeseen
This PR is meant to fix this incompatibility by reverting some of the JSON encoding/decoding related changes. This is not entirely trivial, because we do need a working JSON scheme for CsvNamedRecord (which did not exist in the past). To make sure that everything works, we need to consider the following cases:

[x] 1. Old server + New client
[x] 2. New server + Old client
[x] 3. New server + New client

I ran some quick tests on the command line with a local server, and old and new client versions.
# v<IP_ADDRESS> client + old (?) server
trident list --remote --packages | --groups | --individuals  -j Nr_SNPs

#  v<IP_ADDRESS> client +  v<IP_ADDRESS> server
poseidon-http-server -d 2010_RasmussenNature -c -z testDir
trident list --remote --remoteURL "http://<IP_ADDRESS>:3000" --packages | --groups | --individuals -j Nr_SNPs

#  v<IP_ADDRESS> client + v<IP_ADDRESS> server
wget https://github.com/poseidon-framework/poseidon-hs/releases/latest/download/trident-Linux
chmod +x trident-Linux
./trident-Linux list --remote --remoteURL "http://<IP_ADDRESS>:3000" --packages | --groups | --individuals -j Nr_SNPs

Works for all combinations.

Codecov Report
Base: 68.59% // Head: 71.80% // Increases project coverage by +3.21% :tada:

Coverage data is based on head (8404f18) compared to base (500b9e6).
Patch coverage: 64.28% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #228      +/-   ##
==========================================
+ Coverage   68.59%   71.80%   +3.21%
==========================================
  Files          18       18
  Lines        2283     2270      -13
  Branches      258      246      -12
==========================================
+ Hits         1566     1630      +64
+ Misses        459      394      -65
+ Partials      258      246      -12

Impacted Files
Coverage Δ

src/Poseidon/Janno.hs
83.12% <64.28%> (+3.09%)
:arrow_up:

src/Poseidon/CLI/List.hs
87.90% <0.00%> (+45.96%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

OK - I'm merging this now. Further testing of this very change will happen in #226. I'm taking the full responsibility!


Remap two keys (like y and z) for any modifier key

I want to switch y and z key entirely for any modifier key (no mod, shift, cmd, .... etc.)
It would be cool to have some sort of special modifier shortcut/code which describes that I want to map two keys regardless of the modifier key pressed.
(It's first time I use khd and recognized that undo/redo needed to be mapped again for z and y).
Thanks for khd!

Khd wasn't really built with key-remapping in mind, but as a simple way to launch some script upon a keypress.
Currently, what you want is not possible to do, however there have been other requests regarding ability to remap modifiers and such (Reference: #21).
The ability to perform key-remap might be added in the future.

I've decided this is out of scope for Khd, see #50


On clicking an option it scrolls to pin the widget on top of the page.

Hi, First of all, thank you for this amazing widget.
The problem I am facing is when I click any of the options in the widget it scrolls the page such that the widget is pinned at the top of the screen.
Before clicking.

After clicking.

I will be looking forward to the solution.
Thanks

I am facing the same problem and can't seem to solve it. Any idea?

Can you provide a code example for that?

I saw this issue too. It's not that hard to fix. The problem is in this line
https://github.com/victoryhb/streamlit-option-menu/blob/master/streamlit_option_menu/frontend/src/MyComponent.vue#L20
                <a v-else href="#" class="nav-link" :class="{active: i == selectedIndex, 'nav-link-horizontal':isHorizontal}"

Change the above line to <a href="javascript:void(0);" above
href="#" jumps to the top of the page. There are also other ways to solve the issue

@sshivaji Yes, I figured it out, too.
I replaced href='#' with href='#dummy', because I didn't know any better. I guess your solution is cleaner.


Split optimize_1q_gates pass

The code in the optimize_1q_gates pass says:
                # TODO After we refactor, we should have separate passes for
                # exact and approximate rewriting.

I'm not really sure to which refactor the comments is refering too. @ajavadia any idea?
Probably is time to jump in...

The KAK that we did in the volume paper is what i think this is referring to.

No this is not KAK, it's just a single-qubit rotation merge. The comment is old and from Andrew. It says we should be allowed to remove small rotation angles. I think this is actually done now and can be closed (via #https://github.com/Qiskit/qiskit-terra/pull/1738).
It used to be that this would be optimized away:
qc.u1(sympy.pi, qr[1])
qc.u1(sympy.pi, qr[1])

But this would not:
qc.u1(np.pi, qr[1])
qc.u1(np.pi, qr[1])

Now both are.


new feature request

how is this possible to integrate this feature into this awesome library?

Hi, @jjhesk
I am sorry for the late answer.
Sorry, It does not implemented in this library.
Thank you for your idea.


Add Revert to last commit

What are the steps here other than the call to the repository - do we need to close the file first and then call update files. What if the file is in an active view? Would it work to do the repo call and then call RevertActiveView?

I'm pretty sure just doing the repo revert and then calling Revert on the specific filenode would work.  You can't count on it being the active view, right?  better to just operate directly on the textbuf for the relevant filenode.  the fact that the giv filenode has the textbuf is really key -- that is the only thing that matters -- any relevant load / revert / etc on the textbuf automatically updates the views so you should always be thinking in terms of those textbufs!  in this way, all the basic VCS stuff can all be managed by the filetree and gide can just refer / use the filetree impl of everything (and indeed it operates primarily on the filenodes anyway).

done

hmm, not working now

it is Checkout Git and it works


include helmfile alternative installation

This pr is in response to @JoshVanL in https://github.com/jetstack/cert-manager/pull/1935
NONE

/assign @JoshVanL

Looking good to me, just putting that into the code block
/approve
/ok-to-test
/assign @zakkg3

/unassign

/lgtm

/lgtm :)

/lgtm


Read in PSF products if load_products is True

On declaration of a source, XGA can hunt round for products it generated previously. I need to expand it to support PSFs, and eventually the deconvolved image files I will make.

This happens with this pull request.


NSwag ASP.Net Core middleware not generating models from interfaces

When a controller specifies its return type as an interface, NSwag generates an empty model for it. The following is an interface, IFixtureData:
public interface IFixtureData
{
    ushort Address { get; set; }
    FixtureDefinitionSkeleton Type { get; set; }
    FixtureOptions Options { get; set; }
    string Group { get; set; }
}

In the swagger.json file, the following is generated:
"IFixtureDefinition": {
  "type": "object",
  "x-abstract": true,
  "additionalProperties": false
}

All of my concrete classes are generated properly, but the interfaces are all like this.

Not sure if this feature is actually implemented by NJsonSchema... we use Newtonsoft.Json's ContractResolver to enumerate properties - I'd expect that interfaces are also supported by the resolver... but we need to verify this in http://njsonschema.org with a unit test

This seems to be a Problem with NJsonSchema. Getter and Setter methods are abstract in an Interface and these are not generated by default (see https://github.com/RSuter/NJsonSchema/blob/f7224a3ee33333b3cd439df536f80c5d551dcb21/src/NJsonSchema/Generation/JsonSchemaGenerator.cs#L598 ).
Everything works fine if I just set JsonSchemaGeneratorSettings.GenerateAbstractProperties to true, but this might not work in all situations.

NJsonSchema uses the Newtonsoft.Json contract resolver to enumerate properties and do "reflection" over DTOs: This is done to ensure that the schema and the serialized/deserialized data match... The option GenerateAbstractProperties overrides this behavior and manually uses reflection to add abstract/interface properties - but because it is not used often (also not recommended) it might come with some problems etc. but NJsonSchema would be the place to test and fix this issue...

Should I create a corresponding issue in NJsonSchema? I could probably help with writing the UnitTest and potential fix...

I’ll move this issue over to NJS, but it would be great if you create a (WIP) PR with some tests there...


Missing documentation about Security Rules - timestamp

How to reproduce these conditions
Sample name or URL where you found the bug
https://firebase.google.com/docs/reference/rules/rules.timestamp
Failing Function code used (including require/import commands at the top)
I tried to learn more about timestamps in security rules but the link is crashed.
Steps to set up and reproduce
Access the link at https://firebase.google.com/docs/reference/rules/rules.timestamp
Screenshots
Expected behavior
Documentation about it

Actual behavior
NOT FOUND 404

This is not a bug. In fact, I didn't know where to open a problem like that. Sorry if I was wrong to put it here.

Hi @geeksilva97, I'm going to close this since it isn't related to the functions-samples repo. For now, you can access that page directly with this link, but I've reported the problem to Firebase tech writers and we'll get it fixed soon.

Hi @geeksilva97, I'm going to close this since it isn't related to the functions-samples repo. For now, you can access that page directly with this link, but I've reported the problem to Firebase tech writers and we'll get it fixed soon.

Thanks @jhuleatt
I'm on Slack now too. Very thankful.


RDM-9182: Add exception handler for SQL errors

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/RDM-9182
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Unit test case added as per @sullivangareth comment 👍


[WFRP4e System] Blackpowder Fumble

Hi,
I think that the fumble in a black powder quality weapon is not well implemented. As an example:
If I miss a roll with a double that is pair, the fumble does not automatically "explode" the weapon as a result. All damage in that arm with the unit dice as SL and the weapon is destroyed.From: marbo#6878wfrp4e: 3.3.3wfrp4e-core: 1.2.0wfrp4e-rnhd: 1.3.0wfrp4e-starter-set: 1.3.0

Closing this as I received no reply, and this system already implements this

Closing this as I received no reply, and this system already implements this


Git tags missing

It would be awesome if you could add the missing git tags corresponding with the releases to this repo. That would make it much easier to see which commits are included in which releases. Thanks :)

@rickharrison any comments?

The commits are easily viewable in the commit log

@rickharrison I'm talking about git tags, not commit. Those that would show up at https://github.com/rickharrison/broccoli-asset-rev/tags


If the prediction bbox of faster_rcnn and yolov3 is in the same format?

If they are both in $(x_1, y_1, x_2, y_2)$ or yolov3 is in $(x_c, y_c, w, h)$?

All boxes output from models have the format of (x1, y1, x2, y2)


Attribute quotes are removed, causing XML Parsing Error: not well-formed

Describe the bug
A clear and concise description of what the bug is.
When the attribute contains no spaces, its quotes are automatically optimised (or at least I do not see a setting to disable this) which causes an XML Parsing error.

To Reproduce
Steps to reproduce the behaviour:

Use the following code:

// input: path to input file
// output: path to output file
const fs = require("fs").promises;
const {optimize} = require("svgo");
    fs.readFile(input, "utf8").then(data => {
        const result = optimize(data, {
            path: input,
            multipass: true,
            floatPrecision: 2,
            plugins: ["cleanupAttrs", "removeDoctype", "removeXMLProcInst", "removeComments", "removeMetadata", "removeTitle", "removeDesc", "removeUselessDefs", "removeEditorsNSData", "removeEmptyAttrs", "removeHiddenElems", "removeEmptyText", "removeEmptyContainers", "removeViewBox",]
        });
        fs.writeFile(output, result.data).then(() => resolve(1)).catch(reject);
    });
}

Open output file in a browser such as Mozilla
See error

Expected behavior
Attribute quotes shall not be removed
Desktop (please complete the following information):

SVGO Version: 2.8.0
NodeJs Version: 16.13.0
OS: Ubuntu 20.04 LTS

Hi, which svg do you use as input?

Hi, which svg do you use as input?

Here are samples for source and output SVGs
Source

Output

I just ran your code and all worked as expected. Please check again. Maybe something is missing in reproduction.

I just ran your code and all worked as expected. Please check again. Maybe something is missing in reproduction.

After more debugging, it seems like the output file is further passed to an HTML minifier (not because of svgo). By disabling the HTML minifier, the svgo output works correctly, therefore this is an issue that has to be resolved internally in our project.


Support to literal string

I'm writing shell scripts to be executed inside rhai and missing literal strings make it a bit harder when dealing with double quotes and etc.

What is the preferred syntax for literal strings?
For example, Rust has r#...#" xxxxx "#...#
Some languages have back-ticks, some have @" xxxx ",  some double-up "" and '' to be literals within strings.
Some have """ xxxx """ as multi-line literal strings.
Not difficult to implement, but the trick is to find a good syntax.

I have a version that I've put together with:

Normal strings: " ... "
Normal strings with continuation: " ... \                                                           ..."
Multi-line literal strings: \ ... ``

Looks perfect!

OK, pull from the latest master to check it out.

@patrickelectric you may also look at #121 which is an outstanding issue on string interpolation...

I just put my 2 cents there, I just tested the master branch here and the backstick is working like a charm for multstring literals, thanks!


When can support stream with dynalite?

Our test env most use dynalite,other use local dynamodb,but we want all use dynalite,so what time can support stream with dynalit. it is so cool!!!

Hi @jinghuaz – this is already being tracked in #66 – thanks!


Return more than ten documents with Aggs

Is there a way to return more than ten documents with aggs?
I execute the following for a 24 hour data set:
free_sys_mem_agg <- aggs('{
                           "my_buckets": {
                              "composite" : {
                                "sources" : [
                                  { "date": { "date_histogram" : { "field": "@timestamp", "interval": "1h" } } }
                                ]
                              }
                            }
                          }')

Then search Elasticsearch
elastic(ELASTIC_API, ELASTIC_INDEX_NAME) %search% free_sys_mem_agg

I get the following output:
   doc_count     key.date
1     334559 1.525219e+12
2     333900 1.525223e+12
3     334150 1.525226e+12
4     333399 1.525230e+12
5     332119 1.525234e+12
6     332116 1.525237e+12
7     332100 1.525241e+12
8     332382 1.525244e+12
9     333518 1.525248e+12
10    332609 1.525252e+12

{
    "size": 0,
    "aggs": {
        "my_buckets": {
            "composite": {
                "sources": [
                    {
                        "date": {
                            "date_histogram": {
                                "field": "@timestamp",
                                "interval": "1h",
                                "order": "desc"
                            }
                        }
                    },
                    {
                        "server": {
                            "terms": {
                                "field": "beat.hostname.keyword"
                            }
                        }
                    }
                ]
            },
            "aggregations": {
                "the_max": {
                    "max": {
                        "field": "system.memory.free"
                    }
                }
            }
        }
    }
}

I think you might be missing a size field in the definition of your add - see here.

I figured it out...
date_hist <- aggs('{
    "docs_over_time" : {
            "date_histogram" : {
                "field" : "@timestamp",
                "interval" : "1s"
            }
        }
    }')

df <- elastic(ELASTIC_API, ELASTIC_INDEX_NAME) %search% (match_all_query + date_hist)

Returns 86,400 documents - as expected.
Nice work implementing scan/ scroll (I'm guessing) behind the scenes!  I expected it to time out!

Thanks!


get rid of the "verbosity" flag and replace it with a "v" flag

The "verbosity" flag in cip.go currently has no effect on what is logged by the promoter. Since we are already using the klog library to handle logging, we can just use klog's expected "v" flag to set the verbosity level.

fixed by pull request #221


Parallel on syntax

In the Brane syntax definition there is a parallel On syntax that is not fully worked out. I also cannot find something on it in the documenation. Is this a planned feature that was never documented, or is a bit of the spec missing?
https://github.com/epi-project/brane-documentation/blob/e52e52f1bdf1b8a01c741d01488f0ccf283b8e42/specification/src/appendix/languages/bscript/syntax.md?plain=1#L78

Ah! No it's a mix between legacy on-blocks and the new attributes which I've never added. Good catch. I'll whip up a PR for it in a moment.


Deprecate extra in favor of contexts

:scroll: Description
Deprecate extra in favor of contexts.
:bulb: Motivation and Context
https://docs.sentry.io/platforms/python/enriching-events/context/#additional-data
:green_heart: How did you test it?
:pencil: Checklist

[X] I reviewed submitted code
[ ] I added tests to verify changes
[X] No new PII added or SDK only sends newly added PII if sendDefaultPii is enabled
[X] I updated the docs if needed
[X] All tests passing
[X] No breaking changes

:crystal_ball: Next steps

Change the target branch to main since I've created it from the wrong branch.

Looks good. The PR is still a draft will you be adding something more?

I was just waiting CI/linting, but probably not.


scons on linux: cannot find -lgodot-cpp/bin/godot-cpp.linux.64

OS: Debian Buster
Steps to reproduce
$ cd godot-cpp
$ scons platform=linux headers=../godot_headers generate_bindings=yes
$ cd ..
$ scons platform=linux

Expected results
Builds without errors
Actual results
scons: Reading SConscript files ...
scons: done reading SConscript files.
scons: Building targets ...
g++ -o demo/bin/x11/libgdexample.so -shared src/gdexample.os src/gdlibrary.os -lgodot-cpp/bin/godot-cpp.linux.64
/usr/bin/ld: cannot find -lgodot-cpp/bin/godot-cpp.linux.64
collect2: error: ld returned 1 exit status
scons: *** [demo/bin/x11/libgdexample.so] Error 1
scons: building terminated because of errors.

Solution
Downloading the file referenced in the tutorial and replacing the one here allows the project to build without error. Perhaps this repo should be updated?

Hey @CosineP ,
Thanks! I don't use Linux myself so I had just copied the settings from another project. Another Godoter must have updated the tutorials with a fix. I'll find some time later in the week to compare the example project with the latest updates in the docs, there may be other changes :)

I had this same issue on OSX High Sierra. Using this file:
http://docs.godotengine.org/en/3.0/_downloads/SConstruct
instead of the one in your repo fixed the issue.

Does it work with the changes i committed last night?
On Fri, 3 Aug 2018 at 3:06 am, Cyborg Interactive, LLC <
<EMAIL_ADDRESS>wrote:

I had this same issue on OSX High Sierra. Using this file:
http://docs.godotengine.org/en/3.0/_downloads/SConstruct http://url
instead of the one in your repo fixed the issue.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/BastiaanOlij/gdnative_cpp_example/issues/1#issuecomment-409999138,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB2vaVabhzb1F3cStnseytBMrN0cP_iKks5uMzGKgaJpZM4VG3Tl
.

--
Kindest regards,
Bastiaan Olij
https://www.facebook.com/bastiaan.olij
https://twitter.com/mux213
https://www.youtube.com/channel/UCrbLJYzJjDf2p-vJC011lYw
https://github.com/BastiaanOlij

Ah hang on, sorry i’m on email so didn’t realise this is a different repo,
i fixed gdtest last night, i’ll update this one with the same fix soon!
On Fri, 3 Aug 2018 at 11:10 am, Bastiaan Olij<EMAIL_ADDRESS>wrote:

Does it work with the changes i committed last night?
On Fri, 3 Aug 2018 at 3:06 am, Cyborg Interactive, LLC <
<EMAIL_ADDRESS>wrote:

I had this same issue on OSX High Sierra. Using this file:
http://docs.godotengine.org/en/3.0/_downloads/SConstruct http://url
instead of the one in your repo fixed the issue.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/BastiaanOlij/gdnative_cpp_example/issues/1#issuecomment-409999138,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB2vaVabhzb1F3cStnseytBMrN0cP_iKks5uMzGKgaJpZM4VG3Tl
.

--
Kindest regards,
Bastiaan Olij
https://www.facebook.com/bastiaan.olij
https://twitter.com/mux213
https://www.youtube.com/channel/UCrbLJYzJjDf2p-vJC011lYw
https://github.com/BastiaanOlij

--
Kindest regards,
Bastiaan Olij
https://www.facebook.com/bastiaan.olij
https://twitter.com/mux213
https://www.youtube.com/channel/UCrbLJYzJjDf2p-vJC011lYw
https://github.com/BastiaanOlij

Works for me on Linux! Thanks!

After several attempts, i managed to write a procedure that works every time: https://gitlab.com/frankiezafe/gdnative_template/blob/master/README.md - i don't get why i have to clone godot_headers 2 times (once in godot-cpp and once in the root folder), but it works fine...
when i'm trying to use the godot_header in the root to compile godot-cpp, i get an error:
scons platform=linux headers_dir=../godot_headers generate_bindings=yes
outputs:

scons: Reading SConscript files ...
scons: done reading SConscript files.
scons: Building targets ...
g++ -o src/core/Array.o -c -fPIC -g -std=c++14 -Wwrite-strings -Og -m64 -I. -Igodot_headers -Iinclude -Iinclude/core src/core/Array.cpp
In file included from src/core/Array.cpp:1:0:
include/core/Array.hpp:4:28: fatal error: gdnative/array.h: No such file or directory
compilation terminated.
scons: *** [src/core/Array.o] Error 1
scons: building terminated because of errors.

Hi @frankiezafe,
This is the downside of working with something that is still so actively evolving. The Godot headers have moved into the godot-cpp folder so it is no longer needed to place them in the root of the project. Keep in mind that you clone with the recursive option and make sure you check out the correct branch. The above error sounds like your mixing up the master and 3.0 branches of the components.
Make sure you follow the instructing in the latest docs: http://docs.godotengine.org/en/latest/tutorials/plugins/gdnative/gdnative-cpp-example.html


possibility of adding more introductory code regarding file loaders?

Hi! 😄 thank you for creating this project! It's a great way to understand bundlers more.
File loaders are also a heavily used feature provided by different bundlers. Would you accept very introductory code regarding loaders? Basically we could create a different example folder showing how minipack would work with file loaders.
Here's a gist with a very basic css file loader example (along with the generated bundle.js):
https://gist.github.com/mayank23/6163214ce6b7562bd300b9a79ef5dde4. (still needs explanation comments)
If interested I could make a PR for this. I feel that having some introductory examples of heavily used bundler features would immensely help also.
Thank you!!

Hi 😃, not sure if you had a chance to see this yet?
Thanks!


feat: function call argument parser with newline and indentation

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y

Closes #1325

2. What is the scope of this PR (e.g. component or file name):

kclvm/parser/src/parser/expr.rs

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[x] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[x] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

kclvm/parser/src/tests/error_recovery.rs

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

33 of 39 (84.62%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.005%) to 71.066%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

kclvm/parser/src/parser/expr.rs
33
39
84.62%

Totals

Change from base Build<PHONE_NUMBER>:
0.005%

Covered Lines:
53684

Relevant Lines:
75541

💛  - Coveralls


Document screen effects and add to demo

Codecov Report

Merging #304 (1cd30b3) into master (0bc80d3) will decrease coverage by 0.09%.
The diff coverage is 0.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##           master     #304      +/-   ##
==========================================
- Coverage   96.54%   96.46%   -0.09%
==========================================
  Files         178      178
  Lines        4403     4407       +4
==========================================
  Hits         4251     4251
- Misses        152      156       +4

Files
Coverage Δ

impl/jamtemplate/common/random/random.cpp
90.90% <0.00%> (-9.10%)
:arrow_down:

:mega: Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today!


How high level should node-gtk3 be?

Currently, node-gtk3 is being implemented at a pretty high level. If you look at the current demo, the window is automatically being created and attached to the application. Is this too high level? I want it to be easy to use, but don't want to sacrifice flexibility.
const app = new App({
  title: 'Node Gtk3',
  height: 200,
  width: 200
});
app.run();

@nuxlli @harisvsulaiman @emilioastarita @Place1

I agree that the level is high.
But as generic as this lib may be, perhaps its api must guide primarily to the use that https://github.com/jamrizzi/react-gtk will make of it.

For example, I am really impressed with this api and how it can facilitate the creation of a "react-yue": http://libyue.com/docs/v0.1.1/js/

It's definitely cool. There's already a React Electron. The reason I'm working on React GTK is to create a native React experience for desktop applications. Electron is not native. It's essentially Cordova for desktop.

Yes I agree.
I found this project just looking for alternatives to this approach. In my searches:

qt: The variety of widgets and helpers is excellent. But licensing has become a problem.

efl: Just as yue is simple and light, making it easier to install in different systems. But also a little obscure and little used.

gtk+: Before release of gtk+3, it depended on the X11 subsystem, which made its application unattractive on macOS. But now it is more elegant, even if its installation is too complex.

Getting gtk to work on windows is a little hairy, but it's definitely doable. I successfully got gtk to work on windows in the following repo. I'll definitely use a similar approach when I try and get this to work on windows.
https://github.com/jamrizzi/windows-pygtk
I'm doing all my desktop development with python gtk until I finish this project.

@jamrizzi @nuxlli I took a different approach here https://github.com/harisvsulaiman/Pushy , instead of building the ui in gjs (or something similar), I used dbus as message passing system to build a hybrid app.
This has both a node js process ( with the business logic ) and native process ( UI stuff ).
This allows me to use this app wherever dbus is available.

I'm really excited around all the GTK node bindings so I can potentially hack on a gtk react native.

I know this issue is closed, but how about trying to closely follow GJS's GTK bindings?

@jamrizzi @Place1 @nuxlli Build something that emits Gjs?

That's a really great idea. I'll make a note on the readme that this project will follow GJS bindings.

ba3a5d4910bcb79a11bc3fca176233a8acdf41a2


Add --allow_urls option to audio-yamaha-opx applet

The audio-yamaha-opx applet potentially allows remote users to make GET requests to arbitrary URLs. This may have security implications (e.g., accessing internal IP addresses, or accessing prohibited URLs). This patch disables this feature by default, but allows users to opt back in by passing the --allow_urls flag to the audio-yamaha-opx applet.

Could you squash please?


[DRAFT] feat: support triggers

This is an initial draft to support the creation of triggers. Please let me know what you think.

Thanks for the contribution Julias. As with the function support I need some days to thinks about the API, play with it and change the implementation. But it will definetely be integrated in some form.

Great, thanks 😊  The idea was to make it as simple as possible: either use a function which already exists or implicitly create a function and use that.

Looks very promising, thanks!


Support for Ubuntu 18.04

hello , i am very grateful your work. when i run demo using pixi, i guess the version of pixi and ubuntu18.04 is conflict. when ubuntu18.04 cuda 11.3,what is the version of pixi,can this code work in my computer environment？i am very appreciative for your soon response.

Ubuntu 18.04 has reached its end of life, I would recommend to update to a more recent version.
Otherwise, maybe start with this and see if that gets you any further: https://github.com/prefix-dev/pixi/issues/346#issuecomment-2110364229

@roym899 I reinstalled Ubuntu from 18.04 to 20.04 just for this, and this has not solved issue at all... Actually, the error message is absolutely the same after upgrade.

Sorry to hear that. Have you tried to add the system-requirement as in the link above?


Error : Cannot read property 'trim' of undefined

Line 16 of convert-excel-to-json.js :
Need to remplace :
 return (sheetCell.t === 'n' || sheetCell.t === 'd') ? sheetCell.v : (sheetCell.w.trim && sheetCell.w.trim()) || sheetCell.w;
By :
 return (sheetCell.t === 'n' || sheetCell.t === 'd') ? sheetCell.v : (sheetCell.w && sheetCell.w.trim()) || sheetCell.w;
it's work perfectly with this correction.

Thanks! Can you post here the case where you faced a problem because of
that?
On Thu, Sep 20, 2018, 5:48 AM bikernumber13<EMAIL_ADDRESS>wrote:

Line 16 of convert-excel-to-json.js :
Need to remplace :
return (sheetCell.t === 'n' || sheetCell.t === 'd') ? sheetCell.v :
(sheetCell.w.trim && sheetCell.w.trim()) || sheetCell.w;
By :
return (sheetCell.t === 'n' || sheetCell.t === 'd') ? sheetCell.v :
(sheetCell.w && sheetCell.w.trim()) || sheetCell.w;
it's work perfectly with this correction.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/DiegoZoracKy/convert-excel-to-json/issues/17, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AB_oP-cfQDIDz13hBzCT0MfOqIFEjlxFks5uc1ZSgaJpZM4WxqK6
.

This problem appeared when I wanted to convert an excel file to json.
This excel file has empty lines. For example, the first 3 of my file were
empty. I think it's because of them.
2018-09-20 13:39 GMT+02:00 Diego ZoracKy<EMAIL_ADDRESS>
Thanks! Can you post here the case where you faced a problem because of
that?
On Thu, Sep 20, 2018, 5:48 AM bikernumber13<EMAIL_ADDRESS>wrote:

Line 16 of convert-excel-to-json.js :
Need to remplace :
return (sheetCell.t === 'n' || sheetCell.t === 'd') ? sheetCell.v :
(sheetCell.w.trim && sheetCell.w.trim()) || sheetCell.w;
By :
return (sheetCell.t === 'n' || sheetCell.t === 'd') ? sheetCell.v :
(sheetCell.w && sheetCell.w.trim()) || sheetCell.w;
it's work perfectly with this correction.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/DiegoZoracKy/convert-excel-to-json/issues/17, or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/AB_oP-
cfQDIDz13hBzCT0MfOqIFEjlxFks5uc1ZSgaJpZM4WxqK6>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/DiegoZoracKy/convert-excel-to-json/issues/17#issuecomment-423151557,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AM9Z22I0potp7bes-xpYEMC8vCVITXCrks5uc35ggaJpZM4WxqK6
.

--
Cordialement,
M. Michael BOUHIER
Student at 42
Fullstack Web Developper
Software Engineer
Red Coat Devoxx France since 2016
Tel : +33 6 17 67 77 45
Mail : m http://read.html/?FOLDER=SF_OUTBOX&IDMSG=818&check=&SORTBY=1
<EMAIL_ADDRESS>

Thanks! I'll try to adjust it before the end of this week. But feel free to
send a PR, if you want.
On Thu, Sep 20, 2018, 8:44 AM bikernumber13<EMAIL_ADDRESS>wrote:

This problem appeared when I wanted to convert an excel file to json.
This excel file has empty lines. For example, the first 3 of my file were
empty. I think it's because of them.
2018-09-20 13:39 GMT+02:00 Diego ZoracKy<EMAIL_ADDRESS>
Thanks! Can you post here the case where you faced a problem because of
that?
On Thu, Sep 20, 2018, 5:48 AM bikernumber13<EMAIL_ADDRESS>wrote:

Line 16 of convert-excel-to-json.js :
Need to remplace :
return (sheetCell.t === 'n' || sheetCell.t === 'd') ? sheetCell.v :
(sheetCell.w.trim && sheetCell.w.trim()) || sheetCell.w;
By :
return (sheetCell.t === 'n' || sheetCell.t === 'd') ? sheetCell.v :
(sheetCell.w && sheetCell.w.trim()) || sheetCell.w;
it's work perfectly with this correction.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/DiegoZoracKy/convert-excel-to-json/issues/17, or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/AB_oP-
cfQDIDz13hBzCT0MfOqIFEjlxFks5uc1ZSgaJpZM4WxqK6>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/DiegoZoracKy/convert-excel-to-json/issues/17#issuecomment-423151557
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AM9Z22I0potp7bes-xpYEMC8vCVITXCrks5uc35ggaJpZM4WxqK6
.

--
Cordialement,
M. Michael BOUHIER
Student at 42
Fullstack Web Developper
Software Engineer
Red Coat Devoxx France since 2016
Tel : +33 6 17 67 77 45
Mail : m http://read.html/?FOLDER=SF_OUTBOX&IDMSG=818&check=&SORTBY=1
<EMAIL_ADDRESS>—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/DiegoZoracKy/convert-excel-to-json/issues/17#issuecomment-423152758,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB_oP_DqTfaO0GSseWVGpGpCa4ygeOiWks5uc3-CgaJpZM4WxqK6
.


Backport: HBASE-24705 MetaFixer#fixHoles() does not include the case for read r…

…eplicas (i.e, replica regions are not created) (#2062)
Signed-off-by: Viraj Jasani<EMAIL_ADDRESS>

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 47s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2.3 Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 38s
branch-2.3 passed

+1 :green_heart:
checkstyle
1m 45s
branch-2.3 passed

+1 :green_heart:
spotbugs
3m  4s
branch-2.3 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 16s
the patch passed

-0 :warning:
checkstyle
1m  7s
hbase-server: The patch generated 5 new + 228 unchanged - 0 fixed = 233 total (was 228)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
19m 14s
Patch does not cause any errors with Hadoop 2.10.0 or 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
4m 26s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 30s
The patch does not generate ASF License warnings.

48m 46s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2067/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2067

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 1f5af5035df5 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.3 / 15c8c2f59c

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2067/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

Max. process+thread count
94 (vs. ulimit of 12500)

modules
C: hbase-client hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2067/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 29s
Docker mode activated.

-0 :warning:
yetus
0m  7s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.3 Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 11s
branch-2.3 passed

+1 :green_heart:
compile
1m 33s
branch-2.3 passed

+1 :green_heart:
shadedjars
5m 44s
branch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 30s
hbase-client in branch-2.3 failed.

-0 :warning:
javadoc
0m 38s
hbase-server in branch-2.3 failed.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 21s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 53s
the patch passed

+1 :green_heart:
compile
1m 35s
the patch passed

+1 :green_heart:
javac
1m 35s
the patch passed

+1 :green_heart:
shadedjars
5m 47s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 28s
hbase-client in the patch failed.

-0 :warning:
javadoc
0m 40s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
2m 30s
hbase-client in the patch passed.

+1 :green_heart:
unit
125m 54s
hbase-server in the patch passed.

157m 52s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2067/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2067

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 28fc80aef15f 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.3 / 15c8c2f59c

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2067/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-client.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2067/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2067/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-client.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2067/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2067/1/testReport/

Max. process+thread count
3939 (vs. ulimit of 12500)

modules
C: hbase-client hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2067/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 47s
Docker mode activated.

-0 :warning:
yetus
0m  7s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.3 Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 39s
branch-2.3 passed

+1 :green_heart:
compile
1m 25s
branch-2.3 passed

+1 :green_heart:
shadedjars
5m 15s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 59s
branch-2.3 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 19s
the patch passed

+1 :green_heart:
compile
1m 23s
the patch passed

+1 :green_heart:
javac
1m 23s
the patch passed

+1 :green_heart:
shadedjars
5m  6s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  0s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
2m 10s
hbase-client in the patch passed.

+1 :green_heart:
unit
139m 53s
hbase-server in the patch passed.

168m 48s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2067/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2067

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 06d24e447551 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.3 / 15c8c2f59c

Default Java
1.8.0_232

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2067/1/testReport/

Max. process+thread count
3918 (vs. ulimit of 12500)

modules
C: hbase-client hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2067/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


 Appears to be caused at the createParser level which throws out error chunks. This is my quick and dirty fix that just decodes and checks chunks before feeding them to createParser.

Thank you, beautiful soul!


set default sum in pivot

How to set default sum in pivot ...?

See example here http://nicolas.kruchten.com/pivottable/examples/simple_agg.html

If we're using the aggregatorName property, is there a way to set the default value of the pvtAttrDropdown?

@jwhitmarsh that's what the aggregatorName property does...


Print formatted result on verbose output

As I suggested on a commit

Thank you for your contribution. Instead of overloading the meaning of --verbose, what do you think of the following option:
We change the --size-format option to take four (instead of two) parameters:

decimal
binary
plain
auto

By default, the format is set to auto which automatically chooses either decimal (if we write to a TTY) or plain (if we don't). This way, users can still overwrite the auto format by explicitly choosing decimal, binary, or plain.

This is currently above my knowledge of Rust :stuck_out_tongue_closed_eyes:

Ok, no worries. I'll take a look at this when I find the time.


[Docs] Navigator example should be more complete

It should have multiple scenes, often this is the first place people will look to and this isn't so clear

:+1:

:+1:

I would also suggest mentioning nesting a Navigator inside another Navigator, which is a fairly common use case in iOS.

Where's the example for Navigator? I can only find examples for NavigatorIOS?
It's also helpful to include an example showing how to use Navigator.navigationBar in Modal, like those Apple uses when setting up VPN and Medical ID.

:+1:

I would be nice to have an example like this https://github.com/facebook/react-native/issues/2576.

I would also suggest mentioning nesting a Navigator inside another Navigator, which is a fairly common use case in iOS.
+1

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/docs-navigator-example-should-be-more-complete
ProductPains helps the community prioritize the most important issues thanks to its voting feature.
It is easy to use - just login with GitHub.
Also, if this issue is a bug, please consider sending a PR with a fix.
We're a small team and rely on the community for bug fixes of issues that don't affect fb apps.


Droping domain from URL

Overview
This is to address #113. I don't think there is a need for the domain to exist in the database. You can  link to things without the domain. Also, it allows for other developers  to use this database to make their own APIs.

Seems good to me.


feat: hardened images

Adds hardening bits and pieces for our suite of images.

I've checked out all the python based images and they all work fine.  Looking at https://github.com/cfpb/sbl-frontend/pull/530 it seems the node and nginx images are also good (though that PR needs a main merge).  So I think this should be good to merge once that frontend PR is merged in?


[docs]: fix article "Remove a Self Hosted Server"

Description
Article Remove a Self Hosted Server needs to be updated, more details @ #855
Issue List

[ ] Guide the user to click Resource Name

Steps below needs to be fixed accordingly

1. In the list of servers, find the server you want to remove and click DETAILS

@thlmenezes can you assign this to me?


network: plug in dBFT library

Waiting for #420, #502 .
TODO:

[x] merge #420
[x] move dbft lib to the github

https://api.bitbucket.org/2.0/repositories/nspcc-dev/dbft?fields=scm
Access denied. You must have write or admin access.
=(

@volekerb I am planning to make it public in 1-2 days, after review from @roman-khimov and @realloc

@volekerb I am planning to make it public in 1-2 days, after review from @roman-khimov and @realloc

I see. Just wanted to test #508 heh.

Looks like it's time to merge! @roman-khimov  =)

Oh, and BTW, do you really need a queue in the relayCache now?


feat: replace minimatch with micromatch

I previously detailed the benefits of micromatch in https://github.com/hexojs/hexo/pull/3538
TL;DR micromatch is more active and support more globbing patterns.

No objections from my side. Will test later soon. Do you mind updating README as well? It still links to minimatch:

A minimatch pattern. All matching assets will use the assigned size rules.

Updated readme.
btw, I just noticed the readme includes squares/*.jpg pattern. This pattern doesn't work with micromatch nor minimatch.
const micromatch = require('micromatch')
console.log(micromatch.isMatch('/jack/hey/foo/bar.img', 'foo/*.img'))
// false

const minimatch = require('minimatch')
console.log(minimatch('/jack/hey/foo/bar.img', 'foo/*.img'))
// false

@curbengh case of '/jack/hey/foo/bar.imgis not a big deal since the filter is applied to URLs, not file system path.
Thanks for the contribution, it works nicely on my machine!

Released as 1.4.3

case of /jack/hey/foo/bar.imgis not a big deal since the filter is applied to URLs, not file system path.

But it doesn't match http://example.com/baz/foo/baz.img too.
console.log(micromatch.isMatch('http://example.com/baz/foo/baz.img', 'foo/*.img'))
// false

console.log(micromatch.isMatch('http://example.com/baz/foo/baz.img', '**/foo/*.img'))
// true

I'm not very familiar with this plugin, perhaps I missed something?

My point is that if the images are hosted under foo folder like http://example.com/foo/baz.img
then this is totally correct configuration
foo/*.img

because what will happen in this plugin is that
console.log(micromatch.isMatch('foo/baz.img', 'foo/*.img'))

If you need nested lookup to match baz/foo/avatar.img then you need something like **/foo/*.img indeed.