I am noticing that the error shown in Flyte is not the error that I want to see. Maybe this is only an issue with Flyte on GCP, but it seems good change to actually show the actual error that I care about.

Ohh this seems to be a bug in how the error is unrolled let’s solve it

This one seems more straightforward: I believe

pyflyte-fast-exeecute

is calling

pyflyte-execute

in a subprocess, and simply raising a

CalledProcessError

when the latter fails (due to a missing import in this case). Printing a formatted error message from STDERR of the subprocess might address this issue. There are other issues where say Flytekit is not installed in the image or available in a different venv. Flyte will just report exit code 1 without context about what is actually wrong - Its likely just a k8s/image issue, but unclear how to solve without adding another entrypoint like

sh

to catch and expose the error.