Axel Lin

> > @maenkai esp-idf-v4.3 branch is already EOL. Could you try reproduce this issue with recent esp-idf versions? > > I will try it @maenkai Any update?

@o-marshmallow How is the status of this issue? The fix 4a22a5b only available in v5.0 branch, just wondering if v5.1+ need fix or not?

@filzek Any update for the issue and any feedback for the comment https://github.com/espressif/esp-idf/issues/13480#issuecomment-2056609036 ?

> @AxelLin we thing we can do it in about 10 days so far. @filzek Do you still hit this issue?

> hi @JonathanDotCel , it might because that when you use _esp_wifi_scan_get_ap_records_, it will clean the storage after getting record, then _esp_wifi_scan_get_ap_num_ returns no result. You can try use _esp_wifi_scan_get_ap_num_...

See 26a2f687e7b57fed00b562f899aed8ff0919eca3, this also causes regression in the example code. My question is why the fix is in the example code rather than prevent this regression by revert the breaking...

@Xiehanxin Any feedback about the log in https://github.com/espressif/esp-idf/issues/13721#issuecomment-2143901081 ?

ff94741cd13fbd43a3805ead2b60cc59ebb8f212 is good commit, 2302dd5a91cac6dce2853feda780a1b90a056001 is bad commit. So it looks like below commit causes this regression: Merge branch 'feature/i2c_sleep' into 'master' feat(i2c): Support i2c sleep retention on esp32c6/h2

> @AxelLin Please try to increase the size of `CONFIG_BT_NIMBLE_HOST_TASK_STACK_SIZE` in menuconfig. Why? The error is not stack overflow. Anyway , tested CONFIG_BT_NIMBLE_HOST_TASK_STACK_SIZE=8192 still hit the same error.

@esp-wzh It's in reviewing state, I'm wondering if you can provide the patch for testing.