"Future exception was never retrieved" warning after socket timeout

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Minor - P4
    • 0.5
    • Affects Version/s: 0.5
    • Component/s: tornado
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Glitch in unreleased code: a timeout from a Tornado socket throws socket.error into PyMongo, which calls socket.close, which Motor delegates to Tornado's IOStream.close. Motor still has an unresolved Future from IOStream.read_bytes which is now in an error state, but the greenlet that was going to await this Future has terminated.

      Recent versions of Tornado log a warning when this Future is garbage collected, "Future exception was never retrieved."

      Motor's socket code should retrieve the IOStream.read_bytes Future's exception on timeout.

              Assignee:
              A. Jesse Jiryu Davis
              Reporter:
              A. Jesse Jiryu Davis
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: