Resolved Task Limit error in Flamenco Manager #104201 #104205
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#104205
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "Anish-Bharadwaj/flamenco:104201-Resolving-Task-limit-issue-in-Flamenco-manager"
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?
Resolving Task Limit In Falmenco Manager
In my recent commit, I had to address an issue with SQL Server not liking all dependencies being inserted at once. To resolve this problem, I uploaded the dependencies of a task in batches of 1000 allowing the server to handle larger task loads.
(Accidentally Closed Previous Pull Request #104203)
Could you write a unit test as well, that tests the creation of >1000 tasks? You can just add a new test to
internal/manager/persistence/jobs_test.go
Yeah, definitely! I'll write the unit test for this functionality and add it to this PR
Resolved Task Limit error in Flamenco Manager #104201to WIP: Resolved Task Limit error in Flamenco Manager #104201WIP: Resolved Task Limit error in Flamenco Manager #104201to Resolved Task Limit error in Flamenco Manager #1042018a2ee95fd3
tob235fe5e01
b235fe5e01
to6941e9f931
I was ran into some odd merge conflicts so I reverted a previous push in the:
"force-pushed 104201-Resolving-Task-limit-issue-in-Flamenco-manager from 8a2ee95fd3 to b235fe5e01 "
And then pulled codebase changes again to resolve the issue.
Thanks for the test, I'm glad to have it in there :)
Just a few tiny remarks, almost done!
@ -594,6 +606,37 @@ func createTestAuthoredJobWithTasks() job_compilers.AuthoredJob {
return createTestAuthoredJob("263fd47e-b9f8-4637-b726-fd7e47ecfdae", task1, task2, task3)
}
//Create a Job with a Specified number of tasks
Function documentation in Go should start with the function name, so in this case:
In this particular case, though, I think the comment can be removed as it just repeats the same info that's already in the function name.
@ -596,1 +608,4 @@
//Create a Job with a Specified number of tasks
func createTestAuthoredJobWithNumTasks(numTasks int) job_compilers.AuthoredJob {
//Generates all of the render jobs
Please configure your IDE to use auto-formatting, or run
go fmt ./...
before committing.@ -597,0 +613,4 @@
for i := 0; i < numTasks-1; i++ {
currtask := job_compilers.AuthoredTask{
Name: "render-" + fmt.Sprintf("%d", i),
Type: "ffmpeg",
Just for consistency with the name, this should be
Type: "blender-render"
.@ -16,6 +16,7 @@ import (
)
const schedulerTestTimeout = 100 * time.Millisecond
const schedulerTestTimeoutlong = 5000 * time.Millisecond
This is a good idea, to have another timeout for this longer-running test.
To take it one step further, in
TestCheckIfJobsHoldLargeNumOfTasks()
you could add this code at the start of the function:That way running
go test -short
will actually skip the test. It's not a necessity, but just a cherry on top. Up to you if you want to spend time on this, I'll accept the patch with or without this change.6941e9f931
to140115f820
Thanks!