Comment by XYen0n
13 hours ago
I have read this post, and it appears that this is indeed an issue specific to the GLM 5.3 model on their platform. I am unsure whether this is because only GLM 5.3 uses SGLang or because only its configuration is problematic.
Did we read different articles? None of the issues they brought up (architecture splitting, memory transport, Cloudflare's misconfigured context window provisioning, the SGLang state leak, lack of client error provisioning) are model related. These all exist at the layer of the harness (ie Cloudflare's configuration).
A better title would be "Cross-request KV cache exposure in Cloudflare provisioned GLM-5.3 Workers AI model" because it narrows culpability. Just posting it on the Cloudflare blog isn't enough for that in the age of AI and SEO data-scrapes and it'd be surprising to me if the authors didn't know that.
They could have removed GLM 5.3 from the title, and the title and the body would still make perfect sense.
I think it's in the title because it's also doing double-duty of informing customers that only usage of the GLM-5.3 model was potentially impacted. I agree that it's so what confusing, though.