Connection to SparkGo issue

When trying to connect to spark go  a reboot loop occurs with the following error log.
21:10:42]Found Spark, connecting.
[21:10:42]Scan ended.
[21:10:42]Connected to: f7:eb:ed:0d:b5:3e
[21:10:42]Subscribing to service notifications of FFC2
[21:10:42]Notifications turned on
[21:10:42]Done with this device.
[21:10:42]BLE connection to Spark established.
[21:10:42]Changing to HW preset 1
[21:10:43]Changing to HW preset 1
[21:10:44]Changing to HW preset 1
[21:10:45]Guru Meditation Error: Core  0 panic'ed (LoadProhibited). Exception was unhandled.
[21:10:45]
[21:10:45]Core  0 register dump:
[21:10:45]PC      : 0x400d310f  PS      : 0x00060e30  A0      : 0x800e5e2c  A1      : 0x3ffd1690
[21:10:45]A2      : 0x3ffd16c4  A3      : 0xfffffff4  A4      : 0x00000014  A5      : 0x00060023
[21:10:45]A6      : 0x007bc970  A7      : 0x003fffff  A8      : 0x00000014  A9      : 0x3ffd435f
[21:10:45]A10     : 0x00000070  A11     : 0x3ffd4328  A12     : 0x3ffd41f8  A13     : 0x3ffd3f68
[21:10:45]A14     : 0x00000000  A15     : 0x00000003  SAR     : 0x00000020  EXCCAUSE: 0x0000001c
[21:10:45]EXCVADDR: 0xfffffff4  LBEG    : 0x40090839  LEND    : 0x4009085b  LCOUNT  : 0x00000000
[21:10:45]
[21:10:45]
[21:10:45]Backtrace: 0x400d310c:0x3ffd1690 0x400e5e29:0x3ffd16b0 0x400d5f3b:0x3ffd16f0 0x400d6332:0x3ffd1870 0x401e1452:0x3ffd18b0 0x400f7065:0x3ffd18d0 0x400ea0a9:0x3ffd1950 0x400ea0f3:0x3ffd1970 0x400eb50c:0x3ffd1990 0x400e9de5:0x3ffd19f0 0x400e8319:0x3ffd1a10 0x400ef4d3:0x3ffd1a40 0x400edf88:0x3ffd1a70 0x400edf93:0x3ffd1a90 0x400814b6:0x3ffd1ab0 0x400f7bc2:0x3ffd1ad0
[21:10:45]
[21:10:45]
[21:10:45]
[21:10:45]
[21:10:45]ELF file SHA256: 2bc66c482fdf826f
[21:10:45]
[21:10:45]E (5391) esp_core_dump_flash: Core dump flash config is corrupted! CRC=0x7bd5c66f instead of 0x0
[21:10:45]Rebooting...
[21:10:45]ets Jun  8 2016 00:22:57
[21:10:45]
[21:10:45]rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[21:10:45]configsip: 0, SPIWP:0xee
[21:10:45]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[21:10:45]mode:DIO, clock div:1
[21:10:45]load:0x3fff0000,len:392
[21:10:45]load:0x40078000,len:14204
[21:10:45]ho 0 tail 12 room 4
[21:10:45]load:0x40080400,len:3236
[21:10:45]entry 0x4008057c
[21:10:45]E (50) esp_core_dump_flasrcore dump partition found!
[21:10:45]E (50) esp_core_dump_flash: No core dump partition found!
[21:10:45]Initializing
[21:10:45]Operation mode (boot): 1
[21:10:45]E (12) SPIFFS: mount failed, -10025
[21:10:45]E (13) SPIFFS: mount failed, -10025
[21:10:45]ERROR while trying to open presets list file
[21:10:45]E (24) SPIFFS: mount failed, -10025
[21:10:45]E (25) SPIFFS: mount failed, -10025
[21:10:45]Stopping advertising keyboard
[21:10:45]Starting scan
[21:10:45]Operation mode: 1
[21:10:45]======= Entering APP mode =======
[21:10:45]Initialization done.
[21:10:47]Found Spark, connecting.
[21:10:47]Scan ended.
[21:10:48]Connected to: f7:eb:ed:0d:b5:3e
[21:10:48]Subscribing to service notifications of FFC2
[21:10:48]Notifications turned on
[21:10:48]Done with this device.
[21:10:48]BLE connection to Spark established.
[21:10:48]Changing to HW preset 1
[21:10:48]Guru Meditation Error: Core  0 panic'ed (LoadProhibited).  CRC=0x7bd5c66f instead of 0x0
[21:10:48]Rebooting...
[21:10:48]ets Jun  8 2016 00:22:57
[21:10:48]
[21:10:48]rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[21:10:48]configsip: 0, SPIWP:0xee
[21:10:48]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[21:10:48]mode:DIO, clock div:1
[21:10:48]load:0x3fff0000,len:392
[21:10:48]load:0x40078000,len:14204
[21:10:48]ho 0 tail 12 room 4
[21:10:48]load:0x40080400,len:3236
[21:10:48]entry 0x4008057c
[21:10:48]E (50) esp_core_dump_flasrcore dump partition found!
[21:10:48]E (50) esp_core_dump_flash: No core dump partition found!
[21:10:48]Initializing
[21:10:48]Operation mode (boot): 1
[21:10:48]E (12) SPIFFS: mount failed, -10025
[21:10:48]E (13) SPIFFS: mount failed, -10025
[21:10:48]ERROR while trying to open presets list file
[21:10:48]E (24) SPIFFS: mount failed, -10025
[21:10:48]E (25) SPIFFS: mount failed, -10025
[21:10:48]Stopping advertising keyboard
[21:10:48]Starting scan
[21:10:48]Operation mode: 1
[21:10:48]======= Entering APP mode =======
[21:10:48]Initialization done.
[21:10:51]Found Spark, connecting.
[21:10:51]Scan ended.
[21:10:51]Connected to: f7:eb:ed:0d:b5:3e
[21:10:51]Subscribing to service notifications of FFC2
[21:10:51]Notifications turned on
[21:10:51]Done with this device.
[21:10:51]BLE connection to Spark established.
[21:10:51]Changing to HW preset 1
[21:10:51]Guru Meditation Error: Core  0 panic'ed (LoadProhibited).  CRC=0x7bd5c66f instead of 0x0
[21:10:51]Rebooting...
[21:10:51]ets Jun  8 2016 00:22:57
[21:10:51]
[21:10:51]rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[21:10:51]configsip: 0, SPIWP:0xee
[21:10:51]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[21:10:51]mode:DIO, clock div:1
[21:10:51]load:0x3fff0000,len:392
[21:10:51]load:0x40078000,len:14204
[21:10:51]ho 0 tail 12 room 4
[21:10:51]load:0x40080400,len:3236
[21:10:51]entry 0x4008057c
[21:10:51]E (50) esp_core_dump_flasrcore dump partition found!
[21:10:51]E (50) esp_core_dump_flash: No core dump partition found!
[21:10:51]Initializing
[21:10:51]Operation mode (boot): 1
[21:10:51]E (12) SPIFFS: mount failed, -10025
[21:10:51]E (13) SPIFFS: mount failed, -10025
[21:10:51]ERROR while trying to open presets list file
[21:10:51]E (24) SPIFFS: mount failed, -10025
[21:10:51]E (25) SPIFFS: mount failed, -10025
[21:10:52]Stopping advertising keyboard
[21:10:52]Starting scan
[21:10:52]Operation mode: 1
[21:10:52]======= Entering APP mode =======
[21:10:52]Initialization done.
[21:10:53]Found Spark, connecting.
[21:10:53]Scan ended.
[21:10:54]Connected to: f7:eb:ed:0d:b5:3e
[21:10:54]Subscribing to service notifications of FFC2
[21:10:54]Notifications turned on
[21:10:54]Done with this device.
[21:10:54]BLE connection to Spark established.
[21:10:54]Changing to HW preset 1
[21:10:54]Guru Meditation Error: Core  0 panic'ed (LoadProhibited).  CRC=0x7bd5c66f instead of 0x0
[21:10:54]Rebooting...

@thrivewebdesign I think the interesting point is this one:
[21:10:48]E (12) SPIFFS: mount failed, -10025
[21:10:48]E (13) SPIFFS: mount failed, -10025
[21:10:48]ERROR while trying to open presets list file
[21:10:48]E (24) SPIFFS: mount failed, -10025
[21:10:48]E (25) SPIFFS: mount failed, -10025
Have you loaded the data folder to the Ignitron? Please check here for instructions.

I had previously used the release binary but have built from source today and flashed the firmware again. I can now connect to the spark GO if I turn on the amp then the ignitron then turn the amp off then on again. I can change presets etc ( its fantastic!! ) .  I am still unable to access the presets. Im a bit stumped as to what I'm doing incorrectly as the log from the upload seems ok.

Chip is ESP32-D0WDQ6 (revision v1.0)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: xx:xx:xx:xx:xx:xx
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 921600
Changed.
Configuring flash size...
Auto-detected Flash size: 4MB
Flash will be erased from 0x00210000 to 0x003effff...
Compressed 1966080 bytes to 26489...
Writing at 0x00210000... (50 %)
Writing at 0x00232ff5... (100 %)
Wrote 1966080 bytes (26489 compressed) at 0x00210000 in 9.8 seconds (effective 1605.3 kbit/s)...
Hash of data verified.
Leaving...
Hard resetting via RTS pin...

Does that mean that you can only switch the HW presets but cannot switch to the custom ones?
Can you please send another log of the Spark when you try to switch between presets?

I have managed to upload the preset data ( used platform io rather than Arduino )
I cant seem to establish a pattern for the connection issue, it looks as though the json being broadcast by the Spark go is sometimes not received ( or sent ) as you will see from the log below.
After the connection is established the ignitrON keeps changing the preset to number 1 ( you can audibly hear this if you drum the guitar )
Sometimes it connects first go others it may change to preset 1 - 5 times and connect other times it will just keep changing to preset 1.
Pressing the preset select button on the spark sometimes breaks this cycle. When this is occurring changing the presets on the ignitron does not seem to work.
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5828
entry 0x400806a8
Initializing
Operation mode (boot): 1
Last bank not full, filling with last preset to get bank complete
Last bank not full, filling with last preset to get bank complete
Stopping advertising keyboard
Starting scan
Operation mode: 1
======= Entering APP mode =======
Initialization done.
Found Spark, connecting.
Scan ended.
Connected to: xx:xx:xx:xx:xx:xx
Subscribing to service notifications of FFC2
Notifications turned on
Done with this device.
BLE connection to Spark established.

Found Spark, connecting.
Scan ended.
Connected to: f7:eb:ed:0d:b5:3e
Subscribing to service notifications of FFC2
Notifications turned on
Done with this device.
BLE connection to Spark established.
Changing to HW preset 1
Changing to HW preset 1
Changing to HW preset 1
Changing to HW preset 1
Changing to HW preset 1
Changing to HW preset 1
Changing to HW preset 1
Changing to HW preset 1
Changing to HW preset 1
Changing to HW preset 1
Changing to HW preset 1
Scan initiated
Found Spark, connecting.
Scan ended.
Reconnected client
Connected to: f7:eb:ed:0d:b5:3e
Subscribing to service notifications of FFC2
Notifications turned on
Done with this device.
BLE connection to Spark established.
Changing to HW preset 1
Scan initiated
Found Spark, connecting.
Scan ended.
Reconnected client
Connected to: f7:eb:ed:0d:b5:3e
Subscribing to service notifications of FFC2
Notifications turned on
Done with this device.
BLE connection to Spark established.
 Can you please go to Config_Definitions.h and remove the comment before #ifdef DEBUG, the rebuild and deploy.
If the Spark has switched successfully to HW preset 1, please also try to switch to a custom preset on a different bank.
Please post the logs here.

Rebooting...
ets Jun  8 2016 00:22:57
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5828
entry 0x400806a8
Initializing
Operation mode (boot): 1
Trying to read file list
Last bank not full, filling with last preset to get bank complete
Last bank not full, filling with last preset to get bank complete
Stopping advertising keyboard
Starting scan
Operation mode: 1
======= Entering APP mode =======
Initialization done.
Found Spark, connecting.
Scan ended.
Connected to: f7:eb:ed:0d:b5:3e
Subscribing to service notifications of FFC2
Notifications turned on
Done with this device.
BLE connection to Spark established.
Initial boot, setting preset to HW 1
Changing to HW preset 1
Clearing response buffer.
Sending block:
01FE000053FE1A000000000000000000F00101000138000000F7
Done with this command!
Getting current preset from Spark
Clearing response buffer.
Sending block:
01FE000053FE3C000000000000000000F0010101020100010000000000000000000000000000000000000000000000000000000000000000000000F7
Done with this command!
Received message via BT callback
Received data:
F00101000438F7
Received block with no header start, appending to previous (if present)
Acknowledgement for command 38
Received message via BT callback
Received data:
F001010703012012001901005924004237434346
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
453700362D443345342D00344137382D4234F7F0
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
01010A03010012011938342D4500443837364645
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
3310323542452F5374007564696F207472F7F001
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
013C0301001202196970
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
707944203323302E375900214465736372690070
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
74696F6E2066F7F00101330301001203196F7220
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
4100636F75737469630020507265736574042031
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
2869636F6EF7F00101220301001204192E706E67
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
654A42700000172E0062
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
6961732E6E6F0069736567617465F7F001012703
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
015812051943130011554A3D4F30470111514A3F
ReceE (5417) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
ived block with no header start, appending to previous (if presentE (5430) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
4870090211254A3F0000002E42F7F00101570301
Received block with no header start, appending to previous (if present)
Block not ready for processing,E (5461) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
E (5468) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
E (5476) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
E (5484) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
skipping further processing.
Received message via BT callback
Received data:
0012061942454F7000746963616C436F6C6D7043
Received block with no header start, appendE (5506) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
E (5513) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
E (5521) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
E (5528) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
ing to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
1300114A643F73261301
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
114AF7F00101470301501207193E046027060211
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
4A00000000012D446973746F720074696F6E5453
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
39F7F001012E03015812081942140011494A3E0E
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
6C6201115D4A3E5007210211594A3F3019440311
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
F7F00101660301081209
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
194A00000002002C466C61744100636F75737469
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
631B431500114A3F2BF7F001014B030150120A19
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
38060111454A3F0000000211494A3F0E76060311
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
676C6572431300114A6E3E535C3001114AF7F001
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
6B5A03114AF7F001011F030160120E193F123625
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Initial boot, setting preset to HW 1
Changing to HW preset 1
Clearing response buffer.
Sending block:
01FE000053FE1A000000000000000000F00101000138000000F7
Done with this command!
Getting current preset from Spark
Clearing response buffer.
Sending block:
01FE000053FE3C000000000000000000F0010101020100010000000000000000000000000000000000000000000000000000000000000000000000F7
Done with this command!
Received message via BT callback
Received data:
F00101000438F7
Received block with no header start, appending to previous (if present)
Acknowledgement for command 38
Received message via BT callback
Received data:
F001010703012012001901005924004237434346
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
453700362D443345342D00344137382D4234F7F0
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
01010A03010012011938342D4500443837364645
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
3310323542452F5374007564696F207472F7F001
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
013C0301001202196970
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
707944203323302E375900214465736372690070
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
74696F6E2066F7F00101330301001203196F7220
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
4100636F75737469630020507265736574042031
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
2869636F6EF7F00101220301001204192E706E67
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
654A42700000172E0062
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
6961732E6E6F0069736567617465F7F001012703
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
015812051943130011554A3D4F30470111514A3F
ReceE (7562) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
ived block with no header start, appending to previous (if presentE (7576) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
4870090211254A3F0000002E42F7F00101570301
Received block with no header start, appending to previous (if present)
Block not ready for processing,E (7606) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
E (7613) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
E (7621) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
E (7629) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
skipping further processing.
Received message via BT callback
Received data:
0012061942454F7000746963616C436F6C6D7043
Received block with no header start, appendiE (7651) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
E (7658) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
E (7666) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
E (7674) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
ng to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
1300114A643F73261301
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
114AF7F00101470301501207193E046027060211
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
4A00000000012D446973746F720074696F6E5453
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
39F7F001012E03015812081942140011494A3E0E
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
6C6201115D4A3E5007210211594A3F3019440311
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
F7F00101660301081209
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
194A00000002002C466C61744100636F75737469
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
631B431500114A3F2BF7F001014B030150120A19
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
38060111454A3F0000000211494A3F0E76060311
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
676C6572431300114A6E3E535C3001114AF7F001
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
6B5A03114AF7F001011F030160120E193F123625
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Initial boot, setting preset to HW 1
Changing to HW preset 1
Clearing response buffer.
Sending block:
01FE000053FE1A000000000000000000F00101000138000000F7
Done with this command!
Getting current preset from Spark
Clearing response buffer.
Sending block:
01FE000053FE3C000000000000000000F0010101020100010000000000000000000000000000000000000000000000000000000000000000000000F7
Done with this command!
Received message via BT callback
Received data:
F00101000438F7
Received block with no header start, appending to previous (if present)
Acknowledgement for command 38
Received message via BT callback
Received data:
F001010703012012001901005924004237434346
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
453700362D443345342D00344137382D4234F7F0
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
01010A03010012011938342D4500443837364645
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
3310323542452F5374007564696F207472F7F001
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
013C0301001202196970
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
707944203323302E375900214465736372690070
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
74696F6E2066F7F00101330301001203196F7220
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
4100636F75737469630020507265736574042031
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
2869636F6EF7F00101220301001204192E706E67
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
654A42700000172E0062
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
114AF7F00101470301501207193E046027060211
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
4A00000000012D446973746F720074696F6E5453
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
39F7F001012E03015812081942140011494A3E0E
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
6C6201115D4A3E5007210211594A3F3019440311
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
F7F00101660301081209
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
194A00000002002C466C61744100636F75737469
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
631B431500114A3F2BF7F001014B030150120A19
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
38060111454A3F0000000211494A3F0E76060311
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
414A3F3723720411F7F001017F030128120B194A
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
3F0000020027466C616E
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
676C6572431300114A6E3E535C3001114AF7F001
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
0131030120120C193F293D382602114A3F273961
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
012C44656C6179524065766572736542F7F00101
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
65030168120D191500114A6C3F1F237401114A62
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
3E48421002114A603F2D
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
6B5A03114AF7F001011F030160120E193F123625
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
1604114A3F000000012B626961732E7260657665
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
72624318F7F0010127030130120F1900114A3F31
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
00000001114A3E3075075102114A3F3000000003
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
114A3FF7F001010E0301
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Initial boot, setting preset to HW 1
Changing to HW preset 1
Clearing response buffer.
Sending block:
01FE000053FE1A000000000000000000F00101000138000000F7
Done with this command!
Getting current preset from Spark
Clearing response buffer.
Sending block:
01FE000053FE3C000000000000000000F0010101020100010000000000000000000000000000000000000000000000000000000000000000000000F7
Done with this command!
Received message via BT callback
Received data:
F00101000438F7
Received block with no header start, appending to previous (if present)
Acknowledgement for command 38
Received message via BT callback
Received data:
F001010703012012001901005924004237434346
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
453700362D443345342D00344137382D4234F7F0
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
01010A03010012011938342D4500443837364645
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
3310323542452F5374007564696F207472F7F001
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
013C0301001202196970
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
707944203323302E375900214465736372690070
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
74696F6E2066F7F00101330301001203196F7220
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
4100636F75737469630020507265736574042031
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
2869636F6EF7F00101220301001204192E706E67
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
654A42700000172E0062
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
6961732E6E6F0069736567617465F7F001012703
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
015812051943130011554A3D4F30470111514A3F
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
ReceiE (11912) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
ved data:
4870090211254A3F0000002E42F7F00101570301
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
0012061942454F7000746963616C436F6C6D7043
Received block with no header start, appending to pE (11949) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
E (11956) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
E (11964) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
revious (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
1300114A643F73261301
ReceivedE (11986) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
E (11994) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
E (12001) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
ReceE (12024) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
ived data:
114AF7F00101470301501207193E046027060211
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
4A00000000012D446973746F720074696F6E5453
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
39F7F001012E03015812081942140011494A3E0E
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
6C6201115D4A3E5007210211594A3F3019440311
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
F7F00101660301081209
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
194A00000002002C466C61744100636F75737469
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
631B431500114A3F2BF7F001014B030150120A19
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
38060111454A3F0000000211494A3F0E76060311
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
414A3F3723720411F7F001017F030128120B194A
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
676C6572431300114A6E3E535C3001114AF7F001
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
3E48421002114A603F2D
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
00000001114A3E3075075102114A3F3000000003
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Initial boot, setting preset to HW 1
Changing to HW preset 1
Clearing response buffer.
Sending block:
01FE000053FE1A000000000000000000F00101000138000000F7
Done with this command!
Getting current preset from Spark
Clearing response buffer.
Sending block:
01FE000053FE3C000000000000000000F0010101020100010000000000000000000000000000000000000000000000000000000000000000000000F7
Done with this command!
Received message via BT callback
Received data:
F00101000438F7
Received block with no header start, appending to previous (if present)
Acknowledgement for command 38
Received message via BT callback
Received data:
F001010703012012001901005924004237434346
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
453700362D443345342D00344137382D4234F7F0
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
01010A03010012011938342D4500443837364645
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
3310323542452F5374007564696F207472F7F001
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
013C0301001202196970
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
707944203323302E375900214465736372690070
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
74696F6E2066F7F00101330301001203196F7220
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
4100636F75737469630020507265736574042031
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
2869636F6EF7F00101220301001204192E706E67
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
654A42700000172E0062
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
6961732E6E6F0069736567617465F7F001012703
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
015812051943130011554A3D4F30470111514A3F
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
ReceiE (14050) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
ved data:
4870090211254A3F0000002E42F7F00101570301
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
0012061942454F7000746963616C436F6C6D7043
Received block with no header start, appending to pE (14086) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
E (14094) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
E (14101) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
revious (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
1300114A643F73261301
ReceivedE (14124) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
E (14131) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
E (14139) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
ReceE (14161) NimBLE: ble_hci_rx_acl failed to allocate ACL buffers; increase ACL_BUF_COUNT
ived data:
114AF7F00101470301501207193E046027060211
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
4A00000000012D446973746F720074696F6E5453
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
39F7F001012E03015812081942140011494A3E0E
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
6C6201115D4A3E5007210211594A3F3019440311
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
F7F00101660301081209
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
194A00000002002C466C61744100636F75737469
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
631B431500114A3F2BF7F001014B030150120A19
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
38060111454A3F0000000211494A3F0E76060311
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
414A3F3723720411F7F001017F030128120B194A
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
676C6572431300114A6E3E535C3001114AF7F001
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
3E48421002114A603F2D
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
00000001114A3E3075075102114A3F3000000003
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Initial boot, setting preset to HW 1
Changing to HW preset 1
Clearing response buffer.
Sending block:
01FE000053FE1A000000000000000000F00101000138000000F7
Done with this command!
Getting current preset from Spark
Clearing response buffer.
Sending block:
01FE000053FE3C000000000000000000F0010101020100010000000000000000000000000000000000000000000000000000000000000000000000F7
Done with this command!
Received message via BT callback
Received data:
F00101000438F7
Received block with no header start, appending to previous (if present)
Acknowledgement for command 38
Received message via BT callback
Received data:
F001010703012012001901005924004237434346
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
453700362D443345342D00344137382D4234F7F0
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
01010A03010012011938342D4500443837364645
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
3310323542452F5374007564696F207472F7F001
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
013C0301001202196970
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
707944203323302E375900214465736372690070
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
74696F6E2066F7F00101330301001203196F7220
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
4100636F75737469630020507265736574042031
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
2869636F6EF7F00101220301001204192E706E67
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
654A42700000172E0062
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
114AF7F00101470301501207193E046027060211
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
4A00000000012D446973746F720074696F6E5453
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
39F7F001012E03015812081942140011494A3E0E
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
6C6201115D4A3E5007210211594A3F3019440311
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
F7F00101660301081209
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
194A00000002002C466C61744100636F75737469
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
631B431500114A3F2BF7F001014B030150120A19
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
38060111454A3F0000000211494A3F0E76060311
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
414A3F3723720411F7F001017F030128120B194A
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
3F0000020027466C616E
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
676C6572431300114A6E3E535C3001114AF7F001
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
0131030120120C193F293D382602114A3F273961
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
012C44656C6179524065766572736542F7F00101
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
65030168120D191500114A6C3F1F237401114A62
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
3E48421002114A603F2D
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
6B5A03114AF7F001011F030160120E193F123625
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
1604114A3F000000012B626961732E7260657665
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
72624318F7F0010127030130120F1900114A3F31
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
00000001114A3E3075075102114A3F3000000003
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Received message via BT callback
Received data:
114A3FF7F001010E0301
Received block with no header start, appending to previous (if present)
Block not ready for processing, skipping further processing.
Initial boot, setting preset to HW 1
Changing to HW preset 1
Clearing response buffer.
Sending block:
01FE000053FE1A000000000000000000F00101000138000000F7
Done with this command!
Getting current preset from Spark
Clearing response buffer.
Sending block:
01FE000053FE3C000000000000000000F0010101020100010000000000000000000000000000000000000000000000000000000000000000000000F7
Done with this command!
Initial boot, setting preset to HW 1
Changing to HW preset 1
Clearing response buffer.
Sending block:
01FE000053FE1A000000000000000000F00101000138000000F7
Done with this command!
Getting current preset from Spark
Clearing response buffer.
Sending block:
01FE000053FE3C000000000000000000F0010101020100010000000000000000000000000000000000000000000000000000000000000000000000F7
Done with this command!
Initial boot, setting preset to HW 1
Changing to HW preset 1
Clearing response buffer.
Sending block:
01FE000053FE1A000000000000000000F00101000138000000F7
Done with this command!
Getting current preset from Spark
Clearing response buffer.
Sending block:
01FE000053FE3C000000000000000000F0010101020100010000000000000000000000000000000000000000000000000000000000000000000000F7
Done with this command!
---=== Turned off spark GO ===---
Scan initiated

Thanks for the logs. I have not seen this issue in this form before. What I have noticed is that communication with the Spark 40 is much more stable than with the GO, which could have to do with the difference in message sending I have seen. I think to increase stability on the BT connection, I would need some restructuring of the code. Until I have time to work on this, you could try to check out and build the branch 20240214_refactor_msg_processing, where I did some changes to improve stability around the GO communication. Note that this branch is in development/testing status. Please let me know if that works better for you.

@thrivewebdesign I have further worked on the code in the branch 20240214_refactor_msg_processing.
Messaging to the GO should be much more stable. However, some presets don't get properly updated, I am yet to find the reason. Can you please test by checking out the branch, building and deploying? This could also help me in further investigations on the stability.

@thrivewebdesign I have finally finished the refactoring on message processing and merged that back into the main branch. If you want, you can test it now. Please let me know if it works so we can close this issue

I will download build and test the evening and report back. Thank you so much for hard work.

@thrivewebdesign I did a few performance tweaks and code cleanup to make the code better readable. If you update your code to the latest from the main branch, you should have the final version for now.

@thrivewebdesign I fixed another bug, I have also built in the automatic switch between Spark 40 and Mini/GO messages (with/without header, message length). This should be it, I have tested it with my Spark 40 and the GO.

Thats wonderful, I managed to kill my only 38 pin ESP32 so currently hacking together a test board and will report back. Thanks again for all your hard work, very much appreciated.

Oh no, that is a pity! Hope you can find some replacement. Once you manage to test, please let me know if the issue is resolved for you.

@thrivewebdesign FYI, I did some more improvements to the code which should hopefully make the connection to Spark GO more stable. Did you have a chance yet to test?

Apologies for the delay in getting back to you, I've hobbled together a test rig on strip board and a smaller esp32 I had and it is working so much better thank you. The only issue I noticed was when imitating the tuner when holding the preset switching button ( not an issue for me )  Ill test the latest version and report back. FIY PCB's have arrived and i've started assembling in readiness for the new 38pin esp's arrival. Thanks again for creating such a fantastic project.

@thrivewebdesign thanks for testing and the kind words!
I am glad that it works for you now.
One question before I close this ticket, what is the issue when you hold the preset button? I just tested it and it changes to the Go tuner mode. When pressing again, it switches back to the preset it had before. Can you please provide more information on the behavior in your case?


ModuleNotFoundError: No module named 'transformers.hf_api'

I feel like I'm going crazy, but on two seperate distros (Xubuntu 22.04 and now PopOS 22.04) I'm running into an issue that I didn't have before reinstalling today.
If I install via pip install txtai[all] or [pipeline], after having gotten the latest version installed, it downgrades my version. When txtai is downgraded to 3.5.0, I run into this error:
    from txtai.embeddings import Embeddings
  File "/home/pathos/.local/lib/python3.10/site-packages/txtai/embeddings/__init__.py", line 5, in <module>
    from .base import Embeddings
  File "/home/pathos/.local/lib/python3.10/site-packages/txtai/embeddings/base.py", line 12, in <module>
    from ..scoring import ScoringFactory
  File "/home/pathos/.local/lib/python3.10/site-packages/txtai/scoring/__init__.py", line 5, in <module>
    from .base import Scoring
  File "/home/pathos/.local/lib/python3.10/site-packages/txtai/scoring/base.py", line 10, in <module>
    from ..pipeline.tokenizer import Tokenizer
  File "/home/pathos/.local/lib/python3.10/site-packages/txtai/pipeline/__init__.py", line 20, in <module>
    from .translation import Translation
  File "/home/pathos/.local/lib/python3.10/site-packages/txtai/pipeline/translation.py", line 15, in <module>
    from transformers.hf_api import HfApi
ModuleNotFoundError: No module named 'transformers.hf_api'

And if I don't install this, and install the latest version with pip install git+https://github.com/neuml/txtai or by git clone and pip install ., this issue is fixed and I can run most of the txtai. HOWEVER, then when trying to use Textractor, I run into the follow error:
ImportError: Textractor pipeline is not available - install "pipeline" extra to enable

Which, going back to the beginning, if I install the pipeline extra, 4.5.0 gets uninstalled and 3.5.0 gets installed, and then the first issue crops up that I am unsure how to fix, because reinstalling transformers has done absolutely nothing on both distros now.
Also on the side, before reinstalling because of a bugged install(I tried to update PopOS 21.04 to 22.04 and I think it failed somewhere along the line for some reason, because it was very unstable afterwards and eventually failed entirely this morning.), it was working fantastically and I must say this is an incredible package.
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 510.68.02    Driver Version: 510.68.02    CUDA Version: 11.6     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ...  Off  | 00000000:2D:00.0  On |                  N/A |
|  0%   53C    P0    55W / 260W |   1259MiB / 11264MiB |      5%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

Python 3.10.4

After going through installing each of the dependencies one by one, I found that in Python 3.10.4 onnx, onnxruntime are incompatible at this time. And maybe fasttext. I had to fix it, but I can't remember why. But in the end, I noticed that my deployment server could still run it, and the only difference was Python 3.10.4 (The transformers issue also went away when running 3.5.0 instead of the latest version as well. 3.10.4 seems to break both the pypi version of txtai and the repo version for seperate reasons.)

Thank you for researching this further. You definitely do not want to use txtai 3.5, it's really out of date at this point.
onnx and onnxruntime both don't have Python 3.10 wheels on PyPI. onnx has a source distribution and can be built with the right OS deps installed. onnxruntime does not. This is an open issue as referenced below:
https://github.com/microsoft/onnxruntime/issues/9782
https://github.com/microsoft/onnxruntime/issues/11117
https://github.com/microsoft/onnxruntime/issues/11332
Assuming you don't need ONNX support, as a workaround you can do this:
pip install txtai[pipeline]
pip install txtai --upgrade

That will do what you had previously but then upgrade txtai back to the latest version. If Python 3.10.x isn't that important, you can run with Python 3.9 and everything will work.
Alternatively you can run pip install txtai and then manually install the packages you need from the pipeline extras list.
extras["pipeline"] = [
    "beautifulsoup4>=4.9.3",
    "fasttext>=0.9.2",
    "imagehash>=4.2.1",
    "nltk>=3.5",
    "onnx>=1.10.1",
    "onnxmltools>=1.9.1",
    "onnxruntime>=1.8.1",
    "pandas>=1.1.0",
    "pillow>=9.0.1",
    "sentencepiece>=0.1.91",
    "soundfile>=0.10.3.post1",
    "tika>=1.24",
    "timm>=0.4.12",
]

The onnxruntime project says this will be resolved with 1.12 but no date is set on that.

[ ]

This issue has been resolved upstream with onnxruntime v1.12

Hi All,
I crashed with the same problem on Ubuntu 22.04 (patched) in venv
$ python3 --version
Python 3.10.12
$ pip --version
pip 24.0 from ~/Projects/Python/txtai/lib/python3.10/site-packages/pip (python 3.10)

then I tried:
pip install txtai[pipeline]
pip install txtai[all]

always crashing with the same error:
Collecting fasttext>=0.9.2 (from txtai[all])
  Using cached fasttext-0.9.2.tar.gz (68 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [25 lines of output]
      /Projects/Python/txtai/bin/python3: No module named pip
      Traceback (most recent call last):
        File "<string>", line 38, in __init__
      ModuleNotFoundError: No module named 'pybind11'

      During handling of the above exception, another exception occurred:

      Traceback (most recent call last):
        File "/Projects/Python/txtai/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/Projects/Python/txtai/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
        File "/Projects/Python/txtai/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel
          return hook(config_settings)
        File "/tmp/pip-build-env-ehfcvlx_/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 325, in get_requires_for_build_wheel
          return self._get_build_requires(config_settings, requirements=['wheel'])
        File "/tmp/pip-build-env-ehfcvlx_/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 295, in _get_build_requires
          self.run_setup()
        File "/tmp/pip-build-env-ehfcvlx_/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 487, in run_setup
          super().run_setup(setup_script=setup_script)
        File "/tmp/pip-build-env-ehfcvlx_/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 311, in run_setup
          exec(code, locals())
        File "<string>", line 72, in <module>
        File "<string>", line 41, in __init__
      RuntimeError: pybind11 install failed.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

I'll appreciate any help. Thanks


Fixed bug where spinbox would not update to it's actual value after non-numeric input

The issue is as follows:
After input of a non-numeric value into the line edit of a spinbox, the spinbax value would not update consistently:

The sequence of events:

Input a numeric value (in this case, 1)
Input string value.
The value (the white number in the label below) does not update... but the line edit no longer reflects the actual value of the spinbox. It shows what the user input, not what the underlying value is.
If the random jargon string is put after the numeric value, the spinbox resets to correctly display it's actual numeric value.
If it is put before, it does not update.

The behaviour is now consistent, as below. Essentially, if the spinbox is for float or integer values only, why allow string values?

@akien-mga this is a small change, could you please review or assign reviewer? Thanks

Thanks!

Cherry-picked for 3.2.4.


IC-1857: Hide intervention details until service categories are selected

What does this pull request do?
Hides service category related details section for cohort referrals until user has selected them

What is the intent behind these changes?
Ensure that the page doesn't show incomplete sections

I'm a bit out of touch here -- could we have a before/after screenshot, if that makes sense, please?

Before:

After:
The screenshot in the main comment


Fixed pre-release wasm32-wasip(\d) targets not enabling wasi compile flags in bundled mode.

The wasm32-wasi target is being deprecated in favor of pre-release targets like wasm32-wasip(\d).
This instead matches the prefix wasi target, so any future pre-releases will probably, maybe, work out of the box.

wasm32-wasip1-threads may need a more complicated solution, but this at least works for wasm32-wasip1 and wasm32-wasip2.

@thomcc If possible, could you please help me validate this PR (because I know nothing about wasm) ?

As a note on this, wasm32-wasi was supported previously, that target was renamed to wasm32-wasip1, which is what caused the build issue. The target itself is the same to my knowledge.
For that build target at least, this would be identical. There is p2 on nightly, but my goal here was getting the renamed version of p1 building.

Sorry for the delay.
Looks like https://github.com/gyscos/zstd-rs/commit/fc3a73100b6d3f2ff6dd3da0ff14dd9185ba02f0#diff-d10afeb74f1c422688106d5e75cd08ac2ac0328ef71bb829a5f127f1a105e1f6R138


Change to gpio char driver

Propose to go for char driver instead of sys-fs.
More info here
https://github.com/rust-embedded/gpio-cdev

Seems logical, the gpio-cdev README even says that sysfs will be removed next year.

This API, stabilized with Linux v4.4, deprecates the legacy sysfs interface to GPIOs that is planned to be removed from the upstream kernel after year 2020 (which is coming up quickly).


Adding support for s390x and ppc64le

This PR adds support for s390x and ppc64le architectures for Linux.
Testing was done and verified on #92
Closes #92
@rinchsan Let me know if you need anything else to merge this PR. After merging, are you able to cut a new release of the package?

@rinchsan It looks like all tested passed without issue except the lint. Looking at the errors it seem to be mostly surrounding the tests. I do not think my PR caused the linting to fail.

@james-crowley I don't understand why lint fails, but I'm also sure that it is  not caused by your PR.
And your changes look good to me, I'll approve and merge this PR.
Thank you for your contribution!
I'll fix lint issues after merging this PR, and I will release new version of gosimports including this change soon.

@rinchsan No problem! Thanks for the quick response! I can't wait to get the new packages cut so I can pull them into my project.


2024.8.12 utc+4 hosts block failed

I import all hosts manualy in c:\windows\system32\drivers\etc\host from https://a.dove.isdumb.one/list.txt. Unfortunately, it still prompt popup. Only acrobat installed on this computer, no AGM at all. Is there any new check ip address missing?

I choose use hosts to block. I don't think that is a must to use other software to achieve the goal. Windows hosts will do the same thing too.

I want to help. But I‘m not tech guy. I don't know how to use  Fiddler / Charles Proxy something like that. Is there a tutorial doc for that?


Make StreamConnection Closeable

Consider making StreamConnection auto closeable in a try-with-resources statement by having it implement Closeable.

Interesting, is this the expected patch for this?
diff --git a/stream-parent/stream-core/src/main/java/org/interledger/stream/StreamConnection.java b/stream-parent/stream-core/src/main/java/org/interledger/stream/StreamConnection.java
index 2f0af0c..54f95ac 100644
--- a/stream-parent/stream-core/src/main/java/org/interledger/stream/StreamConnection.java
+++ b/stream-parent/stream-core/src/main/java/org/interledger/stream/StreamConnection.java
@@ -6,6 +6,8 @@ import org.interledger.core.SharedSecret;
 import com.google.common.annotations.VisibleForTesting;
 import com.google.common.primitives.UnsignedLong;

+import java.io.Closeable;
+import java.io.IOException;
 import java.time.Instant;
 import java.util.Objects;
 import java.util.StringJoiner;
@@ -18,7 +20,7 @@ import java.util.concurrent.atomic.AtomicReference;
  *
Any given Connection in a JVM manages a unique sequence id that can be incremented for each Stream Packet sent
  * over the connection.

  */
-public class StreamConnection {
+public class StreamConnection implements Closeable {

   // NOTE: Integer.MAX_VALUE is 1 less than what we want for our Max per IL-RFC-29.
   public static final UnsignedLong MAX_FRAMES_PER_CONNECTION =
@@ -180,6 +182,11 @@ public class StreamConnection {
         .toString();
   }

+  @Override
+  public void close() throws IOException {
+    this.closeConnection();
+  }
+
   /**
    * Valid states for a {@link StreamConnection}. A StreamConnection begins life in the {@link #AVAILABLE} state. Once
    * the first sequence is emitted, the Connection transitions into the {@link #OPEN} state. If a Connection is closed,


[9.x] Prevent $mailer being reset when testing mailables that implement ShouldQueue

class Signup extends Mailable implements ShouldQueue
{
    // snip
}

Mail::mailer('mail-connection')
<EMAIL_ADDRESS>    ->send(new Signup());

public function send_signup_using_correct_mailer()
{
    Mail::fake();

    // snip

    Mail::assertQueued(Signup::class, function ($mail) {
        return $mail->mailer == 'mail-connection'; // FAILS: It is actually NULL
    });
}

When calling send(), the $mailer is set on the Mailable instance, then immediately reset to null on the MailFake (which it should do).
The problem occurs when the Mailable implements ShouldQueue. After the $mailer property has been reset, the queue() method then sets the $mailer again on the Mailable, but this time it is now NULL.
This change fixes that.

Heya thanks. All bugfixes should target 8.x so please send this to 8.x


Supporting Arabic Language

Hello
I noticed that the some analytics features and options only available for English not supported other languages.
such as Call Analytics Summary, Loudness/Sentiment.
you can find screenshots attached

while empty results in Arabic

Yes, please see https://docs.aws.amazon.com/transcribe/latest/dg/supported-languages.html for supported languages / features matrix. Thanks.


Logging on Azure

Any progress on this now that RTM is out?

@marchy The publish-iis tooling will create the correct log path in your web.config for Azure App's LogFiles folder.
https://github.com/aspnet/IISIntegration/blob/dev/src/Microsoft.AspNetCore.Server.IISIntegration.Tools/WebConfigTransform.cs#L88
https://docs.asp.net/en/latest/publishing/iis.html#publish-iis-tool

dup of #1673


Bug/deprecated

Refactored path, updated deprecated dependencies

 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.


Revert "excluding minikube page from main nav"

Reverts layer5io/meshery#153

Thanks for this @anandrkskd. Changing this particular line won't fix our broken link, per say. After you review #157, let's close this PR (#156) in lieu of #157.
This PR (#156) is good for practicing signing commits, though. Review last week's meeting minutes for an alias in .gitconfig that might serve you well. Or, if you're using VS Code, you might enable this option -

@anandrkskd it looks like you got your commits signed-off in this PR. Cool. I'll go ahead and close the PR now.


feedback on PowerShell env setup, clarified env vs. ssh

Changes

explicitly added PowerShell env command, and also linked to the command reference

clarified that using docker-machine env vs. docker-machine ssh are two ways of getting access to the machines, and you can use one or the other method (or both) to work through the tutorial steps

Reviewers
@JimGalasyn  I'll probably merge this before you see it, but wanted to tag you on it. Feel free to submit more comments if it still isn't accurate or needs improvement. Thanks for the feedback.
Signed-off-by: Victoria Bialas<EMAIL_ADDRESS>

LGTM


[WIP] Warn if routes are unreachable

This is a first pass at #1923, with thanks to @knowbody and @grabbou for their help so far.

Ouch - there's no better way than to manually check all ways routes might be bad?

@taion I was thinking about the same thing. not sure if we want to loop through all of the routes just to display the warning message

Yeah, I was going to ask that too. I'm not sure if there's a better way or not - obviously very new to this code base !

maybe we could do something like a DEBUG mode and do variety of checks/validation for people, something for development only?

The approach I would take would be to iterate through all leaf routes, generate the path, route to the path, then verify that we have the expected rendered routes.
Not sure we'd want to check this at run time though. Probably only in debug mode.

@taion :+1:

Hmm, since we support lazy route config I'm not sure how useful this is as a part of the library, maybe this is better as a tool outside of the project that you throw at your route config?

That's definitely an option. Alternatively, we could offer some sort of helper utility for automated testing that does what I suggested above, that users can incorporate into their own test suites.

I like that idea better. It's a development-only issue, so it should be provided as a development-only feature. Another option is to hide it behind a NODE_ENV flag, but that seems more prescriptive and opinionated.

I'm going to close this PR for now, because I don't think this is the direction we want to take for validating route config. Let's move discussion back to #1923 as needed.


Order t-shirts for devcon and retreat

Thoughts?

Thoughts on 2?

Thoughts on 3?

3 all the way 😄

Maybe we could make the 3⃣ logo larger?

gradient in our color scheme - take 4 (cc @oed)

@michaelsena I liked that the previous one blended more colors 🙂

Since this shirt is for devcon 4 (not devcon 3 as on the shirt in the picture;) ) It would be cool if we followed their color gradient: https://devcon4.ethereum.org/

Maybe even do a white shirt to completely follow their color scheme?

Okay, so here are all the options 👍

I prefer 1 over 3. 2 is on the back right?
<3 Deva
Haight is also nice :)

Ok, yeah that makes sense I guess.
Not sure which one I like the most of the deva vs deva on haight 🙂

Like them all. Deva on Haight and BoxCon are my favorites

Like any of them, just prefer a black shirt, hate white ones

I guess we could do both :)

Yeah I'll construct an order of our favorites and repost here before I place, so everyone can make sure they approve.

I'll wear any shirt we make, I ll just wear a black one more ❤

Final Draft:

@oznekenzo would love your input here too :heart:


Possible enhancements in first query

Describe This Problem
The speed of first query in ceresdb with oss is acceptable now, but more enhancements can still be done.
Proposal

[x] Make mergeIterator initializing concurrently
#466
[x] Make pulling sst from sst concurrently
[ ] Get data after pulling from remote storage immediately rather than waiting until it is written to disk cache

Additional Context
No response

There are several TODO in disk_cache.rs now, fix them would address your second proposal.

https://github.com/CeresDB/ceresdb/blob/505b9aca71ccc1ae0f120ef655509b85bfa89fce/components/object_store/src/disk_cache.rs#L132
https://github.com/CeresDB/ceresdb/blob/505b9aca71ccc1ae0f120ef655509b85bfa89fce/components/object_store/src/disk_cache.rs#L175

Closing since no obvious work need to be done now.


V2 - Update rate spread endpoint

The rate spread API wasn't moved over in v2, we still need to use the v1 endpoint.
Endpoint: https://ffiec-api.cfpb.gov/public/rateSpread
Check digit is ok, rate spread only.

Closed by #183


feat(model): initial pass at dealing with unknown enum variants

Reworking enums to have unknown variants to handle discord adding new api features.
Goal: not losing any payloads whenever discord adds something new, while keeping the type safety the enums provide since people depend on that.
This is an initial WIP draft to get discussion going on how the final implementation should look, but is fully functional.
Left to do on this:

[ ] standardize serialization and deserialization tests. they where all over the place, some check serde tokens, others just conversions without serde. We need to decide what kind of test general model serializations and deserializations should have
[ ] figure out a better solution for interactions, possibly by splitting it into 2 enums (a seperate one used for getting the command list over http, and one for the gateway interaction itself. Where dropping unknown interaction types might be slightly acceptable, since we can't do meaningful deserialization with the current models. Or flattening the entire interaction struct like was done with channels recently. Needs more consideration
[ ] Some models are also used as outgoing http payloads. We need to decide if we want to allow sending payloads with these unknown variants or error on them. Allowing unknowns can be useful in allowing people to leverage new options without a library upgrade. But if this different option also needs another field set the library won't be able to do it, nor can we ensure the value is valid. For the creation of application commands this however wasn't an option due to our custom serializer.

Thanks, for the formatting i'm aware there is probably a lot more that needs fixing. i chose to not fix them yet for this draft because the design of this isn't fully done yet, and i'm currently looking for feedback on how it should look/work in the end

standardize serialization and deserialization tests. they where all over the place, some check serde tokens, others just conversions without serde. We need to decide what kind of test general model serializations and deserializations should have

We don't really need to test the tokens, we're essentially testing serde at that point. We should test our own conversion implementations.

figure out a better solution for interactions, possibly by splitting it into 2 enums (a seperate one used for getting the command list over http, and one for the gateway interaction itself. Where dropping unknown interaction types might be slightly acceptable, since we can't do meaningful deserialization with the current models. Or flattening the entire interaction struct like was done with channels recently. Needs more consideration

I believe we're in the long-term process of separating types between their incoming and outgoing variants. I am in favor of more flattening in general but I don't believe it's in the scope of this PR.

Some models are also used as outgoing http payloads. We need to decide if we want to allow sending payloads with these unknown variants or error on them. Allowing unknowns can be useful in allowing people to leverage new options without a library upgrade. But if this different option also needs another field set the library won't be able to do it, nor can we ensure the value is valid. For the creation of application commands this however wasn't an option due to our custom serializer.

I think if people want to use cutting edge new API features that we don't support they can use manual HTTP request bodies. Type flattening may also aid in this, but again out of scope. We may need to place some sort of priority on investigating the role flattening would have for us in general.

Do we still have uses of the serde_repr dependency after this?

Yes, several gateway and interaction structs still use these.

We don't really need to test the tokens, we're essentially testing serde at that point. We should test our own conversion implementations.

i'll replace the relevant tests with just testing the conversions without serde then

I believe we're in the long-term process of separating types between their incoming and outgoing variants. I am in favor of more flattening in general but I don't believe it's in the scope of this PR.

Agreed, i think we can live with it being not perfect here in what data we give when it's unknown and then clean up these few last spots when things are flattened

This does need further work, and based on some discussion in Discord, there seems to be a path forward. We should bracket any work on unknown interaction variants for now, in order to solve that problem more correctly at a later date. Also, we should try to build on whatever existing tests there are for the affected types, and follow up later to make them more consistent with each other and more correct. Lastly, I'll be making a quick PR to add the Forum channel type, as a stopgap in a minor release, which will come before a) this PR and b) Erk's work on the entire forum feature later on.

Looks good, should we mention in CONTRIBUTING.md that enums must have an Unknown variant where applicable?


port dotnet DialogTestClient DialogContext changes

Fixes #1891
Specific Changes

Expose public dialogContext getter, add private _dialogContext with initial value of null.
Minor linting fixes

Testing
Added a new test for inspectingDialogTestClient.dialogContext.

Pull Request Test Coverage Report for Build 113901

8 of 8 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 81.791%

Totals

Change from base Build 113781:
0.002%

Covered Lines:
9327

Relevant Lines:
10991

💛  - Coveralls


Return GATT_SUCCESS when Descriptor is read

Existing code was returning GATT_FAILURE for all code paths in onDescriptorReadRequest - if the config descriptor matches and is valid, GATT_SUCCESS should be returned along with the correct value for ENABLE/DISABLE notification

Got the same issue when i tested it https://github.com/androidthings/sample-bluetooth-le-gattserver/pull/3

Thanks for catching this!

#3 fixed the same issue.. anyways thanks for fixing this finally

@hammmmy Yes, but #3 also included several other changes unrelated to the issue described. In the future, I would recommend splitting unrelated changes into separate PRs.


The execute method doesn't work

I'm trying to connect Memcached server on localhost:11211 and run the get command.
$prompt = 'OK';
$promptError = 'ERROR';
$lineEnding = "\r\n";
$this->telnet->connect("localhost:11211", $prompt, $promptError, $lineEnding);
$resp = $this->telnet->execute("get some_key");
var_dump($resp->getResponseText());

I run this code via phpunit from PowerShell but it doesnt do anything. No error shown but also no any other output. And the console looks like it still executing.

The same result if I try run any other Memcached command. However these commands works fine from Powershell telnet and from Putty.
Any thoughts?

Hi there. Are you sure that your memcached instance is prompting with OK?
I've just run this slightly modified version of your code:
$telnet = Graze\TelnetClient\TelnetClient::factory();
$prompt = '';
$promptError = 'ERROR';
$lineEnding = "\r\n";
$telnet->connect("localhost:11211", $prompt, $promptError, $lineEnding);
$resp = $telnet->execute("get some_key");
var_dump($resp->getResponseText());

And got this result:
root@414973d37ab1:/srv# php telnet-test.php
/srv/telnet-test.php:12:
string(3) "END"

This matches the behaviour when using a standalone telnet client:
root@414973d37ab1:/srv# telnet <IP_ADDRESS> 11211
Trying <IP_ADDRESS>...
Connected to <IP_ADDRESS>.
Escape character is '^]'.
get some_key
END

When I ran it with a prompt of OK it sat there doing nothing because it was waiting for OK to appear.

@biggianteye Now I see that I was using it wrong. But at the moment I can't test it. We can just close the issue. Thanks


Permanent search bar

I only found out today that there is a search option. How about making it better (=permanent) visible? That really helps people getting to their goal quicker. Here's an example of how did they that: https://componently.github.io/componently/.

I think this is due to us using the "old" GitBook version 2.* instead of the "new" Gitbook, which had a problem with chapter numbering at the time. Will try updating, and see if anything breaks/improves.

Is this still relevant? At the moment, the search box is still not permanently visible on our page, but that appears to be mostly because our table of contents is too large to fit in the side bar. The example has a much shorter table of contents.

Reaction from @tbkkr by email:

Misschien even kijken naar V2 van Gitbook, want draaien wij niet nog steeds de oude versie? Volgens mij is de search function wat aangepast in nieuwe versie van gitbook.
wb de ToC links: die moet misschien wat korter, bv:
2.1 > onderbrengen bij 2.7
2.8 en 2.9 ook ondebrengen bij 2.7 wellicht Bij IP & Licences zou ik vooral Licences neerzetten.
2.3 en 2.4 samen
2.6 en 2.7 samen
3.1 > kan weg?

The search bar is indeed part of newer versions, but the problem is that chapter numbering is ugly in newer versions of gitbook, see e.g. https://github.com/GitbookIO/gitbook/issues/1301. If we want the search bar, we should disable numbering the chapters in the table of contents or wait for gitbook to fix the issue.

I discussed with @lodekulik and he advised that it is fine to drop the chapter numbers as is the default in newer gitbook versions. Therefore I think we can safely upgrade to the latest version.

I have switched to the version 3 builder, which should solve this issue.

Except that the search bar still disappears if you scroll down too far. So we need to reduce the number of chapters.

This discussion is outdated. We no longer use GitBook, but docsify. I have briefly looked into how to fix this issue, but cannot find a default option, even though here it is suggested that placing the search bar elsewhere is possible, but not without significant effort and the maintainability issues that brings.
If someone wants to open a PR to make the search bar permanently visible (and retains all other functionality), most welcome! This issue, in the meantime, can be closed.


Unhandled exception when Render page

Hey.
Sorry for bad english :)
When you try to obtain images for a plurality of files, the library may suddenly shut down, throwing out of the program without showing any error.
Add a reference to the assembly. specify a list of files, units 500 and starts processing. To play you need to run a cycle, in which the extracted image of the page for each PDF file.
Sometimes processed 10, sometimes 34 pieces, that is, each time his; the list does not change the files.
`Dim flist As New List(Of String)
flist.AddRange(Directory.GetFiles("x:", ".pdf", SearchOption.AllDirectories).ToList)
flist.AddRange(Directory.GetFiles("z:", ".pdf", SearchOption.AllDirectories).ToList)
For Each ff In flist.Where(Function(x) System.IO.Path.GetFileNameWithoutExtension(x).StartsWith(".") = False)
File.AppendAllText("C:\fx\xrenderLog.txt", ff & vbCrLf)
Try
Using doc As PdfiumViewer.PdfDocument = PdfiumViewer.PdfDocument.Load(ff)
                Dim ts = Now
                For n = 0 To doc.PageCount
                    Dim img = doc.Render(n, 90, 110, 72, 72, PdfiumViewer.PdfRenderFlags.None)
                    img.Save("C:\fx\very\" & n & ".png", System.Drawing.Imaging.ImageFormat.Jpeg)
                Next
                Dim xs As TimeSpan = Now - ts
                File.AppendAllText("C:\fx\renderLog.txt", doc.PageCount & vbTab & xs.TotalSeconds & vbTab & ff & vbCrLf)
            End Using

        Catch ex As Exception
            File.AppendAllText("C:\fx\render.txt", ff & vbTab & ex.ToString)
        End Try
    Next

    Dim k = 1

`

Hey @Jodanas.
Don't forget to correctly dispose of your rendered images:
Using img = doc.Render(n, 90, 110, 72, 72, PdfiumViewer.PdfRenderFlags.None)
    img.Save("C:\fx\very\" & n & ".png", System.Drawing.Imaging.ImageFormat.Jpeg)
End Using

ok, thx:)
This is sample, only for test.

Did this resolve your problem?

Yes, thank you, work, processed all files.
I do not quite understand why the fall when using existing image...

Each time PdfDocument.Render() is called it constructs a new image. This image (reference-object) is returned and a reference to it stored in your local img variable. This variable falls out-of-scope at the Next statement. With the image now out-of-scope (has no more references to it) the garbage collector will eventually collect this object and release any managed memory.
The System.Drawing namespace is largely a wrapper around GDI+. This unmanaged API allocates memory and other resources which cannot be freed by the .NET managed garbage collector.
GDI+ has limits that can easily become relevant when objects are not disposed of correctly and cause crashes, freezing or other unexpected behaviour.
Thus the IDisposable interface is implemented on many of the objects in this namespace and Dispose() methods made available to free any unmanaged resources. This means you could technically write:
Dim img = doc.Render(n, 90, 110, 72, 72, PdfiumViewer.PdfRenderFlags.None)
img.Save("C:\fx\very\" & n & ".png", System.Drawing.Imaging.ImageFormat.Jpeg)
img.Dispose()

However the Using statement is used to provide a guarantee that the Dispose() method will be called even if an exception is thrown. So in a very simplified sense, the Using statement is similar to:
Try
    Dim img = doc.Render(n, 90, 110, 72, 72, PdfiumViewer.PdfRenderFlags.None)
    img.Save("C:\fx\very\" & n & ".png", System.Drawing.Imaging.ImageFormat.Jpeg)
Finally
    img.Dispose()
End Try

This is much nicer:
Using img = doc.Render(n, 90, 110, 72, 72, PdfiumViewer.PdfRenderFlags.None)
    img.Save("C:\fx\very\" & n & ".png", System.Drawing.Imaging.ImageFormat.Jpeg)
End Using

More information:

GDI+ Limitations
Using Statement
Implementing a Dispose Method

Gary, you're the best, thank you)


Give us options to install extensions

Describe your suggested feature
Give us options to install extensions because searching in all extension consumes a lot of data so please give us options to install extensions and use the extension that we like
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with a source, I should be opening an issue in the sources repository.
[X] I have updated the app to version 1.1.13.
[X] I will fill out all of the requested information in this form.

You can pin the sources you want to use and turn off search all sources in global settings and the app would only search pinned sources.

Give us options to install extensions because searching in all extension consumes a lot of data so please give us options to install extensions and use the extension that we like

This isn't possible as there's no way to implement external sources in React Native. There's already an open issue (#166) for it.


Missing Information/A small update suggestion

I would like to make a small suggestion for docker documentation below:
https://docs.microsoft.com/en-us/azure/app-service/configure-custom-container?pivots=container-linux#docker-compose-options
In the limitation of docker compose, there is no mention of VNet integration which is not supported. When I read through the doc, I though VNet integration is supported but on further research I found the below VNet doc which states that VNet integration is not supported for docker compose:
https://docs.microsoft.com/en-us/azure/app-service/overview-vnet-integration#troubleshooting
Could you please mention this VNet limitation in the docker document as well so that anyone who reads the docker documentation will know before-hand that VNet is not supported for docker compose.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1d385179-7730-3b99-aff6-75491deb070a
Version Independent ID: 7da429ea-5421-9d99-3e7c-af1b3fee5ca8
Content: Configure a custom container - Azure App Service
Content Source: articles/app-service/configure-custom-container.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

@v-ljeswani Thanks for the feedback! We are currently investigating and will update you shortly.

@v-ljeswani Thanks again for the feedback! The PR has been raised once reviewed by author of the doc will be visible.
https://github.com/MicrosoftDocs/azure-docs-pr/pull/208088
We will now proceed to close this thread. If there are further questions regarding this matter, please let us know.


Adding a function to override the ssl default roots path.

Fixes the first part of #4834.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

had to close because of git f***up during the outage today. Please see #4934.


mix.setResourceRoot is attached to mix.setPublicPath

hi, first, thanks for the amazing work.
Now the issue/question.
I updated to the latest version (0.8.0) and I'm trying to use the mix.setResourceRoot method but, I realized that I also need to set the mix.setPublicPath in order to work properly.

It works properly if I do like this
mix.setPublicPath('skin/frontend/rwd/smoke');
mix.setResourceRoot('skin/frontend/rwd/smoke');

I don't need to change my public path, just the images destination path.
Thanks ;)

I have tried the same way but i can not get fonts in public/ directory... :(

This was resolved a couple months ago.


Improving the responsiveness of the laughing therapy page.

The are clashing into one another on the laughing therapy videos section.
The about part on laughing therapy page needs improvement in responsiveness.
The top of the header has padding which can be seen through navbar and the padding is irrelevent.
The menu is shifted towards left when u open it.
The hover one video causes other to disappear.
There is sidescrolling on the page.
Can integrate a api to get memes rather than the same old memes.
Improvement on the hover on videos can be done.

want to work on this issue @Susmita-Dey @myhacktech


Fixes gh-2503

A trivial fix
https://github.com/spring-cloud/spring-cloud-netflix/issues/2503

@spencergibb Would like to, however your current tests framework doesn't provide a mocking around certificates, etc.
The current tests around this option are very minimal:
	@Test
	public void validationOfSslHostnamesCanBeDisabledViaProperty() {
		addEnvironment(this.context, "zuul.sslHostnameValidationEnabled=false");
		setupContext();
		assertFalse("Hostname verification should be disabled via property",
				getFilter().isSslHostnameValidationEnabled());
	}

Also, It's the first time I fork and contribute in this repo. I haven't managed to get it compiled yet. Any guideline available for contributors for making the project compile with intellij?

Please Note that hostname validation is therefore disable by default. And it's even worth as this option is not only disabling the hostname validation but also SSL (see #2505).
Therefore, this should be considered as a security issue, a severe one IMHO.

If you are interested in reproducing this, I created a sample project https://github.com/qcastel/forgerockmtlswithzuul which was originally to investigate on testing mutual TLS with a zuul proxy in front of a micro-service.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #2504   +/-   ##
=======================================
  Coverage   65.65%   65.65%
=======================================
  Files         207      207
  Lines        7644     7644
  Branches      943      944    +1
=======================================
  Hits         5019     5019
  Misses       2267     2267
  Partials      358      358

Impacted Files
Coverage Δ

...ix/zuul/filters/route/SimpleHostRoutingFilter.java
89.54% <ø> (ø)
: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 4e8d588...d804d88. Read the comment docs.

I dont think you need to do to that extent.  I think we just need to vaildate that the correct SSLContext is setup in the connection manager.  If you look in SimpleHostRoutingFilterTests there are some reflection utilities you might be able to use to introspect the connection manager.