Delete GDEX-space copy immediately if it doesn't match original

Open
#26 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

No file or test is named in the issue. Start by finding the code that copies data to GDEX-space and compares it with the original; verify how KeyboardInterrupt is handled. Done means a mismatching copy is deleted immediately and KeyboardInterrupt is intercepted.

Written by the indexing model from the issue text.

Description

Make sure to intercept KeyboardInterrupt too!

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.