text:
apple home successfully created fabric, but pair failed (CON-448)

IDF:4.4.3
esp-matter:
commit 9bb410d995b6ae81e2025467e5d5bbf494c1e6b1 (HEAD -> release/v1.0)
Merge: 80a22dc 83c25e9
Author: Hrishikesh Dhayagude <hrishi@espressif.com>
Date:   Fri Mar 31 12:25:30 2023 +0800
I (6780) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (6781) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:0, no connets:0
I (6787) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:0, no connets:0
I (6840) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (6840) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (6847) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:0, no connets:0
I (6857) chip[EM]: >>> [E:50500r M:159526131] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (6868) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:0, no connets:0
I (6878) chip[EM]: <<< [E:50500r M:237483382] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
I (6887) chip[IN]: (S) Sending msg 237483382 on secure session with LSID: 43616
I (6896) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:0, no connets:0
I (6930) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (6930) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:0, no connets:0
I (6931) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (6947) chip[EM]: >>> [E:50501r M:159526132] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
I (6959) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:0, no connets:0
I (6969) chip[DL]: NVS set: chip-config/reg-location = 0 (0x0)
I (6973) esp_matter_attribute: ********** Endpoint 0x0000's Cluster 0x0030's Attribute 0x0000 is ld **********
I (6985) chip[EM]: <<< [E:50501r M:237483383] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
I (6994) chip[IN]: (S) Sending msg 237483383 on secure session with LSID: 43616
I (6996) EF-I: [post_timetask_info:708][post_timetask_info] index[7], need_send_task[1], iot_ack[1], ble_ack[1]
I (7013) EF-I: [post_one_timetask_info:631]read timetask info id[7], cfg[0], en[0], time[0:0:0]
I (7014) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7031) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7039) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7023) EF-I: [post_timetask_info_by_ble:613]post timetask info to ble
I (7050) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (7066) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7073) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7140) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (7140) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (7147) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7157) chip[EM]: >>> [E:50502r M:159526133] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (7169) esp_matter_command: Received command 0x00000000 for endpoint 0x0000's cluster 0x00000030
I (7177) chip[FS]: GeneralCommissioning: Received ArmFailSafe (60s)
I (7184) esp_matter_attribute: ********** Endpoint 0x0000's Cluster 0x0030's Attribute 0x0000 is ld **********
I (7197) chip[EM]: <<< [E:50502r M:237483384] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (7207) chip[IN]: (S) Sending msg 237483384 on secure session with LSID: 43616
I (7217) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7224) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7260) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (7261) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (7267) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7277) chip[EM]: >>> [E:50503r M:159526134] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (7289) esp_matter_command: Received command 0x00000002 for endpoint 0x0000's cluster 0x00000030
I (7298) chip[DL]: NVS set: chip-config/reg-location = 0 (0x0)
I (7304) chip[DL]: NVS set: chip-config/country-code = "XX"
I (7310) esp_matter_attribute: ********** Endpoint 0x0000's Cluster 0x0030's Attribute 0x0000 is ld **********
I (7323) chip[EM]: <<< [E:50503r M:237483385] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (7333) chip[IN]: (S) Sending msg 237483385 on secure session with LSID: 43616
I (7343) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7350) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7380) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (7381) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (7387) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7397) chip[EM]: >>> [E:50504r M:159526135] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (7409) esp_matter_command: Received command 0x00000002 for endpoint 0x0000's cluster 0x0000003E
I (7417) chip[ZCL]: OpCreds: Certificate Chain request received for PAI
I (7428) chip[EM]: <<< [E:50504r M:237483386] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (7437) chip[IN]: (S) Sending msg 237483386 on secure session with LSID: 43616
I (7447) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7453) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7497) EF-I: [post_timetask_info:708][post_timetask_info] index[8], need_send_task[1], iot_ack[1], ble_ack[1]
I (7497) EF-I: [post_one_timetask_info:631]read timetask info id[8], cfg[0], en[0], time[0:0:0]
I (7500) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (7516) EF-I: [post_timetask_info_by_ble:613]post timetask info to ble
I (7524) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7531) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7560) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (7561) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7567) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
W (7593) ledc: LEDC FADE TOO FAST
I (7620) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (7621) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (7627) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7637) chip[EM]: >>> [E:50505r M:159526136] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (7649) esp_matter_command: Received command 0x00000002 for endpoint 0x0000's cluster 0x0000003E
I (7657) chip[ZCL]: OpCreds: Certificate Chain request received for DAC
I (7668) chip[EM]: <<< [E:50505r M:237483387] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (7677) chip[IN]: (S) Sending msg 237483387 on secure session with LSID: 43616
I (7687) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7693) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7770) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (7771) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7777) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7830) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (7831) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7837) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7920) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (7921) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (7927) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (7937) chip[EM]: >>> [E:50506r M:159526137] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (7949) esp_matter_command: Received command 0x00000000 for endpoint 0x0000's cluster 0x0000003E
I (7957) chip[ZCL]: OpCreds: Received an AttestationRequest command
I (7997) EF-I: [post_timetask_info:708][post_timetask_info] index[9], need_send_task[1], iot_ack[1], ble_ack[1]
I (7997) EF-I: [post_one_timetask_info:631]read timetask info id[9], cfg[0], en[0], time[0:0:0]
I (8006) EF-I: [post_timetask_info_by_ble:613]post timetask info to ble
I (8263) EF-I: [main_task_wdt_feed_task:64]feed watch dog for main task
W (8283) EF-W: [memoryMonitoringTasks:43]current free heap:46.30K inter free heap:40.04K min free heap:26.74K
I (8359) chip[ZCL]: OpCreds: AttestationRequest successful.
I (8362) chip[EM]: <<< [E:50506r M:237483388] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (8367) chip[IN]: (S) Sending msg 237483388 on secure session with LSID: 43616
E (8376) chip[DL]: Long dispatch time: 441 ms, for event type 7
I (8381) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (8390) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (8398) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (8407) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (8430) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (8431) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (8437) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (8490) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (8490) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (8503) EF-I: [post_timetask_info:708][post_timetask_info] index[10], need_send_task[1], iot_ack[1], ble_ack[1]
I (8508) EF-I: [post_one_timetask_info:631]read timetask info id[10], cfg[0], en[0], time[0:0:0]
I (8518) EF-I: [post_timetask_info_by_ble:613]post timetask info to ble
I (8580) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (8582) chip[EM]: >>> [E:50507r M:159526138] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (8591) esp_matter_command: Received command 0x00000000 for endpoint 0x0000's cluster 0x00000030
W (8595) ledc: LEDC FADE TOO FAST
I (8600) chip[FS]: GeneralCommissioning: Received ArmFailSafe (60s)
I (8611) esp_matter_attribute: ********** Endpoint 0x0000's Cluster 0x0030's Attribute 0x0000 is ld **********
I (8623) chip[EM]: <<< [E:50507r M:237483389] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (8634) chip[IN]: (S) Sending msg 237483389 on secure session with LSID: 43616
I (8643) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (8650) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (8700) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (8700) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (8977) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (8977) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
W (9623) ledc: LEDC FADE TOO FAST
I (9977) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (9977) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
W (10283) EF-W: [memoryMonitoringTasks:43]current free heap:50.36K inter free heap:44.10K min free heap:26.74K
W (10643) ledc: LEDC FADE TOO FAST
I (10977) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (10977) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (11220) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (11221) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (11263) EF-I: [main_task_wdt_feed_task:64]feed watch dog for main task
W (11663) ledc: LEDC FADE TOO FAST
I (11977) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (11977) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
W (12253) EF-W: [tx_fifo_check_clear_task:35]cleat lan_data_tx_bfifo
W (12283) EF-W: [memoryMonitoringTasks:43]current free heap:50.36K inter free heap:44.10K min free heap:26.74K
W (12673) ledc: LEDC FADE TOO FAST
I (12977) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (12977) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
W (13693) ledc: LEDC FADE TOO FAST
I (13722) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (13770) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (13770) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (13977) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (13977) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (14263) EF-I: [main_task_wdt_feed_task:64]feed watch dog for main task
W (14293) EF-W: [memoryMonitoringTasks:43]current free heap:50.36K inter free heap:44.10K min free heap:26.74K
W (14713) ledc: LEDC FADE TOO FAST
I (14977) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (14977) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
W (15733) ledc: LEDC FADE TOO FAST
I (15977) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (15977) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (16260) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (16261) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
W (16293) EF-W: [memoryMonitoringTasks:43]current free heap:50.36K inter free heap:44.10K min free heap:26.74K
W (16743) ledc: LEDC FADE TOO FAST
I (16977) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (16977) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (17263) EF-I: [main_task_wdt_feed_task:64]feed watch dog for main task
I (17700) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (17703) chip[EM]: >>> [E:50508r M:159526139] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (17711) esp_matter_command: Received command 0x00000004 for endpoint 0x0000's cluster 0x0000003E
I (17720) chip[ZCL]: OpCreds: Received a CSRRequest command
W (17763) ledc: LEDC FADE TOO FAST
I (18054) chip[ZCL]: OpCreds: AllocatePendingOperationalKey succeeded
W (18293) EF-W: [memoryMonitoringTasks:43]current free heap:45.32K inter free heap:39.06K min free heap:26.74K
I (18428) chip[ZCL]: OpCreds: CSRRequest successful.
I (18430) chip[EM]: <<< [E:50508r M:237483390] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (18435) chip[IN]: (S) Sending msg 237483390 on secure session with LSID: 43616
E (18445) chip[DL]: Long dispatch time: 743 ms, for event type 7
I (18449) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (18458) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (18467) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (18475) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (18480) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (18495) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (18502) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (18540) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (18540) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (18571) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (18572) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (18630) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (18633) chip[EM]: >>> [E:50509r M:159526140] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (18641) esp_matter_command: Received command 0x0000000B for endpoint 0x0000's cluster 0x0000003E
I (18650) chip[ZCL]: OpCreds: Received an AddTrustedRootCertificate command
W (18774) ledc: LEDC FADE TOO FAST
I (18998) chip[ZCL]: OpCreds: AddTrustedRootCertificate successful.
I (19000) chip[EM]: <<< [E:50509r M:237483391] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (19007) chip[IN]: (S) Sending msg 237483391 on secure session with LSID: 43616
E (19016) chip[DL]: Long dispatch time: 385 ms, for event type 7
I (19021) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (19030) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (19039) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (19047) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (19050) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (19066) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (19075) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (19083) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (19110) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (19113) chip[EM]: >>> [E:50510r M:159526141] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (19121) esp_matter_command: Received command 0x00000006 for endpoint 0x0000's cluster 0x0000003E
I (19130) chip[ZCL]: OpCreds: Received an AddNOC command
I (19138) chip[FP]: Validating NOC chain
I (19478) chip[FP]: NOC chain validation successful
I (19478) chip[FP]: Added new fabric at index: 0x1
I (19478) chip[FP]: Assigned compressed fabric ID: 0xE04CAAD4458906B6, node ID: 0x00000000E5092ECA
I (19488) chip[TS]: Last Known Good Time: 2023-04-26T09:19:44
I (19494) chip[TS]: New proposed Last Known Good Time: 2023-04-26T09:33:16
I (19502) chip[TS]: Updating pending Last Known Good Time to 2023-04-26T09:33:16
I (19517) chip[ZCL]: OpCreds: ACL entry created for Fabric index 0x1 CASE Admin Subject 0x5982432DEC46C2EB
I (19520) chip[DIS]: Advertise operational node E04CAAD4458906B6-00000000E5092ECA
I (19529) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: E04CAAD4458906B6-00000000E5092ECA.
I (19540) chip[DIS]: mDNS service published: _matter._tcp
I (19547) chip[ZCL]: OpCreds: successfully created fabric index 0x1 via AddNOC
I (19556) chip[EM]: <<< [E:50510r M:237483392] (S) Msg TX to 1:FFFFFFFB00000000 [06B6] --- Type 0001:09 (IM:InvokeCommandResponse)
I (19567) chip[IN]: (S) Sending msg 237483392 on secure session with LSID: 43616
E (19576) chip[DL]: Long dispatch time: 465 ms, for event type 7
I (19581) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (19590) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (19620) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (19621) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (19627) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (19637) chip[EM]: >>> [E:50511r M:159526142] (S) Msg RX from 1:FFFFFFFB00000000 [06B6] --- Type 0001:08 (IM:InvokeCommandRequest)
I (19650) esp_matter_attribute: ********** Endpoint 0x0000's Cluster 0x0030's Attribute 0x0000 is ld **********
I (19661) chip[EM]: <<< [E:50511r M:237483393] (S) Msg TX to 1:FFFFFFFB00000000 [06B6] --- Type 0001:09 (IM:InvokeCommandResponse)
I (19671) chip[IN]: (S) Sending msg 237483393 on secure session with LSID: 43616
I (19681) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (19688) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (19740) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14
I (19741) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (19748) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (19757) chip[EM]: >>> [E:50512r M:159526143] (S) Msg RX from 1:FFFFFFFB00000000 [06B6] --- Type 0001:08 (IM:InvokeCommandRequest)
I (19769) chip[NP]: ESP NetworkCommissioningDelegate: SSID: 华硕
I (19775) chip[DL]: Disconnecting WiFi station interface
E (19781) chip[DL]: esp_wifi_disconnect() failed: UNKNOWN ERROR
W (19778) ledc: LEDC FADE TOO FAST
I (19788) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (19977) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (19977) CHIP[DL]: kCHIPoBLEServiceMode_Enabled:1, kAdvertisingEnabled:1, no connets:0
I (20263) EF-I: [main_task_wdt_feed_task:64]feed watch dog for main task
W (20293) EF-W: [memoryMonitoringTasks:43]current free heap:47.27K inter free heap:41.02K min free heap:26.74K
W (20803) ledc: LEDC FADE TOO FAST

@sidhoo2 Please do not paste the logs, instead upload the complete log file. The logs indicate that the Wi-Fi network connectivity wasn't established. Can you please check the SSID and passphrase, if correct.
Also, the application seems to be different than the standard examples. Please provide any patch/diff on top of an existing example for us to recreate the issue.

@dhrishi  ok, i will pay attention next time.  you are right , but it can paired sucessful some time with this SSID.

@sidhoo2 Please check if the AP is far away from the device. Also, if possible, please reset to factory the ESP32 and upload the commissioning logs from the new boot in case of a failure.

@sidhoo2 Any updates here? Please close the issue if resolved

okay,  can't find the reason, and i hv never meet this issue these days.

repo: espressif/esp-matter


text:
Uncaught (in promise) TypeError: Cannot read property 'BOOTLOADER_FLASH_OFFSET' of null (ESPTOOL-285)

After selecting a .bin file to flash and clicking Program, the console display this error.
Uncaught (in promise) TypeError: Cannot read property 'BOOTLOADER_FLASH_OFFSET' of null

Any ideas how to fix this?

@seeya is this with the latest deployed version that you observed this issue?

@adwait-esp yes, I cloned the latest version and tested again it's the same. It seems like the board didn't connect properly causing the variable this.chip to be null.

@seeya , are you able to perform other operations - like erase flash or get to the console with the same attached chip?

@adwait-esp yes, using the flasher tool from Espressif Systems (https://www.espressif.com/en/support/download/other-tools), I'm able to flash the firmware.bin file at 0x1000.
Also with PlatformIO there's no issue.

Same issue for me. Going to the live demo code at: https://espressif.github.io/esptool-js/. Plugin an ESP32, connect, select a firmware binary, and click program and nothing happens and in the Chrome developer tools console I see:
ESPLoader.js:1288 Uncaught (in promise) TypeError: Cannot read property 'BOOTLOADER_FLASH_OFFSET' of null
at ESPLoader._update_image_flash_params (ESPLoader.js:1288)
at ESPLoader.write_flash (ESPLoader.js:1358)
at HTMLInputElement.programButton.onclick (index.js:279)

Its a timing thing. If i put a breakpoint here and just click continue when it stops there then it doesn't get that "Cannot read property" error any more. Still doesn't flash the ESP32 though, when I click program nothing happens and no errors in the Javascript console.

Not sure if anyone still needs help on this error, but Web USB requires SSL so if you're running the local test server without SSL it will fail with this error message.

Same issue here, on latest Chrome

What is the state of this project in general? Is main a working branch, or should we be using another one? I don't see how it even CAN work, e.g. connecting causes an infinite loop here
There's no way to ever break out of this loop unless there's a timeout:
while (1) {
            try {
                const res = await this.transport.read({timeout: 1000});
                i += res.length;
                //console.log("Len = " + res.length);
                //var str = new TextDecoder().decode(res);
                //this.log(str);
            } catch (e) {
                if (e === "timeout") {
                    break;
                }
            }
            await this._sleep(50);
        }

unless I'm missing something entirely obvious/subtle, the loop above should read:
while (1) {
            // loop until we read something from the device successfully
            try {
                const res = await this.transport.read({timeout: 1000});
                break; // successful read
            } catch (e) {
                if (e === "timeout") {
                    // caught and (expected) error, will continue to attempt connecting.
                    continue;
                }
                // caught a real error
                throw e
            }
            await this._sleep(50);
        }

This project is being maintained and the branch "gh_pages" which serves the https://espressif.github.io/esptool-js/ has the latest updated code.
We have observed intermittent connection issues for some revisions of ESP32 chipsets and we are working to resolve the same. Can you please let us know which ESP32 chipset you are trying to connect to?

It seems to me that the tool might be able to use some polishing, especially concerning handling of error cases and reporting on progress.
My main intention of writing here is to check whether it would make sense to contribute here, or if there are already people working on these (tbh rather obvious) deficits.
The boards I'm using are about as plain vanilla as it gets, e.g. in front of me is a WROOM Devkit, with a Silicon Labs CP210x Bridge:
Chip is ESP32-D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz

but also on a variety of known good devices and different bridges (at least FTDI),  all of which work fine even at high baud rates with the same cable and esptool.py
Out of curiosity, which chipsets/devkits are you using that work?
The connect/sync works sometimes if run at the lowest baud rate. Even when it works, it takes a long time and provides no feedback during connection / sync. And not indication when an error occured. Typically, it's necessary to press Connect twice, because the connect procedure is stuck in the loop described above.
Even in the cases where the connect works, the upload fails. Again with no error indication.

Above issues have been addressed. It now correctly raises if an unsupported chip is passed in (chip == null) and with #33 the latest UI issues has been fixed. Give it a try and please open new issues if you find some.

source: gharchive/issue

authors: a2800276 adwait-esp balloob mikevanis seeya spiceywasabi torntrousers

repo: espressif/esptool-js

license_type: permissive

license_source: github-api


text:
Settings: widgets

I was thinking that maybe it would be nice if we could add widget settings to the settings app, instead of having separate "apps" just to configure a widget?
Something like

A widget can set WIDGETS["mywidget"].settings to a function to handle settings
The settings app gets a new submenu "Widgets", containing (only) all widgets that have a settings property
Ideally widgets also set name, which is used as menu entry

If not set, fall back to the WIDGETS key? So it would just show as "mywidget"
Or should .settings contain both a name and a callback?
Maybe we could get the name from apps.json? Seems like not all widgets use their  id as WIDGETS key though

So you'd have something like this:
  function settings(back) {
    const mySettingsMenu = {
        '': { 'title': 'My Widget' },
        'Sound': {
            value: false,
            onchange: s => {s ? Bangle.beep() : false} // TODO: save new value
        },
        '< Back': back // provided by caller (settings app)
    };
    E.showMenu(mySettingsMenu)
  }
  WIDGETS["mywidget"]={
    /* other properties go here */
    name:"My widget",
    settings:settings,
  };

That sounds like a good idea. Maybe this could be more general though?
For instance if there was an app.settings.json it could be shown and loaded up. It's not just widgets that could benefit from this.
In terms of implementation there's appname.info that's auto-generated by the app loader, so we could add an entry in there if a settings file exists on upload.

That does seem a better solution, I'll give implementing something like that a try.

Nice - thanks! For detecting settings and setting the relevant bit in the app.info, just copy/paste this:
https://github.com/espruino/BangleApps/blob/master/js/appinfo.js#L61,L62
Then finding a list of apps with settings would look a lot like:
var apps = s.list(/\.info$/).map(app=>s.readJSON(app,1)).filter(app=>app&&app.settings);

authors: gfwilliams rigrig

repo: espruino/BangleApps

license: MIT


text:
[messages] overlapping lines when using unicode

Affected hardware version
Bangle 2
Your firmware version
2v14
The bug
Overlapping lines in notification from gadgetbridge

When I receive notification from signal (in groups) sometimes lines of unicode text are partially overlapping on the screen.
I suppose the reason is that the notification header contains: "Group name: Group member", which occupies two lines. And all the subsequent lines are then partially overlapping.
I was not able to reproduce it using gadgetbridge debug, since there you can only set a message, not the header.
I'm not sure if it's a bug in messages or in the gadgetbridge (bangle.js flavor).

Thanks - this is a tricky one to fix. The unicode can't be displayed natively by Bangle.js so it's being converted to an image on the phone.
The Bangle thinks it has chosen a smaller font, but because the text is now and image the font size can't be changed and it overlaps.
If we just changed it so the background of the text wasn't cleared, would that fix it for you?

Thanks, I'm not sure I understand the whole complexity of the issue.
So what you are suggesting is basically, replace "white" with "transparent" in the fond and hope that characters will not overlap?
I suppose it's better than just overwriting with "white", but still characters will overlap in some cases.
A few questions since I do not know how gadgetbridge interacts with messages.
Is there a reason why messages doesn't know the line height?
Or maybe there is a possibility to:
a) set a smaller font in gadgetbridge by default, e.g., as an option? I could then set "always use minimal font" in gadgetbridge to avoid the isse
b) let gadgetbridge (roughly) deduce the desired font size based on the text length

replace "white" with "transparent" in the fond and hope that characters will not overlap?

Yes - it's an easy tweak that shouldn't really break anything.

Is there a reason why messages doesn't know the line height?

It works out the height based on the font - but since it's an image (inside the text) the height isn't related to the font.

I could then set "always use minimal font" in gadgetbridge to avoid the isse

Yes, we could have a font size option - that could be added pretty easily

let gadgetbridge (roughly) deduce the desired font size based on the text length

Yes, it's possible - but also very likely it'll get it wrong!
Another option is to allow Bangle.js to automatically halve the size of images in text if they are too big (or double them if they are too big). which could work well too

I've just implemented the size config (and transparent background) - and it should roll out to the google play store in the next day or so

Thanks, @gfwilliams
I can confirm that we reduced font size + transparent background it looks much better!

Great! Thanks for the update!

authors: gfwilliams idavydov


text:
counter: Add danish translations

Add danish translations for counter on banglejs2. These are app-specific because I shortened them quite a lot to make them fit on the screen, so they might not be applicable for other apps.
This needs  #3576 to work.

Thanks!

source: gharchive/pull-request

authors: atjn thyttan


text:
Gadgetbridge Twist Music Control

Control your music app that handles multiple play-commands on your Gadgetbridge-connected phone. Comes in handy when you want to change the song but your second hand is unavailable.
I hope I have done everything correctly...

This looks great - thanks!

authors: gfwilliams radsvvid


text:
Remove list-reset placeholder from core file

Keep all list styles within the _lists.scss component.

#15

license: mit

license_source: bigquery


text:
Add home button that is accessible on every page

Should be able to navigate to the home/start page at any point

Encapsulated by #52

authors: sharon-wang vezwork

repo: esse-dev/borzoi


text:
Update librdkafka to 1.5.2 and kafkacat to 1.6.0

What's this PR about
I've updated librdkafka to 1.5.2 and kafkacat to 1.6.0.
TODO's:

[x] Run perfecto check on your spec file
[x] Write bibop tests
[x] Enable "Allow edits from maintainers" for this PR
[x] Update the messages below

Did you try to build the package with this spec?: Yes
Is this ready for review?: Yes

Looks good, merged. Thanks!

Packages were built and added to kaos-testing repository.

authors: andyone gongled

repo: essentialkaos/kaos-repo


text:
無 jQuery 版本的 id 查找問題

如果把 zipcode 的 div 放在第一個，就會因為還沒塞 Math.random().toString(36).substr(2, 10) 這個 id 而找不到 county 跟 district 元件

v2.0.4 已修正這個問題

謝謝，不過剛剛又看到另一個問題
如果我在 js 一次給完整的預設資料比如
county: { value: '臺北市' },
district: { value: '中正區' },
zipcode: { value: '100' }

雖然運作正常但 console 也會報錯，但是只要把 zipcode 的資料拿掉或是不要把 zipcode 的 div 放第一個一樣可以解決。
另外想請問非 jQuery 版以後會放到 npm 上嗎？

authors: Knovour essoduke

repo: essoduke/jQuery-TWzipcode


text:
Fix tiny typos in src/common/intl/messages/index.js.

Some people are sometimes reading comments. Yay! ;)

Thank you :-)

authors: cbioley steida

repo: este/este


text:
Version v1.12.2 in deno.land still uses unstable APIs. Culprit: https://github.com/eta-dev/eta/blob/v1.12.2/deno_dist/file-methods.ts

Hi!
The version v1.12.2 in deno.land still uses unstable APIs (https://deno.land/x/eta@v1.12.2/file-methods.ts). The culprit seems to be the tag v.12.2, see https://github.com/eta-dev/eta/blob/v1.12.2/deno_dist/file-methods.ts. Master at https://github.com/eta-dev/eta/blob/master/deno_dist/file-methods.ts is up to date.
This leads to a situation, where programs that use Eta v1.12.2 from deno.land still need to run with the --unstable flag.
Output for the command deno info https://deno.land/x/eta@v1.12.2/mod.ts (with cleaned cache):
Download https://deno.land/x/eta@v1.12.2/mod.ts
Download https://deno.land/x/eta@v1.12.2/parse.ts
Download https://deno.land/x/eta@v1.12.2/compile.ts
Download https://deno.land/x/eta@v1.12.2/compile-string.ts
Download https://deno.land/x/eta@v1.12.2/render.ts
Download https://deno.land/x/eta@v1.12.2/containers.ts
Download https://deno.land/x/eta@v1.12.2/file-handlers.ts
Download https://deno.land/x/eta@v1.12.2/config.ts
Download https://deno.land/x/eta@v1.12.2/file-helpers.ts
Download https://deno.land/x/eta@v1.12.2/polyfills.ts
Download https://deno.land/x/eta@v1.12.2/err.ts
Download https://deno.land/x/eta@v1.12.2/utils.ts
Download https://deno.land/x/eta@v1.12.2/storage.ts
Download https://deno.land/x/eta@v1.12.2/file-utils.ts
Download https://deno.land/x/eta@v1.12.2/file-methods.ts
Download https://deno.land/std@0.66.0/fs/mod.ts
Download https://deno.land/std@0.66.0/path/mod.ts
Download https://deno.land/std@0.66.0/path/glob.ts
Download https://deno.land/std@0.66.0/path/_constants.ts
Download https://deno.land/std@0.66.0/path/_interface.ts
Download https://deno.land/std@0.66.0/path/common.ts
Download https://deno.land/std@0.66.0/path/win32.ts
Download https://deno.land/std@0.66.0/path/posix.ts
Download https://deno.land/std@0.66.0/path/separator.ts
Download https://deno.land/std@0.66.0/fs/ensure_dir.ts
Download https://deno.land/std@0.66.0/fs/empty_dir.ts
Download https://deno.land/std@0.66.0/fs/write_json.ts
Download https://deno.land/std@0.66.0/fs/read_json.ts
Download https://deno.land/std@0.66.0/fs/ensure_file.ts
Download https://deno.land/std@0.66.0/fs/walk.ts
Download https://deno.land/std@0.66.0/fs/eol.ts
Download https://deno.land/std@0.66.0/fs/expand_glob.ts
Download https://deno.land/std@0.66.0/fs/exists.ts
Download https://deno.land/std@0.66.0/fs/move.ts
Download https://deno.land/std@0.66.0/fs/copy.ts
Download https://deno.land/std@0.66.0/fs/ensure_link.ts
Download https://deno.land/std@0.66.0/fs/ensure_symlink.ts
Download https://deno.land/std@0.66.0/fs/_util.ts
Download https://deno.land/std@0.66.0/_util/assert.ts
Download https://deno.land/std@0.66.0/path/_util.ts
local: (my path)
type: TypeScript
dependencies: 39 unique (total 132.91KB)

https://deno.land/x/eta@v1.12.2/mod.ts (684B)
├─┬ https://deno.land/x/eta@v1.12.2/compile-string.ts (3.01KB)
│ ├─┬ https://deno.land/x/eta@v1.12.2/config.ts (4.23KB)
│ │ ├─┬ https://deno.land/x/eta@v1.12.2/compile.ts (1.92KB)
│ │ │ ├── https://deno.land/x/eta@v1.12.2/compile-string.ts *
│ │ │ ├── https://deno.land/x/eta@v1.12.2/config.ts *
│ │ │ ├── https://deno.land/x/eta@v1.12.2/config.ts *
│ │ │ ├── https://deno.land/x/eta@v1.12.2/err.ts (1.29KB)
│ │ │ ├─┬ https://deno.land/x/eta@v1.12.2/file-handlers.ts (9.45KB)
│ │ │ │ ├── https://deno.land/x/eta@v1.12.2/compile.ts *
│ │ │ │ ├── https://deno.land/x/eta@v1.12.2/compile.ts *
│ │ │ │ ├── https://deno.land/x/eta@v1.12.2/config.ts *
│ │ │ │ ├── https://deno.land/x/eta@v1.12.2/config.ts *
│ │ │ │ ├── https://deno.land/x/eta@v1.12.2/err.ts *
│ │ │ │ ├─┬ https://deno.land/x/eta@v1.12.2/file-utils.ts (5.72KB)
│ │ │ │ │ ├── https://deno.land/x/eta@v1.12.2/config.ts *
│ │ │ │ │ ├── https://deno.land/x/eta@v1.12.2/err.ts *
│ │ │ │ │ └─┬ https://deno.land/x/eta@v1.12.2/file-methods.ts (180B)
│ │ │ │ │   ├─┬ https://deno.land/std@0.66.0/fs/mod.ts (480B)
│ │ │ │ │   │ ├─┬ https://deno.land/std@0.66.0/fs/copy.ts (8.45KB)
│ │ │ │ │   │ │ ├── https://deno.land/std@0.66.0/_util/assert.ts (405B)
│ │ │ │ │   │ │ ├─┬ https://deno.land/std@0.66.0/path/mod.ts (717B)
│ │ │ │ │   │ │ │ ├── https://deno.land/std@0.66.0/path/_constants.ts (2.35KB)
│ │ │ │ │   │ │ │ ├── https://deno.land/std@0.66.0/path/_interface.ts (657B)
│ │ │ │ │   │ │ │ ├─┬ https://deno.land/std@0.66.0/path/common.ts (1.14KB)
│ │ │ │ │   │ │ │ │ └─┬ https://deno.land/std@0.66.0/path/separator.ts (264B)
│ │ │ │ │   │ │ │ │   └── https://deno.land/std@0.66.0/path/_constants.ts *
│ │ │ │ │   │ │ │ ├─┬ https://deno.land/std@0.66.0/path/glob.ts (8.12KB)
│ │ │ │ │   │ │ │ │ ├── https://deno.land/std@0.66.0/path/_constants.ts *
│ │ │ │ │   │ │ │ │ ├── https://deno.land/std@0.66.0/path/mod.ts *
│ │ │ │ │   │ │ │ │ └── https://deno.land/std@0.66.0/path/separator.ts *
│ │ │ │ │   │ │ │ ├─┬ https://deno.land/std@0.66.0/path/posix.ts (12.67KB)
│ │ │ │ │   │ │ │ │ ├── https://deno.land/std@0.66.0/path/_constants.ts *
│ │ │ │ │   │ │ │ │ ├── https://deno.land/std@0.66.0/path/_interface.ts *
│ │ │ │ │   │ │ │ │ └─┬ https://deno.land/std@0.66.0/path/_util.ts (3.3KB)
│ │ │ │ │   │ │ │ │   ├── https://deno.land/std@0.66.0/path/_constants.ts *
│ │ │ │ │   │ │ │ │   └── https://deno.land/std@0.66.0/path/_interface.ts *
│ │ │ │ │   │ │ │ ├── https://deno.land/std@0.66.0/path/separator.ts *
│ │ │ │ │   │ │ │ └─┬ https://deno.land/std@0.66.0/path/win32.ts (27.36KB)
│ │ │ │ │   │ │ │   ├── https://deno.land/std@0.66.0/_util/assert.ts *
│ │ │ │ │   │ │ │   ├── https://deno.land/std@0.66.0/path/_constants.ts *
│ │ │ │ │   │ │ │   ├── https://deno.land/std@0.66.0/path/_interface.ts *
│ │ │ │ │   │ │ │   └── https://deno.land/std@0.66.0/path/_util.ts *
│ │ │ │ │   │ │ ├─┬ https://deno.land/std@0.66.0/fs/_util.ts (900B)
│ │ │ │ │   │ │ │ └── https://deno.land/std@0.66.0/path/mod.ts *
│ │ │ │ │   │ │ └─┬ https://deno.land/std@0.66.0/fs/ensure_dir.ts (1.41KB)
│ │ │ │ │   │ │   └── https://deno.land/std@0.66.0/fs/_util.ts *
│ │ │ │ │   │ ├─┬ https://deno.land/std@0.66.0/fs/empty_dir.ts (1.72KB)
│ │ │ │ │   │ │ └── https://deno.land/std@0.66.0/path/mod.ts *
│ │ │ │ │   │ ├── https://deno.land/std@0.66.0/fs/ensure_dir.ts *
│ │ │ │ │   │ ├─┬ https://deno.land/std@0.66.0/fs/ensure_file.ts (1.84KB)
│ │ │ │ │   │ │ ├── https://deno.land/std@0.66.0/path/mod.ts *
│ │ │ │ │   │ │ ├── https://deno.land/std@0.66.0/fs/_util.ts *
│ │ │ │ │   │ │ └── https://deno.land/std@0.66.0/fs/ensure_dir.ts *
│ │ │ │ │   │ ├─┬ https://deno.land/std@0.66.0/fs/ensure_link.ts (1.57KB)
│ │ │ │ │   │ │ ├── https://deno.land/std@0.66.0/path/mod.ts *
│ │ │ │ │   │ │ ├── https://deno.land/std@0.66.0/fs/_util.ts *
│ │ │ │ │   │ │ ├── https://deno.land/std@0.66.0/fs/ensure_dir.ts *
│ │ │ │ │   │ │ └── https://deno.land/std@0.66.0/fs/exists.ts (708B)
│ │ │ │ │   │ ├─┬ https://deno.land/std@0.66.0/fs/ensure_symlink.ts (2.01KB)
│ │ │ │ │   │ │ ├── https://deno.land/std@0.66.0/path/mod.ts *
│ │ │ │ │   │ │ ├── https://deno.land/std@0.66.0/fs/_util.ts *
│ │ │ │ │   │ │ ├── https://deno.land/std@0.66.0/fs/ensure_dir.ts *
│ │ │ │ │   │ │ └── https://deno.land/std@0.66.0/fs/exists.ts *
│ │ │ │ │   │ ├── https://deno.land/std@0.66.0/fs/eol.ts (714B)
│ │ │ │ │   │ ├── https://deno.land/std@0.66.0/fs/exists.ts *
│ │ │ │ │   │ ├─┬ https://deno.land/std@0.66.0/fs/expand_glob.ts (7.44KB)
│ │ │ │ │   │ │ ├── https://deno.land/std@0.66.0/_util/assert.ts *
│ │ │ │ │   │ │ ├── https://deno.land/std@0.66.0/path/mod.ts *
│ │ │ │ │   │ │ └─┬ https://deno.land/std@0.66.0/fs/walk.ts (4.35KB)
│ │ │ │ │   │ │   ├── https://deno.land/std@0.66.0/_util/assert.ts *
│ │ │ │ │   │ │   └── https://deno.land/std@0.66.0/path/mod.ts *
│ │ │ │ │   │ ├─┬ https://deno.land/std@0.66.0/fs/move.ts (1.43KB)
│ │ │ │ │   │ │ ├── https://deno.land/std@0.66.0/fs/_util.ts *
│ │ │ │ │   │ │ └── https://deno.land/std@0.66.0/fs/exists.ts *
│ │ │ │ │   │ ├── https://deno.land/std@0.66.0/fs/read_json.ts (798B)
│ │ │ │ │   │ ├── https://deno.land/std@0.66.0/fs/walk.ts *
│ │ │ │ │   │ └── https://deno.land/std@0.66.0/fs/write_json.ts (1.54KB)
│ │ │ │ │   └── https://deno.land/std@0.66.0/path/mod.ts *
│ │ │ │ ├── https://deno.land/x/eta@v1.12.2/polyfills.ts (294B)
│ │ │ │ └─┬ https://deno.land/x/eta@v1.12.2/utils.ts (2.78KB)
│ │ │ │   ├── https://deno.land/x/eta@v1.12.2/config.ts *
│ │ │ │   └── https://deno.land/x/eta@v1.12.2/polyfills.ts *
│ │ │ └── https://deno.land/x/eta@v1.12.2/polyfills.ts *
│ │ ├─┬ https://deno.land/x/eta@v1.12.2/containers.ts (278B)
│ │ │ ├── https://deno.land/x/eta@v1.12.2/compile.ts *
│ │ │ └─┬ https://deno.land/x/eta@v1.12.2/storage.ts (758B)
│ │ │   └── https://deno.land/x/eta@v1.12.2/utils.ts *
│ │ ├── https://deno.land/x/eta@v1.12.2/err.ts *
│ │ ├── https://deno.land/x/eta@v1.12.2/storage.ts *
│ │ └── https://deno.land/x/eta@v1.12.2/utils.ts *
│ ├─┬ https://deno.land/x/eta@v1.12.2/parse.ts (5.78KB)
│ │ ├── https://deno.land/x/eta@v1.12.2/config.ts *
│ │ ├── https://deno.land/x/eta@v1.12.2/err.ts *
│ │ └── https://deno.land/x/eta@v1.12.2/utils.ts *
│ └── https://deno.land/x/eta@v1.12.2/parse.ts *
├── https://deno.land/x/eta@v1.12.2/compile.ts *
├── https://deno.land/x/eta@v1.12.2/config.ts *
├── https://deno.land/x/eta@v1.12.2/containers.ts *
├── https://deno.land/x/eta@v1.12.2/file-handlers.ts *
├─┬ https://deno.land/x/eta@v1.12.2/file-helpers.ts (504B)
│ ├── https://deno.land/x/eta@v1.12.2/config.ts *
│ └── https://deno.land/x/eta@v1.12.2/file-handlers.ts *
├── https://deno.land/x/eta@v1.12.2/parse.ts *
└─┬ https://deno.land/x/eta@v1.12.2/render.ts (3.87KB)
  ├── https://deno.land/x/eta@v1.12.2/compile.ts *
  ├── https://deno.land/x/eta@v1.12.2/compile.ts *
  ├── https://deno.land/x/eta@v1.12.2/config.ts *
  ├── https://deno.land/x/eta@v1.12.2/config.ts *
  ├── https://deno.land/x/eta@v1.12.2/err.ts *
  ├── https://deno.land/x/eta@v1.12.2/file-handlers.ts *
  └── https://deno.land/x/eta@v1.12.2/polyfills.ts *

Hmm it seems the build process may have glitched or something so the changes weren't included?? However once I do the release of v1rt1ls changes to update for latest Deno version it should be included in the release then....

Okay as an update it seems the problem lied in my own handling of Git, where there was some conflicts in merges I never fixed or something.

Closed by 1.12.3

repo: eta-dev/eta


text:
Publish package on npm

With the release op 1.4.0 we are going to publish this package on npm

+1

+1

:+1:

When is this going to happen?

@binarykitchen when 1.4 is ready

1.4 should be ready around the end of the month @binarykitchen

@eternicode do you want to publish the release on npm? Or can I do it?
Instructions: https://gist.github.com/coolaj86/1318304

The package is published on npm! https://www.npmjs.com/package/bootstrap-datepicker

@eternicode just create a account like described in the first steps here (https://gist.github.com/coolaj86/1318304) and I will add you as a maintainer!

authors: A---- Dakuan acrobat binarykitchen hebbet theofidry

repo: eternicode/bootstrap-datepicker


text:
close piker then call  hide.bs.modal?

$("#myModal" ) .on("hide.bs.modal",
function(e) {
alert("BUG");
});

I found the same problem on "show.bs.modal" event

Me too

authors: Pulsating alanpeng899 ldjdsc


text:
Cannot run lmql-serve - SyntaxError

I anticipate I am missing something fundamental or making some basic mistake - bear with me :bow:
I tried to run lmql-serve to serve the hugging face quantized model with the following command:
poetry run lmql serve-model --loader auto-gptq --cuda --static TheBloke/Llama-2-7B-GPTQ

other commands i tried

poetry run lmql serve-model --loader auto-gptq --cuda TheBloke/Llama-2-7B-GPTQ
poetry run lmql serve-model --loader auto-gptq --static TheBloke/Llama-2-7B-GPTQ
poetry run lmql serve-model --loader auto-gptq TheBloke/Llama-2-7B-GPTQ
poetry run lmql serve-model TheBloke/Llama-2-7B-GPTQ

SyntaxError
But it fails with the following error:
Traceback (most recent call last):
  File "/home/jumski/.asdf/installs/python/3.10.9/lib/python3.10/runpy.py", line 187, in _run_module_as_main
    mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
  File "/home/jumski/.asdf/installs/python/3.10.9/lib/python3.10/runpy.py", line 110, in _get_module_details
    __import__(pkg_name)
  File "/home/jumski/.cache/pypoetry/virtualenvs/langchain-sandbox-guzw3mW8-py3.10/lib/python3.10/site-packages/lmql/__init__.py", line 17, in <module>
    import lmql.runtime.lmql_runtime as lmql_runtime
  File "/home/jumski/.cache/pypoetry/virtualenvs/langchain-sandbox-guzw3mW8-py3.10/lib/python3.10/site-packages/lmql/runtime/lmql_runtime.py", line 12, in <module>
    from lmql.runtime.interpreter import PromptInterpreter
  File "/home/jumski/.cache/pypoetry/virtualenvs/langchain-sandbox-guzw3mW8-py3.10/lib/python3.10/site-packages/lmql/runtime/interpreter.py", line 2, in <module>
    import asyncio
  File "/home/jumski/.cache/pypoetry/virtualenvs/langchain-sandbox-guzw3mW8-py3.10/lib/python3.10/site-packages/asyncio/__init__.py", line 21, in <module>
    from .base_events import *
  File "/home/jumski/.cache/pypoetry/virtualenvs/langchain-sandbox-guzw3mW8-py3.10/lib/python3.10/site-packages/asyncio/base_events.py", line 296
    future = tasks.async(future, loop=self)
                   ^^^^^
SyntaxError: invalid syntax

My environment
lmql
I installed lmql via poetry add lmql[hf]:
❯ poetry show lmql
 name         : lmql
 version      : 0.0.6.5
 description  : A query language for language models.

dependencies
 - accelerate *
 - astunparse 1.6.3
 - numpy *
 - openai *
 - psutil *
 - termcolor *
 - tiktoken *
 - transformers >=4.28.1

python
❯ poetry run python --version
Python 3.10.9

OS / GPU
I'm on Manjaro Linux, using RTX 3090

I am not familiar with poetry, but it looks like an issue with the python version you are running with. Can you provide the more details about your environment.
Note also that --loader auto-gptq is currently only available on 'main' not in 0.0.6.5, as we have not published a release with it.

I got the same error when launching it via:
lmql serve-model llama.cpp:orca-mini-3b.ggmlv3.q4_0.bin
Debian testing , Python 3.11

Can you confirm that you can run the following on your system with the same python version that you are running LMQL with:
python -c "import asyncio"

This looks to happen entirely in asyncio code, which is very odd.

Found this, which may be related: https://github.com/pyinstaller/pyinstaller/issues/6156#issuecomment-904534078
Do you have an compatibility version of asyncio installed?

python -c "import asyncio"

works fine

Do you have an compatibility version of asyncio installed?

pip uninstall asyncio
Wow. Now i get a different error. Seems to be the case.

Has this issue been resolved by uninstalling asyncio? Were you able to resolve the other error that was raised?

authors: h3ndrik jumski lbeurerkellner

repo: eth-sri/lmql


text:
🛑 Piped is down

In 675de64, Piped (https://piped.beans.team) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Piped is back up in 54ab69b after 7 minutes.

repo: ethanrusz/status


text:
feat(framework): disallow assign of fixedbytes of size X to bytes of size Y when X != Y

🗒 Description
fields of type fixedbytesizeN should not be assignable to bytes of size other than N
uvx --with=tox-uv tox
🔗 Related Issues
https://github.com/ethereum/execution-spec-tests/pull/1008
✅ Checklist

[x] All: Set appropriate labels for the changes.
[ ] All: Considered squashing commits to improve commit history.
[ ] All: Added an entry to CHANGELOG.md.
[ ] All: Considered updating the online docs in the ./docs/ directory.
[x] Tests: All converted JSON/YML tests from ethereum/tests have been added to converted-ethereum-tests.txt.
[x] Tests: A PR with removal of converted JSON/YML tests from ethereum/tests have been opened.
[x] Tests: Included the type and version of evm t8n tool used to locally execute test cases:  e.g., ref with commit hash or geth 1.13.1-stable-3f40e65.
[x] Tests: Ran mkdocs serve locally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.

Pushed a solution, why not to be explicit about what you want to achieve:
`

data=Hash(recipient),

data=left_pad_zeros_up_to_size(recipient, 32),
`

repo: ethereum/execution-spec-tests


text:
std::abi

What was wrong?
How was it fixed?
To-Do

[ ] OPTIONAL: Update Spec if applicable

[ ] Add entry to the release notes (may forgo for trivial changes)

[ ] Clean up commit history

Just a question: Is this PR targeting the current fe implementation? I thought you would work on the std for fe-v2 after testing implementation.

Just a question: Is this PR targeting the current fe implementation? I thought you would work on the std for fe-v2 after testing implementation.

this is some non-committal sketch code, ultimately Im targeting v2. is the v2 branch stable enough to work on?

I don't know how stable it should be for you to start working on it. At least the new parser will work. For semantics, I wouldn't add projection stuff, so basically, it's the same except for trait resolving, type inference, and pointer types.
As I said, some std implementations are necessary to implement v2, like encode/decode stuff. So, It'd be better for me if you start targeting v2 implementation. But it's up to you.

authors: Y-Nak g-r-a-n-t

repo: ethereum/fe


text:
Implement merkle proof verification

The LightChain has a method to fetch proofs but currently there's no way to verify those. We need that

This might actually belong in the py-trie codebase but tracking it here for now is fine, or even implementing it here and then migrating it to that codebase is fine.

Implemented and py-trie: https://github.com/ethereum/py-trie/commit/1c4fbbe080ddf51a439cd596098dead17fb78638

authors: gsalgado pipermerriam

repo: ethereum/py-evm


text:
Fix CI failure: Add config to FakeAsyncBeaconChainDB.__init__

What was wrong?
config is added in BaseBeaconChainDB. Sorry I made the CI fail because I didn't rebase before merging my PR.
How was it fixed?
Add config in FakeAsyncBeaconChainDB, and pass the corresponding configs in the tests.
Cute Animal Picture

Thank you for the review:)

repo: ethereum/trinity


text:
fidesctl generate system aws fails with error "No module named 'boto3'"

Bug Description
When attempting to use generate system aws on 1.4.2, I get an immediate error where boto3 is missing. Looking at requirements.txt I see we haven't declared it as a dependency, so I suspect this is an easy fix.
Stacktrace:
(venv) ~/git/fidesdemo% fidesctl generate system aws .fides/aws_systems.yml
Traceback (most recent call last):
  File "/Users/neville/git/fidesdemo/venv/bin/fidesctl", line 8, in <module>
    sys.exit(cli())
  File "/Users/neville/git/fidesdemo/venv/lib/python3.9/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/Users/neville/git/fidesdemo/venv/lib/python3.9/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/Users/neville/git/fidesdemo/venv/lib/python3.9/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/Users/neville/git/fidesdemo/venv/lib/python3.9/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/Users/neville/git/fidesdemo/venv/lib/python3.9/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/Users/neville/git/fidesdemo/venv/lib/python3.9/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/Users/neville/git/fidesdemo/venv/lib/python3.9/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/Users/neville/git/fidesdemo/venv/lib/python3.9/site-packages/click/decorators.py", line 21, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/Users/neville/git/fidesdemo/venv/lib/python3.9/site-packages/fidesctl/cli/generate_commands.py", line 72, in generate_system_aws
    with_analytics(
  File "/Users/neville/git/fidesdemo/venv/lib/python3.9/site-packages/fidesctl/cli/utils.py", line 98, in with_analytics
    raise err
  File "/Users/neville/git/fidesdemo/venv/lib/python3.9/site-packages/fidesctl/cli/utils.py", line 94, in with_analytics
    return command_handler(**kwargs)
  File "/Users/neville/git/fidesdemo/venv/lib/python3.9/site-packages/fidesctl/core/system.py", line 224, in generate_system_aws
    aws_systems = generate_aws_systems(organization_key=organization_key)
  File "/Users/neville/git/fidesdemo/venv/lib/python3.9/site-packages/fidesctl/core/system.py", line 204, in generate_aws_systems
    aws_systems = [
  File "/Users/neville/git/fidesdemo/venv/lib/python3.9/site-packages/fidesctl/core/system.py", line 207, in <listcomp>
    for found_system in generate_function(organization_key)
  File "/Users/neville/git/fidesdemo/venv/lib/python3.9/site-packages/fidesctl/core/system.py", line 65, in generate_redshift_systems
    describe_clusters = describe_redshift_clusters()
  File "/Users/neville/git/fidesdemo/venv/lib/python3.9/site-packages/fidesctl/core/system.py", line 22, in describe_redshift_clusters
    import boto3
ModuleNotFoundError: No module named 'boto3'

Steps to Reproduce

pip install fidesctl on 1.4.2
Setup your local config
Run fidesctl generate system aws .fides/aws_systems.yml
See boto3 error

Expected behavior
This should run a system scan of AWS.
Workaround
I can run pip install boto3 and the command works as expected.
Environment

Version: 1.4.2
OS: Mac OSX
Python Version: 3.9.10
Docker Version: 20.10.11

this requires installing the aws dependencies via pip install fidesctl[aws]

we could add a check here that throw an error if the boto import fails

authors: NevilleS ThomasLaPiana

repo: ethyca/fides


text:
SaaS connector docs

Purpose
To document the following:

What is a SaaS connector
What is a SaaS config schema
Steps to create a new SaaS connection via the Fidesops API

Changes
Checklist

[ ] Applicable documentation updated (guides, quickstart, postman collections, tutorial, fidesdemo, database diagram)
[ ] Good unit test/integration test coverage
[ ] This PR contains a DB migration. If checked, the reviewer should confirm with the author that the down_revision correctly references the previous migration before merging
[ ] The Run Unsafe PR Checks label has been applied, and checks have passed, if this PR touches any external services

Understand you're just getting started @galvana, just wanted to note that the main thing I'd like to see here in the end are the differences with the saas configs that I remember from review including:

saas config references can only go one-way (from)
the corresponding Dataset shouldn't have the identities or references
the fides key on the saas config and the dataset need to match
describe the "placeholder annotations" - those are pretty confusing
saas configs are only relevant for ConnectionConfigs of type "saas"
more explanations of the "data_path" param
Where does "data_type" go? You've mostly put them in the Dataset, but you have one example in the mailchimp  saas config too
Talk a little bit about how the two are merged

Thanks @galvana + @eastandwestwind, brilliant work and very nearly there!

authors: galvana pattisdr seanpreston

repo: ethyca/fidesops


text:
Review documentation of Euler Angles

When I read the documentation of the Euler angles (ZYX for example)
http://ethz-asl-lr.bitbucket.org/kindr/page_rotations.html
it isn't possible that these diagrams fit for both active and passive rotations. Can someone clarify this? Maybe first here, and then in the documentation.

This has been changed for kindr 1.0.0.

authors: furgalep gehrinch

repo: ethz-asl/kindr


text:
Invalid octet 0x80 in OID enoding

I'm getting this error thrown here:
https://github.com/etingof/pysnmp/blob/0aa119f1aaa9dee756aeaf65cd77c72581adcf36/pysnmp/proto/rfc3412.py#L348
The response is from a real device, and is accepted fine by net-snmp and is decoded by tcpdump.  Here is a packet capture of the response PDU.
12:59:42.641343 IP 10.102.2.18.161 > 209.251.86.58.50921:  GetResponse(41)
.1.3.6.1.4.1.32584.1.8.5.1.0=12
        0x0000:  4500 0058 cdd9 4000 7e11 fa0d 0a66 0212  E..X..@.~....f..
        0x0010:  d1fb 563a 00a1 c6e9 0044 f02c 3082 0038  ..V:.....D.,0..8
        0x0020:  0201 0004 0670 7562 6c69 63a2 8200 2902  .....public...).
        0x0030:  0475 f671 9902 0100 0201 0030 8200 1930  .u.q.......0...0
        0x0040:  8200 1506 8200 0e2b 0601 0401 8081 fe48  .......+.......H
        0x0050:  0108 0501 0002 010c                      ........

Looks like parsing error. Can you see the original exception? If you enable pysnmp debugging and retry that request:
from pysnmp import debug
debug.setLogger(debug.Debug('all'))

It should get logged here:
 debug.logger & debug.flagMP and debug.logger('receiveMessage: %s' % (sys.exc_info()[1],))

yes
2017-12-20 15:18:24,106 pysnmp: receiveMessage: msgVersion 1, msg decoded
2017-12-20 15:18:24,106 pysnmp: receiveMessage: msgVersion 1, msg decoded
2017-12-20 15:18:24,107 pysnmp: receiveMessage: Invalid octet 0x80 in OID encoding
2017-12-20 15:18:24,107 pysnmp: receiveMessage: Invalid octet 0x80 in OID encoding

Here is the full traceback:
handle: <Handle AbstractTransportDispatcher._cbFun(<pysnmp.carri...x7f3e5f0b6b70>, ('10.102.2.18', 161), b'0\x82\x008\...0\x02\x01\x0e')>
Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/pysnmp/proto/rfc3412.py", line 331, in receiveMessage
    snmpEngine, transportDomain, transportAddress, wholeMsg
  File "/usr/lib/python3.5/site-packages/pysnmp/proto/mpmod/rfc2576.py", line 250, in prepareDataElements
    msg, restOfWholeMsg = decoder.decode(wholeMsg, asn1Spec=self._snmpMsgSpec)
  File "/usr/lib/python3.5/site-packages/pyasn1/codec/ber/decoder.py", line 1160, in __call__
    **options
  File "/usr/lib/python3.5/site-packages/pyasn1/codec/ber/decoder.py", line 497, in valueDecoder
    component, head = decodeFun(head, asn1Spec, **options)
  File "/usr/lib/python3.5/site-packages/pyasn1/codec/ber/decoder.py", line 1160, in __call__
    **options
  File "/usr/lib/python3.5/site-packages/pyasn1/codec/ber/decoder.py", line 687, in valueDecoder
    tagSet, length, state, **options
  File "/usr/lib/python3.5/site-packages/pyasn1/codec/ber/decoder.py", line 1160, in __call__
    **options
  File "/usr/lib/python3.5/site-packages/pyasn1/codec/ber/decoder.py", line 497, in valueDecoder
    component, head = decodeFun(head, asn1Spec, **options)
  File "/usr/lib/python3.5/site-packages/pyasn1/codec/ber/decoder.py", line 1160, in __call__
    **options
  File "/usr/lib/python3.5/site-packages/pyasn1/codec/ber/decoder.py", line 524, in valueDecoder
    component, head = decodeFun(head, asn1Spec, **options)
  File "/usr/lib/python3.5/site-packages/pyasn1/codec/ber/decoder.py", line 1160, in __call__
    **options
  File "/usr/lib/python3.5/site-packages/pyasn1/codec/ber/decoder.py", line 497, in valueDecoder
    component, head = decodeFun(head, asn1Spec, **options)
  File "/usr/lib/python3.5/site-packages/pyasn1/codec/ber/decoder.py", line 1160, in __call__
    **options
  File "/usr/lib/python3.5/site-packages/pyasn1/codec/ber/decoder.py", line 301, in valueDecoder
    raise error.PyAsn1Error('Invalid octet 0x80 in OID encoding')
pyasn1.error.PyAsn1Error: Invalid octet 0x80 in OID encoding

That error is thrown from code with this comment: ```
# ASN.1 spec forbids leading zeros (0x80) in OID
# encoding, tolerating it opens a vulnerability. See
# http://www.cosic.esat.kuleuven.be/publications/article-1432.pdf
# page 7

Well maybe so, but obviously I have some device that's sending that anyway.  Maybe a config switch to allow this?

And fwiw, here's how Wireshark decodes it.  I am not a ASN.1 expert so I will leave that to others.

@etingof do you have any thoughts on this?  It's a pretty big blocker for using this SNMP library with some devices.

authors: etingof scotloach

repo: etingof/pysnmp


text:
Support additional filtering in the mapping file?

Currently some of the parameters require custom tags in order to be exported correctly, although filtering could be sufficient.
For example, PRC_VINT[REG,PRC] = ~FI_Process(Region,TechName) should either be substituted by preprocessing and a custom tag or could be transformed to something like PRC_VINT[REG,PRC] = ~FI_Process(Region,TechName,Vintage:YES), but the latter would require allowing the mismatch between the number of columns in the mapping.

What do you think @siddharth-krishna ?

Perhaps we can try to implement the filter syntax first and see if that is sufficient? It's a more general operation so hopefully it applies elsewhere too.

Do you mean expanding the existing syntax (e.g. Attribute:ACT_COST) somehow?

Yes. Perhaps we should start thinking of a more general structure for this mapping file so that we can specify general operations like filter?

We definitely can start thinking about it. :-) Do you think allowing fewer columns on the right is doable already (e.g. PRC_VINT[REG,PRC] = ~FI_Process(Region,TechName,Vintage:YES) or PRC_VINT[REG,PRC] = ~FI_Process(Region,TechName,Vintage))?

authors: olejandro siddharth-krishna

repo: etsap-TIMES/times-excel-reader


text:
TypeError: Return value of Phan\Language\Scope::getParentScope() must be an instance of Phan\Language\Scope, null returned

Hi
I just updated phan to the latest version, and I'm now getting the following error when running:
~/.composer/vendor/etsy/phan/phan -i

TypeError: Return value of Phan\Language\Scope::getParentScope() must be an instance of Phan\Language\Scope, null returned in /home/oli/.composer/vendor/etsy/phan/src/Phan/Language/Scope.php:54
Stack trace:
#0 /home/oli/.composer/vendor/etsy/phan/src/Phan/Language/Scope.php(93): Phan\Language\Scope->getParentScope()
#1 /home/oli/.composer/vendor/etsy/phan/src/Phan/Language/Context.php(277): Phan\Language\Scope->getClassFQSEN()
#2 /home/oli/.composer/vendor/etsy/phan/src/Phan/Language/Context.php(296): Phan\Language\Context->getClassFQSEN()
#3 /home/oli/.composer/vendor/etsy/phan/src/Phan/Language/UnionType.php(535): Phan\Language\Context->getClassInScope(Object(Phan\CodeBase))
#4 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/ContextNode.php(167): Phan\Language\UnionType->asClassList(Object(Phan\CodeBase), Object(Phan\Language\Context))
#5 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/ContextNode.php(730): Phan\AST\ContextNode->getClassList()
#6 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/UnionTypeVisitor.php(934): Phan\AST\ContextNode->getClassConst()
#7 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php(57): Phan\AST\UnionTypeVisitor->visitClassConst(Object(ast\Node))
#8 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php(22): Phan\AST\Visitor\Element->acceptKindVisitor(Object(Phan\AST\UnionTypeVisitor))
#9 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/UnionTypeVisitor.php(116): Phan\AST\Visitor\KindVisitorImplementation->__invoke(Object(ast\Node))
#10 /home/oli/.composer/vendor/etsy/phan/src/Phan/Language/UnionType.php(151): Phan\AST\UnionTypeVisitor::unionTypeFromNode(Object(Phan\CodeBase), Object(Phan\Language\Context), Object(ast\Node), true)
#11 /home/oli/.composer/vendor/etsy/phan/src/Phan/Analysis/BinaryOperatorFlagVisitor.php(181): Phan\Language\UnionType::fromNode(Object(Phan\Language\Context), Object(Phan\CodeBase), Object(ast\Node))
#12 /home/oli/.composer/vendor/etsy/phan/src/Phan/Analysis/BinaryOperatorFlagVisitor.php(249): Phan\Analysis\BinaryOperatorFlagVisitor->visitBinaryOpCommon(Object(ast\Node))
#13 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php(300): Phan\Analysis\BinaryOperatorFlagVisitor->visitBinaryIsEqual(Object(ast\Node))
#14 /home/oli/.composer/vendor/etsy/phan/src/Phan/Analysis/BinaryOperatorFlagVisitor.php(60): Phan\AST\Visitor\Element->acceptBinaryFlagVisitor(Object(Phan\Analysis\BinaryOperatorFlagVisitor))
#15 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/UnionTypeVisitor.php(598): Phan\Analysis\BinaryOperatorFlagVisitor->__invoke(Object(ast\Node))
#16 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php(45): Phan\AST\UnionTypeVisitor->visitBinaryOp(Object(ast\Node))
#17 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php(22): Phan\AST\Visitor\Element->acceptKindVisitor(Object(Phan\AST\UnionTypeVisitor))
#18 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/UnionTypeVisitor.php(116): Phan\AST\Visitor\KindVisitorImplementation->__invoke(Object(ast\Node))
#19 /home/oli/.composer/vendor/etsy/phan/src/Phan/Language/UnionType.php(151): Phan\AST\UnionTypeVisitor::unionTypeFromNode(Object(Phan\CodeBase), Object(Phan\Language\Context), Object(ast\Node), true)
#20 /home/oli/.composer/vendor/etsy/phan/src/Phan/Analysis/PreOrderAnalysisVisitor.php(555): Phan\Language\UnionType::fromNode(Object(Phan\Language\Context), Object(Phan\CodeBase), Object(ast\Node))
#21 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php(107): Phan\Analysis\PreOrderAnalysisVisitor->visitIfElem(Object(ast\Node))
#22 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php(22): Phan\AST\Visitor\Element->acceptKindVisitor(Object(Phan\Analysis\PreOrderAnalysisVisitor))
#23 /home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php(252): Phan\AST\Visitor\KindVisitorImplementation->__invoke(Object(ast\Node))
#24 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php(107): Phan\BlockAnalysisVisitor->visitIfElem(Object(ast\Node))
#25 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php(22): Phan\AST\Visitor\Element->acceptKindVisitor(Object(Phan\BlockAnalysisVisitor))
#26 /home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php(203): Phan\AST\Visitor\KindVisitorImplementation->__invoke(Object(ast\Node))
#27 /home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php(401): Phan\BlockAnalysisVisitor->visitBranchedContext(Object(ast\Node))
#28 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php(105): Phan\BlockAnalysisVisitor->visitIf(Object(ast\Node))
#29 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php(22): Phan\AST\Visitor\Element->acceptKindVisitor(Object(Phan\BlockAnalysisVisitor))
#30 /home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php(113): Phan\AST\Visitor\KindVisitorImplementation->__invoke(Object(ast\Node))
#31 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php(312): Phan\BlockAnalysisVisitor->visit(Object(ast\Node))
#32 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php(147): Phan\AST\Visitor\KindVisitorImplementation->visitStmtList(Object(ast\Node))
#33 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php(22): Phan\AST\Visitor\Element->acceptKindVisitor(Object(Phan\BlockAnalysisVisitor))
#34 /home/oli/.composer/vendor/etsy/phan/src/Phan/Analysis.php(345): Phan\AST\Visitor\KindVisitorImplementation->__invoke(Object(ast\Node))
#35 /home/oli/.composer/vendor/etsy/phan/src/Phan/Phan.php(162): Phan\Analysis::analyzeFile(Object(Phan\CodeBase), './app/compiled_...')
#36 /home/oli/.composer/vendor/etsy/phan/src/Phan/ForkPool.php(101): Phan\Phan::Phan\{closure}(142, './app/compiled_...')
#37 /home/oli/.composer/vendor/etsy/phan/src/Phan/Phan.php(190): Phan\ForkPool->__construct(Array, Object(Closure), Object(Closure), Object(Closure))
#38 /home/oli/.composer/vendor/etsy/phan/src/phan.php(42): Phan\Phan::analyzeFileList(Object(Phan\CodeBase), Array)
#39 /home/oli/.composer/vendor/etsy/phan/phan(2): require_once('/home/oli/.comp...')
#40 {main}

My config file looks like this:
<?php

use \Phan\Config;
use \Phan\Issue;

/**
 * This configuration will be read and overlayed on top of the
 * default configuration. Command line arguments will be applied
 * after this file is read.
 *
 * @see src/Phan/Config.php
 * See Config for all configurable options.
 *
 * A Note About Paths
 * ==================
 *
 * Files referenced from this file should be defined as
 *
 * ```
 *   Config::projectPath('relative_path/to/file')
 * ```
 *
 * where the relative path is relative to the root of the
 * project which is defined as either the working directory
 * of the phan executable or a path passed in via the CLI
 * '-d' flag.
 */
return [

        // A list of directories that should be parsed for class and
        // method information. After excluding the directories
        // defined in exclude_analysis_directory_list, the remaining
        // files will be statically analyzed for errors.
        //
        // Thus, both first-party and third-party code being used by
        // your application should be included in this list.
        'directory_list' => ['./'],

        // A directory list that defines files that will be excluded
        // from static analysis, but whose class and method
        // information should be included.
        //
        // Generally, you'll want to include the directories for
        // third-party code (such as "vendor/") in this list.
        //
        // n.b.: If you'd like to parse but not analyze 3rd
        //       party code, directories containing that code
        //       should be added to the `directory_list` as
        //       to `excluce_analysis_directory_list`.
    'exclude_analysis_directory_list' => ['vendor', 'node_modules'],

        // Backwards Compatibility Checking. This is slow
        // and expensive, but you should consider running
        // it before upgrading your version of PHP to a
        // new version that has backward compatibility
        // breaks.
    'backward_compatibility_checks' => true,

        // Run a quick version of checks that takes less
        // time at the cost of not running as thorough
        // an analysis. You should consider setting this
        // to true only when you wish you had more issues
        // to fix in your code base.
        'quick_mode' => true,

        // If enabled, check all methods that override a
        // parent method to make sure its signature is
        // compatible with the parent's. This check
        // can add quite a bit of time to the analysis.
    'analyze_signature_compatibility' => false,

        // If true, missing properties will be created when
        // they are first seen. If false, we'll report an
        // error message if there is an attempt to write
        // to a class property that wasn't explicitly
        // defined.
    'allow_missing_properties' => true,

        // If enabled, scalars (int, float, bool, string, null)
        // are treated as if they can cast to each other.
    'scalar_implicit_cast' => true,

        // Include a progress bar in the output
    'progress_bar' => true,

        // The number of processes to fork off during the analysis
        // phase.
    'processes' => 12,

        // Add any issue types (such as 'PhanUndeclaredMethod')
        // here to inhibit them from being reported
    'suppress_issue_types' => [
        'PhanAccessNonStaticToStatic',
        'PhanAccessPropertyPrivate',
        'PhanAccessPropertyProtected',
        'PhanAccessSignatureMismatch',
        'PhanAccessSignatureMismatchInternal',
        'PhanAccessStaticToNonStatic',
        'PhanCompatibleExpressionPHP7',
        'PhanCompatiblePHP7',
        'PhanContextNotObject',
        'PhanDeprecatedClass',
        'PhanDeprecatedFunction',
        'PhanEmptyFile',
        'PhanNonClassMethodCall',
        'PhanNoopArray',
        'PhanNoopClosure',
        'PhanNoopConstant',
        'PhanNoopProperty',
        'PhanNoopVariable',
        'PhanParamReqAfterOpt',
        'PhanParamSpecial1',
        'PhanParamSpecial2',
        'PhanParamSpecial3',
        'PhanParamSpecial4',
        'PhanParamTooFew',
        'PhanParamTooFewInternal',
        'PhanParamTooMany',
        'PhanParamTooManyInternal',
        'PhanParamTypeMismatch',
        'PhanParentlessClass',
        'PhanRedefineClass',
        'PhanRedefineClassInternal',
        'PhanRedefineFunction',
        'PhanRedefineFunctionInternal',
        'PhanSignatureMismatch',
        'PhanSignatureMismatchInternal',
        'PhanStaticCallToNonStatic',
        'PhanSyntaxError',
        'PhanTraitParentReference',
        'PhanTypeArrayOperator',
        'PhanTypeArraySuspicious',
        'PhanTypeComparisonFromArray',
        'PhanTypeComparisonToArray',
        'PhanTypeConversionFromArray',
        'PhanTypeInstantiateAbstract',
        'PhanTypeInstantiateInterface',
        'PhanTypeInvalidLeftOperand',
        'PhanTypeInvalidRightOperand',
        'PhanTypeMismatchArgument',
        'PhanTypeMismatchArgumentInternal',
        'PhanTypeMismatchDefault',
        'PhanTypeMismatchForeach',
        'PhanTypeMismatchProperty',
        'PhanTypeMismatchReturn',
        'PhanTypeMissingReturn',
        'PhanTypeNonVarPassByRef',
        'PhanTypeParentConstructorCalled',
        'PhanTypeVoidAssignment',
        'PhanUnanalyzable',
        'PhanUndeclaredClass',
        'PhanUndeclaredClassCatch',
        'PhanUndeclaredClassConstant',
        'PhanUndeclaredClassInstanceof',
        'PhanUndeclaredClassMethod',
        'PhanUndeclaredClassReference',
        'PhanUndeclaredConstant',
        'PhanUndeclaredExtendedClass',
        'PhanUndeclaredFunction',
        'PhanUndeclaredInterface',
        'PhanUndeclaredMethod',
        'PhanUndeclaredProperty',
        'PhanUndeclaredStaticMethod',
        'PhanUndeclaredStaticProperty',
        'PhanUndeclaredTrait',
        'PhanUndeclaredTypeParameter',
        'PhanUndeclaredTypeProperty',
        'PhanUndeclaredVariable',
        'PhanUnreferencedClass',
        'PhanUnreferencedConstant',
        'PhanUnreferencedMethod',
        'PhanUnreferencedProperty',
        'PhanVariableUseClause',
    ],
];

Any ideas? I just want to scan for PHP7 compatibility errors

Taking a look.

@oligriffiths Any chance you could send me the line its failing on with any secret stuff removed or obfuscated?

I've no idea what it's failing on, that error is generated by Phan itself

Ah, I can see it's one of our compiled templates, let me take a look and see.

But looking at your code, you're allowing scope to be null in the constructor, but you're enforcing it to have a return value of Scope, so theres an issue there anyway...

This is a long shot in that I don't yet understand where the issue is coming from, but can you pull and try it again? The patch https://github.com/etsy/phan/commit/6ac6454086bf054a9d16496dd1f2721a1486e96d makes certain that we aren't in a class, method or function when in the global scope.

Still getting the same error
TypeError: Return value of Phan\Language\Scope::getParentScope() must be an instance of Phan\Language\Scope, null returned in /home/oli/.composer/vendor/etsy/phan/src/Phan/Language/Scope.php:54
Stack trace:
#0 /home/oli/.composer/vendor/etsy/phan/src/Phan/Language/Scope.php(93): Phan\Language\Scope->getParentScope()
#1 /home/oli/.composer/vendor/etsy/phan/src/Phan/Language/Context.php(277): Phan\Language\Scope->getClassFQSEN()
#2 /home/oli/.composer/vendor/etsy/phan/src/Phan/Language/Context.php(296): Phan\Language\Context->getClassFQSEN()
#3 /home/oli/.composer/vendor/etsy/phan/src/Phan/Language/UnionType.php(535): Phan\Language\Context->getClassInScope(Object(Phan\CodeBase))
#4 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/ContextNode.php(167): Phan\Language\UnionType->asClassList(Object(Phan\CodeBase), Object(Phan\Language\Context))
#5 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/ContextNode.php(226): Phan\AST\ContextNode->getClassList()
#6 /home/oli/.composer/vendor/etsy/phan/src/Phan/Analysis/PostOrderAnalysisVisitor.php(1113): Phan\AST\ContextNode->getMethod('loadEnvironment', false)
#7 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php(117): Phan\Analysis\PostOrderAnalysisVisitor->visitMethodCall(Object(ast\Node))
#8 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php(22): Phan\AST\Visitor\Element->acceptKindVisitor(Object(Phan\Analysis\PostOrderAnalysisVisitor))
#9 /home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php(124): Phan\AST\Visitor\KindVisitorImplementation->__invoke(Object(ast\Node))
#10 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php(237): Phan\BlockAnalysisVisitor->visit(Object(ast\Node))
#11 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php(117): Phan\AST\Visitor\KindVisitorImplementation->visitMethodCall(Object(ast\Node))
#12 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php(22): Phan\AST\Visitor\Element->acceptKindVisitor(Object(Phan\BlockAnalysisVisitor))
#13 /home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php(114): Phan\AST\Visitor\KindVisitorImplementation->__invoke(Object(ast\Node))
#14 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php(312): Phan\BlockAnalysisVisitor->visit(Object(ast\Node))
#15 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php(147): Phan\AST\Visitor\KindVisitorImplementation->visitStmtList(Object(ast\Node))
#16 /home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php(22): Phan\AST\Visitor\Element->acceptKindVisitor(Object(Phan\BlockAnalysisVisitor))
#17 /home/oli/.composer/vendor/etsy/phan/src/Phan/Analysis.php(363): Phan\AST\Visitor\KindVisitorImplementation->__invoke(Object(ast\Node))
#18 /home/oli/.composer/vendor/etsy/phan/src/Phan/Phan.php(162): Phan\Analysis::analyzeFile(Object(Phan\CodeBase), './app/bootstrap...')
#19 /home/oli/.composer/vendor/etsy/phan/src/Phan/ForkPool.php(101): Phan\Phan::Phan\{closure}(262, './app/bootstrap...')
#20 /home/oli/.composer/vendor/etsy/phan/src/Phan/Phan.php(190): Phan\ForkPool->__construct(Array, Object(Closure), Object(Closure), Object(Closure))
#21 /home/oli/.composer/vendor/etsy/phan/src/phan.php(42): Phan\Phan::analyzeFileList(Object(Phan\CodeBase), Array)
#22 /home/oli/.composer/vendor/etsy/phan/phan(2): require_once('/home/oli/.comp...')
#23 {main}

Weirdly, app/bootstrap validates fine if I path directly to it

Seems like if the -l flag is set, you can't path directly to a file, it will evaluate every file in the directory specified in -l. Is there a way to tell it to analyze an entire directory but only parse a specific file?

Also getting the following error:
/home/oli/.composer/vendor/etsy/phan/src/Phan/Analysis/ConditionVisitor.php:255 [8] Undefined index: name
#0  phan_error_handler() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/Analysis/ConditionVisitor.php:255]
#1  Phan\Analysis\ConditionVisitor->visitCall() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php:49]
#2  Phan\AST\Visitor\Element->acceptKindVisitor() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:22]
#3  Phan\AST\Visitor\KindVisitorImplementation->__invoke() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/Analysis/PreOrderAnalysisVisitor.php:564]
#4  Phan\Analysis\PreOrderAnalysisVisitor->visitIfElem() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php:107]
#5  Phan\AST\Visitor\Element->acceptKindVisitor() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:22]
#6  Phan\AST\Visitor\KindVisitorImplementation->__invoke() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php:258]
#7  Phan\BlockAnalysisVisitor->visitIfElem() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php:107]
#8  Phan\AST\Visitor\Element->acceptKindVisitor() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:22]
#9  Phan\AST\Visitor\KindVisitorImplementation->__invoke() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php:209]
#10 Phan\BlockAnalysisVisitor->visitBranchedContext() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php:407]
#11 Phan\BlockAnalysisVisitor->visitIf() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php:105]
#12 Phan\AST\Visitor\Element->acceptKindVisitor() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:22]
#13 Phan\AST\Visitor\KindVisitorImplementation->__invoke() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php:114]
#14 Phan\BlockAnalysisVisitor->visit() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:312]
#15 Phan\AST\Visitor\KindVisitorImplementation->visitStmtList() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php:147]
#16 Phan\AST\Visitor\Element->acceptKindVisitor() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:22]
#17 Phan\AST\Visitor\KindVisitorImplementation->__invoke() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php:281]
#18 Phan\BlockAnalysisVisitor->visitIfElem() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php:107]
#19 Phan\AST\Visitor\Element->acceptKindVisitor() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:22]
#20 Phan\AST\Visitor\KindVisitorImplementation->__invoke() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php:209]
#21 Phan\BlockAnalysisVisitor->visitBranchedContext() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php:407]
#22 Phan\BlockAnalysisVisitor->visitIf() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php:105]
#23 Phan\AST\Visitor\Element->acceptKindVisitor() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:22]
#24 Phan\AST\Visitor\KindVisitorImplementation->__invoke() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php:114]
#25 Phan\BlockAnalysisVisitor->visit() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:312]
#26 Phan\AST\Visitor\KindVisitorImplementation->visitStmtList() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php:147]
#27 Phan\AST\Visitor\Element->acceptKindVisitor() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:22]
#28 Phan\AST\Visitor\KindVisitorImplementation->__invoke() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php:114]
#29 Phan\BlockAnalysisVisitor->visit() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:172]
#30 Phan\AST\Visitor\KindVisitorImplementation->visitForeach() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php:91]
#31 Phan\AST\Visitor\Element->acceptKindVisitor() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:22]
#32 Phan\AST\Visitor\KindVisitorImplementation->__invoke() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php:114]
#33 Phan\BlockAnalysisVisitor->visit() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:312]
#34 Phan\AST\Visitor\KindVisitorImplementation->visitStmtList() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php:147]
#35 Phan\AST\Visitor\Element->acceptKindVisitor() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:22]
#36 Phan\AST\Visitor\KindVisitorImplementation->__invoke() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php:281]
#37 Phan\BlockAnalysisVisitor->visitIfElem() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php:107]
#38 Phan\AST\Visitor\Element->acceptKindVisitor() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:22]
#39 Phan\AST\Visitor\KindVisitorImplementation->__invoke() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php:209]
#40 Phan\BlockAnalysisVisitor->visitBranchedContext() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php:407]
#41 Phan\BlockAnalysisVisitor->visitIf() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php:105]
#42 Phan\AST\Visitor\Element->acceptKindVisitor() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:22]
#43 Phan\AST\Visitor\KindVisitorImplementation->__invoke() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php:114]
#44 Phan\BlockAnalysisVisitor->visit() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:312]
#45 Phan\AST\Visitor\KindVisitorImplementation->visitStmtList() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php:147]
#46 Phan\AST\Visitor\Element->acceptKindVisitor() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:22]
#47 Phan\AST\Visitor\KindVisitorImplementation->__invoke() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php:369]
#48 Phan\BlockAnalysisVisitor->visitClosedContext() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php:459]
#49 Phan\BlockAnalysisVisitor->visitMethod() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php:115]
#50 Phan\AST\Visitor\Element->acceptKindVisitor() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:22]
#51 Phan\AST\Visitor\KindVisitorImplementation->__invoke() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php:114]
#52 Phan\BlockAnalysisVisitor->visit() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:312]
#53 Phan\AST\Visitor\KindVisitorImplementation->visitStmtList() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php:147]
#54 Phan\AST\Visitor\Element->acceptKindVisitor() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:22]
#55 Phan\AST\Visitor\KindVisitorImplementation->__invoke() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php:369]
#56 Phan\BlockAnalysisVisitor->visitClosedContext() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php:446]
#57 Phan\BlockAnalysisVisitor->visitClass() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php:55]
#58 Phan\AST\Visitor\Element->acceptKindVisitor() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:22]
#59 Phan\AST\Visitor\KindVisitorImplementation->__invoke() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/BlockAnalysisVisitor.php:114]
#60 Phan\BlockAnalysisVisitor->visit() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:312]
#61 Phan\AST\Visitor\KindVisitorImplementation->visitStmtList() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/Element.php:147]
#62 Phan\AST\Visitor\Element->acceptKindVisitor() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/AST/Visitor/KindVisitorImplementation.php:22]
#63 Phan\AST\Visitor\KindVisitorImplementation->__invoke() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/Analysis.php:363]
#64 Phan\Analysis::analyzeFile() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/Phan.php:162]
#65 Phan\Phan::Phan\{closure}() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/ForkPool.php:101]
#66 Phan\ForkPool->__construct() called at [/home/oli/.composer/vendor/etsy/phan/src/Phan/Phan.php:190]
#67 Phan\Phan::analyzeFileList() called at [/home/oli/.composer/vendor/etsy/phan/src/phan.php:42]
#68 require_once(/home/oli/.composer/vendor/etsy/phan/src/phan.php) called at [/home/oli/.composer/vendor/etsy/phan/phan:2]

@oligriffiths Ah, I misinterpreted the trace last time. Can you pull and try again?

Still seeing the same errors being emitted.

Any chance you have a few minutes to chat on Gitter (https://gitter.im/etsy/phan?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge) or in #phan on Freenode?

Simplified this as https://github.com/etsy/phan/issues/241 - closing this one.

authors: morria oligriffiths

repo: etsy/phan


text:
🛑 cr1.staging (IPv4, 5060/TCP) is down

In d4989e2, cr1.staging (IPv4, 5060/TCP) (cr1.staging.ettelabs.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cr1.staging (IPv4, 5060/TCP) is back up in db4659e after 12 minutes.

repo: ettelabsinc/ette-uptimejs


text:
http://localhost:8080/trustList , when accessing it after deployment getting 404 not found error.

After deployment when accessing http://localhost:8080/trustList getting below error. Kindly help to resolve it.
C:\Users\VVSA\Downloads\curl-7.78.0_6-win64-mingw\curl-7.78.0-win64-mingw\bin>curl -X GET http://localhost:8080/trustList -H "accept: application/json" -H "X-SSL-Client-SHA256: 397da9eb17467a2b3b83704ab6490a540bef43e84f06a6bd885e6621572da401" -H "X-SSL-Client-DN: C=NL"

Not Found

Access Error: 404 -- Not Found
Cannot open document for: /trustList

Hi @arunextasy we are not able to reproduce your issue.
How did you start the gateway?


text:
Backend - Local Testing

Is your feature request related to a problem? Please describe.
When testing locally, there is persisten CORS errors and as a result makes testing difficult.
Describe the solution you'd like
When running the serverMain.go file, create a parameter flag to allow for local testing.
Describe alternatives you've considered
N/A
Additional context
N/A

Closed by PR #84

repo: euanwm/OpenWeightlifting


text:
0.2.0 Branch

@rslinckx would you mind checking out the 0.2 branch? With this branch I basically wanted to correct the wrongs that were present in 0.1.0, and make Mailthon a better library. These changes were made:

Envelope is now a wrapper over Enclosure objects. This means that the mail_from and rcpt_to addresses can be set without subclass hackery. Also, no more unnecessary multipart emails which (take up a little more bandwidth due to the need for boundaries) unless required.
Enclosure objects now have a sender and receiver property, as well as a string method which means they can be sent via the Postman class.

I was about to add pluggable transports and replace the Postman class with something like Session and Transport but I don't really know if that's useful since I don't swap out the transports that often.
Also do you think that Middleware should have a setup and teardown method instead of just __call__? This will make it far easier to teardown temporary resources that might have been allocated in the life of the middleware.
cc @mrleeh, @kootenpv

It looks great !
Regarding pluggable transports, i don't think there's a need for that at this stage.
Regarding Middleware, maybe there should be some kind of event system (before_connect, before_logout, etc) and middle ware are just subscribers to these events ?

@rslinckx thanks for reminding me of the hooks pattern, I will implement it once I ironed out the bugs and work out how to embed images :smirk:

Progress Update: Sorry for the lack of progress, was really demotivated and bogged on by exams for a while. :sweat_smile:

Response((status_code, message)) => Response(status_code, message), uses namedtuples underneath.
Worked on the tests so that they're more understandable.
High level APIs remain unchanged.

IMHO most of mailthon is already quite stable and solid. Currently I am thinking of extracting the mime-handling part out into a separate package, so that mailthon focuses on SMTP and wrapping stuff around the mime-handling library.
@rslinckx can you recommend/step up as a maintainer? I am unable to actively maintain it for the coming half-year or so due to A-levels.

authors: eugene-eeo rslinckx

repo: eugene-eeo/mailthon


text:
Command line arguments - retest

retesting for the jenkins build

retest this please

Okay on it!

retest this please

repo: eugenp/tutorials


text:
jacob@initialcommit.io - A quick and practical example of Hexagonal Architecture in Java

Submitting this for my Baeldung evaluation article.

Closing per instructions.


text:
Show the current status in the UI

This includes a rewrite of the UI.

Use SignalR instead of raw websockets
Some tailwind styling
Show configuration and simulated state components

Also:

Implement overriding messages

Since the timeout / movement failed injection is now persistent, I've adjusted the proto interface to disable it.

cc @Scretch9

repo: eulynx-live/subsystems


text:
GetMeldungen liefert nicht die Kategorien zurück

Nach dem Ermitteln der Ergebnisliste zu einem Vorgang ermitteln wir die Meldungen zu einem spezifischen Ergebnis.
Das Meldungsobjekt enthält auch eine Kategorie. Diese ist leider nie gefüllt. Das führt dazu, dass wir die Meldungen nicht aufbereiten können und es für unsere Anwender extrem schwer ist zu erkennen, warum ein Angebot rot gescored wurde.

Hallo @steegc,
die "meldungsKategorie" kommt in unseren Testfällen zurück. Könnten sie uns ihren Request & Teil-Response mit Testdaten hier anhängen?
Danke und Liebe grüße
Kone

Kein Feedback...daher close

Hallo,
ich weiß nicht warum ich die Mails nicht bekommen habe. Aber auch das hat sich erledigt.
Die Kategorie hieß zu unserem Zeitpunkt der Implementierung kategorie und noch nicht meldungsKategorie.
Daher wurde das Feld beim Mapping von Json -> POJOs nicht gefüllt.

authors: KoneFuzius steegc

repo: europace/baufismart-angebote-api


text:
Calendar:emit() can be refactored.

This emit dispatcher can be simplified to just know what it need (there are a lot of filters line 38).

This was improved already. Closing it.

https://github.com/evangilo/light-datepicker/pull/11

authors: diasbruno evangilo

repo: evangilo/light-datepicker


text:
Added BigQuery links to Readme

Added links to a public BigQuery dataset of this timezone data. This data can then be queried using the built-in geometry functions to lookup at lat/long to a timezone. This has been super valuable to have this boundary data over the years, so it is great to have it shared with a wider audience too.
For example, will return Europe/London :
SELECT timezone_id FROM `tz-data.latest_EU.timezones` WHERE ST_WITHIN(ST_GEOGPOINT(/* longitude */ -0.13948559859956436,/* latitude */ 51.5029659891868),geometry);

This seems cool and seems to work, but is there a better link that doesn't require logging into the Google Cloud console?

@evansiroky good point! I have created a repo with some documentation and changed the link to that instead :+1:

authors: evansiroky redorkulated

repo: evansiroky/timezone-boundary-builder


text:
🛑 www.actionherojs.com is down

In 3a47df9, www.actionherojs.com (https://www.actionherojs.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: www.actionherojs.com is back up in f27e3dc.

repo: evantahler/upptime