-
Notifications
You must be signed in to change notification settings - Fork 13
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: restartPolicy and limits #50
Conversation
- If restart_policy but restartPolicy does not, uses the former to populate the later - If limits is empty, uses requests so limits == requests
Reviewer's Guide by SourceryThis pull request addresses two issues in the taskmaster.py file: it adds logic to use 'restart_policy' to populate 'restartPolicy' if the latter is missing, and it sets resource limits equal to requests when limits are not specified. File-Level Changes
Tips
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @lvarin - I've reviewed your changes - here's some feedback:
Overall Comments:
- Consider adding brief comments to explain the purpose of each change. This would help future maintainers understand the rationale behind these modifications.
Here's what I looked at during the review
- 🟢 General issues: all looks good
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.
705548b
to
c17fe8b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Summary by Sourcery
Fix issues with task specification by ensuring 'restartPolicy' is set from 'restart_policy' when missing, and aligning 'limits' with 'requests' in container resources when 'limits' is not specified.
Bug Fixes: