mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-08 04:16:03 -05:00
Can't Create Functions - [WinError 32] The process cannot access the file because it is being used by another process #2155
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#2155
Reference in New Issue
Block a user
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?
Originally created by @github-pmj on GitHub (Sep 22, 2024).
Bug Report
Installation Method
.venv
py -m pip install --upgrade open-webui
Environment
**Open WebUI Version:**0.3.23
Ollama (if applicable): 0.3.11
Operating System: Windows 10 22H2
Browser (if applicable): Edge
Confirmation:
Expected Behavior:
The function should be saved
Actual Behavior:
An error is returned and the function is not saved
Description
Bug Summary:
Unable to save a Function from Open-WebUI. After clicking Save, and confirming the action I receive a Win32 error relating to a temporary file being created by the process.:- "[WinError 32] The process cannot access the file because it is being used by another process"
Reproduction Details
Steps to Reproduce:
Attempt to add the sample filter function - providing a name and description (Test, Test).
Click Save and Confirm Action
Error is received
Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Function_Save_Error_Broswer.log
Docker Container Logs:
[Include relevant Docker container logs, if applicable]
Screenshots/Screen Recordings (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Additional Information
[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!