Details
-
Bug
-
Resolution: Works as Designed
-
Major - P3
-
None
-
None
-
None
-
None
-
Service Arch
-
ALL
Description
On deadline expiration, OperationContext::waitForConditionOrInterruptNoAssertUntil() is not returning stdx::cv_status::timeout, instead it's returning stdx::cv_status::no_timeout. As a result, maybeWakeReason in waitForConditionOrInterruptUntil() is set to boost::none, leading to hang of waitForConditionOrInterruptUntil().
Note: Currently, sleepFor(), sleepUntil(), waitForConditionOrInterruptFor() internally calls waitForConditionOrInterruptUntil() and those methods are used in many places of our codebase.