You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, there are multiple places in the code (ResolveSnapshotWork, GenerateBucketsWork, ConditionalWork) that implement the same pattern: run, check if ready, sleep for a short time, then wake self up (done via creating a weak pointer, initializing a lambda to wake self up, then setting up a timer to wait). We should avoid the duplication, and generalize this. For example, we already have wakeSelfUpCallback in BasicWork that can be used. Also, as this pattern seems useful, it might make sense to make it a feature of BasicWork.
The text was updated successfully, but these errors were encountered:
Currently, there are multiple places in the code (ResolveSnapshotWork, GenerateBucketsWork, ConditionalWork) that implement the same pattern: run, check if ready, sleep for a short time, then wake self up (done via creating a weak pointer, initializing a lambda to wake self up, then setting up a timer to wait). We should avoid the duplication, and generalize this. For example, we already have
wakeSelfUpCallback
in BasicWork that can be used. Also, as this pattern seems useful, it might make sense to make it a feature of BasicWork.The text was updated successfully, but these errors were encountered: