<#1103 fix: wrap uv export failures as ImageBuildE...
# flyte-github
a
#1103 fix: wrap uv export failures as ImageBuildError with stderr context Pull request opened by EngHabu Summary
_extract_editables_from_uv_export
runs
uv export --no-emit-project
with
check=True
and lets
CalledProcessError
bubble up unmodified during image build. The default message —
Command '['uv', 'export', '--no-emit-project']' returned non-zero exit status 2.
— drops the captured stderr, which is the only useful piece of information for the user (broken pyproject, lock conflict, etc.). This change catches
CalledProcessError
, includes the stderr/stdout the subprocess emitted, and raises it as
ImageBuildError
so the existing Sentry user-error filter and ClickException handler treat it as user-actionable. Also handles the
uv
-not-installed case with a pointer to install it instead of leaking
FileNotFoundError
. Closes • FLYTE-SDK-3F —
CalledProcessError: Command '['uv', 'export', '--no-emit-project']' returned non-zero exit status 2.
from
_extract_editables_from_uv_export
fixes FLYTE-SDK-3F
Test plan •
test_extract_editables_surfaces_uv_export_failure
— non-zero exit surfaces stderr inside an
ImageBuildError
. •
test_extract_editables_surfaces_missing_uv_binary
—
FileNotFoundError
becomes an
ImageBuildError
pointing at install docs. • Existing
test_get_uv_lock_editable_dependencies_resolves_paths
still passes (12 tests total). •
make fmt
clean. 🤖 Generated with Claude Code flyteorg/flyte-sdk