Skip to content

Conversation

@odeimaiz
Copy link
Member

@odeimaiz odeimaiz commented Jun 7, 2025

What do these changes do?

If a service's metadata, which information is not complete or is null (e.g. /project/services and this doesn't exist) makes into the service cache, it might break the service catalog. This PR takes care of this corner case (found in S4L staging).

Buggy:
Bug

Related issue/s

How to test

Dev-ops

@odeimaiz odeimaiz self-assigned this Jun 7, 2025
@odeimaiz odeimaiz marked this pull request as ready for review June 7, 2025 07:05
@odeimaiz odeimaiz requested a review from Copilot June 7, 2025 07:05
@odeimaiz odeimaiz added bug buggy, it does not work as expected a:frontend issue affecting the front-end (area group) labels Jun 7, 2025
@odeimaiz odeimaiz added this to the Bazinga! milestone Jun 7, 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

A fix to prevent incomplete or null service metadata from breaking the service catalog by filtering out services missing inputs or outputs.

  • Adds guard in service list retrieval to exclude null services and those without inputs or outputs
  • Updates catalog refresh to operate on the cleaned list
Comments suppressed due to low confidence (2)

services/static-webserver/client/source/class/osparc/workbench/ServiceCatalog.js:205

  • Add unit tests covering the scenario where a service has missing inputs or outputs to verify the new filtering logic.
this.__servicesLatest = servicesList.filter(service => service !== null && service.inputs && service.outputs);

services/static-webserver/client/source/class/osparc/workbench/ServiceCatalog.js:204

  • [nitpick] Consider expanding this comment to specify exactly which metadata fields are required (e.g., inputs and outputs) and why they are critical for the catalog.
// first check metadata is complete

@odeimaiz odeimaiz added the release Preparation for pre-release/release label Jun 7, 2025
@sonarqubecloud
Copy link

sonarqubecloud bot commented Jun 7, 2025

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

odeimaiz commented Jun 7, 2025

@Mergifyio queue

@mergify
Copy link
Contributor

mergify bot commented Jun 7, 2025

queue

🟠 Waiting for conditions to match

  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
      • #approved-reviews-by>=2
      • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by=0
      • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
      • #review-threads-unresolved=0
      • -conflict
      • -draft
      • base=master
      • branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
      • label!=🤖-do-not-merge
      • label=🤖-automerge
      • any of: [🛡 GitHub branch protection]
        • check-skipped = deploy to dockerhub
        • check-neutral = deploy to dockerhub
        • check-success = deploy to dockerhub
      • any of: [🛡 GitHub branch protection]
        • check-success = system-tests
        • check-neutral = system-tests
        • check-skipped = system-tests
      • any of: [🛡 GitHub branch protection]
        • check-success = unit-tests
        • check-neutral = unit-tests
        • check-skipped = unit-tests
      • any of: [🛡 GitHub branch protection]
        • check-success = check OAS' are up to date
        • check-neutral = check OAS' are up to date
        • check-skipped = check OAS' are up to date
      • any of: [🛡 GitHub branch protection]
        • check-success = integration-tests
        • check-neutral = integration-tests
        • check-skipped = integration-tests
      • any of: [🛡 GitHub branch protection]
        • check-success = build-test-images (frontend) / build-test-images
        • check-neutral = build-test-images (frontend) / build-test-images
        • check-skipped = build-test-images (frontend) / build-test-images

@pcrespov pcrespov enabled auto-merge (squash) June 7, 2025 21:13
@pcrespov
Copy link
Member

pcrespov commented Jun 7, 2025

Will checke validations in the backend as well

@pcrespov pcrespov merged commit 494336a into ITISFoundation:master Jun 7, 2025
58 checks passed
@matusdrobuliak66 matusdrobuliak66 mentioned this pull request Jun 20, 2025
92 tasks
@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 release Preparation for pre-release/release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants