Closed jonashouben closed 1 year ago
hey @jonashouben , thank you from the community :)
Are you able to reproduce? is it an error related to a Discord update or something? I've tried to reproduce but on many clients works correctly. Just curious to know from what is caused
hey @jonashouben , thank you from the community :)
Are you able to reproduce? is it an error related to a Discord update or something? I've tried to reproduce but on many clients works correctly. Just curious to know from what is caused
Unfortunately not. As written by others in the issue, it only happens for some users. But I'm relatively sure it's the exception message, because that's the only place in MainLoop where it can cause the logger to throw.
@shardick maybe to clarify. The PR is fixing only the logging, not the logged error :)
Thank you for your contribution. The other loggers will be updated to match this before i push another release :)
Hey @Lachee, thanks!
As far as I noticed, the other loggers already have this behavior:
FileLogger: args.Length > 0 ? string.Format(message, args) : message
NullLogger: Nothing logged
Thanks! :)
Thank you for your contribution. This is now released in v1.1.1
✨🌟 🎉
Fixes #207.
The issue are this lines in RpcConnection. When either the Exception Message, or the Stacktrace contains a brace (for example "{").
I fixed it like in the FileLogger - only use the formatted version, when arguments are actually provided.