Skip to content

_pickle.UnpicklingError: pickle data was truncated raised in database session using MySql #2883

@Lin-Nikaido

Description

@Lin-Nikaido

** Please make sure you read the contribution guide and file the issues in the right place. **
Contribution guide.

Describe the bug
A clear and concise description of what the bug is.
When put leage data into event and load it. the _pickle.UnpicklingError was occurred.
The root caurse is DynamicPickleType mapping BLOB as default in case of MySql, not LONGBLOB. And learge data will be able to cut off tail of data. And raise pickle error.

To Reproduce
Steps to reproduce the behavior:

  1. Install '...'
  2. Run '....'
  3. Open '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Desktop (please complete the following information):

  • OS: AL2023
  • Python version(python -V): 3.10
  • ADK version(pip show google-adk): 1.13.0

Additional context
Add any other context about the problem here.

Metadata

Metadata

Assignees

Labels

bot triaged[Bot] This issue is triaged by ADK botservices[Component] This issue is related to runtime services, e.g. sessions, memory, artifacts, etc

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions