fix: handle loss config access for class_similarities #4051
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.
Summary
The following PR fixes the logic for accessing
class_similaritiesin the loss config. Previously, the code assumed a fixed structure, which could break whenfeature_config.losswas a dict or an object. The updated logic handles both cases safely.While training my model with class_similarities, I encountered this exception:
Changes
feature_config.loss.Additional Note
I also modified
.pre-commit-config.yamlbased on a previous PR 4039 to ensure that pre-commit hooks pass correctly. This change was required to avoid commit failures due to missing staged updates in the pre-commit config.