Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] [Libro Lab] When libro lab is started in windows, the awel file path cannot be loaded correctly #2306

Open
3 of 15 tasks
memoryDemo opened this issue Jan 15, 2025 · 1 comment
Labels
bug Something isn't working Waiting for reply

Comments

@memoryDemo
Copy link

Search before asking

  • I had searched in the issues and found no similar issues.

Operating system information

Windows

Python version information

=3.11

DB-GPT version

latest release

Related scenes

  • Chat Data
  • Chat Excel
  • Chat DB
  • Chat Knowledge
  • Model Management
  • Dashboard
  • Plugins

Installation Information

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}
image

2、I took a look at the startup log and it confirmed my point
image

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
image

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
image

2、Error Message
image

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?

  • Yes I am willing to submit a PR!
@memoryDemo memoryDemo added bug Something isn't working Waiting for reply labels Jan 15, 2025
@Aries-ckt
Copy link
Collaborator

sorry about that, we will check out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Waiting for reply
Projects
None yet
Development

No branches or pull requests

2 participants