-
Notifications
You must be signed in to change notification settings - Fork 959
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug(shares/GetSharesByNamespace): missing response type ErrNamespaceNotFound
#2145
Closed
Tracked by
#2106
Labels
Comments
Is this related : rollkit/rollkit#897 ? |
@nashqueue yes, partially |
I'm getting something similar on a rollup, just every so often though da | 2023-05-03T19:44:32.020Z ERROR ipld ipld/namespace_data.go:216 getLeavesWithProofsByNamespace:could not retrieve node {"nID": "\ufffd\ufffd\ufffdy\ufffdq\u0016\ufffd", "pos": 0, "err": "context canceled"} |
19 tasks
I made an issue for the error above, as I believe the error is different, but related #2174 |
vgonkivs
pushed a commit
to vgonkivs/celestia-node
that referenced
this issue
May 22, 2023
…x-nd (celestiaorg#2230) This PR replaces celestiaorg#2156 , as gh was not showing the diff properly. It closes celestiaorg#2145 --------- Co-authored-by: Hlib Kanunnikov <hlibwondertan@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the current implementation, the response from a shrex-nd server for "Hey, my EDS store doesn't have that EDS, so I can't give you the ND" and "Hey, that EDS is in my store, and the data you are looking for doesn't exist in it" are the same. This causes many issues in the stack, leading to a timeout for
GetSharesByNamespace
calls, even when the correct response has been found. This will clearly require a protocol breaking change.This must also be fixed in CascadeGetter, which should recognize the difference between
ErrNotFound
, which moves onto the next getter, andErrNamespaceNotFound
, which should return the data and error.This means IPLDGetter should also return a
share.ErrNamespaceNotFound
for the same reason.The text was updated successfully, but these errors were encountered: