Account for state availability when fetching sync committees #7178
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
michaelsproul
requested changes
Mar 20, 2025
|
Please rebase on |
chong-he
added
waiting-on-author
done |
macladson
reviewed
Mar 28, 2025
There was a problem hiding this comment.
Hi @Ayushdubey86, the PR seems to have commits from other authors related to the mergify config. These changes are only on the stable branch and not present in unstable. Since we need you to target unstable, these changes will need to be removed. I would recommend doing an interactive rebase (git rebase -i unstable) and removing those specific commits. Thanks!
Ayushdubey86
changed the title
Ayushdubey86
deleted the
Account-for-state-availability-when-fetching-sync-committees-#7115
branch
This was referenced May 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello @michaelsproul , do check this pr out once free!
Issue Addressed
Which issue # does this PR address?
Issue -> #7115
Proposed Changes
This pr is a continuation of this pr
Please list or describe the changes introduced by this PR.