Skip to content
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

Remove AppRequestId from api_types, #6969

Open
wants to merge 3 commits into
base: unstable
Choose a base branch
from

Conversation

jxs
Copy link
Member

@jxs jxs commented Feb 11, 2025

It seems we are never matching on it to react on it but rather to log crit! as those situations should not exist first hand.
Status request handling doesnt seem to care if it's Router or Sync.
Therefore it seems redundant to have it, but please give it a check as I may have missed something

as shown by the diffs was redundant
@pawanjay176 pawanjay176 requested review from pawanjay176 and removed request for pawanjay176 February 11, 2025 00:24
Copy link
Member

@AgeManning AgeManning left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah nice.

Looking at this, I think the main logic change is around the Status message. It looks like this PR now sends RPC errors related to status message to Sync.

We probably should avoid doing that, but it might re-introduce this concept of Router vs Sync in case we want to leave it generic if we add more non-sync rpc things later.

Not sure, curious about what you think

beacon_node/network/src/router.rs Show resolved Hide resolved
beacon_node/network/src/router.rs Show resolved Hide resolved
@AgeManning
Copy link
Member

Yeah. I think these changes look sane.

Just to be clear tho. We are now assuming every RPC call is related to sync and no longer have a way to distinguish non-sync network messages. I think in the current state it's fine, because Lighthouse isn't really making non-sync messages.

Although, it looks like there was a panic if we ran this, in the previous version, so it might be worth quickly running this PR to make sure it works as expected.

An easy way to do it locally is here: https://github.com/sigp/lighthouse/tree/stable/testing/network_testing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants