-
Notifications
You must be signed in to change notification settings - Fork 231
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
[Improvement] Update SubnetValLoop
#465
base: main
Are you sure you want to change the base?
Conversation
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.
Merge the latest dev-1.x to solve the conflict.
Fix lint. |
88bbb69
to
266de9f
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## dev-1.x #465 +/- ##
===========================================
+ Coverage 79.32% 79.49% +0.17%
===========================================
Files 280 280
Lines 14096 14094 -2
Branches 2155 2156 +1
===========================================
+ Hits 11181 11204 +23
+ Misses 2452 2422 -30
- Partials 463 468 +5
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
77a59a9
to
f4cdfe5
Compare
The failed test seems not related to this PR? |
SubnetValLoop
1.Fix set_max_subnet or set_min_subnet not found exception 2 Add the fleibility to define custom subnet kinds 3.Support to specifiy None with ResorceEstimator Signed-off-by: Ming-Hsuan-Tu <[email protected]>
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
set_max_subnet
orset_min_subnet
was not found in dev-1.x, so we need to have a fix for that.and also we need to have the feature to define what kind of subnet we want to evaluate.
In addition, we can specify None to resource estimator since its typing is Optional.
Modification
BC-breaking (Optional)
Does the modification introduce changes that break the backward compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here and update the documentation.
Checklist
Before PR:
After PR: