Skip to content
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

Error jacking in from CIDER/Calva using master version #136

Closed
laynor opened this issue May 9, 2021 · 1 comment
Closed

Error jacking in from CIDER/Calva using master version #136

laynor opened this issue May 9, 2021 · 1 comment

Comments

@laynor
Copy link

laynor commented May 9, 2021

I can run the app correcly, and can open a working cljs repl issuing

clj -M -m krell.main -co build.edn -r

at the command line.
However, when I try to start the repl from cider or calva, I get this error

   ReferenceError: Can't find variable: cljs

full stack trace here: https://gist.github.com/laynor/4944b74a36691b8c3be7bb852818fe87

The full project repo is here https://github.com/laynor/krelltest
I asked for help on clojurians, and the project appears to work on other machines. However, I verified with a colleague that's using the same system I'm using and reproduced the issue on his machine.
As a result of this issue, the cider repl is stuck at the user => prompt (clojure/java repl if I understand correctly) and never reaches the cljs.user => repl.

Here are my system details:
Os: Arch linux
Emacs: recent version compiled from sources (master). native comp enabled
Cider version: "CIDER 1.1.0 (package: 20210422.802) (Plovdiv)"
clojure --version: Clojure CLI version 1.10.3.822

java version: tried both openjdk version "1.8.0_292"and jdk 8 downloaded from the Oracle homepage.

Node version 14.3.0

This krell version is working for me: d0e1153.

I still haven't investigated what commit exactly introduces the issue.

@laynor laynor changed the title Error jacking in from CIDER/Calva using master version Error jacking in from CIDER/Calva using master version May 9, 2021
@swannodette
Copy link
Contributor

I believe this was a documentation issue only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants