fix: properly parse the OFCOM list file#1438
Merged
leondz merged 7 commits intoNVIDIA:mainfrom Oct 27, 2025
Merged
Conversation
Contributor
|
DCO Assistant Lite bot All contributors have signed the DCO ✍️ ✅ |
Contributor
Author
|
I have read the DCO Document and I hereby sign the DCO |
Contributor
Author
|
recheck |
leondz
approved these changes
Oct 27, 2025
Collaborator
leondz
left a comment
leondz
left a comment
There was a problem hiding this comment.
thanks. looks generally good, minor change request
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
This PR fixes #1431 so that the
ofcom-potentially-offensive.txtfile is read correctly and is not empty.Verification
python -m pytest tests\detectors\test_detectors_unsafe_content.py::test_data_files_loaded_properly