<#1075 fix: surface missing src path as ImageBuild...
# flyte-github
a
#1075 fix: surface missing src path as ImageBuildError in copy_files_to_context Pull request opened by EngHabu Summary •
copy_files_to_context
is called for every image layer that needs a file or directory inside the Docker build context (requirements files, pyproject/uv.lock, source folders, etc.). It used to delegate the existence check to
shutil.copy
/
shutil.copy2
and let
FileNotFoundError
bubble all the way up. When the user pointed a layer at a path that didn't exist, the raw traceback ended up in Sentry as an unhandled SDK crash even though it's purely a configuration mistake on the user side. Two changes: 1. Guard the entrypoint with
src.exists()
and raise
ImageBuildError
with an actionable message naming the missing path and the most likely culprits (
with_requirements
,
with_source_folder
,
with_pyproject
).
ImageBuildError
is already filtered from Sentry via
_is_user_error
(#1052), so we stop logging this as an SDK crash. 2. Inside the directory branch, defensively catch
FileNotFoundError
from
shutil.copy2
so that a file that disappears between enumeration (
pm.walk
) and the copy (e.g. a transient venv entry, a broken symlink, or a file removed mid-build) only generates a warning rather than aborting the entire image build. Sentry issues Fixes FLYTE-SDK-2X (
FileNotFoundError: [Errno 2] No such file or directory: '/Users/.../flyte-sdk/.venv/lib/python3.13/dist'
from
shutil.copyfile
inside
copy_files_to_context
) Test plan • New regression test
test_copy_files_to_context_missing_src_raises_image_build_error
covers the missing-src branch • New regression test
test_copy_files_to_context_skips_files_that_vanish_mid_walk
covers the vanish-mid-walk branch • Existing
tests/flyte/imagebuild/test_utils.py
suite still passes •
make fmt
clean 🤖 Generated with Claude Code flyteorg/flyte-sdk