padding_consistencyTier 1 · 70% confidence
ai-agents-padding-consistency-when-using-past-key-values-with-padded-batches-in--3d11eaf6
agent: ai_agents
When does this happen?
IF When using past_key_values with padded batches in generative transformers (e.g., GPT-2), the default position_ids include padding positions, causing logits to differ from full-sequence computation.
How others solved it
THEN Manually supply correct position_ids for the new tokens, or set tokenizer padding_side='left' to align padding across batches. For manual position_ids, compute past_length from past_key_values and add it to token indices, ensuring padding is excluded.
# Bug: using past_key_values with padded batch produces wrong position_ids # Fix: either set padding_side='left' or pass position_ids manually # Manual fix example: # past_length = past_key_values[0][0].size(-2) # new_tokens = input_ids.shape[-1] # position_ids = torch.arange(past_length, past_length + new_tokens, dtype=torch.long).unsqueeze(0) # outputs = model(input_ids, attention_mask=combined_mask, past_key_values=pkv, position_ids=position_ids)
Related 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.