ESMCI / ESMCI/inputdataTools

Possibly no safety check when staged file is corrupted with Cntrl-C Interrupt

Open
#23 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
0
Forks
2
Avg merge
3d 2h
Merged PRs (30d)
2

Description

Hello,

I'm not sure if this is a question or a feature request, but I recently tried to rimport a new runoff dataset. Halfway through the first file, I interrupted it with Cntrl-C, and it looks like the file was corrupted in the staging area (about 8GB too small).

If I had permissions for relinking (which thankfully I didn't have) I think the original file would have be overwritten when I ran rimport again.

Is there anyway to have rimport be able to abort the copy operation cleanly? Or maybe have a check with checksums or at least file sizes to ensure consistency before relinking?

Also, Claude had me do `sudo -u cesmdata rm ` to get rid of the corrupted file, which worked (I hope?)

Thanks,
Manish V.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.