-
Notifications
You must be signed in to change notification settings - Fork 1
Use TUS to do replication and make it non-blocking when uploading #99
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
base: main
Are you sure you want to change the base?
Conversation
raymondjacobson
left a comment
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.
seems good, one high level comment.
not 100% sure what the benefit is of having tus do server-server replication, but i dont see it hurting either
| return fmt.Errorf("failed to create TUS request: %w", err) | ||
| } | ||
|
|
||
| createReq.Header.Set("Tus-Resumable", "1.0.0") |
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.
what's this version from? maybe we can lift it from version.go?
| } | ||
| // Handle image uploads immediately with synchronous replication | ||
| if upload.Template == JobTemplateImgSquare || upload.Template == JobTemplateImgBackdrop { | ||
| upload.Mirrors, err = ss.replicateFileParallel(ctx, formFileCID, filePath, upload.PlacementHosts) |
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.
why not handle all replication async?
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.
i agree. unclear why the AI did this
No description provided.