NoPrefetch test in TaskExecutorCursorTest can deadlock

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.1.0-rc0, 6.0.7, 5.0.19, 7.0.0-rc3
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v7.0, v6.0, v5.0, v4.4
    • QO 2023-05-29
    • 23
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      In the NoPrefetchGetMore test, it is currently possible for the main thread to enter the network interface when it is already acting as the network. This causes a deadlock in the test. This occurs when we run hasReadyRequests before the destruction of the NetworkGuard in this lambda, which exits the network.

            Assignee:
            Ben Shteinfeld
            Reporter:
            Ben Shteinfeld
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: