Consume iterate inputs only on the first step
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by tracing iterate(), aiterate(), and the streaming iterate APIs, then compare how they pass inputs across the first and later steps. Use PR #908 as the existing implementation context and verify first-step halt-before, retries, and resumed failed positions; done means later steps receive empty inputs and the release notes call out the change.
Written by the indexing model from the issue text.
Description
The documented semantics say that inputs are provided to the entry action for a run, but iterate(), aiterate(), and streaming iterate APIs currently pass the same input dictionary to every step.
This can cause later actions to receive unintended entry parameters, allow same-named parameters to alter later behavior, and make sync, async, and streaming execution harder to reason about.
Inputs should be consumed by the first executed step only. Subsequent steps should receive an empty input dictionary, while preserving inputs for first-step halt-before, first-step failure retries, and resumed failed positions.
This issue is tracked by PR #908 and should be called out in the release notes.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 199
- Avg merge
- 5d 16h
- Merged PRs (30d)
- 13
Getting set up
- No 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 apache/burr
-
status/needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
apache/burr#809 · 2 comments ·
Maintainers usually reply within 5 days
-
Streaming Event type, type hint, should support union typePossibly taken @mvanhorn claimed this 178 days ago. Openarea/streaming area/typing good first issue help wanted kind/bug priority/high
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
apache/burr#607 · 12 comments ·
Maintainers usually reply within 5 days
-
area/storage area/ui help wanted kind/documentation priority/low
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
apache/burr#524 · 11 comments ·
Maintainers usually reply within 5 days
-
Add documentation on how to run the Burr UI serverMay be free again A pull request for this issue was closed without being merged. Openarea/ui good first issue kind/documentation priority/low
Difficulty 2/5 Half a day Newbie friendliness 68/100
apache/burr#272 · 5 comments ·
Maintainers usually reply within 5 days
-
status/needs-triage
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Maintainers usually reply within 5 days
Similar issues
-
Layers of type "3D Unknown" and "3D Measured Unknown" are refused, so FileGDB multipatch layers can't be readPossibly taken @aidannewsome claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
quantization
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vllm-project/vllm#59904 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mikf/gallery-dl#9791 ·
-
Speaker custom-fields CSV export returns 404 instead of downloading dataPossibly taken @techvoyager-varun claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
fossasia/eventyay#6151 · 1 comment ·
Maintainers usually reply within 1 day
-
P4: low tooling
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
jeffknupp/association#318 ·