Consider adding an additional filtering option to only run analysis after Nth line hit

[markerikson]

Per https://twitter.com/bradleymeck/status/1528165954395447296 , it might be useful to have a breakpoint/print statement filtering option that only starts running analysis after the line has been hit N times.

[jaril]

My understanding of that tweet is that _shu would like to pause at the breakpoint right before a crash. For example, if a breakpoint was hit 1000 times but it crashes between 999 and 1000, then you'd like to pause at 999. In replay, that's super easy since you can just go to the end of the recording, and hit previous hit on that breakpoint twice and you're there. No need for any filtering.

I think that's also what you were trying to explain in this tweet, so this should already be resolved. Am I missing something? Let me know!

[markerikson]

Yeah, I'm suggesting that it might still be useful to say "look, I know this line is gonna get hit 100 times, but skip logging the first 50 of them and only start printing output at 51", etc.

[jaril]

Yeah, I'm suggesting that it might still be useful to say "look, I know this line is gonna get hit 100 times, but skip logging the first 50 of them and only start printing output at 51", etc.

AH got it!

My sense is this is an edge case and a new filter implementation might conflict (and actually, is somewhat addressable) by focus mode. Which I'm just now realizing is exactly what you said here 🤦‍♂️

Switching it to a discussion so @jonbell-lot23 @jcmorrow can weigh in.

[jcmorrow]

Hi! We have #6531 for tracking this exact thing, and yes, this gets much, much better with soft focus mode, but we will still probably need better UI tools for querying things like "Analyze hits number 45 - 50". I think we can safely close this discussion as a duplicate though. Let me know if there's something that this cards captures that #6531 does not!

[jcmorrow]

Added some detail in a loom: https://www.loom.com/share/7ed242fb73874827a94a449de5a92cad