Sleep Scheduler: reconsider what happens when schedule is inactive #99886
Labels
No Label
Good First Issue
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Job Type
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: studio/flamenco#99886
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
At the moment, when a Worker has an inactive sleep schedue, the Sleep Scheduler will reply
awake
when queried for the desired Worker status. This behaviour could be seen as overstepping the responsibilities of the Sleep Scheduler.It might be a better design to let the Sleep Scheduler return an empty string instead, indicating "I don't have anything to say about this Worker". Then the caller could make up its own mind about what to do with the Worker.
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @dr.sybren