-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to task input tab on the task run page #7547
Comments
Note clarification at #6627 (comment) — I do not believe this issue is following correct assumptions. |
Just want to note as a new user -- this page is misleading, I thought this was a bug or I had misconfigured Orion and my inputs were being lost. I'm testing an ETL and was hoping I could see what table the task was working on based on the inputs shown on this screen. |
I came here because this issue describes what I am observing now, although it is marked as resolved and the solutions are merged. I had to follow all merge requests links and read between the lines to come to the conclusion that for now, only the keys are meaningful and the empty arrays are placeholders (?). This is absolutely not clear from the info modal. It mentions that it can include constants, parameters or other tasks, but no word about whether it means only the keys or whether we should also expect values. In that regard, #8295 does some clarification for other issues, but I don't feel it resolves this issue here. |
This is a really bad design, as a new user, I spent a bit of time scratching my head trying to make sense of what a "Task Input" could be and assuming I was using the tools incorrectly. I see the issue is closed but this feature doesn't work as expected. |
First check
Bug summary
Currently the task run page task input tab shows the correct keys but all values are empty. There's a ticket to track api work for that here: #6627 Until that work is done, we should remove the values shown in the tab and only show the keys so that we're not giving the misleading suggestion that all task inputs are empty arrays.
Reproduction
Create a flow with tasks and run it - go to the task run page and look at the task inputs tab
Error
The [] section is misleading
Browers
Prefect version
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: