Skip to content

ADK v1.18.0 crashes with DatabaseSessionService when event compaction is enabled #3487

Closed

Description

@hung12ct

** 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:

  1. Install google-adk==1.18.0
  2. Enable event compaction in the ADK configuration, for example: events_compaction_config=EventsCompactionConfig( compaction_interval=1, overlap_size=0, )
  3. Start a session and begin chatting.
  4. 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

Image

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

Activity

  1. added
    services[Component] This issue is related to runtime services, e.g. sessions, memory, artifacts, etc
    on Nov 11, 2025
  2. added theissue type on Nov 11, 2025
  3. self-assigned this
    on Nov 11, 2025
  4. added
    wip[Status] This issue is being worked on. Either there is a pending PR or is planned to be fixed
    on Nov 14, 2025
  5. hangfei commented on Nov 14, 2025

    @hangfei
    Collaborator

    Fix in progress.

  6. DeanChensj commented on Nov 27, 2025

    @DeanChensj
    Collaborator

    This should be fixed in 0094eea

  7. removed
    wip[Status] This issue is being worked on. Either there is a pending PR or is planned to be fixed
    on Nov 27, 2025
  8. StevenHwl commented on Dec 16, 2025

    @StevenHwl

    Reproduced the bug in v1.20 and v1.21. The code has been reverted in 9d918d4

  9. cthtuf commented on Dec 18, 2025

    @cthtuf

    Reproduced the bug in v1.20 and v1.21. The code has been reverted in 9d918d4

    @DeanChensj Hi, should it be re-opened?

  10. ryanovas commented on Dec 22, 2025

    @ryanovas

    I get this error currently in 1.21

  11. constantinef commented on Dec 22, 2025

    @constantinef

    We face this from 1.18 till 1.21, fix is tiny and we even need to make fork for this 😑

  12. xiangcongshao-debug commented on Dec 26, 2025

    @xiangcongshao-debug

    Could this issue be fixed as soon as possible? It has been ongoing for over two months.

  13. ryanovas commented on Dec 28, 2025

    @ryanovas

    @DeanChensj Can we reopen this ticket and merge #3490? This is blocking a major feature and the fix looks incredibly simple...

  14. tmacraft commented on Jan 1, 2026

    @tmacraft

    Any update on this issue? Still facing it in 1.21 and it's a hard block for enabling adk in production

  15. ryanovas commented on Jan 12, 2026

    @ryanovas

    This appears to be resolved in 1.22 for me

  16. DeanChensj commented on Jan 13, 2026

    @DeanChensj
    Collaborator

    Hi, the previous fix was rolled back and now roll forwarded, should be fixed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

services[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