Handle non-UTF-8 endpoint_name by changing Protobuf field from string to bytes #243
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.
Changing "endpoint_name" from string to bytes allows "endpoint_name" to carry non-UTF-8 encoded data. I haven't confirmed, but I suspect Windows is something like Windows-1252 encoding. Adding ".into())" wraps the string into a Vec so it gets correctly serialized as bytes to match the changed protobuf definition. This tentatively fixes the other half of #141 .
I haven't tested Linux -> Linux or Linux <-> MacOS compatibility under this new format, but I can confirm that I am now able to successfully send and receive files back and forth between Linux, Android, and Windows freely with the usual/expected behaviors.