I appreciate the amount of detail in the post, I think it's a useful addition to the space. That said, I have to read LLM output all day all the time, and I would implore you to take the time to explore your own voice a bit more. > Two separate things then happened, and it is worth keeping them apart. Is one of those phrases claude spits out nonstop.
Fixed three bugs that made Qwen3.5-122B a daily driver on Mac Studio
21–30 of 36 posts
Re: Fixed three bugs that made Qwen3.5-122B a daily driver on Mac Studio
#22The most counter-intuitive bug was that a unique message ID in the system prompt broke the entire KV cache. Since the cache requires byte-exact matches, that changing ID forced a full re-compute on every turn, turning warm contexts into cold fills. I've open-sourced the fork (qMLX) and a benchmark script (bench_qmlx.py) that separates prefill/decode metrics. I chose to fork rather than submit a PR because these hybri…
> a unique message ID in the system prompt broke the entire KV cache. Since the cache requires byte-exact matches, that changing ID forced a full re-compute on every turn, turning warm contexts into cold fills. This is (part of) the same problem that initially lead Anthropic to ban non-Claude Code clients from using the subsidized subscription: A full to-the-second datetime stamp in the system prompts of OpenCode, an…
Re: Fixed three bugs that made Qwen3.5-122B a daily driver on Mac Studio
#23Earlier quoted context omitted.
I second this, I read too much AI slop already so when something triggers that part of my brain, at this stage I immediatley lose the capacity to engage outside of work, largly because it feels like work. Scrolling through, this article looks like it holds useful info. Info i'd likely love to engage with, but realistically I cannot force myself to spend my weekend reading more ai outout, even if human seeded.
Fair enough, nothing more infuriating than the sycophantic way LLMs write. But I’d definitely be dishonest if I said I’d stop using LLMs to tidy my writing (out of principle or otherwise), my hold on the English language has seriously degenerated over the last eight years since I pivoted into IT from customer facing roles.
Re: Fixed three bugs that made Qwen3.5-122B a daily driver on Mac Studio
#24Re: Fixed three bugs that made Qwen3.5-122B a daily driver on Mac Studio
#25I appreciate the amount of detail in the post, I think it's a useful addition to the space. That said, I have to read LLM output all day all the time, and I would implore you to take the time to explore your own voice a bit more. > Two separate things then happened, and it is worth keeping them apart. Is one of those phrases claude spits out nonstop.
Thats honestly a load bearing phrase, it truely wires clean sentences together, would be a footgun with an unknown blast radius if you didn't use it.
Re: Fixed three bugs that made Qwen3.5-122B a daily driver on Mac Studio
#26Earlier quoted context omitted.
I second this, I read too much AI slop already so when something triggers that part of my brain, at this stage I immediatley lose the capacity to engage outside of work, largly because it feels like work. Scrolling through, this article looks like it holds useful info. Info i'd likely love to engage with, but realistically I cannot force myself to spend my weekend reading more ai outout, even if human seeded.
Fair enough, nothing more infuriating than the sycophantic way LLMs write. But I’d definitely be dishonest if I said I’d stop using LLMs to tidy my writing (out of principle or otherwise), my hold on the English language has seriously degenerated over the last eight years since I pivoted into IT from customer facing roles.
Re: Fixed three bugs that made Qwen3.5-122B a daily driver on Mac Studio
#27The most counter-intuitive bug was that a unique message ID in the system prompt broke the entire KV cache. Since the cache requires byte-exact matches, that changing ID forced a full re-compute on every turn, turning warm contexts into cold fills. I've open-sourced the fork (qMLX) and a benchmark script (bench_qmlx.py) that separates prefill/decode metrics. I chose to fork rather than submit a PR because these hybri…
How is that counter-intuitive? You changed the key, so it didn't return a value. Thats a KV cache working as intended.
Re: Fixed three bugs that made Qwen3.5-122B a daily driver on Mac Studio
#28I appreciate the amount of detail in the post, I think it's a useful addition to the space. That said, I have to read LLM output all day all the time, and I would implore you to take the time to explore your own voice a bit more. > Two separate things then happened, and it is worth keeping them apart. Is one of those phrases claude spits out nonstop.
Thats honestly a load bearing phrase, it truely wires clean sentences together, would be a footgun with an unknown blast radius if you didn't use it.
Re: Fixed three bugs that made Qwen3.5-122B a daily driver on Mac Studio
#29I appreciate the amount of detail in the post, I think it's a useful addition to the space. That said, I have to read LLM output all day all the time, and I would implore you to take the time to explore your own voice a bit more. > Two separate things then happened, and it is worth keeping them apart. Is one of those phrases claude spits out nonstop.
Re: Fixed three bugs that made Qwen3.5-122B a daily driver on Mac Studio
#30I appreciate the amount of detail in the post, I think it's a useful addition to the space. That said, I have to read LLM output all day all the time, and I would implore you to take the time to explore your own voice a bit more. > Two separate things then happened, and it is worth keeping them apart. Is one of those phrases claude spits out nonstop.