-
Notifications
You must be signed in to change notification settings - Fork 111
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
old timestamp error in datalad export-to-figshare #3753
Comments
Thanks for the report. Those files come from a tar file generated by For an immediate workaround, you can adjust those files on your system to have a later date (e.g., with |
But I also feel that we better provide safely net within datalad itself, eg verifying that time stamps are in, and if not asking user permission to correct them on their behalf. What do you think? |
No, in my view datalad should not stat every file that it zips and offer to adjust it for the user if it's older than 1980 (or newer than 2107). Looking forward, datalad could use the |
This is done using zipfile.ZipFile's strict_timestamps option, which can be used as soon as Python 3.8 is the minimum supported Python version. Fixes datalad#3753.
What is the problem?
Using
which indeed are pretty old. How did I get a 'kwyk-img/manifest.json' or 'kwyk-img/repositories' file, you might ask?
Well. I had put the kwyk docker image under datalad containers control:
"datalad containers-add -i kwyk-img -u dhub://neuronets/kwyk:latest-cpu kwyk"
and done a few datalad containers-run procedures, such as:
"datalad containers-run -n kwyk --input anat.nii --output "kwyk-output*" -- -m ..."
What version of DataLad are you using (run
datalad --version
)? On what operating system (consider runningdatalad wtf
)?datalad 0.11.7
You asked:
datalad wtf
WTF
configuration <SENSITIVE, report disabled by configuration>
datalad
dataset
dependencies
environment
extensions
git-annex
location
metadata_extractors
system
The text was updated successfully, but these errors were encountered: