-
Notifications
You must be signed in to change notification settings - Fork 73
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
5.7.0 Upgrade - ucar.nc2.NetcdfFiles.openInMemory Errors for BUFR Files #1418
Comments
@Yaqiang, any thoughts on what could be happening here? @jacobwentzib - do you have an example file to help reproduce the error? |
Yes, I need an example file to reproduce the error firstly. |
Thank you for being willing to take a look! |
Got it. I will test ASAP. |
I found the source of the error that the previous code can not make sure only unique categories are included in the protoMessages list. I used the category list to avoid this (maint-5.x...Yaqiang:netcdf-java:develop). It's ok now in my test using MeteoInfoLab script. @jacobwentzib You may test yourself to make sure the change is ok or not with netcdf-java folk repository in my account. |
@Yaqiang Will you be opening a PR for this or are you asking me to do that? And this is wonderful to hear! |
@jacobwentzib I am just not sure if this change could solve all your issues with you data files. So it's better to see you feedback on it. I will open a PR if the feedback is positive. |
Versions impacted by the bug
Recently upgrade to
5.7.0
- Seeing errors when trying to open BUFR files with the strack trace below. I am seeing the following commit: c54869c#diff-87d57326a1634222cff4aaa832d13fd2b0c8578b6965291a81e514c100d6e11b in5.7.0
but little information on the purpose of the change.What went wrong?
Variable 'obs_2' already exists
v
Relevant stack trace
Relevant log messages
No response
If you have an example file that you can share, please attach it to this issue.
If so, may we include it in our test datasets to help ensure the bug does not return once fixed?
Note: the test datasets are publicly accessible without restriction.
Yes
Code of Conduct
The text was updated successfully, but these errors were encountered: