Add comments to needReseThis PR is to add comments to needResetReservedPorts in fluid/pkg/ddc/base/portallocator/bitmap_allocator.go.tReservedPorts in fluid/pkg/ddc/base/portallo…

[withanorchid22]

I. Describe what this PR does

This PR adds function-level comments to needResetReservedPorts in fluid/pkg/ddc/base/portallocator/bitmap_allocator.go. The comments describe that the function checks whether the bitmap allocator needs to reset its reserved port state before allocating ports.

II. Does this pull request fix one issue?

fixes #6095

III. Special notes for reviews

None.

[gemini-code-assist]

Code Review

This pull request adds a descriptive comment to the needResetReservedPorts method in bitmap_allocator.go to explain its purpose. There are no review comments, and I have no additional feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[cheyang]

@withanorchid22 — this PR is blocked from merging by a failing DCO check.
The DCO bot requires every commit to carry a Signed-off-by: trailer; without it the PR cannot land regardless of lgtm / approved labels or otherwise-green CI.

Please resolve this now. For a single-commit PR:

git commit --amend -s
git push --force-with-lease

For multiple commits on this branch:

git rebase --signoff origin/master
git push --force-with-lease

The code review side is finished and any merge labels already on the PR will take effect once DCO turns green. Reference: https://github.com/apps/dco

[cheyang]

/copilot review

[cheyang]

Small nit: the blank line between the BitMapAllocator struct's closing } and the new godoc block was removed, so the comment now runs straight into the type declaration. Could you keep a blank line here so the doc comment stays visually attached to needResetReservedPorts rather than to the struct? The wording of the comment itself is fine.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 64.76%. Comparing base (a826600) to head (43f628f).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #6096   +/-   ##
=======================================
  Coverage   64.76%   64.76%           
=======================================
  Files         484      484           
  Lines       33885    33885           
=======================================
  Hits        21947    21947           
  Misses      10215    10215           
  Partials     1723     1723           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[fluid-e2e-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign yangyuliufeng for approval by writing /assign @yangyuliufeng in a comment. 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:

• OWNERS

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

[fluid-e2e-bot]

Hi @withanorchid22. Thanks for your PR.

I'm waiting for a fluid-cloudnative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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/test-infra repository.