Is it a known issue or there is some admin configuration that need to be updated ?
most-gold-65483
04/04/2023, 9:56 AM
NVM, I missed this part.
b
broad-monitor-993
04/04/2023, 8:57 PM
this is still an interesting topic tho @most-gold-65483, I feel like from a UX perspective exceptions raised explicitly in user-defined code should be recoverable. @high-accountant-32689@thankful-minister-83577 thoughts?
broad-monitor-993
04/04/2023, 9:01 PM
looking at some of the workflows I’ve been playing with, I think this is a bug
broad-monitor-993
04/04/2023, 9:01 PM
@most-gold-65483 would you mind copy-pasting a screenshot when you click onf “Show Error”?
m
most-gold-65483
04/04/2023, 9:46 PM
I feel like from a UX perspective exceptions raised explicitly in user-defined code should be recoverable.
Agree with this. User-space exception might be thrown by some library that a task depends on, explicitly catching it and converting to
FlyteRecoverableException
might not be a lot of code but feel verbose, especially if we have to do it for every tasks.
The error
Copy code
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/flytekit/exceptions/scopes.py", line 203, in user_entry_point
return wrapped(*args, **kwargs)
File "/root/retry_workflows/multi_task_pipeline_workflow.py", line 57, in should_fail
raise ValueError("fail")
Message:
fail
User error.