Issue #8382 requests that Partition.get_next_update() accept a block_size argument so users aren't locked into a fixed block size during OTA updates. PR #8268 adds configurable block_size to esp32.Partition broadly — the affected code list explicitly includes esp32_partition_get_next_update(). The mechanism differs: the PR sets block_size at partition construction/find time rather than as a direct argument to get_next_update(), but the net effect (flexible block_size for OTA partitions) overlaps substantially with what the issue requests. PR merge status is unknown, and it's unclear whether get_next_update() in the PR returns a partition that allows a different block_size than the source partition, which is the specific flexibility the issue asks for.
Suggested action
Check whether PR #8268 was merged. If merged, verify that get_next_update() in the resulting implementation allows callers to specify block_size on the returned partition (e.g., by calling Partition.get_next_update() and then constructing with a different block_size, or by direct argument). If the merged PR fully covers the use case, close issue #8382 as resolved by #8268. If get_next_update() still doesn't accept block_size directly, keep the issue open as a follow-up enhancement.