Proposal to reduce log level to debug

[sagoez]

This tracing doesn't actually provide any meaningful data other than signalling that this method was called (same as the saved user one). Can they be reduced to debug level? I could quickly prepare a PR for that.

Since you can’t delete the issue, I’ll repost the reply you deleted, since is clear you prefer to avoid public confrontation and modify comments to make you look better:

Thanks for the reply, but I don’t appreciate the condescending tone—it’s disrespectful and uncalled for, especially when we’re both capable of a straight-up discussion. Since it’s your library, it’s your call. Thanks for the input and appreciate your help.

[maxcountryman]

I don't like to make these sorts of changes because the tracing crate already provides an interface for configuring this on a per crate basis.

It's also a breaking change but one that is potentially less visible and therefore a bigger footgun, so to speak.

So without a really compelling reason, I have to decline the offer.

[maxcountryman]

I'm honestly a bit stunned that it isn't self evident why changing a log level in that way is a breaking change: it can very easily lead to a situation where a consumer no longer sees a message they were otherwise expecting to see.

Taking a step back, this isn't the right forum to explain tracing usage (please refer to their docs for detailed guidance) or indeed logging more generally and I'd invite you to take those questions to other forums to better understand those things.

Let me be crystal clear: this isn't about avoiding extra effort, it's about ensuring we don't break the library for consumers and asking consumers to use the tracing interface itself as it's intended to be used.