Dinesh Yeduguru 7f9b767277 fix: check conda env name using basepath in exec.py (#1301) ... # What does this PR do? check conda env name using basepath in exec.py The current logic for finding conda prefix does a `endswith` check with just the conda env name, but this will cause us to match incorrect if there is a different conda env which ends with same suffix. In my case, i had stack and llama-stack as the two conda envs. ## Test Plan llama stack run ~/.llama/distributions/fireworks/fireworks-run.yaml		2025-02-27 23:07:23 -08:00
..
__init__.py	API Updates (#73)	2024-09-17 19:51:35 -07:00
config_dirs.py	build: format codebase imports using ruff linter (#1028)	2025-02-13 10:06:21 -08:00
dynamic.py	Add an introspection "Api.inspect" API	2024-10-02 15:41:14 -07:00
exec.py	fix: check conda env name using basepath in exec.py (#1301)	2025-02-27 23:07:23 -08:00
image_types.py	feat: add --run to llama stack build (#1156)	2025-02-23 22:06:09 -05:00
model_utils.py	Ensure model_local_dir does not mangle "C:\" on Windows	2024-11-24 14:18:59 -08:00
prompt_for_config.py	build: format codebase imports using ruff linter (#1028)	2025-02-13 10:06:21 -08:00
serialize.py	API Updates (#73)	2024-09-17 19:51:35 -07:00