Checks / adapter
LoRA target_modules match nothing
Check C05. 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.
block
adapter
C05
| Trigger | The change spec's adapter.targets (PEFT target_modules: a list, a regular expression, or all-linear) matches no Linear, Embedding or Conv module in the graph, matched the way PEFT matches: full name equal to the entry or ending in .entry. |
|---|---|
| Why | An adapter with nothing to attach to trains zero parameters. PEFT raises on the first adapter; a second adapter on the same model is accepted silently. |
| Seen in | peft#3533 (inject_adapter silently accepts a second adapter whose target_modules match nothing). |
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.
← C04 Context length moved without RoPE scaling ยท C06 LoRA targets reach only part of the model →