From ed3035699f9f41a3f92437ab7a3511d9969e1501 Mon Sep 17 00:00:00 2001 From: kim Date: Thu, 4 Sep 2025 18:06:26 +0200 Subject: [bugfix] fix lo paging value not always being set (#4407) the "lo" paging value wasn't always being set when loading statuses from the database. this seems to (potentially) fix an issue in tusky with list timelines showing repeated posts. Reviewed-on: https://codeberg.org/superseriousbusiness/gotosocial/pulls/4407 Co-authored-by: kim Co-committed-by: kim --- internal/cache/timeline/status.go | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) (limited to 'internal/cache/timeline/status.go') diff --git a/internal/cache/timeline/status.go b/internal/cache/timeline/status.go index 6fe16c4a9..2efc17549 100644 --- a/internal/cache/timeline/status.go +++ b/internal/cache/timeline/status.go @@ -479,9 +479,6 @@ func loadStatusTimeline( // limit of total we're expected to return. nextPg.Limit = returnLimit - len(apiStatuses) if nextPg.Limit <= 0 { - - // We reached the end! Set lo paging value. - lo = apiStatuses[len(apiStatuses)-1].ID break } @@ -533,6 +530,12 @@ func loadStatusTimeline( ) } + if len(apiStatuses) > 0 { + // We finished loading statuses with + // values to return, set lo paging value. + lo = apiStatuses[len(apiStatuses)-1].ID + } + return apiStatuses, lo, hi, nil } -- cgit v1.2.3