-
Notifications
You must be signed in to change notification settings - Fork 177
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
bump suitable to fix #643 #644
Conversation
waiting for clojars to be up again... |
Same here. :-) |
Looking into the test errors... |
I'm running the tests locally but its not related to you. |
Hmm I believe there is also an issue with my fix. Apparently calling |
I was incorrect. The tests fail due to upstream in
|
@dpsutton Hmm, that's weird. I think the relevant tests were passing for me last time I checked them. I'll look into this after Clojure/south. |
Got it. Let me know when you manage to track this down. |
So I found the root cause but don't know how to fix it yet. cljs.repl.node uses a hand-made (not via a dynamic var but the thread name) thread-local buffer to store evaluation results (https://github.com/clojure/clojurescript/blob/master/src/main/clojure/cljs/repl/node.clj#L127). The thread that completions are computed in does not seem to be the same as the original thread for creating the repl env (names are something like So when suitable tries to eval we hit a hard nullpointer exception. I could try to add custom code for node here but this seems just a hack on a hack. Any idea what best to do here? |
Well, the way I see we either add custom code or we ignore |
- nodejs would throw nullpointer exception on first completion due to repl-env not being initialized
The issue should be fixed now. |
Thanks! I'll cut a new release later today. |
not being initialized
Before submitting a PR make sure the following things have been done:
Note: If you're just starting out to hack on
cider-nrepl
you might findnREPL's documentation and the
"Design" section of the README extremely useful.*
Thanks!