Hi, I'm trying out the `wait_for_input` gate node ...
# ask-the-community
e
Hi, I'm trying out the
wait_for_input
gate node with a dummy workflow:
Copy code
from datetime import timedelta

from flytekit import wait_for_input, workflow, task

@task
def list_folders(additional_choice: str) -> list[str]:
    choices = ['a', 'b', 'c', additional_choice]
    print(f'Choices: {choices}')
    return choices


@task
def chosen_folder(choice: str) -> str:
    print(f'chose {choice}')
    return choice


@workflow
def gating_demo(additional_choice: str):
    choices = list_folders(additional_choice=additional_choice)
    choice = wait_for_input("choose-folder", timeout=timedelta(hours=1), expected_type=str)
    chosen_folder(choice=choice)
    choices >> choice
It works locally, but remotely I get an input modal that doesn't allow me to input anything, complaining that:
The requested item could not be found
. Am I doing something wrong? The input doesn't seem to be required (no asterisk) but skipping input also doesn't work (same error).
n
@Yee @Eduardo Apolinario (eapolinario) @Jason Porter this may be a bug in gate nodes
Hi @Ena Škopelja I’m working on documentation for this feature right now! Gonna try and reproduce this
what version of flyte console are you using?
I was able to successfully run your workflow:
e
image.png
n
lemme try using
flytectl demo
cluster
hmm, it also successfully completed in demo cluster
e
Let me try running it again, other than that is there something else I give some more info on?
k
Cc @Dan Rammer (hamersaw)
Cc @James Truong seems like a bug in Ui where it loses the handle
d
Thanks for the tag Ketan, This error seems UI related, happy to help debug if there are any concerns about the backend!
j
Yeah, I will check this. @Jason Porter or @Dan Rammer (hamersaw) Could you make an issue on flyte repo, please? (with tagging me).
e
Hi all, thanks for the help, I think I got it, it was a mismatch between the versions of flyteadmin and UI
On closer inspection it seems that the new helm version
flyte 1.4.0
downgraded my UI to
0.0.10
. To be honest I'm not sure how I ended up with
1.4.1
but deploying by running this:
Copy code
helm upgrade -n flyte \
             -f values-gcp.yaml \
             --install \
             --version v1.4.0 \
             flyte flyteorg/flyte-core
gets me UI
v0.0.10
which fixed the problem but I'm not sure it doesn't still exist in the newer UI version or how I can check that.
y
@Eduardo Apolinario (eapolinario)?
e
looking.
@Ena Škopelja, this is a UI issue that will be fixed in the next Flyte release. We're testing it internally and will ping here when it's out.
e
Thanks a lot for checking it out!
106 Views