tursodatabase / tursodatabase/libsql
If bottomless fails to upload a frame to S3 we stop backuping to S3 until next snapshot
Open
Nobody has claimed this yet.
bottomless
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
This issue has no description.
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 has no body, file path, test, or reproduction details. Start by locating the bottomless S3 upload and backup scheduling code, then reproduce a failed frame upload and identify the expected behavior: later backups should continue without waiting for the next snapshot.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100