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

DM-25253: Warn when weights are ignored in statisticsStack #537

Merged
merged 1 commit into from Aug 24, 2020

Conversation

MorganSchmitz
Copy link
Contributor

Jenkins run #32492.

Jira ticket.

Paircoded with @arunkannawadi!

LOGLS_WARN(_log,
"Weights passed on to statisticsStack are ignored as sctrl.getWeighted() is False."
"Set sctrl.setWeighted(True) for them to be used.");
}
Copy link
Member

@TallJimbo TallJimbo Aug 20, 2020

Choose a reason for hiding this comment

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

You can just use LOG_WARN here. The LOGL_ and LOGLS_ variants are just different ways of doing string formatting on the message, but you're not doing any here.

Copy link
Member

Choose a reason for hiding this comment

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

The use of LOG_WARN appears pretty minimal, with no occurrence except in its own unit test. Furthermore, I'm not sure if we want this to go into a default logger if there is one since it appears multiple times. So, we use LOGL_WARN and log it into the appropriate log file instead.

Copy link
Member

Choose a reason for hiding this comment

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

Sorry, I should have suggested LOGL_WARN, not LOG_WARN; I hadn't realized that the "L" suffix controlled whether a log object was accepted and only the "S" suffix controlled the string formatting. But what you've merged is fine.

@MorganSchmitz MorganSchmitz force-pushed the tickets/DM-25253 branch 2 times, most recently from 8a7c2ba to e9c3997 Compare August 24, 2020 19:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants