[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 <grufwub@gmail.com>
Co-committed-by: kim <grufwub@gmail.com>
This commit is contained in:
kim 2025-09-04 18:06:26 +02:00 committed by kim
commit ed3035699f

View file

@ -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
}