My Python script to download StorageFiles seems to have gone bust completely. It now times out waiting for first byte. I changed the previous timeout from 10 seconds to upto 30 seconds and it still didn't kick off. In the last attempt I got this in the file instead of actual data.
Execution Interrupted
at line 2 col 21
line = f.readLine();
^
New interpreter error: MEMORY_BUSY
The command sent to the Bangle (via Python/Bleak) is
getFileCommand = b"\x03\x10\
var f = require('Storage').open('ftclog', 'r');\n\x10\
var line = '';\n\x10\
while ((line != null && line != undefined) && (line.indexOf('\xFF') == -1)){\n\x10\
line = f.readLine();\n\x10\
print(line);\n\x10\
}\n\x10\
"
I also tried using the WebIDE and got similar error. At the time I wasn't sure if it was because I had initiated another connect on a different browser tab.
getFileCommand = b"\x03\x10\
var f = require('Storage').open('ftclog', 'r');\n\x10\
var line = '';\n\x10\
while ((line != null && line != undefined) && (line.indexOf('\xFF') == -1)){\n\x10\
line = f.readLine();\n\x10\
print(line);\n\x10\
}\n\x10\
"
In the WebIDE, atleast it spent good 10 minutes downloading the blurb before failing.
I will try with a longer timeout in the evening in my script.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
My Python script to download
StorageFile
s seems to have gone bust completely. It now times out waiting for first byte. I changed the previous timeout from 10 seconds to upto 30 seconds and it still didn't kick off. In the last attempt I got this in the file instead of actual data.The command sent to the Bangle (via Python/Bleak) is
I also tried using the WebIDE and got similar error. At the time I wasn't sure if it was because I had initiated another connect on a different browser tab.
In the WebIDE, atleast it spent good 10 minutes downloading the blurb before failing.
I will try with a longer timeout in the evening in my script.
Firmware details:
P.S. This may not be related to the firmware refactor. I started having this issue on Friday when I was running
2v04.99
Full Python script on Github