tursodatabase / tursodatabase/libsql
Bug with schema migration when tasks status do not reflect the job status
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
We found a bug with the schema migration scheduler where a job with two tasks was in status Enqueued where the tasks were in status DryRunSuccess and RunSuccess. The scheduler would get stuck because it was expecting tasks in status Enqueue and found none. The scheduler should be more resilient to this, and update the job status if a tasks is found in an unexpected state.
This is likely due to a crash.
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 names no files, tests, or entry points. Start by locating the schema migration scheduler and its job/task status handling, then reproduce a job whose task statuses differ from the expected state. Done means the scheduler does not remain stuck and updates the job status when it encounters an unexpected task state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100