apache / apache/grails-intellij-plugin

Debug issue after updating to Grails 5: lose the ability to set breakpoints again after run

Open
#389 0 comments 0 reactions 0 assignees View on GitHub
bug imported-from-youtrack
Dominant language
Java
Stars
17
Forks
4
Avg merge
5d 15h
Merged PRs (30d)
4

Description

This ticket is based on support feedback.

I am having issues where the Debug gets out of sync and I cannot set breakpoints. After I restart the debugger then I can set breakpoints. After I run my code once, I lose the ability to set breakpoints again. I have noticed this behavior since I updated to Grails 5 roughly a year ago but I kept hoping IDE updates would resolve the issue. This hasn't happened yet and its driving me crazy and need to get this resolved. I have attached screen recording that demonstrates the issue.

I seem to notice this issue only happen when Groovy closures are involved and even more with multiple nested closures. I am running code that does not have closures they I have yet to see this issue. Please let me know if any additional information is needed

## **Scenario:**

1. Set breakpoints

2. Run debug session

_⚠️ attachment `image.png` was not included in the export_{width=81px}

3. When debug session is finished, click to the breakpoint from step 1

**Expected result:** you can click to the breakpoint to remove and add it again.

**Actual result:** the breakpoint becomes [invalid](https://www.jetbrains.com/help/idea/using-breakpoints.html#breakpoint-icons) and you can't add it again.

_⚠️ attachment `image2.png` was not included in the export_{width=485px}

If right-click to the invalid breakpoint:

_⚠️ attachment `image1.png` was not included in the export_{width=298px}
```
IntelliJ IDEA 2023.2.2 (Ultimate Edition)

Build #IU-232.9921.47, built on September 12, 2023

Licensed to 

Subscription is active until June 2, 2024.

Runtime version: 17.0.8+7-b1000.22 amd64

VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 11.0

GC: G1 Young Generation, G1 Old Generation

Memory: 3072M

Cores: 20

Registry:

debugger.watches.in.variables=false
Non-Bundled Plugins:

com.jetbrains.packagesearch.intellij-plugin (232.9921.28)

com.intellij.bigdatatools.core (232.9921.47)

com.intellij.bigdatatools.binary.files (232.8660.206)

com.intellij.bigdatatools.rfs (232.9921.47)

org.intellij.grails (232.8660.142)
Kotlin: 232-1.9.0-IJ9921.47
```

---

*3 attachment(s) referenced here (`image.png`, `image2.png`, `image1.png`) are not part of the CSV export.*
*Imported from [IDEA-333655](https://youtrack.jetbrains.com/issue/IDEA-333655) · Type: Bug · Votes: 3*
*Comments, attachments, dates and reporter are not part of the export — follow the link above for the full history.*

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the scenario in IntelliJ IDEA 2023.2.2 with Grails 5 code containing nested Groovy closures: set breakpoints, run a debug session, and inspect them afterward. Done means the original breakpoints remain valid and can be removed or added again after the session ends.

Written by the indexing model from the issue text.

Assessment

Tech stack
groovy, java
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.