jared2501

@marten-seemann - ah hmm, perhaps RequireClientAuth is a bit of a misnomre then? Also, when you say "as the standard library does", do you mean by allowing the client to...

Hey @raiju -- When I wrote the prdeps extension I had discussed with @uschi2000 about how to handle the case when a library has dependencies that give conflicting recommendations. We...

Ahh I've got a minimal repro: ``` // This fails DirectoryLayer dirLayer = DirectoryLayer.getDefault(); for (int i = 0; i < 100; i++) { String randDir = UUID.randomUUID().toString(); db.run(tx ->...

@ajbeamon - Ah yup this makes sense. @KrzysFR - yeah the array of paths works too. I think users would still find it unexpected that dir operations can't be performed...

@ianlancetaylor @andybons - any chance we could revive the CR above that adds labels to goroutine profiles? I have an annoying goroutine leak that I'm debugging, for which this would...

Scanning through the CL and surrounding code, it appears to add labels to `debug=0` and `debug=1` outputs. The `debug=0` format is protobuf and is used by `go tool pprof`, and...

@ianlancetaylor So I don't believe anything actually parses the `labels:` syntax, since I believe that the text output (i.e. `debug=1`) is there only for debugging using `curl`. The `go tool...

I.e. `go tool pprof` vendors google/pprof, and the code to decode labels is here: [google/pprof/profile/encode.go#L434](https://github.com/google/pprof/blob/master/profile/encode.go#L434)

Super cool to see this merge! Thanks everyone for the work on it :)

My next FR in this area would be to get the labels into the goroutines `debug=2` traces ;) ... but at least this will help out enormously with debugging!