paritytech / paritytech/try-runtime-cli
Remove DB operations in async code
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
you don't have to do it in this PR but worth investing whether it makes things faster or not.
Ideally, we shouldn't do any DB operations in async code it might fuckup the async scheduler in tokio
Originally posted by @niklasad1 in https://github.com/paritytech/substrate/pull/14057#discussion_r1181570805
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 locating the asynchronous code paths and their database operations in the try-runtime-cli repository, then determine how those operations interact with the Tokio scheduler. The issue provides no file or test entry point, so first map the affected code and establish how to verify scheduler safety. Done means the relevant async paths avoid database operations without changing their intended behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain, databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100