ddp/photoassistant
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

first thoughts on pa_job_engine - to keep overall pa_job engine state, also a pa_job_state in each action also a wait_for so we can do basic handling of jobs and dependencies

Browse Source
This commit is contained in:
Damien De Paoli
2021-01-14 22:13:07 +11:00
parent a8789e60fe
commit 46f8d84cd3
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
TODO
View File

@@ -20,6 +20,7 @@
to keep html easy, can keep routes: to keep html easy, can keep routes:
/jobs/import/ -> importlog.html /jobs/import/ -> importlog.html
/jobs/ai/ -> importlog.html??? /jobs/ai/ -> importlog.html???
/jobs/move/ -> importlog.html???
but not sure if any job won't have passes, num files, etc. BUT if it ever does this is how we deal with it but not sure if any job won't have passes, num files, etc. BUT if it ever does this is how we deal with it
@@ -32,7 +33,6 @@
-> when job finished, then Import Files (import_dir only) -> when job finished, then Import Files (import_dir only)
-> when job finished, the set state: awating jobs -> when job finished, the set state: awating jobs
implications, pa_job needs to know if it depends on another, e.g. do find before import (in example above) implications, pa_job needs to know if it depends on another, e.g. do find before import (in example above)
pa web needs to show status for the job engine IN YOUR FACE when not at awaiting jobs yet, afterwards, maybe a simple jobs(<badge>) that is clickable on the gui? pa web needs to show status for the job engine IN YOUR FACE when not at awaiting jobs yet, afterwards, maybe a simple jobs(<badge>) that is clickable on the gui?