roboflow / roboflow/inference

Get rid of `asyncio` in `workflows` and in some parts of `inference`

Open
#424 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
2.5k
Forks
320
Avg merge
1d 14h
Merged PRs (30d)
133

Description

Search before asking
  • I have searched the Inference issues and found no similar feature requests.
Description

Majority of blocks will be running some computations that do not fit into asycio processing.
We have it only due to compatibility with model manager abstraction from inference.

That state creates lots of issues - for instance, while video processing, in threading environment Active Learning data collection was not working due to asyncio background tasks starvation.

Use case

No response

Additional

No response

Are you willing to submit a PR?
  • Yes I'd like to help by submitting a PR!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by mapping where asyncio is used across workflows and the affected parts of inference, then reproduce the reported threaded video-processing case. Review the model manager compatibility boundary and the Active Learning background-task behavior. Done means the unnecessary asyncio dependency is removed without breaking computation or Active Learning collection.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, computer-vision
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.