llama-stack-mirror

mirror of https://github.com/meta-llama/llama-stack.git synced 2025-12-03 18:00:36 +00:00

History

Ashwin Bharambe 8b878e9d48 Some checks failed SqlStore Integration Tests / test-postgres (3.12) (push) Failing after 1s Details Integration Auth Tests / test-matrix (oauth2_token) (push) Failing after 1s Details SqlStore Integration Tests / test-postgres (3.13) (push) Failing after 1s Details Integration Tests (Replay) / Integration Tests (, , , client=, ) (push) Failing after 4s Details Pre-commit / pre-commit (push) Failing after 4s Details Unit Tests / unit-tests (3.12) (push) Failing after 7s Details Unit Tests / unit-tests (3.13) (push) Failing after 5s Details Vector IO Integration Tests / test-matrix (push) Failing after 6s Details fix(ci): export UV_INDEX_STRATEGY to current shell before running uv sync (#4019 ) Fixes #4017 follow-up issue where UV_INDEX_STRATEGY was only exported to GITHUB_ENV but not to the current shell. The commit `e0bb7529` fixed the empty string issue but introduced a new bug: UV_INDEX_STRATEGY was only exported to GITHUB_ENV (for subsequent steps), not to the current shell environment. Since uv sync runs in the same step, it never saw the variable. This caused all CI runs on release-0.3.x to fail with dependency resolution errors like: ``` setuptools was found on https://test.pypi.org/simple/, but not at the requested version. A compatible version may be available on PyPI. Use --index-strategy unsafe-best-match. ``` This fix adds `export UV_INDEX_STRATEGY=unsafe-best-match` to make the variable available in the current shell before running uv commands. Note: Main branch doesn't hit this bug because UV_EXTRA_INDEX_URL is only set on release branches.		2025-11-01 12:54:19 -07:00
..
action.yml	fix(ci): export UV_INDEX_STRATEGY to current shell before running uv sync (#4019 )	2025-11-01 12:54:19 -07:00