Strip out calls to nullify_format_instance #1542
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We had problems in the past with the behaviour of HDF5 under forking/parallel reads e.g. #35 #144 01463cc 2550f7c b19510e 36f63d6 and also #1539.
While testing a fix to centralise this check I stripped out the behaviour of
nullify_format_instance
and found that... I couldn't reproduce any of the problems. After some digging, it looks like in HDF5 1.10.5 this problem was fixed by:Which does reading/writing in a stateless way. So, all of these workaround hacks have become redundant.
Possibly.
All the tests I've run appear to pass - this doesn't remove the need for
nullify_format_instance
completely because there seem to be some vestigial problem with Lazy* formats cctbx/dxtbx#245. Does anyone have any memories/documented cases where this broke before to run tests through also? Otherwise, I'd suggest that we put it in and see if any problems come up related to it.