-
Notifications
You must be signed in to change notification settings - Fork 742
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
Move sync active requests to own modules #6272
Conversation
f5a9bf7
to
abcb558
Compare
Fixed conflicts 👍 |
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.
lgtm
@mergify queue |
🛑 The pull request has been removed from the queue
|
@mergify dequeue |
✅ The pull request has been removed from the queue
|
@mergify queue |
🛑 The pull request has been removed from the queue
|
@mergify requeue |
✅ This pull request will be re-embarked automaticallyThe followup |
🛑 The pull request has been removed from the queue
|
@mergify requeue |
✅ This pull request will be re-embarked automaticallyThe followup |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at e0ccadb |
Issue Addressed
PeerDAS will add two more sync
ActiveRequest*
. Currently there are only two:ActiveBlocksByRootRequest
,ActiveBlobsByRootRequest
as spaghetti in the same fileProposed Changes
Move each
ActiveRequest*
to its own file to make space for upcoming PeerDAS PR with additional requests.No change in logic or code, just copy pasted into new files