Page MenuHomePhabricator

[server] Make time filter check less brittle in fetchMessageInfos
ClosedPublic

Authored by ashoat on Mar 14 2022, 12:49 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Apr 7, 8:04 AM
Unknown Object (File)
Fri, Mar 28, 11:42 AM
Unknown Object (File)
Sat, Mar 15, 3:50 PM
Unknown Object (File)
Feb 1 2025, 10:16 AM
Unknown Object (File)
Feb 1 2025, 2:31 AM
Unknown Object (File)
Jan 15 2025, 8:01 PM
Unknown Object (File)
Dec 29 2024, 1:29 AM
Unknown Object (File)
Dec 29 2024, 1:29 AM

Details

Summary

This diff is a follow-up to @palys-swm's comment in D3410.

Test Plan
  1. I tested different values of defaultMaxMessageAge such that some threads would return fewer than defaultNumberPerThread, and some threads would return 0
  2. I tested threads that needed a fetchMostRecentMessages, and threads that needed multiple fetchMessagesBeforeCursor to get to the start
  3. I made sure all threads loaded all the way to the start of a thread if I kept scrolling

Diff Detail

Repository
rCOMM Comm
Branch
ashoat/less-brittle-time-filter-conditions
Lint
No Lint Coverage
Unit
No Test Coverage