Note that debugging took hours, due to the nature of this bug. commit and PRs are coming from ready local code.
Whilst rewriting the code, I noticed that the epochStart extraction is redundant
(It is nothing special, happened to everyone I guess, including myself several times, both, in hardware and software, to have redundant code)
std::mktime should not be used
depending on std::this_thread::sleep_for(std::chrono::milliseconds(0)); to make code functional can be a workaround at best. Something like this should not stay in the code for long (as it indicates that something is wrong with the code).
re #54
(look at each commit separately)
Note that debugging took hours, due to the nature of this bug. commit and PRs are coming from ready local code.
Whilst rewriting the code, I noticed that the epochStart extraction is redundant
(It is nothing special, happened to everyone I guess, including myself several times, both, in hardware and software, to have redundant code)
std::mktimeshould not be usedstd::this_thread::sleep_for(std::chrono::milliseconds(0));to make code functional can be a workaround at best. Something like this should not stay in the code for long (as it indicates that something is wrong with the code).