Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: dashboard crash on CPU data #10004

Merged
merged 1 commit into from
Dec 20, 2024
Merged

Conversation

smira
Copy link
Member

@smira smira commented Dec 20, 2024

This was introduced in 1.9 cycle.

Fixes #9998

This was introduced in 1.9 cycle.

Fixes siderolabs#9998

Signed-off-by: Andrey Smirnov <[email protected]>
@smira smira force-pushed the fix/dashboard-crash branch from ea6eedf to fb36753 Compare December 20, 2024 10:10
@smira
Copy link
Member Author

smira commented Dec 20, 2024

/m

@talos-bot talos-bot merged commit fb36753 into siderolabs:main Dec 20, 2024
51 checks passed
@rothgar
Copy link
Member

rothgar commented Dec 20, 2024

I'm just curious, why does the numCPUs crash this? That seems so random.

@smira
Copy link
Member Author

smira commented Dec 21, 2024

It was a bug introduced in a PR updating reporting for non-uniform CPUs. When there are no CPUs in the response, we should not try to build any string

@smira smira mentioned this pull request Dec 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backported
Development

Successfully merging this pull request may close these issues.

Dashboard crash in 1.9.0
5 participants