Context

Describe the background behind the problem.

FAILED test/asynchronous/test_discovery_and_monitoring.py::TestUnifiedHelloTimeout::test_Driver_extends_timeout_while_streaming - AssertionError: 2 != 0 : expected 0 not {'serverDescriptionChangedEvent': {'newDescription': {'type': 'Unknown'}}}
FAILED test/test_discovery_and_monitoring.py::TestUnifiedHelloTimeout::test_Driver_extends_timeout_while_streaming - AssertionError: 2 != 0 : expected 0 not {'serverDescriptionChangedEvent': {'newDescription': {'type': 'Unknown'}}}r

it appears to not only be happening in "latest" GH prs (https://github.com/mongodb/mongo-python-driver/actions/runs/29953487057/job/89036653680) but also in server version 7.0 on evergreen (https://spruce.corp.mongodb.com/task/mongo_python_driver_mongodb_v7.0_test_server_version_pypy3.11_sync_noauth_nossl_standalone_cov_patch_f26360d28f933a9d4aa144eaa492bb96a08ddf6d_6a61384a3d24d50007426967_26_07_22_21_38_23/tests?execution=0&sorts=STATUS:ASC) so its unlikely just a latest issue? I'm also not entirely sure what caused it to suddenly fail though? 

see slack thread for full conversation in dbx-devs: https://mongodb.slack.com/archives/C72LB5RPV/p1784758784539619

tldr: this seems to be a result of SERVER-128517 (see comments on the ticket)

Definition of done

What must be done to consider the task complete?

Pitfalls

What should the implementer watch out for? What are the risks?