Find answers from the community

Updated 4 months ago

Any upcoming Bedrock Converse package

Any upcoming Bedrock Converse package update including meta3.1 models ?
L
m
10 comments
Just needs to have a utils file updated with its context window and model name

I have no idea what either of these are for bedrock πŸ€·β€β™‚οΈ This package is mostly community maintained imo

I can probably find this info in bedrock docs sometime today, but I welcome a PR
Attachment
image.png
Actually not I thought the same way @Logan M but that gave constant error because there's a difference between the usage pattern of anthropic and Meta
what do you mean? Whats the error?
Give me a moment I'll replicate the error Right now I'm fighting bedrock's useless ValidationExceptions that gave 100% no traceback except this piece of json
{<EventPayload.EXCEPTION: 'exception'>: ValidationException('An error occurred (ValidationException) when calling the Converse operation: Expected toolResult blocks at messages.0.content for the following Ids: tooluse_8OCpeEUhSBmX6hVMBD50Eg')}
πŸ€” Hmm weird. I don't have access to bedrock to test this so I cant help much. But sounds like the list of messages being passed to bedrock isn't being converted into an expected format
Actually It's occasional the issue comes when either error is not consistent or output is not consistent I passed 5 tools and it was able to use all tools including some retriever tools but somehow the issue evades from everywhere like there the exact message that generates error while returning was able to store correct response without error in the chat store
@Logan M for Say the error originated while generating this message while In the chatstore the responese is correct and its complete as well by role "assistant"
Attachment
image.png
@Logan M I've not gone in depth of llama core package So I'll ask you does this tool response looks consistant for a retriever tool till uuid which is actually ulid you have the metadata of vector store
Attachment
image.png
And TBH the biggest laugh stock is AWS cloudwatch its also returning the same error while we have a proper correct answere from same request in Chat Store IDK what's going on with it
Attachment
image.png
BTW I Replicated the original MGS issue with Meta LLAMA3.1 @Logan M
Add a reply
Sign up and join the conversation on Discord