-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[dagit] Show a better error on invalid run filters (#7494)
## Summary Resolves #7219. A handful of changes to handle errors a bit more gracefully on the Runs page. - If filters are set but no matching runs are found, show a message that indicates this. Currently we just say that there are no runs and direct you to use the launchpad, but this isn't helpful if you *do* have runs but none of them match what you've searched. - If a 400 error occurs during the filter request, show an error that represents this. - The current behavior is to show that a GraphQL error has occurred and continue spinning the page spinner indefinitely. This is a pretty bad experience given that the user might not realize that they have provided an invalid filter. - Modify `Loading` to allow a custom error state. This is used in the error state described above. ## Test Plan View Runs page. Set `status:foo`, verify that the new error appears instead of the page spinning forever. Search for valid values, verify that they are retrieved correctly. Search for something that returns no runs, verify that the new empty state appears.
- Loading branch information
Showing
3 changed files
with
61 additions
and
14 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters