Fix Tooltip Rendering Issue by Upgrading react-charts

[TimothyAsirJeyasing]

This PR addresses the tooltip rendering issues
encountered in [email protected].
The issue has been resolved in [email protected].

https://bugzilla.redhat.com/show_bug.cgi?id=2281587

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: TimothyAsirJeyasing
Once this PR has been reviewed and has the lgtm label, please assign sanjalkatiyar for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[TimothyAsirJeyasing]

[GowthamShanmugam]

/retest

[GowthamShanmugam]

Please check the build failure

[TimothyAsirJeyasing]

/rebuild

[SanjalKatiyar]

update shared dependencies as well...

[SanjalKatiyar]

update shared dependencies as well...

this is still missing...

[SanjalKatiyar]

why do we need changes in analyse file ??

[TimothyAsirJeyasing]

/test odf-console-e2e-aws

[TimothyAsirJeyasing]

why do we need changes in analyse file

We updated the analyzeTest.ts file to fix two key issues: First, after upgrading react-charts, the script needed adjustments to accurately analyze the new build artifacts and avoid misinterpretations during the build process. Second, it was encountering a memory limit error ("Cannot create a string longer than 0x1fffffe8 characters") when processing large files, which we've optimized.

[SanjalKatiyar]

We updated the analyzeTest.ts file to fix two key issues: First, after upgrading react-charts, the script needed adjustments to accurately analyze the new build artifacts and avoid misinterpretations during the build process. Second, it was encountering a memory limit error ("Cannot create a string longer than 0x1fffffe8 characters") when processing large files, which we've optimized.

You have not "optimized" anything, rather just increases the base size to make sure there are no errors while running the script. I don't think all the changes in the analyse file is necessary, plz check again.
#1520 should do the required optimisation.

[TimothyAsirJeyasing]

/retest

[SanjalKatiyar]

fix ur commits in this PR... also check why tests are failing...

[TimothyAsirJeyasing]

/test odf-console-e2e-aws

[GowthamShanmugam]

/test odf-console-e2e-aws

[TimothyAsirJeyasing]

/retest

[alfonsomthd]

/retest

[openshift-ci]

@TimothyAsirJeyasing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/odf-console-e2e-aws	fdfd3fb	link	true	/test odf-console-e2e-aws

Full PR test history. Your PR dashboard.

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.

[alfonsomthd]

@TimothyAsirJeyasing After some investigation about the E2E errors I found that the chart was crashing (at least when you create a storage system and there is no total/available/used capacity yet).
The cause was the tooltip that depends on victory-tooltip dep.
Adding this under the resolutions section of package.json solved the issue in my environment:
"@patternfly/react-charts/victory-tooltip": "^37.1.1"
Probably you'll need to also add this in the shared library.
Please test that all charts affected by this PR work as expected.
@SanjalKatiyar FYI.

[SanjalKatiyar]

If version upgrade is causing multiple issues, can't we try to fix tooltip based on some CSS property ?? (like z-index or something similar)
Let's drop the version upgrade for now, there is no other need to upgrade.