You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like there's a hard coded limit of 30 log messages before logging gets suppressed.
It may be useful if there's an option to control this limit and/or remove it entirely. (the point of a log, after all, is to have a record of all issues that arise)
Thanks!
Which application of Transmission?
transmission-daemon
Which version of Transmission?
4.*
The text was updated successfully, but these errors were encountered:
@ckerr If you are ok with the idea, this is pretty much straightforward thing to do and may be labeled with "good first issue".
Notes for anyone wanting to implement this:
Add some new uint64_t/size_t pref with name like "log message max repeat".
Setting this pref to 0 means no limit at all.
Default compiled-in value must be zero, to disable MaxRepeat with cli tools like create, show, etc.
Default value for daemon is debatable, some pretty low limit like 30 is ok, but daemon at least allows you to override compiled in value with settings.json.
Default value for clients is debatable, but also should be overridable with settings.json.
What is the issue?
It seems like there's a hard coded limit of 30 log messages before logging gets suppressed.
It may be useful if there's an option to control this limit and/or remove it entirely. (the point of a log, after all, is to have a record of all issues that arise)
Thanks!
Which application of Transmission?
transmission-daemon
Which version of Transmission?
4.*
The text was updated successfully, but these errors were encountered: