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
I ran datalad meta-extract on a file that wasn't yet present locally. Just as the docstring said, the command obtained the file content prior to performing the extraction. However, I noticed that there was no information about the fact that the file was retrieved (just a short-lived progress bar that disappeared).
DataLad-core commands that call other intermediate commands (e.g., datalad run's internal get) summarize the actions they took - is it a conscious decision to not have such summaries or INFO messages in metalad output?
The text was updated successfully, but these errors were encountered:
I ran
datalad meta-extract
on a file that wasn't yet present locally. Just as the docstring said, the command obtained the file content prior to performing the extraction. However, I noticed that there was no information about the fact that the file was retrieved (just a short-lived progress bar that disappeared).DataLad-core commands that call other intermediate commands (e.g.,
datalad run
's internalget
) summarize the actions they took - is it a conscious decision to not have such summaries or INFO messages in metalad output?The text was updated successfully, but these errors were encountered: