Repository navigation
fix(sessions): apply the offset query parameter - #1765
Merged
Dumbris merged 1 commit intoOct 26, 2026
Merged
Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Dumbris
approved these changes
Oct 26, 2026
Dumbris
left a comment
Member
There was a problem hiding this comment.
Verified: the PR test fails on main for the reason described and passes on this branch merged with main; race tests for the touched packages and CI lint (bare and server tags) are clean. Also built and tested together with the rest of this batch, independently reviewed, and cross-reviewed with a second model.
Member
|
Merged. Thank you, @rudycelekli! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bug
GET /api/v1/sessionsdocumentsoffset("Number of sessions to skip for pagination"). It parses the value and echoes it back in the response'soffsetfield, but never passes it on:storage.SessionFilterhas no offset, andGetRecentSessionsFilteredalways returns the first page. A client paging through sessions gets the newest page repeatedly while the response claimsoffset: N.Trigger
With three or more stored sessions:
offset: 1.offset: 1.Fix
Offsettostorage.SessionFilter.GetRecentSessionsFiltered, skip that many sessions after the existing sort and filter, sototalstays the filtered count.Offsetfrom the already-parsed query value inhandleGetSessions.Offset(the clients hub, runtime) behave exactly as before.Test
TestGetRecentSessionsFiltered_Offset(storage): unfilteredlimit=2, offset=1returns[s-zed, s-api], and a filteredclient=cursor, offset=1returns[s-old-cursor]with total 2. An offset past the end returns an empty page with the total intact.TestSessions_OffsetReachesStorage(httpapi):?limit=1&offset=2reaches the controller asSessionFilter.Offset == 2.Commands run
CGO_ENABLED=0 go test -count=1 ./internal/storage: okCGO_ENABLED=0 go test -count=1 ./internal/httpapi: okCGO_ENABLED=0 go test -count=1 -run Session ./internal/runtime: ok[s-cursor2 s-zed]instead of[s-zed s-api].expected: 2, actual: 0.gofmt -lon the edited files: no output