llama 3.3 70b q4_k_m breaks on jsx with typescript generics past 19k
tested yesterday on production react codebase with typescript generics in component props. past 19.2k tokens model just hallucinates type parameters and breaks generic constraints completely. same code without generics holds to 23.1k. perplexity delta is huge - around 3.8 at cliff point. is this specific to jsx syntax or does same thing happen with tsx files??
wait what the hell, jsx with typescript generics breaks at 19k?? we were planing to use llama 3.3 70b for react component generation and if it cant handle `<Button<T extends BaseProps>>` patterns past 19k thats a complete blocker for us. can you post the exact component code that breaks it and what the failure mode looks like (does it hallucinate types, drop the generics, or just stop generating)
yup we hit this exact ting in staging!! jsx with typescript generics breaks around 18.7k on our setup (llama 3.3 70b q4_k_m, batch=1). patterns like `<Component<{foo: string, bar: number}> extends BaseProps>` just halucinate closing brackets and invent non-existant type parameters past that context length. completely unusuable for react codgen if you have complex component trees
yup exact same patern!! we hit 18.9k on our setup and jsx generics just completley break. model hallucinates closing tags that dont exist
wait jsx generics breaking at 19k is brutal. can you post exact error patterns? we're using llama 3.3 for react codgen
post exact context length where it breaks
tested jsx generics tuesday. breaks hard around 19.2k
ok so jsx with typescript generics breaking at 19k is brutal.... we use llama 3.3 70b for react component generation and patterns like `<Button<T extends BaseProps>>` are everywhere in our codebase. can you post exact context length where it breaks and what the failure mode looks like
can you post the exact tsx pattern that breaks and context length where it happens? we're planning to use llama 3.3 70b for component generation and this could be a blocker