-
Notifications
You must be signed in to change notification settings - Fork 810
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
Comment unsafe memory usage in ingester push path #2004
Conversation
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.
These are great and useful comments for future reviewers!
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.
Very well explained. Thanks!
May you rebase, given I've merged #2000 please?
See #2006 |
0e897dc
to
d52556a
Compare
Signed-off-by: Bryan Boreham <bryan@weave.works>
…data Signed-off-by: Bryan Boreham <bryan@weave.works>
d52556a
to
e31ea09
Compare
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.
LGTM. @bboreham do you feel comfortable to merge it or plan further improvements?
This is roughly what I was suggesting at #2000 to warn future maintainers.
I have left (what I assume is) the bug unchanged.I have changed the way errors are wrapped to make it clearer how we avoid retaining references to unsafe data inside errors.