fix(scheduler): display maxFloat/maxInt in Resource.String() for infinite values

[r0hansaxena]

What type of PR is this?

kind/bug

What this PR does / why we need it:

Verbose scheduler logs were printing raw sentinel values like math.MaxFloat64
and math.MaxInt64 for unbounded resources, making the output near unreadable.
The String() method on Resource now shows "maxFloat" and "maxInt" in those
cases instead.

Which issue(s) this PR fixes:

Fixes #5148

Special notes for your reviewer:

Only the String() method is affected, no logic changes anywhere.

Does this PR introduce a user-facing change?

[gemini-code-assist]

Code Review

This pull request updates the String() method in pkg/scheduler/api/resource_info.go to handle sentinel values for CPU, memory, and scalar resources by returning 'maxFloat' or 'maxInt' strings. Feedback suggests improving efficiency by using strings.Builder instead of repeated fmt.Sprintf calls, and recommends a unified helper function to ensure consistent handling of both sentinel values across all resource types.

[Copilot]

Pull request overview

This PR improves scheduler log readability by updating (*Resource).String() to render “infinite/unbounded” sentinel values (math.MaxFloat64 / math.MaxInt64) as the short tokens maxFloat and maxInt instead of printing extremely large raw numbers.

Changes:

• Updated Resource.String() to print maxFloat for CPU/memory when they are math.MaxFloat64.
• Updated Resource.String() to print maxInt for scalar resources when they are math.MaxInt64.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[r0hansaxena]

@hajnalmt please have a look

[hajnalmt]

/lgtm

Thanks for the contribution!

[hajnalmt]

I just realized how bad this conversion is here, these are maxInt float64 values for scalar resources, and we save maxInt64 in them. We need to write a new resource API on the long run definitely

[volcano-sh-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details

Needs approval from an approver in each of these files:

• pkg/scheduler/OWNERS

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

[hajnalmt]

/area scheduling
/label tide/merge-method-squash