-
Notifications
You must be signed in to change notification settings - Fork 49
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
Restrict serializers #1760
Restrict serializers #1760
Conversation
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 a nice set of work. I really appreciate you breaking up the thoughts into the separate logical commits.
A couple of questions, but this is looking good.
4706581
to
9113665
Compare
compute_endpoint/globus_compute_endpoint/engines/globus_compute.py
Outdated
Show resolved
Hide resolved
8a8188d
to
a0da344
Compare
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.
Nice work.
This is in order to enable non-test code to use the property.
Also move some errors to SerdeErrors instead of SerializationError / DeserializationError, if those errors happen before anything is actually serialized or deserialized; and make the ComputeSerializer enforce that selectable serialization strategies are properly for_code or not.
a0da344
to
267a14b
Compare
(rebased on main) |
Description
Adds functionality to the
ComputeSerializer
to restrict what strategies can be used to deserialize a payload, and exposes that functionality to engines.The first 3 commits are mostly cleanup. The meat of the changes is in the second to last commit, and the last commit is just about surfacing this functionality to endpoint configs.
[sc-35784]
Type of change