Skip to content

merge queue: embarking unstable (c2ac519) and #9391 together#9403

Closed
mergify[bot] wants to merge 13 commits into
unstablefrom
mergify/merge-queue/fc860607f7
Closed

merge queue: embarking unstable (c2ac519) and #9391 together#9403
mergify[bot] wants to merge 13 commits into
unstablefrom
mergify/merge-queue/fc860607f7

Conversation

@mergify
Copy link
Copy Markdown

@mergify mergify Bot commented Jun 3, 2026

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch unstable (c2ac519) and #9391 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #9391.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: c2ac519c69311527a23ea161b7bde5117755506e
previous_failed_batches: []
pull_requests:
  - number: 9391
    scopes: []
scopes: []
...

dapplion and others added 13 commits June 1, 2026 18:45
… classification

Combine PR #9327's processing-result classification redesign (BlockProcessingResult
becomes Imported/ParentUnknown/Error with producer-side penalty classification in
network_beacon_processor) with PR #9155's RequestState trait removal (concrete
BlockRequest/DataRequest state machine in single_block_lookup.rs, concrete download/
processing handlers in block_lookups/mod.rs). The common.rs RequestState trait is
deleted. ParentUnknown remains reactive (surfaced from the processing result), as in
unstable. All gloas constructs are stripped.
…move-request-state-trait

# Conflicts:
#	beacon_node/network/src/network_beacon_processor/sync_methods.rs
#	beacon_node/network/src/sync/block_lookups/mod.rs
#	beacon_node/network/src/sync/manager.rs
#	beacon_node/network/src/sync/tests/lookups.rs
Brings #9391 up to the latest lookup-sync trait-removal work: concrete
BlockRequest/DataRequest over the reused SingleLookupRequestState<T> state
machine, DataRequestState { WaitingForBlock, Request, NoData } column gating,
seen_timestamp forwarding, and diff minimization vs unstable.
Resolves conflicts from #9379 (Delete unnecessary SyncMessage variants):
- adopt SyncMessage::UnknownParentSidecarHeader (drop UnknownParentDataColumn/
  UnknownParentPartialDataColumn), keeping our unit BlockComponent::Sidecar
  (parent_root is routed separately to handle_unknown_parent)
- keep concrete trait-removal BlockRequest/DataRequestState handlers
Also: move DownloadResult back to its unstable position to minimize diff.
DataRequest no longer carries its own PeerSet clone; the column request reads
self.peers (the lookup's pool) directly. Also fix the stale 'starts as None'
comment on data_request and restore upstream's add_child_components comment.
- drop misleading 'Block request — always present' comment; reword data_request
- add_child_components Sidecar: clearer comment (no stale 'blob request state')
- drop stale '// None = waiting for block'
- fix continue_requests doc state name (AwaitingProcess, not Downloaded)
- on_data_processing_result doc: custody columns
Not needed: a zero-hash (genesis parent) search just creates a lookup that
fails its download attempts and is dropped. Removes logic not present in
unstable; tests pass without it.
@cla-assistant
Copy link
Copy Markdown

cla-assistant Bot commented Jun 3, 2026

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ dapplion
❌ mergify[bot]
You have signed the CLA already but the status is still pending? Let us recheck it.

1 similar comment
@cla-assistant
Copy link
Copy Markdown

cla-assistant Bot commented Jun 3, 2026

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ dapplion
❌ mergify[bot]
You have signed the CLA already but the status is still pending? Let us recheck it.

@mergify mergify Bot closed this Jun 3, 2026
@mergify mergify Bot deleted the mergify/merge-queue/fc860607f7 branch June 3, 2026 15:29
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.

1 participant