Hi, can I test the task and workflow verification code that happens during

flytectl register

locally somehow? As of now there are bugs not caught before then what we’d like to have unit testable.

@bland-printer-19092, can you give an example of a bug you're seeing?

I think one example are if the type from a task is mismatched with what is passed on to be returned from a workflow: eg

@task
def mytask() -> B

@workflow
def wf() -> A
    return mytask()

gives some error pointing to A != B

Oh, you mean test locally. That's a great question, but unfortunately we do not expose a local version of the compilation step that happens in remote invocations of any of the clis (e.g. ​`flytectl register files`​, ​`pyflyte register`​, ​`pyflyte run --remote`​, etc). That only happens in the control plane today.

Ok, I found a workaround to run the flyte demo server locally to run the verification for me.