-
Notifications
You must be signed in to change notification settings - Fork 784
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
[Merged by Bors] - Increase logging channel capacity #1570
[Merged by Bors] - Increase logging channel capacity #1570
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, would be interested to see if @paulhauner has any thoughts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. From the size of the overflows I've seen 2048 should easily cover it.
…ease-logging-channel-capacity # Conflicts: # Cargo.lock
bors r+ |
## Issue Addressed #1464 ## Proposed Changes Increase the slog-async log channel size from the default of 128 to 2048 to reduce the number of dropped logs. ## Additional Info
Pull request successfully merged into master. Build succeeded: |
## Issue Addressed sigp#1464 ## Proposed Changes Increase the slog-async log channel size from the default of 128 to 2048 to reduce the number of dropped logs. ## Additional Info
Issue Addressed
#1464
Proposed Changes
Increase the slog-async log channel size from the default of 128 to 2048 to reduce the number of dropped logs.
Additional Info