Actions
Story #4668
closed
As a user i can instruct a sync to abort early, when diskspace is tight
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
It would be nice, if the sync mechanism, after reading the metadata could anticipate the (possibly) needed diskspace, compare that to the available and take appropriate action before starting to download the content units.
Another option might be to add a "fake_sync" or "dry_run_sync" that reports, whether disk space is sufficient.
Actions
.