Uploaded image for project: 'Realm Core'
  1. Realm Core
  2. RCORE-1987

network::Service does not start waiting on timers if no other events are currently active

    • Type: Icon: Task Task
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sync
    • None

      If there are no events currently pending or being handled in the Service event loop when a timer is started, the event loop will not be "kicked" to update the wait time to accommodate the new timer that was added. As a result, the timer will never fire until the default wait time of 86400 seconds has elapsed.

      Update the event loop to kick the event loop when a new timer is added to ensure the wait time is updated.

            Assignee:
            michael.wilkersonbarker@mongodb.com Michael Wilkerson-Barker (Inactive)
            Reporter:
            michael.wilkersonbarker@mongodb.com Michael Wilkerson-Barker (Inactive)
            AD Sync Client
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: