refs #123

This can happen on slow machines

After notifying, otherwise they might (depending on
std::chrono::time_point's move assignement operator) keep their values,
and be used again when comparing a timeout at a later time

Fix #105

refs #105

refs #93

refs #93

refs #93

Refs #93

refs #93

We don't need the error code and the extended error code, since the
extended already contains the base error

Hugo Beauzée-Luyssen authored 5 years ago and Hugo Beauzée-Luyssen committed 5 years ago

Ref #119