Optimize 'receive_json' for the happy path #1058
Merged
Conversation
This file contains 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
davfsa
force-pushed
the
task/optimize-receive_json-for-happy-path
branch
from
e39deac
to
5c7e237
Compare
davfsa
force-pushed
the
task/optimize-receive_json-for-happy-path
branch
2 times, most recently
from
178452a
to
103cd6a
Compare
|
LGMT though |
davfsa
force-pushed
the
task/optimize-receive_json-for-happy-path
branch
from
103cd6a
to
c5492b9
Compare
FasterSpeeding
previously approved these changes
Mar 6, 2022
davfsa
force-pushed
the
task/optimize-receive_json-for-happy-path
branch
from
c5492b9
to
b8e20ca
Compare
FasterSpeeding
approved these changes
Mar 6, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Checklist
noxand all the pipelines have passed.