Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix the HL H5TB fill-info #5332 #5333

Merged
merged 6 commits into from
Feb 25, 2025
Merged

Conversation

byrnHDF
Copy link
Contributor

@byrnHDF byrnHDF commented Feb 24, 2025

Changed the test values to be unique to verify correct values are used.
Added a h5dump test to test_table so it could verify that fill values are correct.

Fixes #5332

@byrnHDF byrnHDF added Priority - 1. High 🔼 These are important issues that should be resolved in the next release Component - High-Level Library Code in the hl directory Type - Bug / Bugfix Please report security issues to help@hdfgroup.org instead of creating an issue on GitHub labels Feb 24, 2025
@byrnHDF byrnHDF self-assigned this Feb 24, 2025
Copy link
Member

@hyoklee hyoklee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please update release documentation.

hyoklee
hyoklee previously approved these changes Feb 25, 2025
Copy link
Member

@hyoklee hyoklee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://my.cdash.org/viewTest.php?onlypassed&buildid=2833655

It would be nice if you include GH Actions for i386 as well in this PR.

@byrnHDF
Copy link
Contributor Author

byrnHDF commented Feb 25, 2025

https://my.cdash.org/viewTest.php?onlypassed&buildid=2833655

It would be nice if you include GH Actions for i386 as well in this PR.

i386 action already exists - just needed to remove special check for this failure

bmribler
bmribler previously approved these changes Feb 25, 2025
@@ -2676,6 +2686,13 @@ H5TBdelete_field(hid_t loc_id, const char *dset_name, const char *field_name)
if (H5TB_attach_attributes(table_title, loc_id, dset_name, nfields, tid_3) < 0)
goto out;

if (NULL == (src_offset = (size_t *)malloc((size_t)nfields * sizeof(size_t))))
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It doesn't look like src_offset is used below here? The lines below are still assigning member_offset = H5Tget_member_offset(tid_3, (unsigned)i);

Copy link
Contributor Author

@byrnHDF byrnHDF Feb 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like I didn't save the change.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks similar to the other cases where the H5TBget_field_info() call is needed, but it's hard to say. Would probably need to have a specific test for it to check.

@byrnHDF byrnHDF dismissed stale reviews from bmribler and hyoklee via ac0b71c February 25, 2025 18:02
@lrknox lrknox merged commit b26089a into HDFGroup:develop Feb 25, 2025
77 checks passed
@byrnHDF byrnHDF deleted the develop-tb-data branch February 26, 2025 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component - High-Level Library Code in the hl directory Priority - 1. High 🔼 These are important issues that should be resolved in the next release Type - Bug / Bugfix Please report security issues to help@hdfgroup.org instead of creating an issue on GitHub
Projects
None yet
Development

Successfully merging this pull request may close these issues.

HL TB examples are incorrect
5 participants