<#1070 fix: raise clear error when flyte.TriggerTi...
# flyte-github
a
#1070 fix: raise clear error when flyte.TriggerTime is used as a task default Pull request opened by EngHabu Summary When a user declares a task with
flyte.TriggerTime
as the default value for a regular parameter: @env.task async def my_task(t: datetime = flyte.TriggerTime): ... deploy fails with an opaque `TypeTransformerFailedError`:
Expected value of type
<class 'datetime.datetime'>
but got
<flyte._trigger._trigger_time object at …>
That happened because
convert_upload_default_inputs
passed the
flyte.TriggerTime
sentinel through to the datetime literal transformer.
flyte.TriggerTime
is only valid as a value inside
flyte.Trigger(inputs=...)
— it cannot be used as a regular task default. This PR detects the sentinel in
convert_upload_default_inputs
and raises a clear
ValueError
explaining the supported pattern, so users get an actionable error at deploy time instead of a transformer crash. Sentry Fixes FLYTE-SDK-2Q Test plan • Added regression test
test_convert_upload_default_inputs_rejects_trigger_time
•
make fmt
• Existing convert / trigger_serde / triggers test suites pass (132 tests) 🤖 Generated with Claude Code flyteorg/flyte-sdk