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

Potential for file corruption in npy_save and npz_save #54

Open
nmcclatchey opened this issue Oct 6, 2019 · 0 comments
Open

Potential for file corruption in npy_save and npz_save #54

nmcclatchey opened this issue Oct 6, 2019 · 0 comments

Comments

@nmcclatchey
Copy link

In the event that fclose() fails, npy_save() will not detect the failure. Depending on how the library is used, this can lead to serious problems. To mitigate this, if fclose() fails, an exception should be thrown.

The same issue exists in npz_save().
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nmcclatchey