examples/light   chip tool Configuration failed

chip： esp32c3
sdk :    commitid 669070a3d2f9d8cf3dd08cafe8a82ee316a4cf90
LOG：
[2022-11-03 12:21:13.335]# RECV ASCII>
ESP-ROM:esp32c3-api1-20210207
Build:Feb  7 2021
rst:0x1 (POWERON),boot:0xd (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fcd6100,len:0x16bc
load:0x403ce000,len:0x930
load:0x403d0000,len:0x2d28
entry 0x403ce000
I (30) boot: ESP-IDF v4.4.2-dirty 2nd stage bootloader
I (30) boot: compile time 18:46:54
I (30) boot: chip revision: 3
I (32) boot.esp32c3: SPI Speed      : 80MHz
I (37) boot.esp32c3: SPI Mode       : DIO
I (
[2022-11-03 12:21:13.336]# RECV ASCII>
42) boot.esp32c3: SPI Flash Size : 4MB
I (47) boot: Enabling RNG early entropy source...
I (52) boot: Partition Table:
I (56) boot: ## Label            Usage          Type ST Offset   Length
I (63) boot:  0 sec_cert         unknown          3f 06 0000d000 00003000
I (70) boot:  1 nvs              WiFi data        01 02 00010000 00006000
I (78) boot:  2 otadata          OTA data         01 00 00016000 00002000
I (85) boot:  3
[2022-11-03 12:21:13.342]# RECV ASCII>
phy_init         RF data          01 01 00018000 00001000
I (93) boot:  4 ota_0            OTA app          00 10 00020000 001e0000
I (100) boot:  5 ota_1            OTA app          00 11 00200000 001e0000
I (108) boot:  6 fctry            WiFi data        01 02 003e0000 00006000
I (115) boot: End of partition table
I (120) boot: No factory image, trying OTA 0
I (125) esp_image: segment 0: paddr=00020020 vaddr=3c100020 size=2eee0h (19
[2022-11-03 12:21:13.343]# RECV ASCII>
2224) map
I (163) esp_image: segment 1: paddr=0004ef08 vaddr=3fc90400 size=01110h (  4368) load
I (164) esp_image: segment 2: paddr=00050020 vaddr=42000020 size=f4de4h (1002980) map
[2022-11-03 12:21:13.377]# RECV ASCII>
I (326) esp_image: segment 3: paddr=00144e0c vaddr=3fc91510 size=02590h (  9616) load
I (328) esp_image: segment 4: paddr=001473a4 vaddr=40380000 size=1033ch ( 66364) load
I (343) esp_image: segment 5: paddr=001576e8 vaddr=50000010 size=00010h (    16) load
I (349) boot: Loaded app from partition at offset 0x20000
[2022-11-03 12:21:13.433]# RECV ASCII>
I (410) boot: Set actual ota_seq=1 in otadata[0]
I (410) boot: Disabling RNG early entropy source...
I (421) cpu_start: Pro cpu up.
I (429) cpu_start: Pro cpu start user code
I (429) cpu_start: cpu freq: 160000000
I (429) cpu_start: Application information:
I (432) cpu_start: Project name:     light
I (437) cpu_start: App version:      v1.0
I (442) cpu_start: Compile time:     Oct 28 2022 18:46:47
[0
[2022-11-03 12:21:13.478]# RECV ASCII>
;32mI (448) cpu_start: ELF file SHA256:  a19d7d05878f65b8...
I (454) cpu_start: ESP-IDF:          v4.4.2-dirty
I (459) heap_init: Initializing.  Not creating again.
I (552) pp: pp rom version: 9387209
I (552) net80211: net80211 rom version: 9387209
I (572) wifi:wifi driver task: 3fcb03fc, prio:23, stack:6656, core=0
I (572) system_api: Base MAC address is not set
I (572) system_api: read default base MAC address from EFUSE
I (582) wifi:wifi firmware version: eeaa27d
I (582) wifi:wifi certification version:
[2022-11-03 12:21:13.939]# RECV ASCII>
v7.0
I (582) wifi:config NVS flash: enabled
I (592) wifi:config nano formating: disabled
I (592) wifi:Init data frame dynamic rx buffer num: 32
I (592) wifi:Init management frame dynamic rx buffer num: 32
I (602) wifi:Init management short buffer num: 32
I (602) wifi:Init dynamic tx buffer num: 32
I (612) wifi:Init static tx FG buffer num: 2
I (612) wifi:Init static rx buffer size: 1600
I (622) wifi:Init static rx buffer num: 10
I (622) wifi:Init dynamic rx buffer num: 32
I (622) wifi_init
[2022-11-03 12:21:13.940]# RECV ASCII>
: rx ba win: 6
I (632) wifi_init: tcpip mbox: 32
I (632) wifi_init: udp mbox: 6
I (642) wifi_init: tcp mbox: 6
I (642) wifi_init: tcp tx win: 5744
I (642) wifi_init: tcp rx win: 5744
I (652) wifi_init: tcp mss: 1440
I (652) wifi_init: WiFi IRAM OP enabled
I (662) wifi_init: WiFi RX IRAM OP enabled
I (672) chip[DL]: NVS set: chip-counters/reboot-count = 1 (0x1)
I (672) chip[DL]: NVS set: ch
[2022-11-03 12:21:13.942]# RECV ASCII>
ip-counters/total-hours = 0 (0x0)
I (682) chip[DL]: NVS set: chip-config/unique-id = "8ED08C822A2BBF4F"
I (682) chip[DL]: Real time clock set to 946684800 (0100/00/01 00:00:00 UTC)
W (692) BTDM_INIT: esp_bt_controller_mem_release not implemented, return OK
I (702) BTDM_INIT: BT controller compile version [05195c9]
I (702) phy_init: phy_version 912,d001756,Jun  2 2022,16:28:07
W (712) phy_init: failed to load RF calibration data (0x1102)
[2022-11-03 12:21:13.944]# RECV ASCII>
, falling back to full calibration
I (762) BTDM_INIT: Bluetooth MAC: 60:55:f9:77:b4:46

I (762) NimBLE: GAP procedure initiated: stop advertising.

I (772) CHIP[DL]: BLE host-controller synced
[2022-11-03 12:21:14.286]# RECV ASCII>
I (1272) chip[DL]: Configuring CHIPoBLE advertising (interval 25 ms, connectable)
I (1272) NimBLE: GAP procedure initiated: advertise;
I (1272) NimBLE: disc_mode=2
I (1272) NimBLE:  adv_channel_map=0 own_addr_type=1 adv_filter_policy=0 adv_itvl_min=40 adv_itvl_max=40
I (1282) NimBLE:

I (1292) chip[DL]: CHIPoBLE advertising started
E (1292) chip[DL]: Long dispatch time: 601 ms, for event type 2
I (1302) chip[DL]: S
[2022-11-03 12:21:14.331]# RECV ASCII>
tarting ESP WiFi layer
I (1312) wifi:mode : sta (60:55:f9:77:b4:44)
I (1312) wifi:enable tsf
W (1312) wifi:Haven't to connect to a suitable AP now!
I (1312) chip[DL]: Done driving station state, nothing else to do...
I (1322) phy: chan:1,max_power:80
I (1322) phy: chan:2,max_power:80
I (1332) phy: chan:3,max_power:80
I (1332) phy: chan:4,max_power:80
I (1342) phy: chan:5,max_power:80
I (1342) phy: chan:6,max_power:80
[2022-11-03 12:21:14.376]# RECV ASCII>
I (1342) phy: chan:7,max_power:80
I (1352) phy: chan:8,max_power:80
I (1352) phy: chan:9,max_power:80
I (1362) phy: chan:10,max_power:80
I (1362) phy: chan:11,max_power:80
I (1362) phy: chan:12,max_power:80
I (1372) phy: chan:13,max_power:80
I (1372) phy: chan:14,max_power:80
W (1382) wifi:Haven't to connect to a suitable AP now!
I (1382) chip[DL]: Done driving station state, nothing else to do...

[2022-11-03 12:21:14.420]# RECV ASCII>
[0;32mI (1392) chip[SVR]: Server initializing...
I (1392) chip[TS]: Last Known Good Time: [unknown]
I (1402) chip[TS]: Setting Last Known Good Time to firmware build time 2022-10-28T18:53:28
I (1412) chip[DMG]: AccessControl: initializing
I (1412) chip[DMG]: Examples::AccessControlDelegate::Init
I (1422) chip[DMG]: AccessControl: setting
I (1422) chip[DMG]: DefaultAclStorage: initializing
I (1432) chip[DMG]: DefaultAclStorag
[2022-11-03 12:21:14.467]# RECV ASCII>
e: 0 entries loaded
I (1442) chip[ZCL]: Using ZAP configuration...
I (1442) esp_matter_cluster: Cluster plugin init common callback
I (1452) chip[DMG]: AccessControlCluster: initializing
I (1452) chip[ZCL]: 0x3c109108ep 0 clus 0x0000_0030 attr 0x0000_0000 not supported
I (1462) chip[ZCL]: Initiating Admin Commissioning cluster.
E (1472) chip[ZCL]: Duplicate attribute override registration failed
I (1482) chip[DIS]: Updating
[2022-11-03 12:21:14.510]# RECV ASCII>
services using commissioning mode 1
I (1482) chip[DIS]: CHIP minimal mDNS started advertising.
I (1492) chip[DIS]: Advertise commission parameter vendorID=65521 productID=32768 discriminator=3840/15 cm=1
I (1502) chip[DIS]: CHIP minimal mDNS configured as 'Commissionable node device'; instance name: AE098CD874986CCA.
I (1512) chip[DIS]: mDNS service published: _matterc._udp
I (1512) chip[IN]: CASE Server enabling CASE session setups
I (
[2022-11-03 12:21:14.553]# RECV ASCII>
1522) chip[SVR]: Joining Multicast groups
I (1532) chip[SVR]: Server Listening...
I (1532) esp_matter_core: Dynamic endpoint 0 added
I (1542) esp_matter_attribute: ********** Endpoint 0x0001's Cluster 0x0003's Attribute 0x0001 is 0 **********
I (1552) esp_matter_attribute: ********** Endpoint 0x0001's Cluster 0x0004's Attribute 0x0000 is 128 **********
I (1562) esp_matter_attribute: ********** Endpoint 0x0001's Cluster 0x0004's Attribute 0xFFFC is
[2022-11-03 12:21:14.598]# RECV ASCII>
<invalid type: 0> **********
I (1572) esp_matter_attribute: ********** Endpoint 0x0001's Cluster 0x0005's Attribute 0x0000 is 0 **********
I (1582) esp_matter_attribute: ********** Endpoint 0x0001's Cluster 0x0006's Attribute 0xFFFC is 1 **********
I (1592) esp_matter_attribute: ********** Endpoint 0x0001's Cluster 0x0006's Attribute 0x4003 is 1 **********
I (1602) esp_matter_attribute: ********** Endpoint 0x0001's Cluster 0x0006's Attribute 0x0000 is 1 ******
[2022-11-03 12:21:14.643]# RECV ASCII>
****
I (1612) chip[ZCL]: On/Off set value: 1 1
I (1622) esp_matter_attribute: ********** Endpoint 0x0001's Cluster 0x0006's Attribute 0x0000 is 1 **********
I (1632) chip[ZCL]: On/off already set to new value
I (1632) esp_matter_attribute: ********** Endpoint 0x0001's Cluster 0x0008's Attribute 0x0002 is 1 **********
I (1642) esp_matter_attribute: ********** Endpoint 0x0001's Cluster 0x0008's Attribute 0x0003 is 254 **********
I (1652)
[2022-11-03 12:21:14.688]# RECV ASCII>
esp_matter_attribute: ********** Endpoint 0x0001's Cluster 0x0008's Attribute 0xFFFC is 3 **********
I (1662) esp_matter_attribute: ********** Endpoint 0x0001's Cluster 0x0008's Attribute 0x0000 is 64 **********
I (1682) esp_matter_attribute: ********** Endpoint 0x0001's Cluster 0x0008's Attribute 0x4000 is 64 **********
I (1692) esp_matter_attribute: ********** Endpoint 0x0001's Cluster 0x0008's Attribute 0x0000 is 64 **********
I (1702) led_driver_ws2812: le
[2022-11-03 12:21:14.731]# RECV ASCII>
d set r:0, g:0, b:0
I (1702) esp_matter_attribute: ********** Endpoint 0x0001's Cluster 0x0300's Attribute 0x4010 is 250 **********
I (1712) esp_matter_attribute: ********** Endpoint 0x0001's Cluster 0x0300's Attribute 0x0007 is 250 **********
I (1722) esp_matter_attribute: ********** Endpoint 0x0001's Cluster 0x0300's Attribute 0x400B is 0 **********
I (1732) esp_matter_attribute: ********** Endpoint 0x0001's Cluster 0x0300's Attribute 0x400C is 65279 *******
[2022-11-03 12:21:14.776]# RECV ASCII>
***
I (1742) esp_matter_attribute: ********** Endpoint 0x0001's Cluster 0x0300's Attribute 0x0007 is 250 **********
I (1762) led_driver_ws2812: led set r:0, g:0, b:0
I (1762) esp_matter_attribute: ********** Endpoint 0x0001's Cluster 0x0300's Attribute 0x0008 is 2 **********
I (1772) esp_matter_attribute: ********** Endpoint 0x0001's Cluster 0x0300's Attribute 0x4001 is 2 **********
I (1792) esp_matter_core: Dynamic endpoint 1 added
E (
[2022-11-03 12:21:14.821]# RECV ASCII>
1792) chip[DL]: Long dispatch time: 401 ms, for event type 2
I (1802) chip[DL]: Configuring CHIPoBLE advertising (interval 25 ms, connectable)
I (1802) chip[DL]: Device already advertising, stop active advertisement and restart
I (1812) NimBLE: GAP procedure initiated: stop advertising.

I (1822) NimBLE: GAP procedure initiated: advertise;
I (1822) NimBLE: disc_mode=2
I (1832) NimBLE:  adv_channel_map=0 own_addr_type=1 adv_filter_poli
[2022-11-03 12:21:14.865]# RECV ASCII>
cy=0 adv_itvl_min=40 adv_itvl_max=40
I (1842) NimBLE:

I (1842) app_main: Commissioning window opened
I (1842) chip[DL]: WIFI_EVENT_STA_START
I (1852) phy: chan:1,max_power:80
I (1852) phy: chan:2,max_power:80
I (1862) phy: chan:3,max_power:80
I (1862) phy: chan:4,max_power:80
I (1862) phy: chan:5,max_power:80
I (1872) phy: chan:6,max_power:80
I (1872) phy: chan:7,max_power:80
[0;3
[2022-11-03 12:21:14.909]# RECV ASCII>
2mI (1882) phy: chan:8,max_power:80
I (1882) phy: chan:9,max_power:80
I (1882) phy: chan:10,max_power:80
I (1892) phy: chan:11,max_power:80
I (1892) phy: chan:12,max_power:80
I (1902) phy: chan:13,max_power:80
I (1902) phy: chan:14,max_power:80
W (1912) wifi:Haven't to connect to a suitable AP now!
I (1912) chip[DL]: Done driving station state, nothing else to do...
I (1922) led_driver_ws2812: led set r:0, g:0,
[2022-11-03 12:21:14.972]# RECV ASCII>
b:0
I (1922) led_driver_ws2812: led set r:0, g:0, b:0
I (1932) led_driver_ws2812: led set r:25, g:20, b:16

[2022-11-03 12:21:15.170]# RECV ASCII>
>
[2022-11-03 12:21:20.836]# RECV ASCII>
I (7812) chip[DL]: BLE GAP connection established (con 1)
I (7812) chip[DL]: CHIPoBLE advertising stopped
[2022-11-03 12:21:21.204]# RECV ASCII>
I (8152) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (8152) chip[BLE]: local and remote recv window sizes = 5
I (8162) chip[BLE]: selected BTP version 4
I (8162) chip[BLE]: using BTP fragment sizes rx 244 / tx 244.
[2022-11-03 12:21:21.287]# RECV ASCII>
I (8242) chip[DL]: Write request/command received for CHIPoBLE TX CCCD characteristic (con 1 ) indicate = 1
I (8242) chip[DL]: CHIPoBLE subscribe received
I (8242) NimBLE: GATT procedure initiated: indicate;
I (8252) NimBLE: att_handle=14

I (8282) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (8302) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (8302) ch
[2022-11-03 12:21:21.342]# RECV ASCII>
ip[EM]: >>> [E:58277r M:258339830] (U) Msg RX from 0:868ABB49D86F1904 [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)
I (8322) chip[EM]: <<< [E:58277r M:253120939] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:21 (SecureChannel:PBKDFParamResponse)
I (8332) chip[IN]: (U) Sending msg 253120939 to IP address 'BLE'
I (8332) NimBLE: GATT procedure initiated: indicate;
I (8342) NimBLE: att_handle=14

I (8362) chip[DL]: Confirm receive
[2022-11-03 12:21:21.418]# RECV ASCII>
d for CHIPoBLE TX characteristic indication (con 1) status= 14
I (8362) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (8372) chip[EM]: >>> [E:58277r M:258339831] (U) Msg RX from 0:868ABB49D86F1904 [0000] --- Type 0000:22 (SecureChannel:PASE_Pake1)
[2022-11-03 12:21:22.277]# RECV ASCII>
I (9222) chip[EM]: <<< [E:58277r M:253120940] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:23 (SecureChannel:PASE_Pake2)
I (9222) chip[IN]: (U) Sending msg 253120940 to IP address 'BLE'
I (9232) NimBLE: GATT procedure initiated: indicate;
I (9232) NimBLE: att_handle=14

E (9252) chip[DL]: Long dispatch time: 873 ms, for event type 7
I (9292) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14 [
[2022-11-03 12:21:22.321]# RECV ASCII>
0m
I (9292) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (9302) chip[EM]: >>> [E:58277r M:258339832] (U) Msg RX from 0:868ABB49D86F1904 [0000] --- Type 0000:24 (SecureChannel:PASE_Pake3)
I (9322) chip[EM]: <<< [E:58277r M:253120941] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:40 (SecureChannel:StatusReport)
I (9332) chip[IN]: (U) Sending msg 253120941 to IP address 'BLE'
I (9332) NimBLE: GATT procedure initiated:
[2022-11-03 12:21:22.366]# RECV ASCII>
indicate;
I (9342) NimBLE: att_handle=14

I (9342) chip[SC]: SecureSession[0x3fc974d0]: Moving from state 'kEstablishing' --> 'kActive'
I (9362) chip[SVR]: Commissioning completed session establishment step
I (9362) chip[DIS]: Updating services using commissioning mode 0
I (9372) chip[DIS]: CHIP minimal mDNS started advertising.
I (9372) chip[SVR]: Device completed Rendezvous process
I (9382) app_main: Commissioning sessi
[2022-11-03 12:21:22.417]# RECV ASCII>
on started
I (9382) app_main: Commissioning window closed
I (9362) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (9402) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (9412) chip[EM]: >>> [E:58278r M:212217907] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (9432) esp_matter_attribute: ********** Endpoint 0x0000's Cluster 0x0030's Attribute 0x000
[2022-11-03 12:21:22.475]# RECV ASCII>
0 is 0 **********
I (9432) chip[EM]: <<< [E:58278r M:165051971] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
I (9452) chip[IN]: (S) Sending msg 165051971 on secure session with LSID: 51019
I (9462) NimBLE: GATT procedure initiated: indicate;
I (9462) NimBLE: att_handle=14

I (9482) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (9492) NimBLE: GATT procedure initia
[2022-11-03 12:21:22.531]# RECV ASCII>
ted: indicate;
I (9502) NimBLE: att_handle=14

I (9512) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (9522) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (9532) chip[EM]: >>> [E:58279r M:212217908] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (9542) esp_matter_command: Received command 0x0000 for enpoint 0x0000's cluster 0x00000030
[2022-11-03 12:21:22.577]# RECV ASCII>

I (9552) chip[FS]: GeneralCommissioning: Received ArmFailSafe (60s)
I (9562) esp_matter_attribute: ********** Endpoint 0x0000's Cluster 0x0030's Attribute 0x0000 is 3 **********
I (9572) chip[EM]: <<< [E:58279r M:165051972] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (9572) chip[IN]: (S) Sending msg 165051972 on secure session with LSID: 51019
I (9592) NimBLE: GATT procedure initiated: indicate;
[0;
[2022-11-03 12:21:22.638]# RECV ASCII>
32mI (9602) NimBLE: att_handle=14

I (9622) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (9622) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (9632) chip[EM]: >>> [E:58280r M:212217909] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (9652) esp_matter_command: Received command 0x0002 for enpoint 0x0000's cluster 0x00000030
I (9652) chi
[2022-11-03 12:21:22.682]# RECV ASCII>
p[DL]: NVS set: chip-config/reg-location = 0 (0x0)
I (9662) chip[DL]: NVS set: chip-config/country-code = "XX"
I (9662) esp_matter_attribute: ********** Endpoint 0x0000's Cluster 0x0030's Attribute 0x0000 is 4 **********
I (9682) chip[EM]: <<< [E:58280r M:165051973] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (9692) chip[IN]: (S) Sending msg 165051973 on secure session with LSID: 51019
I (9692) NimBLE: GATT
[2022-11-03 12:21:22.740]# RECV ASCII>
procedure initiated: indicate;
I (9702) NimBLE: att_handle=14

I (9722) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (9732) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (9742) chip[EM]: >>> [E:58281r M:212217910] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (9752) esp_matter_command: Received command 0x0002 for enpoint 0x0000's c
[2022-11-03 12:21:22.796]# RECV ASCII>
luster 0x0000003E
I (9762) chip[ZCL]: OpCreds: Certificate Chain request received for PAI
I (9772) chip[EM]: <<< [E:58281r M:165051974] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (9772) chip[IN]: (S) Sending msg 165051974 on secure session with LSID: 51019
I (9782) NimBLE: GATT procedure initiated: indicate;
I (9802) NimBLE: att_handle=14

I (9812) chip[DL]: Confirm received for CHIPoBLE TX c
[2022-11-03 12:21:22.864]# RECV ASCII>
haracteristic indication (con 1) status= 14
I (9822) NimBLE: GATT procedure initiated: indicate;
I (9832) NimBLE: att_handle=14

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

I (9872) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (9882) CHIP
[2022-11-03 12:21:22.910]# RECV ASCII>
[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (9892) chip[EM]: >>> [E:58282r M:212217911] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (9902) esp_matter_command: Received command 0x0002 for enpoint 0x0000's cluster 0x0000003E
I (9912) chip[ZCL]: OpCreds: Certificate Chain request received for DAC
I (9922) chip[EM]: <<< [E:58282r M:165051975] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001
[2022-11-03 12:21:22.955]# RECV ASCII>
:09 (IM:InvokeCommandResponse)
I (9922) chip[IN]: (S) Sending msg 165051975 on secure session with LSID: 51019
I (9932) NimBLE: GATT procedure initiated: indicate;
I (9952) NimBLE: att_handle=14

I (9962) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (9972) Ni
[2022-11-03 12:21:23.021]# RECV ASCII>
mBLE: GATT procedure initiated: indicate;
I (9982) NimBLE: att_handle=14

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

I (10022) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (10032) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con
[2022-11-03 12:21:23.095]# RECV ASCII>
1 12
I (10042) chip[EM]: >>> [E:58283r M:212217912] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (10052) esp_matter_command: Received command 0x0000 for enpoint 0x0000's cluster 0x0000003E
I (10062) chip[ZCL]: OpCreds: Received an AttestationRequest command
[2022-11-03 12:21:23.274]# RECV ASCII>
I (10242) chip[ZCL]: OpCreds: AttestationRequest successful.
I (10242) chip[EM]: <<< [E:58283r M:165051976] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (10252) chip[IN]: (S) Sending msg 165051976 on secure session with LSID: 51019
I (10262) NimBLE: GATT procedure initiated: indicate;
I (10272) NimBLE: att_handle=14

E (10272) chip[DL]: Long dispatch time: 231 ms, for event type 7
I (102
[2022-11-03 12:21:23.339]# RECV ASCII>
92) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (10302) NimBLE: GATT procedure initiated: indicate;
I (10312) NimBLE: att_handle=14

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

I (10352) chip[DL]: Confirm received for CHIPoBLE TX characteristic in
[2022-11-03 12:21:23.430]# RECV ASCII>
dication (con 1) status= 14
I (10372) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (10372) chip[EM]: >>> [E:58284r M:212217913] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (10392) esp_matter_command: Received command 0x0004 for enpoint 0x0000's cluster 0x0000003E
I (10392) chip[ZCL]: OpCreds: Received a CSRRequest command
[2022-11-03 12:21:23.762]# RECV ASCII>
I (10742) chip[ZCL]: OpCreds: AllocatePendingOperationalKey succeeded
[2022-11-03 12:21:23.951]# RECV ASCII>
I (10912) chip[ZCL]: OpCreds: CSRRequest successful.
I (10912) chip[EM]: <<< [E:58284r M:165051977] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (10932) chip[IN]: (S) Sending msg 165051977 on secure session with LSID: 51019
I (10932) NimBLE: GATT procedure initiated: indicate;
I (10942) NimBLE: att_handle=14

E (10942) chip[DL]: Long dispatch time: 570 ms, for event type 7
I (10972) chip
[2022-11-03 12:21:24.032]# RECV ASCII>
[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (10972) NimBLE: GATT procedure initiated: indicate;
I (10982) NimBLE: att_handle=14

I (11002) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (11022) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (11042) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I
[2022-11-03 12:21:24.109]# RECV ASCII>
(11052) chip[EM]: >>> [E:58285r M:212217914] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (11062) esp_matter_command: Received command 0x000B for enpoint 0x0000's cluster 0x0000003E
I (11072) chip[ZCL]: OpCreds: Received an AddTrustedRootCertificate command
[2022-11-03 12:21:24.580]# RECV ASCII>
I (11422) chip[ZCL]: OpCreds: AddTrustedRootCertificate successful.
I (11422) chip[EM]: <<< [E:58285r M:165051978] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (11432) chip[IN]: (S) Sending msg 165051978 on secure session with LSID: 51019
I (11442) NimBLE: GATT procedure initiated: indicate;
I (11452) NimBLE: att_handle=14

E (11452) chip[DL]: Long dispatch time: 402 ms, for event type 7
[0;32
[2022-11-03 12:21:24.586]# RECV ASCII>
mI (11482) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (11482) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (11532) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (11552) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (11562) chip[EM]: >>> [E:58286r M:212217915] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:Invok
[2022-11-03 12:21:24.625]# RECV ASCII>
eCommandRequest)
I (11582) esp_matter_command: Received command 0x0006 for enpoint 0x0000's cluster 0x0000003E
I (11582) chip[ZCL]: OpCreds: Received an AddNOC command
I (11592) chip[FP]: Validating NOC chain
[2022-11-03 12:21:25.311]# RECV ASCII>
I (12292) chip[FP]: NOC chain validation successful
I (12292) chip[FP]: Added new fabric at index: 0x1
I (12292) chip[FP]: Assigned compressed fabric ID: 0x527C1F3629DC158C, node ID: 0x0000000000007283
I (12302) chip[TS]: Last Known Good Time: 2022-10-28T18:53:28
I (12312) chip[TS]: New proposed Last Known Good Time: 2021-01-01T00:00:00
I (12312) chip[TS]: Retaining current Last Known Good Time
I (12332) chip[ZCL]: OpCreds: ACL e
[2022-11-03 12:21:25.356]# RECV ASCII>
ntry created for Fabric index 0x1 CASE Admin Subject 0x000000000001B669
I (12332) chip[DIS]: Advertise operational node 527C1F3629DC158C-0000000000007283
I (12342) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: 527C1F3629DC158C-0000000000007283.
I (12352) chip[DIS]: mDNS service published: _matter._tcp
I (12362) chip[ZCL]: OpCreds: successfully created fabric index 0x1 via AddNOC
I (12372) chip[EM]: <<< [E:58286r M:
[2022-11-03 12:21:25.416]# RECV ASCII>
165051979] (S) Msg TX to 1:FFFFFFFB00000000 [158C] --- Type 0001:09 (IM:InvokeCommandResponse)
I (12382) chip[IN]: (S) Sending msg 165051979 on secure session with LSID: 51019
I (12392) NimBLE: GATT procedure initiated: indicate;
I (12392) NimBLE: att_handle=14

E (12402) chip[DL]: Long dispatch time: 839 ms, for event type 7
I (12422) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (12432) C
[2022-11-03 12:21:25.461]# RECV ASCII>
HIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (12442) chip[EM]: >>> [E:58287r M:212217916] (S) Msg RX from 1:FFFFFFFB00000000 [158C] --- Type 0001:08 (IM:InvokeCommandRequest)
I (12462) esp_matter_attribute: ********** Endpoint 0x0000's Cluster 0x0030's Attribute 0x0000 is 14 **********
I (12462) chip[EM]: <<< [E:58287r M:165051980] (S) Msg TX to 1:FFFFFFFB00000000 [158C] --- Type 0001:09 (IM:InvokeCommandResponse)
I (12472) chip[IN
[2022-11-03 12:21:25.522]# RECV ASCII>
]: (S) Sending msg 165051980 on secure session with LSID: 51019
I (12482) NimBLE: GATT procedure initiated: indicate;
I (12482) NimBLE: att_handle=14

I (12512) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (12522) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (12532) chip[EM]: >>> [E:58288r M:212217917] (S) Msg RX from 1:FFFFFFFB00000000 [158C] --- Type 0001:08 (IM:InvokeC
[2022-11-03 12:21:25.572]# RECV ASCII>
ommandRequest)
I (12542) chip[NP]: ESP NetworkCommissioningDelegate: SSID: wcs
I (12552) chip[DL]: WiFi station mode change: Enabled -> Disabled
I (12562) chip[DL]: WiFi station mode change: Disabled -> Enabled
I (12572) phy: chan:1,max_power:80
I (12572) phy: chan:2,max_power:80
I (12582) phy: chan:3,max_power:80
I (12582) phy: chan:4,max_power:80
I (12582) phy: chan:5,max_power:80
I (12592) phy: cha
[2022-11-03 12:21:25.616]# RECV ASCII>
n:6,max_power:80
I (12592) phy: chan:7,max_power:80
I (12592) phy: chan:8,max_power:80
I (12602) phy: chan:9,max_power:80
I (12602) phy: chan:10,max_power:80
I (12602) phy: chan:11,max_power:80
I (12612) phy: chan:12,max_power:80
I (12612) phy: chan:13,max_power:80
I (12612) phy: chan:14,max_power:80
W (12632) wifi:Haven't to connect to a suitable AP now!
I (12632) chip[DL]: Attempting to connect WiF
[2022-11-03 12:21:25.660]# RECV ASCII>
i station interface
I (12642) chip[DL]: WiFi station state change: NotConnected -> Connecting
I (12642) chip[DL]: Done driving station state, nothing else to do...
I (12652) phy: chan:1,max_power:80
I (12652) phy: chan:2,max_power:80
I (12652) phy: chan:3,max_power:80
I (12662) phy: chan:4,max_power:80
I (12662) phy: chan:5,max_power:80
I (12672) phy: chan:6,max_power:80
I (12682) phy: chan:7,max_powe
[2022-11-03 12:21:25.705]# RECV ASCII>
r:80
I (12682) phy: chan:8,max_power:80
I (12692) phy: chan:9,max_power:80
I (12692) phy: chan:10,max_power:80
I (12692) phy: chan:11,max_power:80
I (12702) phy: chan:12,max_power:80
I (12702) phy: chan:13,max_power:80
I (12702) phy: chan:14,max_power:80
W (12712) wifi:Haven't to connect to a suitable AP now!
I (12712) chip[DL]: Attempting to connect WiFi station interface
E (12722) wifi:sta is connecting,
[2022-11-03 12:21:25.749]# RECV ASCII>
return error
E (12722) chip[DL]: esp_wifi_connect() failed: ESP_ERR_WIFI_CONN
I (12732) phy: chan:1,max_power:80
I (12742) phy: chan:2,max_power:80
I (12742) phy: chan:3,max_power:80
I (12752) phy: chan:4,max_power:80
I (12752) phy: chan:5,max_power:80
I (12752) phy: chan:6,max_power:80
I (12762) phy: chan:7,max_power:80
I (12762) phy: chan:8,max_power:80
I (12762) phy: chan:9,max_power:80
[2022-11-03 12:21:25.794]# RECV ASCII>
I (12772) phy: chan:10,max_power:80
I (12772) phy: chan:11,max_power:80
I (12772) phy: chan:12,max_power:80
I (12782) phy: chan:13,max_power:80
I (12782) phy: chan:14,max_power:80
W (12782) wifi:Haven't to connect to a suitable AP now!
I (12792) chip[DL]: Attempting to connect WiFi station interface
E (12802) wifi:sta is connecting, return error
E (12812) chip[DL]: esp_wifi_connect() failed: ESP_ERR_WIFI_CONN
W (12812) w
[2022-11-03 12:21:25.854]# RECV ASCII>
ifi:Haven't to connect to a suitable AP now!
E (12822) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
[2022-11-03 12:21:26.896]# RECV ASCII>
I (13862) wifi:new:<6,0>, old:<1,0>, ap:<255,255>, sta:<6,0>, prof:1
[2022-11-03 12:21:27.548]# RECV ASCII>
I (14462) wifi:state: init -> auth (b0)
I (14502) wifi:state: auth -> assoc (0)
I (14512) wifi:state: assoc -> run (10)
I (14532) wifi:connected with wcs, aid = 3, channel 6, BW20, bssid = 86:1b:77:95:f6:32
I (14542) wifi:security: WPA2-PSK, phy: bgn, rssi: -33
I (14552) wifi:pm start, type: 1
I (14552) wifi:set rx beacon pti, rx_bcn_pti: 14, bcn_timeout: 14, mt_pti: 25000, mt_time: 10000
I (14552) chip[DL]: WIFI_EVENT_STA_CONNECTED
I (14562) chip[DL]: WiFi station state change:
[2022-11-03 12:21:27.593]# RECV ASCII>
Connecting -> Connecting_Succeeded
I (14572) phy: chan:1,max_power:80
I (14572) phy: chan:2,max_power:80
I (14582) phy: chan:3,max_power:80
I (14582) phy: chan:4,max_power:80
I (14592) phy: chan:5,max_power:80
I (14592) phy: chan:6,max_power:80
I (14592) phy: chan:7,max_power:80
I (14602) phy: chan:8,max_power:80
I (14602) phy: chan:9,max_power:80
I (14602) phy: chan:10,max_power:80

[2022-11-03 12:21:27.637]# RECV ASCII>
[0;32mI (14612) phy: chan:11,max_power:80
I (14612) phy: chan:12,max_power:80
I (14612) phy: chan:13,max_power:80
I (14622) phy: chan:14,max_power:80
I (14572) wifi:BcnInt:102400, DTIM:3
I (14632) chip[DL]: WiFi station state change: Connecting_Succeeded -> Connected
I (14642) chip[DL]: WiFi station interface connected
I (14642) esp_matter_attribute: ********** Endpoint 0x0000's Cluster 0x0030's Attribute 0x0000 is 16 **********

[2022-11-03 12:21:27.682]# RECV ASCII>
[0;32mI (14652) chip[EM]: <<< [E:58288r M:165051981] (S) Msg TX to 1:FFFFFFFB00000000 [158C] --- Type 0001:09 (IM:InvokeCommandResponse)
I (14672) chip[IN]: (S) Sending msg 165051981 on secure session with LSID: 51019
I (14682) NimBLE: GATT procedure initiated: indicate;
I (14682) NimBLE: att_handle=14

I (14682) chip[ZCL]: WiFiDiagnosticsDelegate: OnConnectionStatusChanged
I (14692) chip[DL]: Done driving station state, nothing else to do...
[2022-11-03 12:21:27.726]# RECV ASCII>
E (14692) chip[DL]: Long dispatch time: 142 ms, for event type 49152
I (14712) chip[DIS]: Advertise operational node 527C1F3629DC158C-0000000000007283
I (14712) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: 527C1F3629DC158C-0000000000007283.
I (14722) chip[DIS]: mDNS service published: _matter._tcp
I (14732) chip[SVR]: Operational advertising enabled
I (14732) chip[DL]: Updating advertising data
[0;3
[2022-11-03 12:21:27.785]# RECV ASCII>
2mI (14722) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
[2022-11-03 12:21:28.568]# RECV ASCII>
I (15552) esp_netif_handlers: sta ip: <IP_ADDRESS>, mask: <IP_ADDRESS>, gw: <IP_ADDRESS>
I (15552) chip[DL]: IP_EVENT_STA_GOT_IP
I (15562) chip[DL]: IPv4 address changed on WiFi station interface: <IP_ADDRESS>/<IP_ADDRESS> gateway <IP_ADDRESS>
I (15572) chip[DL]: IPv4 Internet connectivity ESTABLISHED
I (15572) app_main: Interface IP Address changed
I (15572) chip[DIS]: Updating services using commissioning mode 0
I (15
[2022-11-03 12:21:28.646]# RECV ASCII>
592) chip[DIS]: CHIP minimal mDNS started advertising.
I (15592) chip[DIS]: Advertise operational node 527C1F3629DC158C-0000000000007283
I (15602) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: 527C1F3629DC158C-0000000000007283.
I (15622) chip[DIS]: mDNS service published: _matter._tcp
[2022-11-03 12:21:28.741]# RECV ASCII>
I (15722) chip[EM]: >>> [E:58289r M:258339833] (U) Msg RX from 0:5D0C5FD66C8DB1E8 [0000] --- Type 0000:30 (SecureChannel:CASE_Sigma1)
I (15732) chip[IN]: CASE Server received Sigma1 message. Starting handshake. EC 0x3fc98d48
I (15732) chip[IN]: CASE Server disabling CASE session setups
I (15752) chip[EM]: <<< [E:58289r M:253120942 (Ack:258339833)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (15762) chip[IN]:
[2022-11-03 12:21:28.806]# RECV ASCII>
(U) Sending msg 253120942 to IP address 'UDP:<IP_ADDRESS>%st1:62047'
I (15762) chip[SC]: Received Sigma1 msg
I (15782) chip[SC]: CASE matched destination ID: fabricIndex 1, NodeID 0x0000000000007283
[2022-11-03 12:21:29.339]# RECV ASCII>
I (16292) chip[EM]: <<< [E:58289r M:253120943 (Ack:258339833)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:31 (SecureChannel:CASE_Sigma2)
I (16302) chip[IN]: (U) Sending msg 253120943 to IP address 'UDP:<IP_ADDRESS>%st1:62047'
I (16302) chip[SC]: Sent Sigma2 msg
E (16302) chip[DL]: Long dispatch time: 582 ms, for event type 3
[2022-11-03 12:21:29.457]# RECV ASCII>
I (16432) chip[EM]: >>> [E:58289r M:258339834 (Ack:253120943)] (U) Msg RX from 0:5D0C5FD66C8DB1E8 [0000] --- Type 0000:32 (SecureChannel:CASE_Sigma3)
I (16452) chip[EM]: <<< [E:58289r M:253120944 (Ack:258339834)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (16462) chip[IN]: (U) Sending msg 253120944 to IP address 'UDP:<IP_ADDRESS>%st1:62047'
I (16462) chip[SC]: Received Sigma3 msg
E (16482) chip[SC]: The d
[2022-11-03 12:21:29.520]# RECV ASCII>
evice does not support GetClock_RealTimeMS() API: 6c.  Falling back to Last Known Good UTC Time
[2022-11-03 12:21:30.554]# RECV ASCII>
I (17532) chip[EM]: <<< [E:58289r M:253120945 (Ack:258339834)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:40 (SecureChannel:StatusReport)
I (17552) chip[IN]: (U) Sending msg 253120945 to IP address 'UDP:<IP_ADDRESS>%st1:62047'
I (17552) chip[SC]: SecureSession[0x3fc97588]: Moving from state 'kEstablishing' --> 'kActive'
I (17562) chip[IN]: CASE Session established to peer: <000000000001B669, 1>
I (17562) chip[IN]: CASE Server enabling CASE
[2022-11-03 12:21:30.598]# RECV ASCII>
session setups
E (17582) chip[DL]: Long dispatch time: 1140 ms, for event type 3
I (17582) chip[DL]: IP_EVENT_GOT_IP6
I (17592) chip[DL]: IPv6 addr available. Ready on WIFI_STA_DEF interface: fe80:0000:0000:0000:6255:f9ff:fe77:b444
I (17602) app_main: Interface IP Address changed
I (17602) chip[DIS]: Updating services using commissioning mode 0
I (17612) chip[DIS]: CHIP minimal mDNS started advertising.
I (17622) chip[DIS]:
[2022-11-03 12:21:30.693]# RECV ASCII>
Advertise operational node 527C1F3629DC158C-0000000000007283
I (17622) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: 527C1F3629DC158C-0000000000007283.
I (17642) chip[DIS]: mDNS service published: _matter._tcp
I (17642) ROUTE_HOOK: Hook already installed on netif, skip...
I (17542) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
[2022-11-03 12:21:30.781]# RECV ASCII>
I (17762) chip[EM]: >>> [E:58290r M:120997417] (S) Msg RX from 1:000000000001B669 [158C] --- Type 0001:08 (IM:InvokeCommandRequest)
I (17762) esp_matter_command: Received command 0x0004 for enpoint 0x0000's cluster 0x00000030
I (17772) chip[FS]: GeneralCommissioning: Received CommissioningComplete
I (17792) chip[FP]: Metadata for Fabric 0x1 persisted to storage.
I (17792) chip[TS]: Committing Last Known Good Time to storage: 2022-10-28T18:53:28
[0
[2022-11-03 12:21:30.825]# RECV ASCII>
;32mI (17802) chip[ZCL]: OpCreds: Fabric index 0x1 was committed to storage. Compressed Fabric Id 0x527C1F3629DC158C, FabricId<PHONE_NUMBER>000001, NodeId<PHONE_NUMBER>007283, VendorId 0xFFF1
I (17822) chip[FS]: GeneralCommissioning: Successfully commited pending fabric data
I (17832) chip[FS]: Fail-safe cleanly disarmed
I (17832) esp_matter_attribute: ********** Endpoint 0x0000's Cluster 0x0030's Attribute 0x0000 is 0 **********
I (17842) chip[EM]: <<< [E:58290r M:
[2022-11-03 12:21:30.870]# RECV ASCII>
44921704 (Ack:120997417)] (S) Msg TX to 1:000000000001B669 [158C] --- Type 0001:09 (IM:InvokeCommandResponse)
I (17852) chip[IN]: (S) Sending msg 44921704 on secure session with LSID: 51020
I (17862) chip[EM]: >>> [E:58289r M:258339835 (Ack:253120945)] (U) Msg RX from 0:5D0C5FD66C8DB1E8 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (17872) chip[SVR]: Commissioning completed successfully
I (17882) chip[DIS]: Updating services using commissioning mode
[2022-11-03 12:21:30.915]# RECV ASCII>
0
I (17882) chip[DIS]: CHIP minimal mDNS started advertising.
I (17902) chip[DIS]: Advertise operational node 527C1F3629DC158C-0000000000007283
I (17902) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: 527C1F3629DC158C-0000000000007283.
I (17922) chip[DIS]: mDNS service published: _matter._tcp
I (17922) chip[SC]: SecureSession[0x3fc974d0]: Moving from state 'kActive' --> 'kPendingEviction'
I (17932) chip[
[2022-11-03 12:21:30.960]# RECV ASCII>
BLE]: Releasing end point's BLE connection back to application.
I (17942) app_main: Commissioning complete
I (17952) NimBLE: GAP procedure initiated: stop advertising.

I (17952) NimBLE: GAP procedure initiated: terminate connection; conn_handle=1 hci_reason=19

I (17872) chip[DL]: Write request/command received for CHIPoBLE TX CCCD characteristic (con 1 ) indicate = 0
I (17972) chip[DL]: CHIPoBLE unsubscribe received
I (17972) chip[D
[2022-11-03 12:21:31.004]# RECV ASCII>
L]: BLE GAP connection terminated (con 1 reason 0x213)
W (17982) Timer: Timer not stopped
W (17982) Timer: Timer not stopped
W (18002) BTDM_INIT: esp_bt_mem_release not implemented, return OK
I (18002) esp_matter_core: BLE deinit successful and memory reclaimed
E (18012) chip[DL]: Long dispatch time: 137 ms, for event type 32781
I (18012) chip[EM]: >>> [E:58290r M:120997418 (Ack:44921704)] (S) Msg RX from 1:000000000001B669 [158C] --- T
[2022-11-03 12:21:31.065]# RECV ASCII>
ype 0000:10 (SecureChannel:StandaloneAck)
I (18022) app_main: Commissioning window closed
E (18032) chip[BLE]: no endpoint for unsub recvd
[2022-11-03 12:21:51.173]# RECV ASCII>
W (38132) wifi:idx:0 (ifx:0, 86:1b:77:95:f6:32), tid:0, ssn:10, winSize:64

@shun-dgut Logs says that commissioning was successful.

�[0;32mI (17872) chip[SVR]: Commissioning completed successfully�[0m

Can you elaborate a bit more on "chip tool Configuration failed"?
A minor suggestion: May be for next issues, you can put the logs into file or put them under .

@shun-dgut Logs says that commissioning was successful.

�[0;32mI (17872) chip[SVR]: Commissioning completed successfully�[0m

Can you elaborate a bit more on "chip tool Configuration failed"?
A minor suggestion: May be for next issues, you can put the logs into file or put them under .

Thanks for your reply, but it seems out of control. I tried adding with home in ios 16.1, ca
matter send cmd.txt
n connect to the same network, but can't control it, home display doesn't respond.
This is the control log of the chip tool.

@shun-dgut Logs says that commissioning was successful.

�[0;32mI (17872) chip[SVR]: Commissioning completed successfully�[0m

Can you elaborate a bit more on "chip tool Configuration failed"?
A minor suggestion: May be for next issues, you can put the logs into file or put them under .

This is the control log of the chip tool
matter send cmd.txt

I also tried adding devices using ios16.1 home, devices can be added but not controlled

@shun-dgut Looks like you have attached an empty log file. Can you please re-attach the one with logs?

I also tried adding devices using ios16.1 home, devices can be added but not controlled

Did you use this along with Apple HomePod or Apple TV? Because, it would be required for controlling the devices.

matter send cmd.txt
Sorry, this is the log.
Matter over wifi can't communicate directly with home?

@shun-dgut Looks like you have attached an empty log file. Can you please re-attach the one with logs?

I also tried adding devices using ios16.1 home, devices can be added but not controlled

Did you use this along with Apple HomePod or Apple TV? Because, it would be required for controlling the device
matter send cmd.txt
s.

Sorry, this is the log.
Matter over wifi can't communicate directly with home?

Matter over wifi can't communicate directly with home?

Please take a look at this thread https://github.com/espressif/esp-matter/issues/78#issuecomment-1296698698

@shun-dgut Please close this if your issue is resolved

@shun-dgut Closing this as the original issue is addressed. Please create a new one in case you see any problems


Binding should expose an observable decorator

Should be a subset of the bindable functionality that can be used on any class instance field -
import {observable} from 'aurelia-binding';

export class MyViewModel {
  user;
  constructor() {
    this.user = new User();
  }
}

class User {
  @observable name = '';
  nameChanged(newValue) {
    console.log(newValue);
  }
}

I like this idea!
I think this will do the trick
function observable(target, propertyName, descriptor) {
  // use a convention to compute the inner property name and the callback
  // function name.
  let innerPropertyName = `_${propertyName}`;
  let callbackName = `${propertyName}Changed`;

  // set the initial value of the property.
  target[innerPropertyName] = descriptor.initializer();

  // we're adding a getter and setter which means the property descriptor
  // cannot have a "value" or "writable" attribute
  delete descriptor.writable;
  delete descriptor.initializer;

  // add the getter and setter to the property descriptor.
  descriptor.get = function() { return this[innerPropertyName]; };
  descriptor.set = function(newValue) {
      let oldValue = this[innerPropertyName];
      this[innerPropertyName] = newValue;
      if (this[callbackName]) {
        this[callbackName](newValue, oldValue);
      }
    };

  // make sure Aurelia doesn't use dirty-checking by declaring the property's
  // dependencies. This is the equivalent of "@computedFrom(...)".
  descriptor.get.dependencies = [innerPropertyName];
}

What about an option to explicitly specify the changed handler?

That would be cool- also- this decorator doesn't seem to work in TypeScript.

@jdanyow do you think it would work somehow to break this out somehow to work from multiple decorators?  That way both @bindable and @observable could use the same code to implemented the changeHandler?

@PWKad That's a tricky question. There are parts of that code that are very behavior-specific, such as the options check, for example.

@jdanyow I just got around to testing what you put in and it seems to work perfect on a class instance field.  If I add some tests to binding to support this as a class decorator and a class instance field decorator think we can get this in the next release?

Sounds good to me- some outstanding questions/concerns:

does it work in typescript
what repo does it go in?
maybe the name isn't quite right.  Maybe something like @notifyChanged or @notifies is more accurate?
option to specify the handler function name

@EisenbergEffect thoughts?

I think this will preserve the default value, even in typescript:
function observable(target, propertyName, descriptor) {
  // use a convention to compute the inner property name and the callback
  // function name.
  let innerPropertyName = `_${propertyName}`;
  let callbackName = `${propertyName}Changed`;

  // typescript or babel?
  let babel = arguments.length === 3;

  if (babel) {
    // babel passes in the property descriptor with a method to get the initial value.
    // set the initial value of the property.
    target[innerPropertyName] = descriptor.initializer();
  } else {
    // typescript doesn't pass in the property descriptor.
    descriptor = {};
  }

  // we're adding a getter and setter which means the property descriptor
  // cannot have a "value" or "writable" attribute
  delete descriptor.writable;
  delete descriptor.initializer;

  // add the getter and setter to the property descriptor.
  descriptor.get = function() { return this[innerPropertyName]; };
  descriptor.set = function(newValue) {
      let oldValue = this[innerPropertyName];
      this[innerPropertyName] = newValue;
      if (this[callbackName]) {
        this[callbackName](newValue, oldValue);
      }
    };

  // make sure Aurelia doesn't use dirty-checking by declaring the property's
  // dependencies. This is the equivalent of "@computedFrom(...)".
  descriptor.get.dependencies = [innerPropertyName];

  if (!babel) {
    Object.defineProperty(target, propertyName, descriptor);
  }
}

This is a modified version accepting a changeHandler to be specified, both @observable   value = 10;and @observable({changeHandler: ‘myHandler’}) value=10;are working.
 function observable(targetOrConfig, key, descriptor) {
	console.trace('observable');
	let deco = function(target, key2, descriptor2) {
		// use a convention to compute the inner property name and the callback
		// function name.
		let innerPropertyName = `_${key2}`;
		let callbackName = (targetOrConfig && targetOrConfig.changeHandler) || `${key2}Changed`;

		// set the initial value of the property.
		target[innerPropertyName] = descriptor2.initializer();

		// we're adding a getter and setter which means the property descriptor
		// cannot have a "value" or "writable" attribute
		delete descriptor2.writable;
		delete descriptor2.initializer;

		// add the getter and setter to the property descriptor.
		descriptor2.get = function() { return this[innerPropertyName]; };
		descriptor2.set = function(newValue) {
			let oldValue = this[innerPropertyName];
			this[innerPropertyName] = newValue;
			if (this[callbackName]) {
				this[callbackName](newValue, oldValue);
			}
		};

		// make sure Aurelia doesn't use dirty-checking by declaring the property's
		// dependencies. This is the equivalent of "@computedFrom(...)".
		descriptor2.get.dependencies = [innerPropertyName];
	}

	if(key) {
		let target = targetOrConfig;
		targetOrConfig = null;
		return deco(target, key, descriptor);
	}

	return deco;
}

@jdanyow Should we put this in the box? In the binding repo or elsewhwere? Of note on this implementation is that the callback timing will be different than other scenarios.

yes, I think so.  Do you think the name @observable is appropriate or should it be something else? @notifies or @notifyChanged maybe?
@Scapal would you be interested in submitting a PR to the binding repo for this (with tests, etc)? (if not, no worries- we're just always looking for new contributers :rocket:)

I'm not sure what the best name is. I don't particularly like "notifies" or "notifyChanged" though...but I'm not sure if "observable" is the best name either...though I like that the best, mostly because of how it reads when combined with the property  name.

Yes @jdanyow and @Scapal have done a great job today of getting a working concept in place.
Personal opinion - @observable seems to be most common but does slightly conflict with other concepts.  @notifies or anything similar doesn't feel right.
Here's a user story to back it up, maybe this helps (or maybe it makes me look crazy) -
As a property of a class,
When my value changes,
I want to conventionally call a changed handler method (or a supplied override).
@observable
@watcher
@watch
@subscribe

I'll make some tests.
Concerning the naming, @subscribeshould be more related to observe more complex scenario and external data. I almost always inject a datastore component in my views and I'd like to have a simple decorator to subscribe to a change inside those datastore.
For the moment I use this code below. Is there a better way to do it?

Does this sound enough for a unit test?
import {observable} from '../../src/utils/observable-decorator.js';

describe('observable decorator', () => {
	it('changeHandler valueChanged should be called when changing the decorated property', () => {
		class Test  {
			@observable value = '';
			valueChanged () {
				this.test = this.value;
			}
		};

		var test = new Test();

		expect(test.test).not.toBeDefined();
		test.value = 'hello';
		expect(test.test).toBeDefined();
		expect(test.test).toEqual('hello');

		test.value = 'world';
		expect(test.test).toEqual('world');
	});

	it('changeHandler should be called when changing the decorated property', () => {
		class Test  {
			@observable({changeHandler: 'customHandler'}) value = '';
			valueChanged () {
				this.test = 'fail';
			}
			customHandler () {
				this.test = this.value + ' world';
			}
		};

		var test = new Test();

		expect(test.test).not.toBeDefined();
		test.value = 'hello';
		expect(test.test).toBeDefined();
		expect(test.test).toEqual('hello world');
	});
});

@Scapal looking good- will need a test for scenarios where the handler method name is passed in via config and a test for situations where the handler doesn't exist.

@EisenbergEffect

Of note on this implementation is that the callback timing will be different than other scenarios.

Another approach would be to use a plugin using Container.setHandlerCreatedCallback, setting a custom handler that would subscribeand unsubscribe a properyObserveron handler.invoke() and the overridden deactivate.
Would that be a better way?

I'm not sure that putting something like that on the Container would make sense, but you could put it directly on the observable function itself with a default implementation, so it always works as above...but it would be possible for the BindingEngine, once instantiated to possible override that. @jdanyow What do you think?

I see a lot of patterns needing to override activate and deactivate for decorator support. Wouldn't it be easier to integrate a basic mechanism making it easy for decorators to add some code execution there?
A decorator for aurelia-event-aggregator like @subscribe-event would also be nice for example. aurelia-fluxis already doing it that way.
The basic pattern is to implement a custom metadata property (using Symbols to avoid conflicts) where you store all the info from your decorators, and place a hook on the container (using setHandlerCreatedCallback), override the invoke and the target.deactivate to iterate over those metadata and implement the event subscriptions, observers...
Making this more straightforward or at least have a 'best practice' for such cases would be nice. The ability for a plugin to register for activate and deactivateeasily and receive a dedicated Metadata root point could be all what is needed.
Does is sound like a good design pattern?

The following code, which is my first attempt for the @observable feature, does that, only without using setHandlerCreatedCallback, directly from the decorator, so it only works if used after the optional attachedand detached definition. Here the decorator is on the change handler function, not the property.
Using setHandlerCreatedCallback and custom metadata would allow me to overcome this problem, but maybe it is a bit heavy to put that on the container.
export function onPropertyChange(...properties) {
	return function(target, key, descriptor) {
		let targetAttached = target.attached;
		let targetDetached = target.detached;

		target.attached = function() {
			properties.forEach( (propertyName) => {
				let subscriptionHandle = 'observe_' + propertyName + '_' + key;

				this[subscriptionHandle] =
					this.bindingEngine.propertyObserver(this, propertyName)
						.subscribe( () =>  this[key]() );
			});

			if(targetAttached !== undefined)
				return targetAttached.bind(this)();
		}

		target.detached = function() {
			properties.forEach( (propertyName) => {
				let subscriptionHandle = 'observe_' + propertyName + '_' + key;

				this[subscriptionHandle].dispose();
			});

			if(targetDetached !== undefined)
				return targetDetached.bind(this)();
		}

		return descriptor;
	}
}

@Scapal Any luck?  Anything you need feedback on at the moment?

@jdanyow @EisenbergEffect Any feedback for @Scapal ?  I love this so much I literally can't wait  :)

We don't want any attached/detached hacks. So, let's not have that particular implementation. I think this implementation is probably fine: https://github.com/aurelia/binding/issues/270#issuecomment-183449523
I'd like to see a PR. Probably the best place is the binding library. @jdanyow What do you think?

@EisenbergEffect binding repo sound good to me.  I agree this implementation looks the best out of all the options:  https://github.com/aurelia/binding/issues/270#issuecomment-183449523
@Scapal would be willing to create the PR in the binding repo?

@jdanyow Yes, I'm putting it all together. There was still an error when no initializer was provided.

PR was merged- thanks again @Scapal


update docs_CN with MigrationGuides

sync the docs_CN with  English docs

Codecov Report

Merging #1425 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1425   +/-   ##
=======================================
  Coverage   88.41%   88.41%
=======================================
  Files           5        5
  Lines         164      164
=======================================
  Hits          145      145
  Misses         19       19

Continue to review full report at Codecov.

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

Thanks for doing this @lovesomeone 👍


Slow compared to map?

Hi, i was trying to benchmark haxmap vs map,
https://github.com/kokizzu/kokizzu-benchmark/blob/master/assoc/go-haxmap/haxmap.go
vs
https://github.com/kokizzu/kokizzu-benchmark/blob/master/assoc/map.go
the diff
https://pastebin.com/diff/V3Y04Uha
but haxmap took like 51s vs 14s using map
time go run go-haxmap/haxmap.go
6009354 6009348 611297
36186112 159701682 23370001

CPU: 51.86s     Real: 26.87s    RAM: 2 386 608KB

time go run map.go
6009354 6009348 611297
36186112 159701682 23370001

CPU: 14.29s     Real: 12.43s    RAM: 2 271 672KB

the scenario is different. go standard map is not concurrent map. Now the haxmap  use lock free list to ensure that the map is concurrently safe，different from shard map with rwlock(this is waitfree lock)

A more fair comparison would be to a map with a Mutex/RWMutex


add spurious events to icgm sensor generator

I added in two tests for the spurious events and a demo file. I also exposed some other variables that we may want to capture (e.g., sensor pass percentage and the icgm traces generated during training). I am sure this is not perfect, but hopefully enough to allow everyone to keep moving forward.

@ed-nykaza Note that the Travis CI checks failed for the PR. I looked at the details and it's a Python 3.6 issue that I think is straightforward to fix. I'll just add it in this commit.

So unfortunately there is more code needed to make this work with the current iCGM analysis. And it looks like another case of duplicate code causing problems that I think maybe came about with Jason and @ed-nykaza just didn't know about it. The calculate_sensor_bias_properties() and the generate_icgm_sensors() do similar things. The spurious event stuff is integrated with generate_icgm_sensors but the iCGM analysis also needs the calculate_sensor_bias_properties to work. And there isn't test coverage that catches it. I'll take a look and see if there is an easy solution since Ed is out for now.

It seems to be more than a duplicate code issue and therefore not an easy fix. It boils down to assumptions of available information in the iCGM code that don't play well with the simulator.


Update README.md

Please review this and let me know if you want any changes.

Hi! Thank you so much for sending a contribution :)

Note: At the time between I started writing this answer and actually finishing it, @ikayz himself submitted a commit updating the install instructions, so I'm closing this PR as the issue is already solved. Still, there were some interesting info in my answer that should help you improve future contributions :)

Here are some corrections:

To run this project in your machine, follow the below steps:

Fork this repository.

To test things locally, a fork is not needed, cloning this repo is enough.

Clone this repository using eihter of the given options.

I'm not sure what you meant by "either of the given options". Could you clarify?

Open the repository in your text editor.

There's also no need to open the repo with a text editor. Did you mean a terminal?

Delete the yarn.lock file.

This is actually unwanted. A .lock file ensures developers that the packages' versions they're using is the ones expected at release time, and so meaning that these versions should work (since newer versions might introduce breaking changes that the developer is not aware at the time of release). Deleting a yarn.lock would mean that the dependency fetcher could get a newer and uncompatible version for a package, which would mean unexpected errors. This post clarifies things a little better: https://www.techgalery.com/2019/02/can-i-delete-package-lock-or-yarn-lock.html.

Run Command-  npm install
Run the project by using command- npm start
Then you can serve the website locally on  http://localhost:3000

This part is correct :) What I would suggest, though, is to use the code-fences syntax from Markdown (instead of <h4> tags). Writing:
```
This
```

In Markdown (.md) is rendered as:
This

Thank you so much @JPTIZ  for an elaborate reply. Being a fresher in open-source I learned a lot from your answer.
Looking forward to contribute more :)

@Shubham-Agarwal16  - Hey Shubham - we've opened some more issues - feel free to take a look and see if any of the others are good for you! :)


C++: StringStream

Hackerrank problem link
Provide your hackerrank problem link here.
Issue Checklist

[x] If you have previously contributed to this repo, you declare that you have not made a pull request for more than one issue in this repo till now.
[x] Your forked repo is up-to-date with the the origin remote.
[x] Have you checked that the hackerrank problem you are raising is not already present in the repo?
[x] Have you checked that the hackerrank problem you are raising is not raised by or assigned to another contributor?

Hacktoberfest Contributor

[x] Are you a Hacktoberfest Contributor?

Any other Changes?
If you are raising an issue with some more changes, please provide the details here.

Oops, looks like somebody made a PR on this one just 5 minutes ago


No feedback about errors

I just installed the plugin, I generated a key, created a secret gist, then I press "upload settings" in menu and nothing happens. I press Ctrl+alt+u and nothing happens. Even the console is empty.
And when I go to the gist page, it's empty as I left it.
I suppose that some error happened on the way, but I would certainly appreciate some message about this in the UI.

Hi, it looks like the settings were uploaded after a few minutes, but still, some visual feedback about the whole operation would be great. When you don't give visual feedback, users will think your application is broken, even when it isn't.

@mik01aj : Thanks, good idea

Notification where added just before this issue.
You can open another issue if you want more specific notifications.


All user Langflow data is lost with (most) of upgrades

Bug Description
Running pip install --upgrade langflow
when it actually upgrades to the next release, like to 1.013 in this case, all the previous data is lost - all flows, components, global variables. however had several upgrades, when data remained.
that is quite inconvenient obviously, as any keys are lost, any flows in work are lost etc.
First question - is there a way to restore the info that was lost in such an upgrade?
Second, proposal to solve this issue for the next upgrades.
Reproduction
Run pip install --upgrade langflow

like for the latest upgrade to 1.013

Expected behavior
All global variables, user flows and components shall remain intact in every upgrade.
Who can help?
No response
Operating System
MacOS
Langflow Version
1.012-013
Python Version
3.11
Screenshot
No response
Flow File
No response

Hey, Langflow stores the database on the langflow installation directory.
e.g.
/Users/xx/.pyenv/versions/3.11.7/envs/langflow/lib/python3.11/site-packages/langflow/langflow.db
is it possible that you changed the py env or wiped it out or reinstalled from scratch?
I'd suggest to set the db path to a known place next time
export LANGFLOW_DATABASE_URL=sqlite:////Users//langflow.db
On docker, if you don't mount the volume you will lose all the files there
an alternative is to use a local PG instance


Made "terminal" explicit, corrected grammar

At first, I didn't get that this type related to the terminal, so I've updated the content to make that explicit to hopefully help others in the same position. Whilst there, I corrected the grammar in the content.

Wow, you are my hero today 🎈


PowerShell on Target Machines does not process scripts using non-interactive account correctly

Environment
VSTS
Agent: Private
Agent.OS | Windows_NT
Agent.OSVersion | 10.0.14393
Agent.Version | 2.126.0
Issue Description
I am using the PowerShell on Target Machines task (v1 and v2) with a non-interactive user account. This works generally fine , but calling Invoke-Pester fails (using Pester v 41.1. and 4.2.0) with this error message:

A command that prompts the user failed because the host program or the command type does not support user interaction. Try a host program that supports user interaction, such as the Windows PowerShell Console or Windows PowerShell ISE, and remove prompt-related commands from command types that do not support user interaction, such as Windows

This does not happen when executing the Invoke-Pester command myself via Invoke-Command -ScriptBlock -Credential, therefore the VSTS task is to blame.
Error logs
2018-02-19T13:19:27.3864541Z 	 Deployment started on target machine...
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z System.AggregateException: Failed to execute the powershell script. Consult the logs below for details of the error.
2018-02-19T13:19:27.3864541Z A command that prompts the user failed because the host program or the command type does not support user interaction. Try a host program that supports user interaction, such as the Windows PowerShell Console or Windows PowerShell ISE, and remove prompt-related commands from command types that do not support user interaction, such as Windows PowerShell workflows. ---> System.Management.Automation.CmdletInvocationException: A command that prompts the user failed because the host program or the command type does not support user interaction. Try a host program that supports user interaction, such as the Windows PowerShell Console or Windows PowerShell ISE, and remove prompt-related commands from command types that do not support user interaction, such as Windows PowerShell workflows. ---> System.Management.Automation.Host.HostException: A command that prompts the user failed because the host program or the command type does not support user interaction. Try a host program that supports user interaction, such as the Windows PowerShell Console or Windows PowerShell ISE, and remove prompt-related commands from command types that do not support user interaction, such as Windows PowerShell workflows.
2018-02-19T13:19:27.3864541Z    at System.Management.Automation.Internal.Host.InternalHostRawUserInterface.ThrowNotInteractive()
2018-02-19T13:19:27.3864541Z    at System.Management.Automation.Internal.Host.InternalHostRawUserInterface.get_BackgroundColor()
2018-02-19T13:19:27.3864541Z    at Microsoft.PowerShell.Commands.ConsoleColorCmdlet.get_BackgroundColor()
2018-02-19T13:19:27.3864541Z    at Microsoft.PowerShell.Commands.WriteHostCommand.ProcessRecord()
2018-02-19T13:19:27.3864541Z    at System.Management.Automation.CommandProcessor.ProcessRecord()
2018-02-19T13:19:27.3864541Z    --- End of inner exception stack trace ---
2018-02-19T13:19:27.3864541Z    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
2018-02-19T13:19:27.3864541Z    at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke)
2018-02-19T13:19:27.3864541Z    at System.Management.Automation.PowerShell.Worker.CreateRunspaceIfNeededAndDoWork(Runspace rsToUse, Boolean isSync)
2018-02-19T13:19:27.3864541Z    at System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
2018-02-19T13:19:27.3864541Z    at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
2018-02-19T13:19:27.3864541Z    at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings settings)
2018-02-19T13:19:27.3864541Z    at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Deployment.PowershellExecutor.<>c__DisplayClass28_0.<Invoke>b__0()
2018-02-19T13:19:27.3864541Z    at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Utilities.RetryExecutor.<>c__DisplayClass19_0`1.<Execute>b__0()
2018-02-19T13:19:27.3864541Z    at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Utilities.RetryExecutor.Execute(Action action)
2018-02-19T13:19:27.3864541Z    at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Utilities.RetryExecutor.Execute[T](Func`1 action)
2018-02-19T13:19:27.3864541Z    at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Deployment.PowershellExecutor.Invoke(String errorContextMessage, Boolean writeResultToLog, Boolean isCancellable, ActionPreference errorActionPreference)
2018-02-19T13:19:27.3864541Z    --- End of inner exception stack trace ---
2018-02-19T13:19:27.3864541Z    at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Deployment.PowershellExecutor.Invoke(String errorContextMessage, Boolean writeResultToLog, Boolean isCancellable, ActionPreference errorActionPreference)
2018-02-19T13:19:27.3864541Z    at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Deployment.ScriptExecutor.ExecuteScript(IPowerShell powerShell, String script, String arguments, Boolean isScriptDotSourced, Boolean useHttp)
2018-02-19T13:19:27.3864541Z    at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Deployment.DeploymentService.RunPowerShellScripts(DeploymentMachineSpecification deploymentMachine, ScriptSpecification scriptSpecification, ScriptSpecification initializationScriptSpecification, String applicationPath, IPowerShell powerShellSession)
2018-02-19T13:19:27.3864541Z ---> (Inner Exception #0) System.Management.Automation.CmdletInvocationException: A command that prompts the user failed because the host program or the command type does not support user interaction. Try a host program that supports user interaction, such as the Windows PowerShell Console or Windows PowerShell ISE, and remove prompt-related commands from command types that do not support user interaction, such as Windows PowerShell workflows. ---> System.Management.Automation.Host.HostException: A command that prompts the user failed because the host program or the command type does not support user interaction. Try a host program that supports user interaction, such as the Windows PowerShell Console or Windows PowerShell ISE, and remove prompt-related commands from command types that do not support user interaction, such as Windows PowerShell workflows.
2018-02-19T13:19:27.3864541Z    at System.Management.Automation.Internal.Host.InternalHostRawUserInterface.ThrowNotInteractive()
2018-02-19T13:19:27.3864541Z    at System.Management.Automation.Internal.Host.InternalHostRawUserInterface.get_BackgroundColor()
2018-02-19T13:19:27.3864541Z    at Microsoft.PowerShell.Commands.ConsoleColorCmdlet.get_BackgroundColor()
2018-02-19T13:19:27.3864541Z    at Microsoft.PowerShell.Commands.WriteHostCommand.ProcessRecord()
2018-02-19T13:19:27.3864541Z    at System.Management.Automation.CommandProcessor.ProcessRecord()
2018-02-19T13:19:27.3864541Z    --- End of inner exception stack trace ---
2018-02-19T13:19:27.3864541Z    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
2018-02-19T13:19:27.3864541Z    at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke)
2018-02-19T13:19:27.3864541Z    at System.Management.Automation.PowerShell.Worker.CreateRunspaceIfNeededAndDoWork(Runspace rsToUse, Boolean isSync)
2018-02-19T13:19:27.3864541Z    at System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
2018-02-19T13:19:27.3864541Z    at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
2018-02-19T13:19:27.3864541Z    at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings settings)
2018-02-19T13:19:27.3864541Z    at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Deployment.PowershellExecutor.<>c__DisplayClass28_0.<Invoke>b__0()
2018-02-19T13:19:27.3864541Z    at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Utilities.RetryExecutor.<>c__DisplayClass19_0`1.<Execute>b__0()
2018-02-19T13:19:27.3864541Z    at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Utilities.RetryExecutor.Execute(Action action)
2018-02-19T13:19:27.3864541Z    at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Utilities.RetryExecutor.Execute[T](Func`1 action)
2018-02-19T13:19:27.3864541Z    at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Deployment.PowershellExecutor.Invoke(String errorContextMessage, Boolean writeResultToLog, Boolean isCancellable, ActionPreference errorActionPreference)<---
2018-02-19T13:19:27.3864541Z Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\Pester\lib\legacy\Gherkin.dll'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\Pester\Dependencies\Axiom\Axiom.psm1'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Verify-Equal'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Verify-True'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Verify-False'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Verify-Null'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Verify-NotNull'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Verify-Same'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Verify-NotSame'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Verify-Throw'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Verify-Type'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Verify-AssertionFailed'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z The 'Verify-AssertionFailed' command in the Axiom' module was imported, but because its name does not include an approved verb, it might be difficult to find. The suggested alternative verbs are "Test".
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Importing function 'Verify-AssertionFailed'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z The 'Verify-Equal' command in the Axiom' module was imported, but because its name does not include an approved verb, it might be difficult to find. The suggested alternative verbs are "Test".
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Importing function 'Verify-Equal'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z The 'Verify-False' command in the Axiom' module was imported, but because its name does not include an approved verb, it might be difficult to find. The suggested alternative verbs are "Test".
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Importing function 'Verify-False'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z The 'Verify-NotNull' command in the Axiom' module was imported, but because its name does not include an approved verb, it might be difficult to find. The suggested alternative verbs are "Test".
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Importing function 'Verify-NotNull'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z The 'Verify-NotSame' command in the Axiom' module was imported, but because its name does not include an approved verb, it might be difficult to find. The suggested alternative verbs are "Test".
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Importing function 'Verify-NotSame'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z The 'Verify-Null' command in the Axiom' module was imported, but because its name does not include an approved verb, it might be difficult to find. The suggested alternative verbs are "Test".
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Importing function 'Verify-Null'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z The 'Verify-Same' command in the Axiom' module was imported, but because its name does not include an approved verb, it might be difficult to find. The suggested alternative verbs are "Test".
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Importing function 'Verify-Same'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z The 'Verify-Throw' command in the Axiom' module was imported, but because its name does not include an approved verb, it might be difficult to find. The suggested alternative verbs are "Test".
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Importing function 'Verify-Throw'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z The 'Verify-True' command in the Axiom' module was imported, but because its name does not include an approved verb, it might be difficult to find. The suggested alternative verbs are "Test".
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Importing function 'Verify-True'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z The 'Verify-Type' command in the Axiom' module was imported, but because its name does not include an approved verb, it might be difficult to find. The suggested alternative verbs are "Test".
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Importing function 'Verify-Type'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Context'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Describe'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'In'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'It'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Mock'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Assert-VerifiableMock'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Assert-MockCalled'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Set-TestInconclusive'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Assert-VerifiableMocks'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'InModuleScope'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Invoke-Mock'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'New-Fixture'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Get-TestDriveItem'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Setup'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Should'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Invoke-Pester'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'BeforeEach'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'AfterEach'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'BeforeAll'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'AfterAll'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Set-DynamicParameterVariable'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Get-MockDynamicParameter'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'New-PesterOption'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'SafeGetCommand'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Invoke-Gherkin'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Find-GherkinStep'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'BeforeEachFeature'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'AfterEachFeature'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'BeforeEachScenario'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'AfterEachScenario'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'GherkinStep'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting alias 'Given'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting alias 'When'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting alias 'Then'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting alias 'And'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting alias 'But'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'Add-AssertionOperator'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'New-MockObject'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'EnterTestGroup'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'LeaveTestGroup'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'AddTestResult'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'AddSetupOrTeardownBlock'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'GetTestCaseSetupBlocks'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'GetTestCaseTeardownBlocks'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'GetCurrentTestGroupSetupBlocks'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'GetCurrentTestGroupTeardownBlocks'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'EnterTest'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting function 'LeaveTest'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting variable 'Strict'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting variable 'Show'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.3864541Z Exporting variable 'TagFilter'.
2018-02-19T13:19:27.3864541Z
2018-02-19T13:19:27.4027575Z Exporting variable 'ExcludeTagFilter'.
2018-02-19T13:19:27.4027575Z
2018-02-19T13:19:27.4027575Z Exporting variable 'TestNameFilter'.
2018-02-19T13:19:27.4027575Z
2018-02-19T13:19:27.4027575Z Exporting variable 'SessionState'.
2018-02-19T13:19:27.4027575Z
2018-02-19T13:19:27.4027575Z Exporting variable 'CommandCoverage'.
2018-02-19T13:19:27.4027575Z
2018-02-19T13:19:27.4027575Z Exporting variable 'InTest'.
2018-02-19T13:19:27.4027575Z
2018-02-19T13:19:27.4027575Z Exporting variable 'TestResult'.
2018-02-19T13:19:27.4027575Z
2018-02-19T13:19:27.4027575Z Exporting variable 'TotalCount'.
2018-02-19T13:19:27.4027575Z
2018-02-19T13:19:27.4027575Z Exporting variable 'Time'.
2018-02-19T13:19:27.4027575Z
2018-02-19T13:19:27.4027575Z Exporting variable 'PassedCount'.
2018-02-19T13:19:27.4027575Z
2018-02-19T13:19:27.4027575Z Exporting variable 'FailedCount'.
2018-02-19T13:19:27.4027575Z
2018-02-19T13:19:27.4027575Z Exporting variable 'SkippedCount'.
2018-02-19T13:19:27.4027575Z
2018-02-19T13:19:27.4027575Z Exporting variable 'PendingCount'.
2018-02-19T13:19:27.4027575Z
2018-02-19T13:19:27.4027575Z Exporting variable 'InconclusiveCount'.
2018-02-19T13:19:27.4027575Z
2018-02-19T13:19:27.4027575Z Exporting variable 'IncludeVSCodeMarker'.
2018-02-19T13:19:27.4027575Z
2018-02-19T13:19:27.4027575Z Exporting variable 'TestSuiteName'.
2018-02-19T13:19:27.4027575Z
2018-02-19T13:19:27.4027575Z Exporting variable 'TestActions'.
2018-02-19T13:19:27.4027575Z
2018-02-19T13:19:27.4027575Z Exporting variable 'TestGroupStack'.
2018-02-19T13:19:27.4027575Z
2018-02-19T13:19:27.4027575Z
2018-02-19T13:19:27.4027575Z
2018-02-19T13:19:27.4027575Z Deployment status for machine '**************.com:5985' : 'Failed'
2018-02-19T13:19:27.8083540Z ##[error]A command that prompts the user failed because the host program or the command type does not support user interaction. Try a host program that supports user interaction, such as the Windows PowerShell Console or Windows PowerShell ISE, and remove prompt-related commands from command types that do not support user interaction, such as Windows PowerShell workflows.

@bergmeister the task does not support the interactive commands execution. Could you please try to consider the option of invoking the pester with PassThru argument. Here you can find the details
https://github.com/pester/Pester/wiki/Invoke-Pester#example-5

@bergmeister are you got unblocked here

I am doing the remoting using Invoke-Command myself now as a workaround and there is no interactive command execution.

closing this as @bergmeister is not blocked on this. We will update this once new version of task is available


Deliver - submit for review

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
Complete output when running fastlane, including the stack trace and command used
I just tried to deliver with --submit_for_review parameter - which didn't work.
I tried it with different variations:
deliver --submit_for_review
deliver --skip_metadata --skip_screenshots --ipa fileToUpload.ipa --submit_for_review
deliver --ipa fileToUplaod.ipa --submit_for_review
in all cases - I get:
_[17:12:16]: Submitting the app for review...
[17:12:24]: Successfully submitted the app for review!
_
but when I get in to iTuneConnect - the app is still in "Prepare for Submission" status.
Another thing I noticed - there is no parameters for "What's New in This Version" and also parameters regarding submission: *Export Compliance, **Advertising Identifier
Or did I miss something?
Thanks.
Environment
deliver version: deliver 1.11.2
fastlane version (run fastlane -v): fastlane 1.81.0
Do you use bundler to execute fastlane (i.e. bundle exec fastlane)?
no.
Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)?
no.

@nAviram Great to hear from you again. Can you try setting this parameter to true rather than just including it as a flag? That should get you up and running 👍

@TKBurner  - I just tried now again, added this line with the flag to the Deliverfile:
_submit_for_review true
_
I run the deliver command - and the deliver started to run, all looking good (screenshots, metadata, etc') and even wrote the submission succeeded:
[18:07:28]: Saving changes
[18:07:42]: Successfully uploaded screenshots to iTunes Connect
[18:07:42]: Price Tier unchanged (tier 0)
[18:07:48]: Uploading app icon...
[18:07:56]: Finished the upload to iTunes Connect
[18:07:57]: Selecting the latest build...
[18:07:58]: Selecting build 1.6.3 (2)...
[18:07:59]: Successfully selected build
[18:07:59]: Submitting the app for review...
[18:08:06]: Successfully submitted the app for review!
BUT, than I go to the iTunesConnect - and the App is still on "Prepare for Submission" status :(

@nAviram Thanks for working with me. Can you add the --verbose flag on to the end of your command. I want to see what could be causing this issue. Thanks!

I tried it again with --verbose.
log is attached:
Log-submit_for_review.txt
And I want to rise my question once again - there is no parameters for "What's New in This Version" and also parameters regarding submission: Export Compliance, *Advertising Identifier...
I also noticed that there are 'missing beta entitlements' on the external testing status (I've opened another issue about it - regarding gym)

Hi @nAviram! Thanks for working with me. Have you tried deliver --submit_for review true?

still not working.
I run the command:
deliver --verbose --ipa /path/to/app/app.ipa --submit_for_review true

when I log in to iTunesConnect - it's still on "Prepare for Submission" status.

Hi @nAviram Thanks for following up. Can you run fastlane run update_fastlane? Also can you set force parameter to true?
Thanks! 👍

@nAviram
i had the same issue and it was because of missing submission_information
deliver(submission_information: {
      add_id_info_limits_tracking: true,
      add_id_info_serves_ads: true,
      add_id_info_tracks_action: true,
      add_id_info_tracks_install: true,
      add_id_info_uses_idfa: true,
      content_rights_has_rights: true,
      content_rights_contains_third_party_content: true,
      export_compliance_platform: 'ios',
      export_compliance_compliance_required: false,
      export_compliance_encryption_updated: false,
      export_compliance_app_type: nil,
      export_compliance_uses_encryption: false,
      export_compliance_is_exempt: false,
      export_compliance_contains_third_party_cryptography: false,
      export_compliance_contains_proprietary_cryptography: false,
      export_compliance_available_on_french_store: false
    });

and/or in deliverfile
submission_information({
      add_id_info_limits_tracking: true,
      add_id_info_serves_ads: true,
      add_id_info_tracks_action: true,
      add_id_info_tracks_install: true,
      add_id_info_uses_idfa: true,
      content_rights_has_rights: true,
      content_rights_contains_third_party_content: true,
      export_compliance_platform: 'ios',
      export_compliance_compliance_required: false,
      export_compliance_encryption_updated: false,
      export_compliance_app_type: nil,
      export_compliance_uses_encryption: false,
      export_compliance_is_exempt: false,
      export_compliance_contains_third_party_cryptography: false,
      export_compliance_contains_proprietary_cryptography: false,
      export_compliance_available_on_french_store: false
    });

you have to change the variables to fit your application ;).
the documentation about submission_information is here https://github.com/fastlane/fastlane/blob/master/deliver/Deliverfile.md#submission_information

OHHH!!!! THANK YOU!!!! how did I miss that?!
and I already asked twice about it (hmmm hmmm @TKBurner ) - because it makes no sense that this information is missing...
I'll try it out and update. THANKS again!

@nAviram Glad to hear you got up and running!
@hjanuschka Thanks for stepping in here. I really appreciate it 👍

Updating my submission_information seemed to fix the same issue for me, too. What I had was slightly outdated. So if you are hitting this and thinking to yourself "but I have my submission information set up already!"... double check.

@owurman Awesome! Really glad to hear you got up and running! 👍


[Bug] [master-server] master & work die quickly

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
Install the dolphin cluster. Then start-all.sh. jps found that work and server hang just after starting. Checked maser's logs and found that it could not register with zk. And the following error was reported.
Caused by: org.apache.zookeeper.KeeperException$UnimplementedException: KeeperErrorCode = Unimplemented for /dolphinscheduler/nodes/master
i checked the version. zk:3.4.14.   ds:3.1.3
What you expected to happen
the master and work shuold be start right
How to reproduce
let it start
Anything else
No response
Version
3.1.x
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

The 3.1.X version requires at least 3.5.X zookeeper version.

The 3.1.X version requires at least 3.5.X zookeeper version.

注册中心：ZooKeeper (3.4.6+)，下载地址
??plz updatad the doc


Pull Request: Integrate .env File Support and Add Backend Usage Example

Description
This pull request introduces two enhancements to the MindSearch project:

Environment Variables Configuration:

Added support for managing environment variables using a .env file.
Updated models.py to load environment variables using python-dotenv.
Modified GPT-4 and Silicon model configurations to use values from the .env file or defaults.
Updated .gitignore to exclude the .env file.
Updated requirements.txt to include python-dotenv.

Backend Usage Example:

Added backend_example.py to demonstrate how to interact with the backend directly, without using the frontend.

Changes

.env.example: Added with necessary environment variable placeholders.
.gitignore: Updated to exclude .env file.
README.md: Documented environment variable setup and backend usage example.
backend_example.py: New script for direct backend interaction.
models.py: Updated to load environment variables for model configurations.
requirements.txt: Added python-dotenv dependency.

How to Test

Setup Environment Variables:

Rename .env.example to .env and fill in the required values.

Run Backend Example:

Ensure the backend is running.
Execute python backend_example.py to test direct backend interaction.

Additional Information

This update simplifies the configuration process and provides an example for users who prefer backend interaction without a frontend.
Note: The README currently refers to this as a "forked version." If this pull request is accepted, I am happy to update the README to reflect the changes in the main repository.

Thanks for your contribution, we will review as soon as possible


Add SciPy 2024 abstract to docs

The abstract ended up being a nice high level overview so might as well include it.
Once the poster is finalized, I'll add it too.

Thanks Jared!


install from latest source

i used cargo to install lsd because i needed the -I flag and i read that this is only in the master branch and not yet released
i thought if i install it via cargo i will get the latest version but it also installs v 16
so... how to i install it from git ? there is nothing mentioned about that in the readme and i am not experienced in rust :)
btw thanks for this awesome project !

Hi @breuerfelix,
For what I know, if you run cargo install it will install you the latest tagged version and not the latest commit. I think you can use the --rev option in order to fetch a specific commit.
In you case it should give something like:
cargo install --rev c4d5f5ea0b1ee9ae549438b58df79f00fa209023

thanks for mentioning this !
i googled into this direction and got it working with:
cargo install --git https://github.com/Peltoche/lsd.git --branch master

i can create a PR today and add that to the readme if you like to :)


Switch MongoDB tests to use Docker

MongoDB is a binary server. The current log4j-mongodb tests download a generic binary MongoDB distribution and try to run it. The distribution is not self-contained and requires several libraries (e.g., OpenSSL) to be available on the target host.
Those libraries are not always available in the required version: e.g., currently MongoDB needs OpenSSL 1, but OpenSSL 3 is bundled in the most recent Debian.
This PR switches from the binary distribution to the usage of the latest Docker image available.
The advantages of this approach are:

We always test against the newest server version available.
The success of the tests does not depend on the libraries installed on the host.
Tests can run in parallel. In the current approach, parallel tests failed since each one tried to download MongoDB separately.

The main disadvantage is that Docker will be required to test log4j-mongodb. This is the case for the CI, but individual developers might need to install it too.
Fixes #2229.

Nice improvement @ppkarwasz 😀

Does it mean you approve? If not, what changes are you expecting?

Oh, tests are stuck, it must be Friday 13th again! :wink: