thunks

type Clock ¶

type Clock struct {
}

Clock implements the clockwork.Clock interface

func (fc Clock) After(d time.Duration) <-chan time.Time

func (fc Clock) Now() time.Time

func (fc Clock) Since(t time.Time) time.Duration

func (fc Clock) Sleep(d time.Duration)

type TestReader ¶

type TestReader struct {
	Next io.Reader
	// contains filtered or unexported fields
}

TestReader returns bytes from Next whenever asked, unless the number of bytes requested is 1, in which case it always returns 0x00.

This is because in go >= 1.11 the crypto libraries non-deterministically read a single byte from the PRNG in order to prevent people doing what we do and relying on the internal details of cryptographic operations.

For our purposes, having deterministic crypto in tests is super handy, and we have mechanisms for updating our expectations. So, while it might be better if we didn't rely on the crypto/* internals, on balance, the convenience of fixed test data outweighs the uglyness of this hack.

You might ask why we don't use a zero-reader as suggested by the commit message. The reason is that rsa key generation seems to spin forever when given a random source that always returns 0.

[1] https://github.com/golang/go/commit/6269dcdc24d74379d8a609ce886149811020b2cc

func (z *TestReader) Read(dst []byte) (n int, err error)