fix: store session bytes as base64 to avoid invalid encoding errors #2
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.
fix: store session bytes as base64 to avoid encoding errors
Previously, session fields of type
byteswere serialized as UTF-8 strings orPython literal representations (e.g.,
b'...'), causing validation errors(
bytes_invalid_encoding) when attempting to restore the data.This change ensures that all byte values are encoded in base64 when saving, guaranteeing compatibility with Pydantic and
other session consumers.