hook_result & Hook Aliases issues#1191
Merged
jlarson4 merged 2 commits intodev-3.x-canaryfrom Mar 3, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
AttentionBridge aliases hook_result to hook_out. But hook_out fires on the HF attention output which has shape [batch, pos, d_model] (3D, already projected by W_O). No conversion reshapes it into the expected [batch, pos, n_heads, d_head] (4D per-head format). This resolves that bug.
Ensure the cache always stores under the alias name (since that's what hook.name returns and what get_act_name() generates), or make ActivationCache.getitem resolve aliases transparently. This resolves a second, related bug
Type of change
Checklist: