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

Using category list to make sure only unique categories are included #1421

Merged
merged 2 commits into from
Mar 5, 2025

Conversation

Yaqiang
Copy link
Contributor

@Yaqiang Yaqiang commented Mar 5, 2025

Description of Changes

The commit: c54869c#diff-87d57326a1634222cff4aaa832d13fd2b0c8578b6965291a81e514c100d6e11b try to read all messages when the bufr data file contains multiple message categories. But the bug exists when the messages were not arranged in file category by category. So I use category list to make sure only unique categories are included in the protoMessages list to solve the bug.

PR Checklist

@Yaqiang Yaqiang requested a review from lesserwhirls as a code owner March 5, 2025 07:19
@lesserwhirls
Copy link
Collaborator

Thank you @Yaqiang! I've added the file that triggered the initial issue to our extended unit tests. Now that this file can be read (thanks to your fix), it uncovered another unrelated bug. I have a fix for that, so nothing for you to worry about with respect to your PR. But thank you so much!

@lesserwhirls lesserwhirls merged commit aaa267a into Unidata:maint-5.x Mar 5, 2025
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants