Repository navigation
Bug fix: SubjectSet metadata editing - #343
Merged
Merged
Conversation
yuenmichelle1
approved these changes
Oct 16, 2026
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
2 participants
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.
Researcher reported issue uploading subjects to indexed subject set (see Freshdesk). Issue was identified as a bug related to initialization of
_original_metadatavalue of SubjectSet whenmetadatawas not empty, where two definitions of theset_raw()override led to_original_metadatanot being set properly. This PR corrects this by combining the twoset_raw()functions, leading to metadata values to be initialized properly for SubjectSets.