[BUG]: DataladDataGrabber is not using the WorkDirManager #386
No reviewers
Labels
No labels
CRITICAL
Stale
WIP
bug
concept
coordinate
dataset
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
maintenance
maps
marker
mask
on hold
parcellation
preprocess
question
ready
storage
template-space
triage
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
juaml/junifer!386
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/386"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Is there an existing issue for this?
Current Behavior
When using any DataladBase datagrabber, I observed that it was being cloned in a directory outside what I've set in the workdir manager.
Expected Behavior
The datasets should be cloned within the workdir manager path
Steps To Reproduce
/tmpEnvironment
Relevant log output
No response
Anything else?
Check this:
github.com/juaml/junifer@299b4549c8/junifer/datagrabber/datalad_base.py (L81-L82)Codecov Report
All modified and coverable lines are covered by tests ✅
Additional details and impacted files
100.00% <ø> (ø)Flags with carried forward coverage won't be shown. Click here to find out more.
90.07% <ø> (+0.44%)