fix(testitall): Update context too large endpoints#318
Open
Conversation
- replace the payload string to randomly generated string to avoid compression - renamed the endpoint to /response-too-large - updated testitall.actions.json and testitall.openapi.json to reflect the changes
jnxyp
force-pushed
the
testitall-almost-too-large-update
branch
from
9e82a19 to
c5ee533
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
/context-too-largeendpoint to/response-too-large, as it is acutally used to test the response size limit of the extension callout