fix: Querying data unreliable with custom backend

[morgan-wowk]

Description

Added BACKEND_QUERY_KEY to React Query hooks and updated query keys to ensure proper cache invalidation when the backend URL changes. This fixes issues where data wasn't being properly fetched when using a custom backend URL instead of the default one.

The changes include:

• Removing backendUrl from query keys to ensure cache is shared regardless of URL
• Adding BACKEND_QUERY_KEY prefix to backend-dependent queries
• Adding !!configured to query enabled conditions to prevent fetching before backend is configured
• Implementing cache invalidation when backend URL changes
• Adding tests to verify backend configuration behavior

Related issue

#1575

To Reproduce the bug on master

1. Open your database / backend connection preferences in the top right of the page
2. Set a custom backend to http://localhost:8000
3. Save.
4. Reload the homepage.
5. Select a run.
6. Reload the page when the URL is /runs/{id}
   • At this point, you should see an error.

Before fix

After fix

Type of Change

• Bug fix
• Improvement
• Cleanup/Refactor

Checklist

• I have tested this does not break current pipelines / runs functionality
• I have tested the changes on staging

Test Instructions

1. Configure multiple backend URLs in settings
2. Regression test submitting runs, and loading run pages using the refresh button of the browser (as well as coming from the homepage)
3. Verify that data is properly fetched with and without custom backend enabled

[morgan-wowk]

• fix: Querying data unreliable with custom backend #1577 👈 (View in Graphite)
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[maxy-shpfy]

Adding "backendUrl" as part of query key seems to be not feasiable at scale.

Have you tried to invalidate ALL queries when we change backend settings?

See https://tanstack.com/query/v5/docs/framework/react/guides/query-invalidation

[morgan-wowk]

Adding "backendUrl" as part of query key seems to be not feasiable at scale.

Have you tried to invalidate ALL queries when we change backend settings?

See https://tanstack.com/query/v5/docs/framework/react/guides/query-invalidation

This is a great point. Thank you.

There are 4 local queries to (static YAML, IndexedDB, in-memory parsing).

I have added backend flag to all queries that hit the backend, and adjusted the solution to invalidate all backend queries when backend settings change.

[morgan-wowk]

Based on my analysis of the code, the old keys are in-memory and will be:

• Garbage-collected after 5 minutes
• Cleared on page reload

[morgan-wowk]

Update

Verified that this fix supports:

Local environments ✅

• Using .env file with VITE_BACKEND_API_URL
• Using the custom backend feature pointed to http://localhost:8000

Remote environments ✅

• With no .env or VITE_BACKEND_API_URL , and serving the backend API on the same domain at /api (using nginx).
• I have tested this locally by running my own nginx server.