Frank Dana

Shoot, sorry, I missed that you'd already covered that: > This happens with any access mode option selected, and also when attempting to launch (rather than attach to) minimalwidgetapplication. I...

I tracked down a discussion I recalled having a while back regarding how this has to be handled for `gdb`: https://gist.github.com/mike-myers-tob/9a6013124bad7ff074d3297db2c98247 Basically, the binary has to be codesigned (a local...

@IanJempson > I started the tutorial, thought this looks great, then within 15 minutes found myself dealing with an error message that told me what the problem was but not...

@Zac-HD > I think it's pretty unlikely that we're the only people ever to make this mistake, Word. It almost makes me think the problem is the API. Having `pytest.mark.skip`...

@RonnyPfannschmidt A ruff rule might help _pytest_, but the implicit concern here is about the potential hundreds of **other** projects whose test files may contain the same silent mistake. A...

Oh! Oh, that's a neat idea, yeah. (**Edit:** GitHub really needs to add :bulb: to its paltry set of comment reactions.)

> And as you said, there's the problem of having different versions of Graphviz (even though it's probably very stable now, you never know what's going to happen or what...

The other tricky thing here is, if this were to be implemented, the corresponding getters and setters would really need to be defined using the enums as their output/input types...

This is also why we need to get coverage collection spun up on our test suite, so that we'll **KNOW** which code _isn't_ being tested despite our massive collection of...

@lkk7 I'll take a first stab at it, and make it a goal to open a WIP PR early in the process. That way, you & anyone else can pitch...