Closed marcalff closed 1 month ago
Based on PR contribution #2662 from @yurishkuro
Nit: I personally don't care but when you have new contributors (e.g. someone just starting in oss) I always try to preserve their own commits, e.g. by branching off of their branch, so that they get proper credit as contributors. E.g. GitHub shows all authors:
Based on PR contribution #2662 from @yurishkuro
Nit: I personally don't care but when you have new contributors (e.g. someone just starting in oss) I always try to preserve their own commits, e.g. by branching off of their branch, so that they get proper credit as contributors.
Good point, I need to improve my github skills to do that.
Now that 2662 is closed, the branch is deleted so I can't reopen it to use it.
@yurishkuro Feel like submitting a 1 line change using the web interface, to get the git credits fixed ?
Do not merge label, waiting for additional commit.
Ready for review.
Feel like submitting a 1 line change using the web interface, to get the git credits fixed ?
no it's fine, like I said, I don't care, it was more of a general comment on a nicer way of accepting contributions.
Feel like submitting a 1 line change using the web interface, to get the git credits fixed ?
no it's fine, like I said, I don't care, it was more of a general comment on a nicer way of accepting contributions.
Thanks. Point taken.
To add to change set upon merge:
Co-authored-by: Yuri Shkuro <yurishkuro@users.noreply.github.com>
Attention: Patch coverage is 64.28571%
with 5 lines
in your changes are missing coverage. Please review.
Project coverage is 87.59%. Comparing base (
497eaf4
) to head (75ec527
). Report is 63 commits behind head on main.
I see a perf concern here if the SDK is not configured.
I'll take perf concern over segfault. Right now the noop implementation is simply not usable.
I'll take perf concern over segfault. Right now the noop implementation is simply not usable.
Yes segfault was indeed a bug to be fixed. The fix is unfortunately adding a perf overhead for instrumented libraries when the logging is not enabled, which is not good. Not an issue with this PR, more of the constraint added by the design. I will create a tracking issue for this to be handled separately.
Fixes #2656
Based on PR contribution #2662 from @yurishkuro
Changes
Please provide a brief description of the changes here.
NoopLogger was incorrectly returning nullptr, causing segfaults in client code. After this change it returns a dummy no-op log record.
For significant contributions please make sure you have completed the following items:
CHANGELOG.md
updated for non-trivial changes