Change the way on how workflows runs code remotely
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 319
- 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
We have now run() and run_remotely() blocks methods. Additionally, there is only one single flag deciding on local vs remote run
Probably better idea would be to have only run() and be able to decide on local vs remote run at the step level, based on environment configuration.
Original idea: https://github.com/roboflow/inference/pull/343#discussion_r1585670447
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
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 workflow block methods run() and run_remotely(), then read the design discussion in PR #343 linked from the issue. Clarify how environment configuration should select local versus remote execution at each step; done means the separate remote method is replaced by the agreed step-level behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100