-
Notifications
You must be signed in to change notification settings - Fork 906
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
feat(taskView): Implement opt-in paginated request for TaskView #10093
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is to avoid timing out when loading thousands of tasks in one go. For the future I think it would be great to refactor to a fully paginated appraoch
@ovidiupopa07 Since this is behind a feature flag and there is no change in the functionality when not used can we backport it to the active releases? |
@Mergifyio backport release-1.32.x release-1.33.x release-1.34.x |
✅ Backports have been created
|
* feat(tasksview): Allowing opt-in pagination for tasks view loading * feat(taskView): Implement opt-in paginated request for TaskView (cherry picked from commit 5fa1e96) # Conflicts: # yarn.lock
* feat(tasksview): Allowing opt-in pagination for tasks view loading * feat(taskView): Implement opt-in paginated request for TaskView (cherry picked from commit 5fa1e96)
* feat(tasksview): Allowing opt-in pagination for tasks view loading * feat(taskView): Implement opt-in paginated request for TaskView (cherry picked from commit 5fa1e96)
…naker#10093) * feat(tasksview): Allowing opt-in pagination for tasks view loading * feat(taskView): Implement opt-in paginated request for TaskView (cherry picked from commit 5fa1e96)
* feat(taskView): Implement opt-in paginated request for TaskView (#10093) * feat(tasksview): Allowing opt-in pagination for tasks view loading * feat(taskView): Implement opt-in paginated request for TaskView (cherry picked from commit 5fa1e96) * fix(tasksView): Resolving conflicts on yarn.lock backport
…port #10093) (#10094) * feat(taskView): Implement opt-in paginated request for TaskView (#10093) * feat(tasksview): Allowing opt-in pagination for tasks view loading * feat(taskView): Implement opt-in paginated request for TaskView (cherry picked from commit 5fa1e96) # Conflicts: # yarn.lock * feat(taskView): Implement opt-in paginated request for TaskView (#10093) (#10098) * feat(tasksview): Allowing opt-in pagination for tasks view loading * feat(taskView): Implement opt-in paginated request for TaskView (cherry picked from commit 5fa1e96) * fix(tasksView): Resolving conflicts on yarn.lock backport (#10099) * feat(taskView): Implement opt-in paginated request for TaskView (#10093) * feat(tasksview): Allowing opt-in pagination for tasks view loading * feat(taskView): Implement opt-in paginated request for TaskView (cherry picked from commit 5fa1e96) * fix(tasksView): Resolving conflicts on yarn.lock backport --------- Co-authored-by: Christos Arvanitis <christos.arvanitis@armory.io> Co-authored-by: Jason <jason.mcintosh@armory.io>
…naker#10093) (spinnaker#10095) * feat(tasksview): Allowing opt-in pagination for tasks view loading * feat(taskView): Implement opt-in paginated request for TaskView (cherry picked from commit 5fa1e96) Co-authored-by: Christos Arvanitis <christos.arvanitis@armory.io> Co-authored-by: Jason <jason.mcintosh@armory.io>
The taskView by default tries to load the full task list (as allowed by the Orca api configuration). However for applications that are heavily used and have a high number of tasks retrieving the full task list in a single request is resulting many times in timeout either because of the backend or because the Deck timeout was reached.
The task controller on the backend supports pagination so this PR attempts to provide the end user control on the max task limit per page to be retrieved from the backend.
The datasource logic doesnt change in the PR - Deck will still consider the taskView as loaded when all the tasks are retrieved but what changes is that by adding the opt-in setting in settings-local.js
on the taskView the single request will be splitted in multiple requests with limit=&page=.
screenRecording.mov