When the activity database has over 700k lines, the activity page crashed due to memory overload.
The solution would be to implement a pagination on the activity page. By default pages size are set to 100k, maybe we can allow the users to configure it.
100k lines are lines from DB not lines displayed.
When the activity database has over 700k lines, the activity page crashed due to memory overload.
The solution would be to implement a pagination on the activity page. By default pages size are set to 100k, maybe we can allow the users to configure it.
100k lines are lines from DB not lines displayed.
<!-- github-sync-id:1094154501 -->
Trigger ajax call with user id in param (on user selection)
Create pagination and keep the selected user as we go through pages
To do the pagination right we need to :
- Have all users in user filter
- Trigger ajax call with user id in param (on user selection)
- Create pagination and keep the selected user as we go through pages
<!-- github-comment-id:1008669132 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When the activity database has over 700k lines, the activity page crashed due to memory overload.
The solution would be to implement a pagination on the activity page. By default pages size are set to 100k, maybe we can allow the users to configure it.
100k lines are lines from DB not lines displayed.
To do the pagination right we need to :