Skip to content
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

RangeError: Maximum call stack size exceeded #135

Open
monique2208 opened this issue Jan 7, 2025 · 1 comment
Open

RangeError: Maximum call stack size exceeded #135

monique2208 opened this issue Jan 7, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@monique2208
Copy link

I get the following error when running the validator in verbose mode on a specific dataset (I have not encountered the error anywhere else so far).

error: Uncaught (in promise) RangeError: Maximum call stack size exceeded
        output.push(...formatFiles(subIssues, options))
               ^
    at formatIssues (https://jsr.io/@bids/validator/2.0.1/src/utils/output.ts:67:16)
    at https://jsr.io/@bids/validator/2.0.1/src/utils/output.ts:29:22
    at Array.map (<anonymous>)
    at consoleFormat (https://jsr.io/@bids/validator/2.0.1/src/utils/output.ts:28:43)
    at main (https://jsr.io/@bids/validator/2.0.1/src/main.ts:39:[21](https://data.anc.plus.ac.at/bids-datasets/auditory/nsss_crossmodmarkov/-/jobs/10376#L21))
    at eventLoopTick (ext:core/01_core.js:168:7)
    at async https://jsr.io/@bids/validator/2.0.1/src/bids-validator.ts:3:16

I am not sure what is special about the dataset, but maybe the size of the output is a problem. I have the following warning with non-verbose validation:

/sub-09e35b07bebf/ses-01/meg/sub-09e35b07bebf_ses-01_task-audmarkov_run-01_events.tsv - WARNING: [UNITS_MISSING] No unit specified. Using "Hz" as the default - "Frequency/782". TSV line: 3. (For more information on this HED warning, see https://hed-specification.readthedocs.io/en/latest/Appendix_B.html#units-missing.)    207198 more files with the same issue

There are no 200000 files, I think these are the number of lines the warning applies to.

@effigies effigies added the bug Something isn't working label Jan 7, 2025
@effigies
Copy link
Contributor

effigies commented Jan 7, 2025

Good to know. output.push(...) should be replaceable by a more efficient method. That said, you probably do have 200k+ warnings and I'm not sure verbose output will be particularly helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants