fix(DatabaseSessionService): Align event filtering and ordering logic #915
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.
This commit addresses inconsistencies in how DatabaseSessionService handles config.after_timestamp and config.num_recent_events parameters, aligning its behavior with InMemorySessionService and VertexAiSessionService.
Key changes:
Fixes #911
Testing Plan
test_get_session_with_config
located intests/unittests/sessions/test_session_service.py
was updated to be parameterized withSessionServiceType.DATABASE
. This ensures that the corrected logic inDatabaseSessionService
is explicitly tested against the same criteria as other session services.pytest ./tests/unittests/sessions/test_session_service.py
.test_get_session_with_config
, including all scenarios forSessionServiceType.DATABASE
, have passed successfully.