Bug: Flickering of First Hovered Label on Chart

[pwoltschk]

Title: Flickering of First Hovered Label on Chart

Description:

On the NuGet package page, the interactive chart has an issue. When moving the mouse along the curve, the first label hovered over begins to flicker (triggers hover animation), even while hovering on other data points.

Steps to Reproduce:

1. Visit the NuGet package page with the interactive chart.
2. Hover over a data point on the curve to display its label.
3. Move the mouse along the curve to other points.
4. Observe the first label flickering intermittently.

Expected Behavior:

• Only the label corresponding to the current mouse position should play the hover animation.
• Previous labels should not flicker.

[pwoltschk]

Seems the bug we are issuing here is a issue with chart js chartjs/Chart.js#6956

[bruno-garcia]

PR with a fix merged (thanks @pwoltschk )

But CI is failing with:

✔ Browser application bundle generation complete.
02 02 2025 01:56:21.671:INFO [karma-server]: Karma v6.4.4 server started at http://localhost:9876/
02 02 2025 01:56:21.673:INFO [launcher]: Launching browsers ChromeHeadless with concurrency unlimited
02 02 2025 01:56:21.678:INFO [launcher]: Starting browser ChromeHeadless
02 02 2025 01:56:21.990:ERROR [launcher]: Cannot start ChromeHeadless
	[0202/0[15](https://github.com/dotnet/nuget-trends/actions/runs/13094511160/job/36535180812#step:9:16)621.761313:FATAL:zygote_host_impl_linux.cc(126)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
02 02 2025 01:56:21.990:ERROR [launcher]: ChromeHeadless stdout: 
02 02 2025 01:56:21.990:ERROR [launcher]: ChromeHeadless stderr: [0202/015621.761313:FATAL:zygote_host_impl_linux.cc(126)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
02 02 2025 01:56:21.992:INFO [launcher]: Trying to start ChromeHeadless again (1/2).
02 02 2025 01:56:22.209:ERROR [launcher]: Cannot start ChromeHeadless
	[0202/015622.031577:FATAL:zygote_host_impl_linux.cc(126)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
02 02 2025 01:56:22.210:ERROR [launcher]: ChromeHeadless stdout: 
02 02 2025 01:56:22.210:ERROR [launcher]: ChromeHeadless stderr: [0202/015622.031577:FATAL:zygote_host_impl_linux.cc(126)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
02 02 2025 01:56:22.211:INFO [launcher]: Trying to start ChromeHeadless again (2/2).
02 02 2025 01:56:22.437:ERROR [launcher]: Cannot start ChromeHeadless
	[0202/015622.25[18](https://github.com/dotnet/nuget-trends/actions/runs/13094511160/job/36535180812#step:9:19)07:FATAL:zygote_host_impl_linux.cc(126)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
02 02 2025 01:56:22.437:ERROR [launcher]: ChromeHeadless stdout: 
02 02 2025 01:56:22.438:ERROR [launcher]: ChromeHeadless stderr: [0202/015622.251807:FATAL:zygote_host_impl_linux.cc(126)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
02 02 [20](https://github.com/dotnet/nuget-trends/actions/runs/13094511160/job/36535180812#step:9:21)25 01:56:22.438:ERROR [launcher]: ChromeHeadless failed 2 times (cannot start). Giving up.
✔ Browser application bundle generation complete.
✔ Browser application bundle generation complete.
Error: Process completed with exit code 1.

Not sure why, VM is set to ubuntu-latest

[bruno-garcia]

Seems to be exactly related to that:
puppeteer/puppeteer#12818 (comment)

[bruno-garcia]

OK this fixed it:

• fix ci due to gha issue #278

[bruno-garcia]

Verified the fix is live: https://nugettrends.com/packages?months=120&ids=Sentry