Loading...

XML

Word

Printable

Blocked:
False
Ready:
False
QE Test Coverage:
+
Release Note Text:
Undefined
Workaround:

Workaround Exists
Workaround Description:

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.

Environment

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