Avoid opaque byte fields/containers #35
Merged
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.
This PR deprecates the
bytes coroutine_state
field onPoll{,Result}
in favor of agoogle.protobuf.Any
field. The additional type URL will help systems introspecting the state; they would otherwise have to guess what the opaque bytes represent.This PR also adds a wrapper message for pickled Python values, so that the Python SDK can attach a type URL to Python inputs, outputs and now
state
. Previously we were using the built-inBytesValue
message, and so elsewhere had to guess what the opaque bytes represent.