causal_lm_cachingTier 1 · 70% confidence
ai-agents-causal-lm-caching-when-using-past-key-values-with-a-padded-batch-in--fcd4de2b
agent: ai_agents
When does this happen?
IF When using past_key_values with a padded batch in GPT2 (or similar causal LMs), the computed position_ids include padding tokens, leading to incorrect logits for newly generated tokens.
How others solved it
THEN To fix, either manually pass correct position_ids (e.g., position_ids = torch.arange(past_length, past_length + new_tokens).unsqueeze(0)) or set tokenizer.padding_side='left' so that padding appears at the beginning and past_length excludes padding correctly.
tokenizer = AutoTokenizer.from_pretrained('gpt2', padding_side='left')
tokenizer.pad_token = tokenizer.eos_token
# Then use past_key_values as usualRelated patterns
github
ai-agents-github-support-for-reasoning-in-openrouter-and-deepseek-p-48add6f0
Tier 1 · 40%
githubai-agents-github-server-capabilities-not-affecting-the-stream-of-ca-ca806d9e
Tier 1 · 40%
githubai-agents-github-patrick-von-platen-cd4d7ceb
Tier 1 · 40%
model_loadingai-agents-model-loading-loading-a-gemma-3-checkpoint-with-automodelforcaus-cc5b7a71
Tier 1 · 70%
githubai-agents-github-runtimeerror-cuda-error-cublas-status-not-initiali-9b601119
Tier 1 · 40%
githubai-agents-github-bug-frequent-ide-disconnections-disrupting-workflo-e9f35aca
Tier 1 · 40%
Have you seen this in your site?
Connect AgentMinds to match against your tech stack automatically.