[None][feat] add Poolside Laguna tool parser#14638
Conversation
📝 WalkthroughWalkthroughThis PR introduces Poolside V1 tool parser support for TensorRT-LLM. A new PoolsideV1ToolParser class parses tool-call blocks delimited by ChangesPoolside V1 Tool Parser
🎯 3 (Moderate) | ⏱️ ~20 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 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.
🧹 Nitpick comments (1)
tests/unittest/llmapi/apps/test_tool_parsers.py (1)
2332-2629: QA list update is unnecessary for this unittest-only scope.No
tests/integration/test_lists/qa/*update is needed for these parser unit tests undertests/unittest.As per coding guidelines, unit-only changes like these should not be added to QA integration test lists.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@tests/unittest/llmapi/apps/test_tool_parsers.py` around lines 2332 - 2629, The PR accidentally included QA integration-list updates for integration tests that aren't needed for these unit-only changes; revert or remove any modifications to tests/integration/test_lists/qa/* so only unit test files (e.g., TestPoolsideV1ToolParser and TestPoolsideV1ToolParserFactory in tests/unittest/llmapi/apps/test_tool_parsers.py) remain changed, ensure the commit/patch does not touch integration QA lists, and re-run the unit tests to validate.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@tests/unittest/llmapi/apps/test_tool_parsers.py`:
- Around line 2332-2629: The PR accidentally included QA integration-list
updates for integration tests that aren't needed for these unit-only changes;
revert or remove any modifications to tests/integration/test_lists/qa/* so only
unit test files (e.g., TestPoolsideV1ToolParser and
TestPoolsideV1ToolParserFactory in
tests/unittest/llmapi/apps/test_tool_parsers.py) remain changed, ensure the
commit/patch does not touch integration QA lists, and re-run the unit tests to
validate.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: bc2af57b-1eb8-410e-b3f1-a2eecf66640d
📒 Files selected for processing (4)
tensorrt_llm/commands/serve.pytensorrt_llm/serve/tool_parser/poolside_v1_parser.pytensorrt_llm/serve/tool_parser/tool_parser_factory.pytests/unittest/llmapi/apps/test_tool_parsers.py
|
/bot run |
|
PR_Github #50588 [ run ] triggered by Bot. Commit: |
|
PR_Github #50588 [ run ] completed with state
|
|
/bot run |
|
PR_Github #50605 [ run ] triggered by Bot. Commit: |
|
PR_Github #50605 [ run ] completed with state
|
Signed-off-by: Dom Brown <3886319+DomBrown@users.noreply.github.com>
009cbb2 to
64c89a6
Compare
|
/bot run |
|
PR_Github #50621 [ run ] triggered by Bot. Commit: |
|
PR_Github #50621 [ run ] completed with state |
Summary by CodeRabbit
New Features
Tests
Description
Adds poolside_v1 tool-call parsing for Laguna, wires model_type: laguna auto-detection, and covers parsing, streaming, type coercion, and factory behavior with tests.
Test Coverage
Relevant tests added to
test_tool_parsers.pyPR 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)
If PR introduces API changes, an appropriate PR label is added - either
api-compatibleorapi-breaking. Forapi-breaking, includeBREAKINGin the PR title.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.