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

ResourceSummary add check index for -1 #3950

Merged
merged 1 commit into from
Aug 18, 2023

Conversation

liangyuanpeng
Copy link
Contributor

@liangyuanpeng liangyuanpeng commented Aug 17, 2023

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Check for invaild index to avoid the panic.

Related:

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

@karmada-bot karmada-bot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Aug 17, 2023
Signed-off-by: Lan Liang <gcslyp@gmail.com>
@RainbowMango
Copy link
Member

I guess @halfrost is still trying to figure out the root cause at #3854.
Let's wait for a while.

@liangyuanpeng
Copy link
Contributor Author

I guess @halfrost is still trying to figure out the root cause at #3854.

Absolutely, So this PR would not to close the issue. just add the defensive code to avoid the panic.

@RainbowMango RainbowMango added this to the v1.7 milestone Aug 17, 2023
@halfrost
Copy link
Contributor

halfrost commented Aug 18, 2023

I guess @halfrost is still trying to figure out the root cause at #3854. Let's wait for a while.

Yes, indeed, I tested my code in the testing environment myself. I haven't been able to reproduce the #3854 issue mentioned. I'm also waiting for them to provide more detailed logs. Because the right interval of the last interval is positive infinity, it's certain that corresponding modeling can be found. Returning -1 is a requirement of goformat tool: each branch needs to return a value.

I agree with this PR, adding this defensive code will enhance the stability of Karmada. As for issue #3854 , once that guys provides more detailed logs to replicate the panic, I can promptly fix it.

Copy link
Member

@RainbowMango RainbowMango left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@karmada-bot karmada-bot added the lgtm Indicates that a PR is ready to be merged. label Aug 18, 2023
@karmada-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RainbowMango

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

@karmada-bot karmada-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 18, 2023
@karmada-bot karmada-bot merged commit f7a10b9 into karmada-io:master Aug 18, 2023
12 checks passed
@liangyuanpeng liangyuanpeng deleted the rs_check branch August 18, 2023 02:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants