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

containers-run renders internal subdatasets call #174

Closed
adswa opened this issue Mar 21, 2022 · 1 comment · Fixed by #175
Closed

containers-run renders internal subdatasets call #174

adswa opened this issue Mar 21, 2022 · 1 comment · Fixed by #175

Comments

@adswa
Copy link
Member

adswa commented Mar 21, 2022

This is how a datalad containers-run command looks like:

datalad containers-run  --container-name code/containers/repronim-reproin
subdataset(ok): code/containers (dataset)
subdataset(ok): artwork (dataset)
subdataset(ok): inputs/rawdata (dataset)
[INFO   ] Making sure inputs are available (this may take some time) 
Total:   0%|              

The subdataset result reports should not be rendered.

@adswa
Copy link
Member Author

adswa commented Mar 21, 2022

Looks like this line here might be the culprit:

for sub in curds.subdatasets(return_type='generator'):

adswa added a commit to adswa/datalad-container that referenced this issue Mar 21, 2022
Else, a datalad containers-run command will start by reporting
on all subdatasets in the dataset hierarchy (see datalad#174).
This disables the result renderer in the spirit of
datalad/datalad#6461

Fixes datalad#174
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant