mirror of
https://github.com/esphome/esphome.git
synced 2026-02-28 18:04:19 -07:00
185786604b
NVS/FDB write failures are permanent (flash worn out, partition full, handle invalid). The NVS layer already performs internal garbage collection during writes, so retrying the same call will always fail again. Keeping failed entries in the vector leaked memory and forced a reverse-iterate + per-element erase pattern that generated ~130 bytes of inlined vector move/destroy code for NVSData objects. Replace with a forward range-for and a single clear() at the end.
