Skip to content
This repository has been archived by the owner on Nov 5, 2024. It is now read-only.

Bedrock InvokeModel lacking documentation and clarity around StopSequences parameter #692

Closed
RyanFitzSimmonsAK opened this issue Feb 2, 2024 · 5 comments
Assignees
Labels
bedrock documentation Improvements or additions to documentation service-api This issue pertains to the AWS API service-docs Issue relates to missing information in service documentation

Comments

@RyanFitzSimmonsAK
Copy link

Original issue : boto/boto3#3993

Ticket # for internal reference : P116361553

@RyanFitzSimmonsAK RyanFitzSimmonsAK self-assigned this Feb 2, 2024
@RyanFitzSimmonsAK RyanFitzSimmonsAK added service-api This issue pertains to the AWS API service-docs Issue relates to missing information in service documentation labels Feb 2, 2024
@RyanFitzSimmonsAK
Copy link
Author

RyanFitzSimmonsAK commented Feb 5, 2024

The service team added some documentation to the User Guide that clarifies some ambiguity.

Stop sequences (stopSequences) – Specify a character sequence to indicate where the model should stop. Currently, you can only specify one of the following options:

|

User:

I will provide another update when I get more information about the overly restrictive regex.

@tim-finnigan tim-finnigan added documentation Improvements or additions to documentation bedrock labels Apr 16, 2024
@adinathtw
Copy link

Are there any further updates / work around on this issue?

@RyanFitzSimmonsAK
Copy link
Author

The Bedrock documentation around stopSequences was updated again. If there are still issues surrounding this, please feel free to open a new issue.

Copy link

This issue is now closed.

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

@manwithaplandy
Copy link

The real issue here was never that the documentation was wrong, it was that the user is unable to specify any stop sequences because the regex check was too restrictive. Was that issue resolved?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bedrock documentation Improvements or additions to documentation service-api This issue pertains to the AWS API service-docs Issue relates to missing information in service documentation
Projects
None yet
Development

No branches or pull requests

4 participants