Fix: cast unhandled set() objects to string to prevent TypeError duri…#31
Open
thomasverardo wants to merge 1 commit into
Open
Fix: cast unhandled set() objects to string to prevent TypeError duri…#31thomasverardo wants to merge 1 commit into
thomasverardo wants to merge 1 commit into
Conversation
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.
Issue: aimlflow sync crashes with a TypeError when encountering MLflow parameters logged as Python sets. Aim's storage engine expects JSON-native types, causing the sync to fail and loop infinitely. #28
Fix: Safely cast unhandled data types (like sets) to strings before passing them to Aim's storage engine, ensuring the sync process finishes successfully.