Skip to content
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

Log: fix some parts of messages not being discarded early #10238

Open
wants to merge 1 commit into
base: support/2.14
Choose a base branch
from

Conversation

yhabteab
Copy link
Member

Backport of #10177

`m_IsNoOp` was introduced to avoid building up log messages that will later be
discarded, like debug messages if no debug logging is configured. However, it
looks like the template operator<< implemented in the header file was forgotten
when adding this feature, all other places writing into `m_Buffer` already have
an if guard like added by this commit.
@cla-bot cla-bot bot added the cla/signed label Nov 14, 2024
@icinga-probot icinga-probot bot added this to the 2.14.4 milestone Nov 14, 2024
if (!m_IsNoOp) {
m_Buffer << val;
}

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is fine. But I don't see how users suffer from this until v2.15. Especially, given that we've deferred actual bugs. (Which is ok as v2.14.4 is already large enough.)

Copy link
Member Author

@yhabteab yhabteab Nov 14, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But I don't see how users suffer from this until v2.15.

They suffer from unnecessary log buffering, but I'm fine with not backporting it.

Especially, given that we've deferred actual bugs. (Which is ok as v2.14.4 is already large enough.)

What do you mean by actual bugs? Isn't this also a bug? Your justification doesn't make sense. Just because you think we've already backported enough, you don't want to include any other fixes? There isn't a rule that defines the size of a bug fix release, so I don't understand why you keep bringing this argument.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean by actual bugs? Isn't this also a bug?

Users don't even notice this.

Just because you think we've already backported enough, you don't want to include any other fixes?

At least if users don't even notice this.

There isn't a rule that defines the size of a bug fix release,

Not a precise hard limit, but a rule of thumb, I hope.
I mean, so far we've opened backport PRs for 62(!) merged PRs.

@yhabteab yhabteab modified the milestone: 2.14.4 Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants