GODRIVER-3480ClosedGone away

Address CSOT Compliance Issue in Timeout Handling for Cursor Constructors

h3. Detailed steps to reproduce the problem? The CSOT specifications states the following: {quote} If set, drivers MUST apply the timeoutMS option to the initial aggregate operation. Drivers MUST also apply the original timeoutMS value to each next call on the change stream but MUST NOT use it to derive a maxTimeMS field for getMore commands {quote} One can verify that the Go Driver does not do this by running the ["timeoutMS applies to full resume attempt in a next call"|https://gith

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue

No components specified.

Labels
Tags and classification

No labels assigned.