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

[GH-ISSUE #10441] 0.6.7-rc0 makes open-webui unable to access recent history #6864

New Issue
Closed
opened 2026-04-12 18:41:58 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-12 18:41:58 -05:00
Owner
Copy Link

Originally created by @scscgit on GitHub (Apr 28, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/10441

What is the issue?

When upgrading from 0.6.6 to 0.6.7-rc0, open-webui loses the ability for the models to be aware of recent chat history. As this is a patch version bump, I believe semver shouldn't allow for such breaking changes. Please mention the breaking change conflict in the v0.6.7-rc0 tag description.

See the relevant issue, where you were blamed by a contributor:

Relevant log output

https://github.com/user-attachments/files/19931555/-ollama-dockerlog.txt

OS

Windows, Docker

GPU

Nvidia

CPU

AMD

Ollama version

0.6.7-rc0

Originally created by @scscgit on GitHub (Apr 28, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/10441 ### What is the issue? When upgrading from 0.6.6 to 0.6.7-rc0, open-webui loses the ability for the models to be aware of recent chat history. As this is a patch version bump, I believe semver shouldn't allow for such breaking changes. Please mention the breaking change conflict in the [v0.6.7-rc0 tag](https://github.com/ollama/ollama/releases/tag/v0.6.7-rc0) description. See the relevant issue, where you were blamed by a contributor: * https://github.com/open-webui/open-webui/issues/13259 ### Relevant log output ```shell https://github.com/user-attachments/files/19931555/-ollama-dockerlog.txt ``` ### OS Windows, Docker ### GPU Nvidia ### CPU AMD ### Ollama version 0.6.7-rc0
GiteaMirror added the bug label 2026-04-12 18:41:58 -05:00
GiteaMirror commented 2026-04-12 18:42:00 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Apr 28, 2025):

You have set OLLAMA_CONTEXT_LENGTH=-1, which causes ollama to discard all messages other than the last one.

<!-- gh-comment-id:2836010524 --> @rick-github commented on GitHub (Apr 28, 2025): You have set `OLLAMA_CONTEXT_LENGTH=-1`, which causes ollama to discard all messages other than the last one.
GiteaMirror commented 2026-04-12 18:42:00 -05:00
Author
Owner
Copy Link

@scscgit commented on GitHub (Apr 28, 2025):

@rick-github Interesting, I did not set up anything, I only created a new container and left the database to migrate from an old version

<!-- gh-comment-id:2836018833 --> @scscgit commented on GitHub (Apr 28, 2025): @rick-github Interesting, I did not set up anything, I only created a new container and left the database to migrate from an old version
GiteaMirror commented 2026-04-12 18:42:00 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Apr 28, 2025):

Yes, I saw OLLAMA_CONTEXT_LENGTH:-1 in the log and thought it was set in your enviroment (as a default meaning use the ollama default), but checking the code in this commit (424f648632) I see that the default value was changed from 2048 to -1. @drifkin

<!-- gh-comment-id:2836029918 --> @rick-github commented on GitHub (Apr 28, 2025): Yes, I saw `OLLAMA_CONTEXT_LENGTH:-1` in the log and thought it was set in your enviroment (as a default meaning use the ollama default), but checking the code in this commit (https://github.com/ollama/ollama/commit/424f648632c925ce14a75018c4dcab395e035993) I see that the default value was changed from 2048 to -1. @drifkin
GiteaMirror commented 2026-04-12 18:42:01 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Apr 28, 2025):

You can restore history to 0.6.7-rc0 by explicitly setting OLLAMA_CONTEXT_LENGTH=4096 in the docker environment stanza.

<!-- gh-comment-id:2836043531 --> @rick-github commented on GitHub (Apr 28, 2025): You can restore history to 0.6.7-rc0 by explicitly setting `OLLAMA_CONTEXT_LENGTH=4096` in the docker environment stanza.
GiteaMirror commented 2026-04-12 18:42:02 -05:00
Author
Owner
Copy Link

@drifkin commented on GitHub (Apr 28, 2025):

Thanks for reporting. The intent is that -1 means "pick 2048 or 4096 depending on hardware". I'll take a look at the message truncation, will try to get a fix in quickly

<!-- gh-comment-id:2836059252 --> @drifkin commented on GitHub (Apr 28, 2025): Thanks for reporting. The intent is that -1 means "pick 2048 or 4096 depending on hardware". I'll take a look at the message truncation, will try to get a fix in quickly
GiteaMirror commented 2026-04-12 18:42:03 -05:00
Author
Owner
Copy Link

@drifkin commented on GitHub (Apr 28, 2025):

was able to repro, fix coming soon

<!-- gh-comment-id:2836095129 --> @drifkin commented on GitHub (Apr 28, 2025): was able to repro, fix coming soon
GiteaMirror commented 2026-04-12 18:42:04 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Apr 30, 2025):

Fixed with #10451

<!-- gh-comment-id:2842637673 --> @rick-github commented on GitHub (Apr 30, 2025): Fixed with #10451
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 bug
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#6864
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?