Improve TaskHandler polling strategy

Open
#97 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

  • #130 by @someone — closed without merging

Assessment

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

Research direction

Start by locating TaskHandler and its current polling implementation. Clarify how batchSize, the worker subprocess, and per-task subprocesses should interact, then verify that workers poll indefinitely and each polled task is executed and updated in its own subprocess.

Written by the indexing model from the issue text.

Description

enhancement
  • Add new parameter for batchSize
  • Each worker will have a standalone subprocess to poll indefinitely
    • For each polled task, start a new subprocess to execute and update it
Dominant language
Python
Stars
104
Forks
43
Avg merge
1d 13h
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

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.

More from conductor-oss/python-sdk

All issues in conductor-oss/python-sdk

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.