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

Allow log-level parameter to affect log from reading config #1789

Merged
merged 5 commits into from
Oct 31, 2023

Conversation

szokeasaurusrex
Copy link
Member

Fixes #1787

@szokeasaurusrex szokeasaurusrex enabled auto-merge (squash) October 30, 2023 15:47
match matches.get_one::<String>("log_level") {
Some(log_level) => match log_level.parse() {
Ok(log_level) => {
set_max_level(log_level);
Copy link
Contributor

Choose a reason for hiding this comment

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

I would prefer this to happen at the call site instead of in this function. I think it's very easy to miss here.

@szokeasaurusrex szokeasaurusrex merged commit 358134c into master Oct 31, 2023
16 checks passed
@szokeasaurusrex szokeasaurusrex deleted the szokeasaurusrex/fix-config-log-level branch October 31, 2023 09:22
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.

Prints log message regarding SENTRY_PROPERTIES being loaded to STDERR ignoring --log-level
2 participants