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
As per the caveat in the README: when we loop and retry a lock, we create a fresh key on S3, which means created-at moves forward. If another process is doing the same, it could "cut us in line". There are trade-offs either way, and we're not exactly calling this a bug, but this Issue serves to track discussion on the matter.
The text was updated successfully, but these errors were encountered:
As per the caveat in the README: when we loop and retry a lock, we create a fresh key on S3, which means created-at moves forward. If another process is doing the same, it could "cut us in line". There are trade-offs either way, and we're not exactly calling this a bug, but this Issue serves to track discussion on the matter.
The text was updated successfully, but these errors were encountered: