Resume mode for `dcloud insert`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Idea: resume mode, for resuming an upload if it gets cut off.
Not sure how best this could work. Maybe it should track the byte offset of the file it has read (useful for progress bars too) and record that somewhere, maybe in
filename.csv.progress- but only if you pass the--resumeor--continueoption. On subsequent uses of that it could continue from that offset.Not sure if it should protect you against attempting a continue when the file itself has been modified. It could store a hash of the file content, but that would prevent it from resuming against a file that has had data appended to it.
Originally posted by @simonw in https://github.com/simonw/dclient/issues/8#issuecomment-1648550104
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the implementation of dcloud insert and its option parsing, then trace how uploads track progress and handle interruptions. Define the behavior of --resume or --continue, including progress-file storage and modified or appended source files; done means an interrupted upload can continue reliably without changing default behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100