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 #15525] [CLOSED] server: show pull summary after resolving manifest #77481

New Issue
Closed
opened 2026-05-05 10:08:55 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-05-05 10:08:55 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/15525
Author: @samrusani
Created: 4/12/2026
Status: ❌ Closed

Base: main ← Head: server/pull-manifest-summary

📝 Commits (1)

  • d0bf7ed server: show pull summary after resolving manifest

📊 Changes

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

View changed files

📝 server/images.go (+3 -0)

📄 Description

Summary

  • After pulling the manifest, displays the resolved model name, number of files, and total download size before starting layer downloads
  • Uses the existing format.HumanBytes helper for human-readable sizes
  • Single status line addition in PullModel(), works for both standard and tensor transfer paths

Example output:

pulling manifest
pulling llama3.2:latest with 9 files (4.9 GB total)
pulling 68e0ec597aee: 100% ...

Fixes #15275

Test plan

  • Verified existing tests use strings.Contains assertions (not exact output matching), so the new status line does not break server/internal/registry/server_test.go or server/routes_test.go
  • Manual test: ollama pull <model> should show the summary line between "pulling manifest" and the first layer download

🤖 Generated with Claude Code

🔄 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/15525 **Author:** [@samrusani](https://github.com/samrusani) **Created:** 4/12/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `server/pull-manifest-summary` --- ### 📝 Commits (1) - [`d0bf7ed`](https://github.com/ollama/ollama/commit/d0bf7edb5bd2a2b2cea0a15707cfd7d324c21ad3) server: show pull summary after resolving manifest ### 📊 Changes **1 file changed** (+3 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `server/images.go` (+3 -0) </details> ### 📄 Description ## Summary - After pulling the manifest, displays the resolved model name, number of files, and total download size before starting layer downloads - Uses the existing `format.HumanBytes` helper for human-readable sizes - Single status line addition in `PullModel()`, works for both standard and tensor transfer paths Example output: ``` pulling manifest pulling llama3.2:latest with 9 files (4.9 GB total) pulling 68e0ec597aee: 100% ... ``` Fixes #15275 ## Test plan - [x] Verified existing tests use `strings.Contains` assertions (not exact output matching), so the new status line does not break `server/internal/registry/server_test.go` or `server/routes_test.go` - [ ] Manual test: `ollama pull <model>` should show the summary line between "pulling manifest" and the first layer download 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <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 10:08:55 -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#77481
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?