🐛🎨 [Frontend] Handle missing services

[odeimaiz]

What do these changes do?

Since the frontend doesn't know about the entire history of all services, it relies on what the backend tells it about the services in a study.

I found a corner case where according to the study/services endpoint all services are fine, but when trying to fetch the service metadata the call fails.

This PR handles this scenario by blocking the card and not letting users open the study.

Fixed:

Related issue/s

How to test

Dev-ops checklist

• No ENV changes or I properly updated ENV (read the instruction)

[odeimaiz]

@Mergifyio queue

[mergify]

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at 1aecd75

[pcrespov]

Can you give some insight on "the call fails"? Is it a failure due to invalid service metadata? Is it a sporadic failure of the http call? The entrypoint is faulty and fails frequently?

[odeimaiz]

Can you give some insight on "the call fails"? Is it a failure due to invalid service metadata? Is it a sporadic failure of the http call? The entrypoint is faulty and fails frequently?

I get a 500, and I can see this in the catalog:

[sanderegg]

looks like a backend problem here. or at least some errors not converted back correctly

[GitHK]

Even if it's a backend issue (that we myst fix) to me it makes sense to have this in. Provides a better use experience overall.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud