-
-
Notifications
You must be signed in to change notification settings - Fork 645
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
stacktraces don't show until cider-stacktrace is manually evaluated #586
Comments
I've also been having the same issue (for a while now). If I remove all Cask dependencies and .emacs.d configuration except that which pertains to CIDER, then stacktraces render fine without manually evaluating the file. Unfortunately I've been having a lot of trouble tracking down the exact culprit that's causing the conflict, but I'll take another look this evening. |
Not sure if it's the same thing, but I can't run a test until I evaluate cider-stacktrace.el manually and restart cider. If I don't do this, C-c, C-, gives me "Can't find nREPL middleware providing op stacktrace. Please, install cider-nrepl and restart CIDER". Maybe related, maybe not - I always get the following message on cider-jack-in: "Cannot decode message: ; CIDER 0.7.0alpha (package: 20140602.500) (Java 1.6.0_29, Clojure 1.5.1, nREPL 0.2.3)". |
@jeffvalk Could you have a look at this problem? Perhaps some autoload issue or something similar? |
I haven't been able to reproduce the stacktrace not showing up. If anyone has a minimal test case, that would be helpful. @bbatsov What I am seeing, though, is a consistent parade of |
The issue seems to be with installing
|
I haven't looked at this in depth yet, but something else is at play. I uninstalled |
Isn't this the same issue as #597? |
This seems to have resolved itself for me on the last few cider updates. The first exception doesn't get displayed, but subsequent ones do. |
Probably also fixes the related clojure-emacs#583 and clojure-emacs#586.
Probably also fixes the related clojure-emacs#583 and clojure-emacs#586.
Probably also fixes the related clojure-emacs#583 and clojure-emacs#586.
Probably also fixes the related clojure-emacs#583 and clojure-emacs#586.
Probably also fixes the related clojure-emacs#586.
Probably also fixes the related clojure-emacs#586.
Probably also fixes the related clojure-emacs#586.
I'm seeing an issue with stacktraces that causes them not to be shown until
cider-stacktrace.el
is manually evaluated. This is with cider installed from melpa using cask. As far as I can tell I only have one version of cider on myload-path
, and no out of date.elc
files.After evaluating an expression that causes an exception to be thrown, I see in
*messages*
:The
*cider-error*
buffer is made visible, but is empty.Turning on
debug-on-error
results in the following stack trace. I have been unable to get a stacktrace for thevoid-variable
error, which seems to be the root cause of the exceptions not displaying properly.After evaluating
cider-stacktrace.el
, evaluating a clojure expression that throws an exception gives this in*messages*
, but still displays the clojure exception correctly:The text was updated successfully, but these errors were encountered: