[GODRIVER-2972] Fix wiremessage RequestID race in operation.Execute Created: 06/Sep/23 Updated: 06/Dec/23 Resolved: 07/Sep/23 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.13.0, 1.13.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Preston Vasquez | Assignee: | Preston Vasquez |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Documentation Changes: | Not Needed | ||||||||||||||||
| Documentation Changes Summary: | 1. What would you like to communicate to the user about this feature? |
||||||||||||||||
| Description |
|
There is a race condition in the Go Driver's operation.Execute method where concurrent operation wire messages could have the same requestID, since the CurrentRequestID function is called after a "next" request ID is received in the operation.Execute method. |
| Comments |
| Comment by Githook User [ 07/Sep/23 ] |
|
Author: {'name': 'Preston Vasquez', 'email': 'prestonvasquez@icloud.com', 'username': 'prestonvasquez'}Message: |