-
-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timbre crashing Cider workflow (?) #369
Comments
@gdulus Hi Paweł, thanks for the detailed info - that's helpful 👍 No obvious cause comes to mind from Timbre's end, but I can reproduce on my end with the deps I happened to have loaded: [com.taoensso/timbre "6.1.0"]
[cider/cider-nrepl "0.30.0"]
[nrepl "1.0.0"] and the Calling
Seems plausible that something in Timbre's implementation is tripping up CIDER or nrepl, etc. - but can't say off-hand. I'm actually not familiar with Am just focused on some other tasks for today, but will try take a look at this in the next couple days and come back to you. |
@ptaoussanis Thank you and no worries about the timeline |
@gdulus Hi Paweł, Interesting- so I just came back to this to investigate, and now I've been unable to reproduce the problem. Not sure if I'm missing something obvious. Would you please check the test repo that I've uploaded and see if you can reproduce the error on your side? Steps I've been trying:
Currently, that's triggering a successful ns reload for me. I see from your example that you're running a snapshot release of Cider? Thanks |
Hey @ptaoussanis In the next couple of days, I will do the same for the version with Cider 1.6.0 as this means I need to downgrade Doom Emacs to the version shipped with the stable version of Cider) |
I'm able to reproduce this error using the test repo without Cider. Hopefully the following steps make it easier to track down. Since Cider (and other editors that jack in) is adding
Then I ran In the repl:
I also tried changing versions of timbre in the test project:
|
@bclark-videra Hi Byron, thanks for the assistance on this! I can confirm that adding Will try investigate further. |
@gdulus @bclark-videra So it looks like the cause of the trouble was an update to one of Timbre's dependencies. Until the upstream issue can be fixed, you can temporarily work around the problem by adding the following dependency to your This will force the old dependency to be used, the same one that was included with Timbre v5.x. Apologies for the trouble, and thanks again for the report and assistance with debugging! |
Thanks for tracking down the underlying cause, @ptaoussanis, even though it wasn't in timbre. |
Will be addressed in a new Timbre release that I'll be pushing shortly, marking as done. |
There's currently an upstream issue with new Pretty versions, Ref. clj-commons/pretty#93 Until the issue can be fixed, Timbre will switch back to the last known-working version of Pretty.
There's currently an upstream issue with new Pretty versions, Ref. clj-commons/pretty#93 Until the issue can be fixed, Timbre will switch back to the last known-working version of Pretty.
Hey,
First of all, thank you for a great project. Second, this is more of a question than a bug submission at this moment.
I'm experiencing strange behavior when timbre is used as a dependency in my project. When working with Doom Emacs (Clojure + Cider), when timbre is required in a namespace, reloading all namespaces (cider-ns-reload-all) leads to the exception:
code used to test it:
I have tested this with all possible combinations of required namespaces and only timbre leads to these issues.
Cider repl:
my project.clj
The text was updated successfully, but these errors were encountered: