Currently, the assertion failure handler in LFS (and maybe elsewhere) enters a silent empty infinite loop upon assertion failure.
Ideally, we want a log message to be emitted, and likely an action other than "locking up" (entering an empty infinite loop) to be done in this case. Ideally, I think we want to avoid failing asserts and avoid calling that assert, but need to ensure it's not an issue if LittleFS triggers an assert fail.
Currently, the assertion failure handler in LFS (and maybe elsewhere) enters a silent empty infinite loop upon assertion failure.
Ideally, we want a log message to be emitted, and likely an action other than "locking up" (entering an empty infinite loop) to be done in this case. Ideally, I think we want to avoid failing asserts and avoid calling that assert, but need to ensure it's not an issue if LittleFS triggers an assert fail.