Skip to content

merge queue: embarking unstable (b781227) and #9327 together#9392

Closed
mergify[bot] wants to merge 7 commits into
unstablefrom
mergify/merge-queue/5c23c174a5
Closed

merge queue: embarking unstable (b781227) and #9327 together#9392
mergify[bot] wants to merge 7 commits into
unstablefrom
mergify/merge-queue/5c23c174a5

Conversation

@mergify
Copy link
Copy Markdown

@mergify mergify Bot commented Jun 2, 2026

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

Branch unstable (b781227) and #9327 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #9327.
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: b781227f1d676a549f4e0b687d277bcdaaf2fd82
previous_failed_batches: []
pull_requests:
  - number: 9327
    scopes: []
scopes: []
...

dapplion and others added 7 commits May 20, 2026 06:08
Reshape BlockProcessingResult from the AC-verdict-passthrough
Ok/Err/Ignored enum to Imported(info) | Error { penalty, reason }. The
producer (network_beacon_processor) translates beacon-chain
Result<AvailabilityProcessingStatus, BlockError> into this shape via a
new classify_processing_result(), so the consumer only has to resolve
the symbolic WhichPeerToPenalize against an in-scope PeerGroup.

- New WhichPeerToPenalize { BlockPeer, CustodyPeerForColumn(u64) } with
  an `apply(action, &peer_group, reason, cx)` helper. Penalty policy
  lives once in classify_processing_result instead of being duplicated
  across consumer arms.
- Producer emits stable identifiers via two const modules
  (processing_result_info, processing_result_reason) so producer and
  consumer never trade ad-hoc string literals.
- Ignored becomes Error { penalty: None, reason: "processor_overloaded" }
  with a producer-side warn!; the consumer drops the lookup as before.
- DuplicateFullyImported and GenesisBlock map to Imported (which makes
  the consumer's "successfully imported" branch fall out naturally and
  removes the per-BlockError policy block — net -88 lines in mod.rs).
- on_processing_result_inner now captures the downloaded block's
  parent_root up-front, before borrowing request_state mutably, so the
  parent_unknown branch keeps working for any R.

Test rig: three tests construct the new variants directly. Extracted
from #9155 (gloas-lookup-sync) onto bare sigp/unstable.
Conflict resolutions:
- network_beacon_processor/mod.rs: keep BlockProcessingResult re-export;
  drop unused FixedBlobSidecarList import (removed upstream).
- sync/block_lookups/mod.rs: keep PR's classified BlockProcessingResult
  handling (Imported/ParentUnknown/Error); discard old BlockError match.
- sync/tests/lookups.rs: drop the two new blob crypto-failure tests; blob
  lookup sync was deprecated/removed upstream (#9383), deleting the
  corrupt_last_blob_* helpers they relied on. Column equivalents remain.
- sync_methods.rs: drop BlockError::BlobNotRequired arm (variant removed
  upstream) from the exhaustive penalty match.
@cla-assistant
Copy link
Copy Markdown

cla-assistant Bot commented Jun 2, 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 2, 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 2, 2026
@mergify mergify Bot deleted the mergify/merge-queue/5c23c174a5 branch June 2, 2026 02:50
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