WaitCR does not renew lock in between R intervals (and should) #1

Closed
opened 2024-07-24 02:28:14 +00:00 by james · 0 comments
Owner

WaitCR should continue asserting its token until it's allowed to continue otherwise, if C was > F, which is perfectly valid, the new agent would fail before it starts.

When waiting for C, the new agent should write to the lock once per R.

WaitCR should continue asserting its token until it's allowed to continue otherwise, if C was > F, which is perfectly valid, the new agent would fail before it starts. When waiting for C, the new agent should write to the lock once per R.
james changed title from WaitCR does not write lock in between R intervals to WaitCR does not renew lock in between R intervals (and should) 2024-07-24 02:29:04 +00:00
james added this to the 0.2.0 milestone 2024-07-24 02:30:44 +00:00
james closed this issue 2024-07-24 04:10:20 +00:00
james referenced this issue from a commit 2024-07-24 04:52:22 +00:00
james referenced this issue from a commit 2024-07-24 04:55:17 +00:00
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: james/putex#1
No description provided.