You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
I have searched the issue tracker for a similar issue and not found a similar issue.
General issue report
When looking at this documentation, i noticed that documentation of some functions like sntp_init is missing. This is less of a problem since this function has docs in the official lwIP docs, but the docs of some ESP specific functions like sntp_setservername are to be found nowhere except in the source files themselves, which is no easy task to do as you have to dig for them very deep. esp_time_impl_set_boot_time is also not documented. https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/system/system_time.html
Is it supposed to be like this, and if not, can you please fix it?
The text was updated successfully, but these errors were encountered:
* Fix thread safety issues in non-core locking
* Add option to verify thread safety issues in lwip (core-lock assertion)
* Make esp_sntp.h thread safe API
* Fix sntp example
(v4.4 - fixes minor merge issue that duplicated
DHCP_DEFINE_CUSTOM_TIMEOUTS and DHCP_REQUEST_TIMEOUT_SEQUENCE)
Closes#9908Closes#10502Closes#10466
Answers checklist.
General issue report
When looking at this documentation, i noticed that documentation of some functions like sntp_init is missing. This is less of a problem since this function has docs in the official lwIP docs, but the docs of some ESP specific functions like sntp_setservername are to be found nowhere except in the source files themselves, which is no easy task to do as you have to dig for them very deep. esp_time_impl_set_boot_time is also not documented.
https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/system/system_time.html
Is it supposed to be like this, and if not, can you please fix it?
The text was updated successfully, but these errors were encountered: