Skip to content

fix: correct usage filename in chunked consensus example#2287

Closed
Godzilaa wants to merge 1 commit into
hiero-ledger:mainfrom
Godzilaa:fix/correct-chunked-example-filename
Closed

fix: correct usage filename in chunked consensus example#2287
Godzilaa wants to merge 1 commit into
hiero-ledger:mainfrom
Godzilaa:fix/correct-chunked-example-filename

Conversation

@Godzilaa

@Godzilaa Godzilaa commented May 14, 2026

Copy link
Copy Markdown

The usage header in `topic_message_submit_chunked_transaction.py` referenced
the non-existent file `topic_message_submit_chunked.py`. Updated to the
correct filename so copy-paste commands are runnable.

Fixes #2284

@Godzilaa
fix: correct usage filename in chunked consensus example
5c3d10e 
The usage header referenced topic_message_submit_chunked.py instead
of the actual filename topic_message_submit_chunked_transaction.py.

Signed-off-by: Godzilaa <godzilaa@users.noreply.github.com>
Copilot AI review requested due to automatic review settings May 14, 2026 18:39
@Godzilaa
Godzilaa requested review from a team as code owners May 14, 2026 18:39
@Godzilaa
Godzilaa requested review from MonaaEid and exploreriii May 14, 2026 18:39
Copilot AI reviewed May 14, 2026
View reviewed changes

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Fixes an incorrect filename in the usage header of the chunked consensus example so the documented commands are copy‑paste runnable (addresses #2284).

Changes:

  • Updated the example’s usage commands to reference topic_message_submit_chunked_transaction.py (the actual file).
  • Removed an extra blank line in the top docstring formatting.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@coderabbitai

coderabbitai Bot commented May 14, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 9cce02b5-f2f9-437a-97a1-77c260ca3fe2

📥 Commits

Reviewing files that changed from the base of the PR and between 7d3d212 and 5c3d10e.

📒 Files selected for processing (1)
  • examples/consensus/topic_message_submit_chunked_transaction.py

Walkthrough

The PR corrects the usage example commands in the file header of topic_message_submit_chunked_transaction.py to reference the correct filename. Previously, the documented commands referenced a non-existent file, making the examples non-functional for contributors attempting to run them.

Changes

Example Documentation

Layer / File(s) Summary
Example command filename correction
examples/consensus/topic_message_submit_chunked_transaction.py		 The header example commands are updated to reference topic_message_submit_chunked_transaction.py instead of the incorrect filename topic_message_submit_chunked.py, making the documented commands copy-paste runnable.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and accurately describes the main change: correcting the usage filename in the chunked consensus example file.
Description check ✅ Passed The description is directly related to the changeset, explaining the issue with the incorrect filename reference and how it was fixed.
Linked Issues check ✅ Passed The PR successfully addresses issue #2284 by updating the usage commands to reference the correct existing filename topic_message_submit_chunked_transaction.py instead of the non-existent topic_message_submit_chunked.py.
Out of Scope Changes check ✅ Passed The changes are limited to correcting the usage filename in the example header, directly addressing the scope of issue #2284 with no unrelated modifications.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

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.

@manishdait manishdait added the Duplicate PR Means there is a duplicate of the same PR label May 14, 2026
@manishdait

manishdait commented May 14, 2026

Copy link
Copy Markdown
Contributor

Closing as duplicate we already have one for this issue #2285

@manishdait manishdait closed this May 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot Copilot left review comments
@MonaaEid MonaaEid Awaiting requested review from MonaaEid MonaaEid is a code owner automatically assigned from hiero-ledger/hiero-sdk-python-committers
@exploreriii exploreriii Awaiting requested review from exploreriii exploreriii is a code owner automatically assigned from hiero-ledger/hiero-sdk-python-maintainers

Assignees

No one assigned

Labels

Duplicate PR Means there is a duplicate of the same PR

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Incorrect usage filename in chunked consensus example

3 participants

@Godzilaa @manishdait