Check that messages are well-formed before enqueueing #235
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
Memory usage on my machine was significantly higher for whatever reason, hovering around 200 MB (heap, not live data, that was _waaay_ less). So set the limit at double that.
edsko
force-pushed
the
edsko/serialize-outputs
branch
from
e34ee99
to
3f58f07
Compare
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.
We force messages to NF before enqueueing them. This ensures that if those messages contain any pure exceptions (due to a bug in a client or a server), we detect the problem when the message is enqueued, and can throw an appropriate exception.