Jon Cluce

This looks like it's working for memory.  I'm going through now and adding `n_procs` similarly to control the number of threads  and [adding to the developer...

Almost certainly the same root cause: ```Python Node: cpac_pipeline_benchmark-FNIRT_sub-3699991_ses-1.nii_reg-3_desc-preproc-3_bold_374 Working directory: /ocean/projects/med250004p/shared/regtests/regression_outputs_v1.8.8/benchmark-FNIRT/KKI/sub-3699991/working/pipeline_benchmark-FNIRT/cpac_pipeline_benchmark-FNIRT_sub-3699991_ses-1/_scan_rest_run-1_acq-1/nii_reg-3_desc-preproc-3_bold_374 Node inputs: format_string = sub-3699991_ses-1_task-rest_run-1_acq-1_reg-3_desc-preproc3_bold in_file = /ocean/projects/med250004p/shared/regtests/regression_outputs_v1.8.8/benchmark-FNIRT/KKI/sub-3699991/working/pipeline_benchmark-FNIRT/cpac_pipeline_benchmark-FNIRT_sub-3699991_ses-1/nuisance_regression_space-native_reg-Regressor_3_246/_scan_rest_run-1_acq-1/nuisance_regression/residuals.nii.gz keep_ext = True parse_string = use_fullpath = False Traceback (most...

@sgiavasis do you know if this is still an issue or if it was the same as [this one](https://github.com/FCP-INDI/C-PAC/pull/2011#string%20indices%20must%20be%20integers)?

At a glance, https://github.com/FCP-INDI/C-PAC/blob/266f7a4b7ae18eb91dd406686f4b668c0b25c5f2/CPAC/anat_preproc/anat_preproc.py#L1981-L1996 this NodeBlock is most suspicious to me since it has the same config option as https://github.com/FCP-INDI/C-PAC/blob/266f7a4b7ae18eb91dd406686f4b668c0b25c5f2/CPAC/anat_preproc/anat_preproc.py#L1960-L1975 and has `space-T1w_desc-brain_mask` as an input

This is overdue for an update anyway, but I wonder why it suddenly broke? It looks like that section of code is over 5 years old

I'm putting my notes here for the 1.8.8-dev motion regression: --- I thought I fixed this in #2230, but it's clearly not (fully) resolved; it looks like at least sometimes...

I think adding an `__all__` to [`__init__.py`](https://github.com/nipy/nibabel/blob/4ee2a49cccbd317fedac4be9d21308782d552edf/nibabel/__init__.py) would resolve this warning (by explicitly making the intended symbols public), but I don't know if there's a design reason to not set...

> Does __all__ preserve that? If `__all__` literally includes all the public symbols in `__init__.py`, the resulting namespace from `import nibabel as nib` should be the same. And I should...

I think an `__init__.pyi` is exactly the way to go (and an `__all__` in the `*.pyi` should satisfy the linter). I'll put in a PR shortly.