Delete output paths after upload
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.5k
- Forks
- 696
- Avg merge
- 7d 19h
- Merged PRs (30d)
- 2
Description
Currently, you hand off the output file to cog and then none of your code runs and the file gets left in place.
However, there's a class of bug where models can return outputs for previous predictions if some overwrite fails.
This also stops us from using tmp files as output files, since they never get deleted. Cog should probably delete those files (or even give the user a temp directory/overlay to work in).
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
The issue does not name a file or test. Start by tracing how output files are handed off to Cog after prediction, then determine whether cleanup or a temporary working area is the intended direction. Done should prevent uploaded output files from remaining in place and avoid reusing stale outputs after an overwrite failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- backend, machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100