[flytepropeller][compiler] Error Handling when Type is not found

[Future-Outlier]

Tracking issue

https://linear.app/unionai/issue/DX-948/flytepropeller-compiler-error-handling-when-type-is-not-found

Why are the changes needed?

When developing JSON IDL, I found that if I registered task to flytepropeller but flytepropeller didn't support the corresponding flyteidl, flyteadmin will crash and the error message from flyteadmin doesn't have a clear error message.

Before

flytekit

flytepropeller

After

We should give a good error message and avoid crashing the propeller.

What changes were proposed in this pull request?

Improve error message when inputType is nil, which means flytepropeller didn't support that type.

How was this patch tested?

single binary and unit test.

Setup process

flytekit: flyteorg/flytekit#2600
flyteidl: #5542
flyte: this branch

from flytekit import task, workflow

@task()
def t5(input: dict) -> dict:
    print(input)
    print("different")
    return input.update({"b": 2}).update({"c": 3})

@workflow
def wf2(input: dict={'d': 1, }) -> dict:
    return t5(input=input)

pyflyte run --remote build/PR/JSON/example.py wf2

Screenshots

Check all the applicable boxes

• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.

Related PRs

#5542

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 36.17%. Comparing base (025296a) to head (4cdce3e).
Report is 129 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5612      +/-   ##
==========================================
+ Coverage   35.89%   36.17%   +0.28%     
==========================================
  Files        1301     1302       +1     
  Lines      109419   109417       -2     
==========================================
+ Hits        39281    39587     +306     
+ Misses      66041    65694     -347     
- Partials     4097     4136      +39     

Flag	Coverage Δ
unittests-datacatalog	51.37% <ø> (ø)
unittests-flyteadmin	55.34% <100.00%> (+1.64%)	⬆️
unittests-flytecopilot	12.17% <ø> (ø)
unittests-flytectl	62.28% <ø> (ø)
unittests-flyteidl	7.09% <ø> (ø)
unittests-flyteplugins	53.31% <ø> (ø)
unittests-flytepropeller	41.73% <ø> (-0.03%)	⬇️
unittests-flytestdlib	55.27% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[eapolinario]

@Future-Outlier , can you fix the lint error?

[wild-endeavor]

@Future-Outlier just wondering does this fail in the same way for pyflyte register? or is it just run?

[Future-Outlier]

@Future-Outlier just wondering does this fail in the same way for pyflyte register? or is it just run?

Both failed
They will go through the same code piece