BIDS-validator Error 1: [Code 0] INTERNAL ERROR

Hello everyone,

I tried to validate OASIS3 dataset and faced with the problem. Below the error output of the online bids-validator:

Error 1: [Code 0] INTERNAL ERROR


NaN KB |


Maximum call stack size exceeded; please help the BIDS team and community by opening an issue >at ( with the evidence here.


RangeError: Maximum call stack size exceeded at Oi (>validator/_next/static/lcAFkzjYJB3Y9y9R5kJls/pages/index.js:1:1384079) at https://bids->

Looks like that the dataset is too big for the validation, am I right? The dataset description:

  • 8792 Files, 61.31GB
  • 351 - Subjects
  • 565 - Sessions
Available Tasks
  • rest
Available Modalities
  • bold
  • dwi
  • T1w

You can find the output log file attached.controls_errors.txt (418.9 KB)

BIDS-validation is important for me because I am preprocessing this dataset with FMRIPrep. And during bids validation in FMRIPrep, a different error appears:

You are using fMRIPrep-20.0.7, and a newer version of fMRIPrep is available: 20.1.1. Please check out our documentation about how and when to upgrade:
Making sure the input data is BIDS compliant (warnings can be ignored in most cases).

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:213:35)
at process._tickCallback (internal/process/next_tick.js:68:7)

Traceback (most recent call last):
File “/usr/local/miniconda/bin/fmriprep”, line 10, in
File “/usr/local/miniconda/lib/python3.7/site-packages/fmriprep/cli/”, line 319, in main
validate_input_dir(exec_env, opts.bids_dir, opts.participant_label)
File “/usr/local/miniconda/lib/python3.7/site-packages/fmriprep/utils/”, line 146, in validate_input_dir
subprocess.check_call([‘bids-validator’, bids_dir, ‘-c’,])
File “/usr/local/miniconda/lib/python3.7/”, line 341, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command ‘[‘bids-validator’, PosixPath(’/home/elevchenko/OASIS-3/raw_data/controls’), ‘-c’, ‘/tmp/tmpfulb8q86’]’ returned non-zero exit status 3.
Sentry is attempting to send 0 pending error messages

Do you have any ideas why such errors appear?

So the second is a bug with the validator. I have made an issue for it and will update here when a fix has been made and a new version published:

First one is a problem at large that will take a bit longer to figure out. We are seeing the validator run into a variety of limits depending on system as datasets grow in size.

As a heads up the validator called inside fMRIPrep ignores a wide variety of issues during bids-validation:

If its urgent to try and process this through fmriprep before a fix is implemented there is a flag in fmriprep to skip the validator:

1 Like

Thank you very much!

Yes, I think I am gonna use --skip_bids_validation flag because I am pretty sure that is is bids valid.

I don’t know are these problems dependent or related somehow to each other, but I faced with a problem during fMRIPrep usage on this dataset. Detailed description is here: