Forward-merge release/0.5 into main - #1739
Merged
Merged
Conversation
) * fix(entities): hide pending-deletion workspaces from the list API List was returning workspaces that GET/DELETE already 404, leaving Studio in a contradictory state. Filter deletion_stage IS NULL on list, and document --controller-group all instead of changing the runner so Helm API pods keep running without controllers. Signed-off-by: Tyler Bray <tbray@nvidia.com> * chore: sync OpenAPI specs with list-workspaces docstring The FastAPI description for hiding deleting workspaces is part of the public spec, so regenerate the committed OpenAPI copies (and the SDK nmpcontext snapshot) to match. Signed-off-by: Tyler Bray <tbray@nvidia.com> --------- Signed-off-by: Tyler Bray <tbray@nvidia.com>
Contributor
Author
|
SUCCESS - forward-merge complete. |
Contributor
|
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
2 participants
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.
Forward-merge triggered by push to release/0.5 that creates a PR to keep main up-to-date. If this PR is unable to be immediately merged due to conflicts, it will remain open for the team to manually merge. See forward-merger docs for more info.