[SERVER-39240] WriteConcernOptions timeout constants can be used before they are initialized Created: 29/Jan/19 Updated: 29/Oct/23 Resolved: 30/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.8 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding 2019-02-11 |
| Participants: |
| Description |
|
The timeout constants defined under WriteConcernOptions can be used before they are initialized in places where we construct static WriteConcernOptions constants, such as here. Because of this, these usages get the zero-initialized value and can lead to unexpected errors. |
| Comments |
| Comment by Githook User [ 30/Jan/19 ] |
|
Author: {'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev'}Message: |