github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 03:18:23 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #22324] issue: new function filter_allowed_access_grants not imported in 2 modules #58365

New Issue
Closed
opened 2026-05-05 23:02:50 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-05 23:02:50 -05:00
Owner
Copy Link

Originally created by @schveiguy on GitHub (Mar 6, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22324

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.8.8

Ollama Version (if applicable)

No response

Operating System

Ubuntu 24.04

Browser (if applicable)

No response

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 provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

Ability to change tool/skill access from private to public, and vice versa.

Actual Behavior

UI appears to allow changing access, but the backend has an error, refreshing the page shows the access permission was not changed.

Steps to Reproduce

  1. Clean install.
  2. Add a simple tool, make the tool private.
  3. Edit the tool, try to change the access to public.
  4. UI claims the access has updated, and reflects public.
  5. Refresh the page.
  6. Edit the tool access again, tool is still private.

Logs & Screenshots

Log in the console:

Image

Log on backend (last few lines):

  File "/usr/local/lib/python3.11/site-packages/fastapi/routing.py", line 426, in app
    raw_response = await run_endpoint_function(
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/fastapi/routing.py", line 314, in run_endpoint_function
    return await dependant.call(**values)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/backend/open_webui/routers/tools.py", line 579, in update_tool_access_by_id
    form_data.access_grants = filter_allowed_access_grants(
                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
NameError: name 'filter_allowed_access_grants' is not defined

Additional Information

In 176f9a7816 a function was introduced in several modules called filter_allowed_access_grants. In two of the modules refactored, the symbol is not imported. This results in a failure to adjust the public/private permission of a tool (or presumably a skill, but I have not tested that).

I believe this is as simple as adding the two imports.

Originally created by @schveiguy on GitHub (Mar 6, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22324 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!). - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.8.8 ### Ollama Version (if applicable) _No response_ ### Operating System Ubuntu 24.04 ### Browser (if applicable) _No response_ ### 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 **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior Ability to change tool/skill access from private to public, and vice versa. ### Actual Behavior UI appears to allow changing access, but the backend has an error, refreshing the page shows the access permission was not changed. ### Steps to Reproduce 1. Clean install. 2. Add a simple tool, make the tool private. 3. Edit the tool, try to change the access to public. 4. UI claims the access has updated, and reflects public. 5. Refresh the page. 6. Edit the tool access again, tool is still private. ### Logs & Screenshots Log in the console: <img width="723" height="43" alt="Image" src="https://github.com/user-attachments/assets/5ff5a104-61e5-4df5-a71a-add76fff4016" /> Log on backend (last few lines): ``` File "/usr/local/lib/python3.11/site-packages/fastapi/routing.py", line 426, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/fastapi/routing.py", line 314, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/backend/open_webui/routers/tools.py", line 579, in update_tool_access_by_id form_data.access_grants = filter_allowed_access_grants( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ NameError: name 'filter_allowed_access_grants' is not defined ``` ### Additional Information In https://github.com/open-webui/open-webui/commit/176f9a781619d836be003d28d53904639cad4128 a function was introduced in several modules called `filter_allowed_access_grants`. In two of the modules refactored, the symbol is not imported. This results in a failure to adjust the public/private permission of a tool (or presumably a skill, but I have not tested that). I believe this is as simple as adding the two imports.
GiteaMirror added the bug label 2026-05-05 23:02:50 -05:00
GiteaMirror commented 2026-05-05 23:02:55 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Mar 6, 2026):

c85afce702

<!-- gh-comment-id:4014172503 --> @Classic298 commented on GitHub (Mar 6, 2026): https://github.com/open-webui/open-webui/commit/c85afce702caebf027d7a8791be9326e71548158
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#58365
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?