[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:
Depends
is depended on by GODRIVER-2810 Switch to polling monitoring when run... Closed
Problem/Incident
is caused by GODRIVER-2572 Add log messages to Server selection ... Closed
Backwards Compatibility: Fully Compatible
Documentation Changes: Not Needed
Documentation Changes Summary:

1. What would you like to communicate to the user about this feature?
2. Would you like the user to see examples of the syntax and/or executable code and its output?
3. Which versions of the driver/connector does this apply to?


 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: GODRIVER-2972 Fix wiremessage RequestID race in operation.Execute (#1375)
Branch: master
https://github.com/mongodb/mongo-go-driver/commit/68bf155d63446251f63603eebd74a12707bcdf51

Generated at Thu Feb 08 08:39:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.