<#1079 fix: include underlying cause in upload sig...
# flyte-github
a
#1079 fix: include underlying cause in upload signed-url error message Pull request opened by EngHabu Summary `_upload_single_file`'s generic
except Exception
branch wrapped the underlying error with a static message —
f"Failed to get signed url for {fp}."
— and dropped the cause's text. The chained
__cause__
was still attached, but the surfaced message gave users zero hint about what actually went wrong. For FLYTE-SDK-2H, the chained cause is:
Copy code
RuntimeError: SelectCluster failed for operation=1: validation error:
 - project_id.organization: value length must be at least 1 characters [string.min_len]
i.e. the user's
org
config is empty and the server rejects it. With this PR, the user sees that text instead of a vague "Failed to get signed url" with no actionable info. This is a one-line change to `src/flyte/remote/_data.py`: - raise RuntimeSystemError(type(e).name, f"Failed to get signed url for {fp}.") from e + raise RuntimeSystemError(type(e).name, f"Failed to get signed url for {fp}: {e}") from e The typed
ConnectError
branches above (
NOT_FOUND
/
PERMISSION_DENIED
/
UNAVAILABLE
/ generic) already include
{e.message}
, so this just brings the catch-all branch in line. Sentry issues • FLYTE-SDK-2H — primary target. Cause: server-side
project_id.organization
validation failure (empty org). Fixes FLYTE-SDK-2H Test plan • New regression test in
tests/flyte/remote/test_data_errors.py
covering the empty-org RuntimeError shape from FLYTE-SDK-2H, asserting the surfaced message includes the underlying validation text and
__cause__
is preserved. • Existing parametrized
ConnectError
tests still pass. •
make fmt
clean. • Commit signed (
-s
). 🤖 Generated with Claude Code flyteorg/flyte-sdk