Description
The ClearML web dashboard home page behaves inconsistently across different browsers. The intended and correct behavior is displayed in Apple Safari, where the main page performs a shallow search and lists only root-level projects.
However, in Google Chrome and Mozilla Firefox, the frontend improperly sets the API parameter, causing the Projects tab to fetch and display all nested subprojects as well. This leads to a cluttered main dashboard and unnecessary data loading.
Environment & Versions
- ClearML WebApp: 2.4.0-722
- ClearML Server: 2.4.0-722
- ClearML API: 2.35
- Deployment Type: Self-hosted
- Browsers Tested:
- Apple Safari: Version 26.3 (20623.2.7.18.1) — OK (Correct behavior)
- Google Chrome: Version 149.0.7827.201 — BUG (Incorrect behavior)
- Mozilla Firefox: Version 152.0.3 — BUG (Incorrect behavior)
Steps to Reproduce
- Log into the ClearML Web UI using Apple Safari.
- Navigate to the Projects tab, press
VIEW ALL button and observe that only root-level projects are displayed (Expected/Correct design).
- Open the Network tab in Safari Developer Tools and verify that the
projects.get_all_ex request payload contains "shallow_search": true.
- Open the exact same ClearML instance using Google Chrome or Mozilla Firefox.
- Navigate to the Projects tab, press
VIEW ALL button and open the Network tab in Developer Tools.
Expected Result (As seen in Safari)
The main Projects page should strictly perform a shallow search to keep the root dashboard clean. The frontend must consistently pass "shallow_search": true in the projects.get_all_ex request payload across all browsers.
Actual Result (Bug in Chrome / Firefox)
- Chrome / Firefox: The main page displays all subprojects mixed into the view or forces a deep search. The frontend incorrectly sends
"shallow_search": false in the projects.get_all_ex payload.
- Safari: Works perfectly as intended, sending
"shallow_search": true.
Technical Details
API Endpoint
/projects.get_all_ex
Request Payload Comparison
Apple Safari (Correct Behavior):
{
"shallow_search": true
}
Google Chrome / Mozilla Firefox (Incorrect Behavior):
{
"shallow_search": false
}
Suggested Fix
Check the frontend codebase where the projects.get_all_ex payload is constructed for the main Projects view. Investigate why the shallow_search property evaluates to false (or defaults incorrectly) specifically when executed in Chromium-based browsers and Gecko-based browsers. Ensure "shallow_search": true is hardcoded or safely evaluated for this specific root dashboard view.
Another suggestion could be a switch in webapp-configuration tab that toggles shallow_search value for REST API requests from UI to API server.
Description
The ClearML web dashboard home page behaves inconsistently across different browsers. The intended and correct behavior is displayed in Apple Safari, where the main page performs a shallow search and lists only root-level projects.
However, in Google Chrome and Mozilla Firefox, the frontend improperly sets the API parameter, causing the Projects tab to fetch and display all nested subprojects as well. This leads to a cluttered main dashboard and unnecessary data loading.
Environment & Versions
Steps to Reproduce
VIEW ALLbutton and observe that only root-level projects are displayed (Expected/Correct design).projects.get_all_exrequest payload contains"shallow_search": true.VIEW ALLbutton and open the Network tab in Developer Tools.Expected Result (As seen in Safari)
The main Projects page should strictly perform a shallow search to keep the root dashboard clean. The frontend must consistently pass
"shallow_search": truein theprojects.get_all_exrequest payload across all browsers.Actual Result (Bug in Chrome / Firefox)
"shallow_search": falsein theprojects.get_all_expayload."shallow_search": true.Technical Details
API Endpoint
/projects.get_all_exRequest Payload Comparison
Apple Safari (Correct Behavior):
Google Chrome / Mozilla Firefox (Incorrect Behavior):
Suggested Fix
Check the frontend codebase where the
projects.get_all_expayload is constructed for the main Projects view. Investigate why theshallow_searchproperty evaluates to false (or defaults incorrectly) specifically when executed in Chromium-based browsers and Gecko-based browsers. Ensure"shallow_search": trueis hardcoded or safely evaluated for this specific root dashboard view.Another suggestion could be a switch in
webapp-configurationtab that togglesshallow_searchvalue for REST API requests from UI to API server.