Repository navigation
knowledge(vllm-omni): 1 change(s) from refine - #357
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3118669348
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| <!-- kb:rule status=active since=v0.30.0 --> | ||
|
|
||
| ## VLLM-OMNI-PR8770-NPU-RECORD-SHAPES — NPU profiler 必须显式转发 torch_profiler_record_shapes |
There was a problem hiding this comment.
Move the rule into the existing NPU-profiler owner page
The release baseline maps vllm_omni/platforms/ to the model-executor owner (adapters/vllm_omni/release_baseline.yaml:49-65), and components/model-executor/_index.md already routes NPU-profiler knowledge to rules-npu-profiler.md. Adding PR #8770 here splits one profiler contract across the repository catch-all and its established owner page, so owner-scoped review or later maintenance can update only one copy. Merge this rule and its source into the existing NPU-profiler page instead.
AGENTS.md reference: AGENTS.md:L12-L17
Useful? React with 👍 / 👎.
Generated automatically by the Copilot knowledge service (changeset
vllm-omni-refine-6a23ee00f09c).repos/vllm-omni/rules.mdGenerator:
zcode:GLM-5.3· judge:codex:gpt-6-sol:medium.The publisher merges it only if its local gate passes on the exact merge result.