hello 👋 I noticed today that the flyte UI is displaying the incorrect node path name for one of my sub-workflows. in my screenshot you can see the top red box and bottom red box have the same path name. the top one is mislabeled but the bottom one is correct. we're using

flytekit==0.24.0

do you know what the top one should read?

the top one should read

onemodel.models.label_market_share._flyte.label_market_share_standalone

and its signature is

@workflow
def label_market_share_standalone(
    shared_params: dict,
    specific_model_params: typing.Dict[str, pd.DataFrame],
) -> typing.Tuple[Schema, Schema]:

the signature for the bottom one is

@workflow
def msr_standalone(
    shared_params: dict,
    specific_model_params: typing.Dict[str, pd.DataFrame],
) -> Schema:

cc @Jason Porter

I just noticed more errors in the screenshot... the

label-market-share-forecast

node in the first red box should read

onemodel.models.label_market_share._flyte.label_market_share_task

as its path (and it's a python task, not a sub-workflow). its signature is

@task(
    requests=Resources(mem="1Gi", cpu="250m"),
    limits=Resources(mem="2Gi", cpu="1"),
)
def label_market_share_task(
    shared_params: dict,
    parameters: typing.Dict[str, pd.DataFrame],
) -> Schema:

similarly in the bottom red box the

msr-forecast

should read

onemodel.models.msr._flyte.msr_task

as its path (and it's a python task, not a sub-workflow). its signature is

@task(
    cache=True,
    cache_version=environ["VERSION"],
    requests=Resources(mem="1Gi", cpu="250m"),
    limits=Resources(mem="2Gi", cpu="1"),
)
def msr_task(
    shared_params: dict,
    parameters: typing.Dict[str, pd.DataFrame],
) -> Schema:

Hey @Kelsey Messer - what version of flyteconsole are you running? I don't know if it's what's causing the issue here but I know there was a bug that expressed the same way that we fixed around v0.31?

@Dylan Wilder do you know the flyteconsole version? not sure where to find that

Is there a little "i" icon in the top right? If there is that will show you which version you're running; if not then that is likely the problem because it means you have an older version (the "version display" release preceded the fix for the task-name mapping)

ah ok. we're using 0.31.4

Hmmm

@Kelsey Messer can you also post in here the workflow definition.

message has been deleted

should we hop on a call?

@Yee I'm out of laptop now, will be able to look at it near 4pm

all good thanks. just want to make sure we’re on the same page.

I won't have time today but I'm free tomorrow noon-3pm EST if you want to chat then

sounds good

This look similar to what I’ve seen recently. https://flyte-org.slack.com/archives/CTJJLM8BY/p1639739277022300

just fyi we are still investigating this

We are still working on it, it’s a bit of a tricky one 🙂 I’m switching to it tomorrow - while Jason is out.

oh i forgot he was out… all good thank you!

New issue to track this work was created https://github.com/flyteorg/flyte/issues/2117 . It is currently actively in progress. We will update the thread when fix would be published. Thank you a lot for bringing it up and being patient with us 🙂

@Sören Brunk / @Kelsey Messer for you guys to know, this is only a visualization bug.

@Kelsey Messer The partial fix for this visualization issue was just merged to flyte-console. Full fix will require some infrastructure changes, so we can not yet provide expected timeline for the fix. This issue has been resolved in version 0.42.1 🎉 The release is available on GitHub release

thank you!