fix: avoid returning 500 on apps when workspace stopped #11656
Merged
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Currently we return a 500 error when trying to access workspace apps when a workspace is in the stopped state. This is mainly because we weren't wrapping
sql.ErrNoRowswhen no workspace agents are returned. In such cases we want to return a404which makes sense since we can't find the agent we want to route it to; however, this is more an implementation detail and would be confusing to the user in the majority of cases where the agents are "destroyed" due to terraform. I added a400for the case where the workspace is stopped to help the error be a bit more informative to the user.fixes #11106