Aaron Jacobs

There are arch-specific implementations because each contains [arch-specific assumptions](https://github.com/jacobsa/crypto/blob/master/cmac/hash_amd64.go#L28-L33) about the size of a block in relation to the size of `uintptr`. `crypto. fastXORWords` is functionally equivalent but the support...

I would assume you want to update code that's in that file, near that panic. It's checking assumptions for the local code.

I have no specific ideas or tips, but I will say (very generically, sorry) that with past issues like this I was able to get a lot of mileage out...

Unfortunately I'm unlikely to be able to help you figure out what's going on here. If you root cause this let me know, and I'm happy to discuss how to...

It seems unlikely (but not impossible) that the problem is in the Go code itself. You might try looking at the kernel stacks (`/proc//stack`) for the various threads of the...

That's from a pull request written by @matevzmihalic. I don't know anything about it. Please feel free to fix it if the documentation and your experimentation both agree.

I don't remember for sure, but I suspect it's this (from the termios [man page](http://linux.die.net/man/3/termios)): > MIN == 0; TIME == 0: If data is available, read(2) returns immediately, with...

Would it also work to just change the magic value of `100`? I don't know why I chose that.

I suppose an `AllowNonBlocking bool` field that disabled the check in question would be fine.

For context, this is waiting on the approval and implementation of https://github.com/grpc/proposal/pull/238.