Decide whether P6 needs batch execution (/v1/batches) now that KEDA fan-out is going away
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 12/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- kubernetes, typescript
- Domain
- api, backend, distributed-systems
Research direction
This is a design decision, not a code change, and the payload names no source file. Start with the linked #279 resolution and #490, #378 and #401, which the issue says hold the evidence for whether a batch resource is needed. Done is a recorded decision on batch versus async-session fan-out, posted as a comment, ADR or spec section. A spec in docs/specs/ follows only if the answer is yes.
Written by the indexing model from the issue text.
Description
Problem
Batch execution (many independent prompts or leaves submitted together, run with bounded concurrency, results collected later) has no home on P6 and no issue. On the deprecated path the closest thing is async: true fan-out drained by KEDA leaf-worker pods. The #279 resolution decided there is no run noun and no second /v1/runs: user-owned async dispatch is async: true on a session, "or /v1/batches if a real batch appears". That condition is currently undecided, and removing Knative/KEDA removes the only batch-shaped capacity.
Scope
A decision first, then build only if the answer is yes.
- Is there a real batch need? Collect evidence from the #490 responses and from the subagents epic (#378): is fan-out of N independent leaves from one submission enough, or is a batch resource with its own lifecycle needed?
- If a client-side loop over async sessions is enough: document it and close this issue, noting the limits (admission, per-subject quota).
- If a batch resource is needed: design
/v1/batches.- Submission and ownership, per-item state, partial failure and retry, cancel, and result retrieval.
- Bounded concurrency through supervisor admission, and per-subject quota (#360, #391).
- Retention (#390).
- Declarative continuations (#401, option a) may cover the same ground. Decide whether a batch is a degenerate graph.
Acceptance
- A recorded decision (comment, ADR or spec section) on batch versus async-session fan-out.
- If yes: a spec in
docs/specs/and implementation issues, ordered after #386 to #390.
Related
#279 (resolution), #386, #389, #390, #391, #401, #360, #490, #378
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 9
- Avg merge
- 9h 31m
- Merged PRs (30d)
- 139
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from rossoctl/moca
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
rossoctl/moca#421 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
Similar issues
-
bug hacktoberfest help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
libredb/libredb-studio#1941 ·
Maintainers usually reply within 1 day
-
chore other
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
alastair-smith/card-games#308 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
paperclipai/paperclip#17379 ·
Maintainers usually reply within 1 day
-
[good first issue, hacktoberfest] 🏯 Hacktoberfest Task - Add new Anime Quote 626 (good-first-issue)Opencommunity first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
lingdojo/kana-dojo#33040 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
bug mobile ui
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day