Add task args to prefect UI

[sgoodm]

Currently individual tasks show no task specific data (e.g., input args) via the UI. Adding this would be helpful to diagnose what is running, what has failed, etc.

Note: as mentioned in #111, the fact that we wrap prefect tasks such that they ultimately never look "failed" to prefect might minimize the use of this. Perhaps we could also include a param to display such as the retry count for a function?

[jacobwhall]

Right now, opening an individual task run in the Prefect Orion UI shows the following view:

It looks like the task got an empty list as an input, which is incorrect. I thought this was a bug in the UI.

This is being discussed in PrefectHQ/prefect#6627. As I understand, these "Task Inputs" views in the Prefect Orion UI are not intended to display all the parameter values of that task's function, and instead indicate which parameter values have been passed using futures from upstream tasks:

only relationships between tasks are tracked here

The values should not be empty if the task was passed a value from one or more upstream tasks. In that case, the upstream task run ids would be referenced in the list.

It looks like displaying some of the parameter values is on the roadmap:

In the future, Prefect should do some sort of minimal tracking of the actual data passed between tasks so it can be displayed in the UI. However, that feature should be a separate ticket.

I'll watch the issues in the Prefect repository. For now, I don't think we can monitor task input parameters from the UI.

[jacobwhall]

The folks at Prefect renamed the "Task Inputs" tab to "Task Futures" to better describe the purpose of this view (PrefectHQ/prefect#8295).

Edit: note that the linked PR hasn't been merged yet

[zhen0]

Updates to that tab (as noted in PrefectHQ/prefect#8295) are still a work in progress - I'm trying to make the current purpose of the tab more clear until we can add more info such as task parameters.

[jacobwhall]

@zhen0 thanks for your work on this! I'll keep watching the relevant issues on PrefectHQ/prefect to see how this progresses.