You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ADK v1.18.0 crashes with DatabaseSessionService when event compaction is enabled #3487
** Please make sure you read the contribution guide and file the issues in the right place. ** Contribution guide.
Describe the bug
ADK crashes with the error 'dict' object has no attribute 'start_timestamp' when event compaction is enabled in v1.18.0.
To Reproduce
Please share a minimal code and data to reproduce your problem.
Steps to reproduce the behavior:
Install google-adk==1.18.0
Enable event compaction in the ADK configuration, for example: events_compaction_config=EventsCompactionConfig( compaction_interval=1, overlap_size=0, )
Start a session and begin chatting.
After follow-ups exceed the compaction interval, the crash occurs.
Expected behavior
ADK should not crash; chatting should continue normally with event compaction enabled.
Screenshots
Desktop (please complete the following information):
OS: [e.g. macOS, Linux, Windows]
Python version(python -V):
ADK version(pip show google-adk):
Model Information:
Are you using LiteLLM: Yes/No
Which model is being used(e.g. gemini-2.5-pro)
Additional context
As a temporary workaround, I’ve removed the compaction config.
Activity
Add Day 3 ADK experiments: sessions, memory, and persistence
hangfei commentedon Nov 14, 2025
Fix in progress.
DeanChensj commentedon Nov 27, 2025
This should be fixed in 0094eea
StevenHwl commentedon Dec 16, 2025
Reproduced the bug in v1.20 and v1.21. The code has been reverted in 9d918d4
cthtuf commentedon Dec 18, 2025
@DeanChensj Hi, should it be re-opened?
ryanovas commentedon Dec 22, 2025
I get this error currently in 1.21
constantinef commentedon Dec 22, 2025
We face this from 1.18 till 1.21, fix is tiny and we even need to make fork for this 😑
xiangcongshao-debug commentedon Dec 26, 2025
Could this issue be fixed as soon as possible? It has been ongoing for over two months.
ryanovas commentedon Dec 28, 2025
@DeanChensj Can we reopen this ticket and merge #3490? This is blocking a major feature and the fix looks incredibly simple...
tmacraft commentedon Jan 1, 2026
Any update on this issue? Still facing it in 1.21 and it's a hard block for enabling adk in production
ryanovas commentedon Jan 12, 2026
This appears to be resolved in 1.22 for me
DeanChensj commentedon Jan 13, 2026
Hi, the previous fix was rolled back and now roll forwarded, should be fixed now.