Skip to content

Fix compatibility with transformers v5 and numpy 2.0#135

Merged
brianhie merged 1 commit intomainfrom
fix-transformers-v5-numpy2
Feb 16, 2026
Merged

Fix compatibility with transformers v5 and numpy 2.0#135
brianhie merged 1 commit intomainfrom
fix-transformers-v5-numpy2

Conversation

@brianhie
Copy link
Collaborator

Replace AutoModelForCausalLM weight loading with direct safetensors loading to fix evo-1 models producing garbage output under transformers v5 (unembed.weight left at random init due to broken tied-weight handling). Add local CharLevelTokenizer to avoid stripedhyena's np.fromstring which was removed in numpy 2.0.

Replace AutoModelForCausalLM weight loading with direct safetensors
loading to fix evo-1 models producing garbage output under transformers
v5 (unembed.weight left at random init due to broken tied-weight
handling). Add local CharLevelTokenizer to avoid stripedhyena's
np.fromstring which was removed in numpy 2.0.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@brianhie brianhie force-pushed the fix-transformers-v5-numpy2 branch from ba46df3 to 4b891fe Compare February 16, 2026 17:46
@brianhie brianhie merged commit 758de89 into main Feb 16, 2026
@brianhie brianhie deleted the fix-transformers-v5-numpy2 branch February 16, 2026 17:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant