-
Notifications
You must be signed in to change notification settings - Fork 0
feat(blobber): Use new /blobs lighthouse endpoint to fetch blobs from CL
#58
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
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
prestwich
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i was not requesting an error type. I was requesting a clear explanation of the API and why it was designed that way. I think that "give me whatever subset of X,Y,Z you have" is a useful API. I also think that "give me exactly X,Y,Z, or nothing" is a useful function. What I'm looking for 0 panics, and for the rustdoc to tell me exactly how to achieve both of those things
prestwich
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
DRY the two functions
document that we assume the CL returns correct blobs and not unrelated data
…om CL This massively simplifies CL blob fetching code. Instead of having to match blobs with versioned hashes with potential problems, we can just ask for exactly the blobs we want using the slot and versioned hashes. It reduces the entire CL fetching code to an API call. Closes ENG-1667
1abc53a to
ab28dcd
Compare

This massively simplifies CL blob fetching code. Instead of having to match blobs with versioned hashes with potential problems, we can just ask for exactly the blobs we want using the slot and versioned hashes. It reduces the entire CL fetching code to an API call.
Closes ENG-1667