It's not clear what the type of "out" is, other than it has Stat() and
Read([]byte) methods, but, assuming it's an io.Reader at least, if you
examine the return values from Read, like:
n, err := out.Read(buffer)
you may get a clue to what's going wrong, for example n might not be the
full size
This topic reminded me of this other thing I remember seeing:
https://github.com/marcusolsson/goddd - there are some further links to
blog posts and stuff on the README on that project, and there's a related
talk on YouTube from one of the Go conferences.
On Friday, August 18, 2017 at 11:29:0
You've missed the regexp argument to -bench; try just a . to match all
benchmarks.
(In fact go test will be interpreting crypto/tls/... as the regular
expression, and with no further parameter is trying to test what's in the
current directory.)
-bench regexp
Run only those benchmarks match
For PKCS8 (rather than PKCS1), use PEM type "PRIVATE KEY" (rather than "RSA
PRIVATE KEY").
You may be constructing the ASN1 by hand deliberately, but just in case you
didn't see it, there's also a standard library function
x509.MarshalPKCS8PrivateKey()
https://godoc.org/crypto/x509#MarshalPKCS
The pull request is not going too smoothly:
https://github.com/Homebrew/homebrew-core/pull/47510
(I just looked at the repo - I'm not involved with homebrew at all, except
as a user.)
On Monday, December 9, 2019 at 9:36:01 PM UTC, Brian Hatfield wrote:
>
> Hi there,
>
> This appears to still n
