Rufus

Thanks for letting me know. I haven't yet tested slf4j-timbre with timbre 5.0.0. I will investigate this issue ASAP

I have successfully reproduced this issue and have identified the root cause. It is a consequence of timbre renaming `:level` to `:min-level` in 5.0.0. When slf4j-timbre is compiled (against timbre...

@jsyrjala please try `0.3.20`!

That is very strange :confused: Please could you give me as much detail as possible about how your project is triggering this behaviour? A small test case would be ideal....

Hi guys, sorry the lack of timbre 5 support is causing annoyance. I have most of the code ready but have been very short of time recently due to work....

@awb99 yes! Please try out [the new snapshot](https://clojars.org/com.fzakaria/slf4j-timbre/versions/0.3.21-6-9f1d565-SNAPSHOT) and let me know if it works for you. I've not yet finished my overhaul of the integration tests, which should give...

Thanks, will look into this

Does putting apache.http.* in timbre's `:ns-blacklist` resolve the issue? I realise this isn't a proper solution but the blacklist *should* be checked before the call to `getStackTrace` occurs.

Yes I understand your concern. Thanks for confirming the blacklist works. Please could you now check timbre's `:ns-log-level` works? Put `:ns-log-level [["apache.http.*" :error]]` in your config, and check the calls...

I implemented this in https://github.com/fzakaria/slf4j-timbre/pull/36#issuecomment-562430641 because people had the opposite problem: they started using slf4j-timbre and suddenly the old slf4j default level of `info` was effectively lowered to `debug` (timbre's...