-
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
spit out more informative/meaningful msg whenever some file is not actually accessible #197
Comments
This is not an intended validator error it's a language feature inside the validator throwing an un-handled error because it wasn't expecting the git annex formatting. Is this the correct url (datasets.datalad.org/openfmri/ds000206/sourcedata) to fetch the git-annex data to re-create this? |
On Tue, 20 Sep 2016, constellates wrote:
if just to fetch the "structure" do git clone http://datasets.datalad.org/openfmri/ds000206/.git but if you need the load as well, since for now only from tarballs, you datalad install ///openfmri/ds000206 (after datalad/datalad#613 is merged, we will |
Hmm.. After cloning that dataset and running the validator I get the following
And if I run it on the sourcedata like your example I get this.
I'm also not seeing files like this |
On Tue, 20 Sep 2016, constellates wrote:
THANKS for trying! And I am sorry -- I should have looked in detail myself... $> cat ~/bin/bids-validator-docker set -eu but the problem was that I provided relative path to the dataset... providing full path works... hopa:/tmp/datasets.datalad.org/openfmri/ds000206 feel free to close unless you do want to catch that exception and spit |
No worries. I'm glad you figured it out and I got a small introduction to datalad in the process! I'll keep this open for the time being so we can potentially add some more error handling/reporting around our file stat checking. |
world was a much less a better place back then, I think it improved and new dedicated issues would make it even better |
just trying on a git-annex repo without files actually fetched (just to validate the hierarchy, file names), but the error is not really 'informative' -- I wish it could at least say which file it wants to see
FWIW --verbose wasn't helpful much
The text was updated successfully, but these errors were encountered: