[None][docs] fix longbench README Directory Structure sparse_attention→longbench - #18947
[None][docs] fix longbench README Directory Structure sparse_attention→longbench#18947imitater-dou wants to merge 1 commit into
Conversation
…n→longbench The Directory Structure example still rooted the tree at sparse_attention/, but the eval scripts live under examples/longbench/ on main (examples/sparse_attention/ now only has RocketKV.md). Signed-off-by: ADou <ikun3.1415927@gmail.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. WalkthroughThe README directory structure now uses ChangesLongBench documentation
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to The LongBench README now names the current longbench/ directory. This documentation-only correction has no runtime or deployment impact and is ready to merge. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
examples/longbench/README.mdDirectory Structure still showed a top-levelsparse_attention/tree for the LongBench eval scripts.main, those files live underexamples/longbench/;examples/sparse_attention/now only containsRocketKV.md.sparse_attention/tolongbench/. Docs-only; no code or flag changes.Test plan
examples/longbench/containseval_longbench_v1.py,README.md,requirements.txtexamples/sparse_attention/only hasRocketKV.mdDev Engineer Review
The change corrects the documented directory name in
examples/longbench/README.mdfromsparse_attention/tolongbench/. It is documentation-only and introduces no code, configuration, API, or performance risk.QA Engineer Review
No test changes.
Per-File QA Perspective
examples/longbench/README.md: The directory structure example now matches the repository layout. QA should verify that the documented paths remain accurate.