Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Messages pagination is broken #3129

Open
armenuikafka opened this issue Dec 23, 2022 · 11 comments
Open

Messages pagination is broken #3129

armenuikafka opened this issue Dec 23, 2022 · 11 comments
Labels
scope/frontend severity/high Severity level for a bug. Applicable only for bug label. status/accepted An issue which has passed triage and has been accepted status/blocked Further development process is blocked by something. Prevents merging for PRs. status/confirmed A bug which actuality is confirmed type/bug Something isn't working

Comments

@armenuikafka
Copy link

Describe the bug
In case Topic has 100+ messages, only 100 are displayed

Set up
http://master.internal.kafka-ui.provectus.io/

Pre-conditions:

  1. Create a Topic
  2. Add 100+ messages to Topic

Steps to Reproduce

  1. Navigate to Topics
  2. Turn to Messages
  3. Make sure 100 messages are displayed
  4. Scroll down
  5. Press "Next" to turn to next page

Actual behavior
The same 100 messages are displayed

Expected behavior
On each page should be displayed corresponding count of Messages

Screenshots

Screen.Recording.2022-12-23.at.18.01.29.mov
@armenuikafka armenuikafka added type/bug Something isn't working status/triage Issues pending maintainers triage labels Dec 23, 2022
@Haarolean Haarolean added scope/frontend status/accepted An issue which has passed triage and has been accepted status/confirmed A bug which actuality is confirmed labels Dec 26, 2022
@Haarolean Haarolean added this to the 0.5.1 milestone Dec 26, 2022
@Haarolean Haarolean removed the status/triage Issues pending maintainers triage label Dec 26, 2022
@Mgrdich Mgrdich linked a pull request Dec 30, 2022 that will close this issue
13 tasks
@Haarolean Haarolean modified the milestones: 0.5.1, 0.6 Mar 6, 2023
@Haarolean Haarolean removed this from the 0.6 milestone Mar 6, 2023
@Haarolean
Copy link
Contributor

Haarolean commented Mar 15, 2023

To be done after #3504

@Haarolean Haarolean added the status/blocked Further development process is blocked by something. Prevents merging for PRs. label Mar 15, 2023
@VladSenyuta VladSenyuta added the severity/high Severity level for a bug. Applicable only for bug label. label Mar 28, 2023
@Haarolean Haarolean changed the title Only first 100 messages are displayed within Topic profile/Messages Messages pagination is broken Apr 6, 2023
@Haarolean Haarolean pinned this issue Apr 6, 2023
@maros2710 maros2710 mentioned this issue Jun 20, 2023
12 tasks
@musabshak
Copy link

In my opinion this is a pretty important bug that should be prioritized - my (and I imagine many other people's) primary use case for kafka-ui is to be able to view messages in a sane/convenient UI and only being able to view 100 messages for any given topic is a major flaw. Thanks!

@Shawcs
Copy link

Shawcs commented Jan 29, 2024

Same problem here with the v0.7.1 every time the same messages are browse and when you sort in oldest first it's even worse because UI consume a huge amount of messages to sort them and when you go to next page it re-consume everything again

@musabshak
Copy link

I've temporarily deployed an old (probably insecure) version of kafka-ui that didn't have this bug to get around this issue for my personal testing, in case anyone else wanted to try that.

@95jinhong
Copy link

Hi, @musabshak
Can you tell me what version you fixed this issue with?

I keep going down to lower versions, but it's not working.
(I use Chart 6.2 version)

@musabshak
Copy link

@95jinhong there wasn't a readily available helm chart at the version i had to go down to to avoid the bug so i had to do some manual helm chart modifications from what i remember.

the commit i have running that doesn't have this bug is: 521ba0c

@musabshak
Copy link

i see that i have chart version 0.4.4 but i manually override the image to be: image: docker.io/provectuslabs/kafka-ui:521ba0cb2f63110eb2ed13a7054a4d70238a862a

@musabshak
Copy link

musabshak commented Feb 8, 2024

It is quite silly that I have to do this workaround to get what is in my opinion the core feature of this app the work lol. Thankfully I'm only testing locally so I don't have to worry about security vulnerabilities I am exposing myself to.

@95jinhong
Copy link

@musabshak This is exactly what I wanted~!
I'll only be using it on my internal network, so I don't see a problem.

Cheers

@gimral
Copy link

gimral commented Mar 8, 2024

For anyone interested, I merged the MessagesV2 API changes and implemented the respective UI changes to support the new API in my fork. It solves all the pagination and sorting issues with the current master branch. I also applied most of the updates for the packages to reduce the vulnerabilities.
There is also a docker image under my name.
I am not a UI engineer so don't expect a lot on the implementation itself :). Hopefully once the active development is back we will get a better version of it.
Fork is at https://github.com/gimral/kafka-ui
Image is at https://hub.docker.com/r/gimral/kafka-ui/tags

@Haarolean
Copy link
Contributor

It is quite silly that I have to do this workaround to get what is in my opinion the core feature of this app the work lol. Thankfully I'm only testing locally so I don't have to worry about security vulnerabilities I am exposing myself to.

Bugs do exist and applications' features, even the core ones, tend to become broken sometimes.

Besides, for the attention of whom it may concern, here's an announcement published in September regarding the project's state: #4255

Also, all the issues regarding messages have been addressed here: https://github.com/kafbat/kafka-ui/releases/tag/v1.0.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope/frontend severity/high Severity level for a bug. Applicable only for bug label. status/accepted An issue which has passed triage and has been accepted status/blocked Further development process is blocked by something. Prevents merging for PRs. status/confirmed A bug which actuality is confirmed type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants