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.
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
Update graphql.net to 4.6.1 #10782
Update graphql.net to 4.6.1 #10782
Changes from 13 commits
1bb2098
db0571f
908a97f
d1316e4
dc4f3fc
cb9af75
6d77452
83fe01a
582a233
6434fd6
15c07da
d8deeff
f7d210a
9c3429e
6dbbe25
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you mean that somewhere in our grapqhl code with have a call to a
Serialize
method (NewtonSoft?) that is not async and this is triggered inIDocumentWriter.WriteaAsync
.If buffering is required, maybe use a smaller reused buffer instead of a single one as big as the payload, and pool it too? Another option might be to use
BufferedStream
betweendocumentWriter
andcontext.Response.Body
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might use BufferedStream so not all the payload is serialized in memory.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok you can remove the comment .. these newtsonsoft refs make me cry tho .. we gotta sortt it out been system.text.json compliant at some point :P (its fine cos there is other stuff like this already)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was about to say the same thing before seeing the comment. We shouldn't tie it to NewtonSoft. If the field is
MultiTextField
then cast to that, or map to it, and access its own properties.