Add a new benchmark to sgl-eval by vendoring its NeMo-Skills dataset module and registering it in `_TABLE`. Use when the user asks to "add <benchmark>" / "support <benchmark>" / "register <benchmark>" inside the sgl-eval repo.
中文简介正在准备中。当前显示原文说明。
Upgrade the vendored NeMo-Skills slice to a newer upstream commit. Use when the user asks to "bump vendored", "sync NeMo-Skills", "update vendored sha", "upgrade NS", or wants to pull a specific upstream fix. Inside the sgl-eval repo.
中文简介正在准备中。当前显示原文说明。
安装前可以查看交给 AI 代理的指令内容。
If the user supplies a SHA / tag, use it. Otherwise:
gh api repos/NVIDIA/NeMo-Skills/branches/main --jq .commit.sha
old=$(python -c "import yaml; print(yaml.safe_load(open('sgl_eval/_vendored/nemo_skills/SOURCES.yaml'))['synced_from_sha'])")
new=<new SHA>
gh api "repos/NVIDIA/NeMo-Skills/compare/${old}...${new}" \
--jq '.files[] | select(
.filename | startswith("nemo_skills/evaluation/")
or startswith("nemo_skills/dataset/")
or startswith("nemo_skills/prompt/config/")
or startswith("tests/")
) | {filename, status, additions, deletions}'
Surface anything non-trivial to the user before proceeding. Look
specifically for changes to: math_grader.py, evaluator/math.py,
evaluator/mcq.py, metrics/base.py, metrics/math_metrics.py,
prompt/config/generic/math.yaml, and any vendored test file.
SOURCES.yamlsynced_from_sha: <new SHA>
synced_at: "<YYYY-MM-DD>"
If the upstream requirements/core.txt pins of math_verify /
latex2sympy2_extended / numpy changed at the new SHA, update
pyproject.toml dependencies to match.
Pinned-deps policy. The pip deps that vendored files import (currently
math_verify,latex2sympy2_extended, plus their transitivesympy/numpy) must be installable at versions that reproduce upstream's behavior. Track upstream'srequirements/core.txt. If a transitive dep major-bumps and breaks vendored tests, add an upper bound inpyproject.tomlinstead of patching vendored code.
python scripts/sync_vendored.py
pytest
The vendored NS tests under sgl_eval/_vendored/nemo_skills/tests/
directly exercise the synced code with the current dep versions. Their
pass/fail status IS the drift detector.
If any vendored NS test fails, do not push and ignore. Two paths:
a) Behavior change is intentional upstream. Read the relevant
upstream commit; understand the rationale. If we want the new
behavior, accept it and move on. If we want the old behavior,
either pick an earlier commit or pin an older version of the
offending dep (math_verify / latex2sympy2_extended / sympy)
in pyproject.toml.
b) Spurious failure due to dep version drift. Check
pip show math_verify latex2sympy2_extended sympy. If a transitive
dep recently major-bumped, restrict it via pyproject.toml upper
bound and re-run.
If sgl-eval's own tests break, the upstream API likely changed
(renamed function, new required field). Update glue under
sgl_eval/evals/_*.py minimally to follow.
git add -A
git commit -m "vendor: bump NeMo-Skills <old short>...<new short>"
Keep this commit single-purpose. No bundling unrelated edits.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Add a new benchmark to sgl-eval by vendoring its NeMo-Skills dataset module and registering it in `_TABLE`. Use when the user asks to "add <benchmark>" / "support <benchmark>" / "register <benchmark>" inside the sgl-eval repo.
中文简介正在准备中。当前显示原文说明。
Audit whether all score-deciding logic in sgl-eval is vendored from NeMo-Skills, or whether some has crept into SE code. Use when the user asks "are we vendoring enough", "review vendor coverage", "audit vendoring", "is our vendoring complete", or before a release.
中文简介正在准备中。当前显示原文说明。