-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Native
-
None
Rebecca and Sophie introduced a subtle bug in their test for an unrelated issue, by specifying the following when creating a client:
const client = configuration.newClient( { w: 1, readPreference: ReadPreference.SECONDARY }, { poolSize: 1, auto_reconnect: false } );
Resulting in this error:
Uncaught TypeError: self.s.connectOptions.readPreference.equals is not a function
at shouldTriggerConnect (/Users/katherinewalker/drivers/node/mongodb-core/lib/topologies/replset.js:770:42)
at /Users/katherinewalker/drivers/node/mongodb-core/lib/topologies/replset.js:841:15
at applyAuthenticationContexts (/Users/katherinewalker/drivers/node/mongodb-core/lib/topologies/replset.js:731:12)
at Server.<anonymous> (/Users/katherinewalker/drivers/node/mongodb-core/lib/topologies/replset.js:802:7)
at /Users/katherinewalker/drivers/node/mongodb-core/lib/topologies/server.js:506:16
at /Users/katherinewalker/drivers/node/mongodb-core/lib/connection/pool.js:531:18
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)
This would seem to indicate that read preferences passed by string to the MongoClient constructor are not properly resolved into ReadPreference types.