[SERVER-24264] ConnectionString shouldn't use verify() Created: 23/May/16  Updated: 25/Jan/17  Resolved: 24/May/16

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: 3.3.8

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: Sharding 15 (06/03/16)
Participants:
Linked BF Score: 0

 Description   

verify() is non-fatal on production builds but fatal on debug builds, which makes it very difficult to use correctly. We should replace the usages of verify() in ConnectionString with uassert(), at least until we can get rid of all assertions from ConnectionString and use Status returns instead.



 Comments   
Comment by Githook User [ 24/May/16 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-24264 SERVER-23973 Replace calls to verify() in ConnectionString with uassert
Branch: master
https://github.com/mongodb/mongo/commit/ec5ce3087e17bb78cccc8a3bc50fdef7bc0997f3

Generated at Thu Feb 08 04:05:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.