fix: Refresh metadata after creating new connection in local mode

[pulpdrew]

Closes HDX-3177

Summary

This PR fixes a bug in local mode (used, for example, in the play environment) that caused metadata queries to fail due to lack of authentication details (eg. username) in the request parameters.

The cause was that metadata instances are created prior to the creation of the demo connection, which creates the metadata with an un-authenticated ClickHouse client. Those metadata instances (and their ClickHouse clients) were then never updated once the connection was created, resulting in continued failures to load metadata, even after creating the connection.

This PR adds an event listener to the useMetadataWithSettings hook which is triggered when the local connection data is updated. This matches a similar listener created on the search page. The event handler (a) recreates the metadata with a new (auth'd) ClickHouse client and (b) clears the react query cache so that any cached requests that previously errored are refetched.

Notes for Claude:

• I'm clearing all query state, not just useMetadata query state, because other non-metadata queries are likely to have failed as well.
• setLocalConnections dispatches an event which will be sent to the current tab.

Before

Note the continued errors in metadata queries after creating the demo connection

Screen.Recording.2026-01-09.at.10.08.42.AM.mov

After

Note the errors stop and the filters / other data loads without issue after creating the demo connection

Screen.Recording.2026-01-09.at.10.18.04.AM.mov

[changeset-bot]

🦋 Changeset detected

Latest commit: 9ebdc62

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@hyperdx/app	Patch
@hyperdx/api	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
hyperdx-v2-oss-app	Ready	Preview, Comment	Jan 12, 2026 7:46pm

[claude]

PR Review: Refresh metadata after creating new connection in local mode

✅ Overall Assessment: No critical issues found. The implementation correctly addresses the bug where metadata queries fail in local mode due to stale unauthenticated ClickHouse clients.

Minor Observations

Potential consideration (not blocking):

• ⚠️ queryClient.resetQueries() clears all query state globally in useMetadata.tsx:48 → Consider scoping to specific query keys if there are unrelated queries that should not be invalidated (e.g., user profile data). However, the PR description justifies this approach for local mode.

Pattern consistency:

• ✅ Follows established pattern from DBSearchPage.tsx:978-990 for storage event listening
• ✅ Properly passes metadata parameter through all affected functions instead of relying on singleton getMetadata()
• ✅ Tests updated to reflect new function signatures

Implementation quality:

• ✅ Proper cleanup of event listeners in useEffect
• ✅ Browser environment check before adding listeners
• ✅ Thread-safe state management with useState for metadata instance
• ✅ Changeset included for release notes

Code quality:

• ✅ Type-safe additions with proper TypeScript usage
• ✅ Consistent with project patterns per CLAUDE.md guidelines
• ✅ No security concerns (proper authentication flow)

---

Recommendation: Approve and merge. The global query reset is acceptable for local mode's connection-change scenario.

[github-actions]

E2E Test Results

✅ All tests passed • 60 passed • 4 skipped • 756s

Status	Count
✅ Passed	60
❌ Failed	0
⚠️ Flaky	0
⏭️ Skipped	4

Tests ran across 4 shards in parallel.

View full report →

storage event is being issues anyways

[wrn14897]

LGTM. I'd suggest doing a bit more testing with the preview before merging