<#1056 fix: filter InitializationError from Sentry...
# flyte-github
a
#1056 fix: filter InitializationError from Sentry Pull request opened by EngHabu Summary •
InitializationError
is what the SDK raises when the user runs a CLI command (or calls
flyte.deploy
/
flyte.upload_file
/ etc.) without having first called
flyte.init()
or
flyte.init_from_config()
. The exception's message is a clear, actionable instruction to the user — not a crash report worth paging on. • Sentry has collected several of these reports already (see linked issues below). Add
InitializationError
to the existing user-error filter in
flyte._sentry
alongside
DeploymentError
and
ImageBuildError
. Sentry issues Fixes FLYTE-SDK-7 (InitializationError on
flyte deploy
) Fixes FLYTE-SDK-8 (InitializationError during
upload_file
) Test plan • New
test_capture_exception_skips_initialization_error
unit test • Full
tests/flyte/test_sentry.py
suite passes flyteorg/flyte-sdk