[GODRIVER-204] Eliminate internal use of panic() wherever possible Created: 23/Jan/18 Updated: 28/Oct/23 Resolved: 06/Feb/18 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 0.0.1 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | David Golden | Assignee: | Samuel Rossi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Epic Link: | GODRIVER Alpha UX | ||||||||||||
| Description |
|
There are a number of internal functions that panic when hitting an unexpected situation, e.g. message_query.AddMeta. Many of these are effectively "should never get here" sentinels, but nonetheless, these should be converted to return errors whenever possible. When not possible, we must ensure such panics are caught with deferred recover() calls. |
| Comments |
| Comment by Githook User [ 06/Feb/18 ] |
|
Author: {'email': 'saghmrossi@gmail.com', 'name': 'Saghm Rossi', 'username': 'saghm'}Message: Change-Id: Iac10de6a98e1682b572f23ad76b3028a48383cc8 |
| Comment by Samuel Rossi (Inactive) [ 01/Feb/18 ] |
|
Blocked on new BSON library being merged into driver |