<#1052 fix: filter DeploymentError/ImageBuildError...
# flyte-github
a
#1052 fix: filter DeploymentError/ImageBuildError from Sentry Pull request opened by EngHabu Summary
DeploymentError
and
ImageBuildError
are both defined as
RuntimeUserError
subclasses in `flyte/errors.py`: they are raised at deploy / build time to feed an actionable, user-facing message back through the CLI (bad trigger schema, image push permission denied, remote image build failure, etc.). They are not SDK crashes -- but the Sentry filter added in #1039 only short-circuited click exceptions, so every such user error still showed up in Sentry with the user's stack trace. Extend
_is_user_error
to also skip these two classes. Other
RuntimeUserError
subclasses (OOM, retries exhausted, image pull backoff, etc.) are deliberately left in so runtime telemetry is unaffected. Closes • FLYTE-SDK-P --
ImageBuildError: Build failed
from remote image builder • FLYTE-SDK-1P -- `DeploymentError`: TriggerTime input missing from task • FLYTE-SDK-20 --
DeploymentError
for scheduled trigger configuration • FLYTE-SDK-A -- `DeploymentError`: build-image task deploy failure • FLYTE-SDK-9 -- `DeploymentError`: build-image task deploy failure • FLYTE-SDK-8 -- `DeploymentError`: build-image task deploy failure • FLYTE-SDK-7 -- `DeploymentError`: build-image task deploy failure • FLYTE-SDK-6 -- `DeploymentError`: build-image task deploy failure
fixes https://github.com/flyteorg/flyte-sdk/issues/FLYTE-SDK-P
fixes https://github.com/flyteorg/flyte-sdk/issues/FLYTE-SDK-1P
fixes https://github.com/flyteorg/flyte-sdk/issues/FLYTE-SDK-20
Test plan • New unit tests in
tests/flyte/test_sentry.py
cover the two new filtered types. • Existing click filter tests still pass. •
make fmt
clean. 🤖 Generated with Claude Code flyteorg/flyte-sdk