-
Type: Task
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Component/s: Initial DNS Seedlist Discovery
-
Needed
-
Summary
mongodb/specifications@b508f6d introduced initial-dns-seedlist-discovery spec tests that expect an error when specifying an invalid type or integer value for srvMaxHosts. This contradicts the Connection String spec, which states that a warning should be logged and the parsed value ignored.
That same commit also introduced uri-options tests for the same cases, which correctly expect a warning. Unlike uri-options, the initial-dns-seedlist-discovery spec test format has no syntax for asserting warnings (only errors), so we should just remove the incorrect (and redundant) tests.
Motivation
Who is the affected end user?
Drivers.
Is this issue urgent?
It should be done close to DRIVERS-1519 so drivers can remove any work-arounds they might have added to get the incorrect initial-dns-seedlist-discovery tests passing (unless they were being skipped).
Is this ticket required by a downstream team?
No.
Is this ticket only for tests?
Yes.
- split to
-
CDRIVER-4239 Remove srvMaxHosts tests expecting an error for invalid values
- Backlog
-
CSHARP-3992 Remove srvMaxHosts tests expecting an error for invalid values
- Backlog
-
CXX-2421 Remove srvMaxHosts tests expecting an error for invalid values
- Backlog
-
GODRIVER-2253 Remove srvMaxHosts tests expecting an error for invalid values
- Closed
-
MOTOR-864 Remove srvMaxHosts tests expecting an error for invalid values
- Closed
-
NODE-3812 Remove srvMaxHosts tests expecting an error for invalid values
- Closed
-
PHPC-2016 Remove srvMaxHosts tests expecting an error for invalid values
- Closed
-
PYTHON-3040 Remove srvMaxHosts tests expecting an error for invalid values
- Closed
-
RUBY-2851 Remove srvMaxHosts tests expecting an error for invalid values
- Closed
-
RUST-1126 Remove srvMaxHosts tests expecting an error for invalid values
- Closed
-
JAVA-4425 Remove srvMaxHosts tests expecting an error for invalid values
- Closed