You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When registering a collection using the DataladDataProvider, the size is always unset.
That's because the size-setting method crawls through the dataset and builds a sum of the size of all files (skipping directories and symlinks), but because the content of all the files is replaced by symbolic links, not files are found.
It seems Datalad might have a better size-fetching method, it would need to be included as part of the DataProvider API (provider_file_attributes(userfile) maybe?).
The text was updated successfully, but these errors were encountered:
When registering a collection using the DataladDataProvider, the size is always unset.
That's because the size-setting method crawls through the dataset and builds a sum of the size of all files (skipping directories and symlinks), but because the content of all the files is replaced by symbolic links, not files are found.
It seems Datalad might have a better size-fetching method, it would need to be included as part of the DataProvider API (
provider_file_attributes(userfile)
maybe?).The text was updated successfully, but these errors were encountered: