rosemarYuan opened a new issue, #795:
URL: https://github.com/apache/flink-agents/issues/795

   ### Search before asking
   
   - [x] I searched in the 
[issues](https://github.com/apache/flink-agents/issues) and found nothing 
similar.
   
   ### Description
   
   ### Search before asking
   
   - [x] I searched in the 
[issues](https://github.com/apache/flink-agents/issues) and found nothing 
similar.
   
   ### Description
   
   The Skills Agent quickstart documentation and the corresponding example code 
use different Ollama model names, so users who follow the doc will pull 
`qwen3:8b` but the code actually requests `qwen3.5:9b`, causing a 
model-not-found error at runtime.
   
   **Documentation** 
(`docs/content/docs/get-started/quickstart/skills_agent.md`):
   - Line 102 (Python code block): `model="qwen3:8b"`
   - Line 160 (Java code block): `.addInitialArgument("model", "qwen3:8b")`
   - Lines 327, 330 ("Prepare Ollama" section): `ollama pull qwen3:8b`
   
   **Actual code**:
   - `python/flink_agents/examples/quickstart/agents/math_agent.py:75`: 
`model="qwen3.5:9b"`
   - 
`examples/src/main/java/org/apache/flink/agents/examples/agents/MathAgent.java:78`:
 `.addInitialArgument("model", "qwen3.5:9b")`
   
   Introduced in PR #707 — doc and code were created in the same PR with this 
inconsistency.
   
   **Suggested fix**: Align the doc to match the code by changing `qwen3:8b` → 
`qwen3.5:9b` in `skills_agent.md`, and add `ollama pull qwen3.5:9b` to the 
"Prepare Ollama" section.
   
   ### Are you willing to submit a PR?
   
   - [x] I'm willing to submit a PR!
   
   ### How to reproduce
   
    -
   
   ### Version and environment
   
    - 
   
   ### Are you willing to submit a PR?
   
   - [x] I'm willing to submit a PR!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to