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

Open
#23 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
tooling

Research direction

Start with the rimport copy and relinking flow described in the report, and reproduce an interrupted copy with Cntrl-C. Determine how the staging file is handled before relinking; done should mean an interrupted or inconsistent copy cannot overwrite the original, with the chosen consistency check covered by tests.

Written by the indexing model from the issue text.

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.

Dominant language
Python
Stars
0
Forks
2
Avg merge
3d 2h
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ESMCI/inputdataTools

All issues in ESMCI/inputdataTools

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.