Describe the bug
Logs contain trace level messages even though slack-log-level is set to 'info.
To Reproduce
Steps to reproduce the behavior:
Eval (setq slack-log-level 'info)
Switch to the *Slack Log - Team* buffer.
Note that it contains many trace level ping/pong log messages.
Backtrace
n/a
Expected behaviortrace and debug level log messages shouldn't be logged.
Screenshots
n/a
Environment:
OS: Debian Bullssye
Emacs Version: 29.x.x (built from git)
emacs-slack Version: git ff46d88, the latest as of this writing
Additional context
Log message buffers are unbounded, and the excessive logging (4 messages every 10 seconds per team) causes them to become unwieldy, consume unnecessary memory, and lag Emacs. They seem to grow at a rate of around 45mb/team/day.
Describe the bug Logs contain
trace
level messages even thoughslack-log-level
is set to'info
.To Reproduce Steps to reproduce the behavior:
(setq slack-log-level 'info)
*Slack Log - Team*
buffer.trace
level ping/pong log messages.Backtrace n/a
Expected behavior
trace
anddebug
level log messages shouldn't be logged.Screenshots n/a
Environment:
Additional context
Log message buffers are unbounded, and the excessive logging (4 messages every 10 seconds per team) causes them to become unwieldy, consume unnecessary memory, and lag Emacs. They seem to grow at a rate of around 45mb/team/day.