Adrian D.

Results 172 comments of Adrian D.

Hello @ory-name-tbd, thanks for reaching out. I have replicated the issue and got the same behavior where `outputTokens` does not follow the `maxTokens`. Since this is a Bedrock issue, I...

Hello thanks for the patience and an update has been given from the team. The Bedrock team has mentioned that Sonnet 3.5v1 has a max output token limit of 4096.

Hello @s-isobe, thanks for reaching out. I have replicated the issue and got the same error. I will discuss to the team for the change provided and I will let...

Hello @s-isobe, thanks for the patience. I have reached out to the RDSDataService in relation to their service model that the response returns a null as Boto is not expecting...

Hello @anoncam, thanks for reaching out. Is this supplychain related or would be related to the current [AWS supplychain](https://docs.aws.amazon.com/cli/latest/reference/supplychain/)? It looks like the API `supplychain` already exists.

Thanks for bringing this up. This FR will remain open for tracking and for other users. Also, as per our [contribution process](https://aws.github.io/aws-cli/contribution_process.html), the PR will be closed as it does...

Hello @hxddh, thanks for bringing up the issue. It looks like you are using a 3rd Party provider called Baidu. Please ensure that the 3rd party is using most up...

Hi @hxddh, thanks for reaching out. The error has gave a mismatch from what was received from the 3rd party `Expected checksum iXcQTg== did not match calculated checksum: AoSIYQ==`. Since...

Hello, re-looking at the issue, >1. The -i and -b options do not check if the directory name has been supplied. The shift command fails, but the script continues. -...

Hello @jusdino, thank you for reaching out. I have tried having [query client](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/dynamodb/client/query.html)and [query resource](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/dynamodb/table/query.html) and found that indeed we cannot use the same parameter from client to resource. Looking...