[Issue]: Todos status argument missing in Tool calling
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- cpp
- Domain
- ai, backend-api-design
Research direction
No source file, test, or reproducible steps are named. Start by reproducing the Qwen3.5-9b tool-calling failure with DeepSeek Harness 0.12 alpha3 and inspect the tool-call handling for the todos status field. Done means identifying whether FastFlowLM or the model output omits or emits invalid statuses, with a minimal reproduction or confirmed settings issue.
Written by the indexing model from the issue text.
Description
Problem Description
Model: Qwen3.5-9b
Tool: DeepSeek Harness 0.12 alpha3
FastFlowLM v1.0.3
I'm new to agent coding, not sure if it's my settings or something with FLM
It's complaining about:
Error: invalid arguments: "todos[1].status" must be one of ["pending","in_progress","completed"]; "todos[2].status" must be one of ["pending","in_progress","completed"]; missing required property "todos[3].status"
Operating System
Windows 11
CPU
AMD Ryzen AI MAX+ 395
GPU
8060s
ROCm Version
v1.0.0
ROCm Component
No response
Steps to Reproduce
No response
(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
rocminfo --support output
Paste output here
Additional Information
No response
- Dominant language
- C++
- Stars
- 1.9k
- Forks
- 156
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 14
Getting set up
- Ships a Dockerfile or Docker Compose file
- No 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 ROCm/FastFlowLM
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ROCm/FastFlowLM#757 ·
Maintainers usually reply within 2 days
-
No valid checkpoint to restore + Max length reached on multi-turn tool calls (Qwen3.6-MoE, NPU)Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ROCm/FastFlowLM#744 · 2 comments ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ROCm/FastFlowLM#741 · 1 comment ·
Maintainers usually reply within 2 days
-
Download timeoutOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ROCm/FastFlowLM#520 · 7 comments ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ROCm/FastFlowLM#434 · 1 comment ·
Maintainers usually reply within 2 days
Similar issues
-
upstream update
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conan-io/conan-center-index#31098 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ml-explore/mlx-c#136 ·
-
bug chart-audit
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day