Fix TestKmsTLSOptions on Windows

ExportXMLWordPrintableJSON

    • Type: Build Failure
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Tests
    • None
    • Python Drivers
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      Name of Failure:

      Async KMS reads fail with WinError 10054 on Windows + Python 3.14.7 (TestKmsTLSOptions).

      Link to task:

      test-non-standard-v7.0-python3.14-auth-ssl-sharded-cluster

      Context of when and why the failure occurred:

      Since Sept 19, async `TestKmsTLSOptions` fails deterministically (5-6 tests/run).
      The image bumped from Python 3.14.0 to 3.14.7.

      The mock KMS servers close without TLS `close_notify`.

      Proposed Fix: blocking reads in a worker thread via `_async_blocking_socket_call`.

      This failure is also present in the v4.18 branch.

      Stack trace:

      File "pymongo/network_layer.py", line 222, in _async_socket_receive_ssl
    read = conn.recv_into(mv[total_read:])
ConnectionResetError: [Errno 10054] An existing connection was forcibly closed by the remote host
h3.

            Assignee:
            Alex Clark
            Reporter:
            Steve Silvester
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: