beacon-chain invalid memory addreses or nil pointer dereference
qymlyl opened this issue · comments
Describe the bug
When blobscan obtains a non-existent blob, prysm reports a null pointer exception
blobscan send request to beacon-chain
beacon-chain error
Has this worked before in a previous version?
Unverified
🔬 Minimal Reproduction
No response
Error
No response
Platform(s)
Linux (x86)
What version of Prysm are you running? (Which release)
use doceker, gcr.io/prysmaticlabs/prysm/beacon-chain:HEAD-2f2152
Anything else relevant (validator index / public key)?
No response
shouldn't be an issue in previous versions but thanks for the report we'll get this fixed
merged to fix develop, should be fixed there, and 5.0.3 should still be ok.