-
Notifications
You must be signed in to change notification settings - Fork 34
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
Update Zone09 #1211
Update Zone09 #1211
Conversation
@matsduf I noticed "rcode" value was passed to the message tag but not used, this is due to an oversight in the specification, but I took the liberty of adding it nonetheless since it is still given in the list of arguments. See https://github.com/zonemaster/zonemaster/blob/v2022.2.2/docs/specifications/tests/Zone-TP/zone09.md?plain=1#L115 EDIT: nevermind, there is already a PR to update the specification. zonemaster/zonemaster#1128 |
ns_ip_list => join( q{;}, sort $unexpected_rcode_mx{$rcode} ) | ||
ns_ip_list => join( q{;}, sort @{ $unexpected_rcode_mx{$rcode} } ) |
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.
Our current unit tests do not catch this type of errors. I do not say that we should add such tests to the unit tests, but we should be aware of it.
Purpose
This PR proposes a fix to a bug in Zone09. It also adds a missing return value in a message tag.
Context
Fixes #1210
Relates to zonemaster/zonemaster#1128
Changes
Z09_UNEXPECTED_RCODE_MX
How to test this PR