You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
seems to compensate for most invalid configs that arise from the bug
The bug seems to occur when a list is followed by a top-level key (or maybe whenever a list is followed by a key more than one level higher in the hierarchy)
To reproduce
No response
Preconfig
default
abcd-options
anat-only
blank
ccs-options
fmriprep-options
fx-options
monkey
monkey-ABCD
ndmg
nhp-macaque
preproc
rbc-options
rodent
Custom pipeline configuration
No response
Run command
No response
Expected behavior
Generated pipeline YAML matches the pipeline config that was run exactly
Acceptance criteria
Generated pipeline YAML matches the imported pipeline config exactly
CI test added to check for 👆
Screenshots
C-PAC version
v1.8.5-dev
Container platform
Singularity
Docker and/or Singularity version(s)
Singularity v3.8.7-1.el8
Additional context
Longterm, I think it'll be better to move the comments into the node blocks for a SSOT and draw the config comments from the node block comments, rather than generating them from the default template, but I think for now we can just patch this function and add a CI test.
The text was updated successfully, but these errors were encountered:
Describe the bug
This function
C-PAC/CPAC/utils/yaml_template.py
Lines 11 to 316 in 9586d71
As far as I've been able to tell:
C-PAC/CPAC/utils/utils.py
Lines 2301 to 2425 in 9586d71
To reproduce
No response
Preconfig
Custom pipeline configuration
No response
Run command
No response
Expected behavior
Generated pipeline YAML matches the pipeline config that was run exactly
Acceptance criteria
Screenshots
C-PAC version
v1.8.5-dev
Container platform
Singularity
Docker and/or Singularity version(s)
Singularity v3.8.7-1.el8
Additional context
Longterm, I think it'll be better to move the comments into the node blocks for a SSOT and draw the config comments from the node block comments, rather than generating them from the default template, but I think for now we can just patch this function and add a CI test.
The text was updated successfully, but these errors were encountered: