[BUG]: HDF5FeatureStorage raises errors under normal operation #196
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!196
Loading…
Reference in a new issue
No description provided.
Delete branch "update/hdf5-file-and-group-check"
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 an HDF5FeatureStorage, the output log contains ERRORs related to HDF% storage.
This is because the current implementation of H5io does not allow to test if a file contains certain variables. So all the "flow" of checking if the
metaor certain md5 variable exists is done by try/catch blocks.This is a not a good programming practice. For example, an IOError might be due to a failure in the underlying storage, but we will consider it as something "normal because there is no meta variable".
Solution: Implement a function in h5io to test for variables and use it.
Expected Behavior
No errors in the log, no expceptions being raised.
Steps To Reproduce
Environment
Relevant log output
No response
Anything else?
No response
Will add to
latest.incafter #199 is merged so as to not have conflicts.Codecov Report
100.00% <ø> (ø)93.24% <100.00%> (-0.16%)Flags with carried forward coverage won't be shown. Click here to find out more.
93.54% <100.00%> (-2.38%)two more small tests will give us better coverage, @synchon can you do them?
Yeah I am adding that. I intentionally removed the tests to see where it affects.