github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-06 16:11:34 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[PR #14466] docs: add missing message field to chat streaming final response #19962

New Issue
Open
opened 2026-04-16 07:21:53 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-16 07:21:53 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/14466
Author: @Anandesh-Sharma
Created: 2/26/2026
Status: 🔄 Open

Base: main ← Head: fix-chat-streaming-docs

📝 Commits (1)

  • 374c155 docs: add missing message field to chat streaming final response

📊 Changes

1 file changed (+4 additions, -0 deletions)

View changed files

📝 docs/api.md (+4 -0)

📄 Description

Summary

  • Adds the missing message field to the streaming chat API example's final response
  • The actual API always includes message: { role: "assistant", content: "" } in the final streaming response, but the documentation omitted it
  • This mismatch caused confusion for client library authors implementing strict response parsing (e.g., Pydantic validation)

Fixes #9900

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/ollama/ollama/pull/14466 **Author:** [@Anandesh-Sharma](https://github.com/Anandesh-Sharma) **Created:** 2/26/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix-chat-streaming-docs` --- ### 📝 Commits (1) - [`374c155`](https://github.com/ollama/ollama/commit/374c155b0f8a3dca23c86941df0354ce29afe80a) docs: add missing message field to chat streaming final response ### 📊 Changes **1 file changed** (+4 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/api.md` (+4 -0) </details> ### 📄 Description ## Summary - Adds the missing `message` field to the streaming chat API example's final response - The actual API always includes `message: { role: "assistant", content: "" }` in the final streaming response, but the documentation omitted it - This mismatch caused confusion for client library authors implementing strict response parsing (e.g., Pydantic validation) Fixes #9900 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-16 07:21:53 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#19962
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?