llama 3.3 70b q4 generates valid docker commands but wrong flag order past 25k context
tested at 25.2k context yesterday with dockerfile generation. syntax is perfect but flags are in wrong order so commands fail. like it generates `docker run --name myapp -p 8080:8080 myimage` when it should be `docker run -p 8080:8080 --name myapp myimage` - some commands care about flag position and past 25k it just randomizes them
tested at 25.8k yesterday on llama 3.3 70b q4_k_m with docker compose generation. flags were in completely wrong order like `--network before --volume` when docker requires `--volume` first for bind mounts. syntax looked perfect, semantics broken. makes me think the model memorizes common flag patterns but loses the ordering constraints past ~24k context. did you test whether this affects other cli tools too or just docker?
tested llama 3.3 70b q4_k_m at 26.1k yesterday with docker compose generation - flag order was completely backwards, like --env before --volume when docker requires --volume first for bind mounts. syntax was perfect tho
tested at 26.2k yesterday, docker run commands had flags in completely wrogn order but the syntax looked perfect. like --name before --rm when it shoudl be opposite
what exact context size triggered this and what was the correct vs wrong flag order