Add native support for toxicity detection guardrail microservice #1258
+211
−19
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
for more information, see https://pre-commit.ci
daniel-de-leon-user293
requested review from
lvliang-intel,
letonghan,
ftian1 and
chensuyue
as code owners
Signed-off-by: Daniel Deleon <[email protected]>
Signed-off-by: Daniel Deleon <[email protected]>
qgao007
reviewed
Feb 6, 2025
| toxicity_detection_port = int(os.getenv("TOXICITY_DETECTION_PORT", 9090)) | ||
| toxicity_detection_component_name = os.getenv("TOXICITY_DETECTION_COMPONENT_NAME", "OPEA_NATIVE_TOXICITY") | ||
|
|
||
| print(f"HELLO:-{toxicity_detection_component_name}-") |
There was a problem hiding this comment.
Don't use print in the code.
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.
Description
After the re-architecture, Intel/toxic-prompt-roberta was removed from the toxicity detection microservice. This PR brings back the free, token-less, lightweight model as the default option for users.
The new component name, used by default if no component name is passed, is
OPEA_NATIVE_TOXICITY. Users who have a Prediction Guard API key must now setTOXICITY_DETECTION_COMPONENT_NAMEtoPREDICTIONGUARD_TOXICITY_DETECTION.The reason for choosing to default to
Intel/toxic-promp-robertais that it reduces friction for new users. Acquiring a Prediction Guard API key adds an extra step for new users who may be trying to use OPEA under the assumption it is free and open-source.Issues
n/aType of change
List the type of change like below. Please delete options that are not relevant.
Dependencies
None
Tests
Ran README manually and toxicity detection test script
test_guardrails_bias_detection_toxicdetection.pySigned-off-by: Daniel Deleon [email protected]