Andrew Leech

Yeah I threw this change up quickly partially as just a way to document: * some learnings from the recent work I did with handling this in SW on the...

Thanks @Josverl yes I've since realised that True / True essentially is the default in pyserial anyway, so certainly isn't the right setting. Even though I think it "should" be...

Hi @TakeoTakahashi2020 thank you for sharing those configuration files, I definitely think they add real value here. I appreciate the suggestion about the compatible fsp version, I've updated my readme...

I'm not sure if it's documented but I'm pretty sure the filesystem libraries are not thread/interrupt safe, this is one of the main blocking issues when looking into how to...

I'm not sure but the problem might not actually be from the file write, it might be a race condition / rare issue from the gc memory allocation itself. It...

Not sure, it's just a guess. I do occasionally see some thread init tests fail intermittently in CI which then pass on a rerun. I'm not sure which test(s) it...

I'm not certain about that, not sure if it's explicitly true? Did you find any references about this, or are you asking it as a question?

I wouldn't say it's expected, no, there should never be a GC crash like that. However I don't know if there are any known bugs/limitations in that area. I agree...

Yes creating strings like that will certainly cause memory allocations. Just to be clear, you're saying you get the same gc crash with this test too? So this means the...

From your original message: ``` micropython: ../../py/gc.c:906: gc_realloc: Assertion '(((area)->gc_alloc_table_start[(block) / (4)] >> (2 * ((block) & ((4) - 1)))) & 3) == (1)' failed. ``` Every time it fails...