Stu Hood

Just had a user run into a git-ignored directory that contained BUILD files causing them trouble. This would still be a really good thing to do.

There are some comments on the implementing ticket: https://github.com/pantsbuild/pants/pull/9310#pullrequestreview-377237911 The idea of holding onto ignore state as we descend the tree might be related to some of the optimizations mentioned...

This relates to #14886 as well: assuming that you had enough tests to saturate your cores initially, you might end up with a large single test file still running after...

I think that to do this, you would: 1. Add a boolean option to the `pytest` subsystem to control whether it is enabled, [similar to this one](https://github.com/pantsbuild/pants/blob/258ab2602a05b1450540d8d3d89f51407aa416fa/src/python/pants/backend/python/subsystems/pytest.py#L137-L148). It will likely...

It's possible to do this using an implementation of `tokio_util::codec::Decoder` (which presumably allocates a large buffer under the hood, and then passes you small slices from it?): ``` fn stream_for(r:...

Also very related is: #16667.

> That might be intuitive - that is how `git grep` works for example. But not `git-status` or `git-diff`.

I think that #14720 can help with the most egregious case of this: that we are forced to run target generation for all languages (which is expensive for Go), even...

Closing in favor of #18911.

The recently landed dependency rules feature now implements this: example here: #17630. Thanks for doing some exploration in this area!