Use hexsha to verify junifer-data integrity #434
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!434
Loading…
Reference in a new issue
No description provided.
Delete branch "enh/junifer_data_hexsha"
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?
This PR will implement a hexsha check using junifer data.
This way, if the expected version and hexsha pair do not match in junifer data, an error will be raised.
It might look like an overkill, but junifer-data is now a key component that will definitely affect the computation if modified.