Danny Tuppeny

@elliette assuming you hadn't already started, I'm going to take a look at this.

I just checked and it does appear we have this (although it's `one` not `single` - I presume that's correct and it was just a typo above):  The complete...

Seems like this has come back - I saw this on Firebase Studio today:

I have a fix for this, but I implemented my tests in a different way to what VS Code does, because the spec doesn't make it clear whether `"changed"` breakpoint...

VS Code clarified the current behaviour is intended (and will hopefully update the spec). I've updated my change to match this behaviour and verified that adding a single breakpoint to...

Fixed by https://github.com/dart-lang/sdk/commit/d0a7ef44595fc7ab2991c391c6cd0609b7688402, but will require a DDS release to get to Flutter.

@bkonyi it's not urgent, but would it be possible to do a DDS release in time to roll into Flutter before the next beta branch? (I don't know when that...

@bkonyi thank you! Please let me know if you encounter any issues rolling it in (or if it needs doing manually, if you'd like me to look at it).

This fix is now in Flutter too. When adding/removing breakpoints, I now see just one add/remove request to the VM for each, and the responses indicate breakpoints that were already...

It's likely this fix will be reverted for now due to some other issues (see https://docs.google.com/document/d/1eeEHG3EL4D5EbB3YiAO5X2TcCRIciFMSPKL_hFGP0Gk/edit?disco=AAABk-csO5o), so re-opening this to fix again after.