mirror of
https://github.com/OffchainLabs/prysm.git
synced 2026-01-08 04:54:05 -05:00
blobsDataFromStoredDataColumns: Ask the use to use the --supernode flag and shorten the error mesage. (#16097)
**What type of PR is this?** Other **What does this PR do? Why is it needed?** `blobsDataFromStoredDataColumns`: Ask the use to use the `--supernode` flag and shorten the error mesage. **Acknowledgements** - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description to this PR with sufficient context for reviewers to understand this PR.
This commit is contained in:
@@ -450,7 +450,7 @@ func (p *BeaconDbBlocker) blobsDataFromStoredDataColumns(root [fieldparams.RootL
|
|||||||
if count < peerdas.MinimumColumnCountToReconstruct() {
|
if count < peerdas.MinimumColumnCountToReconstruct() {
|
||||||
// There is no way to reconstruct the data columns.
|
// There is no way to reconstruct the data columns.
|
||||||
return nil, &core.RpcError{
|
return nil, &core.RpcError{
|
||||||
Err: errors.Errorf("the node does not custody enough data columns to reconstruct blobs - please start the beacon node with the `--%s` flag to ensure this call to succeed, or retry later if it is already the case", flags.Supernode.Name),
|
Err: errors.Errorf("the node does not custody enough data columns to reconstruct blobs - please start the beacon node with the `--%s` flag to ensure this call to succeed", flags.SemiSupernode.Name),
|
||||||
Reason: core.NotFound,
|
Reason: core.NotFound,
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|||||||
3
changelog/manu-logs-beacon-chain.md
Normal file
3
changelog/manu-logs-beacon-chain.md
Normal file
@@ -0,0 +1,3 @@
|
|||||||
|
### Changed
|
||||||
|
|
||||||
|
- `blobsDataFromStoredDataColumns`: Ask the use to use the `--supernode` flag and shorten the error mesage.
|
||||||
Reference in New Issue
Block a user