feat: add set_node_account_ids to the query chain

[AntonioCeppellini]

Description:
This PR updates TransactionResponse.get_receipt() adding set_node_account_ids([self.node_id]) to the query chain

we now

• Pin receipt queries to the submitting node (self.node_id)
• Have a new dedicated test file
• Follow other SDKs pattern

Related issue(s):

Fixes #1686

Notes for reviewer:

Checklist

• Documented (Code comments, README, etc.)
• Tested (unit, integration, etc.)

[github-actions]

Hi, this is MergeConflictBot.
Your pull request cannot be merged because it contains merge conflicts.

Please resolve these conflicts locally and push the changes.

Quick Fix for CHANGELOG.md Conflicts

If your conflict is only in CHANGELOG.md, you can resolve it easily using the GitHub web editor:

1. Click on the "Resolve conflicts" button in the PR
2. Accept both changes (keep both changelog entries)
3. Click "Mark as resolved"
4. Commit the merge

For all other merge conflicts, please read:

• Resolving Merge Conflicts
• Rebasing Guide

Thank you for contributing!

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

Walkthrough

Pins receipt queries in TransactionResponse.get_receipt() to the submitting node by calling .set_node_account_ids([self.node_id]) on TransactionGetReceiptQuery, adds unit tests validating pinning with mocked node responses, and updates CHANGELOG.md entries accordingly.

Changes

Cohort / File(s)	Summary
Changelog CHANGELOG.md	Updated Unreleased/Changed entries to reflect Key equality/hash additions and that receipt queries are pinned to the submitting node; adjusted wording for Key entry.
Receipt Query Pinning src/hiero_sdk_python/transaction/transaction_response.py	Modified TransactionResponse.get_receipt() to call .set_node_account_ids([self.node_id]) on the TransactionGetReceiptQuery before .execute(client).
Receipt Pinning Tests tests/unit/test_transaction_response.py	Added tests verifying TransactionResponse public attributes and that get_receipt() pins receipt queries to the submitting node using mocked node responses (one node returns non-retryable error, the submitting node returns SUCCESS).

Sequence Diagram(s)

sequenceDiagram
    participant Client as Client
    participant TxResponse as TransactionResponse
    participant ReceiptQ as TransactionGetReceiptQuery
    participant NodeA as "Node 0.0.3"
    participant NodeB as "Node 0.0.4"

    Client->>TxResponse: response.get_receipt(client)
    TxResponse->>ReceiptQ: new TransactionGetReceiptQuery()
    ReceiptQ->>ReceiptQ: .set_transaction_id(txId)
    ReceiptQ->>ReceiptQ: .set_node_account_ids([submittingNode])
    ReceiptQ->>NodeA: execute(query)
    alt NodeA returns non-retryable error
        NodeA-->>ReceiptQ: error
        ReceiptQ-->>Client: error (pinned to submitting node)
    else NodeA returns SUCCESS
        NodeA-->>ReceiptQ: receipt SUCCESS
        ReceiptQ-->>Client: receipt SUCCESS
    end

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding set_node_account_ids to the query chain in TransactionResponse.get_receipt().
Description check	✅ Passed	The description clearly explains the change: pinning receipt queries to the submitting node via set_node_account_ids([self.node_id]), adding tests, and aligning with other SDKs.
Linked Issues check	✅ Passed	The PR successfully implements the primary objective from #1686: pinning receipt queries to submitting node via set_node_account_ids([self.node_id]), adds required tests, and includes a changelog entry.
Out of Scope Changes check	✅ Passed	All changes are directly related to pinning receipt queries to the submitting node. No unrelated modifications detected.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ 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

Issue Planner is now in beta. Read the docs and try it out! 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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 3

[coderabbitai]

Actionable comments posted: 1

[tech0priyanshu]

Hii @AntonioCeppellini great work done ... lgtm

[tech0priyanshu]

some merge conflict @AntonioCeppellini

[manishdait]

lgtm, just needs a rebase

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

@@           Coverage Diff           @@
##             main    #1727   +/-   ##
=======================================
  Coverage   93.29%   93.29%           
=======================================
  Files         141      141           
  Lines        9116     9116           
=======================================
  Hits         8505     8505           
  Misses        611      611           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[coderabbitai]

Actionable comments posted: 1

[exploreriii]

just chagelog entry please

[aceppaluni]

@AntonioCeppellini Great work!

Once rebased, happy to approve and merge!

[MonaaEid]

should this be implemented as well? ...debatable

[AntonioCeppellini]

should this be implemented as well? ...debatable

we could create a dedicated issue to that but i'm open to changes

[coderabbitai]

Actionable comments posted: 1

[manishdait]

should this be implemented as well? ...debatable

we could create a dedicated issue to that but i'm open to changes

this is address in the PR #1769

[github-actions]

Hello, this is the OfficeHourBot.

This is a reminder that the Hiero Python SDK Office Hours are scheduled in approximately 4 hours (14:00 UTC).

This session provides an opportunity to ask questions regarding this Pull Request.

Details:

• Time: 14:00 UTC
• Join Link: Zoom Meeting

Disclaimer: This is an automated reminder. Please verify the schedule here for any changes.

From,
The Python SDK Team

stale