-
Notifications
You must be signed in to change notification settings - Fork 26
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
Multiple objects returned in results for same message_index in chat completions - detection orchestrator API #302
Comments
As discussed with #288 incoming, the bug will likely apply to output detections [affecting |
After testing output detection locally with both the latest version pre-merge of the input detection message_index results fix, and the fixed version now merged, it doesn't seem that output detection had a bug with respect to multiple results under the same
As is seen, the results are accumulated as would be expected, which wasn't the case with input results on message_index. Therefore, I changed the title of this issue to reflect only the message_index for input detection results as being an issue |
The fix for this issue was merged into main. If there is another bug for output detection, it will be opened in a separate issue. |
Describe the bug
There appears to be a bug found within the returned
json_response["detections"]
section when making a call to the chat completions - detections orchestrator API. For instance, when there are multiple inputresults
from themessage_index
, where there are two separate objects created, versus one instance under the samemessage_index
with both results present.To Reproduce
Make a call to the chat completions - detection API with the following payload:
Expected behavior
for the detections section, the results should be sorted as the following:
The text was updated successfully, but these errors were encountered: