You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The path of the all_in_one_entrance awel file cannot be read in windows.
What you expected to happen
Thank you for your feedback! To better understand the issue:
1、I observed that Libro reads the USERPROFILE environment variable by default, which on windows is /Users/{Username}, so I tried logging into the Libro lab web page(http://127.0.0.1:5671/) and found that the initial directory was indeed set to /Users/{Username}
2、I took a look at the startup log and it confirmed my point
4、Summary bug speculation: When Windows Libro loads, the path of USERPROFILE is read, the default root path is already /Users/{Username}, but when the api interface is spliced, it is still spliced from the root path of "/", resulting in inconsistent context paths and no awel file
Search before asking
Operating system information
Windows
Python version information
DB-GPT version
latest release
Related scenes
Installation Information
Installation From Source
Docker Installation
Docker Compose Installation
Cluster Installation
AutoDL Image
Other
Device information
Device: GPU
GPU: count 1
GPU Memory: 24G
Models information
LLM: gpt-4o
Embedding: text-embedding-3-small
What happened
The path of the all_in_one_entrance awel file cannot be read in windows.
What you expected to happen
Thank you for your feedback! To better understand the issue:
1、I observed that Libro reads the USERPROFILE environment variable by default, which on windows is /Users/{Username}, so I tried logging into the Libro lab web page(http://127.0.0.1:5671/) and found that the initial directory was indeed set to /Users/{Username}
2、I took a look at the startup log and it confirmed my point
3、Therefore, I guess whether the root path is /Users/{Username}, resulting in the repeated addition of /Users/{Username} to the request api, resulting in the failure to find the awel file. I tried to modify the api address and delete the corresponding part of the USERPROFILE environment variable, and the modified connection is 【http://127.0.0.1:5671/api/contents/.dbgpts/packages/b01e70f9f4fefdf6fba0d1e3339728e9/all-in-one-entrance/all_in_one_entrance?1736912687405】 the file path can be read normally
4、Summary bug speculation: When Windows Libro loads, the path of USERPROFILE is read, the default root path is already /Users/{Username}, but when the api interface is spliced, it is still spliced from the root path of "/", resulting in inconsistent context paths and no awel file
How to reproduce
step to reproduce the behavior:
1、Operation procedure
2、Error Message
3、api Request 404
【GET】http://127.0.0.1:5671/api/contents/Users/{Username}/.dbgpts/packages/b01e70f9f4fefdf6fba0d1e3339728e9/all-in-one-entrance/all_in_one_entrance?1736912687405
Additional context
No response
Are you willing to submit PR?
The text was updated successfully, but these errors were encountered: