Prysm: Panic from minio/sha256 in beacon chain node

[0xKiwi]

Running Prysm, after block 282339 my beacon chain node panicked with the following error logs (very long)

```[2020-05-27 01:07:52] INFO p2p: Peer disconnected active=338 peer=16Uiu2HAmEqsMWmGt9Vik6UygpMpq7kNQm7Dx64LCTNVcj2cDhUj1
runtime: invalid pc-encoded table f=github.com/golang/protobuf/proto.(*tagMap).put pc=0x80b9e1 targetpc=0x80b9ef tab=[0/0]0x0
value=0 until pc=0x80b897
value=72 until pc=0x80b963
value=0 until pc=0x80b964
value=72 until pc=0x80b9a4
value=0 until pc=0x80b9a5
value=72 until pc=0x80b9d7
value=0 until pc=0x80b9e1
fatal error: invalid runtime symbol table

goroutine 0 [idle]:
runtime: unexpected return pc for runtime.sigtramp called from 0x7f58ba19e890
stack: frame={sp:0xc02501d968, fp:0xc02501d9c0} stack=[0xc025016000,0xc02501e000)
000000c02501d868: 000000000046d1f7 0000000000af814c
000000c02501d878: 000000c03e4976c0 0000000000000000
000000c02501d888: 000000c030e22780 000000c00238b500
000000c02501d898: 0000000000000101 0000000000000000
000000c02501d8a8: 0000000000000000 0000000000000000
000000c02501d8b8: 0000000000000000 000000c00d475080
000000c02501d8c8: 0000000000000000 000000c02501daf0
000000c02501d8d8: 000000c02501d9c0 000000c02501d958
000000c02501d8e8: 000000000046c749 000000c00000001b
```

Ubuntu Linux, commit hash is 5afee4ba

[rauljordan]

@0xKiwi this is something we should bring to the minio sha256 repo, they might need to know your Go version and maybe more of a stack trace. I've seen this one before and seems like a bug in their repo.

[shayzluf]

assigning to @0xKiwi to keep it updated with the upstream issue

[no-response[bot]]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

[terencechain]

@0xKiwi should this be closed?

[no-response[bot]]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.