establishCursors/AsyncRequestsSender can leave dangling request if interrupted

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • v4.4
    • Query 2020-03-09, Query 2020-03-23, Query 2020-04-06, Query 2020-04-20, Query 2020-05-04
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If the AsyncRequestsSender is interrupted after sending one or more requests, it may not be able to gracefully cancel that request. establishCursors() has some cleanup logic to mitigate this, but I'm pretty sure that if we're interrupted then this line will also throw the interrupted error, and we won't be able to clean up our cursors.

              Assignee:
              Nicholas Zolnierz
              Reporter:
              Charlie Swanson
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: