Skip to content
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

🥅 Handle unexpected detector responses #102

Merged
merged 1 commit into from
Jun 25, 2024

Conversation

evaline-ju
Copy link
Collaborator

Related to #96 - if a detector is not returning the expected number of responses [one per chunk] we want to surface an error rather than provide incorrect results

Error log example - 2024-06-25T20:17:15.224226Z ERROR fms_guardrails_orchestr8::orchestrator: unary task failed request_id=5718f002-1621-4667-9e6f-53b28e048e5b error=Detector xyz did not return expected number of responses

User sees {"code":500,"details":"unexpected error occured while processing request"} [since this is not a user-fixable error]

Closes: #100

Signed-off-by: Evaline Ju <69598118+evaline-ju@users.noreply.github.com>
Copy link
Collaborator

@gkumbhat gkumbhat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

@evaline-ju evaline-ju merged commit a071cb6 into foundation-model-stack:main Jun 25, 2024
1 check passed
@evaline-ju evaline-ju deleted the detector-check branch June 25, 2024 21:13
pmcjr pushed a commit to pmcjr/fms-guardrails-orchestrator that referenced this pull request Jul 1, 2024
Signed-off-by: Evaline Ju <69598118+evaline-ju@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants