to @brief-window-55364 Can you point out which flyte exception will face breaking change in this PR written by @glamorous-carpet-83516? Actually, this PR remains the error level as before. We can take a look before the next release https://github.com/flyteorg/flytekit/pull/2671

This diff https://github.com/flyteorg/flytekit/pull/2671/files#diff-932d345851356237c198d139fa9a11d53d68257dc05387e933680ed2e764a50fL155-R147 Before it was

e.error_code

now it's hardcoded as

"ERROR"

cc @glamorous-carpet-83516

what error did you raise in your task?

cc @brief-window-55364 sorry for the ping, I can help today with Kevin

Hey! I've got some time today to work on this and see what's up

yes thank you < 3

Just a month or something late but ended up finding something. https://github.com/flyteorg/flytekit/pull/3059 let me know if you have any questions 🙂

@brief-window-55364 the change LGTM, thanks