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

[PR #720] [MERGED] relay model runner error message to client #15575

New Issue
Closed
opened 2026-04-16 05:02:30 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-16 05:02:30 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/720
Author: @BruceMacD
Created: 10/6/2023
Status: ✅ Merged
Merged: 10/12/2023
Merged by: @BruceMacD

Base: main ← Head: brucemacd/failed-llama-runner

📝 Commits (4)

📊 Changes

2 files changed (+42 additions, -15 deletions)

View changed files

📝 cmd/cmd.go (+1 -12)
📝 llm/llama.go (+41 -3)

📄 Description

This got missed in the migration to subprocesses.

Old error displayed in CLI:

failed to start llama runner

New error (will relay the actual error from the model runner):

Error: llama runner failed: out of memory

resolves #630

🔄 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/720 **Author:** [@BruceMacD](https://github.com/BruceMacD) **Created:** 10/6/2023 **Status:** ✅ Merged **Merged:** 10/12/2023 **Merged by:** [@BruceMacD](https://github.com/BruceMacD) **Base:** `main` ← **Head:** `brucemacd/failed-llama-runner` --- ### 📝 Commits (4) - [`44f7c4f`](https://github.com/ollama/ollama/commit/44f7c4f568be6d7d37bee393ebbcef4bb9861d17) give direction to user when runner fails - [`305aa4f`](https://github.com/ollama/ollama/commit/305aa4f1bdd168cecf9a2ca8675e644e14f73b05) Update llama.go - [`c94c87b`](https://github.com/ollama/ollama/commit/c94c87b2753edf8259cd4bd89d2a6dd36b2b9ef9) Update llama.go - [`0cf0284`](https://github.com/ollama/ollama/commit/0cf0284795ac75dd7aaff18f125947b83e6460de) also relay errors from timeout ### 📊 Changes **2 files changed** (+42 additions, -15 deletions) <details> <summary>View changed files</summary> 📝 `cmd/cmd.go` (+1 -12) 📝 `llm/llama.go` (+41 -3) </details> ### 📄 Description This got missed in the migration to subprocesses. Old error displayed in CLI: ``` failed to start llama runner ``` New error (will relay the actual error from the model runner): ``` Error: llama runner failed: out of memory ``` resolves #630 --- <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 05:02:30 -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#15575
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?