Fork me on GitHub
#cider
<
2024-01-15
>
vemv07:01:07

Have a great week cider

🚀 5
lassemaatta10:01:43

What might be wrong if cider-log-framework only lists logback and j.u.l. but not timbre? cider-version reports 1.14.0-snapshot

vemv11:01:01

Assuming cider-nrepl is latest as well (maybe your project / user config overrides it), I don't immediately know But it works to set it in .dir-locals or otherwise https://github.com/clojure-emacs/logjam/blob/6b370391f50b76149ffac608758ac8468428a459/.dir-locals.el#L8

lassemaatta11:01:01

I'm running with [cider/cider-nrepl "LATEST"] so I hope it's fresh enough 🙂

vemv11:01:42

You can check ~/.m2/repository/cider/cider-nrepl/ for good measure :)

lassemaatta11:01:22

0.43.3, 0.44.0, & 0.45.0 , so at least the latest has been fetched

vemv11:01:34

yeah surely it's in use LMK if simply setting cider-log-framework-name worked

lassemaatta11:01:05

Nope, I tried altering the variable directly from emacs, but couldn't see any effect. Well, perhaps there's just something broken in my setup, no need to debug further. I was just curious how the new log feature worked

vemv11:01:37

Were you following the https://docs.cider.mx/cider/debugging/logging.html? It describes a couple ways - which one had you tried? I understand it's not critical but it would help us to have things in a great state, and discoverable/usable

lassemaatta11:01:59

pretty much 1. (setopt cider-log-framework "Timbre") 2. cider-log-show 3. See "Log framework:" prompt in the minibuffer with Logback & Java Util Logging as choices (which conflicts what the guide says about not asking about the framework)

vemv11:01:05

Gave it another try, keeps working

lassemaatta11:01:22

I guess this has something to do with cider-sync-request:log-frameworks not returning anything related to timbre :man-shrugging:

lassemaatta11:01:59

our project is using timbre 5.2.1 from march 2022, so perhaps there's some requirement to use a more recent version?

vemv11:01:43

log-frameworks is dynamic - doesn't return a hardcoded list > our project is using timbre 5.2.1 from march 2022, so perhaps there's some requirement to use a more recent version? Seems a good call. Timbre and Encore often incur into incompatible changes. So maybe our require was failing, hiding the choice? Feel free to try latest

lassemaatta11:01:59

yeah, got it working with the latest 6.3.1 timbre. I can do a bit of bisecting to figure out the minimal version that works

🙌 1
lassemaatta11:01:27

it looks like 6.3.1 is the only version that works, I tried 6.0.0 and a few other version in between.

vemv11:01:05

We didn't use any crazy internal Timbre feature, probably it has more to do with the fact that Peter went on a big streak on all his projects, so probably a few breaking changes happened

vemv11:01:26

maybe :exclusions would work (favor your Timbre+Encore, exclude ours), feel free to inspect the dep tree (scratch that - for us Timbre is :provided , nothing should be pulled)