llama-stack-mirror

mirror of https://github.com/meta-llama/llama-stack.git synced 2025-10-07 12:47:37 +00:00

History

ehhuang 426cac078b Some checks failed SqlStore Integration Tests / test-postgres (3.12) (push) Failing after 0s Details Integration Auth Tests / test-matrix (oauth2_token) (push) Failing after 0s Details Test Llama Stack Build / generate-matrix (push) Successful in 3s Details Integration Tests (Replay) / Integration Tests (, , , client=, ) (push) Failing after 4s Details Vector IO Integration Tests / test-matrix (push) Failing after 3s Details Test External Providers Installed via Module / test-external-providers-from-module (venv) (push) Has been skipped Details Test Llama Stack Build / build-single-provider (push) Failing after 3s Details SqlStore Integration Tests / test-postgres (3.13) (push) Failing after 6s Details Test Llama Stack Build / build-custom-container-distribution (push) Failing after 3s Details Test Llama Stack Build / build-ubi9-container-distribution (push) Failing after 3s Details Python Package Build Test / build (3.12) (push) Failing after 3s Details Python Package Build Test / build (3.13) (push) Failing after 2s Details Test External API and Providers / test-external (venv) (push) Failing after 4s Details Unit Tests / unit-tests (3.13) (push) Failing after 3s Details API Conformance Tests / check-schema-compatibility (push) Successful in 11s Details Test Llama Stack Build / build (push) Failing after 3s Details Unit Tests / unit-tests (3.12) (push) Failing after 4s Details UI Tests / ui-tests (22) (push) Successful in 44s Details Pre-commit / pre-commit (push) Successful in 1m24s Details chore: use uvicorn to start llama stack server everywhere (#3625 ) # What does this PR do? https://github.com/llamastack/llama-stack/pull/3462 allows using uvicorn to start llama stack server which supports spawning multiple workers. This PR enables us to launch >1 workers from `llama stack run` (will add the parameter in a follow-up PR, keeping this PR on simplifying) by removing the old way of launching stack server and consolidates launching via uvicorn.run only. ## Test Plan ran `llama stack run starter` CI		2025-10-06 14:27:40 +02:00
..
__init__.py	chore(rename): move llama_stack.distribution to llama_stack.core (#2975 )	2025-07-30 23:30:53 -07:00
auth.py	refactor(logging): rename llama_stack logger categories (#3065 )	2025-08-21 17:31:04 -07:00
auth_providers.py	feat: Add Kubernetes auth provider to use SelfSubjectReview and kubernetes api server (#2559 )	2025-09-08 11:25:10 +02:00
quota.py	refactor(logging): rename llama_stack logger categories (#3065 )	2025-08-21 17:31:04 -07:00
routes.py	feat: introduce API leveling, post_training, eval to v1alpha (#3449 )	2025-09-26 16:18:07 +02:00
server.py	chore: use uvicorn to start llama stack server everywhere (#3625 )	2025-10-06 14:27:40 +02:00
tracing.py	feat: introduce API leveling, post_training, eval to v1alpha (#3449 )	2025-09-26 16:18:07 +02:00