-
Notifications
You must be signed in to change notification settings - Fork 264
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
ncdump error message when unknown filter is used in 4.8.0 could be better... #1996
Comments
Tagging @DennisHeimbigner |
We have an NC_ENOFILTER err code that I can use. Or were you referring to a log message? |
DennisHeimbigner
added a commit
to DennisHeimbigner/netcdf-c
that referenced
this issue
May 18, 2021
re: Unidata#1996 Improve the error message and location that is reported when reading a filter with a variable that uses a filter that is not available on the reading platform. This requires checking the availability of the filter, recording it, and failing when any attempt is made to read or write that variable. A test case was added for this in tst_filter.sh. Also, LOG level 0 message is generated giving the variable and the filter id. Note that by design if there is no attempt to read or write the variable, then no error is reported; this means that, for example, ncdump -h will list the filter even though it is not actually available. This is important for allowing a user to see the filter details.
See PR #2000 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I do an ncdump on a file with an unknown filter, I get an error message in the middle of the ncdump:
This is because I am using the zstd filter, and ncdump knows nothing of it since it is not currently installed.
But shouldn't the error message be better? How about something like:
"Unknown HDF5 filter encountered, cannot display data for variable var_0"
The text was updated successfully, but these errors were encountered: