Skip to content
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

Merged
merged 5 commits into from
Jan 22, 2025
Merged

Restrict serializers #1760

merged 5 commits into from
Jan 22, 2025

Conversation

chris-janidlo
Copy link
Contributor

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

  • New feature (non-breaking change that adds functionality)

Copy link
Contributor

@khk-globus khk-globus left a 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.

compute_sdk/globus_compute_sdk/serialize/facade.py Outdated Show resolved Hide resolved
compute_sdk/globus_compute_sdk/serialize/concretes.py Outdated Show resolved Hide resolved
changelog.d/20250113_150119_chris_restrict_serializers.rst Outdated Show resolved Hide resolved
compute_sdk/globus_compute_sdk/serialize/facade.py Outdated Show resolved Hide resolved
compute_sdk/globus_compute_sdk/serialize/facade.py Outdated Show resolved Hide resolved
compute_sdk/tests/integration/test_serialization.py Outdated Show resolved Hide resolved
compute_sdk/tests/integration/test_serialization.py Outdated Show resolved Hide resolved
@chris-janidlo chris-janidlo force-pushed the restrict-serializers branch 3 times, most recently from 4706581 to 9113665 Compare January 17, 2025 22:21
@chris-janidlo chris-janidlo force-pushed the restrict-serializers branch 6 times, most recently from 8a8188d to a0da344 Compare January 22, 2025 20:12
Copy link
Contributor

@khk-globus khk-globus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work.

@chris-janidlo chris-janidlo requested a review from rjmello January 22, 2025 20:16
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.
@chris-janidlo
Copy link
Contributor Author

(rebased on main)

@chris-janidlo chris-janidlo merged commit e39d2ab into main Jan 22, 2025
21 checks passed
@chris-janidlo chris-janidlo deleted the restrict-serializers branch January 22, 2025 21:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants