<#1039 fix: don't report click.Abort/ClickExceptio...
# flyte-github
a
#1039 fix: don't report click.Abort/ClickException to Sentry Pull request opened by EngHabu Summary •
click.Abort
,
click.exceptions.Exit
, and
click.ClickException
are raised on purpose to display user-facing messages (Ctrl+C, declined prompts, missing dependencies, etc.). They are not crashes and shouldn't generate Sentry issues. • This PR adds a small
_is_user_error
filter at the top of
capture_exception
so they short-circuit before any Sentry init/flush. Closes • FLYTE-SDK-H —
Abort
from
click.confirm
• FLYTE-SDK-G — Docker daemon not reachable • FLYTE-SDK-J — Timed out waiting for Flyte cluster • FLYTE-SDK-W — Timed out waiting for kubeconfig • FLYTE-SDK-Q — Failed to pull image • FLYTE-SDK-5 — Failed to start container Test plan • New unit tests in tests/flyte/test_sentry.py cover the filter (Abort/Exit/ClickException) and verify real errors still report. • Smoke test
flyte start devbox
locally with no docker running — should print the friendly message and not bump Sentry. 🤖 Generated with Claude Code flyteorg/flyte-sdk