github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 19:08:59 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #14089] issue: RELEVANCE_THRESHOLD not resettable #17137

New Issue
Closed
opened 2026-04-19 22:53:25 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-19 22:53:25 -05:00
Owner
Copy Link

Originally created by @brainboutique on GitHub (May 20, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14089

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.6.10

Ollama Version (if applicable)

v0.6.5

Operating System

Linux

Browser (if applicable)

Chrome

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have listed steps to reproduce the bug in detail.

Expected Behavior

On /admin/settings, I would expect the RELEVANCE_THRESHOLD to be resettable to "null" (not 0).

Reason: I suspect that a tool call returns a unknown relevance and therefore is skipped while re-ranking

Actual Behavior

Keeps old value.

Steps to Reproduce

  1. Open settings
  2. Clear out field
  3. Save
  4. F5 to reload OR check server response in developer tools.

Logs & Screenshots

/api/v1/retrieval/config/update

Request payload (as copied from developer console)
{
"status": true,
...
"RELEVANCE_THRESHOLD": null,
...
}

Response payload (as copied from developer console)

{
"status": true,
...
"RELEVANCE_THRESHOLD": 0.0,
...
}

Additional Information

No response

Originally created by @brainboutique on GitHub (May 20, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/14089 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.10 ### Ollama Version (if applicable) v0.6.5 ### Operating System Linux ### Browser (if applicable) Chrome ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have listed steps to reproduce the bug in detail. ### Expected Behavior On /admin/settings, I would expect the RELEVANCE_THRESHOLD to be resettable to "null" (not 0). Reason: I suspect that a tool call returns a unknown relevance and therefore is skipped while re-ranking ### Actual Behavior Keeps old value. ### Steps to Reproduce 1. Open settings 2. Clear out field 3. Save 4. F5 to reload OR check server response in developer tools. ### Logs & Screenshots /api/v1/retrieval/config/update Request payload (as copied from developer console) { "status": true, ... "RELEVANCE_THRESHOLD": null, ... } Response payload (as copied from developer console) { "status": true, ... "RELEVANCE_THRESHOLD": 0.0, ... } ### Additional Information _No response_
GiteaMirror added the bug label 2026-04-19 22:53:25 -05:00
GiteaMirror commented 2026-04-19 22:53:27 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (May 20, 2025):

r_score must be a float.

<!-- gh-comment-id:2894876807 --> @tjbck commented on GitHub (May 20, 2025): r_score must be a float.
GiteaMirror commented 2026-04-19 22:53:27 -05:00
Author
Owner
Copy Link

@brainboutique commented on GitHub (May 20, 2025):

@tjbck then how to disable threshold filtering? "0" apparently has different semantics.

<!-- gh-comment-id:2894937448 --> @brainboutique commented on GitHub (May 20, 2025): @tjbck then how to disable threshold filtering? "0" apparently has different semantics.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
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/open-webui#17137
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?