-
Notifications
You must be signed in to change notification settings - Fork 260
fix: [NPM] add check for invalid /0 cidr #1739
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
Conversation
huntergregory
left a comment
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.
added a comment about the UT. Could you also add a short description of the current issue and how your PR fixes it?
| ipblock: "2345:0425:2CA1:0000:0000:0567:5673:23b5 nomatch", | ||
| want: false, | ||
| }, | ||
| { |
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.
not sure if there's a test for valid /0 yet
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.
updated
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
Merge queue setting changed
* add check for invalid /0 cidr * added UT for valid cidr --------- Co-authored-by: Hunter Gregory <42728408+huntergregory@users.noreply.github.com>
Reason for Change:
This fixes an issue where we were not throwing an error for CIDRs whose IPs were not 0.0.0.0 and ended with /0 during translation. Any CIDR with [ip]/0 is invalid unless IP is 0.0.0.0.
Issue Fixed:
Requirements:
Notes:
Add check for invalid /0 CIDRs