Wifi station sometimes unable to connect (IDFGH-46)

sometimes wifi station never connects and just immediately fires the disconnect event in response to connect request:
reason given is 201. there are no visible differences in initialization messages and there are no code differences - this just sometimes happens on our automated hardware test rig. it doesn't happen often, i'd say once in a couple dozen times.
AP is out of suspicion: at the very same time other hw tests, including on another esp32 device, connect to it just fine.
wifi messages for normal run:
E (2765) wifi: esp_wifi_get_mode 768 wifi is not init
mgos_wifi_set_mode   WiFi mode: STA
E (2775) wifi: esp_wifi_set_mode 761 wifi is not init
I (2785) wifi: frc2_timer_task_hdl:3ffc1fac, prio:22, stack:2048
I (2795) wifi: Init lldesc rx mblock:25
I (2795) wifi: Init lldesc rx ampdu len mblock:7
I (2805) wifi: Init lldesc rx ampdu entry mblock:4
I (2815) wifi: pp_task_hdl : 3ffcfa6c, prio:23, stack:8192
E (2815) wifi: esp_wifi_connect 794 wifi not start
I (2825) wifi: mode : sta (24:0a:c4:00:39:f8)
event_handler        event: 2
mgos_wifi_setup_sta  WiFi STA: Connecting to Cesanta
mgos_i2c_create      I2C initialized (SDA: 22, SCL: 23)
mgos_sys_config_init HTTP server started on [80]
mg_rpc_channel_mqtt  0x3ffd0fac docker-agent.2B2088A1119E6083/rpc
mg_rpc_channel_uart  0x3ffd1074 UART0
mgos_init            Init done, RAM: 153684 free, 151108 min free
Tick
I (4465) wifi: n:11 0, o:1 0, ap:255 255, sta:11 0, prof:1
I (5025) wifi: state: init -> auth (b0)
I (5035) wifi: state: auth -> assoc (0)
Tock
I (5045) wifi: state: assoc -> run (10)
I (5055) wifi: connected with Cesanta, channel 11
mgos_wifi_on_change_ Wifi: connected

bad run:
E (2749) wifi: esp_wifi_get_mode 768 wifi is not init
mgos_wifi_set_mode   WiFi mode: STA
E (2759) wifi: esp_wifi_set_mode 761 wifi is not init
I (2759) wifi: frc2_timer_task_hdl:3ffc131c, prio:22, stack:2048
I (2769) wifi: Init lldesc rx mblock:25
I (2779) wifi: Init lldesc rx ampdu len mblock:7
I (2779) wifi: Init lldesc rx ampdu entry mblock:4
I (2789) wifi: pp_task_hdl : 3ffced58, prio:23, stack:8192
E (2799) wifi: esp_wifi_connect 794 wifi not start
I (2799) wifi: mode : sta (24:0a:c4:00:39:f8)
event_handler        event: 2
mgos_wifi_setup_sta  WiFi STA: Connecting to Cesanta
mgos_sys_config_init HTTP server started on [80]
mg_rpc_channel_mqtt  0x3ffd02b4 docker-agent.2D0C09498A207136/rpc
mg_rpc_add_channel   0x3ffd02b4 '*' MQTT
mg_rpc_channel_uart  0x3ffd0368 UART0
mg_rpc_add_channel   0x3ffd0368 '' UART
mgos_init            Init done, RAM: 161224 free, 161224 min free
mgos_upd_boot_finish 1 0
wifi_event_handler   WiFi STA: disconnected, reason 201; reconnecting
mgos_wifi_on_change_ Wifi: disconnected
wifi_event_handler   WiFi STA: disconnected, reason 201; reconnecting
mgos_wifi_on_change_ Wifi: disconnected
... (this continues in a tight loop) ...

(ignore the "not init" and "not start" errors, they are handled in the code and wifi is inited and started as required).

https://github.com/espressif/esp-idf/blob/master/components/esp32/include/esp_wifi_types.h#L86
Could be signal issue?  Other person mentioned this error had an antenna problem.

no, as i said, at the very same instant a bunch of other devices (1 more esp32 and 2 esp8266) were running other tests on the same AP.

Does that rule out a hw issue on the esp32 board?  Have you seen the issue on multiple units?

admittedly, this i don't know. i don't have logs from the past cases, will need to wait for this to happen again to see if it's the same.

just happened on the other device we have running automated tests, so i don't think it's hardware

Any correlation to mgos_upd_boot_finish aka happens after an ota update?

@rojer are you able to get an 802.11 frame capture ("monitor mode" capture) for the good & bad behaviour?

not easily, but i'll look into it later (currently traveling).
but complete lack of any output suggests that it's probably some sort of initialization failure.

fwiw, this still happens sometimes

still happening, including on latest IDF.
latest "good" log:
esp32_mgos_init      aws_iot_test_fw<PHONE_NUMBER> (20170510-152825/master@1120910a)
esp32_mgos_init      Mongoose OS Firmware<PHONE_NUMBER> (20170510-152825/master@1120910a)
esp32_mgos_init      ESP-IDF v1.0-1290-gc66b4fb
esp32_mgos_init      Boot partition: app_0, Task ID: 0x3ffbbc38, RAM: 219052 free
esp32_fs_mount       Mounting SPIFFS from fs_0 (131072 @ 0x190000)
esp32_fs_mount       Total: 113201, used: 18323, free: 94878
mgos_sys_config_init MAC: 240AC40039E0
mgos_sys_config_init WDT: 30 seconds
E (2727) wifi: esp_wifi_get_mode 781 wifi is not init
mgos_wifi_set_mode   WiFi mode: STA
E (2737) wifi: esp_wifi_set_mode 774 wifi is not init
I (2737) wifi: wifi firmware version: 384bc4e
I (2747) wifi: config NVS flash: enabled
I (2747) wifi: config nano formating: disabled
I (2757) wifi: Init dynamic tx buffer num: 32
I (2767) wifi: Init dynamic rx buffer num: 64
I (2767) wifi: wifi driver task: 3ffbd00c, prio:23, stack:3584
I (2777) wifi: Init static rx buffer num: 10
I (2777) wifi: Init dynamic rx buffer num: 0
I (2787) wifi: Init rx ampdu len mblock:7
I (2787) wifi: Init lldesc rx ampdu entry mblock:4
I (2797) wifi: wifi power manager task: 0x3ffd118c prio: 21 stack: 2560
E (2807) wifi: esp_wifi_connect 813 wifi not start
I (2807) wifi: wifi timer task: 3ffd21f8, prio:22, stack:3584
I (2837) phy: phy_version: 350, Mar 22 2017, 15:02:06, 0, 0
I (2837) wifi: mode : sta (24:0a:c4:00:39:e0)
event_handler        event: 2
mgos_wifi_setup_sta  WiFi STA: Connecting to Cesanta
mgos_sys_config_init HTTP server started on [80]
mg_rpc_channel_mqtt  0x3ffd2aa0 docker-agent.5H9JOPRA/rpc/#
mg_rpc_add_channel_i 0x3ffd2aa0 '*' MQTT, trusted
mg_rpc_channel_uart  0x3ffd2bd8 UART0
mg_rpc_add_channel_i 0x3ffd2bd8 '' UART, trusted
mg_rpc_add_channel_i 0x3ffd2c4c 'RPC.LOCAL' loopback, trusted
mgos_init            Init done, RAM: 182208 free, 181504 min free
mgos_upd_boot_finish 1 0
mg_rpc_ev_handler    0x3ffd2c4c CHAN OPEN (loopback)
I (2977) wifi: n:1 0, o:1 0, ap:255 255, sta:1 0, prof:1
I (3817) wifi: state: init -> auth (b0)
I (3827) wifi: state: auth -> assoc (0)
I (3837) wifi: state: assoc -> run (10)
I (3857) wifi: connected with Cesanta, channel 1
mgos_wifi_on_change_ Wifi: connected
I (4387) event: ip: <IP_ADDRESS>, mask: <IP_ADDRESS>, gw: <IP_ADDRESS>
mgos_wifi_on_change_ WiFi: ready, IP <IP_ADDRESS>, DNS <IP_ADDRESS>

and "bad":
esp32_mgos_init      aws_iot_test_fw<PHONE_NUMBER> (20170510-152825/master@1120910a)
esp32_mgos_init      Mongoose OS Firmware<PHONE_NUMBER> (20170510-152825/master@1120910a)
esp32_mgos_init      ESP-IDF v1.0-1290-gc66b4fb
esp32_mgos_init      Boot partition: app_0, Task ID: 0x3ffbbc38, RAM: 219052 free
esp32_fs_mount       Mounting SPIFFS from fs_0 (131072 @ 0x190000)
esp32_fs_mount       Total: 113201, used: 22339, free: 90862
mgos_sys_config_init MAC: 240AC40039E0
mgos_sys_config_init WDT: 30 seconds
E (2740) wifi: esp_wifi_get_mode 781 wifi is not init
mgos_wifi_set_mode   WiFi mode: STA
E (2750) wifi: esp_wifi_set_mode 774 wifi is not init
I (2750) wifi: wifi firmware version: 384bc4e
I (2760) wifi: config NVS flash: enabled
I (2760) wifi: config nano formating: disabled
I (2770) wifi: Init dynamic tx buffer num: 32
I (2780) wifi: Init dynamic rx buffer num: 64
I (2780) wifi: wifi driver task: 3ffbd19c, prio:23, stack:3584
I (2790) wifi: Init static rx buffer num: 10
I (2790) wifi: Init dynamic rx buffer num: 0
I (2800) wifi: Init rx ampdu len mblock:7
I (2800) wifi: Init lldesc rx ampdu entry mblock:4
I (2810) wifi: wifi power manager task: 0x3ffd124c prio: 21 stack: 2560
E (2820) wifi: esp_wifi_connect 813 wifi not start
I (2830) wifi: wifi timer task: 3ffd22b8, prio:22, stack:3584
I (2850) phy: phy_version: 350, Mar 22 2017, 15:02:06, 0, 0
I (2860) wifi: mode : sta (24:0a:c4:00:39:e0)
event_handler        event: 2
mgos_wifi_setup_sta  WiFi STA: Connecting to Cesanta
mgos_sys_config_init HTTP server started on [80]
mg_rpc_channel_mqtt  0x3ffd2b40 docker-agent.5H9JOPRA/rpc/#
mg_rpc_add_channel_i 0x3ffd2b40 '*' MQTT, trusted
mg_rpc_channel_uart  0x3ffd2c78 UART0
mg_rpc_add_channel_i 0x3ffd2c78 '' UART, trusted
mg_rpc_add_channel_i 0x3ffd2cec 'RPC.LOCAL' loopback, trusted
mgos_init            Init done, RAM: 182028 free, 181468 min free
mgos_upd_boot_finish 1 0
mg_rpc_ev_handler    0x3ffd2cec CHAN OPEN (loopback)
mongoose_poll        New heap free LWM: 180356
wifi_event_handler   WiFi STA: disconnected, reason 201; reconnecting
mgos_wifi_on_change_ Wifi: disconnected
wifi_event_handler   WiFi STA: disconnected, reason 201; reconnecting
mgos_wifi_on_change_ Wifi: disconnected
wifi_event_handler   WiFi STA: disconnected, reason 201; reconnecting
mgos_wifi_on_change_ Wifi: disconnected
wifi_event_handler   WiFi STA: disconnected, reason 201; reconnecting
mgos_wifi_on_change_ Wifi: disconnected
wifi_event_handler   WiFi STA: disconnected, reason 201; reconnecting
mgos_wifi_on_change_ Wifi: disconnected
...

Hi @rojer reason 201 is WIFI_REASON_NO_AP_FOUND, it means the esp32 doesn't find the specified AP, it looks strange because other device can connect the AP while the bad esp32 can't find the AP. Currently the log is not enough for debugging this issue, also I didn't observe any similar behavior in our lab test.
Could you help to provide following info?

If possible, capture the packets in the channel on which the AP is running (here it's channel 1, ht20), filter the packets with esp32 and AP's mac, because I need to check whether the esp32's probe request is sent out or not? also whether the AP's probe response is sent out or not?
Do you configure the channel dwell duration with esp_wifi_scan_start? The default behavior of esp32 foreground scan is to scan each channel for 120ms, if the dwell scan duration is configured to a smaller duration, then esp32 may fails to find the AP
Check the hardware status of the bad esp32, is this problem only happen to this specified esp32 board and all other esp32 board are good?
Relative position between the bad esp32 board and the AP, does the bad esp32 board has the same test environment (such as distance, position etc) as the good esp32/8266?
I will as our QA to do some stability test about this issue and hope we can reproduce it in lab....

@liuzfesp thanks for response. it's not that easy for me to do packet capture, as none of the adapters i have in the area seem to be doing monitor mode properly - some just flat out don't support it, and one that claims to just returns no packets. i'll try to figure something out.
i don't configure any parameters related to scan. i configure station and then just invoke connect.
this happens on both esp32 devkit boards we have configured in this hardware test rig. and both logs i posted here are actually from the same device, just seconds apart.
it must be something related to scan, it even seems that it's never started, for whatever reason-  these disconnection events come pretty quickly, as if station is not even trying to find AP - failing to even initiate scan, perhaps? there are no error log entries though, as you can see.
perhaps, you could throw in a couple info or debug-level messages in key places of the scan process?

HI @rojer " you could throw in a couple info or debug-level messages in key places of the scan process", it's a good idea, however, currently in release 2.1 (and former release), the release version, we don't have too much infor/log for wifi debug, we have a bunch of debug info/log in debug version, I think the detailed debug/info should be ready in next release (not release2.1).

I experience the same issue. When I perform scan, the AP I want to connect to is found with a signal strength -33. However, when I connect, I receive disconnected with reason 201. ESP32 connects to the AP only in 1 out of 15 cases. So far i haven't found any pattern.

I am getting similar failure condition and can repeat reliable. I monitor the system core firmware with TeraTerm version 4.89 to my serial USB interface. The error message I get that tell me I have crashed is "E (43684) Wifi ieee 80211_sta.c 649. If I wait for a period of time the system start a core dump.
My application is sending approximately 191 bytes of data thru the "pub" function. My message packet is a JSON formated string that is NULL terminated. If I call "pub" 11 times it generates the above error. The time period for sending these packets is about once every 10 seconds. All packets are received and are correct except the last when the failure occurs. My "pub" msg buffer is set to 512 because some of my packet are larger than others.
I am controlling the application via AMAZON AWS tools, test interface MQTT Client.

Although perhaps unrelated, this later issue discusses some workarounds which might lead to a solution: issue 539
Notably the fact that it happens when waking from deepsleep. You apparently have to restart the ESP32 after waking up.

Hi @rojer @danstirling @yaqwsx we have a lot of optimization about scan in latest IDF master branch and some optimization in release 2.1, could you help to check whether this issue still exist or NOT?

the issue still stands: sometimes station just won't connect.
however, i think i have additional information: in this case it seems to not scan channel 11 for some reason.
we run an automated test that:

connects to our wifi network (Cesanta)
scans wifi networks in the background
these are carried out at the same time, so we tell wifi station to connect but also run wifi scan every 5 seconds and print results.
so, sometimes the following happens:
station cannot connect to Cesanta
scan results never contain APs with channel 11
incidentally, Cesanta uses channel 11. so (1) seems to be the reason for (2), so it's no wonder.
why the scan skips channel 11 however, i have no clue.
for example, here's the result of a scan from a good run:

mgos_wifi_setup_sta  WiFi STA: Connecting to Cesanta
I (691) phy: phy_version: 362.0, 61e8d92, Sep  8 2017, 18:48:11, 0, 0
I (691) wifi: mode : sta (24:0a:c4:00:39:e0)
...
mgos_net_on_change_c WiFi STA: connecting
I (2031) wifi: n:11 0, o:1 0, ap:255 255, sta:11 0, prof:1
I (2971) wifi: state: init -> auth (b0)
I (2981) wifi: state: auth -> assoc (0)
sw_timer_cb          0 ctr 0 -> 16697, diff = 16697
I (2991) wifi: state: assoc -> run (10)
I (3011) wifi: connected with Cesanta, channel 11
mgos_net_on_change_c WiFi STA: connected
sw_timer_cb          1 ctr 16697 -> 20001, diff = 3304
I (3541) event: sta ip: <IP_ADDRESS>, mask: <IP_ADDRESS>, gw: <IP_ADDRESS>
mgos_net_on_change_c WiFi STA: ready, IP <IP_ADDRESS>, GW <IP_ADDRESS>, DNS <IP_ADDRESS>
...
mgos_wifi_dev_scan_c WiFi scan done, num_res 9
wifi_scan_cb         123 9 results 0x3ffcacc4
wifi_scan_cb         123 SSID 'Cesanta' chan 11 auth 3 RSSI -45
wifi_scan_cb         123 SSID 'eduroam' chan 1 auth 5 RSSI -61
wifi_scan_cb         123 SSID 'TCDguest' chan 1 auth 0 RSSI -62
wifi_scan_cb         123 SSID 'DIRECT-D3C1860 Series' chan 11 auth 3 RSSI -70
wifi_scan_cb         123 SSID 'ICHEC Staff 2.4G' chan 7 auth 3 RSSI -77
wifi_scan_cb         123 SSID 'Amethyst WiFi' chan 9 auth 4 RSSI -77
wifi_scan_cb         123 SSID 'ICHEC Guest' chan 7 auth 3 RSSI -78
wifi_scan_cb         123 SSID 'ICHEC Staff 2.4G' chan 12 auth 3 RSSI -87
wifi_scan_cb         123 SSID 'ICHEC Staff' chan 12 auth 3 RSSI -87
...
mgos_wifi_dev_scan_c WiFi scan done, num_res 5
wifi_scan_cb         123 5 results 0x3ffdbbf8
wifi_scan_cb         123 SSID 'Cesanta' chan 11 auth 3 RSSI -45
wifi_scan_cb         123 SSID 'Mongoose_05E802' chan 6 auth 3 RSSI -48
wifi_scan_cb         123 SSID 'TCDguest' chan 6 auth 0 RSSI -53
wifi_scan_cb         123 SSID 'eduroam' chan 6 auth 5 RSSI -53
wifi_scan_cb         123 SSID 'DIRECT-D3C1860 Series' chan 11 auth 3 RSSI -71

note that channel 11 has two APs: Cesanta and DIRECT-D3C1860 Series (whatever that is).
on a bad run, however, repeated scans never contain anything on channel 11:
mgos_wifi_setup_sta  WiFi STA: Connecting to Cesanta
I (689) phy: phy_version: 362.0, 61e8d92, Sep  8 2017, 18:48:11, 0, 0
I (689) wifi: mode : sta (24:0a:c4:00:39:e0)
...
mgos_net_on_change_c WiFi STA: connecting
sw_timer_cb          0 ctr 0 -> 10002, diff = 10002
esp32_wifi_ev        Disconnected from Cesanta, reason: 201
mgos_net_on_change_c WiFi STA: disconnected
mgos_net_on_change_c WiFi STA: connecting
sw_timer_cb          1 ctr 10002 -> 20002, diff = 10000
sw_timer_cb          2 ctr 20002 -> 30001, diff = 9999
sw_timer_cb          3 ctr 30001 -> 40002, diff = 10001
esp32_wifi_ev        Disconnected from Cesanta, reason: 201
mgos_net_on_change_c WiFi STA: disconnected
mgos_net_on_change_c WiFi STA: connecting
sw_timer_cb          4 ctr 40002 -> 50003, diff = 10001
sw_timer_cb          5 ctr 50003 -> 60002, diff = 9999
mgos_wifi_dev_scan_c WiFi scan done, num_res 6
wifi_scan_cb         123 6 results 0x3ffcab5c
wifi_scan_cb         123 SSID 'Mongoose_003AAA' chan 6 auth 3 RSSI -14
wifi_scan_cb         123 SSID 'Cesanta' chan 11 auth 3 RSSI -47
wifi_scan_cb         123 SSID 'eduroam' chan 6 auth 5 RSSI -53
wifi_scan_cb         123 SSID 'ICHEC Guest' chan 12 auth 3 RSSI -87
wifi_scan_cb         123 SSID 'ICHEC Staff' chan 12 auth 3 RSSI -88
wifi_scan_cb         123 SSID 'ICHEC Staff 2.4G' chan 12 auth 3 RSSI -88
sw_timer_cb          6 ctr 60002 -> 70001, diff = 9999
sw_timer_cb          7 ctr 70001 -> 80001, diff = 10000
sw_timer_cb          8 ctr 80001 -> 90002, diff = 10001
sw_timer_cb          9 ctr 0 -> 0, diff = 0
sw_timer_cb          10 ctr 0 -> 0, diff = 0
mgos_wifi_dev_scan_c WiFi scan done, num_res 2
wifi_scan_cb         123 2 results 0x3ffcaa5c
wifi_scan_cb         123 SSID 'ICHEC Staff' chan 12 auth 3 RSSI -87
wifi_scan_cb         123 SSID 'ICHEC Staff 2.4G' chan 12 auth 3 RSSI -87
sw_timer_cb          11 ctr 0 -> 0, diff = 0
sw_timer_cb          12 ctr 0 -> 0, diff = 0
sw_timer_cb          13 ctr 0 -> 0, diff = 0
sw_timer_cb          14 ctr 0 -> 0, diff = 0
sw_timer_cb          15 ctr 0 -> 0, diff = 0
mgos_wifi_dev_scan_c WiFi scan done, num_res 3
wifi_scan_cb         123 3 results 0x3ffcaa9c
wifi_scan_cb         123 SSID 'ICHEC Guest' chan 12 auth 3 RSSI -88
wifi_scan_cb         123 SSID 'ICHEC Staff 2.4G' chan 12 auth 3 RSSI -89
wifi_scan_cb         123 SSID 'ICHEC Staff' chan 12 auth 3 RSSI -90
sw_timer_cb          16 ctr 0 -> 0, diff = 0
sw_timer_cb          17 ctr 0 -> 0, diff = 0
sw_timer_cb          18 ctr 0 -> 0, diff = 0
sw_timer_cb          19 ctr 0 -> 0, diff = 0
sw_timer_cb          20 ctr 0 -> 0, diff = 0
mgos_wifi_dev_scan_c WiFi scan done, num_res 7
wifi_scan_cb         123 7 results 0x3ffcab9c
wifi_scan_cb         123 SSID 'Mongoose_E03C9A' chan 6 auth 3 RSSI -44
wifi_scan_cb         123 SSID 'TCDwifi-firststeps' chan 6 auth 0 RSSI -52
wifi_scan_cb         123 SSID 'TCDguest' chan 6 auth 0 RSSI -52
wifi_scan_cb         123 SSID 'eduroam' chan 6 auth 5 RSSI -52
wifi_scan_cb         123 SSID 'ICHEC Guest' chan 12 auth 3 RSSI -88
wifi_scan_cb         123 SSID 'ICHEC Staff' chan 12 auth 3 RSSI -88
wifi_scan_cb         123 SSID 'ICHEC Staff 2.4G' chan 12 auth 3 RSSI -89
sw_timer_cb          21 ctr 0 -> 0, diff = 0
sw_timer_cb          22 ctr 0 -> 0, diff = 0
sw_timer_cb          23 ctr 0 -> 0, diff = 0
sw_timer_cb          24 ctr 0 -> 0, diff = 0
sw_timer_cb          25 ctr 0 -> 0, diff = 0
mgos_wifi_dev_scan_c WiFi scan done, num_res 3
wifi_scan_cb         123 3 results 0x3ffcaa9c
wifi_scan_cb         123 SSID 'ICHEC Staff 2.4G' chan 12 auth 3 RSSI -87
wifi_scan_cb         123 SSID 'ICHEC Guest' chan 12 auth 3 RSSI -87
wifi_scan_cb         123 SSID 'ICHEC Staff' chan 12 auth 3 RSSI -89
sw_timer_cb          26 ctr 0 -> 0, diff = 0
sw_timer_cb          27 ctr 0 -> 0, diff = 0
sw_timer_cb          28 ctr 0 -> 0, diff = 0
sw_timer_cb          29 ctr 0 -> 0, diff = 0
sw_timer_cb          30 ctr 0 -> 0, diff = 0
mgos_wifi_dev_scan_c WiFi scan done, num_res 3
wifi_scan_cb         123 3 results 0x3ffcaa9c
wifi_scan_cb         123 SSID 'ICHEC Guest' chan 12 auth 3 RSSI -88
wifi_scan_cb         123 SSID 'ICHEC Staff' chan 12 auth 3 RSSI -89
wifi_scan_cb         123 SSID 'ICHEC Staff 2.4G' chan 12 auth 3 RSSI -90
sw_timer_cb          31 ctr 0 -> 0, diff = 0
sw_timer_cb          32 ctr 0 -> 0, diff = 0
sw_timer_cb          33 ctr 0 -> 0, diff = 0
sw_timer_cb          34 ctr 0 -> 0, diff = 0
sw_timer_cb          35 ctr 0 -> 0, diff = 0
mgos_wifi_dev_scan_c WiFi scan done, num_res 5
wifi_scan_cb         123 5 results 0x3ffcab1c
wifi_scan_cb         123 SSID 'Cesanta' chan 11 auth 3 RSSI -46
wifi_scan_cb         123 SSID 'ICHEC Staff' chan 7 auth 3 RSSI -76
wifi_scan_cb         123 SSID 'ICHEC Guest' chan 12 auth 3 RSSI -87
wifi_scan_cb         123 SSID 'ICHEC Staff 2.4G' chan 12 auth 3 RSSI -89
wifi_scan_cb         123 SSID 'ICHEC Staff' chan 12 auth 3 RSSI -91
sw_timer_cb          36 ctr 0 -> 0, diff = 0
sw_timer_cb          37 ctr 0 -> 0, diff = 0
sw_timer_cb          38 ctr 0 -> 0, diff = 0
sw_timer_cb          39 ctr 0 -> 0, diff = 0
sw_timer_cb          40 ctr 0 -> 0, diff = 0
mgos_wifi_dev_scan_c WiFi scan done, num_res 7
wifi_scan_cb         123 7 results 0x3ffcab9c
wifi_scan_cb         123 SSID 'Mongoose_0039F8' chan 6 auth 3 RSSI -27
wifi_scan_cb         123 SSID 'TCDwifi-firststeps' chan 6 auth 0 RSSI -52
wifi_scan_cb         123 SSID 'TCDwifi-firststeps' chan 1 auth 0 RSSI -61
wifi_scan_cb         123 SSID 'ICHEC Staff 2.4G' chan 12 auth 3 RSSI -88
wifi_scan_cb         123 SSID 'ICHEC Guest' chan 12 auth 3 RSSI -89
wifi_scan_cb         123 SSID 'ICHEC Staff' chan 12 auth 3 RSSI -89
wifi_scan_cb         123 SSID 'creme-backup2' chan 1 auth 4 RSSI -95
sw_timer_cb          41 ctr 0 -> 0, diff = 0
sw_timer_cb          42 ctr 0 -> 0, diff = 0
sw_timer_cb          43 ctr 0 -> 0, diff = 0
sw_timer_cb          44 ctr 0 -> 0, diff = 0
sw_timer_cb          45 ctr 0 -> 0, diff = 0
mgos_wifi_dev_scan_c WiFi scan done, num_res 6
wifi_scan_cb         123 6 results 0x3ffcab5c
wifi_scan_cb         123 SSID 'Mongoose_E03C9A' chan 6 auth 3 RSSI -44
wifi_scan_cb         123 SSID 'TCDguest' chan 6 auth 0 RSSI -52
wifi_scan_cb         123 SSID 'eduroam' chan 6 auth 5 RSSI -52
wifi_scan_cb         123 SSID 'ICHEC Staff 2.4G' chan 12 auth 3 RSSI -88
wifi_scan_cb         123 SSID 'ICHEC Staff' chan 12 auth 3 RSSI -88
wifi_scan_cb         123 SSID 'ICHEC Guest' chan 12 auth 3 RSSI -89
sw_timer_cb          46 ctr 0 -> 0, diff = 0
sw_timer_cb          47 ctr 0 -> 0, diff = 0
sw_timer_cb          48 ctr 0 -> 0, diff = 0
sw_timer_cb          49 ctr 0 -> 0, diff = 0
sw_timer_cb          50 ctr 0 -> 0, diff = 0
... etc, etc ...

WiFi log for scan/connect will be ready in IDF v3.3 soon, then we can debug the hard-reproduce WiFi connected issue with the log.

I guess it's not your case, but anyway...
Something similar happened to me after updating to esp-idf v3.3. With older versions there was no problem. The bug was uncorrect wifi_config_t initialization. wifi_config_t wifi_config  = {0} at the beginning helped.

Thanks, @ImrichFischer. That fixed the connection problem for me in 3.1 and in 3.2.

@ImrichFischer  非常感谢,我也是这个问题哈哈哈

@ImrichFischer. Thank U
here is the code for those who need it
        wifi_config_t sta_config = {
		.sta = {
			.ssid = "MYWIFI",
                        .password="MYPASSWORD",
                        .scan_method=WIFI_FAST_SCAN,    /**< do all channel scan or fast scan */

                                                        //WIFI_FAST_SCAN = 0,   /**< Do fast scan, scan will end after find SSID match AP */
                                                        //WIFI_ALL_CHANNEL_SCAN, /**< All channel scan, scan will end after scan all the channel */
                        .bssid_set=0,
                        /**bssid_set < whether set MAC address of target AP or not. Generally,
                         * station_config.bssid_set needs to be 0;
                         * and it needs to be 1 only when users need to check the MAC address of the AP.*/
                        .bssid={0},                             /**< MAC address of target AP*/
                        .channel=0,                             /**< channel of target AP. Set to 1~13 to scan starting from the specified channel before connecting to AP. If the channel of AP is unknown, set it to 0.*/
                        .listen_interval=0,                     /**< Listen interval for ESP32 station to receive beacon when WIFI_PS_MAX_MODEM is set. Units: AP beacon intervals. Defaults to 3 if set to 0. */
                        .sort_method=WIFI_CONNECT_AP_BY_SIGNAL, /**< sort the connect AP in the list by rssi or security mode */
                                                                //WIFI_CONNECT_AP_BY_SIGNAL = 0,        /**< Sort match AP in scan list by RSSI */
                                                                //WIFI_CONNECT_AP_BY_SECURITY,          /**< Sort match AP in scan list by security mode */
                        .threshold.rssi=0,                      /**< When sort_method is set, only APs which have an auth mode that is more secure than the selected auth mode and a signal stronger than the minimum RSSI will be used. */
                                                                //int8_t rssi;/**< The minimum rssi to accept in the fast scan mode */
                        .threshold.authmode=WIFI_AUTH_OPEN      /**< The weakest authmode to accept in the fast scan mode */

                                                                //WIFI_AUTH_OPEN = 0,         /**< authenticate mode : open */
                                                                //WIFI_AUTH_WEP,              /**< authenticate mode : WEP */
                                                                //WIFI_AUTH_WPA_PSK,          /**< authenticate mode : WPA_PSK */
                                                                //WIFI_AUTH_WPA2_PSK,         /**< authenticate mode : WPA2_PSK */
                                                                //WIFI_AUTH_WPA_WPA2_PSK,     /**< authenticate mode : WPA_WPA2_PSK */
                                                                //WIFI_AUTH_WPA2_ENTERPRISE,  /**< authenticate mode : WPA2_ENTERPRISE */
                                                                //WIFI_AUTH_MAX
               }
        };

I guess it's not your case, but anyway...
Something similar happened to me after updating to esp-idf v3.3. With older versions there was no problem. The bug was uncorrect wifi_config_t initialization. wifi_config_t wifi_config = {0} at the beginning helped.

Thaks!

I had the same issue under IDF 4.0. Doing the null initialization fixed the problem.

I had the same issue under IDF 4.0. Doing the null initialization fixed the problem.

Where are you adding this? wifi_config_t wifi_config = {0} Is it in the iot_wifi.c file? I see it´s already like that and I am still getting the same problem

Where are you adding this? wifi_config_t wifi_config = {0} Is it in the iot_wifi.c file? I see it´s already like that and I am still getting the same problem

@hackaprende You must to add this line (wifi_config_t wifi_config = {0}) before call this function esp_wifi_set_config(ESP_IF_WIFI_STA, &wifi_config). In the wifi application layer on your project.

@hackaprende You must to add this line (wifi_config_t wifi_config = {0}) before call this function esp_wifi_set_config(ESP_IF_WIFI_STA, &wifi_config). In the wifi application layer on your project.


Consumes a lot of CPU  when appWillForeground

Step 0: Are you in the right place?
Yes, I think so
[REQUIRED] Step 1: Describe your environment

Xcode version: 11.4.1
Firebase SDK version: 6.26.0
Firebase Component: FirebaseMLNLTranslate
Component version: 0.18.0
Installation method: CocoaPods

[REQUIRED] Step 2: Describe the problem
Consumes a lot of CPU  when appWillForeground ,because GoogleDataTransport DecodeArchive

Steps to reproduce:
after download models
in foreground from background
demo: https://github.com/xiaohuihui000/googleTranslate
Relevant Code:
// TODO(you): code here to reproduce the problem

on some phone  will crash

can you help me ?
thanks!

@xiaohuihui000 Sorry you encountered the issue. This part was refactored and should not cause performance issues any more. The fix is expected to be available in Firebase 6.28.0 version that is scheduled for the release for the mid next week.


Runtime memory consumption statistics

Are there any statistics pertaining to GPU memory consumption along with the FPS information?

Sorry, we don't have statistics for GPU memory consumption.


Removal of 21.03.21 for Shotcut duplicate

Removing v21.03.21 of the duplicate
Microsoft Reviewers: Open in CodeFlow

Thanks @ItzLevvie!


Prevent system field ambiguity

What do you think about using the tableAlias constant instead of just .r? I think its cleaner this way.

Here, compose_record's deleted_at and compose_record_value's deleted_at were in collision. I prefixed all compose_record's fields with the given alias.

Codecov Report

Merging #22 into master will increase coverage by 0.27%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master      #22      +/-   ##
==========================================
+ Coverage    43.2%   43.48%   +0.27%
==========================================
  Files         362      362
  Lines       23488    23758     +270
==========================================
+ Hits        10149    10332     +183
- Misses      11791    11858      +67
- Partials     1548     1568      +20

Impacted Files
Coverage Δ

compose/repository/record.go
71.49% <33.33%> (+0.06%)
:arrow_up:

compose/rest/record.go
38.46% <0%> (+1.13%)
:arrow_up:

compose/rest/request/util.go
26.76% <0%> (+1.3%)
:arrow_up:

compose/rest/request/record.go
33.9% <0%> (+3.71%)
:arrow_up:

compose/service/record.go
56.84% <0%> (+4.72%)
:arrow_up:

compose/rest/handlers/record.go
46.87% <0%> (+8.49%)
:arrow_up:

Continue to review full report at Codecov.

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


direct deeplink to share to teams

[Enter feedback here]
Is there a direct deeplink to share to teams as it exists for going to channel and chat
Eg
https://teams.microsoft.com/share?href={URL}
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 9cb013cb-3a19-2142-5286-692ff9b32ea6
Version Independent ID: 9cb013cb-3a19-2142-5286-692ff9b32ea6
Content: Share to Teams from web apps - Teams
Content Source: msteams-platform/concepts/build-and-test/share-to-teams-from-web-apps.md
Service: msteams
GitHub Login: @surbhigupta
Microsoft Alias: lajanuar

There doesn't seem to be any direct deep link available for 'share to teams' as it exists for navigating to channel and chat.


sui move prove is unable to filter modules for verification

Steps to Reproduce Issue

sui move new mre1
Create the following two modules in sources:
2.1. sources/five.movemodule mre1::five {
    public(friend) fun five(): u256 { 5 }

    spec five {
        // this function never aborts
        aborts_if false;

        // purposefully wrong!
        ensures result == 4;
    }
}

2.2. sources/seven.movemodule mre1::seven {
    public(friend) fun seven(): u256 { 7 }

    spec seven {
        // this function never aborts
        aborts_if false;

        ensures result == 7;
    }
}

Run (cd mre1; sui move prove)
Run (cd mre1; sui move prove --target five)

Expected Result
Recall that sui move prove --help outputs
Options:
  -p, --path <PACKAGE_PATH>                     Path to a package which the command should be run with respect to
  -t, --target <TARGET_FILTER>                  The target filter used to prune the modules to verify. Modules with a name that contains this string will be part of verification
  ...

Meaning that sui move prove --target five should only run the Move Prover for the mre1::five module.
The expected result for both commands, sui move prove and sui move prove --target five is that both find the error with the purposefully incorrect specification of mre1::five::five.
Actual Result
The command sui move prove finds the aforementioned error, while sui move prove --target five fails with
Duplicate package entry for 'mre1'

System Information
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.6 LTS
Release:        20.04
Codename:       focal

$ rustc --version
rustc 1.73.0 (cc66ad468 2023-10-03)

$ sui --version
sui 1.12.0-1b5f809a1

Support for the prover is being sunset, so this can be closed; see #15480


Sorting on last login in the Rancher UI not working properly

Sorting by last login will produce unexpected results in large groups of users.
SURE-9004
Actual behavior
Users not sorted by last login
Expected behavior
Users sorted by last login
Screenshots

@gaktive FYI - I raised a PR to fix this in 2.10. I think that we should also patch for 2.9.

Related to #11866

/backport v2.9.3

This needs manual validation. Follow-up task created for automation https://github.com/rancher/qa-tasks/issues/1592

Last login sorting working as expected.
Tested in:
Rancher v2.10-ae6ac83471545ab47d052d2d760daa2e6646a969-head
Dashboard master 225e3e6
https://github.com/user-attachments/assets/4150c5ac-2bc5-437c-9f52-878f6457d26b


implement reading/writing libp2p private key from disk

will allow for having persistent peer IDs across restarts.
see https://github.com/astriaorg/astria/blob/main/crates/astria-gossipnet/src/network.rs#L107

This is required in order to enable soft commitments in the dev cluster


Change Nutanix credentials format

Update Nutanix Secret template to use base64 encoded credentials.

/hold
This is an anticipatory PR; requires a new version of CAPX before we merge this.

PR to change the CAPX version that supports new format https://github.com/aws/eks-anywhere-build-tooling/pull/1433

/assign @abhinavmpandey08

/unhold

/ok-to-test

/retest

/test eks-anywhere-release-tooling-test-presubmit


Cannot read properties of null (reading 'blur') when changing view via select on Chrome

Reproduction Link

N/A, I was unable to reproduce via a fiddle, not sure if that is set to 3.0? Here is a code snippet though that did reproduce:

<template>

      <Multiselect
        ref="something"
        v-model="selectedOpt"
        :options="opts"
        :searchable="true"
        :group-select="false"
        :multiple="true"
        :close-on-select="false"
        @select="something = false"
      />

      <Multiselect
        ref="somethingelse"
        v-model="selectedOpt"
        :options="opts"
        :searchable="true"
        :group-select="false"
        :multiple="true"
        :close-on-select="false"
        @select="something = true"
      />

</template>

Steps to reproduce

This is 3.0, on Vue 3. See above: have two multiselects that you can toggle between by choosing an option on one of them, an error will throw. This only happens on Chrome. If you trigger the select function that toggles between the selects, the error is thrown.

Expected behaviour

This works fine and throws no errors.

Actual behaviour
An error is thrown implying this.$refs.search is null, and errors on the following line:
if (typeof this.$refs.search !== 'undefined') this.$refs.search.blur();

The error is Cannot read properties of null (reading 'blur').

Hi, also having the same error when unmouting the VueMultiselect component, it only occurs if the searchable prop is set to true.
The error is thrown by this condition check in multiselectMixin.js, related to PR https://github.com/shentao/vue-multiselect/pull/1497:
https://github.com/shentao/vue-multiselect/blob/master/src/multiselectMixin.js#L691
if (this.searchable) {
  if (typeof this.$refs.search !== 'undefined') this.$refs.search.blur()
} else {
  if (typeof this.$el !== 'undefined') this.$el.blur()
}

I get the same error

same here

Same error when using dynamic-options-provider. Happens If immediately leave the page while options are still being fetched.


Catch invalid URI when parsing mainstream URL

Fixes https://govuk.sentry.io/issues/5657864742/?alert_rule_id=963054&alert_type=issue&notification_uuid=6fae429a-a184-4a8d-bcd4-a2a9aa6cbf89&project=202259&referrer=slack

⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠
Follow these steps if you are doing a Rails upgrade.

I figured we already return nil for some scenarios (return nil if url.blank?) so Whitehall already knows how to handle nil in this case. But agreed, it does indicate a failure somewhere else in the process!


Jenkins builds fail randomly to pull supervisor image

Log
open /var/lib/docker/tmp/GetImageBlob084191237: no such file or directory
open /var/lib/docker/tmp/GetImageBlob084191237: no such file or directory
ERROR: resin-supervisor-disk: No local supervisor images found.
ERROR:
ERROR: Task 237 (/yocto/resin-board/build/../layers/meta-resin/meta-resin-common/recipes-containers/docker-disk/docker-resin-supervisor-disk.bb, do_package_write_rpm) failed with exit code '1'
ERROR: resin-supervisor-disk: No local supervisor images found.
ERROR:
ERROR: Task 232 (/yocto/resin-board/build/../layers/meta-resin/meta-resin-common/recipes-containers/docker-disk/docker-resin-supervisor-disk.bb, do_package_qa) failed with exit code '1'
``

Failed log: https://jenkins.dev.resin.io/job/yocto-odroid-ux3/1875/console

I believe this issue is caused by a cleanup cron job on the build slaves deleting volumes too aggressively. There's a PR for a probable fix here: https://github.com/resin-io/resin-containers/pull/154

This change has now been merged, so hopefully this is fixed.
https://github.com/resin-io/resin-containers/pull/157


Fix a break due to if intent doesnt have any slots, AWS doesn't add Slots : {} to the JSON

This is due to the if the intent doesn't have any slots, AWS/alexa doesn't add "slots: {}" to the JSON. Same issue to the Attributes when the session starts.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for contribution!


Support for grouped checkboxes

Nice package, works like a charm on most points. The only thing I am missing is the support for bundled checkboxes. Right now if the checkbox has multiple values, only the first entry is persisted to localstorage. Would be nice to have.

https://github.com/fawaz-alesayi/svelte-use-persist/pull/11

Closed by #11
Thanks


'NoneType' object has no attribute 'image_data_format'

Hi, I am trying to run the code , I have tested with tensorflow 1.14.0 and 2.1 and I am receiving the same error.
`/opt/conda/lib/python3.7/site-packages/efficientnet/model.py in EfficientNet(width_coefficient, depth_coefficient, default_resolution, dropout_rate, drop_connect_rate, depth_divisor, blocks_args, model_name, include_top, weights, input_tensor, input_shape, pooling, classes, **kwargs)
    322                                       default_size=default_resolution,
    323                                       min_size=32,
--> 324                                       data_format=backend.image_data_format(),
    325                                       require_flatten=include_top,
    326                                       weights=weights)

AttributeError: 'NoneType' object has no attribute 'image_data_format'`

Same issue faced,
But I am using in this way,
keras_applications.imagenet_utils.preprocess_input(x, data_format='channels_last', mode='torch', **kwargs)
becoz skimage will return [height, width, channel] so i have used data_format='channels_last' by default

This happens to me as well in keras but I solved it by importing correct package from efficientnet import keras as eff_model


Add support for clock-synchronization

Clock synchronization is necessary for federations to operate correctly in real-time. We have two alternatives:

Add clock-sync as a runtime feature. Inspired by reactor-c
Develop a library reactor doing clock sync that can be instantiated in the federate

After a discussion with @edwardalee and @tanneberger we will initially go with (2).  A few points:

Clock-sync ports should be connected with physical connections, because then the time-of-reception will be the logical tag of the event triggering the reaction handling it.
To minimize the time between reading physical time and storing it in the payload of an event, and the time where the event is sent over a connection, we should make this happen at a very odd tag where nothing else is happening in the federate. We can do that by scheduling an action at (current_time, UINT32_MAX) which is unlikely to coincide with anything.


Display non-ascii space characters as they are

Fixes #15
Currently, NON-ASCII space characters such as \u{3000} are output as unicode escapes.
https://doc.rust-lang.org/reference/tokens.html?highlight=unicode#unicode-escapes
This is due to the inner processing in proc-macro2.
I've attempted to resolve this problem by implementing unescape_unicode function.

LGTM thank you very much! :+1:


Update thrift bindings to match 5.3

Primarily, the return type for sql_validate was changed from TTableDescriptor to  TRowDescriptor in OmniSciDB. This affects use of sql execute from the IBIS client as it performs a sql validate step prior to execution.

@xmnlab this will overwrite some of the changes you made in #321, it looks like the only relevant one may be this check for int. Does that look like it is still necessary? https://github.com/omnisci/pymapd/pull/321/files#r431384929

@jclay I have tested it locally and it worked. also it worked with your ibis PR https://github.com/ibis-project/ibis/pull/2256/files
thanks!


Revealing the cursor line does work in some cases when height is small and sticky scroll enabled

Broken ("editor.stickyScroll.enabled": true):

Working ("editor.stickyScroll.enabled": false):

In monaco playground:
Broken:

Working (sticky scrolling turned off):

Since this affects monaco editor use-cases where the editor has a small height and sticky scrolling is enabled by default, I added the "important" label.

duplicate of https://github.com/microsoft/vscode/issues/227750. Closing this in favor of the other issue.


Adding DevContainer for local and CodeSpace Development

To allow for better local development I created a devcontainer that has the docsify CLI to allow you to review your changes as they are being made.

Launch the devcontainer
hit F5 to run the launch.json file in .vscode
This will start CLI and connect to port 3000

Edits that are saved will cause a reload of the site with the new changes.
Note: This can also be run in a code space as well. Hot reload does not work. You will need to manually refresh the page.

@kevball2 will test this and merge.

I've tested this just now, thank you so much @kevball2 :) merging and I've credited you on the docs https://github.com/learntocloud/learn-to-cloud/wiki/How-to-use-DevContainer-for-local-and-CodeSpace-Development


Create new API for attendance events and attendees

Adds an endpoint for Attendees.
Updates a seemingly unused AttendeeSerializer and UserSerializer
Added (an easier) way to check if an attendee is on a waitlist.
The main magic here happens in the AttendViewSet that takes post requests from regme and handles the end user accordingly.
Sorry for the poorly organized commits. :disappointed:

This might not be done yet. We're not quite sure how we're going to get the events to begin with, so we might require some changes there if we can't find a clever way to filter our way to what we want.

I added filtering by attendance event. Everything should be complete now, and (hopefully) ready to merge.

Okay, THIS time it's ready.

For real this time though.


Message was too large, server rejected it to avoid allocation error when using Headers

@pkedy from https://github.com/Shopify/sarama/pull/1040#issuecomment-365025401
That error can occur in two ways:

The producer will short-circuit a message on its own if it detects it too large: https://github.com/Shopify/sarama/blob/f7be6aa2bc7b2e38edf816b08b582782194a1c02/async_producer.go#L274-L277 That check currently includes the length of headers, but maybe it shouldn't?
The broker sends it back to us.

If increasing the client-side config makes it go away that sounds like the first case? Kafka 0.11 did change how some of these configs were checked broker-side (e.g. https://github.com/Shopify/sarama/issues/959#issuecomment-333950995) but AFAICT that was mostly loosening the restrictions, not tightening them.

In the case where compression is enabled the size test coming into async producer in dispatcher() is performed against the uncompressed payload. Is this intentional?

:thinking: it's been a while but I think it is; if I remember correctly the broker-side check is also against the uncompressed size. Or at least, it was for the older compression formats. It's possible that the new 1.0 record set format changed that?

I ran a quick couple of tests and it would seem the broker side uses compressed size for test.
producer messages.max.bytes 20M, compression off, topic created with  max.message.bytes 5M
msg size of 15M rejected "kafka server: Message was too large, server rejected it to avoid allocation error."
producer messages.max.bytes 20M, compression gzip, topic created with  max.message.bytes 5M
msg size of 15M accepted and consumer from kafka-console-consumer
(I set producer side to 20M to skip the test in dispatcher).

I think it is done like this because there is no efficient way to determine the size of the raw data after the compression, which you need to know in advance to spawn a new messages buffer in brokerProducer worker when it exceeds max message limit.
But this is not a big problem. In case you use compression and this limit, you can just make it 2-3 times larger (as the average compression rate), and this would give similar results.

kafka verion: 2.2
message bytes: 276
compression: off
sarama: 1.20.1
socket.request.max.bytes=1048576000  & a second try with 104857600
Ive been trying to produce the same message 10M times and its succeeds most times (5/6) but (1/6) fails with "message too large" error. It seems that if the size of each message is the same, the same number of messages should fit in each batch. It should either always success or always fail, no?


Optimum-Intel Notebook

Hi @tomaarsen
This fixes a small type and replaces the SetFit model with the same model but under my namespace so I can track usage more easily.
Thanks

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


theme openwrt-2020: cut fqdn in titles

Something like hostonly = hostname:match("^[^%.]+") should be simpler and more efficient.
Apart from that please don't hardcode OpenWrt @  in the title.

Thanks, im not an expoer in javascript!
Why should "OpenWrt" not be hardcoded, and replaced by what? It should not be translated and OpenWrt is not renamed so often :)

Yep, % is the escape character in Lus regular expression patterns, see https://www.lua.org/pil/20.2.html
As for the OpenWrt remark - OpenWrt is often used by downstream projects that wish to rebrand it to something else, for that there exists a configuration option (https://github.com/openwrt/openwrt/blob/master/package/base-files/image-config.in line 158) which we should respect. Since parsing that from /etc/os-release or /etc/openwrt_version is tedious and introduces further overhead it might be easier to not show any distro name to begin with.

Thx!
But it is okay to have "luci" in the title?
Using the name of the web site which opened as the 1st in the title and after that the subpage is common. Just open some webiste. This helps to find the correct browser tab quickly. When you have opened many tabs, only the start of the title is displayed.
What about to add VERSION_DIST to a place where it could accessed with less overhead? Maybe ubus?
Btw, you could attach #L158 to github links

As there is yet existing because of the hostname
local boardinfo = util.ubus("system", "board") or { }

it is enough to add
local distrib = boardinfo.release.distribution or "?"

Problem I see now is that when there's multiple tabs open with different OpenWrt devices, they all start with OpenWrt - ...

Title hah to set for for every skin
This commit is only a "backport" form dark skin, which im using.
So i not really need this, and as you dont like it i just close it


Memory Leak causes invalid junit XML output

When using the latest git version and memory leak detection, in case of an error the junit xml output can contain invalid characters.
It would be good, if the memory dump is either completely suppressed when using xml output, or the output is done as hex numbers.

I assume this is fixed now. If not, please post a test that shows this.


Navigating Recursively Not Supported?

I have a dynamic route /:username. On mobile, if I navigate from /user1 to /some-other-page and link to /user2, rather than pushing a copy of that page with the new username parameter it navigates back to the previous page with the old username parameter. Is there some option or setting we need to enable in order to utilize recursive navigation?

can you try adding getId to your <Screen />?
<Screen
  name="user"
  getId={({ params }) => params?.username}
/>

@nandorojo That worked, thanks! Did I miss this somewhere in the documentation? If not, it would be great if it could be added.

Check out React Navigation docs for most configuration on the native side: https://reactnavigation.org/docs/screen/#getid

Okay, that's useful, but as someone who's been using React Navigation for years I've never needed that prop until using React Navigation + Solito, so it would have been helpful to me to have had this linked from the Dynamic Route section in the documentation.
Thanks again!

yeah that’s a good place to document it, I’m open to a PR

PR: https://github.com/nandorojo/solito/pull/176


dynamixel-workbench: 0.2.0-0 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository dynamixel-workbench to 0.2.0-0:

upstream repository: https://github.com/ROBOTIS-GIT/dynamixel-workbench.git
release repository: https://github.com/ROBOTIS-GIT-release/dynamixel-workbench-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.5.26
previous version for package: 0.1.9-0

dynamixel_workbench
* added conver function to PRO user
* added dxl_info_cnt init function
* added compatibility for different protocol
* added static
* added convert function
* added baudrate sorting
* added all dynamixel series
* added RX-10
* added millis
* added init dynamixel example
* added setting for packet handler
* added monitor example
* added item
* added dynamixel_item
* added toolbox_ros and modified arduino path
* added linux build and example
* added begin and getprotocolversion function
* modified linux version
* modified description
* modified model_info
* modified variable range
* modified setTools function
* modified sync function
* modified merge conflict
* modified variable name
* modified reset function
* modified function name and return variable name
* modified name of return var
* modified item name
* modified reset function
* modified item name (added underscore)
* modified function name
* modified function for ROS depend
* modified function to make space
* modified begin function to reduce storage space
* modified MX (2.0) protocol setting bug
* modified example
* modified sync and bulk comm
* modified lib
* modified begin
* modified variable
* modified begin function
* modified joint and wheel mode
* modified variable name
* modified begin function
* modified set function
* modified dynamixel item
* modified scan function
* modified folder tree
* modified dynamixel_tool
* modified toolbox structure
* modified .device and modified funtion for opencm and opencr
* modified ifdef
* modified get file
* modified arduino version
* modified get device in arduino
* fixed reset bug
* deleted dead code
* deleted empty space
* deleted xl define
* deleted debug code and update ping func
* test OpenCM
* Contributors: Darby Lim, Karl D. Hansen, Yoonseok Pyo

dynamixel_workbench_controllers
* added blank
* added linux build and example
* added multi port example
* modified bug
* modified torque example
* modified example
* modified controllers
* modified linux version
* deleted build
* deleted footnote
* deleted annotation
* Contributors: Darby Lim, Yoonseok Pyo

dynamixel_workbench_operators
* modified example
* deleted build
* Contributors: Darby Lim, Karl D. Hansen

dynamixel_workbench_single_manager
* added debug code
* added scan range param
* added baudrate sorting
* added all dynamixel series
* added publisher
* added new msg header
* added AX Message
* added protocol version function
* added linux build and example
* modified merge conflict
* modified make file
* modified function name and return variable name
* modified factory rest and added baud rate function
* modified function for ROS depend
* modified linux version
* deleted warning
* Contributors: Darby Lim, Yoonseok Pyo

dynamixel_workbench_single_manager_gui
* added baudrate sorting
* added baud rate item and operating mode item
* added linux build and example
* modified dynamixel workbench lib
* modified make file
* modified function
* deleted build
* Contributors: Darby Lim

dynamixel_workbench_toolbox
* added conver function to PRO user
* added dxl_info_cnt init function
* added compatibility for different protocol
* added static
* added convert function
* added baudrate sorting
* added all dynamixel series
* added RX-10
* added millis
* added init dynamixel example
* added setting for packet handler
* added monitor example
* added item
* added dynamixel_item
* added toolbox_ros and modified arduino path
* added linux build and example
* added begin and getprotocolversion function
* modified linux version
* modified description
* modified model_info
* modified variable range
* modified setTools function
* modified sync function
* modified merge conflict
* modified variable name
* modified reset function
* modified function name and return variable name
* modified name of return var
* modified item name
* modified reset function
* modified item name (added underscore)
* modified function name
* modified function for ROS depend
* modified function to make space
* modified begin function to reduce storage space
* modified MX (2.0) protocol setting bug
* modified example
* modified sync and bulk comm
* modified lib
* modified begin
* modified variable
* modified begin function
* modified joint and wheel mode
* modified variable name
* modified begin function
* modified set function
* modified dynamixel item
* modified scan function
* modified folder tree
* modified dynamixel_tool
* modified toolbox structure
* modified .device and modified funtion for opencm and opencr
* modified ifdef
* modified get file
* modified arduino version
* modified get device in arduino
* fixed reset bug
* deleted dead code
* deleted empty space
* deleted xl define
* deleted debug code and update ping func
* test OpenCM
* Contributors: Darby Lim, Yoonseok Pyo

Is this the same release which was reverted in #17018?

It looks like it. @robotpilot should this be 0.2.1?

It is fixed version.

오전 6:53에 "Tully Foote"<EMAIL_ADDRESS>작성:

It looks like it. @robotpilot https://github.com/robotpilot should this
be 0.2.1?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ros/rosdistro/pull/17019#issuecomment-367487018, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACktq7lk22rqTrzD7Jge3AAf3WFp_J_lks5tXJBwgaJpZM4SM3BC
.

I see, you retagged 0.2.0. In general we don't recommend retagging. There are many parts of build and release systems that expect tags to be constant, and cache the content/do not retrigger if the version is the same as a previously known release. I think this will go through and overwrite past tagged versions but if it doesn't you may need to release 0.2.1 to make sure the updates propagate correctly. In the future we strongly recommend avoiding changing tags.
Checking the release repo it appears that you cleared it and created a new one without the current tags. We generally recommend keeping the old tags and branchs available. Removing them will break anyone who is trying to build based on the current state and will not allow rollbacks.

@tfoote @dirk-thomas
I didn't know the rule about retagging. I'm sorry about it.
I would like to express my gratitude to Tully and Thomas for understanding this.
If the problem still occurs in this revised patch, we will re-PR it again in the next sync.
I appreciate the ongoing package management and building work of the ROS community.
I seem to be disturbed by their efforts. I will do my best to build our system to prevent this from next week.
I have to follow as much as you do, but I am really sorry that I can't.
Thank you so much.


Update plugin_transmission.py to fix bug #2804

Try to fix bug #2804 by making RPC client object re-initiated for every task rather then doing it once for whole plugin.

Oops, sorry, didn't see you had made the change. Thanks!

Oops, sorry, didn't see you had made the change. Thanks!


The great refactor - 0.5

We're going to do a big refactor of the source code in the next couple of days to change the internals and improve the API. Anyone planning to make a big PR might want to hold off until we're done.

Wow this sounds ominous! But also great since we'll be much better positioned for future improvements.

Things we might want to implement:

https://github.com/apollostack/apollo-client/issues/706
https://github.com/apollostack/apollo-client/issues/646
https://github.com/apollostack/apollo-client/issues/644
https://github.com/apollostack/apollo-client/issues/615
https://github.com/apollostack/apollo-client/issues/616
https://github.com/apollostack/apollo-client/issues/617

Additional stuff:

Move to graphql-anywhere
Implement stuff from this document: https://meteor.quip.com/hyaMALbIQFK9

Hi guys,
I know this is a hard question to answer, but what is your rough estimate for this release? I'm not expecting to hear the exact date as I understand that there is still too much uncertainty given the number of open issues. However, what would be good is to know the order of the deadline – is it expected to be in a couple of weeks or sometime next year?
The main reason why I'm curious is because I'd love to try a GraphQL file upload (#586) at some point. You seem like preparing some great changes and I'm really looking forward to play with them!

Hmm.. I remember seeing #586 in Release 0.5 milestone, which was added there 8 days ago. But that label is no longer there.

GitHub keeps track of milestones being added or removed, so I don't think it was.
0.5 is currently very close to release, so any new features would be something for the next release.
The first step would be working on a design, perhaps let's talk on the existing issue or open a new issue about file upload to do a discussion?

lined up in #843


[SUPPORT]  Failed to archive commits,  thow  error 'Directory is not empty'

hudi version:  0.10.0-patch
fs: aws s3
log:
2022-04-22 17:31:51
org.apache.flink.util.FlinkException: Global failure triggered by OperatorCoordinator for 'hoodie_stream_write' (operator ef1a0eded9d886851d0ae5a7b94ad01d).
	at org.apache.flink.runtime.operators.coordination.OperatorCoordinatorHolder$LazyInitializedCoordinatorContext.failJob(OperatorCoordinatorHolder.java:553)
	at org.apache.hudi.sink.StreamWriteOperatorCoordinator.lambda$start$0(StreamWriteOperatorCoordinator.java:170)
	at org.apache.hudi.sink.utils.NonThrownExecutor.lambda$execute$0(NonThrownExecutor.java:103)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.hudi.exception.HoodieException: Executor executes action [commits the instant<PHONE_NUMBER>3115515] error
	... 5 more
Caused by: org.apache.hudi.exception.HoodieCommitException: Failed to archive commits
	at org.apache.hudi.table.HoodieTimelineArchiveLog.archive(HoodieTimelineArchiveLog.java:334)
	at org.apache.hudi.table.HoodieTimelineArchiveLog.archiveIfRequired(HoodieTimelineArchiveLog.java:130)
	at org.apache.hudi.client.AbstractHoodieWriteClient.archive(AbstractHoodieWriteClient.java:765)
	at org.apache.hudi.client.HoodieFlinkWriteClient.postCommit(HoodieFlinkWriteClient.java:339)
	at org.apache.hudi.client.AbstractHoodieWriteClient.commitStats(AbstractHoodieWriteClient.java:198)
	at org.apache.hudi.client.HoodieFlinkWriteClient.commit(HoodieFlinkWriteClient.java:112)
	at org.apache.hudi.sink.StreamWriteOperatorCoordinator.doCommit(StreamWriteOperatorCoordinator.java:496)
	at org.apache.hudi.sink.StreamWriteOperatorCoordinator.commitInstant(StreamWriteOperatorCoordinator.java:472)
	at org.apache.hudi.sink.StreamWriteOperatorCoordinator.lambda$notifyCheckpointComplete$2(StreamWriteOperatorCoordinator.java:225)
	at org.apache.hudi.sink.utils.NonThrownExecutor.lambda$execute$0(NonThrownExecutor.java:93)
	... 3 more
Caused by: org.apache.hudi.exception.HoodieIOException: `s3a://sprs-qz-dw-prod-ue1/qz_ods/ac_account_transfer_record/.hoodie/.temp/20220421063410412': Directory is not empty
	at org.apache.hudi.common.fs.FSUtils.deleteDir(FSUtils.java:655)
	at org.apache.hudi.table.marker.DirectWriteMarkers.deleteMarkerDir(DirectWriteMarkers.java:75)
	at org.apache.hudi.table.HoodieTimelineArchiveLog.deleteAnyLeftOverMarkers(HoodieTimelineArchiveLog.java:340)
	at org.apache.hudi.table.HoodieTimelineArchiveLog.archive(HoodieTimelineArchiveLog.java:320)
	... 12 more
Caused by: org.apache.hadoop.fs.PathIsNotEmptyDirectoryException: `s3a://sprs-qz-dw-prod-ue1/qz_ods/ac_account_transfer_record/.hoodie/.temp/20220421063410412': Directory is not empty
	at org.apache.hadoop.fs.s3a.S3AFileSystem.innerDelete(S3AFileSystem.java:1752)
	at org.apache.hadoop.fs.s3a.S3AFileSystem.delete(S3AFileSystem.java:1697)
	at org.apache.hudi.common.fs.HoodieWrapperFileSystem.lambda$delete$14(HoodieWrapperFileSystem.java:340)
	at org.apache.hudi.common.fs.HoodieWrapperFileSystem.executeFuncWithTimeMetrics(HoodieWrapperFileSystem.java:100)
	at org.apache.hudi.common.fs.HoodieWrapperFileSystem.delete(HoodieWrapperFileSystem.java:339)
	at org.apache.hudi.common.fs.FSUtils.deleteDir(FSUtils.java:650)
	... 15 more

.temp/20220421063410412   has subfolder

@todd5167 Did you retry? From stacktrace it looks like recursive delete failed at some point. Can you please share hudi write configs and data timeline (in .hoodie directory)? Also, what was the state of .temp/20220421063410412 directory at the time? If it's still intact can you please send the ls -lrt .temp/20220421063410412 ?

Looks like we don't allow recursive delete in some cases https://github.com/apache/hudi/blob/762623a15cfeba6f3fe936c238d660685ae62b50/hudi-common/src/main/java/org/apache/hudi/common/fs/FSUtils.java#L686
@yihua do you know why that's the case?

All the subdirs are deleted in parallel before executing L686 above.  It is likely that there are concurrent operations on the same instant, e.g., one trying to delete the .temp/<instant_time> while the other adding new markers to .temp/<instant_time>.  @todd5167 Once you provide more information on the timeline as @codope suggested, we can dig deeper into the root cause.

@yihua @codope  Flink writes hudi configuration information as follows. I have restored from flink savepoint multiple times and keep getting this error.  When the exception occurs .temp/20220421063410412 has subfolders.    My temporary solution is, boolean result = fs.delete(dirPath, true); not sure what's wrong with this.
  'connector' = 'hudi',
  'path' = 's3a://xxxxxxx/hudi/ac_withdraw_record',
  'table.type' = 'MERGE_ON_READ',
  'write.bucket_assign.tasks' = '2',
  'write.tasks' = '2',
  'changelog.enabled' = 'false',
  'hoodie.cleaner.policy' = 'KEEP_LATEST_FILE_VERSIONS' ,
  'hoodie.cleaner.fileversions.retained' = '2' ,
  'write.task.max.size' = '2048',
  'write.index_bootstrap.tasks' = '4',
  'index.bootstrap.enabled' = 'true',
  'index.global.enabled' = 'false',
  'compaction.tasks' = '4',
  'compaction.max_memory' = '1024',
  'hoodie.compact.inline.trigger.strategy' = 'NUM_COMMITS',
  'hive_sync.enable' = 'true',
  'hive_sync.mode' = 'glue',
  'hive_sync.table' = 'ac_withdraw_record',
  'hive_sync.skip_ro_suffix' = 'true',
  'hive_sync.db' = 'hudi_meta',
  'hoodie.compact.inline.max.delta.commits' = '6'

@todd5167 the point is that even before fs.delete(dirPath, false) is called, the subfolders should have been deleted already.  So I'm wondering why the subfolders are not deleted in the first place.  If you're not comfortable sharing the whole .hoodie folder, could you simply list the .hoodie folder with aws s3 ls <table_path>/.hoodie?  Or you can take a screenshot of the files in .hoodie folder in S3 Web UI.  I'm interested in the timeline of the table, and the type of instance<PHONE_NUMBER>3410412, whether it is deltacommit, compaction, etc.

I have restored from flink savepoint multiple times and keep getting this error.

I guess you mean you tried to restart the flink job but kept hitting the same exception.  I assume you're not talking about Hudi restore or savepoint?

@yihua   Because this problem causes the flink job to restart frequently, I use fs.delete(dirPath, true) to delete the folder.After I changed the code again, the ./hoodie folder was cleaned up by me. I re-consume historical data and incremental data again.

@todd5167 Got it.  If you can also provide the steps in your setup to reproduce the problem, we can try to reproduce the problem on our end as well to identify the root cause.  @danny0405 are you aware of a similar issue of deleting marker directory in Flink?

deleteAnyLeftOverMarkers

I'm not quite sure, we actually clean the MARKER folder each time we commit an instant, and here we do it again when the instant was archived? (curious about the background here ?), and like what @codope saied, the call in #L682-L684 already delete recursively first.
The instant commit and archiving both happens in JobManager in single thread, so there should not be parallelism problem.
@todd5167 Did you write to the same table from two separate Flink jobs ?

deleteAnyLeftOverMarkers

I'm not quite sure, we actually clean the MARKER folder each time we commit an instant, and here we do it again when the instant was archived? (curious about the background here ?), and like what @codope saied, the call in #L682-L684 already delete recursively first.
The instant commit and archiving both happens in JobManager in single thread, so there should not be parallelism problem.
@todd5167 Did you write to the same table from two separate Flink jobs ?

@danny0405  A flink job corresponds to a hudi table.   checkpoint config:
Interval	10m 0s
Timeout	 3m 0s
Minimum Pause Between Checkpoints	0ms
Maximum Concurrent Checkpoints	2

So you do not write into same table from two separate Flink jobs.

So you do not write into same table from two separate Flink jobs.

yes

@todd5167 What kind of instant of time<PHONE_NUMBER>3410412, is it a delta commit or commit or cleaning ?

@todd5167 : can you respond to Danny's question above. and if you got it working, can you let us know what was the root cause and how did you get around it.

@nsivabalan  @danny0405    I deleted the ./hoodie folder and re-executed it because I needed to restore the task.Therefore, I can't see the Action information.

@todd5167 I'm going to close this ticket as you have got past it.  Feel free to reopen the issue if you see it again.


[Security] Fix DOM XSS vulnerability in search

When displaying a user's search query on the search results page, we should use textContent instead of innerHTML to prevent XSS per this OWASP cheatsheet.
Note: This change is already in dev.

Coverage remained the same at 98.913% when pulling d9b272cca1b8e400524fabafaa6979d141865e3e on fix-search-dom-xss into 73f13ac9de0acbd4fa28246c7a99f1f3acccd95b on master.


T5 Model Bringup

Unique ops in T5

Eltwise

multiply
add
sqrt
subtract
recip
exp

Reduce Avg
Reduce Max
Reduce Sum
Reshape
Matmul
hslice
hstack
transpose

Besides, the proposed set of ops, these are related to the inference? I assume training for T5 is still TBD until we get few more PoC for the basic MNIST models working e2e.

What do you think about creating milestones for each model that we're bringing up?
As we're at the early stage of this compiler, there will be more jobs for each model to work e2e. Therefore, it seems reasonable to have milestones for each one until we see that the new model bringup is becoming less complex.
I'm asking this as a new op bringup can be a good ramp-up task for new folks on Forge and MLIR projects. Therefore, having some of them in the backlog is beneficial.

I agree completely and I really like this idea of having milestones for each model.  There will be a lot of overlapping work between the models so it could help to have individuals run ahead, try pushing on a model, file issues for the ops/issues they're running into and then we can cross-reference which models are blocked on what which can help us prioritize what the best bang for buck is.
And yet, above was just inference.


feat: --force-schema-version CLI option

It forces Schemathesis to use the specific Open API spec version when parsing the schema
Closes #876

Codecov Report

Merging #878 (d94ae1b) into master (aeca312) will decrease coverage by 0.05%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #878      +/-   ##
==========================================
- Coverage   98.97%   98.92%   -0.06%
==========================================
  Files          62       62
  Lines        4292     4263      -29
  Branches      733      735       +2
==========================================
- Hits         4248     4217      -31
- Misses         21       22       +1
- Partials       23       24       +1

Flag
Coverage Δ

unittests
98.92% <100.00%> (-0.04%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/schemathesis/runner/__init__.py
100.00% <ø> (ø)

src/schemathesis/cli/__init__.py
100.00% <100.00%> (ø)

src/schemathesis/loaders.py
96.73% <100.00%> (+0.31%)
:arrow_up:

src/schemathesis/extra/pytest_plugin.py
98.38% <0.00%> (-1.62%)
:arrow_down:

src/schemathesis/models.py
96.25% <0.00%> (-0.10%)
:arrow_down:

src/schemathesis/hooks.py
98.18% <0.00%> (-0.05%)
:arrow_down:

src/schemathesis/lazy.py
98.61% <0.00%> (-0.02%)
:arrow_down:

src/schemathesis/runner/events.py
98.76% <0.00%> (-0.02%)
:arrow_down:

src/schemathesis/runner/impl/core.py
97.36% <0.00%> (-0.02%)
:arrow_down:

src/schemathesis/targets.py
100.00% <0.00%> (ø)

... and 8 more

Continue to review full report at Codecov.

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


Revisit IJsonOutputFormatter

IJsonOutputFormatter is currently just used as a marker interface to indicate that a formatter outputs JSON. We should revisit this approach and see if we can come up with something cleaner and more general.

We decided to remove the dependency on formatting in JsonResult and JsonViewComponentResult and instead just use JSON.NET directly. Remove IJsonOutputFormatter as part of this work.

Part 1 - f206cf6759dd09920c8a30cd98e2800e70e878cf

Are the serializer settings from MvcJsonOptions still used by default?

I look a look here and @JamesNK is right. This should be respecting MvcJsonOptions


Add codecov.io setup - fixes #18

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@46ddb1e). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             master    #25   +/-   ##
=======================================
  Coverage          ?   100%
=======================================
  Files             ?      6
  Lines             ?     74
  Branches          ?      0
=======================================
  Hits              ?     74
  Misses            ?      0
  Partials          ?      0

Continue to review full report at Codecov.

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


Drop support for pandas<2

[x] Closes #10962
[ ] Tests added / passed
[ ] Passes pre-commit run --all-files

For context: We decided to hold off merging this until after the next release so that we can remove python 3.9 support in the same release


Docs remake

Still need to merge content 😄

Well I did get it to build on me machine 😅 however this could also be a similar issue to what I experienced in my own deployment earlier - literally deleted the vercel project and re-initialized it with the same src and it worked again... lets cross that bridge later


Calls nmap with ip:port tuples instead of IP addresses

While trying to recover a small "hobby" cluster from broken sync, one of the three nodes was unable to come up without non-Puppet intervention:
Error: '/usr/bin/galera_new_cluster' returned 1 instead of one of [0]

It was trying to bootstrap even though other machines in the cluster were up already. strace showed nmap getting called with funky arguments:
[pid 26009] execve("/usr/bin/grep", ["grep", "-q", "4567/tcp open"], 0x55c0bd142b78 /* 27 vars */ <unfinished ...>
[pid 26008] execve("/usr/bin/nmap", ["nmap", "-Pn", "-p", "4567", "192....208:4567", "90....198:4567", "192....2:4567"], 0x55c0bd142b48 /* 27 vars */ <unfinished ...>

(IPs middle octets garbled but otherwise unmodified) Failed 3× in a row including one after a full package purge again. I've just upped MySQL by hand, and a subsequent puppet run worked fine.
Sorry, don't have a trace now, but can do experiments if needed.

@Wilm0r Please add the Puppet config/code that you are using for Galera/MySQL.

Oops yes, forgot.
$galera_ips = ["192....208", "90....198", "192....2"]

class sql_replica {
        $all_ip4 = ($networking["interfaces"].map |$if, $ips| { $ips["ip"] }).filter |$ip| { $ip != undef }

        class { "galera":
                cluster_name    => "mysql.i.gaast.net",
                galera_servers  => $galera_ips,
                galera_master   => "tosca.beilen.gaast.net",
                local_ip        => intersection($all_ip4, $galera_ips)[0],
                configure_firewall => false,

                vendor_type     => "mariadb",
                vendor_version  => "10.3",
                # Passwords removed
}

I now realise this was on the machine tagged as master, so obviously that explains part of why it was trying to bootstrap there and not on the others, ugh I don't know how I missed that. But still, the arguments to nmap were wrong, and I'm certainly giving it clean IP addresses.
Full versions list at https://p.gaa.st/view/adb999ef

#162


Fix Nav bar styles

Overview
A couple style updates to the nav bar.
Details

Increase the font-size of the “Settings” tab to be consistent with the others.
Admin view: Fix the background color of the subtabs of “Settings” and Profile on hover and click
Volunteer view: Same thing with Profile tab
There should be 1 color that fills the entire item (gray for hover, red for click)
View example screenshots here

Assign me

The hover & click colors look perfect!
But the font size of the settings tab still does not look very consistent with others on my end.


[SDPA-2985] Prominent acknowledgment message.

JIRA issue: https://digital-engagement.atlassian.net/browse/SDPA-2985
Changed

Add 'default' and 'standalone' themes to acknowledgment.
Add styling for standalone theme.
Add to Tide page with check on 'field_show_ack_to_country' field.

Screenshots

Hi @alan-cole please update story snapshots if failed in tests.


Treemap controls migration

CATEGORY
Choose one

[ ] Bug Fix
[ ] Enhancement (new features, refinement)
[x] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY
Moving unique control(s) from controls.jsx to /explore/controlPanels/Treemap.js

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN

ADDITIONAL INFORMATION

[x] Has associated issue: https://github.com/apache/incubator-superset/issues/9187
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

REVIEWERS
@kristw This is a teeny one... lots more of these coming. I'm assuming these will be easier to review if they come in one at a time, but let me know if you'd prefer I batch them.

Codecov Report

Merging #9352 into master will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #9352   +/-   ##
=======================================
  Coverage   59.00%   59.00%
=======================================
  Files         374      374
  Lines       12133    12133
  Branches     2987     2987
=======================================
  Hits         7159     7159
  Misses       4795     4795
  Partials      179      179

Impacted Files
Coverage Δ

superset-frontend/src/explore/controls.jsx
40.14% <ø> (ø)

Continue to review full report at Codecov.

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


Adding 6 as a valid option for the manual feed

The number 6 is not a valid option when Manual feed hooper is used. I added the number 6 to the array of valid options.

Oh really I miss the 6... Good catch.
Thank you for your help 🙂


What is the format of sending the event ？

hi , i want to send an event to Core Data. I query the document and find it hasn't been updated yet (I have cleared the browser cache). I also looked this up, but didn't know what format to send the event JSON.

Could you please tell me what the format is or tell me how to query ? Thanks.

It's AddEventRequest
https://app.swaggerhub.com/apis-docs/EdgeXFoundry1/core-data/2.0.0#/AddEventRequest
Please refer to the API document
https://app.swaggerhub.com/apis-docs/EdgeXFoundry1/core-data/2.0.0#/default/post_event__profileName___deviceName___sourceName_
The v2 document is still working in progress.  We will fix it.

We have this issue https://github.com/edgexfoundry/edgex-docs/issues/495 to track this document update.


completed task10

issue: #219

Hey @adityaagg4689
Thanks for opening this PR 🚀. Mentor will review your pull request soon and till then, keep contributing and stay calm.
Thanks for contributing in OpenCode'24 ✨✨!

Hey @adityaagg4689
Your PR has been merged 🥳🥳 and you have earned 10 points.
Thanks for contributing in OpenCode'24 ✨✨


Generated names should be pretty regardless of case

Our database uses camel case for our column names and I've used camel case for our query labels as well and the result is SOMEQUERYTHATISCAMELCASED. It would be nice if camel case would generate SOME_QUERY_THAT_IS_CAMEL_CASED as well.
If I use underscore the generated sql states are named Update_hockey_player which is a bit ugly.

With the new version 0.6, it would be also cool if class names would start with an upper case letter (new Foo.InsertAllFooFields for an insertAllFooFields label) and method names would be lowercase (Foo.FACTORY.selectAllFooFields(...) and Foo.FACTORY.selectAllFooFieldsMapper() for an selectAllFooFields label on a SELECT query).
Right now, you have to use uppercase INSERT, UPDATE and DELETE label names and lowercase SELECT label names to achieve proper naming.

Case mapping is generally a terrible practice that we actively avoid.
Supporting multiple casing strategies is doubly bad.
We'll likely instead get to a place where a single case style creates
fairly idomatic generated code. Yes we're not there yet, but we're not
going to be doing crazy case mapping transformations and won't be
supporting multiple case styles for labels or column names.
On Thu, Mar 16, 2017 at 5:59 AM Thomas Keller<EMAIL_ADDRESS>wrote:

With the new version 0.6, it would be also cool if class names would start
with an upper case letter (new Foo.InsertAllFooFields for an
insertAllFooFields label) and method names would be lowercase (
Foo.FACTORY.selectAllFooFields(...) and
Foo.FACTORY.selectAllFooFieldsMapper() for an selectAllFooFields label on
a SELECT query).
Right now, you have to use uppercase INSERT, UPDATE and DELETE label
names and lowercase SELECT label names to achieve proper naming.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/square/sqldelight/issues/602#issuecomment-287009606,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEEESZor-_dsrNkxHfLFq1ZQFokgFNAks5rmQgKgaJpZM4MeYd0
.

This would be solved using aliases too I guess.

As of the next version (0.7.0) we only generate methods and classes for which camelCase suffices.
I'm not sure we even need to generate the table and column constants anymore...


Makes Secrets module

Problem to solve
First:
Creating a sops encrypted file should be simple, let's create a terraform module for it,
so products can just invoke the module and voila! a sops key is possible
Second:
Having dev/prod keys is not enough for re-usability.
Today if we want to have creds for some service, then we have to:

copy paste creds, which hurts maintainability
use many product roles for 1 product, which hurts separation of concerns

Proposal
Abstract common code with terraform modules so we avoid this copy-paste
Once creating kms keys with terraform modules is simple, then let's have many sops files for common objects, for instance:

sops file for redshift db creds
sops file for X shared product

Then grant product users access to the individual sops files, for maximum access control and granularity

As terraform infra handles a state, I figured this would be easier to implement by managing modules in our product repository that would allow to:

Create aws and cloudflare users
Create kms keys
Publish aws users to gitlab

All these features were implemented here and are being used across all our products.
Regarding simplifying sops secrets creation, makeSopsEncryptedFile utility has been created.


Auto-select text onResume

Text should be auto selected when user goes back to app

Fixed in<PHONE_NUMBER>d0b3f2e5a3c07c77efd7dbf7dc8a0d

I'm reopening this, it seems that the text is auto selected only when the edit view loses focus and that doesn't happen as often as I thought it would.

I think this is ok with 8149b1e4e4d23985c0044685d8a42d8a2013bcf8


[FEAT]: Embedded chat usability from a backend customer support standpoint.

What would you like to see?
(1) Is there a way we can refer to the sessionID in any of the inputs? Example:
Allow us to set data-sponsor-link="https://something.com?chat_session_id=SESSION_ID".

Have the script fill in the sessionID.
Would you be willing to do that?
Would let us correlate client and conversation.

RE: README.md
(2) Would be really useful to be able to search embed chat history by sessionID.

Also, can't really see the whole sessionID.

(3) Is there a way to customize the message that shows up when the quota for the embed session has been surpassed?

To a customer, it might appear like we didn't pay our bill, and we want to let them know in a diplomatic way that their number of chats are limited... while also not appearing inept.

Our support team would be very pleased with these small improvements :)
❤

This issue was copied from another thread. For some reason my phone is having trouble copying the images. Here is the link to the other thread with the screenshots for context. https://github.com/Mintplex-Labs/anything-llm/issues/1511#issuecomment-2131466688

Concerning (1).
Would be nice to have feature (1) available in all the possible link fields, including emails.
Also, usage possibilities for mailto.
Btw, do we need to make that a mailto, or does the embedded script do it? Exploring this: https://dev.to/cooljasonmelton/more-stuff-you-can-do-with-mailto-3o89. That way if a user clicks the email or the link to create a ticket, the sessionID gets to hitch a ride :)
(4) low priority for us.
And one Very small thing our folks noticed is that the embedded chat text input area is not centered vertically.


Identity 3863

Should be put in hole until required changed to kernel are committed..

https://github.com/wso2/carbon-kernel/pull/577


Unknown error occurred

Guys first installation and I keep getting "Unknown error occurred".
Using Nefit Easy (CT100).
Nefit Easy Bosch Thermostat integration works.
Any advise where to start troubleshooting?

2022-07-07 17:56:07 WARNING (MainThread) [aioxmpp.node.PresenceManagedClient] out of connection attempts
2022-07-07 17:56:07 ERROR (MainThread) [aioxmpp.node.PresenceManagedClient] main failed
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/aioxmpp/node.py", line 837, in _on_main_done
task.result()
File "/usr/local/lib/python3.9/site-packages/aioxmpp/node.py", line 996, in _main
await self._main_impl()
File "/usr/local/lib/python3.9/site-packages/aioxmpp/node.py", line 951, in _main_impl
tls_transport, xmlstream, features = await connect_xmlstream(
File "/usr/local/lib/python3.9/site-packages/aioxmpp/node.py", line 384, in connect_xmlstream
options = list(await discover_connectors(
File "/usr/local/lib/python3.9/site-packages/aioxmpp/node.py", line 145, in discover_connectors
starttls_srv_records = await network.lookup_srv(
File "/usr/local/lib/python3.9/site-packages/aioxmpp/network.py", line 331, in lookup_srv
answer = await repeated_query(
File "/usr/local/lib/python3.9/site-packages/aioxmpp/network.py", line 300, in repeated_query
raise TimeoutError()
TimeoutError
2022-07-07 17:56:07 ERROR (MainThread) [custom_components.bosch.config_flow] Error connecting Bosch at 519913648 -
2022-07-07 17:56:07 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request
resp = await request_handler(request)
File "/usr/local/lib/python3.9/site-packages/aiohttp/web_app.py", line 504, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.9/site-packages/aiohttp/web_middlewares.py", line 117, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 79, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 220, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 137, in handle
result = await result
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 205, in post
return await super().post(request, flow_id)
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 62, in wrapper
result = await method(view, request, *args, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 109, in post
result = await self._flow_mgr.async_configure(flow_id, data)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 260, in async_configure
result = await self._async_handle_step(
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 348, in _async_handle_step
if result["type"] not in (
TypeError: 'NoneType' object is not subscriptable

I have tried both. first Nefit and now Easycontrol. Same results (identical log)

Well, I do use a VPN, but neither my Nefit easy nor my HAOS run through a VPN.
I do run pfSense+ with pfBlockerNG and snort installed.
Do you think it may have to do with that? Why?
Again, my ksya/ha-nefiteasy integration works (some disconnections occasionally and currently not working with 2022.7.0). The Nefit android app and HAOS work fine.
Thanks anyway for thinking with me.

other people reported that wrong configuration of vpn made Bosch servers to ban vpn IPs. If you use Nefit easy, then you should use Nefit option in my intergation. Try without vpn and let me know

not running through a VPN. i'll see if i can find some info in firewall logs.
thanks anyway.


[Migrated] After running zappa deploy, i get these strange errors

Originally from: https://github.com/Miserlou/Zappa/issues/2158 by AkshayAwate
Traceback (most recent call last):
File "/home/akshay/.local/lib/python3.8/site-packages/zappa/cli.py", line 2778, in handle
sys.exit(cli.handle())
File "/home/akshay/.local/lib/python3.8/site-packages/zappa/cli.py", line 512, in handle
self.dispatch_command(self.command, stage)
File "/home/akshay/.local/lib/python3.8/site-packages/zappa/cli.py", line 538, in dispatch_command
self.load_settings(self.vargs.get('settings_file'))
File "/home/akshay/.local/lib/python3.8/site-packages/zappa/cli.py", line 2116, in load_settings
self.zappa = Zappa( boto_session=session,
File "/home/akshay/.local/lib/python3.8/site-packages/zappa/core.py", line 310, in init
self.lambda_client = self.boto_client('lambda', config=long_config)
File "/home/akshay/.local/lib/python3.8/site-packages/zappa/core.py", line 341, in boto_client
return self.boto_session.client(service, *args, **self.configure_boto_session_method_kwargs(service, kwargs))
File "/home/akshay/.local/lib/python3.8/site-packages/boto3/session.py", line 258, in client
return self._session.create_client(
File "/home/akshay/.local/lib/python3.8/site-packages/botocore/session.py", line 834, in create_client
client = client_creator.create_client(
File "/home/akshay/.local/lib/python3.8/site-packages/botocore/client.py", line 83, in create_client
client_args = self._get_client_args(
File "/home/akshay/.local/lib/python3.8/site-packages/botocore/client.py", line 285, in _get_client_args
return args_creator.get_client_args(
File "/home/akshay/.local/lib/python3.8/site-packages/botocore/args.py", line 71, in get_client_args
final_args = self.compute_client_args(
File "/home/akshay/.local/lib/python3.8/site-packages/botocore/args.py", line 147, in compute_client_args
endpoint_config = self._compute_endpoint_config(
File "/home/akshay/.local/lib/python3.8/site-packages/botocore/args.py", line 218, in _compute_endpoint_config
return self._resolve_endpoint(**resolve_endpoint_kwargs)
File "/home/akshay/.local/lib/python3.8/site-packages/botocore/args.py", line 300, in _resolve_endpoint
return endpoint_bridge.resolve(
File "/home/akshay/.local/lib/python3.8/site-packages/botocore/client.py", line 360, in resolve
resolved = self.endpoint_resolver.construct_endpoint(
File "/home/akshay/.local/lib/python3.8/site-packages/botocore/regions.py", line 133, in construct_endpoint
result = self._endpoint_for_partition(
File "/home/akshay/.local/lib/python3.8/site-packages/botocore/regions.py", line 148, in _endpoint_for_partition
raise NoRegionError()
botocore.exceptions.NoRegionError: You must specify a region.
zappa.settings.json
{
"dev": {
"django_settings": "backoffice.live_settings",
"profile_name": "default",
"project_name": "luna-new",
"runtime": "python3.8",
"s3_bucket": "zappa-undo0e9rf"
},
"dev_ap_east_1": {
"aws_region": "ap-east-1",
"extends": "dev"
},
"dev_ap_northeast_1": {
"aws_region": "ap-northeast-1",
"extends": "dev"
},
"dev_ap_northeast_2": {
"aws_region": "ap-northeast-2",
"extends": "dev"
},
"dev_ap_northeast_3": {
"aws_region": "ap-northeast-3",
"extends": "dev"
},
"dev_ap_south_1": {
"aws_region": "ap-south-1",
"extends": "dev"
},
"dev_ap_southeast_1": {
"aws_region": "ap-southeast-1",
"extends": "dev"
},
"dev_ap_southeast_2": {
"aws_region": "ap-southeast-2",
"extends": "dev"
},
"dev_ca_central_1": {
"aws_region": "ca-central-1",
"extends": "dev"
},
"dev_cn_north_1": {
"aws_region": "cn-north-1",
"extends": "dev"
},
"dev_cn_northwest_1": {
"aws_region": "cn-northwest-1",
"extends": "dev"
},
"dev_eu_central_1": {
"aws_region": "eu-central-1",
"extends": "dev"
},
"dev_eu_north_1": {
"aws_region": "eu-north-1",
"extends": "dev"
},
"dev_eu_west_1": {
"aws_region": "eu-west-1",
"extends": "dev"
},
"dev_eu_west_2": {
"aws_region": "eu-west-2",
"extends": "dev"
},
"dev_eu_west_3": {
"aws_region": "eu-west-3",
"extends": "dev"
},
"dev_sa_east_1": {
"aws_region": "sa-east-1",
"extends": "dev"
},
"dev_us_east_1": {
"aws_region": "us-east-1",
"extends": "dev"
},
"dev_us_east_2": {
"aws_region": "us-east-2",
"extends": "dev"
},
"dev_us_gov_east_1": {
"aws_region": "us-gov-east-1",
"extends": "dev"
},
"dev_us_gov_west_1": {
"aws_region": "us-gov-west-1",
"extends": "dev"
},
"dev_us_west_1": {
"aws_region": "us-west-1",
"extends": "dev"
},
"dev_us_west_2": {
"aws_region": "us-west-2",
"extends": "dev"
}
}

You're not defining "aws_region" in your stage definition.
closing.


Added parsing for vat_rate and address fields. Added static partner name field

This PR adds fields for VAT rate, address and partner name for Pepephone invoices.

@bosd pdftotext extracts it all in one line like this:
PEPEMOBILE S.L.Registro Mercantil de Madrid, Tomo 24.019, Libro 0, Folio 108, Sección 8, Hoja M-431409 e Inscripción 10ª. CIF: ESB85033470 Avda de Bruselas, num. 38,
28108 Alcobendas, Madrid. España

I've used the CIF to find that line, but the capture group only takes the address.

Thanks, now I understand


[Paper] Dark mode theme changes background color of AppBar and Paper

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
Theme with dark mode active slightly changes the background color of AppBar and Paper elements. EG #000000 turns into #171717 for the AppBar.
This does not happen when the mode is set to light.

Expected Behavior 🤔
#000000 should display as #000000.

Steps to Reproduce 🕹

https://codesandbox.io/s/appbar-y9tef?file=/src/App.tsx
Your Environment 🌎

Tech
Version

react
v17.0.2

@mui/material
v5.0.4

@emotion/react
v11.5.0

@emotion/styled
v11.5.0

  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

The AppBar and Paper in dark mode apply background-image in addition to background-color, based on elevation (to lighten up surfaces with higher elevation). If you'd like to override it, pass background: "#000" instead of backgroundColor: "#000" to the sx prop.

I am newbie in frontend and with mui, but it looks like not intuitive behavior, which was not clear documented

@XAKEPEHOK you're right, we don't have this in the docs. I'll update the Elevation section of the Paper documentation page.


perf: deadlocks with isolated-vm

Probably related to
https://github.com/laverdet/isolated-vm/issues/302
https://github.com/laverdet/isolated-vm/issues/307
https://github.com/laverdet/isolated-vm/issues/321
Reproducible example:
/* eslint-disable */

import {defaultCacheOptions, LoggerFactory, WarpFactory} from "warp-contracts";
import {IvmPlugin} from "warp-contracts-ivm-plugin";

LoggerFactory.INST.logLevel('debug');
// LoggerFactory.INST.logLevel('none', 'DefaultStateEvaluator');
const logger = LoggerFactory.INST.create('ivm-example');

async function main() {
  const contractTxId = 'XIutiOKujGI21_ywULlBeyy-L9d8goHxt0ZyUayGaDg';

  const warp = WarpFactory
    .forMainnet({...defaultCacheOptions, inMemory: true})
    .use(new IvmPlugin({}));

  const result = await warp
    .contract(contractTxId)
    .setEvaluationOptions({
      allowBigInt: true,
      internalWrites: true,
    })
    .readState();

  console.log(result.cachedValue.validity);
}

main().catch((e) => console.error(e));

In my case it always hangs at 1201. interaction:

We need to generate a stacktrace and report this to library authors.

Reading the above issues, it is probably also worth experimenting with isolated-vm version 4.3.6 (which probably requires downgrading the node to ver. 16).
If that won't help - try to temporarily remove the isolate disposal code - https://github.com/warp-contracts/warp-contracts-plugins/blob/main/warp-contracts-ivm-plugin/src/IvmHandlerApi.ts#L85

Downgrading to node 16.18.1, warp 12.30, isolated-vm in 4.3.6 works fine

https://github.com/laverdet/isolated-vm/issues/330

https://github.com/laverdet/isolated-vm/issues/330#issuecomment-1353254772 @janekolszak ?
although not sure if we want to use the isolated-vm...

Let's stick with VM2 + separate node process (supplied by the bullmq's sandboxed processors).
With the possible addition of the https://github.com/taskforcesh/bullmq/issues/1555 - it should be 'good enough' for now.
In the future - consider switching to SES.


temp table for pull tracking

Simple tracking table - to be deleted post-Neon interaction

Missing a comma... feel free to accept.

Sorry!!!
-- Thomas Keeley
If a Smurf holds its breath for too long, what color does it turn??
Para. Jeff Dunham
On Thu, Mar 29, 2018 at 5:34 AM, Aric Stewart<EMAIL_ADDRESS>wrote:

Missing a comma... feel free to accept.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/CON-In-A-Box/CIAB-Signin/pull/109#issuecomment-377194513,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABEkRJHPy_ZlqO2bDtva8Ra1dY6UhDWtks5tjLihgaJpZM4TAGFT
.

fixed.
-- Thomas Keeley
If a Smurf holds its breath for too long, what color does it turn??
Para.
Sorry!!!
-- Thomas Keeley
If a Smurf holds its breath for too long, what color does it turn??
Para. Jeff Dunham
On Thu, Mar 29, 2018 at 5:34 AM, Aric Stewart<EMAIL_ADDRESS>wrote:

Missing a comma... feel free to accept.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/CON-In-A-Box/CIAB-Signin/pull/109#issuecomment-377194513,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABEkRJHPy_ZlqO2bDtva8Ra1dY6UhDWtks5tjLihgaJpZM4TAGFT
.

Great!


List of shared lib Electron is dependent on

libgtk2
libgconf2
libnss3
libasound

The above list is what electron reports are missing when I was running it from a Ubuntu server without GUI built-in. After installing them I was able to run it and direct the view to my VcXsrv on the Windows host via SSH.
In addition to the above I also installed xdg-utils to eliminate an error message during running.
Any other stuff I should pay attention to in this development setup?

You can find a list in Build Instructions (Linux).