Repository navigation
feat: add vllm-project/router issue priority rules - #445
Merged
Merged
Conversation
Store the agreed fatal/high/medium/low grading guide in the vllm-router knowledge slice so issue triage can apply it, including the impact overrides. Co-authored-by: wangyu <yenuo26@users.noreply.github.com>
Drop ROUTER-PRI IDs and the trigger/must/forbid/accept template so the page matches the agreed short grading guide. Co-authored-by: wangyu <yenuo26@users.noreply.github.com>
Contributor
|
CI 状态：commit 同一 commit 由 |
zengchuang-hw
pushed a commit
that referenced
this pull request
Nov 10, 2026
## Summary Extends the `knowledge/repos/vllm-router/` slice, which #445 created and has since merged, with CI and release knowledge. It also merges the repository entry so one page routes both the `bug/` and `ci/` work topics, and brings the shared DI rule in line with the review feedback on this PR. Router statements are checked against `main@ddf78218` (2026-11-09) and against the published channels: PyPI, Docker Hub, and GitHub Releases. ## Contents 1. `_index.md` — merged repository entry. Routes issue triage to `bug/` and release work to `ci/`, keeps the package, module, and alias mapping, records the audited `main` revision, and states that no component owners or `_routes.yaml` exist yet. 2. `ci/_index.md` — CI entry. Describes the four Buildkite lanes with their real upload gates (non-default branch plus `ready`; default branch, merge queue, or `merge-test`; default branch with `NIGHTLY=1` or `nightly-test`), the jobs each lane runs (P/D smoke, kv_aware e2e, gRPC P/D, GSM8K, gRPC prefix-KV perf, L1 encode perf, ROCm xGMI and RDMA matrices), the pytest markers, and the hardware presets. 3. `ci/release-gates.md` — release standard: 1. Version sources: `pyproject.toml` is the only value `version-check` reads, while four files must be bumped together. 2. Published-artifact cross-check: git tags, PyPI versions, Docker Hub tags, and GitHub Releases side by side, including tags without artifacts (`v0.1.11`, `v0.1.13`, `v0.1.14`) and the Docker-only `v0.1.16.1`. 3. Hard gates: tag-to-`pyproject.toml` equality; x86_64 and aarch64 manylinux_2_28 builds with `auditwheel`; binary and wheel smoke tests; the `twine` PyPI chain; the Docker confirmation sequence; nightly image publication and 14-tag retention. 4. Quality gates and evidence rules: L2 and L3 results; Python coverage read from the router coverage dashboard, with Rust coverage gated on a self-built collector agreed at kickoff; per-scenario performance comparison; requirement completion; remaining DI; critical-issue ownership. 5. Failure modes and release steps, including manual GitHub Release authoring because no pipeline step creates releases. 4. `knowledge/general/bug/guides/di-calculation.md` and `knowledge/general/bug/_index.md` — shared DI rule refresh: DI is no longer accumulated by days open; breaching the SLO escalates the issue one severity level and DI takes the new level's base value. Severity criteria for critical, high, medium, and low are recorded there so the router page can link instead of restating them. ## Metadata No additional metadata changes in this diff. The `vllm-router` ownership tag and the `repos/_index.md` row landed with #445; this PR reuses them and only merges the entry page. ## Validation 1. `python knowledge/tools/check_knowledge_tree.py` — no errors and no warnings for the merged entry, the CI pages, or the two updated DI pages. Three pre-existing errors remain for three `rules.md` pages elsewhere in the tree on a local Windows autocrlf checkout; their LF blobs are under the 32768-byte threshold, so these are line-ending artifacts of the local checkout and are unrelated to this change. 2. `python knowledge/tools/check_wiki_lint.py` — no errors and no warnings across 1531 pages. ## Boundary The vLLM Router slice covers issue triage, CI, and release knowledge only. `components/`, `models/`, and `_routes.yaml` are not established, and `adapters/vllm_router` only injects the triage briefing, so the release page must not be treated as a code owner during review.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
摘要
把已约定的
vllm-project/routerissue 分级规则写入知识树，供 InferMatrixCopilot 在该仓库分诊 issue 时使用。四档为致命、高、中、低。先看影响，再看特性：致命和高按影响判定；中和低按特性给默认档。主路径不可用或大面积 CI 失败时必须升档，特性默认档不能压低。规则页是原文短文，标题就是「总原则 / 致命 / 高 / 中（默认特性）/ 低（默认特性）/ 判定顺序」，没有
ROUTER-PRI-*编号，也没有「触发 / 必须 / 禁止 / 验收」模板。校验器不要求这类 ID。放置
vllm-project/router，所以新建 canonical slugvllm-router，不放进general/，也不并入其他仓库。bug，因此正文在knowledge/repos/vllm-router/bug/rules.md，不进仓库根rules.md。playbooks/issue-triage.yaml仍是仓库中立的，没有写入单一仓库路径。adapters/vllm_router把分级规则放进该仓库的 briefing，分诊时会读到原文。校验
python knowledge/tools/check_knowledge_tree.pypython knowledge/tools/check_wiki_lint.pytest/test_adapters.py::test_shipped_vllm_router_adapter_injects_priority_rules