-
Notifications
You must be signed in to change notification settings - Fork 14
LCORE-399: Simplify image building and dependency list. Drop requirements.txt #95
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
base: main
Are you sure you want to change the base?
Conversation
931f79a to
f55d89d
Compare
…ents.txt. The lightspeed-stack image 0.2.0 bundles now all required Python dependencies. Also bump up the lightspeed-stack image to 0.2.0.
f55d89d to
0f8e4ad
Compare
|
@romartin @TamiTakamiya @justjais @ldjebran Could you please take a look? It looks OK to me on face value.. but I'm worried about moving to I also suspect @matysek Do you know if |
|
@romartin I updated the dependency to lightspeed-stack 0.2.0. It is based on llama-stack:0.2.17. Lightspeed-stack in git was updated to 0.2.18 after lightspeed-stack 0.2.0 release. |
|
I am afraid that lightspeed provider will install llama-stack:0.2.16 on top, so we need to bump up to llama-stack:0.2.18 first and aap-rag |
|
@ldjebran thank you for checking. I checked it and fixed adding the providers. I tested building the providers should be now bundled properly without upgrading llama-stack version. |
|
Hey @matysek Sorry for delayed response. Most part of this PR is already out of date, as we're actually using There are other small improvements that still apply, and would be great incorporating. If that's a problem, please let us know and we'll work on it. Thanks in advance! |
Description
LCORE-399: Simplify image building and dependency list. Drop requirements.txt
The lightspeed-stack image 0.2.0 bundles now all required Python dependencies. Also bump up the lightspeed-stack image to 0.2.0.
Testing
Steps to test
Production deployment