Cannot commission smart light example

ESP-IDF: v5.2.1
ESP-Matter: v1.2
Swift Toolchain: org.swift.59202406131a
Swift Version: 6.0-dev (LLVM 57177aa1b91540b, Swift 8be62863326595c)
Target: arm64-apple-macosx15.0
I setup my environment following the steps here
I then cloned the examples and followed the steps for the smart light example here
My ESP32C6 gets flashed and runs the example fine until I enter the setup code in the Home app then it encounters a Load Access Fault and restarts itself, the Home app then displays "Unable to Connect to Network" "Make sure the network can reach your accessory, reset the accessory and try adding to your home again"
Here is the output logs
🏎   Hello, Embedded Swift! (Smart Light)
I (676) led_driver_ws2812: Initializing light driver
I (676) led_driver_ws2812: led set r:0, g:0, b:0
I (706) pp: pp rom version: 5b8dcfa
I (706) net80211: net80211 rom version: 5b8dcfa
I (716) wifi:wifi driver task: 4083dac0, prio:23, stack:6656, core=0
I (716) wifi:wifi firmware version: a9f5b59
I (716) wifi:wifi certification version: v7.0
I (716) wifi:config NVS flash: enabled
I (726) wifi:config nano formating: disabled
I (726) wifi:mac_version:HAL_MAC_ESP32AX_761,ut_version:N
I (736) wifi:Init data frame dynamic rx buffer num: 32
I (736) wifi:Init static rx mgmt buffer num: 5
I (746) wifi:Init management short buffer num: 32
I (746) wifi:Init dynamic tx buffer num: 32
I (746) wifi:Init static tx FG buffer num: 2
I (756) wifi:Init static rx buffer size: 1700
I (756) wifi:Init static rx buffer num: 10
I (766) wifi:Init dynamic rx buffer num: 32
I (766) wifi_init: rx ba win: 6
I (766) wifi_init: tcpip mbox: 32
I (776) wifi_init: udp mbox: 6
I (776) wifi_init: tcp mbox: 6
I (786) wifi_init: tcp tx win: 5760
I (786) wifi_init: tcp rx win: 5760
I (786) wifi_init: tcp mss: 1440
I (796) wifi_init: WiFi IRAM OP enabled
I (796) wifi_init: WiFi RX IRAM OP enabled
I (826) chip[DL]: NVS set: chip-counters/reboot-count = 4 (0x4)
I (826) chip[DL]: Real time clock set to 946684800 (0100/00/01 00:00:00 UTC)
I (826) BLE_INIT: Using main XTAL as clock source
I (836) BLE_INIT: ble controller commit:[217f1bf]
I (836) phy_init: phy_version 250,e14681b,Jan 24 2024,17:43:11
I (896) phy: libbtbb version: 939f79c, Jan 24 2024, 17:43:26
I (896) NimBLE: GAP procedure initiated: stop advertising.

I (896) NimBLE: Failed to restore IRKs from store; status=8

I (906) CHIP[DL]: BLE host-controller synced
I (1406) chip[DL]: Configuring CHIPoBLE advertising (interval 25 ms, connectable)
I (1406) NimBLE: GAP procedure initiated: advertise;
I (1406) NimBLE: disc_mode=2
I (1406) NimBLE:  adv_channel_map=0 own_addr_type=1 adv_filter_policy=0 adv_itvl_min=40 adv_itvl_max=40
I (1416) NimBLE:

I (1426) chip[DL]: CHIPoBLE advertising started
I (1426) chip[DL]: Starting ESP WiFi layer
W (1436) wifi:(bf)761:0x600a7cac:0x01b4b4b0
W (1436) wifi:(agc)0x600a7128:0xd203b800, min.avgNF:0xce->0xd2(dB), RCalCount:0x3b, min.RRssi:0x800(-128.00)
W (1446) wifi:(TB)WDEV_PWR_TB_MCS0:19
W (1446) wifi:(TB)WDEV_PWR_TB_MCS1:19
W (1456) wifi:(TB)WDEV_PWR_TB_MCS2:19
W (1456) wifi:(TB)WDEV_PWR_TB_MCS3:19
W (1456) wifi:(TB)WDEV_PWR_TB_MCS4:19
W (1466) wifi:(TB)WDEV_PWR_TB_MCS5:19
W (1466) wifi:(TB)WDEV_PWR_TB_MCS6:18
W (1466) wifi:(TB)WDEV_PWR_TB_MCS7:18
W (1476) wifi:(TB)WDEV_PWR_TB_MCS8:17
W (1476) wifi:(TB)WDEV_PWR_TB_MCS9:15
W (1476) wifi:(TB)WDEV_PWR_TB_MCS10:15
W (1486) wifi:(TB)WDEV_PWR_TB_MCS11:15
I (1486) wifi:11ax coex: WDEVAX_PTI0(0x55777555), WDEVAX_PTI1(0x00003377).

I (1496) wifi:mode : sta (60:55:f9:f7:29:34)
I (1496) wifi:enable tsf
W (1496) wifi:Haven't to connect to a suitable AP now!
I (1506) chip[DL]: Done driving station state, nothing else to do...
W (1506) wifi:Haven't to connect to a suitable AP now!
I (1516) chip[DL]: Done driving station state, nothing else to do...
I (1526) chip[SVR]: Initializing subscription resumption storage...
I (1526) chip[SVR]: Server initializing...
I (1536) chip[TS]: Last Known Good Time: 2023-10-14T01:16:48
I (1536) chip[DMG]: AccessControl: initializing
I (1546) chip[DMG]: Examples::AccessControlDelegate::Init
I (1556) chip[DMG]: AccessControl: setting
I (1556) chip[DMG]: DefaultAclStorage: initializing
I (1566) chip[DMG]: DefaultAclStorage: 0 entries loaded
I (1576) chip[ZCL]: Using ZAP configuration...
I (1576) esp_matter_cluster: Cluster plugin init common callback
I (1576) chip[DMG]: AccessControlCluster: initializing
I (1586) chip[ZCL]: 0x421357a8ep 0 clus 0x0000_0030 attr 0x0000_0000 not supported
I (1596) chip[ZCL]: Initiating Admin Commissioning cluster.
I (1606) chip[DIS]: Updating services using commissioning mode 1
I (1606) chip[DIS]: CHIP minimal mDNS started advertising.
I (1616) chip[DIS]: Advertise commission parameter vendorID=65521 productID=32768 discriminator=3840/15 cm=1
I (1626) chip[DIS]: CHIP minimal mDNS configured as 'Commissionable node device'; instance name: 093C757B250575F9.
I (1636) chip[DIS]: mDNS service published: _matterc._udp
I (1636) chip[IN]: CASE Server enabling CASE session setups
I (1646) chip[SVR]: Joining Multicast groups
I (1656) chip[SVR]: Server Listening...
I (1656) esp_matter_core: Dynamic endpoint 0 added
I (1666) esp_matter_attribute: ********** W : Endpoint 0x0001's Cluster 0x00000003's Attribute 0x00000001 is 0 **********
lightEndpoint.eventHandler:
unknown
0
I (1676) esp_matter_attribute: ********** W : Endpoint 0x0001's Cluster 0x00000004's Attribute 0x00000000 is 128 **********
lightEndpoint.eventHandler:
unknown
128
I (1696) esp_matter_attribute: ********** W : Endpoint 0x0001's Cluster 0x00000004's Attribute 0x0000FFFC is <invalid type: 0> **********
I (1706) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000006's Attribute 0x0000FFFC is 1 **********
I (1716) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000006's Attribute 0x00004003 is 0 **********
I (1726) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000006's Attribute 0x00000000 is 0 **********
I (1736) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000006's Attribute 0x00000000 is 0 **********
I (1756) chip[ZCL]: Endpoint 1 On/off already set to new value
I (1756) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000008's Attribute 0x00000002 is 1 **********
I (1766) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000008's Attribute 0x00000003 is 254 **********
I (1786) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000008's Attribute 0x0000FFFC is 3 **********
I (1796) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000008's Attribute 0x00000000 is 64 **********
I (1806) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000008's Attribute 0x00004000 is 64 **********
I (1816) esp_matter_attribute: ********** W : Endpoint 0x0001's Cluster 0x00000008's Attribute 0x00000000 is 64 **********
lightEndpoint.eventHandler:
levelControl
64
I (1836) led_driver_ws2812: led set r:63, g:63, b:63
I (1836) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000300's Attribute 0x00004010 is 250 **********
I (1846) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000300's Attribute 0x00000007 is 250 **********
I (1866) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000300's Attribute 0x0000400B is 0 **********
I (1876) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000300's Attribute 0x0000400C is 65279 **********
I (1886) esp_matter_attribute: ********** W : Endpoint 0x0001's Cluster 0x00000300's Attribute 0x00000007 is 250 **********
lightEndpoint.eventHandler:
colorControl(colorTemperatureMireds)
250
I (1906) led_driver_ws2812: led set r:63, g:51, b:40
I (1906) esp_matter_attribute: ********** W : Endpoint 0x0001's Cluster 0x00000300's Attribute 0x00000008 is 2 **********
lightEndpoint.eventHandler:
colorControl(colorMode)
2
I (1926) esp_matter_attribute: ********** W : Endpoint 0x0001's Cluster 0x00000300's Attribute 0x00004001 is 2 **********
I (1936) esp_matter_core: Dynamic endpoint 1 added
I (1946) chip[DL]: WIFI_EVENT_STA_START
W (1946) wifi:Haven't to connect to a suitable AP now!
I (1956) chip[DL]: Done driving station state, nothing else to do...
I (1956) chip[DL]: Configuring CHIPoBLE advertising (interval 25 ms, connectable)
I (1966) chip[DL]: Device already advertising, stop active advertisement and restart
I (1976) NimBLE: GAP procedure initiated: stop advertising.

I (1986) NimBLE: GAP procedure initiated: advertise;
I (1986) NimBLE: disc_mode=2
I (1996) NimBLE:  adv_channel_map=0 own_addr_type=1 adv_filter_policy=0 adv_itvl_min=40 adv_itvl_max=40
I (2006) NimBLE:

I (2006) main_task: Returned from app_main()
I (7086) chip[DL]: BLE GAP connection established (con 1)
I (7096) chip[DL]: CHIPoBLE advertising stopped
I (7796) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 16
I (7796) chip[BLE]: local and remote recv window sizes = 5
I (7796) chip[BLE]: selected BTP version 4
I (7806) chip[BLE]: using BTP fragment sizes rx 244 / tx 244.
I (7976) chip[DL]: Write request/command received for CHIPoBLE TX CCCD characteristic (con 1 ) indicate = 1
I (7976) chip[DL]: CHIPoBLE subscribe received
I (7976) NimBLE: GATT procedure initiated: indicate;
I (7986) NimBLE: att_handle=18

I (8016) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (8016) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 16
I (8026) chip[EM]: >>> [E:58064r S:0 M:97973608] (U) Msg RX from 0:E718CD1E08D6E3CA [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)
I (8046) chip[EM]: <<< [E:58064r S:0 M:227999118] (U) Msg TX to 0:0000000000000000 [0000] [BLE] --- Type 0000:21 (SecureChannel:PBKDFParamResponse)
I (8056) NimBLE: GATT procedure initiated: indicate;
I (8056) NimBLE: att_handle=18

I (8066) chip[SVR]: Commissioning session establishment step started
I (8106) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (8106) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 16
I (8116) chip[EM]: >>> [E:58064r S:0 M:97973609] (U) Msg RX from 0:E718CD1E08D6E3CA [0000] --- Type 0000:22 (SecureChannel:PASE_Pake1)
I (8186) chip[EM]: <<< [E:58064r S:0 M:227999119] (U) Msg TX to 0:0000000000000000 [0000] [BLE] --- Type 0000:23 (SecureChannel:PASE_Pake2)
I (8186) NimBLE: GATT procedure initiated: indicate;
I (8196) NimBLE: att_handle=18

I (8246) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (8246) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 16
I (8256) chip[EM]: >>> [E:58064r S:0 M:97973610] (U) Msg RX from 0:E718CD1E08D6E3CA [0000] --- Type 0000:24 (SecureChannel:PASE_Pake3)
I (8266) chip[EM]: <<< [E:58064r S:0 M:227999120] (U) Msg TX to 0:0000000000000000 [0000] [BLE] --- Type 0000:40 (SecureChannel:StatusReport)
I (8276) NimBLE: GATT procedure initiated: indicate;
I (8286) NimBLE: att_handle=18

I (8286) chip[SC]: SecureSession[0x40822b00, LSID:40926]: State change 'kEstablishing' --> 'kActive'
I (8296) chip[SVR]: Commissioning completed session establishment step
I (8306) chip[DIS]: Updating services using commissioning mode 0
I (8306) chip[DIS]: CHIP minimal mDNS started advertising.
I (8316) chip[DIS]: Advertise commission parameter vendorID=65521 productID=32768 discriminator=3840/15 cm=0
I (8326) chip[DIS]: CHIP minimal mDNS configured as 'Commissionable node device'; instance name: 093C757B250575F9.
I (8336) chip[DIS]: mDNS service published: _matterc._udp
I (8346) chip[SVR]: Device completed Rendezvous process
I (8316) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (8356) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 16
I (8366) chip[EM]: >>> [E:58065r S:40926 M:200157078] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (8386) chip[EM]: <<< [E:58065r S:40926 M:202262816] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [BLE] --- Type 0001:05 (IM:ReportData)
I (8396) NimBLE: GATT procedure initiated: indicate;
I (8396) NimBLE: att_handle=18

I (8446) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (8446) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 16
I (8456) chip[EM]: >>> [E:58066r S:40926 M:200157079] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (8466) chip[EM]: <<< [E:58066r S:40926 M:202262817] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [BLE] --- Type 0001:05 (IM:ReportData)
I (8476) NimBLE: GATT procedure initiated: indicate;
I (8486) NimBLE: att_handle=18

I (8516) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (8516) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 16
I (8526) chip[EM]: >>> [E:58067r S:40926 M:200157080] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (8536) chip[EM]: <<< [E:58067r S:40926 M:202262818] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [BLE] --- Type 0001:05 (IM:ReportData)
I (8546) NimBLE: GATT procedure initiated: indicate;
I (8556) NimBLE: att_handle=18

I (8586) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (8586) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 16
I (8586) chip[EM]: >>> [E:58068r S:40926 M:200157081] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (8606) chip[EM]: <<< [E:58068r S:40926 M:202262819] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [BLE] --- Type 0001:05 (IM:ReportData)
I (8616) NimBLE: GATT procedure initiated: indicate;
I (8616) NimBLE: att_handle=18

I (8646) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (8646) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 16
I (8656) chip[EM]: >>> [E:58069r S:40926 M:200157082] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (8666) chip[EM]: <<< [E:58069r S:40926 M:202262820] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [BLE] --- Type 0001:05 (IM:ReportData)
I (8676) NimBLE: GATT procedure initiated: indicate;
I (8686) NimBLE: att_handle=18

I (8766) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (8766) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 16
I (8766) chip[EM]: >>> [E:58070r S:40926 M:200157083] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (8786) esp_matter_attribute: ********** R : Endpoint 0x0000's Cluster 0x00000030's Attribute 0x00000000 is 0 **********
I (8796) chip[EM]: <<< [E:58070r S:40926 M:202262821] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [BLE] --- Type 0001:05 (IM:ReportData)
I (8806) NimBLE: GATT procedure initiated: indicate;
I (8806) NimBLE: att_handle=18

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

I (8896) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (8896) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 16
I (8906) chip[EM]: >>> [E:58071r S:40926 M:200157084] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (8916) chip[EM]: <<< [E:58071r S:40926 M:202262822] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [BLE] --- Type 0001:05 (IM:ReportData)
I (8926) NimBLE: GATT procedure initiated: indicate;
I (8936) NimBLE: att_handle=18

I (8966) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (8966) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 16
I (8976) chip[EM]: >>> [E:58072r S:40926 M:200157085] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (8986) esp_matter_command: Received command 0x00000000 for endpoint 0x0000's cluster 0x00000030
I (8996) chip[FS]: GeneralCommissioning: Received ArmFailSafe (60s)
I (8996) esp_matter_attribute: ********** W : Endpoint 0x0000's Cluster 0x00000030's Attribute 0x00000000 is 4 **********
Guru Meditation Error: Core  0 panic'ed (Load access fault). Exception was unhandled.

Stack dump detected
Core  0 register dump:
MEPC    : 0x4200af3a  RA      : 0x4200b3be  SP      : 0x408468c0  GP      : 0x4081ae30
0x4200af3a: $s10__idf_main6MatterO4NodeC12eventHandler4type8endpoint7cluster9attribute5valueyAA0C14AttributeEventO_AA8EndpointVAA7ClusterVs6UInt32VSpySo21esp_matter_attr_val_taGSgtF at ??:?
0x4200b3be: $s10__idf_main8RootNodeV9attribute8identifyACSgyAA20MatterAttributeEventO_AA8EndpointVAA7ClusterVs6UInt32VSpySo21esp_matter_attr_val_taGSgtc_ySo0m1_N0O14identificationO13callback_typeV_s6UInt16Vs5UInt8VA0_tctcfcs5Int32VAtDOAWV_Az2nRSvSgtcfU_ at ??:?

TP      : 0x4080cb4c  T0      : 0x4200fcc4  T1      : 0x0000000f  T2      : 0xffffffff
0x4080cb4c: xQueueGiveFromISR at /Users/jnbra/esp/esp-idf/components/freertos/FreeRTOS-Kernel/queue.c:1347
0x4200fcc4: MatterPostAttributeChangeCallback(chip::app::ConcreteAttributePath const&, unsigned char, unsigned short, unsigned char*) at /Users/jnbra/esp/esp-matter/components/esp_matter/esp_matter_attribute_utils.cpp:2044

S0/FP   : 0x40835394  S1      : 0x00000001  A0      : 0x00000001  A1      : 0x408353b0
A2      : 0x40835bec  A3      : 0x00000000  A4      : 0x40846958  A5      : 0x40834b80
A6      : 0x4200b3e4  A7      : 0x4084f570  S2      : 0x00000000  S3      : 0x40835bec
0x4200b3e4: $s10__idf_main8RootNodeV9attribute8identifyACSgyAA20MatterAttributeEventO_AA8EndpointVAA7ClusterVs6UInt32VSpySo21esp_matter_attr_val_taGSgtc_ySo0m1_N0O14identificationO13callback_typeV_s6UInt16Vs5UInt8VA0_tctcfcs5Int32VAtDOAWV_Az2nRSvSgtcfU_To at ??:?

S4      : 0x40846958  S5      : 0x408353b0  S6      : 0x00000001  S7      : 0x00000000
S8      : 0x00000000  S9      : 0x4213c144  S10     : 0x40846e40  S11     : 0x00000000
T3      : 0x00000024  T4      : 0x00000080  T5      : 0x00000040  T6      : 0xdfffffff
MSTATUS : 0x00001881  MTVEC   : 0x40800001  MCAUSE  : 0x00000005  MTVAL   : 0x00000008
0x40800001: _vector_table at ??:?

MHARTID : 0x00000000

Backtrace:

0x4200af3a in $s10__idf_main6MatterO4NodeC12eventHandler4type8endpoint7cluster9attribute5valueyAA0C14AttributeEventO_AA8EndpointVAA7ClusterVs6UInt32VSpySo21esp_matter_attr_val_taGSgtF ()
#0  0x4200af3a in $s10__idf_main6MatterO4NodeC12eventHandler4type8endpoint7cluster9attribute5valueyAA0C14AttributeEventO_AA8EndpointVAA7ClusterVs6UInt32VSpySo21esp_matter_attr_val_taGSgtF ()
#1  0x4200b3be in $s10__idf_main8RootNodeV9attribute8identifyACSgyAA20MatterAttributeEventO_AA8EndpointVAA7ClusterVs6UInt32VSpySo21esp_matter_attr_val_taGSgtc_ySo0m1_N0O14identificationO13callback_typeV_s6UInt16Vs5UInt8VA0_tctcfcs5Int32VAtDOAWV_Az2nRSvSgtcfU_ ()
Backtrace stopped: frame did not save the PC
ELF file SHA256: 4bb77fb8b

I (2656) esp_core_dump_flash: Save core dump to flash...
I (2662) esp_core_dump_flash: Erase flash 12288 bytes @ 0x3e6000
I (2766) esp_core_dump_flash: Write end offset 0x2684, check sum length 4
I (2766) esp_core_dump_flash: Core dump has been saved to flash.
Rebooting...
ESP-ROM:esp32c6-20220919
Build:Sep 19 2022
rst:0xc (SW_CPU),boot:0xc (SPI_FAST_FLASH_BOOT)
Saved PC:0x4001975a
0x4001975a: software_reset_cpu in ROM

SPIWP:0xee
mode:DIO, clock div:2
load:0x40875720,len:0x1804
load:0x4086c410,len:0xe58
load:0x4086e610,len:0x2e20
entry 0x4086c41a
I (26) boot: ESP-IDF v5.2.1 2nd stage bootloader
I (27) boot: compile time Jun 24 2024 16:08:15
I (28) boot: chip revision: v0.0
I (30) boot.esp32c6: SPI Speed      : 80MHz
I (34) boot.esp32c6: SPI Mode       : DIO
I (39) boot.esp32c6: SPI Flash Size : 4MB
I (44) boot: Enabling RNG early entropy source...
I (50) boot: Partition Table:
I (53) boot: ## Label            Usage          Type ST Offset   Length
I (60) boot:  0 esp_secure_cert  unknown          3f 06 0000d000 00002000
I (68) boot:  1 nvs              WiFi data        01 02 00010000 0000c000
I (75) boot:  2 nvs_keys         NVS keys         01 04 0001c000 00001000
I (83) boot:  3 otadata          OTA data         01 00 0001d000 00002000
I (90) boot:  4 phy_init         RF data          01 01 0001f000 00001000
I (97) boot:  5 ota_0            OTA app          00 10 00020000 001e0000
I (105) boot:  6 ota_1            OTA app          00 11 00200000 001e0000
I (112) boot:  7 fctry            WiFi data        01 02 003e0000 00006000
I (120) boot:  8 coredump         Unknown data     01 03 003e6000 00010000
I (128) boot: End of partition table
I (132) esp_image: segment 0: paddr=00020020 vaddr=42130020 size=3cb28h (248616) map
I (242) esp_image: segment 1: paddr=0005cb50 vaddr=40800000 size=034c8h ( 13512) load
I (250) esp_image: segment 2: paddr=00060020 vaddr=42000020 size=12d4bch (1234108) map
I (753) esp_image: segment 3: paddr=0018d4e4 vaddr=408034c8 size=17164h ( 94564) load
I (798) esp_image: segment 4: paddr=001a4650 vaddr=4081a630 size=04f58h ( 20312) load
I (822) boot: Loaded app from partition at offset 0x20000
I (823) boot: Disabling RNG early entropy source...
I (834) cpu_start: Unicore app
W (844) clk: esp_perip_clk_init() has not been implemented yet
I (850) cpu_start: Pro cpu start user code
I (850) cpu_start: cpu freq: 160000000 Hz
I (850) cpu_start: Application information:
I (853) cpu_start: Project name:     light
I (858) cpu_start: App version:      1.0
I (863) cpu_start: Compile time:     Jun 24 2024 16:07:54
I (869) cpu_start: ELF file SHA256:  4bb77fb8b...
I (874) cpu_start: ESP-IDF:          v5.2.1
I (879) cpu_start: Min chip rev:     v0.0
I (884) cpu_start: Max chip rev:     v0.99
I (888) cpu_start: Chip rev:         v0.0
I (893) heap_init: Initializing. RAM available for dynamic allocation:
I (900) heap_init: At 40830B30 len 0004BAE0 (302 KiB): RAM
I (906) heap_init: At 4087C610 len 00002F54 (11 KiB): RAM
I (913) heap_init: At 50000000 len 00003FE8 (15 KiB): RTCRAM
I (920) spi_flash: detected chip: generic
I (924) spi_flash: flash io: dio
W (927) spi_flash: Detected size(8192k) larger than the size in the binary image header(4096k). Using the size in the binary image header.
W (941) rmt(legacy): legacy driver is deprecated, please migrate to `driver/rmt_tx.h` and/or `driver/rmt_rx.h`
I (952) sleep: Configure to isolate all GPIO pins in sleep state
I (958) sleep: Enable automatic switching of GPIO sleep configuration
I (965) esp_core_dump_flash: Init core dump to flash
I (971) esp_core_dump_flash: Found partition 'coredump' @ 3e6000 65536 bytes
I (988) esp_core_dump_flash: Core dump data checksum is correct
I (988) esp_core_dump_flash: Found core dump 9860 bytes in flash @ 0x3e6000
I (993) coexist: coex firmware version: 77cd7f8
I (998) coexist: coexist rom version 5b8dcfa
I (1003) main_task: Started on CPU0
I (1003) main_task: Calling app_main()
🏎   Hello, Embedded Swift! (Smart Light)
I (1013) led_driver_ws2812: Initializing light driver
I (1013) led_driver_ws2812: led set r:0, g:0, b:0
I (1043) pp: pp rom version: 5b8dcfa
I (1043) net80211: net80211 rom version: 5b8dcfa
I (1053) wifi:wifi driver task: 4083dac0, prio:23, stack:6656, core=0
I (1053) wifi:wifi firmware version: a9f5b59
I (1053) wifi:wifi certification version: v7.0
I (1063) wifi:config NVS flash: enabled
I (1063) wifi:config nano formating: disabled
I (1063) wifi:mac_version:HAL_MAC_ESP32AX_761,ut_version:N
I (1073) wifi:Init data frame dynamic rx buffer num: 32
I (1073) wifi:Init static rx mgmt buffer num: 5
I (1083) wifi:Init management short buffer num: 32
I (1083) wifi:Init dynamic tx buffer num: 32
I (1093) wifi:Init static tx FG buffer num: 2
I (1093) wifi:Init static rx buffer size: 1700
I (1093) wifi:Init static rx buffer num: 10
I (1103) wifi:Init dynamic rx buffer num: 32
I (1103) wifi_init: rx ba win: 6
I (1113) wifi_init: tcpip mbox: 32
I (1113) wifi_init: udp mbox: 6
I (1113) wifi_init: tcp mbox: 6
I (1123) wifi_init: tcp tx win: 5760
I (1123) wifi_init: tcp rx win: 5760
I (1133) wifi_init: tcp mss: 1440
I (1133) wifi_init: WiFi IRAM OP enabled
I (1133) wifi_init: WiFi RX IRAM OP enabled
I (1163) chip[DL]: NVS set: chip-counters/reboot-count = 5 (0x5)
I (1163) chip[DL]: Real time clock set to 946684800 (0100/00/01 00:00:00 UTC)
I (1163) BLE_INIT: Using main XTAL as clock source
I (1173) BLE_INIT: ble controller commit:[217f1bf]
I (1173) phy_init: phy_version 250,e14681b,Jan 24 2024,17:43:11
I (1233) phy: libbtbb version: 939f79c, Jan 24 2024, 17:43:26
I (1233) NimBLE: GAP procedure initiated: stop advertising.

I (1233) NimBLE: Failed to restore IRKs from store; status=8

I (1243) CHIP[DL]: BLE host-controller synced
I (1743) chip[DL]: Configuring CHIPoBLE advertising (interval 25 ms, connectable)
I (1743) NimBLE: GAP procedure initiated: advertise;
I (1743) NimBLE: disc_mode=2
I (1743) NimBLE:  adv_channel_map=0 own_addr_type=1 adv_filter_policy=0 adv_itvl_min=40 adv_itvl_max=40
I (1753) NimBLE:

I (1763) chip[DL]: CHIPoBLE advertising started
I (1763) chip[DL]: Starting ESP WiFi layer
W (1773) wifi:(bf)761:0x600a7cac:0x01b4b4b0
W (1773) wifi:(agc)0x600a7128:0xd21c9b8a, min.avgNF:0xce->0xd2(dB), RCalCount:0x1c9, min.RRssi:0xb8a(-71.38)
W (1783) wifi:(TB)WDEV_PWR_TB_MCS0:19
W (1783) wifi:(TB)WDEV_PWR_TB_MCS1:19
W (1793) wifi:(TB)WDEV_PWR_TB_MCS2:19
W (1793) wifi:(TB)WDEV_PWR_TB_MCS3:19
W (1793) wifi:(TB)WDEV_PWR_TB_MCS4:19
W (1803) wifi:(TB)WDEV_PWR_TB_MCS5:19
W (1803) wifi:(TB)WDEV_PWR_TB_MCS6:18
W (1803) wifi:(TB)WDEV_PWR_TB_MCS7:18
W (1813) wifi:(TB)WDEV_PWR_TB_MCS8:17
W (1813) wifi:(TB)WDEV_PWR_TB_MCS9:15
W (1813) wifi:(TB)WDEV_PWR_TB_MCS10:15
W (1823) wifi:(TB)WDEV_PWR_TB_MCS11:15
I (1823) wifi:11ax coex: WDEVAX_PTI0(0x55777555), WDEVAX_PTI1(0x00003377).

I (1833) wifi:mode : sta (60:55:f9:f7:29:34)
I (1833) wifi:enable tsf
W (1833) wifi:Haven't to connect to a suitable AP now!
I (1843) chip[DL]: Done driving station state, nothing else to do...
W (1843) wifi:Haven't to connect to a suitable AP now!
I (1853) chip[DL]: Done driving station state, nothing else to do...
I (1863) chip[SVR]: Initializing subscription resumption storage...
I (1863) chip[SVR]: Server initializing...
I (1873) chip[TS]: Last Known Good Time: 2023-10-14T01:16:48
I (1873) chip[DMG]: AccessControl: initializing
I (1883) chip[DMG]: Examples::AccessControlDelegate::Init
I (1893) chip[DMG]: AccessControl: setting
I (1893) chip[DMG]: DefaultAclStorage: initializing
I (1903) chip[DMG]: DefaultAclStorage: 0 entries loaded
I (1913) chip[ZCL]: Using ZAP configuration...
I (1913) esp_matter_cluster: Cluster plugin init common callback
I (1913) chip[DMG]: AccessControlCluster: initializing
I (1923) chip[ZCL]: 0x421357a8ep 0 clus 0x0000_0030 attr 0x0000_0000 not supported
I (1933) chip[ZCL]: Initiating Admin Commissioning cluster.
I (1943) chip[DIS]: Updating services using commissioning mode 1
I (1943) chip[DIS]: CHIP minimal mDNS started advertising.
I (1953) chip[DIS]: Advertise commission parameter vendorID=65521 productID=32768 discriminator=3840/15 cm=1
I (1963) chip[DIS]: CHIP minimal mDNS configured as 'Commissionable node device'; instance name: 8E237CF666682BC5.
I (1973) chip[DIS]: mDNS service published: _matterc._udp
I (1973) chip[IN]: CASE Server enabling CASE session setups
I (1983) chip[SVR]: Joining Multicast groups
I (1993) chip[SVR]: Server Listening...
I (1993) esp_matter_core: Dynamic endpoint 0 added
I (2003) esp_matter_attribute: ********** W : Endpoint 0x0001's Cluster 0x00000003's Attribute 0x00000001 is 0 **********
lightEndpoint.eventHandler:
unknown
0
I (2013) esp_matter_attribute: ********** W : Endpoint 0x0001's Cluster 0x00000004's Attribute 0x00000000 is 128 **********
lightEndpoint.eventHandler:
unknown
128
I (2033) esp_matter_attribute: ********** W : Endpoint 0x0001's Cluster 0x00000004's Attribute 0x0000FFFC is <invalid type: 0> **********
I (2043) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000006's Attribute 0x0000FFFC is 1 **********
I (2053) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000006's Attribute 0x00004003 is 0 **********
I (2063) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000006's Attribute 0x00000000 is 0 **********
I (2073) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000006's Attribute 0x00000000 is 0 **********
I (2093) chip[ZCL]: Endpoint 1 On/off already set to new value
I (2093) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000008's Attribute 0x00000002 is 1 **********
I (2103) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000008's Attribute 0x00000003 is 254 **********
I (2123) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000008's Attribute 0x0000FFFC is 3 **********
I (2133) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000008's Attribute 0x00000000 is 64 **********
I (2143) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000008's Attribute 0x00004000 is 64 **********
I (2153) esp_matter_attribute: ********** W : Endpoint 0x0001's Cluster 0x00000008's Attribute 0x00000000 is 64 **********
lightEndpoint.eventHandler:
levelControl
64
I (2173) led_driver_ws2812: led set r:63, g:63, b:63
I (2173) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000300's Attribute 0x00004010 is 250 **********
I (2183) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000300's Attribute 0x00000007 is 250 **********
I (2203) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000300's Attribute 0x0000400B is 0 **********
I (2213) esp_matter_attribute: ********** R : Endpoint 0x0001's Cluster 0x00000300's Attribute 0x0000400C is 65279 **********
I (2223) esp_matter_attribute: ********** W : Endpoint 0x0001's Cluster 0x00000300's Attribute 0x00000007 is 250 **********
lightEndpoint.eventHandler:
colorControl(colorTemperatureMireds)
250
I (2243) led_driver_ws2812: led set r:63, g:51, b:40
I (2243) esp_matter_attribute: ********** W : Endpoint 0x0001's Cluster 0x00000300's Attribute 0x00000008 is 2 **********
lightEndpoint.eventHandler:
colorControl(colorMode)
2
I (2263) esp_matter_attribute: ********** W : Endpoint 0x0001's Cluster 0x00000300's Attribute 0x00004001 is 2 **********
I (2273) esp_matter_core: Dynamic endpoint 1 added
I (2283) chip[DL]: WIFI_EVENT_STA_START
W (2283) wifi:Haven't to connect to a suitable AP now!
I (2293) chip[DL]: Done driving station state, nothing else to do...
I (2293) chip[DL]: Configuring CHIPoBLE advertising (interval 25 ms, connectable)
I (2303) chip[DL]: Device already advertising, stop active advertisement and restart
I (2313) NimBLE: GAP procedure initiated: stop advertising.

I (2323) NimBLE: GAP procedure initiated: advertise;
I (2323) NimBLE: disc_mode=2
I (2333) NimBLE:  adv_channel_map=0 own_addr_type=1 adv_filter_policy=0 adv_itvl_min=40 adv_itvl_max=40
I (2343) NimBLE:

I (2343) main_task: Returned from app_main()
I (31943) chip[DL]: Configuring CHIPoBLE advertising (interval 500 ms, connectable)
I (31943) chip[DL]: Device already advertising, stop active advertisement and restart
I (31943) NimBLE: GAP procedure initiated: stop advertising.

I (31953) NimBLE: GAP procedure initiated: advertise;
I (31953) NimBLE: disc_mode=2
I (31963) NimBLE:  adv_channel_map=0 own_addr_type=1 adv_filter_policy=0 adv_itvl_min=800 adv_itvl_max=800
I (31973) NimBLE:

Since the ESP32C6 only supports 2.4Ghz I have tried disabling both the 5Ghz and 6Ghz networks on my router but to no avail, I was however able to get it commissioned with Espressif's own matter light example even when the 5Ghz & 6Ghz networks were enabled.
Any help would be greatly appreciated!

I also have this issue. Followed the guide to the dot and unable to connect but ESP Launch Pad works flawlessly.

I got stuck at this point as well. I noticed in the WWDC video that they had pre-connected to Matter. This makes me wonder if this is a known issue.

I was wondering if this perhaps could be due to there not being a Threads Border router in the network?

I have a thread border router on my network and I still have this issue.

I got stuck at this point as well. I noticed in the WWDC video that they had pre-connected to Matter. This makes me wonder if this is a known issue.

I put together the tutorial while following the exact steps listed in it. The setup I used was an Airport Express (2012), a HomePod (2018) both updated to the latest firmware and an iPhone running the latest version of iOS 17 at the time. All devices were setup from scratch.
Note: I did end up using idf.py erase-flash at least once to restart the paring process from scratch.
The original post in this thread does include a crash in the log which is definitely interesting and not something I encountered.
0x4200af3a: $s10__idf_main6MatterO4NodeC12eventHandler4type8endpoint7cluster9attribute5valueyAA0C14AttributeEventO_AA8EndpointVAA7ClusterVs6UInt32VSpySo21esp_matter_attr_val_taGSgtF at ??:?
0x4200b3be: $s10__idf_main8RootNodeV9attribute8identifyACSgyAA20MatterAttributeEventO_AA8EndpointVAA7ClusterVs6UInt32VSpySo21esp_matter_attr_val_taGSgtc_ySo0m1_N0O14identificationO13callback_typeV_s6UInt16Vs5UInt8VA0_tctcfcs5Int32VAtDOAWV_Az2nRSvSgtcfU_ at ??:?

Hopefully I or someone else can try to find time next week to reproduce this crash and see if it the root issue.

Same problem with same logs here...

I have got the same problem but it seems that the issue is with Swifts automatic resource management.
When running the example, I noticed the message app_main() finished.
From the Backtrace i suspect the error to be in this code snippet
struct RootNode {
  init?(attribute: @escaping AttributeCallback, identify: @escaping identifyCallback) {
    [...]

    let context = Context(attribute: attribute, identify: identify)
    withUnsafeMutablePointer(to: &nodeConfig.root_node)
      // Transfer ownership to the node. This is a leak for now, but we don't expect nodes to be created and destroyed repeatedly.
      _ = esp_matter.endpoint.root_node.create(node, $0, 0x00, Unmanaged.passRetained(context).toOpaque())
    }

    [...]
  }
}

(Disclaimer: I don't know anything about this kind of debugging, this is just an uneducated guess based on the readable words in the trace)
Because the example finished app_main() without errors, this code is not outright flawed but probably more subtile.
If app_main() finishes, all local variables declared would get wiped, including the app and led-objects. Passing references to these objects (or parts of it) back to the idf-matter library would result in chaos. And indeed, in the Matter-wrapper-code the cleanup is prevented by throwing Unmanaged.passRetained() at everything and a healthy memory leak but it'll be fine-comment.
To get around Swifts Resource Management I just appended a while true { sleep(1) } to the app_main(). After that, i was able to see the glory that is Matter Accessory Connection in HomeKit and finally a working Matter Device from Embedded Swift 😱.
Hope that helps someone.

@anders0nmat makeshift solution is working for me

I can also confirm that @anders0nmat's infinite loop solution works on my end.

@anders0nmat great digging, are you interested in putting a pr for this workaround while we find a better solution?
Note: I think we should keep these crash-related issues open until a real solution is found.


Main event loops terminate when connection errors are received

pySonoffLAN version: latest
Python version: 3.7
Operating System: HASSOS

Description
Main event loops terminate when connection errors are received
What I Did
This issues is the root cause of the sonoff-lan-mode repo issue 56
I have a draft PR which fixes the issue I've experienced for your review.

Thanks again for this, and sorry for my slow responses!
I've looked through, tested and merged this evening, and will be releasing a new version of pysonofflan shortly to allow updating the hass component.

That's version 0.3.0 released to PyPI with your changes merged in - thanks again!


Pods filter by Status

What would you like to be added:
On Workloads->Pods allow to filter by status.
That would help user to filter any pending or "non running" pods.
Why is this needed:
We run > 200 pods and finding anything not running takes time and is error prone.
Environment you are Lens application on:
non enviorment specific

Kubernetes distribution: [EKS, AKS, GKE, Rancher, ...]
k3s
Desktop OS:
windows

FYI the search field does search the status message on the pods.

Closing as duplicate of https://github.com/lensapp/lens/issues/2069


SDK Python. Fix code style issues

https://app.codacy.com/gh/Visual-Regression-Tracker/sdk-python/issues?bid=19757392

I'm happy to take this one.
I added flake8 based linting, but it looks like Codacy uses Prospector and Bandit. I'll see if I can use the same tools for dev, and then resolve reported issues.

Awesome, assigned this to you

I've had a bit of a play with prospector/bandit/pylint running locally and the results don't match up with those from codacy.
I think, rather than provide local linting which doesn't match up, I'll remove the local linting and rely on codacy.

@dcrowe thanks for making project better!


Move type/trait aliases to futures-util

This moves type aliases (BoxFuture, LocalBoxFuture, BoxStream, LocalBoxStream) and Trait aliases (TryFuture, TryStream) to futures-util.
part of #2207

Type aliases (BoxFuture, LocalBoxFuture, BoxStream, LocalBoxStream)

Move to futures-util.
They are just type aliases of Pined future/stream.

Trait aliases (TryFuture, TryStream)

Move to futures-util.
They are just trait aliases of future/stream that return Result, but the real trait aliases are not yet stable, so they have some limitations. See #2200 for one of the limitations.

This PR is marked as a draft because based on #2335.
See the second commit for actual changes in this PR.

Oh, a lot of conflicts...


Bug: Bug on Windows Classic Install and Microsoft App

I'm getting the error:
Windows 10 with (classic install)
InvalidOperationException
No process is associated with this object.
at System.Diagnostics.Process.EnsureState(State state)
at System.Diagnostics.Process.get_HasExited()
at GrocyDesktop.Management.PhpManager.Stop()
at GrocyDesktop.FrmMain.FrmMain_FormClosing(Object sender, FormClosingEventArgs e)
at System.Windows.Forms.Form.OnFormClosing(FormClosingEventArgs e)
at System.Windows.Forms.Form.RaiseFormClosingOnAppExit()
at System.Windows.Forms.Application.ExitInternal()
at System.Windows.Forms.Application.Restart()
at GrocyDesktop.FrmMain.ToolStripMenuItem_EnableBarcodeBuddy_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Same thing on Microsoft App:
ArgumentException
Item has already been added. Key in dictionary: 'PHP_FCGI_MAX_REQUESTS'  Key being added: 'PHP_FCGI_MAX_REQUESTS'
at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add)
at GrocyDesktop.Management.PhpManager.Start()
at GrocyDesktop.FrmMain.SetupPhpFastCgiServer()
at GrocyDesktop.FrmMain.<FrmMain_Shown>d__34.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
Any help?

Duplicate of #39, wasn't reproducible there, isn't reproducible by what you described above - I'll solve any bug which is reproducible, as always.
Maybe, just because that's more than often the underlying problem, you have fancy antimalware software running which blocks for example starting the integrated PHP server / php.exe.

I don't have any antimalware or antivirus on my pc and i disable Windows Security at all. I install it right and when open it i'm getting this error one classic install and on app.

Then please describe each and every detail of your configuration / other installed software (would take a lot of time to recreate the complete environment that way, don't know if I will do it) or provide the complete environment in a virtual a machine or something.
Just what I said above: A problem needs to be reproducible, otherwise I can't fix it. I can't guess the problem by a single error message. "It doesn't work on my machine but I don't have provided any details about it at all" - would it possible for you to say anything about what the cause could be? I doubt it.


add CommandDotNet to cli section

CLI/CommandDotNet - CommandDotNet
Model your console app using C# in a composable manner.  Define commands with methods.  Define subcommands with properties or nested classes.  Extensible parsing and command execution.

lgtm

cheers.  thank you.


Incompatibility with Dehydration.

Use the config (changeable in the file in your configs folder or via ModMenu) to move the bar :)


tracing not working with celery worker

I didn't get the time to dig too far but I can't have epsagon traces with celery.
From what I've seen, the _get_trace function returns None, as the unique_id is None and the singleton_trace is also None.
I'm running celery with the following command:
celery -A <app_name> worker --beat --scheduler django

and I tried both the auto tracing config and calling epsagon.init directly, but the outcome is the same.

:tada: This issue has been resolved in version 1.66.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Dateformatting bugs

When I use YYYY in the dateformat, I'm getting 232023 instead of just 2023. If I switch to yyyy, it produces 2023.
When I use DD in the dateformat, I'm not getting a 0-padded day. I tried dd, but that didn't work either.

I have done some testing and have not been able to replicate either of your problems. In all cases, YYYY produces 2023 and DD gives me the correct zero-padded day.
Are you able to share your configuration (just the psi-header parts).
Regards
D

Hi,
I have tested again with your complete configuration and I have managed to replicate what you are seeing. The difference is that the dataformat() call in the changeLogEntryFormat does not have quotes around the format string. Try modifying your config to be "changeLogEntryTemplate": ["<<dateformat('YYYY.MM.DD')>>\t<<initials>>\t\t"]. I notice that one of the examples also does not add quotes so I will change that and the incorrect reference to changeLogItemTemplate.
D


Release openssh v0.10.0

This change is

@jonhoo Can you give me admin permission of this repository and access to the crates.io so that I can publish crates?
I understand you are quite busy and don't have the time to review and do release, but I do have a bit time for that.
Thank you in advance!

@NobodyXu Done and done! Thank you for taking this on, and please take good care of it :sweat_smile: I'll still be around every now and again, but don't want to keep being a bottleneck for this crate :)

Thank you!


NPE thrown when working with InfluxDb 0.9 rc2

Method ping() worked properly with influxDb 0.8.
When we started to use InfluxDb version 0.9 rc2 method ping() failed with following exception:
2015-02-23 17:23:05,388  SEVERE [com.gigaspaces.webui.common] - java.lang.NullPointerException; Caused by: java.lang.NullPointerException
at org.influxdb.impl.InfluxDBImpl.ping(InfluxDBImpl.java:107)

Hi Evgeny,
this is easily possible because the current version is in no way implemented against the v0.9 API of influxdb.  So if you need 0.9 support you need to wait. I will probably start 0.9 support after 0.9 is released.

Ok, thank you!

Hi
Are you still not supporting 0.9 InfluxDB?
Thank you,
Evgeny

Im am currently working on a 0.9 branch but this will take at least 2 more weeks to be pushed to github.

ok, thank you for update!

Hi,
i created a 0.9.0_support branch on github with my current work visible. This version is not meant to be published as is to maven repos, because i consider this as a first alpha version with some api breakage comming.
To use it you have to clone the git repo and checkout the 0.9.0_support branch.
then compile it with:
mvn clean install -Dmaven.test.skip (not all tests pass actually)
and then you can use the new library.
It is not a plug in replacement to the existing 0.8 compatible library.
Only writing, querying, creating/deleting/listing databases is currently supported. For Usage example look into InfluxDBTest.java.
Feedback to this version is welcome, contributions as well.
So please go test it  :-)
Greetings
Stefan

I will close this ticket, as this references a version which is not compatible with the 0.9 branch of influxdb,


[CanonicalizeInstruction] Process instruction "at" load after rewriting.

When a load/load_borrow is canonicalized, canonicalization should continue from where the load was before rather than the first instruction that was after it.  Enables narrowing the load through a sequence of projections.

@swift-ci please test

@swift-ci please apple silicon test

@swift-ci please apple silicon benchmark

@swift-ci please test source compatibility


Module rename

Renaming contents to match ADPcoWin rename.

Closing this as it is now part of PR #4.


feat(ui): implement activity item error dialog

Description:
Resolves #2580

How Has This Been Tested?
Manually

Screenshots (if appropriate):

Types of changes:
UX enhancement

Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[ ] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage decreased (-0.0003%) to 20.096% when pulling 5af92246397b3d24215938670c1230c8aeef65b3 on korhaliv:feat/activity-error-desc into b5c1964d1a768cef1c65359be0cc5f50d7edd7c3 on LN-Zap:next.

@mrfelton updated


Use public ecr registry instead of dockerhub - This will rate limit when you start scaling it

ERROR: failed to solve: codiumai/pr-agent:github_action: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/codiumai/pr-agent/manifests/sha256:ab7023d01dca17997084858158feb66f91ee77f56db08471fdba98d073dab055: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
Warning: Docker build failed with exit code 1, back off 1.809 seconds before retry.
/usr/bin/docker build -t f1ad72:2d931e7311a44a52a118e2a317f8deb8 -f "/home/runner/_work/_actions/Codium-ai/pr-agent/main/Dockerfile.github_action_dockerhub" "/home/runner/_work/_actions/Codium-ai/pr-agent/main"
#0 building with "default" instance using docker driver
#1 [internal] load build definition from Dockerfile.github_action_dockerhub
#1 transferring dockerfile: 158B done
#1 DONE 0.0s
#2 [internal] load .dockerignore
#2 transferring context: 170B done
#2 DONE 0.0s
#3 [internal] load metadata for docker.io/codiumai/pr-agent:github_action
#3 ERROR: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/codiumai/pr-agent/manifests/sha256:ab7023d01dca17997084858158feb66f91ee77f56db08471fdba98d073dab055: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

[internal] load metadata for docker.io/codiumai/pr-agent:github_action:

Dockerfile.github_action_dockerhub:1
 1 | >>> FROM codiumai/pr-agent:github_action
 2 |

ERROR: failed to solve: codiumai/pr-agent:github_action: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/codiumai/pr-agent/manifests/sha256:ab7023d01dca17997084858158feb66f91ee77f56db08471fdba98d073dab055: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
Warning: Docker build failed with exit code 1, back off 1.169 seconds before retry.
/usr/bin/docker build -t f1ad72:2d931e7311a44a52a118e2a317f8deb8 -f "/home/runner/_work/_actions/Codium-ai/pr-agent/main/Dockerfile.github_action_dockerhub" "/home/runner/_work/_actions/Codium-ai/pr-agent/main"
#0 building with "default" instance using docker driver
#1 [internal] load .dockerignore
#1 transferring context:
#1 transferring context: 170B done
#1 DONE 0.0s
#2 [internal] load build definition from Dockerfile.github_action_dockerhub
#2 transferring dockerfile: 158B done
#2 DONE 0.0s
#3 [internal] load metadata for docker.io/codiumai/pr-agent:github_action
#3 ERROR: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/codiumai/pr-agent/manifests/sha256:ab7023d01dca17997084858158feb66f91ee77f56db08471fdba98d073dab055: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

[internal] load metadata for docker.io/codiumai/pr-agent:github_action:

Dockerfile.github_action_dockerhub:1
 1 | >>> FROM codiumai/pr-agent:github_action
 2 |

ERROR: failed to solve: codiumai/pr-agent:github_action: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/codiumai/pr-agent/manifests/sha256:ab7023d01dca17997084858158feb66f91ee77f56db08471fdba98d073dab055: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
Error: Docker build failed with exit code 1

what ? is this a commercial? auto message?

Nope no commercial. Default images are of dockerhub, dockerhub has limits - using public ecr would give better rate limits

ok. thanks. will consider

Can you please remove the invalid label?

@slice-sarthakd thanks, we'll look for ways to solve the rate limit issue, AWS or other solutions.

As a workaround in the meanwhile, does authenticating help? https://github.com/docker/login-action#dockerhub
Can you share your usage stats? (how many PRs and comments per hour you are using).
Also, for higher use rate it will probably benefit you to run as a webhook and host your own instance.

@okotek yep I have done the third one only for now 3 days back - changed the base image in the fork and using it: https://github.com/Codium-ai/pr-agent/compare/main...TypicalDefender:pr-agent:feature-pragent-ecr

Your changes are totally equivalent.

@slice-sarthakd Regarding public ECR repo,
https://aws.amazon.com/blogs/containers/understanding-data-transfer-costs-for-aws-container-services/
All data transfer into Amazon ECR Public incurs no charge from Amazon ECR. Data transfer out is subject to charges when more than 5 TB/month is transferred out to non-AWS destinations, and you have authenticated to Amazon ECR with an AWS account. Up to 500 GB/month can be transferred out to non-AWS destinations to clients that have not authenticated (that is, anonymously). After that limit is reached, no further anonymous data transfer is allowed.
It looks like it's impossible to use anonymously >500GB/month.
We'll look at other solutions.


mpl2: fix boundary penalty and bug in macro placement

The way that the boundary penalty is currently implemented causes SA to push the macros based on the outline of the level in which it's currently working instead of pushing them to the core boundaries. This leads many macros to be placed near the center in many designs, deteriorating QoR.
These changes are to ensure that macros are pushed in the direction of the design's boundaries.
I'm also making another fix here. It looks like there was a bug that was probably introduced by copy and pasting code during the original development:

Removing the varying factor applied to outline during macro placement && ensuring we actually use run_id == 0 in the first SA thread build.

@maliberty CI Results:
[ERROR] finish__timing__drv__hold_violation_count fail test: 182.0 <= 141.0
Update metrics?

Update metrics?

If that's the only issue then just update.

@maliberty PR with the metrics: https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts/pull/1823


Improve vlm support (add idefics3 support)

This PR is a work in progress and add support for Idefics3 in TGI. opening for transparency and feedback.
This implementation uses the AutoProcessor/Idefics3Processor that will be added when this PR is merged: https://github.com/huggingface/transformers/pull/32473
todos

[ ] add more comprehensive tests
[ ] ensure rust image token logic is correct
[ ] ensure correct config is loaded (related to processor_kwargs)
[ ] refactors/cleanup typos etc..

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Improved the accuracy of the FPSCounter by using Flutter's internal frame timings.

Description
Changed the way the FPS gets calculated, instead of using the delta values from the update loop I am using WidgetsBinding.instance.addTimingsCallback, Flutter calls this with a list of FrameTiming which we can use to calculate the FPS value.
This does mean that it is no longer required to return true in recordFPS because the values will always get recorded by Flutter. It also means that recordDt() will no longer have any purpose, but I kept it in, in case someone is using it for something else.
Quite from the Discord:

Well I do think it is more accurate. For instance in my 3D game I noticed the flame FPS sometimes dropped to 29.90 and then back to 60 within a single frame. Which is strange for that to happen in a single frame. With my variant I can see it dropping to 48 and then 30 and then to 48 and back to 60 again(just a random example not actual numbers)
Spread over multiple frames as a FPS drop should be. Making me think that the flame FPS is kind off averaging out and approximating the value instead of being true to the Flutter render cycle.

Notes: I would recommend that this gets tested a bit more to see if my assumptions are correct.
Type of change
Please delete options that are not relevant.

[X] Improvement?
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:
If something is unclear, please submit the PR anyways and ask about what you thought was unclear.

[x] This branch is based on develop
[x] This PR is targeted to merge into develop (not master)
[x] I have added an entry under [next] in CHANGELOG.md
[x] I have formatted my code with flutter format
[ ] I have made corresponding changes to the documentation
[ ] I have added examples for new features in doc/examples
[ ] The continuous integration (CI) is passing

I still haven't had much time to fully test this myself nor update the docs, just wanted to give a headsup that I havent forgotten about it.


Support sidecars

Tekton tasks may specify sidecars, see https://tekton.dev/vault/pipelines-v0.16.3/tasks/#specifying-sidecars. One use case for sidecars is to run a database for use with integration tests. To support this, our builder tasks (ods-build-go and friends) would need to be able to run a sidecar.
However, it seems like sidecars cannot be configured from a pipeline, only from within a task. This is problematic as we don't want to run a sidecar all the time, nor do we want that every user who wants to use a sidecar needs to create a custom task.
One idea I have is to automatically generate a "sidecar companion task": based on ods-build-go, generate a ods-build-go-with-sidecar task. This task also has a few parameters which allow to specify the image to use and the script to execute.
Other ideas?
FYI @felipecruz91 @renedupont

This is problematic as we don't want to run a sidecar all the time, nor do we want that every user who wants to use a sidecar needs to create a custom task.

Fully agree. In my view ods-pipeline should provide an additional task with support for sidecar containers.

One idea I have is to automatically generate a "sidecar companion task"

Yes, I guess we have no other option at the moment. The only drawback I see for now is maintainability (we'll now have twice the number of tasks per every builder task).
Perhaps you can elaborate a bit more on how to automatically generate the task? I'd like to have some make command that injects the sidecar container in a list of predefined tasks and the tasks generated (manifests) are then applied to the cluster.

The idea would be:

Read the normal builder task from cluster
Inject the sidecar and additional parameters
Install the task with the sidecar in the cluster

That way we do not need to maintain two tasks. However the tests should verify that the sidecar works as expected.
Example:
Original task:
apiVersion: tekton.dev/v1beta1
kind: ClusterTask
metadata:
  name: ods-build-go
spec:
  description: Builds Go (module) applications.
  params:
    - name: enable-cgo
      description: Whether to enable CGO. When not enabled the build will set `CGO_ENABLED=0`.
      type: string
      default: "false"
  steps:
    - name: build-go-binary
      image: build/package/Dockerfile.go-toolset
      resources: {}
      script: go build
      workingDir: $(workspaces.source.path)
  workspaces:
    - name: source

Modified task with sidecar:
apiVersion: tekton.dev/v1beta1
kind: ClusterTask
metadata:
  name: ods-build-go
spec:
  description: Builds Go (module) applications.
  params:
    - name: enable-cgo
      description: Whether to enable CGO. When not enabled the build will set `CGO_ENABLED=0`.
      type: string
      default: "false"
    - name: sidecar-image
      description: Image to use for sidecar
      type: string
    - name: sidecar-script
      description: Image to use for sidecar
      type: string
      default: ''
  steps:
    - name: build-go-binary
      image: build/package/Dockerfile.go-toolset
      resources: {}
      script: go build
      workingDir: $(workspaces.source.path)
  sidecars:
  - image: $(params.sidecar-image)
    name: sidecar
    script: $(params.sidecar-script)
  workspaces:
    - name: source


[FEATURE] manifestCreator: embeds field

embeds field in created manifest.json now contains all nested
manifests independent from the reverse field embeddedBy, which
points from an embedded manifest to the library's manifest.

Coverage decreased (-0.04%) to 93.799% when pulling ac88f7249dc8c0f7915495cc47c15868f18133f7 on manifest-creator-embeds into 390587b8a136c7af86b570b4414f2dfe55d1281b on master.

Coverage decreased (-0.04%) to 93.799% when pulling ac88f7249dc8c0f7915495cc47c15868f18133f7 on manifest-creator-embeds into 390587b8a136c7af86b570b4414f2dfe55d1281b on master.


MNIST prediction in Standalone mode does not produce results

Environment:

Python version 3.6
Spark version 2.3.1
TensorFlow version 1.10.0
TensorFlowOnSpark version 1.3.2
Cluster version Standalone

Describe the bug:
I have a master machine running two slaves on the same machine.
I was able to launch the MNIST training according to the instructions and the model was made successfully. When I launch the MNIST prediction, I don't see any error messages or exceptions in the log, the prediction is successful, but the results are missing. The "predictions" directory is created, but it contains only two files: ._SUCCESS.crc and _SUCCESS.
Spark Submit Command Line:
Same as in the Github wiki.

@kecsap can you try using an absolute path for your "predictions" directory?

It was the absolute path for predictions directory. By some reason, the conversion did not produce the image files for prediction and that directory was empty. After deleting the conversion directories and run the conversion again, the prediction started to work. Maybe an assert should happen in the MNIST program if there is no examples for prediction.


support custom, app-wide, default tooltip-options

currently you must either use the pre-defined default options or re-define custom options for each instance of the tooltip directive.
This allows you to create your custom default options once. The order of priority is maintained:

Was: custom_instance_options -> default_global_options
Now: custom_instance_options -> custom_default_options -> default_global_options

@mriess260 thanks for the help! I will check and add your changes to the branch

@mriess260  - thanks for It. @drozhzhin-n-e - any Eta on this. We were seeking for this option since long time.

@mriess260 can we leave the possibility for a simple import of the module? For those who do not need to override the default settings.
  imports: [
    TooltipModule
  ]

I see what you mean; that's probably a good idea. I'll make the change.

@mriess260 great!

I see what you mean; that's probably a good idea. I'll make the change.

Did you get the chance to make the changes ?

@drozhzhin-n-e ok, I think it should be good now.

@mriess260 - There is conflict.

@sks40gb thanks, I was in a rush and didn't think to check

@mriess260 It works, thanks!

Could we have this pushed to npm please?


Test: Git - setting/action to always replace local tags

Refs: https://github.com/microsoft/vscode/issues/176799

[ ] anyOS @anthonykim1
[x] anyOS @deepak1556

Complexity: 2
Create Issue

About a year ago we have added code to detect when a git pull operation fails due to conflicting tags. This error condition can occur if someone force pushes a tag. This milestone we added a new setting, git.replaceTagsWhenPull, and a user gesture to always replace local tags.
Prerequisites

Install the latest VS Code Insiders
Ensure that the git.replaceTagsWhenPull setting is set to false
Clone the same git repository in two separate folders (ex: folder1, folder2)

Test plan

Open folder1 in one instance, and folder2 in the second instance
Open a terminal window and run the following commands in folder1:

git tag v1 -m v1
git push --tags

Open a terminal window and run the following commands in folder2:

git tag v1 -m v1 HEAD^1
git push --tags --force

Launch VS Code Insiders and open folder1
Execute the "Git: Pull" command

Confirm that a dialog is shown that provides details about the conflicting tag

Choose "Always Replace Local Tag(s)" option

Confirm that the pull operation completes
Confirm that the git.replaceTagsWhenPull setting is set to true in your user settings

Switch back to the terminal window and execute the following commands in folder1:

git tag v2 -m v2
git push --tags

Switch back to the terminal window and execute the following commands in folder2:

git tag v2 -m v2 HEAD^2
git push --tags --force

Switch back to VS Code that has folder1 opened and execute the "Git: Pull" command

Confirm that no dialog is being show
Confirm that the pull operation completes successfully

Everything as expected until: I got an error `fatal: Failed to resolve 'HEAD^2' as a valid ref.` when trying to run `git tag v2 -m v2 HEAD^2`. I ran `git tag v2 -m v2` and followed the remaining steps, and saw no dialog is shown as expected.


Question: How do I specify shm-size?

Rancher Version:
Rancher	v1.1.3
Cattle	v<IP_ADDRESS>
User Interface	v1.1.12
Rancher Compose	v0.8.6
Docker Version:
1.12.1
**Question **
How do I do the equivalent of docker run --shm-size when I launch a container from Rancher UI
Thanks

It isn't supported yet.
https://github.com/rancher/rancher/issues/4708


GPS settings on Forage Box?

Indigo Ag reported that the GPS settings on their forage box needed to be modified. What were the modifications? Is this common? Do we need to alert the rest of the users?

Cynthia and I have a call today at 1:30 to go over her issue. 3 other users have had similar issues with their GPS puck not making a good connection. The workaround is disabling the external GPS in the GPS configuration menu, using the GPS in the geoscout. Josh from Bayer says this makes collection less "repeatable but should degrade accuracy". I can add this in the troubleshooting section but I'm apprehensive since this should be a last resort option. We'll keep track of who disabled these settings in the FSB notes

This is very expensive equipment from Holland. They need to give us a
solution better than this. Let's set an emergency call up about this. If 3+
people have already had this issue so early in the season I imagine it will
continue.
On Fri, Mar 24, 2023 at 12:53 PM jordannicolette @.***>
wrote:

Cynthia and I have a call today at 1:30 to go over her issue. 3 other
users have had similar issues with their GPS puck not making a good
connection. The workaround is disabling the external GPS in the GPS
configuration menu, using the GPS in the geoscout. Josh from Bayer says
this makes collection less "repeatable but should degrade accuracy". I can
add this in the troubleshooting section but I'm apprehensive since this
should be a last resort option. We'll keep track of who disabled these
settings in the FSB notes
—
Reply to this email directly, view it on GitHub
https://github.com/precision-sustainable-ag/Hotline-Issues/issues/290#issuecomment-1483116530,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL3LJLLJDRTS77JZHELDOSDW5XGRVANCNFSM6AAAAAAWGX7QUI
.
You are receiving this because you were assigned.Message ID:
@.***>

--
Sarah Seehaver Eagen
Precision Sustainable Agriculture
Southern Cover Crops Council Program Manager
840 Oval Drive Campus Box 7825 Raleigh, NC 27606
phone:<PHONE_NUMBER>

Why do we need the external puck for day to day accuracy? @saseehav will talk with Josh about why we have this external puck for our data needs.


better handling of dox feature

cc @EPashkin @sdroege

👍

And as elsewhere, the commit message :P

:-°


msync git clone with 'path already exists'

When attempting to run msync, the first run works as expected.
However any further runs fail, as shown here: https://gist.github.com/fatmcgav/98629849f717c1dfa901
Git version = 2.5.0
OSX 10.10.4

@fatmcgav can you see if #56 fixes your issue?

:+1:

@cmurphy Cheers for the quick turn around... I'll give it a go in the morning.
Cheers
Gav

@cmurphy Yep, that does the trick :)


Stationxml filters

All StationXML translations are complete, at least for the currently accepted format.
Changes:

Added mt_metadata/timeseries/stationxml to deal with all the translations, use obspy.core.inventory module to help with the translations and writing of stationxml files. Translations for each level in a StationXML file:
- Inventory
- Network
- Station
- Channel
Added tests/timeseries/stationxml to test translations
Added data to house example stationxml files
Added mt_metadata/timeseries/filters to deal with filters
All filters have a to/from_obspy functions to help with translation.
Filters can hold the main 4 types of filters that should be encountered:

Poles-Zeros
Coefficient
Time Delay
Frequency-Amplitude-Phase

Codecov Report

Merging #19 (538098c) into main (b578ac1) will increase coverage by 1.81%.
The diff coverage is 77.79%.

:exclamation: Current head 538098c differs from pull request most recent head 6e7ed92. Consider uploading reports for the commit 6e7ed92 to get more accurate results

@@            Coverage Diff             @@
##             main      #19      +/-   ##
==========================================
+ Coverage   68.00%   69.81%   +1.81%
==========================================
  Files         135      148      +13
  Lines        6669     7652     +983
==========================================
+ Hits         4535     5342     +807
- Misses       2134     2310     +176

Impacted Files
Coverage Δ

data/xml/__init__.py
0.00% <0.00%> (ø)

mt_metadata/base/metadata.py
66.99% <ø> (+0.33%)
:arrow_up:

mt_metadata/timeseries/filters/helper_functions.py
0.00% <0.00%> (ø)

mt_metadata/utils/summarize.py
0.00% <ø> (ø)

setup.py
0.00% <0.00%> (ø)

mt_metadata/timeseries/filters/plotting_helpers.py
9.85% <9.85%> (ø)

mt_metadata/timeseries/filters/filter_base.py
56.43% <56.43%> (ø)

mt_metadata/timeseries/channel.py
88.52% <66.66%> (-5.36%)
:arrow_down:

...ta/timeseries/stationxml/xml_station_mt_station.py
77.37% <66.66%> (+0.72%)
:arrow_up:

...data/timeseries/filters/channel_response_filter.py
69.74% <69.74%> (ø)

... and 50 more

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 415ec06...6e7ed92. Read the comment docs.

@kkappler I completed the pull request assuming you were done with tables.  I'll leave this branch open until you feel like you are finished with the filters and then you can delete the branch.


Needed exclusive touch settings.

I'm using this controller in my project,at some place on touching multiple buttons at a time my app crashes.I have used exclusive touch to avoid such crashes.It would be be great if you could provide such settings.

Agree. I have a view controller and want to disable multiple touches. But exlusiveTouch does not affect it. Please, advice something.

Agree. I have a view controller and want to disable multiple touches. But exlusiveTouch does not affect it. Please, advice something.


alertmanager_notifications_total and alertmanager_notifications_failed_total should be initialised

These should be initialised to the integrations used.

@brian-brazil For an Alertmanager newbie like me, could you add more description to this issue?

This is a standard instrumentation thing, metrics should be initialised to 0 with all potential label values.


OpenSuse Tumbleweed-Slowroll support

I tried the installer script on Slowroll and it isn't supported. Could "support" be added, assuming there are no actual issues with this?

@J-Kappes Could you please open the issue on https://github.com/OpenVoiceOS/ovos-installer ?


roadmap updates

update the roadmap to include 2.2.0 plan and early 2.3.0 thoughts

/azp run mrtk_docs


User Input for Simulation Parameters

There should be a way to input simulation parameters (number of boids, force strengths, etc) by the user rather than just hardcoding.

Solved by #10


Reload does not work when in cluster settings

Describe the bug
Reloading Lens (using CMD+R or the menu option) should reload the renderer. This works great. However, when in the cluster settings view it does nothing. I know that the command shortcut is working on macos at least because the menu is flashing as expected.
To Reproduce
Steps to reproduce the behavior:

Right click a cluster icon and click settings
Try and reload the window
See that nothing reloads

Expected behavior
The window should reload in all places
Environment (please complete the following information):

Lens Version: master 43f304427399bed476a596c86e838dbe6260efd9
OS: [e.g. OSX] macos
Installation method (e.g. snap or AppImage in Linux): git clone

@nevalla This still is an issue on 3.6.0-rc2

So this is real issue more on dev env rather than on production?

I don't understand, if I run my downloaded copy of the RC then this issue still exists (that reloads on the cluster settings page do nothing)

Yeah, I get it and agree that this is still a bug. Just thinking out loud what would you expect to happen if the reload was actually working, would you see any text to change?

Well I would expect the reload to do what the reload does on every other screen (like the cluster home screen). If for some reason the UI got bugged. I think that this will be more important with the extensions going forward since they could be buggy too. (I reload VS code at least a couple times a day for instance).

I think that this will be more important with the extensions going forward since they could be buggy too. (I reload VS code at least a couple times a day for instance).

Fair point

The main issue here that when you have active cluster opened and then go to Cluster Settings - it tries to reload opened dashboard (active cluster). Fixing behavior can be full app reload when located in Preferences, Cluster Settings and Add Cluster page.


Samples columns not working in metric checks

  - invalid_count(gender) = 0:
      valid values: ["M", "Q"]
      samples columns: [employee_key, first_name]

SAS-2748


EDU-840 Import CSV into media analysis plugin

Closes https://educandu.atlassian.net/browse/EDU-840

Works super smooth 😎
Just a small glitch I found, when you export, then import, then try to export again, the download is no longer triggered (destination picker dialog doesn't open).

Works super smooth sunglasses Just a small glitch I found, when you export, then import, then try to export again, the download is no longer triggered (destination picker dialog doesn't open).

Hm, I cannot reproduce that on my machine. Is it still the case after my changes (and are there any hints of an error)?

Works super smooth sunglasses Just a small glitch I found, when you export, then import, then try to export again, the download is no longer triggered (destination picker dialog doesn't open).

Hm, I cannot reproduce that on my machine. Is it still the case after my changes (and are there any hints of an error)?

It still happens, basically with exporting twice in a row (not even importing in between). When you try to export the second time, nothing happens and there are no errors.

Works super smooth sunglasses Just a small glitch I found, when you export, then import, then try to export again, the download is no longer triggered (destination picker dialog doesn't open).

Hm, I cannot reproduce that on my machine. Is it still the case after my changes (and are there any hints of an error)?

It still happens, basically with exporting twice in a row (not even importing in between). When you try to export the second time, nothing happens and there are no errors.

As agreed upon, the multiple downloads are restricted by some browser settings. There's nothing we can do about it now.


pFIO_tests_mpi_2comm crash with GCC 10.2 and Open MPI 4.1.0

Reporting that I have a crash with the mpi_2comm pFIO test in MAPL using GCC 10.2 and Open MPI 4.1.0. I tried this on Discover with GCC 10.1.0 and Open MPI 4.0.4, but it passed. I'll work on trying to get Open MPI 4.1.0 built on discover so this can be tried there.
test 6
      Start  6: pFIO_tests_mpi_2comm

6: Test command: /Users/mathomp4/installed/Compiler/gcc-gfortran-10.2.0/openmpi/4.1.0/bin/mpiexec "-n" "18" "--oversubscribe" "-oversubscribe" "/Users/mathomp4/Models/MAPL-GCC10/MAPL/build-Debug/pfio/tests/pfio_ctest_io.x" "-nc" "6" "-nsi" "6" "-nso" "6" "-ngo" "1" "-ngi" "1" "-v" "T,U" "-s" "multicomm" "-nw" "3"
6: Test timeout computed to be: 1500
6:  start app rank:           0
6:  start app rank:           1
6:  start app rank:           2
6:  start app rank:           3
6:  start app rank:           4
6:  start app rank:           5
6:  iclient sent terminate signal
6:  oclient sent terminate signal
6:  iclient sent terminate signal
6:  oclient sent terminate signal
6:  iclient sent terminate signal
6:  oclient sent terminate signal
6:  iclient sent terminate signal
6:  oclient sent terminate signal
6:  iclient sent terminate signal
6:  oclient sent terminate signal
6:  iclient sent terminate signal
6:  oclient sent terminate signal
6:
6: Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
6:
6: Backtrace for this error:
6:
6: Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
6:
6: Backtrace for this error:
6: #0  0x10dc4ed3d
6: #1  0x10dc4e16d
6: #2  0x7fff6a9055fc
6: #0  0x103e27d3d
6: #1  0x103e2716d
6: #2  0x7fff6a9055fc
6:
6: Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
6:
6: Backtrace for this error:
6: #3  0x10ce369d2
6: #0  0x1033d4d3d
6: #1  0x1033d416d
6: #2  0x7fff6a9055fc
6: #3  0x1030189d2
6: #4  0x10ce3d9dc
6: #4  0x10301f9dc
6: #5  0x10ce3d8fb
6: #6  0x10ccbc279
6: #7  0x10ccbcf3e
6: #3  0x1025c69d2
6: #4  0x1025cd9dc
6: #5  0x10301f8fb
6: #6  0x102e9e279
6: #7  0x102e9ef3e
6: #5  0x1025cd8fb
6: #6  0x10244c279
6: #7  0x10244cf3e
6: --------------------------------------------------------------------------
6: Primary job  terminated normally, but 1 process returned
6: a non-zero exit code. Per user-direction, the job has been aborted.
6: --------------------------------------------------------------------------
6: --------------------------------------------------------------------------
6: mpiexec noticed that process rank 17 with PID 0 on node gs6101-parcel exited on signal 11 (Segmentation fault: 11).
6: --------------------------------------------------------------------------
 6/11 Test  #6: pFIO_tests_mpi_2comm .............***Failed    3.27 sec

Hmm. I just tested locally on my laptop with Intel 19.1.3 and Open MPI 4.1.0 and it passed. So...huh

More fun: I just seemed have encountered this crash with GCC 10.2.0 and Open MPI 4.1.0 on my macOS laptop. Hmm.

More fun: I just seemed have encountered this crash with GCC 10.2.0 and Open MPI 4.1.0 on my macOS laptop. Hmm.

I believe this now works as well thanks to @weiyuan-jiang. I'll close and open a new ticket if needed.


Allow starring of community packages in installed list

Allow toggling of whether a package is starred on atom.io from inside Atom.
This eases the install of Atom on other computers by using apm stars --install.

Thanks, @aioue, looks like a duplicate of https://github.com/atom/settings-view/issues/141.


Fix error in interfaces example

Currently, the interface example contains a call to the distance function which does not exist. Therefore, the area interface function should be re-implemented/fixed.

Hey! I would like to work on this?

Hey! I would like to work on this?

@sowmiyamuthuraman Thank you for showing interest in contribution but for this issue #24 PR is already raised.
But there are other Issues open which you can pick. Let me know if you want any help.

Fixed with #24.


Docs/generate ref docs

/build

Add typedoc config samples for auto-generating docs from source code.
Add cleanup script for post-processing typedoc output into matching format and path structure for JSS docs.

Next.js

SDK reference doc generated from comments & update nav links.

Fundamentals

Add reference docs for core package & update nav links.

/src
Update Sidenav to highlight parent pages when child is active (used to preserve link highlight in the nav when child ref pages are active).
Description / Motivation

Testing Details

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Documentation update (non-breaking change; modified files are limited to the /docs directory)

Since we only generate ref docs as .md and not for display on the website, most of the changes in this PR are irrelevant. For future releases, the only relevant content would be the correct typedoc configuration - to be included at a later time. Closing this PR as obsolete.


Trapping sporadically segfaults

The test unhandled.wast occasionally triggers a segfault in the testsuite, e.g.
Caused by:
  process didn't exit successfully: `/home/dhil/projects/wasmfx/wasmtime/target/debug/deps/all-2197ac4314cc5afd` (signal: 11, SIGSEGV: invalid memory reference)

We should investigate the cause of this segfault. It appears related to trap generation and potentially propagation across multiple linked stacks.

Potentially relevant for PR#58.

I've investigated this. The problem is that trace_through_wasm in backtrace.rs breaks due to how the trampolines we use to run fibers overwrite some data in VMRuntimeLimits.
The idea of trace_through_wasm is to follow a chain of frame pointers until hitting the stack frame belonging to the original beginning of the execution of wasm code, called  trampoline_sp. Concretely, the function assumes that trampoline_sp denotes the stack pointer of the trampoline where execution of wasm code started, and that the currently running wasm frames are located immediately below it.
The value of trampoline_sp is obtained from the last_wasm_entry_sp field of the VMRuntimeLimits. Unfortunately, this means that whenever we start execution of a continuation with resume, the array calling trampoline that we use overwrites  this value with the current stack pointer. In other words, the value of last_wasm_entry_sp may be a pointer inside the last fiber where we started executing a function as a continuation, which means that it can be entirely unrelated to whatever fiber has been switched to in the meantime.
Unfortunately, I don't see a simple way of avoiding that the last_wasm_entry_sp field gets overwritten: This is done by existing trampolines that we re-use, and can't easily change. With last_wasm_entry_sp therefore being overwritten, we don't know where the wasm stack frames end once reaching the main stack.
We could probably use the chain of ContinuationObject pointers in the VMContext to detect such situations and construct a backtrace for all frames in the chain of ContinuationObjects, but this backtrace would be incomplete, because we cannot include frames from the main stack: In order to detect when we reach the outermost wasm frame on the main stack, we would need to have access to the "original" value of last_wasm_entry_sp (i.e., when switching from the host into wasm code initially to start execution).
There is some logic in traphandlers.rs to model (what I think is) a chain of stacks used by the existing async implementation, but it's probably a bad idea to try to use that for our purposes (in particular, we would have to keep the parent pointers in yet another chain of stacks up to date when switching stacks).

Thanks for diagnosing this issue! I do recall thinking about trace_through_wasm for linked stacks in the past.
It reads to me that you suggest we implement some bespoke backtracing mechanism rather than trying to shoehorn or piggyback on the existing infrastructure. I think I agree with this sentiment at this stage.
I don't think it will be terrible difficult to implement. The key is to carefully record the last entry pointers, as you suggest, we could attach this on the continuation headers. I'm inclined to believe the backtracing metadata only should be available in debug mode.

Fixed in a previous PR by @frank-emrich.


Better entrypoint override for interactive mode

Is your feature request related to a problem?
It's related to slow redeployments around interactive mode.
Which solution do you suggest?
When running devspace dev -i the entrypoint override could be something like this:
      interactive:
        images:
          - name: frontend
            entrypoint:
              - sh
            cmd:
              - -c
              - "trap 'exit 1' TERM; sleep 999999999 & wait"

Which alternative solutions exist?
Manually provide the interactive config I pasted in the previous section.
Additional context
Doing sleep 999999999 as the entrypoint takes a long time for the pod to terminate, because sleep doesn't handle SIGTERM - https://superuser.com/a/1299463/157978
As is I just wait 10+ seconds for the pod to terminate before the new one is launched:
$ kubectl get all
NAME                            READY   STATUS        RESTARTS   AGE
pod/frontend-6c99b95f86-lmhmj   1/1     Terminating   0          2m2s
...

I'm happy to take a whack at this myself if you want, just wasn't sure if it might a quick fix for someone more familiar with the code (assuming it's a change worth adding).
/kind feature

@ralfthewise thanks for opening this issue! Yes sounds good, I think we can change that, would be great if you could open a PR for this (you can simply change the default ENTRYPOINT and CMD in this file https://github.com/devspace-cloud/devspace/blob/master/cmd/dev.go#L648).

Sounds good, will do.

Closing due to inactivity. If you are still facing this issue or need this feature, please reopen for us to re-look at it.
The latest devspace version may address your needs, so please look at the latest version before opening a new issue.


Added two feature collection layer samples

Feature collection layer
Feature collection layer (query)

Copyright headers need to be changed to 2017 for the code files that were created in 2017

everything else looks good, you can go ahead and merge when you've updated the copyright


VPC and Transit Gateway

I would like to use this VPC module in combination with the transit gateway module (https://registry.terraform.io/modules/terraform-aws-modules/transit-gateway/aws/latest) in a way to route traffic from the private subsets (only) to the transit gateway. I did not find a solution since I can not manage the route tables for private subnets, nor can I add a new route table. Is there a way to perform this action? Even if there is a way to modify the route tables I would get a circular dependency between the vpc module and transit gateway module since the transit gateway attachments need the ids of the private subnets and the route table of the VPC would need the transit gateway ID.

This module outputs private_route_table_ids which you can use in conjunction with aws_route resources that you create yourself. You don't need to specify the attachment ID, you just need to specify the transit_gateway_id. In my configuration, I deployed the TGW ENIs into a different set of private subnets, but I don't know if that is a strict requirement.


If Train_loss = 0.00002 but Valid_loss = 5.81674, is model still learning?

Hello,
I've started training the model on custom dataset and found that after 10K iterations, Training loss has decreased to 0.00002 but validation loss is still on higher side and accuracy ~10%.
I'm not really sure if model is still learning in further iterations. Could someone help me here, if I should continue the training or need to look in other parameters of model training?
Thanks in advance

Hello,
I guess the training is almost done, thus continue training would be not a good solution.
I recommend checking the difference between your custom dataset and the validation dataset.
If they are very different, you should make your own validation dataset for your purpose.
Hope it helps,
Best

Hello,
I guess the training is almost done, thus continue training would be not a good solution.
I recommend checking the difference between your custom dataset and the validation dataset.
If they are very different, you should make your own validation dataset for your purpose.
Hope it helps,
Best

Hi @ku21fan
First of all, thank you for this great work!
Similar to @peeush-agarwal problem, I am facing the same problem although I had made my custom train, validation and test dataset. The data distribution is also consistent in the training and validation set but still getting this:
[10000/300000] Train loss: 0.00000, Valid loss: 3.39168, Elapsed_time: 1757.51917
Any suggestion is highly appreciated.

I have the same problem. The data is being generated similarly from the same distribution for train/validation like this:
trdg --output_dir train -b 2 -na 2 -ft fonts/fe_font.TTF -c 1000000 -rs -let -num -k 5 -rk -bl 1 -rbl --case upper
trdg --output_dir validate -b 2 -na 2 -ft fonts/fe_font.TTF -c 1000 -rs -let -num -k 5 -rk -bl 1 -rbl --case upper
# here whitespaces needs to be replaced by tabulations in labels.txt
python3 create_lmdb_dataset.py train train/labels.txt train_lmdb
python3 create_lmdb_dataset.py train validate/labels.txt validate_lmdb

So I just used similar train code from EasyOCR and it worked on my data. Don't know what is the problem with training here.

Hello,
I also have the same problem. after 10k iteration, my train loss is almost 0, but the validation loss is about 1.5.
My train data and validation data came from the same distribution and they are all 10-digit numbers with the same font.
Anyone knows how to overcome this problem?


UI

Implement UI for 2 components: UserSignIn, UserSignOut
Done!

Screenshot Components for quick review.

Screenshot for prview:


Triplet loss

Proposed changes:

reformulate our margin loss as triplet loss

Status (please check what you already did):

[ ] added some tests for the functionality
[x] updated the documentation
[x] updated the changelog (please check changelog for instructions)
[x] reformat files using black (please check Readme for instructions)

/modeltest
 dataset_branch: "triplet-loss"
 include:
  - dataset: ["all"]
    config: ["all"]


Set launch_template.ami_id attrs to private

Reference Issues or PRs

What does this implement/fix?
Put a x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features not to work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

Testing

[ ] Did you test the pull request locally?
[ ] Did you add new tests?

How to test this PR?

Any other comments?

Checking pydantic docs to be sure this is the correct setting

This is what the validation error will look like if the user tries to pass the ami_id field

The reason for not completely removing it, is that once the error on the terraform side of things is addressed, we can just re-enable this field instead of re-including

just waiting for the tests


[Bug]: msgraph-developer-proxy is damaged and cannot be opened

From 0.2.3 onwards, I am unable to start the proxy on macOS Monterey 12.6.2 (21G320), as I receive the below error.

0.2.1 and 0.2.2 releases work fine.

Interestingly v0.3.0 works on my MacBook Air (Intel) running macOS Monterey 12.6.2 (21G320)

Hi, I can run it on my MacBook Pro (M1 Max):

Out of interest, what is your SHA256 sum @garrytrinder, was wondering if its different in anyway?

We compared the checksum between the working and not-working version and they were the same @leeford

Thanks for checking @gavinbarron @leeford
Back to the drawing board 🤔

@garrytrinder what processor is your Mac running? I seem to recall there being some challenges with lots of software when Apple pivoted to using their own silicon.

I fresh installed v0.3.0 on macOS Ventura 13.1 running on Apple M1 and everything seems to work as expected (using default zsh terminal). Definitely sounds like something uniquely corrupted in your environment. Have you tried the general macOS guidance for fixing "[XX] is damaged and can't be opened"? (ex: https://osxdaily.com/2019/02/13/fix-app-damaged-cant-be-opened-trash-error-mac/)

@garrytrinder what processor is your Mac running? I seem to recall there being some challenges with lots of software when Apple pivoted to using their own silicon.

If I recall correctly, @garrytrinder is on Intel

Fixed!!
It appears that Gatekeeper had put the file into quarantine for some reason.
To remove the file from quarantine, execute the following in a terminal prompt:
xattr -d com.apple.quarantine ~/msgraph-developer-proxy/msgraph-developer-proxy

Thanks for the link to the article @toddanglin 👍

Reopening as I am having issue with the proxy that I think is still related this.
Although I can now execute the proxy, the certificate is not saved to the .config/msgraph-developer-proxy folder and is not added into keychain, this results in SSL errors.
Interestingly, I can build v0.3 locally in Visual Studio for Mac and run the built executable which works as expected.

Hey @garrytrinder, is this still an issue for you?

Tested on a fresh install of macOS Ventura and all is working fine with v0.8.


Tapping on disabled RadioListTile dismisses bottom sheet

I’m using showModalBottomSheet to show a list of RadioListTiles as options. I still want to show unavailable options — so they show up as disabled (onchanged = null). However, when you tap those disabled options it seems like the tap passes through and dismisses the sheet. It seems unexpected.
As a workaround, @Hixie suggested wrapping the RadioListTile in an AbsorbPointer. I also wrapped that in a GestureDetector with an empty onTap. The below works for me.
  final tile = new GestureDetector(
    onTap: () {},
    child: new AbsorbPointer(
      absorbing: !merchandiseItemSize.isAvailable,
      child: new RadioListTile<String>(
        title: new Text(
          "$sizeTitle ($priceString)",
        ),
        value: sizeTitle,
        groupValue: _sizeValue,
        onChanged: merchandiseItemSize.isAvailable ? _updateSelectedSize : null,
      ),
    ),
  );

Forget the AbsorbPointer, I was barking up the wrong tree with that one. But wrapping the whole part of the sheet that you want to have not dismiss the sheet with a new GestureDetector(onTap: () { }, ...) should solve it.

The question is whether we want that behaviour by default for Radio, RadioListTile, or anything else, or if it's specifically a question for sheets, or if we should just document it somewhere...

Hi @alardizabal  is this issue still meant to be open?

Hi @alardizabal
I tried to replicate the issue you described on dartpad
and doesn't seem to occur anymore
May I close this issue?
Thank you

I’m unable to reproduce the issue to pinpoint the cause. The issue needs further investigation.

Given how long we have had this behaviour, maybe we should call it intentional and close this bug...

I'm gong to close this issue because it no longer seems to be reproducible, https://github.com/flutter/flutter/issues/10593#issuecomment-655490988, and because - if it were reproducible - it's unlikely to be a welcome change anymore, https://github.com/flutter/flutter/issues/10593#issuecomment-658463583.


Fix -Wconversion and -Wsign-conversion Clang warnings.

I use json11 in my own project, which I usually compile with Clang and have following warnings:
/Users/yazevnul/Documents/my/github/ysda-search-engine/src/third_party/json11/json11.cpp:370:20: warning: implicit conversion loses integer precision: 'int' to 'char' [-Wconversion]
return fail("unexpected end of input", 0);
~~~~~~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/yazevnul/Documents/my/github/ysda-search-engine/src/third_party/json11/json11.cpp:439:39: warning: implicit conversion changes signedness: 'int' to 'size_type'
(aka 'unsigned long') [-Wsign-conversion]
if (!in_range(esc[j], 'a', 'f') && !in_range(esc[j], 'A', 'F')
~~~ ^
/Users/yazevnul/Documents/my/github/ysda-search-engine/src/third_party/json11/json11.cpp:439:70: warning: implicit conversion changes signedness: 'int' to 'size_type'
(aka 'unsigned long') [-Wsign-conversion]
if (!in_range(esc[j], 'a', 'f') && !in_range(esc[j], 'A', 'F')
~~~ ^
/Users/yazevnul/Documents/my/github/ysda-search-engine/src/third_party/json11/json11.cpp:440:46: warning: implicit conversion changes signedness: 'int' to 'size_type'
(aka 'unsigned long') [-Wsign-conversion]
&& !in_range(esc[j], '0', '9'))
This PR should fix them.

Thanks! Can you fill out our CLA at https://opensource.dropbox.com/cla/ and then I can merge this?

Can't merge without CLA, but equivalent fixes have been made independently.


Fix pip package description

Description
This PR fixes pip package description by changing wrong oneDNN inscription from 'ONEDNN' to 'oneDNN'.

@mxnet-bot run ci [unix-cpu]


Support Array for Level option

Support array type for level option.
I noticed that there is a no code for when level option has array type.
So, I have changed index.js file.

Pull Request Test Coverage Report for Build 30

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.05%) to 98.947%

Totals

Change from base Build 29:
-1.05%

Covered Lines:
69

Relevant Lines:
69

💛  - Coveralls

Pull Request Test Coverage Report for Build 30

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.05%) to 98.947%

Totals

Change from base Build 29:
-1.05%

Covered Lines:
69

Relevant Lines:
69

💛  - Coveralls

Pull Request Test Coverage Report for Build 30

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.05%) to 98.947%

Totals

Change from base Build 29:
-1.05%

Covered Lines:
69

Relevant Lines:
69

💛  - Coveralls

I'll update test.js because of coverage and then re-write it.