-
Notifications
You must be signed in to change notification settings - Fork 263
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
Variable created with ENUM type can't be read after reopen #1308
Comments
as you noted, the problem is occuring in netcdf-c. I suggest opening a ticket at https://github.com/Unidata/netcdf-c |
Thanks @jswhit, would it be possible to transfer the issue to netcdf-c repo? |
@kmuehlbauer other than via copy and paste, I don't know of any way to do that. |
@jswhit Thanks! Within the same organization issues can be transferred to another repo. See: https://docs.github.com/en/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository. If that doesn't work for some reason, I'll copy and paste. |
@kmuehlbauer sorry but the option to transfer an issue to Unidata/netcdf-c is not available for me. |
@jswhit Thanks for trying and no worries. I'll create a new issue over at netcdf-c. |
I've opened a discussion over at netcdf-c Unidata/netcdf-c#2846. |
To report a non-security related issue, please provide:
the version of the software with which you are encountering an issue
netcdf4-python 1.6.5, netcdf-c '4.9.2 of Dec 10 2023 17:23:27 $'
environmental information (i.e. Operating System, compiler info, java version, python version, etc.)
Linux Mint, python 3.12
a description of the issue with the steps needed to reproduce it
When creating variables with enum types like the following:
It seems that
enum_var2
is lost when reopening the file:Checking this it seems, that the variable is not recognized by netcdf-c:
The variable was actually written to the file, as we can see from the h5dump:
I'm assuming that the enum type is not discovered on read as it is in the other group and the variable is silently dropped because of this.
It would be more fitting if an error would be raised when trying to create a variable with a type which is not accessible by the software.
The text was updated successfully, but these errors were encountered: