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
Middleware for metrics #576
Middleware for metrics #576
Changes from 7 commits
6ffc4d2
5ddf9f8
2e76638
e580f44
a700902
53b1ac2
c8eac37
cc7b3f5
040d384
189fe0b
20e2ee2
17ab865
53bf4d1
27d700d
012a6d8
9d2be21
f481464
3c4aff4
ef1c90d
d8b7e07
e6d47b5
2b5da63
245b011
4d1313f
9544dd1
9fefc84
10e586a
4204cb6
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.
you can remove these feature guards, the
utils
by itself have conditional compilation that should be sufficient but I think you have to changeutils
to be a non-optional dependency for that to work.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.
nice 👍
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 assume that the max size error is an error based on user input being too large?
I wonder whether the
tracing::error!("Error serializing response: {:?}", err);
line should instead be above this InternalError bit, so we only get output for the unexpected errors?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.
It means that
output
from an executed call exceeded the max limit but the "request" itself was below the limit.Thus, it depends what you mean with the user but the
registered callback
created a response bigger than the max limit.Yes, or downgrade the error above to warn or something but the
InternalError
"should" be infallible/bug IIRC.