Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-3416

[KI] Workspace fails to start when VS Code is the editor and the git repository has no devfile

XMLWordPrintable

    • False
    • None
    • False
    • Release Notes
    • Hide
      = New workspaces might fail to start with Visual Studio Code

      pass:[<!-- vale RedHat.TermsErrors = NO -->]

      Currently, starting a new workspace fails when entering the URL of a Git repository that does not contain a devfile and specifying the Technology Preview editor, Visual Studio Code. The error message states the following reason: *Unable to resolve che-code plugins: Not able to find any dev container component in DevWorkspace*. There is currently no workaround for this issue.
      Show
      = New workspaces might fail to start with Visual Studio Code pass:[<!-- vale RedHat.TermsErrors = NO -->] Currently, starting a new workspace fails when entering the URL of a Git repository that does not contain a devfile and specifying the Technology Preview editor, Visual Studio Code. The error message states the following reason: *Unable to resolve che-code plugins: Not able to find any dev container component in DevWorkspace*. There is currently no workaround for this issue.
    • Known Issue
    • Done

      Mario requested a known issue about https://github.com/eclipse/che/issues/21560.

      Although VS Code is a Technology Preview in 3.2 (and we don't normally write known issues for Technology Preview features), considering the fact that it is to become the default editor in 3.3, it makes sense to document this known issue.

              vsvydenk Valerii Svydenko
              rhn-support-mleonov Max Leonov
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: