mirror of
https://github.com/open-webui/open-webui.git
synced 2026-03-11 00:04:08 -05:00
Windows import pwd error
#316
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 @babico on GitHub (Feb 18, 2024).
Bug Report
Description
Bug Summary:
Python
pwdlibrary not in Windows solangchainlibrary can't work after runstart_windows.bat.Steps to Reproduce:
Expected Behavior:
Work
Actual Behavior:
Not work
Environment
Reproduction Details
Confirmation:
Logs and Screenshots
Browser Console Logs:
Additional Information
I found solution on langchain issue page https://github.com/langchain-ai/langchain/issues/17514#issuecomment-1949073290 I change
requirements.txtwith pwdless version, and it just work. I didn't test it properly maybe it has some issue.@jannikstdl commented on GitHub (Feb 19, 2024):
This seems to be a problem with langchain. Either we wait until it gets fixed (in the issue the next release was mentioned) or we set the langchain package to a specific version which will work (
langchain==0.1.6 langchain-community==0.0.19 langchain-core==0.1.23.) I think we should wait sincestart_windowsis still in the making.. @tjbck what do you think?For now you can run start.sh in WSL for Windows. Or
pip unistall langchain langchain-communityandpip install langchain==0.1.6 langchain-community==0.0.19on your machine.@tjbck commented on GitHub (Feb 19, 2024):
I believe it's best if we wait until langchain team sort this out, like @jannikstdl mentioned
start_windows.batis WIP at the moment. I'll keep this issue open and be monitoring this issue closely.@jannikstdl commented on GitHub (Feb 23, 2024):
@babico this should be fixed https://github.com/langchain-ai/langchain/pull/17532 , can you try this again and give feedback?
Before run
pip install --upgrade langchain langchain-communityon your machine / virtual env.@babico commented on GitHub (Feb 23, 2024):
Yes, installing the new version fixed the problem. It worked directly without any problem.
@tjbck commented on GitHub (Feb 24, 2024):
Thanks for the confirmation, I'll close this issue!