Open danfleck opened 1 month ago
Hello @danfleck Could you please share a sample application with sdkconfig file that can be used to reproduce this issue. Thanks!
Here is a modified example program that shows the problem. The timeouts are very short because on working hardware, the connection doesn't really timeout. The watchdog timeout is 500ms and the http_open timeout is 300ms. When I run this on an ESP dev board the watchdog timeout runs, not the http_open timeout. I'm not sure if this is representative of the exact problem I am seeing because on my board the timeouts are 10s and 5s.
(Make sure to not init the task watchdog on startup in sdkconfig.)
SDKCONFIG sdkconfig.txt
Answers checklist.
IDF version.
v5.2.2
Espressif SoC revision.
ESP32-S3
Operating System used.
macOS
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
None
Development Kit.
Custom board
Power Supply used.
Battery
What is the expected behavior?
I expect the esp_http_client_open call to timeout within the timeout_ms milliseconds.
What is the actual behavior?
It does not timeout, so the watchdog is triggered.
Steps to reproduce.
This is happening due to unstable power supply on my board which is causing HTTP transmission errors. However, it should still timeout I believe within the timeout_ms time.
set timeout_ms = 5000 is_async = false
(Watchdog timeout is set to 10sec) Run the code and attempt to open an https connection.
Debug Logs.
More Information.
No response