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

[PR #15101] [MERGED] app: fix false "out of date" model warnings #15023

New Issue
Closed
opened 2026-04-13 01:08:43 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 01:08:43 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/15101
Author: @BruceMacD
Created: 3/27/2026
Status: ✅ Merged
Merged: 3/27/2026
Merged by: @BruceMacD

Base: main ← Head: brucemacd/app-stale-check

📝 Commits (2)

  • b720a26 app: fix false "out of date" model warnings
  • c2aa0bd Update gotypes.gen.ts

📊 Changes

5 files changed (+27 additions, -37 deletions)

View changed files

📝 app/ui/app/codegen/gotypes.gen.ts (+2 -4)
📝 app/ui/app/src/api.ts (+8 -8)
📝 app/ui/app/src/components/ModelPicker.tsx (+1 -18)
📝 app/ui/responses/types.go (+2 -3)
📝 app/ui/ui.go (+14 -4)

📄 Description

file on disk) against the registry's Ollama-Content-Digest header.
These never matched because PullModel re-serializes the manifest JSON
before writing, producing different bytes than the registry's original.

The fallback comparison (local modified_at vs upstream push time) was
also broken: the generated TypeScript Time class discards the actual
timestamp value, so Date parsing always produced NaN.

Fix by moving the staleness comparison server-side where we have
reliable access to both the local manifest file mtime and the upstream
push time. The /api/v1/model/upstream endpoint now returns a simple
stale boolean instead of raw digests for the frontend to compare.

Also adds User-Agent to the CORS allowed headers for dev mode.

🔄 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/15101 **Author:** [@BruceMacD](https://github.com/BruceMacD) **Created:** 3/27/2026 **Status:** ✅ Merged **Merged:** 3/27/2026 **Merged by:** [@BruceMacD](https://github.com/BruceMacD) **Base:** `main` ← **Head:** `brucemacd/app-stale-check` --- ### 📝 Commits (2) - [`b720a26`](https://github.com/ollama/ollama/commit/b720a264a6a7ec4d6be4331ee2c12ae35291bc95) app: fix false "out of date" model warnings - [`c2aa0bd`](https://github.com/ollama/ollama/commit/c2aa0bdb7470e3bd31444c71044db46511ebad12) Update gotypes.gen.ts ### 📊 Changes **5 files changed** (+27 additions, -37 deletions) <details> <summary>View changed files</summary> 📝 `app/ui/app/codegen/gotypes.gen.ts` (+2 -4) 📝 `app/ui/app/src/api.ts` (+8 -8) 📝 `app/ui/app/src/components/ModelPicker.tsx` (+1 -18) 📝 `app/ui/responses/types.go` (+2 -3) 📝 `app/ui/ui.go` (+14 -4) </details> ### 📄 Description file on disk) against the registry's Ollama-Content-Digest header. These never matched because PullModel re-serializes the manifest JSON before writing, producing different bytes than the registry's original. The fallback comparison (local modified_at vs upstream push time) was also broken: the generated TypeScript Time class discards the actual timestamp value, so Date parsing always produced NaN. Fix by moving the staleness comparison server-side where we have reliable access to both the local manifest file mtime and the upstream push time. The /api/v1/model/upstream endpoint now returns a simple `stale` boolean instead of raw digests for the frontend to compare. Also adds User-Agent to the CORS allowed headers for dev mode. --- <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-13 01:08:43 -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#15023
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?