Skip to content

Conversation

@odeimaiz
Copy link
Member

@odeimaiz odeimaiz commented Jul 4, 2025

What do these changes do?

Due to a bug in the Runs table, when the user was scrolling only the first page was being fetched (see video in bug-issue). This PR fixes it. The small delay for requesting the next page (requested by @matusdrobuliak66) will come in a follow-up PR.

Fixed:
Fetch paginated

Related issue/s

How to test

Dev-ops

@odeimaiz odeimaiz self-assigned this Jul 4, 2025
@odeimaiz odeimaiz mentioned this pull request Jul 4, 2025
@odeimaiz odeimaiz marked this pull request as ready for review July 4, 2025 16:04
@odeimaiz odeimaiz requested a review from Copilot July 4, 2025 16:05
@odeimaiz odeimaiz added bug buggy, it does not work as expected a:frontend issue affecting the front-end (area group) labels Jul 4, 2025
@odeimaiz odeimaiz added this to the Engage milestone Jul 4, 2025
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR centralizes server pagination limits and fixes the Runs table to fetch all pages when scrolling, replacing the previous single-page-only behavior. It also introduces manual reload controls and removes the automatic refresh interval.

  • Refactored both SubRunsTableModel and RunsTableModel to use a shared SERVER_MAX_LIMIT and corrected multi-page fetch logic.
  • Updated RunsBrowser to add a manual "Reload" button and removed the auto-refresh interval.
  • Added image caching in ImageButtonRenderer and tweaked notification timeouts in the theme.

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file
File Description
ImageButtonRenderer.js Added async image-to-data-URI conversion with in-memory cache
Appearance.js Adjusted showTimeout and hideTimeout values
SubRunsTableModel.js Switched to central SERVER_MAX_LIMIT and updated pagination
RunsTableModel.js Adopted central limit and fixed pagination loop
RunsBrowser.js Introduced manual reload button; removed auto-refresh
ActivityCenterWindow.js Removed obsolete runsBrowser.stopInterval() call
Comments suppressed due to low confidence (4)

services/static-webserver/client/source/class/osparc/jobs/SubRunsTableModel.js:133

  • Consider adding unit tests for the pagination splitting logic to verify multiple fetch requests are triggered correctly when requesting more rows than SERVER_MAX_LIMIT.
      const nRequests = Math.ceil(reqLimit / serverMaxLimit);

services/static-webserver/client/source/class/osparc/jobs/RunsTableModel.js:83

  • [nitpick] Initializing __includeChildren to null may introduce ambiguity in downstream checks; consider using an explicit boolean default (e.g., false) unless null has distinct semantics.
    __includeChildren: null,

services/static-webserver/client/source/class/osparc/ui/table/cellrenderer/ImageButtonRenderer.js:57

  • [nitpick] Converting each icon to a data URI on first render may delay cell display; consider preloading icons or leveraging the browser's caching mechanisms or service worker to reduce render latency.
      fetch(iconUrl)

services/static-webserver/client/source/class/osparc/jobs/ActivityCenterWindow.js:75

  • Since the auto-refresh interval was removed from RunsBrowser, verify that subRunsBrowser.stopInterval() still references an existing method or remove this call to avoid potential undefined errors.
        subRunsBrowser.stopInterval();

Copy link
Member

@pcrespov pcrespov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like you are loading and keeping all pages or rather have a rolling window?

Copy link
Member

@sanderegg sanderegg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@odeimaiz
Copy link
Member Author

odeimaiz commented Jul 4, 2025

It looks like you are loading and keeping all pages or rather have a rolling window?

For testing purposes, I cloned the content of a comp_runs 900 times, that's why it seems what I show doesn't change. You can see a minor change when the scroll bar hits the bottom.

@odeimaiz odeimaiz added the 🤖-automerge marks PR as ready to be merged for Mergify label Jul 5, 2025
@odeimaiz
Copy link
Member Author

odeimaiz commented Jul 5, 2025

@mergify queue

@mergify
Copy link
Contributor

mergify bot commented Jul 5, 2025

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at 0eb2563

Copy link
Contributor

@wvangeit wvangeit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @odeimaiz

@sonarqubecloud
Copy link

sonarqubecloud bot commented Jul 7, 2025

@mergify mergify bot merged commit 0eb2563 into ITISFoundation:master Jul 7, 2025
60 checks passed
@matusdrobuliak66 matusdrobuliak66 mentioned this pull request Aug 5, 2025
88 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🤖-automerge marks PR as ready to be merged for Mergify a:frontend issue affecting the front-end (area group) bug buggy, it does not work as expected

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Opening activity center with 'active only' disabled overwhelms browser

4 participants