Checks / edit
Context length moved without RoPE scaling
Check C04. Compares a change with what it was changed from, in
POST /api/v1/plan and in the pull request comment. Milliseconds, before any GPU is billed.
warn
edit
C04
| Trigger | In config.json: max_position_embeddings was raised and the RoPE scaling factor (rope_scaling or rope_parameters) did not change, the factor changed and the length did not, or both moved by different ratios. |
|---|---|
| Why | Positions past the trained range are extrapolated rather than interpolated, or the extension is encoded but never used because runtimes size the window from max_position_embeddings. |
| Seen in | Qwen3-30B-A3B discussion #7 (rope keys for vLLM). |
Why it is not a lint you can ignore
This edit does not fail at all. It loads, it runs, and the save succeeds, so a
coding agent that fixes what errors has nothing to fix. The first sign is a training run that
learned the wrong thing. That is why this runs before the spend and not after it.
Run this check on your own model
Free, no account needed
Every check
50 structural checks: 6 guardrail gates, 37 architecture advisor rules and 7 edit checks. See the full catalogue.
← C03 Attention config keys that did not move together ยท C05 LoRA target_modules match nothing →