feat: filter startup-failed workspaces#25073
Closed
maschwenk wants to merge 1 commit into
Closed
Conversation
Member
|
This is a good direction, but I feel doing it in a more systematic way, as proposed in #23207, would be more robust. What do you think? |
Contributor
Author
|
@matifali totally! happy to close this PR and you guys plan to solve more systematically |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem:
There is currently no way to filter for running Workspaces that startup failures
Solution:
Adds a backend-supported
startup_failed:<true|false>workspace search filter and wires the Workspaces status dropdown to exposeStartup failedas a synthetic running-state filter.Selecting the new status preserves existing owner, template, and organization filters while applying
status:running startup_failed:true. The search query, SDK filter serialization, API docs, tool help, generated database code, and Storybook/backend coverage are updated together.