NODE-7908ClosedWorks as Designed
Unawaited cursor.hasNext() has unexpected non-deterministic behavior
h3. Use Case As a developer, I want to be able to proactively trigger database fetch via cursor.hasNext() without awaiting the result. So that I could minimize latency when doing multiple interactions over the network. h3. User Experience * _cursor.hasNext() should be idempotent irrespective of whether the result is awaited or not if the cursor is not consumed in between the invocations._ h3. Current behavior Non-deterministic. * One time I was able to desync the command stream o