WIP: Allow jobs to be submitted in paused
status
#104318
No reviewers
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: studio/flamenco#104318
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "David-Zhang-10/flamenco:submit-as-paused"
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?
Overview
This pull request implements Issue #99439 Allow jobs to be submitted in paused status and builds upon PR #104313 Support pausing jobs.
Deliverables
paused
status before submission to Flamenco Manager.paused
status, the job shows up correctly in the web interface.Pause Job
button ba454cd4a0pause-requested
status c32a591e55It's better to keep the add-on out of this PR, and focus only on the API side.
These are good to have in this PR.
This was just a partial review, I haven't actually tried the code yet. I'll do that once #104313 lands and we can disentangle the two PRs.
@ -20,2 +20,3 @@
"type": "echo-sleep-test",
"submitter_platform": "manager"
"submitter_platform": "manager",
"initial_status": "paused"
Change this to
queued
so that the semantics of the script don't change.For these kind of "I need a slightly different script" cases, I ususally just make a copy, then add its filename to
.git/info/exclude
so I don't accidentally commit it.@ -59,6 +59,7 @@ require (
github.com/remyoudompheng/bigfft v0.0.0-20230129092748-24d4a6f8daec // indirect
github.com/valyala/bytebufferpool v1.0.0 // indirect
github.com/valyala/fasttemplate v1.2.1 // indirect
golang.org/toolchain v0.0.1-go1.9rc2.windows-amd64 // indirect
How did this new dependency get added?
@ -92,7 +92,9 @@ func (f *Flamenco) SubmitJob(e echo.Context) error {
logger = logger.With().Str("job_id", authoredJob.JobID).Logger()
// TODO: check whether this job should be queued immediately or start paused.
This TODO can now be removed.
@ -132,2 +132,4 @@
}
if sj.InitialStatus != nil {
aj.Status = *sj.InitialStatus
What's the reason to handle this here, rather than in
func (f *Flamenco) SubmitJob(e echo.Context) error
? I think it's better to keep the status asunder-construction
while the job is still under construction, and then let it go to its initial status afterwards (like the currentunder-construction
→queued
transition).Pull request closed