The system can wait arbitrarily long between acquiring a DeferredToken (token acquisition resulted in queuing) and calling get() on it. This leads to subtle inaccuracy in the production queuing implementation, but also non-determinism in test. Instead, we should track the absolute deadline for the deferred token's "nap time" using the current tick source.
Track absolute napTime in DeferredToken
- Assignee:
-
Matt Broadstone
- Reporter:
-
Matt Broadstone
- Votes:
-
0 Vote for this issue - Watchers:
-
2 Start watching this issue
- Created:
- Updated:
- Resolved: