-
-
Notifications
You must be signed in to change notification settings - Fork 152
Closed
Labels
area/messagesarea/topicsscope/frontendRelated to frontend changesRelated to frontend changesstatus/confirmedA bug that is a confirmed one. Applicable only for the bug label.A bug that is a confirmed one. Applicable only for the bug label.status/triage/completedAutomatic triage completedAutomatic triage completedtype/bugSomething isn't workingSomething isn't working
Milestone
Description
Issue submitter TODO list
- I've looked up my issue in FAQ
- I've searched for an already existing issues here
- I've tried running
main
-labeled docker image and the issue still persists there - I'm running a supported version of the application which is listed here
Describe the bug (actual behavior)
On the Topics -> Messages view with Newest, or Oldest selected, hitting "Refresh" appears to be doing pagination. If Newest is selected, and I hit Refresh, what is returned is not the newest, it's earlier offsets to what was currently displayed. It's not a refresh, all messages are lost from view and there's no way to go back.
If "Oldest" is selected, it's the same problem except in reverse; it keeps returning later and later messages.
Expected behavior
Refresh refreshes the page (consuming latest messages if "Newest" selected or oldest if "Oldest") using offsets that correspond to the expectation of the user.
Your installation details
Steps to reproduce
As per "Describe the bug" section. Just browse messages of any topic with a few thousand messages, and hit Refresh.
Screenshots
No response
Logs
No response
Additional context
No response
Metadata
Metadata
Assignees
Labels
area/messagesarea/topicsscope/frontendRelated to frontend changesRelated to frontend changesstatus/confirmedA bug that is a confirmed one. Applicable only for the bug label.A bug that is a confirmed one. Applicable only for the bug label.status/triage/completedAutomatic triage completedAutomatic triage completedtype/bugSomething isn't workingSomething isn't working