Skip to content

Conversation

@asm582
Copy link
Member

@asm582 asm582 commented Oct 17, 2022

remove panic calls

@asm582 asm582 requested a review from dmatch01 October 17, 2022 19:07
Copy link
Collaborator

@dmatch01 dmatch01 left a comment

Choose a reason for hiding this comment

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

We need a way to debug this problem in the since this is a workaround. 1 of the 2 options below is suggest. I would recommended option 1 because there it is efficient in logging only when there is a problem.

  1. Change functions that had panic to also return an error as a second parameter and have the caller provide logging information about the issue.
  2. Every entity that calls these previously panic functions will need to log info. before calling. So for instance that line number you found in the bug. Those lines of code will need to generate log entries to generate details to debug the problem.
@asm582
Copy link
Member Author

asm582 commented Nov 4, 2022

Thanks @dmatch01 , LGTM!

Copy link
Collaborator

@dmatch01 dmatch01 left a comment

Choose a reason for hiding this comment

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

Thanks for doing the test case. I have a Q about this test case. I'm not quite how it confirms there is not panic. In otherwards: If I take this test case and add it to the previous version of code will it pass/fail? If you can check this that would be great. Otherwise if it still passes on the older code can you add a issue in mcad to fix this test case? That way I can go ahead and approve with merge. Thank you!

@dmatch01 dmatch01 merged commit 3815ca6 into project-codeflare:quota-management Nov 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants