-
Notifications
You must be signed in to change notification settings - Fork 435
Improve error message when length exceeds receive limit #1247
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -92,6 +92,19 @@ public enum GRPCError { | |
| } | ||
| } | ||
|
|
||
| /// The length of the received payload was longer than is permitted. | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If we want to be really nice to the user, we could point them to the config struct that they need to tune. |
||
| public struct PayloadLengthLimitExceeded: GRPCErrorProtocol { | ||
| public let description: String | ||
|
|
||
| public init(actualLength length: Int, limit: Int) { | ||
| self.description = "Payload length exceeds limit (\(length) > \(limit))" | ||
| } | ||
|
|
||
| public func makeGRPCStatus() -> GRPCStatus { | ||
| return GRPCStatus(code: .resourceExhausted, message: self.description) | ||
| } | ||
| } | ||
|
|
||
| /// It was not possible to compress or decompress a message with zlib. | ||
| public struct ZlibCompressionFailure: GRPCErrorProtocol { | ||
| var code: Int32 | ||
|
|
||
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
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
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
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.
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.
When we create the error in
LengthPrefixedMessageReader.swiftwe already capture the context. Is it right, that we capture the context here again, even though we pass the original error onwards?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.
The context just holds the error (and location info). Here we just have the wrapped error and no context. It's intentional that we capture it again, although the reason we have to do this is a bit gross: the error we're switching over is
Equatablebut the error wrapper providing context is notEquatable(because not all wrapped errors areEquatable). The server doesn't wrap/unwrap the error like this so we still need to capture the context inLengthPrefixedMessageReader.swift.