clockworklabs / clockworklabs/SpacetimeDB
Determine which async worker in `Host::try_init` is failing to drop the `Lockfile` when `try_init` is cancelled
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
Follow-up from #2857 . Some async task spawned by Host::try_init is keeping a handle on the Lockfile alive longer than it should, making Host::try_init not cancel-safe. Find out what task that is, and make it so that it drops the Lockfile immediately when try_init is cancelled, or the database is otherwise shut down.
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 at the Host::try_init entry point and review the cancellation behavior described in follow-up issue #2857. Trace each async task spawned during initialization to identify which retains the Lockfile, then verify that cancellation or database shutdown releases it immediately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100