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.

Sign up for GitHub

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

Jump to bottom

nc_inq_type fails with NC_INT64 #240

Closed
WardF opened this issue Mar 28, 2016 · 2 comments
Closed

nc_inq_type fails with NC_INT64 #240

WardF opened this issue Mar 28, 2016 · 2 comments
Assignees
@WardF
Labels
status/confirmed status/fix required type/bug
Milestone
4.4.1

Comments

@WardF
Copy link
Member

WardF commented Mar 28, 2016

This was first reported as an error in the netcdf-cxx interface, see

Diagnosis is ongoing.
@WardF WardF added this to the 4.4.1 milestone Mar 28, 2016
@WardF WardF self-assigned this Mar 28, 2016
@WardF
Copy link
Member Author

WardF commented Apr 4, 2016

nc_inq_type() fails when queried with an invalid ncid and a type that is not present in the base nc3 data model. After discussion with @DennisHeimbigner we've decided that this function should return information, as there are other safeguards in place should the user try to use a data type not available to the file they're working with.

WardF added a commit that referenced this issue Apr 5, 2016
@WardF
Modified nc_inq_type so that it will return valid information for val…
6409b11 
…id data types even if the associated ncid doesn't have access to those data types. See #240 for more information.
@WardF
Copy link
Member Author

WardF commented Apr 5, 2016

The fix has been merged into master, closing out.

@WardF WardF closed this as completed Apr 5, 2016
@cptspacemanspiff cptspacemanspiff mentioned this issue Feb 17, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@WardF WardF

Labels
status/confirmed status/fix required type/bug
Projects
None yet
Milestone
4.4.1
Development

No branches or pull requests
1 participant
@WardF