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

Failed to launch debug session in the "Go" devfile

    XMLWordPrintable

Details

    • +
    • Hide

      OCP 4.4

      Server image
      "quay.io/crw/server-rhel8@sha256:868375fdf05487437fd3ff85fb77964839b3b79093ba8840233512cc9003014e"

      Devfile registry image
      "quay.io/crw/devfileregistry-rhel8@sha256:0f3d8c3354a74796d9322ad70d61eaa06394f0e88f4fef5a8d9309891a550c7e"

      Plugin registry image
      "quay.io/crw/pluginregistry-rhel8@sha256:fcdfb694baedb177d60ce76a863253ecef35dc19b6b0ea06694a14dc9c6cb6f1"

       

      Setup:

      Codeready installed using operatorhub UI with enabled
      TLS, OAuth and self-signed certificate options. 

       

      Steps to reproduce:

      • Go to dashboard and create workspace using default "Go" devfile
      • Go inside created workspace
      • Expand root project folder and open the "main.go" file
      • Open debug view and try to launch the "Debug current file" configuration
      • Pay attention to the error popup

       

      Expected behavior:

      Debug session is started

       

      Observed behavior:

      Debug session failed to start

       

       

      Show
      OCP 4.4 Server image "quay.io/crw/server-rhel8@sha256:868375fdf05487437fd3ff85fb77964839b3b79093ba8840233512cc9003014e" Devfile registry image "quay.io/crw/devfileregistry-rhel8@sha256:0f3d8c3354a74796d9322ad70d61eaa06394f0e88f4fef5a8d9309891a550c7e" Plugin registry image "quay.io/crw/pluginregistry-rhel8@sha256:fcdfb694baedb177d60ce76a863253ecef35dc19b6b0ea06694a14dc9c6cb6f1"   Setup: Codeready installed using operatorhub UI with enabled TLS, OAuth and self-signed certificate options.    Steps to reproduce: Go to dashboard and create workspace using default "Go" devfile Go inside created workspace Expand root project folder and open the "main.go" file Open debug view and try to launch the "Debug current file" configuration Pay attention to the error popup   Expected behavior: Debug session is started   Observed behavior: Debug session failed to start    

    Description

      Failed to launch debug session in the "Go" devfile

      Attachments

        1. che-machine-execpdn.log
          2 kB
        2. image-2020-06-25-12-20-16-609.png
          image-2020-06-25-12-20-16-609.png
          222 kB
        3. theia-ideju6.log
          83 kB
        4. vscode-gote0.log
          4 kB

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. CRW-778 Error highlighting doesn't work in the "Go" devfile

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              vsvydenk Valerii Svydenko
              iokhrime Ihor Okhrimenko (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: