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

(maint) Finish the 2.4.2 release by merging master to develop #3614

Closed
wants to merge 3 commits into from

Conversation

gep13
Copy link
Member

@gep13 gep13 commented Jan 30, 2025

This back-merges the changes made to master during the release into develop.

gep13 and others added 3 commits January 22, 2025 11:58
Prior to this change, trace level logging was available to everyone.
However, due to the sensitive nature of some of the output, the
decision has been taken to restrict trace logging to only elevated
sessions.

When an attempt is made to use trace logging in a non-elevated session,
a warning will be shown, and no trace logging will be shown.  In
addition, if the -r option is in play, the warning about no trace
logging will go to the log file, but won't be displayed.
(#3604) Don't allow trace logging when not elevated
@gep13 gep13 requested a review from AdmiringWorm January 30, 2025 14:17
@gep13 gep13 self-assigned this Jan 30, 2025
Copy link
Member

@AdmiringWorm AdmiringWorm left a comment

Choose a reason for hiding this comment

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

LGTM

@gep13
Copy link
Member Author

gep13 commented Jan 31, 2025

Closing this to re-open with recent change on develop branch.

@gep13 gep13 closed this Jan 31, 2025
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.

3 participants