You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When viewing the workflow executions table, on the workflow details page, clicking the "Load More" button can cause the table to render items on top of each other.
Note: It is possible that this is caused by the rendering of error messages in failed items.
Expected behavior
The next set of results renders correctly.
Flyte component
Overall
Flyte Setup and Installation scripts
Flyte Documentation
Flyte communication (slack/email etc)
FlytePropeller
FlyteIDL (Flyte specification language)
Flytekit (Python SDK)
FlyteAdmin (Control Plane service)
FlytePlugins
DataCatalog
FlyteStdlib (common libraries)
FlyteConsole (UI)
Other
To Reproduce
Steps to reproduce the behavior:
View the details page for a workflow with enough executions (> 25) to show the Load More button.
Click the button to load more records.
Observe the rendering of the items appended to the list.
Screenshots
The text was updated successfully, but these errors were encountered:
schottra
added
bug
Something isn't working
ui
Admin console user interface
untriaged
This issues has not yet been looked at by the Maintainers
labels
Sep 11, 2020
* feat: launch plans list #none;
* fix: launch plan detail page the top navigation header
* fix: added expected inputs and fixed inputs; #none
* fix: remove radio buttons for view all launch plan versions; #none
Signed-off-by: James <[email protected]>
Describe the bug
When viewing the workflow executions table, on the workflow details page, clicking the "Load More" button can cause the table to render items on top of each other.
Note: It is possible that this is caused by the rendering of error messages in failed items.
Expected behavior
The next set of results renders correctly.
Flyte component
To Reproduce
Steps to reproduce the behavior:
Screenshots
The text was updated successfully, but these errors were encountered: