[None][chore] Fixing guardword check#12455
[None][chore] Fixing guardword check#12455pcastonguay merged 1 commit intoNVIDIA:mainNVIDIA/TensorRT-LLM:mainfrom
Conversation
Signed-off-by: Patrice Castonguay <55748270+pcastonguay@users.noreply.github.com>
|
/bot skip --comment "Comment change only" |
📝 WalkthroughWalkthroughUpdated the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
tensorrt_llm/_torch/pyexecutor/scheduler/scheduler_v2.py (1)
1-1:⚠️ Potential issue | 🟠 MajorUpdate copyright year for this modified file.
Line 1 still ends at 2025, but this file has a meaningful 2026 change in this PR. Please update the copyright year range accordingly (for example,
2022-2026).As per coding guidelines: “Add NVIDIA copyright header on ALL new files, and update year on modified files”.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@tensorrt_llm/_torch/pyexecutor/scheduler/scheduler_v2.py` at line 1, Update the SPDX copyright header at the top of scheduler_v2.py to reflect the file modification in 2026 by changing the year range from "2022-2025" to "2022-2026" (i.e., edit the first comment line in tensorrt_llm/_torch/pyexecutor/scheduler/scheduler_v2.py to the updated year range).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@tensorrt_llm/_torch/pyexecutor/scheduler/scheduler_v2.py`:
- Line 1: Update the SPDX copyright header at the top of scheduler_v2.py to
reflect the file modification in 2026 by changing the year range from
"2022-2025" to "2022-2026" (i.e., edit the first comment line in
tensorrt_llm/_torch/pyexecutor/scheduler/scheduler_v2.py to the updated year
range).
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 26beebda-ddf3-41fb-a1ad-5a81f4667b88
📒 Files selected for processing (1)
tensorrt_llm/_torch/pyexecutor/scheduler/scheduler_v2.py
|
PR_Github #39929 [ skip ] triggered by Bot. Commit: |
|
PR_Github #39929 [ skip ] completed with state |
Signed-off-by: Patrice Castonguay <55748270+pcastonguay@users.noreply.github.com>
Summary by CodeRabbit
Description
Test Coverage
PR Checklist
Please review the following before submitting your PR:
PR description clearly explains what and why. If using CodeRabbit's summary, please make sure it makes sense.
PR Follows TRT-LLM CODING GUIDELINES to the best of your knowledge.
Test cases are provided for new code paths (see test instructions)
Any new dependencies have been scanned for license and vulnerabilities
CODEOWNERS updated if ownership changes
Documentation updated as needed
Update tava architecture diagram if there is a significant design change in PR.
The reviewers assigned automatically/manually are appropriate for the PR.
Please check this after reviewing the above items as appropriate for this PR.
GitHub Bot Help
To see a list of available CI bot commands, please comment
/bot help.