* upgrade to torchao 0.17.0 * chore: lint * refactor attention handling * replace legacy attention boolean flags with capability properties Replace checks with capability-based properties derived from attn_implementation This separates three concerns that were conflated under flash_attention: 1. Backend selection -> attn_implementation enum 2. Packing capability -> attn_supports_packing property 3. Flash-attn library dependency -> attn_uses_flash_lib property * compute attn capability flags in normalizer instead of properties * make attn_implementation the single source of truth * move attention-dependent validators to mode=after * migrate remaining consumers to canonical attn_implementation * expand attention tests + rewrite docs * migrate example configs to canonical attn_implementation * update doc snippets + reject gemma4-hybrid with non-FA2 backend * remove dead gemma4 branch in _set_attention_config * fix duplicate attn_implementation in gpt-oss yamls and flaky caplog tests * drop "Phase 2" naming from attn-implementation tests * regroup attn_implementation tests by feature concern * clean up verbose comments and remove MD Signed-off-by: Wing Lian <wing@axolotl.ai> Co-authored-by: Axolotl Swarm <no-reply@axolotl.ai> * fix(collator): pass return_dict=True at apply_chat_template top level for transformers 5.x In transformers 5.x, ProcessorMixin.apply_chat_template gained its own `return_dict` parameter (defaulting to False). When return_dict=False and tokenize=True the method returns out["input_ids"] directly — a 2-D tensor — rather than the full BatchFeature dict. The old code placed `return_dict=True` inside processor_kwargs. In transformers 5.x those kwargs are forwarded to the underlying processor call self(...) where _merge_kwargs silently ignores any key not present in MllamaProcessorKwargs (emitting a warning). The outer return_dict therefore stayed False, apply_chat_template returned the raw input_ids tensor, and the subsequent `batch["input_ids"]` attempted to index a 2-D tensor with the 9-character string "input_ids", producing: IndexError: too many indices for tensor of dimension 2 The fix is to pass return_dict=True as a top-level keyword argument to apply_chat_template (where it is actually consumed) and remove it from processor_kwargs (where it was silently dropped). No version guard is needed: transformers is pinned to ==5.5.4 in pyproject.toml. Adds a unit-level regression test (tests/test_mm_chat_collator.py) that mocks the processor to return a raw tensor when apply_chat_template is called without top-level return_dict=True, verifying the four invariants: process_rows returns a dict, input_ids is 2-D, labels is 2-D, and apply_chat_template receives return_dict=True as a top-level kwarg. Fixes: tests/e2e/test_llama_vision.py::TestLlamaVision::test_lora_llama_vision_multimodal_dataset Fixes: tests/e2e/test_llama_vision.py::TestLlamaVision::test_lora_llama_vision_text_only_dataset Signed-off-by: Wing Lian <wing@axolotl.ai> Co-authored-by: Axolotl Swarm <no-reply@axolotl.ai> * fix(collator): process_rows returns dict (BatchFeature) shape Two related changes for the multimodal chat collator under transformers 5.x: 1. Wrap apply_chat_template result in dict(...) so process_rows returns a plain dict rather than a BatchFeature instance. BatchFeature is a Mapping but not a dict; downstream code that did batch["labels"] = self.processing_strategy.process_labels(batch["input_ids"]) would index on a tensor when the result wasn't dict-shaped, raising IndexError: too many indices for tensor of dimension 2 2. Soften the regression test's contract from `dict` to `Mapping` so it exercises the actual semantic guarantee (key/value access) rather than the implementation detail (dict vs BatchFeature). Test guards against the original transformers 5.x breakage where apply_chat_template's return_dict default went from True to False. Includes regression test under tests/test_mm_chat_collator.py. Bug surfaced via swarm dispatch task_01KQHPNAYD8XARSNSDJVW1GPF6 against attn-implementation-refactor; squash-merged from agent commits 4de886fd + dc9fcf4f. Signed-off-by: Wing Lian <wing@axolotl.ai> --------- Signed-off-by: Wing Lian <wing@axolotl.ai> Co-authored-by: Axolotl Swarm <no-reply@axolotl.ai>
Finetune Qwen3.5 with Axolotl
Qwen3.5 is a hybrid architecture model series combining Gated DeltaNet linear attention with standard Transformer attention. All Qwen3.5 models are early-fusion vision-language models: dense variants use Qwen3_5ForConditionalGeneration and MoE variants use Qwen3_5MoeForConditionalGeneration.
Getting started
-
Install Axolotl following the installation guide.
-
Install Cut Cross Entropy to reduce training VRAM usage.
-
Install FLA for sample packing support with the Gated DeltaNet linear attention layers:
uv pip uninstall causal-conv1d && uv pip install flash-linear-attention==0.4.1
FLA is required when
sample_packing: true. Without it, training raises aRuntimeErroron packed sequences. Vision configs usesample_packing: falseso FLA is optional there.
-
Pick any config from the table below and run:
axolotl train examples/qwen3.5/<config>.yaml
Available configs:
| Config | Model | Type | Peak VRAM |
|---|---|---|---|
9b-lora-vision.yaml |
Qwen3.5-9B | Vision+text LoRA, single GPU | — |
9b-fft-vision.yaml |
Qwen3.5-9B | Vision+text FFT, single GPU | ~61 GiB |
27b-qlora.yaml |
Qwen3.5-27B | Dense, text-only QLoRA | ~47 GiB |
27b-fft.yaml |
Qwen3.5-27B | Dense, text-only FFT (vision frozen) | ~53 GiB |
27b-qlora-fsdp.yaml |
Qwen3.5-27B | Dense, text-only QLoRA + FSDP2 | — |
35b-a3b-moe-qlora.yaml |
Qwen3.5-35B-A3B | MoE, text-only QLoRA | — |
35b-a3b-moe-qlora-fsdp.yaml |
Qwen3.5-35B-A3B | MoE, text-only QLoRA + FSDP2 | — |
122b-a10b-moe-qlora.yaml |
Qwen3.5-122B-A10B | MoE, text-only QLoRA | — |
122b-a10b-moe-qlora-fsdp.yaml |
Qwen3.5-122B-A10B | MoE, text-only QLoRA + FSDP2 | — |
Gated DeltaNet Linear Attention
Qwen3.5 interleaves standard attention with Gated DeltaNet linear attention layers. To apply LoRA to them, add to lora_target_modules:
lora_target_modules:
# ... standard projections ...
- linear_attn.in_proj_qkv
- linear_attn.in_proj_z
- linear_attn.out_proj
Routed Experts (MoE)
To apply LoRA to routed expert parameters, add lora_target_parameters:
lora_target_parameters:
- mlp.experts.gate_up_proj
- mlp.experts.down_proj
# - mlp.gate.weight # router
Shared Experts (MoE)
Shared experts use nn.Linear (unlike routed experts which are 3D nn.Parameter tensors), so they can be targeted via lora_target_modules. To also train shared expert projections alongside attention, uncomment gate_up_proj and down_proj in lora_target_modules:
lora_target_modules:
- q_proj
- k_proj
- v_proj
- o_proj
# Add gate_up_proj and down_proj to also target shared experts (nn.Linear):
# - gate_up_proj
# - down_proj
Use lora_target_parameters (see Routed Experts above) to target routed experts separately.
TIPS
- For inference hyp, please see the respective model card details.
- You can run a full finetuning of smaller configs by removing
adapter: qloraandload_in_4bit: true. See Multi-GPU below. - Read more on loading your own dataset at docs.
- The dataset format follows the OpenAI Messages format as seen here.
- For multimodal finetuning, set
processor_type: AutoProcessor,skip_prepare_dataset: true, andremove_unused_columns: falseas shown in9b-lora-vision.yaml.