[SERVER-54406] NetworkInterfaceMock should allow simultaneous interruption and response Created: 08/Feb/21 Updated: 29/Oct/23 Resolved: 25/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0, 4.4.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | Benjamin Caimano (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||||||
| Sprint: | Security 2021-02-22, Security 2021-03-08 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 16 | ||||||||||||||||
| Description |
|
There are no guards around NetworkInterfaceMock::NetworkOperation::setResponse() here and here. This means that tests that feature timeouts or interruptions cannot safely experience an interruption during a response. Poorly written tests may also experience undefined behavior because it is not explicitly defined who wins "races". |
| Comments |
| Comment by Githook User [ 02/Mar/21 ] |
|
Author: {'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}Message: (cherry picked from commit 6166a40b8da9634203cdebc91617d657453e0038) |
| Comment by Githook User [ 22/Feb/21 ] |
|
Author: {'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}Message: |