Using Add Condition & Add Log successively confuses the debugger

[juliandescottes]

You can trigger this by various sequence of actions that involve creating breakpoints, here is one which is easy to reproduce:

• open a script in the debugger
• right click on a line number
• click Add Condition
• Do not submit a condition
• right click on the same line number
• click Add Log
• try to remove the breakpoint
  ER: breakpoint is removed
  AR: breakpoint stays in the gutter

Trying to add other breakpoints on other lines will fail. Closing and reopening the debugger will not display all the breakpoints

[YisraelV]

/claim
If that's OK I would like to try and debug this.

[claim]

Thanks for claiming the issue! 👋

!!! Please check your email and confirm the invitation

Here are some links for getting setup, contributing, and developing. We're always happy to answer questions in slack! If you become busy, feel free to /unclaim it.

🦊 Debugger team!

[jasonLaster]

I think Brian submitted a PR for this last night. I'll check and get back to you

[YisraelV]

@jasonLaster thanks for letting me know. In general is it safe to assume an unclaimed issue is good to work on, or should I first ask here\on slack?

[YisraelV]

@jasonLaster any news on this?

[jasonLaster]

Hi @YisraelV brian's PR addresses this concern. I think it is safe to assume, but in this case you got unlucky. I'm sorry.

[juliandescottes]

@jasonLaster I guess this should be closed then? Is #7749 the good PR?

[nmicht]

This is fixed on current master Latest commit f4621c3
I think we can close it