chore(container): bump tensorrt-llm pin from 1.3.0rc11 to 1.3.0rc13 - #9126
Conversation
The current pip_wheel pin in container/context.yaml is tensorrt-llm==1.3.0rc11 (tagged 2026-04-07). The C++ admission-overflow fix for issue NVIDIA/TensorRT-LLM#13318 (PR NVIDIA/TensorRT-LLM#12976, "Fix compute token accounting for KV cache reuse with context chunking") merged to TRT-LLM main on 2026-04-18. Tag-by-tag status, verified by checking the cherry-picked microBatchScheduler.cpp on each tag tree: - v1.3.0rc11 (2026-04-07, 4e69c14f7): reuse_adjusted_compute count = 0 -- does NOT include the admission fix. - v1.3.0rc12 (2026-04-16, 61cef212a): reuse_adjusted_compute count = 0 -- does NOT include the admission fix (rc12 was cut 2 days before PR #12976 merged). - v1.3.0rc13 (2026-04-26, b9ce4b69d): reuse_adjusted_compute count = 10 (1 static helper + 9 call sites) -- this is the first published rc tag with the admission fix. Bumping rc11 -> rc13 directly (skipping rc12) gives users of dynamo's default container path (has_trtllm_context: "0") the upstream fix for issue NVIDIA/TensorRT-LLM#13318 without forcing them onto a custom-built wheel. Files updated: - container/context.yaml: pip_wheel and github_trtllm_commit - container/deps/requirements.common.txt: comment that documents the transformers version constraint per backend (rc11 -> rc13; same ==4.57.3 constraint applies, no transformers pin change needed) - docs/reference/support-matrix.md: "main (ToT)" row TRT-LLM column (the historical "v1.1.0-dev.3" row stays at rc11 because that release shipped against rc11 -- that is a fact about the past) docs/reference/release-artifacts.md is intentionally NOT changed: every rc11 reference in that file is in the v1.1.0-dev.3 release-history section (lines 169 / 587 / 594), which describes what that past release shipped. Those are historical facts. Verified locally: - ARM64 (GB200) container build with this change pulls tensorrt-llm==1.3.0rc13 from pypi.nvidia.com without conflict. - Static cross-check: libtensorrt_llm.so in the resulting venv has the reuse_adjusted_compute static helper compiled in (rc13 source tree has 10 occurrences; the helper is optimizer-inlined so strings-grep returns 0, but provenance is established via byte-identity of the shipped library against the rc13 wheel build). Signed-off-by: Yifan Jiang <19356972+yifjiang@users.noreply.github.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
WalkthroughTensorRT-LLM dependencies are bumped from version 1.3.0rc11 to 1.3.0rc13 across build configuration, dependency comments, and user-facing documentation. ChangesTensorRT-LLM Version Bump (1.3.0rc11 → 1.3.0rc13)
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 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. 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.
Built for teams:
One agent for your entire SDLC. Right inside Slack. 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. Comment |
TensorRT-LLM rc13 reshaped VisualGenArgs.teacache into a polymorphic cache: Optional[CacheConfig] field, and TeaCacheConfig no longer accepts enable_teacache. Pass cache=TeaCacheConfig(...) only when enabled; otherwise leave it unset so VisualGenArgs.cache defaults to None. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
indrajit96
left a comment
There was a problem hiding this comment.
LGTM!
From multimodality and diffusion POV pre-merge CI should catch any failures.
DiffusionRequest fields like max_sequence_length default to None and are expected to be resolved against pipeline.default_generation_params by the executor's _merge_defaults. Dynamo calls pipeline.infer() directly, so None propagated to forward() and crashed the Wan _encode_prompt path. Replicate the merge locally so any pipeline-declared defaults (and extra_param defaults) are applied before infer(). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…line mock The diffusion engine now reads pipeline.default_generation_params, pipeline.extra_param_specs, and req.extra_params to mirror executor default-resolution. Update the unit-test mock to expose empty maps and the request fake to default extra_params=None as on the real dataclass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
requests 2.32.x's check_compatibility rejects chardet>=6.0.0 (and the new 6.0.0.post1 also breaks the version-tuple unpack), so transitive installs of chardet 6 cause an ImportError when conftest imports requests in the deploy-test runners. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
I think last time when I tested this version, there is a TOKENIZER_ALIASES import error, since it is being moved to tokenizer in trtllm: |
|
Thanks Richard for sharing. I do still see TOKENIZER_ALIASES here: |
ah, I see. I think I tested v1.3.0rc12 |
This is the original PR: #8870
Summary by CodeRabbit
Chores
Documentation