Skip to content

Commit

Permalink
Remove RELEASE.txt entries from previous releases found in
Browse files Browse the repository at this point in the history
HISTORY-1_14.txt
  • Loading branch information
lrknox committed May 7, 2024
1 parent 74e60cc commit 73f78b4
Showing 1 changed file with 0 additions and 29 deletions.
29 changes: 0 additions & 29 deletions release_docs/RELEASE.txt
Original file line number Diff line number Diff line change
Expand Up @@ -1087,35 +1087,6 @@ Bug Fixes since HDF5-1.14.4 release
- Renamed h5fuse.sh to h5fuse

Addresses Discussion #3791

- Fixed an issue with unmatched MPI messages in ph5diff

The "manager" MPI rank in ph5diff was unintentionally sending "program end"
messages to its workers twice, leading to an error from MPICH similar to the
following:

Abort(810645519) on node 1 (rank 1 in comm 0): Fatal error in internal_Finalize: Other MPI error, error stack:
internal_Finalize(50)...........: MPI_Finalize failed
MPII_Finalize(394)..............:
MPIR_Comm_delete_internal(1224).: Communicator (handle=44000000) being freed has 1 unmatched message(s)
MPIR_Comm_release_always(1250)..:
MPIR_finalize_builtin_comms(154):

- Fixed an issue in h5repack for variable-length typed datasets

When repacking datasets into a new file, h5repack tries to determine whether
it can use H5Ocopy to copy each dataset into the new file, or if it needs to
manually re-create the dataset, then read data from the old dataset and write
it to the new dataset. H5repack was previously using H5Ocopy for datasets with
variable-length datatypes, but this can be problematic if the global heap
addresses involved do not match exactly between the old and new files. These
addresses could change for a variety of reasons, such as the command-line options
provided to h5repack, how h5repack allocate space in the repacked file, etc.
Since H5Ocopy does not currently perform any translation when these addresses
change, datasets that were repacked with H5Ocopy could become unreadable in the
new file. H5repack has been fixed to repack variable-length typed datasets without
using H5Ocopy to ensure that the new datasets always have the correct global heap
addresses.

- Names of objects with square brackets will have trouble without the
special argument, --no-compact-subset, on the h5dump command line.
Expand Down

0 comments on commit 73f78b4

Please sign in to comment.