OperationContext::waitForConditionOrInterruptNoAssertUntil() is not returning stdx::cv_status::timeout on deadline expiration.

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Service Arch
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

       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.

            Assignee:
            [DO NOT USE] Backlog - Service Architecture
            Reporter:
            Suganthi Mani
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: