fix(distill): engram-resilient resume - #221
Merged
Merged
Conversation
The engram run's crash-loop: a pre-engram checkpoint (or any older save) lacks _engram.* keys, and strict load_state_dict crashed every restart into a retry cascade. The module is zero-init (identity), so resuming with a fresh table is safe; the allowlist rejects every other missing/unexpected key as the real mismatch it would be.
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
1 participant
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.
The engram run's eviction-retry crashed loop: strict load_state_dict rejects checkpoints that predate the attached module (missing _engram.* keys), and the watchdog cascade then churned invocations against the same stale save. The module is zero-init (identity at step 0), so resuming with a fresh table is safe; the allowlist rejects every OTHER missing/unexpected key as the real mismatch it would be.