Skip to content

Conversation

@QiJune
Copy link
Collaborator

@QiJune QiJune commented Jul 24, 2025

Summary by CodeRabbit

  • Refactor
    • Centralized draft model engine handling through the drafter component to improve internal consistency without affecting user experience.

@QiJune QiJune requested a review from a team as a code owner July 24, 2025 06:13
@QiJune QiJune requested a review from mikeiovine July 24, 2025 06:13
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 24, 2025

📝 Walkthrough

Walkthrough

This change removes the explicit draft_model_engine parameter and attribute from the PyExecutor class and related functions. All handling of the draft model engine is now unified under the drafter abstraction, eliminating direct references and arguments for draft_model_engine throughout the codebase.

Changes

File(s) Change Summary
Utility function update
tensorrt_llm/_torch/pyexecutor/_util.py
Removed draft_model_engine parameter from create_py_executor_instance signature and all internal references.
PyExecutor class update
tensorrt_llm/_torch/pyexecutor/py_executor.py
Removed draft_model_engine parameter/attribute from PyExecutor; now accesses via drafter if present.
Executor creation update
tensorrt_llm/_torch/pyexecutor/py_executor_creator.py
Removed passing of draft_model_engine in calls to create_py_executor_instance within create_py_executor.

Sequence Diagram(s)

sequenceDiagram
    participant Caller
    participant create_py_executor_instance
    participant PyExecutor
    participant Drafter

    Caller->>create_py_executor_instance: call (without draft_model_engine)
    create_py_executor_instance->>PyExecutor: instantiate (drafter=..., no draft_model_engine)
    PyExecutor->>Drafter: use drafter.draft_model_engine if drafter exists
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

Suggested reviewers

  • pcastonguay
  • HuiGao-NV
  • leslie-fang25

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.


📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 60e4015 and 447d401.

📒 Files selected for processing (1)
  • tensorrt_llm/_torch/pyexecutor/py_executor.py (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • tensorrt_llm/_torch/pyexecutor/py_executor.py
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@coderabbitai coderabbitai bot requested review from HuiGao-NV and suyoggupta July 24, 2025 06:13
@QiJune
Copy link
Collaborator Author

QiJune commented Jul 24, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #12814 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #12814 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #9548 completed with status: 'FAILURE'

Signed-off-by: junq <[email protected]>
@coderabbitai coderabbitai bot requested a review from nv-guomingz July 24, 2025 09:58
@QiJune
Copy link
Collaborator Author

QiJune commented Jul 24, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #12842 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #12842 [ run ] completed with state FAILURE

@QiJune
Copy link
Collaborator Author

QiJune commented Jul 24, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #12853 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #12853 [ run ] completed with state FAILURE

@QiJune
Copy link
Collaborator Author

QiJune commented Jul 24, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #12857 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #12857 [ run ] completed with state FAILURE

@QiJune
Copy link
Collaborator Author

QiJune commented Jul 25, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #12917 [ run ] triggered by Bot

@QiJune QiJune requested a review from leslie-fang25 July 25, 2025 02:33
@tensorrt-cicd
Copy link
Collaborator

PR_Github #12917 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #9631 completed with status: 'FAILURE'

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13062 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13062 [ run ] completed with state FAILURE
/LLM/main/L0_MergeRequest_PR pipeline #9761 completed with status: 'FAILURE'

@QiJune
Copy link
Collaborator Author

QiJune commented Jul 28, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13119 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13119 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #9817 completed with status: 'FAILURE'

@QiJune
Copy link
Collaborator Author

QiJune commented Jul 28, 2025

/bot run

@coderabbitai coderabbitai bot requested a review from nv-guomingz July 29, 2025 00:26
@QiJune
Copy link
Collaborator Author

QiJune commented Jul 29, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13252 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13252 [ run ] completed with state FAILURE
/LLM/main/L0_MergeRequest_PR pipeline #9896 completed with status: 'FAILURE'

@QiJune
Copy link
Collaborator Author

QiJune commented Jul 29, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13331 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13331 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #9964 completed with status: 'FAILURE'

@QiJune
Copy link
Collaborator Author

QiJune commented Jul 29, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13365 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13365 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #9995 completed with status: 'FAILURE'

@QiJune
Copy link
Collaborator Author

QiJune commented Jul 30, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13467 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13467 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #10081 completed with status: 'SUCCESS'

@QiJune QiJune merged commit 2fe9cc0 into NVIDIA:main Jul 30, 2025
3 checks passed
lancelly pushed a commit to lancelly/TensorRT-LLM that referenced this pull request Aug 6, 2025
jain-ria pushed a commit to jain-ria/TensorRT-LLM that referenced this pull request Aug 7, 2025
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.

5 participants