-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: user-scheduled tasks #120
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seeded to stare at this for a bit to figure out the flows, but in general looks good.
Would be great to test this somehow, I don't think any of us will use this feature any time soon, so having that test is quite important.
Would also be nice to implement some small Go server implementing some simple policy like round-robin serving this API - mostly as a base for people to take and modify to fit their needs
Also the Do() error cases need intelligent handling so as not to fail tasks on scheduling-server down. |
Here's a sketch of a dramatically simpler system than what we had before.
There was as little change as possible to the task engine: I just needed a way to peaceably return the task to the queue without a failure getting logged.
It's not a perfect system (see downsides), but it's so much simpler to reason about that I think we can verify that it would work.
Notice the interface passthru.