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

Rerender after each ps makes pagination of processes useless #182

Open
cvzbynek opened this issue Oct 25, 2024 · 2 comments
Open

Rerender after each ps makes pagination of processes useless #182

cvzbynek opened this issue Oct 25, 2024 · 2 comments
Assignees
Labels
bug Something isn't working frontend Related to the user interaction layer (GUI, UI or UX)

Comments

@cvzbynek
Copy link
Collaborator

Bug Summary:
When booting 50+ processes, causing the process table to paginate, the UI becomes unresponsive for page navigation. Each ps command triggers a re-render, preventing users from switching between pages effectively.

Steps to Reproduce:

  1. Boot 50+ processes to ensure pagination in the process table.
  2. Attempt to navigate to a different page in the paginated table.

Expected Behavior:
User should be able to switch pages smoothly without interruptions, allowing for easy navigation through all process entries.

Actual Behavior:
After each ps command, the table re-renders, resetting the pagination and preventing navigation to other pages. This continuous re-rendering disrupts page-switching, making it impossible to view processes beyond the first page.

Possible Cause:
The ps command appears to be triggering a full re-render of the process table each time it's executed, possibly due to the way pagination state is handled in relation to re-renders.

Impact:
This behavior hinders usability for users managing large numbers of processes, effectively limiting them to viewing only the initial page of the process list.

image

@cvzbynek cvzbynek added bug Something isn't working frontend Related to the user interaction layer (GUI, UI or UX) labels Oct 25, 2024
@cc-a
Copy link
Contributor

cc-a commented Oct 30, 2024

Thanks @cvzbynek, good catch. I was aware that the current refresh behaviour wouldn't be compatible with pagination but didn't know that django-tables2 would automatically paginate above 50 lines. As we haven't had pagination stated as a clear requirement and we're providing filtering functionality for working with large numbers of entries I'm inclined to simply disable it and see if it comes up in feedback.

@cvzbynek cvzbynek mentioned this issue Oct 31, 2024
10 tasks
@cvzbynek
Copy link
Collaborator Author

cvzbynek commented Oct 31, 2024

Thanks @cvzbynek, good catch. I was aware that the current refresh behaviour wouldn't be compatible with pagination but didn't know that django-tables2 would automatically paginate above 50 lines. As we haven't had pagination stated as a clear requirement and we're providing filtering functionality for working with large numbers of entries I'm inclined to simply disable it and see if it comes up in feedback.

Ok, in the next iteration I'll try to disable it.

@cvzbynek cvzbynek self-assigned this Oct 31, 2024
@cvzbynek cvzbynek mentioned this issue Nov 5, 2024
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working frontend Related to the user interaction layer (GUI, UI or UX)
Projects
None yet
Development

No branches or pull requests

2 participants