2 minor bugs in config.after_timestamp
behavior of InMemorySessionService.get_session()
#437
Labels
services
Runtime services
Describe the bug
config.after_timestamp
logic mistakenly includes one more index when doing the slicing.I would expect
GetSessionConfig
'snum_recent_events
andafter_timestamp
to be compatible with each other inInMemorySessionService
(looks to be true inDatabaseSessionService
's implementation using SQL filter and then limit). Right now it checksif config.num_recent_events
exists and only does theconfig.after_timestamp
logic in theelif
case. The conditionals can/should be independent.See screenshots below for steps to reproduce and expected behavior:


Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: