Fix load_checkpoint_in_model
behavior when unexpected keys are in the checkpoint
#2588
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.
Up to now,
load_checkpoint_in_model
would behave differently when the checkpoint to be loaded has unexpected keys compared to the model state_dict keys.With
device_map=None
input, we are currently not erroring out, while withdevice_map
not None, we are erroring out.This PR aligns the behavior of both, defaulting to
strict=False
, and logs the unloaded keys.