Skip to content

merge queue: embarking unstable (5bad119) and #820 together#825

Closed
mergify[bot] wants to merge 5 commits intounstablefrom
mergify/merge-queue/f59e4223cf
Closed

merge queue: embarking unstable (5bad119) and #820 together#825
mergify[bot] wants to merge 5 commits intounstablefrom
mergify/merge-queue/f59e4223cf

Conversation

@mergify
Copy link

@mergify mergify bot commented Feb 11, 2026

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

Branch unstable (5bad119) and #820 are embarked together for merge.

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

Required conditions of queue default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: 5bad119e7b99ada4e65f2f634f6e9835dbac1c6b
previous_failed_batches: []
pull_requests:
  - number: 820
...

diegomrsantos and others added 5 commits February 10, 2026 12:21
…scription

During fork transitions, a peer may be subscribed to the same subnet via
topics from different forks (e.g., ssv.v2.42 and /ssv/mainnet/boole/42).
Previously, unsubscribing from one fork's topic would clear the subnet
bit entirely, even though the peer was still subscribed via the other
fork's topic.

Track subscriptions per fork so each fork maintains its own bitmap. Query
methods aggregate across forks using bitwise union when checking subnet
coverage.

Closes #818

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Address review feedback: log a warning when a subnet ID exceeds the
bitfield capacity instead of silently ignoring it, and add a test
verifying that duplicate subscribes on the same fork+subnet don't
break state.
Add peer ID to the out-of-bounds subnet warning log and replace the
imperative loop in aggregate_fork_bitmaps with a functional fold.
@github-actions
Copy link

Your PR title doesn't follow the Conventional Commit guidelines.

Example of valid titles:

  • feat: add new user login
  • fix: correct button size
  • docs: update README

Usage:

  • feat: Introduces a new feature
  • fix: Patches a bug
  • chore: General maintenance tasks or updates
  • test: Adding new tests or modifying existing tests
  • perf: Performance improvements
  • refactor: Changes to improve code structure
  • docs: Documentation updates
  • ci: Changes to CI/CD configurations
  • revert: Reverts a previously merged PR

Breaking Changes

Breaking changes are noted by using an exclamation mark. For example:

  • feat!: changed the API
  • chore(node)!: Removed unused public function

Help

For more information, follow the guidelines here: https://www.conventionalcommits.org/en/v1.0.0/

@mergify mergify bot closed this Feb 11, 2026
@mergify mergify bot deleted the mergify/merge-queue/f59e4223cf branch February 11, 2026 16:07
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