Make M3 monorepo compatible with Go 1.14

[andrewmains12]

Filing M3 Issues

This is a catchall issue for all known barriers to running the M3 stack on Go 1.14. We can split out child issues as we find them for large enough problems.

murmur3 library uses unsafe operations: Flaky "unsafe pointer conversion"-panics with -race and go1.14rc1 #29

The murmur3 library we use uses unsafe operations, which now fail with Go 1.14 and -race. See: spaolacci/murmur3#29 .

Fix will likely also need to apply to our murmur3 fork: github.com/m3db/stackmurmur3.

One potential fix is to move to https://github.com/twmb/murmur3. #2539 has a POC of this approach.

etcd bbolt uses unsafe code and panics with -race

Similar issue to the above; only fails in tests with -race. Probably fixed in later etcd versions--see etcd-io/bbolt#187

=== RUN   TestReuseLeaseID
fatal error: checkptr: unsafe pointer conversion

goroutine 13 [running]:
runtime.throw(0x2124032, 0x23)
        /Users/amains/Code/gocode/go1.14.6/src/runtime/panic.go:1116 +0x72 fp=0xc00045f058 sp=0xc00045f028 pc=0x1076ba2
runtime.checkptrAlignment(0xc0001de3f0, 0x206f2a0, 0x1)
        /Users/amains/Code/gocode/go1.14.6/src/runtime/checkptr.go:20 +0xc9 fp=0xc00045f088 sp=0xc00045f058 pc=0x1048719
go.etcd.io/bbolt.(*Bucket).write(0xc00045f200, 0x0, 0x0, 0x0)
        /Users/amains/Code/gocode/pkg/mod/go.etcd.io/[email protected]/bucket.go:624 +0x15c fp=0xc00045f0f0 sp=0xc00045f088 pc=0x1b8c4fc
go.etcd.io/bbolt.(*Bucket).CreateBucket(0xc0002da018, 0x2b01a34, 0x7, 0x7, 0xc00045f460, 0x1c50be6, 0xc000288ba8)
        /Users/amains/Code/gocode/pkg/mod/go.etcd.io/[email protected]/bucket.go:181 +0x465 fp=0xc00045f2b0 sp=0xc00045f0f0 pc=0x1b88945
go.etcd.io/bbolt.(*Tx).CreateBucket(...)
        /Users/amains/Code/gocode/pkg/mod/go.etcd.io/[email protected]/tx.go:108
go.etcd.io/etcd/mvcc/backend.(*batchTx).UnsafeCreateBucket(0xc000385d70, 0x2b01a34, 0x7, 0x7)

[andrewmains12]

#2539 is the first step towards fixing the murmur issue.

[andrewmains12]

Sorry unintentionally deleted a comment from @vdarulis :

I'll pull in the new lib for m3db/bloom fork, as it actually should even improve perf.

[vdarulis]

Tried running tests again - there's another issue with unsafe pointer conversions in m3dbx/pilosa, likely just need to backport a single commit from upstream.