Details
-
Spec Change
-
Resolution: Unresolved
-
Unknown
-
None
-
Needed
-
Description
Summary
SRV option URI spec tests introduced in DRIVERS-1519 expect both valid: false and warning: true. In practice, the tests will either raise errors (e.g. using options with non-SRV scheme) or warnings (e.g. invalid value/type), but not both. This was missed during the POCs as neither Java nor Go differentiate errors and warnings raised during URI parsing.
Motivation
Is this ticket only for tests?
Yes.
Attachments
Issue Links
- related to
-
PYTHON-2832 Provide options to limit number of mongos servers used in connecting to sharded clusters
-
- Closed
-
- split to
-
GODRIVER-2196 Do not expect both valid:false and warning:true in SRV option URI spec tests
-
- Closed
-
-
CDRIVER-4196 Do not expect both valid:false and warning:true in SRV option URI spec tests
-
- Backlog
-
-
CXX-2397 Do not expect both valid:false and warning:true in SRV option URI spec tests
-
- Backlog
-
-
NODE-3696 Do not expect both valid:false and warning:true in SRV option URI spec tests
-
- Closed
-
-
CSHARP-3926 Do not expect both valid:false and warning:true in SRV option URI spec tests
-
- Closed
-
-
JAVA-4364 Do not expect both valid:false and warning:true in SRV option URI spec tests
-
- Closed
-
-
MOTOR-840 Do not expect both valid:false and warning:true in SRV option URI spec tests
-
- Closed
-
-
PHPLIB-746 Do not expect both valid:false and warning:true in SRV option URI spec tests
-
- Closed
-
-
PYTHON-2955 Do not expect both valid:false and warning:true in SRV option URI spec tests
-
- Closed
-
-
RUBY-2819 Do not expect both valid:false and warning:true in SRV option URI spec tests
-
- Closed
-
-
RUST-1068 Do not expect both valid:false and warning:true in SRV option URI spec tests
-
- Closed
-