llama-stack-mirror/llama_stack/core/server
Ashwin Bharambe 71ead88bce
fix(logging): move module-level initialization to explicit setup calls (#3874)
- Moved environment variable parsing and `setup_logging()` call from
module level to proper initialization points
- Added explicit `setup_logging()` calls in `server.py::create_app()`
and `library_client.py::AsyncLlamaStackAsLibraryClient.__init__()`

Module-level side effects are bad practice and can cause issues with
import order, testing, and circular dependencies. The previous
implementation ran logging setup on every import of the log module,
which is unpredictable and difficult to control.

---------

Co-authored-by: Claude <noreply@anthropic.com>
2025-10-21 11:08:25 -07:00
..
__init__.py chore(rename): move llama_stack.distribution to llama_stack.core (#2975) 2025-07-30 23:30:53 -07:00
auth.py fix(auth): allow unauthenticated access to health and version endpoints (#3736) 2025-10-10 13:41:43 -07:00
auth_providers.py fix: nested claims mapping in OAuth2 token validation (#3814) 2025-10-20 12:34:55 -07:00
quota.py feat(stores)!: use backend storage references instead of configs (#3697) 2025-10-20 13:20:09 -07:00
routes.py chore(cleanup)!: remove tool_runtime.rag_tool (#3871) 2025-10-20 22:26:21 -07:00
server.py fix(logging): move module-level initialization to explicit setup calls (#3874) 2025-10-21 11:08:25 -07:00
tracing.py feat: introduce API leveling, post_training, eval to v1alpha (#3449) 2025-09-26 16:18:07 +02:00