The test:

"should tail cursor using maxAwaitTimeMS for 3.2 or higher"

Is failing on latest servers because the operation interrupted error returns to the driver quick enough to make the distance between start time and end time time less than 500ms.

AC

• Fix test failure on main and 4.x
• Split tests into two scenarios
  • When a tailable await cursor is constructed with a maxAwaitTimeMS value, it should respect the await time ms on the server (maxAwaitTimeMS elapses between server responses).
  • When iterating a cursor (for-await loop), when the cursor is closed on the server side, the client correctly closes the cursor and passes the operation interrupted error to the user.
• Follow up with server team to see if error timing was intentionally changed