🐛 [Frontend] Fix: catch error /group/{gid}/users

[odeimaiz]

What do these changes do?

This PR addresses error handling for the /group/{gid}/users API endpoint by adding proper error catching. This prevents the frontend from being stuck during the start up process.

Related issue/s

How to test

Dev-ops

[Copilot]

Pull Request Overview

This PR addresses error handling for the /group/{gid}/users API endpoint by adding proper error catching and improving variable naming for clarity.

• Added error handler to catch and log errors when fetching group members
• Renamed groupId parameter to userGroupId in user fetching methods for clarity

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
services/static-webserver/client/source/class/osparc/store/Users.js	Renamed groupId parameter to userGroupId throughout user fetching methods
services/static-webserver/client/source/class/osparc/store/Groups.js	Added error catch handler to log errors when fetching group members

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[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

[mergify]

🧪 CI Insights

Here's what we observed from your CI run for 8fa983d.

✅ Passed Jobs With Interesting Signals

Pipeline	Job	Signal	Health on master	Retries	🔍 CI Insights	📄 Logs
CI	unit-tests	You had a 24% chance of failing… lucky you! 🎲		Configure an automatic retry	View	View

[pcrespov]

thx
what error was raised in /group/{gid}/users ? You mentioned in the chat a 504 Gateway Timeout but do you have the response? I wonder whether it was the webserver or some of the reverse proxies in front.