[Bug] Heatmap tooltip stuck when data refreshes

[gtsirkalova]

Version

5.4.3

Link to Minimal Reproduction

https://codepen.io/Galya-Tsirkalova/pen/NWZywmW

Steps to Reproduce

1. I create the chart setting it's option chart?.setOption(currentOption);
2. Every 10 seconds I receive fresh data from an API
3. When I receive the data I format it in the way the chart expects it
4. Set the new option
5. Hover over the chart very swiftly and try to hover over the tooltip

Current Behavior

When the new data is on it's way and seems like at the moment the chart content is re-rendering if I manage to hover over the tooltip it gets stuck on the screen. I have to hover again on the chart in order it to disappear

NB. It's not possible the issue to be reproduced using the provided codepen because it happens when the data reloads (new data comes from the API)

Expected Behavior

The tooltip disappears when I hover out of the chart

Environment

- OS: Ubuntu 24.04 LTS
- Browser: Chromium Version 127.0.6533.26 (Official Build) snap (64-bit)
- Framework: React

Any additional comments?

No response

[gjenkins8]

Hi 👋 Can you give an example please

[Diliz]

Hello!

Got the same issue here with the latest helm:

version.BuildInfo{Version:"v3.15.2", GitCommit:"1a500d5625419a524fdae4b33de351cc4f58ec35", GitTreeState:"clean", GoVersion:"go1.22.4"}

I have two versions of the same chart in a helm registry:

• 0.5.2
• 0.5.2+mytaggedversion

In the Chart.yaml file, I have a dependency, its version to 0.5.2, or =0.5.2. I launch an helm dependy build.

What is happening:

The version of the subchart is now 0.5.2+mytaggedversion, in the Chart.lock file

What should happen:

The version of the subchart stays to 0.5.2, in the Chart.lock file

[HenriBlacksmith]

Hello,

I have the exact same problem as @Diliz, I am using SemVer2 versions for my Helm Charts that I publish to an Artifactory.

The version format is {major}.{minor}.{patch}+{build} where build is a short git commit SHA.

Then I am trying to generate a Chart.lock file from a Chart.yaml targeting a precise value of my chart like 0.9.4+352bd but I always get the latest version based on the publication date in Artifactory.

I would expect an option to allow helm dependency build to not upgrade to the latest build or a specific command like helm dependency lock to generate a lockfile exactly matching the Chart.yaml version constraint.

[HenriBlacksmith]

I opened a separate issue for my case but it looks like Helm actually does not properly handle equality constraints with either build info or pre-releases: https://github.com/helm/helm/issues/13245

[github-actions[bot]]

This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs.