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

("Quarkus" workspace) Debug stops at the breakpoint only if breakpoint set up during debug session

    XMLWordPrintable

Details

    • Workaround Exists
    • Hide

      As a workaround you can use one of this way:
      1. Set a breakpoint after starting the debugger
      2. If the debugger is already started you can remove and set again the breakpoint
      If you do one of this way, the debugger should stop on the line with the breakpoint.

      Show
      As a workaround you can use one of this way: 1. Set a breakpoint after starting the debugger 2. If the debugger is already started you can remove and set again the breakpoint If you do one of this way, the debugger should stop on the line with the breakpoint.
    • +

    Description

      Environment

      • OCP 4.6 cluster
      • Codeready deployed by operatorhub
      • TLS, oAuth
      • list of the used images in the attachments (used-images.md)

      Steps to reproduce

      • Create workspace using the "Quarkus" default devfile
      • Go inside created workspace and open the "GreetingResource.java"
      • Run the "1. Package the application" predefined command
      • Run the "2. Start Quarkus in devmode (hot deploy + debug)" predefined command
      • Open the deployed sample in the preview widget (using displayed notification)
      • Go to the "GreetingResource.java" editor tab and set breakpoint to the 21-th row
      • Open the debug panel and run the "Attach to Remote Quarkus App" debug configuration
      • Go to preview widget and type URL for trigger breakpoint <root-url>/hello/greeting/test-request and press "Enter" button
      • Pay attention that breakpoint is not triggered
      • Remove breakpoint and set it again to the 21-th row
      • Refresh preview widget
      • Pay attention that breakpoint is triggered

      Expected behavior
      Breakpoint is triggered

      Observed behavior
      Breakpoint is triggered only after resetting it during debug session

      Attachments

        1. screencast.mp4
          475 kB
        2. used-images.md
          7 kB

        Activity

          People

            tdancs Tibor Dancs
            iokhrime Ihor Okhrimenko (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: