-
Notifications
You must be signed in to change notification settings - Fork 27
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
ansi
namespace attempts to require nrepl.core
, causes exceptions in some cases
#93
Comments
This is almost certainly related to the code in the |
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.
Looking into this now; I've wired up your sample project to the org.clj-commons/pretty source and can reproduce your error. When I comment out the |
Using |
cider-nrepl
, minimal repro includedansi
namespace attempts to require nrepl.core
, causes exceptions in some cases
That's great news Howard, thanks so much for your help on this - and your work on Pretty in general! Cheers :-) |
@hlship Hi Howard, thanks for all your work on Pretty!
I have an issue to report, involving an apparent interaction between recent versions of Pretty, and cider-nrepl.
Quick info:
[io.aviso/pretty "1.3"]
and[io.aviso/pretty "1.4.4"]
, but not with[io.aviso/pretty "1.1.1"]
.cider-nrepl
, nothing else - so it looks like this might be a problem either with Pretty, or that Pretty is triggering an issue with cider-nrepl.Instructions to reproduce
lein repl
(require '[beholder.handlers] :reload-all)
On my system this reliably generates the following error:
Do you have any ideas what might have changed since 1.1.1 to cause this?
I couldn't find any related open or closed issues.
Thanks for any assistance! Cheers :-)
The text was updated successfully, but these errors were encountered: