-
Notifications
You must be signed in to change notification settings - Fork 109
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
Validator error with config file, fixed with ignoreSubjectConsistency #1233
Comments
Hi @ins0mniac2, could you please post the contents of your config file here? Does the validator run normally if you do not pass a config file? Did you try running the validator on a different dataset using the config file of the other dataset? |
@sappelhoff , thanks for responding. The validator throws the error whether we explicitly use the "-c" argument to specify the config file or don't use any arguments. We haven't tried it with a different dataset yet. I attached the config file as a zip file -- it wasn't formatted correctly when I pasted the content. |
for convenience, here it is pasted again (after downloading and unzipping your file) {
"ignore": [],
"warn": [],
"error": [],
"ignoredFiles": [
"/docs/**",
"/code/**",
"/ignoredir/**",
"**/*BAD*.nii.gz",
"**/*BAD*.json"
]
} If the error also occurs without the config file, it's likely that the config file is not a problem 🤔 Finding out if the validator throws this issue on other datasets would be the next step. you can try some on https://github.com/bids-standard/bids-examples |
Just to clarify, the error does NOT happen when the config file is not there at all, but does happen with it being there, regardless of whether it's specified on the command line with "-c" or not. I assume even without "-c", it is picking it up as the file is saved under the default name it is looking for ( .bids-validator-config.json ) ? Thanks for posting the content. I need to find the "verbatim" tag in here! |
ahh okay
yes 👍
you can use markdown code blocks:
for example
renders: def fun(a):
return a**2 and
renders: {a: true} even marking a syntax error, because I should have written |
ah, markdown. thanks! based on the above clarification, do you have any further thoughts or trying on another dataset is what you would still suggest next ? |
yes, trying on another dataset would be imporant now. I don't have more ideas unfortunately |
Hey @ins0mniac2 I hope you were able to resolve your issue in the meantime. I am closing this now because we'd need more information to clarify whether this is a bug to be fixed, or something else. Happy to re-open if this is still a problem and if you can provide further info. |
We've also hit this in nipreps/fmriprep#2409 after bumping the bids-validator to the
Command and config
|
@mgxd I don't think this is the same issue. Or if so, it's likely to get buried because it's closed. Do you want to open a new one? |
not sure if it is the same issue, but also not sure if the original issue filed here was resolved (no PR backref), so here is what I get with some elderly validator (well -- all is in container, used for other studies and actually for this one before with less subjects etc -- didn't investigate yet when started to fail)
and the config file used is
|
Using 1.6.2 with no command line options, when using a config file, we get the following error:
Unhandled rejection (
reason: TypeError: Cannot read property 'split' of undefined
at Minimatch.match (/usr/lib/node_modules/bids-validator/node_modules/minimatch/minimatch.js:717:9)
at minimatch (/usr/lib/node_modules/bids-validator/node_modules/minimatch/minimatch.js:107:42)
at Object.ignoredFile (/usr/lib/node_modules/bids-validator/utils/config.js:11:13)
at Function.format (/usr/lib/node_modules/bids-validator/utils/issues/index.js:65:16)
at Function.exceptionHandler (/usr/lib/node_modules/bids-validator/utils/issues/index.js:191:25)
at validateMisc.then.then.then.then.then.then.then.then.catch.err (/usr/lib/node_modules/bids-validator/validators/bids/fullTest.js:217:35)
at processTicksAndRejections (internal/process/task_queues.js:86:5)
).
The error doesn't occur when we add --ignoreSubjectConsistency option to the command line, which we do to avoid the error described here: https://neurostars.org/t/validator-internal-error-due-to-dataset-size/17829
The text was updated successfully, but these errors were encountered: