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
Resume same files after interruption #34
Milestone
Comments
Sebl29
added a commit
that referenced
this issue
Sep 6, 2014
FileWatcher and several callable tasks, which can abort or check for file creation/modification/deletion.
Sebl29
added a commit
that referenced
this issue
Sep 8, 2014
Sebl29
added a commit
that referenced
this issue
Sep 10, 2014
an FileInProgressMark allows resuming to different remote repos (up and download). IntegrationTest (SyncAbortIT) watches with FileWatcher and interrupts, resumes.
Sebl29
added a commit
that referenced
this issue
Sep 10, 2014
Added functionality and test, to move a file that is in progress (so moving also chunks, and don't delete the chunks in a clean up step).
Sebl29
added a commit
that referenced
this issue
Sep 10, 2014
Sebl29
added a commit
that referenced
this issue
Sep 12, 2014
nlmarco
pushed a commit
that referenced
this issue
Nov 29, 2014
Fixed wrong assumption in the test about the file order by adding a sort operation. Files are now transferred in alphabetical order.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After an interruption, first finish those files that were already started, before. New files might have been added in the meantime, but no matter how the listing order changed, the new files should wait.
The text was updated successfully, but these errors were encountered: