Defensive coding for negative indices in tool calls #469
+16
−3
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.
Hello,
I was integrating the AWS Bedrock openAI-compatible API and encountered a slight difference in behaviour.
Chunks being streaming back from AWS Bedrock have their index set to
-1
, whilst on openAI they come back as0
until the JSON is ready to be returned.This causes an out of bound exception on the modified line.
There are other differences in the chunks, but they don't cause a crash and I seem to be able to consume them fine.
AWS Bedrock chunk response:
OpenAI chunk response