Michael Diamond

AFAIK this is still an issue.

AFAIK this is still an issue.

@OllisGit I don't mind this bug sitting idle, I'm sure you have better things to do, but could you turn off the auto-closer? I don't know what else to do...

Note that `bc::invalidate_all` would (presumably) behave differently than `bc::expire` - the former would clear all invocations of that function while the latter would only expire that particular invocation (e.g. `bc::expire::foo...

> So, If your storage is encrypted at rest, you have to shutdown bashhub, to have it actually encrypted. @bebehei I don't think that reasoning is correct. It simply means...

See #285 for `PathSubject`; I'd like to see that added, even just as a stub.

We're inconsistent here, currently, too - at least in [`ThrowableSubject`](https://github.com/google/truth/blob/c382d6bf90/core/src/main/java/com/google/common/truth/ThrowableSubject.java#L64) we `fail()` on nulls in order to support chained assertions. We'd discussed making `Subject.actual()` NPE if the input is `null`,...

This would be appreciated by me too. I'd be happy to draft a PR if there's a design we can agree on. The proposed `@test "description" BACKEND NJOBS {` syntax...

I just want to make sure there's buy-in from core, and flesh out any further design constraints.

I've chatted with @sublimino and we're talking about a couple of approaches (which I'll share in more detail later), but one issue that needs to be settled before I can...