Skip to content

Investigate 302 connecting to workspace that is stopped #262

@code-asher

Description

@code-asher

image_720

The plugin starts a workspace (if needed) and waits until the workspace is ready before connecting, which makes me wonder:

  • Is it not following redirects?
  • If not, should it?
  • Or is there just a bug in this start and wait logic?
  • Why does this error not display the request details? I thought we added that.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions