-
Notifications
You must be signed in to change notification settings - Fork 208
[REVIEW] Fix a few memory leaks. #2710
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
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 look like good fixes to me. Thanks @legrosbuffle!
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.
Thanks @legrosbuffle !
/ok to test cbe040b |
@legrosbuffle could you run pre-commit to fix failing style checker? |
cbe040b
to
15411c7
Compare
Done, thanks. I force-pushed the fix, I'm not sure what the convention is in this repo ? |
@legrosbuffle force push is not a problem, we squash merge. Thank you! |
/ok to test 15411c7 |
@legrosbuffle it seems like your force pushed commit does not have the fixes for passing style checker? |
6c3802a
to
708771e
Compare
708771e
to
01a6cb2
Compare
Sorry, I think it should be good now. |
/ok to test 01a6cb2 |
/merge |
No description provided.