Skip to content

backport: Merge bitcoin#27151, 25849, 27608#7128

Open
vijaydasmp wants to merge 3 commits intodashpay:developfrom
vijaydasmp:Feb_2026_05
Open

backport: Merge bitcoin#27151, 25849, 27608#7128
vijaydasmp wants to merge 3 commits intodashpay:developfrom
vijaydasmp:Feb_2026_05

Conversation

@vijaydasmp
Copy link

bitcoin backports

@vijaydasmp vijaydasmp changed the title Feb 2026 05 backport: Merge bitcoin#25943 Feb 4, 2026
@vijaydasmp vijaydasmp changed the title backport: Merge bitcoin#25943 backport: Merge bitcoin#25943, 27151, 25849 Feb 4, 2026
@github-actions
Copy link

github-actions bot commented Feb 4, 2026

⚠️ Potential Merge Conflicts Detected

This PR has potential conflicts with the following open PRs:

Please coordinate with the authors of these PRs to avoid merge conflicts.

@vijaydasmp vijaydasmp changed the title backport: Merge bitcoin#25943, 27151, 25849 backport: Merge bitcoin#27151, 25849, 25077 Feb 4, 2026
e846269 util: Remove duplicate include (Andrew Chow)

Pull request description:

  Duplicate `#include <utility>` is upsetting the linter.

ACKs for top commit:
  davidgumberg:
    ACK bitcoin@e846269
  theStack:
    ACK e846269
  john-moffett:
    ACK e846269

Tree-SHA512: 9e45d8f6a2dd5efcb8eb1c3c440d94b16490dbd63255784cb39863767fa07227e06da112a150ef337ef89e2e305b60b00d5b1c12ff7e1e9c02f6648ed97fac8c
…tring

fac09f4 refactor: Remove not needed empty RPC doc std::string (MacroFake)

Pull request description:

  Not sure why this was put there, so remove it

ACKs for top commit:
  aureleoules:
    ACK fac09f4.

Tree-SHA512: 7fae9c612dbb82db39e3dc6e20cc7d0c8128f4abf27e34f4854f908dc1bf3ad48ebee2dbbb864a9ce95e98c5d57119bf976793945a2084a43d137c2d95a25ea1
@vijaydasmp vijaydasmp changed the title backport: Merge bitcoin#27151, 25849, 25077 backport: Merge bitcoin#27151, 25849 Feb 25, 2026
…or other peers

52e5207 p2p: Avoid prematurely clearing download state for other peers (Suhas Daftuar)

Pull request description:

  Avoid letting one peer send us data that clears out the download request (and related timers etc) from another peer.

  The exception is if a block is definitely stored to disk, in which case we'll clear the download state (just as we do for compact blocks).

ACKs for top commit:
  jamesob:
    ACK 52e5207 ([`jamesob/ackr/27608.1.sdaftuar.p2p_avoid_prematurely_cl`](https://github.com/jamesob/bitcoin/tree/ackr/27608.1.sdaftuar.p2p_avoid_prematurely_cl))
  instagibbs:
    ACK 52e5207
  fjahr:
    Code review ACK 52e5207
  mzumsande:
    Code Review ACK 52e5207

Tree-SHA512: 3ee92507edc3303c16c70ca44ba6c28c104afe95196e4b9167032590ed23d4f569f654f8eb8758940bd6536bc9ca810d2a77d2739db386b927e8b3f3cf55cb16
@vijaydasmp vijaydasmp changed the title backport: Merge bitcoin#27151, 25849 backport: Merge bitcoin#27151, 25849, 27608 Feb 25, 2026
@vijaydasmp vijaydasmp marked this pull request as ready for review February 26, 2026 01:03
@coderabbitai
Copy link

coderabbitai bot commented Feb 26, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d71b89c and 9959cde.

📒 Files selected for processing (3)
  • src/net_processing.cpp
  • src/support/lockedpool.cpp
  • src/wallet/rpc/spend.cpp
💤 Files with no reviewable changes (1)
  • src/support/lockedpool.cpp

Walkthrough

The pull request introduces peer-aware block request removal by modifying the RemoveBlockRequest method to accept an optional from_peer parameter, ensuring blocks are only removed from the in-flight map when requested from a specific peer. Multiple call sites throughout block processing logic are updated to pass appropriate peer context (or std::nullopt where peer-specific removal is not applicable). Additionally, an #include <utility> header is removed from a support file, and RPC help text formatting is simplified in wallet spend methods.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 12.50% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the PR as a backport merging three specific upstream Bitcoin PRs (#27151, #25849, #27608), which directly matches the changeset containing these exact backports.
Description check ✅ Passed The description 'bitcoin backports' is related to the changeset as it correctly identifies the PR's purpose of merging upstream Bitcoin changes, though it lacks detail about the specific changes involved.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

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