Issues with debugging

[Hixie]

I asked someone on gitter for feedback on the debugging experience with Flutter and this is what they said:

Kent Boogaart @kentcb 20:06

These may be specific to IntelliJ (which I am using with reluctance until major issues in VS Code addin are resolved):

I wish breakpoints within an expression were possible/more obvious. Particularly pertinent when trying to set a breakpoint within a lambda.
sometimes I hover over a local and it just doesn't show the tooltip for an expression. I can often point at a different local that contains that local and go from there, but it's frustrating.
breakpoints in tests I simply cannot get to work. I'm not sure, but it may be due to me using community IntelliJ.
Other than that, pretty happy with the experience.

[kentcb]

Another thing while I remember it...

I find it super frustrating that test failures look like this:

Problems:

• Maybe this is a Dart thing (I have no idea), but the stack trace is unintelligible to me. The encoding (%5C), the alignment. It's all just a bit ... ugh
• The thing I tend to care about most (expected versus actual) is right at the bottom of the stack trace, so I have to scroll right to the end to see it.

Other problems with the test runner:

• Why not auto-select the first failed test?
• It seems to randomly decide to keep certain nodes collapsed/expanded and I have no idea why. It would be nice if it just remembered which nodes I have collapsed and which are expanded, from one test run to the next.
• I still haven't figured out how to create a test configuration that will just run all my tests, which are in separate files (one per feature). Instead, I have to create one test configuration per file.

[devoncarew]

Thanks for the feedback! I'm curious, re:

The encoding (%5C)

Are you on windows? It's not clear to me where in the stack that encoding issue is occurring,

[kentcb]

@devoncarew Yes, I'm on Windows.

[vasilich6107]

Hi. @Hixie @devoncarew @pq
I've found this issue while searching for existing issues with IDEA plugin debugging experience.

For last half a year I have issues with debugging ios/androi/web apps via IDEA plugin.
The most annoying one it ghost breakpoints.

Almost every debug session results into having ghost breakpoints - when I uncheck the red dot - idea debugger(IDEA or AndroidStudio) will continue to stop at that place. This happens for ios/android/web debug.

The only way to get rid from ghost breakpoints is to restart the debug session and it is very annoying.
Could you clarify if this issue has any progress in fixing cause while debugging the dev experience drops to the very bottom.

This issue gets additional context
#6770