Skip to content

Comments

OCPBUGS-74557: Fixed Metrics page React error #306 by exporting QueryBrowser component#16016

Merged
openshift-merge-bot[bot] merged 3 commits intoopenshift:mainfrom
krishagarwal278:OCPBUGS-74557
Feb 18, 2026
Merged

OCPBUGS-74557: Fixed Metrics page React error #306 by exporting QueryBrowser component#16016
openshift-merge-bot[bot] merged 3 commits intoopenshift:mainfrom
krishagarwal278:OCPBUGS-74557

Conversation

@krishagarwal278
Copy link
Contributor

@krishagarwal278 krishagarwal278 commented Feb 10, 2026

Screenshot 2026-02-10 at 1 56 57 PM After: Screenshot 2026-02-10 at 1 56 32 PM

Summary by CodeRabbit

  • New Features
    • Query browser component is now available in the public API for developers to use.

@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 10, 2026
@openshift-ci-robot
Copy link
Contributor

@krishagarwal278: This pull request references Jira Issue OCPBUGS-74557, which is invalid:

  • expected the bug to target the "4.22.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Screenshot 2026-02-10 at 1 56 57 PM After: Screenshot 2026-02-10 at 1 56 32 PM

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from Leo6Leo and sg00dwin February 10, 2026 19:00
@openshift-ci openshift-ci bot added the component/shared Related to console-shared label Feb 10, 2026
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 10, 2026

📝 Walkthrough

Walkthrough

This pull request expands the public API surface of the console-shared components package by re-exporting the query-browser module through the main components index file. The change adds a single export statement (export * from './query-browser') to frontend/packages/console-shared/src/components/index.ts, making query-browser components and utilities available to consumers of the package without requiring direct path imports.

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title references exporting QueryBrowser component to fix a React error, which directly aligns with the changeset that adds a public re-export of './query-browser' from the components index file.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

No actionable comments were generated in the recent review. 🎉

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.


Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Member

@logonoff logonoff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what components are importing from console shared root barrel that require this? can we rewrite the imports instead of writing an export?

@krishagarwal278
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 10, 2026
@openshift-ci-robot
Copy link
Contributor

@krishagarwal278: This pull request references Jira Issue OCPBUGS-74557, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @yapei

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested a review from yapei February 10, 2026 19:33
@krishagarwal278
Copy link
Contributor Author

/retest

1 similar comment
@krishagarwal278
Copy link
Contributor Author

/retest

@openshift-ci openshift-ci bot added component/core Related to console core functionality component/dev-console Related to dev-console labels Feb 16, 2026
@krishagarwal278
Copy link
Contributor Author

krishagarwal278 commented Feb 16, 2026

Hi @logonoff i now changed the imports in MonitoringDashboardGraph and resource-metrics to use console/dynamic-plugin-sdk/src/lib-core instead of direct path imports from console/shared avoiding the barrel export. Metrics page loading as expected 👍🏻

@krishagarwal278
Copy link
Contributor Author

/acknowledge-critical-fixes-only

Copy link
Member

@logonoff logonoff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Feb 16, 2026
@krishagarwal278
Copy link
Contributor Author

/retest

@logonoff
Copy link
Member

ERROR in HandleCyclesPlugin: 5 total cycles detected, 0 of which are min-length :-(

You'll need to fix some cycles

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 16, 2026
@krishagarwal278
Copy link
Contributor Author

/retest

Copy link
Member

@logonoff logonoff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If it works it works..

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 17, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 17, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: krishagarwal278, logonoff

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@krishagarwal278
Copy link
Contributor Author

/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Feb 17, 2026
@krishagarwal278
Copy link
Contributor Author

/verified later @yanpzhan

@openshift-ci-robot openshift-ci-robot added verified-later verified Signifies that the PR passed pre-merge verification criteria labels Feb 17, 2026
@openshift-ci-robot
Copy link
Contributor

@krishagarwal278: This PR has been marked to be verified later by @yanpzhan.

Details

In response to this:

/verified later @yanpzhan

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Copy link
Member

@logonoff logonoff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/hold

now that I think about it.. there's another file frontend/public/components/utils/resource-metrics.tsx which also imports from @console/shared/src/components/query-browser... do we need to update that?

Does updating the import directly to use

import { QueryBrowser } from '@console/shared/src/components/query-browser/QueryBrowser';

work..?

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 17, 2026
@krishagarwal278
Copy link
Contributor Author

i mean that import is working fine in resource-metrics.tsx
Screenshot 2026-02-17 at 2 30 44 PM
what i mean is, the metrics page here isn't crashing and rendering as expected

i updated my import from the original console/shared to avoid the cycles issue

@logonoff
Copy link
Member

okay that's fair.. I suppose we can try the other way in a follow up. not a big problem but I find it a little weird importing from dynamic-core-api.ts since it's meant as a re-export file for plugins

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 17, 2026
@krishagarwal278
Copy link
Contributor Author

/retest

1 similar comment
@krishagarwal278
Copy link
Contributor Author

/retest

@openshift-merge-bot openshift-merge-bot bot merged commit 55e73cc into openshift:main Feb 18, 2026
8 checks passed
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 18, 2026

@krishagarwal278: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-ci-robot
Copy link
Contributor

@krishagarwal278: Jira Issue OCPBUGS-74557: All pull requests linked via external trackers have merged:

This pull request has the verified-later tag and will need to be manually moved to VERIFIED after testing. Jira Issue OCPBUGS-74557 has been moved to the MODIFIED state.

Details

In response to this:

Screenshot 2026-02-10 at 1 56 57 PM After: Screenshot 2026-02-10 at 1 56 32 PM

Summary by CodeRabbit

  • New Features
  • Query browser component is now available in the public API for developers to use.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@jhadvig
Copy link
Member

jhadvig commented Feb 18, 2026

/cherry-pick release-4.21

@openshift-cherrypick-robot

@jhadvig: new pull request created: #16038

Details

In response to this:

/cherry-pick release-4.21

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@krishagarwal278
Copy link
Contributor Author

/cherrypick release-4.19

@krishagarwal278
Copy link
Contributor Author

/cherry-pick release-4.19

@openshift-cherrypick-robot

@krishagarwal278: #16016 failed to apply on top of branch "release-4.19":

Applying: OCPBUGS-74557: Fixed Metrics page React error #306 by exporting QueryBrowser component
Using index info to reconstruct a base tree...
M	frontend/packages/console-shared/src/components/index.ts
Falling back to patching base and 3-way merge...
Auto-merging frontend/packages/console-shared/src/components/index.ts
CONFLICT (content): Merge conflict in frontend/packages/console-shared/src/components/index.ts
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 OCPBUGS-74557: Fixed Metrics page React error #306 by exporting QueryBrowser component

Details

In response to this:

/cherrypick release-4.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot

@krishagarwal278: #16016 failed to apply on top of branch "release-4.19":

Applying: OCPBUGS-74557: Fixed Metrics page React error #306 by exporting QueryBrowser component
Using index info to reconstruct a base tree...
M	frontend/packages/console-shared/src/components/index.ts
Falling back to patching base and 3-way merge...
Auto-merging frontend/packages/console-shared/src/components/index.ts
CONFLICT (content): Merge conflict in frontend/packages/console-shared/src/components/index.ts
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 OCPBUGS-74557: Fixed Metrics page React error #306 by exporting QueryBrowser component

Details

In response to this:

/cherry-pick release-4.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@krishagarwal278
Copy link
Contributor Author

/cherry-pick release-4.20

@openshift-cherrypick-robot

@krishagarwal278: new pull request created: #16040

Details

In response to this:

/cherry-pick release-4.20

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. component/core Related to console core functionality component/dev-console Related to dev-console component/shared Related to console-shared jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. verified Signifies that the PR passed pre-merge verification criteria verified-later

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants