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

[PR #13785] [MERGED] /api/show: default to empty model_info #76683

New Issue
Closed
opened 2026-05-05 09:19:38 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-05-05 09:19:38 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/13785
Author: @drifkin
Created: 1/19/2026
Status: ✅ Merged
Merged: 1/19/2026
Merged by: @drifkin

Base: main ← Head: drifkin/api-show-compat

📝 Commits (1)

  • e77e8b0 /api/show: default to empty model_info

📊 Changes

2 files changed (+4 additions, -1 deletions)

View changed files

📝 api/types.go (+1 -1)
📝 server/routes.go (+3 -0)

📄 Description

For /api/show, a fully missing model_info field trips up various integrators (including a recent Android Studio integration).

The primary source of missing info tends to come from models with a remote that are also missing other data. It seems better to me to return an empty model_info than making up some other fields within model_info (like saying the architecture is remote or something like that). So this does slightly change /api/show's behavior that possibly someone is relying on, but it seems more important to ensure the field is always there (from a quick sampling integrations seem to be robust to missing fields within it).

Fixes: https://github.com/ollama/ollama/issues/13783

🔄 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/13785 **Author:** [@drifkin](https://github.com/drifkin) **Created:** 1/19/2026 **Status:** ✅ Merged **Merged:** 1/19/2026 **Merged by:** [@drifkin](https://github.com/drifkin) **Base:** `main` ← **Head:** `drifkin/api-show-compat` --- ### 📝 Commits (1) - [`e77e8b0`](https://github.com/ollama/ollama/commit/e77e8b0608401225cc0100f12149ee2507f0a9e6) `/api/show`: default to empty model_info ### 📊 Changes **2 files changed** (+4 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `api/types.go` (+1 -1) 📝 `server/routes.go` (+3 -0) </details> ### 📄 Description For `/api/show`, a fully missing `model_info` field trips up various integrators (including a recent Android Studio integration). The primary source of missing info tends to come from models with a remote that are also missing other data. It seems better to me to return an empty `model_info` than making up some other fields within `model_info` (like saying the architecture is `remote` or something like that). So this does slightly change `/api/show`'s behavior that possibly someone is relying on, but it seems more important to ensure the field is always there (from a quick sampling integrations seem to be robust to missing fields _within_ it). Fixes: https://github.com/ollama/ollama/issues/13783 --- <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-05-05 09:19:38 -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#76683
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?