Summary

The CSOT spec now significantly diverges in its description of the feature from both the Python and Go implementations. We should wait for the spec to be updated (allowing language-specific syntax, bumping timeouts in tests, removing requirements for timeoutMode on cursors and timeoutMS options on non-client types) and the resolution of DRIVERS-2347. Once the spec is more stabilized and representative of what we've implemented in Go, we should make sure our implementation aligns with the new spec and continue the epic.

Motivation

Who is the affected end user?

Users of CSOT in the Go driver.

How does this affect the end user?

CSOT is not fully designed and remains provisional API. Users should have access to a more stable timeout API.

How likely is it that this problem or use case will occur?

Likely that users may encounter inconsistencies in CSOT features.

If the problem does occur, what are the consequences and how severe are they?

May push users away.

Is this issue urgent?

No. And we probably can't do this until CSOT spec work is re-prioritized.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

No.