[SERVER-31247] enhance LockerNoOp Created: 25/Sep/17 Updated: 06/Dec/22 Resolved: 24/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
Currently, LockerNoOp returns mostly "true" for functions that ask if a resource is locked. However, it returns "false" for isLocked() and isWriteLocked(), and will crash if you call isReadLocked(). |
| Comments |
| Comment by Sara Williamson [ 24/Jun/19 ] |
|
Instead, we plan to do |