From 3702a72bdf16f021c1b34664b83da377aff48bff Mon Sep 17 00:00:00 2001
From: Warren James <warren.james@mongodb.com>
Date: Mon, 14 Oct 2024 15:12:31 -0400
Subject: [PATCH] add comment explaining why we do not check for non-zero
 cursor id

---
 .../client_side_operations_timeout.prose.test.ts                | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/test/integration/client-side-operations-timeout/client_side_operations_timeout.prose.test.ts b/test/integration/client-side-operations-timeout/client_side_operations_timeout.prose.test.ts
index 5abf7d41f3..3073f6747a 100644
--- a/test/integration/client-side-operations-timeout/client_side_operations_timeout.prose.test.ts
+++ b/test/integration/client-side-operations-timeout/client_side_operations_timeout.prose.test.ts
@@ -437,6 +437,8 @@ describe('CSOT spec prose tests', function () {
        * 1. Verify that an `aggregate` command and two `getMore` commands were executed against the `db.coll` collection during the test.
        */
       it('sends correct number of aggregate and getMores', metadata, async function () {
+        // NOTE: we don't check for a non-zero ID since we lazily send the initial aggregate to the
+        // server. See ChangeStreamCursor._initialize
         const changeStream = client
           .db('db')
           .collection('coll')