Fixed Sometimes Failing PyPI potentially_compromised_email_domain #268
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zmallen
approved these changes
Jul 20, 2023
|
|
||
| @pytest.mark.parametrize("package_info, detector", | ||
| [(empty_author_pypi, pypi_detector), (empty_author_npm, npm_detector)]) | ||
| def test_email_domain_none(self, package_info, detector): |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In response to this issue, fixed the sometimes failing PyPI rule
potentially_compromised_email_domain.The rule sometimes fails because the email address stored in
package_infocan beNoneand there is no check that the email_address isNonebefore doing any parsing. Added a simpleNonecheck before returning email addresses for npm and python. Added a test for a None or null emailhttps://datadoghq.atlassian.net/browse/SINT-1432