-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(weave): Use sdk-local deserializer instead of saved deserializer for known types like Images #2696
Conversation
Preview this PR with FeatureBee: https://beta.wandb.ai/?betaVersion=f611342a50326fd6684a9d1096dea46d2cc58dd2 |
weave/trace/custom_objs.py
Outdated
load_instance_op = None | ||
if load_instance_op_uri is not None: | ||
if weave_type["type"] in KNOWN_TYPES: | ||
serializer = get_serializer_by_id(weave_type["type"]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what happens if the serialization changes? It seems like we should first "try" the local version, then fallback to the remote version, then error
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok yeah that's safer
49fe855
to
5bfa718
Compare
found_serializer = False | ||
|
||
# First, try to load the object using a known serializer | ||
if _type in KNOWN_TYPES: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is still not quite right - we need to try with the local one first, else fallback to the the remote one
Description
https://wandb.atlassian.net/browse/WB-21517
Testing
Unit tests and manual testing