Skip to content
This repository has been archived by the owner on Jan 19, 2022. It is now read-only.

Transition Slaveloan to a form of workflow rather than a celery "chain" #349

Closed
Callek opened this issue Sep 17, 2015 · 1 comment
Closed

Transition Slaveloan to a form of workflow rather than a celery "chain" #349

Callek opened this issue Sep 17, 2015 · 1 comment
Assignees
@Callek
Labels
difficult slaveloan
Milestone
slaveloan 0.3

Comments

@Callek
Copy link
Contributor

Callek commented Sep 17, 2015

We are having issues with some celery jobs not starting, and with my "waitfor_manual_action" things not waiting as long as we expect.

After a few days of deep investigation and no good reasons for "why" any of that is dying, efforts are better spent transitioning this code over.
@Callek Callek self-assigned this Sep 17, 2015
@Callek Callek added this to the slaveloan 0.3 milestone Sep 17, 2015
@Callek
Copy link
Contributor Author

Callek commented Sep 21, 2015

Thinking on this more: Since we want to be able to do some parts in parallel and we're not being cyclic, terminology and mental concept is probably more consistent with a Workflow rather than State Machine design

@Callek Callek changed the title Transition Slaveloan to a form of state-machine rather than a celery "chain" Transition Slaveloan to a form of workflow rather than a celery "chain" Sep 21, 2015
@Callek Callek closed this as completed Dec 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Callek Callek

Labels
difficult slaveloan
Projects
None yet
Milestone
slaveloan 0.3
Development

No branches or pull requests
1 participant
@Callek