Year 2038 Problem

#1

If you are asking a question, please follow this template:

  1. My goal is: to use a device with Mongoose OS after Year 2038
  2. My actions are: ///
  3. The result I see is: ///
  4. My expectation & question is:
    Is Mongoose OS or its libraries affected by https://en.wikipedia.org/wiki/Year_2038_problem?
#2

Your question seems (to me) a bit too broad.
In principle, time is usually provided by the underlying vendor SDK; in the case of the ESP32, for example, Espressif’s IDF. You can get from mOS an int64_t current time in microseconds, which will be enough for your applications’ needs.
As per the other libraries, if you have some in mind perhaps someone may comment. Some will in fact depend on the protocol they handle, for example SNTP, which means you will have to provide for updates to keep current. I wouldn’t expect a networked device to be fully operational 18 years from now without updates anyway. These protocol handlers themselves sometimes also depend on a provider (lwIP, for example), but this may be different among different devices.

1 Like
#3

Yup it is very broad.
But as the Y2k38 Problem has an effect on multiple layers, I just want to know if the project can say from itself “If run on XY hardware (with sdk YZ), mongoose os is Y2k38 proof (or unlikely to fail)”.