Dataset write does not write if file was written and then deleted.
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 459
- Forks
- 359
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 73
Description
Step to reproduce:
- do a loop
- finish the loop
- delete the file on disk
Then try to save agin:
- data.write()
The file won't re appear on disk.
@alexcjohnson is there a design idea behind this behaviour that I can't see ?
@everynodyelse Is this the wanted behaviour ?
Do we want a way to force save anyway ?
Contributor guide
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 reproducing the sequence in the issue: complete a loop, delete the dataset file, then call data.write(). Trace the Dataset write entry point and existing persistence tests, and clarify whether a deleted file should be recreated; done means the intended behavior is documented and covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100