github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-10 07:43:10 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

feat: Run tools in virtualenv #6384

New Issue
Closed
opened 2025-11-11 16:53:26 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-11 16:53:26 -06:00
Owner
Copy Link

Originally created by @alex780505 on GitHub (Sep 12, 2025).

Check Existing Issues

  • I have searched the existing issues and discussions.

Problem Description

Hi,

I have some tools that are used for requesting data on an Elasticsearch v8.1 cluster, that I cannot upgrade.
Until OWUI version 0.6.27, I could use elasticsearch8 as a requirement to add Elasticsearch v8 client.
Since OWUI version 0.6.28, and the move to Elasticsearch9.1 on OWUI, It's not working anymore since v9.1 introduce Elastic-transport v9+ which is uncompatible with v8.

Desired Solution you'd like

A solution could be to uninstall v9.1 and install v8, but it's not a good practice I think.

A better option could be that each tool run in it's own virtualenv so dependencies aren't an issue, whatever the conflicting packet is.

What do you think of this option ?

Alternatives Considered

No response

Additional Context

No response

Originally created by @alex780505 on GitHub (Sep 12, 2025). ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description Hi, I have some tools that are used for requesting data on an Elasticsearch v8.1 cluster, that I cannot upgrade. Until OWUI version 0.6.27, I could use elasticsearch8 as a requirement to add Elasticsearch v8 client. Since OWUI version 0.6.28, and the move to Elasticsearch9.1 on OWUI, It's not working anymore since v9.1 introduce Elastic-transport v9+ which is uncompatible with v8. ### Desired Solution you'd like A solution could be to uninstall v9.1 and install v8, but it's not a good practice I think. A better option could be that each tool run in it's own virtualenv so dependencies aren't an issue, whatever the conflicting packet is. What do you think of this option ? ### Alternatives Considered _No response_ ### Additional Context _No response_
GiteaMirror commented 2025-11-11 16:53:27 -06:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Sep 12, 2025):

If you're using pip install should be addressed with 3e1b14f570 in dev

@tjbck commented on GitHub (Sep 12, 2025): If you're using pip install should be addressed with 3e1b14f57094637c41b27cc767c6ffd3c0c0ace4 in dev
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
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#6384
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?