Add check for max payload size when publishing messages #1211
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.
This adds check if the messages Client is publishing to a server it is connected too does not exceed
max_payload
.This unfortunately asks for changing the error from a simple struct that maps error from
mpsc
error to a new one.Tests of how disruptive the error change is is under progress, hence the Draft.
We are using new
Atomic
instead of relying on the server info watcher for performance reasons.Signed-off-by: Tomasz Pietrek tomasz@nats.io