[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: |
|
||||
| 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: |