Skip to content

fix: do not add readOnly fields to the requestBody #421

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

Merged
merged 1 commit into from
Jun 4, 2024

Conversation

cloudnautique
Copy link
Contributor

According to the spec readOnly fields SHOULD NOT be sent in the request, but maybe present in the response. The LLM has made several errors making calls when these fields are present by including the readOnly fields in the request and getting HTTP 422's.

This change loops through the args, and drops readOnly fields from the requestBodyContent arg on the tool.

According to the spec readOnly fields SHOULD NOT be sent in
the request, but maybe present in the response. The LLM has made
several errors making calls when these fields are present by including
the readOnly fields in the request and getting HTTP 422's.

This change loops through the args, and drops readOnly fields from the
requestBodyContent arg on the tool.

Signed-off-by: Bill Maxwell <[email protected]>
@cloudnautique cloudnautique requested a review from g-linville June 3, 2024 23:39
@ibuildthecloud ibuildthecloud self-requested a review June 4, 2024 00:30
@cloudnautique cloudnautique merged commit 58afa9f into gptscript-ai:main Jun 4, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants